Ok, so i have this problem with my sd card on l7.Today i bought new 8gb sd card , and when i started using it i noticed that Android folder didnt appeared automatically and when you downloading files and instaling , they install in phone memory not in sd card.Another thing is that i want to install games (obb file) and i cant do that because there are no android folder in sd , and because of that i cant make obb folder in it and install games.In my previous sd card i didnt even noticed anything like that because android folder was there and all files were automatically installed there. My old sd was 2gb and it was old from my previous phone nokia c3 and when i putted back old sd there i noticed that android folder was gone, so it couldnt be problem with sd card .I tried factory reset but it changed nothing.My phone is not rooted and i wont root it because i dont want to brake my warranty.I really need your help on this one.Sorry for my bad english.
Rooting doesn't brake your warranty, unlocking the bootloader does... and about the sd card problem, I'm also facing that ****, we unfortunately must wait for a dev to support us about this issue....
Berat1337 said:
Rooting doesn't brake your warranty, unlocking the bootloader does... and about the sd card problem, I'm also facing that ****, we unfortunately must wait for a dev to support us about this issue....
Click to expand...
Click to collapse
are you sure? i really think rooting voids warranty
EchoLT said:
are you sure? i really think rooting voids warranty
Click to expand...
Click to collapse
Unlocking the bootloader does void your warranty, not the rooting, because if you root, you can un-root the phone but you cannot "lock" the bootloader after you unlock it... you can lock it but it will say "relocked" not locked.
Related
Hi,
I'm hoping someone can give me some advice. I'm not very technically minded, and this is my first Android handset.
Like an idiot, I upgraded to 1.72 shortly after it was released. I got the usual text notification problems. As of this morning, my third SD card has failed since the update.
First of all, I know people have had issues with the card unmounting, but has this actually resulted in damage to people's cards? All three of mine have became unreadable shortly after I started getting the 'SD card unexpectedly removed' message.
The issues are now started to really hack me off, and so I've been looking in to downgrading to 1.32. I've found several guides on how to do this, and with regards to rooting. My question is, do I have to root it to downgrade?
I've found one guide where it goes through downgrading first (creating a temproot?), and then says that performing the steps to root the device afterwards are voluntary. Is this the case?
Also, if I end up having to root, etc will I lose access to any apps, such as Market, etc
Thanks for your help.
Andy
s32bauer said:
Hi,
I'm hoping someone can give me some advice. I'm not very technically minded, and this is my first Android handset.
Like an idiot, I upgraded to 1.72 shortly after it was released. I got the usual text notification problems. As of this morning, my third SD card has failed since the update.
First of all, I know people have had issues with the card unmounting, but has this actually resulted in damage to people's cards? All three of mine have became unreadable shortly after I started getting the 'SD card unexpectedly removed' message.
The issues are now started to really hack me off, and so I've been looking in to downgrading to 1.32. I've found several guides on how to do this, and with regards to rooting. My question is, do I have to root it to downgrade?
I've found one guide where it goes through downgrading first (creating a temproot?), and then says that performing the steps to root the device afterwards are voluntary. Is this the case?
Also, if I end up having to root, etc will I lose access to any apps, such as Market, etc
Thanks for your help.
Andy
Click to expand...
Click to collapse
i beleve HTC has had to replcace many SD Cards, because they have been damaged due to the update. i don't think you need to root to downgrade, infact, on the 1.72 software version, you have to downgrade to root, so if you follow the downgrade and root sticky in the android developent section, and just stop after the downgrade procedure, before you root
Hi Andy,
You cannot root 1.72/75. You need to create a Goldcard and downgrade before you can root.
The SD Card problem HTC know about, contact them and explain what has happened. You should get a replacement, maybe even for all three.
Rooting a 1.32 ROM is easy and undo-able, It does not affect app such as Market, GMail, etc... All it allows is read/write access to system files, nothing more.
S-OFF (Security OFF) on the other hand will break any attempt to upgrade via an OTA.
EDIT: Beat me too it!
Ah that's great. So I should be able to simply downgrade back to 1.32 without having to root, and everything will be just as it was when I bought the phone?
Hello there..!!
Can any1 plz help me recover my deleted files from the internal memory of Moto G. I accidently deleted a folder named emulator from the device and in result i lost all my data.Can any one plz tell me how to recover those files WITHOUT ROOTING my phone. I have tried many software but say to root my device first, but i dont want to do this cz it will void my handset warranty..?? Its urgent PLZ HELP...!!!!!
I think you have to root in order to do that.
Seems like you have deleted /storage/emulated, right?
I don't know any method that can save your data without rooting, next time be more careful about deleting things you don't know about.
Sorry for your loss bro. I hope someone comes up with an idea to save your data, but I don't think it's gonna happen without rooting.
edit: You can try this http://forum.xda-developers.com/showthread.php?t=2774016 to root without unlocking the bootloader (no warranty void) if you have 4.4.2
Ok I'm sure some of you are thinking "what's the difference?" and "what a noob" or something like that. But given where i come from, that being the original Motorola Droid 1 rooting used to be extremely simple and easy since there was only ONE model for the motorola DROID 1 here in the states. I have a Moto x PURE edition and was curious if there is in fact a difference between that and the STYLE/PLAY models that would make it impossible to unlock my bootloader and root it? I know that for some time it was very difficult because you couldn't officially unlock your bootloader with out being a developer for it, yet developer options are fully accessible on the moto x pure. I'm beyond confused and need some clarification on this.
I'm currently on 6.0
security patch feb 1, 2016 (not the latest one even tho it keeps asking me to update it)
system version 24.201.3.clark_retus.retus.en.US retus
and build number MPHS24.49-18-3
i honestly have no clue if i'm able to unlock the boot loader with out bricking it automatically
and i honestly have no clue if i'm able to root it with out bricking it automatically because in the past i've tried rooting other devices similar to this and failed miserably.
please don't tell me to just go on the forums and look up root methods and unlocking the boot loader because simply put they have a combined forum of both the international model and the US model so sifting through all of it just to get things clear is beyond frustrating since i have no clue what i'm looking at anymore :/
another thing to note is that i was previously on the LG G4 which makes my confusion understandable from my perspective since in some cases it's possible to root the G4 and in some other cases it's NOT possible to root the G4 and each model has it's own number and build and blah blah blah making it impossible to know if mine is rootable or not.
The bootloader can be unlocked and this phone can be rooted, no problem.
There is the XT1575 (the Pure, the US version) and the XT1572 (the Style, the international version). They have different modems, but other than that most things seem pretty interchangeable between them.
This isn't like some US phones where the carriers got their ugly mitts on them, and you can do whatever you want with the T-Mobile version but the Verizon and AT&T versions are locked up like Fort Knox. It is not some super-brickable Samsung. If you know what you're doing and the bootloader is unlocked, there are few software problems you couldn't fastboot your way out of on this device.
Read the Heisenberg guide. It tells you most of what you need to know. Understand that unlocking the bootloader will wipe your phone, so backup appropriately if you've been using it.
The Heisenberg guide is outdated on rooting marshmallow. Don't do the ivcarlos thing it mentions; supersu has advanced to the point that it handles all that boot image patching automagically for you as long as you install it right. You just have to force supersu to flash systemless; there are probably at least a dozen if not more threads about that in Q&A too and it has probably been discussed in the Heisenberg thread too.
The dead simple way to force supersu to install systemless is to start with version 2.62. It always flashed systemless.
ok then i have a quick question for you then. If it's answerable.
Can i run a rom from a micro SD card formatted as internal storage? or will this cause issues for me? i couldn't afford the 32 gb or higher model and thus i'm stuck with a meager 16 gb of internal storage with a 64 gb micro sd card currently. I'm planning on upgrading that as soon as i can afford to do so to a 128 gb micro sd card but as it is it seems that my phone LOVES to just forget about certain settings and permissions and even that i have playlists for my music player on the micro sd card. IDK if i'm having software issues with the phone itself and thus need to get the phone replaced but as it is currently every time i reboot my phone or it reboots on it's own (which can happen often depending on the day and time) it decides to randomly forget certain things.
silvernirvash said:
ok then i have a quick question for you then. If it's answerable.
Can i run a rom from a micro SD card formatted as internal storage? or will this cause issues for me? i couldn't afford the 32 gb or higher model and thus i'm stuck with a meager 16 gb of internal storage with a 64 gb micro sd card currently. I'm planning on upgrading that as soon as i can afford to do so to a 128 gb micro sd card but as it is it seems that my phone LOVES to just forget about certain settings and permissions and even that i have playlists for my music player on the micro sd card. IDK if i'm having software issues with the phone itself and thus need to get the phone replaced but as it is currently every time i reboot my phone or it reboots on it's own (which can happen often depending on the day and time) it decides to randomly forget certain things.
Click to expand...
Click to collapse
I would concur that the phone rebooting is a problem and one that should be fixed before your unlock and/or root. I have the xt1575 and I am in the same place trying to determine if I should take the plunge and unlock and root it. But I wanted to wait for a few months before doing so to ensure it worked first.
As to the 16gb sd card it should be ok to use. You go with what you can afford. I have used a 16, 32 64 and 28 in this phone and all is well.
As for which method or hoos instructions to use I am not sure because everyone says to use the Heisenberg's guide and not the info for the other so I am just as confused. I am still continuing to do the research for the complete guide for 6.0 with the july patched. I want to make sure I use the latest as well as the one that works guide.
Good luck and get that phone replaced...
if your still under warranty get the phone replaced if it is rebooting and doing odd things when you unlock the boot loader moto will void the warranty and the only thing that will be covered is hardware defects...
mirrin said:
if your still under warranty get the phone replaced if it is rebooting and doing odd things when you unlock the boot loader moto will void the warranty and the only thing that will be covered is hardware defects...
Click to expand...
Click to collapse
This!!! You might as well take the update and hard reset (Unlocking your bootloader will do this regardless so you would still have to start from out of box experience). If your reboot and wonky issues don't get resolved with a hard reset, warranty the phone. If you are wanting an unlocked bootloader for root and custom ROM purposes, only proceed after your phone is confirmed working or you get a warranty replacement. Once you unlock the bootloader, if there is hardware/software problems, Motorola may very well deny any claim due to voided warranty.
Hier
I Root my phone few days ago. I would like to use a sdcard. It tells me my phone is encrypted ! Is it ok ?? How Can i desable or unencrypted my phone ?
The phone comes encrypted to decrypt it you go into twrp and delete every thing and reinstall the ROM I do believe its along those lines but look into it.
bghyt said:
The phone comes encrypted to decrypt it you go into twrp and delete every thing and reinstall the ROM I do believe its along those lines but look into it.
Click to expand...
Click to collapse
Hello
I do not have a ROM. I must find one. I do not know how to do it. I do not want to brick the mobile.
it poses problems the fact that the mobile is encrypted?
it's having rooted the mobile that did that?
So the new security patch bricked my 8 pro into qualcomm crash dump screen.
I have done no funny business at all, yes my bootloader is unlocked and yes I have root. But it is only for basic things like titanium backup and permission ruler. I have never done anything crazy with my phone, never even flashed a rom, my phone has been rooted for well over a year and I always install all the security patches so this was super random and I'm pissed off.
Anyways I cannot find a video about recovering the phone without erasing everything and I thought this was only necessary when you DON'T have an unlocked bootloader. I thought it was possible to flash oxygen with fastboot and it fixes the problem. But I just dont know exactly how to do this and I didnt want to screw up anything. I'm totally fine with losing root and having the bootloader locked again I just really want to save my data. Any help and I would be grateful, because at this point I'm going to work tommorow without my phone.
one way... MSM tool and ITS deleting all your files
beterman said:
one way... MSM tool and ITS deleting all your files
Click to expand...
Click to collapse
wow man, this literally came from the security patch
If phone is accessible via ADB ( no bootloop ! ) then you can pull the data of interest by means of ADB-commands to a connected computer.
Look inside here:
[TOOL][ADB][WIN]Android Partitions Backupper / Cloner
Hi all, wrote a Windows CMD script that backups / clones partitions of an Android device via ADB because I wasn't content with any 3rd-party APK what claims to do this job. The backups /clones are stored on Windows computer as...
forum.xda-developers.com
Codeman785 said:
So the new security patch bricked my 8 pro into qualcomm crash dump screen.
I have done no funny business at all, yes my bootloader is unlocked and yes I have root. But it is only for basic things like titanium backup and permission ruler. I have never done anything crazy with my phone, never even flashed a rom, my phone has been rooted for well over a year and I always install all the security patches so this was super random and I'm pissed off.
Anyways I cannot find a video about recovering the phone without erasing everything and I thought this was only necessary when you DON'T have an unlocked bootloader. I thought it was possible to flash oxygen with fastboot and it fixes the problem. But I just dont know exactly how to do this and I didnt want to screw up anything. I'm totally fine with losing root and having the bootloader locked again I just really want to save my data. Any help and I would be grateful, because at this point I'm going to work tommorow without my phone.
Click to expand...
Click to collapse
Far as I'm aware the security patch was incremental and not a full update, seeing as you're rooted then I'd advise against installing incremental updates, when you update get the full one and pull the boot image for instances just like this.
Easiest way out of this is MSM although if you can obtain the boot image from 9.9 then you may be able to save it by booting that image / patched image.