Hi all, this is my first time posting in XDA and I finally managed to brick my phone. Please help me The story goes as below :
1) I was using Slimbean 4.2.2 stable build 8, with the said CWM 6.0.4.7. and tried to reinstall the rom fresh from the original zip from slimroms website.
2) Did the usual wipe user data and cache partition
3) Wiped dalvik cache
4) I was curious and bravely decided to use the mounts and storage option. Browsed through the list and decided to format /system, /cache, /preload, /data, and /boot. Suddenly felt like something just went wrong, so stopped before the /modem section.
5) Thinking that I finally cleared my phone from all of the previous rom's files and such, went into install zip menu. Tried installing zip from sdcard1 (external).
6) CWM shows my external card properly. Selected the zip file. Wait. Phone reboots into CWM.
7) Thought I missed something, tried rebooting as usual. Directly went into CWM again. Pushed the button combination for download mode, went into download mode just fine.
8) Used CWM boot into bootloader mode menu, phone reboots into CWM again.
9) Tried using the "install zip from sdcard" menu. Phone reboots into CWM again.
10) Checked the log, it says
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found
I:Can't partition non mmcblk device: /devices/platform/s3c-sdhci.2/mmc_host/mmcl
Right now its 1 AM in the morning, and I have morning shift tomorrow. Please help me people The only probable solution left for me is installing Samsung original ROM using ODIN, hoping that everything will be set as usual again.
izhamznl said:
Hi all, this is my first time posting in XDA and I finally managed to brick my phone. Please help me The story goes as below :
1) I was using Slimbean 4.2.2 stable build 8, with the said CWM 6.0.4.7. and tried to reinstall the rom fresh from the original zip from slimroms website.
2) Did the usual wipe user data and cache partition
3) Wiped dalvik cache
4) I was curious and bravely decided to use the mounts and storage option. Browsed through the list and decided to format /system, /cache, /preload, /data, and /boot. Suddenly felt like something just went wrong, so stopped before the /modem section.
5) Thinking that I finally cleared my phone from all of the previous rom's files and such, went into install zip menu. Tried installing zip from sdcard1 (external).
6) CWM shows my external card properly. Selected the zip file. Wait. Phone reboots into CWM.
7) Thought I missed something, tried rebooting as usual. Directly went into CWM again. Pushed the button combination for download mode, went into download mode just fine.
8) Used CWM boot into bootloader mode menu, phone reboots into CWM again.
9) Tried using the "install zip from sdcard" menu. Phone reboots into CWM again.
10) Checked the log, it says
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found
I:Can't partition non mmcblk device: /devices/platform/s3c-sdhci.2/mmc_host/mmcl
Right now its 1 AM in the morning, and I have morning shift tomorrow. Please help me people The only probable solution left for me is installing Samsung original ROM using ODIN, hoping that everything will be set as usual again.
Click to expand...
Click to collapse
Your mistake was in step (4) you did everything right except format /boot you have wiped your boot img (bad mistake) connect to odin and flash stock again.
tallman43 said:
Your mistake was in step (4) you did everything right except format /boot you have wiped your boot img (bad mistake) connect to odin and flash stock again.
Click to expand...
Click to collapse
Thank you man. That did the job. I reflash stock rom using ODIN and it boot just fine. Gonna try flashing slimbean again tomorrow. Thanks for your help
izhamznl said:
Thank you man. That did the job. I reflash stock rom using ODIN and it boot just fine. Gonna try flashing slimbean again tomorrow. Thanks for your help
Click to expand...
Click to collapse
Glad to see it worked there was nothing wrong that you did apart from the last option /boot...I suggest you use PhilZ recovery it as a option in settings to "clean to install a new rom" which formats all the correct partitions for you..
tallman43 said:
Glad to see it worked there was nothing wrong that you did apart from the last option /boot...I suggest you use PhilZ recovery it as a option in settings to "clean to install a new rom" which formats all the correct partitions for you..
Click to expand...
Click to collapse
I used to use Philz recovery, touch version. But it seems to have something that I don't like back then, so I opted back to CWM. Maybe I should try Philz again. BTW, why does the mmcblk error comes out? Should I be worried. Because when I check the log now, it still occurs even though my phone is fully functional now.
Related
Hey guys. I just updated my Legend to the newest stable CM (with dalvik wipe, using ROM manager) and it freezes upon booting. I can get to recovery mode and I have ADB.
What do I do ? Is there a way to flash a ROM using ADB ?
It's been a long time since I worked with this stuff.
I don't think you can flash from ADB.
I suggest try to download the Cyanogen 7.1.0 rom again and check the MD5 after to make sure it is intact, I downloaded directly onto my phone then used ES file manager to check the MD5 # I had to download a few times because the MD5 # was not correct.
---------- Post added at 04:24 AM ---------- Previous post was at 04:21 AM ----------
grandioso said:
Hey guys. I just updated my Legend to the newest stable CM (with dalvik wipe, using ROM manager) and it freezes upon booting. I can get to recovery mode and I have ADB.
What do I do ? Is there a way to flash a ROM using ADB ?
It's been a long time since I worked with this stuff.
Click to expand...
Click to collapse
A quick question in your method, did you ONLY wipe the Davlik cache or did you wipe the system as well? I think you will have to wipe system & davlik when flashing a different rom.
How do I find out if md5 is correct or not ?
More importantly, what do I do after I donwload it ? It's not like I can do anything with the phone now, except get to recovery mode and control the phone via ADB in recovery mode.
And I only wiped dalvik cache.
I have help out someone with a similar issue here
http://forum.xda-developers.com/showpost.php?p=18597552&postcount=2
If you want to check MD5 # on the computer goto google and search for a MD5 file checker, ok you might want to know what MD5 is? its a check sum, the correct check sum is on the same page you downloaded on the cyanogen website.
if you know adb commands then you could always "push" the rom zip file to the sdcard on the phone, then flash it using CWM you'll need to wipe system and davlik at the very least.
First try to wipe data factory reset, wipe cache and wipe dalvikcache.
Reboot and it must be OK.
If it doesn't work download again cm7 stable, and flash it again with the 3 wipe.
I did a "clear storage" from HBOOT, but it didn't work.
When I get into recovery, I get a screen with a red exclamation mark. I guess that means I don't have CWM recovery. I have the files on my SD card, but htey have been copied from my previous one.
So I guess I'll need to flash CWM again...
You must have used fake flash to flash the rom correct?
Boot it into recovery and press the vol up button and the power button together ok?
It might give you an error once but press it again and again and you'll get into android recovery ok
Then go to install update.zip and cycle down to it using vol up and down buttons and the power button to select ok
Then it should load up clock work mod and you can use the trackpad now
Select mounts and storage and select mount SD card
Then connect USB and put the newly downloaded rom on your phone and once it's completed go back and go into advance settings I think... And do wipe cache and etc... Then go on install from SD and select your rom
Hope it helped
I flashed the ROM from ROM manager. I had CWM, but I don't anymore, because I changed SD cards. I have come to the point where I only need the goddamn update.zip file, but I can't find it anywhere and I think I'll go mad if I don't find it NOW
EDIT: Ok, I found it. At least I did a backup of my previous SD card....
Hi a newbie here.
Recently i flashed my S2 with I9100XXKI3 and rooted it with CF-Root(CF-Root-SGS2_XX_OXA_KI3-42-v4.2-CWM4).
I wanted to Install a custom ROM and I chose Villain ROM 3.0.
As i read in the forum,
Went to CWM recovery mode,
1. Wiped Data
2. Wiped Cache
3. Wiped Dalvik
4. Select 'Install ZIP from SD Card'
5. Select 'Choose Zip from SD Card'
6. Reboot
The phone rebooted. The phone dint bootup. It was in the starting screen.
After 15 mins i rebooted the phone and went to CWM recovery mode.
There i found the /sdcard /cache etc are not accessable.
It errors out saying unable to mount /sdcard.
Then i reflashed to stock via odin and the stock is working fine.
Please help me on this.
Also dont tell me to search the forum for answer as i already did with 0 answers.
I tried installing Lightening rom... same issue please i need somebody to help me....
Is it because of I9100XXKI3???
does anyone know about cwm? having some weird /cache issues... reminiscent of the eMMC problems on the HTC desire. Any help would be appreciated! (i use infectedrom nightlys, my restored version loads fine, latest version does NOT, and presents the issues below...)
I downloaded, wiped like normal, flashed... and then got a list of CWM errors... cannot mount /cache/recovery/xxxxxxxxx (5 of them). cannot open either.
mount /command
mound /log
open /log
mount /last_log
open /last_log
any ideas on what to do??
****edit***** so I restored. worked great. downloaded a new copy of r194. md5 match check. matched. wiped data/factory reset (passed on cache wipe option thinking maybe it would prevent this error)... seemed to flash okay. no /cache mounting error message after flashing. rebooted system. now my phone is stuck on the initial "htc" white loading screen that pops up first when booting. been stuck like this for around 5 minutes. normally a new flash loads much faster than this. battery pull. rebooted to recovery. same error message.
cwm3.1.0.2. been working for a couple months now. dunno what to do. restoring last working version until i figure out what to do. help plz!
Afaik, CWM 5.0.2.1 is the latest version. Maybe you must update that to flash the new ROM.
Maybe restore a working setup, and in ROM Manager, update CWM via the first option @ top of list in ROM Manager. Flash it (CWM Recovery) a couple times.
Also, in ROM Manager, menu, settings, erase recovery s/b checked.
Then make a backup of the working setup with the new cwm version, then do full wipe : factory reset, cache, dalvik, and system (in advanced) then flash new ROM.
There's this also :
http://forum.xda-developers.com/showthread.php?t=1179386
Sent from my HTC ThunderBolt using XDA Premium App
haha! thank you. had to use rommanager and update CWM. flashed like a charm after i updated. thanks!!
Hi Guys
Im having some problems trying to install a custom rom into my new Galaxy SIII I9300.
The rom in question is OmegaRom V35
After roooting and all, yesterday i tryed installing the rom with mobile odin, following all the instructions.
The result was the phone rebooted after the instalation seemed to be ok, but got stuck on the booting animation, and never got out of there.
I Had then to inject cwm with odin desktop, wiped data, cache anda dalvik, and then proceed to install the stock rom with desktop odin. All went well and the phone worked great.
I thought that maybe the problem was with mobile odin pro. So today, i went and proceeded to install Omega V35 via CWM. I again put the file on internal sd card, wiped data, cache and dalvik, and the rom started flashing. It all started good but, with no warning, at the mniddle of the installation, when applications were being installed, the phone went automatically and wuickly back to CWM!
Of course the installation wasnt finished, so i was stuck with cwm on reboot. Again made wipe data, cache and Dalvik, tried again to flash Omega V35, and again, the same problem...
In the end, i had to flash the stock rom again.
I searched the forum, but i cant seem to find the problem for this. I followed all the instructions, and had no error messages besides CWM skiping the format of the card, and some message (that i've seen in videos as normal), when wiping Dalvik!
Any clue to what's happening?
A clue read the instructions for the rom .
<b>Installation:Install CWM Recovery with Odin - Get CWM Recovery here
Boot to CWM Recovery using volume up, power button and home key
Backup your device and make sure to keep a copy of the backup to your pc!
Wipe data / factory reset (Not needed if you already have Omega)
Install Omega
(Wipe cache will be done automatically during installation so you can skip this step
Wipe dalvik cache will be done automatically during installation so you can skip this step)</b>
JJEgan said:
A clue read the instructions for the rom .
<b>Installation:Install CWM Recovery with Odin - Get CWM Recovery here
Boot to CWM Recovery using volume up, power button and home key
Backup your device and make sure to keep a copy of the backup to your pc!
Wipe data / factory reset (Not needed if you already have Omega)
Install Omega
(Wipe cache will be done automatically during installation so you can skip this step
Wipe dalvik cache will be done automatically during installation so you can skip this step)</b>
Click to expand...
Click to collapse
Maybe i didn't expressed myself correctly, but today i followed those instructions twice, and, at each of these tries the
same thing happened. When the flashing was running apparently problemless it simply stoped and went to CWM without rebooting.
rebentador said:
Maybe i didn't expressed myself correctly, but today i followed those instructions twice, and, at each of these tries the
same thing happened. When the flashing was running apparently problemless it simply stoped and went to CWM without rebooting.
Click to expand...
Click to collapse
Maybe The File Is Damaged Try To Download Again, Check MD5 Before Flashing
THE.W!ZARD said:
Maybe The File Is Damaged Try To Download Again, Check MD5 Before Flashing
Click to expand...
Click to collapse
I had already checked the md5, and the file is ok...
When you try to flash it through cwm recovery what error do you get while flashing?
Sent from my GT-I9300 using xda premium
Amritttt said:
When you try to flash it through cwm recovery what error do you get while flashing?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
None whatsoever. The flashing process seems to be running ok, It starts, i select default instalation, after i can see the apps being installed and suddenly, it all stops and goes into cwm without any message or warning...
Hi everyone, I have a problem with my phone.
It is no longer booting into the OS, instead it boots into the recovery mode.
So here's what happened. I was on Google Play Store looking for some utility apps, and found this "[ROOT] Rashr" app, read its details and got interested in it since I also do wanna try to back up my CWM Recovery. I don't even completely understand what it means, but as what the apps says, I really thought that with it, backing up my recovery will be very easy, just like how ROM is backed up when you do a NANDroid backup. So, after it was installed, I head on to its Back-Up section, ticked the box for "Recovery", and tapped on "Go", expecting that it would work. It said "Rebooting..." and booted to recovery mode, so I thought that I had to complete the "Recovery Back-Up" inside CWM, so I spent time looking through the options. And, this is where I discovered that CWM has a rainbow color mode. When I found out that no signs of back up could be done in CWM, I rebooted from within CWM. BUT, it still booted to Recovery Mode.
I tried . . .
Odin, but since it boots only to recovery, Odin isn't detecting it.
Wiped the data, cache partition, and Dalvik cache. Then restore.
Can this be fixed? I badly need help.
I have:
CWM Recovery v6.0.3.6 (used when I rooted the phone), updated to v6.0.4.5 (current)
Stock ROM 4.1.2
Recent NANDroid Backup
Any inputs will be very much appreciated. Thanks.
No intention of giving the "Rashr" app a bad name. I just didn't know how to use it.
Endroyed said:
My device is no longer booting into the OS, instead it boots into the recovery mode.
So here's what happened. I was on Google Play Store looking for some utility apps, and found this "[ROOT] Rashr" app, read its details and I got interested in it since I also do wanna try to back up my CWM Recovery. I don't even completely understand what it means, but as the apps says, I really thought that with it, backing up my recovery will be very easy, just like how ROM is backed up when you do a NANDroid backup. So, after it was installed, I head on to its Back-Up section, ticked the box for "Recovery", and tapped on "Go" with expecting that it would work. It said "Rebooting..." and it booted to recovery mode. And I thought that I had to complete the "Recovery Back-Up" inside CWM, so I spent time looking through the options. When I found out that no signs of back up could be done in CWM, I rebooted from within CWM. BUT, it still booted into Recovery Mode. Can this be fixed?
I have:
CWM Recovery v6.0.3.6 (used when I rooted the phone), updated to v6.0.4.5 (current)
Stock ROM 4.1.2
Recent NANDroid Backup
Click to expand...
Click to collapse
Flash Stock Revovery.
http://forum.xda-developers.com/showthread.php?t=2716953
Can Download From Here.
put into memory card.
and select install zip external-sd card select zip and flash it
Cheers!
manojkumar8552 said:
Flash Stock Revovery.
http://forum.xda-developers.com/showthread.php?t=2716953
Can Download From Here.
put into memory card.
and select install zip external-sd card select zip and flash it
Click to expand...
Click to collapse
I never thought the solution would be that simple. Hehe Thanks manoj. :good:
Finally fixed it!
What I did:
1) Flashed the stock Recovery. I was surprised it was able to boot to Android cause I was thinking that the zip is only the stock recovery. It had errors though. Home Screen won't appear or load.
2) When rebooted, it got stuck in SAMSUNG boot animation, but it was all good cause Odin was still able to detect it which means it can still be rooted. So . . .
3) Flashed CWM Recovery v6.0.3.6
3) Wiped data, cache partition, and Dalvik cache.
4) Restored the backup.
Endroyed said:
I never thought the solution would be that simple. Hehe Thanks manoj. :good:
Click to expand...
Click to collapse
No Problems Buddy !!!
Step by step getting all f,,,, Fundas of Android soon