Hello everyone,
I'm new to rooting and ROM's so I've been playing around since my Captivate's speaking is broken and of no use (I have a Note now.) I was using CornKernel and had installed CM 10.1 but the nightly I had installed was horrible and I wanted to revert to stable I HAD been running. Anyways, had a problem restoring the stable so I did a battery pull.
I could no longer get into CornKernel recovery, so I flashed Semaphore's ClockworkMod Recovery from CM's install directions. I now get this error I AM able to get into download, but not load any .zip's via this new recovery:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
you flashed an old version of cwm and it isn't compatible with cm10, I think.
if you can get into download mode and flash stock kk4 via usb and odin or heimdall, you should be able to recover. then you can do corn to get cwm back.
If you have a cwm backup of your stable 10.1 rom on a dropbox or google drive, don't try to recover it using Corn Kernel version of cwm. Do the full wipe, factory reset and flash stable CM10.0 plus appropriate gapps from Corn kernel. Then restore your backup, if you have it.
laughingT said:
you flashed an old version of cwm and it isn't compatible with cm10, I think.
if you can get into download mode and flash stock kk4 via usb and odin or heimdall, you should be able to recover. then you can do corn to get cwm back.
If you have a cwm backup of your stable 10.1 rom on a dropbox or google drive, don't try to recover it using Corn Kernel version of cwm. Do the full wipe, factory reset and flash stable CM10.0 plus appropriate gapps from Corn kernel. Then restore your backup, if you have it.
Click to expand...
Click to collapse
Thing is, I pushed via ODIN, Cornkernel again (same I originally used) and it loads, but then the status bar (phone) just sits at full and won't show the recovery menu. I then tried CWM and got the error in the image. So why won't Cornkernel work?
I'll try KK4 later tomorrow.
Like I said, I'm new at this.
I can't flash anything from internal SD at all. It just comes up and says can't read from E: I tried CornKernel again, the CWM kernel in the CM instructions, and a stock kernel. Both stock and the CM kernel (the pic in 1st post) go into recovery but don't do anything but give errors/invalid arguments. CornKernel just reboots after the splash screen. I've done the factory reset, dalvik and cache partition cleared.
stock:
from your screenshot, you are still on wrong version of cwm, I think. Corn doesn't use 3e.
Can you get into download mode? that is the yellow triangle with the shovelling androbot.
laughingT said:
from your screenshot, you are still on wrong version of cwm, I think. Corn doesn't use 3e.
Can you get into download mode? that is the yellow triangle with the shovelling androbot.
Click to expand...
Click to collapse
I didn't screenshot Corn. The 1st screenshot is Semaphore's ClockworkMod Recovery, found here, step 1: http://wiki.cyanogenmod.org/w/Install_CM_for_captivatemtd
2nd is a stock KK4 kernel I found as suggested in previous posts.
Yes, download mode works fine. ODIN detects the phone, but Windows won't let me put anything into the E: internal storage, or external for that matter.
The image you posted is stock 3e recovery on a kk4 rom, and not CWM recovery.
you need to install Corn kernel via usb with either odin or helmdall. You can find the corn kernel in captivate development forum. It will change your existing kk4 rom by replacing the kernel and will add CWM recovery that you need, but it will still be a kk4 rom, because it doesn't change the android OS.
I flashed Corn, this is what I get. Flashed it 3 times, same result.
Just sits there.
did you flash a complete kk4 rom, verify that you are rooted, before flashing corn? if not, then, do so. see TRusselo's thread in stickies for links to complete stock kk4. you will need to do it via usb. then get rooted, then flash corn.
the full rom will be a larger tar file that will take a long time to flash.
you might want to use full odin, rather than the oneclick versions. I am assuming you are using odin 1.85 for windows. you are going to put a tar file in the pda slot, then flash the complete stock kk rom first, then root the phone. wipe the cache, wipe the dalvik cache, and do a complete boot. then verify you have root, with an app like root checker, or run superuser to check - it wont run if your are not rooted.
if all that checks out, then go back to download mode, and flash corn from odin.
Related
I'm a HTC guy here and we always just use recovery (Amon_Ra or Clockwork) to wipe data/system restore before flashing a new rom. We don't have to revert all the way back to completely stock. It seems to me that I should just be able to use the update.zip to install Clockwork recovery, do a full wipe, and flash a new rom.
If I'm already on the stock rom do I still need to ODIN before rooting/flashing or can I just root/flash? Every time I switch roms do I have to ODIN back to stock, re-root, then reflash? That sounds really obnoxious.
Just wondering if anyone can explain the difference to me because it's not making sense. I'm suddenly REALLY glad I have an HTC phone with T-mobile.
Thanks!
This confused me at first as well since I had a magic.
I think mainly it is because of the lagfixes and compatibility with some of the recovery modes. Instead of thinking whether this may be right or not, if you ODIN then flash a new rom, you get rid of potential problems compared to just the standard wipe. That's my take on it anyways and I just follow the majority.
Sent from my GT-I9000
don't blame me when your phone explodes but i've never flashed back to stock once i starting using custom ROMs. and i've flashed at least 10.
It is highly advisable when going to a new ROM to go back to stock - it will wipe the entire phone clean using ODIN vs. just doing an "update.zip" on top of the existing ROM.
Sure it is a pain in the ass - but if you think about it each Captivate ROM in the Dev Forum are completely different from each other - different kernels/modems/lagfixes/oc/uv/even playing with the sbl.bin file.
So - to prevent the new users in the world from complaining that x,y,z didn't work - they are told to flash back to stock.
And look, for me to move to a new ROM from a prior one - and this includes ODIN back to stock and restoring using Tibu - takes me 20 minutes.
My personal recommendation is to always ODIN back to stock when moving to a new ROM.
If your just doing an update and they are minor sure go ahead and flash over the top - odds are it won't hurt anything.
But.. if the chef/dev has done major changes? Go back to Odin to prevent issues when flashing to the new ROM.
And Phateless - for the "advanced" folks it goes like this to flash a new ROM:
Odin back to stock -> Run CWM's update.zip -> Flash the new ROM -> Restore & Done.
No need to re-root if you have CWM already - ODIN doesn't completely format the SDCard
avgjoegeek said:
It is highly advisable when going to a new ROM to go back to stock - it will wipe the entire phone clean using ODIN vs. just doing an "update.zip" on top of the existing ROM.
Sure it is a pain in the ass - but if you think about it each Captivate ROM in the Dev Forum are completely different from each other - different kernels/modems/lagfixes/oc/uv/even playing with the sbl.bin file.
So - to prevent the new users in the world from complaining that x,y,z didn't work - they are told to flash back to stock.
And look, for me to move to a new ROM from a prior one - and this includes ODIN back to stock and restoring using Tibu - takes me 20 minutes.
My personal recommendation is to always ODIN back to stock when moving to a new ROM.
If your just doing an update and they are minor sure go ahead and flash over the top - odds are it won't hurt anything.
But.. if the chef/dev has done major changes? Go back to Odin to prevent issues when flashing to the new ROM.
Click to expand...
Click to collapse
I agree, wiping is important and I always do it from recovery by choosing WIPE DATA/FACTORY RESET. My actual question is this:
Why not just use Clockwork Recovery to wipe? That's what I always did with my Magic 32B and what I've done so far with my Glacier. It has never caused me any trouble to do it this way.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As for the sdcard and maintaining root - I'm really not sure how that's related, as root access is under /system, which doesn't live on the sdcard, right?
avgjoegeek said:
And Phateless - for the "advanced" folks it goes like this to flash a new ROM:
Odin back to stock -> Run CWM's update.zip -> Flash the new ROM -> Restore & Done.
No need to re-root if you have CWM already - ODIN doesn't completely format the SDCard
Click to expand...
Click to collapse
That's actually how I flashed Cog 2.3b8. From her stock setup just update.zip to clockwork recovery, wipe data/factory reset, flashed Cognition and went on with my life.
QUESTION - Updating to Cog 3 do I need to uninstall lagfix before flashing anything else? Can I flash Cog 3 over Cog 2 as an update.zip without wiping data? If I do wipe will a WIPE DATA/FACTORY RESET be sufficient or do I need to ODIN? If I use the wipe through clockwork do I need to uninstall lagix first?
Sorry for all the questions, I'm still learning how all of these things interact with each other.
you need to disable not uninstall lagfix first for safe.
you can use cwm to install cog 3. but i would recommend to go back using odin and do a master clear. it will make your rom clean.
mengbo said:
you need to disable not uninstall lagfix first for safe.
you can use cwm to install cog 3. but i would recommend to go back using odin and do a master clear. it will make your rom clean.
Click to expand...
Click to collapse
So add the disable lagfix folder, reboot, then go back to cwr, wipe data flash, cog3? I would really like to avoid wiping if possible, but oh well...
that is correct. copy the cog 3 install package to your phone internal sd, remove external sd and sim before update for safe by the way .
I have a flashing problem, I don't know how to explain very well, every time I try to flash a kernel/mod etc via recovery, it disapears after rebooting the system, it won't stick there! I tried to upgrade from thunderzap to siri via CWM, and it didn't upgrade.. So I made a fresh install, flashed JB via odin, everything was fine, but now I can't flash anything via recovery, not even the CWM recovery, It shows that it's successfully flashed, but it simply disappears after the first reboot, I need held really bad. I can't find something similar, it can be a hardware problem? I successfully flashed root, but can't do nothing more, it will not "stay" in my phone. Devs, what do you think I should try?
Одг: Flashing problems
Tekie said:
I have a flashing problem, I don't know how to explain very well, every time I try to flash a kernel/mod etc via recovery, it disapears after rebooting the system, it won't stick there! I tried to upgrade from thunderzap to siri via CWM, and it didn't upgrade.. So I made a fresh install, flashed JB via odin, everything was fine, but now I can't flash anything via recovery, not even the CWM recovery, It shows that it's successfully flashed, but it simply disappears after the first reboot, I need held really bad. I can't find something similar, it can be a hardware problem? I successfully flashed root, but can't do nothing more, it will not "stay" in my phone. Devs, what do you think I should try?
Click to expand...
Click to collapse
First, CWM can't be flashed via recovery and stay. That is temp CWM. You need to install kernel with integrated CWM. You need to unpack SIRI zip, to get CWM flashable instalation. You probabli just flashed zip that contains both kernels, dd, and CWN flashable. Did you get success message after instaling it?
Sent from Galaxy S Advance
If you don't know the DD commands you can also download Universal Kernel Flash Tool and flash using this simple APP.
All you need is to download the "kernel.bin.md5" you want to flash to your phone, load it with the app and press flash (explanation in the link).
Yeah, it is successfull! For example from stock recovery I flash the CWM update zip (the separate version, as in instructions). The recovery is now CWM, I can flash everything, it says successfull, but it doesen't "stay" in my phone after reboot. Should I asume is a hardware problem? Flashing via Odin is working, flashing root zip is working as well.
I also tried flashing siri RC3 (with CWM integrated) via Terminal Emulator, it worked, but the phone it's still broken, when I try to update to RC4 via recovery, or flash anything else, it is flashed, it shows that the installing was successfully but after reboot.. boom it isn't there
Tekie said:
Yeah, it is successfull! For example from stock recovery I flash the CWM update zip (the separate version, as in instructions). The recovery is now CWM, I can flash everything, it says successfull, but it doesen't "stay" in my phone after reboot. Should I asume is a hardware problem? Flashing via Odin is working, flashing root zip is working as well.
Click to expand...
Click to collapse
How did you flash CWM. You used that Temporary CWM. Like you do not listen to me. It is Temporary because it will not stay. You need to install kernel with CWM. Because it is on the same partition. SO YOU CAN'T INSTALL CWM WITHOUT KERNEL. IT WILL BE PERMANENT ONLY WHEN IT IS INSTALED INTEGRATED INSIDE OF KERNEL. Any of our JB custom kernels have permanent CWM.
It seems i'm not a too good explainer. Is there any way to make screenshots in recovery? I will show you step by step
I installed siri RC3 via terminal emulator, now I have permanent CWM, but I can't flash anything with it, even if it says the kernel is successfully upgraded, etc. I don;t know how to take screenshots in recovery, but I have those:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Installing siri RC3)
(The siri RC 3)
(the kernel after "successfully" flashed siri RC4 via CWM)
It seems I can't flash anything via recovery, stock or CWM it doesen't make a difference, but terminal emulator or odin are fine. Another mention: I know I am kinda noob, but i'm not retarded, I know hot to use recovery, it worked fine since today...
Tekie said:
I installed siri RC3 via terminal emulator, now I have permanent CWM, but I can't flash anything with it, even if it says the kernel is successfully upgraded, etc. I don;t know how to take screenshots in recovery, but I have those:
View attachment 1749221 (Installing siri RC3)
View attachment 1749222 (The siri RC 3)
View attachment 1749223 (the kernel after "successfully" flashed siri RC4 via CWM)
It seems I can't flash anything via recovery, stock or CWM it doesen't make a difference, but terminal emulator or odin are fine. Another mention: I know I am kinda noob, but i'm not retarded, I know hot to use recovery, it worked fine since today...
Click to expand...
Click to collapse
Hm, lets do one test. I will make you flashable zip with some application and you see if it is installed. Just to figure out what app to put in system.
P.S. No, do one thing. Backup your ROM in CWM. Then use Frapeti's CWM that deodex ROM. And see if all *.odex files are gone from system/app.
http://forum.xda-developers.com/showthread.php?t=2095301
Or try black status bar mod from there. If it is changed to black, that it is working normaly.
The status bar mod worked (I did it before deodex and it worked, so I think it doesn't require deodex.. doesn't matter)
I installed deodex zip, it worked.. So the problem is only when I flash kernles or mods that are .zip ... I think I will stick to stock with a kernel that doesn't require flashing and that's all.. if you can find an answer I will be very thankful anyway.
Одг: Flashing problems
Tekie said:
The status bar mod worked (I did it before deodex and it worked, so I think it doesn't require deodex.. doesn't matter)
I installed deodex zip, it worked.. So the problem is only when I flash kernles or mods that are .zip ... I think I will stick to stock with a kernel that doesn't require flashing and that's all.. if you can find an answer I will be very thankful anyway.
Click to expand...
Click to collapse
And what file did you use for kernel, post link to see is it CWM flashable. You can't just zip it and install.
Sent from Galaxy S Advance
shut_down said:
And what file did you use for kernel, post link to see is it CWM flashable. You can't just zip it and install.
Sent from Galaxy S Advance
Click to expand...
Click to collapse
Siri kernel RC4 http://www.tusfiles.net/w043syx4a7hg
There are other things that "disappear" after flashing like moded lockscreen or moded sms. It will just not flsuh zips, I can't explain why terminal emulator is working, or why deodex.zip is installing.. I'm too tired to figure it out. Can you learn me another way to flash the RC4 kernel without recovery? thunderzap is a little choppy and siri RC3 has some vibrator bugs wich make it unusable for daily use.
Tekie said:
Siri kernel RC4 http://www.tusfiles.net/w043syx4a7hg
There are other things that "disappear" after flashing like moded lockscreen or moded sms. It will just not flsuh zips, I can't explain why terminal emulator is working, or why deodex.zip is installing.. I'm too tired to figure it out. Can you learn me another way to flash the RC4 kernel without recovery? thunderzap is a little choppy and siri RC3 has some vibrator bugs wich make it unusable for daily use.
Click to expand...
Click to collapse
You did unpack this zip and used I9070_CWM_FLASHABLE_SIRI_KERNEL_rc-4.zip? You should't flash I9070_SIRI_KERNEL_Rc-4_PACKAGE.zip. Because it contains CWM flashable zip, that you should flash, and kernel that should be flashed with DD command. It is a package, just for easy download.
And you can't flash ThunderZap from its official thread with CWM. It can be only instaled with DD command method.
For SMS you need to remove current secmms.apk to make new work. And to remove secmms.odex if you are not deodexed.
I think there is no problem with your instalations in CWM, just need to figure out how things work.
Thanks man, I totally forgot about that! I was so worried about the broken flashing thing that I forgot, thank you a lot, i will just flash with dd.
Tekie said:
Thanks man, I totally forgot about that! I was so worried about the broken flashing thing that I forgot, thank you a lot, i will just flash with dd.
Click to expand...
Click to collapse
You are welcome. And do not worry, everything is ok with your phone.
Here I can't really find the correct answer for this (or i just don't understand it)
I want to remove EVERYYYYTHING in my phones and sd card
Include the apps and roms too
And return to factory stock
I don't want to backup anything at all
(except sync my contacts)
I already download my stock roms
But of course i still do nothing with it
I am using Ultimate N7000 XXLSZ JellyBean 4.1.2 v5.2 But it seem to eat more battery than i needed
Even turned off about 2 hours it drain 3 percents battery
And turn on = EXTREMELY fast drain (with screen on)
First ... manually delete all data on internal and external SD card by mounting it as USB storage.. then boot into recovery... go to Philz settings and choose "Clean Before New Rom Install" ... then go to advanced and choose reboot download.. connect to pc and flash stock rom
nokiamodeln91 said:
First ... manually delete all data on internal and external SD card by mounting it as USB storage.. then boot into recovery... go to Philz settings and choose "Clean Before New Rom Install" ... then go to advanced and choose reboot download.. connect to pc and flash stock rom
Click to expand...
Click to collapse
I Clear manually delete all data
Then boot to recovery go to PhilZ Settings
But there is no "Clean Before New Rom Install"
There is only
Open Recovery Script
Custom Backup and restore
Aroma file manager
GUI Preferences
Save and restore settings
Reset All Recovery Settings
About
+++++Go Back+++++
PhilZ Touch 4
CWM Base version : 6.0.2.8
It's changed in the new version. Check in some menus like wipe data/factory reset or philz settings custom backup & restore or others.
Thank!!!
It's Done
Here what i do
Manual delete everything
Boot to recovery
Wipe data/Factory reset
Wipe cache partition
Wipe dalvik cache
Boot to download
Then use odin 3 to flash stock rom
So it's all stock now?
nokiamodeln91 said:
So it's all stock now?
Click to expand...
Click to collapse
Yeah
And there is no root no cwm anything at all
Just like brought from store
Well
Now i got new problem
I am going to root + cwm (PhilZ-cwm6) but there is no kernel version
I hope you know where is kernel version
It thai language
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
First you told us you want to remove everything and return to factory stock etc.
And now you want to root with Philz kernel?
So I guess it was a way to make your device clean.
Why did you install that specific version of ICS for N7000B?
(it's the latest ICS for Thailand and N7000B - maybe that's why)
And you are sure in having a N7000B?
ไม่เข้าใจภาษาไทย - อ่านได้
You can use any ics kernel like ddlrb or xxlrt
ThaiDai said:
First you told us you want to remove everything and return to factory stock etc.
And now you want to root with Philz kernel?
So I guess it was a way to make your device clean.
Why did you install that specific version of ICS for N7000B?
(it's the latest ICS for Thailand and N7000B - maybe that's why)
And you are sure in having a N7000B?
Click to expand...
Click to collapse
It like formating pirate window
Basicly
I want to remove all apps and turn it to stock rom and root it again
Well the reason i install n7000b cause my device is n7000b
Why would i install n7000 anyway if i will i think i better keep custom rom
ThaiDai said:
First you told us you want to remove everything and return to factory stock etc.
And now you want to root with Philz kernel?
So I guess it was a way to make your device clean.
Why did you install that specific version of ICS for N7000B?
(it's the latest ICS for Thailand and N7000B - maybe that's why)
And you are sure in having a N7000B?
ไม่เข้าใจภาษาไทย - อ่านได้
Click to expand...
Click to collapse
กะไว้แล้วว่าต้องเป็นคนไทย
เห็นรูปมีธงชาติไทย
Hi. here is my situation: i had the phone unlocked and on stock 4.1 firmware, rooted.
Today i wanted to try kitkat and downloaded some Xperia V 4.4 Rom. after going into recovery i started the install but i failed somewhere in the middle.
Well, ended up accidentally backing out of CWM (i had a nandroid backup) without repairing the fone and now its stuck in a bootloop. its the fastest i've seen, the phone is on for line 2 seconds (on SONY logo) then reboots. i tried adb, fastboot, but these require (i think) some level of initialization that the phone just doesnt get into.
I tried PC Companion but it says it cannot repair the phone as custom firmware is detected. Can i force it to update even in this situation?
mechlord said:
Hi. here is my situation: i had the phone unlocked and on stock 4.1 firmware, rooted.
Today i wanted to try kitkat and downloaded some Xperia V 4.4 Rom. after going into recovery i started the install but i failed somewhere in the middle.
Well, ended up accidentally backing out of CWM (i had a nandroid backup) without repairing the fone and now its stuck in a bootloop. its the fastest i've seen, the phone is on for line 2 seconds (on SONY logo) then reboots. i tried adb, fastboot, but these require (i think) some level of initialization that the phone just doesnt get into.
I tried PC Companion but it says it cannot repair the phone as custom firmware is detected. Can i force it to update even in this situation?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Use flashtool to flash a stock FTF
can you enter into cwm? if can then maybe is your original rom that not compatible with your new kernel, as i notice you completely forgot to flash back to your original stock kernel when you revert back to your nandroid backup. so just flash back to stock kernel and boot it normally.
davidtkf88 said:
can you enter into cwm? if can then maybe is your original rom that not compatible with your new kernel, as i notice you completely forgot to flash back to your original stock kernel when you revert back to your nandroid backup. so just flash back to stock kernel and boot it normally.
Click to expand...
Click to collapse
CMW backups include kernel, so that's not the issue, also in a bootloop you never get to load the hijacked chargemon, so you cant enter recovery
gregbradley said:
CMW backups include kernel, so that's not the issue, also in a bootloop you never get to load the hijacked chargemon, so you cant enter recovery
Click to expand...
Click to collapse
Then the only way is to enter fastboot mode and flash stock kernel
gregbradley said:
CMW backups include kernel, so that's not the issue, also in a bootloop you never get to load the hijacked chargemon, so you cant enter recovery
Click to expand...
Click to collapse
I did a nandroid backup, but it didnt use it. I backed out of cwm after the installation failed.. i cant get into CWM again because the LED doesnt light up. Like i said, the phone powers for like 2 seconds and then restarts.
I think the cwm i had was overwritten or is somehow unusable. i cant use any tool because the phone doesnt sat powered long enough for any tool to recognize it. i dont even think it initializes whatever it is initialized for adb and the rest
davidtkf88 said:
can you enter into cwm? if can then maybe is your original rom that not compatible with your new kernel, as i notice you completely forgot to flash back to your original stock kernel when you revert back to your nandroid backup. so just flash back to stock kernel and boot it normally.
Click to expand...
Click to collapse
I did a nandroid backup, but it didnt use it. I backed out of cwm after the installation failed.. i cant get into CWM again because the LED doesnt light up. Like i said, the phone powers for like 2 seconds and then restarts.
I think the cwm i had was overwritten or is somehow unusable. i cant use any tool because the phone doesnt sat powered long enough for any tool to recognize it. i dont even think it initializes whatever it is initialized for adb and the rest
Flash a stock kernel, use doomkernel, enter Recovery and restore your backup
Leave it on charge for a few hours first
Sent from my C6903 using XDA Premium 4 mobile app
Hey folks,
So I'm trying to load android 2.3.6 on my i9000 (it was previously running 4.2). The thing is, it's home button is broken so I can't easily access the recovery mode. So I've built a jig, forced the phone into download mode, and from there on flashed 2.3.6 using THIS method.
The phone then automatically reboots into Clockworkmod Recovery 3.0.0.5. I then wipe dalvik and cache, and factory reset the phone. Then when I'm trying to boot into android, the phone enters a bootloop. It doesn't even show the boot animation, just the Galaxy S black/white splash screen. At that point I can't seem to get back into the recovery, because of that broken home button.
What I've done so far:
- Checked that my SD card isn't faulty. I can perfectly browse files with the recovery. Mounting the SD card however doesn't work. I don't know why.
- Before I used heimdall to flash the ROM, I tried using Odin v1.83. I clicked repartition and used a 512.pit file. Could it be that my partitions are messed up?
- My end goal is to flash Cyanogenmod 10.2.1. I tried flashing the 10.2.1 .zip (it was still on my sd card, luckily) through the recovery. But that also results in a boot loop, where I cannot get past the boot animation. I know a solution to that would be to clear user data and dalvik again, but I don't know how to get into recovery mode from there.
So, any ideas what I could do? I have a feeling that something's up with my partitions, but I don't have the knowledge to know for sure. Any help is very much appreciated!
vindikleuk said:
So, any ideas what I could do? I have a feeling that something's up with my partitions, but I don't have the knowledge to know for sure. Any help is very much appreciated!
Click to expand...
Click to collapse
Follow
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[Tutorial] How to Unbrick, Flash, Downgrade, Root, Update i9000 from Froyo to Kit Kat and use PIT file, to repartition with the JVU 2.3.6
Check this out! Links to useful Guides and " Banned " Documentaries
vindikleuk said:
Hey folks,
So I'm trying to load android 2.3.6 on my i9000 (it was previously running 4.2). The thing is, it's home button is broken so I can't easily access the recovery mode. So I've built a jig, forced the phone into download mode, and from there on flashed 2.3.6 using THIS method.
The phone then automatically reboots into Clockworkmod Recovery 3.0.0.5. I then wipe dalvik and cache, and factory reset the phone. Then when I'm trying to boot into android, the phone enters a bootloop. It doesn't even show the boot animation, just the Galaxy S black/white splash screen. At that point I can't seem to get back into the recovery, because of that broken home button.
What I've done so far:
- Checked that my SD card isn't faulty. I can perfectly browse files with the recovery. Mounting the SD card however doesn't work. I don't know why.
- Before I used heimdall to flash the ROM, I tried using Odin v1.83. I clicked repartition and used a 512.pit file. Could it be that my partitions are messed up?
- My end goal is to flash Cyanogenmod 10.2.1. I tried flashing the 10.2.1 .zip (it was still on my sd card, luckily) through the recovery. But that also results in a boot loop, where I cannot get past the boot animation. I know a solution to that would be to clear user data and dalvik again, but I don't know how to get into recovery mode from there.
So, any ideas what I could do? I have a feeling that something's up with my partitions, but I don't have the knowledge to know for sure. Any help is very much appreciated!
Click to expand...
Click to collapse
Flash proper/stock jvu not any rooted or customized one. Then root it and then flash your ROM properly...
Sent from my GT-I9000 using Tapatalk 2
TeKnoGin said:
Flash proper/stock jvu not any rooted or customized one. Then root it and then flash your ROM properly...
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
Wow, how did I not think of that? Thanks!