Related
ok, so i'm trying to put a bootanimation and the trackball succession mod on my phone.
i downloaded the files, renamed them, put them in my tools folder and opened the command window. typed adb remount, that worked. typed adb devices, my phone is there so that worked. and when i type adb push and the whole file name and what not it says cannot stat no such file or directory.
so i tried putting it on the root of my c drive and doing it that way and it still wouldn't work.
any suggestions or anyone know what's going on here??
Copy/paste out the entire adb session. Include a dir listing of the folder you are presently in as well.
i'm sorry, but i'm kind of new to all of this, so i'm not sure how to include the dir listing of the folder
but here's the session
C:\Users\SubyWIll\Desktop\android\tools>adb remount
remount succeeded
C:\Users\SubyWIll\Desktop\android\tools>adb devices
List of devices attached
HT9CSP818771 device
C:\Users\SubyWIll\Desktop\android\tools>adb push bootanimation.zip /data/local
cannot stat 'bootanimation.zip': No such file or directory
C:\Users\SubyWIll\Desktop\android\tools>
can you provide a dir listing of your tools folder?
You can simply just:
dir > toolsdir.txt
then copy/paste the results.
ah, i think i got it now.
Volume in drive C has no label.
Volume Serial Number is EC86-7915
Directory of C:\Users\SubyWIll\Desktop\android\tools
03/18/2010 03:19 PM <DIR> .
03/18/2010 03:19 PM <DIR> ..
02/05/2010 06:22 PM 43,684 acp.exe
02/05/2010 06:22 PM 2,530,671 adb.exe
02/05/2010 06:22 PM 96,256 AdbWinApi.dll
02/05/2010 06:22 PM 60,928 AdbWinUsbApi.dll
02/05/2010 06:23 PM 3,394 android.bat
02/05/2010 06:23 PM 1,565 apkbuilder.bat
03/18/2010 01:47 PM 1,704,320 bootanimation.zip.zip
02/05/2010 06:23 PM 2,129 ddms.bat
02/05/2010 06:22 PM 128,177 dmtracedump.exe
02/05/2010 06:23 PM 1,491 draw9patch.bat
02/05/2010 06:22 PM 10,897,908 emulator.exe
02/05/2010 06:22 PM 493,759 etc1tool.exe
02/05/2010 06:22 PM 994,279 fastboot.exe
02/05/2010 06:23 PM 1,528 hierarchyviewer.bat
02/05/2010 06:22 PM 30,963 hprof-conv.exe
02/05/2010 06:23 PM <DIR> Jet
02/05/2010 06:23 PM 1,680 layoutopt.bat
02/05/2010 06:22 PM <DIR> lib
02/05/2010 06:22 PM 86,528 mgwz.dll
02/05/2010 06:22 PM 29,498 mksdcard.exe
02/05/2010 02:53 PM 203,735 NOTICE.txt
03/16/2010 05:37 PM 4,048,896 recovery.img
03/18/2010 02:19 PM 504,467 services.jar.zip
02/05/2010 02:53 PM 33 source.properties
02/05/2010 06:22 PM 1,696,645 sqlite3.exe
03/18/2010 03:20 PM 0 toolsdir.txt
02/05/2010 06:23 PM 1,982 traceview.bat
02/05/2010 06:22 PM 1,447,375 zipalign.exe
26 File(s) 25,011,891 bytes
4 Dir(s) 50,512,666,624 bytes free
is that what you need?
remove the last .zip from bootanimation.zip.zip and try again
or adb push bootanimation.zip.zip /data/local/bootanimation.zip
For best practices, I recommend removing the trailing .zip.
deprecate said:
remove the last .zip from bootanimation.zip.zip and try again
or adb push bootanimation.zip.zip /data/local/bootanimation.zip
For best practices, I recommend removing the trailing .zip.
Click to expand...
Click to collapse
haha i just noticed that, but why did it add a .zip to the end? i just added one .zip when i renamed it lol. i'm a little confused on how to remove the last .zip though lol
SubyWill said:
haha i just noticed that, but why did it add a .zip to the end? i just added one .zip when i renamed it lol. i'm a little confused on how to remove the last .zip though lol
Click to expand...
Click to collapse
My guess.
you have "hide file extensions" enabled in windows explorer so when you added a zip to the file, it simply tacked it onto the name which contained the .zip already.
To remove the zip, simple right click, rename, and move the cursor to where you can delete the last 4 chars (.zip).
deprecate said:
My guess.
you have "hide file extensions" enabled in windows explorer so when you added a zip to the file, it simply tacked it onto the name which contained the .zip already.
To remove the zip, simple right click, rename, and move the cursor to where you can delete the last 4 chars (.zip).
Click to expand...
Click to collapse
ahh i figured it all out, thanks man! i appreciate the help!
SubyWill said:
ahh i figured it all out, thanks man! i appreciate the help!
Click to expand...
Click to collapse
No worries. Glad you got it sorted out
Hello,
I have an issue on my Galaxy S I-9000
I have CM10 (nigthly 3 Dec)
My problem is when phone starts (reboot, power on, reset) my phone does not ask me to enter PIN number.
Consequently I don't have network access.
The only way to get this is to connect few seconds my phone to USB cable to my laptop.
I do nothing more than connect it (I don't press OK to accept USB connexion), only wait few seconds.
Then I type my code PIN, everything works perfect!
The problem is always when I restart, reset my phone... I need my USB cable to get the Enter PIN window...!
Note that my SIM card works very well in the Nexus phone of my wife.
Her SIM card has the same problem than my mine in my Galaxy S...
I tried several times. It works only in official release Gingerbread, but not with CM10.
I updated Modem to radio-cm7-BUJV5-signed.zip (my operator is SFR), same result...!
Does any one can help me to solve my problem?
New inputs
Hello,
Here is new input: I noted that it is not USB connection with PC activating the "Enter PIN" windows and network but it is USB power presence on USB connector. When I connect only my battery charger on USB connector after few seconds I've got the "Enter PIN" !!!
Anyway this does not solve the issue... but it is easier to manage
I've checked my efs folder:
Code:
Directory of E:\DATA\_PERSONNEL_\GalaxySFR\CM10\efs\efs
04/12/2012 17:16 <DIR> .
04/12/2012 17:16 <DIR> ..
04/12/2012 17:16 <DIR> .android
03/12/2012 16:33 1 048 576 .nv2.bak
03/12/2012 16:33 32 .nv2.bak.md5
03/12/2012 16:33 2 097 152 .nv_data.bak
03/12/2012 16:33 32 .nv_data.bak.md5
03/12/2012 16:33 1 .nv_state
03/12/2012 16:33 8 cryptprop_applied_result
03/12/2012 16:33 4 cryptprop_onetimeboot
03/12/2012 16:33 2 cryptprop_securewipedata
04/12/2012 17:16 <DIR> imei
04/12/2012 17:16 <DIR> lost+found
04/12/2012 17:10 2 097 152 nv_data.bin
04/12/2012 17:10 32 nv_data.bin.md5
03/12/2012 16:33 0 updated_filesystem
11 File(s) 5 242 991 bytes
Directory of E:\DATA\_PERSONNEL_\GalaxySFR\CM10\efs\efs\.android
04/12/2012 17:16 <DIR> .
04/12/2012 17:16 <DIR> ..
0 File(s) 0 bytes
Directory of E:\DATA\_PERSONNEL_\GalaxySFR\CM10\efs\efs\imei
04/12/2012 17:16 <DIR> .
04/12/2012 17:16 <DIR> ..
0 File(s) 0 bytes
Directory of E:\DATA\_PERSONNEL_\GalaxySFR\CM10\efs\efs\lost+found
04/12/2012 17:16 <DIR> .
04/12/2012 17:16 <DIR> ..
0 File(s) 0 bytes
In addition I attached screenshots before and after PIN entered of Parameters\About the phone\
May be the efs folder is not mounted / activated after startup and for any reason the USB power connection activates it.
Does anyone can help me? Terminal command line maybe?
Regards,
\Tr€g0r
I found and read this post http://forum.xda-developers.com/showthread.php?t=1813559 but franckly speaking it is hard to follow (I'm not a native english speaker)
My problem looks like I don't have correct IMEI on startup or efs folder is not mounted, but I did not read anywhere that USB power supply can activate correctly my IMEI (if I type #06# my number starting by 3544060... is displayed).
Please I need expert support to understand my issue and get a fix :good:
Thank you very much
no expert?
EFS
You need your EFS data / IMEI.
Flash an original ROM via Odin - this should reestablish your /EFS data
Then take a backup of your EFS data (I think you need to root your device first)
EFS data is in the root folder: emmc/modem/efs
Have a copy on your SD card or computer so that you anytime can restore these data (includes your IMEI number)
- and thereafter you may install CyanogenMod again ...
Good luck
Chipsi said:
You need your EFS data / IMEI.
Flash an original ROM via Odin - this should reestablish your /EFS data
Then take a backup of your EFS data (I think you need to root your device first)
EFS data is in the root folder: emmc/modem/efs
Have a copy on your SD card or computer so that you anytime can restore these data (includes your IMEI number)
- and thereafter you may install CyanogenMod again ...
Good luck
Click to expand...
Click to collapse
THANK YOU to answer me!
Just to be sure I correctly understand what you wrote:
1/ With odin I flash original ROM: I have a JV4_JV4_JV4.tar (289Mo: 303*565*312 bytes). Is it OK? Do I need to repartition (pit 512)?
2/ Then I need to root it: I have CF-Root-XX_OXA_JW4-v4.4-CWM3RFS.tar (7Mo: 7*383*040 bytes). Is it OK?
3/ Then I need to save efs folder (for instance with SGS tool box on Play store)
4/ Install CyanogenMod 10 again
5/ Wait and see...!
Correct?
I have a similar problem, but only when installing KB3 modem.
The phone asks for the PIN, but nothing happens. It seems that the SIM is blocked.
No problem by flashing JVU or JW4, and with the stock one.
Any ideas?
Yesterday I upgraded to JB, everything was fine until I got the idea how to reset the odin counter with terminal emulator.
I rebooted and then came back the wizard and it was in Russian, if I tried to do it crashed.
The baseband has been lost (although I have recovered)
NOW
If I try to flash jb or any other rom:
--Copyng media file:
E:Failed to mount /efs (Invalid argument)
--Appling multi csc
e: failed to mount /efs (Invalid argument)
e: multi_csc:Can't mount /efs
Click to expand...
Click to collapse
my phone displays the name and imei no problems, the baseband I recovered by flashing the stock rom samsung
I have a backup of EFS folder
(I had done it long ago with root explorer, just that I did not make a binary copy but a tar archive)
but even if you put it back with root explorer disappears and returns a folder with a lot less efs file
Content of my TAR backup of /efs
Il volume nell'unit… D Š Doc - Prog
Numero di serie del volume: 86DA-7FA3
Directory di D:\Administrator\Desktop\efs
14/02/2013 02:15 <DIR> .
14/02/2013 02:15 <DIR> ..
14/02/2013 02:12 <DIR> .files
31/12/2011 16:00 1 .nv_state
14/02/2013 02:12 <DIR> bluetooth
20/11/2012 14:01 6 calibration_data
01/01/2012 01:05 9 cryptprop_applied_result
03/01/2013 17:40 10 cryptprop_lockscreen.lockoutattemptdeadline
03/01/2013 17:52 6 cryptprop_lockscreen.password_type
03/01/2013 16:59 5 cryptprop_lockscreen.patterneverchosen
03/01/2013 17:52 6 cryptprop_lock_pattern_autolock
03/01/2013 16:59 5 cryptprop_lock_pattern_tactile_feedback_enabled
03/01/2013 16:59 5 cryptprop_lock_pattern_visible_pattern
13/01/2013 00:37 5 cryptprop_onetimeboot
01/01/2012 01:06 3 cryptprop_persist.sys.language
04/01/2013 12:46 12 cryptprop_persist.sys.timezone
01/01/2012 01:00 1 cryptprop_rebootMode
13/01/2013 00:37 3 cryptprop_securewipedata
14/02/2013 02:12 <DIR> dmp
01/01/2012 01:01 1 essiv
14/02/2013 02:12 <DIR> FactoryApp
10/08/2012 17:57 0 GUARDFIL
14/02/2013 02:12 <DIR> imei
14/02/2013 02:15 0 lista.txr
31/12/2011 16:00 217 nv.log
31/12/2011 16:00 0 nv_data.bin.md5
14/02/2013 02:12 <DIR> RFHAL
14/02/2013 02:12 <DIR> RFHAL.DEF
14/02/2013 02:12 <DIR> wifi
19 File 295 byte
10 Directory 239.271.510.016 byte disponibili
Click to expand...
Click to collapse
How can i fix it?
UP =(
KiraHack said:
UP =(
Click to expand...
Click to collapse
up
Up
Одг: e: failed to mount /efs (Invalid argument)
KiraHack said:
Up
Click to expand...
Click to collapse
Maybe you should flash it with Odin, but I am not sure. And if somebody know he will already answer you.
Sent from Galaxy S Advance
Try to mount efs partition as rw and ext4 type, then try to extract your backup again
Sent from my GT-I9070 using xda app-developers app
frapeti said:
Try to mount efs partition as rw and ext4 type, then try to extract your backup again
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
The partition can not be mount =(
There's a lot of people out there with bricked KFHD 2013 (the newest Fire HD), with a lot of them requesting for the stock system images for this device. Unfortunately, no one has done so yet. However, if you have this device, and are rooted, you can help. To create these images, connect to a PC via ADB and enter these commands:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0p10 of=/data/local/backup/stock-boot.img"
adb shell su -c "dd if=/dev/block/mmcblk0p11 of=/data/local/backup/stock-system.img"
adb pull "/data/local/backup/stock-recovery.img"
adb pull "/data/local/backup/stock-boot.img".
adb pull "/data/local/backup/stock-system.img""
If someone could upload these somewhere and provide the download link it would be greatly appreciated.
Ph0enix_216 said:
There's a lot of people out there with bricked KFHD 2013 (the newest Fire HD), with a lot of them requesting for the stock system images for this device. Unfortunately, no one has done so yet. However, if you have this device, and are rooted, you can help. To create these images, connect to a PC via ADB and enter these commands:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0p10 of=/data/local/backup/stock-boot.img"
adb shell su -c "dd if=/dev/block/mmcblk0p11 of=/data/local/backup/stock-system.img"
adb pull "/data/local/backup/stock-recovery.img"
adb pull "/data/local/backup/stock-boot.img".
adb pull "/data/local/backup/stock-system.img""
If someone could upload these somewhere and provide the download link it would be greatly appreciated.
Click to expand...
Click to collapse
*clapping*
About time someone posted this, i was thinking of doing it myself soon. Hopefully someone will pull their images and maybe, just maybe they will get added to kffa.
stunts513 said:
*clapping*
About time someone posted this, i was thinking of doing it myself soon. Hopefully someone will pull their images and maybe, just maybe they will get added to kffa.
Click to expand...
Click to collapse
There are so many threads for bricks posted in the Q&A section that it's seriously disorienting. My mom's got the Fire HD 2013, but I've been told that tinkering with it is a major no-no .
Assuming someone can pull the system images off the Fire HD 2013, then this script here should work on it as well.
Nobody wants to help?
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a rooted Kindle Fire HD running CyanogenMod 11<<<
I'll do it, I have adb setup but am getting an error entering the first command in. Do I have to have the device rooted for this to work?
Error is "su: not found"
su makes me think I need to root it...
Lol, yeah it needs to be rooted.
Sent from my KFHD running CM11
Ok I've rooted, now getting different error. I'll see what I can do to work through it.
C:\android-sdk\platform-tools>adb shell su -c "dd if=/dev/block/mmcblk0p10 of=/data/local/backup/stock-boot.img"
/data/local/backup/stock-boot.img: cannot open for write: No such file or directory
---------- Post added at 10:14 PM ---------- Previous post was at 10:10 PM ----------
Got past that error as well, just had to create the /data/local/backup directory
I've entered the first command in and I'm waiting... not sure if it locked up or if it should take a while to run.
---------- Post added at 10:16 PM ---------- Previous post was at 10:14 PM ----------
And of course right when I post it finishes. I'm running the second command, but are we missing on command to create the stock-recovery.img file?
---------- Post added at 10:39 PM ---------- Previous post was at 10:16 PM ----------
Ok I don't really know what I'm doing but I did some quick reading about partitions so that I could grab the recovery and I found the command that lists the data I think we want. So this is the layout on my kindle.
[email protected]:/dev/block/platform/omap_hsmmc.1/by-name # ll
ll
lrwxrwxrwx root root 2014-02-17 21:42 boot -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-02-17 21:42 bootloader -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-02-17 21:42 cache -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-02-17 21:42 crypto -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-02-17 21:42 efs -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-02-17 21:42 idme -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-02-17 21:42 misc -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-02-17 21:42 recovery -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-02-17 21:42 system -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-02-17 21:42 userdata -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-02-17 21:42 xloader -> /dev/block/mmcblk0p1
So these are the commands that I ran.
adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/data/local/backup/stock-boot.img"
adb shell su -c "dd if=/dev/block/mmcblk0p7 of=/data/local/backup/stock-recovery.img"
adb shell su -c "dd if=/dev/block/mmcblk0p9 of=/data/local/backup/stock-system.img"
-- I had to do a chmod 644 * on the /data/local/backup/ directory so that I could pull the files.
adb pull "/data/local/backup/stock-recovery.img"
adb pull "/data/local/backup/stock-boot.img"
adb pull "/data/local/backup/stock-system.img"
I should have the files posted soon. Do we need any of the others?
---------- Post added at 11:01 PM ---------- Previous post was at 10:39 PM ----------
Here are the files.
* Removed link
---------- Post added at 11:02 PM ---------- Previous post was at 11:01 PM ----------
I'll check this thread tomorrow, hopefully I can help out with getting this device going.
Your sure your Kindle is the "KIndle Fire HD 7 2013 MODEL, right?'
davethebrave14 said:
Your sure your Kindle is the "KIndle Fire HD 7 2013 MODEL, right?'
Click to expand...
Click to collapse
I just got this as a warranty replacement from Amazon yesterday. Model on the back cover is P48WVB4. This is the add supported model, not sure if that matters.
bmasephol said:
I just got this as a warranty replacement from Amazon yesterday. Model on the back cover is P48WVB4. This is the add supported model, not sure if that matters.
Click to expand...
Click to collapse
Does it have a front mounted camera and HDMI output? Also, run the command "adb shell mount > /sdcard/mount.txt" Then pull it off your device and post it here.
Sent from my iPod touch using Tapatalk
Ph0enix_216 said:
Does it have a front mounted camera and HDMI output? Also, run the command "adb shell mount > /sdcard/mount.txt" Then pull it off your device and post it here.
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
No front camera. Only port is headphone and micro USB. I'll have to do the adb later tonight to check that.
---------- Post added at 02:50 PM ---------- Previous post was at 02:34 PM ----------
Maybe another important piece is that this is the 8gb version, not a 16gb.
bmasephol said:
No front camera. Only port is headphone and micro USB. I'll have to do the adb later tonight to check that.
---------- Post added at 02:50 PM ---------- Previous post was at 02:34 PM ----------
Maybe another important piece is that this is the 8gb version, not a 16gb.
Click to expand...
Click to collapse
You definitely have the 2013 version. If you have 8GB of storage on your SD card, try to keep in mind that the total space of all three images is about 1GB (the boot and recovery ones should be pretty small, whereas the system image is pretty massive).
Sent from my iPod touch using Tapatalk
Ph0enix_216 said:
There's a lot of people out there with bricked KFHD 2013 (the newest Fire HD), with a lot of them requesting for the stock system images for this device. Unfortunately, no one has done so yet. However, if you have this device, and are rooted, you can help. To create these images, connect to a PC via ADB and enter these commands:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0p10 of=/data/local/backup/stock-boot.img"
adb shell su -c "dd if=/dev/block/mmcblk0p11 of=/data/local/backup/stock-system.img"
adb pull "/data/local/backup/stock-recovery.img"
adb pull "/data/local/backup/stock-boot.img".
adb pull "/data/local/backup/stock-system.img""
If someone could upload these somewhere and provide the download link it would be greatly appreciated.
Click to expand...
Click to collapse
Kindle Fire HD 2013 Soho:
boot0block.img 4096 kb ~ 4 mb
stock-recovery.img 8192 kb ~ 8mb
stock-boot.img 8192 kb ~ 8 mb
stock-system.img 1277952 kb ~ 1.22 gb
Uploading to server. Will post links asap.
blambo said:
Kindle Fire HD 2013 Soho:
boot0block.img 4096 kb ~ 4 mb
stock-recovery.img 8192 kb ~ 8mb
stock-boot.img 8192 kb ~ 8 mb
stock-system.img 1277952 kb ~ 1.22 gb
Uploading to server. Will post links asap.
Click to expand...
Click to collapse
Those are the exact sizes of the files inside the zip I have posted... minus the boot0block.img. Didn't pull that one. But would probably be good to have more than one source.
bmasephol said:
Those are the exact sizes of the files inside the zip I have posted... minus the boot0block.img. Didn't pull that one. But would probably be good to have more than one source.
Click to expand...
Click to collapse
Sure, exactly.
Links:
boot0block.zip img CRC = AA7AB538
stock-boot.zip img CRC = DF69BAA8
stock-recovery.zip img CRC = B95DDD44
stock-system.zip img CRC = CA6A9595
Please check your CRCs.
Good luck with it.
blambo said:
Sure, exactly.
Links:
boot0block.zip img CRC = AA7AB538
stock-boot.zip img CRC = DF69BAA8
stock-recovery.zip img CRC = B95DDD44
stock-system.zip img CRC = CA6A9595
Please check your CRCs.
Good luck with it.
Click to expand...
Click to collapse
Thank you, kind sir!
Sent from my iPod touch using Tapatalk
blambo said:
Sure, exactly.
Links:
boot0block.zip img CRC = AA7AB538
stock-boot.zip img CRC = DF69BAA8
stock-recovery.zip img CRC = B95DDD44
stock-system.zip img CRC = CA6A9595
Please check your CRCs.
Good luck with it.
Click to expand...
Click to collapse
how can I use the images on my kindle I get a red flash then it goes straight to fastboot im of the understanding that the images may fix my kindle can someone explain how I would go about using them thanks
Um just thought i'd add I wouldn't post your boot0block, it contains things like your serial number, device I'd to kindle market(used for blacklisting), mac address, etc), its kinda personal info, its like whenever someone dumps their nvram they always erase their imei out of it so no one can jack their imei.
Sent from my Amazon Kindle Fire HD using Tapatalk
blambo said:
Sure, exactly.
Links:
boot0block.zip img CRC = AA7AB538
stock-boot.zip img CRC = DF69BAA8
stock-recovery.zip img CRC = B95DDD44
stock-system.zip img CRC = CA6A9595
Please check your CRCs.
Good luck with it.
Click to expand...
Click to collapse
stunts513 said:
Um just thought i'd add I wouldn't post your boot0block, it contains things like your serial number, device I'd to kindle market(used for blacklisting), mac address, etc), its kinda personal info, its like whenever someone dumps their nvram they always erase their imei out of it so no one can jack their imei.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
True. But it's always good to back it up, as there have been a few cases (according to @Hashcode) where the boot0block has been wiped. Always good to have a backup of it handy. You just can't use someone else's to restore yours, and vice versa.
My next question is: does fastboot work for the Fire HD 2013 (soho) in the same way as the Fire HD 2012 (tate)?
Dead upon arrival.
I would have sent you mine if it wasn't rooted by amazon this very afternoon by update 11.3.2.1... going past my hosts file... probably a new push server IP.
please i cant restore my device, i was using quantum rom with ak kernel, all was ok, i let my device run out of battery, when i put it to charge i was stuck in a bootloop. i go to twrp to restore my nandroid backups, i always get error "failed" on restoring data... these backups always worked fine!! then i wipe all the usual things (dãlvik, data, cache, system, even internal storage and format data) try to flash any rom and give me error:
***formatting system***
assert failed: format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system")
E:Error executing updater binary in zip ' /sdcard1/ROM NAME.zip
i really need to resolve this, its my work and personal phone. i have external sd card with roms and backups and access to bootloader screen and twrp, but cant flash anything!!
already tried stock recovering with adb fastboot but its not recognizing phone.. (i think usb debbuging was off if that matters). also tried fix permisions, and partition sd card in twrp, it gives me error: E:Unable to locate device to partition.
anyone?
i can flash small zips, but flashing roms always get me same error. fix permissions get me E:Unable to chmod error. partition sd card give me E:Unable to locate device to partition. restoring backups gives error also. help please
CPMAGMPC said:
i can flash small zips, but flashing roms always get me same error. fix permissions get me E:Unable to chmod error. partition sd card give me E:Unable to locate device to partition. restoring backups gives error also. help please
Click to expand...
Click to collapse
I think the partitions on your phone somehow got screwed.
Reinstall Stock, either KK or Lollipop via fastboot, that will reset the partitions to their proper state.
But keep in mind, by doing so, Internal Memory is going to be erased, but no the External SD Card.
i already tried that but i cant access with fast boot, it keeps me getting device not found.. so im stuck with twrp...also wiping data is not a problem because i already wiped all internal storage
SirRhor said:
I think the partitions on your phone somehow got screwed.
Reinstall Stock, either KK or Lollipop via fastboot, that will reset the partitions to their proper state.
But keep in mind, by doing so, Internal Memory is going to be erased, but no the External SD Card.
Click to expand...
Click to collapse
CPMAGMPC said:
i already tried that but i cant access with fast boot, it keeps me getting device not found.. so im stuck with twrp...also wiping data is not a problem because i already wiped all internal storage
Click to expand...
Click to collapse
If the device is not found is most likely because the Motorola drivers are not installed correctly, or not installed at all. So check that.
Reinstall the drivers, get into the bootloader and see if the device is recognized by Windows.
EDIT: Give me 10 minutes and I will send you the links of both installers for ABD that I use.
EDIT 2: Install both of these files:
https://www.dropbox.com/s/8dvpquv805r2rxi/Motorola%20Device%20Manager.exe?dl=0
https://www.dropbox.com/s/miyw2cu21ldyuwo/UniversalADBdriver.msi?dl=0
{
"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"
}
Uninstaled all driver from windows and installed yours. problem persists,device is not found maybe usb debbuging not active on the device? i searched google and cant find an option to enable it outside the rom settings, since i cannot boot...
SirRhor said:
If the device is not found is most likely because the Motorola drivers are not installed correctly, or not installed at all. So check that.
Reinstall the drivers, get into the bootloader and see if the device is recognized by Windows.
EDIT: Give me 10 minutes and I will send you the links of both installers for ABD that I use.
EDIT 2: Install both of these files:
https://www.dropbox.com/s/8dvpquv805r2rxi/Motorola%20Device%20Manager.exe?dl=0
https://www.dropbox.com/s/miyw2cu21ldyuwo/UniversalADBdriver.msi?dl=0
Click to expand...
Click to collapse
anyone as a solution? had this amazing device for 2 months only.. it was all good, tried all sort of amazing roms on this forum and now its dead... at least for now i hope.. i dont know if it helps but everytime i boot the phone or get in bootloader mode it keeps showing me quantum LP logo, even after i flashed titan prime or hyperdrive, but that was ok for a week or so till my device went out of juice.
also when i try to flash a cm 12.1 based rom phone reboots almost at finish not give me any error, when i flash other roms i get the error. when i flash addons or kernels i get success. wierd stuff
CPMAGMPC said:
anyone as a solution? had this amazing device for 2 months only.. it was all good, tried all sort of amazing roms on this forum and now its dead... at least for now i hope.. i dont know if it helps but everytime i boot the phone or get in bootloader mode it keeps showing me quantum LP logo, even after i flashed titan prime or hyperdrive, but that was ok for a week or so till my device went out of juice.
Click to expand...
Click to collapse
So you also have this problem, the same happened here. I am experiencing the same, but it seems impossible to solve :-\
Battery drained, device shutdown and afterwards partitions messed, no write operations possible.
Is your device encrypted, too?
Did you have an app pinned when the battery drained?
Here is another one on Reddit:
https://www.reddit.com/r/MotoG/comments/331wfs/moto_g_2014_bootloop/
I suspect this user has the same problem:
http://forum.xda-developers.com/moto-g-2014/help/factory-reset-t3075587
And I described the same here:
http://forum.xda-developers.com/moto-g-2014/help/factory-reset-t3075587
BTW: I need more than 10 minutes to solve those reCAPTCHAs here - this is ridiculous, did technology already surpass us?
mine wasnt encrypted. no apps pinned. i was taking shots in camera app when device shutdown at 0%. it seems that data partition is messed up, when i try to restore backups on other partitions i get success, not if i restore data. maybe there are some commands we can insert in twrp command line to solve this mess?
cxxxx said:
So you also have this problem, the same happened here. I am experiencing the same, but it seems impossible to solve :-\
Battery drained, device shutdown and afterwards partitions messed, no write operations possible.
Is your device encrypted, too?
Did you have an app pinned when the battery drained?
Here is another one on Reddit:
https://www.reddit.com/r/MotoG/comments/331wfs/moto_g_2014_bootloop/
I suspect this user has the same problem:
http://forum.xda-developers.com/moto-g-2014/help/factory-reset-t3075587
And I described the same here:
http://forum.xda-developers.com/moto-g-2014/help/factory-reset-t3075587
BTW: I need more than 10 minutes to solve those reCAPTCHAs here - this is ridiculous, did technology already surpass us?
Click to expand...
Click to collapse
Whatever you try dont try fastboot erase all
This would destroy your phone my first gen and second gen are died out of this command :crying:
I just found a twrp I could boot directly using fastboot... I am now in TWRP... to be continued. I'll keep you informed, I want to backup now first.
For now, this is the one I finally was able to boot:
http://techerrata.com/file/twrp2/titan/openrecovery-twrp-2.8.5.0-titan.img
Some more findings:
Code:
# fastboot oem fb_mode_set
...
FAILED (remote failure)
In the flashfile.xml form stock firmware-package, this command is listed before all the flash-commands.
Another irregularity is that the device cannot be locked again:
Code:
[[email protected] ~]# fastboot oem lock
...
(bootloader) Phone is locked successfully!
(bootloader) Please flash valid signed system image now!
OKAY [ 1.020s]
finished. total time: 1.020s
[[email protected] ~]# fastboot getvar securestate
securestate: locked
finished. total time: 0.001s
[[email protected] ~]# fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.251s
[[email protected] ~]# fastboot getvar securestate
securestate: unlocked
finished. total time: 0.034s
---------- Post added at 10:49 AM ---------- Previous post was at 10:45 AM ----------
J0SH1X said:
This would destroy your phone my first gen and second gen are died out of this command :crying:
Click to expand...
Click to collapse
I already heard of it.
The symptoms we are facing seem to be very similar to what you experience after issuing this command, but it has not been run.
---------- Post added at 11:04 AM ---------- Previous post was at 10:49 AM ----------
Backup is not possible.
Mounting /data fails all the time, no valid filesystem is recognized.
When using TWRP for "advanced format" it claims to create an ext2-filesystem, but it still cannot be accessed or overwritten.
I am able to open a shell using adb, but I'm unsure how to proceed.
---------- Post added at 11:19 AM ---------- Previous post was at 11:04 AM ----------
Could someone with a working device show me the output of
Code:
parted /dev/block/mmcblk0 print
?
I'd like to compare with my partitioning:
Code:
/system # parted /dev/block/mmcblk0 print
Model: MMC SEM08G (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 67.2MB 67.1MB ext4 modem
2 67.2MB 67.8MB 524kB sbl1
3 67.8MB 67.8MB 32.8kB DDR
4 67.9MB 68.9MB 1036kB aboot
5 69.4MB 69.6MB 205kB rpm
6 69.9MB 70.4MB 410kB tz
7 70.5MB 70.5MB 32.8kB sdi
8 70.5MB 71.0MB 524kB utags
9 71.0MB 73.1MB 2097kB logs
10 73.1MB 75.5MB 2388kB padA
11 75.5MB 76.5MB 1036kB abootBackup
12 77.0MB 77.2MB 205kB rpmBackup
13 77.5MB 78.0MB 410kB tzBackup
14 78.1MB 78.1MB 32.8kB sdiBackup
15 78.1MB 78.6MB 524kB utagsBackup
16 78.6MB 79.7MB 1077kB padB
17 79.7MB 81.3MB 1573kB modemst1
18 81.3MB 82.8MB 1573kB modemst2
19 82.8MB 83.3MB 500kB hob
20 83.3MB 83.4MB 32.8kB dhob
21 83.5MB 85.1MB 1573kB ext2 fsg
22 85.1MB 85.1MB 1024B fsc
23 85.1MB 85.1MB 8192B ssd
24 85.1MB 86.1MB 1049kB sp
25 86.1MB 86.3MB 131kB cid
26 86.3MB 89.4MB 3146kB ext3 pds
27 89.4MB 93.6MB 4194kB logo
28 93.6MB 97.8MB 4194kB clogo
29 97.9MB 106MB 8389kB ext4 persist
30 106MB 107MB 524kB misc
31 107MB 117MB 10.4MB boot
32 117MB 128MB 10.5MB recovery
33 128MB 129MB 1049kB deviceinfo
34 129MB 146MB 16.8MB ext4 ftmlog
35 146MB 706MB 560MB ext4 cache
36 706MB 1863MB 1158MB ext4 system
37 1863MB 1872MB 8389kB kpan
38 1872MB 7784MB 5913MB userdata
Partitions are there, but something is wrong with userdata, there is no filesystem and I cannot create one:
Code:
/system # mkfs.ext2 /dev/block/mmcblk0p38
mkfs.ext2: lseek: Value too large for defined data type
---------- Post added at 11:24 AM ---------- Previous post was at 11:19 AM ----------
parted crashes when trying to format:
Code:
(parted) mkfs
mkfs
Warning: The existing file system will be destroyed and all data on the
partition will be lost. Do you want to continue?
Yes/No? Yes
Yes
Partition number? 38
38
File system type? [ext2]?
Error: Invalid superblock. Are you sure this is an ext2 file system?
You found a bug in GNU Parted! Here's what you have to do:
Don't panic! The bug has most likely not affected any of your data.
Help us to fix this bug by doing the following:
Check whether the bug has already been fixed by checking
the last version of GNU Parted that you can find at:
http://ftp.gnu.org/gnu/parted/
Please check this version prior to bug reporting.
If this has not been fixed yet or if you don't know how to check,
please visit the GNU Parted website:
http://www.gnu.org/software/parted
for further information.
Your report should contain the version of this release (1.8.8.1.179-aef3)
along with the error message below, the output of
parted DEVICE unit co print unit s print
and the following history of commands you entered.
Also include any additional information about your setup you
consider important.
Error: SEGV_MAPERR (Address not mapped to object)
Aborted
/system #
---------- Post added at 12:13 PM ---------- Previous post was at 11:24 AM ----------
is /cache/kernel_last_log from recovery or from system-boot?
This is interesting:
Code:
<6>[ 627.767910,2] F2FS-fs (mmcblk0p38): mounting..
<3>[ 627.903098,2] F2FS-fs (mmcblk0p38): recovery did not fully complete
<6>[ 627.903235,1] F2FS-fs (mmcblk0p38): mounted filesystem
<7>[ 627.903687,1] SELinux: initialized (dev mmcblk0p38, type f2fs), uses xattr
<6>[ 629.503418,0] EXT4-fs (mmcblk0p36): mounted filesystem with ordered data mode. Opts:
<7>[ 629.503560,0] SELinux: initialized (dev mmcblk0p36, type ext4), uses xattr
<6>[ 629.505612,0] F2FS-fs (mmcblk0p38): mounting..
<3>[ 629.638769,0] F2FS-fs (mmcblk0p38): recovery did not fully complete
<6>[ 629.638999,0] F2FS-fs (mmcblk0p38): mounted filesystem
<7>[ 629.639667,0] SELinux: initialized (dev mmcblk0p38, type f2fs), uses xattr
I also am able to write data on the partition using dd, so it is no hardware-problem. //edit: Bull****? When I dd'd the filesystem, nothing should be able to mount.
It is strange, that I can use /cache on adb shell, while fastboot says there would be an invalid partition type "raw" for /cache and /data.
---------- Post added at 12:43 PM ---------- Previous post was at 12:13 PM ----------
Code:
~ # dd if=/dev/zero of=/dev/block/mmcblk0p38 bs=8192 conv=fsync
dd: writing '/dev/block/mmcblk0p38': No space left on device
721777+0 records in
721776+0 records out
5912788992 bytes (5.5GB) copied, 501.042553 seconds, 11.3MB/s
This is so weird. This command usually destroys any single bit on a partition. "conv=fsync" makes sure that the data is actually written to the device.
The command finishes, but still kernel claims to have mounted something here when system boots:
Code:
<6>[ 629.505612,0] F2FS-fs (mmcblk0p38): mounting..
<3>[ 629.638769,0] F2FS-fs (mmcblk0p38): recovery did not fully complete
<6>[ 629.638999,0] F2FS-fs (mmcblk0p38): mounted filesystem
<7>[ 629.639667,0] SELinux: initialized (dev mmcblk0p38, type f2fs), uses xattr
---------- Post added at 01:26 PM ---------- Previous post was at 12:43 PM ----------
during formatting, dmesg is full of messages like:
Code:
<3>[ 1289.062754,0] Buffer I/O error on device mmcblk0p38, logical block 262
<4>[ 1289.062838,0] lost page write due to I/O error on mmcblk0p38
<3>[ 1289.062991,0] Buffer I/O error on device mmcblk0p38, logical block 263
<4>[ 1289.063075,0] lost page write due to I/O error on mmcblk0p38
<3>[ 1289.063233,0] end_request: I/O error, dev mmcblk0, sector 3661824
<3>[ 1289.063328,0] end_request: I/O error, dev mmcblk0, sector 3661880
Not sure if this TWRP is broken or my internal storage.
I think I give up on this. Glad to live in EU where I still should have warranty as the device is not older than 6 months
So you saying that if we leave in eu and phone purchased before 6 mo ago, we can still send phone to warranty even if we unlocked bootloader and did all the s* with it? I leave in portugal so i would think im in.
CPMAGMPC said:
So you saying that if we leave in eu and phone purchased before 6 mo ago, we can still send phone to warranty even if we unlocked bootloader and did all the s* with it? I leave in portugal so i would think im in.
Click to expand...
Click to collapse
if you have bought it after 6 month ago, see here:
http://piana.eu/root
You might need to convince the shop were you bought it, but generally in EU rooting/unlocking does not taint warranty. Note that it's the warranty the seller gives you, not the warranty from Motorola.
Just for interest, when you format your /data-partition, do you also get I/O-errors when entering dmesg?
I did not even unlock my device before the problem occured, so I assume that this problem is not caused by your custom rom.
when i format data partition in twrp i get success, but i check data after and all apps, photos etc still there and i can copy that data to my pc with usb and windows explorer.
cxxxx said:
if you have bought it after 6 month ago, see here:
http://piana.eu/root
You might need to convince the shop were you bought it, but generally in EU rooting/unlocking does not taint warranty. Note that it's the warranty the seller gives you, not the warranty from Motorola.
Just for interest, when you format your /data-partition, do you also get I/O-errors when entering dmesg?
I did not even unlock my device before the problem occured, so I assume that this problem is not caused by your custom rom.
Click to expand...
Click to collapse
My wife's XT1064 (Canadian Single SIM) is doing this exact same thing. Boot loops after the battery drained to 0%. All the options in the fastboot menu do nothing other than show the Motorola android logo.
Can someone link me to the proper firmware for the XT1064 factory image? This forum is pretty haphazardly laid out...
jippers said:
My wife's XT1064 (Canadian Single SIM) is doing this exact same thing. Boot loops after the battery drained to 0%. All the options in the fastboot menu do nothing other than show the Motorola android logo.
Can someone link me to the proper firmware for the XT1064 factory image? This forum is pretty haphazardly laid out...
Click to expand...
Click to collapse
Unfortunately they can be found only in a share on filefactory: http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=1
See here: http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/
Are you sure you did not confuse power-button with volume-up-button in fastboot menu? I did nearly a whole day
But even after I found out, I was not able to start recovery until I tried to flash with a custom recovery - what did not succeed, but at least stock recovery started then and I am able to boot TWRP directly using "fastboot boot recovery.img".
Would be nice to hear whether your storage is messed up, too.
I have faced the same prblm . Just boot into boot loader mode and download stock Firmware from http://forum.xda-developers.com/moto-g-2014/general/moto-g-2014-factory-firmware-images-t2869485 and then flash everything Cheers u have fixed ur moto G.
Source: Experienced it. lol I have a lot of sad experiences.
already tried that.. the problem is adb fastboòt never recognizes my device, only if im twrp it gets recognized, but then when i try to send commands with fastboot, device returns to boòtloader mode, and then it stops being detected again. i really think my device as no return.. hope im wrong :crying:
Mohandass said:
I have faced the same prblm . Just boot into boot loader mode and download stock Firmware from http://forum.xda-developers.com/moto-g-2014/general/moto-g-2014-factory-firmware-images-t2869485 and then flash everything Cheers u have fixed ur moto G.
Source: Experienced it. lol I have a lot of sad experiences.
Click to expand...
Click to collapse
CPMAGMPC said:
already tried that.. the problem is adb fastboòt never recognizes my device, only if im twrp it gets recognized, but then when i try to send commands with fastboot, device returns to boòtloader mode, and then it stops being detected again. i really think my device as no return.. hope im wrong :crying:
Click to expand...
Click to collapse
What PC OS are u using? I use Windows 7... I think Motorola's Drivers aren't Compatible with Windows 8 Yet As when i tried on my Friends PC with Windows 8, My phone wasn't recognised in bootloader mode even with Drivers installed...