Related
Hello I'm new to the nexus line and recently upgraded form a SGS. my phone is Rooted, unlocked boot loader and running the most recent version of CWM 5.5.0.4. I'm running the GSM version of the Nexus.
My question is how do I flash the my first rom? When I boot into recovery and click install zip from SDcard i get "E: Can't mount /sdcard/" I am also unable to mound the data partition within. windows drivers are installed for both fastboot and adb so I can flash that way, i'm just wondering what the exact steps are and if that error mounting data is normal.
I also downloaded the most recent franco.Kernel as I want to run that, I know how to flash that with fastboot but wasnt' sure if that is how you would flash a rom with the nexus, on the SGS i used to use odin.
Thanks and sorry for the noobness.
How did you "unlock fastboot" and "root" and "install CWM"? Did you use one of the "Tool Kits"?
Do you have ROM Manager installed on your device?
yiannisthegreek said:
How did you "unlock fastboot" and "root" and "install CWM"? Did you use one of the "Tool Kits"?
Do you have ROM Manager installed on your device?
Click to expand...
Click to collapse
Sorry, Yes I have ROM Manager installed and its' paid for.
I unlocked my boot loader using fastboot oem unlock, I rooted by using an app because I couldn't mount the data partition in recovery so had to use some app some guy made that downloaded the su.zip from clockwork and flashed on it's own.
I installed CWM using fastboot.
fastboot flash recovery recovery.img
it's the dam data partition that i'm really having trouble with, i'm just wondering if this is normal, all the posts on the web say to flash a zip by choosing "choose zip from scard" but mine wont mount???
I should also mention that my entire device is encrypted.....that is whats causing it isn't it?
I'm not 100% sure but it could be that you flashed the wrong recovery.
According to this thread
http://forum.xda-developers.com/showthread.php?t=1357642
the recovery for the GSM version is 5.5.0.2 and not 0.4.
I would flash the correct recovery then try again.
You can not mount sdcard from CWM recovery (don't ask me why, I don't know.. maybe because it is not supported yet ..)
anyway, do like me, use CWM 5.5.0.2 and then try again toflash zip files .. It works for me
P4p3r1n0 said:
You can not mount sdcard from CWM recovery (don't ask me why, I don't know.. maybe because it is not supported yet ..)
anyway, do like me, use CWM 5.5.0.2 and then try again toflash zip files .. It works for me
Click to expand...
Click to collapse
He posted it on his Google+ account here:
https://plus.google.com/112476065271141473049/posts
I'm starting to think it's my encrypted phone, technically when I boot I have to decrypt the device before it boots into android.
I'm going to factory reset and see if that helps. I have a feeling that is what my problem is
OK so that was the problem, the data partition was encrypted (now that I think of this it makes sense that it wouldn't mount) anyways, for whatever reason a factory reset from android wouldn't work. I removed the "recovery-from-boot.p" file from my system folder originally so the CWM image would remain in tact.
anyways, I flashed the original recovery over the CWM recovery, preformed a factory wipe (which is the only way to decrypt your phone) then flashed CWM back on and now I can mount the data partition
what a pain in the ass, guess I wont be encrypting the phone any time soon, I wish there was an option to decrypt the drive and then get into recovery....wouldn't have this issue.
spectre85 said:
OK so that was the problem, the data partition was encrypted (now that I think of this it makes sense that it wouldn't mount) anyways, for whatever reason a factory reset from android wouldn't work. I removed the "recovery-from-boot.p" file from my system folder originally so the CWM image would remain in tact.
anyways, I flashed the original recovery over the CWM recovery, preformed a factory wipe (which is the only way to decrypt your phone) then flashed CWM back on and now I can mount the data partition
what a pain in the ass, guess I wont be encrypting the phone any time soon, I wish there was an option to decrypt the drive and then get into recovery....wouldn't have this issue.
Click to expand...
Click to collapse
It is possible now on 4.1.2 to decrypt the device. You must provide a password for dectypting (chane from unlock pin to passw).
I have an International version of Note 2 (N7100) rooted with CWM recovery 6.0.4.3 (touch) installed.
In order to analyze the wakelock problem (most of the time, the CPU is at 200Mhz rather than deep sleep when it is not used. Also "battery info" tells me the battery was mostly used by "Android OS"), I have to factory reset the device and flash to the stock 4.3 ROM. I monitored the newly setup phone for a day before I rooted it and install CWM recovery 6.0.4.3 for full system backup.
Happily used the phone for a week. After my son played with it for an afternoon, the wakelock problem comes back. Not sure what settings did he changed or apps he installed. So I go ahead backup the current rom and restore the phone from the previous backups.
Here was what I have done:
1. Boot into Clockworkmod recovery
2. Clear all partition / factory reset
3. Select Backup and restore.
4. Select the backup directory that I want to restore from (the one without wakelock problem)
5. Wait for the restoration process to finish
6. System reboots.
After system rebooted, it kept popping up "unfortunately com.google.process.gapps has stopped". The device was not usable, because the message will pop up again once I click OK to dismiss it. I then tried the following, but none of them works.
1. Restore from different backups
2. Enable "download service" from application manager. (It was not disabled)
3. Reset all apps settings from "Application manager" (menu)
Trying option 2 and 3 was a pain as the popup messages was blocking the screen, I have to be really quick to dismiss the message box and touch on the command.
BTW, the CWM recovery touch was installed from Odin, not from ROM manager. I experience the following problems:
1. Issue with "backup current ROM" command from "ROM manager". It cannot find /ex_sdcard when it goes to recovery.
2. It cannot find dalvik partition to wipe.
3. Backup to zip command does not work. It does backup the files and at the end it said the backup file is in /storage/sdcard/clockworkmod/image.zip. But I cannot find the zip file any where, including the external sd card.
Here is what I did to restore my phone to previous state with stock ROM:
1. Use Odin to flash the stock rom (samsung 4.3 for N7100), which will restore the stock recovery instead of the CWM recovery.
2. Reboot the device.
3. Use Odin to flash CWM recovery.
4. Reboot the device.
5. Go into recovery and restore only the /data partition.
6. Wipe /cache.
7. Reboot the device
8. Boot back to recovery and root the device.
Now I have the phone at my previous state.
Does it mean CWM recovery will not work with stock ROMs ? or I did something wrong.
Also, I still have not find out what was the cause for the wakelock problem in "Android OS". I have two backups where one has the problem and one does not. I have tried untar them and compare them with WinMerge, but there were a lots of files to go through.
fatice said:
I have an International version of Note 2 (N7100) rooted with CWM recovery 6.0.4.3 (touch) installed.
In order to analyze the wakelock problem (most of the time, the CPU is at 200Mhz rather than deep sleep when it is not used. Also "battery info" tells me the battery was mostly used by "Android OS"), I have to factory reset the device and flash to the stock 4.3 ROM. I monitored the newly setup phone for a day before I rooted it and install CWM recovery 6.0.4.3 for full system backup.
Happily used the phone for a week. After my son played with it for an afternoon, the wakelock problem comes back. Not sure what settings did he changed or apps he installed. So I go ahead backup the current rom and restore the phone from the previous backups.
Here was what I have done:
1. Boot into Clockworkmod recovery
2. Clear all partition / factory reset
3. Select Backup and restore.
4. Select the backup directory that I want to restore from (the one without wakelock problem)
5. Wait for the restoration process to finish
6. System reboots.
After system rebooted, it kept popping up "unfortunately com.google.process.gapps has stopped". The device was not usable, because the message will pop up again once I click OK to dismiss it. I then tried the following, but none of them works.
1. Restore from different backups
2. Enable "download service" from application manager. (It was not disabled)
3. Reset all apps settings from "Application manager" (menu)
Trying option 2 and 3 was a pain as the popup messages was blocking the screen, I have to be really quick to dismiss the message box and touch on the command.
BTW, the CWM recovery touch was installed from Odin, not from ROM manager. I experience the following problems:
1. Issue with "backup current ROM" command from "ROM manager". It cannot find /ex_sdcard when it goes to recovery.
2. It cannot find dalvik partition to wipe.
3. Backup to zip command does not work. It does backup the files and at the end it said the backup file is in /storage/sdcard/clockworkmod/image.zip. But I cannot find the zip file any where, including the external sd card.
Here is what I did to restore my phone to previous state with stock ROM:
1. Use Odin to flash the stock rom (samsung 4.3 for N7100), which will restore the stock recovery instead of the CWM recovery.
2. Reboot the device.
3. Use Odin to flash CWM recovery.
4. Reboot the device.
5. Go into recovery and restore only the /data partition.
6. Wipe /cache.
7. Reboot the device
8. Boot back to recovery and root the device.
Now I have the phone at my previous state.
Does it mean CWM recovery will not work with stock ROMs ? or I did something wrong.
Also, I still have not find out what was the cause for the wakelock problem in "Android OS". I have two backups where one has the problem and one does not. I have tried untar them and compare them with WinMerge, but there were a lots of files to go through.
Click to expand...
Click to collapse
I did not find the problem with restoration using CWM, but did find out what causes the wakelock: "Automatic call recorder Pro".
Disable the auto start function and battery drains is back to 1% per hour during standby.
fatice said:
I have an International version of Note 2 (N7100) rooted with CWM recovery 6.0.4.3 (touch) installed.
In order to analyze the wakelock problem (most of the time, the CPU is at 200Mhz rather than deep sleep when it is not used. Also "battery info" tells me the battery was mostly used by "Android OS"), I have to factory reset the device and flash to the stock 4.3 ROM. I monitored the newly setup phone for a day before I rooted it and install CWM recovery 6.0.4.3 for full system backup.
Happily used the phone for a week. After my son played with it for an afternoon, the wakelock problem comes back. Not sure what settings did he changed or apps he installed. So I go ahead backup the current rom and restore the phone from the previous backups.
Here was what I have done:
1. Boot into Clockworkmod recovery
2. Clear all partition / factory reset
3. Select Backup and restore.
4. Select the backup directory that I want to restore from (the one without wakelock problem)
5. Wait for the restoration process to finish
6. System reboots.
After system rebooted, it kept popping up "unfortunately com.google.process.gapps has stopped". The device was not usable, because the message will pop up again once I click OK to dismiss it. I then tried the following, but none of them works.
1. Restore from different backups
2. Enable "download service" from application manager. (It was not disabled)
3. Reset all apps settings from "Application manager" (menu)
Trying option 2 and 3 was a pain as the popup messages was blocking the screen, I have to be really quick to dismiss the message box and touch on the command.
BTW, the CWM recovery touch was installed from Odin, not from ROM manager. I experience the following problems:
1. Issue with "backup current ROM" command from "ROM manager". It cannot find /ex_sdcard when it goes to recovery.
2. It cannot find dalvik partition to wipe.
3. Backup to zip command does not work. It does backup the files and at the end it said the backup file is in /storage/sdcard/clockworkmod/image.zip. But I cannot find the zip file any where, including the external sd card.
Here is what I did to restore my phone to previous state with stock ROM:
1. Use Odin to flash the stock rom (samsung 4.3 for N7100), which will restore the stock recovery instead of the CWM recovery.
2. Reboot the device.
3. Use Odin to flash CWM recovery.
4. Reboot the device.
5. Go into recovery and restore only the /data partition.
6. Wipe /cache.
7. Reboot the device
8. Boot back to recovery and root the device.
Now I have the phone at my previous state.
Does it mean CWM recovery will not work with stock ROMs ? or I did something wrong.
Also, I still have not find out what was the cause for the wakelock problem in "Android OS". I have two backups where one has the problem and one does not. I have tried untar them and compare them with WinMerge, but there were a lots of files to go through.
Click to expand...
Click to collapse
I have to say, I did encounter the replication of the same exact problem. It kept popping up "unfortunately com.google.process.gapps has stopped". I was using the same CWM recovery 6.0.4.3 for my N7100 using stock android 4.3.
Try to do so many things but fail to get rid of the pop up. At the end, I ended up having to flash rom using Odin.
Anyway, I think, there's some bug with CWM recovery 6.0.4.3 that caused the error to happen. I managed to use TRWP 2.6.3.1 without any problem to restore after that.
Regards,
Had exactly same problem, i downgraded cwm from 6.0.4.6 to 6.0.4.4 by using odin
Than restore works fine no problems with services.
Note 3 sm-n900w8
warlab said:
Had exactly same problem, i downgraded cwm from 6.0.4.6 to 6.0.4.4 by using odin
Than restore works fine no problems with services.
Note 3 sm-n900w8
Click to expand...
Click to collapse
Hi.
How did you downgraded CWM using odin? I am stuck in the same problem.
Khizer Jalal
khizerjalal said:
Hi.
How did you downgraded CWM using odin? I am stuck in the same problem.
Khizer Jalal
Click to expand...
Click to collapse
Download image and overwrite existing one
Now i see that i have entered the rooting world in it's darkest time
I had the exact same problem of yours with CWM 6.0.4.3 and and the exact same problem with titanium backup(when i restore APP DATA for almost all apps they crash and keep popping messages). so there was no restore feature for me for long time
BUT TB restoring of App data is fixed when i updated TB to latest version and the CWM nandroid after-restore problem is fixed when yesterday i upgraded to philz 6.46.3, the restored ROM works flawlessly.
Now I think(not sure) what was going on is related to something called "FIX Permissions" or in other words when we restore system + data things get messed up that each app can't find it's own DATA folder causing it to crash. CWM and titanium backup didn't use to fix that mess but now they do so these problems won't occur anymore.
Hi guys,
Long time reader, and great help to be found I hope!
I just bought a Z1C, followed successfully the full DRM backup, full root process and bootloader unlocked, from the guide posted : http://forum.xda-developers.com/showthread.php?t=2642081
I took a full backup of DRM keys and Nandroid.
I then went to load the Resurrection Remix ROM. I booted in to PhilZ recovery and did a full wipe and factory reset - "Ready for ROM". This completed successfully.
I then realized I forgot to copy the Resurrection ROM files onto my external SD and cancelled/exit out of PhilZ Recovery.
Now when I power up, all I get is SONY logo. I assume this is because the phone has no operating system due to the ROM being wiped and nothing being installed in it's place.
I can confirm I can get into Fastboot mode (Blue LED, but connecting USB and holding UP volume button) but nothing else!!!
If anyone has any ideas, I would really really appreciate it!
thanks in advance!
... ok, so I found a quick fix, sorry for the alarm. I just used ADB to flashboot a version of CWM6 and made it boot into recovery, copied the Resurrection ROM onto my external SD with a card-reader (seperate) then installed the ROM ... hooray! Now I can sleep.
Thanks to anyone who started reading...
For future reference, just using fastboot to install a boot partition with a recovery on it is sufficient to fix these kinds of issues.
fastboot boot path/to/boot.img
or
fastboot flash boot path/to/boot.img
And for the record, with most recoveries you can mount your SDcard on your computer via USB, in CWM it is available in the mounts menu as "Mount USB storage"
Rekoil said:
For future reference, just using fastboot to install a boot partition with a recovery on it is sufficient to fix these kinds of issues.
fastboot boot path/to/boot.img
or
fastboot flash boot path/to/boot.img
And for the record, with most recoveries you can mount your SDcard on your computer via USB, in CWM it is available in the mounts menu as "Mount USB storage"
Click to expand...
Click to collapse
Thanks for the tips. I'm a bit new to this thing ... I assume your commands above will create a separate partition for booting, but how do I get to that recovery screen? ... and I assume boot.img is a recovery boot file? Renamed from CWM?
My issue above was I couldn't load up anything (Sony logo appears, and nothing else, couldn't proceed to recovery screen by pressing UP volume) ... I only could connect to my computer in flash mode for Flashtools to read, and had to start the whole "root my phone" process again.
I am playing around with the stock Sony UK ROM, but I am keen to flash Aura's AURom or maybe another one ... is there a way that I can basically create a "rollback point" so that if I don't like the new ROM I can re-instate what I am playing with now? I really don't want to have to go through the whole root process again if I semi-brick again! Just want to do an easy "undo" ...
Many thanks for putting up with the noob-ness.
boot.img is an image of the kernel. Note that this command is only for unlocked bootloader.
Seems you are using dualrecovery (which resides inside /system) and since you wiped /system you couldn't get into recovery anymore. If you have unlocked bootloader you should use a custom kernel. You can use the one of [NUT] (same functionality as dualrecovery) or the one from Doomlord.
I really don't want to have to go through the whole root process again
Click to expand...
Click to collapse
You do realize that the root process with unlocked bootloader is as followed:
1. Flash custom kernel
2. Go to recovery and flash SuperSU zip
zxz0O0 said:
You do realize that the root process with unlocked bootloader is as followed:
1. Flash custom kernel
2. Go to recovery and flash SuperSU zip
Click to expand...
Click to collapse
Exactly, and if you have saved your TA partition already, then you can always unlock the bootloader, root, and then relock bootloader by flashing your TA partition back.
Awesome, thanks guys for all the help. I will give the AURom a go and hopefully succeed this time.
One last question, what is contained in the TA backup, and what is in a Nandroid backup? From reading, TA is just a set of keys and Nandroid is a Rom backup?
TA backup is a backup of the Trim Area partition, inside of this partition there are DRM keys. Nandroid backup is a backup of various partitions (/system, /data/, etc.) but not TA partition.
zxz0O0 said:
TA backup is a backup of the Trim Area partition, inside of this partition there are DRM keys. Nandroid backup is a backup of various partitions (/system, /data/, etc.) but not TA partition.
Click to expand...
Click to collapse
Super thanks guys, much appreciated
First some details: M9, 5.0.2 w/ Sense 7, TWRP 2.8.6.1, S-Off. I have two nandroid backups on my micro SD card
I tried flashing the experimental xposed for 64 bit lollipop found [here](http://forum.xda-developers.com/xposed/xposed-android-5-1-successfully-t3074586). I waited 10 minutes but it never booted past the "HTC One Powered by Android" screen.
I booted into recovery and connected my phone to the computer. I was going to use adb but it couldn't detect the device in either bootloader, download, or recovery mode (yet it showed in Device Manager as HTC One), so I used windows file manager to place [this](http://forum.xda-developers.com/xposed/xposed-framework-disabler-incase-t3100669) on my sd card, which is supposed to disable xposed for lollipop, which I flashed in recovery. I tried booting again but no luck.
I went back to recovery, and decided to restore one of my backups. It always error-ed because it was mounted as read only, and I can't figure out how to change that in the Mount section of TWRP.
I found [this](http://www.theandroidsoul.com/htc-o...m-as-read-write-in-2-8-6-0beta-version-76248/) terminal command online "mount -t ext4 /dev/block/bootdevice/by-name/system /system", and after using it was able to restore one of my nandroid backups (I restored System, Boot, Data, and System Image). However, this did not let me escape the bootloop.
So I went back to recovery and intended to try again. I factory reset in recovery, and attempted to restore using that nandroid backup using just System, Data, and Boot. However, it wouldn't (mount problem). I executed the aforementioned terminal command again, and it still wouldn't let me restore (mount problem). So I entered the same terminal command again and it failed because "the device is busy."
I'm really at a loss for what to do right now.
How old are those nandroids? Did you do them with the 2.8.6.x betas? Some people have had trouble restoring nandroids from the betas in 2.8.6.1.
You might try reflashing your rom, or flashing a full stock firmware package.
leadCactus said:
First some details: M9, 5.0.2 w/ Sense 7, TWRP 2.8.6.1, S-Off. I have two nandroid backups on my micro SD card
I tried flashing the experimental xposed for 64 bit lollipop found [here](http://forum.xda-developers.com/xposed/xposed-android-5-1-successfully-t3074586). I waited 10 minutes but it never booted past the "HTC One Powered by Android" screen.
I booted into recovery and connected my phone to the computer. I was going to use adb but it couldn't detect the device in either bootloader, download, or recovery mode (yet it showed in Device Manager as HTC One), so I used windows file manager to place [this](http://forum.xda-developers.com/xposed/xposed-framework-disabler-incase-t3100669) on my sd card, which is supposed to disable xposed for lollipop, which I flashed in recovery. I tried booting again but no luck.
I went back to recovery, and decided to restore one of my backups. It always error-ed because it was mounted as read only, and I can't figure out how to change that in the Mount section of TWRP.
I found [this](http://www.theandroidsoul.com/htc-o...m-as-read-write-in-2-8-6-0beta-version-76248/) terminal command online "mount -t ext4 /dev/block/bootdevice/by-name/system /system", and after using it was able to restore one of my nandroid backups (I restored System, Boot, Data, and System Image). However, this did not let me escape the bootloop.
So I went back to recovery and intended to try again. I factory reset in recovery, and attempted to restore using that nandroid backup using just System, Data, and Boot. However, it wouldn't (mount problem). I executed the aforementioned terminal command again, and it still wouldn't let me restore (mount problem). So I entered the same terminal command again and it failed because "the device is busy."
I'm really at a loss for what to do right now.
Click to expand...
Click to collapse
I have created a guide to install xposed, its in the themes and apps section, called screen off animation.
---------- Post added at 01:54 PM ---------- Previous post was at 01:49 PM ----------
To get back to a functional ROM I would try to install a ROM which matches the firmware that you're on, perform a full wipe of data, android secure, cache and dalvic. You can use the file manager within twrp, also make sure your running the latest beta version of twrp.
You haven't bricked your device it will be recoverable..
Backup your nandroid, wipe everything (full internal storage data, cache, EVERYTHING). If that doesnt work, go to advanced wipe-> check everything and then click on repair as ext4
I admit it; I am totally confused by what S-ON and S-OFF allows/doesn't allow. I did read this, which was helpful, but it still not clear to me.
I know with S-ON that I can: (A) Unlock the bootloader; (B) add TWRP as the recovery; and (C) Flash a custom ROM. I know this because I have done all of these things.
But I don't know how to (if it is possible to) restore a TWRP backup. I tried and failed: when I hit "Restore" TWRP replied
Code:
Cannot restore System -- mounted read only
Am I supposed to mount the System read-write to restore my TWRP backup? Or is it just not possible?
I haven't bricked my phone (yet) -- though it won't boot into a TWRP-restored ROM either. I can get to download mode, recover, and the bootloader.
Yes you can restore a backup while S-on.
You need to uncheck the option to mount the system partition as read-only in TWRP. This can be found under the "Mount" menu.
Sent from my HTC 10
Thanks for the help! That's weird because that's what I did after TWRP said it couldn't restore the system because it is read only; I went to the Mount option and unchecked the box for
Code:
Mount system partition read-only
The restore succeeded in TWRP, but froze at the HTC white screen.
To fix from the HTC white screen I: (1) held down the power button and the down volume until the soft buttons flashed for 15 seconds, that brought me to download mode; (2) selected recovery with the arrow and power keys; (3) in TWRP I wiped everything but the drives and reinstalled a custom ROM (Viper); (4) booted; (5) once it booted into Viper, rebooted to recovery; and (6) used TWRP to restore just the Cache and the Data partitions. After that, all was as before except it wouldn't let me unlock (not at startup, after booting), saying "bad pin." So I had to reboot into TWRP and using ADB:
Code:
rm /data/system/locksettings.db && rm /data/system/*.key
Hopefully, it was just a one-off error. But at least I now know you can do it two ways.
Thanks again, this HTC world is a bit different.
Has the backup been your own one? Otherwise are you sure that the backup fits your firmware version, and you didn't have a bad download of the backup in case you got it from someone else!?
Sent from my HTC 10 using XDA Labs
5m4r7ph0n36uru said:
Has the backup been your own one? Otherwise are you sure that the backup fits your firmware version, and you didn't have a bad download of the backup in case you got it from someone else!?
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Thanks - yes, it was my own backup. I haven't tried again, as everything is working. But I'm hoping that it was just a flawed restore or, more likely, I hit an extra button somewhere that I don't remember.
Which TWRP version are you currently using? Maybe it's just bene a little stubborn.
Sent from my HTC 10 using XDA Labs
5m4r7ph0n36uru said:
Which TWRP version are you currently using? Maybe it's just bene a little stubborn.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
I'm on twrp-3.0.2-5. Hopefully that's right. I'll post back if it happens on my next restore. For now, I'm going to just enjoy the phone for a bit!