Related
I heard something recently about fileshare sites being shut down...is that what I'm experiencing. Tried to download files from: http://forum.xda-developers.com/showthread.php?t=1359068 and none of the links work. Actually a couple did but said I could only download a file I uploaded myself. I tried downloading from another thread on this site and had the same problem. Any solutions/alternatives? How can I download from the link I posted above?
Thanks!
Firecracker_RC said:
I heard something recently about fileshare sites being shut down...is that what I'm experiencing. Tried to download files from: http://forum.xda-developers.com/showthread.php?t=1359068 and none of the links work. Actually a couple did but said I could only download a file I uploaded myself. I tried downloading from another thread on this site and had the same problem. Any solutions/alternatives? How can I download from the link I posted above?
Thanks!
Click to expand...
Click to collapse
I see a KJ4 link. Have you tried the KJ5 thread? It's the newest one for our 7310.
Hi nirogu325, thanks for replying. This is what I am trying to do:
-Enable adhoc connection so I can use my windows mobile phone as a hotspot for my tabl, and
-Enable USB charging for my tab in my car and elsewhere, not just wall jack.
Based on what I've read, I need busybox (Titanium back up says it's installed but when I downloaded an app called wifiadhocenabler, it says it is not installed. Installing it from the market says I need Nand Unlock and this is where I'm stuck at the moment. Do you know how to perform this on the P7310? Or an easier way to meet the objectives above?
Thanks again
Firecracker_RC said:
Hi nirogu325, thanks for replying. This is what I am trying to do:
-Enable adhoc connection so I can use my windows mobile phone as a hotspot for my tabl, and
-Enable USB charging for my tab in my car and elsewhere, not just wall jack.
Based on what I've read, I need busybox (Titanium back up says it's installed but when I downloaded an app called wifiadhocenabler, it says it is not installed. Installing it from the market says I need Nand Unlock and this is where I'm stuck at the moment. Do you know how to perform this on the P7310? Or an easier way to meet the objectives above?
Thanks again
Click to expand...
Click to collapse
I assume you're on a stock firmware. If I were you, I'd flash this specific version which is already rooted and has busybox as you can read in the OP. Also, flash the v2d version of the motley kernel and go here for the USB charging script and instructions on enabling. I know that last link is for the 10.1, but it is the one motley linked to in the v2b version changelog in his kernel thread.
After my soft brick yesterday, I used Odin to "install" the version you attached in your General Guide post P310XARKJ5_P7310UEKJ5_HOME.tar.md5). That's the one, right?
Anyway, the good news is, I decided to install BusyBox without doing the Nand Unlock (maybe it was already done?), and it worked! The wifiadhocenabler app works now and I have a connection to my wm phone! Yay! Before trying the app (for the sake of onlookers) I tried the other method with the wpa_supplicant, such as the one here: http://androidtablethacks.com/android-tablet-hacks/how-to-enable-adhoc-wifi-on-android-tablets/ and it did not work for me. The app did!
So now, I'll try the kernel you posted above and then the USB charging.
I'm going to look over your general guide to see if I can figure out how to flash. I'm guessing it's the same or similar to when I recovered my tab in Odin...?
Firecracker_RC said:
After my soft brick yesterday, I used Odin to "install" the version you attached in your General Guide post P310XARKJ5_P7310UEKJ5_HOME.tar.md5). That's the one, right?
Anyway, the good news is, I decided to install BusyBox without doing the Nand Unlock (maybe it was already done?), and it worked! The wifiadhocenabler app works now and I have a connection to my wm phone! Yay! Before trying the app (for the sake of onlookers) I tried the other method with the wpa_supplicant, such as the one here: http://androidtablethacks.com/android-tablet-hacks/how-to-enable-adhoc-wifi-on-android-tablets/ and it did not work for me. The app did!
So now, I'll try the kernel you posted above and then the USB charging.
I'm going to look over your general guide to see if I can figure out how to flash. I'm guessing it's the same or similar to when I recovered my tab in Odin...?
Click to expand...
Click to collapse
If you mean flashing a CWM package as the motley kernel, a file goes in the SDcard, you access the CWM Recovery and flash. That's a generic way BUT depending on what you will flash you may have to wipe. That's why I avoided altogether putting generic instructions regarding CWM packages in my guide (instructions may vary between ROM and kernels). Read your flashable package's thread carefully.
kind of like rooting? Yes, do I have to wipe to flash the motley kernel? I'm not seeing the flashable packages thread, can you point me to it?
Firecracker_RC said:
kind of like rooting? Yes, do I have to wipe to flash the motley kernel? I'm not seeing the flashable packages thread, can you point me to it?
Click to expand...
Click to collapse
No, lol. If you want to flash the motley kernel just follow that thread's instructions. I gave you the motley kernel thread link in a previous post. For kernels, no wipe is necessary, for ROMs, yes.
Ok, thank you. lol
Firecracker_RC said:
Ok, thank you. lol
Click to expand...
Click to collapse
You're welcome. Some people have the tendency NOT to wipe while flashing ROMs...yet complain later on the road. Always wipe when it comes to ROMs if you want to avoid issues. The only bugs you will experience are the ones that come with the ROM already. Better safe than sorry.
Ah, that leads me to wonder...When my tab was soft bricked and I used Odin3 and inserted the KJ5 file into the PDA section, and so on (I think that was flashing), was I supposed to do a wipe before I did that? If so, would it be better if I started from scratch again? ...hoping not, but better now than latter I'm thinking.
Firecracker_RC said:
Ah, that leads me to wonder...When my tab was soft bricked and I used Odin3 and inserted the KJ5 file into the PDA section, and so on (I think that was flashing), was I supposed to do a wipe before I did that? If so, would it be better if I started from scratch again? ...hoping not, but better now than latter I'm thinking.
Click to expand...
Click to collapse
No. ODIN clears everything (including kernels, ROMs and CWM Recoveries). Everything back to stock. I was just referring to flashing other custom ROMs (non-ODIN, i.e. CWM flashable) procedures. Stick to the thread instructions in your chosen ROM and you'll be fine. It's just that some don't follow instructions and due to that, they may experience weird bugs.
That's good news, and strange, because after I used Oden3 (in the way I previously described), all my apps and files were still in tact. Does it just affect the system and not the file memory?
P.S. Hey! I'm no longer a noob! lol I just noticed I am now a "Junior Member".
P.S.S. I'm now running my tablet off my wm hotspot while charging it on my pc! woohoo
Firecracker_RC said:
That's good news, and strange, because after I used Oden3 (in the way I previously described), all my apps and files were still in tact. Does it just affect the system and not the file memory?
P.S. Hey! I'm no longer a noob! lol I just noticed I am now a "Junior Member".
Click to expand...
Click to collapse
That is because you didn't check F.Reset Time on the left side of ODIN before flashing. It is advisable to make sure it is checked. Thanks, I'm gonna put that little but important detail in my guide (dunno how I missed that one ). I advise using Titanium Backup (for apps backup) and then ODIN. You might be fine as you are, but if you ever experience something weird then you know.
Firecracker_RC said:
P.S.S. I'm now running my tablet off my wm hotspot while charging it on my pc! woohoo
Click to expand...
Click to collapse
I'm glad you made it!
Thanks for your support. If I ever have some extra change and feel like making a donation, I'll keep you in mind! Hey, where's your donation link anyway? Better get one!
nirogu325 said:
That is because you didn't check F.Reset Time on the left side of ODIN before flashing. It is advisable to make sure it is checked. Thanks, I'm gonna put that little but important detail in my guide (dunno how I missed that one ). I advise using Titanium Backup (for apps backup) and then ODIN. You might be fine as you are, but if you ever experience something weird then you know.
Click to expand...
Click to collapse
My tablet is definitely a little laggy now, but that could be the 3.2 HC. Since I did not check that off, does it mean that it did not install on a clean wipe? I'm wondering if I should just do it while I remember the path to how I got where I'm at now. I doubt I'll remember everything down the road.
I have been making nandroid backups as well as titanium app backups.
Firecracker_RC said:
My tablet is definitely a little laggy now, but that could be the 3.2 HC. Since I did not check that off, does it mean that it did not install on a clean wipe? I'm wondering if I should just do it while I remember the path to how I got where I'm at now. I doubt I'll remember everything down the road.
I have been making nandroid backups as well as titanium app backups.
Click to expand...
Click to collapse
As for donations, nah it's ok, I am no developer. As for the suggestion, it was just that, a suggestion for next time. Keep that in mind. It will become a habit down the road.
Sent from my GT-P7310
nirogu325,
I'm back to do my clean wipe. I performed the wipe/data reset in nandroid and now it's saying there is an update from KJ5 to LA3. Do you still think the custom kj5 is better than the stock LA3? I'm wondering if I should just install the update, root, install the motley kernel and go from there...?
Hope you're well! I still think you should add a donate link...you don't have to be a developer, your assistance/guidance is equally helpful to the community.
While I'm waiting, I flashed http://forum.xda-developers.com/showthread.php?t=1375112 and then I noticed I have the old CMR so I downloaded your updated package: GTab89Files and I cannot paste a single file from that folder onto my tab. I can paste files from other folders, but this one I copy and when I go to paste the paste option is not enabled; if I drag I get a little red circle with a line through it. Any ideas as to why it's rejecting?
Should I root my Nexus 6? Why or why not?
Would I be able to go back to 100% stock everything to have my warranty back? Or will people know I unlocked/rooted it?
Would I be able to un-brick my device? (Soft and hard?)
Would I be able to install OTA updates, or would I have to use custom roms?
I have been thinking of using the Nexus toolkit by Wugfresh, what order should I do everything in? I want to decrypt my phone as well.
Should i use the root toolkit or manually unlock and root using Command prompt?
Thank you all
You should post this in the Q & A section
Unlocking and rooting means custom rom, i think you have your answer
Use the toolkit by wugfresh. Simple and good.
C00lBeanz said:
Should I root my Nexus 6? Why or why not?
Would I be able to go back to 100% stock everything to have my warranty back? Or will people know I unlocked/rooted it?
Would I be able to un-brick my device? (Soft and hard?)
Would I be able to install OTA updates, or would I have to use custom roms?
I have been thinking of using the Nexus toolkit by Wugfresh, what order should I do everything in? I want to decrypt my phone as well.
Should i use the root toolkit or manually unlock and root using Command prompt?
Thank you all
Click to expand...
Click to collapse
I am of the opinion that if you own a Nexus, you should root it.. it's too easy and development is awesome.
You could go back to 100% stock, yes. No on would ever be able to tell. You can do that in Wug's Toolkit.
You can undo a soft brick, hard bricks are hard to do on a Nexus.. don't do things you don't understand in Fastboot and you shouldn't hard brick. I dunno about undoing one of those, though.
You can't install OTA, but you can use Wug's toolkit or Fastboot to flash stock updates if you wish to go stock. If not, custom ROMs are updated to match whatever base (OTA) Google is currently using, so you would never be unable to update like on a locked phone like a Samsung because of root.
If you use the Kit, you should unlock your device, decrypt if you want to, if not no need, and install custom recovery with root, simple. It's very easy to do in Fastboot, though, and I would encourage you to learn.
wrongway213 said:
I am of the opinion that if you own a Nexus, you should root it.. it's too easy and development is awesome.
You could go back to 100% stock, yes. No on would ever be able to tell. You can do that in Wug's Toolkit.
You can undo a soft brick, hard bricks are hard to do on a Nexus.. don't do things you don't understand in Fastboot and you shouldn't hard brick. I dunno about undoing one of those, though.
You can't install OTA, but you can use Wug's toolkit or Fastboot to flash stock updates if you wish to go stock. If not, custom ROMs are updated to match whatever base (OTA) Google is currently using, so you would never be unable to update like on a locked phone like a Samsung because of root.
If you use the Kit, you should unlock your device, decrypt if you want to, if not no need, and install custom recovery with root, simple. It's very easy to do in Fastboot, though, and I would encourage you to learn.
Click to expand...
Click to collapse
Thank you for answering all of my questions
But I read somewhere that you should decrypt the phone after everything is done like the recovery, ROM, or does it not matter when you decrypt it? Would it stay decrypted?
C00lBeanz said:
Thank you for answering all of my questions
But I read somewhere that you should decrypt the phone after everything is done like the recovery, ROM, or does it not matter when you decrypt it? Would it stay decrypted?
Click to expand...
Click to collapse
No, it wouldn't even be possible to do it that way. You read exactly wrong, it's basically the opposite. You want to decrypt as soon as you unlock. Decrypting your phone formats your userdata, internal sd card at all, meaning it erases EVERYTHING on your phone. If you wish to decrypt, you want to do it after unlocking and before rooting and you always want to make sure to check if a ROM forces encryption before flashing it.. if you flash a ROM that forces encryption when you're decrypted it'll encrypt all your data. If you want to flash a ROM that forces encryption, make sure to flash it with a kernel that does not force encryption to remain unencrypted, Personally I just remain encrypted, easier and no performance difference Ive noticed, just read/write speeds and that has zero effect on use.
wrongway213 said:
No, it wouldn't even be possible to do it that way. You read exactly wrong, it's basically the opposite. You want to decrypt as soon as you unlock. Decrypting your phone formats your userdata, internal sd card at all, meaning it erases EVERYTHING on your phone. If you wish to decrypt, you want to do it after unlocking and before rooting and you always want to make sure to check if a ROM forces encryption before flashing it.. if you flash a ROM that forces encryption when you're decrypted it'll encrypt all your data. If you want to flash a ROM that forces encryption, make sure to flash it with a kernel that does not force encryption to remain unencrypted, Personally I just remain encrypted, easier and no performance difference Ive noticed, just read/write speeds and that has zero effect on use.
Click to expand...
Click to collapse
Is CyanogenMod decrypted?
No, Cm forces encryption. If you want to remain decrypted on official CM nightlies you'll need to make sure you're flashing them with a custom kernel that does not force encryption. I recommend Franco personally but many kernels will work for that purpose.
wrongway213 said:
No, Cm forces encryption. If you want to remain decrypted on official CM nightlies you'll need to make sure you're flashing them with a custom kernel that does not force encryption. I recommend Franco personally but many kernels will work for that purpose.
Click to expand...
Click to collapse
What is your recommended rom and kernel?
C00lBeanz said:
What is your recommended rom and kernel?
Click to expand...
Click to collapse
Lots of good ROMs and kernels but feel free to look in my sig lol
wrongway213 said:
Lots of good ROMs and kernels but feel free to look in my sig lol
Click to expand...
Click to collapse
Does dirty unicorns have forced decryption off? Or do I have to flash the kernel too?
C00lBeanz said:
Does dirty unicorns have forced decryption off? Or do I have to flash the kernel too?
Click to expand...
Click to collapse
I am running Dirty Unicorn as my Daily with Sensei Kernel, great battery and smooth. It does not force encryption with the Kernel that comes with it.
If you go to any Roms post it will 99% of the time tell you if it is forced or not.
I recently received my nexus 6 a couple days ago and I LOVE it. The problem I am having at the moment is that I can't seem to get it to go decrypt. I downloaded the tool kit and my devices build isn't present. As a result, the tool kit it won't allow me to run the decrypt option on the fastboot window.
It's anyone running into this. My build is a LNX***.
First, what toolkit are you talking about?
Second, to decrypt the N6 you need to flash a modified boot image and then wipe your phone.
Thirdly, what's build LNX***?
Didgeridoohan said:
First, what toolkit are you talking about?
Second, to decrypt the N6 you need to flash a modified boot image and then wipe your phone.
Thirdly, what's build LNX***?
Click to expand...
Click to collapse
I'm using the nexus root toolkit . I have the flash on my computer and LNX07M is the build I have on the device. Maybe I should install a custom ROM first?
Nexus 6....man I missed being rooted.
KappaAce2010 said:
I'm using the nexus root toolkit . I have the flash on my computer and LNX07M is the build I have on the device. Maybe I should install a custom ROM first?
Nexus 6....man I missed being rooted.
Click to expand...
Click to collapse
You just need a custom kernel and a wipe.
another prime example of why you shouldn't use toolkits, if you don't understand what they are doing you shouldn't be using them.
To decrypt all you need to do is:
Backup your internal storage to a PC
Either use custom recovery to wipe everything including internal storage, install your rom and install a kernel that doesn't force
or
factory reset your phone, but before it boots up go back into recovery and flash a custom kernel that doesn't enforce
Circaflex said:
another prime example of why you shouldn't use toolkits, if you don't understand what they are doing you shouldn't be using them.
To decrypt all you need to do is:
Backup your internal storage to a PC
Either use custom recovery to wipe everything including internal storage, install your rom and install a kernel that doesn't force
or
factory reset your phone, but before it boots up go back into recovery and flash a custom kernel that doesn't enforce
Click to expand...
Click to collapse
Well if you to come off as a jerk, you have accomplished your goal. All you had to do was state what was needed and none of bs personal ideals you have. It's a Q & A section, so you should expect questions like this to arise.
Thank you for the input though.
Nexus 6....man I missed being rooted.
KappaAce2010 said:
Well if you to come off as a jerk, you have accomplished your goal. All you had to do was state what was needed and none of bs personal ideals you have. It's a Q & A section, so you should expect questions like this to arise.
Thank you for the input though.
Nexus 6....man I missed being rooted.
Click to expand...
Click to collapse
Although you're right, it is a personal ideal of many of us, I don't think he intended to come off as a jerk. But his point is that toolkits often remove the need for knowledge, which can become a problem for some users.
The good thing about nexus devices is that everything is pretty easy to do, so if you get stuck - continue to ask.
+1 to what rootSU said. And you should probably upgrade. That build is ancient and doesn't even have an official factory image (the reason it's not available in NRT).
Didgeridoohan said:
+1 to what rootSU said. And you should probably upgrade. That build is ancient and doesn't even have an official factory image (the reason it's not available in NRT).
Click to expand...
Click to collapse
I already plan on doing this anyway. Just time is conflicting with me at the moment.
rootSU said:
Although you're right, it is a personal ideal of many of us, I don't think he intended to come off as a jerk. But his point is that toolkits often remove the need for knowledge, which can become a problem for some users.
The good thing about nexus devices is that everything is pretty easy to do, so if you get stuck - continue to ask.
Click to expand...
Click to collapse
Well it happened, it's not going anywhere. Either way thanks guys for the advice. I should figure out everything tonight.
Nexus 6....man I missed being rooted.
Everything is a go. Fully decrypted and loving it. Thanks again.
I'm working on a (100% legit legal and 100% ORIGINAL works) way to flash to our /system partition for kitkat.
I've put my turbo through physical abuse. And it finally croaked weeks after "the drop".
I would need someone who has flashed a /system img via mofo to run USBlyzer on the correct port during the flashing process and then save and upload the log file. I will guide as needed. Remote desktop would allow me to quickly setup and start the process.
No longer having a phone that even turns on, I've resorted to using as USBlyzer as my debugging info by comparing my output to the known correct output. However, I have only logged the beginning of an upload. I need a complete, in order log.
I can help in about 12 hours
Why not apply yourself to figuring out how to root 5.1, maintain root upgrading to 5.1, or how to use mofo to flash 5.1? I think people care more about that then anything else.
Because I've spent countless days on 4.4, I know how it works. Its actually pretty simple, way less complicated than when I first started with it. And I rather help those that were smart enough to stay on the 4.4 bootloader and waited for the mofo flashable 5.1 rom. Because anyone who cared or even had the fainted idea about exploits knew better than to upgrade, when they could STILL get 5.1, but would have to wait... like what less than a week before the first flashable image appeared?
5.1:
How it works: Nobody has a clue because the 4.4 loophole is patched.
4.4
How it works: (I'm just making an example don't pick apart my math or partition sizes)
system.img = 3.5gb
cache partition = 1.5gb
So with a modified fastboot, you will write to the cache partition, but send more than 1.5gb of data, since the /system partition is next in order anything you send now will actually write to /system and not the /cache partition.
There are a few quirks I've seen, fastboot sends the "download" command 2x back to back, while the first "download" command hardly sends anything. This has something I assume to be "fake writing" Not quite sure. Its like it writes a tiny amount of data to /cache, sends the second "download" command to now write to /system. I've noticed that the data sent to /cache is actually a clone of a portion of the data sent to /system. Also there is 3gb of ram on the device, so after that gets filled up, the flash command is sent, then it goes back to download commands.
At the end it erases /cache because its full of garbage.
koftheworld said:
Why not apply yourself to figuring out how to root 5.1, maintain root upgrading to 5.1, or how to use mofo to flash 5.1? I think people care more about that then anything else.
Click to expand...
Click to collapse
SaschaElble said:
Because I've spent countless days on 4.4, I know how it works. Its actually pretty simple, way less complicated than when I first started with it. And I rather help those that were smart enough to stay on the 4.4 bootloader and waited for the mofo flashable 5.1 rom. Because anyone who cared or even had the fainted idea about exploits knew better than to upgrade, when they could STILL get 5.1, but would have to wait... like what less than a week before the first flashable image appeared?
Click to expand...
Click to collapse
Fair enough that is exactly why I stayed on kk.
I still have not had anyone help out. If done right, nothing will be wiped or corrupted. Just need someone who has flashed a modded /system using mofo and still have that .img file. Flashing the same file again wont harm anything and will get me the info needed.
Does anyone have any info on the lolipop .img s
SaschaElble said:
I still have not had anyone help out. If done right, nothing will be wiped or corrupted. Just need someone who has flashed a modded /system using mofo and still have that .img file. Flashing the same file again wont harm anything and will get me the info needed.
Click to expand...
Click to collapse
I'm interested in helping, but I'm not interested in giving you remote access to my computer. No offense, I just don't know you and really have no reason to trust you. If you give me instructions on how to generate the log file that you want, I'll be happy to do it. I'm tech savvy enough to modify system images, so you shouldn't have to dumb it down too much for me.
TheSt33v said:
I'm interested in helping, but I'm not interested in giving you remote access to my computer. No offense, I just don't know you and really have no reason to trust you. If you give me instructions on how to generate the log file that you want, I'll be happy to do it. I'm tech savvy enough to modify system images, so you shouldn't have to dumb it down too much for me.
Click to expand...
Click to collapse
just use a vm...
Michaelmansour1997 said:
just use a vm...
Click to expand...
Click to collapse
Good idea. I'd be willing to do that.
Okay,
Download USBlyzer
Turn on device in fastboot mode
Open USBlyzer
On the left hand side of USBlyzer, watch, while you plug in the device
checkmark the new device in USBlyzer in the left hand side (should say xt1254 or turbo or fastboot or anything that indicates the turbo)
click "start capture" in USBlyzer
Open mofo and flash your rom as usual.
When mofo is done, go back to USBlyzer and save the capture log where you will remember.
That log data contains your device serial and UID for your turbo... Thanks for helping the turbo community!
TheSt33v said:
I'm interested in helping, but I'm not interested in giving you remote access to my computer. No offense, I just don't know you and really have no reason to trust you. If you give me instructions on how to generate the log file that you want, I'll be happy to do it. I'm tech savvy enough to modify system images, so you shouldn't have to dumb it down too much for me.
Click to expand...
Click to collapse
That should work
Michaelmansour1997 said:
just use a vm...
Click to expand...
Click to collapse
SaschaElble said:
Okay,
Download USBlyzer
Turn on device in fastboot mode
Open USBlyzer
On the left hand side of USBlyzer, watch, while you plug in the device
checkmark the new device in USBlyzer in the left hand side (should say xt1254 or turbo or fastboot or anything that indicates the turbo)
click "start capture" in USBlyzer
Open mofo and flash your rom as usual.
When mofo is done, go back to USBlyzer and save the capture log where you will remember.
Enjoy uploading 5-8gb of log data since you don't trust me being on your computer. Oh and since we are talking trust, that log data contains your device serial and UID for your turbo... SO actually you might not even want to do that either. Thanks for helping the turbo community!
Click to expand...
Click to collapse
I think I can handle that. Unless you were planning on coming to my house with a flash drive, I'm pretty sure a large file transfer was inevitable, so I'm okay with uploading it somewhere. Thanks for the info about the sensitive information though. If I can figure out how to remove that from the log, I will do so before sending it to you. If I can't, I'll consider sending it to you anyway. If I can't do any of that (because, you know, apparently I'm a moron for not immediately realizing that I could use a VM to have you do this exact same thing), then sorry for bugging you.
TheSt33v said:
I think I can handle that. Unless you were planning on coming to my house with a flash drive, I'm pretty sure a large file transfer was inevitable, so I'm okay with uploading it somewhere. Thanks for the info about the sensitive information though. If I can figure out how to remove that from the log, I will do so before sending it to you. If I can't, I'll consider sending it to you anyway. If I can't do any of that (because, you know, apparently I'm a moron for not immediately realizing that I could use a VM to have you do this exact same thing), then sorry for bugging you.
Click to expand...
Click to collapse
Open the log (ends in .ulz) in a hex editor such as HxD, and you can zero out your serial and UID, I apologise for the rude response. I've surprisingly had lots of resistance getting everyone on the same page here on xda. I did screw up by posting a modded mofo package, but that needs to be water under the bridge. I'm working on making a legit version.
The part that was surprising is how a few people had the knowledge on how to make a clean and 100% original version but refused to share it or gave vague hints.
SaschaElble said:
Open the log (ends in .ulz) in a hex editor such as HxD, and you can zero out your serial and UID, I apologise for the rude response. I've surprisingly had lots of resistance getting everyone on the same page here on xda. I did screw up by posting a modded mofo package, but that needs to be water under the bridge. I'm working on making a legit version.
The part that was surprising is how a few people had the knowledge on how to make a clean and 100% original version but refused to share it or gave vague hints.
Click to expand...
Click to collapse
No worries. I've been following your posts. I don't really care about who you piss off. You seem to be knowledgeable/talented enough to recreate and improve upon mofo, and that's good enough for me. Just promise me that you'll send me a copy of whatever you come up with if you get yourself banned again .
I'll start the process as soon as I'm near my PC, and I'll pm you a link as soon as the upload is complete.
TheSt33v said:
No worries. I've been following your posts. I don't really care about who you piss off. You seem to be knowledgeable/talented enough to recreate and improve upon mofo, and that's good enough for me. Just promise me that you'll send me a copy of whatever you come up with if you get yourself banned again .
I'll start the process as soon as I'm near my PC, and I'll pm you a link as soon as the upload is complete.
Click to expand...
Click to collapse
lol. I will for sure! But I won't get banned again. Not if everyone plays by the same rules they expect me to.
Anyone is free to contact me at (Edit: I was such an idiot. 5 years later... wow. ) If you want an easy two click way to get onto my channel on IRC follow the link in my signature.
if i was rooted id help, but i have one turbo on lolipop and one bricked which is supposed to be on lolipop
Michaelmansour1997 said:
if i was rooted id help, but i have one turbo on lolipop and one bricked which is supposed to be on lolipop
Click to expand...
Click to collapse
I would buy the bricked one, or you can let me see if I can fix it remotely.
NEW:
My vouching thread for those who I request access to their device remotely or gain knowledge of sensitive information:
http://forum.xda-developers.com/general/off-topic/saschaelble-vouching-thread-want-help-t3150299
Do you have a hangouts
(originally posted in the flashfire threads, but it was suggested I post here)
My apologies if this has already been covered (I could not find an answer in searching)
I appreciate that it can be dangerous to use flashfire to flash the bootloader partition and that one should use fastboot. My question is:
If I download a FW package and the bootloader has changed, what happens if I flash to the kernel, system, cache, vendor etc... and do not flash to bootloader and radio? Will the flash fail; will the phone soft brick; will nothing happen and I can go merrily along?
The question derives from this: If the phone can become unusable with a mismatched bootload and radio to the rest of the images, it would require to unpack the package and check for a version prior to flashing other partitions (so I assume). If I go that far, would it not be easier to not use flashfire and simply manually flash the required files when updates are available?
Thanks
N6, unlocked and rooted (previously always updating latest patches and rerooting myself (using TWRP), but wishing to try flashire)
RLBL said:
(originally posted in the flashfire threads, but it was suggested I post here)
My apologies if this has already been covered (I could not find an answer in searching)
I appreciate that it can be dangerous to use flashfire to flash the bootloader partition and that one should use fastboot. My question is:
If I download a FW package and the bootloader has changed, what happens if I flash to the kernel, system, cache, vendor etc... and do not flash to bootloader and radio? Will the flash fail; will the phone soft brick; will nothing happen and I can go merrily along?
The question derives from this: If the phone can become unusable with a mismatched bootload and radio to the rest of the images, it would require to unpack the package and check for a version prior to flashing other partitions (so I assume). If I go that far, would it not be easier to not use flashfire and simply manually flash the required files when updates are available?
Thanks
N6, unlocked and rooted (previously always updating latest patches and rerooting myself (using TWRP), but wishing to try flashire)
Click to expand...
Click to collapse
it is really rare that a bootloader flash is required, and a radio update is never required. if you dont flash them, then you just dont flash them, thats all.
I'd add that going to a major update you'll want to pay close attention. The bootloader probably will need updating. e.g. lollipop to MM, the bootloader had to be updated.
The radio is optional and often with trial and error, you'll find a particular one that for your hardware, in your area, you get the best signal. There is a thread with N6 flashable radios here: http://forum.xda-developers.com/showthread.php?t=3066052.
Had you posted that you had an N6 in your original post, I'd have helped you, because that's what I use
ktmom said:
I'd add that going to a major update you'll want to pay close attention. The bootloader probably will need updating. e.g. lollipop to MM, the bootloader had to be updated.
The radio is optional and often with trial and error, you'll find a particular one that for your hardware, in your area, you get the best signal. There is a thread with N6 flashable radios.
Had you posted that you had an N6 in your original post, I'd have helped you, because that's what I use
Click to expand...
Click to collapse
both mm a lollipop, i never updated my bootloader. i did update it after mm though.
ktmom said:
I'd add that going to a major update you'll want to pay close attention. The bootloader probably will need updating. e.g. lollipop to MM, the bootloader had to be updated.
The radio is optional and often with trial and error, you'll find a particular one that for your hardware, in your area, you get the best signal. There is a thread with N6 flashable radios here: http://forum.xda-developers.com/showthread.php?t=3066052.
Had you posted that you had an N6 in your original post, I'd have helped you, because that's what I use
Click to expand...
Click to collapse
Oh That looks interesting. My Cellular signal sucks even though I am supposedly close to some towers. I am going to try using flashfire with these (hope I don't brick myself lol)
So I assume that when N comes out officially and I need to change bootloaders, I would do so via fasboot, then afterwards I can the the updates via fashfire.
RLBL said:
Oh That looks interesting. My Cellular signal sucks even though I am supposedly close to some towers. I am going to try using flashfire with these (hope I don't brick myself lol)
So I assume that when N comes out officially and I need to change bootloaders, I would do so via fasboot, then afterwards I can the the updates via fashfire.
Click to expand...
Click to collapse
all the radios, and bootloaders, are available in flashable zip for here on xda as well. to flash via twrp recovery
simms22 said:
all the radios, and bootloaders, are available in flashable zip for here on xda as well. to flash via twrp recovery
Click to expand...
Click to collapse
Cool... But I only used TWRP to flash the SU binaries to root. Now that I am rooted, I figured I could simply go back to stock recovery* and use flashfire going forward.
* I figured that because I had no other use for for a custom recovery presently, I may as well stay completely stock and rooted. Furthermore, from my understanding (which can be wrong) I no longer need a custom recovery to flash/install anything, as flashfire can do it all. Of course that brings one to ask "why am I rooted if I am staying stock?". I root my device so I can simulate a power button press without cancelling smart lock operations (either through tasker shell keyevent, gravity screen, or nova prime swipe gesture). I like not having to use the buttons on my phone
Why get rid of custom recovery? Just leave it and keep a backup on hand, then when there is an issue with basically anything you can just restore your backup instead of freaking out and running here using caps and exclamation marks asking how to fix.
scryan said:
Why get rid of custom recovery? Just leave it and keep a backup on hand, then when there is an issue with basically anything you can just restore your backup instead of freaking out and running here using caps and exclamation marks asking how to fix.
Click to expand...
Click to collapse
1 - why use a custom recovery if I do not need to (serious question, not being confrontational - see below)
2 - I totally know how to flash to whatever I want without using any toolkits (and ofc using a custom recovery)
3 - Why would one assume that one panics? (just because I have a low post count and admittedly an Android noob - N6 1st phone - does not mean I am an idiot)
4 - Considering I am not using custom ROMs and staying stock, I would think the likelihood of things going wrong is low (could be totally wrong there lol but I have done everything myself manually since the get go (never even taken an OTA for my upgrades), and never had 1 issue as of yet. This post was a general question in nature. It was not posted because I needed something to be fixed)
If I do not need it, why have it: I am experimenting to see if I can use FF completely stock (and rooted). Please provide some rationale as to why I should keep a custom recovery so I can evaluate (you may be 100% right). The point is: from my understanding one can use FF without a custom recovery so why not try... so far, so good.
On backups: be aware (not that you should care, but you did comment)... I have nothing on my phone that requires backing up at that... I can completely wipe the phone and it only takes time to do a google restore and I am back to where I am (been there, done that. Annoying for time though lol but I have no data on the phone safe from tasker profiles which are on my google drive and easily restored).
And what happens when you flash a bootloader and something screws up? You can't fix it from the stock recovery menu, now can you. So what not have something useful on the recovery partition for that 1 and 1000 chance something goes wrong.... Just my opinion, being I've been flashing phones since the first Android device was released on T-Mobile. The g1 (still have and still flash Roms
Sent from my Nexus 6 using XDA Free mobile app
RLBL said:
1 - why use a custom recovery if I do not need to (serious question, not being confrontational - see below)
2 - I totally know how to flash to whatever I want without using any toolkits (and ofc using a custom recovery)
3 - Why would one assume that one panics? (just because I have a low post count and admittedly an Android noob - N6 1st phone - does not mean I am an idiot)
4 - Considering I am not using custom ROMs and staying stock, I would think the likelihood of things going wrong is low (could be totally wrong there lol but I have done everything myself manually since the get go (never even taken an OTA for my upgrades), and never had 1 issue as of yet. This post was a general question in nature. It was not posted because I needed something to be fixed)
If I do not need it, why have it: I am experimenting to see if I can use FF completely stock (and rooted). Please provide some rationale as to why I should keep a custom recovery so I can evaluate (you may be 100% right). The point is: from my understanding one can use FF without a custom recovery so why not try... so far, so good.
On backups: be aware (not that you should care, but you did comment)... I have nothing on my phone that requires backing up at that... I can completely wipe the phone and it only takes time to do a google restore and I am back to where I am (been there, done that. Annoying for time though lol but I have no data on the phone safe from tasker profiles which are on my google drive and easily restored).
Click to expand...
Click to collapse
1. the only one important thing about having twrp installed.. backups and restores. before dlashing or changing anything, i akways create a backup in twrp. if something doesnt work out, you can always restore your backup, as ive done many many times. its a quicky fix it.
31ken31 said:
And what happens when you flash a bootloader and something screws up? You can't fix it from the stock recovery menu, now can you. So what not have something useful on the recovery partition for that 1 and 1000 chance something goes wrong.... Just my opinion, being I've been flashing phones since the first Android device was released on T-Mobile. The g1 (still have and still flash Roms
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I think that was the whole point of my post was it not? What happens if you DON'T flash a bootloader while using FF (but in the case where it did change)? And like I said, in the 1/1000 chance that something does go wrong and I did not have a backup: Flash the complete package via adb? Like I said, I have nothing to backup, thus nothing to recover. Not saying I shouldn't, just saying I don't. I only used TWRP to gain root access, nothing more (no custom ROMs, kernels, optimizations, anything on my phone...not even local app data saves - I am one of those old farts who uses their phone as a PDA with phone capabilities and that is it. All "data" is cloud based for calendar info etc.)
It was a relatively simple (general) question around some experimentation I am doing to see if it would work if one was completely stock (safe from root); did not think it would turn in an philosophical argument on whether or not one should use a stock recovery (which I have been using a custom up until yesterday, but was thinking about putting it back on this evening anyways, just because)
Anyways, got my answer... thx
simms22 said:
1. the only one important thing about having twrp installed.. backups and restores. before dlashing or changing anything, i akways create a backup in twrp. if something doesnt work out, you can always restore your backup, as ive done many many times. its a quicky fix it.
Click to expand...
Click to collapse
Thanks!... Obviously when I do venture into more with the phone I will do that. Currently it is a work and personal device so the only thing I do is flash Google stock builds instead of waiting for OTAs. Not saying I should not have a backup, but I don't. Only once after the 1st flash I re-locked the bootloader (as per instructions). What I waste of time; but it did show me that in a non-efficient disaster recovery, I can get everything back to where I was.
A restore would have been efficient, but I have found that I really have nothing to back up.. yet.
I guess a (off-topic) question I have for you is: What and Why did things not work out? In my case where I am only flashing stock loads (not waiting for OTAs), what could one anticipate going wrong that a re-flash could not recover from, but a restore could? Example a write corruption of a partition and the only thing I can do is boot into recovery as my PC cannot see the phone via adb? Can something like that happen?
Backing up system is what saves your a**
Sent from my Nexus 6 using XDA Free mobile app
31ken31 said:
Backing up system is what saves your a**
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
cool... but... what if you are stock? Save my ass from what? Will a (re)flash of stock binaries not suffice?
Look I appreciate I am sounding argumentative, but I am curious to understand what can happen and why. I can understand the "need" to do it if customizing a device etc... but I am very curious as to why if you are stock:
example:
A stock user unlocks his bootloader so they can flash files straight from google be it OTAs or the complete package. It is not listed anywhere to have a custom recovery in their instructions which would lead one to believe it is not required if flashing said files... I assume something could go wrong of course and the most efficient way is to do a restore from backup... but I also assume one could simply re-flash and start over.
I am not devaluating the merits of a custom recovery; I was just curious if one could use (easily) flash fire without one - and one can. The purpose of the question was two-fold:
- because I was flashing stock, then reflashing twrp to get root I found the process longer than it needed to be so I thought I could use flashfire and have it do it for me.
- then I realized that flashing re-roots as well so I did not need to flash the custom recovery to obtain root. I thought "hey what if I accidentally checked "recovery" and accidentally went back to stock. No harm done as I can move on and still be rooted.
Not sure my butt needs saving to ask. You may be doing something that having backups is a good and safe idea... what if you are not? No harm in still using a custom of course, but it was just a question (I ask such questions so I know in advance why something happened and what to do so I do not come running to forums in all caps as someone else said lol)
off topic: If one has nothing to backup, what is there to restore?
RLBL said:
cool... but... what if you are stock? Save my ass from what? Will a (re)flash of stock binaries not suffice?
Look I appreciate I am sounding argumentative, but I am curious to understand what can happen and why. I can understand the "need" to do it if customizing a device etc... but I am very curious as to why if you are stock:
example:
A stock user unlocks his bootloader so they can flash files straight from google be it OTAs or the complete package. It is not listed anywhere to have a custom recovery in their instructions which would lead one to believe it is not required if flashing said files... I assume something could go wrong of course and the most efficient way is to do a restore from backup... but I also assume one could simply re-flash and start over.
I am not devaluating the merits of a custom recovery; I was just curious if one could use (easily) flash fire without one - and one can. The purpose of the question was two-fold:
- because I was flashing stock, then reflashing twrp to get root I found the process longer than it needed to be so I thought I could use flashfire and have it do it for me.
- then I realized that flashing re-roots as well so I did not need to flash the custom recovery to obtain root. I thought "hey what if I accidentally checked "recovery" and accidentally went back to stock. No harm done as I can move on and still be rooted.
Not sure my butt needs saving to ask. You may be doing something that having backups is a good and safe idea... what if you are not? No harm in still using a custom of course, but it was just a question (I ask such questions so I know in advance why something happened and what to do so I do not come running to forums in all caps as someone else said lol)
off topic: If one has nothing to backup, what is there to restore?
Click to expand...
Click to collapse
its all a matter of choice, period.
flashing stock, you dont need to do anything. flashing different mods, custom roms, gapps, or supersu, you need to use twrp recovery. you can even flash twrp to be permenant or flash twrp for a one time use. if you are flashing custom roms/mods regularly, its convieniant to have twrp, if your not it doesnt matter. but the one thing twrp is great for is backing up, in case. and you dont need many back ups, just one recent backup. so you can back up, then get rid of twrp until needed again. anyways, its all a personal choice, and thats all it is. for me, flashing twrp then leaving it makes sense, since ill never ever do anything stock. for you, you have your own needs and wants.
simms22 said:
its all a matter of choice, period.
flashing stock, you dont need to do anything. flashing different mods, custom roms, gapps, or supersu, you need to use twrp recovery. you can even flash twrp to be permenant or flash twrp for a one time use. if you are flashing custom roms/mods regularly, its convieniant to have twrp, if your not it doesnt matter. but the one thing twrp is great for is backing up, in case. and you dont need many back ups, just one recent backup. so you can back up, then get rid of twrp until needed again. anyways, its all a personal choice, and thats all it is. for me, flashing twrp then leaving it makes sense, since ill never ever do anything stock. for you, you have your own needs and wants.
Click to expand...
Click to collapse
Thank you for answering the question.
I figure when this phone (or whichever phone) is not my daily driver and no longer linked to sensitive stuff I will start venturing into the domain of custom ROMs and Kernels.
RLBL said:
Thank you for answering the question.
I figure when this phone (or whichever phone) is not my daily driver and no longer linked to sensitive stuff I will start venturing into the domain of custom ROMs and Kernels.
Click to expand...
Click to collapse
custom recoveries just make things easier for you, overall, to do stuff. but kernels, that could be the bomb. but you will need to learn about how to use governors/schedulers to make any kind of headways. for example, i use a completely different governor/scheduler(ondemand/deadline) than any other nexus kernel, and i feel that my way makes my phone much better/faster than any other setup. and thats whats important to me
Update: test passed (I knew it would)
With a stock recovery, I was able to use flashfire and upgrade to the latest update and re-root.