Database Info

[Q] Rooting Photon Q LOST and CONFUSED

Hi, I am new to this and decided I need to root my Photon so I can use it as a WIFI hotspot for my Samsung Galaxy Note 10.1 Tablet. I have read so much I am totally lost and confused. I have tried pdanet foxfi(which did work with my laptop but that is now unusable) and such but I can only browse web on my tablet and nothing else. Every app says check internet conection or wifi connection. I need to be able to use apps that require wifi such as team viewer. Please help. I don't know the first thing about this.
I have sprint (regrettably stuck for 2 years now) but love my photon. If someone can post a link with like 1 2 3 type steps it would be fantastic. I know zilch and the more I read the less I know like minus zilch lol. I find using my tablet is so much easier too read that I would rather use it if I can for internet stuff versus my phone.
Thank you.

Is your device rooted and the bootloader unlocked?
Have you considered CyanogenMod or another custom ROM? Tethering works out of the box on most of those.
When I was on the stock ROM (before CM was on the device...) I used a wifi tether app from the Play Store, but you did have to be rooted to use it.

Mehuman2 said:
If someone can post a link with like 1 2 3 type steps it would be fantastic.
Click to expand...
Click to collapse
The link in my signature might help you.

arrrghhh said:
Is your device rooted and the bootloader unlocked?
Have you considered CyanogenMod or another custom ROM? Tethering works out of the box on most of those.
When I was on the stock ROM (before CM was on the device...) I used a wifi tether app from the Play Store, but you did have to be rooted to use it.
Click to expand...
Click to collapse
Haven't considered anything yet, am just learning bout this. Phone is standard, no unlocking or anything. I am just leaning terms also. I don't know how to unlock or root. So neither are done. Have no idea about ROMs yet. As I said, am just starting so forgive me for being ignorant of these things at this time.

Mehuman2 said:
Haven't considered anything yet, am just learning bout this. Phone is standard, no unlocking or anything. I am just leaning terms also. I don't know how to unlock or root. So neither are done. Have no idea about ROMs yet. As I said, am just starting so forgive me for being ignorant of these things at this time.
Click to expand...
Click to collapse
No worries.
I think there's still a way to root without unlocking - but here's the jist.
Unlocking allows you to do anything - custom recovery, custom ROM, whatever you please. Rooting only allows apps on your device root access - so you still have stock recovery, stock ROM.

arrrghhh said:
Is your device rooted and the bootloader unlocked?
Have you considered CyanogenMod or another custom ROM? Tethering works out of the box on most of those.
When I was on the stock ROM (before CM was on the device...) I used a wifi tether app from the Play Store, but you did have to be rooted to use it.
Click to expand...
Click to collapse
Solust said:
The link in my signature might help you.
Click to expand...
Click to collapse
Thank you. Am going to look at link now.

arrrghhh said:
No worries.
I think there's still a way to root without unlocking - but here's the jist.
Unlocking allows you to do anything - custom recovery, custom ROM, whatever you please. Rooting only allows apps on your device root access - so you still have stock recovery, stock ROM.
Click to expand...
Click to collapse
Thank you. I see the difference now. I wouldn't mind both then. I just hope I don't brick it. I believe that means I don't want to make it into a paperweight.

Mehuman2 said:
Thank you. I see the difference now. I wouldn't mind both then. I just hope I don't brick it. I believe that means I don't want to make it into a paperweight.
Click to expand...
Click to collapse
lol, yes. Unlocking is pretty simple, just make sure you are getting the code correct - has to match exactly!
The only downside is the official warranty is voided - but if you have insurance with your provider, they should still honor it. Just the manufacturer warranty is voided.

arrrghhh said:
lol, yes. Unlocking is pretty simple, just make sure you are getting the code correct - has to match exactly!
The only downside is the official warranty is voided - but if you have insurance with your provider, they should still honor it. Just the manufacturer warranty is voided.
Click to expand...
Click to collapse
I get off work in a few hours and after some sleep will go try that link up above. Desktop running xp. Have never connected photon to PC yet. Hopefully will go smoothly.

You should be fine running XP. The instructions from Windows 7 should be the same and if not they should be similar enough that you know what to do. I put the disclaimer in there because I don't like saying "this is how you do this" without having tested it first hand.

I installed the drivers and SDK now onto the rest hopefully tomorrow as I didn't want to start with only a few minutes left before I had to come to work.
Sent from my XT897

Solust said:
You should be fine running XP. The instructions from Windows 7 should be the same and if not they should be similar enough that you know what to do. I put the disclaimer in there because I don't like saying "this is how you do this" without having tested it first hand.
Click to expand...
Click to collapse
I have the files downloaded and installed. My says there is a problem with my device. I am trying to go to explorer so I can copy files to my desktop so I don't lose them but I can't get it to show up in my list of drives.
I have to work til 6pm or so therefore I won't be able to try anything til I get home. I remember the last Motorola I had also (Droid 3), I could never "sync" to my pc as my pc wouldn't recognize it to let me view files. Can anyone tell me what I am missing? I will reconnect my phone tonite and get the exact messages that the pc are telling me when I connect my phone. Thank you

