Database Develop

[Q] How to get my free space?

Sorry in advance for my not perfect english.
I'm using less than 7GB on my Moto X "16gb" but it says that I don't have space left.
When I'm checking with ES Explorer 3, with the options ticked to show all hiddens files, it's said that what I take is less than 7GB. The same on Windows and Linux.
But when I do the ES Explorer 3: SD analyser it's said that 11.41GB is used, but if I calcul everything single size on that screen, I see only less than 7GB.
So what is all about that?
What I really want is to know how do I get my 5GB left? I use only 7GB out of 12GB. So, in simple mathematics, 12-7=5!!!
I don't wanna remove my 7GB stuff because I'm supossed to have 5GB left.
I put the pictures too in the attachments box.
Thanks in advance.
EDIT:
I was needed to delete some user stuff but now, without adding anything, is re-say that I don't have space left
I'm tired of this sh*t. NOBODY to help? I payed for 12GB but don't have it, I'm sick of this

Check out this similar thread...
http://forum.xda-developers.com/moto-x/moto-x-qa/lost-files-sdcard-15-gigs-space-t2833710
?

KJ said:
Check out this similar thread...
http://forum.xda-developers.com/moto-x/moto-x-qa/lost-files-sdcard-15-gigs-space-t2833710
?
Click to expand...
Click to collapse
I don't see a LOST.DIR folder and I never deleted file on the phone from the computer, only from the phone itself.
Still don't know what to do :/
It's there a efficient way to see if there's actually a LOST.DIR folder? I mean beside just plugged in on Windows or Linux?
Anyways, thanks for your post

Only other thing other than that folder, is maybe needing to just flash stock again. And see if its fine after.
But you could keep searching on missing space.... There's many many threads for other devices too. Your issue may not be device specific and Troubleshooting ideas from other devices could help.
Or sit tight and see if anyone has other ideas.
But don't downgrade android versions. You'd need to flash the version you're on now again.

KJ said:
Only other thing other than that folder, is maybe needing to just flash stock again. And see if its fine after.
But you could keep searching on missing space.... There's many many threads for other devices too. Your issue may not be device specific and Troubleshooting ideas from other devices could help.
Or sit tight and see if anyone has other ideas.
But don't downgrade android versions. You'd need to flash the version you're on now again.
Click to expand...
Click to collapse
How to flash stock again if I'm not rooted? Also I don't want to lost my files on the sdcard...
I gonna see elsewhere but it's bad needing to see everywhere for such a thing, I still not understand why is possible
EDIT:
I keep searching but still not found the same problem than me, they said the same message but the phone itself actually that there a those GB free, beside me that it said that I only have MB free.
I don't wanna reset my phone because this not supossed to happen, never...
The worse is I can't even install a 500kb app lol
EDIT 2: I unistalled a big app but still cannot the 500kb one WTF Happen?

It maybe isn't "supposed" to happen... But things just happen.
See return to stock section in the "complete Moto x guide" in general. You can flash some ways without losing data. But in your case with corrupt partition, I would wipe it all. Or it might not get fixed. Transfer important things to your pc. As far as apps and data, try helium. I hear it doesn't need root. Then transfer is backup to your pc too.

KJ said:
It maybe isn't "supposed" to happen... But things just happen.
See return to stock section in the "complete Moto x guide" in general. You can flash some ways without losing data. But in your case with corrupt partition, I would wipe it all. Or it might not get fixed. Transfer important things to your pc. As far as apps and data, try helium. I hear it doesn't need root. Then transfer is backup to your pc too.
Click to expand...
Click to collapse
I can't use helium cause I can't install anything
I also cannot backup my files on the computer, it keep crashing in the process of copying....
I tired of this, why can't it be just what it's should be seriously
EDIT:
I don't see your way to flash stock in the complete guide..
A factory/reset from the settings isn't good?

This guide...
http://forum.xda-developers.com/showthread.php?t=2603358
First post, "returning to stock".
No point in stressing about why... Or how it should be... It is what it is now.
If you can't communicate with the pc properly, you may have issues flashing also. Try another cable maybe?
I'm not sure what else to say. Flashing to stock is maybe the only way. Sorry!

KJ said:
This guide...
http://forum.xda-developers.com/showthread.php?t=2603358
First post, "returning to stock".
No point in stressing about why... Or how it should be... It is what it is now.
If you can't communicate with the pc properly, you may have issues flashing also. Try another cable maybe?
I'm not sure what else to say. Flashing to stock is maybe the only way. Sorry!
Click to expand...
Click to collapse
Why does it said "and Locking Bootloader" do I need Bootloader Unlocked first?

jlibion said:
Why does it said "and Locking Bootloader" do I need Bootloader Unlocked first?
Click to expand...
Click to collapse
Nope. Keep reading.... There are a bunch of different sections.
---------- Post added at 02:48 PM ---------- Previous post was at 02:46 PM ----------
That's for guys that want to relock theirs. Just skip "fastboot oem lock" at the end.
Look up RSDLite as well, another way to return to stock.

