Database Develop

[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.

[Q] Having trouble upgrading to 4.4.2 stock on Verizon

I have a Moto X Developer Edition rooted on Verizon with TWRP 2.6.3.1 and stock Android 4.4 on it. I have been trying to upgrade to 4.4.2 without doing the OTA, and without having to reflash TWRP.
So far, I have been unsuccessful.
I have tried Blur_Version.140.45.5.ghost_verizon.Verizon.en.US.zip (approximate file size 150MB) from multiple sources as all the posts I read keep saying that is what works. I have also tried a ~650MB version I found somewhere. In addition, I tried the upgrade located here: sbf.droid-developers.org/phone.php?device=0 which is called VZW_XT1060_4.4.2-KXA20.16-1.25.2_CFC_1FF.xml.zip (It's the 4.4.2 upgrade listed under Verizon US).
All of these fail. In TWRP, about 2-3 steps after it verified md5, it simply says "Failed" with no explanation as to why.
Here is my question:
How can I upgrade to 4.4.2 without a data wipe, and without having to reflash TWRP?
I have no interest in going to a ROM, I want to stay stock, and if I must, I will reflash the recovery if I have to, but I *really* don't want to.

Flash stock recovery, take the OTA, flash TWRP again.
It's so simple, so painless, so quick and it will not wipe your data.

tcrews said:
Flash stock recovery, take the OTA, flash TWRP again.
It's so simple, so painless, so quick and it will not wipe your data.
Click to expand...
Click to collapse
I was hoping to avoid that (Yep, I really am that lazy...) but that's what I was going to do tonight if I couldn't get my hands on a .zip to flash.
Ironically, I bought the Dev Edition specifically so things like this would be easy.

It is easy.....just need to do it.
I support my sister, her husband and my wife (as well as my own) who all have Moto X's. 2 seconds to flash recovery, however long it takes for the OTA to install and reboot and then 2 seconds to flash TWRP again. Heck...I'd just leave the stock recovery in place since it's not needed if you don't plan on flashing any ROMs. The OTA doesn't even remove root.

tcrews said:
It is easy.....just need to do it.
I support my sister, her husband and my wife (as well as my own) who all have Moto X's. 2 seconds to flash recovery, however long it takes for the OTA to install and reboot and then 2 seconds to flash TWRP again. Heck...I'd just leave the stock recovery in place since it's not needed if you don't plan on flashing any ROMs. The OTA doesn't even remove root.
Click to expand...
Click to collapse
Oh, that last bit is good to know! Well, I think even if it did remove root, getting it back is easy on the DE.
I think you're right though, I probably won't install TWRP again, I specifically got the Moto X because I was tired of messing around with stuff when I all I want is a rooted, stock Android experience.

So, after several hours of messing with this, and thinking the stock recovery had gotten messed up because the instructions I had for getting in to it were wrong, I finally got the OTA installing...
and it fails.
I don't know why, I haven't seen the error (I'm not looking at the phone when it fails).
So... Awesome.

Taegost said:
So, after several hours of messing with this, and thinking the stock recovery had gotten messed up because the instructions I had for getting in to it were wrong, I finally got the OTA installing...
and it fails.
I don't know why, I haven't seen the error (I'm not looking at the phone when it fails).
So... Awesome.
Click to expand...
Click to collapse
Are there files out so you can just flash 4.4.2 with mfastboot? Would be easiest.

kj2112 said:
Are there files out so you can just flash 4.4.2 with mfastboot? Would be easiest.
Click to expand...
Click to collapse
I assume so, but I haven't found any instructions specifically saying how to do that, except for the ones that tell you how to return to stock without using RSD Lite.
Unfortunately, I don't know enough about how all this stuff works to be able to figure out which bits and pieces to put together to get upgraded without wiping my data.
What really pisses me off is that I specifically bought this phone so I wouldn't have issues like this, and here I am...
BTW: The only thing the error says is "Error". That's it, nothing else.

Taegost said:
I assume so, but I haven't found any instructions specifically saying how to do that, except for the ones that tell you how to return to stock without using RSD Lite.
Unfortunately, I don't know enough about how all this stuff works to be able to figure out which bits and pieces to put together to get upgraded without wiping my data.
What really pisses me off is that I specifically bought this phone so I wouldn't have issues like this, and here I am...
BTW: The only thing the error says is "Error". That's it, nothing else.
Click to expand...
Click to collapse
This guide has a return to stock section. It will tell you how to flash the stock firmware.
http://forum.xda-developers.com/showthread.php?t=2603358
Unfortunately the moto x is not a simple phone for tinkering with, like say a nexus, even the dev edition.
It can be easier once you do fully understand everything. Just gotta know what applies to you...meaning mostly the locked versus unlocked methods for everything.
After owning an s2, a moto x and now an n5 (n7 too...but I don't tinker with it really....its a family device) I've come to the mind set that for flashers and rooters.....nothing at all beats owning a nexus. Every other device has some limitations that a nexus won't have.

kj2112 said:
This guide has a return to stock section. It will tell you how to flash the stock firmware.
http://forum.xda-developers.com/showthread.php?t=2603358
Unfortunately the moto x is not a simple phone for tinkering with, like say a nexus, even the dev edition.
It can be easier once you do fully understand everything. Just gotta know what applies to you...meaning mostly the locked versus unlocked methods for everything.
After owning an s2, a moto x and now an n5 (n7 too...but I don't tinker with it really....its a family device) I've come to the mind set that for flashers and rooters.....nothing at all beats owning a nexus. Every other device has some limitations that a nexus won't have.
Click to expand...
Click to collapse
Yeah, that's the page I was talking about when I said I found the full instructions...
I specifically bought this phone because I didn't want to mess around with it like this, I just wanted to root it so I could use Titantium Backup and be done with it... and now I'm stuck at a halfway point.... Again...
I'll probably end up just doing the full wipe and manually flash to 4.4.2 (RSD Lite doesn't see my device... yay), since I have gone from my mute button not working (with 4.2.2), to a really bad echo for whomever I'm talking to when it's on speakerphone (Even when speakerphone is muted... THAT made for a fun conference call...).

Taegost said:
Yeah, that's the page I was talking about when I said I found the full instructions...
I specifically bought this phone because I didn't want to mess around with it like this, I just wanted to root it so I could use Titantium Backup and be done with it... and now I'm stuck at a halfway point.... Again...
I'll probably end up just doing the full wipe and manually flash to 4.4.2 (RSD Lite doesn't see my device... yay), since I have gone from my mute button not working (with 4.2.2), to a really bad echo for whomever I'm talking to when it's on speakerphone (Even when speakerphone is muted... THAT made for a fun conference call...).
Click to expand...
Click to collapse
Flashing stock and rooting on an unlocked Moto x is basically the same as a nexus. It really is simple, once you are familiar with fastboot.
I guess there are toolkits that automate everything....like Samsung's Odin, and there's a few for nexus....but it really doesn't help anyone learn. And that's kinda what this hobby is all about.
But, I am sorry you're having trouble. Not sure what else to add. The guides are there, and they work. Usually. I can't think of anything to add to whats already been said.
Hope it works out for you!

kj2112 said:
Flashing stock and rooting on an unlocked Moto x is basically the same as a nexus. It really is simple, once you are familiar with fastboot.
I guess there are toolkits that automate everything....like Samsung's Odin, and there's a few for nexus....but it really doesn't help anyone learn. And that's kinda what this hobby is all about.
But, I am sorry you're having trouble. Not sure what else to add. The guides are there, and they work. Usually. I can't think of anything to add to whats already been said.
Hope it works out for you!
Click to expand...
Click to collapse
I don't think I'm articulating my issue properly. I understand how to do everything in the guides you mentioned, they're a piece of cake. That doesn't solve my problem.
My problem is that I want to get to 4.4.2 WITHOUT wiping my data, but can't do the update via OTA or flashing in recovery. RSD Lite doesn't work either.
The ONLY option I have available to me is to manually push the update with fastboot, which I can definitely do with the instructions provided... But those instructions require me to wipe my data.
I know it's possible to apply the update with fastboot without requiring me to wipe my data, but I don't know enough about the inner workings to know which steps to skip, and which need to be modified, in order to make that happen.

Taegost said:
I don't think I'm articulating my issue properly. I understand how to do everything in the guides you mentioned, they're a piece of cake. That doesn't solve my problem.
My problem is that I want to get to 4.4.2 WITHOUT wiping my data, but can't do the update via OTA or flashing in recovery. RSD Lite doesn't work either.
The ONLY option I have available to me is to manually push the update with fastboot, which I can definitely do with the instructions provided... But those instructions require me to wipe my data.
I know it's possible to apply the update with fastboot without requiring me to wipe my data, but I don't know enough about the inner workings to know which steps to skip, and which need to be modified, in order to make that happen.
Click to expand...
Click to collapse
It says right at the bottom of the return to stock section in the guide I linked too.....you can skip
Fastboot erase user data
fastboot erase cache
Though if you have any problems after, you might have to do it again and do erase those, before spending time trying to figure out what's wrong.

kj2112 said:
It says right at the bottom of the return to stock section in the guide I linked too.....you can skip
Fastboot erase user data
fastboot erase cache
Though if you have any problems after, you might have to do it again and do erase those, before spending time trying to figure out what's wrong.
Click to expand...
Click to collapse
Wow... Attention to detail -5
Sorry about that, when I looked through that article, I skimmed through and saw that the "Return to Stock" section was (almost) identical to the other instructions I was reading...But I missed that last paragraph when I looked at the link you provided, the directions I was using referenced that article but did not include that last bit...
Thank you for your patients, I feel like a dumbass now *sheepish grin*

Taegost said:
Wow... Attention to detail -5
Sorry about that, when I looked through that article, I skimmed through and saw that the "Return to Stock" section was (almost) identical to the other instructions I was reading...But I missed that last paragraph when I looked at the link you provided, the directions I was using referenced that article but did not include that last bit...
Thank you for your patients, I feel like a dumbass now *sheepish grin*
Click to expand...
Click to collapse
No worries!! .
And sorry, its userdata. My keyboard split the words up.
---------- Post added at 11:16 AM ---------- Previous post was at 11:15 AM ----------
And, you may very well have issues doing that way. But its worth a shot first. If you do have issues, then you can erase those and repeat the process.

if using fastboot/mfastboot, I would still erase cache, as it doesn't touch your data/apps/config.
Another tip, use this mfastboot -> http://mark.cdmaforums.com/X-STUFF/Mfastboot-4.4.zip
or you can use RSDlite to flash the SBF, but there is a corresponding line for "erase data"
Two helpful links that will help explain what you saw...
Taking the OTA -> http://mark.cdmaforums.com/MotoX-OTA.html
various ways to Return to stock -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html

kj2112 said:
No worries!! .
And sorry, its userdata. My keyboard split the words up.
---------- Post added at 11:16 AM ---------- Previous post was at 11:15 AM ----------
And, you may very well have issues doing that way. But its worth a shot first. If you do have issues, then you can erase those and repeat the process.
Click to expand...
Click to collapse
Alrighty, well I was able to successfully flash to 4.4.2 using the Fastboot instructions. Flashed TWRP afterwards and got root right back. Now that I know, this won't be a trial in the future (fingers crossed!)
Thanks for your help and patience

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...

unrootable (prototype N6)

hey everyone just picked up a prototype N6 from a buddy and having serious issues rooting this verion. i have rooted my other N6 with no issues but this build (shamu-userdebug l lrw80j 1454210 dev-keys) just wont seem to work if anyone can point me in the right direction that would be great ty. this version included a power button on the back of the phone which was nice and why it caught my eye.

What have you tried and where does it fail?
Root is usually unlock bootloader, flash recovery, flash supersu from recovery.
The problem you may have if the hardware is different is that the kernel would then be different, meaning there wont be a version of TWRP with a bootable kernel for your device. So just like you cannot run TWRP for a HTC on the Nexus 6, that could be the same case.

oh ok i see what you mean. everytime it gets to the try to temp load twrp it never seems to boot up im using the toolkit .and now it seems that i can't even boot into the system anymore just into fast boot but i can still use the flash boot flash options in root tool kit and i think you are so right about the kernel but just dont know which one to use i tried restoring /baseband /boot/system with a orignal factory 6.0 but individually but not working . is there a different method you think i can try? ty for your help.

sunnybwoy1 said:
oh ok i see what you mean. everytime it gets to the try to temp load twrp it never seems to boot up im using the toolkit .and now it seems that i can't even boot into the system anymore just fast boot. is there a different method you think i can try? ty for your help
Click to expand...
Click to collapse
If you're going to root, recovery is important.
There are apps that can root once booted into android, but you're playing with fire, especially if there hardware is different - as that means you will not have a factory image to flash either. These things are best kept untouched.

Great and I just messed up this systems IMG. cause I'm just stuck at the fastboot now I hope there is away around this. I had a feeling I shouldn't have gotten this version but wanted to be different now it just cost me smfh. Here are the pics of the phone and info

Here are some pics of the phone and build number

sunnybwoy1 said:
Here are some pics of the phone and build number
Click to expand...
Click to collapse
I cant think of a way around it. You could try flashing a stock system.img via fastboot but I cant say I'm hopeful and likely will make things worse. Without custom recovery, it is unlikely that you can repair it.
You can of course try and factory reset it. Who knows, may make it boot?

Yea flashing the system. IMG in fastboot made it worst well I used the new android m system so maybe that's why. Not looking good I hope I can get some answers soon or if maybe someone can mod a system. IMG I can use with this hardware .

sunnybwoy1 said:
Yea flashing the system. IMG in fastboot made it worst well I used the new android m system so maybe that's why. Not looking good I hope I can get some answers soon or if maybe someone can mod a system. IMG I can use with this hardware .
Click to expand...
Click to collapse
I don't think you'll get help here.

to me, it doesnt look like a n6, it looks like a moto x pro..

simms22 said:
to me, it doesnt look like a n6, it looks like a moto x pro..
Click to expand...
Click to collapse
It does, but it definitely does have an engineering bootloader and says shamu XT1103, so it's another one of "those"

danarama said:
It does, but it definitely does have an engineering bootloader and says shamu XT1103, so it's another one of "those"
Click to expand...
Click to collapse
yup. i bet it was the moto x pro, but in development still. they probably used all the shamu software on it at first. im curious whether it would take the moto x pro software.

I'm going to try to flash a stock N6 ROM to see if it will load.

Is this prototype the one with fingerprints sensor on the back?

It has a power button on the back.

sunnybwoy1 said:
Great and I just messed up this systems IMG. cause I'm just stuck at the fastboot now I hope there is away around this. I had a feeling I shouldn't have gotten this version but wanted to be different now it just cost me smfh. Here are the pics of the phone and info
Click to expand...
Click to collapse
PM Me if you decide to "part" with it.

Won't boot into recovery

Hello. I have unlocked bootloader successfully (it says "unlocked" at screen and also "tampered"). I have all the fastboot/adb software on my windows pc and can communicate with the phone. I flash recovery via fastboot and it is successful...includes a "recovery" option under bootloader options but it just flashes a disclaimer screen and quickly goes back to bootloader screen. Without custom recovery I cannot root this phone which is my goal. I have tried to reflash other recovery images, including cmw and twrp - I believe cmw is on it now but it won't open.
Hoping someone can assist me with this.
Thank you

belowHeights00 said:
Hello. I have unlocked bootloader successfully (it says "unlocked" at screen and also "tampered"). I have all the fastboot/adb software on my windows pc and can communicate with the phone. I flash recovery via fastboot and it is successful...includes a "recovery" option under bootloader options but it just flashes a disclaimer screen and quickly goes back to bootloader screen. Without custom recovery I cannot root this phone which is my goal. I have tried to reflash other recovery images, including cmw and twrp - I believe cmw is on it now but it won't open.
Hoping someone can assist me with this.
Thank you
Click to expand...
Click to collapse
Reflash whichever recovery you plan to use then remove the battery and put it back in then hold the volume down button and then press and hold the power button at the same time and the phone should then boot to recovery. Make a backup after so you have something to fall back on just in case.

MrMike2182 said:
Reflash whichever recovery you plan to use then remove the battery and put it back in then hold the volume down button and then press and hold the power button at the same time and the phone should then boot to recovery. Make a backup after so you have something to fall back on just in case.
Click to expand...
Click to collapse
Thanks for the reply! I just now gave that a shot but it had no effect.

belowHeights00 said:
Thanks for the reply! I just now gave that a shot but it had no effect.
Click to expand...
Click to collapse
Are you actually holding both buttons down at the same time until the screen turns on? Don't let them go hold them both down until your screen lights up. Then select recovery but if it doesn't work then try below.
Try flashing this version of twrp https://twrp.me/devices/htcdesire510usa32bit.html ... If you're not in the USA I need to know.

Flashing twrp didn't change anything unfortunately. I recently tried re-locking my bootloader and attempted to flash stock images back to the phone but when I press "yes" to the question about voiding the warranty before unlocking the bootloader again...the disclaimer just flashes and the phone won't let it.
Also, I cannot seem to restore it to stock through the menu...nor the bootloader screen.
So now I have "tampered" and "Relocked" banners on top of bootloader screen.
One the upside, the phone itself works fine (I currently only use it for wifi).
Only thing I can think of is I originally flashed a corrupt recovery img (or incompatible version).
Hoping you or someone else has any ideas as to how to get this thing working again. I'd be happy with reverting completly back to stock and starting the process over..

belowHeights00 said:
Flashing twrp didn't change anything unfortunately. I recently tried re-locking my bootloader and attempted to flash stock images back to the phone but when I press "yes" to the question about voiding the warranty before unlocking the bootloader again...the disclaimer just flashes and the phone won't let it.
Also, I cannot seem to restore it to stock through the menu...nor the bootloader screen.
So now I have "tampered" and "Relocked" banners on top of bootloader screen.
One the upside, the phone itself works fine (I currently only use it for wifi).
Only thing I can think of is I originally flashed a corrupt recovery img (or incompatible version).
Hoping you or someone else has any ideas as to how to get this thing working again. I'd be happy with reverting completly back to stock and starting the process over..
Click to expand...
Click to collapse
What service provider are you using?
Don't toss the unlock code you got from HTC you're gonna need the very first one you got keep it forever.

I'm using Boost but I think I figured it out. It ended up being a corrupt download of cmw. I actually used an ruu to get back stock and now the whole process went smoothly. Just looking for a rom that fits...got any recommendations in that area?

belowHeights00 said:
I'm using Boost but I think I figured it out. It ended up being a corrupt download of cmw. I actually used an ruu to get back stock and now the whole process went smoothly. Just looking for a rom that fits...got any recommendations in that area?
Click to expand...
Click to collapse
Not really since everyone has their own tastes but I'd advise you to create a backup in your recovery so you can use it in case something goes wrong. Currently me and a friend are working on CM13/12..

MrMike2182 said:
Not really since everyone has their own tastes but I'd advise you to create a backup in your recovery so you can use it in case something goes wrong. Currently me and a friend are working on CM13/12..
Click to expand...
Click to collapse
Funny enough I never made a backup before and constantly have to re-locate stock images due to soft bricking. I now am making backups so as not to go through that again.
I have a question perhaps you could answer -- if I install a rom that doesn't include any additional tweaks such as extended personaliation options in settings (transitions, etc, etc.)..is there a mod I can flash to achieve that?

belowHeights00 said:
Funny enough I never made a backup before and constantly have to re-locate stock images due to soft bricking. I now am making backups so as not to go through that again.
I have a question perhaps you could answer -- if I install a rom that doesn't include any additional tweaks such as extended personaliation options in settings (transitions, etc, etc.)..is there a mod I can flash to achieve that?
Click to expand...
Click to collapse
For extended personalizing other than developer options, I'd use Xposed.

MrMike2182 said:
Not really since everyone has their own tastes but I'd advise you to create a backup in your recovery so you can use it in case something goes wrong. Currently me and a friend are working on CM13/12..
Click to expand...
Click to collapse
How have you started working on that, i gthink i should join too. Are you working on the USA model or UK? (X86 or X64)

Zubagy said:
How have you started working on that, i gthink i should join too. Are you working on the USA model or UK? (X86 or X64)
Click to expand...
Click to collapse
The USA model because myself and rb don't have the EU phone to even test anything on it.. We still have a lot of booting problems right now. I'd say if you wanted to help I'd have to ask what you know about building roms from source? Have you done it before?
P.S: There's already a CM-12.1 available for the EU model although it does have some issues.. You should read about it if you want to try it..

MrMike2182 said:
The USA model because myself and rb don't have the EU phone to even test anything on it.. We still have a lot of booting problems right now. I'd say if you wanted to help I'd have to ask what you know about building roms from source? Have you done it before?
P.S: There's already a CM-12.1 available for the EU model although it does have some issues.. You should read about it if you want to try it..
Click to expand...
Click to collapse
Not really, But perhaps it time to learn

Zubagy said:
Not really, But perhaps it time to learn
Click to expand...
Click to collapse
It's pretty cool and fun once you get the hang of making things and seeing them function right, and the other thing is... You'll need a pretty decent computer to compile/build with and it'll need to have at least 4GB ram (more is better) and about 50 to 100 GB hard drive space for building your rom plus the CM source code needs to be on your system too...

MrMike2182 said:
It's pretty cool and fun once you get the hang of making things and seeing them function right, and the other thing is... You'll need a pretty decent computer to compile/build with and it'll need to have at least 4GB ram (more is better) and about 50 to 100 GB hard drive space for building your rom plus the CM source code needs to be on your system too...
Click to expand...
Click to collapse
I guess then am good to go, are those the only requirements....... i dont have any source code though

Zubagy said:
I guess then am good to go, are those the only requirements....... i dont have any source code though
Click to expand...
Click to collapse
Well how fast is your internet? By the way.. I'm using a Linux operating system... What are you using? It cannot be done on Windows unless you use a VM.

Hey, I also faced this problem but I find the solution and successfully flash twrp
Hey, I also faced this problem but I find the solution and successfully flash tarp recovery.
belowHeights00 said:
Hello. I have unlocked bootloader successfully (it says "unlocked" at screen and also "tampered"). I have all the fastboot/adb software on my windows pc and can communicate with the phone. I flash recovery via fastboot and it is successful...includes a "recovery" option under bootloader options but it just flashes a disclaimer screen and quickly goes back to bootloader screen. Without custom recovery I cannot root this phone which is my goal. I have tried to reflash other recovery images, including cmw and twrp - I believe cmw is on it now but it won't open.
Hoping someone can assist me with this.
Thank you
Click to expand...
Click to collapse

MrMike2182 said:
Well how fast is your internet? By the way.. I'm using a Linux operating system... What are you using? It cannot be done on Windows unless you use a VM.
Click to expand...
Click to collapse
Sorry for the delay, yes.... i am using vm ware... my net is not that fast... but it can get things done.