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.
Related
I've installed Fresh ROM on my Evo Shift 4G. It worked for about a week, then the GPS stopped working (a known bug with this device and Gingerbread). I restarted the device as normal, and when it came back up all my downloaded apps and the Market were gone, and the device was in that strange indeterminate state where I'm both synced to a Gmail account and not at the same time (the Setup app appears in the Apps folder). Signing in doesn't help.
I rebooted into Clockwork Recovery (3.2.0.1), wiped data/factory reset, wiped the cache, wiped dalvik, and installed Fresh ROM again.
Once that was complete and booted, I signed in, attempted to install an app and the phone reset. There's no file manager installed nor terminal app so I can't delete things by bash. I connected over USB and tried to adb shell in, but that caused the phone to reset.
I'm stuck. Clearly something has not been properly wiped prior to installing Fresh ROM.
What do I need to do to get out of this loop?
SoopahMan said:
I've installed Fresh ROM on my Evo Shift 4G. It worked for about a week, then the GPS stopped working (a known bug with this device and Gingerbread). I restarted the device as normal, and when it came back up all my downloaded apps and the Market were gone, and the device was in that strange indeterminate state where I'm both synced to a Gmail account and not at the same time (the Setup app appears in the Apps folder). Signing in doesn't help.
I rebooted into Clockwork Recovery (3.2.0.1), wiped data/factory reset, wiped the cache, wiped dalvik, and installed Fresh ROM again.
Once that was complete and booted, I signed in, attempted to install an app and the phone reset. There's no file manager installed nor terminal app so I can't delete things by bash. I connected over USB and tried to adb shell in, but that caused the phone to reset.
I'm stuck. Clearly something has not been properly wiped prior to installing Fresh ROM.
What do I need to do to get out of this loop?
Click to expand...
Click to collapse
Sounds like you either had a bad Flash, a bad Download, or both. So redownload the Rom you choose, then Clear and Flash your device according to THESE INSTRUCTIONS .
Thanks for the response. I downloaded the ROM again and ran a check - identical to the file I downloaded previously. So, if the ROM is the culprit, then the latest version of Fresh ROM for Evo Shift does not work (4.1.1).
I followed the instructions linked, wiping the cache and dalvik-cache twice (why?), and wiping system etc prior to installing the ROM.
I'm running into the exact same issues as before - I can't install anything from the Market, and the phone resets if I connect it to a computer over USB. When it resets, it resets multiple times and when it comes back up the 4G no longer works.
If I rerun the above instructions, the 4G works again, but I'm stuck back in this loop - can't use the Market or connect it over USB or it will reset, so forth.
Could Fresh ROM 4.1.1 for Evo Shift be bad? I still suspect the real problem is something is not sufficiently wiped or setup prior to install.
In case it might help, here's an ls -al after installing Fresh Rom 4.1.1 on my phone (an HTC Evo Shift 4G after following the above install instructions).
/
drwxr-xr-x 2 root root 0 Jan 17 07:39 boot
drwxr-xr-x 4 root root 1024 Jan 17 07:41 cache
drwxrwx--x 2 root root 0 Jan 1 1970 data
drwxr-xr-x 2 root root 0 Jan 17 07:39 datadata
-rw-r--r-- 1 root root 3462 Jan 1 1970 default.prop
drwxr-xr-x 12 root root 3060 Jan 17 07:39 dev
drwxr-xr-x 2 root root 0 Jan 17 07:39 emmc
drwxr-xr-x 2 root root 0 Jan 17 07:39 etc
-rwxr-x--- 1 root root 94372 Jan 1 1970 init
-rwxr-x--- 1 root root 899 Jan 1 1970 init.rc
dr-xr-xr-x 79 root root 0 Jan 1 1970 proc
drwxr-xr-x 4 root root 0 Jan 1 1970 res
drwx------ 2 root root 0 May 15 2011 root
drwxr-x--- 2 root root 0 Jan 1 1970 sbin
drwxr-xr-x 2 root root 0 Jan 17 07:39 sd-ext
drwxrwxrwx 78 root root 32768 Jan 1 1970 sdcard
drwxr-xr-x 18 root root 0 Jan 17 07:39 sys
drwxr-xr-x 3 root root 0 Jan 1 1970 system
drwxr-xr-x 2 root root 0 Jan 17 07:45 tmp
-rw-r--r-- 1 root root 0 Jan 1 1970 ueventd.goldfish.rc
-rw-r--r-- 1 root root 4027 Jan 1 1970 ueventd.rc
-rw-r--r-- 1 root root 987 Jan 1 1970 ueventd.speedy.rc
/data
(empty)
/system
drwxr-xr-x 2 root root 0 Jan 1 1970 bin
/system/bin
(empty)
/sys
drwxr-xr-x 2 root root 0 Jan 17 07:53 android_camera
drwxr-xr-x 2 root root 0 Jan 17 07:53 android_camera_awb_cal
drwxr-xr-x 2 root root 0 Jan 17 07:53 android_touch
drwxr-xr-x 2 root root 0 Jan 17 07:53 block
drwxr-xr-x 2 root root 0 Jan 17 07:39 board_properties
drwxr-xr-x 9 root root 0 Jan 17 07:53 bus
drwxr-xr-x 2 root root 0 Jan 17 07:53 camera_led_status
drwxr-xr-x 47 root root 0 Jan 17 07:53 class
drwxr-xr-x 4 root root 0 Jan 17 07:53 dev
drwxr-xr-x 10 root root 0 Jan 17 07:39 devices
drwxr-xr-x 2 root root 0 Jan 17 07:53 firmware
drwxr-xr-x 3 root root 0 Jan 17 07:53 fs
drwxr-xr-x 6 root root 0 Jan 17 07:53 kernel
drwxr-xr-x 62 root root 0 Jan 17 07:53 module
drwxr-xr-x 2 root root 0 Jan 17 07:53 power
drwxr-xr-x 2 root root 0 Jan 17 07:53 systemlog
I can post more or other diagnostics if others have something to recommend. Really stuck here.
Is it odd that /sd-ext is at root and not located on the SD card, and a directory not a symlink?
Now that you have 10 posts you should try posting your questions in the thread for flipz's rom.So the dev can help and maybe anyone else that is running this rom. Also have you tried the a2sd remove command adb shell or from terminal emulator? See if that helps.
Sent from my PG06100 using Tapatalk
A bit more to isolate the problem:
If the phone resets (due to attempting an install from the Market or plug in from USB), 4G fails - but if I restart the phone at that point, when it reboots 4G works again. So 4G appears to be fine, it's the resets that are at the core of the issue.
I shutdown, removed the SD card, booted, and attempted to install an app and got the same reset, so it's not the SD card - it's definitely a problem somewhere on internal storage.
What else do I need to clear to clear this up?
Fresh ROM's pages say to look in /data/app and /system/app for a place where an app already exists that would cause a conflict.
Here's /data after booting the ROM and setting up a Gmail account:
lrwxrwxrwx 1 root root 14 Jan 17 07:54 app -> /system/sd/app
lrwxrwxrwx 1 root root 22 Jan 17 07:54 app-private -> /system/sd/app-private
drwx------ 5 system system 1024 Jan 6 1980 backup
drwxrwx--x 2 system system 14336 Jan 17 16:25 dalvik-cache
drwxrwx--x 161 system system 9216 Jan 17 07:57 data
drwxr-x--- 2 root log 1024 Jan 17 07:54 dontpanic
lrwxrwxrwx 1 root root 11 Jan 17 07:54 drm -> /data/local
-rw-r--r-- 1 root root 6134 Jan 6 1980 dta2sd.lg1
-rw-r--r-- 1 root root 6266 Jan 6 1980 dta2sd.lg2
-rw-r--r-- 1 root root 6266 Jan 6 1980 dta2sd.log
drwxrwxrwx 2 root root 1024 Jan 17 07:54 htcfs
drwxr-xr-x 4 root root 1024 Jan 17 07:42 jit
drwxrwx--x 4 shell shell 1024 Jan 17 07:54 local
drwxrwx--- 2 root root 12288 Jan 17 07:41 lost+found
drwxrwx--t 10 system misc 1024 Jan 17 07:55 misc
drwx------ 2 root root 1024 Jan 6 1980 property
drwx------ 3 system system 1024 Jan 17 07:55 secure
drwxrwxr-x 9 system system 1024 Jan 17 17:48 system
drwxrwx--- 3 system system 1024 Jan 17 17:14 wimax
I'd like to know if app and app-private are as expected (they appear to be the result of the ROM install, since they were completely wiped prior to installing it). The app symlink is a strange one. It points to /system/sd/app, which I can't cd to. /system/sd I can cd to, and this is all it contains:
-rw-r--r-- 1 root root 17 Aug 1 2008 placeholder
A file named placeholder. What?
I'm starting to suspect apps2sd. None of the relevant partitioning steps are in those install instructions, and they appear to be specific to the apps2sd of CyanogenMod. Google's appears to support a DOS partition, while CyanogenMod's appears to only support an ext3 partition, which I do not have.
At the same time, removing the SD card didn't change things, so color me confused.
As suggested by FdxRider you should definately post up in the Rom thread. That way you can get help resolving the issue from others running the same Rom.
It was apps2sd.
To resolve this problem, I had to:
Reboot into ClockwordModRecovery
Connect the phone to a computer over USB
In Clockwork, choose Mount Storage and choose the last option, Mount USB.
Dump anything I wanted to keep off of the SD card (most importantly, the FreshRom zip file).
Then, back in Clockwork, Advanced>Partition SD
Choose a size (they recommend 1024M)
This wipes out everything on the SD card, creates a Linux partition for apps2sd to use, marks the rest as a Windows partition.
Wait till it's done, then, still from ClockworkModRecovery:
Wipe cache, dalvik cache, system, data
Factory reset
Now Mount USB again so you can copy the FreshRom zip back onto the Windows partition (the only part that will come up on a Windows machine).
Eject on the Windows machine to ensure the copy completes, Unmount in Clockwork.
Install the ROM again
Let it boot, restart
Setup my Google Account/Gmail user
And one final thing:
As it turns out ES File Explorer is pre-installed on this ROM. That means installing it from the Market will make the phone go crazy regardless of proper setup. But I am now able to install other apps just fine from the Market (at last).
reset loop NO clockwork until factory reset
I installed Fresh 4.1.1 on my shift 4g
I went to install ROM Manager got it downloaded and it reset the phone at install.
I even tried going to the website and installing it that way. Same results.
I can't get clockwork to work, when i hold the volume down and then press power nothing happens until i release the power button then it goes directly to the Fresh install.
PLEASE HELP!!!!
---------- Post added at 05:30 AM ---------- Previous post was at 05:09 AM ----------
I got the problem solved. I used the RRU and it walked me through a recovery, part of it was yanking the battery. DUH!
I'm getting the attached errors when running TWRP using:
Code:
fastboot boot openrecovery-twrp-2.8.3.0-xt1032.img
Here is a summary of the message:
Code:
Device driver software was not successfully installed
XT1032 No driver found
USB Composite Device Ready to use
MTP USB Device Failed
Motorola ADB Interface No driver found
If I flash instead of just booting, I only get the MTP USB Device error. I know that I have working drivers for fastboot & adb, but I'm not sure how relevant they are when the Moto G is in recovery. I just included all errors shown in the message window.
Can I safely ignore the errors?
Here are the details (1st generation Moto G):
* Android 4.4.4
* Kernel version 3.4.42-g67b2f25
* System version 210.12.50.falcon_umts.Telus.en.CA
* Build number KXB21.14-L1.50
* Laptop: Windows 7 64-bit
Background for reference only
-----------------------------
In case this heads off any questions, here is the history and context behind my usage scenario.
I've unlocked my boot loader and wanted to backup the carrier's OS before installing CyanogenMod and/or rooting. The carrier is Koodo Mobile, and I wanted to make a backup rather than download what was available on the web.
"fastboot boot cwm.img" didn't work, so I used "fastboot flash recovery cwm.img" (actual file was recovery-clockwork-6.0.4.7-falcon.img from http://www.clockworkmod.com/rommanager). When I tried to go into recovery, I got an android logo with the message "No command".
According to http://forum.xda-developers.com/showthread.php?t=2563599, the Android 4.4 bootloader doesn't work with CWM, and I would have to flash the 4.3 bootloader. Or so it seems to me. Being new to the whole smartphone thing, I decided against doing that and went with TWRP instead (http://teamw.in/project/twrp2/233). I got the same "No Command", and http://forum.xda-developers.com/showpost.php?p=49122115&postcount=129, indicated that I could not flash TWRP due to its size. Instead:
Code:
fastboot boot openrecovery-twrp-2.8.3.0-xt1032.img
It ran and created backup files according my settings (including PDS, as per http://www.reddit.com/r/MotoG/comments/2cpxem/pds_partition):
Code:
[X] Data (156MB)
[ ] Cache (11MB)
[X] System (763MB)
[X] Boot (10MB)
[X] PDS (3MB)
No Encryption Refresh Sizes
Storage: Internal Storage (4040MB)
[X] Enable compression
[ ] Skip MDF generation during backup
The files were located at both /mnt/shell/emulated/0/TWRP/BACKUPS/TA929174HF and /storage/emulated/legacy/TWRP/BACKUPS/TA929174HF. In the Windows Explorer, it was found in "Computer\XT1032\Internal storage\TWRP\BACKUPS\TA929174HF".
I later ran across webpages saying that you should use mfastboot for large *.img files, and that seemed to allow me to flash TWRP onto the Moto G. When I re-did the backup, I only go the MTP message in the device driver error window. Here is the listing of the Windows folder "Computer\XT1032\Internal storage\TWRP\BACKUPS\TA929174HF\2015-01-04--20-29-45 KXB21.14-L1.50":
Code:
-rw-rw---- root sdcard_r 10485760 2015-01-04 21:31 boot.emmc.win
-rw-rw---- root sdcard_r 48 2015-01-04 21:31 boot.emmc.win.md5
-rw-rw---- root sdcard_r 70714967 2015-01-04 21:30 data.f2fs.win
-rw-rw---- root sdcard_r 48 2015-01-04 21:30 data.f2fs.win.md5
-rw-rw---- root sdcard_r 64 2015-01-04 21:30 data.info
-rw-rw---- root sdcard_r 3145728 2015-01-04 21:31 pds.emmc.win
-rw-rw---- root sdcard_r 47 2015-01-04 21:31 pds.emmc.win.md5
-rw-rw---- root sdcard_r 487236 2015-01-04 21:31 recovery.log
-rw-rw---- root sdcard_r 475807073 2015-01-04 21:31 system.ext4.win
-rw-rw---- root sdcard_r 50 2015-01-04 21:31 system.ext4.win.md5
-rw-rw---- root sdcard_r 64 2015-01-04 21:31 system.info
So, I just managed to get the Bootloader unlocked, flashed CWRM and then accidentally hit the factory reset button from the system settings menu, and am now stuck in the reset recovery screen.
I have access to adb but not fastboot. I have not done anything with NVFLASH
Am I permanently screwed for this motherboard or can I still be recovered?
ls -l /dev/block/mmc*
__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!
brw------- 1 root root 179, 0 Aug 29 02:23 /dev/block/mmcblk0
brw------- 1 root root 179, 16 Aug 29 02:23 /dev/block/mmcblk0boot0
brw------- 1 root root 179, 32 Aug 29 02:23 /dev/block/mmcblk0boot1
brw------- 1 root root 179, 1 Aug 29 02:23 /dev/block/mmcblk0p1
brw------- 1 root root 179, 10 Aug 29 02:23 /dev/block/mmcblk0p10
brw------- 1 root root 179, 2 Aug 29 02:23 /dev/block/mmcblk0p2
brw-rw---- 1 root system 179, 3 Aug 29 02:23 /dev/block/mmcblk0p3
brw-rw---- 1 root system 179, 4 Aug 29 02:23 /dev/block/mmcblk0p4
brw------- 1 root root 179, 5 Aug 29 02:23 /dev/block/mmcblk0p5
brw------- 1 drm drm 179, 6 Aug 29 02:23 /dev/block/mmcblk0p6
brw-rw---- 1 root system 179, 7 Aug 29 02:23 /dev/block/mmcblk0p7
brw------- 1 root root 179, 8 Aug 29 02:23 /dev/block/mmcblk0p8
brw------- 1 root root 179, 9 Aug 29 02:23 /dev/block/mmcblk0p9
Click to expand...
Click to collapse
Code:
adb shell
~ #cd sys
/sys # ls
ls
block class devices fs module tf_driver
bus dev firmware kernel power
/sys #cd block
/sys/block # ls
ls
loop0 loop2 loop4 loop6 mmcblk0 mmcblk0boot1
loop1 loop3 loop5 loop7 mmcblk0boot0 zram0
can I use this to edit something and unbrick?
Stephenopolos said:
Code:
adb shell
~ #cd sys
/sys # ls
ls
block class devices fs module tf_driver
bus dev firmware kernel power
/sys #cd block
/sys/block # ls
ls
loop0 loop2 loop4 loop6 mmcblk0 mmcblk0boot1
loop1 loop3 loop5 loop7 mmcblk0boot0 zram0
can I use this to edit something and unbrick?
Click to expand...
Click to collapse
If you reboot by long pressing the power button, does it boot straight back to recovery?
If so you can try these commands to clear the Wipe Data command from the misc partition:
Code:
adb shell
dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1
reboot
Good luck!
Thanks for the quick response. Yes it does drop immediately into the recovery/reset wipe data screen on reboot.
It's pretty late and I want to avoid making any mistakes in typing commands so I'm going to try that in the morning.
Also, while i'm not the best at the command line side, I am comfortable opening things up, so if it doesn't work I'm not entirely opposed to just buying a replacement MB and swapping it out. Hopefully it'll work though.
Stephenopolos said:
Thanks for the quick response. Yes it does drop immediately into the recovery/reset wipe data screen on reboot.
It's pretty late and I want to avoid making any mistakes in typing commands so I'm going to try that in the morning.
Also, while i'm not the best at the command line side, I am comfortable opening things up, so if it doesn't work I'm not entirely opposed to just buying a replacement MB and swapping it out. Hopefully it'll work though.
Click to expand...
Click to collapse
If you use Wipe Data from the bootloader or the Factory reset from Settings a command gets written to misc to start the recovery and wipe data.
Problem is, custom recoveries don't really "get" the command and do not execute it so the command does not get erased from misc and you're stuck in booting to recovery because the bootloader executes that command on each boot.
If your recovery is CWM you can try just leaving it on the wipe data screen for a few hours. With past CWM versions that usually worked and it eventually finished the wipe. Not with TWRP though.
Connect the tab to power and leave it on the wipe data screen until tomorrow. Then you can still try to clear the command with dd.
Copy and paste it. You don't want to have any typos with a dd command...
berndblb said:
Problem is, custom recoveries don't really "get" the command
Click to expand...
Click to collapse
Only if your recovery kernel is too old to work with the bootloader, in which case it can't access any partitions.
berndblb said:
If your recovery is CWM you can try just leaving it on the wipe data screen for a few hours. With past CWM versions that usually worked and it eventually finished the wipe. Not with TWRP though.
Click to expand...
Click to collapse
TWRP should do its "Factory Reset" (which doesn't clear /sdcard). I've never tried it because I don't want to restore everything from a backup.
ran command this morning, and it hung in the shell... just sits there without finishing the command.
frustrating... I thought i'd read everything and triple read it again, but the main thread for custom recoveries for this tablet, didn't really mention anything about avoiding factory reset from device.
oh well. found a MB on ebay cheap i'll try the command again in a bit and if it doesn't work then next week i'll be installing a mb myself.
Code:
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1
1+0 records in
1+0 records out
64 bytes (64B) copied, 402.164494 seconds, 0B/s
I'm assuming this means success...
will see in a bit... tablet is now claiming it has a low battery after I told it to reboot.
Hallelujah! it worked! berndblb You're my new favorite person in the world today.
_that said:
Only if your recovery kernel is too old to work with the bootloader, in which case it can't access any partitions.
TWRP should do its "Factory Reset" (which doesn't clear /sdcard). I've never tried it because I don't want to restore everything from a backup.
Click to expand...
Click to collapse
I have never tried it either. Just seen users reporting that with CWM installed the command eventually went through if you left it alone long enough. That doesn't seem to work with TWRP. But that's just hearsay....
Stephenopolos said:
Hallelujah! it worked! berndblb You're my new favorite person in the world today.
Click to expand...
Click to collapse
Very good!
But you have to thank @_that ^^^ for the command. He's the one I stole it from
berndblb said:
I have never tried it either. Just seen users reporting that with CWM installed the command eventually went through if you left it alone long enough. That doesn't seem to work with TWRP. But that's just hearsay....
Very good!
But you have to thank @_that ^^^ for the command. He's the one I stole it from
Click to expand...
Click to collapse
... you got to me first though...
Anyway, I had difficulty getting CM11 and CM12 to install eventually managed to get zombipop to install by dropping it onto a USB stick and using the keyboard dock. Had to flash a new recovery image as well.. apparently the one I put on there the first time around was screwy.
Stephenopolos said:
... you got to me first though...
Anyway, I had difficulty getting CM11 and CM12 to install eventually managed to get zombipop to install by dropping it onto a USB stick and using the keyboard dock. Had to flash a new recovery image as well.. apparently the one I put on there the first time around was screwy.
Click to expand...
Click to collapse
Luck for you that I was here first. _that would have made you pull all kinds of logs before giving you the same command :laugh: :cyclops:
berndblb said:
Luck for you that I was here first. _that would have made you pull all kinds of logs before giving you the same command :laugh: :cyclops:
Click to expand...
Click to collapse
The required logs in this case are already in the OP. But thank you for taking over first level support.
Hi Guys
I'm new to the Forum and start with asking a question - apologize for that, I know that it's impolite.
I'm pretty desperate at the moment. Tried to switch on my Galaxy Nexus some days ago and it did not start. If I try to switch it on (long button press), the google logo appears for about 72 seconds, then "something" happens on the screen (usually the logo becomes brighter and horizontal lines appear on the screen). And that's it.
There's no clear reason why the mobile is broken now.
The big problem is that I have lots of pictures of my little boy on that device, from his birth until now (it's his first birthday tomorrow). These pics are very very important to me, the only pictures I have from his birth. I did not backup those pictures - I'm stupid :crying:. So my goal is to rescue those images from the device somehow. Currently I'm spending every free second to read and learn how to recover those images...
Device info:
Galaxy Nexus, Tuna Maguro 16GB
HW Version: 9
Bootloader Version: PRIMEMD04
Baseband Version: I9250XXLJ1
Everything is stock version, Android 4.4.2 (I think), stock bootloader
What I've tried so far:
- Installed fastload / ADB on Ubuntu 14.04 from repo. Manually installed ADB 1.0.32 as well.
- I can boot the device into Fastboot / Rescue / Odin mode, that works.
- Tried to clear the cache. It hangs after "Formatting /cache". No "completed" message. If I go to the recovery menu now, I get a couple of messages which say
"E:failed to mount /cache (Invalid argument)"
and then lots of "Can't mount /cache/recovery/log" messages.
If I boot in Rescue Mode, select "apply update from ADB" and connect the mobile to the PC:
Code:
[ 502.524071] usb 1-5: new high-speed USB device number 3 using ehci-pci
[ 502.657321] usb 1-5: New USB device found, idVendor=18d1, idProduct=d001
[ 502.657330] usb 1-5: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 502.657348] usb 1-5: Product: Galaxy Nexus
[ 502.657352] usb 1-5: Manufacturer: samsung
[ 502.657355] usb 1-5: SerialNumber: (redacted)
So it gets detected, at least.
Then:
Code:
$ ./adb get-state
sideload
$ ./adb devices -l
List of devices attached
(serial redacted) sideload usb:1-5
$ ./adb backup -all
adb: unable to connect for backup
$ ./adb bugreport
error: closed
$ ./adb shell pwd
error: closed
$ ./adb logcat
- waiting for device -
^C
I've downloaded the stock yakju ROM from the google dev website (can't post links, sorry).
There are a bunch of files in that archive:
Code:
$ ll
total 298996
drwxr-x--- 2 m m 4096 Aug 21 2013 ./
drwxr-xr-x 7 m m 4096 Aug 30 23:50 ../
-rw-r----- 1 m m 2363392 Aug 21 2013 bootloader-maguro-primemd04.img
-rw-r----- 1 m m 956 Aug 21 2013 flash-all.bat
-rwxr-x--x 1 m m 827 Aug 21 2013 flash-all.sh*
-rwxr-x--x 1 m m 785 Aug 21 2013 flash-base.sh*
-rw-r----- 1 m m 291192953 Aug 21 2013 image-yakju-jwr66y.zip
-rw-r----- 1 m m 12583168 Aug 21 2013 radio-maguro-i9250xxlj1.img
Code:
$ zipinfo image-yakju-jwr66y.zip
Archive: image-yakju-jwr66y.zip
Zip file size: 291192953 bytes, number of entries: 5
?rw-r--r-- 2.0 unx 4481024 b- defN 09-Jan-01 00:00 boot.img
?rw-r--r-- 2.0 unx 5042176 b- defN 09-Jan-01 00:00 recovery.img
?rw-r--r-- 2.0 unx 485561008 b- defN 09-Jan-01 00:00 system.img
-rw------- 2.0 unx 140860420 b- defN 13-Aug-13 22:56 userdata.img
-rw-r----- 2.0 unx 93 b- defN 13-Aug-13 16:00 android-info.txt
So my questions are:
Am I doing the right thing here? I Hope that this is a software problem and the hardware is ok.
If yes, which of those file(s) should I flash to the device, without risking loss of data?
Can you think of any other possibility to recover the data? Clockwork mod or TWRP maybe? Or a custom sideload script (inside the uploaded zip file).
I've read that flashing a custom bootloader wipes the device - so maybe CW / TWRP is not a good idea.
Thank you very very much in advance for your help.
Matt
backupnoob said:
Hi Guys
I'm new to the Forum and start with asking a question - apologize for that, I know that it's impolite.
I'm pretty desperate at the moment. Tried to switch on my Galaxy Nexus some days ago and it did not start. If I try to switch it on (long button press), the google logo appears for about 72 seconds, then "something" happens on the screen (usually the logo becomes brighter and horizontal lines appear on the screen). And that's it.
There's no clear reason why the mobile is broken now.
The big problem is that I have lots of pictures of my little boy on that device, from his birth until now (it's his first birthday tomorrow). These pics are very very important to me, the only pictures I have from his birth. I did not backup those pictures - I'm stupid :crying:. So my goal is to rescue those images from the device somehow. Currently I'm spending every free second to read and learn how to recover those images...
Device info:
Galaxy Nexus, Tuna Maguro 16GB
HW Version: 9
Bootloader Version: PRIMEMD04
Baseband Version: I9250XXLJ1
Everything is stock version, Android 4.4.2 (I think), stock bootloader
What I've tried so far:
- Installed fastload / ADB on Ubuntu 14.04 from repo. Manually installed ADB 1.0.32 as well.
- I can boot the device into Fastboot / Rescue / Odin mode, that works.
- Tried to clear the cache. It hangs after "Formatting /cache". No "completed" message. If I go to the recovery menu now, I get a couple of messages which say
"E:failed to mount /cache (Invalid argument)"
and then lots of "Can't mount /cache/recovery/log" messages.
If I boot in Rescue Mode, select "apply update from ADB" and connect the mobile to the PC:
Code:
[ 502.524071] usb 1-5: new high-speed USB device number 3 using ehci-pci
[ 502.657321] usb 1-5: New USB device found, idVendor=18d1, idProduct=d001
[ 502.657330] usb 1-5: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 502.657348] usb 1-5: Product: Galaxy Nexus
[ 502.657352] usb 1-5: Manufacturer: samsung
[ 502.657355] usb 1-5: SerialNumber: (redacted)
So it gets detected, at least.
Then:
Code:
$ ./adb get-state
sideload
$ ./adb devices -l
List of devices attached
(serial redacted) sideload usb:1-5
$ ./adb backup -all
adb: unable to connect for backup
$ ./adb bugreport
error: closed
$ ./adb shell pwd
error: closed
$ ./adb logcat
- waiting for device -
^C
I've downloaded the stock yakju ROM from the google dev website (can't post links, sorry).
There are a bunch of files in that archive:
Code:
$ ll
total 298996
drwxr-x--- 2 m m 4096 Aug 21 2013 ./
drwxr-xr-x 7 m m 4096 Aug 30 23:50 ../
-rw-r----- 1 m m 2363392 Aug 21 2013 bootloader-maguro-primemd04.img
-rw-r----- 1 m m 956 Aug 21 2013 flash-all.bat
-rwxr-x--x 1 m m 827 Aug 21 2013 flash-all.sh*
-rwxr-x--x 1 m m 785 Aug 21 2013 flash-base.sh*
-rw-r----- 1 m m 291192953 Aug 21 2013 image-yakju-jwr66y.zip
-rw-r----- 1 m m 12583168 Aug 21 2013 radio-maguro-i9250xxlj1.img
Code:
$ zipinfo image-yakju-jwr66y.zip
Archive: image-yakju-jwr66y.zip
Zip file size: 291192953 bytes, number of entries: 5
?rw-r--r-- 2.0 unx 4481024 b- defN 09-Jan-01 00:00 boot.img
?rw-r--r-- 2.0 unx 5042176 b- defN 09-Jan-01 00:00 recovery.img
?rw-r--r-- 2.0 unx 485561008 b- defN 09-Jan-01 00:00 system.img
-rw------- 2.0 unx 140860420 b- defN 13-Aug-13 22:56 userdata.img
-rw-r----- 2.0 unx 93 b- defN 13-Aug-13 16:00 android-info.txt
So my questions are:
Am I doing the right thing here? I Hope that this is a software problem and the hardware is ok.
If yes, which of those file(s) should I flash to the device, without risking loss of data?
Can you think of any other possibility to recover the data? Clockwork mod or TWRP maybe? Or a custom sideload script (inside the uploaded zip file).
I've read that flashing a custom bootloader wipes the device - so maybe CW / TWRP is not a good idea.
Thank you very very much in advance for your help.
Matt
Click to expand...
Click to collapse
Hello and thank you for using XDA Assist.
We cannot provide technical support nor can other members reply to your posts here on XDA Assist but fortunately there is an XDA area dedicated to the Samsung Galaxy Nexus family at http://forum.xda-developers.com/galaxy-nexus which would be a good starting place. I suggest you post your question with all relevant details (Tuna and Maguro are not identical!) in the friendly Q&A forum there at http://forum.xda-developers.com/galaxy-nexus/help where the experts familiar with your device will be best able to guide you.
Good luck!
Ok, thank you very much Mike, will ask there.
{
"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"
}
Code:
/* Disclaimer
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed. Please do some research
* if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you blame me in any way for what happens to your device, I will laugh at you.
* BOOM! goes the dynamite
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 7 (nougat), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What's working :
*Boots
*Touch
*RIL [Calls, Mobile Data, Dual SIM]
*Wifi
*Wifi Tethering
*Bluetooth
*Camera
*Camcorder
*Audio
*Sensors
*Flash
*GPS
*Notification LED
*OTG
*VoLTE (comming soon)
*FM Radio
Instructions :
Download the latest build and GApps
* Reboot to recovery
* Wipe data/factory reset
* Flash the latest build and GApps
* Reboot
* If you want to root LineageOS, take a look at this thread:
Requriment TWRP: https://mega.nz/#!qwdXjRYB!0Ka5rwLU8ev-5bRYA9M0sFx_3xnCFIGaZXNt03JjNrA
Download Link:
Mega.nz
XDA:DevDB Information
[F2FS / EXT4] LineageOs 14.1 For General Mobile 5+, ROM for the General Mobile GM 5 Plus
Contributors
kaankulahli, wzedlare
Source Code: https://github.com/OneDeveloperOrganization/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: 1.0
Created 2016-09-25
Last Updated 2017-07-04
@ kaankulahli achievements
oyş As Byraklari As
Has been sources released or will be? Where I could access them?
berkantkz said:
Has been sources released or will be? Where I could access them?
Click to expand...
Click to collapse
not yet, maybe next days.
kaankulahli said:
not yet, maybe next days.
Click to expand...
Click to collapse
Can I see the sources? I might help you
send a private message.
Right now, All of the hardware problems are fixed.
Fixed minor bugs . (Microphone)
Download link is broken.
links renewed.
kaankulahli said:
links renewed.
Click to expand...
Click to collapse
sorry download link still broken
Oops, new links added .
in recovery "twrp-3.0.2-1-shamrock" i did a full wipe/factory reset,
and flashed cm_shamrock-ota-38062b8f0f.zip (14.0-20161004-unofficial-shamrock) + open_gapps-arm-7.0-mini-20161005.zip,
then did a wipe dalvik+cache, and boot system.
now i got these 2 errors:
- android system -there's an internal error with your device, contact your manufacturer for details. then i just entered through
- SIM card missing. a sim card has not been detected in our phone
system is running nicely with Wifi, but "no sim card detected".
in settings i noticed that there's a Unknown Baseband version.
i did a TWRP-restore of my previous twrp-backup: cm-13.0-20160912-UNOFFICIAL-shamrock-by-turkdevs ,
now everything works normal again.
how to solve the above errors?
7dwergen said:
i did a full wipe/factory reset, and flashed cm_shamrock-ota-38062b8f0f.zip + open_gapps-arm-7.0-mini-20161005.zip, wipe dalvik+cache, did boot system.
then i got these 2 errors:
- android system -there's an internal error with your device, contact your manufacturer for details. then i just entered through
- SIM card missing. a sim card has not been detected in our phone
system is running nicely with Wifi, but no sim card detected. in settings i noticed that there's a Unknown Baseband version.
i did a restore of the previous cm-13.0-20160912-UNOFFICIAL-shamrock-by-turkdevs.zip , this rom works normal.
how to solve the above errors?
Click to expand...
Click to collapse
Please install 7.0 stock and transfer to cm from stock rom.
7dwergen said:
in recovery "twrp-3.0.2-1-shamrock" i did a full wipe/factory reset,
and flashed cm_shamrock-ota-38062b8f0f.zip (14.0-20161004-unofficial-shamrock) + open_gapps-arm-7.0-mini-20161005.zip,
then did a wipe dalvik+cache, and boot system.
now i got these 2 errors:
- android system -there's an internal error with your device, contact your manufacturer for details. then i just entered through
- SIM card missing. a sim card has not been detected in our phone
system is running nicely with Wifi, but "no sim card detected".
in settings i noticed that there's a Unknown Baseband version.
i did a TWRP-restore of my previous twrp-backup: cm-13.0-20160912-UNOFFICIAL-shamrock-by-turkdevs ,
now everything works normal again.
how to solve the above errors?
Click to expand...
Click to collapse
Can you paste a screenshot from the partitions that you've backed up?
berkantkz said:
Can you paste a screenshot from the partitions that you've backed up?
Click to expand...
Click to collapse
there it is;
/external_sd/TWRP/BACKUPS/d9e7aab0 # ls -la 2016-10-05--17-10-15_cm_shamrock-use
rdebug_6.0.1_MOB31E_2e9510ad/
drwxrwxrwx 2 media_rw media_rw 4096 Oct 5 2016 .
drwxrwxrwx 5 media_rw media_rw 4096 Oct 5 2016 ..
-rw-rw-r-- 1 media_rw media_rw 67108864 Oct 5 2016 boot.emmc.win
-rw-rw-r-- 1 media_rw media_rw 48 Oct 5 2016 boot.emmc.win.md5
-rw-rw-r-- 1 media_rw media_rw 786587720 Oct 5 2016 data.ext4.win000
-rw-rw-r-- 1 media_rw media_rw 51 Oct 5 2016 data.ext4.win000.md5
-rw-rw-r-- 1 media_rw media_rw 185203104 Oct 5 2016 data.ext4.win001
-rw-rw-r-- 1 media_rw media_rw 51 Oct 5 2016 data.ext4.win001.md5
-rw-rw-r-- 1 media_rw media_rw 65 Oct 5 2016 data.info
-rw-rw-r-- 1 media_rw media_rw 88080384 Oct 5 2016 modem.emmc.win
-rw-rw-r-- 1 media_rw media_rw 49 Oct 5 2016 modem.emmc.win.md5
-rw-rw-r-- 1 media_rw media_rw 3182671 Oct 5 2016 oem.ext4.win
-rw-rw-r-- 1 media_rw media_rw 47 Oct 5 2016 oem.ext4.win.md5
-rw-rw-r-- 1 media_rw media_rw 59 Oct 5 2016 oem.info
-rw-rw-r-- 1 media_rw media_rw 1867443 Oct 5 2016 recovery.log
-rw-rw-r-- 1 media_rw media_rw 11534336 Oct 5 2016 splash.emmc.win
-rw-rw-r-- 1 media_rw media_rw 50 Oct 5 2016 splash.emmc.win.md5
-rw-rw-r-- 1 media_rw media_rw 649600246 Oct 5 2016 system.ext4.win
-rw-rw-r-- 1 media_rw media_rw 50 Oct 5 2016 system.ext4.win.md5
-rw-rw-r-- 1 media_rw media_rw 65 Oct 5 2016 system.info
/external_sd/TWRP/BACKUPS/d9e7aab0 #
kaankulahli said:
Please install 7.0 stock and transfer to cm from stock rom.
Click to expand...
Click to collapse
did you mean this 7.0 stock rom ?
https://www.androidfilehost.com/?w=files&flid=96107
GM_5_PLUS_DUAL_ANDROID_7.0_NOUGAT_OTA_BY_TURKDEVS.zip
7dwergen said:
there it is;
/external_sd/TWRP/BACKUPS/d9e7aab0 # ls -la 2016-10-05--17-10-15_cm_shamrock-use
rdebug_6.0.1_MOB31E_2e9510ad/
drwxrwxrwx 2 media_rw media_rw 4096 Oct 5 2016 .
drwxrwxrwx 5 media_rw media_rw 4096 Oct 5 2016 ..
-rw-rw-r-- 1 media_rw media_rw 67108864 Oct 5 2016 boot.emmc.win
-rw-rw-r-- 1 media_rw media_rw 48 Oct 5 2016 boot.emmc.win.md5
-rw-rw-r-- 1 media_rw media_rw 786587720 Oct 5 2016 data.ext4.win000
-rw-rw-r-- 1 media_rw media_rw 51 Oct 5 2016 data.ext4.win000.md5
-rw-rw-r-- 1 media_rw media_rw 185203104 Oct 5 2016 data.ext4.win001
-rw-rw-r-- 1 media_rw media_rw 51 Oct 5 2016 data.ext4.win001.md5
-rw-rw-r-- 1 media_rw media_rw 65 Oct 5 2016 data.info
-rw-rw-r-- 1 media_rw media_rw 88080384 Oct 5 2016 modem.emmc.win
-rw-rw-r-- 1 media_rw media_rw 49 Oct 5 2016 modem.emmc.win.md5
-rw-rw-r-- 1 media_rw media_rw 3182671 Oct 5 2016 oem.ext4.win
-rw-rw-r-- 1 media_rw media_rw 47 Oct 5 2016 oem.ext4.win.md5
-rw-rw-r-- 1 media_rw media_rw 59 Oct 5 2016 oem.info
-rw-rw-r-- 1 media_rw media_rw 1867443 Oct 5 2016 recovery.log
-rw-rw-r-- 1 media_rw media_rw 11534336 Oct 5 2016 splash.emmc.win
-rw-rw-r-- 1 media_rw media_rw 50 Oct 5 2016 splash.emmc.win.md5
-rw-rw-r-- 1 media_rw media_rw 649600246 Oct 5 2016 system.ext4.win
-rw-rw-r-- 1 media_rw media_rw 50 Oct 5 2016 system.ext4.win.md5
-rw-rw-r-- 1 media_rw media_rw 65 Oct 5 2016 system.info
/external_sd/TWRP/BACKUPS/d9e7aab0 #
Click to expand...
Click to collapse
That's good you've backed up modem. To have sim working CM-14, wipe everything, then install CM-14 (and gapps as optional), restore the modem partition. Reboot your device. Mustafa work. And if it Works, I suggest you to back your modem partition somewhere like ön your local or Google Drive or Mega or Mediafire...
Modem includes your IMEI number. ?f you lost it, that back-up will help you. This saves your life.
Good luck. You can pm me anytime. I'm glad to help.
berkantkz said:
That's good you've backed up modem. To have sim working CM-14, wipe everything, then install CM-14 (and gapps as optional), restore the modem partition. Reboot your device. Mustafa work. And if it Works, I suggest you to back your modem partition somewhere like ön your local or Google Drive or Mega or Mediafire...
Modem includes your IMEI number. ?f you lost it, that back-up will help you. This saves your life.
Good luck. You can pm me anytime. I'm glad to help.
Click to expand...
Click to collapse
thanks a lot for your suggestion so fast, berkantkz !
but unfortunately it did not solve my problem, still the same error situation.
'think i'am doing something stupid (or not?)
so i restored the last twrp-backup with cm13, system is up and running smoothly as before..
strange, it is exactly the same error situation i got some weeks ago, after flashing: cm-13.0-20160802-UNOFFICIAL-shamrock_by-TURKDEVS.zip
afterwards i could flash: cm-13.0-20160912-UNOFFICIAL-shamrock-by-turkdevs.zip , this rom solved that problem....