Please help! My Droid 4 is rebooting after every few minutes, it is entirely unusable. As well, it is unwilling to accept my SIM card. IDK what happened, what triggered it, nor how to fix it. What I have done so far:
1. While rooted and using a lighter stock rom (myfishbear I believe), the phone started these loops. I turned it off, entered safestrap recovery and wiped dalvik, cache, and data. Rebooted, problems still occur.
2. Changed ROM to AOKP, reboots stop however SIM card does not function at all.
3. Changed back to stock, reboots continue, SIM card still not functioning.
4. Changed to CM10 patched to definitely work with GSM carriers (olegfusion's patch). SIM does not work. Not recognized, phone not connecting to network.
5. Went to "safe" system (if I understand correctly), the stock stock vanilla ICS system. Reboots continue, SIM still not working. Factory reset, dalvik wiped as well.
6. Decided to try to fastboot a recovery as a last resort. Fastboot works, however the problem still exhibits itself. SIM not working, reboots continue, and I cannot pass the activation screen to be able to try anything else.
Can anyone please help me? I saved any and all bug reports that were on internal before doing anything, I also created backups of the ROMs before going ahead and reflashing the thing. I have no idea what to do anymore
I've found out what is making it crash. Somehow the radio is not working anymore. I've tried fastboot flash radio radio.img, however it fails. Here is the log:
Code:
-- Install /cache ...
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
Finding update package...
I:Update location: /tmp/sideload/package.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1461 bytes; signature 1438 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
installing motoflash extensions
installing NV updater extensions
installing omapdevtype updater extension
Formatting of Cache is required
Reading input Flash image....
Registering bp flash device
Registering lte flash device
Searching for flash devices...
Unable to find flash devices
Retry flashing
Searching for flash devices...
Unable to find flash devices
Retry flashing
Searching for flash devices...
Unable to find flash devices
Retry flashing
script aborted: assert failed: motorola.motoflash("/tmp/bp.img")
assert failed: motorola.motoflash("/tmp/bp.img")
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
W:failed to mount /dev/block/mmcblk0p1 (No such file or directory); trying /dev/block/mmcblk0
E:failed to mount /sdcard (No such file or directory)
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
Please someone help me out! Is this a hardware problem? Can it be fixed with a flash to an older radio.img? Are there custom radio.img's out that are known to fix this problem? Is there a way for me to fix it myself? Am I sending it in to Moto?
Related
Flashing from CM 5.0.8 using Rom Managers FRF83. It downloads three files, ERE27, FRF50, and FRF83. I get this error when installing part two
Code:
Installing: SDCARD:/clockworkmod/download/android.antbox.org/koush/google/passion/signed-passion-FRF50-from-ERE27.1e519a24.zip
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: SDCARD:/clockworkmod/download/android.antbox.org/koush/google/passion/signed-passion-FRF50-from-ERE27.1e519a24.zip
Opening update package...
I:Update file path: /sdcard/clockworkmod/download/android.antbox.org/koush/google/passion/signed-passion-FRF50-from-ERE27.1e519a24.zip
Installing update...
I:Trying update-binary.
installing HTC updater extensions
Failed to mount /dev/block/mtdblock3 on /system: Device or resource busy
mtd mount of system failed: Device or resource busy
Verifying current system...
mtd read matched size 2101248 sha e7f20e513e5bd5c30e20670e992092296ee731a0
0 bytes free on /cache (6762912 needed)
error opening /cache/recovery/otatest: No such file or directory
0 regular files in deletable directories
no files can be deleted to free space on /cache
unable to make 6762912 bytes available on /cache
script aborted: assert failed: apply_patch_space(6762912)
assert failed: apply_patch_space(6762912)
E:Error in /sdcard/clockworkmod/download/android.antbox.org/koush/google/passion/signed-passion-FRF50-from-ERE27.1e519a24.zip
(Status 7)
Installation aborted.
Failure at line 7:
install_zip SDCARD:/clockworkmod/download/android.antbox.org/koush/google/passion/signed-passion-FRF50-from-ERE27.1e519a24.zip
From what I'm reading, this means that the updater script from Rommanager doesn't release the mount on system after the first flash, because I can easily navigate to the directory after I receive this error and install it manually. I figure the way it works is after install it umounts.
Just as an FYI, if others are trying this, this is what I did to overcome. 1.Using clockwork recovery
2.mount SD
3.find FRF83fromFRF50
4. copy to /sdcard/update.zip
5. manually install ERE27toFRF50
6. let it boot
7. reboot into stock recovery
8. install update.zip through stock recovery
BOOM FRF83
Ooops, sorry MODs. It originated as a question, but I figured it out mid writing this. Please move to general. Sorry
I used the latest leaked update and flashed my droid 3 to Version 5.6.890, but now I having problem with my camera, so I decided to enter the Recovery mode and do the Data Wiping, but I found out I cannot enter the recovery mode...the screen shows AP FASTBOOT MODE and "BOOT FAILURE"...
So have I half bricked my Droid 3...? is there any way I can solve this problem and safe the Recovery Mode?
Thanks.
Read this post and this thread.
limaxray said:
Read this post and this thread.
Click to expand...
Click to collapse
Thanks for the information, I tried the method, but still failing to fix the problem, this is what the screen shows after i run the commend.
PHP:
[email protected]_solana:/# sh /etc/install-recovery.sh
sh /etc/install-recovery.sh
blk: partition "emstorage" size 12203196416 not a multiple of io_buffer_size 524
288
contents of partition "recovery" didn't match MTD:recovery:2048:ed2ac38df0bab0b2
382dc3330707ff884981f335
file "MTD:recovery:2048:ed2ac38df0bab0b2382dc3330707ff884981f335" doesn't have a
ny of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to stat "/data/saved.file": No such file or directory
failed to load cache file
applying patch to MTD:boot:8388608:c2c527aa31b9e529de6c6a574e4e589f1d2965d9
LoadPartitionContents called with bad filename (MTD:recovery)
blk: partition "emstorage" size 12203196416 not a multiple of io_buffer_size 524
288
contents of partition "recovery" didn't match MTD:recovery
partition read matched size 8388608 sha c2c527aa31b9e529de6c6a574e4e589f1d2965d9
543948800 bytes free on /cache (8388608 needed)
[email protected]_solana:/#
What's the output of
Code:
df /system
limaxray said:
What's the output of
Code:
df /system
Click to expand...
Click to collapse
It shows:
PHP:
Filesystem Size Used Free Blksize
/system 320M 310M 9M 1024
and I have also extract "install-recovery.sh" from the latest OTA package, and push to system/etc, now when i run the commend it shows:
PHP:
[email protected]_solana:/# sh /etc/install-recovery.sh
sh /etc/install-recovery.sh
blk: partition "emstorage" size 12203196416 not a multiple of io_buffer_size 524
288
partition read matched size 2048 sha ed2ac38df0bab0b2382dc3330707ff884981f335
EDIT: Solved, maybe after the space is freed up a little, I was able to enter the recovery mode again, and I re-flashed the OTA update again, everything is working now!
If you were able to enter recovery, then you were successful in running install-recovery.sh.
In any case, I'm glad you were able to get it to work.
I would to install cyanogenmod 10... I started from GB stock firmware(overcome I think)... I rooted device, then I put the zip file on internal memory... I started device holding power on and volup key... I wiped data/factory reset, then wiped cache... I finally chose install zip card but I received this error:
Installing /sdcard/cm-10-20120908-NIGHTLY-p1.zip
Finding update package
Opening update package
Installing update
assert failed: run_program("/tmp/updater.sh") == 0
E:Error in /sdcard/cm-10-20120908-NIGHTLY-p1.zip
(status 7)
Installation aborted.
I did a sho log in advanced menu:
I:Can't partition unsafe device: /dev/block/mmcblk0p1
I:Can't format unknown volume: /external_sd
I:Can't partition unsafe device:/dev/block/mmcblk1p1
I don't understand what I should to do... Can you help me???
My device is a p1000(gsm)... Now is accessible only in download mode and in CWM recovery...
I solved with one more step... First I returned to stock GB, then installed CM9 and updated to CM10 with cdesai instruction... Installation finished...
Hi all,
I got error blkdiscard failed invalid argument while flashing [ROM][MI3/Mi4][CM-12.1][Android-5.1.1]CM-Cancro.
Many said that I had to extend partition to 1.2GB, which I already did. I can install Temasek rom with extended
partition, but failed with Bitti09 rom.
Here is what I have did before
-flash r11 cwm
-manually extend partition
-script extend partition
-flash TWRP
all step above failed to install [ROM][MI3/Mi4][CM-12.1][Android-5.1.1]CM-Cancro.
Now running with audahadi Temasek rom.
Here is my log from TWRP
PHP:
Installing '/sdcard/Custom_rom/cm-12.1-20150613-UNOFFICIAL-mi3-cancro.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
minzip: Extracted 4 file(s)
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
Patching system image unconditionally...blockimg version is 2
erasing 318848 blocks
script aborted: blkdiscard failed: Invalid argument
blkdiscard failed: Invalid argument
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/Custom_rom/cm-12.1-20150613-UNOFFICIAL-mi3-cancro.zip'
Error flashing zip '/sdcard/Custom_rom/cm-12.1-20150613-UNOFFICIAL-mi3-cancro.zip'
Updating partition details...
Please help...
Finally I have solved this problem. Yes "blkdiscard failed: Invalid argument" is error of unsuitable partition space to install a rom.
Initially my partition was like this
system = 1242 MB (1.2GB)
system1= 100 MB
After google and reading most comment from partition thread, I found out there is three version of system partition size which is 730MB, 1242MB and 1337 MB.
I found that @audahadi partition script use
system = 1337 MB
system1= 5MB
Quote:
Originally Posted by audahadi
This Procedure May Will Brick Your Device!!!!!
Only for users who comfort with single partition layout only !!!
This is a script to partiton your system partition as like stated in OP. Tested with Clockworkmod recovery.
How to use? Just flash through recovery on either partition. Remember, this will wipe your system partition, do backup for safe or no if you like to live dangerously.
Repartition_MI3W_1_2GB.zip
Credit :
http://forum.xda-developers.com/show....php?t=2765846
http://forum.xda-developers.com/gala...-data-t2762594
Click to expand...
Click to collapse
So using that script, i have succeed install CM based rom.
sorry but could you please elaborate!! I don't get it.. how could I see my partitions?! and how can I change them?!
sorry for being noob.
Go to google play and install Disc Info app. You can see your partition
Sent from my MI 3W using XDA Forums
Can you give me the link for system = 1337 MB
system1= 5MB partition?
Here you go
http://forum.xda-developers.com/attachment.php?attachmentid=3321267&d=1432050198
Sent from my MI 3W using XDA Forums
Hi all,
I've made an attempt at installing CyanogenMod 12.1 (and later 12.0 to see if that would work) onto my GT-I8190T.
I've been following the instructions from http://forum.xda-developers.com/showthread.php?t=2400123, the only difference being I am using the clockworkmod for recovery.
After reaching step 11 (installing the rom). It will load and eventually fail. I've transcribed the messages that come onto the screen below.
Installing: /external_sd/os upgrade stuff/cm12.1_golden.nova.20150723.zip
Finding update package...
Opening update package...
Installing update...
Warning: No file_contextsdetected filesystem ext4 for /dev/block/mmcblk0p22
detected filesytem ext4 for /dev/block/mmcblk0p25
detected filesytem ext4 for /dev/block/mmcblk0p22
Then after a few minutes of installing it fails. Unfortunately the entire message is not left on the screen but what I do see is:
r:system_file:s0 failed: Operation not supported on transport endpoint
set_metadata_recursive: some changes failed
E:Error in /external_sd/os upgrade stuff/cm12.1_golden.nova.20150723.zip
(Status 7)
Installation aborted.
Any help or advice would be much appreciated thank you.
bails51 said:
Hi all,
I've made an attempt at installing CyanogenMod 12.1 (and later 12.0 to see if that would work) onto my GT-I8190T.
I've been following the instructions from http://forum.xda-developers.com/showthread.php?t=2400123, the only difference being I am using the clockworkmod for recovery.
After reaching step 11 (installing the rom). It will load and eventually fail. I've transcribed the messages that come onto the screen below.
Installing: /external_sd/os upgrade stuff/cm12.1_golden.nova.20150723.zip
Finding update package...
Opening update package...
Installing update...
Warning: No file_contextsdetected filesystem ext4 for /dev/block/mmcblk0p22
detected filesytem ext4 for /dev/block/mmcblk0p25
detected filesytem ext4 for /dev/block/mmcblk0p22
Then after a few minutes of installing it fails. Unfortunately the entire message is not left on the screen but what I do see is:
r:system_file:s0 failed: Operation not supported on transport endpoint
set_metadata_recursive: some changes failed
E:Error in /external_sd/os upgrade stuff/cm12.1_golden.nova.20150723.zip
(Status 7)
Installation aborted.
Any help or advice would be much appreciated thank you.
Click to expand...
Click to collapse
Had same problem yesterday but google told me that possible cause is outdated/old recovery kernel so I decided to update my old CWM to TWRP. From this recovery kernel I had no issues at all upgrading to CM12.1.
Tip: Never use CWM to flash Lollipop!