New N6 shipped with developer build?

Just bought a brand new N6 and its not downloading any ota's, still on 5.0. The build is LNX07M which is a developer build and apparently will not download any ota's. Has anyone heard of this? Did a quick Google search and there is hardly anything about this build.
I have no access to a computer, am I stuck on this build and 5.0?

csdaytona said:
Just bought a brand new N6 and its not downloading any ota's, still on 5.0. The build is LNX07M which is a developer build and apparently will not download any ota's. Has anyone heard of this? Did a quick Google search and there is hardly anything about this build.
I have no access to a computer, am I stuck on this build and 5.0?
Click to expand...
Click to collapse
no access at all?

simms22 said:
no access at all?
Click to expand...
Click to collapse
Not at the moment. What will I need to do?
This is my first nexus device and the last phone I rooted/flashed was the G1 way back in the day.
I was excited to get my phone today so this kind of sucks....

csdaytona said:
Not at the moment. What will I need to do?
This is my first nexus device and the last phone I rooted/flashed was the G1 way back in the day.
I was excited to get my phone today so this kind of sucks....
Click to expand...
Click to collapse
ohh.. that sucks. i remember my g1
i have a way that will probably work out fine, but this way is highly looked down upon on xda. would you be willing to try? btw, im one of those that would look down on this way, unless in certain situations..

simms22 said:
ohh.. that sucks. i remember my g1
i have a way that will probably work out fine, but this way is highly looked down upon on xda. would you be willing to try? btw, im one of those that would look down on this way, unless in certain situations..
Click to expand...
Click to collapse
OK what is it and why is it frowned upon?

csdaytona said:
OK what is it and why is it frowned upon?
Click to expand...
Click to collapse
because its not "proper", and normally isnt used properly. but ill explaine to you the proper way. you can try an app called kingsroot. you csnt get it at the play store, youll have to search google for it. after you install it, then run it, youll have root. but, youre not done yet. you will want to download the latest twrp recovery for the nexus 6 with your phone and keep it there. then you will unstall flashify from the play store. you will now use flashify to flash the twrp recovery. now, last thing, to get your bootloader unlocked. you will install any bootloader unlock apps, like boot unlocker or similar(that might delete everything from your phone), then youre done. ive never tried this on a nexus, but have on other devices, just so you know.

simms22 said:
because its not "proper", and normally isnt used properly. but ill explaine to you the proper way. you can try an app called kingsroot. you csnt get it at the play store, youll have to search google for it. after you install it, then run it, youll have root. but, youre not done yet. you will want to download the latest twrp recovery for the nexus 6 with your phone and keep it there. then you will unstall flashify from the play store. you will now use flashify to flash the twrp recovery. now, last thing, to get your bootloader unlocked. you will install any bootloader unlock apps, like boot unlocker or similar(that might delete everything from your phone), then youre done. ive never tried this on a nexus, but have on other devices, just so you know.
Click to expand...
Click to collapse
That seems like a lot of work. If I can get to a computer tomorrow, what can I do then?
Btw, thanks for helping me out.

csdaytona said:
That seems like a lot of work. If I can get to a computer tomorrow, what can I do then?
Btw, thanks for helping me out.
Click to expand...
Click to collapse
If you can get to a computer, download this: https://dl.google.com/dl/android/aosp/shamu-mra58k-factory-5b07088c.tgz
It's the Marshmallow (6.0) factory image for the Nexus 6. Run the batch file inside and it'll flash your phone. Note that this WILL wipe it.
Here's the actual Google-supplied information on it: https://developers.google.com/android/nexus/images?hl=en

|Jason8| said:
If you can get to a computer, download this: https://dl.google.com/dl/android/aosp/shamu-mra58k-factory-5b07088c.tgz
It's the Marshmallow (6.0) factory image for the Nexus 6. Run the batch file inside and it'll flash your phone. Note that this WILL wipe it.
Here's the actual Google-supplied information on it: https://developers.google.com/android/nexus/images?hl=en
Click to expand...
Click to collapse
First time doing this, but it's OK to jump straight to 6.0?

csdaytona said:
First time doing this, but it's OK to jump straight to 6.0?
Click to expand...
Click to collapse
It'll be fine. It's the complete system image, so it doesn't matter what you're on currently. Note that you will have to install all sorts of extra crap to get the Android SDK installed and working and the proper drivers, but it's not that hard, just gigs of downloads when everything is all said and done.
Like I said, it WILL wipe your phone completely.

