i9305 (soft) bricked after twrp OTA flash - Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help &

Hi guys, I did a terrible mistake.
Currently I was using my S3 i9305 with AICP 10. To update with the OTA they require TWRP and I thought, why not changing from CWM 6.0.4.7 to the most recent TWRP so that the update process will go fully automatic.
I downloaded the App, but didn't make a Nandroid backup before. Then I installed the proposed TWRP version for my phone. After that the Phone restarted and was stuck at the samsung-logo - restarting every 5 seconds.
So what do I have now?
I have a phone that goes until the bootanimation of ACIP. But then it is looping. ... for hours. I can go into download mode and I already got access to TWRP or CWM - I can install both with Odin v3.09
After researching for more than 4 hours I may kindly ask for your help.
What can I do to get my phone back on? I don't care about the data on the phone. (I already copied the internal SD to my computer).
I tried to reinstall the AICP 10 + Gapps, but that did not work.
Is there anybody out there who is able to help the stupid me?
Thank you very much in advance.
Greetings
Peter

Solved - Installed the Original Samsung FIrmware from Sammobile - then went back to TWRP and then to my ROM.
Please close

Related

[Q] CWM Error - Status 7

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.

[Q] [GT-S6500D] Problems with CWM & BOOT

Okay so I searched on this forum to see is there a post similar to mine, but couldn't find a fix to my problem..
So, three weeks ago I rooted my device, installed cwm and everything that was needed, and I did it. The same day somehow i rebooted with ROM Manager, and I couldn't get out of clockworkmod, and I don't know how (probably by some other tutorial on this forum for rooting, I flashed clockworkmod-jena.5.2.0.8.tar.md5 via Odin3 v1.85 , instead of clockworkmod-5.0.2.8.tar.md5 , and i somehow managed to get into normal mode again... Everything was working till today, when I got a notification about some software update, and when I pressed the Reboot button, it booted into recovery and I can't get out of cwm for three hours now.. I tried the stuff i did the last time - no result. I restored data from my previous backup, still no result. I formatted data and cache, again no result. Downloaded a Stock Backup.zip file, and again it boots in cwm. I really need your help about this, I don't know what I'm doing and I don't wanna do something bad and brick my phone..
Thanks, I hope I'll get a reply :S
download official stock firmware from http://www.sammobile.com and flash it via odin, and don't use cwm manager again:good:

S3 MINI GT-I8190N Boot Loop HELP

Hi guyes, I really messed up tired to install a rom on my S3 Mini (CM 11.0 KitKat) came up with status 7 installation aborted
, backed out rebooted the phone goes straight into CWM wiped the davlik cache and cache, rebooted the phone same boot again straight into CWM, took out battery gave it 2 minutes no help. Really need some help Please:crying:
Jhamat123 said:
Hi guyes, I really messed up tired to install a rom on my S3 Mini (CM 11.0 KitKat) came up with status 7 installation aborted
, backed out rebooted the phone goes straight into CWM wiped the davlik cache and cache, rebooted the phone same boot again straight into CWM, took out battery gave it 2 minutes no help. Really need some help Please:crying:
Click to expand...
Click to collapse
Mhhm,
Did you install using Odin or via CWM?
Try installing another ROM with CWM.
If that doesn't work, try to install Stock ROM back.
danielsinnema said:
Mhhm,
Did you install using Odin or via CWM?
Try installing another ROM with CWM.
If that doesn't work, try to install Stock ROM back.
Click to expand...
Click to collapse
Hi there I installed using cwm, I have been looking for the stock rom, but havent been able to find it, Thanks in advance
Jhamat123 said:
Hi there I installed using cwm, I have been looking for the stock rom, but havent been able to find it, Thanks in advance
Click to expand...
Click to collapse
Stock ROMs from Samsung can be found here: http://www.sammobile.com/firmwares/
Search for your device in the search bar.
Type: ''GT-I8190N''.
Download the right ROM. (Your country and eventually your provider).
Download and install Odin 3.07 (if you hadn't already).
Download and install Samsung Drivers for mobile phone. (If you hadn't already).
How to flash:
1) Go into recovery mode and perform a factory reset.
2) Open Odin Downloader.
3) Turn system off and go into Download mode.
4) Connect device to PC using USB cable.
5) Odin should recognize your phone now, if not: Check if Samsung Drivers have been installed correctly.
6) Click on PDA and add the file you have just downloaded from sammobile.
7) Make sure ''Auto Reboot'' and ''F. Reset Time'' is enabled.
8) Press start and wait untill the installation is finished.
9) Done.
If you are not familiar with this, ask me for more details and I'll explain more.
Jhamat123 said:
Hi guyes, I really messed up tired to install a rom on my S3 Mini (CM 11.0 KitKat) came up with status 7 installation aborted
, backed out rebooted the phone goes straight into CWM wiped the davlik cache and cache, rebooted the phone same boot again straight into CWM, took out battery gave it 2 minutes no help. Really need some help Please:crying:
Click to expand...
Click to collapse
Download MaclawStudio’s TWRP Recovery v2.6.3.0
flash it whith CWM and flash rom again
it will solve your problem
It's working!
Thank you guys. Since yesterday I had the bootloop problem and tried everything to solve it. Flashed various stock roms and nothing worked. Now this one worked. Thank you again!

