Hi,
We have a problem with an Optimus 2X.
1. We rooted the phone
2. Installed ClockworkMod recovery from ROM Manager (Flash recovery option). Successful window appeared.
3. We boot in recovery mode from ROM Manager.
The phone now hangs on boot at the LG Logo. There is no way to boot in recovery, and there is no way to do a normal boot. (Tried to boot with volumen down and lock buttons pressed, and without pressing volume down...)
It's like there was a flag that forces the phone to "boot in recovery" or something like that.
So we can't boot the phone in any mode...
We also tried smartflash, but nothing...
Any idea? How can we restore it?
Thank you very much in advance...
I would try the procedure at this link: add "http:" infront of my links, for some reason i'm not allowed to post outside links.
//android.modaco.com/content/lg-optimus-2x-2x-modaco-com/335474/25-mar-nvflash-stock-rom-release-v10b-dated-1300166062-15-03-2011/
It uses the nvidia flash tool and will allow you to flash a clean stock rom without booting up the device or going into clockwork.
The stock rom version that you can download on the link above will do fine. After you've flashed the stockrom you can reinstall clockworkmod. If I were you I would do that using these instructions:
//android.modaco.com/content/lg-optimus-2x-2x-modaco-com/335479/10-may-3-0-2-8-clockworkmod-recovery-for-the-lg-optimus-2x/
Basically all you need to do is attach the phone to the computer, make sure usb debugging is enabled and double click the install clockworkmod.bat file found in the extracted zip file downloaded from the link below.
http://forum.xda-developers.com/showthread.php?t=1098745
After that you should be able to flash all the custom roms you want. I hear the latest Cyanogen nightly is pretty stable!
I had the same problem and question a couple of days ago...
Mine also when trying to install CWM..
Follow this link and flash with NVflash and You should be good to go again
http://android.modaco.com/content/l...rom-release-v10b-dated-1300166062-15-03-2011/
I also gave up on the CWM flashing from PC and paid for this app in the market:
https://market.android.com/details?id=com.modaco.twoxrecoveryboot&feature=search_result
Its .99 pence so not to bad... remember You NEED ROOT for the CWM recovery flashy thingy
After all flashing I just went with the stock ROM with the 0606 upgraded baseband
Works ok now (flashed with smartflash)
The 0606 baseband ROM can be found here:
Happy unbricking!
Thank you very much to both!
NVflash did the trick and I could fix the full brick!
Now I don't fear anything... nvflash can resurrect it!! xD
Thank you very much!!!!!
THANK YOU SO SO SO SO SO SO MUCH GUYS!!!!!!!!
i was messing about for about 5 hours because my apx driver didn't successfully install but i finally found one and got it to work.
i am so relieved. I can sleep easy tonight
once again a huge thanks.
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 im using [XXBLL5-V8] Ripper Rom with Perseus Kernel and 23 toggles .. i tried to install the Moto theme and the Alexander one but they don't change anything .. i tried to install a theme for multi-window but that don't change anything either .. what i`m doing wrong ?
1) installed the rom with factory restore and format sistem and wipe all
2) install Perseus kernel
3) make rom little with apk from updateme
4) install 23 toggles
5) install alexander theme ( no change )
6) install moto theme (no change )
7) install theme for multi window (no change )
What recovery are you using. The themes are VR Themes and are not compatible with TWRP recovery but should work for CWM recovery. If you are using CWM is there free space on the internal storage as the zip has to extract the files and mod them on the storage and then sends puts them into the system. If you have an external sd you could try to move the theme zip file from the internal storage to external and see that lets you flash it
will this work on a GT93005t
Thanks
Simon
i9305T, yes.
I using TWRP recovery so this is the culprit , will the touch CWM work ? I really don't like the normal one with the volume keys and all :crying:
If you want a touch CWM then I recommend using Philz.
Check this thread out http://forum.xda-developers.com/showthread.php?t=2091223
Has link to original thread with download links
Will the http://forum.xda-developers.com/showthread.php?t=1995320&page=129 work with your rom , i want the normal icons and the mod for transparent bar and notification .. cant make it work
Do we have a custom SystemUI that we can flash so the mods for 23 toggles and Drop Down Mods will work ,or do they have to be made specific for the 9305 ?
The Motomoto theme say it install a new bootanimation , but i have the original animation still
PaulM_Ro said:
I using TWRP recovery so this is the culprit , will the touch CWM work ? I really don't like the normal one with the volume keys and all :crying:
Click to expand...
Click to collapse
hey saw your situation and thought i had a very similar one that could be note worthy. i have been using pandariam for awhile now and absolutely love it. thats besides the fact, i had followed his instrutions on installing the cwm recovery 5.5 because of everyone having problems with the touch versions. now whenever the 5.7 release came out i just recently updated to TWRP which cause all themes that were availiable in his pacage to prove unworkable. i had tried probably about 7-8 times before backdating to CWM recovery 5.5 until the kinks are worked out. the touch is nice and user friendly but not when ever it doesnt work with the user's wishes. hope this helped a little and if u run into a problem connecting to your pc or flashing back to cwm 5.5 PM me because i ran into a data network hiccup and a one whenever i tried to flash back to the older version.
Just rooted my phone and tried to instal CM10.1 but now the phone wont start,its stucked at the LG logo.
The only thing thats working is the CWM.
I have tried another version of CM10.1 but still wont start.
SirIntegra said:
Just rooted my phone and tried to instal CM10.1 but now the phone wont start,its stucked at the LG logo.
The only thing thats working is the CWM.
I have tried another version of CM10.1 but still wont start.
Click to expand...
Click to collapse
Are you on new bootloader when you tried to install CM10.1? (New Bootloader = LG with Red splash, Old Bootloader = Pure White LG letters with Icon) You must be on old Bootloader (For Gingerbread) before doing so.... I recommend you clean first the bootloader and partition using WKPARK's file and guide here: http://forum.xda-developers.com/showthread.php?t=1968280, APX Drivers can be grabbed here: https://www.box.com/s/c5d0e911cz9jhz3ab9y1 Credits to umar for reuploading. After that you will have to mount cleaned system on CWM and format your internal SD, then flash nightly rom patched by Wkpark's CM10 patcher so that buttons would work, and flash su660ics' provided kernel by a vietnamese developer here.
Well,thank you verry much for the info!
Anyway,now i`m back tt the stock ROM (GB 2.3.4).
But i still wanna instal CM10.1,or at least CM10 and i`m still wondering why the installation didnt work ??
I mean,i have followed 100% a tutorial on how to install CM10.1.
I tried once but the phone booted with the same ICS 4.0.4,then i tried again,the same result,and the last time when i tried i got stuck at that LG logo,but now its ok.
But how can i install CM10.1 or another version ?? I didnt do anything wrong...i think it didnt work because there are some problems that i`m not aware of...
So , i rooted my X8 yesterday and then installed CWM. Everything went fine (I was following tutorials made here - awesome work by the way)
then when i loaded 3 custom roms , i went to CWM made a backup , formated cache , data , system and then when i tried installing them i got the error 7. ive seen that its a common error. So after that , i couldnt load the phone and it was stuck in "Sony Ericsson" screen forever. couldnt load CWM aswell. Then i flashed the original ftf and it booted normally. rooted again and installed CWM. Next thing , i flashed 2.6.29.6-nAa-jb-03 Custom jb kernel. Everything went fine , then i formated data , cache and system. But when i tried to load the Roms it couldnt mount sd card.
So now i can neither install a rom nor restore the phone.
Can someone help me ?
(by the way , phone stays at nAa Freedom Within screen. or the CWM )
What's the point in flashing that kernel?
Sent from my E16i using Tapatalk 2
XPERIAnced said:
So , i rooted my X8 yesterday and then installed CWM. Everything went fine (I was following tutorials made here - awesome work by the way)
then when i loaded 3 custom roms , i went to CWM made a backup , formated cache , data , system and then when i tried installing them i got the error 7. ive seen that its a common error. So after that , i couldnt load the phone and it was stuck in "Sony Ericsson" screen forever. couldnt load CWM aswell. Then i flashed the original ftf and it booted normally. rooted again and installed CWM. Next thing , i flashed 2.6.29.6-nAa-jb-03 Custom jb kernel. Everything went fine , then i formated data , cache and system. But when i tried to load the Roms it couldnt mount sd card.
So now i can neither install a rom nor restore the phone.
Can someone help me ?
(by the way , phone stays at nAa Freedom Within screen. or the CWM )
Click to expand...
Click to collapse
re insert the sd card, i too have experienced this problem many times, try it mate
Okay , so i tried inserting it again and again. nothing really changed.
Gogeta to be honest , im a total newb @ these things i just started readin about custom roms rooting e.t.c
So , can you tell me why i didnt need to flash that kernel?
i mean i wanted to instal MiniCM10 and the requiremenents were these
Requirements:
Latest 2.1.1.A.0.6/2.1.1.C.0.0 SE firmware / Baseband: M76XX-TSNCJOLYM-53404015
Unlocked bootloader
Latest version of the 2.6.32 nAa JB kernel
latest not old, naa05 is the latest
Sent from my katana with a sharpness over 9000!
Oh , so that would be the problem right?
How do i fix this? i need to flash the original tft then root again - install recovery - unlock using s1tool and then flash the latest nAa?
Thank you by the way.
you can enter recovery so you can flash the new version by wiping data cache and system, but first, is your sd card formatted? format it first to avoid those problems
Sent from my katana with a sharpness over 9000!
XPERIAnced said:
Okay , so i tried inserting it again and again. nothing really changed.
Gogeta to be honest , im a total newb @ these things i just started readin about custom roms rooting e.t.c
So , can you tell me why i didnt need to flash that kernel?
i mean i wanted to instal MiniCM10 and the requiremenents were these
Requirements:
Latest 2.1.1.A.0.6/2.1.1.C.0.0 SE firmware / Baseband: M76XX-TSNCJOLYM-53404015
Unlocked bootloader
Latest version of the 2.6.32 nAa JB kernel
Click to expand...
Click to collapse
You said it yourself, its .32 kernel not .29 which u flashed
XPERIAnced said:
Oh , so that would be the problem right?
How do i fix this? i need to flash the original tft then root again - install recovery - unlock using s1tool and then flash the latest nAa?
Thank you by the way.
Click to expand...
Click to collapse
Just flash the latest 2.6.32 nAa jb ftf
sent from your device using Facebook app :screwy:
i tried flashing the latest but i get an error 995 it also says that i need to install the drivers for the device and the flashtool but they are already installed
- EDIT.
It works. thank you very much everyone, i just flashed one more time and it worked. its really amazing.
One last thing. whats that zip with google apps? should i install it too ?
yeah you should after installing the rom, good luck!
Sent from my katana with a sharpness over 9000!