csdaytona said:
That seems like a lot of work. If I can get to a computer tomorrow, what can I do then?
Btw, thanks for helping me out.
Click to expand...
Click to collapse
if you can get to a computer..
you can unlock your bootloader with "fastboot oem unlock"
then fastboot flash twrp recovery
then flash a custom kernel wiyh the latest supersu in your new recovery.
and then boot up with root, an unlocked bootloader, and a custom recovery

|Jason8| said:
It'll be fine. It's the complete system image, so it doesn't matter what you're on currently. Note that you will have to install all sorts of extra crap to get the Android SDK installed and working and the proper drivers, but it's not that hard, just gigs of downloads when everything is all said and done.
Like I said, it WILL wipe your phone completely.
Click to expand...
Click to collapse
Not worried about wiping the phone, I've literally only had it for a few hours and nothing is loaded on it.
Would be possible to just install an ota to get me on the right upgrade path? I'm just trying to do the quickest and easiest method possible.

csdaytona said:
Not worried about wiping the phone, I've literally only had it for a few hours and nothing is loaded on it.
Would be possible to just install an ota to get me on the right upgrade path? I'm just trying to do the quickest and easiest method possible.
Click to expand...
Click to collapse
If it's not grabbing an OTA, not sure what else you can do, short of downloading all the OTAs and flashing via recovery. But no guarantee that'll work as you're on a development build... There probably isn't an OTA to go from your development build to a release build.

csdaytona said:
I have no access to a computer, am I stuck on this build and 5.0?
Click to expand...
Click to collapse
simms22 said:
no access at all?
Click to expand...
Click to collapse
csdaytona said:
Not at the moment.
Click to expand...
Click to collapse
csdaytona said:
That seems like a lot of work. If I can get to a computer tomorrow, what can I do then?
Click to expand...
Click to collapse
Dude, come on... I know this is the Q&A section, and were supposed to be nicer here... But this lazyness is bull****.
You act like using a computer is impossible, then as soon as it takes some work.... You can get at one the next day?
Stop expecting to be spoon fed and at least try to learn something fist. There are a TON of write ups on how to do this. You spend how much money on a phone, and now you don't care to educate yourself on it?
Instead of expecting other to do all the work for you, read through the stickied index thread in the general section
http://forum.xda-developers.com/nexus-6/general/nexus-6-index-thread-t3229412
It has a newbie guide that literally holds your hand through the whole process. Post 2 has info on "how to flash factory images", use method 2 as method 1 in that thread will not work with the MM factory image.
Nice people have already spend a lot of time and effort documenting these things for you, as they are common questions. People like Simms and the other posters in this thread answer questions and offer support for free out of the kindness of their heart... Don't create extra work for them by ignoring all the effort already put out by other members, expecting it all to be regurgitated to you.
|Jason8| said:
If it's not grabbing an OTA, not sure what else you can do, short of downloading all the OTAs and flashing via recovery. But no guarantee that'll work as you're on a development build... There probably isn't an OTA to go from your development build to a release build.
Click to expand...
Click to collapse
Fastboot, as described in the threads mentioned above, will completely overwrite the pertinent partitions, regardless of what was there... dev build or not. No need to flash and apply countless incremental updates. Google provides not only full system images, but the information to use them on their web page...

|Jason8| said:
If it's not grabbing an OTA, not sure what else you can do, short of downloading all the OTAs and flashing via recovery. But no guarantee that'll work as you're on a development build... There probably isn't an OTA to go from your development build to a release build.
Click to expand...
Click to collapse
Gotcha. I'll try to flash 6.0 tomorrow. Wish me luck.
Thanks for the help!

scryan said:
Fastboot, as described in the threads mentioned above, will completely overwrite the pertinent partitions, regardless of what was there... dev build or not. No need to flash and apply countless incremental updates. Google provides not only full system images, but the information to use them on their web page...
Click to expand...
Click to collapse
I linked him to that already. No need to be a **** about it. He was looking for an easy way to do it now, when he doesn't have a computer. **** got crazy, so he asked if it would be easier with a computer, which the answer is yes.
Wouldn't you be excited as **** if you had a new phone? Wouldn't you want to get it up and running as quickly as possible? Well... now he's gotta wait until he has a computer. Obviously installing an OTA and doing the incremental updates would be easier, which is what he was looking for. Since that's not an option, we laid out other ways to go about doing it. So he's getting to a computer tomorrow.
---------- Post added at 09:51 PM ---------- Previous post was at 09:50 PM ----------
csdaytona said:
Gotcha. I'll try to flash 6.0 tomorrow. Wish me luck.
Thanks for the help!
Click to expand...
Click to collapse
No problem man. I wish you luck!
If you do plan on modding it/rooting it/romming it in the future, DEFINITELY unlock your bootloader before you set up the phone or that'll wipe it, too.

