Ok, I'll admit it, for a lot of things, especially system administration, I prefer the command line.
Is there a reason why I would not use tar to do "full backup" of data (as opposed to TiBackup or the like)?
One advantage is that I can extract a tar on another box and, for example, check it in to a VC system.
Admittedly, busybox tar isn't the most full-featured implementation (no one-file-system option, for example), but I believe it does have an exclude-from-file option that works.
I may be wrong, but I don't think tar on our phones can save ownership and permissions (too lazy to try it out right now). I suppose it wouldn't be too hard to write a script to save any info that tar would not preserve into a properties file and then have a restore script that would read the properties file and chown and chmod every file after extracting.
xviiivx said:
I may be wrong, but I don't think tar on our phones can save ownership and permissions
Click to expand...
Click to collapse
busybox tar appears to work like "any" tar, at least for non-extended attributes (I don't know if the kernel supports xattrs )
Code:
$ tar tvf test.tar | head -n 10
drwxr-xr-x 0/0 0 2011-02-07 20:58 system/etc/
-rw-r--r-- 0/0 15346 2011-02-07 20:58 system/etc/apns-conf.xml
-rw-r--r-- 0/0 25 2011-02-07 20:58 system/etc/hosts
-rw-r--r-- 0/0 99026 2011-02-07 20:58 system/etc/NOTICE.html.gz
-r-xr-x--- 0/2000 1200 2011-02-07 20:58 system/etc/init.goldfish.sh
-rw-r--r-- 0/0 1707 2011-02-07 20:58 system/etc/vold.fstab
-rw-r--r-- 0/0 195 2011-02-07 20:58 system/etc/gps.conf
drwxr-xr-x 0/0 0 2011-02-07 20:58 system/etc/security/
-rw-r--r-- 0/0 91755 2011-02-07 20:58 system/etc/security/cacerts.bks
drwxr-xr-x 0/0 0 2011-02-07 20:58 system/etc/security/drm/
and does appear to preserve links as well
Code:
$ tar tvf test2.tar | head -n 10
lrwxrwxrwx 0/0 0 2011-03-15 12:09 etc -> /system/etc
These were created using busybox tar from /system/etc and of /etc, adb pull-ed, and extracted on another system (Cygwin, in this case).
If you look in the TitaniumBackup directory on the sdcard, each app has 3 files:
appname.apk.gz- I didn't check, but obviously is probably just a backup of the apk
appname.tar.gz (looks like a tar of the /data/data/app dir)
appname.properties- looks like it includes a huge chuck of data for the icon and some misc information, a lot of which appears to be... market information?
I don't know how important the third file is, but it looks like Titanium is using tar. You could download a junk app and try it with that app and see if it works.
Just a guess, but I bet untarring may not be enough, you'll probably have to run the command "pm install" on each apk.
Thanks Fubuya!
That leads me to two useful "conclusions"
tar probably works just fine
TiBackup files are likely extractable on a POSIX box
Yeah, on linux, one is just text and I extracted the other two just fine (tar -zxvf for one and gunzip for the other). It's probably just a matter of finding out if there are any extra tricks you need to know about. Looks like Tibackup has a forum here, if you run into problems maybe they'd be nice enough to translate what's happening on the backend of their backup process.
Cyanogenmod 7 for the Lenovo Ideapad A1, by Milaq and myself.
BEFORE YOU BEGIN
You should install the modified bootloader that allows you to get into fastboot mode if necessary. This is because there is only one kernel on the A1, and if the kernel causes problems (unlikely, but it's better save yourself the risk) you won't be able to boot normally or into recovery. Being able to boot into fastboot mode gives you a way out of this by allowing you to flash a kernel through usb with the fastboot command. See this post: http://forum.xda-developers.com/showpost.php?p=25186171&postcount=120
Simple installation guide
David Artiss has written a beginners' guide that walks you through the process of installing CM7 starting from the stock system. Get to it here:
http://www.artiss.co.uk/2012/04/installing-cyanogenmod-on-a-lenovo-ideapad-a1
Syncing and building it:
Clone the Cyanogenmod repository:
Code:
repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
Then add the local manifest:
Code:
git clone https://github.com/milaq/android.git local-android
cd local-android
git checkout gingerbread
cd ..
cp local-android/local_manifest.xml android/.repo
They sync the repo, get rom manager, and build:
Code:
cd android
repo sync
./vendor/cyanogen/get-rommanager
source build/envsetup.sh && brunch A1_07
What works:
Graphics HW acceleration
Touchscreen
Buttons (vol, power, menu, back, home)
Removable SD card
Audio
Accelerometer
Wifi (see caveat below)
Bluetooth
Vibration
Internal SD card
Front and back camera for still images, video recording from back camera
GPS
HW accelerated decoding (h.264 etc)
Issues
No 3G on the 3G versions.
Video recording from the front camera
Accelerometer switch not working
Market gives phone layout instead of tablet layout after update
Modified partition layout used with CWM 5.0.2.8 seems to prevent the internal SD card mounting.
GPS Time from android.location.Location.getTime() is wrong (1 day ahead?).
DSPManager sometimes crashes when headphones are inserted.
Bluetooth file transfer doesn't work, but Bluetooth HID seems to work.
IRC Channel
#ideapad-a1 on irc.freenode.net.
Recent logs at http://shron.de/irclogs/ideapad-a1.log
Some older logs at http://shron.de/ideapad-a1.log
Download page
Nightly builds, built by Milaq and hosted by goo.im:
http://goo.im/devs/milaq/a107/cm-7
Acknowledgments
Many thanks to:
Milaq - fixing loads of things: Camera, GPS, vibration, autobrightness, cpu responsiveness, scrolling performance, wifi geolocation, disabling background blur, hiding phone signal by default, density fixes, etc, etc, ...
SpiegelEiXXL - many discussions and thoughts, setting up nightly builds, hosting nightly builds.
Pati- for spotting how to prevent the reboots and internal SD card fixes.
Templis - Channel logs
Collaboration
Please feel free to discuss this porting effort here, point out errors, fork the repositories, submit patches/pull requests etc!
Latest updates:
18 Feb: Nightly downloads added. Please follow the commit log on Github for further details of updates: https://github.com/gmarkall/android_device_ideapad_a1/commits/gingerbread
12 Feb: Fixed the 5:43 reboot issue, wifi (sort of), and accelerometer. New version on download page.
17 Jan: Got it booting, added download page.
15 Jan: Made some very hacky changes that allow an otapackage to be built.
14 Jan: Tried flashing it - so far not quite booting as far as the home screen, but does get to the boot screen.
13 Jan: I had the wrong size for the system partition, which was causing make_ext4fs to fail. This is now corrected, and the build finishes.
13 Jan: I created an IRC channel for discussion of Clockworkmod, Cyanogenmod and development on the A1. It is #ideapad-a1 on irc.freenode.net.
12 Jan: I've added a few more bits and bobs to the build - in particular editing BoardConfig.mk to include settings for building libaudio.so, using the camera stub for the time being, bluetooth settings, etc. Also added some missing files: /etc/media_profiles.xml and vold.a1.fstab, overlay.omap3.so.
11 Jan: added a script that pulls the proprietary libraries off the device and creates a vendor/lenovo/a1 folder for them.
I have a 16GB Lenovo A1 and am more than happy to help out with any testing you need with CM7!
Just drop me a PM if you want any private testing done or I will test out the moment you post a Rom here to flash.
Thanks, Charlie.
awesome! did you already try to flash and run it?
BuzzyB said:
awesome! did you already try to flash and run it?
Click to expand...
Click to collapse
Not yet. At the moment the build system doesn't quite work for making a flashable zip suitable for the ideapad. I want to get the build system to make the update.zips without any manual intervention, rather than just putting one together by hand - otherwise it will be a pain every time I change something to have to manually make a new update.zip.
BuzzyB said:
awesome! did you already try to flash and run it?
Click to expand...
Click to collapse
I tried flashing it - I'm not quite getting as far as the home screen in booting yet, but it's a start:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
nice teaser
Awesome!!!
Simply wonderful!
Update
something new...
:sehorn:
Cool beans!
So with the latest version I have, after bootup there's some problems with dalvik-cache.
The files in /cache/dalvik-cache and their permissions are:
Code:
# ls -l
-rw-r--r-- 1 system system 850744 Aug 1 2008 [email protected]@[email protected]
-rw-r--r-- 1 system system 57112 Aug 1 2008 [email protected]@[email protected]
-rw-r--r-- 1 system system 232920 Aug 1 2008 [email protected]@[email protected]
-rw-r--r-- 1 system system 27960 Aug 1 2008 [email protected]@[email protected]
-rw-r--r-- 1 root root 266000 Jan 16 23:36 [email protected]@[email protected]
-rw-r--r-- 1 system system 194352 Aug 1 2008 [email protected]@[email protected]
-rw-r--r-- 1 system system 13880 Aug 1 2008 [email protected]@[email protected]
-rw-r--r-- 1 root root 778656 Jan 16 23:36 [email protected]@[email protected]
-rw-r--r-- 1 system system 7448 Aug 1 2008 [email protected]@[email protected]
-rw-r--r-- 1 root root 24128 Jan 16 23:36 [email protected]@[email protected]
-rw-r--r-- 1 root root 4798600 Jan 16 23:36 [email protected]@[email protected]
-rw-r--r-- 1 root root 1391096 Jan 16 23:36 [email protected]@[email protected]
-rw-r--r-- 1 root root 8087736 Jan 16 23:36 [email protected]@[email protected]
-rw-r--r-- 1 system system 6816 Aug 1 2008 [email protected]@[email protected]
-rw-r--r-- 1 system system 4504 Aug 1 2008 [email protected]@[email protected]
-rw-r--r-- 1 system system 61616 Aug 1 2008 [email protected]@[email protected]
-rw-r--r-- 1 system system 89720 Aug 1 2008 [email protected]@[email protected]
-rw-r--r-- 1 system system 28496 Aug 1 2008 [email protected]@[email protected]
-rw-r--r-- 1 root root 1638216 Jan 16 23:36 [email protected]@[email protected]
-rw-r--r-- 1 system system 147728 Aug 1 2008 [email protected]@[email protected]
-rw-r--r-- 1 system system 8496 Aug 1 2008 [email protected]@[email protected]
Logcat is at: http://www.doc.ic.ac.uk/~grm08/ideapad/cm7-a1-logcat-jan-17.txt
Any suggestions?
Did you try to chmod 777 /cache/dalvik-cache
Just for testing it?
OTA use data/dalvik-cache and have the same File right like you do.
# create dalvik-cache and double-check the perms
mkdir /data/dalvik-cache 0771 system system
chown system system /data/dalvik-cache
chmod 0771 /data/dalvik-cache
# create the lost+found directories, so as to enforce our permissions
mkdir /data/lost+found 0770
mkdir /cache/lost+found 0770
---------- Post added at 09:47 PM ---------- Previous post was at 09:35 PM ----------
What rights have your /cache/dalvik-cache Folder?
It schould have 771
But i think that /cache have only 770
xbdesign said:
Did you try to chmod 777 /cache/dalvik-cache
Just for testing it?
Click to expand...
Click to collapse
I did try that, but it didn't make any difference unfortunately.
So what rights you have now for that Folder (after/at boot)?
xbdesign said:
So what rights you have now for that Folder (after/at boot)?
Click to expand...
Click to collapse
Code:
# ls -l
drwxrwx--x 2 system system 3072 Jan 17 21:02 dalvik-cache
I just noticed that it's only things that run as app_XX that have a problem opening /cache/dalvik-cache/[email protected]@ ...
Things that run as system, e.g. com.android.settings, don't seem to have a problem.
I feel like I'm missing something obvious now!
Right,
all Positions that have root have a Problem
-rw-r--r-- 1 root root
On STOCK ROM there are no Files that have one root root.
They are all having
system system
or
system app_<AppNr>
or
system radio
xbdesign said:
Right,
all Positions that have root have a Problem
-rw-r--r-- 1 root root
Click to expand...
Click to collapse
What is the problem? Those are the same permissions as on my CM7 Desire which doesn't have this issue.
No Problem.
Just wondering why every one of them giving an Error.
I have no working CM7 to compare it to.
---------- Post added at 10:59 PM ---------- Previous post was at 10:52 PM ----------
Are you at stage where you can Wipe dalvik-cache, or it is hapening by building/restoring it?
Hi guys
Last night i was messing with my GPS and Ndrive gave me an error saying invalid ID, after researching i found that my imei was set to unknown, a reboot solved the issue and it was with the original imei. This morning i wanted to try trinity kernel so i booted in recovery, wiped cache and installed Trinity. After boot Whatsapp gave me an error that my number was changed bla bla to try to recover bu resending me a SMS but the SMS never came and i noticed this time that my IMEI was a generic one starting with 0049.
All fine since i have a efs.img backup, but for some reason i just can't change it back. I tried to delete the efs folder with root explorer with r/w permission but outputs a error that cannot delete. I tried the many tools around but one doesn't recognize my efs.img backup and the other outputs an error about permissions.
I also tried cat /mnt/sdcard/efs.img >> /dev/block/mtdblock6
It doesn't output any error, but after reboot the IMEI is still the generic one. I really need to fix this asap because it's my only working phone available atm.
Any idea?
I have some ideas. Firstly though, can you provide any .nv.log files you have? There shouldn't be any identifiable info but check to make sure anyway. New, old, anything will help.
Otherwise, after flashing with cat, delete nv_data.bin and rename nv_data.bak to nv_data.bin. Delete all .md5 files.
I have not had any need to replace these files nor experience with lost imeis so feel free not to take my advice. There is little you can do to raise hell at this stage since you already have a backup.
Harbb said:
I have some ideas. Firstly though, can you provide any .nv.log files you have? There shouldn't be any identifiable info but check to make sure anyway. New, old, anything will help.
Otherwise, after flashing with cat, delete nv_data.bin and rename nv_data.bak to nv_data.bin. Delete all .md5 files.
I have not had any need to replace these files nor experience with lost imeis so feel free not to take my advice. There is little you can do to raise hell at this stage since you already have a backup.
Click to expand...
Click to collapse
This is the nv.log
Sun Jan 2 05:50:40 2005: No NV backup found. Create one before MD5 on.
Sun Jan 2 05:50:40 2005: NV data back-up begin.
Sun Jan 2 05:50:40 2005: nv_data.bin does not exist.
Sun Jan 2 05:50:40 2005: NV data backup stopped due to NV data size.
Sun Jan 2 05:50:40 2005: MD5 is turned on.
Sun Jan 2 05:50:40 2005: nv_data.bin does not exist.
Sun Jan 2 05:50:40 2005: default NV restored.
Sun Jan 2 06:33:41 2005: MD5 is turned off on 0
Mon Apr 18 17:35:22 2011: NV data back-up begin.
Mon Apr 18 17:35:22 2011: NV data back-up begin.
Mon Apr 18 17:35:22 2011: NV data back-uped.
Mon Apr 18 17:35:22 2011: MD5 is turned on.
Mon Apr 18 22:51:52 2011: MD5 is turned off on 0
Mon Apr 18 22:53:33 2011: NV data back-up begin.
Mon Apr 18 22:53:33 2011: NV data back-up begin.
Mon Apr 18 22:53:33 2011: NV data back-uped.
Mon Apr 18 22:53:33 2011: MD5 is turned on.
Tue Apr 19 07:00:12 2011: MD5 is turned off on 2
Tue Apr 19 12:01:21 2011: enabling MD5 automatically because it was off temporarily.
Tue Apr 19 12:01:21 2011: NV data back-up begin.
Tue Apr 19 12:01:21 2011: NV data back-up begin.
Tue Apr 19 12:01:21 2011: NV data back-uped.
Tue Apr 19 12:01:22 2011: MD5 is turned on.
Tue Apr 19 12:01:36 2011: MD5 is turned off on 0
Tue Apr 19 12:03:21 2011: NV data back-up begin.
Tue Apr 19 12:03:21 2011: NV data back-up begin.
Tue Apr 19 12:03:21 2011: NV data back-uped.
Tue Apr 19 12:03:22 2011: MD5 is turned on.
Tue Apr 19 12:04:08 2011: MD5 is turned off on 0
Tue Apr 19 12:04:50 2011: NV data back-up begin.
Tue Apr 19 12:04:50 2011: NV data back-up begin.
Tue Apr 19 12:04:50 2011: NV data back-uped.
Tue Apr 19 12:04:51 2011: MD5 is turned on.
Tue Apr 19 12:08:01 2011: MD5 is turned off on 2
Tue Apr 19 12:09:37 2011: MD5 is turned off on 0
Tue Apr 19 12:10:01 2011: NV data back-up begin.
Tue Apr 19 12:10:01 2011: NV data back-up begin.
Tue Apr 19 12:10:01 2011: NV data back-uped.
Tue Apr 19 12:10:02 2011: MD5 is turned on.
Tue Apr 19 12:16:06 2011: MD5 is turned off on 2
Tue Apr 19 12:16:14 2011: NV data back-up begin.
Tue Apr 19 12:16:14 2011: NV data back-up begin.
Tue Apr 19 12:16:14 2011: NV data back-uped.
Tue Apr 19 12:16:30 2011: MD5 is turned on.
Tue Apr 19 12:22:29 2011: MD5 is turned off on 2
Tue Apr 19 12:22:37 2011: NV data back-up begin.
Tue Apr 19 12:22:37 2011: NV data back-up begin.
Tue Apr 19 12:22:37 2011: NV data back-uped.
Tue Apr 19 12:22:52 2011: MD5 is turned on.
Click to expand...
Click to collapse
Solved the issue. Wiped the ROM in recovery and reinstalled it after deleting the efs folder.
Hi
I tried everything to restore this phone back to stock, but every fast boot command fails.
Motorola drivers are installed on my pc, they are version 6.4 64 bit.
I put my device into Fastboot Flash mode by pressing power+volume down, adb interface shows in device manager.
Then I can do fastboot devices and it returns: "TA986029AY fastboot"
When I run adb devices it returns:
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
No devices are listed.
Does anyone know why fastboot works and not adb?
Bootloader is unlocked.
I did this by:
fastboot oem get_unlock_data
Concatenated the strings
Went to Motorola site to get a unique ID
fastboot oem unlock UNIQUE_KEY
When I turn on the device, it displays a message that the bootloader is unlocked.
My fastboot/adb tools are from google, the latest. I just downloaded the android sdk tools using command line sdkmanager.
I downloaded this firmware:
XT1039_PEREGRINE_VFEU_5.1_LPBS23.13-17.3-1_cid7_CFC.xml
I am not sure if it the right one since I am not able to get into settings in the phone about phone since it is displaying a black screen.
Is there a fastboot command that would reveal this?
Before flashing I run: fastboot -w
It outputs this:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
wiping cache...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.063s]
erasing 'cache'...
OKAY [ 0.063s]
What is a (bootloader) slot-count: not found?
Does not look right.
Then I run these commands:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
They all succeed, but they still show (bootloader) slot-count: not found.
Reboot the phone, I still have a black screen.
I also tried:
fastboot update XT1039_Retail_EU_444_Untouched.zip
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
archive does not contain 'android-info.txt'
error: update package 'XT1039_Retail_EU_444_Untouched.zip' has no android-info.txt
What is an android-info.txt file? I think the zip file above is wrong, where do I get a stock firmware image file with android-info.txt file?
I am totally lost for now.
I need some GURU that can help me here.
Thank you in advance
Best regards
Alfred56
Try using ...
alfred56 said:
Hi
I tried everything to restore this phone back to stock, but every fast boot command fails
Thank you in advance
Best regards
Alfred56
Click to expand...
Click to collapse
Try using Motorola Fastboot (mFastboot-v2 - XDA Forums - XDA Developers), then try flashing a stock rom for your phone and country from: https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816
S.
sdembiske said:
Try using Motorola Fastboot (mFastboot-v2 - XDA Forums - XDA Developers), then try flashing a stock rom for your phone and country from: https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816
S.
Click to expand...
Click to collapse
Thank you for your reply sdembiske.
I cannot use adb since no devices are listed when I issue the adb devices command. This has been tried with the Motorola drivers and also the universal adb drivers for the adb interface in device manager.
fastboot/mfastboot work.
How do I transfer the recoverytwrp2-8-7.img or cm-12.1-20150725-UNOFFICIAL-peregrine.zip to my mobile since I cannot use adb sideload?
Can this be achieved via fastboot?
Alfred56
Motorola fastboot is specifically for Moto devices ...
alfred56 said:
Thank you for your reply sdembiske.
I cannot use adb since no devices are listed when I issue the adb devices command. This has been tried with the Motorola drivers and also the universal adb drivers for the adb interface in device manager.
fastboot/mfastboot work.
How do I transfer the recoverytwrp2-8-7.img or cm-12.1-20150725-UNOFFICIAL-peregrine.zip to my mobile since I cannot use adb sideload?
Can this be achieved via fastboot?
Alfred56
Click to expand...
Click to collapse
Motorola fastboot is specifically for Moto devices.
Search and download this: "mFastboot-v2 - XDA Forums - XDA Developers" - install it and try it. It is not regular adb fastboot and will often work on Moto devices when adb fastboot won't. If it works, you should be able to push your file to your SD card - failing that flash a system image if you can get a hold of one - start with the site I referenced in my first post and ask for help.
Failing all that, try FWUL on XDA (https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755), burn it to a flash drive and boot it up on your computer and plug your phone in. If you have issues using it, post to steadfasterX (it's his site and has been very helpful in my dealings with him).
That's all I got for you.
S.
PS: when people try to help, don't forget to click the Thanks button ...
sdembiske said:
Motorola fastboot is specifically for Moto devices.
Search and download this: "mFastboot-v2 - XDA Forums - XDA Developers" - install it and try it. It is not regular adb fastboot and will often work on Moto devices when adb fastboot won't. If it works, you should be able to push your file to your SD card - failing that flash a system image if you can get a hold of one - start with the site I referenced in my first post and ask for help.
Failing all that, try FWUL on XDA (https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755), burn it to a flash drive and boot it up on your computer and plug your phone in. If you have issues using it, post to steadfasterX (it's his site and has been very helpful in my dealings with him).
That's all I got for you.
S.
PS: when people try to help, don't forget to click the Thanks button ...
Click to expand...
Click to collapse
Thanks again mate.
I managed to get adb devices to work, now it shows:
C:\android\platform-tools>adb devices
List of devices attached
TA986029AY sideload
when I go into recovery and select adb sideload.
I downloaded this ota package:
98bf5eb65e89fb5a4257135dfdff76662ffc01c9.98bf5eb65e89fb5a4257135dfdff76662ffc01c9.incremental-KTU84P.M003_18-LRX21Z.M002_15.zip
But when I try to upload it I get:
adb sideload failed to verify signature
Obviously I have the wrong OTA package.
Where can I download totally Motorola stock OTA images for XT1039 LTE either KitKat 4.4 or Lollipop 5.1?
I searched everywhere I cannot find them or the links are broken.
I already tried with mFastboot-v2 and use the zip files that contain the xml file.
Everything succeeds but after I reboot I get optimizing apps 1 of xxx and then blank very dark grey screen.
Regards
See if you can ...
alfred56 said:
Thanks again mate.
I managed to get adb devices to work, now it shows:
C:\android\platform-tools>adb devices
List of devices attached
TA986029AY sideload
when I go into recovery and select adb sideload.
I downloaded this ota package:
98bf5eb65e89fb5a4257135dfdff76662ffc01c9.98bf5eb65e89fb5a4257135dfdff76662ffc01c9.incremental-KTU84P.M003_18-LRX21Z.M002_15.zip
But when I try to upload it I get:
adb sideload failed to verify signature
Obviously I have the wrong OTA package.
Where can I download totally Motorola stock OTA images for XT1039 LTE either KitKat 4.4 or Lollipop 5.1?
I searched everywhere I cannot find them or the links are broken.
I already tried with mFastboot-v2 and use the zip files that contain the xml file.
Everything succeeds but after I reboot I get optimizing apps 1 of xxx and then blank very dark grey screen.
Regards
Click to expand...
Click to collapse
See if you can ... get help from the authors of the following:
5.1: https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816
4.4: https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-kitkat-rom-t3160127
https://forum.xda-developers.com/mo...t1039-moto-g-4g-stock-firmware-kxb21-t2805619
Did you not install a custom recovery and root after unlocking your bootloader? Priority!
https://forum.xda-developers.com/moto-g/4g-development/unofficial-twrp-3-0-0-0-moto-g-lte-t3310450
S.
sdembiske said:
See if you can ... get help from the authors of the following:
5.1: https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816
4.4: https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-kitkat-rom-t3160127
https://forum.xda-developers.com/mo...t1039-moto-g-4g-stock-firmware-kxb21-t2805619
Did you not install a custom recovery and root after unlocking your bootloader? Priority!
https://forum.xda-developers.com/moto-g/4g-development/unofficial-twrp-3-0-0-0-moto-g-lte-t3310450
S.
Click to expand...
Click to collapse
Hi,
I have downloaded the latest TWRP twrp-3.1.0-0-peregrine.img and flash using the following command:
fastboot flash recovery twrp-3.1.0-0-peregrine.img
This is the output:
C:\android\platform-tools>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (9434 KB)...
OKAY [ 0.327s]
writing 'recovery'...
OKAY [ 0.178s]
finished. total time: 0.507s
I am concerned about the slot-count/slot-suffixes not found.
Then I unplug the phone and:
1) Volume down to select recovery
2) Volume up
3) The droid image appears
4) Power+volume up and TWRP does not load, just the standard Motorola recovery.
What am I doing wrong? Or has this phone had it?
Thanks
Regards
Alfred56
alfred56 said:
Hi,
I have downloaded the latest TWRP twrp-3.1.0-0-peregrine.img and flash using the following command:
fastboot flash recovery twrp-3.1.0-0-peregrine.img
This is the output:
C:\android\platform-tools>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (9434 KB)...
OKAY [ 0.327s]
writing 'recovery'...
OKAY [ 0.178s]
finished. total time: 0.507s
I am concerned about the slot-count/slot-suffixes not found.
Then I unplug the phone and:
1) Volume down to select recovery
2) Volume up
3) The droid image appears
4) Power+volume up and TWRP does not load, just the standard Motorola recovery.
What am I doing wrong? Or has this phone had it?
Thanks
Regards
Alfred56
Click to expand...
Click to collapse
It sounds like your install of TWRP was successful ... but ...
From the TWRP site: https://twrp.me/devices/motorolamotog2014lte.html
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Try again and follow their suggestion
S.
PS: Don't forget to click the Thanks button when someone is trying to help ...
sdembiske said:
It sounds like your install of TWRP was successful ... but ...
From the TWRP site: https://twrp.me/devices/motorolamotog2014lte.html
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Try again and follow their suggestion
S.
PS: Don't forget to click the Thanks button when someone is trying to help ...
Click to expand...
Click to collapse
Thanks again for your great assistance.
I tried to flash twrp again using:
fastboot flash recovery twrp.img
Console output:
C:\android\platform-tools>fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (8314 KB)...
OKAY [ 0.293s]
writing 'recovery'...
OKAY [ 0.160s]
finished. total time: 0.456s
But on the mobile XT1039 LTE it shows:
mismatched partition size (recovery)
Anyway I have run out of avenues, I will probably chuck this phone into the bin.
It is probably cheaper to buy another phone rather than spending the last 3 days to make this work.
I still do not understand what this means and how to fix it:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
My best regards
Alfred56
PS: I am going to bed....it is 12:42 AM in Melbourne AUS.
alfred56 said:
Thanks again for your great assistance.
I tried to flash twrp again using:
fastboot flash recovery twrp.img
Console output:
C:\android\platform-tools>fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (8314 KB)...
OKAY [ 0.293s]
writing 'recovery'...
OKAY [ 0.160s]
finished. total time: 0.456s
But on the mobile XT1039 LTE it shows:
mismatched partition size (recovery)
Anyway I have run out of avenues, I will probably chuck this phone into the bin.
It is probably cheaper to buy another phone rather than spending the last 3 days to make this work.
I still do not understand what this means and how to fix it:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
My best regards
Alfred56
PS: I am going to bed....it is 12:42 AM in Melbourne AUS.
Click to expand...
Click to collapse
The mismatched partition size (recovery) can be ignored. It looks like TWRP successfully installed. The slot count reference has been attributed to a newer version of adb (can't confirm) but doesn't seem to impact from my understanding.
Did you ... after the install and immediately After typing fastboot reboot, hold the key combo and boot to TWRP ?
Read the following post by senior member cam1john, that I've copied and pasted from XDA: https://forum.xda-developers.com/moto-e/help/moto-e-unlocked-wont-to-twrp-screen-t3333443/page3
I got this error time after time: "(bootloader) has-slot:recovery: not found"
I used this command just like everyone else:
Code:
fastboot flash recovery recovery.img
Didn't work didn't work, and I couldn't do anything else cause I was following directions.
Then I tried:
Code:
fastboot boot recovery.img
and it worked the first time, no error, and it went into twrp automatically. Just thought I'd share that since I spent a few hours trying to change what I was doing wrong.
Ring any bells ... ?
S.
NB: Common courtesy is to click the Thanks button when you are asking for help and people respond.
sdembiske said:
The mismatched partition size (recovery) can be ignored. It looks like TWRP successfully installed. The slot count reference has been attributed to a newer version of adb (can't confirm) but doesn't seem to impact from my understanding.
Did you ... after the install and immediately After typing fastboot reboot, hold the key combo and boot to TWRP ?
Read the following post by senior member cam1john, that I've copied and pasted from XDA: https://forum.xda-developers.com/moto-e/help/moto-e-unlocked-wont-to-twrp-screen-t3333443/page3
I got this error time after time: "(bootloader) has-slot:recovery: not found"
I used this command just like everyone else:
Code:
fastboot flash recovery recovery.img
Didn't work didn't work, and I couldn't do anything else cause I was following directions.
Then I tried:
Code:
fastboot boot recovery.img
and it worked the first time, no error, and it went into twrp automatically. Just thought I'd share that since I spent a few hours trying to change what I was doing wrong.
Ring any bells ... ?
S.
NB: Common courtesy is to click the Thanks button when you are asking for help and people respond.
Click to expand...
Click to collapse
Hi,
I was able to use the command fastboot boot twrp.img to boot straight into TWRP.
First I wiped:
Dalvik cache, System, Data and cache.
Then I pressed install, selected a rom stored on my secondary SDCARD called XT1039_Retail_EU_51_Untouched_Stagefright_Patched.zip
TWRP confirmed that it was uploaded fine.
But when I rebooted the phone I got:
Optimizing apps 1 of 59, then it went black again.
I possibly have the wrong ROM, I don't know.
Thanks
Regards
Alfred56
You're making progress ...
alfred56 said:
Hi,
I was able to use the command fastboot boot twrp.img to boot straight into TWRP.
First I wiped:
Dalvik cache, System, Data and cache.
Then I pressed install, selected a rom stored on my secondary SDCARD called XT1039_Retail_EU_51_Untouched_Stagefright_Patched.zip
TWRP confirmed that it was uploaded fine.
But when I rebooted the phone I got:
Optimizing apps 1 of 59, then it went black again.
I possibly have the wrong ROM, I don't know.
Thanks
Regards
Alfred56
Click to expand...
Click to collapse
You're making progress ... now go back into TWRP and select Wipe and then swipe the bottom slider on that screen to do a factory reset then reboot again. If that that doesn't do the trick, then try a different rom (It would be helpful if you knew exactly what the stock firmware was when you got the phone in order to match it).
S.
sdembiske said:
The mismatched partition size (recovery) can be ignored. It looks like TWRP successfully installed. The slot count reference has been attributed to a newer version of adb (can't confirm) but doesn't seem to impact from my understanding.
Did you ... after the install and immediately After typing fastboot reboot, hold the key combo and boot to TWRP ?
Read the following post by senior member cam1john, that I've copied and pasted from XDA: https://forum.xda-developers.com/moto-e/help/moto-e-unlocked-wont-to-twrp-screen-t3333443/page3
I got this error time after time: "(bootloader) has-slot:recovery: not found"
I used this command just like everyone else:
Code:
fastboot flash recovery recovery.img
Didn't work didn't work, and I couldn't do anything else cause I was following directions.
Then I tried:
Code:
fastboot boot recovery.img
and it worked the first time, no error, and it went into twrp automatically. Just thought I'd share that since I spent a few hours trying to change what I was doing wrong.
Ring any bells ... ?
S.
NB: Common courtesy is to click the Thanks button when you are asking for help and people respond.
Click to expand...
Click to collapse
Hi Sdembiske,
How are you?
I will give you an update about what is happening.
As I said earlier I am able to boot into TWRP 3.1 and run tasks like wipe, format and install.
I noticed that even if I wipe everything (Dalvik cache+cache+data+Internal Storage+System), some files are not deleted.
For example when I use twrp file manager and navigate to /sdcard/dcim/camera, I can still see many jpg/mp4 files that have not been wiped.
I thought the WIPE function would complete delete all files.
Feels as if some parts of internal storage are read-only.
Then I thought I might not have root access, so I downloaded superboot and ran superboot-windows.bat.
After rebooting the phone, the key combination that takes you into recovery was not working.
The key combo for my XT1039 is to get into bootloader mode first (power+volume down), volume down to recovery, volume up to select recovery, dead droid appears no command and finally power+volume up, but it does not work. You to try several times and eventually it goes into standard motorola recovery.
Still not sure which firmware image to download.
There are, I believe 3 kind of images:
IE:
OTA packages
XT1039_PEREGRINE_RETEU_5.1_LPB23.13-17.6_cid7_CFC.xml.zip
XT1039_Retail_EU_51_Untouched_Stagefright_Patched.zip
Which one do I use for TWRP install option?
Thanks
Alfred56
Are you still able to ...
alfred56 said:
Hi Sdembiske,
How are you?
I will give you an update about what is happening.
As I said earlier I am able to boot into TWRP 3.1 and run tasks like wipe, format and install.
I noticed that even if I wipe everything (Dalvik cache+cache+data+Internal Storage+System), some files are not deleted.
For example when I use twrp file manager and navigate to /sdcard/dcim/camera, I can still see many jpg/mp4 files that have not been wiped.
I thought the WIPE function would complete delete all files.
Feels as if some parts of internal storage are read-only.
Then I thought I might not have root access, so I downloaded superboot and ran superboot-windows.bat.
After rebooting the phone, the key combination that takes you into recovery was not working.
The key combo for my XT1039 is to get into bootloader mode first (power+volume down), volume down to recovery, volume up to select recovery, dead droid appears no command and finally power+volume up, but it does not work. You to try several times and eventually it goes into standard motorola recovery.
Still not sure which firmware image to download.
There are, I believe 3 kind of images:
IE:
OTA packages
XT1039_PEREGRINE_RETEU_5.1_LPB23.13-17.6_cid7_CFC.xml.zip
XT1039_Retail_EU_51_Untouched_Stagefright_Patched.zip
Which one do I use for TWRP install option?
Thanks
Alfred56
Click to expand...
Click to collapse
I'm scratching my head Afred56, not pulling out my hair as I'm sure you must be now. Thanks for asking.
Are you still able to ... get into TWRP using the command you used that worked (Note: if it wasn't it should be renamed to recovery.img)? If not, reinstall it.
For root: download Chainfire's SuperSu from here: https://download.chainfire.eu/696/supersu/ push it to your sd card or copy it over if you can and then install the zip. You can follow the directions from here: http://www.theandroidsoul.com/how-to-flash-supersu-using-twrp-recovery-and-root-any-android-device/
I would use first: Retail EU 5.1 ROM (Untouched) (543mb) [Download] (Partially 'Stagefright' Patched) from: https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t31428
Then, follow this:
How to flash:
1) Boot into latest TWRP and Format Data (Wipe > Format DATA > Yes) - This step is essential, and will wipe Internal Storage (Downloads, Music, Photos etc, **backup important files**)
2) Transfer ROM to SDCARD or Internal Storage. This may be done in Windows via MTP, or using adb sideload or adb push ROM.zip /sdcard/
3) TWRP > Wipe > Factory reset and flash ROM.
4) Reboot.
5) Call / WiFi issues can be solved by flashing 5.1 Radio Firmware (Below) for your Model.
Then: Flash(install) via TWRP from the same site
Updated Google Dialer
XT1039 Stock 5.1 Dialer | Messenger (Clear Dalvik Cache after flashing)
Full Stagefright Patch (Dec 2015) - [Download]
As well as flash 5.1 Radio Firmware for your Model from that site.
Really don't know what else I can tell you or give to you. Try posting to Lost101's site where you download the stock rom from - he has been very helpful to many.
Don't give up ... and don't go off half cocked trying different things before getting some additional input.
You will get there and learn a lot in the process.
Cheers,
S.
Good luck
sdembiske said:
I'm scratching my head Afred56, not pulling out my hair as I'm sure you must be now. Thanks for asking.
Are you still able to ... get into TWRP using the command you used that worked (Note: if it wasn't it should be renamed to recovery.img)? If not, reinstall it.
For root: download Chainfire's SuperSu from here: https://download.chainfire.eu/696/supersu/ push it to your sd card or copy it over if you can and then install the zip. You can follow the directions from here: http://www.theandroidsoul.com/how-to-flash-supersu-using-twrp-recovery-and-root-any-android-device/
I would use first: Retail EU 5.1 ROM (Untouched) (543mb) [Download] (Partially 'Stagefright' Patched) from: https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t31428
Then, follow this:
How to flash:
1) Boot into latest TWRP and Format Data (Wipe > Format DATA > Yes) - This step is essential, and will wipe Internal Storage (Downloads, Music, Photos etc, **backup important files**)
2) Transfer ROM to SDCARD or Internal Storage. This may be done in Windows via MTP, or using adb sideload or adb push ROM.zip /sdcard/
3) TWRP > Wipe > Factory reset and flash ROM.
4) Reboot.
5) Call / WiFi issues can be solved by flashing 5.1 Radio Firmware (Below) for your Model.
Then: Flash(install) via TWRP from the same site
Updated Google Dialer
XT1039 Stock 5.1 Dialer | Messenger (Clear Dalvik Cache after flashing)
Full Stagefright Patch (Dec 2015) - [Download]
As well as flash 5.1 Radio Firmware for your Model from that site.
Really don't know what else I can tell you or give to you. Try posting to Lost101's site where you download the stock rom from - he has been very helpful to many.
Don't give up ... and don't go off half cocked trying different things before getting some additional input.
You will get there and learn a lot in the process.
Cheers,
S.
Good luck
Click to expand...
Click to collapse
I can still:
boot directly into twrp
wipe completely (Dalvik cache, Cache, Data, Internal storage, system)
adb push XT1039_Retail_EU_51_Untouched_Stagefright_Patched.zip /sdcard1/
TWRP Install /sdcard1/XT1039_Retail_EU_51_Untouched_Stagefright_Patched.zip
Phone screen:
Updating partition details
...done
Full SELinux support is present
MTP Enabled
Installing zip file 'sdcard1/XT1039_Retail_EU_51_Untouched_Stagefright_Patched.zip'
Checking For MD5 file...
Skipping MD5 check: no MD5 file found
>>> XT1039 Retail Europe 5.1 Stock ROM (Untouched) <<<
Installing Android
Please wait...
Flashing Kernel...
Finished!
script succeded: result was [1.000000]
Updating partition details...
...done
Reboot
Motorola Logo, then black screen
I will try now with supersu as well
Read the instructions ... carefully!
alfred56 said:
I can still:
boot directly into twrp
wipe completely (Dalvik cache, Cache, Data, Internal storage, system)
adb push XT1039_Retail_EU_51_Untouched_Stagefright_Patched.zip /sdcard1/
TWRP Install /sdcard1/XT1039_Retail_EU_51_Untouched_Stagefright_Patched.zip
Phone screen:
Updating partition details
...done
Full SELinux support is present
MTP Enabled
Installing zip file 'sdcard1/XT1039_Retail_EU_51_Untouched_Stagefright_Patched.zip'
Checking For MD5 file...
Skipping MD5 check: no MD5 file found
>>> XT1039 Retail Europe 5.1 Stock ROM (Untouched) <<<
Installing Android
Please wait...
Flashing Kernel...
Finished!
script succeded: result was [1.000000]
Updating partition details...
...done
Reboot
Motorola Logo, then black screen
I will try now with supersu as well
Click to expand...
Click to collapse
Read the instructions ... carefully!
Boot into latest TWRP and Format Data (Wipe > Format DATA > Yes) - This step is essential
Couple of further thoughts ...
Couple of further thoughts ...
- When you turn your phone off completely and just plug it in to charge, do you get the battery icon on the screen to show it charging? I'm wondering if you can charge the battery fully or whether it could be dead or almost dead.
- do you know your carrier that the phone was originally from? If so, find the CID out for that carrier (try googling it) and then try and get a stock rom with that particular CID and try flashing it.
- have you tried holdng down the power button firmly until it shuts down and starts to reboot, all without releasing the power button? Not sure if it might work but others have suggested it as well as removing the back cover off in some way (I've never done it but understand it can be done), removing the battery and then re-installing it).
- other things that have been suggested: https://forum.xda-developers.com/showthread.php?t=2607327
I also had this same problem with my moto G .
I deleted the cache and the user data and then re-entered the system. (There were a few minutes, you might want to wait)
fastreboot erase cache
fastreboot erase userdata
fastreboot reboot
and/or as well:
fastboot erase cache
fastboot erase userdata
fastboot reboot
Other than that, I'm not sure what the issue is, but it does seem like a software issue and not a hardware issue, since you can see TWRP recovery, etc.
S.
sdembiske said:
Couple of further thoughts ...
- When you turn your phone off completely and just plug it in to charge, do you get the battery icon on the screen to show it charging? I'm wondering if you can charge the battery fully or whether it could be dead or almost dead.
- do you know your carrier that the phone was originally from? If so, find the CID out for that carrier (try googling it) and then try and get a stock rom with that particular CID and try flashing it.
- have you tried holdng down the power button firmly until it shuts down and starts to reboot, all without releasing the power button? Not sure if it might work but others have suggested it as well as removing the back cover off in some way (I've never done it but understand it can be done), removing the battery and then re-installing it).
- other things that have been suggested: https://forum.xda-developers.com/showthread.php?t=2607327
I also had this same problem with my moto G .
I deleted the cache and the user data and then re-entered the system. (There were a few minutes, you might want to wait)
fastreboot erase cache
fastreboot erase userdata
fastreboot reboot
and/or as well:
fastboot erase cache
fastboot erase userdata
fastboot reboot
Other than that, I'm not sure what the issue is, but it does seem like a software issue and not a hardware issue, since you can see TWRP recovery, etc.
S.
Click to expand...
Click to collapse
Hi Mate,
I already performed those suggested commands, opened the phone, disconnected the battery for a minute.
It does charge with the charger and it shows 100% charged.
My mobile is an outright purchase, it is not linked to any carrier. In Australia you can buy outright phone, not with a carrier customized rom.
Tried different roms without success using twrp, adb sideload and fastboot/mboot.
With fastboot all the commands report ok. With TWRP I get an error 7 and error 255 with certain roms.
I believe my ROM is XT1039 Peregrine 23 17.6-1.
Anyway does not matter how much and wipe this unit, there are always remnants in my internal storage that will not erase.
I can flash all kind of ROMS into it and there are still files there that cannot be deleted, IE /sdcard/DCIM/Camera photos and videos.
I ran these commands using the adb shell:
C:\android\platform-tools>adb shell ls -lh /sdcard/
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxrwxr-x 5 media_rw media_rw 4.0K Jul 21 22:11 Android
drwxrwxr-x 4 media_rw media_rw 4.0K Feb 10 2017 DCIM
drwxrwxr-x 2 media_rw media_rw 4.0K Dec 25 08:09 Download
drwxrwxr-x 2 media_rw media_rw 4.0K Jun 19 2016 Notifications
drwxrwxr-x 2 media_rw media_rw 4.0K Dec 25 08:47 Pictures
drwxrwxr-x 2 media_rw media_rw 4.0K Dec 5 2015 Ringtones
drwxrwxr-x 6 media_rw media_rw 4.0K Feb 11 2017 WhatsApp
drwxrwxr-x 4 media_rw media_rw 4.0K Nov 6 18:35 __chartboost
drwxrwxr-x 3 media_rw media_rw 4.0K Feb 9 2016 com.facebook.katana
drwxrwxr-x 3 media_rw media_rw 4.0K Dec 29 2015 com.facebook.orca
drwxrwxr-x 3 media_rw media_rw 4.0K Dec 5 2015 media
drwxrwxr-x 2 media_rw media_rw 4.0K Nov 7 08:05 ubisoft
and the next to list the Camera folder:
C:\android\platform-tools>adb shell ls -lh /sdcard/DCIM/Camera
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
-rw-rw-r-- 1 media_rw media_rw 501.6K Feb 10 2017 IMG_20170210_234915911.jpg
-rw-rw-r-- 1 media_rw media_rw 511.2K Feb 10 2017 IMG_20170210_234919068.jpg
-rw-rw-r-- 1 media_rw media_rw 1.0M Feb 12 2017 IMG_20170212_201907780.jpg
-rw-rw-r-- 1 media_rw media_rw 1.0M Feb 12 2017 IMG_20170212_201914781.jpg
-rw-rw-r-- 1 media_rw media_rw 494.0K Feb 12 2017 IMG_20170212_201923163.jpg
-rw-rw-r-- 1 media_rw media_rw 494.2K Feb 12 2017 IMG_20170212_201945345.jpg
-rw-rw-r-- 1 media_rw media_rw 1.0M Feb 12 2017 IMG_20170212_202646422.jpg
-rw-rw-r-- 1 media_rw media_rw 1.1M Feb 12 2017 IMG_20170212_202719249.jpg
-rw-rw-r-- 1 media_rw media_rw 1019.5K Feb 12 2017 IMG_20170212_202746763.jpg
-rw-rw-r-- 1 media_rw media_rw 1008.2K Feb 12 2017 IMG_20170212_202801772.jpg
-rw-rw-r-- 1 media_rw media_rw 898.1K Feb 12 2017 IMG_20170212_204118155.jpg
-rw-rw-r-- 1 media_rw media_rw 1017.9K Feb 12 2017 IMG_20170212_204208307_HDR.jpg
-rw-rw-r-- 1 media_rw media_rw 905.4K Feb 12 2017 IMG_20170212_205508085.jpg
-rw-rw-r-- 1 media_rw media_rw 1.0M Feb 12 2017 IMG_20170212_205521103_HDR.jpg
-rw-rw-r-- 1 media_rw media_rw 1015.8K Feb 12 2017 IMG_20170212_205537343.jpg
-rw-rw-r-- 1 media_rw media_rw 920.8K Feb 12 2017 IMG_20170212_205552722.jpg
-rw-rw-r-- 1 media_rw media_rw 1.0M Feb 13 2017 IMG_20170213_194653469.jpg
-rw-rw-r-- 1 media_rw media_rw 458.8K Feb 14 2017 IMG_20170214_181302706.jpg
-rw-rw-r-- 1 media_rw media_rw 946.8K Feb 14 2017 IMG_20170214_191408430.jpg
-rw-rw-r-- 1 media_rw media_rw 1.0M Feb 14 2017 IMG_20170214_191411961.jpg
-rw-rw-r-- 1 media_rw media_rw 1003.3K Feb 14 2017 IMG_20170214_191414674.jpg
-rw-rw-r-- 1 media_rw media_rw 956.0K Feb 14 2017 IMG_20170214_225001191.jpg
-rw-rw-r-- 1 media_rw media_rw 995.0K Feb 14 2017 IMG_20170214_225031857.jpg
-rw-rw-r-- 1 media_rw media_rw 1018.9K Feb 14 2017 IMG_20170214_225035253.jpg
-rw-rw-r-- 1 media_rw media_rw 998.5K Feb 14 2017 IMG_20170214_225037915.jpg
-rw-rw-r-- 1 media_rw media_rw 596.2K Mar 10 2017 IMG_20170310_133924792.jpg
-rw-rw-r-- 1 media_rw media_rw 543.4K Mar 10 2017 IMG_20170310_133926974.jpg
-rw-rw-r-- 1 media_rw media_rw 1.1M Mar 10 2017 IMG_20170310_153628688.jpg
-rw-rw-r-- 1 media_rw media_rw 1.1M Mar 10 2017 IMG_20170310_153654589.jpg
-rw-rw-r-- 1 media_rw media_rw 946.6K Mar 18 2017 IMG_20170318_110314854.jpg
-rw-rw-r-- 1 media_rw media_rw 899.4K Mar 18 2017 IMG_20170318_110342489.jpg
-rw-rw-r-- 1 media_rw media_rw 768.3K Mar 20 2017 IMG_20170320_185756533.jpg
-rw-rw-r-- 1 media_rw media_rw 767.5K Mar 20 2017 IMG_20170320_185759446.jpg
-rw-rw-r-- 1 media_rw media_rw 1.1M Mar 28 2017 IMG_20170328_140647014.jpg
-rw-rw-r-- 1 media_rw media_rw 1002.9K Mar 28 2017 IMG_20170328_140654540.jpg
-rw-rw-r-- 1 media_rw media_rw 1.0M Mar 28 2017 IMG_20170328_140700548.jpg
-rw-rw-r-- 1 media_rw media_rw 993.5K Apr 1 2017 IMG_20170401_122744620.jpg
-rw-rw-r-- 1 media_rw media_rw 946.6K Apr 6 2017 IMG_20170406_174107216.jpg
-rw-rw-r-- 1 media_rw media_rw 846.7K Apr 6 2017 IMG_20170406_174125309.jpg
-rw-rw-r-- 1 media_rw media_rw 857.5K Apr 6 2017 IMG_20170406_174127874.jpg
-rw-rw-r-- 1 media_rw media_rw 59.6M Feb 10 2017 VID_20170210_234829190.mp4
-rw-rw-r-- 1 media_rw media_rw 30.3M Feb 12 2017 VID_20170212_201920817.mp4
-rw-rw-r-- 1 media_rw media_rw 36.6M Feb 12 2017 VID_20170212_202604850.mp4
-rw-rw-r-- 1 media_rw media_rw 89.3M Feb 13 2017 VID_20170213_194656999.mp4
-rw-rw-r-- 1 media_rw media_rw 15.1M Feb 14 2017 VID_20170214_181250724.mp4
-rw-rw-r-- 1 media_rw media_rw 43.8M Feb 14 2017 VID_20170214_225040708.mp4
The above files cannot be erased for some reason despit me selecting all partitions using TWRP WIPE Advanced, followed with a format.
Regards
Alfred56
alfred56 said:
Hi Mate,
I already performed those suggested commands, opened the phone, disconnected the battery for a minute.
It does charge with the charger and it shows 100% charged.
My mobile is an outright purchase, it is not linked to any carrier. In Australia you can buy outright phone, not with a carrier customized rom.
Tried different roms without success using twrp, adb sideload and fastboot/mboot.
With fastboot all the commands report ok. With TWRP I get an error 7 and error 255 with certain roms.
I believe my ROM is XT1039 Peregrine 23 17.6-1.
Anyway does not matter how much and wipe this unit, there are always remnants in my internal storage that will not erase.
I can flash all kind of ROMS into it and there are still files there that cannot be deleted, IE /sdcard/DCIM/Camera photos and videos.
I ran these commands using the adb shell:
C:\android\platform-tools>adb shell ls -lh /sdcard/
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxrwxr-x 5 media_rw media_rw 4.0K Jul 21 22:11 Android
drwxrwxr-x 4 media_rw media_rw 4.0K Feb 10 2017 DCIM
drwxrwxr-x 2 media_rw media_rw 4.0K Dec 25 08:09 Download
drwxrwxr-x 2 media_rw media_rw 4.0K Jun 19 2016 Notifications
drwxrwxr-x 2 media_rw media_rw 4.0K Dec 25 08:47 Pictures
drwxrwxr-x 2 media_rw media_rw 4.0K Dec 5 2015 Ringtones
drwxrwxr-x 6 media_rw media_rw 4.0K Feb 11 2017 WhatsApp
drwxrwxr-x 4 media_rw media_rw 4.0K Nov 6 18:35 __chartboost
drwxrwxr-x 3 media_rw media_rw 4.0K Feb 9 2016 com.facebook.katana
drwxrwxr-x 3 media_rw media_rw 4.0K Dec 29 2015 com.facebook.orca
drwxrwxr-x 3 media_rw media_rw 4.0K Dec 5 2015 media
drwxrwxr-x 2 media_rw media_rw 4.0K Nov 7 08:05 ubisoft
and the next to list the Camera folder:
C:\android\platform-tools>adb shell ls -lh /sdcard/DCIM/Camera
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
-rw-rw-r-- 1 media_rw media_rw 501.6K Feb 10 2017 IMG_20170210_234915911.jpg
-rw-rw-r-- 1 media_rw media_rw 511.2K Feb 10 2017 IMG_20170210_234919068.jpg
-rw-rw-r-- 1 media_rw media_rw 1.0M Feb 12 2017 IMG_20170212_201907780.jpg
-rw-rw-r-- 1 media_rw media_rw 1.0M Feb 12 2017 IMG_20170212_201914781.jpg
-rw-rw-r-- 1 media_rw media_rw 494.0K Feb 12 2017 IMG_20170212_201923163.jpg
-rw-rw-r-- 1 media_rw media_rw 494.2K Feb 12 2017 IMG_20170212_201945345.jpg
-rw-rw-r-- 1 media_rw media_rw 1.0M Feb 12 2017 IMG_20170212_202646422.jpg
-rw-rw-r-- 1 media_rw media_rw 1.1M Feb 12 2017 IMG_20170212_202719249.jpg
-rw-rw-r-- 1 media_rw media_rw 1019.5K Feb 12 2017 IMG_20170212_202746763.jpg
-rw-rw-r-- 1 media_rw media_rw 1008.2K Feb 12 2017 IMG_20170212_202801772.jpg
-rw-rw-r-- 1 media_rw media_rw 898.1K Feb 12 2017 IMG_20170212_204118155.jpg
-rw-rw-r-- 1 media_rw media_rw 1017.9K Feb 12 2017 IMG_20170212_204208307_HDR.jpg
-rw-rw-r-- 1 media_rw media_rw 905.4K Feb 12 2017 IMG_20170212_205508085.jpg
-rw-rw-r-- 1 media_rw media_rw 1.0M Feb 12 2017 IMG_20170212_205521103_HDR.jpg
-rw-rw-r-- 1 media_rw media_rw 1015.8K Feb 12 2017 IMG_20170212_205537343.jpg
-rw-rw-r-- 1 media_rw media_rw 920.8K Feb 12 2017 IMG_20170212_205552722.jpg
-rw-rw-r-- 1 media_rw media_rw 1.0M Feb 13 2017 IMG_20170213_194653469.jpg
-rw-rw-r-- 1 media_rw media_rw 458.8K Feb 14 2017 IMG_20170214_181302706.jpg
-rw-rw-r-- 1 media_rw media_rw 946.8K Feb 14 2017 IMG_20170214_191408430.jpg
-rw-rw-r-- 1 media_rw media_rw 1.0M Feb 14 2017 IMG_20170214_191411961.jpg
-rw-rw-r-- 1 media_rw media_rw 1003.3K Feb 14 2017 IMG_20170214_191414674.jpg
-rw-rw-r-- 1 media_rw media_rw 956.0K Feb 14 2017 IMG_20170214_225001191.jpg
-rw-rw-r-- 1 media_rw media_rw 995.0K Feb 14 2017 IMG_20170214_225031857.jpg
-rw-rw-r-- 1 media_rw media_rw 1018.9K Feb 14 2017 IMG_20170214_225035253.jpg
-rw-rw-r-- 1 media_rw media_rw 998.5K Feb 14 2017 IMG_20170214_225037915.jpg
-rw-rw-r-- 1 media_rw media_rw 596.2K Mar 10 2017 IMG_20170310_133924792.jpg
-rw-rw-r-- 1 media_rw media_rw 543.4K Mar 10 2017 IMG_20170310_133926974.jpg
-rw-rw-r-- 1 media_rw media_rw 1.1M Mar 10 2017 IMG_20170310_153628688.jpg
-rw-rw-r-- 1 media_rw media_rw 1.1M Mar 10 2017 IMG_20170310_153654589.jpg
-rw-rw-r-- 1 media_rw media_rw 946.6K Mar 18 2017 IMG_20170318_110314854.jpg
-rw-rw-r-- 1 media_rw media_rw 899.4K Mar 18 2017 IMG_20170318_110342489.jpg
-rw-rw-r-- 1 media_rw media_rw 768.3K Mar 20 2017 IMG_20170320_185756533.jpg
-rw-rw-r-- 1 media_rw media_rw 767.5K Mar 20 2017 IMG_20170320_185759446.jpg
-rw-rw-r-- 1 media_rw media_rw 1.1M Mar 28 2017 IMG_20170328_140647014.jpg
-rw-rw-r-- 1 media_rw media_rw 1002.9K Mar 28 2017 IMG_20170328_140654540.jpg
-rw-rw-r-- 1 media_rw media_rw 1.0M Mar 28 2017 IMG_20170328_140700548.jpg
-rw-rw-r-- 1 media_rw media_rw 993.5K Apr 1 2017 IMG_20170401_122744620.jpg
-rw-rw-r-- 1 media_rw media_rw 946.6K Apr 6 2017 IMG_20170406_174107216.jpg
-rw-rw-r-- 1 media_rw media_rw 846.7K Apr 6 2017 IMG_20170406_174125309.jpg
-rw-rw-r-- 1 media_rw media_rw 857.5K Apr 6 2017 IMG_20170406_174127874.jpg
-rw-rw-r-- 1 media_rw media_rw 59.6M Feb 10 2017 VID_20170210_234829190.mp4
-rw-rw-r-- 1 media_rw media_rw 30.3M Feb 12 2017 VID_20170212_201920817.mp4
-rw-rw-r-- 1 media_rw media_rw 36.6M Feb 12 2017 VID_20170212_202604850.mp4
-rw-rw-r-- 1 media_rw media_rw 89.3M Feb 13 2017 VID_20170213_194656999.mp4
-rw-rw-r-- 1 media_rw media_rw 15.1M Feb 14 2017 VID_20170214_181250724.mp4
-rw-rw-r-- 1 media_rw media_rw 43.8M Feb 14 2017 VID_20170214_225040708.mp4
The above files cannot be erased for some reason despit me selecting all partitions using TWRP WIPE Advanced, followed with a format.
Regards
Alfred56
Click to expand...
Click to collapse
In the Wipe screen in TWRP, you have clicked on Format Data on the right lower side?
In the Mount screen in TWRP have you ticked all partitions? Try it, please, system in particular - don't worry if a tick won't hold in USB OTG.
- Have you clicked on Fix Contents in the Advanced Tap in TWRP? Do it in a final try.
That's all I got - sorry if you are not able to get up & running
I'm out of ideas but hopefully someone can find a solution for you. That's it for me, sorry.
Cheers and Best of Luck,
S.
sdembiske said:
In the Wipe screen in TWRP, you have clicked on Format Data on the right lower side?
In the Mount screen in TWRP have you ticked all partitions? Try it, please, system in particular - don't worry if a tick won't hold in USB OTG.
- Have you clicked on Fix Contents in the Advanced Tap in TWRP? Do it in a final try.
That's all I got - sorry if you are not able to get up & running
I'm out of ideas but hopefully someone can find a solution for you. That's it for me, sorry.
Cheers and Best of Luck,
S.
Click to expand...
Click to collapse
Shouldn't you be able to delete user files without TWRP? I mean, unless the hard drive is corrupt or something?
You can first try the
Code:
wipefs -a [partition]
command
From the man pages:
wipefs can erase filesystem, raid or partition-table signatures (magic strings) from the specified device to make the signatures invisible for libblkid.
wipefs does not erase the filesystem itself nor any other data from the device. When used without any options, wipefs lists all visible filesystems and the offsets of their basic signatures.
wipefs calls the BLKRRPART ioctl when it has erased a partition-table signature to inform the kernel about the change.
Then try a full format of the hard disk.