Still can't get PC to recognize phone.
Sent from my XT897

Mehuman2 said:
Still can't get PC to recognize phone.
Sent from my XT897
Click to expand...
Click to collapse
Different cable? Different port? Different PC?
Are you sure the drivers are installed? Does the PC make a sound when you plug it in, indicating that it recognized *something* being plugged in?
How does it show up in device manager?
Please give us as much detail as you possibly can. What you've tried, etc.

Also, if you have debugging on turn it off, or if it's off, turn it on.
Sent from my SPH-D700 using Tapatalk 2

[Q] The hardest rescue

Hi everyone!
Just a little question, as I'm facing this situation right here:
is there a way to revive a phone that doesn't boot, nor lets me access recovery mode or fastboot or bootloader?

UltimateGoblin said:
Hi everyone!
Just a little question, as I'm facing this situation right here:
is there a way to revive a phone that doesn't boot, nor lets me access recovery mode or fastboot or bootloader?
Click to expand...
Click to collapse
Which phone are you talking about?

I'm talking about the Alcatel V860. It's absolutely an uncommon model, that's the reason why I'm speaking in general.

UltimateGoblin said:
I'm talking about the Alcatel V860. It's absolutely an uncommon model, that's the reason why I'm speaking in general.
Click to expand...
Click to collapse
Please ask specific questions as its related to the phone model. I'm not hopefully about it. You can get it serviced by "bootloader repair" Should be about 40$.
Some of the more common phones can be unbricked on your own.

LS.xD said:
Please ask specific questions as its related to the phone model. I'm not hopefully about it. You can get it serviced by "bootloader repair" Should be about 40$.
Some of the more common phones can be unbricked on your own.
Click to expand...
Click to collapse
I've already posted here, but I received only one answer, so I decided to speak more general just to know if it is theoretically possible to rescue a phone in the situation I described.
Anyway, do you think that there is no way that the pc can communicate with a phone that doesn't even reach the bootloader?

Ok, I'll ask a different question: the phone I'm talking about ended up this bad while flashing an official OTA.
How is that possible?
I thought there was no possible way that an OTA messed with the bootloader, or the recovery... or fastboot! Doesn anyone know what could possibly have gone wrong during the update?

