Related
Hi there XDA community,
I would like to know if there is an up-to-day tutorial that has working file links? I would like to upgrade, root, and unlock my Xoom. I just bought a Motorola Xoom from 1saleaday.com the Model is an MZ601 and says "approved by IDA for use in Singapore" it is currently just as is and is not unlocked or rooted. I would like to get it upgraded, unlocked, and rooted so I can use it for what I got it for. It has WiFi and Data service that supports WCDMA 850/900/1900/2100, GSM 850/900/1800/1900, ATO_ITEM: AP1520AD3X3. It is currently running on Android Honeycomb 3.0.1, build number H.6.1-38-9. If you any ideas, files, links, tutorials (up-to-day), or can help, that would be great!
Thanks InfiniteImmortal.
P.S.
Here are the configurations;
Model Number: MZ601
Android version: 3.0.1
Firmware: GAS_ASIA_USAEVRSTURTIRD_P016
Baseband version: N_014.83.28P
Baseband configuration: UCAEVEUB1B8EU034.0R
Kernel: 2.6.36.3 [email protected] #1
Build Number: H.6.1-38-9
More specs will be provided if they are needs, thanks again II!
yeah, there are tons of tutorials, relatively up to date. Relatively, because the new method to root xyboards might work for classic xooms too. This method would not require you to unlock your xoom for rooting and thus allow titanium backup to backup all your data before unlocking and thus wiping your xoom.
Just from the first page in the Q/A- and Xoom-general forums:
[HOW TO][UPDATED GUIDE] Unlocking & Rooting your XOOM!
Xoom root and bootloader unlock (a post by me)
and maybe this
[HOW TO] Motorola Xoom 2/Xyboard Root Method by Dan Rosenberg
I order one from the same seller on E-bay today
and for sure need the same help
but I need some Q
is the seller ship the item quikly for you ?
is this come in sealed box ?
sorry but I'm afraid of them
Response to purity0flove
purity0flove said:
I order one from the same seller on E-bay today
and for sure need the same help
but I need some Q
is the seller ship the item quikly for you ?
is this come in sealed box ?
sorry but I'm afraid of them
Click to expand...
Click to collapse
It only took a week for me to get mine via UPS. The box came to my house sealed, it had never been opened. But I bought a new one, not a refurbished one. Hope this could help.
II
Response to llama-power
llama-power said:
yeah, there are tons of tutorials, relatively up to date. Relatively, because the new method to root xyboards might work for classic xooms too. This method would not require you to unlock your xoom for rooting and thus allow titanium backup to backup all your data before unlocking and thus wiping your xoom.
Just from the first page in the Q/A- and Xoom-general forums:
[HOW TO][UPDATED GUIDE] Unlocking & Rooting your XOOM!
Xoom root and bootloader unlock (a post by me)
and maybe this
[HOW TO] Motorola Xoom 2/Xyboard Root Method by Dan Rosenberg
Click to expand...
Click to collapse
Okay I will go and read these threads, but are you for sure they work on the EU models? I have read on many different sites and threads that say the normal way of rooting, unlocking, and upgrading for US models have bricked the EU ones to were they did not work anymore. This is one reason why I'm looking for an up-to-date threads that say they work with the EU models. If you could clarify more that would be great.
Thanks, II
InfiniteImmortal said:
It only took a week for me to get mine via UPS. The box came to my house sealed, it had never been opened. But I bought a new one, not a refurbished one. Hope this could help.
II
Click to expand...
Click to collapse
yes I ordered one from 1saleaday.com on E-bay .. this seller buy also on E-bay ... new not Refurbished ! and ship with UPS but didn't now still didn't ship and wait for him !
InfiniteImmortal said:
Okay I will go and read these threads, but are you for sure they work on the EU models?
Click to expand...
Click to collapse
Yes, the one post I have marked with "(a post by me)" is exactly how I rooted my xoom and that is a german MZ601. And it works, no brick
InfiniteImmortal said:
I have read on many different sites and threads that say the normal way of rooting, unlocking, and upgrading for US models have bricked the EU ones to were they did not work anymore.
Click to expand...
Click to collapse
That is weird. I have never read a thread about a brick that occured using the method I (and others) described. Could you maybe post a link to such a thread?
To Clarify this: the Unlock should impose absolutely no risk at all as it is a feature implemented by motorola. The recovery, even if it didn't work, wouldn't lead to a brick. And the universal xoom root should not do any magic either, it should only add two files to the filesystem (su and Superuser.apk) and remove those files that would make your new shiny recovery go byebye once booted
Ty my knowledge, only the "flashing a custom rom" part is a source of bricking. And that can easily be avoided by flashing a MZ601-rom instead of something else
That said, nobody can guarantee you that this is completely safe. There is a thread right next door with a poor guy whose xoom bricked itself overnight. That was a wifi-xoom, and so far no one knows why that happened. We're still working on a solution, though
InfiniteImmortal said:
Okay I will go and read these threads, but are you for sure they work on the EU models? I have read on many different sites and threads that say the normal way of rooting, unlocking, and upgrading for US models have bricked the EU ones to were they did not work anymore. This is one reason why I'm looking for an up-to-date threads that say they work with the EU models. If you could clarify more that would be great.
Thanks, II
Click to expand...
Click to collapse
tell me what way you chioce and made and the result .. cuz I will root my item when I recive
---------- Post added at 11:05 PM ---------- Previous post was at 10:54 PM ----------
If I root my xoom can I go back again on Original mood cuz I heard that if I rooted Xoom I will not be able to up-date it via OTA again !
purity0flove said:
If I root my xoom can I go back again on Original mood cuz I heard that if I rooted Xoom I will not be able to up-date it via OTA again !
Click to expand...
Click to collapse
yes, you will be able to go back to the original rom and lock your bootloader again. If you do that, you will be able to get ota updates (if you really want to do so, usually custom roms are ahead of the ota-updates)
You should make a backup of your xoom right after starting the new recovery, even before rooting. That will give you a set of files that, if you restore them, will reset your xoom back to stock, thus you'll only have to re-lock your bootloader to get ota-updates
Response to llama-power
llama-power said:
You should make a backup of your xoom right after starting the new recovery, even before rooting. That will give you a set of files that, if you restore them, will reset your xoom back to stock, thus you'll only have to re-lock your bootloader to get ota-updates
Click to expand...
Click to collapse
I'm now intrigued, I to would like to know how to do this. I'm all for safety measures when it comes to doing things that could damage my stuff.
II
Response to llama-power
llama-power said:
That is weird. I have never read a thread about a brick that occured using the method I (and others) described. Could you maybe post a link to such a thread?
Click to expand...
Click to collapse
Here are two of the links that I was telling you about
Motorola Xoom Root the Easy way
&
Xoom One-Click Root/Unroot
In the first one I found out about it in the comments sections. I read everything on the pages.
II
Custom ROM Files
Hey llama-power,
You say in your thread post that "If you already downloaded your new rom, put that onto the sdcard as well, it should be a flashable .zip-file".
Do you by chance have the links to these files? I know I.C.S. is the latest one, but I'm happy with an old one if it is stable. Or if you have a custom ROM for the Xoom that would be great. I have a Samsung Captivate generation 1 that I use Firefly or Cognition on, along with the original stock ROM as backup just in case. Any links or files would be very cool!
II
Suggested Thread
Just to let you know your suggested thread "and maybe this [HOW TO] Motorola Xoom 2/Xyboard Root Method by Dan Rosenberg" does not work on my Xoom, but thanks for your suggestion. I'll try the other ones you put up, so far I have read every page on every linked thread I've come across. Lots and lots of helpful info on those as well as your pages. But if you can respond to my three earlier posts that would be helpful too. Starting to get information overload, haha.
II
Response to llama-power
Just to let you know your instructions worked like a charm! Went step-by-step and everything worked with no problems at all.
A few more question, yes I know MORE questions! haha. Where is the backup I make stored at? I would like to put it in my backups folder for the Xoom under its drive in my computer. Currently the 3G data service is still not working on it, but is recognizing AT&T network. It says "Mobile Network State: Disconnected" just like before and suggestions? Other then that I also still don't have access to the micro SD card in Android, but can access it in the Recovery.
I now think its time for a new platform, NO more Honeycomb 3.0.1! If you have any suggestions your more than welcome to say or suggest just like for the other posts!
llama-power You ROCK!
Time for me to get some sleep! Been reading and doing Xoom stuff for hours now. I'll be on later to night to read your posts!
Sincerely, InfiniteImmortal
InfiniteImmortal said:
Here are two of the links that I was telling you about
Motorola Xoom Root the Easy way
&
Xoom One-Click Root/Unroot
Click to expand...
Click to collapse
Wow, wasn't aware of that. But these methods are really old. The method I mentioned is the universial root-method by solarnz which is supposed to work on every 'classic' xoom (despite the family edition with its locked bootloader)
InfiniteImmortal said:
You say in your thread post that "If you already downloaded your new rom, put that onto the sdcard as well, it should be a flashable .zip-file".
Do you by chance have the links to these files?
Click to expand...
Click to collapse
I am using the team eos nightlies. Works really nicely except deep-sleep isn't working for me while wifi is enabled. Don't know if that is a rom-issue though, might be some app I use. Anyways, it's not really a problem to me, battery life is still more than sufficient.
You can get the team EOS nightlies for your xoom (MZ601 / umts_everest / EU-3G) from this thread. Download the latest nightly build and the latest G-Apps package (thats the Google Mail, Market, etc. apps) from the link in the same thread. Put those onto your sdcard and flash them from recovery. Wipe /data, /cache and dalvik-cache first, then install the rom, then the g-apps package and finally reboot. Do not reboot between the steps. When upgrading from one nightly to another omit wiping /data.
InfiniteImmortal said:
Just to let you know your suggested thread "and maybe this [HOW TO] Motorola Xoom 2/Xyboard Root Method by Dan Rosenberg" does not work on my Xoom,
Click to expand...
Click to collapse
How did you determine that it didn't work? The only difference you should see is the new app "Superuser.apk". If it really didn't work: sad
InfiniteImmortal said:
Just to let you know your instructions worked like a charm! Went step-by-step and everything worked with no problems at all.
Click to expand...
Click to collapse
thanks, glad to read that
InfiniteImmortal said:
Where is the backup I make stored at?
Click to expand...
Click to collapse
on your sdcard: $SDCARD$/clockworkmod/backup/$DATE_AND_TIME_OF_YOUR_BACKUP$. just copy that entire folder, it contains many .img-files (one for each partition) plus another file for checksums. You will need all those files for a restore. You may, however, rename the directory.
InfiniteImmortal said:
I would like to put it in my backups folder for the Xoom under its drive in my computer.
Click to expand...
Click to collapse
great idea
InfiniteImmortal said:
Currently the 3G data service is still not working on it, but is recognizing AT&T network. It says "Mobile Network State: Disconnected" just like before and suggestions?
Click to expand...
Click to collapse
that is weird. What do you mean with "just like before"? As you haven't flashed another rom yet, nothing regarding connectivity should have changed so far. A few pointers to eliminate some errors: is Airplane mode off? Is mobile data enabled? Are you connected to a wifi-network? Did you set up your AT&T-apn correctly?
InfiniteImmortal said:
Other then that I also still don't have access to the micro SD card in Android, but can access it in the Recovery.
Click to expand...
Click to collapse
yeah, once you flash your new rom, you should be able to access that sd-card. As stated before, you are just rooted, that gives you the power to change things but if you didn't (like installing something that is supposed to give you access to your sdcard), nothing should have changed
InfiniteImmortal said:
I now think its time for a new platform, NO more Honeycomb 3.0.1! If you have any suggestions your more than welcome to say or suggest just like for the other posts!
Click to expand...
Click to collapse
see above, use team eos nightlies
Response to llama-power
llama-power said:
I am using the team eos nightlies.
You can get the team EOS nightlies for your xoom (MZ601 / umts_everest / EU-3G) from this thread. Download the latest nightly build and the latest G-Apps package (thats the Google Mail, Market, etc. apps) from the link in the same thread. Put those onto your sdcard and flash them from recovery. Wipe /data, /cache and dalvik-cache first, then install the rom, then the g-apps package and finally reboot. Do not reboot between the steps. When upgrading from one nightly to another omit wiping /data.
Click to expand...
Click to collapse
Okay I'll look into this one since I know you said it works for you.
llama-power said:
How did you determine that it didn't work? The only difference you should see is the new app "Superuser.apk". If it really didn't work: sad
Click to expand...
Click to collapse
I know you have already seen the other thread that I posted to, and about how I know it didn't work. You commented on the thread with your own post, thanks for backing me up.
llama-power said:
on your sdcard: $SDCARD$/clockworkmod/backup/$DATE_AND_TIME_OF_YOUR_BACKUP$. just copy that entire folder, it contains many .img-files (one for each partition) plus another file for checksums. You will need all those files for a restore. You may, however, rename the directory.
great idea
Click to expand...
Click to collapse
Thanks, I did the same thing on my Samsung Captivate and since my mother has the same phone I made it so it could be used on ether one, less file management for me. Haha
llama-power said:
What do you mean with "just like before"? As you haven't flashed another rom yet, nothing regarding connectivity should have changed so far.
Click to expand...
Click to collapse
You are correct on this, nothing has changed from before except becoming rooted and unlocked. I was hoping that just maybe a full system wipe might fix the connection issue I was having. I was being over optimistic!
llama-power said:
A few pointers to eliminate some errors: is Airplane mode off? Is mobile data enabled? Are you connected to a wifi-network? Did you set up your AT&T-apn correctly?
Click to expand...
Click to collapse
Yes airplane mode is off and Mobile data service is enabled. I have tried it with WiFi both on and off, before and after rooting and unlocking but still nothing. As for the AT&T-APN being setup correctly, I used the exact same settings that are being used in my phone with nothing different; but still to no prevail. Do you know if there is a settings list or configuration out somewhere for the APN?
llama-power said:
yeah, once you flash your new rom, you should be able to access that sd-card... if you didn't (like installing something that is supposed to give you access to your sdcard), nothing should have changed
Click to expand...
Click to collapse
Yeah I kinda guessed at that one, I remembered reading about the Honeycomb 3.1.0 update giving users the ability to use the micro SD cards today. That was before I read your post. lol You might know about this, Do you know where the repository of updates are located for the Motorola Xoom 'classic' model? I was thinking it would be a good idea to have all of them, if I ever wanted to use my warranty it would be good to have the latest stock ROM on it! It's better to be safe then up an icy creek in the Alps with a swim suit on!
II
InfiniteImmortal said:
Okay I'll look into this one since I know you said it works for you.
Do you know if there is a settings list or configuration out somewhere for the APN?
Click to expand...
Click to collapse
Just to let you know I'm using the ROM you recommended and I love it so far. As for the data service on the AT&T network it now works, after switching to the new ROM and it loaded the proper APN settings which were different from my phone. And of course with a new ROM the SD card now works as well. So my last and final question would be as stated before where can I find the oldest most up to date stock ROM?
Best regards, InternetImmortal
Sent from my MZ601 using XDA App on EOS
InfiniteImmortal said:
Just to let you know I'm using the ROM you recommended and I love it so far. As for the data service on the AT&T network it now works, after switching to the new ROM and it loaded the proper APN settings which were different from my phone. And of course with a new ROM the SD card now works as well.
Click to expand...
Click to collapse
glad you like it
InfiniteImmortal said:
So my last and final question would be as stated before where can I find the oldest most up to date stock ROM?
Click to expand...
Click to collapse
well, there are a couple of sources for a stock rom. For one, your sd-card should contain one (I restored my backup yesterday and yes, it even reset the recovery to stock)...
Also, motorola offers some filesystem images at http://developer.motorola.com/products/software/, but you'll need to register with them to get to the download (should be free, though)
Finally, it might be desirable to have some .sbf-file for your xoom. Those can be flashed using a software called rsd lite, even when you aren't able to enter your recovery system. Doesn't always work, so it's not more than a Hail Mary move... However, Motorola does a lot to keep these files from floating around the web, so I won't be able to provide you with a link.
As always thanks for the keen insight. Just came across a few threads that perked my interest. Have you ever tried to get working SMS text messaging and voice calling on the Xoom? Since I'm using the SIM from my phone to do the data I was hoping there might be a way. I haven't done a lot of reading on this yet but you seem to know everything.
Sent from my MZ601 using XDA App on EOS
InfiniteImmortal said:
Have you ever tried to get working SMS text messaging and voice calling on the Xoom?
Click to expand...
Click to collapse
nope. The sim inside my xoom is on the same contract as the sim in my phone and I had to pick one that would receive texts. Naturally, since I always carry my phone, that's where the texts go, so the xoom wouldn't ever receive a text ever anyways. Voice calling is currently not possible on the xoom. So the only upside of that would be that I could send texts using the xoom, but that isn't so much better than texting on my Desire HD. Plus, that would tear apart the messaging threads between my phone and the xoom.
However, there's a thread in the xoom development section where flashable zip-files are published for every eos nightly, you should be able to just flash that over your rom and thus enable texting.
Actually, I might try that some time, but right now I should really learn for that exam on friday:-/
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
Hi, I read that anyone with a developer's account can access the developers' preview build of Android L, that was supposed to be available today, I have a developer's account (to upload apps to the market) but I don't see any build of android L, is this the required account? or is there any other type of account required? thanks!
saman0suke1 said:
Hi, I read that anyone with a developer's account can access the developers' preview build of Android L, that was supposed to be available today, I have a developer's account (to upload apps to the market) but I don't see any build of android L, is this the required account? or is there any other type of account required? thanks!
Click to expand...
Click to collapse
it will be here when its released, as of yet it is not released
http://developer.android.com/index.html
keep refreshing the page like the rest of us
saman0suke1 said:
Hi, I read that anyone with a developer's account can access the developers' preview build of Android L, that was supposed to be available today, I have a developer's account (to upload apps to the market) but I don't see any build of android L, is this the required account? or is there any other type of account required? thanks!
Click to expand...
Click to collapse
I guess it'll be available in a few hours.
I guess they just haven't released it, yet.
Don't forget their different timezone.
Thank you all, maybe I'm getting too desperate I just wanted to confirm that my account is the right one, I'll be refreshing until it appears, thanks again!
EDIT: I believe being rooted would not be a problem at the moment of the installation, right? I know that I'll lose root after that, but as long as the actual installation does not give me problems, it's fine.
saman0suke1 said:
Thank you all, maybe I'm getting too desperate I just wanted to confirm that my account is the right one, I'll be refreshing until it appears, thanks again!
EDIT: I believe being rooted would not be a problem at the moment of the installation, right? I know that I'll lose root after that, but as long as the actual installation does not give me problems, it's fine.
Click to expand...
Click to collapse
Considering that the images will have to be flashed through fastboot, you'll probably lose root and everything else on data/system partitions (unless they don't wipe it, but I think it does).
saman0suke1 said:
Thank you all, maybe I'm getting too desperate I just wanted to confirm that my account is the right one, I'll be refreshing until it appears, thanks again!
EDIT: I believe being rooted would not be a problem at the moment of the installation, right? I know that I'll lose root after that, but as long as the actual installation does not give me problems, it's fine.
Click to expand...
Click to collapse
maybe it will be problem to root new androi L cause I've read somwhere that there is a lot of security updates and also samsung knox in new android so we will see if it will be able to root
saman0suke1 said:
Thank you all, maybe I'm getting too desperate I just wanted to confirm that my account is the right one, I'll be refreshing until it appears, thanks again!
EDIT: I believe being rooted would not be a problem at the moment of the installation, right? I know that I'll lose root after that, but as long as the actual installation does not give me problems, it's fine.
Click to expand...
Click to collapse
if it's a factory image it'll wipe the whole phone and root probably wont work until its updated to support L
MidnightDevil said:
Considering that the images will have to be flashed through fastboot, you'll probably lose root and everything else on data/system partitions (unless they don't wipe it, but I think it does).
Click to expand...
Click to collapse
That's fine, I believe that flash through fastboot does not include a total wipe including camera folder and all that right? never done it that way, better be prepared. Thanks!
saman0suke1 said:
That's fine, I believe that flash through fastboot does not include a total wipe including camera folder and all that right? never done it that way, better be prepared. Thanks!
Click to expand...
Click to collapse
As long as you don't flash the userdata.img, all /sdcard data will be fine. You don't have to flash userdata.img to bump android versions! System, boot would do just fine (and bootloader if they bump it as well)
Or you could just wait till a flashable zip is posted. Someone will have one up within hours of release.
Roxas598 said:
if it's a factory image it'll wipe the whole phone and root probably wont work until its updated to support L
Click to expand...
Click to collapse
Whole phone means photos, and any kind of files? I prefer to ask so I make a backup first :S , never done it this way, thanks!
saman0suke1 said:
Whole phone means photos, and any kind of files? I prefer to ask so I make a backup first :S , never done it this way, thanks!
Click to expand...
Click to collapse
Read my previous post.
saman0suke1 said:
Whole phone means photos, and any kind of files? I prefer to ask so I make a backup first :S , never done it this way, thanks!
Click to expand...
Click to collapse
Yep every single thing on the phone will be gone so backup everything you need
saman0suke1 said:
That's fine, I believe that flash through fastboot does not include a total wipe including camera folder and all that right? never done it that way, better be prepared. Thanks!
Click to expand...
Click to collapse
You'll lost everything... Photos,data file...
vin4yak said:
As long as you don't flash the userdata.img, all /sdcard data will be fine. You don't have to flash userdata.img to bump android versions! System, boot would do just fine (and bootloader if they bump it as well)
Click to expand...
Click to collapse
Unless they changed the folder structure like they did a few releases ago - if they did, best to do a clean install.
I'm backing up right now just in case.
Don't wanna mess with the installation script by flashing some things and not others (although there would be virtually no risk by flashing system and boot partition), but better safe than sorry, after all, we can just shove everything back when finished
Consider ir a backup routine, and you'll have an updated bk
jj14 said:
Unless they changed the folder structure like they did a few releases ago - if they did, best to do a clean install.
Click to expand...
Click to collapse
That's an entirely different scenario. Each and everyone of us would need to wipe clean if that happens but usually a system and boot flash would do just fine
The N5 has been my FIRST of many, many, many Android phones and even Windows Pocket PC phones that I haven't felt the need to unlock/root etc. Everything has just worked great on it and I have always been able to do everything I wanted to do from this phone. I have been so satisfied with the phone that it has kept me away from XDA for a while. Don't know if that is a good thing or bad, lol. I used to be on this site for hours every single day and now I feel like I am light years behind in rooting. HA!
L has me interested though and I am contemplating unlocking my bootloader for it which just becomes a PITA with losing your data and adding things back and all that great stuff that takes so much of your time. Then if things suck you have to flash back to something else and the never ending process continues. The N5 has gotten me so much time back in my life but I feel like it might demand some of my time back to it. Oh I hate this stuff!!!!
I think I'll make a backup, just in case, as someone said previously, I would prefer to make a clean installation if it's needed and use the image provided by Google.
Thanks!
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?
Hi all, I hope this isn't a thread that has already been posted... I found it interesting that there is no TWRP or any custom recovery for Pixel 7/7 Pro. I understand it's not needed to flash different rom's such as Paranoid Android or Spark OS but I figure it would be helpful no? My prior device was a iPhone 12, haven't run a rooted android since my Galaxy s4 way back in the day. Is this something somebody is actively pursuing or no as it's not needed? Curious on what the situation is with this, loving my p7 pro. Cheers!
TWRP has been nearly an entire Android version behind for awhile now so I haven't been able to use it on my last couple phones. I believe it is still being worked on but since it's been so far behind due to the changes to Android and it's migration to ramdisk installation it's mostly fallen out of use sadly. I do miss it sometimes as well.
jake.99x3 said:
I figure it would be helpful no?
Click to expand...
Click to collapse
No, its useless. Pixel devices have unlocked bootloaders and support fastboot, therefore recovery is not needed.
Well, a lot of old and new Samsung phones and tablets are running TWRP and root. Yes, with Android 13. Is it strictly because there is that A and B split thing going on ? Personally I have not written to my B partition in many months if ever.
Can there be a lesson learned from that ?
96carboard said:
No, its useless. Pixel devices have unlocked bootloaders and support fastboot, therefore recovery is not needed.
Click to expand...
Click to collapse
I don't know about that. It may not be needed but the advantages are profoundly easier than having to learn terminal commands
Also you can't do flashes and restores without a PC whereas when we had active working custom recovery it could be done anywhere at anytime.
JakeDHS07 said:
Also you can't do flashes and restores without a PC whereas when we had active working custom recovery it could be done anywhere at anytime.
Click to expand...
Click to collapse
Exactly! I used to do a complete backup, periodically. One day I screwed something up playing around at work, went to Recover and flashed my backup. Fixed it in a few minutes
Yeah it would be nice to have for sure
Same here, a nice custom recovery would be sweet. If I had any clue how to build one I would be all over it.
JakeDHS07 said:
Also you can't do flashes and restores without a PC whereas when we had active working custom recovery it could be done anywhere at anytime.
Click to expand...
Click to collapse
Is it even possible to do a nandroid backup anymore with the changes to Android filesystems and permissions? I mean you can't even flash a full firmware package in fastboot anymore, part of it has to be done from fastbootd.
old_fart said:
Well, a lot of old and new Samsung phones and tablets are running TWRP and root. Yes, with Android 13. Is it strictly because there is that A and B split thing going on ? Personally I have not written to my B partition in many months if ever.
Can there be a lesson learned from that ?
Click to expand...
Click to collapse
The A/B system is not for power users who manually flash things. It's so that updates for the 99% who use their phones normally can be done in the background. It also adds a failsafe in case one slot gets corrupted since it will automatically boot the other slot after so many failures. Previously such a failure would be an automatic brick.
Also, I think most of us power users are using the A/B system normally at this point too. You have to go out of your way to not flash an update to the other slot, all the defaults do.
HipKat said:
I don't know about that. It may not be needed but the advantages are profoundly easier than having to learn terminal commands
Click to expand...
Click to collapse
That's insane. And dangerous. When it messes up, good luck fixing it.
96carboard said:
That's insane. And dangerous. When it messes up, good luck fixing it.
Click to expand...
Click to collapse
Ummmm, what??
TWRP is a big miss for me. Nandroid Backups and phone based file explorer without having to boot to Android were just two of the numerous features I used regularly. To say it would be useless is ridiculous.
I for one would be very happy to have it make an appearance on the Pixel 7 Pro. I'm not holding my breath though, the Pixel 6 and 6 Pro still don't have it I believe.
I've used TWRP in the past. I've never understood the attraction.
Even with A/B a recovery is useful, but why would I want to play with volume buttons to express my wishes?
Just take a stock recovery, patch adbd to be rooted, patch the kernel to be permissive, done.
As Patrick Henry said, "Give me ADB or give me death!"
Renate said:
I've used TWRP in the past. I've never understood the attraction.
Even with A/B a recovery is useful, but why would I want to play with volume buttons to express my wishes?
Just take a stock recovery, patch adbd to be rooted, patch the kernel to be permissive, done.
As Patrick Henry said, "Give me ADB or give me death!"
Click to expand...
Click to collapse
You sure you've used it? TWRP is fully touch screen.
Beefheart said:
You sure you've used it? TWRP is fully touch screen.
Click to expand...
Click to collapse
You're right. I'm conflating stock recovery with TWRP.
I do remember big tiles and tapping on them.
Still, I prefer to keep my fingers on the (desktop) keyboard.
Renate said:
You're right. I'm conflating stock recovery with TWRP.
I do remember big tiles and tapping on them.
Still, I prefer to keep my fingers on the (desktop) keyboard.
Click to expand...
Click to collapse
I'm as much of a command line fan as the next nerd, but TWRP offers multiple features not available via ADB.
Renate said:
I've used TWRP in the past. I've never understood the attraction.
Even with A/B a recovery is useful, but why would I want to play with volume buttons to express my wishes?
Just take a stock recovery, patch adbd to be rooted, patch the kernel to be permissive, done.
As Patrick Henry said, "Give me ADB or give me death!"
Click to expand...
Click to collapse
Because when you don't have a computer to connect to do a restore, for example, it's imperative to have a Recovery that does backups so you can
HipKat said:
Because when you don't have a computer to connect to do a restore, for example, it's imperative to have a Recovery that does backups so you can
Click to expand...
Click to collapse
Ok. You're doing backups to a USB flash drive? Fair enough.
But, since this thread is questioning whether any custom recovery is in development wouldn't it be helpful if someone knocked off at least a custom recovery to the extent that I mentioned?
Renate said:
Ok. You're doing backups to a USB flash drive? Fair enough.
But, since this thread is questioning whether any custom recovery is in development wouldn't it be helpful if someone knocked off at least a custom recovery to the extent that I mentioned?
Click to expand...
Click to collapse
No, doing backups to internal storage, actually. How am I going to access a USB flash drive with a telephone if I’m sitting at a friend’s house and something gets corrupted, phone won’t boot, and I have to reboot to recovery where I can access an internal back up? Which cannot be done with stock recovery.