|Jason8| said:
Wouldn't you be excited as **** if you had a new phone? Wouldn't you want to get it up and running as quickly as possible? Well... now he's gotta wait until he has a computer. Obviously installing an OTA and doing the incremental updates would be easier, which is what he was looking for. Since that's not an option, we laid out other ways to go about doing it. So he's getting to a computer tomorrow.
Click to expand...
Click to collapse
You act like I was born with a nexus 6... It was a new phone to me too. I was so excited I read as much as I could on it, thanking the people who were so gracious to spend their personal time writing guides so I could understand the process well enough to be comfortable with my phone and help others here.

scryan said:
Dude, come on... I know this is the Q&A section, and were supposed to be nicer here... But this lazyness is bull****.
You act like using a computer is impossible, then as soon as it takes some work.... You can get at one the next day?
Stop expecting to be spoon fed and at least try to learn something fist. There are a TON of write ups on how to do this. You spend how much money on a phone, and now you don't care to educate yourself on it?
Instead of expecting other to do all the work for you, read through the stickied index thread in the general section
http://forum.xda-developers.com/nexus-6/general/nexus-6-index-thread-t3229412
It has a newbie guide that literally holds your hand through the whole process. Post 2 has info on "how to flash factory images", use method 2 as method 1 in that thread will not work with the MM factory image.
Nice people have already spend a lot of time and effort documenting these things for you, as they are common questions. People like Simms and the other posters in this thread answer questions and offer support for free out of the kindness of their heart... Don't create extra work for them by ignoring all the effort already put out by other members, expecting it all to be regurgitated to you.
Fastboot, as described in the threads mentioned above, will completely overwrite the pertinent partitions, regardless of what was there... dev build or not. No need to flash and apply countless incremental updates. Google provides not only full system images, but the information to use them on their web page...
Click to expand...
Click to collapse
i have absolutely no computer nor laptop access, so i completely understand(understood) his side as well.

scryan said:
You act like I was born with a nexus 6... It was a new phone to me too. I was so excited I read as much as I could on it, thanking the people who were so gracious to spend their personal time writing guides so I could understand the process well enough to be comfortable with my phone and help others here.
Click to expand...
Click to collapse
He googled his build number and didn't get many hits on it. So he's asking if there's a way to get it up and running tonight without a computer. Seems valid to me. You jump into the thread offering no help at all and start talking **** about the guy. That's the exact opposite of what you're saying you strive to do. I don't get it.

simms22 said:
i have absolutely no computer nor laptop access, so i completely understand(understood) his side as well.
Click to expand...
Click to collapse
At that point its a legitamate question. This is a very different situation that is not well covered here, and requires a unique solution not many would come up with.
But "I absolutely have no computer nor laptop access" is pretty different then "I can access one TOMORROW. Sheesh, having something 1 day away is pretty far from it not being a possibility.
And I think you would agree it would be a significantly better idea to wait that day then to proceed with the method you gave (not that it was bad of you to give it... but you tried to differentiate and he held out to avoid being told to do it the hard way)
|Jason8| said:
He googled his build number and didn't get many hits on it. So he's asking if there's a way to get it up and running tonight without a computer. Seems valid to me. You jump into the thread offering no help at all and start talking **** about the guy. That's the exact opposite of what you're saying you strive to do. I don't get it.
Click to expand...
Click to collapse
We are told time and time again that their are no bad questions. Truth is there are more bad questions then good ones.
Him asking about a build that provides few google hits is very legitimate.
Him asking about doing it without a computer because he doesn't have one is legitimate.
It only becomes an issue when he doesn't get the answer he wants, and all of a sudden he does have computer access.
And given that he is going to proceed in a computer... It becomes nothing more then "How do I update my phone?", which is VERY well documented.
I not only gave him the link to the information he needed, AND even corrected the information pointing out that the flashall script fails and that he would need to use the second method listed in the instructions I linked him to (since I know he will likely have limited time to fail and figure out whats wrong)
"That's the exact opposite of what you're saying you strive to do. I don't get it."
Then let me explain.
Would you skip your homework, ignore your textbook, then show up to class asking your teacher to explain it again? We are here to help... but how or why should I care more about it then he does? With no attempt made to learn, how much should I care to teach him?
Its a pretty big **** you to all those who have spend countless hours documenting this stuff to help new people to ignore their work and tell someone to do it again.

Need help rooting Nexus 6 on 6.0.0

I want to root my Nexus 6 running stock android 6.0.0 but not sure exactly how to do it. Any help would be greatly appreciated. Thanks

dbzturtle said:
I want to root my Nexus 6 running stock android 6.0.0 but not sure exactly how to do it. Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Chainfire just released a new root for mm, http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
Sent from my Nexus 6 using Tapatalk

blueyes said:
Chainfire just released a new root for mm, http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It says that it's experimental and will likely have bugs. is there a stable way to root? If not I don't mind waiting until there is.