UltimateGoblin said:
Ok, I'll ask a different question: the phone I'm talking about ended up this bad while flashing an official OTA.
How is that possible?
I thought there was no possible way that an OTA messed with the bootloader, or the recovery... or fastboot! Doesn anyone know what could possibly have gone wrong during the update?
Click to expand...
Click to collapse
Actually, it seems like your phone is bricked, there are some methods to unbrick some phones but I don't know if they would work for you, just try to do a Google search how to unbrick a bricked phone, and it might return with some useful stuff, try everything that's possible, because nothing worst can happen over a brick(except it can blast in your hand if you connect a high voltage in place of battery)(lol, it won't happen! )
Hit Thanks if I helped sent from my SM-T211

Already done that, I'm giving up if my pc cannot communicate with the phone.
At this point I'd only like to know how could an OTA corrupt the bootloader.

UltimateGoblin said:
Already done that, I'm giving up if my pc cannot communicate with the phone.
At this point I'd only like to know how could an OTA corrupt the bootloader.
Click to expand...
Click to collapse
Only thing you can do now is, go to store(from where you buy your phone, act dumb and tell them that this won't turn on, they might replace your phone!
Hit Thanks if I helped sent from my SM-T211

Thanks. Anyone else?

UltimateGoblin said:
Thanks. Anyone else?
Click to expand...
Click to collapse
So, what exactly you did?
Hit Thanks if I helped sent from my SM-T211

It wasn't me, it was my cousin, who flashed an OTA which apparently corrupted all the layers of the OS. I believe him, but I find it incredibly difficult to happen, so I wanted to know if that could really happen.

UltimateGoblin said:
It wasn't me, it was my cousin, who flashed an OTA which apparently corrupted all the layers of the OS. I believe him, but I find it incredibly difficult to happen, so I wanted to know if that could really happen.
Click to expand...
Click to collapse
What do you mean by ota corrupting all layers of os?
I never heard of it.
Hit Thanks if I helped sent from my SM-T211

It means that the flashing went bad and now the phone is unusable. I cannot make it communicate with the pc. No access to recovery nor bootloader nor fastboot nor anything.

UltimateGoblin said:
It means that the flashing went bad and now the phone is unusable. I cannot make it communicate with the pc. No access to recovery nor bootloader nor fastboot nor anything.
Click to expand...
Click to collapse
Try smart phone flash tool(on pc), I recently came across a thread in which author said he have a hard bricked xolo phone and it don't boot to anything, but responds to SP Flash tool. Give it a try, if might work.
I don't have it's link, Google it
Hit Thanks if I helped sent from my SM-T211

UltimateGoblin said:
It means that the flashing went bad and now the phone is unusable. I cannot make it communicate with the pc. No access to recovery nor bootloader nor fastboot nor anything.
Click to expand...
Click to collapse
Did that worked?
Sent from my SM-T211 using xda app-developers app

[Q] Considering rooting the Nexus 5

So I have a black Nexus 5 with a capacity of 16GB. The device is only about 4 months old, so I still have it covered with warranty until June 2016. The device is as good as new and I'm very happy with it because everything is so fast and smooth.
Recently I've been thinking about rooting the device for maybe some little extras. For example, I have GTA SA installed but I would like to play it with the Cleo mod to have a little bit more fun. Or maybe I'll install some kind of adblocker so I could enjoy my brand new phone without the annoying gold diggers. Or perhaps I want to hide some apps from my app drawer so it would look neat and organised. Or I would like to install an apk that isn't available for non-rooted devices. Or in case I want to see the battery percentage next to the time display or anything like that.
As you can see I would only want to root it for rather small reasons. I definitely don't want to overclock anything because it already meets my criteria for speed, nor do I want to install any custom ROMs because I really like the pure android experience. So I have a few questions because I'm a total noob at the field of tweaking android:
Is my current data going to be wiped if I would want to root it?
I'm aware of the upcoming Android L release, so would I be able to update it right away (remember, I'm not going to use any custom ROMs) or would I have to unroot and reset everything first?
In case something goes wrong and I want to use my warranty, could any traces be found after I would have unrooted the device? (because rooting voids your warranty, right?)
What would be the top reasons to root the Nexus 5? For example, any features the device should've had but unfortunately hasn't.
And is it actually 100% safe...?
So regarding to the last question... A friend of mine has a rooted Moto G, he made me familiar with rooting and it's probably thanks to him that I'm considering it. Everything was going well but there were a few times that he woke up and his phone wasn't worth more than a brick. Apparently, it was because of some ROM he installed. This probably won't affect me in any way because like I said, I'm not going to install any custom ROMs, but my friend expected everything to be normal while it wasn't. He probably did everything like it should be done but then he suddenly woke up with a brick next to his head. So apparently, even if you do everything exactly like they tell you to do it, there's still a slight chance that it's going to end up badly, right?
So basically, I'm considering rooting my device but I'm still not sure what I would have to do because there are lots of tutorials and everything is quite confusing and I have some questions. All the help would be greatly appreciated, thanks in advance!

root/unlockbootloader/install twrp&busybox no data loss
root/unlockbootloader/install twrp&busybox no data loss without P.C, okay here we go mod's remove if you think it's not helping. download towelroot by geohot,now the rest from playstore, es file exploer,super su,busybox,reboot app,nexus unlock bootloader,
make sure you have security unknowen sources ticked and verify apps unticked.
download towelroot from chrome with es file exploer open and install hit make it rain tab, next install busybox,next install super su app.unlockbootloader with in the app.,install twrp and auto install recovery for hammerhead from twrp, now you should have full root after reboot.super user and busybox unlocked bootloader and twrp installed, and you know what the reboot app is for . no data loss and without a P.C, or you could use fastboot install just look in Q&A, kind regard's joe hope this help's.

Spaceblow said:
Is my current data going to be wiped if I would want to root it?
Click to expand...
Click to collapse
Yep; when you unlock bootloader of your device (before root), all of data will be wiped.
Spaceblow said:
I'm aware of the upcoming Android L release, so would I be able to update it right away (remember, I'm not going to use any custom ROMs) or would I have to unroot and reset everything first?
Click to expand...
Click to collapse
Nope. When you upgrade to Android L, it might be overwrite existing system clearly.
Spaceblow said:
In case something goes wrong and I want to use my warranty, could any traces be found after I would have unrooted the device? (because rooting voids your warranty, right?)
Click to expand...
Click to collapse
We are using Google Nexus. Just revert with Nexus Factory Image.
http://developers.google.com/android/nexus/images
Spaceblow said:
What would be the top reasons to root the Nexus 5? For example, any features the device should've had but unfortunately hasn't.
Click to expand...
Click to collapse
In my case, to connect NTFS filesystem.
Spaceblow said:
And is it actually 100% safe...?
Click to expand...
Click to collapse
Maybe, but it's at your own risk.

Jongmin Kim said:
Yep; when you unlock your device (before root), all of data will be wiped.
Nope. When you upgrade to Android L, it might be overwrite existing system clearly.
No. We are using Google Nexus. Just revert with Nexus Factory Image.
http://developers.google.com/android/nexus/images
In my case, to connect NTFS filesystem.
Maybe, but it's at your own risk.
English is too difficult... I'm trying to understand right now.
Click to expand...
Click to collapse
root and then unlock bootloader with the app from playstore. has to be this way. regard's p.s no data wiped ,

