OS is missing, will not take previous ROM. Droid Turbo (quark) - Verizon Motorola Droid Turbo Q&A, Help & Troublesh

So, here I am asking for help on this poorly supported device because I currently have a device that will not take trusted ROM's that I have flashed previously. The backstory behind this predicament starts with trying to flash a new ROM that suggested to wipe the cache before flashing, so I did. In the middle of this process i got impatient and restarted to bootloader. After attempting many times to flash my normal setup, it would not take anything so I factory reset the phone and now it sits. I have tried sideloadingand my command prompts does not recognize my commands. I do have a tweak drive (OTG) with the latest version of my device on the drive but it will not agree with anything I put forward like an intolerable toddler.

MrJudo said:
So, here I am asking for help on this poorly supported device because I currently have a device that will not take trusted ROM's that I have flashed previously. The backstory behind this predicament starts with trying to flash a new ROM that suggested to wipe the cache before flashing, so I did. In the middle of this process i got impatient and restarted to bootloader. After attempting many times to flash my normal setup, it would not take anything so I factory reset the phone and now it sits. I have tried sideloadingand my command prompts does not recognize my commands. I do have a tweak drive (OTG) with the latest version of my device on the drive but it will not agree with anything I put forward like an intolerable toddler.
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. To get you the help you need, I'm going to move this thread to your device's Q&A forum. Good luck!