dbzturtle said:
It says that it's experimental and will likely have bugs. is there a stable way to root? If not I don't mind waiting until there is.
Click to expand...
Click to collapse
Fastboot flash twrp, and then flash 2.52superuser.sip in recovery. Look up wugfresh Nexus root toolkit, it'll explain the process.
Sent from my Nexus 6 using Tapatalk

I rooted my N6 on Android 6.0 with 2.52 weeks ago and it's absolutely fine - I've seen no problems at all. The "experimental" mention is a disclaimer to cover Chainfire in case you have problems - a very sensible warning in my opinion, but in this case you can probably ignore it.
And I agree with blueyes - Nexus Root Toolkit is pretty much idiot-proof as long as you read the instructions and in particular choose the correct ROM.

dahawthorne said:
I rooted my N6 on Android 6.0 with 2.52 weeks ago and it's absolutely fine - I've seen no problems at all. The "experimental" mention is a disclaimer to cover Chainfire in case you have problems - a very sensible warning in my opinion, but in this case you can probably ignore it.
And I agree with blueyes - Nexus Root Toolkit is pretty much idiot-proof as long as you read the instructions and in particular choose the correct ROM.
Click to expand...
Click to collapse
The problem with using toolkits when they are "idiot-proof" is that if you go into the process as an idiot, you leave the process still an idiot, so if something goes wrong with the device at a later date, the user has not got the skills to fix it, which becomes a problem on these forums as rather than telling someone how to fix it, we also have to teach the skills that should already have been learned.
Toolkits are great if you know what they're doing but if you dont, use fastboot the first time to get an understanding of it and also to ensure you know it is working on your computer correctly. It's easier to troubleshoot PC configurations when the device is fully working rather than waiting until it is "broken"

"you leave the process still an idiot"
I'll take that in the spirit I think you meant it...
Sure, point taken, but the problem with telling someone to start learning to use tools they don't understand is that this forum ends up with a flood of "I've bricked my device" posts. I agree that the manual way is useful for resolving problems, and I don't use NRT for everything - I'd say maybe 50% of the time for installing a brand new factory ROM, and the rest of the time using ADB/Fastboot for stuff I (think I) understand.
I just think that if someone has taken the time and trouble to give me the commands typed perfectly in the correct order and proven to work, why would I risk typing them in maybe in the wrong order or accidentally installing an image into the wrong partition? My own stupid fault, sure, but why take the long way round instead of the simple straight proven path?
Just sayin'...

dahawthorne said:
"you leave the process still an idiot"
I'll take that in the spirit I think you meant it...
Sure, point taken, but the problem with telling someone to start learning to use tools they don't understand is that this forum ends up with a flood of "I've bricked my device" posts. I agree that the manual way is useful for resolving problems, and I don't use NRT for everything - I'd say maybe 50% of the time for installing a brand new factory ROM, and the rest of the time using ADB/Fastboot for stuff I (think I) understand.
I just think that if someone has taken the time and trouble to give me the commands typed perfectly in the correct order and proven to work, why would I risk typing them in maybe in the wrong order or accidentally installing an image into the wrong partition? My own stupid fault, sure, but why take the long way round instead of the simple straight proven path?
Just sayin'...
Click to expand...
Click to collapse
It's not really the long way round. Once everything is installed, its as quick if not quicker. And as I said, you need all this installed for ongoing maintenance anyway so may as well do this whilst your device is working.
You can't brick your device by flashing to the wrong partition so there are no floods of posts from people doing things manually at all. .if you flash to the wrong partition,.just flash to the right partition. It's not rocket science either. If you flash a radio, flash it to the radio partition. If you flash system, flash it to the system partition. ...and if you type something wrong, it won't do anything at all.
Fastboot is well documented (by me and others) in the general forum. People should feel free to nude toolkits once they have learned it, but noobs should definitely learn it and use it the first time for the reasons I have already mentioned.
To root is so simple.
1. In fastboot, use
"fastboot oem unlock"
2. In fastboot, flash a custom twrp recovery image
"fastboot flash recovery twrp.img "
3. If marshamallow, flash a custom boot.img to allow it to be rooted
"fastboot flash boot boot.img"
4. Copy SuperSU to sdcard
5. Flash SuperSU zip from recovery
Once these steps have been carried out, you've used fastboot, know how it works and also have proof your computer has working fastboot. That ticks essential boxes.that every root user needs to have ticked. Once they're ticked, use toolkits to your hearts desire.
The worst thing about noobs using toolkits is when we need them to use fastboot when helping with their issues, they don't know what it is and we have to teach them that. We also need to troubleshoot setting it up which can be extremely hard if their device is bricked or in a state of needing repair. 10 minutes learning now can help prevent hours of wasting our time later. Surely it's only being courteous to learn these things ?

Where can I find a custom boot image ? I'm asking because I'm rooted but every time I try to go into recovery it ask me for a password