Spaceblow said:
So I have a black Nexus 5 with a capacity of 16GB. The device is only about 4 months old, so I still have it covered with warranty until June 2016. The device is as good as new and I'm very happy with it because everything is so fast and smooth.
Click to expand...
Click to collapse
First of all:
Lethargy said:
I think OP got his question reversed. Should be:
"Why buy a Nexus 5 if you're not going to root?"
:angel:
Click to expand...
Click to collapse
Spaceblow said:
So I have a few questions because I'm a total noob at the field of tweaking android:
Is my current data going to be wiped if I would want to root it?
I'm aware of the upcoming Android L release, so would I be able to update it right away (remember, I'm not going to use any custom ROMs) or would I have to unroot and reset everything first?
In case something goes wrong and I want to use my warranty, could any traces be found after I would have unrooted the device? (because rooting voids your warranty, right?)
What would be the top reasons to root the Nexus 5? For example, any features the device should've had but unfortunately hasn't.
And is it actually 100% safe...?
Click to expand...
Click to collapse
1. Unlocking the bootloader is what wipes the data partition, not root access.
2. Don't bother with OTAs to update, they're too much of a bother to try to get to work, when you can just flash factory images/zip, most likely before you even get the OTA pushed to you.
3. Depends where you bought it from. If you got it off the Play Store, then Google does not care about the software you have on your device as long as it's a legitimate manufacturing fault covered by the warranty. You can RMA to Google with a custom ROM and kernel if you wanted to. If you bought it from elsewhere, You'll have to send it to LG for repair. It's possible to reflash factory images and reset the tamper flag, there isn't anything else on the Nexus 5 that will tell LG anything. The easiest way is using LG Flashtool, which can be found in the first link of my signature. If your device is completely dead however, it doesn't matter since LG wouldn't be able to boot it up.
4. Root access is simply root access. You get access to /system, and therefore can use root apps and other modifications.
5. The root process itself is pretty much 100% safe. The Nexus 5 is really, really hard to brick, unless you flash something that isn't meant for your device or something similar, so user error is the only risk in the process. Software-wise, of course root access comes at some form of a security risk. Just be sure of what apps you're granting root access to and you should have no problem.
Spaceblow said:
So regarding to the last question... A friend of mine has a rooted Moto G, he made me familiar with rooting and it's probably thanks to him that I'm considering it. Everything was going well but there were a few times that he woke up and his phone wasn't worth more than a brick. Apparently, it was because of some ROM he installed. This probably won't affect me in any way because like I said, I'm not going to install any custom ROMs, but my friend expected everything to be normal while it wasn't. He probably did everything like it should be done but then he suddenly woke up with a brick next to his head. So apparently, even if you do everything exactly like they tell you to do it, there's still a slight chance that it's going to end up badly, right?
Click to expand...
Click to collapse
Most likely user error, or simply because a Moto device could be locked down more (which also makes it riskier and harder to restore) and not as easy to develop for. The Nexus 5 is one of the hardest devices to brick (again, excluding user error), and if you have any issues it would either be user error or a bug in the ROM/kernel.
Spaceblow said:
So basically, I'm considering rooting my device but I'm still not sure what I would have to do because there are lots of tutorials and everything is quite confusing and I have some questions. All the help would be greatly appreciated, thanks in advance!
Click to expand...
Click to collapse
Check out the first link of my signature and read some threads before proceeding blindly.
There are ways to gain root access without unlocking the bootloader and without a PC as mentioned above, but it's recommended to do it the traditional way by backing up your internal storage to a PC first and using fastboot. Those methods are useful for other devices that are more locked down. This is a Nexus device, it's better to do it properly.

Lethargy said:
First of all:
1. Unlocking the bootloader is what wipes the data partition, not root access.
2. Don't bother with OTAs to update, they're too much of a bother to try to get to work, when you can just flash factory images/zip, most likely before you even get the OTA pushed to you.
3. Depends where you bought it from. If you got it off the Play Store, then Google does not care about the software you have on your device as long as it's a legitimate manufacturing fault covered by the warranty. You can RMA to Google with a custom ROM and kernel if you wanted to. If you bought it from elsewhere, You'll have to send it to LG for repair. It's possible to reflash factory images and reset the tamper flag, there isn't anything else on the Nexus 5 that will tell LG anything. The easiest way is using LG Flashtool, which can be found in the first link of my signature. If your device is completely dead however, it doesn't matter since LG wouldn't be able to boot it up.
4. Root access is simply root access. You get access to /system, and therefore can use root apps and other modifications.
5. The root process itself is pretty much 100% safe. The Nexus 5 is really, really hard to brick, unless you flash something that isn't meant for your device or something similar, so user error is the only risk in the process. Software-wise, of course root access comes at some form of a security risk. Just be sure of what apps you're granting root access to and you should have no problem.
Most likely user error, or simply because a Moto device could be locked down more (which also makes it riskier and harder to restore). The Nexus 5 is one of the hardest devices to brick (again, excluding user error), and if you have any issues it would either be user error or a bug in the ROM/kernel.
Check out the first link of my signature and read some threads before proceeding blindly.
There are ways to gain root access without unlocking the bootloader and without a PC as mentioned above, but it's recommended to do it the traditional way by backing up your internal storage to a PC first and using fastboot. Those methods are useful for other devices that are more locked down. This is a Nexus device, it's better to do it properly.
Click to expand...
Click to collapse
lol yeah i have to agree with you, but i find this help's when on the go,

