Hi.
I'm trying to flash a new ROM on to my DX after being on the stock JB ROM.
Bootloader unlock went fine and the recoveries I've tried (TWRP 2.5.0.0 and CWM touch and non-touch versions) have all flashed fine.
But the recoveries aren't wiping or flashing properly even though they say the actions have been successful - factory reset/wipe works fine but I tried wiping /system/ and this had no effect, and neither does flashing a ROM - I've tried mySense, myOne and Fulmix and flashed the boot.img's with fastboot, but it has no effect on the phone - it just boots into stock with some of the apps from these ROMs added e.g. superSU. I can't get root on stock either.
Nandroid backups also fails immediately in all the recoveries I've tried.
The phone still works fine in stock at the moment.
In CWM there is an error which keeps appearing after actions and on boot:
Code:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
I followed the instructions from this thread, and my laptop is running Lubuntu 13.04 (I have an Ubuntu 13.04 Live USB and Windows 7 in a VM if required).
Thanks in advance for any help.
You're using JB recovery for ICS hboot or vice versa. Which hboot do you have? For versions 1.24 and lower use a recovery for ICS hboot, for version 1.25... use a recovery for JB hboot, there are several (Philz Touch or neXus TWRP), just take a look in Original Android Development Section.
dansou901 said:
You're using JB recovery for ICS hboot or vice versa. Which hboot do you have? For versions 1.24 and lower use a recovery for ICS hboot, for version 1.25... use a recovery for JB hboot, there are several (Philz Touch or neXus TWRP), just take a look in Original Android Development Section.
Click to expand...
Click to collapse
That was it. Thanks.
If I'm running ics can I just flash JB over it?
Sent from my HTC Desire X using xda app-developers app
imbtrthanu said:
If I'm running ics can I just flash JB over it?
Sent from my HTC Desire X using xda app-developers app
Click to expand...
Click to collapse
depends on hboot version
Related
Hi peeps
(I've tried looking for related posts but nothing comes up with my stuff)
I have downloaded Rom Manager Premium and also downloaded clockwork recovery, how ever every time I reboot into recovery to install i get this
E:failed to verify whole-file signature
E:signature verification failed
I have flashed the file before using Odin but i get other stuff saying E: cant mount (random stuff)
My phone is rooted
What am i doing wrong?
Rom Manager & CWRecovery don't work together on the SGS2. It's one or the other. For example, if you have CWRecovery installed (as a result of rooting your phone with a CFRoot kernel, for example), using Rom Manager has a tendency to break CWRecovery and/or put your phone into a bootloop.
So you're going to have to decide what you want to use.
Also
I have noticed I have Clockwork recovery once and I flashed a new ROM and i was left with the stock recovery. Is that normal too?
Depends what you used/did to flash the new rom. If you flashed it in CWRecovery, then that's unusual for it to be broken purely by flashing a custom rom meant for a I9100/T. Not completely unheard of mind you, but not usual.
If you used Rom Manager to flash the rom when you already had CWRecovery installed, then as per my previous post, it's obvious CWRecovery was broken by Rom Manager.
Again as per my previous post, one or t'other. Up to you. But use both at your peril.
olster said:
Also
I have noticed I have Clockwork recovery once and I flashed a new ROM and i was left with the stock recovery. Is that normal too?
Click to expand...
Click to collapse
So would you recommend that I remove ROM manager and just flash CW Recovery?
I wouldn't recommend you do anything/use one over the other. I'm just saying that you run the risk of having major problems (bootloop/broken CWRecovery) if you have both on your phone/try to use both.
Personally speaking, I've never had a problem rebooting my phone into CWRecovery every/any time I want to flash a rom/kernel/backup/restore.
Up to you which you use.
olster said:
So would you recommend that I remove ROM manager and just flash CW Recovery?
Click to expand...
Click to collapse
It looks like Im having problems with my boot recovery as I try to use clockwork its saying cant mount, even trying to access SD CARD.
Is there a way of clearing every thing and starting again?
Also when I use clockwork recovery
Anything I try to do i get this
E: can't mount /cache/recovery/command
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
What rom/kernel are you running and how did you root your phone ?
You could try flashing a CFRoot kernel from here, if that doesn't work you should probably get your stock firmware from here and flash that in Odin. After that you can use a CFRoot kernel to root your phone.
That will give you a clean slate with CWRecovery working.
Edit to add - Yes, you're getting that in CWRecovery because Rom Manager obviously broke it as I've already said.
olster said:
It looks like Im having problems with my boot recovery as I try to use clockwork its saying cant mount, even trying to access SD CARD.
Is there a way of clearing every thing and starting again?
Click to expand...
Click to collapse
I am using 2.3.6 XWKK5 ROM with the CF-Root-SGS2_XW_OXA_KK5-v5.0-CWM5.tar
Then try my suggestions in my previous post.
Right, I have managed to start again and got it working again.
Thanks your help
NP. Glad you got it working
olster said:
Right, I have managed to start again and got it working again.
Thanks your help
Click to expand...
Click to collapse
i unlocked my 3d using the HTC method as i have 1.5 hboot. I installed twrp 2.2 and tried to install the stock rooted 2.17zip but it says e:unable to mount /data and then when it loads up it gets stuck on a black screen right after the htc logo.
pbg225 said:
i unlocked my 3d using the HTC method as i have 1.5 hboot. I installed twrp 2.2 and tried to install the stock rooted 2.17zip but it says e:unable to mount /data and then when it loads up it gets stuck on a black screen right after the htc logo.
Click to expand...
Click to collapse
use 4EXT Recovery Touch and retry
Here is the story....
My Desire HD was rooted & S-OFF
It stayed in HTC opening screen when I flashed another ROM
So I found a RUU and flashed it...
and it still can't open (stay in "HTC" screen)
The strange things was that my phone still had CWM ,but the phone became S-ON
and the CWM had errors below...
----------------------------------------------------------------
ClockworkMod Recovery v2.5.1.2 (MoDaCo r2)
E:Can't mount CACHE:recovery/cmmand
E:Can't mount CACHE:recvery/log
E:Can't open CHCHE:recovery/log
----------------------------------------------------------------
I flash another ROM & RUU
even flashed another CMW (flash update.zip)
it still doesn't work....
Please help me
thank you!!!
wantommy said:
Here is the story....
My Desire HD was rooted & S-OFF
It stayed in HTC opening screen when I flashed another ROM
So I found a RUU and flashed it...
and it still can't open (stay in "HTC" screen)
The strange things was that my phone still had CWM ,but the phone became S-ON
and the CWM had errors below...
----------------------------------------------------------------
ClockworkMod Recovery v2.5.1.2 (MoDaCo r2)
E:Can't mount CACHE:recovery/cmmand
E:Can't mount CACHE:recvery/log
E:Can't open CHCHE:recovery/log
----------------------------------------------------------------
I flash another ROM & RUU
even flashed another CMW (flash update.zip)
it still doesn't work....
Please help me
thank you!!!
Click to expand...
Click to collapse
I'd head over to http://forum.xda-developers.com/forumdisplay.php?f=885 and ask there.. probably better chance at getting a quick bit of help..
I have been trying to get to JB for the past couple of days, but I think I've screwed something up and I'm not sure how bad.. After some frustration with my PC giving me an error when sending the JB boot.img, (which magically decided to work 10 hours later with an ICS boot.img) I wanted to get my phone back to the 4.1 ICS rom I was using with NAND backup (Tron 1.2). I got it to show the correct bootscreen. I loaded the boot.img with fastboot and it stayed on the boot screen for 30 mins.
I found out that my Amon Ra was old and I used "fastboot flash recovery" to update 3.15. Between the NAND restore and the Amon Ra update, I noticed that when I accessed recovery it would and still does pop up with this immediately.
RA Revamped
Build : RA-VIGOR-v.3.15 - getitnowmarketing
E: Can't mount /dev/block/mmcblk0p36
(file exists)
E: Can't mount CACHE: recovery/command
E: Can't mount /dev/block/mmcblk0p36
(file exists)
E: Can't mount CACHE: recovery/log
E: Can't open CACHE: recovery/log
E: Can't mount /dev/block/mmcblk0p36
(file exists)
From what I've read with similar errors on other devices, the internal memory is screwed up and I need a new device. whomp whomp. Not a huge deal ultimately, but I would love to avoid that and continue with this device. Any ideas?
Here's some extra info:
2.25.0000
1.22.10.0421r/1.22.10.0424r
mainver 1.00.000.0
JayToTheMo said:
I have been trying to get to JB for the past couple of days, but I think I've screwed something up and I'm not sure how bad.. After some frustration with my PC giving me an error when sending the JB boot.img, (which magically decided to work 10 hours later with an ICS boot.img) I wanted to get my phone back to the 4.1 ICS rom I was using with NAND backup (Tron 1.2). I got it to show the correct bootscreen. I loaded the boot.img with fastboot and it stayed on the boot screen for 30 mins.
I found out that my Amon Ra was old and I used "fastboot flash recovery" to update 3.15. Between the NAND restore and the Amon Ra update, I noticed that when I accessed recovery it would and still does pop up with this immediately.
RA Revamped
Build : RA-VIGOR-v.3.15 - getitnowmarketing
E: Can't mount /dev/block/mmcblk0p36
(file exists)
E: Can't mount CACHE: recovery/command
E: Can't mount /dev/block/mmcblk0p36
(file exists)
E: Can't mount CACHE: recovery/log
E: Can't open CACHE: recovery/log
E: Can't mount /dev/block/mmcblk0p36
(file exists)
From what I've read with similar errors on other devices, the internal memory is screwed up and I need a new device. whomp whomp. Not a huge deal ultimately, but I would love to avoid that and continue with this device. Any ideas?
Here's some extra info:
2.25.0000
1.22.10.0421r/1.22.10.0424r
mainver 1.00.000.0
Click to expand...
Click to collapse
upgrade to amon ra 3.16 and see if it helps:
link
place zip on root of sd card
rename it PH98IMG.zip
boot into hboot
accept the install
reboot phone
(remember to remove zip when you are done)
synisterwolf said:
upgrade to amon ra 3.16 and see if it helps:
link
place zip on root of sd card
rename it PH98IMG.zip
boot into hboot
accept the install
reboot phone
(remember to remove zip when you are done)
Click to expand...
Click to collapse
Thanks for replying. I did the update and it's giving the same errors.
Try wiping it under mounts. Worked for me.
Flyhalf205 said:
Try wiping it under mounts. Worked for me.
Click to expand...
Click to collapse
I'm sorry, I'm not quite sure what you mean. Are you talking about choosing "Wipe" and wiping cache or doing something under "Mounts"? Because I don't have an option to wipe anything under "Mounts".
I tried to wipe cache earlier but I get the same error plus:
Error mounting /cache/!
Skipping format...
/cache wipe complete!
To go ahead and put this out there, I get failures with "Wipe ALL data/factory reset"
Formatting DATA:....
E: Can't mount /dev/block/mmcblk0p35
(File exists)
Error mounting /data/!
Skipping format....
Formatting SDCARD:.android_secure...
Formatting INTERNALSD:.android_secure...
E: Can't mount /dev/block/mmcblk037 (or /dev/block/mmcblk0p38)
(Invalid Argument)
Error mounting /internal_sdcard/.android_secure!
Skipping format...
Formatting CACHE:...
E: Can't mount /dev/block/mmcblk0p36
(File exists)
Error mounting /cache/!
Skipping format
Skipping format of /sd-ext
Userdata wipe complete!
Running the ruu should fix your problem
Sent from my Nexus 7 using Tapatalk HD
Go into the stock ROM than go to settings than storage and erase the SD card in there and it should fix those partitions.
Edit: also 3.16 version of the recovery is out if you want to update it
Sent from my ADR6425LVW using xda app-developers app
dottat said:
Running the ruu should fix your problem
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
That did it, I'm on 4.2.2 now! Thanks a ton!
Help!
JayToTheMo said:
That did it, I'm on 4.2.2 now! Thanks a ton!
Click to expand...
Click to collapse
I am having this issue. I have tried running the RUU from my computer and it is not solving the problem. It keeps giving me an "Error 155:Unknown"
Insydr4God said:
I am having this issue. I have tried running the RUU from my computer and it is not solving the problem. It keeps giving me an "Error 155:Unknown"
Click to expand...
Click to collapse
Can you download the 605.12 version in the PH98IMG format and then put that on your SD card and boot into hboot ?
Androidpolice has a link to the ph98img version of the ruu....that will take the PC out of the loop for you and let the phone take care of the update.
Sent from my Nexus 7 using Tapatalk HD
I have an unlocked bootloader. According to the Android Police article I found it will not flash with a locked bootloader. I think I also have Amon Ra installed as that is what I used to root in the first place.
Insydr4God said:
I have an unlocked bootloader. According to the Android Police article I found it will not flash with a locked bootloader. I think I also have Amon Ra installed as that is what I used to root in the first place.
Click to expand...
Click to collapse
so relock and flash it. have you tried yet?
For what it's worth.. i didn't relock my bootloader and simply flashed it. I then re-flashed recovery and used a ph98img file to change my hboot back to the modded 2.27 version (I am s-off so the phone simply doesn't care anymore).
Insydr4God said:
I have an unlocked bootloader. According to the Android Police article I found it will not flash with a locked bootloader. I think I also have Amon Ra installed as that is what I used to root in the first place.
Click to expand...
Click to collapse
It's the opposite of that. You need to be locked to run an RUU. Amon Ra won't matter to run an RUU, once you have run it you will have stock recovery and stock ROM. Then you can unlock again and flash Amon Ra or TWRP.
Also, be very patient when you run it. It should run through twice - it goes to a black screen for a bit then goes back to bootloader and goes through the updating process again. It will let you know when it's done, could take up to 15 min or so.
I tried relocking and flashing the build with the global update. I haven't had a chance to download the previous build to see if it works. The 4.0.x build told me that boot was older. Before trying to root again I had downloaded all the OTA updates. I am in so far over my head.. LOL
Insydr4God said:
I tried relocking and flashing the build with the global update. I haven't had a chance to download the previous build to see if it works. The 4.0.x build told me that boot was older. Before trying to root again I had downloaded all the OTA updates. I am in so far over my head.. LOL
Click to expand...
Click to collapse
If it makes you feel any better I'm in the same boat with the sd card, i've tried the ruu, the sd patch from other threads, formatted the card to fat32 on the pc and still no luck. The Infected 2.5 Rom runs great though just cant get the sd card to show up.
blueblazer96 said:
If it makes you feel any better I'm in the same boat with the sd card, i've tried the ruu, the sd patch from other threads, formatted the card to fat32 on the pc and still no luck. The Infected 2.5 Rom runs great though just cant get the sd card to show up.
Click to expand...
Click to collapse
Are you sure its not a hardware issue? Sorta sounds like it if hboot doesn't see the sdcard either. Did you try a different card?
Well...before I tried that I must have done something wrong while trying to fix that so now I can't get past the boot loader lol, so working on that now, just gonna try to get it all back to stock and start over.
Sent from my Nexus 7 using Tapatalk 2
Hello Everybody,
my boss got me a Galaxy ACE S5830i in order to test some app development and I immediately managed to root it and install a custom ROM.
These were the steps I took
1- I flashed the update.zip I found around the web, for example here -> http://www.theandroidroot.com/root-install-cwm-recovery-samsung-galaxy-ace-s5830i/
2- I flashed CWM 5.0 and immediately, without rebooting, saw the new Recovery. So it really did install!
3- I updated to CWM 6
4- I flashed thunder kernel in order to make the CWM permanent -> http://forum.xda-developers.com/showthread.php?t=2335947
5- I rebooted the phone in recovery mode and got the CWM. Everything was fine up to now
6- I flashed a ROM (after wiping everything). Actually, several roms. I tried first with CGM, then with Aroma and Retribution Beta. http://forum.xda-developers.com/showthread.php?t=1806471 All of them managed to install but none of them works. What ALWAYS happens is that the ROM installs, then I reboot and the phone does not go past the Samsung Logo. Then, and here we come to the weirdest part, when I reboot in recovery mode in order to flash another rom... I get the stock recovery! No CWM, no customizations!
What's happening, in your opinion? I tried to flash a custom ROM with Odin as well, but being on Linux I had to use JOdin and could not manage to flash anything because (as it ALWAYS happens with JOdin) I was not able to load a suitable PIT file. No success with wine+odin as well.
Please, could somebody help me? I can't use my boss phone, and can't return it to him until I get a working ROM on it
Thank you in advance
P.S. When I get to the Recovery I see some rows to the bottom:
-- Appling Multi-CSC --
E:failed to mount /system (Invalid argument)
E:failed to mount /system (Indalid argument)
and (I know 'cause I tried) I can't mount or format the /system partition. Maybe it's related, maybe it's not...
ilsecondodasinistra said:
Hello Everybody,
my boss got me a Galaxy ACE S5830i in order to test some app development and I immediately managed to root it and install a custom ROM.
These were the steps I took
1- I flashed the update.zip I found around the web, for example here -> http://www.theandroidroot.com/root-install-cwm-recovery-samsung-galaxy-ace-s5830i/
2- I flashed CWM 5.0 and immediately, without rebooting, saw the new Recovery. So it really did install!
3- I updated to CWM 6
4- I flashed thunder kernel in order to make the CWM permanent -> http://forum.xda-developers.com/showthread.php?t=2335947
5- I rebooted the phone in recovery mode and got the CWM. Everything was fine up to now
6- I flashed a ROM (after wiping everything). Actually, several roms. I tried first with CGM, then with Aroma and Retribution Beta. http://forum.xda-developers.com/showthread.php?t=1806471 All of them managed to install but none of them works. What ALWAYS happens is that the ROM installs, then I reboot and the phone does not go past the Samsung Logo. Then, and here we come to the weirdest part, when I reboot in recovery mode in order to flash another rom... I get the stock recovery! No CWM, no customizations!
What's happening, in your opinion? I tried to flash a custom ROM with Odin as well, but being on Linux I had to use JOdin and could not manage to flash anything because (as it ALWAYS happens with JOdin) I was not able to load a suitable PIT file. No success with wine+odin as well.
Please, could somebody help me? I can't use my boss phone, and can't return it to him until I get a working ROM on it
Thank you in advance
P.S. When I get to the Recovery I see some rows to the bottom:
-- Appling Multi-CSC --
E:failed to mount /system (Invalid argument)
E:failed to mount /system (Indalid argument)
and (I know 'cause I tried) I can't mount or format the /system partition. Maybe it's related, maybe it's not...
Click to expand...
Click to collapse
can u get temporary cwm recovery when selecting
'apply update from sd'
then look at this thread
forum.xda-developers.com/showthread.php?t=1118688
as9333 said:
can u get temporary cwm recovery when selecting
'apply update from sd'
then look at this thread
forum.xda-developers.com/showthread.php?t=1118688
Click to expand...
Click to collapse
Hello,
thank you for answering.
I can temporary get to CWM recovery for sure, but I don't know how to push the erase_image file (that I found) to the device. I'm only able to copy files on the SD, using another phone, and then flash them from CWM. Is there a way to make adb able to detect the device even when it's in recovery?
Thank you
ilsecondodasinistra said:
Hello,
thank you for answering.
I can temporary get to CWM recovery for sure, but I don't know how to push the erase_image file (that I found) to the device. I'm only able to copy files on the SD, using another phone, and then flash them from CWM. Is there a way to make adb able to detect the device even when it's in recovery?
Thank you
Click to expand...
Click to collapse
First try to flash another rom..if that not work then flash stock rom from odin..
Here is the link for unbrick your device.go here and try to unbrick..
http://forum.xda-developers.com/showthread.php?t=1840645
Sent from my GT-S5830i using Tapatalk 2
Are the ROMs you tried based on CM7/9? Because if they are, you need to format your system partitions to EXT4. You can do that with the multi-formatter.
Also, you say that you have your stock recovery back. Check the ROM zips that you flashed for any boot.img. If there is, check which kernel and which version. Some older kernels still have stock recovery.
As even stock recovery cannot mount /system, clearly your system partitions are corrupt. Format with the multi-formatter and flash a CM7/9 based ROM or flash back stock firmware via Odin.
If you choose the multi-formatter, remember to flash a kernel afterwards. And if you prefer, one with a permanent CWM.
Sent because I <3 Aerith