I9001 bricked/soft-bricked, please help

Hi!
Today i wanted to update my firmware just because Samsung Kies asked me if i wanted to. I couldn't have been more wrong when i chose to update.
The update froze at 3% and after a lot of time i unplugged the phone and ended up with a brick instead of a phone.
If i try to turn it on, i get a black screen with a "phone--!--pc" picture. I can enter Download Mode by pressing VolumeDown + HomeButton + PowerButton and i get an android logo with ''Downloading... Do not turn off target'' written under it.
My phone was never rooted, nor updated ( it remained with its out-of-the-factory OS and everything ).
For the past 6 hours i've been trying to use Odin v4.43 along with AriesVE.ops (the one from the well-known WORKED2 archive) to try and get recovery-clockwork to work.
So my questions are:
Given the fact that my phone was not rooted, how can i get my GT-I9001 to work again? Is this even possible?
Can i first root it in its condition, then flash a custom rom like cyanogenmod? Or do i need to install a stock rom and then try a custom one?
What other options do i have?
Everything i've tried so far with Odin froze while downloading and i have no other solution to this problem. Please help!
zerkylo said:
Hi!
Today i wanted to update my firmware just because Samsung Kies asked me if i wanted to. I couldn't have been more wrong when i chose to update.
The update froze at 3% and after a lot of time i unplugged the phone and ended up with a brick instead of a phone.
If i try to turn it on, i get a black screen with a "phone--!--pc" picture. I can enter Download Mode by pressing VolumeDown + HomeButton + PowerButton and i get an android logo with ''Downloading... Do not turn off target'' written under it.
My phone was never rooted, nor updated ( it remained with its out-of-the-factory OS and everything ).
For the past 6 hours i've been trying to use Odin v4.43 along with AriesVE.ops (the one from the well-known WORKED2 archive) to try and get recovery-clockwork to work.
So my questions are:
Given the fact that my phone was not rooted, how can i get my GT-I9001 to work again? Is this even possible?
Can i first root it in its condition, then flash a custom rom like cyanogenmod? Or do i need to install a stock rom and then try a custom one?
What other options do i have?
Everything i've tried so far with Odin froze while downloading and i have no other solution to this problem. Please help!
Click to expand...
Click to collapse
Yes it is possible as long as your device boots into Download mode.
No you can't root it in its current condition.
You need to download a stock firmware, flash it using Odin or Heimdall (recommended), then root it and finally install a custom ROM if you want.
kalpetros said:
Yes it is possible as long as your device boots into Download mode.
No you can't root it in its current condition.
You need to download a stock firmware, flash it using Odin or Heimdall (recommended), then root it and finally install a custom ROM if you want.
Click to expand...
Click to collapse
Thank you for answering!
I fixed the issue. Tried different usb port along with a different version of CWM (5.5.0.4) which I installed with Odin v4.43. CWM 5.5.0.4 caused a bootloop, but i used it only to install CWM 6.0.4.9 from external_sd, so the bootloop problem was gone. Then flashed CyanogenMod 11 and now works like a charm !
I attached an archive with CWM 5.5.0.4, AriesVE.ops and Odin v4.43, so that anyone having my problem can solve it the way i did. But keep in mind that this version of CWM *may* cause a bootloop, so prior to installing it, you should have a working version of CWM on your external_sd. Use CWM 5.5.0.4 to install the better version of CWM from your external_sd. Also, whatever you do is at your own risk!

[Q] Can't Install KitKat on s3 mini HELP!

