Hello fellow Bionic users!
I have a bit of a dilemma that I'm not sure on what to do.
Tried using the FXZ method. My phone goes to Safestrap mode and that's it. No boot to OS at all. So unless my ignorance is that bad, I don't think it works.
I was looking at the Fastboot method, but I cannot find any working links.
TL;DR Device is soft-bricked, or maybe even hard-bricked. But I'm determined to figure it out. Just looking for some more technical help.
TiA!
Go here and use Timmy10shoes files if needed...http://androidforums.com/bionic-all-things-root/480176-how-flash-5-5-893-5-9-902-rsdlite.html
Related
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
Hey every one I'm in desperate need of help. Its been about a week and seeked help from other places and you guys are my last hope. As the title states, My '12 model Nexus 7 is suck in a boot loop after trying to update. I really didn't want to, but the darn notifications just would not stop. I've cleared the cache in recovery mode as of right now.
My main thing is to be able to save all my data before flashing the device. I hear there are ways to still root the device while stuck in a loop and recovering data then. True? I don't know, I just want my pictures and important files. Please, I beg for all your help and I will be greatly thankful for any ideas. Thanks in advance.
My Nexus is completely stock just so everyone knows.
Tawcoma26 said:
Hey every one I'm in desperate need of help. Its been about a week and seeked help from other places and you guys are my last hope. As the title states, My '12 model Nexus 7 is suck in a boot loop after trying to update. I really didn't want to, but the darn notifications just would not stop. I've cleared the cache in recovery mode as of right now.
My main thing is to be able to save all my data before flashing the device. I hear there are ways to still root the device while stuck in a loop and recovering data then. True? I don't know, I just want my pictures and important files. Please, I beg for all your help and I will be greatly thankful for any ideas. Thanks in advance.
My Nexus is completely stock just so everyone knows.
Click to expand...
Click to collapse
Can you access the bootloader? The thing is, in order to root Nexus 7 you need to unlock it via fastboot. Unfortunately unlocking the bootloader implies the act of wiping all data on your tablet.
I'm not sure if stock recovery let you use the adb (I've never used it), but if it does you can use it to pull all your photos and important files out of it before flashing a new image (usually, on CWR, you can do this using a "sideload" option in recovery...something like "update via sideload").
Without an unlocked booloader there aren't many things you can do to save your Nexus 7...
Similar Issue with Me
Tawcoma26 said:
Hey every one I'm in desperate need of help. Its been about a week and seeked help from other places and you guys are my last hope. As the title states, My '12 model Nexus 7 is suck in a boot loop after trying to update. I really didn't want to, but the darn notifications just would not stop. I've cleared the cache in recovery mode as of right now.
My main thing is to be able to save all my data before flashing the device. I hear there are ways to still root the device while stuck in a loop and recovering data then. True? I don't know, I just want my pictures and important files. Please, I beg for all your help and I will be greatly thankful for any ideas. Thanks in advance.
My Nexus is completely stock just so everyone knows.
Click to expand...
Click to collapse
Well, unless you are unlocked already this may not work. I had a similar issue but my Nexus was unlocked and rooted. I was playing around with the OTA 4.3 release and got stuck in bootloop and no adb when trying to reroot. What I had to do was use Wug's toolkit and do the BACK TO STOCK 4.2.2 with the current status set to soft-bricked/bootloop. (I also had to plug and unplug from the computer repeated times in order to get adb and fastboot to work while within this script). That allowed me to get unstuck. I then had to use Nexus 7 Toolkit to regain root as Wug would not work for some reason. I am currently back on my favorite 4.2.2 custom rom. Again, you might have to be unlocked already and you will loose your data. This is why i use DRIVE and SKYDRIVE to store backups. You never know what might happen with a device with no removable storage.
As far as the USB driver, the only thing that worked for me was to load the android sdk onto my computer. The other methods failed at this point. Again, crazy stuff was going on.
However, I was able to get to the file system when connected to the computer and could see my media file. My N7 was doing some wonky stuff.
Try using the Nexus Root Toolkit (by Wugfresh), there is an option to Restore+Unroot that will put the device back to pristine condition. When you select that there are two other options that go along with it, one is the table is booting normally, the other is stuck in a boot loop. Select the option that you are stuck in a boot loop and hopefully you can get yourself back to a working tablet, then root and do all the other stuff.
Alright im gonna explain my exact situation here and hope to god you guys can help me...
My girl is out of town and im sure is getting ****ing irate by now considering our means of communication are our phones..
Today i was looking into "milk" streaming for samsung, it told me to edit "Build.Prop" in the system file to make it appear as a samsung galaxy s4, specically..
Code:
ro.product.model=Galaxy S4
ro.product.brand=Samsung
ro.product.manufacturer=Samsung
I did this as was stated, i made the backup but i decided to reboot my phone.. which in turn bricked it, i see the Motorola logo when it turns on but then it goes to a black screen (if its relevant.. i feel like its still running but the screen wont display) i decided to go into recovery and factory reset it (again to clarify a bit, XT1060 running android 4.4, rooted with supersu and Jcase's method.) so at this point.. im stuck with a phone i have no way to replace at the moment, (still under warrenty, but was rooted so its iffy if they will or not.. especially considering i messed with a system file. cant afford the monetary risk to find out).. im stuck in only being able to get to bootloader/recovery.. cant start up the phone to the actual OS. cosider factory settings where usb debugging isnt possible to enable at the moment, is there ANY POSSIBLE way i could fix this and get it to a working state again? if anyone can help me here they will have my undying gratitude and ill do anything i POSSIBLY can to help them.. :/ thanks to all who make the effort to do so
Did you try a factory reset?
Next, you might just need to restore stock image with fastboot or rsdlite. You will need the proper carrier version you were currently on and same android version.
For fastboot ... See this guide and the restore stock section.
http://forum.xda-developers.com/showthread.php?t=2603358
And rsdlite has a thread in development.
You may lose all data, pics, music...etc. At least with the rsdlite way. I think. Its been awhile. I might be wrong about this.
Other than that....not sure how else you can fix it myself. Maybe wait a bit to see if you get more suggestions. Good luck!!
You may have to download the Verizon 4.4 SBF, and fastboot flash system to fix it, however, I don't know how this will impact your root and write protection disabled (assuming you used SlapMyMoto and MotoWpNoMo).
Hello everyone. I don't know a whole lot about HTCs, but I want one badly after rooting one for a friend. I have another friend that tried to root a 626 verizon version on 6.0 with a tutorial on the HTC site for a different phone (he didn't ask me, I assure you and I gave him a scolding) and his recovery is broken. He's not sure if he fastbooted TWRP onto it or not but I think he may have without unlocking the bootloader. Is there possibly a stock recovery that he could fastboot back on there? His system is still booting and adb and fastboot are still connecting, I just don't know if there is a stock recovery for his and since it's not mine, I don't want to spend hours looking. Also, he doesn't have a lot of understanding yet as this was his first root attempt so I'm asking for him. Thanks so much for any help with this. Any Android down makes me sad. I told him if he wants to root get something non-verizon. He just ordered an unlocked S5 and I told him thats a very good place to start. But, if possible, I hope we can get his HTC right again. I also told him not to factory reset EVER if we can't get his recovery back. Thanks so much for any help.
Hoping someone has a minute to inform me of how to repair my bionc from vzw. I had safestrap 3.73 on and upgraded to safestrap 3.75 with rooted stock moto image from way back when. I saw a lineage 14.1 image install and thought what the heck. couldnt hurt. so I did a nandroid backup with compression to the external sdcard of all partions(securedata,system,data,webroot). did another backup to the internal partion. had the prefrered storage device as intenrnal memory. I then wiped system-data-cache-dalvik and left webtop and secure partion alone. I tried unlocking the bootloader from moto bye getting my device info in fastboot but fastboot did not understand the "oem" command. I remember I was able to boot multiple boots but it had to share the same kerenl so I firgured what the the heck. I could always safestrap back and restore if lineage os failed. my mistake. I assumed. I then found there was a file called moto-fastboot but not sure if it was any different than google's fastboot. before I get things anymore screwed up I thought I would kindly ask for someone to throw me a lifepreserver because I wanna get me and the brick outta the water.
anyhow now it tries to boot, reboots and gets a dead android bmp screen. I can get into fastboot still
any help greatly appreciated. I have not used rsdlite in a while nor can I find the cdma_targa_9.8.2O-72_VZW-22_1ff.xml.zip file to manually doit through fastboot. (my own diagnoses but hey I'm an advnace noob with super cape and no superpowers)
yes my weaknesses are no-fear and stupidity based on not reading, reading and then reading a little more.
rp201 said:
Hoping someone has a minute to inform me of how to repair my bionc from vzw. I had safestrap 3.73 on and upgraded to safestrap 3.75 with rooted stock moto image from way back when. I saw a lineage 14.1 image install and thought what the heck. couldnt hurt. so I did a nandroid backup with compression to the external sdcard of all partions(securedata,system,data,webroot). did another backup to the internal partion. had the prefrered storage device as intenrnal memory. I then wiped system-data-cache-dalvik and left webtop and secure partion alone. I tried unlocking the bootloader from moto bye getting my device info in fastboot but fastboot did not understand the "oem" command. I remember I was able to boot multiple boots but it had to share the same kerenl so I firgured what the the heck. I could always safestrap back and restore if lineage os failed. my mistake. I assumed. I then found there was a file called moto-fastboot but not sure if it was any different than google's fastboot. before I get things anymore screwed up I thought I would kindly ask for someone to throw me a lifepreserver because I wanna get me and the brick outta the water.
anyhow now it tries to boot, reboots and gets a dead android bmp screen. I can get into fastboot still
any help greatly appreciated. I have not used rsdlite in a while nor can I find the cdma_targa_9.8.2O-72_VZW-22_1ff.xml.zip file to manually doit through fastboot. (my own diagnoses but hey I'm an advnace noob with super cape and no superpowers)
yes my weaknesses are no-fear and stupidity based on not reading, reading and then reading a little more.
Click to expand...
Click to collapse
Howdy! Sorry it's taken three months for your question to get any attention. Bionic forum's pretty dead, eh? I'm amazed it's still an officially supported Lineage device. Go team!
Sadly, the no one ever found a bootloader unlock, as a fellow informed me here two years ago. Unless some clever hacker happens upon a Bionic and decides to crack it for kicks, it's not likely to happen. But at least we have SafeStrap and Lineage!
You may know this already, but you didn't mention it in your post, so I'll go ahead and say: when installing a ROM like Lineage on the Bionic with SafeStrap, you need to install it on ROM Slot 1, not the Stock ROM Slot. I imagine that might be why you bricked your phone (I've done it myself a few times too ).
Now that I've given you the skinny on the Bionic's limitations, let's see if we can't get you back afloat. Whenever I bricked mine, I never used RDS Lite—I found a utility called House of Moto. You can find the home page here, but you'll need to create an account to see the important stuff and the downloads (you'll also need to install Java). But if you're more familiar with RDS Lite, feel free to use that instead
System images for the Bionic are hard to find nowadays. I seem to have found one link to an article with a direct download link to an update file at the bottom, which I'll link to here. Whether the update file is the same as an FXZ file RDS Lite/House of Moto requires, I'm not sure. Give it a try and see how it goes! If not, I may have a copy of the file on my old computer at my parents' house. If the linked update file doesn't work, I'll see if I can't get ahold of my image file.
Finally, if you do happen to get things up and running happily, I've got a list of optimizations that help Lineage run more smoothly.
Best of luck! :good: