Hi
Nexus 7 is rooted and trying to update ROM...Stuck on Google logo screen at start-up..
Can get into cwm recovery.
Trying to put rom in storage so I can flash it.
In the mounts and storage menu when i select mount /sdcard...Nothing happens.
When i select mount /system...the name changes to unmount /system
I just need to access the storage so i can flash my rom
I cannot see the flash storage on my computer when I select mount /sdcard or /system
So I tried just pushing the rom from adb.
#adb devices
#adb mount /sdcard (command does not work)
#adb mount /system (command does not work)
#adb push SmoothROM-v4.1.zip /sdcard/SmoothROM-v4.1.zip (just get back " _ " No transfer rates or anything)
Please help me flash this ROM
Thank You
-----------------------------------------------------------------------
Ok I fixed it...I pushed the rom using qtadb....with that software i could see the filestructure...i pushed the file to /data/media (i think)...and i could find the zip from clockwork...rom just installed...works great...
Please can some clarify how the storage works in nexus 7? Where is the sdcard files? is it stored in /data/media ?
why did the adb mount command did not work?
Adb push (file name) /mnt/sdcard/(final directory of your choice)
Shouldn't need to mount anything
Somehow I managed to make it so my Nexus 4 can't mount internal sdcard. I've tried formatting it from CWM and everything, no luck.
What do I do to get a working phone again?
You can't use "mount /sdcard" with the N4 because it is the command to mount *external* sdcard
What are you trying to achieve?
If you're trying to flash a zip already in sdcard:
flash zip => 0 => your sdcard folder
to push to sdcard, use adb push filename /sdcard/0/filename
Sent from my Nexus 4 in a Faraday cage
Apparently using that command ("mount /sdcard") actually destroyed the mounting of it so it couldn't be mounted in CWM.
Only way to resolve was wiping /data
Hi,
well... what can i say... i bricked my beloved defy. =(
How it happened:
Since Quarx's CyanogenMod 7 i used several CyanogenMod Versions from Quarx und Epsylon until about 2 weeks ago. I had the CM10 (4.1.2) Version from 11.05. installed.
Then i saw Quarx new release from 16.06.
Before i flashed the new version i made a full backup with cwm 5.7.0. Then i installed the new version trough cwm. everything look fine. But there wen't something really wrong. After rebooting the phone got stuck even before 2ndinit. I tried it several times but the the phone wasn't booting any more.
I thought: no problem. I have a backup. Let's restore is quickly. The easiest way to me was:
- start the phone in bootloader
- flash a stock sbf with rsd lite (sbf: JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_UCAJRDNFRYORTCOREEU_P023_A008_HWp3_Service1FF.sbf
- root the phone with superoneclick
- install 2ndinit for defy (SndInitDefy_2.3.apk i think it's cwm 5.0.3.1)
- restore backup
but here the problem beginns trying to recover /system(log from recovery):
2013-06-17.15.18.36:
logo.img is present. 1024 kB
recovery.img is present. 8192 kB
devtree.img is present. 512 kB
boot.img is present. 8192 kB
data.ext3.tar is present. 1039389 kB
system.ext3.tar is present. 323612 kB
Checking MD5 sums...
./system.ext3.tar: OK
I:couldn't find default type
Found new backup image: /sdcard/clockworkmod/backup/2013-06-17.15.18.36//system.ext3.tar
Restoring system...
Skip system unmount, remount read-only
Remount /system read-only
I:/system is not safe to format
I:Erasing from device...
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
Skip system unmount, remount read-only
Remount /system read-only
50-cm.sh60-baseband.sh70-bootmenu.sh70-gapps.sh80-battd.shApollo.apkApplicationsProvider.apkAudioEffectSettings.apkBackupRestoreConfirmation.apkBluetooth.apkBrowser.apkCMFileManager.apkCMFileManagerThemes.apkCMWallpapers.apkCalculator.apkCalendar.apkCalendarProvider.apk
..... and so on and so on. (is quite a long list ).....
Error while restoring /system!
Problem while restoring system !
-------------------------------------------------------
i tried so many things like:
- install cm10 an try restoring with cwm 5.7.0 (same error)
- different stock sbf's (makes no difference)
- extracting system.ext3.tar and copying i to /system with adb (stops copying at about 50%)
and much much more... i forgot the rest ^^
the thing is.... i have no idea what exactly is going wrong. In my opinion it's here in the log: "Remount /system read-only". how should cwm be able to write the backup into system i it is mounted as "read-only".
im working on it since the last 2 weeks and it is getting super frustrating =(
Hopefully someone has better ideas than me? I would appreciate it.
At least: thanks for reading!
There are 2 possibilities according to me (I may be wrong:silly
1. Your backup might be corrupt -> try another backup
2. Your eMMC memory chip may be corrupt -> send your phone for service
TRY Wipe system cache and data then restore.
OR
Install CM10 with cwm (example 26 March build), restore only data, then dirty flash the latest CM10 (only wipe cache and dalvik). Old builds of CM10 can cause problems.
hotdog125 said:
There are 2 possibilities according to me (I may be wrong:silly
1. Your backup might be corrupt -> try another backup
2. Your eMMC memory chip may be corrupt -> send your phone for service
TRY Wipe system cache and data then restore.
OR
Install CM10 with cwm (example 26 March build), restore only data, then dirty flash the latest CM10 (only wipe cache and dalvik). Old builds of CM10 can cause problems.
Click to expand...
Click to collapse
Thank you for your answer!
I believe the backup files are ok. md5 is ok and the recovery log says: backup ok, but internal storage.... is weired.
Maybe a fried eMMC. But how? And buying a new phone is sadly way cheaper than service.
I wiped cache and data endless times. But no luck.
Is it possible to wipe (format) system?
I installed different versions from cm10 and they are running fine. But i really would like to restore my backup. There's a lot of work in it. =(
Tried this also 2 times: http://forum.xda-developers.com/showthread.php?t=1807899
But with this method, the phone won't boot up and got stuck in a bootloop. Can't even see the cm logo. An it makes no difference what version of CM10 is installed.
dediknight said:
Thank you for your answer!
I believe the backup files are ok. md5 is ok and the recovery log says: backup ok, but internal storage.... is weired.
Maybe a fried eMMC. But how? And buying a new phone is sadly way cheaper than service.
I wiped cache and data endless times. But no luck.
Is it possible to wipe (format) system?
I installed different versions from cm10 and they are running fine. But i really would like to restore my backup. There's a lot of work in it. =(
Tried this also 2 times: http://forum.xda-developers.com/showthread.php?t=1807899
But with this method, the phone won't boot up and got stuck in a bootloop. Can't even see the cm logo. An it makes no difference what version of CM10 is installed.
Click to expand...
Click to collapse
Yes, wiping system is important in this case. The option is present on the main screen of CWM.
hotdog125 said:
Yes, wiping system is important in this case. The option is present on the main screen of CWM.
Click to expand...
Click to collapse
I would like to format /system. But how? I can't find this option in cwm (5.7.0).
- Reboot system now
- Apply update from sdcard
- Wipe data/factory reset
- Wipe cache partition
- Install zip from sdcard
- Backup and restore
- Mounts and storage
- Advanced
- Power off
- Exit Recovery
- Go Back
It is possible to format some unmounted partitions in "Mounts and storage". But if i unmount /system there is only the option to "remount /system" but nothing linke "format /system".
dediknight said:
I would like to format /system. But how? I can't find this option in cwm (5.7.0).
- Reboot system now
- Apply update from sdcard
- Wipe data/factory reset
- Wipe cache partition
- Install zip from sdcard
- Backup and restore
- Mounts and storage
- Advanced
- Power off
- Exit Recovery
- Go Back
It is possible to format some unmounted partitions in "Mounts and storage". But if i unmount /system there is only the option to "remount /system" but nothing linke "format /system".
Click to expand...
Click to collapse
My bad. You can try Defy full wiper (DO NOT REBOOT AFTER FULL WIPE).
hotdog125 said:
My bad. You can try Defy full wiper (DO NOT REBOOT AFTER FULL WIPE).
Click to expand...
Click to collapse
Thank you very much. Sadly, it wasn't the solution to my Problem. But the error messages getting a bit clearer now ^^.
Here is the recovery log:
-- Installing: /sdcard/defy_fullwipe_ext3.zip
Finding update package...
I:Update location: /sdcard/defy_fullwipe_ext3.zip
Opening update package...
Installing update...
FULL WIPE FOR MOTO DEFYmount: failed to mount /dev/block/mmcblk1p21 at /system: Device or resource busy
mount: failed to mount /dev/block/mmcblk1p25 at /data: Device or resource busy
mount: failed to mount /dev/block/mmcblk1p24 at /cache: Device or resource busy
.
..
...
....
.....
......
.......
........
.........
..........
...........
***********
script result was [because /system got wiped]
Congrats, your ass is now wiped
!!Do not reboot now!!
If you do, you will have to flash an SBF
because /system got wiped
Install from sdcard complete.
2013-06-17.15.18.36:
logo.img is present. 1024 kB
recovery.img is present. 8192 kB
devtree.img is present. 512 kB
boot.img is present. 8192 kB
data.ext3.tar is present. 1039389 kB
system.ext3.tar is present. 323612 kB
Checking MD5 sums...
./system.ext3.tar: OK
I:couldn't find default type
Found new backup image: /sdcard/clockworkmod/backup/2013-06-17.15.18.36//system.ext3.tar
Restoring system...
Skip system unmount, remount read-only
Remount /system read-only
E:format_volume failed to unmount "/system"
Error while formatting device /system!
Problem while restoring system !
--End of log--
OK, somehow the devices are "busy" so the wipe script couldn't wipe. Although in cwm it said it was successful.
So i tried unmounting /system, /cache and /data before running the script. Here's what i got:
-- Installing: /sdcard/defy_fullwipe_ext3.zip
Finding update package...
I:Update location: /sdcard/defy_fullwipe_ext3.zip
Opening update package...
Installing update...
FULL WIPE FOR MOTO DEFYmount: failed to mount /dev/block/mmcblk1p21 at /system: Device or resource busy
mount: failed to mount /dev/block/mmcblk1p25 at /data: Invalid argument
mount: failed to mount /dev/block/mmcblk1p24 at /cache: Device or resource busy
unmount of /data failed; no such volume
script result was [because /system got wiped]
.
..
...
....
.....
......
.......
........
.........
..........
...........
***********
Congrats, your ass is now wiped
!!Do not reboot now!!
If you do, you will have to flash an SBF
because /system got wiped
Install from sdcard complete.
--End of log--
Is it possible to do something about the "busy" partitions. Whatever they're busy doing
Check out these threads, not sure they'll help - http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/.
AND http://forum.xda-developers.com/showthread.php?p=20707200
Your partitions may be in the wrong format.
EDIT - You can try starting from sbf, then installing your preferred CM10 release, and then extracting the backups into the respective directories using ES file explorer (only the files that you've changed).
EDIT 2 - Install CM10 with clockworkmod (not TWRP) and then go to bootmenu (press go back on the main screen of recovery), and then format system and data to ext4, and then try restoring backup. <------ try this first
why??
sir. i tried this 2 xperia ROM. my unit is OT 918n. i completed the installation of BRAVIA_LACV--Es_V4 & Xperia by Jarey..
why is it the screen wont work. i mean the touch panel. so i can setup the setting at 1st boot. why it wont work the touch panel??
and 1 thing. i backup 1st my phone before i follow this instraction. just keeping safe. and if i restore the backup it stock in the white alcatel with sounds. just in their always repeating it will not continue to the main menu. WHy? can you answer it please.
chawnix said:
sir. i tried this 2 xperia ROM. my unit is OT 918n. i completed the installation of BRAVIA_LACV--Es_V4 & Xperia by Jarey..
why is it the screen wont work. i mean the touch panel. so i can setup the setting at 1st boot. why it wont work the touch panel??
and 1 thing. i backup 1st my phone before i follow this instraction. just keeping safe. and if i restore the backup it stock in the white alcatel with sounds. just in their always repeating it will not continue to the main menu. WHy? can you answer it please.
Click to expand...
Click to collapse
You are in the wrong device forum.
Sent from my Nexus 7 using Tapatalk
:good::fingers-crossed:Thank you, i have a similar problem. My battery's Defy was completly discharge. Normaly, i plug my Defy, wait for 10 % charging, and i turn it on and i let the battery charging all night. But, i forgot to turn my defy on, and the morning when i turn it on, the cyanogen 7 logo bootloop.
I do a wipe system reset to factory, the defy turn on, and when i restore my backup, bootloop again.
I do what hotdog125 write, i was thinking its works, but it didn't.
I lost my data, :crying::crying::crying::crying: but i have a nice cyanogen 10 bootloop :laugh::laugh::laugh:
I finaly restore my defy with a backup do with recorvery when my phone make a bootloop.
I put cyanogen 7 and i found an application name Nandroid Manager http://forum.xda-developers.com/showthread.php?t=2044414 , 1,46 euros, that permit to restore all or a part of the backup you do.
I restore my apps, my sms, my mms, my call log etc... i want to keep. My contact was backup on my gmail account.
Like i saw it works, i put cyanogen 11 and redo the partial restore.
My defy was fine, and increased from mb525 to mb526 when i install Cyanogen 11.
I recommand when you have an android phone to root it, put an recorvery, put Nandroid Manager and backup with recorvery regularly, you could restore all your phone if you don't change your rom, or resotre partial data if you change your rom.
Thank you to your site.:laugh::highfive:
Just now after a reboot, I found that Google Play Service stops working. It happened quiet a few times before, so I decided to do what I always do - remove the Google Play Service and flash it again.
So I rebooted into recovery, removed gapps backup script under /system/addon.d using Aromafm, and tried to flash the latest CM nightly - and the flash failed with status 7.
Then I found that I can no longer boot into system, but I still have access to boot loader (fastboot) and recovery. So I begin to check what's wrong with my /system partition and found that once it's mounted, I can not umount it. At first I thought it's a file system problem so I tried to fix it with e2fsck - but I can't umount it so e2fsck won't work!
So I rebooted my phone again, executed e2fsck -cfy /dev/block/platform/msm_sdcc.1/by-name/system but it didn't show any error - it's like the file system is file but I just can't umount it for some reason I can not understand (If I try umount it, I'll get "invalid arguments")
Lucky enough there's nothing wrong with the secondary system partition (I have TDB enabled before and always been using system1) so I managed to flash the latest nightly to system2 and get my phone booted, but I still can't get access to system1
Anyone, help :crying:
Update
This is becoming weirder and weirder...
After a few days of usage, I did a lot modification to 2nd /system partition, I noticed that sometimes I got boot loop - if I connect the phone to my laptop and use adb logcat I can see the logcat loops forever. Using adb reboot can make my phone reboot and get into Android system.
So I powered off my phone, booted to recovery, and as I expected, the same thing happens to 2nd /system partition - it can be mounted with no problem, but I can not unmount it (except for power off the phone, of course)
I thought maybe there's something wrong with that partition, maybe bad block or whatever, so I copied the entire 2nd /system to 1st /system partition using dd - Then the 1st /system partition can't be unmounted as well.
Now I'm f_cked, so I decided to format 1st /system partition once again and start fresh, after format I went and try mount then unmount 2nd /system partition - now it can be successfully unmounted. I was shocked at the time that I thought something went wrong I acturally formatted both partitions, but turns out all data in 2nd /system partition is fine and the "can't unmount" issue is gone.
Now boot loop doesn't happen anymore, but I'm too afraid to do any more modifications to /system partition, therefore I have skipped a few nightly updates. I won't risk brick my phone until I can get my hands on a new one (It's just too hard to find a phone that has a great performance and not that freaking huge! Seriously, I would buy another Mi 2S if they still sell it.)
Does anyone know what could possibly happening here... I'm so confused...
Here is the comment chain on the Reddit post. I am /u/windexi.
I flashed BQL1 in Odin, using the options - Auto Reboot - Re-partition - F. Reset Time - Nand Erase All. It flashed successfully. I went to recovery, and wiped my /data, and cache partition. After running "adb sideload update.zip" however, when it starts to install after finishing the verification, it gives me the same error mentioned in the comment chain.
"failed to mount /dev/block/bootdevice/by-name/system at /system: Permission denied"
I think I was possibly given the wrong update.zip or something, or I am flashing the wrong file. I have currently been flashing this BLQ1 file for SM-G950U
Please help me out here, I'm at my wits end.
Did you flash QL1 for the U or U1?
joe3681 said:
Did you flash QL1 for the U or U1?
Click to expand...
Click to collapse
I believe for the U. Here is the link I was given...
Note the update.zip file needs to be placed in the micro sd card, not internal storage.
alvin612 said:
Note the update.zip file needs to be placed in the micro sd card, not internal storage.
Click to expand...
Click to collapse
I originally flashed the update.zip using adb sideload. But atm I am copying to a microsd to try that. I booted up the ROM and it looks like I am on BQL1, so I am on the correct ROM here.
alvin612 said:
Note the update.zip file needs to be placed in the micro sd card, not internal storage.
Click to expand...
Click to collapse
I tried using the SD Card and got the same error as before again
"failed to mount /dev/block/bootdevice/by-name/system at /system: Permission denied"
iamnotexisting said:
I tried using the SD Card and got the same error as before again
"failed to mount /dev/block/bootdevice/by-name/system at /system: Permission denied"
Click to expand...
Click to collapse
Sorry bud I don't know what's going on. Every time I messed up I just Odin back to stock and start over, haha, but I did back up what I wanted (call logs, SMS, apps) via Smart Switch. Hope this helps.