Here are two posts I posted on another site. If someone could help me out here, it would be greatly appreciated.
Post 1
I have a Galaxy s3 mini GT-I8190L and I tried rooting and installing Kitkat but I've been having some issues.
Here is what I did:
Downloaded Odin and Kies (for the phone drivers, Kies was closed while using Odin)
Downloaded CMW Recovery and a root.zip file
Flashed CMW and placed the root.zip on extSD card.
In Recovery mode, backed up system then installed the root file.
Downloaded Root Checker and it said I have root.
Then downloaded slim4.4_golden.nova.20140630.zip and a gapps file and placed them both on the extSD.
Using Recovery (Vol Up+Home+Power), wiped data and davika (whatever it's called) and then flashed slim4 file. But I got an error.
I then tried cm11.0_golden.nova.20140823.zip which went smoothly and then gapps-kk-20140606-signed.zip but in middle it stopped with an error and said something about process 7 (I think).
Anyone know what I should do? Would it be better to go through Odin instead of Recovery (using Odin compatible files, of course)?​
Post 2
Changed to TWRP2
Backed up all data then did a full format incl. chache and davlik.
Then installed th SlimKAT file and gApps.
(I did NOT format chache after install)
Rebooted pone and saw Galaxy sIII mini screen like normal then cam SlimKAT logo (replacing Samsung's) but it just remained on the flashing SlimKAT logo.
I removed the battery and restored the phone using TWRP Recovery.
I then downloaded Nova Fusion's CM11 for s3 mini and tried flashing it but I got a Failed message. This happened with a number of Nova's files, including the latest (cm11.0_goldem.nova.20140830.zip)
I tried downloading the Odin version but for some reason it keeps stopping in middle (and I don't have unlimited internet and can't keep downloading files).
Didn't think this should be so hard...
Any help would be appreciated!​
Please note, during part of this time I was unable to get into DOWNLOAD or RECOVERY modes. I ended up removing the battery and that helped, but for only one time. I had to remove the battery a number of times to get into these modes.
If you need more info, I will try to give it. Any help would be appreciated. Thanks!
SiDi™
Go to NovaFusion.pl/download/ and choose you want rom and click odin andthen download andthen flash via odin
Try it, I don't know it is working or not
send for I8190N R-Mod v3 using XDA Premium 4 mobile app
SayIDidIt™ said:
Here are two posts I posted on another site. If someone could help me out here, it would be greatly appreciated.
Post 1
I have a Galaxy s3 mini GT-I8190L and I tried rooting and installing Kitkat but I've been having some issues.
Here is what I did:
Downloaded Odin and Kies (for the phone drivers, Kies was closed while using Odin)
Downloaded CMW Recovery and a root.zip file
Flashed CMW and placed the root.zip on extSD card.
In Recovery mode, backed up system then installed the root file.
Downloaded Root Checker and it said I have root.
Then downloaded slim4.4_golden.nova.20140630.zip and a gapps file and placed them both on the extSD.
Using Recovery (Vol Up+Home+Power), wiped data and davika (whatever it's called) and then flashed slim4 file. But I got an error.
I then tried cm11.0_golden.nova.20140823.zip which went smoothly and then gapps-kk-20140606-signed.zip but in middle it stopped with an error and said something about process 7 (I think).
Anyone know what I should do? Would it be better to go through Odin instead of Recovery (using Odin compatible files, of course)?​
Post 2
Changed to TWRP2
Backed up all data then did a full format incl. chache and davlik.
Then installed th SlimKAT file and gApps.
(I did NOT format chache after install)
Rebooted pone and saw Galaxy sIII mini screen like normal then cam SlimKAT logo (replacing Samsung's) but it just remained on the flashing SlimKAT logo.
I removed the battery and restored the phone using TWRP Recovery.
I then downloaded Nova Fusion's CM11 for s3 mini and tried flashing it but I got a Failed message. This happened with a number of Nova's files, including the latest (cm11.0_goldem.nova.20140830.zip)
I tried downloading the Odin version but for some reason it keeps stopping in middle (and I don't have unlimited internet and can't keep downloading files).
Didn't think this should be so hard...
Any help would be appreciated!​
Please note, during part of this time I was unable to get into DOWNLOAD or RECOVERY modes. I ended up removing the battery and that helped, but for only one time. I had to remove the battery a number of times to get into these modes.
If you need more info, I will try to give it. Any help would be appreciated. Thanks!
SiDi™
Click to expand...
Click to collapse
Enable 3 button combo?
http://forum.xda-developers.com/showthread.php?t=2157105
CWM doesnt support KitKat, you need TWRP or Philz touch.
or flash via odin

Categories

Resources