joecool666 said:
lol yeah i have to agree with you, but i find this help's when on the go,
Click to expand...
Click to collapse
If you don't have access to a PC, or you're using a locked-down Samsung/HTC/Moto/Sony/whatever device, then sure, go ahead and use the exploit methods.
But if you do have access to a PC, and it's a Nexus device, just do it properly, it'll cause fewer possible issues.

Lethargy said:
If you don't have access to a PC, or you're using a locked-down Samsung/HTC/Moto/Sony/whatever device, then sure, go ahead and use the exploit methods.
But if you do have access to a PC, and it's a Nexus device, just do it properly, it'll cause fewer possible issues.
Click to expand...
Click to collapse
i do use my p.c and lg flashtool and fastboot.just incase lol.and it is the better way of doing it, p.s when OTG rooting don't forget to bring the XDA app.

joecool666 said:
root and then unlock bootloader with the app from playstore. has to be this way. regard's p.s no data wiped ,
Click to expand...
Click to collapse
You mean Towelroot? I'm also considering this option because it would be nice to keep all my data.
Lethargy said:
First of all:
1. Unlocking the bootloader is what wipes the data partition, not root access.
2. Don't bother with OTAs to update, they're too much of a bother to try to get to work, when you can just flash factory images/zip, most likely before you even get the OTA pushed to you.
3. Depends where you bought it from. If you got it off the Play Store, then Google does not care about the software you have on your device as long as it's a legitimate manufacturing fault covered by the warranty. You can RMA to Google with a custom ROM and kernel if you wanted to. If you bought it from elsewhere, You'll have to send it to LG for repair. It's possible to reflash factory images and reset the tamper flag, there isn't anything else on the Nexus 5 that will tell LG anything. The easiest way is using LG Flashtool, which can be found in the first link of my signature. If your device is completely dead however, it doesn't matter since LG wouldn't be able to boot it up.
4. Root access is simply root access. You get access to /system, and therefore can use root apps and other modifications.
5. The root process itself is pretty much 100% safe. The Nexus 5 is really, really hard to brick, unless you flash something that isn't meant for your device or something similar, so user error is the only risk in the process. Software-wise, of course root access comes at some form of a security risk. Just be sure of what apps you're granting root access to and you should have no problem.
Most likely user error, or simply because a Moto device could be locked down more (which also makes it riskier and harder to restore) and not as easy to develop for. The Nexus 5 is one of the hardest devices to brick (again, excluding user error), and if you have any issues it would either be user error or a bug in the ROM/kernel.
Check out the first link of my signature and read some threads before proceeding blindly.
There are ways to gain root access without unlocking the bootloader and without a PC as mentioned above, but it's recommended to do it the traditional way by backing up your internal storage to a PC first and using fastboot. Those methods are useful for other devices that are more locked down. This is a Nexus device, it's better to do it properly.
Click to expand...
Click to collapse
This is some great information, thank you very much! So in case I would want to do it manually, this thread has everything I need (in combination with the 15 seconds ADB Installer)?

Spaceblow said:
This is some great information, thank you very much! So in case I would want to do it manually, this thread has everything I need (in combination with the 15 seconds ADB Installer)?
Click to expand...
Click to collapse
Yep. :good: I also recommend using TWRP instead of CWM as your recovery. PhilZ Touch is also another good alternative, but it is no longer maintained and probably won't work for Lollipop's default encryption.
Latest SuperSU is located here, flashable in a custom recovery.

Lethargy said:
Yep. :good: I also recommend using TWRP instead of CWM as your recovery. PhilZ Touch is also another good alternative, but it is no longer maintained and probably won't work for Lollipop's default encryption.
Latest SuperSU is located here, flashable in a custom recovery.
Click to expand...
Click to collapse
Thanks for helping me but I used Towelroot and it works flawlessly!