getmoneygreen said:
Where can I find a custom boot image ? I'm asking because I'm rooted but every time I try to go into recovery it ask me for a password
Click to expand...
Click to collapse
If you're encrypted, recovery will always ask you for a password. If you've set a password in android, you use that..if you have not set a password in android, you use the default twrp password.

I am an Android Noob! My first Android devices were the Nexus Player and the Nexus 6. (I came from iPhones and Apple TV) It did not take me long at all to learn how to use fastboot and adb. I manually flashed my Nexus 6 and Nexus Player to 6.0 before the OTAs were rolling out no problem. I have root on both of my devices.
My point is, if I can learn how to do this in a matter of a day (I have not had my Nexus 6 a full month yet) You can learn how to do it as well. There are tons of guides out there on how to do all of this. Google is your friend. You will feel awesome and have a sense of accomplishment if you take the time to learn this stuff. It is easy to learn, not hard at all! I come from a pretty extensive tech background so I was a step ahead, but anyone can do / learn this stuff.
There are toolkits that can do this stuff for you pretty much. I have not downloaded or used one myself. I don't trust someone else's code with my device. That's just me though. I like to feel in control when I flash stuff.

@danarama
"Surely it's only being courteous to learn these things ?"
I know that it's all too easy to be taken wrong when writing a post, so I'll say up front that I'm serious - thanks for posting those steps. I've watched the NRT run through its steps a number of times and it clearly does a lot more than this, which is why i'm glad that it's doing the typing for me
I have used your steps when flashing various things, I've just never used them for a ROM upgrade - except once when I was trying to recover a broken-radio N5 and was installing Chroma.
One value at least of the NRT for noobs is its help in setting up your PC's drivers - that alone is a good reason to look at it.
Just for interest, what would happen if I flashed recovery into the radio partition? Or the boot partition?
Seriously, thanks for these steps - I appreciate it.

dahawthorne said:
@danarama
"Surely it's only being courteous to learn these things ?"
I know that it's all too easy to be taken wrong when writing a post, so I'll say up front that I'm serious - thanks for posting those steps. I've watched the NRT run through its steps a number of times and it clearly does a lot more than this, which is why i'm glad that it's doing the typing for me
I have used your steps when flashing various things, I've just never used them for a ROM upgrade - except once when I was trying to recover a broken-radio N5 and was installing Chroma.
One value at least of the NRT for noobs is its help in setting up your PC's drivers - that alone is a good reason to look at it.
Just for interest, what would happen if I flashed recovery into the radio partition? Or the boot partition?
Seriously, thanks for these steps - I appreciate it.
Click to expand...
Click to collapse
Radio may boot but won't connect to a network.
Boot is the kernel so it won't boot without it (bootloop)
Both can be fixed by flashing the correct image to the correct partition.
The images in the factory image are appropriately labelled too, so it would be difficult to flash to the wrong partition without realizing it was wrong.. Eg
"fastboot flash radio boot.img" looks wrong when you have radio.img too.

Thanks, danarama. I suppose that's the point I was trying to make at the top - that if you're a bit of a thicko then you could flash to the wrong partition, which a predefined script won't. As long as it's recoverable, no problem, but I remember the pumping heart and breathlessness as I watched my devices on several occasions sitting with the boot animation for 10-15 minutes and thinking "What the hell do I do now?"
I know I'm hijacking this thread (sorry...) but is there anything you can think of that would definitely hard-brick my device if I'm being thick or careless? I've never managed it, and maybe as Android progresses it's becoming harder to hard-brick, but is there ever a time when I need to think "There's no way back from this one"?

danarama said:
If you're encrypted, recovery will always ask you for a password. If you've set a password in android, you use that..if you have not set a password in android, you use the default twrp password.
Click to expand...
Click to collapse
Thank for the heads up really appreciate that. BTW what is the default password for twrp

getmoneygreen said:
Thank for the heads up really appreciate that. BTW what is the default password for twrp
Click to expand...
Click to collapse
Not sure, Im not encrypted. But its documented somewhere by twrp dev. Maybe on their site or in their thread

Got Sprint Userdebug

this one was more of a proof of concept but it works. you will get the red triangle but don't worry about it. BUUUUUT if you wanna run it. Here's how:
DISCLAMER: first and foremost, I take NO responsibilities for the possibility of a bricked phone(none whatsoever). if you brick it, it's YOUR fault, not mine.
ALWAYS BACKUP YOUR DATA BEFORE YOU DO ANYTHING
1.your phone has to be fully running ZV4. DO NOT DELETE YOUR DATA (but do back it up in case something does happen)
2. Make sure you have LGUP working. if not, refer to here
3. Download the edited ZV4.tot from here, and extract the zip.
4. Put phone in download mode ( Phone off, vol up while plugging in usb from PC).
5. Start LGUP
6. Make sure you see a com # and phone model
7. At the bottom where it says BIN, select it, at which point you should see 3 dot on the right, select it and choose the tot file that you downloaded from here
8. make sure you select "update" and none of the others. if you select any of the other options it will bootloop the phone.
If you bootloop your device:
1. Put phone in download mode ( Phone off, vol up while plugging in usb from PC).
2. Start LGUP
3. Make sure you see a com # and phone model
4. At the bottom where it says BIN, select it, at which point you should see 3 dot on the right, select it and choose the original ZV4 .tot file that you got from Honestly Annoying that he has listed here
5. select "refurbish", then "start" and wait for the magic.
I give creds to Honestly Annoying, and Tungkick for providing the original ZV4 tot file