The_Merovingian said:
Greetings,
Thank you for using XDA Assist. To get you the help you need, I'm going to move this thread to your device's Q&A forum. Good luck!
Click to expand...
Click to collapse
Assuming that you know how to use fastboot. You can probably flash the system image (more like system img chunks) to get you out of that state. I'm not saying that'll fix it, but you should definitely try out.
Also as a side note, wiping cache can sometimes take a while so NEVER reboot your device while doing so. (But I'm sure you learned that by now.)

Clearing the cache on my Turbo XT1254 took almost a half an hour. I googled it while it was clearing because I thought that it locked up.

Related

[Q] Any way to put Safestrap Recovery on without APK?

My Droid 4 is bricked, but out seems to me that if I could get safestrap recovery in, I could boot any working "safe" ROM and leave my non-functioning "unsafe" system alone until the day a fastboot image becomes available.
The only wrinkle is that since the current OS is bricked, I can't load the Safestrap recovery via Apk. Is there any way to load it using one of the remaining capabilities in the phone (normal recovery, fastboot, etc.)?
I definitely don't have the full technical ability to answer your question, but to get the ball rolling:
Can you get adb up and running? If you can't, my guess is no... If you can, somebody who knows more than I do might be able to get you going...
Call Motorola or the wireless vendor where you got your phone and play dumb.
How did you brick your phone?
I bricked mine the first time by restoring a saved stock rom that I had made. Little did I know, but I got the webtop save mixed up, and totally soft-bricked my handset.
Safestrap is a good alternative to having nothing, but you should read everything there is to know about it before installing it. Conceptually, it doesn't share a whole lot with the original clockworkmod recovery.
RueTheDayTrebek said:
Call Motorola or the wireless vendor where you got your phone and play dumb.
Click to expand...
Click to collapse
I've thought about it. (1) there's stuff on the internal "sdcard" (/sdcard, as distinct from the removable real SDC) I'd like to recover if I could, so restoring the phone I have right now is preferable, unless restoring from a fastboot recovery wipes /sdcard).. and (2) I hate the idea of "cheating" on a warranty for a self-inflicted product failure, both on the ethics of it and on the remote possibility I could get caught.
How did you brick your phone?
Click to expand...
Click to collapse
I had safely rooted the phone (Droid 4 Utility is awesome) and installed Titanium Backup Pro. I was playing around with freezing bloatware, deleting bloatware, and the like... the last thing I did before rebooting and never coming back was integrating system application dalvik cache into the ROM and then undoing that integration. But I can't be sure that was the killer, since I hadn't rebooted for a while before that... one of the other changes earlier could have been it.
Safestrap is a good alternative to having nothing, but you should read everything there is to know about it before installing it. Conceptually, it doesn't share a whole lot with the original clockworkmod recovery.
Click to expand...
Click to collapse
Yeah, I recognize it's a very different world because of the locked bootstrap, so I'd obviously have to adapt to the differences, but just the ability to get some use out of the phone before the fastboot recovery leaks would be a good start. My needs are not great. Something besides repeated reboots ("Droid..." every 10 seconds until the battery runs flat) would make me happier than a pig in slop.
podspi said:
I definitely don't have the full technical ability to answer your question, but to get the ball rolling:
Can you get adb up and running? If you can't, my guess is no... If you can, somebody who knows more than I do might be able to get you going...
Click to expand...
Click to collapse
Yeah. The times I've tried, the phone never boots to the point that the USB debugging driver on the PC ever sees the phone ("adb devices" lists nothing).
About the only interaction I can get to is to force the phone into fastboot and plugging in with the fastboot USB driver on the PC. RSD Lite does see the phone then. Too bad I don't have a fastboot recovery to use at that point.

System partition not booting up?

I'll try to keep this one explained simple
- Was running have boot loader unlocked and am rooted, was trickdroid
- Decided to try what else was out there for ROMS, switched to Renovate rom, was a downgrade from trickdroid in my eyes
- Decided to switch to one more rom before making the jump back to trickdroid, accidentally wiped internal storage data along with everything else
- After wasting most of my day messing with this crap, I finally got everything back to somewhat operational again
- My internal memory and Cache at one point were unmountable and read 0MB, had to do a factory reset via boot loader then a full wipe using TWRP
- Finally have trickdroid installed and its semi operational, aside from the fact that when I load it, it instantly has no service, no internet, nothing. It sends me to the launcher portion and there are no apps on there either. Shortly after it starts it will restart the device.
-After doing several restarts into recovery I have confirmed that the system partition consistently unchecks itself and I have already attempted fixing permissions several times and doing a system wipe and full ROM install again.. same issue to no avail.
- Last night I actually managed to pull up icons and programs, somehow, but again there was no system being loaded up
A little help please? I am in a state of a soft brick at this point, which is not bad considering I had a SUPER HARD brick earlier.
Help me, please. I just want to get this phone back to a functioning state!
Armygoat05 said:
- Finally have trickdroid installed and its semi operational, aside from the fact that when I load it, it instantly has no service, no internet, nothing. It sends me to the launcher portion and there are no apps on there either. Shortly after it starts it will restart the device.
-After doing several restarts into recovery I have confirmed that the system partition consistently unchecks itself and I have already attempted fixing permissions several times and doing a system wipe and full ROM install again.. same issue to no avail.
- Last night I actually managed to pull up icons and programs, somehow, but again there was no system being loaded up
A little help please? I am in a state of a soft brick at this point, which is not bad considering I had a SUPER HARD brick earlier.
Help me, please. I just want to get this phone back to a functioning state!
Click to expand...
Click to collapse
A hard brick is unrecoverable. It means your phone is literally as responsive as a brick. I would say your phone is pretty functional if the actual OS loads.
Anyway, have you tried RUU? That usually brings everything back to normal. Be sure to use the correct one, and note that you will lose EVERYTHING. Even root.
EDIT: Try this.
sauprankul said:
A hard brick is unrecoverable. It means your phone is literally as responsive as a brick. I would say your phone is pretty functional if the actual OS loads.
Anyway, have you tried RUU? That usually brings everything back to normal. Be sure to use the correct one, and note that you will lose EVERYTHING. Even root.
EDIT: Try this.
Click to expand...
Click to collapse
So I did try using this link and downloaded the full zip file and unzipped as per instructions of QBKing77 off of youtube, then clicked setup.exe within the folder which was unzipped, but after it ran through its setup process, nothing else popped up? I tried doing it as well through hasoons all in one toolkit but while that worked, it didn't work as expected and it just stayed at the black htc screen. I'm lost at the moment.
Trickdroid works on the Sprint variant?
Sent from my HTCONE using xda premium
sounds to me like you flashed an international rom and messed up your partitions
run an RUU
flex360 said:
sounds to me like you flashed an international rom and messed up your partitions
run an RUU
Click to expand...
Click to collapse
That's what I was thinking too.
Sent from my HTCONE using xda premium
We should add to the Q/A sticky the names of ROMs NOT to flash like Android revolution, trickdroid, etc.
P.S. He tried RUU, he's having trouble.
sauprankul said:
We should add to the Q/A sticky the names of ROMs NOT to flash like Android revolution, trickdroid, etc.
P.S. He tried RUU, he's having trouble.
Click to expand...
Click to collapse
I'll add it right now
Done Q21
bigdaddy619 said:
I'll add it right now
Click to expand...
Click to collapse
Sweet, will save a lot of noobs a lot of trouble.
sauprankul said:
Sweet, will save a lot of noobs a lot of trouble.
Click to expand...
Click to collapse
Maybe if they actually read it haha
bigdaddy619 said:
Maybe if they actually read it haha
Click to expand...
Click to collapse
It wouldn't be as bad if the Int'l forum was marked so. If I were new, I would assume all HTC Ones are the same too.
sauprankul said:
It wouldn't be as bad if the Int'l forum was marked so. If I were new, I would assume all HTC Ones are the same too.
Click to expand...
Click to collapse
Very true there are HTC One forums for:
International
Sprint
AT&T
T-Mobile
So it could be confusing to some
Hello from my finally unbricked one! Turns out I was having issues with the computer itself launching installshield so it wouldn't keep the factory RUU running. I did it from a different computer and it did it in stride.. I'm so happy to have this thing back. So on a sidenote I had to rwlock bootloader and then I had to reload the factory RUU.

Plz Help! HTC One Stuck On Start Up Screen

I went to install the most recent up date. When it got done installing it started to reboot. It then got stuck on the HTC start up screen. I do not know a whole bunch on phones but did a little research and tried to recover and reboot the phone and neither worked. I would really like to find a fix that does not involve erasing all my data. I have all the pictures of my baby from the past year, from the time that he was born until now, and I would really hate to lose those. Thank you!
foreveryours117 said:
I went to install the most recent up date. When it got done installing it started to reboot. It then got stuck on the HTC start up screen. I do not know a whole bunch on phones but did a little research and tried to recover and reboot the phone and neither worked. I would really like to find a fix that does not involve erasing all my data. I have all the pictures of my baby from the past year, from the time that he was born until now, and I would really hate to lose those. Thank you!
Click to expand...
Click to collapse
Maybe some more information... what ROM, was this a stock OTA? If you have custom recovery and are attempting to flash a custom ROM, then try to reflash...if you have lost your data already or to avoid data loss;try side-loading a ROM...can't tell you much from what I've read, but if you can hold power+ volume down simultaneously for about 15 secs you should end up in recovery, if you installed a custom recovery; e.g.Philz, TWRP, CWM...then you'll pop up there....
It is safe to say that if you don't have any of these custom recoveries then you'll need to use the RUU found in the Dev section....
foreveryours117 said:
I went to install the most recent up date. When it got done installing it started to reboot. It then got stuck on the HTC start up screen. I do not know a whole bunch on phones but did a little research and tried to recover and reboot the phone and neither worked. I would really like to find a fix that does not involve erasing all my data. I have all the pictures of my baby from the past year, from the time that he was born until now, and I would really hate to lose those. Thank you!
Click to expand...
Click to collapse
... by the look of you message, it feels you havent unlocked your bootloader and here i will be happy to be wrong. if you have already then you got a bright chance of flashing a custom recovery via fastboot and retrieving your data mounting the storage from recovery ...
Devilish_Angel said:
... by the look of you message, it feels you havent unlocked your bootloader and here i will be happy to be wrong. if you have already then you got a bright chance of flashing a custom recovery via fastboot and retrieving your data mounting the storage from recovery ...
Click to expand...
Click to collapse
No I have not done this. I am assuming there is no way to do that at this point?
hooover said:
Maybe some more information... what ROM, was this a stock OTA? If you have custom recovery and are attempting to flash a custom ROM, then try to reflash...if you have lost your data already or to avoid data loss;try side-loading a ROM...can't tell you much from what I've read, but if you can hold power+ volume down simultaneously for about 15 secs you should end up in recovery, if you installed a custom recovery; e.g.Philz, TWRP, CWM...then you'll pop up there....
It is safe to say that if you don't have any of these custom recoveries then you'll need to use the RUU found in the Dev section....
Click to expand...
Click to collapse
I am sorry, I am completely stupid when it comes to phone. I know that I have not done any customizations. It is not rooted and would not have a custom ROM, not quite sure what that is. Everything should be stock. So what would I have to do to do the option that you have stated? I apologize for my lack of knowledge.
does your pc recognize the the phone when you plug it in? you could try extracting the data like stated before, but you're not rooted so that'd be a problem. an ruu would be your best bet, even though you'll lose your data. I HIGHLY suggest creating a dropbox and backing up your photos, it has done wonders for me.
playonword said:
does your pc recognize the the phone when you plug it in? you could try extracting the data like stated before, but you're not rooted so that'd be a problem. an ruu would be your best bet, even though you'll lose your data. I HIGHLY suggest creating a dropbox and backing up your photos, it has done wonders for me.
Click to expand...
Click to collapse
It recognizes it to an extent. My computer will ding recognizing that it is plugged in but since it does not go past the start up screen you can't get into the phone storage. I do have a dropbox but with the thousands of pictures on my phone it unfortunately only stored a month or so of pictures. I am not so much worried about the phone, as I have insurance on it and can get it replaced. Just really want the pictures. When looking online I had read something about unlocking the boot menu and downloading a ROM I believe. Do you know anything about that and if it would work for me? Or is that the same thing as the RUU?
foreveryours117 said:
No I have not done this. I am assuming there is no way to do that at this point?
Click to expand...
Click to collapse
... you can but then you are gonna lose everything after unlocking so there is no point ...
Mine gets stuck on boot screen occasionally. Sounds weird but hold the phone drectly up to a light bulb and try to reboot the phone. This works for my particular problem. Not sure why but it does.
foreveryours117 said:
It recognizes it to an extent. My computer will ding recognizing that it is plugged in but since it does not go past the start up screen you can't get into the phone storage. I do have a dropbox but with the thousands of pictures on my phone it unfortunately only stored a month or so of pictures. I am not so much worried about the phone, as I have insurance on it and can get it replaced. Just really want the pictures. When looking online I had read something about unlocking the boot menu and downloading a ROM I believe. Do you know anything about that and if it would work for me? Or is that the same thing as the RUU?
Click to expand...
Click to collapse
Hold power and vol-down together until it reboots into bootloader. Connect to USB and select 'fastboot' on the bootloader menu. That should get you to fastboot. From there, you can HTCDEV unlock the thing (in all likelihood).

Nexus 6 is horrible

I have a nexus 6. The sound quality is horrible with headphones and the speakers. I unlocked the bootloader, rooted the nexus 6. A lot of the custom roms I have tried freeze during installation and soft brick the phone. The only rom that works is the stock rom.
alucke
That's a rather non-descript post. Who's your carrier, what Rom's are you talking about, any custom kernels, did you perform a wipe before installing? As far as the Audio goes, I've got no complaints from the speakers nor using headphones (both hardwired and BT headphones). You do realize that the first boot after installing a fresh Rom can take several minutes, some as long as 8 minutes while everything is set in place. More info so that we can help, please.
alucke said:
I have a nexus 6. The sound quality is horrible with headphones and the speakers. I unlocked the bootloader, rooted the nexus 6. A lot of the custom roms I have tried freeze during installation and soft brick the phone. The only rom that works is the stock rom.
alucke
Click to expand...
Click to collapse
lol your doing something wrong.
i have flashed most of the available roms, in total hundreds of times, never failed to boot, not even once.
i know i say this often, but ill say it again(even if im wrong this time).. i bet you used used a toolkit to root your device. too bad that you learn absolutely nothing from a toolkit. what you should do is put your phone down, and not touch it until you do some serious research into your device. how you do things properly, what can you flash, etc. these are things that you have to do before you ever root your device.
Is this a rant or are you asking for help? This is a development forum, so not really the place to rant. If you want help, please ask specific questions whilst supplying relevant information
Need education
simms22 said:
i know i say this often, but ill say it again(even if im wrong this time).. i bet you used used a toolkit to root your device. too bad that you learn absolutely nothing from a toolkit. what you should do is put your phone down, and not touch it until you do some serious research into your device. how you do things properly, what can you flash, etc. these are things that you have to do before you ever root your device.
Click to expand...
Click to collapse
You are correct. Where do I go for help and advice upon this phone OS? I am willing to learn but know of no courses or clubs to join. I am taking lessons online at the Google developers site. This is a start but slow go. As an update, my soft bricked Nexus6 is back in order. I some how managed to use the Root Tool Kit and "pushed" the factory to the phone. I assume this restored my ABD and debug thereby establishing USB connection between PC and phone. I then wiped Cache, system and Dvalick. and loaded Cyanogen Mod 12.1 and Gapps. For a while there I lost debug and was never able to open the phone and enable it.
Still,I would like to know the alternate way such as sideload ABD and commands, Fastboot, Bootloader, etc.. Thank you.
---------- Post added 21st September 2015 at 12:09 AM ---------- Previous post was 20th September 2015 at 11:59 PM ----------
simms22 said:
i know i say this often, but ill say it again(even if im wrong this time).. i bet you used used a toolkit to root your device. too bad that you learn absolutely nothing from a toolkit. what you should do is put your phone down, and not touch it until you do some serious research into your device. how you do things properly, what can you flash, etc. these are things that you have to do before you ever root your device.
Click to expand...
Click to collapse
You are correct. Where do I go for help and advice upon this Android phone OS? I am willing to learn but know of no courses or clubs to join. I am taking lessons online by self at the Google developers site. This is a start but slow go. As an update, my soft bricked Nexus 6 is back in order. I some how managed to use the Root Tool Kit v2.0.4 and "pushed" the factory, I downloaded from Google, to the phone. I assume this restored my ABD allowing debug thereby establishing USB connection between PC and Nexus 6, I then wiped Cache, system and Dvalick. and loaded Cyanogen Mod 12.1 and Gapps. For a while there I lost debug and was never able to open the Nexus 6 bootloader or Fastboot.
Still,I would like to know the alternate way such as sideload ABD and commands, Fastboot, Bootloader, etc.. Thank you.
This is the most idiotic post I've seen here all day. Seriously sell your nexus 6 and go buy a different phone if you don't like the phone or face the fact that you either don't know how to use a nexus device or you have a defective phone. But I'm almost entirely convinced this is 100% user error
Sent from my Nexus 6 using XDA Free mobile app
ray6279 said:
You are correct. Where do I go for help and advice upon this phone OS? I am willing to learn but know of no courses or clubs to join. I am taking lessons online at the Google developers site. This is a start but slow go. As an update, my soft bricked Nexus6 is back in order. I some how managed to use the Root Tool Kit and "pushed" the factory to the phone. I assume this restored my ABD and debug thereby establishing USB connection between PC and phone. I then wiped Cache, system and Dvalick. and loaded Cyanogen Mod 12.1 and Gapps. For a while there I lost debug and was never able to open the phone and enable it.
Still,I would like to know the alternate way such as sideload ABD and commands, Fastboot, Bootloader, etc.. Thank you.
Click to expand...
Click to collapse
here is a good place to start
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
good luck!
Android documentation is kinda lacking
Its not terrible... Its just not entirely coherent, well organized or complete. A lot of poking around and learn by doing, patching together threads that document how things work ect...
Here is my suggestion:
Follow the second link posted by simms22 above, this one here: http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
Go here: https://developers.google.com/android/nexus/images?hl=en
And download the latest image for your phone (shamu, the images at the bottom of the list are most recent. All carriers currently use same build, unless your on tmobile or Fi)
Use some kind of unzipping program (not sure if winrar can do .tgz, if not just google "Windows .tgz") to decompress the image you download. This will have a few .img files in it and a .zip Unzip the .zip for the rest of the partition images for the phone.
With these you can use fastboot to re-format partition to stock.
Here is an older guide, while devices may vary a little... and things have changed since 2011, were still mostly talking about system, boot, recovery, data....
http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/
I would say read through the above guides thoroughly, then manually update your phone to stock.
You will notice the stock flash-all script will
Code:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.10.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.101.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-shamu-lmy48m.zip
You probably don't want to do all this... You will notice the last command I showed is fastboot -w update image-shamu-lmy48m.zip (assuming you downloaded the lmy48m image)
We already unzipped this, so rather then flash it in bulk (flashing userdata.img will wipe device) lets flash everything but leave data in place.
So get fastboot working, go to bootloader, and as the script does
With fastboot:
Flash the bootloader
then use fastboot to reboot, to the bootloader
flash the radio
then use fastboot to reboot to the bootloader
then fasboot flash system, recovery, boot and cache images, skipping userdata to avoid wiping the sd card.
At this point reboot. It may take a while for the first boot as android sets itself up and optimizing applications. If things appear to be hung give it 10 minutes before forcing a reboot checking your images and trying again. Pay attention to the output of the commands and make sure there are no errors. If there are read them, and google them.
Now you should be able to boot, and you will be fully stock. This is what it takes to recover from almost any situation. Often you can just flash system to update. Boot will overwrite your kernel, so it is often skipped when custom kernels are used... particularly when not encrypted.
Now find the website for twrp and find the image for your device, then go back to bootloader mode and flash recovery, after flashing reboot directly to recovery.
Also find chainfire's website with the recovery flashable supersu (should be a .zip)
Make sure the supersu install zip is on your phone, and the recovery is on your computer.
Reboot to bootloader and fastboot flash twrp to your recovery partition, then immediately reboot to recovery mode to finish the install.
In recovery make a backup of your working stock system.
After that install supersu
Reboot, and you should be stock and rooted with a backup of your completely stock system.
From here if your want to install a rom reboot to recovery, wipe caches, system and data. On future upgrades backup first, and try only wiping system and caches, then flash the new version of the rom and you wont have to set anything back up. You will have to reinstall xposed if your use it, as well as supersu if your rom does not include it for some reason.
If you do all that, read those guides to the point where you understand each step, and read the thread or at least the last hand full of pages of any rom or utility that you use... Things should work pretty good.
It so easy for some to assume user error, the phone might be a defective I know hate the layout of mine, and out of 13 android phones currently this d*m thing is the only one that freezes on me and will not show up in Linux (two versions) or windows 7 and it still stock. I have hated the phone from day two and tried very hard to use it stock for as long i could. I finally said screw it and went back to my old lg g flex till just died.. I wish i could sell this...but I am stuck trying to make it work. still cant even make it show up in any os and that makes it a bit hard to do anything (and yes my USB ports and drivers and cables are fine i have checked)
And likewise to this post , useless as well
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
nevermind
simms22 said:
nevermind
Click to expand...
Click to collapse
:laugh: :laugh:
Was going to post, and had this thought also....
btw JJD loves his N6 and his speakers Rock!
#nuffsaid
Nexus 6 ftw!
disturb1 said:
It so easy for some to assume user error, the phone might be a defective I know hate the layout of mine, and out of 13 android phones currently this d*m thing is the only one that freezes on me and will not show up in Linux (two versions) or windows 7 and it still stock. I have hated the phone from day two and tried very hard to use it stock for as long i could. I finally said screw it and went back to my old lg g flex till just died.. I wish i could sell this...but I am stuck trying to make it work. still cant even make it show up in any os and that makes it a bit hard to do anything (and yes my USB ports and drivers and cables are fine i have checked)
Click to expand...
Click to collapse
It is user error.
SOME hardware is bad... But people like to view their phones as these temperamental beasts that "need to settle" and "all have their own intricacies"
Its a computer. Is this the way we look at laptops?
Two, or two hundred version of linux... Doesn't really matter because linux is a kernel and MTP implementation is handled separately. Not Nexus' fault that you didn't configure linux correctly, or that you expected someone else to do it for you for free, and they didn't do it either.
What file manager do you use, and did you have gvfs-mtp or kio-mtp installed?
What utilities were you using to mount the mtp drive?
These instructions are for arch linux, https://wiki.archlinux.org/index.php/MTP#simple-mtpfs (I use simple mtpfs), adapt them to your distro, find your distros documentation.
But then you don't really need it to show up in the OS? Does fastboot recognize it? Have you installed udev rules for it?
ok, thanks for all the input. I will give the nexus 6 a try again, root it. Can anyone point me to a custom rom that is somewhat close to stock?
I like Pure Nexus
scryan said:
It is user error.
SOME hardware is bad... But people like to view their phones as these temperamental beasts that "need to settle" and "all have their own intricacies"
Its a computer. Is this the way we look at laptops?
Two, or two hundred version of linux... Doesn't really matter because linux is a kernel and MTP implementation is handled separately. Not Nexus' fault that you didn't configure linux correctly, or that you expected someone else to do it for you for free, and they didn't do it
Click to expand...
Click to collapse
Not sure if I just have issues with lollipop or the hardware and lollipop
I have it rooted now and also still hate it I don't have the sound issues that some have but freezing was a constant with nexus T-Mobile stock ROM or maybe I have a lucky lemon ether way
I don't blame others or look to others to do my rooting rom installation or themes nor do I assume that it the phone every time all I am saying is we need to stop blaming every confused user as noob and assume people are not trying to learn
I been here 3 years but I lurk and learn and move on but I constantly see issues of flaming it is sad ...I see your reply and that fact that you offered help is what I like to see what I would offer if I knew an answer..
Honestly I am just not a fan of the phone but I made my bed and in it I must... hack at it till I am happy...

Issues after trying to Root : Bootloader Code 3 : Soft Bricked?

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

Categories

Resources