Related
I have 2 nook colors one for me and one for my girlfriend, I am/was running CM 7 on them. Its been awhile since ive updated them. Ive tried the newest nightly and the latest STABLE release. Both got hung up on the same spot. The green CM logo will say its loading then it will go into a black screen lit by the backlight and just hangs there. no boot animation, no boot loop. Just sits there. Or It will just reboot itself back into clockwork after saying it installed the rom. Ive used the CWM removal and that made it just hung on a nook bootup screen.
Ive let it sit for 15 minutes and nothing. Im not new as ive rooted my og droid, my dx and 2 nook colors. I havent really had this issue with the nooks. not really sure what to do. Ive wiped data/cache formatted the symsted, data and cache and nothing.
My steps are as follows.
1)Download either Phiremod test 7 or ANY CM nightly
2) plug my data sdcard into my computer and transfer
3)boot into clockwork
4)Wipe pretty much everything (I also tried installing on top of the stable releases)
5)Install.
I know to expect issues but there HAS to be something im doing wrong that lets one nook install flawlessly and another nook that wont install any nightly or test build. If it didnt boot up they wouldnt leak the nightly. Its something on my end. I gotta figure it out
I also just went back to stock and re-rooted and I have the same issue
oman0123 said:
I have 2 nook colors one for me and one for my girlfriend, I am/was running CM 7 on them. Its been awhile since ive updated them. Ive tried the newest nightly and the latest STABLE release. Both got hung up on the same spot. The green CM logo will say its loading then it will go into a black screen lit by the backlight and just hangs there. no boot animation, no boot loop. Just sits there. Or It will just reboot itself back into clockwork after saying it installed the rom. Ive used the CWM removal and that made it just hung on a nook bootup screen.
Ive let it sit for 15 minutes and nothing. Im not new as ive rooted my og droid, my dx and 2 nook colors. I havent really had this issue with the nooks. not really sure what to do. Ive wiped data/cache formatted the symsted, data and cache and nothing.
My steps are as follows.
1)Download either Phiremod test 7 or ANY CM nightly
2) plug my data sdcard into my computer and transfer
3)boot into clockwork
4)Wipe pretty much everything (I also tried installing on top of the stable releases)
5)Install.
I know to expect issues but there HAS to be something im doing wrong that lets one nook install flawlessly and another nook that wont install any nightly or test build. If it didnt boot up they wouldnt leak the nightly. Its something on my end. I gotta figure it out
I also just went back to stock and re-rooted and I have the same issue
Click to expand...
Click to collapse
You probably have the wrong bootloader and kernel...the newest cm7s are based on the 2.6.32, not the older 2.6.29 (or something), and the newest 1.2 bootloader..which you probably don't have if it's "been awhile"..lol...You have to upgrade your Cwm first, from 3.0.1.0 to 3.0.2.8, I think, then flash your Cwm to a nightly after 86??(Google to check), and it will change your boot partition to the correct one...If your nook still says "touch the future", you're on the wrong bootloader.....Also, quit using Phiremod.....it's a copy of Cm7 first of all, but by the time it's released, it's already outdated, it's not updated like it should be, and it's Douchey. Google the basics of what I described above if it sounds like that might be your problem and lmk how it works out for you....Btw....I used nightly 106 for this exact thing on another of my Nooks a few days ago and it worked flawlessly...There are newer nightlies out, but that one for sure worked.....
Sent from my NookColor using Tapatalk
I might be confused; Is one of your Nooks OK or are they both refusing to boot anything based on the .32 Linux kernel?
As I read it you aren't having trouble loading either with 7.0.3 stable. Correct?
The only thing I could suggest is loading the stable version, downloading the latest nightly CM (skip Phiredrop's theme for now) DIRECTLY to the SD card (skip the computer step), and do a factory reset and format boot, system, data, and cache (all four).
Load just the nightly and gapps (save the OC kernel for later), and then see if THAT boots all the way up.
Of course make sure you have a full backup of the stable OS install before you start.
If none of that works, then prepare the SD card as an install card and try that. Do you have just the one card?
Thanks for the replies....I thought 3.2.0.1 was the newest clockwork? I guess I need to pay more attention to the nook. lmao Mazook I think you are on the right track. Also to the phiremod is that the og droid equivalent to UD? hahahaha I actually liked the look of phiremod but i digress...
On that note I installed the uboot 1.2 and flashed it and it still boots into clockwork but that maybe because I may be on an outdated cwm im the one i stated above
DiDGR8 said:
I might be confused; Is one of your Nooks OK or are they both refusing to boot anything based on the .32 Linux kernel?
As I read it you aren't having trouble loading either with 7.0.3 stable. Correct?
The only thing I could suggest is loading the stable version, downloading the latest nightly CM (skip Phiredrop's theme for now) DIRECTLY to the SD card (skip the computer step), and do a factory reset and format boot, system, data, and cache (all four).
Load just the nightly and gapps (save the OC kernel for later), and then see if THAT boots all the way up.
Of course make sure you have a full backup of the stable OS install before you start.
If none of that works, then prepare the SD card as an install card and try that. Do you have just the one card?
Click to expand...
Click to collapse
Ive tried all of that. hopefull mazooks way works. Otherwise im out of ideas
oman0123 said:
Thanks for the replies....I thought 3.2.0.1 was the newest clockwork? I guess I need to pay more attention to the nook. lmao Mazook I think you are on the right track. Also to the phiremod is that the og droid equivalent to UD? hahahaha I actually liked the look of phiremod but i digress...
On that note I installed the uboot 1.2 and flashed it and it still boots into clockwork but that maybe because I may be on an outdated cwm im the one i stated above
Click to expand...
Click to collapse
If I remember correctly, you can't just jump from 3.0.0.6 or 3.0.1.0 to newest...there's one in between that transitions the upgrade in bootloaders...I'm pretty sure I went 3.0.1.0 to 3.0.2.8 to flashing Cm7 nightly 106...then to upgrade to Cwm 3.2.0.1 while in Rom manager, while using Cm7....leSigh....Clockworkmod is the only thing I can't stand about using my Nook....(though I rarely need it any more) AmonRa is such a better (and fully functional) recovery build...One thing I wish we had gotten.....
Sent from my NookColor using Tapatalk
What I did was....
back to stock today.
re-rooted.
installed Rom manager
Flashed Clockwork
It gave me 3.0.2.1
I searched for 3.0.2.8 and got posts back in december. Which one is it that i want?
oman0123 said:
What I did was....
back to stock today.
re-rooted.
installed Rom manager
Flashed Clockwork
It gave me 3.0.2.1
I searched for 3.0.2.8 and got posts back in december. Which one is it that i want?
Click to expand...
Click to collapse
While in Rom Manager, go to "flash older clockworckmod recoveries ".....then choose 3.0.2.8 (Make a nandroid first) and have all the stuff you want to flash ready to go on the SD...then go into recovery from Rom Manager, which will put you in 3.0.2.8......if that doesn't do it, try the same thing again, but go to 3.0.1.0 first....then, once you get into a working cm7 with 3.0.1.0, try it all again.(upgrade to 3.0.2.8 by" try it all again" , but this time from 3.0.1.0)...you're basically trying to reinstall your boot partition, but in a different location than where it is now...its a hassle, but you can do it through just rom manager.....it's just a hassle...
Sent from my NookColor using Tapatalk
mazook98 said:
While in Rom Manager, go to "flash older clockworckmod recoveries ".....then choose 3.0.2.8 (Make a nandroid first) and have all the stuff you want to flash ready to go on the SD...then go into recovery from Rom Manager, which will put you in 3.0.2.8......if that doesn't do it, try the same thing again, but go to 3.0.1.0 first....then, once you get into a working cm7 with 3.0.1.0, try it all again.(upgrade to 3.0.2.8 by" try it all again" , but this time from 3.0.1.0)...you're basically trying to reinstall your boot partition, but in a different location than where it is now...its a hassle, but you can do it through just rom manager.....it's just a hassle...
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Well Id love to try that but.....My nook wont turn on. It was fully charged today. Im either gonna make a bootable cwm or go back to stock and root again. I dont know if that will work though because its not even powering up.
Ok....i think im making progess....The newest nightly just goes into a bootloop. better than a clockwork bootloop i guess..... any advice on how to get it to install properly? i feel like im making progress. normal bootloops are better than what i was getting
Bueller............Bueller lmao.
Seriously though.....if anybody can figure this out it would make my year
Try this, install stock 1.2....
boot it up, go through the annoying setup, log into google apps, then power down.
Boot into CWR SD, this should have the os that you want already on it, and the google apps file.
THen click install from zip, choose zip, install the OS, after complete install google apps, then restart without sd
Do not format anything, it should do the trick.
So I updated the MIUI on my Cappy from whatever I had before to 2.3.30 that is GB 2.3.7 from this location:
http://miuiandroid.com/community/threads/archived-miui-versions-captivate-gb.16558/
I didnt care for it so I downloaded SlimICS. I downloaded the base and the cappy essentials. Put them both on my internal sd. I factory reset, wiped data, cache and system and dalvic, just as i do for every phone i work on. I ran the SlimICS base and now it keeps rebooting and going back into recovery and doing this:
Finding update package...
Opening update package...
Installing update...
Slim ICS
Once Slim ICS pops up, it reboots and does it all over. I can yank the battery and manually go into recovery, but if i try to boot it up normal, it goes back into the loop. I am on CWM 5.0.2.7 also.
So what did i miss?
GB bootloaders most likely missing - flash 'em using Heimdall. And SlimICS doesn't have modem. So. Flash my ROM for a change may be.
Sounds like you just need to flash again. You have to do that when you are going from GB to ICS, and vice versa I believe.
And you flashed the base and the cappy essentials right? Not just the base
Sent from my SGH-I897 using xda premium
korockinout13 said:
Sounds like you just need to flash again. You have to do that when you are going from GB to ICS, and vice versa I believe.
Click to expand...
Click to collapse
trying to flash again just put it back in the loop. And I read that that does happen alot going from GB to ICS on the Cappy. But for Slim it didnt work.
Wdustin1 said:
And you flashed the base and the cappy essentials right? Not just the base
Click to expand...
Click to collapse
I never could get that far because it was the base that I started to install and it got bootlooped on, everytime it restarted, it went back into recovery and started to run the base again, and repeated boot loop. I read somewhere that teamhacksung's rom would get me over the GB to ICS bridge. This one here:
http://forum.xda-developers.com/showthread.php?t=1363760
It did the bootloop to, but when i yanked the battery and went back in and installed it a 2nd time, it didnt restart and installed correctly. After that I installed SlimICS. But I dont like it as much as i thought i would and now when i try to reinstall teamhacksung ROM, it errors out during the beggining of the installation. The MD5 is still fine. I dont think it likes the version of CWM recovery that SlimICS installed. I know CWMR went to an older version when i went from teamhacksung to SlimICS.
Flash glitch kernel first. Also, don't use the builds from that thread, it is old. Just flash the latest CM9 nightly
Swyped from my ICS Samsung Captivate
Stuck in A boot loop after flashing paranoid rom to cappy i897
I downloaded all needed files to internal SD just as the (how to upgrade the captivate i897 to Paranoid ROM said to do )
wipe data factory reset,wipe cache,selected install zip zip>package (pa_captivatemtd-1.99-13AUGUST2012.zip, md5sum: cc03bacf0f07a94bf25b482d64b94e63) then it started boot looping / att screen twice then android guy ,, then falling over with exclamation point in the middle of him , let it go considering options of 3 button combo weren't working ,, beside guide said 5-10 min to install then it made it to devil kernel installed gapps >> (gapps-jb-20120726-signed.zip, md5sum: f62cfe4a827202899919fd932d5246d7) now back in the boot loop again>>
i did make a nandroid backup but cant seem to get into cwm recovery or download mode . I did follow that guide to a tee.
any help or suggestions on this i would greatly appreciated if this post in wrong spot sry im new.
Also stuck in bootloop reverting to Gingerbread
I am also stuck in boot loop after attempting to restore back into Gingerbread.
Here's how I got in this mess: I had been running Gingerbread on my Captivate for several months (rooted). I decided it was time to try upgrading to Jelly Bean (cm9 version). I installed ClockworkMod Recovery and that appeared to be working, so I made a NANDroid and proceeded to install CyanogenMod on my phone.
It booted OK, but I didn't like it and figured I'd just revert by restoring my NANDroid. Only thing is, it didn't restore correctly and my phone was stuck at the initial AT&T "bars" screen.
So I attempted to reboot in recovery and restore my latest update.zip. This did not seem to help at all. My phone would just boot to the AT&T screen and be stuck there. I checked to see adb was reachable behind the scenes but it wasn't.
After that I loaded Odin 1.85, downloaded a copy of the stock Captivate ROM, unzipped it and loaded it to my ROM (using the method described in this link I'm not allowed to show you because I'm a new user), more or less.
Odin said it was successful, but the phone is now still stuck in a boot loop. The ClockworkMod Recovery options are gone from the recovery menu. Now it looks like my stock recovery menu. There are some diagnostics on the recovery screen:
-- Copying media files --
E: failed to mount /dbdata (Invalid argument)
E: copy_dbdata_media: Can't mont /dbdata
your storage not prepared yet. please use UI menu
for format and reboot actions.
Meida files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Installing Multi-CSC
Applied CSC-code 'ATT'
Successfully copied multi-CSC.
-----
the bold text indicating errors appears in orange.
I tried "wipe data/factory reset" and "wipe cache partition" and rebooting. This had no apparent effect. The Captivate still continues to loop on reboot.
What next? It seems like it's missing something it needs to boot that's not in the standard Gingerbread Captivate image I downloaded with Odin. What else do I need to do? Keep in mind that right now the only way I can get files onto the phone is Odin (or similar) via the USB port. The phone never gets booted enough to get to it with adb, let alone mounting as a drive on my computer.
Thanks
Reply Back.
HG_User said:
I am also stuck in boot loop after attempting to restore back into Gingerbread.
Here's how I got in this mess: I had been running Gingerbread on my Captivate for several months (rooted). I decided it was time to try upgrading to Jelly Bean (cm9 version). I installed ClockworkMod Recovery and that appeared to be working, so I made a NANDroid and proceeded to install CyanogenMod on my phone.
It booted OK, but I didn't like it and figured I'd just revert by restoring my NANDroid. Only thing is, it didn't restore correctly and my phone was stuck at the initial AT&T "bars" screen.
So I attempted to reboot in recovery and restore my latest update.zip. This did not seem to help at all. My phone would just boot to the AT&T screen and be stuck there. I checked to see adb was reachable behind the scenes but it wasn't.
After that I loaded Odin 1.85, downloaded a copy of the stock Captivate ROM, unzipped it and loaded it to my ROM (using the method described in this link I'm not allowed to show you because I'm a new user), more or less.
Odin said it was successful, but the phone is now still stuck in a boot loop. The ClockworkMod Recovery options are gone from the recovery menu. Now it looks like my stock recovery menu. There are some diagnostics on the recovery screen:
-- Copying media files --
E: failed to mount /dbdata (Invalid argument)
E: copy_dbdata_media: Can't mont /dbdata
your storage not prepared yet. please use UI menu
for format and reboot actions.
Meida files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Installing Multi-CSC
Applied CSC-code 'ATT'
Successfully copied multi-CSC.
-----
the bold text indicating errors appears in orange.
I tried "wipe data/factory reset" and "wipe cache partition" and rebooting. This had no apparent effect. The Captivate still continues to loop on reboot.
What next? It seems like it's missing something it needs to boot that's not in the standard Gingerbread Captivate image I downloaded with Odin. What else do I need to do? Keep in mind that right now the only way I can get files onto the phone is Odin (or similar) via the USB port. The phone never gets booted enough to get to it with adb, let alone mounting as a drive on my computer.
Thanks
Click to expand...
Click to collapse
While searching threw all this mess on this site and various other :
I did stumble on something that might help u get your cwm
mode Look up Captivate Q&A the scroll to T, Russel thread has file needed to get your cwm mode working using rageagaistcage method.
Odin has multi file upload for stock alone check to make sure you selected right one . then just reflash should be good
mine i examine really thoroughly and figure out i try to jump to high .
i had stock then firefly then darkfire which is based off i900 <> Cappy rom bad <>idea on my part i try to jump to paranoid rom from darkfire '
don't think files were save to SD internal card - download section instead so firmware lost track of it self .
reviewing errors made on my part order 2 jig for my 2 cappys
my plan use jig get into download flash back to stock using odin one click using kies flash to froyo and stick with it for another six months
while reading everything i need to know about flashing that high up , besides that rom will become more stable less bugs and it will give me
time to see what errors occurs with this phone model on that rom last time i check there was only 7 posted user using it
again i was trying to flash paranoid rom for Samsung captivate SGH_I897'' I hope you get your issue resolved.
If u try one click unbrick and on win xp uninstall kies the drivers will not work together log in to administrator account <> just Google it if not on welcome screen there a few ways to get into that account,, but that did work for me on my cappy . let me know how u make out. ??
---------- Post added at 06:38 PM ---------- Previous post was at 06:27 PM ----------
321321wrick said:
While searching threw all this mess on this site and various other :
I did stumble on something that might help u get your cwm
mode Look up Captivate Q&A the scroll to T, Russel thread has file needed to get your cwm mode working using rageagaistcage method.
Odin has multi file upload for stock alone check to make sure you selected right one . then just reflash should be good
mine i examine really thoroughly and figure out i try to jump to high .
i had stock then firefly then darkfire which is based off i900 <> Cappy rom bad <>idea on my part i try to jump to paranoid rom from darkfire '
don't think files were save to SD internal card - download section instead so firmware lost track of it self .
reviewing errors made on my part order 2 jig for my 2 cappys
my plan use jig get into download flash back to stock using odin one click using kies flash to froyo and stick with it for another six months
while reading everything i need to know about flashing that high up , besides that rom will become more stable less bugs and it will give me
time to see what errors occurs with this phone model on that rom last time i check there was only 7 posted user using it
again i was trying to flash paranoid rom for Samsung captivate SGH_I897'' I hope you get your issue resolved.
If u try one click unbrick and on win xp uninstall kies the drivers will not work together log in to administrator account <> just Google it if not on welcome screen there a few ways to get into that account,, but that did work for me on my cappy . let me know how u make out.
There also Ginger Bread Boot loaders Needed for it to start up Correctly - i personally don't know that much bout gingerbread rom i didn't like it as much as froyo WiFi issues'' the the stock odin should erase all info on your part thou 'e use Is OCD 1 i897UCJF6>lowercase work every time for me.
cept now because my usb is not able to charge phone or enter download mode or recovery which leaves jig option .
Click to expand...
Click to collapse
HG_User,
U can't go back to GB (or froyo/eclair) from CM, MIUI, ICS, JB, AOSP etc., etc. without using Odin or Heimdall---because of the different partitions used---Stock firmware is bml/rfs and all the AOSP etc etc are mtd/yaffs(2).
And u can only restore a backup when u r back running the base rom where u made the back up.
Use this...Stock i897ucKK4 GB 2.3.5 with or without bootloaders... http://forum.xda-developers.com/showthread.php?p=18370912
This kk4 should get u going. Then u can use Odin to flash Corn Kernel to get a cwm back...:thumbup:
Sent from my SGH-I897 using xda premium
... one step on the way: Back to Eclair
thanks for the advice. Ultimately, I decided I should use Odin 3 1-click to revert back to original (2.1 Eclair) firmware that I found on the first post of thread titled
[STOCK ROM] Odin3 One-Click Downloader and Drivers CAPTIVATE ONLY
This is a huge step forward because it makes my phone work, but it's also a step back in time to the early Eclair days.
Now my next step is to upgrade back to Gingerbread...
Edit: Thanks to all who pointed me in the right direction. I took the phone back to Eclair then used Samsung KiesMini (twice) to get it back to Gingerbread. After re-rooting and removing the AT&T Bloatware, it works fine again. I might try upgrading again to ICS or JB, but I didn't like Cyanogen 9 at all. Maybe I'm just used to the way AT&T polishes the UI, but Cyanogen didn't appeal at all. Now looking for a relatively polished but lightweight ICS or JB version... Also, it would be nice if when I upgrade it preserves the installed apps and what's on my home screens, but that seems unlikely going from AT&T-branded Gingerbread to an independent ICS or JB.
Hello Folks,
First I have to say that I watched the noob video and read everything about E:Error in /mnt/sdcard/cm-10.0.0.-galaxysmtd.zip (Status 7) on this forum and what google gave me.
My situation:
PC OS is Windows 7 64bit (if someone needs to know)
Phone:
Samsung Galaxy S GT-I9000
SSN: I9000GSMH
What happend:
I bought a used phone about two months ago with latest installed stock rom 2.3.5 it is. Then i downloaded cm-10-20121126-NIGHTLY-galaxysmtd and followed the instructions on wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Full_Update_Guide. I installed CWM with Heimdall Suite. Everything worked well.
Today I decided to install a newer version of CM, I downloaded the cm-10-20121210-NIGHTLY-galaxysmtd and cm-10.0.0-galaxysmtd and copied them both on the phone memory. I turned off the phone and turned it on in recovery mod, and I got the recovery mode that was on cm-10-20121126-NIGHTLY-galaxysmtd installed. It wasn't the standard CWM that I installed with Heimdall Suite. I wiped with it data and cache and installed cm-10-20121210-NIGHTLY-galaxysmtd and then rebooted the phone. But the phone got stuck and didn't want to reboot. So i tried to go to recovery mod again to reinstall the cm-10.0.0-galaxysmtd but the phone couldn't access the recovery mod anymore.
After that I reinstalled with Heimdall Suite the ClockwordMod Recovery v2.5.1.0 SpeedMod Kernel like the first time I did. and successfully booted to recovery mod and again wiped cache and data and tried to install cm-10.0.0-galaxysmtd when i got the error
This is the image, just copy/paste in address bar.
imageshack.us/f/685/07032008448.jpg
So, now my phone has no OS installed.
There are some other issues too, I can't mount my external sd card in CWM, why, I don't know, so I only have cm-10-20121210-NIGHTLY-galaxysmtd and cm-10.0.0-galaxysmtd on my phone memory to install.
I would really really like if someone could help me to solve my problem, I have no other phone. And please when you tell to install something give me the needed link because I really downloaded a lot of things that didn't work.
adobih said:
Hello Folks,
First I have to say that I watched the noob video and read everything about E:Error in /mnt/sdcard/cm-10.0.0.-galaxysmtd.zip (Status 7) on this forum and what google gave me.
My situation:
PC OS is Windows 7 64bit (if someone needs to know)
Phone:
Samsung Galaxy S GT-I9000
SSN: I9000GSMH
What happend:
I bought a used phone about two months ago with latest installed stock rom 2.3.5 it is. Then i downloaded cm-10-20121126-NIGHTLY-galaxysmtd and followed the instructions on wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Full_Update_Guide. I installed CWM with Heimdall Suite. Everything worked well.
Today I decided to install a newer version of CM, I downloaded the cm-10-20121210-NIGHTLY-galaxysmtd and cm-10.0.0-galaxysmtd and copied them both on the phone memory. I turned off the phone and turned it on in recovery mod, and I got the recovery mode that was on cm-10-20121126-NIGHTLY-galaxysmtd installed. It wasn't the standard CWM that I installed with Heimdall Suite. I wiped with it data and cache and installed cm-10-20121210-NIGHTLY-galaxysmtd and then rebooted the phone. But the phone got stuck and didn't want to reboot. So i tried to go to recovery mod again to reinstall the cm-10.0.0-galaxysmtd but the phone couldn't access the recovery mod anymore.
After that I reinstalled with Heimdall Suite the ClockwordMod Recovery v2.5.1.0 SpeedMod Kernel like the first time I did. and successfully booted to recovery mod and again wiped cache and data and tried to install cm-10.0.0-galaxysmtd when i got the error
This is the image, just copy/paste in address bar.
imageshack.us/f/685/07032008448.jpg
So, now my phone has no OS installed.
There are some other issues too, I can't mount my external sd card in CWM, why, I don't know, so I only have cm-10-20121210-NIGHTLY-galaxysmtd and cm-10.0.0-galaxysmtd on my phone memory to install.
I would really really like if someone could help me to solve my problem, I have no other phone. And please when you tell to install something give me the needed link because I really downloaded a lot of things that didn't work.
Click to expand...
Click to collapse
you having the wrong CWm installed, you can go to this link to download the cf-root kernel. http://forum.xda-developers.com/showthread.php?t=788108 hope this will help .
BTW when flashing JB from GB you need to flash CM9 then follow by CM10, if you can try flash it from GB 2.3.6 (E.g xxjvu)
i try flashing JB from GB is work if i flash twice but i got missing IMEI. so i suggest you following this step to flash.
GB(stock rom with ROOT) - ICS(CM7) - JB(CM10)
Samtan4326 said:
you having the wrong CWm installed, you can go to this link to download the cf-root kernel. http://forum.xda-developers.com/showthread.php?t=788108 hope this will help .
BTW when flashing JB from GB you need to flash CM9 then follow by CM10, if you can try flash it from GB 2.3.6 (E.g xxjvu)
i try flashing JB from GB is work if i flash twice but i got missing IMEI. so i suggest you following this step to flash.
GB(stock rom with ROOT) - ICS(CM7) - JB(CM10)
Click to expand...
Click to collapse
First off all thanks for helping.
I tried this one:
CF-ROOT-4.4-I9000BGJW5-1187857
CF-Root-4.4-I9000BOJW6-CL1177078
CF-Root-JP6-v1.2-Busybox-1.17.1 (this one didn't want to start recovery at all)
CF-Root-XX_OXA_JW4-v4.4-CWM3RFS
all I got from all of them is this
imageshack.us/f/805/08032008449.jpg (copy link to address bar )
Member Chainfire said "THIS IS NOT A ROM - it is only a kernel. You need to have a firmware already on your device"
I don't know really what that means. Probably that I have to install something else too, but what ?
Please can you tell me ?
And which of these CF-Roots is the right one, or the newest one, or how do recognize that ?
Thanks everyone who helps me.
eba
Well, I solved my problem, now i have cm-10.0.0-galaxysmtd ROM installed. If someone has this problem, this is one way how to solve it (but doesn't mean it's the best one).
If you have no ROM installed on your I9000 and don't know which kernel to use, try this way:
Watch this video on YouTube that user "Puggered UK" uploaded:
youtube.com/watch?v=iRnH13sRAIc
- You can skip to 1.52 because you don't have any ROM on your phone, and download the EZ Odin package from the link in the About section (4shared.com/archive/TuHUfVjA/EZOdin.html).
- Start EZ Odin, put the PIT, PDA, PHONE and CSC file in the right box, connect your phone in download mode to the PC and press START, and wait till the process is complete.
- After a while you should have Android 2.3.? installed on your phone.
- Update Google market to Google play, then update ROM Manager, and start ROM Manager. Choose to Flash Clockwork Mod Recovery, choose your phone and flash it.
- Copy on your internal sd memory cm-10.0.0-galaxysmtd that you downloaded from CyanogenMod web site.
- Restart your phone in Recovery mod, wipe data/cache, and install cm-10.0.0-galaxysmtd from internal sd card.
- Then, when it's done restart the phone, and do the last step again in Cyanogen CW recovery.
- After it's done, restart the phone and you will have CM 10 on your phone installed.
Or just watch the video and you will se what to do.
adobih said:
Well, I solved my problem, now i have cm-10.0.0-galaxysmtd ROM installed. If someone has this problem, this is one way how to solve it (but doesn't mean it's the best one).
If you have no ROM installed on your I9000 and don't know which kernel to use, try this way:
Watch this video on YouTube that user "Puggered UK" uploaded:
youtube.com/watch?v=iRnH13sRAIc
- You can skip to 1.52 because you don't have any ROM on your phone, and download the EZ Odin package from the link in the About section (4shared.com/archive/TuHUfVjA/EZOdin.html).
- Start EZ Odin, put the PIT, PDA, PHONE and CSC file in the right box, connect your phone in download mode to the PC and press START, and wait till the process is complete.
- After a while you should have Android 2.3.? installed on your phone.
- Update Google market to Google play, then update ROM Manager, and start ROM Manager. Choose to Flash Clockwork Mod Recovery, choose your phone and flash it.
- Copy on your internal sd memory cm-10.0.0-galaxysmtd that you downloaded from CyanogenMod web site.
- Restart your phone in Recovery mod, wipe data/cache, and install cm-10.0.0-galaxysmtd from internal sd card.
- Then, when it's done restart the phone, and do the last step again in Cyanogen CW recovery.
- After is done, restart the phone and you will have CM 10 on your phone installed.
Or just watch the video and you will se what to do.
Click to expand...
Click to collapse
hey,
had that problem too, yesterday. will try your suggestions later and report back!
hope it helps...
Grz
beckzz said:
hey,
had that problem too, yesterday. will try your suggestions later and report back!
hope it helps...
Grz
Click to expand...
Click to collapse
Well, I help you as much as I can and know, just write me where you stuck. And if you have some difficulties explaining it in English, dann kannst du mir auch auf deutsch schreiben, das verstehe ich auch
I had this status 7 thing 2 yesterday while installing cm10. It also seemed I couldnt get into recovery. What I had to do is flash the zip 4 times. First time it got stuck at boot.
So I took battery out & try to get in to recovery (volume up+home button+power button & -->release buttons the moment u see bootanimation<--) but it started bootlooping/got stuck again.
So I took battery out again, did the 3 button combo for the second time & I waited a little longer, a minute maybe 2 & it went to recovery. (I guess the first time it didnt went straight to recovery like it normally does, I wasnt patient enough). If not getting into recovery with waiting the first time just try to keep getting in recovery with 3 button combo & wait a couple of minutes. Eventually it does. I had the same thing 2 months ago coming from jb-->ics-->cm10, thats how I remembered.
Didnt wipe a thing just went straight to the zipfile & flashed it in total 4 or 5 times till it said install completed on the screen. Didnt wipe nothing in between the flashing
Then flashed gapps & voila
Donovan662 said:
I had this status 7 thing 2 yesterday while installing cm10. It also seemed I couldnt get into recovery. What I had to do is flash the zip 4 times. First time it got stuck at boot.
So I took battery out & try to get in to recovery (volume up+home button+power button & release buttons the moment u see bootanimation) but it started bootlooping/got stuck again.
So I took battery out again, did the 3 button combo for the second time & I waited a little longer, a minute maybe 2 & it went to recovery. (I guess the first time it didnt went straight to recovery like it normally does, I wasnt patient enough)
Didnt wipe a thing just went straight to the zipfile & flashed it in total 4 or 5 times till it said install completed on the screen
Then flashed gapps & voila
Click to expand...
Click to collapse
I tried like hundred times or more, but every time with the same result and I also tried with different kernels without success. Maybe some other error caused your status 7 error than mine. But anyway, it's always good to try all possibilities to resolve the problem.
Haha I went crazy not getting into recovery 2 months ago I did it at least 15 times till it eventually got into recovery. Weird cuz I released it the moment I saw cyanogen boot animation. I had to wait a lil longer after releasing so it seems & better timing maybe but only with flashing cm10 from stock. The error was the same tho I saw your picture
Donovan662 said:
Haha I went crazy not getting into recovery 2 months ago I did it at least 15 times till it eventually got into recovery. Weird cuz I released it the moment I saw cyanogen boot animation. I had to wait a lil longer after releasing so it seems & better timing maybe but only with flashing cm10 from stock. The error was the same tho I saw your picture
Click to expand...
Click to collapse
Unfortunately I wasn't that lucky, but I tell you something else. Now I know that no matter what I do and how badly i brick my phone I can always use that method to bring it to life back. So it's kind of final help that works if nothing else works
by the way did you apply sdcard:update zip? Or choose zip from sd card?
Donovan662 said:
by the way did you apply sdcard:update zip? Or choose zip from sd card?
Click to expand...
Click to collapse
I choose zip from sd card because I forgot to rename the file before copying to sd card, and when I lost my bricked my phone it was already to late to rename it. But i don't think that that was the problem, I mean it's just a name string that has no meaning after all.
hey guys,
finally i made it...
thx adobih for your offer, but i'll try to do it in english...think(hope) my english is not that bad
so my problem was the following, slightly different from yours:
i bought a used Galaxy S I9000 for my girlfried as a christmas present cause her Galaxy Ace is the worst Android-phone i ever saw ^^
this "new" Galaxy S has never been rooted before, it never enjoyed a custom ROM - completely stock with 2.2.1 froyo ^^
Here is, what i did to get cm10 stable to work:
1. Updated android to latest official android 2.3.6 with Samsung Kies
2. then i followed the step "Installing the ClockworkMod Recovery" from here
--- ATTENTION: Heimdall 1.3.2 screwed things up (due to a bug i think, only download-mode was available afterwards), use Heimdall 1.3.1 to be safe
3. then i pushed cm 9.1 stable, cm 10.0 stable and latest gapps for 10.0 to the device
4. then i flashed cm 9.1 stable via CWM - an Error occured
5. then i selected "reboot system" in CWM (NOT "reboot recovery"!!)
6. device reboots and starts to install CM 9.1 Stable on its own
7. booted to the now "new" CWM installed by cm 9.1 zip
8. flashed cm 9.1 zip again
8. booted cm 9.1 normally, everything was working fine
9. booted into cwm
10. flashed cm 10.0 zip - an error occured
11. then i selected "reboot system" in CWM (NOT "reboot recovery"!!)
12. device reboots and starts to install CM 10.0 Stable on its own
13. booted to the now "new" CWM installed by cm 10.0 zip
14. flashed cm 10.0 zip again
15. a warning occured "incompatible filesystem, flash again to confirm"
16. flashed cm 10.0 zip again
17. booted cm 10.0 normally, everything was working fine
18. booted CWM again, flashed gapps
19. booted cm 10.0 normally, everything was working fine
I was not able to flash cm 10.0 directly after flashing codeworxs kernel with heimdall. think this is related to changed partition sizes and stuff...
device only booted to CWM again, i was not able to boot the system - bootloop. Once i tried to flash cm10, there was no success when trying to flash cm 9 after that.
i tried it 3-4 times to flash cm 10 directly with no success. i checked md5 sums of the downloaded files, but everything was fine.
the detour with cm 9.1 was the only way to get it to work.
after trying to flash cm10 directly it always screwed something and was not able to get any further.
to start again, i had to go back to stock with odin. For that i used these instructions and files. (its in german, but very well illustrated, so all of you should be able to follow the steps).
When starting from stock, you can follow the steps above and everything should be fine.
took me some hours to figure out the correct order of the steps....
this is a slightly different problem as the one in op, so i decided to provide my solution here.
the heimdall 1.3.2-bug occured with the i9000 of a friend of mine, too. only heimdall 1.3.1 did what it was supposed to.
for all people interested: i decided to flash semaphore kernel for better customization options....running pretty well
EDIT: thx to everybody in this thread posting your experiences, all together it pointed me to the solution.. THX!
Grz
beckzz said:
hey guys,
finally i made it...
thx adobih for your offer, but i'll try to do it in english...think(hope) my english is not that bad
so my problem was the following, slightly different from yours:
i bought a used Galaxy S I9000 for my girlfried as a christmas present cause her Galaxy Ace is the worst Android-phone i ever saw ^^
this "new" Galaxy S has never been rooted before, it never enjoyed a custom ROM - completely stock with 2.2.1 froyo ^^
Here is, what i did to get cm10 stable to work:
1. Updated android to latest official android 2.3.6 with Samsung Kies
2. then i followed the step "Installing the ClockworkMod Recovery" from here
--- ATTENTION: Heimdall 1.3.2 screwed things up (due to a bug i think, only download-mode was available afterwards), use Heimdall 1.3.1 to be safe
3. then i pushed cm 9.1 stable, cm 10.0 stable and latest gapps for 10.0 to the device
4. then i flashed cm 9.1 stable via CWM - an Error occured
5. then i selected "reboot system" in CWM (NOT "reboot recovery"!!)
6. device reboots and starts to install CM 9.1 Stable on its own
7. booted to the now "new" CWM installed by cm 9.1 zip
8. flashed cm 9.1 zip again
8. booted cm 9.1 normally, everything was working fine
9. booted into cwm
10. flashed cm 10.0 zip - an error occured
11. then i selected "reboot system" in CWM (NOT "reboot recovery"!!)
12. device reboots and starts to install CM 10.0 Stable on its own
13. booted to the now "new" CWM installed by cm 10.0 zip
14. flashed cm 10.0 zip again
15. a warning occured "incompatible filesystem, flash again to confirm"
16. flashed cm 10.0 zip again
17. booted cm 10.0 normally, everything was working fine
18. booted CWM again, flashed gapps
19. booted cm 10.0 normally, everything was working fine
I was not able to flash cm 10.0 directly after flashing codeworxs kernel with heimdall. think this is related to changed partition sizes and stuff...
device only booted to CWM again, i was not able to boot the system - bootloop. Once i tried to flash cm10, there was no success when trying to flash cm 9 after that.
i tried it 3-4 times to flash cm 10 directly with no success. i checked md5 sums of the downloaded files, but everything was fine.
the detour with cm 9.1 was the only way to get it to work.
after trying to flash cm10 directly it always screwed something and was not able to get any further.
to start again, i had to go back to stock with odin. For that i used these instructions and files. (its in german, but very well illustrated, so all of you should be able to follow the steps).
When starting from stock, you can follow the steps above and everything should be fine.
took me some hours to figure out the correct order of the steps....
this is a slightly different problem as the one in op, so i decided to provide my solution here.
the heimdall 1.3.2-bug occured with the i9000 of a friend of mine, too. only heimdall 1.3.1 did what it was supposed to.
for all people interested: i decided to flash semaphore kernel for better customization options....running pretty well
EDIT: thx to everybody in this thread posting your experiences, all together it pointed me to the solution.. THX!
Grz
Click to expand...
Click to collapse
More or less I think we both had the same problem, because I also used this link wiki.cyanogenmod.org/wiki/Samsung_Galaxy_S:_Full_Update_Guide and heimdall 1.3.2 for flashing my phone. Just it always finished successfully so I didn't realize it was the root of all problems. I used also then Odin from the youtube video that I posted in a few posts earlier, installed Android 2.3.6 and then installed ROM Manager from Google play, and used the app to flash to ClockworkMod Recovery. After that I installed directly CM10 stable with success, and without CM9 detour.
Hi, I'm a noob for messing with my phone.
Although I have googled for 7+ hours I have found nothing that helped me, only things that **** me over.
So here is the story:
I decided to install Cyanogenmod 10 on my device. That worked out okay and stuff, but I couldn't install gapps. It said everything was ok but when i started CM10 gapps wasn't there. I tried 10-20 diffrent versions of CM10, all with gapps and diffrent versions of gapps but it didn't work.
Then I installed CWM. I installed CM10 + Gapps with CWM. Then I tried rebooting my device. CWM booted up. CWM boots up everytime I try to boot the device. I googled and found a file, exitrecovery.zip. I installed that via CWM but it didn't work. So, after some more googleing I found a thread on here that said to flash Boot_loader.tar onto my phone via Odin Multi Downloader. Of course, I messed that up. I tried to flash it using "PDA" instead of "BOOT". So that didnt work. I flashed it again using "BOOT" but now it shuts down after the Samsung text on screen.
I am about to attempt to flash the stock OS into my device using the Package option in Odin (Luckily Download mode still works).
Is using Package the correct way to flash the stock OS into my phone?
When I have it working again I want to install CM10 with gapps. Why didn't gapps install?
How can I install gapps correctly?
How do I get out of the CWM boot loop?
Someone please help me because I don't know what to do anymore!
EDIT: Succesfully flashed in stock firmware. But how do I install CM10 and have gapps working?
Thanks in advance,
-Spore
Easyest way to rescue your phone is to flash 3 file ROM with pit and re-partition.
one of many guides is here
Use one of multicsc ROMs (i'd use JVZ)
Then it gets little tricky when getting to CM10
First of all flash semaphore kernel for JVZ (google it)
Then I'd go through CM9 stable to CM10. Flashing guides are easy to find
Edit. Maybe u're using wrong Gapps? for CM10 gaps are from 20120606 (or something like that - newest are for cm10.1)
Got it working!
I figured everything out on my own.
Here's how I did it for anyone with the same problem:
Download the files ill list below.
Put them all on your phone's internal SD
Boot into Recovery Mode
Install CMW6014-TOUCH-CM9recovery.zip
Reboot into Recovery Mode
Clear everything.
Install cm-10-20130130-ivendor-alpha7-ariesve.zip
Install gapps-jb-20121011.zip
Reboot.
And you're done!
Files are listed down below. Since I'm a new user i have to put a dot in the URL.
The only other file you'll need is fs1.d-h.st/download/00026/J34/cm-10-20130130-ivendor-alpha7-ariesve (dot) zip
does this work for cm9?
SporeSpood said:
I figured everything out on my own.
Here's how I did it for anyone with the same problem:
Download the files ill list below.
Put them all on your phone's internal SD
Boot into Recovery Mode
Install CMW6014-TOUCH-CM9recovery.zip
Reboot into Recovery Mode
Clear everything.
Install cm-10-20130130-ivendor-alpha7-ariesve.zip
Install gapps-jb-20121011.zip
Reboot.
And you're done!
Files are listed down below. Since I'm a new user i have to put a dot in the URL.
The only other file you'll need is fs1.d-h.st/download/00026/J34/cm-10-20130130-ivendor-alpha7-ariesve (dot) zip
Click to expand...
Click to collapse
Hello, thank you for posting this. I noticed that the one file that you said we should download looks like it is for cm10. is that correct? I have cm9.
Also, what do you mean by "clear everything"?
{EDIT} I figured it out. For any other user that has this problem-- you must ensure that you are using the correct version of gapps as others have noted.
In OP's answer to his own question, he used cm10. and the appropriate gapps for jelly bean. That didn't work for me since I was using ICS. Do not use the file he listed for cm10 unless you mean to install that specific version of cm10, which probably won't work for your phone.
Also, google took about 6 hours to recognise my account on the play store. This is apparently a common issue, and I have read multiple threads where people are not seeing their device linked up to their account after upgrading to custom ROMs. The play store app worked on my phone, but not when using an outside device linked to that account (my desktop). I called google support and they said that they had no idea what was wrong, 3 hours later, it just started working.
So be patient if you do not have the option to use the play store from outside sources right away.
Hi, device is rooted, and clockworkmod recovery 6.0.4.5 installed.
ROM is JB, the official update from LG. Today device reported there is an update to the installed firmware.
I rebooted in CM recovery, took a nandroid backup, booted, and accepted to download the official update to my official JB rom. After downloading I was asked to reboot (in order to install), and the phone reboots to the CM recovery.
From there I don't know what to do. I have tried rebooting, but again find myself to the CM recovery. I have tried "reboot to bootloader" and get stuck at the LG boot screen logo with the message "Now Ready!" in tiny white letters on the upper left corner.
I would try "install zip" but I don't know where the downloaded update is (if it even is in an acceptable zip format)
Phone isn't bricked, I guess I can always restore from the recently taken backup, but I really would like to know if there is a way to install this update.
Thank you
http://forum.xda-developers.com/showthread.php?p=50645445
Could you please please please try to search the next time I've seen this question for probably 3-4 times
Sent from my LG-P880 using xda app-developers app
you can't ota over unlocked bl/cwm, you must flash update manually
moneyvirus said:
http://forum.xda-developers.com/showthread.php?p=50645445
Could you please please please try to search the next time I've seen this question for probably 3-4 times
Click to expand...
Click to collapse
You're right, but you know, sometimes you just can't nail the right keywords especially if its not your native language. I searched, but obviously not good enough.
Rudjgaard said:
you can't ota over unlocked bl/cwm, you must flash update manually
Click to expand...
Click to collapse
Sadly, this seems to be the case.. bummer.
Thanks everyone
Not even my nandroid backup can help me get to where I was before? So much for nandroid being the ultimate backup, a "snapshot image" of the device...
So, what if, I use CM recovery to install a custom rom, and then restore from my nandroid backup (being the official JB) ?
Flash with kdz flasher original ROM then flash cwm you can put back your backup. I think the problem starts that the update pushes something in the boot section that is expecting an other (read original) recovery . when you installed cwm it boots up cwm so that's why an nandroid backup doesn't work I think ( to be honest I'm not 100% sure this is correct)
Sent from my LG-P880 using xda app-developers app
I can't even flash cyanogenmod???
I downloaded latest stable build, copied it to sd card, selected it from the CM recovery ("install zip"), installed fine, reboot, still stuck at CM recovery!!!
What gives?
EPa said:
I can't even flash cyanogenmod???
I downloaded latest stable build, copied it to sd card, selected it from the CM recovery ("install zip"), installed fine, reboot, still stuck at CM recovery!!!
What gives?
Click to expand...
Click to collapse
Have you yet followed the advice and installed the KDZ?
Trying to avoid that, as it seems too much work for a phone that was working fine, and stuck to recovery due to some silly boot flag or something.
Saw it as a chance to try cyanogenmod. But it seems having CM recovery and the cyanogenmod rom on the sd card won't cut it! Talk about failure..
EPa said:
Trying to avoid that, as it seems too much work for a phone that was working fine, and stuck to recovery due to some silly boot flag or something.
Saw it as a chance to try cyanogenmod. But it seems having CM recovery and the cyanogenmod rom on the sd card won't cut it! Talk about failure..
Click to expand...
Click to collapse
I don't think you will have a choice. If you created the nandroid backup on your SD card then you aren't going to lose it, so just flash the KDZ, root again and install your backup, or accept the LG update and rebuild all your software again.
Yes, one thing is for sure. I had to install the KDZ to be able to proceed with anything..
It's just funny having a working CWM recovery and a cyanogen rom on the device and after flashing it, still not having a device that boots. A "recovery"/flash tool, should be able to "recover" from such a situation..
EPa said:
Yes, one thing is for sure. I had to install the KDZ to be able to proceed with anything..
It's just funny having a working CWM recovery and a cyanogen rom on the device and after flashing it, still not having a device that boots. A "recovery"/flash tool, should be able to "recover" from such a situation..
Click to expand...
Click to collapse
You can't blame the recovery. It is clearly stated many, many times that you should never attempt an official OTA update with a non-standard (rooted or recovery installed) device. On other devices you could even hard-brick AFAIK, so consider yourself lucky that you only had to reflash a KDZ and start again.
For restoring stock rom use this: http://forum.xda-developers.com/showthread.php?t=2682146 I can confirm it works and it is (very) easy.
Yes that's what I used and I also confirm it works and is very easy.