schizoidd said:
this one was more of a proof of concept but it works. you will get the red triangle but don't worry about it. BUUUUUT if you wanna run it. Here's how:
DISCLAMER: first and foremost, I take NO responsibilities for the possibility of a bricked phone(none whatsoever). if you brick it, it's YOUR fault, not mine.
ALWAYS BACKUP YOUR DATA BEFORE YOU DO ANYTHING
1.your phone has to be fully running ZV4. DO NOT DELETE YOUR DATA (but do back it up in case something does happen)
2. Make sure you have LGUP working. if not, refer to here
3. Download the edited ZV4.tot from here
4. Put phone in download mode ( Phone off, vol up while plugging in usb from PC).
5. Start LGUP
6. Make sure you see a com # and phone model
7. At the bottom where it says BIN, select it, at which point you should see 3 dot on the right, select it and choose the tot file that you downloaded from here
8. make sure you select "update" and none of the others. if you select any of the other options it will bootloop the phone.
If you bootloop your device:
1. Put phone in download mode ( Phone off, vol up while plugging in usb from PC).
2. Start LGUP
3. Make sure you see a com # and phone model
4. At the bottom where it says BIN, select it, at which point you should see 3 dot on the right, select it and choose the original ZV4 .tot file that you got from Honestly Annoying that he has listed here
5. select "refurbish", then "start" and wait for the magic.
I give creds to Honestly Annoying, and Tungkick for providing the original ZV4 tot file
Click to expand...
Click to collapse
What exactly does this do? I'm very interested in this... It has some potential
Also, what is the red triangle? Does it not let you boot?

Honestly Annoying said:
What exactly does this do? I'm very interested in this... It has some potential
Also, what is the red triangle? Does it not let you boot?
Click to expand...
Click to collapse
it lets you boot fully. you just get a warning that your device can't be verified

schizoidd said:
it lets you boot fully. you just get a warning that your device can't be verified
Click to expand...
Click to collapse
Damn... great job with this! Can you please explain (with as much detail as you can) how you did this? This is extremely promising and I'm trying out some stuff now

Honestly Annoying said:
What exactly does this do? I'm very interested in this... It has some potential
Also, what is the red triangle? Does it not let you boot?
Click to expand...
Click to collapse
Honestly Annoying said:
Damn... great job with this! Can you please explain (with as much detail as you can) how you did this? This is extremely promising and I'm trying out some stuff now
Click to expand...
Click to collapse
well, simply I used a hex editor

schizoidd said:
well, simply I used a hex editor
Click to expand...
Click to collapse
But what parts did you edit? This could be very helpful

@autoprime Anything here?

Is this a pre-rooted tot file?

newbreedsoftware said:
Is this a pre-rooted tot file?
Click to expand...
Click to collapse
no. all it does is make your device show userdebug. nothing else is done, no root, no nothing. this one was a proof of concept to see if editing the .tot file would work.

What the crap @schizoidd. I live in Boise too.
I'd possibly be down to help out.
A thing about signatures, if it's a md5 type signature, you can make changes and not trigger failed verification if all characters are in there. Moved around but not changed. Like string "abcdef" can be changed to "fedcba" because it still evaluates the same. So maybe change a tot's security directory to the reverse and the phone won't be able to find it. I think I read that somewhere on these boards.

Would this work with the dirtysanta exploit from the LG v20?

i am not sure if this is an actual debug firmware.. it almost seems he took a stock zv4 tot and simply used a hex editor to say its a debug firmware?

eagleeyered said:
mostly. took a lot more than that. only used the hexeditor to extract the images for edit and to put them back in.
Click to expand...
Click to collapse
my point was, just because it was modded to "look" like a debug doesnt make it a debug.. if it was youd have fastboot enabled and you could simply unlock the bootloader..
---------- Post added at 01:24 AM ---------- Previous post was at 01:24 AM ----------
essentially that makes this thread misleading as you dont have sprint user debug