Spaceblow said:
Thanks for helping me but I used Towelroot and it works flawlessly!
Click to expand...
Click to collapse
Cool. :good:
Even though you now have root access, I recommend using Bootunlocker or whatever app to unlock the bootloader from within Android (which doesn't wipe), then flashing a custom recovery with fastboot while in the bootloader anyways.
Why?
If something goes wrong and your phone doesn't boot, you'll have no choice but to unlock the bootloader WITH a wipe using fastboot, then flash a custom recovery or reflash factory images, unless you've done the above, in which case you can dirty-flash (no wipe) a stock ROM zip downloadable here. :angel:

back up
Spaceblow said:
Thanks for helping me but I used Towelroot and it works flawlessly!
Click to expand...
Click to collapse
make sure you make a back up back up most important,regard's joe

To be clear, the *whole* phone including your sdcard partition will be wiped so make sure you back up before unlocking your bootloader. I would use an app like ES File Explorer and copy all your files to Dropbox or Google Drive if you dont have a computer but you'll need a computer anyway.
Sent from my Nexus 5 using XDA Free mobile app

MrObvious said:
To be clear, the *whole* phone including your sdcard partition will be wiped
Click to expand...
Click to collapse
If we want to be clear, we should also be accurate. The *whole* phone is not wiped. The /data partition is wiped, which includes /data/app (where user apps are stored) /data/data (where user settings and app data is stored) and /data/media (where /sdcard data is stored)

Lethargy said:
Cool. :good:
Even though you now have root access, I recommend using Bootunlocker or whatever app to unlock the bootloader from within Android (which doesn't wipe), then flashing a custom recovery with fastboot while in the bootloader anyways.
Why?
If something goes wrong and your phone doesn't boot, you'll have no choice but to unlock the bootloader WITH a wipe using fastboot, then flash a custom recovery or reflash factory images, unless you've done the above, in which case you can dirty-flash (no wipe) a stock ROM zip downloadable here. :angel:
Click to expand...
Click to collapse
Thanks for the tip but then I'll be unable to receive OTA updates unless I restore everything, including everything being wiped, right?
joecool666 said:
make sure you make a back up back up most important,regard's joe
Click to expand...
Click to collapse
By using Titanium Backup?

Spaceblow said:
Thanks for the tip but then I'll be unable to receive OTA updates unless I restore everything, including everything being wiped, right?
Click to expand...
Click to collapse
All guides and info threads are in my signature. One such INFO thread is OTA help-desk, which explains that you can receive OTA with custom recovery, however there are extra steps.
However, please let me explain 1 thing. OTA is the ultimate noob move. Only root-noobs receive OTA updates. They are the most inconvenient method of updating your OS if you are rooted. Long before you even receive the OTA update, there will be a pre-rooted flashable.zip that can be flashed via recovery.
noobs will often say "but..but..but I wont have to wipe if I accept an OTA"... Little do they know... Even after an official OTA, things screw up. Whenever an OS is upgraded, a wipe is highly recommended as OTA's are imperfect and data between apps and settings conflicts between versions.
OTA is a fools errand if you're rooted. Now you're rooted, leave OTA to the unrooted and learn to manage your rooted device properly. All the info you could ever need is available in my signature as previously mentioned.

Spaceblow said:
Thanks for the tip but then I'll be unable to receive OTA updates unless I restore everything, including everything being wiped, right?
By using Titanium Backup?
Click to expand...
Click to collapse
or helium back up

Owning a Nexus makes fastboot your best friend, especially if you have issues.
Read up on adb/fastboot and forget OTA's. Nothing like a clean fresh install of a new version. And there's many options to save /backup your data and important files.
Without learning fastboot and adb.... Simple fix issues can become major headaches.
Don't be intimidated. Read, learn, then do. ?
---------- Post added at 09:49 AM ---------- Previous post was at 09:48 AM ----------
@rootSU has everything you need in his sticky roll up thread.

rootSU said:
All guides and info threads are in my signature. One such INFO thread is OTA help-desk, which explains that you can receive OTA with custom recovery, however there are extra steps.
However, please let me explain 1 thing. OTA is the ultimate noob move. Only root-noobs receive OTA updates. They are the most inconvenient method of updating your OS if you are rooted. Long before you even receive the OTA update, there will be a pre-rooted flashable.zip that can be flashed via recovery.
noobs will often say "but..but..but I wont have to wipe if I accept an OTA"... Little do they know... Even after an official OTA, things screw up. Whenever an OS is upgraded, a wipe is highly recommended as OTA's are imperfect and data between apps and settings conflicts between versions.
OTA is a fools errand if you're rooted. Now you're rooted, leave OTA to the unrooted and learn to manage your rooted device properly. All the info you could ever need is available in my signature as previously mentioned.
Click to expand...
Click to collapse
Well, you convinced me to take my N5 to a step further.
So I already Towelrooted my phone which gave me root access and an untouched bootloader and recovery. My next step would be to backup every app and all data to be sure in case something goes wrong, this would be done by using Titanium Backup. Then I should be unlocking the bootloader by simply using BootUnlocker for Nexus Devices so I wouldn't get my data wiped (I know I would be able to restore it with my backup but I rather do it a bit faster and less complex). When I did that, I have to head over to this thread and flash TWRP by following the instructions at "2. Installing a Custom Recovery".
So after all these steps my phone would have no limitations and it would be as unlocked as for example your Nexus 5, right?

Marshall London root?

Hey guys,
I really don't know where to ask this since this phone doesn't have a forum or anything - at least that I know of. If there is one I am glad if you can point me to it.
So, is there any way to root this device? I only bought it as a second phone for listening to music but I'd really like to root it, so, do you know anyhting?

Paraxes said:
Hey guys,
I really don't know where to ask this since this phone doesn't have a forum or anything - at least that I know of. If there is one I am glad if you can point me to it.
So, is there any way to root this device? I only bought it as a second phone for listening to music but I'd really like to root it, so, do you know anyhting?
Click to expand...
Click to collapse
I dont have this phone, but maybe try those one-click root software

Iv got one too and i need too root this phone..
IF anyone working on smth for the marshall please let us know
:angel:

Try King Root latest version. Not Kingoroot, but King Root.

KingoRoot, King Root not working. Anything else?

Thanks for reporting. Hoping for a root option before pulling the trigger...
Sent from my XT1095 using Tapatalk

not any news on this? i would love to root this phone and have a custom firmware. mine is full of bugs thats make it useless as a phone and camera, the only good thing about mine is the sound!

Me too want to root this phone, anyone know? Kingoroot & King Root cant root. After failed to root, it popup to ask them for help. It's around 150+ people already interested to root this phone.

This was essential for me. I have given up on purchasing this device. Based on monitoring the support page, it also seems the manufacturer is slow to develop updates. This device is starting to look like a manufacturer's experiment. I hope they do create an updated device and open to the US market...
Edit: Typo
Sent from my XT1095 using Tapatalk

Is there already an option for rooting because there has been a software update but KingRoot doesn't work

If I were you, I'd try to flash root binaries via the recovery menu. Keep in mind, that I don't have that phone. If that fails, you can wait for the custom recovery and you can try to install binaries from there. Keep me updated.
Sent from Lenovo a6000 1GB version.

eKeith said:
This was essential for me. I have given up on purchasing this device. Based on monitoring the support page, it also seems the manufacturer is slow to develop updates. This device is starting to look like a manufacturer's experiment. I hope they do create an updated device and open to the US market...
Edit: Typo
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Yes it is extremely slow development on this phone, since i did get it at the release there have been like 4-5 updates and none major update just some bugfixes that actually made the phone worse.
The support at MP is good fast answers but their not that good at helping you, they basically just copy&paste a standard Q&A.
My phone does stop vibrate occasionally, notification led is only functional sometimes, random reboots, Led flash is unusable on taking photos it does blend the lens so photos get almost black and some minor bugs, did contact support about this and they was not able to do anything due to that this is a gift from them. I had to pay for a shipping and repair myself.
I was hoping for root and custom rom, but as it seems that it will never happen i have an nice looking paperweight.

VaktBleppe said:
Yes it is extremely slow development on this phone, since i did get it at the release there have been like 4-5 updates and none major update just some bugfixes that actually made the phone worse.
I was hoping for root and custom rom, but as it seems that it will never happen i have an nice looking paperweight.
Click to expand...
Click to collapse
A custom rom might be a stretch due to the unique nature of the device, closed source code for the DAC, among other things. I have had trouble finding source code for this device, using code from similar devices tend to run into kernel panic issues.
I am working on a way to have flashable system images and a custom recovery on this device... and also a way to return the device completely to stock. The good news is that once you have binaries, you can use Fastboot to restore partitions. I have been able to re-flash experimental recovery builds with the original without any issue. No need to unlock or root.
And yes, root is possible. Kingoroot worked for me and I was able to successfully remove Kingo for SuperSU using the built in root swap tool in SuperSU.
I plan on starting a new thread for everything that I have for the Marshall London when I have everything working. Root, recovery, flashable ZIPs and stock images.
It may not be a device that is widely used but it definitely has a niche. I use it exclusively as an MP3 player because of its amazing sound. I also will be using it as a travel phone when I go to Europe. Shame the phone didn't find a larger market or even make it to North America because it's a very unique phone.

dooyet said:
Iv got one too and i need too root this phone..
Click to expand...
Click to collapse
serfaxa said:
KingoRoot, King Root not working. Anything else?
Click to expand...
Click to collapse
eKeith said:
Thanks for reporting. Hoping for a root option before pulling the trigger...
Click to expand...
Click to collapse
VaktBleppe said:
not any news on this? i would love to root this phone and have a custom firmware.
Click to expand...
Click to collapse
deddo86 said:
Me too want to root this phone, anyone know?
Click to expand...
Click to collapse
DanielPrime said:
Is there already an option for rooting because there has been a software update but KingRoot doesn't work
Click to expand...
Click to collapse
You now have root and a working recovery for the Marshall London.
https://forum.xda-developers.com/general/general/kb-1501-marshall-london-megathread-info-t3621059/

Question Reasons not to root

Hi,
I've done a quick search but can't find anything definitive so a quick response on here would be greatly appreciated.
Are there any reasons not to root on a P7P? Like tripping Knox on Samsung devices? Basically, irreversible side effects of unlocking the BL or installing Magisk? I'm rooted on a Doogee S98 Pro, a Xiaomi MiPad 4 and a Samsung Tab S6 at the moment and I don't think I could go back to having no root. It's pretty much my main reason for not buying an S22 Ultra.

Hi
this is one of the major benefits of the P7P in my perspective: you can unlock, root, unroot, relock without any negative side effects. You don't trip any fuse or have other effects that cannot be undone by a simple reflash.
Plus, maybe due to this, the P7P is one of the phones where the dev community is still quite active.....
Sent from my rooted P7P

s3axel said:
Hi
this is one of the major benefits of the P7P in my perspective: you can unlock, root, unroot, relock without any negative side effects. You don't trip any fuse or have other effects that cannot be undone by a simple reflash.
Plus, maybe due to this, the P7P is one of the phones where the dev community is still quite active.....
Sent from my rooted P7P
Click to expand...
Click to collapse
Perfect answer, thanks!

Pretty hard to brick a Pixel.
Just make sure you don't relock your bootloader unless you're fully stock. I've seen a bunch of people doing that throughout these forums here for some reason.

Yup, if you want to unroot once you're rooted, it's absolutely imperative you flash full stock before toggling OEM Unlock and issuing any ADB commands to re-lock the bootloader. Do that without flashing back to factory stock and you end up with a phone that can't boot because the bootloader is locked with a non-stock build, you can't unlock the bootloader because the OEM is toggled, and you can't flash a stock build because the bootloader is locked. Brick time.
Other than that it's a fairly safe phone to play around with.
I strongly recommend Pixel Flasher, it makes the whole process easier, but make sure you read up on it before doing anything.
📳🔥PixelFlasher for Google Pixel 7 Pro Support Thread.
This is the support thread of PixelFlasher (PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features). Note: This thread is meant for issues and problems faced in...
forum.xda-developers.com

GrapheneOS also supports relocking the bootloader, although I can't think of a reason why you'd want to.

The best reason not to root is that it's not needed in 2022. I can't imagine "needing" to do something with root that cannot be accomplished without root. YMMV

jaseman said:
The best reason not to root is that it's not needed in 2022. I can't imagine "needing" to do something with root that cannot be accomplished without root. YMMV
Click to expand...
Click to collapse
Call recording, full backup and restore, hosts based ad blockers.

Once rooted, it's annoying having to disable all Magisk mods, run updates, then re-root every month. I've also had updates corrupt the A/B Partitions. The warning screen for unlocked bootloader alone is a nuisance. If you're ok with that, go right ahead.

Guyinlaca said:
disable all Magisk mods, run updates, then re-root every month
Click to expand...
Click to collapse
You're adding steps and no indication of why. Just install the update with modified boot.img and call it good.

96carboard said:
Call recording, full backup and restore, hosts based ad blockers.
Click to expand...
Click to collapse
I went 3 days before rooting my P7P since I was unfamiliar with the process. I was able to root OnePlus blindfolded, but the forums made Pixel seem difficult. It was the most miserable 3 days when everything I wanted to use/customize depended on root.

without root I could not even get 5G working. Furthermore the AOSP Mods on the stock ROM... Systemless Hosts AdBlocking, Re-Vanced, .......
I unlocked and rooted the phone before even booted it the first time

Guyinlaca said:
Once rooted, it's annoying having to disable all Magisk mods, run updates, then re-root every month.
Click to expand...
Click to collapse
Updated to November, didn't disable any Magisk mods, no issues.
It's only some mods which cause issues. Not got them installed, you can perform the update without touching Magisk.

Guyinlaca said:
Once rooted, it's annoying having to disable all Magisk mods, run updates, then re-root every month. I've also had updates corrupt the A/B Partitions. The warning screen for unlocked bootloader alone is a nuisance. If you're ok with that, go right ahead.
Click to expand...
Click to collapse
You don't have to disable all your Magisk Mods

K1nsey6 said:
I went 3 days before rooting my P7P since I was unfamiliar with the process. I was able to root OnePlus blindfolded, but the forums made Pixel seem difficult. It was the most miserable 3 days when everything I wanted to use/customize depended on root.
Click to expand...
Click to collapse
And wasn't it funny when you realized that root on Pixel is actually easier than everything else?

Hello , i need help for rooting my p7p. If have a video step by step its be very helpfull. Sorry for my bad english " Salut " from Romania thanks

ZoM4cs said:
Hello , i need help for rooting my p7p. If have a video step by step its be very helpfull. Sorry for my bad english " Salut " from Romania thanks
Click to expand...
Click to collapse
Here is a guide you can follow.

96carboard said:
Call recording, full backup and restore, hosts based ad blockers.
Click to expand...
Click to collapse
Umm that's illegal bro.

chivamex10 said:
Umm that's illegal bro.
Click to expand...
Click to collapse
Maybe where you are, but not here and not in most places. So keep your legal advice to yourself, BRO.

chivamex10 said:
Umm that's illegal bro.
Click to expand...
Click to collapse
Actually in most jurisdictions it's what's called a one party consent requirement wherein one of the parties involved must be aware and consent. In this case the person doing the recording qualifies as the consenting party. In other places two party or more consent is required but not everywhere