Not a pro by any means but not a newb either. but after updating to 902 when I refroze stuff I think I froze something you're not supposed to and now it won't complete boot... how do I fix this? There must be some way to either unfreeze manually via PC or even flash over it. I just need to be functional again. Ugh. I was halfway well versed in original Droid flashing and using the PC but pretty new to the bionic.
Thanks guys!
well, tried to use releasedroot to restore my system back to .588, it failed and now all I get is AP Fastboot Flash Mode (s) (Flash Failure)
0A.61
in the releasedroot thing it said something about Infopfresh failure when it tried to restore....
any help?? please? i'm hoping to god its not totally bricked beyond all possibility of fix....
anyone in SE Michigan willing to help a guy out? willing to cover expenses for time.
Thanks again,
Steve
hmmmm, think i might have fixed this.... thank god there are some folks smarter than myself in this world.
read through a lot of posts, got the regular recovery to work, then had to fix the flashfailure.... looks like i even still have root. now, to get back to all the same settings i had before.... (and be a little more diligent and pay attention as to what things I'm freezing).
thanks guys!!
I think using releasedroot on 902 screws things up. I got stuck in fastboot after using it. Had to manually flash the images to get her
to boot.
Sent from my DROID BIONIC using Tapatalk
MSUICEMAN said:
hmmmm, think i might have fixed this.... thank god there are some folks smarter than myself in this world.
read through a lot of posts, got the regular recovery to work, then had to fix the flashfailure.... looks like i even still have root. now, to get back to all the same settings i had before.... (and be a little more diligent and pay attention as to what things I'm freezing).
thanks guys!!
Click to expand...
Click to collapse
Reading, generally, gets you thru
Related
Earlier my boyfriend tried to update my phone and we had errors. previously had cyanogen's mod working fine, but when we put AOSP_1.6_DRD20_ExpPack_v2.3.3 on it, we had errors galore. Now, I figured he was asleep and i'd try to factory restore it, and now i am stuck on the G1 screen.....and have no clue what to do, seeing as i think i pretty much screwed my phone...if anyone can help me ( in lamens terms ) that would be wonderful...thanks in advance...
efaith1983 said:
Earlier my boyfriend tried to update my phone and we had errors. previously had cyanogen's mod working fine, but when we put AOSP_1.6_DRD20_ExpPack_v2.3.3 on it, we had errors galore. Now, I figured he was asleep and i'd try to factory restore it, and now i am stuck on the G1 screen.....and have no clue what to do, seeing as i think i pretty much screwed my phone...if anyone can help me ( in lamens terms ) that would be wonderful...thanks in advance...
Click to expand...
Click to collapse
Can you boot into recovery?
I feel I've made a terrible (and stupid) mistake. I decided to unroot my phone from cyanogen roms. I read a how to guide that I guess was outdated because now I have android 1.0 firmware. The guidw was [how to] unroot by tubaking182 (absolutely zero offense to him, not his fault, I'm stupid, etc etc.) So I now have stock version 1.0. There's no check for system updates under about phone in settings so I can't do that. There are file manager apps that I could use to rename the necessary updates into update.zip, but there's no apps available like download crutch so I can download them. I also can't enter recovery. It gives me a triangle with an exclamation inside next to a image of a phone and that's it and I have no idea how to install an update without recovery mode. As I'm sure you've noticed by now, I'm the epitome of newb and feel free to laugh at my failure. I just really need someone to help me and would be eternally grateful. In all likelihood, I'll need step by step instructions on what to do. I know this is a lot to ask and I've really done nothing to earn this help... I really just need assistance. Thank you to anyone who helps me in advance
Not to be an asshole and say "Shoulda Coulda Woulda" but you really should have done your research before embarking on bricking your phone.
ItsAndroidsWorld had many videos on You Tube. Look for ones on how to root, then how to install the death spl, then look for the ones with Super D or FastTest .. as it seems as though they are probably the best roms for everyday use at this point.
I've found that using these videos via You Tube is the easiest way to go.
Good Luck.
^^^ ABOVE POST stolen from another similar thread.
psyko-m1 said:
Not to be an asshole and say "Shoulda Coulda Woulda" but you really should have done your research before embarking on bricking your phone.
Click to expand...
Click to collapse
he didn't brick his phone, don't scare him
To OP: The same happened to me when I was a n00b at this ****.
Dude, google is your friend.
Calm down.
tsk tsk tsk.....Im gonig to say this....WRONG SECTION
but I will be nice as well. just find the updates on google from 1.0 to 1.5 and oh yeah to get back into recovery from the triangle withthe !...alt L...but if you somehow brick ya phone youe fault not mine next time do ya research before you mess with ya phone
Technically speaking he is in a DEFCON 2 "Brick" situation.
Sorry.
psyko-m1 said:
Technically speaking he is in a DEFCON 2 "Brick" situation.
Sorry.
Click to expand...
Click to collapse
Well he's in the wet cement
SeEsAw12 said:
Well he's in the wet cement
Click to expand...
Click to collapse
Or...
You are late for work and have a flat...
click on this http://theunlockr.com/category/howto/android_how_tos/htc-mytouch-3g-magic/:cool:
remove the cool http://theunlockr.com/category/howto/android_how_tos/htc-mytouch-3g-magic/
this website should help you get back on track and you just need to download the nbh file to get it back to cupcake
BUT 0MGAWWZZZ N00BZORZ DO3S 1.0 HAVE A DA SENSE RAOM???
in all seriousness, there's nothing actually wrong with your phone. You completely unrooted it. By following the aforementioned instructions, it'll be easy to reroot and update. What I DO find weird is why you're not getting 1.5 OTA...
although i hate when people post in the wrong section - im in a good mood this morning
http://zenthought.org/content/project/flashrec
not sure if it works in 1.0 - it should as it uses a rather old bug to do so
Easy as pie...just follow the guide in my sig.
=)
To those who say I bricked it, I know that's not the case it still works so I obviously didn't brick it... not that fail thankfully.
To thenameismax, AHA! I did not know about alt+l retrieving text so thank you thank you thank you. I just need to get the necessary updates and copy them to sd card root, rename update.zip/install one at a time... I think lol
Thanks again to all who helped and sorry about the wrong section. When I was rooting, it was in development. I assumed that unrooting would be too and therefore problems with that... further fail.
afiellerddr said:
To those who say I bricked it, I know that's not the case it still works so I obviously didn't brick it... not that fail thankfully.
To thenameismax, AHA! I did not know about alt+l retrieving text so thank you thank you thank you. I just need to get the necessary updates and copy them to sd card root, rename update.zip/install one at a time... I think lol
Thanks again to all who helped and sorry about the wrong section. When I was rooting, it was in development. I assumed that unrooting would be too and therefore problems with that... further fail.
Click to expand...
Click to collapse
yeah man no problem. good luck.
Don't do anything. In a day or two you get an OTA update.
You can force the update like people have mentioned, but as long as you can hold off for a day or two you dont need to.
BTW, at some point you will see the E or 3G icon downloading like crazy and you dont know why. It is downloading the update. Stay away from task killers and in my experience it is good to be around wifi.
Just relax.
Sent Move Request
I need some ideas on how to fix my phone. I used to flash new roms all the time but a few weeks ago I started having problems.
When trying to load a new rom my phone would get hung at the multi colored X. Then once I got a rom to stick I would get lots of force closes when I hit the settings button.
I'm tired of dealing with it but I'm not sure how to fix it. Here are two Logcats of the phone stuck at the mulit colored X.
I would appreciate the help at getting my phone back to normal.
Logcat 1
Logcat 2
im not a expert but try unlocking ur bootloader and uploading all the update files from 2.2 froyo or something that helped me unbrick my almost brick
I would try passimg before fastboot flashing anything. If you want to know how to passimg it's in the wiki under unroot restore.
hitmanre said:
im not a expert but try unlocking ur bootloader and uploading all the update files from 2.2 froyo or something that helped me unbrick my almost brick
Click to expand...
Click to collapse
Thanks a ton! Your suggestion lead me to this thread.
http://forum.xda-developers.com/showthread.php?t=717870
I've spent hours trying everything I could to fix it. My phones been half busted for about 2 months.
I didn't think it would but it did. It brought my phone back to stock 2.1. I grabbed z4root to root it, then reflashed hboot, radio and went back to CM7 nightly. All is well with the world again.
Dude Random21 said:
I would try passimg before fastboot flashing anything. If you want to know how to passimg it's in the wiki under unroot restore.
Click to expand...
Click to collapse
Thank you, I just got it fixed using the method you described.
no problem, it sucks to have that feeling in ur stomach that u broke a 500$ device, thats why i like helping around while i can
Good Evening everyone. As the title says i need help.
I have had my phone rooted fine in the past but went ahead and did the .893 update wich is where something went screwy. It booted fine after doing the .893 update however after doing a reboot it would not boot. just stayed at the M dual core. I think something went wrong on the update because all my apps were still there when it did boot.
So i tried doing a return to stock using the RSD lite program..that fails right away no matter what i do.
So i went and tried to do the One click fastboot system restore program.
Now when i did that the INFOpreflash validation failure showed up however everything else went through fine. the phone reboots and everything works just not great the signal strenght is very low.
The version that got installed says 5.5.1_84_dbn-55. So i try Pete's root method and it go thru to step 2 but then fails at rebooting for the second time saying it could not get root via local.prop.
If anyone could please help me get back to normal stock it would be much appreciated
Not to be a jerk, but did you READ any thread on here before you did this??
1) Unless you used p3droid's forever root method, you're done. No root.
2) Wrong forum - should be in general
3) RSD won't work.
4) I don't feel sorry for you. You should have researched more. If you would have taken the time to read a few threads, you would have known the answers before you did this.
Enjoy your new build - you'll be with it for awhile.
Sent from my DROID BIONIC using xda premium
P.S. You are stock now.
Sent from my DROID BIONIC using xda premium
harsh, but true...has nobody heard of google...?
Sent from my DROID BIONIC using XDA App
dubsx said:
harsh, but true...has nobody heard of google...?
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Or XDA?
Sent from my DROID BIONIC using xda premium
I did do the forever root and i did read that thread three times b4 i attempted it. I know i am stock. I checked the mount_ext3.sh file and those three lines are no longer there.
And i also have googled this but cannot find an answer hence why i am asking on here..all options i have found to try to reroot have failed
that too, haha...
Sent from my DROID BIONIC using XDA App
Sidewind75 said:
I did do the forever root and i did read that thread three times b4 i attempted it. I know i am stock. I checked the mount_ext3.sh file and those three lines are no longer there.
And i also have googled this but cannot find an answer hence why i am asking on here..all options i have found to try to reroot have failed
Click to expand...
Click to collapse
Well, you didn't list that in the OP.
At this point, I don't know. Here is all I got: enter stock recovery and wipe everything. Reboot. Cross your fingers.
Sent from my DROID BIONIC using xda premium
mistawolfe said:
Not to be a jerk, but did you READ any thread on here before you did this??
1) Unless you used p3droid's forever root method, you're done. No root.
2) Wrong forum - should be in general
3) RSD won't work.
4) I don't feel sorry for you. You should have researched more. If you would have taken the time to read a few threads, you would have known the answers before you did this.
Enjoy your new build - you'll be with it for awhile.
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
Not to be a jerk...(goes on to be a jerk)
I love when people preface their statements with stuff like "I'm not racist BUUUUTTT". It's like a contrition...but in reverse!
quentin0 said:
Not to be a jerk...(goes on to be a jerk)
I love when people preface their statements with stuff like "I'm not racist BUUUUTTT". It's like a contrition...but in reverse!
Click to expand...
Click to collapse
Sometimes the truth hurts. He messed up. Don't shoot the messenger.
Moderator Message
Breathe in, breathe out!!!!
I'll breathe when this .893 goes through and I keep root
There is also some very seriously contradictory info in the OP. While castigating him for being a noob did anyone notice that he claims to have flashed the update and then reverted to stock?
This is impossible from our current understanding of how the bootloader works.
More information about the exact steps followed and the exact results at each step would be very helpful to try and figure out what really happened.
OK?
Less heat and more light...
I just got a little frustrated, as every time I open XDA today I see the same/similar post.
Cell - I didn't see in the OP where he said he flashed back. I read where he tried, but I didn't see any mention of 896.
I could not get the .893 to boot after a reboot so i used the One-click fastboot restore and root which brought back to stock but also made it so that i can no longer root. It fails every time on the local.prop process saying adb could not get root access. I did try the stock recovery and still no go. I also tried the adb fix that was posted to remove local.prop but when i tried it says file not found. I have rooted and messed with many phones in the past from Droid 1 and up and this is the first problem that i couldnt solve so as i said any help would be appreciated.
Oh and i have also tried to unroot it..it also fails at adb not being able to gain root access
Sidewind75 said:
I could not get the .893 to boot after a reboot so i used the One-click fastboot restore and root which brought back to stock but also made it so that i can no longer root. It fails every time on the local.prop process saying adb could not get root access. I did try the stock recovery and still no go. I also tried the adb fix that was posted to remove local.prop but when i tried it says file not found. I have rooted and messed with many phones in the past from Droid 1 and up and this is the first problem that i couldnt solve so as i said any help would be appreciated
Click to expand...
Click to collapse
This isn't going to help your current issue, but how long did you let it sit (after installing 893) before you decided it wouldn't boot? I ask because the guy who was ballsy enough to do it here said the first boot takes about 7 minutes.
EDIT: Nevermind - mine booted in 2 minutes.
it was fully booted and operational. i just did a power off after a half our or so and power back on and it just sat at the M dual core screen...i dont know why it would not boot. I tried pulling the battery. taking out the sim card and all that. the only thing that would get it booted was the One-click fastboot restore and root program so I at least have a working phone but for some reason the signal strength is horrible
Sidewind75 said:
it was fully booted and operational. i just did a power off after a half our or so and power back on and it just sat at the M dual core screen...i dont know why it would not boot. I tried pulling the battery. taking out the sim card and all that. the only thing that would get it booted was the One-click fastboot restore and root program so I at least have a working phone but for some reason the signal strength is horrible
Click to expand...
Click to collapse
Try to do the fastboot again and root it through there. Or, if you did that already (root in fastboot restore) try rooting afterwards.
Might sound dumb, but did you forget to save the chmod changes to the build file? It's a fairly easy mistake and it is the only thing I can think of.
tghockey07 said:
Might sound dumb, but did you forget to save the chmod changes to the build file? It's a fairly easy mistake and it is the only thing I can think of.
Click to expand...
Click to collapse
yes I did and i checked it twice after making sure root explore was closed reopened and checked the file the chmods where there...but now they are not. and seeing as how i cant root i cannot get them back on it
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