eagleeyered said:
who said it was me that created that file. that was all schizoidd. but i can tell you that there was a lot more than "just edited to look like userdebug". if it was edited to look like that, it wouldn't say that it was edited on boot, nor would it boot at all. it would just brick your device. now as he said, "this one was more of a proof of concept". in other words, it was made to see if the TOT for ZV4 (and others) could be picked apart and edited and put back together.
you do realize that the userdebug/eng ZV4 boot.img that tunkick released was used to make that even bootable. and it was schizoidd that realized that it was a userdebug boot, not an eng boot. if it wasn't for schizoidd, the userdebug on ZV4 would have never been released. it was only a proof of concept(i.e. bugs). fastboot is one and adb root is the other. but if you also look around, there was a ZV4 fastboot that was released. which kind of worked. and as we get close to releasing a good modded tot for the latest version of the software for our device, another one gets released. And as there are only 5 (yes 5) give-or-take people working diligently on attaining root for the LS992 with only 2 test devices, that stuff takes time, especially when one has to be replaced. for the record, 8 phones have been fried while attaining root (and that is out of pocket for the cost of those devices). so until we can get more people on the project, either as testers or as devs, it will take a while.
Click to expand...
Click to collapse
before you get panties in a bunch no one ever said you released anything.. was just going based off his posts and clearly saying all he did was use a hex editor and you guys not having any actual ddbug features it doesnt appear to be a debug firmware.. if it did youd have an unlocked BL already with fastboot

eagleeyered said:
just to give you a heads-up. ALL of the fastboot areas have been disabled and aren't in the aboot.img at all for the LS992. the only one that has fastboot that is close to what is needed is the tmobile version. and integrating 2 boot and 2 aboots and tring to get it to boot is hard. especially since an improper edited aboot results in bricked device.
And i was only pointing out the facts. i aint at all mad.
Click to expand...
Click to collapse
just a heads up, if you had debug firmware the aboot would have the necessary fastboot commands.. thats what im tryna tell you lol
we got a debug firmware on the lg v20 and debug aboot was already unlocked and had fastboot working
---------- Post added at 03:45 AM ---------- Previous post was at 03:44 AM ----------
not to mention the OPs account was disabled lol.. i wonder why

eagleeyered said:
as we dont have an actual userdebug device, we have to build the bootloader from the ground, up from source (kind of a pain).
although the QSEC_HASH key is the same from the LS992 and the V20. so might be able to pull some things from that, and they are based on the MSM board. i just want to make sure before saying the V20 root method will work, i wanna check to make sure that the aboot and boot is compatiblle
Click to expand...
Click to collapse
lol if you are making it from the ground up then it will never be a debug firmware.. debug firmwares come directly from the device manufacturer/carrier.. not something domeone just whips up..
youre not creating a debug anytjing, you guys are trying to find a way to unlock/root the device is all lol

eagleeyered said:
no one said it was easy.
Click to expand...
Click to collapse
i know.. but op sayin he got userdebug isnt true lol he has a slightly modified rom that if anything is only visually a userdebug

eagleeyered said:
oh, and do you wanna know why Schiziodd was banned? he was banned for the simple fact that him and one other person got into an arguement and due to that person using a technicallity in words and also trapping, he got banned. if he had known that what he had was what it was, he would have deleted it and added it for everyone and then left it at that.
Click to expand...
Click to collapse
lol sorry but this comment confuses me.. he was banned due to a technicality in words?? wht does that even mean lol.. he was trapped on xda??
and if he knew what he had was what it was he could have deleted it and add it for everyone then left? why would he delete and readd?
it sounds like he took someone elses work and got banned for it but who knows, im not a mod lol but doesnt seem to be a trustworthy fellow at all...

elliwigy said:
lol sorry but this comment confuses me.. he was banned due to a technicality in words?? wht does that even mean lol.. he was trapped on xda??
and if he knew what he had was what it was he could have deleted it and add it for everyone then left? why would he delete and readd?
it sounds like he took someone elses work and got banned for it but who knows, im not a mod lol but doesnt seem to be a trustworthy fellow at all...
Click to expand...
Click to collapse
Please check PMs, ignore eagleeyered...
Also you are very right about this only being hex edited. there is no official userdebug anything in this TOT, as I have tested this and flashed myself. Thread is misleading.

eagleeyered said:
[/COLOR]i have a ZV4 userdebug that boots and has the system set to RW. the only reason it's not released is due to the fact that not a lot of people are on ZV4.
Click to expand...
Click to collapse
So, less than a month ago, you're telling people on 4 not to update because IT'S COMING!! within a month. Now you're saying you've got it, it works, AND ON TIME, but you're not going to release it because, what, the "not a lot of people" who would want it, wouldn't want it now?
Hell, if I was actually able to deliver on something that big, ESPECIALLY within the time frame I set for it, I'd be paying Google to get my work to the top of search results. I'd be going door to door with it. I'd set up shop in front of Sprint stores until they stop selling the device, crowing about my ability to get RW to ANY build of this thing. But, that's just me, I guess.
You see how incredibly fishy that seems?

messed up my bionic

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: