Hello dear community, I hope someone can help me. I probably made a big mistake when I unlocked the boot loader on my moto G2. I suspect that all my apps and data are gone now? After unlocking and restarting the phone, I noticed that the startup process was not as usual. I then switched off the phone directly. Are my apps and data really gone now?
dausen50 said:
Hello dear community, I hope someone can help me. I probably made a big mistake when I unlocked the boot loader on my moto G2. I suspect that all my apps and data are gone now? After unlocking and restarting the phone, I noticed that the startup process was not as usual. I then switched off the phone directly. Are my apps and data really gone now?
Click to expand...
Click to collapse
Yes. Unlocking the device will wipe everything except external SD.
It's basically like a factory reset.
Wolfcity said:
Yes. Unlocking the device will wipe everything except external SD.
It's basically like a factory reset.
Click to expand...
Click to collapse
Thanks for your reply Wolfcity, although it is very painful. Are there any tools with which a rescue would be possible, such as Testdisk, PhotoRec, Foremost, Scalpel, ...?
The Smatphone is actually equipped with a memory card (SAMSUNG Evo Plus, 64 GB, Micro-SDXC). I would be very grateful for suggestions on data recovery.
In case it is still important that Motorola has Android 6.0 Marshmallow and the memory card is formatted as internal memory.
dausen50 said:
Thanks for your reply Wolfcity, although it is very painful. Are there any tools with which a rescue would be possible, such as Testdisk, PhotoRec, Foremost, Scalpel, ...?
The Smatphone is actually equipped with a memory card (SAMSUNG Evo Plus, 64 GB, Micro-SDXC). I would be very grateful for suggestions on data recovery.
In case it is still important that Motorola has Android 6.0 Marshmallow and the memory card is formatted as internal memory.
Click to expand...
Click to collapse
As you're not rooted there are very few apps that can backup your stuff like https://play.google.com/store/apps/details?id=com.rerware.android.MyBackupPro
There are ways to do it with ADB commands, just google it.
As you said you restarted your device after the unlocking procedure there won't be anything to save....
About your SD card formatted as internal storage: I never did that but I would think that data stored there will be erased too.
Related
Hi All,
Looking for some assistance please; I'm planning to trade-in my HTC One for an upgrade to a HTC One M8 most probably. Retailer is happy to accept the phone with a custom rom on it, so it saves me the bother of returning fully to stock. Got latest ARHD rom onboard but still S-On and original firmware.
Want to free up as much of the Internal Storage/SD Card as possible before handing it over (we got them with 25Gb available out of the 32Gb didn't we), but afraid to hit factory reset in recovery in case it clears the entire storage including recovery files/partition etc and rom image etc, and therefore wont reboot properly.
What's the cleanest and safest way to maximize available space without losing key data/files please? All thoughts welcomed/gratefully received!
sb09 said:
Hi All,
Looking for some assistance please; I'm planning to trade-in my HTC One for an upgrade to a HTC One M8 most probably. Retailer is happy to accept the phone with a custom rom on it, so it saves me the bother of returning fully to stock. Got latest ARHD rom onboard but still S-On and original firmware.
Want to free up as much of the Internal Storage/SD Card as possible before handing it over (we got them with 25Gb available out of the 32Gb didn't we), but afraid to hit factory reset in recovery in case it clears the entire storage including recovery files/partition etc and rom image etc, and therefore wont reboot properly.
What's the cleanest and safest way to maximize available space without losing key data/files please? All thoughts welcomed/gratefully received!
Click to expand...
Click to collapse
in your custom recovery choose wipe / and check everything but system ... that will wipe everything and the phone will still bootup and work fine
Use app like App2Sd or Link2Sd or system app remover. May be it will help to free up space by uninatalling unwanted apps or by movibg it to sdcard..
clsA said:
in your custom recovery choose wipe / and check everything but system ... that will wipe everything and the phone will still bootup and work fine
Click to expand...
Click to collapse
Hi, many thanks for your response! So I'm using TWRP 2.6.3.4 and options in wipe include the usual Dalvik, cache and data etc plus Internal Memory and System, so your saying I can check internal memory but not system and all will be well? Wont I need to put TWRP and Rob image files (and any others) back on afterwards? Thanks.
sb09 said:
Hi, many thanks for your response! So I'm using TWRP 2.6.3.4 and options in wipe include the usual Dalvik, cache and data etc plus Internal Memory and System, so your saying I can check internal memory but not system and all will be well? Wont I need to put TWRP and Rob image files (and any others) back on afterwards? Thanks.
Click to expand...
Click to collapse
it won't erase your recovery or system .. that's all that's needed to boot the phone
clsA said:
it won't erase your recovery or system .. that's all that's needed to boot the phone
Click to expand...
Click to collapse
Great, that's what I'll do then! Thank you. :good:
Hey everyone,
I'm having a storage issue with my Nexus 6. My available space is showing up as 32GB even though I have 64GB of real space. When I was on full stock, it showed up correctly, but after I flashed the no-encrypt boot.img in Android Development, Its showing up as 32 GB instead of 64.
Help appreciated!
You're going to have to do a factory reset from the backup & reset menu. Back up anything you want to keep since it will wipe EVERYTHING on your device. That's the only thing that worked for me when I had the issue with my N5 and that's what is suggested in the toolkit
Hero_Guy said:
You're going to have to do a factory reset from the backup & reset menu. Back up anything you want to keep since it will wipe EVERYTHING on your device. That's the only thing that worked for me when I had the issue with my N5 and that's what is suggested in the toolkit
Click to expand...
Click to collapse
Quick question, I have the exact same thing happening with my Nexus 6P - will this same fix work for me?
Hero_Guy said:
You're going to have to do a factory reset from the backup & reset menu. Back up anything you want to keep since it will wipe EVERYTHING on your device. That's the only thing that worked for me when I had the issue with my N5 and that's what is suggested in the toolkit
Click to expand...
Click to collapse
Yeah well, that is why toolkits are worse then paying attention and learning things
http://forum.xda-developers.com/nexus-6/general/phone-gb-storage-to-factory-reset-t3225492
No need to factory reset, you can fix through TWRP
JNCHD said:
Hey everyone,
I'm having a storage issue with my Nexus 6. My available space is showing up as 32GB even though I have 64GB of real space. When I was on full stock, it showed up correctly, but after I flashed the no-encrypt boot.img in Android Development, Its showing up as 32 GB instead of 64.
Help appreciated!
Click to expand...
Click to collapse
Did you resolve this using the TWRP method? I can't get it to work and I'm at my wits end.
mrdannyaitch said:
Did you resolve this using the TWRP method? I can't get it to work and I'm at my wits end.
Click to expand...
Click to collapse
What did you do and what part didn't work?
quick glance at TWRP makes me think all you need to do is go Wipe>advanced wipe>select data>repair or change file system>RESIZE. it seems like this should do it but having a 32gb n6 I can't test that. doesn't wipe anything so it could be worth a shot
Apologies, am typing from my phone and can't worm out how to link to another thread but there's also a thread where someone else has a 64gb showing 25gb which there are more details on.
Essentially I've flashed the December factory image using fastboot, using various methods:
All stages per the Q&A sticky, including flashing userdata and then using the TWRP method. Also all stages but replacing fastboot flash userdata with fastboot format userdata as I'm aware that the userdata.IMG is not intended for the 64gb.
Trying the TWRP method to resize always ends up with the same result, the red message saying my phone is unstable (or similar, I've seen other threads with the correct message, again apologies but am on my phone).
I've tried locking and relocking OEM lock to see if that helps or not, but nothing does.
My initial request for help on the other thread is because I got a replacement phone under insurance and didn't check if it was 32gb or 64gb and then noticed I only have 25, with the bootloader saying its a 32gb phone. I've asked but have had no answer yet whether the bootloader would change, is would it always actually know its a 64gb even if internal memory only shows it as a 32gb?
Believe it or not, I called Motorola and even with the IMEI and serial number, they could not tell me what my phone was!
Last night i did the deencrypt mod, cf auto root, and flashed twrp. I have only 23 gb available(at least 2gb missing) and Im confused out the box I swear i had near 26. I know that twrp and root dont take up that much space. Is the userdata.img taking up that much storage? I already reset to factory to see if that would clear anything. Is anyone else having this issue?
Can't offer any suggestions, but wanted to confirm that even after removing encryption I still have 26GB available.
After resetting back to factory default, does it still show up as only 23GB?
nerdgenius said:
Last night i did the deencrypt mod, cf auto root, and flashed twrp. I have only 23 gb available(at least 2gb missing) and Im confused out the box I swear i had near 26. I know that twrp and root dont take up that much space. Is the userdata.img taking up that much storage? I already reset to factory to see if that would clear anything. Is anyone else having this issue?
Click to expand...
Click to collapse
if you bought your phone from at&t, its probably the crap in the oem partition
It is a at&t phone but I deleted all the crap out the oem partition. Even the at&t still has 25 gigs with apps installed.
Did you make a backup prior to dencrypting? Might explain it...?
No I haven't. I will just reflash the stock image and try again.
This happened to me yesterday. I have the 64gb version and after trying to decrypt I was down to 23gb. I flashed the firmware, and then relocked the bootloader, and my space was back. Fair warning after relocking your boot up time will take forever.
This happened to me yesterday night too. I have the N6 64gb and after:
- unlock bootloader
- decrypt
- cf root
I was down to 23gb. What I should do now?? I don't care about data but what I have to do, will I lose root acces and decrytion??
Any Tutorial? I'm not that smart ;]
Happened on the Nexus 5 sometimes. Here's an article of how to fix that phone. Maybe the steps are similar.
http://www.droidviews.com/your-32gb-nexus-5-now-shows-only-16gb-here-is-how-to-fix-it/
Ok but do you think I can use a Tool Kit 1.9.9 ?
porn does take up a lot of space even if you have it in a zip folder labeled "Disney movies"
dligon said:
porn does take up a lot of space even if you have it in a zip folder labeled "Disney movies"
Click to expand...
Click to collapse
u know from experience..
I didn't decrypt my phone, but after flashing a stock image I did only have about 23 gb of space showing on my 64 gb phone. I had to do a factory reset to restore the missing space. Note this is a reset from the phone's settings menu (Settings > Backup & Reset > Factory data reset). It takes a while, and obviously deletes all the data on the phone.
Yep, Factory reset from settings - This way solve my problem, :good:
Do a factory reset. That will solve your problem.
My total space is 25.98gb on the 32gb model my phone is decrypted and rooted. I got it from US Cellular. No problems here besides apps like Facebook taking up several hindered megabytes....
Nexus 6
Just use fast boot to format user cache and see if that works. This happened to me 3-4 tens gene restoring my phone and its an easy fix. There is no need to relock your BL. There is also another OP I made a whole ago when this happened it me which could have answered your question much faster.
Hello all,
I'm currently running Lollipop 5.0.2 on my Moto G 2014 with no sign of the OTA to Marshmallow.
This thread contains Marshmallow firmware images.
The only issue with these is that they are for Indian and Brazillian variants of the XT1068.
Does anyone have a link to an official Marshmallow (6.0 or 6.0.1) firmware image for the Moto G 2014 Dual-Sim GB XT1068 that I can flash via fastboot?
If this really isn't possible (I realise this is a very specific request!), will the Indian/Brazillian variants work on my GB phone and will they be different in any way?
Many thanks in advance!
Hi .. Check this link :http://firmware.center/firmware/Motorola/Moto G (2nd gen-2014)/Stock/XT1068/. You can find the GB version there.
@garyben60 Thanks so much! Will this work with Dual-Sim as it doesn't have DS in the filename?
treela said:
@garyben60 Thanks so much! Will this work with Dual-Sim as it doesn't have DS in the filename?
Click to expand...
Click to collapse
. I think so . I think that past kit kat it will work for both but just check before you install.
@garyben60 How can I check? Is there a risk of hard-bricking my phone if I flash the wrong firmware image for my device?
I can only suggest you ask here or on similar forums. My feeling is you won't hardbrick your but I will try and find out for you.
garyben60 said:
I can only suggest you ask here or on similar forums. My feeling is you won't hardbrick your but I will try and find out for you.
Click to expand...
Click to collapse
Thanks! I would think that it wouldn't hard-brick but don't want to run the risk.
treela said:
Thanks! I would think that it wouldn't hard-brick but don't want to run the risk.
Click to expand...
Click to collapse
@garyben60 I flashed XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34_cid7_CFC.xml.zip (so not the GB one) and it worked fine.
It was taking ages to boot up (even longer than the first boot after a firmware flash normally takes, I think) so I reflashed. It took ages again and eventually booted up into Marshmallow
There was a very useful list of parts of the firmware filenames and what they mean but I can't find it now...
Thanks very much. I'll report back to say whether everything's working in case this thread helps others.
treela said:
@garyben60 I flashed XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34_cid7_CFC.xml.zip (so not the GB one) and it worked fine.
It was taking ages to boot up (even longer than the first boot after a firmware flash normally takes, I think) so I reflashed. It took ages again and eventually booted up into Marshmallow
There was a very useful list of parts of the firmware filenames and what they mean but I can't find it now...
Thanks very much. I'll report back to say whether everything's working in case this thread helps others.
Click to expand...
Click to collapse
. I'm glad you came right with the firmware. I would like to know what you think of Marshmallow. Please post some feedback here. Thanks!
@garyben60 Marshmallow is brilliant. It's faster than Lollipop, battery life is much improved and multitasking is also much better. There's some great new features also and a couple of bugs seem to have been fixed. I haven't tried the second SIM slot but I'm sure it works fine. Are you thinking of updating?
treela said:
@garyben60 Marshmallow is brilliant. It's faster than Lollipop, battery life is much improved and multitasking is also much better. There's some great new features also and a couple of bugs seem to have been fixed. I haven't tried the second SIM slot but I'm sure it works fine. Are you thinking of updating?
Click to expand...
Click to collapse
I have been thinking of installing the update but I've been very hesitant to do so because all the problems people are having. I want to ask how did you deal with the micro SD card issue? Did you adopt it as internal memory? If so, how did you get media files loaded on it as it is encrypted and can't be seen by any other device. (i.e your computer?). If you adopted it as regular external memory like with lollipop, how is you internal memory coping with not being able to move apps to the external SD card? If I can get satisfactory answers to these questions then I will do the update. Thanks for your feedback thus far. :good:
@garyben60 You're welcome I haven't used an SD yet but I'll pop one in now and report back if that's OK.
treela said:
@garyben60 You're welcome I haven't used an SD yet but I'll pop one in now and report back if that's OK.
Click to expand...
Click to collapse
THANK YOU
@garyben60 I'm so sorry - I completely forgot about this thread!
I formatted the SD as internal storage. This works well and when you plug your phone into PC when it is on, you can access your SD card. Unfortunately, accessing the internal storage or SD card is not possible from TWRP when the SD card is formatted as internal storage. This is very frustrating. You can move files to /data and then boot into TWRP and flash them from there but you have to be rooted first and I can't find a way to root because you need to flash a zip from the internal storage that you can't access! I'll try transferring a zip from the PC to TWRP later.
The storage behaviour in Marshmallow is rather confusing. Although you can access the SD card from the PC, I can't find a way to access the internal storage (unless it is merged with the SD card in the PC view, which may be the case).
Say if there's any other info I can give
Hello, I want to try rooting my phone. My phone doesn't have much internal storage space, and I got a 128 gb sd card. So I really want to move my app data into it, and I think I need to root my phone for that. I heard I first have to unlock my bootloader first though. Can someone tell me things I should know before attempting this my first time?
I am aware that it will wipe my phone, though I do wonder if it will wipe my SD card too though.