Hey All,
I've never had issues installing roms in the past, but now that I have encountered a problem it seems to be a big one.
I 'updated' from a nightly build of CM10.2 to the Milestone 1 version of CM10.2.
My phone booted after the update, but things were closing and not responding, so I decided to see if a reboot would solve some issues. It didn't.
Now my phone won't get past the boot screen. When I go into recovery, CWM states that it can't mount or open /sdcard, /cache/recovery/log, /cache/recovery/last_log.
I can't do anything.
In addition, adb won't find my device.
Any suggestions?
Thanks
Are you using the latest version of CWM?
I am not. I believe the version I have is 6.0.2.3.
I was thinking I would be able to sideload the newer version of CWM, but couldn't find a way to do that if ADB won't recognize the device.
I suggest flashing the update again just to be sure. You can flash a new recovery from the bootloader using fastboot.
Welp, I think it's a lost cause. Device is now non-responsive to anything. It's been plugged into the wall-charger for a few hours now... Any attempt to turn it on or get into bootloader results in a red LED notification.
Thanks for taking the time to respond!
Related
So I've been running MIUI 1.8.whatever for a few weeks and finally realized there hadn't been an update in a while. After discovering MIUI move into the 1.9.Xs I downloaded 1.9.16 and proceeded to update via CWM. While updating it told me 1.9.16 runs off the Gingerbread kernel. At that point I got worried since I had been running the Froyo kernel since I rooted my DX.
After the update I told it to reboot and now it gets stuck at the white M logo. I can boot into regular recovery but I CANNOT get my phone to boot into CWM recovery so I can run the backup!
I've tried every button combination with no luck. i've booted into regular recovery and selected reboot having read that it will boot back into CWM recovery. Needless to say that didn't work either. And lastly I tried running RSDLite to SBF the phone to .602 but since the phone can't fully boot up RSDLite doesn't see the phone.
That is where I am at and I seek the help and guidance of you much smarter folks to help me get my phone at minimum to CWM recovery.
PLEASE HELP!!!
Boot the phone into bootloader mode, then SBF.
Sent from my DROIDX using XDA App
I got it into bootloader mode now, but my computer isn't finding the OMAP drivers and the installation keeps failing. How can I get these drivers onto my computer? RSD isn't seeing the phone even in bootloader so these drivers seem to be the key.
You can find the drivers in this thread:
http://forum.xda-developers.com/showthread.php?t=1258599
Sent from my DROIDX using XDA App
I got RSDLite to see the phone. Now when I try to flash it, it makes it all the way to checking the checksums (which all pass) then tries to switch the phone to BP passthrough. It keeps failing to switch the phone to BP passthrough and now my phone will only boot to the Bootloader screen and says Code Corrupt. It'll let me run the flash again but RSDLite keeps failing at that BP passthrough switch.
Thats where i'm at now.
Try a different SBF file. I had problems like this when i tried to SBF once, but once I found the SBF file that works for me, its always worked since. (I've had to SBF like 6 times now haha)
will find an older sbf file and try that. Wil let you know.
Alright we've made progress! I was able to finally get the phone SBF'd to .602. Then I rocked the Pete's Droid Rooting program and all seemed to have gone smoothly... Except I cannot boot into CWM recovery at all! I've ensured ROM Manager has the correct flash for CWM installed, but when I click Reboot into CWM Recovery, it'll reboot normally. So I turned the phone off and held the Home + Power button to boot into regular recovery. I get the ! logo with the green android, but when I hit hte Search button nothing happens.
So now I'm rooted, but can't get to CWM Recovery to install ROMS.
What do you guys think?
Yeah, Reboot into Recovery from ROM Manager doesn't work for me usually either...in fact, I had to go into the Bootstrapper app, install the recovery again, and then hit Reboot Recovery. This is on Apex though, but can't hurt to try it.
Yea I finally got it figured out. Its been so long since I originally rooted my phone I forgot all about D2Bootstrapper. And I didn't read the how-to guide for updating to MIUI 1.9.16 so that was all on me.
I searched everywhere, but can't find the same problem as mine. I am stuck in the CW recovery screen, after rebooting times after times.
I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install (flash), I hold the power forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stack at the cw recovery screen. Help...
I love my nook and have a road trip coming up. It will be nice to watch a kid movie to keep the kids entertained.
Had you flashed CmWR into eMMC?
Check the ROM information on /dev/block/mmcblk0p2.... this sounds a LOT like the problem 12paq had...
http://forum.xda-developers.com/showthread.php?t=1495913
@Dizzyden, thanks for the tip.
I did repartition to 1g/5g awhile back. I am not sure where to start. 12paq tried many things, which one was the solution? Your rombackup.zip?
Many thanks....
@votinh
what do you mean? I am not using the N&O apps or OS. Pure CM9, therefore I guess it is flashed in eMMC. If not, please advice.
DizzyDen said:
Check the ROM information on /dev/block/mmcblk0p2.... this sounds a LOT like the problem 12paq had...
http://forum.xda-developers.com/showthread.php?t=1495913
Click to expand...
Click to collapse
how can I check this"Check the ROM information on /dev/block/mmcblk0p2"?
please advice.
I tried to adb shell the nook, but not devices found? please help.
Finally, with the help from the good people of this forum, I was able to restore back to B&N, and reflash CM9 from there.
Thank to you all.
Yesterday my nook color was working great. Today I turned the screen on and it hung. Now I'm having the above problem with it hanging at clockwork recovery.
I've got CM7.1 stable on there running from emmc.
can't get adb to recognize the device since it is in cwr... how did you do it?
chilimac02 said:
can't get adb to recognize the device since it is in cwr... how did you do it?
Click to expand...
Click to collapse
Install the google drivers for adb... if you are in CWR adb is enabled... just have to get the drivers loaded on your computer.
try this:
http://forum.xda-developers.com/showthread.php?t=958748
dumper1234 said:
I searched everywhere, but can't find the same problem as mine. I am stuck in the CW recovery screen, after rebooting times after times.
I have been updating the CM9 nightly for a while, didn't have any problem. But when I tried to flash 02-17 nightly, I messed up and in the middle of the install (flash), I hold the power forcing to reboot. Now, it keeps going loop back to the CW recovery screen every time I tried to reboot.
--
I tried to reinstall the whole thing with the boot-able sdcard, but didn't work. please help! someone?
I tried to wipe, reformatted the system, data, cash, boot. Still stack at the cw recovery screen. Help...
I love my nook and have a road trip coming up. It will be nice to watch a kid movie to keep the kids entertained.
Click to expand...
Click to collapse
It may be that your "boot to recovery" flag is set, and if so, it will always boot to that until it is cleared. When the cyanogenmod logo comes up hold the n button until the boot menu comes up. Then choose boot to emmc. If it works, go to ROM Manager and flash a new CWM Recovery to emmc.
Welcome to the nightmare I lived last week. Don't worry I woke up, was able to fully recover and forget the dream ever occurred.
I to tried to reformat to 1gb/5gb and ended up in the same boot loop.. If you are in the same spot I was, your boot partition got wiped out. And you may notice EMMC is gone.
After much searching I came across a file... Looking....Looking...Looking...
..........................Ah yes here it is. Here is what worked for me.
1. Boot to recovery (Should be easy at this point)
2. Format System, Data, and Cache.
3. Install the attached Zip file. (RecoveryFix.zip), this should recreate the Boot partition and fix the EMMC.
4. Reboot to recovery
5. Install favorite Rom or restore from backup.
6. Reboot to test.
Again this is what finally worked for me, and I went through a lot of trial and error to get there. I am guessing at your situation being exactly the same as mine.
PS. Ignore my since of humor if you need to.
Hey all! I've been lurking around XDA for years for various devices. I'm good with computers but newer to Android/Linux. And I don't have much of a programming background. I have done some installing of custom ROMS on a phone of mine and even dabbling in a kitchen some. So it's not totally foreign to me.
I've been reading about custom ROMS on and off for a few months thinking about installing a custom ROM. And then actually reading and researching it the last day or two. Since we're not going to get Jelly Bean I decided finally to update to a custom Jelly Bean ROM. I am finding all the information very unorganized and very spread out. And not very comprehensive. Which is making it hard to get a good grasp of everything. Things like what SKBs are and APX mode. And exactly what processes you need to take to install which ROMS. If you need to install a kernel or it does it automatically ect. Very confusing! I thought I had figured out enough to do it.
On my A500 I had the latest Acer ICS OTA update but rooted. I want to install the CM10 Jellytime ROM. I did a factory reset. Using AfterOTA v1.09 I installed first "Bootloader Ics v3.14.8+Thor v1.7.3". Then after that I changed to "Bootloader Ics v3.14.8+Recovery Twrp v2.1.3. It seemed to work fine. I got into the bootloader. I have the Jellytime ZIP file on my external SD card. The first time I think I just clicked install, picked the ZIP and did the swipe to install. Which brings me to my big question. What is it supposed to do after that? It just went back to the Recovery boot animation and back into the recovery without seemingly doing anything. If I rebooted holding the Vol-, it would just go into Recovery and not flash anything. If I just let it boot it would boot the factory ROM. The Thor recovery did something similar.
I then did the wiping/formatting of all of the cache, factory resets and system. And when I tried to install it again basically the same results. Except now it won't boot into the factory ROM since I wiped the system. Which will also not let it connect over USB and to the AfterOTA. If I turn it on holding the Vol+ and get the boot menu and pick the fastboot it tries to do the fastboot but just hangs on the Fastboot notification.
I've been searching and reading but can't figure out if I didn't do something I should have or missed a step. Any help would be appreciated.
Ah! I figured it out! I didn't realize that even though you're using a custom recovery program that you still have to name the ROM file "update.zip". I thought that might be the case but couldn't connect the tablet to the computer via USB and didn't have an SD adapter to connect the card to the computer and change the name. I ended up getting a card adapter. After I changed the name it worked.
briwayjones said:
Ah! I figured it out! I didn't realize that even though you're using a custom recovery program that you still have to name the ROM file "update.zip". I thought that might be the case but couldn't connect the tablet to the computer via USB and didn't have an SD adapter to connect the card to the computer and change the name. I ended up getting a card adapter. After I changed the name it worked.
Click to expand...
Click to collapse
great, thanks for posting your solution
So I flashed the latest nightly of CM10 onto my TF101. It was working well, nice and smooth... except I couldn't seem to install the Play store. I tried several different APK's including the latest one, and none of them seemed to work. The app would simply crash as soon as it started to load. So then I tried to flash in the Google Apps apk from this page. It seems to have replaced the entire CM10 build with that package, and since I'm such a genus with the greatest of ideas I had already deleted the CM10 zip file that was on my sdcard (because why would I EVER run into problems with flashing nightlies when I have so little experience doing so?)
So now my tablet is stuck in Clockwork MOD purgatory. It won't reboot into anything but CWM recovery, and I can't access the sdcard from my adb shell. Trying to push that CM10 zip file just results in a "protocol error."
Please help. I did want to replace this tablet with something newer, but I didn't want to do it this soon, nor did I want to lose the ability to sell this one or give it to a family member in need of a computing device.
Restore it to stock with Easy Flasher then start over. There's other ways to recover too, if you search the forums/google for "(tf101) recovery loop".
Lethe6 said:
Restore it to stock with Easy Flasher then start over. There's other ways to recover too, if you search the forums/google for "(tf101) recovery loop".
Click to expand...
Click to collapse
I started to try that, but for some reason I couldn't get into apx mode. It would just default into the CWM recovery when you press volume up. However, if you press nothing it seems to start a "cold boot" process which brought up CM10. The play store problem seems to be fixed though. The only problem is that if I don't hold the volume down button when I boot or reboot and let it "cold" boot, it goes right back into CWM recovery. I'm not sure if this will cause problems, but for now I can deal with it. I'll bring it back to stock and start all over with it if I start seeing any problems.
So thanks! Your advice helped, just not in the way you intended
Hello,
I was running CM7.2 but had an issue so I flashed back to the stock rom. Now I'm trying to flash a new custom rom but for some reason 2ndinit is not working.
I rooted and installed the recovery menu from 2ndinit, but I am not seeing a blue light on bootup.
The phone boots into the stock rom just fine, but I cannot get into the recovery menu.
Any help?
Problem
Cannot access ClockworkMod Recovery menu after installing 2ndInit
What I've tried
Wiped SD
Wiped Data
Reflashed JORDN_U3_6.36.0
Rooted
Installed 2ndinit 2.3
Still no luck, upon boot there is no LED. If I hold the down volume for the entire boot I am met with an android exclamation mark.
Update...
I was able to access an old version of CWM v2.5 using 2ndinit 2.0.
But that brings with it a new set of problems. When trying to access the SD card from CWM, it cannot mount it.
Using ADB and the commands in this forum (forum.cyanogenmod.com/topic/33179-problems-installing-71-recovery-cant-mount-sdcard/) I was able to mount the SD and install CM7.2.
Now I am having GPS and 3g connectivity issues with CM7.2 that I've never had before. It makes me wonder if that hack way of mounting the SD messed up the installation?
I am using the US T-Mobile 3.4.2-107-9 baseband.
Takkun88 said:
Hello,
I was running CM7.2 but had an issue so I flashed back to the stock rom. Now I'm trying to flash a new custom rom but for some reason 2ndinit is not working.
I rooted and installed the recovery menu from 2ndinit, but I am not seeing a blue light on bootup.
The phone boots into the stock rom just fine, but I cannot get into the recovery menu.
Any help?
Problem
Cannot access ClockworkMod Recovery menu after installing 2ndInit
What I've tried
Wiped SD
Wiped Data
Reflashed JORDN_U3_6.36.0
Rooted
Installed 2ndinit 2.3
Still no luck, upon boot there is no LED. If I hold the down volume for the entire boot I am met with an android exclamation mark.
Click to expand...
Click to collapse
Hi there. Any luck getting this to work, as i have the same issue.
I rooted the phone, then installed 2ndInit and when i reboot it has no blue light. When i run the Defy 2mdInit in android it lights up red, then goes green, so appears to be doing all right stuff.
A silly question but one i cant find a answer too, is how to reboot! Im holding down the power button, then selecting power off. Once off i power on again, now technically thats a cold restart. Is there a different method to rebooting/restarting once the green light is on?
Many thanks.
Twister42ZA said:
Hi there. Any luck getting this to work, as i have the same issue.
I rooted the phone, then installed 2ndInit and when i reboot it has no blue light. When i run the Defy 2mdInit in android it lights up red, then goes green, so appears to be doing all right stuff.
A silly question but one i cant find a answer too, is how to reboot! Im holding down the power button, then selecting power off. Once off i power on again, now technically thats a cold restart. Is there a different method to rebooting/restarting once the green light is on?
Many thanks.
Click to expand...
Click to collapse
If you just want to install a custom rom, like cm7 then you don't need to go through that process. You could try this method instead http://forum.xda-developers.com/showthread.php?t=1787541
Please note: This method does not work for BL7 bootloader.
pravarth said:
If you just want to install a custom rom, like cm7 then you don't need to go through that process. You could try this method instead http://forum.xda-developers.com/showthread.php?t=1787541
Please note: This method does not work for BL7 bootloader.
Click to expand...
Click to collapse
Hi There Pravarth.
Im completely new to all this, and this will be the first phone i mod. All i would like to do is install CM 10.2 (Android 4.3) and overclock to 1.0Ghz.
I know the Kernel needs to be changed to overclocking from what i read, so if i do the ROM update via this method, is there a option to overclock then too?
Is there a known issie with 2ndInit not doing the blue light on a reboot?
Many thanks.
Twister42ZA said:
Hi There Pravarth.
Im completely new to all this, and this will be the first phone i mod. All i would like to do is install CM 10.2 (Android 4.3) and overclock to 1.0Ghz.
I know the Kernel needs to be changed to overclocking from what i read, so if i do the ROM update via this method, is there a option to overclock then too?
Is there a known issie with 2ndInit not doing the blue light on a reboot?
Many thanks.
Click to expand...
Click to collapse
First of all, do you have a defy or defy+? Because some methods dont work for defy+
Then you should probably read this if you new to flashing: http://forum.xda-developers.com/showthread.php?t=1216982
I also suggest going from stock to cm7 and then cm10.2
Cm10.2 is overclocked to 1ghz by default. You dont have to do anything
pravarth said:
First of all, do you have a defy or defy+? Because some methods dont work for defy+
Then you should probably read this if you new to flashing: http://forum.xda-developers.com/showthread.php?t=1216982
I also suggest going from stock to cm7 and then cm10.2
Cm10.2 is overclocked to 1ghz by default. You dont have to do anything
Click to expand...
Click to collapse
Hi again.
I have a Defy with no moto blur and a red lens.
I have read a lot about flashing, and downloaded all the files i needed, rooted the phone then first problem came getting 2ndInit. I was having issues with the phone resetting when connected via usb so got the SndInitDefy_2.3.apk which runs fine, goes through all the steps, red light becomes a green light and says success. But then when i reboot it never shows the blue light.
Also a lot of these guides are Windows based and i dont use Windows i use Linux.
What are the benifits of going to CM10.2 via CM7, is there a reason for this?
Am i rebooting the correct way by doing a shut down then starting the phone again? Is there no way to do a hot reboot rather than a cold reboot?
Thanks again for your replies.
I don't know what went wrong, you should have been able to see the blue led. But, it's much easier to recover by flashing the easy recovery sbf. Then reboot to recovery and flash cm7. I say flash cm7 because the new cm10.2 has a newer version of update-binary so it wont flash successfully.
You need cm7 just for the CWM and bootmenu, from there you can flash cm10.2
You can use this method to flash sbf using linux http://forum.xda-developers.com/showthread.php?t=1076138
pravarth said:
First of all, do you have a defy or defy+? Because some methods dont work for defy+
Then you should probably read this if you new to flashing: http://forum.xda-developers.com/showthread.php?t=1216982
I also suggest going from stock to cm7 and then cm10.2
Cm10.2 is overclocked to 1ghz by default. You dont have to do anything
Click to expand...
Click to collapse
Hi.
I seem to be having more success now, i got SndInit1.4.apk and now it gives the blue light and im in the BootMenu!
So maybe the new version has some issues!
---------- Post added at 05:55 PM ---------- Previous post was at 05:01 PM ----------
Well im now ablle to at least get the bootmenu, however everything is there but it wont mount my sd card. Its shows the following..
ClockworkMod Recovery v2.5.1.8
E:Can't mount /dev/blocl/mmcblk0p1 (or /dev/blocl/mmnblk0)
(No such file or directory)
E:Can't mount /sdcard
Any ideas what is causing this problem?
I did try with another SD card, tried a smaller one thinking its a size issue, then formatted it too and same error message comes up.
Hope im giving enough info, but thats all i can see. Thanks again.
Twister42ZA said:
Hi.
ClockworkMod Recovery v2.5.1.8
E:Can't mount /dev/blocl/mmcblk0p1 (or /dev/blocl/mmnblk0)
(No such file or directory)
E:Can't mount /sdcard
Any ideas what is causing this problem?
I did try with another SD card, tried a smaller one thinking its a size issue, then formatted it too and same error message comes up.
Hope im giving enough info, but thats all i can see. Thanks again.
Click to expand...
Click to collapse
So, I'm guessing you flashed froyo, root and then sndinit? Did you try the easy recovery method?
While I've had similar issue before, I would just assume it was some bad flash and start over. Never wondered why it would happen. It is quite a pain. But most importantly, make sure the battery doesn't go low otherwise it wont allow you to flash.
Usually all such problems go away if you return to stock and try again
Here's what I usually do: Flash froyo stock + super one click to root + 2ndinitdefy2.0apk (It has the new version of CWM). Then flash cm7
OR
Flash froyo stock + easy recovery sbf. Then flash cm7 from stock recovery
Hope this works
Your link to everything about the Defy was very helpful and informative.
Im still on Eclair which seems like that might be the problem, so i guess i need to get Windows...i do have a old Windows XP so will find that old hard drive and boot into that then try the SDlite app and try install a stock 2.2 rom.
At the moment it has a French rom, in English though, so will try find a 2.2 French rom sbf. I think the issue might be 2.1 not being able to use the SD card like 2.2 and up does. Also 2ndInit v2.3 does not work, any other lower version does work, but gives a sd card error.
So my bext question, where do i get a standard 2.2 french rom? There is a link on here, but its the Orange version, not sure if that will be ok.
All i did was root, then 2ndInit. Rooting was a knightmare, eventually used the Motorola1Click Root and that worked, nothing else worked.
Thanks for all your help, knowing all the technical stuff is one thing, knowing all the orders, files and so on is another.