Hi,
I'm having a major issue with not being able to flash roms using clockworkmod for some strange reason.
I decided to move from MIUI rom because every time I gave it a chance when new versions came out, it constantly let me down with countless bugs and such. So, I've decided to go back to modified stock ROMs as they seem more reliable.
When I attempted to flash using clockworkmod (that comes with MIUI) it failed to apply the new (non-MIUI) ROM and forced it to go into a bootloop which knackered up going into recovery, so my only other option was to go into download mode and flash a stock ROM (I chose the latest, I9000XXJW4), root it, flash cyanogenmod and try again.
But unfortunately this did not work and now I'm stuck on the stock ROM.
I've taken a video of the exact moment it all goes wrong. Also, below is each step taken of the process.
youtube.com/watch?v=EmZAZ3DeL2U
1) Download Samsung Value Pack (I9000XXJW4) and CF-Root-XX_OXA_JW4-v4.4-CWM3RFS
2) Galaxy S rebooted to download mode
3) Used Odin3 1.85 to apply JW4_JW4_JW4.TAR file to the PDA section. Re-Partition is not checked.
4) Allowed the device to reboot to the home screen.
5) Powered off the device and booted back to download mode
6) Used Odin3 1.85 to apply CF-Root-XX_OXA_JW4-v4.4-CWM3RFS.TAR to the PDA section. Re-Partition is not checked.
7) Allowed the device to reboot to the home screen (The video begins now).
8) Launched the CWM application (with root permissions) and rebooted to Recovery.
9) Wipe data/factory reset selected and confirmed
10) Wipe Dalvik Cache selected and confirmed
11) Format /system selected and confirmed
12) Install zip from SD Card, Choose Zip from sdcard and update-cm-7.1.0-GalaxyS-signed.zip selected and confirmed.
13) Here is an extract from the log that follows before rebooting:
- Finding update package...
- Opening update package...
- Installing update...
- Checking state of BML/MTD...
14) Self-Rebooted
15) Boot-loop
Any help is greatly appreciated!
Thanks,
Andy
when it bootloops it does it cause it just flashed the kernel and its trying to run the stock rom on the cynogen kernel. so pull the battery, put it back in. reboot into recovery and flash the rom again. it should work the second time cause its using the cynogen mods version of cwm recovery. let it boot it will take a while. but that should work.
dont forget to hit thanks!
taz0697 said:
when it bootloops it does it cause it just flashed the kernel and its trying to run the stock rom on the cynogen kernel. so pull the battery, put it back in. reboot into recovery and flash the rom again. it should work the second time cause its using the cynogen mods version of cwm recovery. let it boot it will take a while. but that should work.
dont forget to hit thanks!
Click to expand...
Click to collapse
Genius!
Thank You!
Cannot believe the solution was staring at me the entire time!!
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.
Okay so, I'm not exactly sure if this is the right place but I'll ask here anyway.
I took my old i9000 out of the closet and started playing around with it as I want to use it on my upcoming travel. To make long story short, I used to have a custom ROM on the phone all those years ago, but I am by no means an expert on the subject.
So what I have done so far today:
1. Returned the phone to stock ROM with Odin (XWJW1 or something, most recent anyway)
2. Rooted with Semaphore 2.7.4.
3. Installed Rom Manager and Superuser to check for CWM updates (which caused some sort of a verification error when I tried to boot to CWM through the app).
4. Downloaded the appopriate Slimkat and gapps and moved them into the internal storage.
But after the last step (and after wipe cache, format system etc) when I try to install the ROM, the bar on the screen progresses only slightly and after "Installing update..." it crashes (just goes black without any error messages) and gets stuck with just "Semaphore" on the screen.
I wish to update the phone to Slimkat 4.4.2. But what causes this problem, any ideas? Am I doing something wrong? If anyone can give any help that would be much appreciated!
PS. If I wanted to install for example Philz recovery, how am I supposed to do it when the file is .img?
Anyone?
I guess no one is using this phone anymore?
Yes, you are doing many things bit wrong.... (and many people use this phone still). I hope following will help you:
*recovery and kernel are sharing the same partition on the i9000 what means that you can't flash recovery separately
*make sure to backup your IMEI if still there
*flash first CM10.2 to get updated recovery for KitKat roms and to resize the system and data partitions to those used by all KitKat roms and reboot once into the system. You will need to flash trice to make it work (1. only warning of resizing to come and data lost- and status 7 abort, 2. only recovery update, 3. successful flashing)
*flash SlimKat and latest SlimGapps (addons) for 4.4.4
*PhilZ touch screen isn't yet working well on the i9000 but if you flash Mackay KK kernel, you can get beautiful TWRP touch recovery
tetakpatalked from Nexus 7 flo
Hi guys,
First of all, i made a new thread after looking for a solution for days and pretty much everywhere.
• My issue : i can't get any custom rom to boot. Everytime i flash one, i get stuck with endless bootanim
• so you know :
- flashing original firmwares from sammobile or stock based roms (i.e N4elite) with odin or recovery works perfectly. roms boot and everything work flawlessly.
- i tried almost every lollipop roms (RR, Nameless 2.0 and 2.1, cm12.1, asop, aicp)
- i tried different recoveries (CWM, TWRP, PSN_TWRP)
- i tried different gapps packages
- all downloaded files were good
- i tried wiping everything, even tried changing file system to f2fs (and reverted back to ext4)
- i guess flash memory is ok since Sammy roms work
- my battery is almost new, i changed it not so long ago
- i was running an early cm12.1 build and everything was ok, the issue occured when i tried to flash cm12.1 stable 3 build
As i'm now out of idea, any suggestion would be appreciated.
Thanks !
fraydz said:
Hi guys,
First of all, i made a new thread after looking for a solution for days and pretty much everywhere.
• My issue : i can't get any custom rom to boot. Everytime i flash one, i get stuck with endless bootanim
• so you know :
- flashing original firmwares from sammobile or stock based roms (i.e N4elite) with odin or recovery works perfectly. roms boot and everything work flawlessly.
- i tried almost every lollipop roms (RR, Nameless 2.0 and 2.1, cm12.1, asop, aicp)
- i tried different recoveries (CWM, TWRP, PSN_TWRP)
- i tried different gapps packages
- all downloaded files were good
- i tried wiping everything, even tried changing file system to f2fs (and reverted back to ext4)
- i guess flash memory is ok since Sammy roms work
- my battery is almost new, i changed it not so long ago
- i was running an early cm12.1 build and everything was ok, the issue occured when i tried to flash cm12.1 stable 3 build
As i'm now out of idea, any suggestion would be appreciated.
Thanks !
Click to expand...
Click to collapse
Hello,
I got the same issues ...
Trying to root the Stockrom results in the disappearance of baseband. Maybe this could help? I need to get some sleep first.
Regards
Heiko
EDIT: I thought maybe I fill in a bit more detail. I had CM 11 running which also flashed my recovery to cwm. So I used the TWRP Manager to install new Recovery, but I didn't check the Partition! So it didn't work as planned. Phone was in a boot loop and restartet every 5s. But TWRP via Odin worked. I wiped every partition available in Odin and installed Stock. Which seems to work without root.
CM 11 results in a boot loop.
CM 10.3 boots up, bud doesn't find the modem (same as Stock with root)
I hope there is some help. I like this phone a lot.
I did reinstall Samsung Stock via Kies.
And thank god that solved the Problem.
Restored my backup and everything is working again.
Heikoles said:
I did reinstall Samsung Stock via Kies.
And thank god that solved the Problem.
Restored my backup and everything is working again.
Click to expand...
Click to collapse
thanks for your feedback and ideas.
i tried to flash stock with kies, it ended with an error, but flashing stock firmware with odin worked, and everything was ok (including modem)...
for now i'm stuck with stock firmware flashed with odin
EDIT :
i finally succeeded.
- flashed old 4.3 firmware with odin without auto reboot
- the flash failed at the end
BUT
- manual reboot in download
- flashed TWRP tar
- reboot in recovery
- flashed 4.3 modem zip
let system boot
reboot in recovery
flash any rom and gapps !
Hi everyone,
some who frequently read the forum may know already that there are issues with the latest official TWRP for the Galaxy S3 LTE. The recovery partition on the Galaxy S3 LTE is too small for the latest recovery provided by TWRP. The partitions are messed up, you won't be able to mount /system and /data. Some users couldn't even flash their preferred ROM. As of now the buggy recovery is getting fixed.
I am not responsible for any damage, losing data or weird behavior you encounter while doing one of the following steps. As reported by several users step 1 was the way for them to fix their phone. Be sure of what you're doing. Make sure you know how to boot into recovery/Download Mode to do these things mentioned here and how to use odin. If not, XDA users have provided several guides. Use the search.
If you already flashed the faulty recovery, flashed a custom ROM with it and your phone ends up in a bootloop there are several ways to fix this issue.
1. Via odin and official stock firmware - please note: You might lose all your data you have on your internal storage
Download the latest official Samsung firmware from sammobile or look on XDA for provided stock ROMs by the AMCHA team. Boot your phone into Download Mode and flash the official firmware via odin. If you're done, reboot into stock recovery (which will be provided after flashing the stock firmware), perform a factory reset and let your phone boot up once. First boot might take some time, so be patient. Although the first boot might not be needed, do it anyway to see if your phone is still in a bootloop or suffers from other damage. If the phone boots up fine reboot into Download Mode again, flash TWRP 2.8.5.0 or any other latest custom recovery (preferably the recovery the maintainers recommend in their development threads) and flash your preferred ROM. Your phone should now work as it should.
2. Via stock based custom ROM (if you haven't flashed any ROM via TWRP 2.8.7.0 already - please note: You might lose all your data in this process as well
Some users managed to get their phone working by flashing a stock based custom ROM like AMCHA or N4 Elite. If you only flashed the buggy recovery and didn't flash a custom ROM this way should be the step you should try first. Download any stock based custom ROM and flash it via the faulty one. If your phone boots up fine, boot into Download Mode and downgrade recovery or use any other recovery recommended for the ROM you're using. If you encounter issues or weird behavior with your phone go with step 1.
3. Via flashing a fixed TWRP 2.8.7.0 - please note: You might as well lose data
In this option you can flash a fixed version of TWRP which an user of XDA has provided. Many thanks to StdBarbarossa for his work. Unfortunately in his build you cannot mound your SD card via PC as it's not working at the moment. Make sure you have all the needed files already on your SD card. For some users this way was working for them. Boot your phone into recovery, click on install, change from .zip to .image, choose the Alpha17.img, install it by swiping and reboot your phone into recovery. Perform a wipe (preferably a factory reset, cache and dalvik cache might be working too) and see if your phone boots up fine. Here the same: if you're still facing issues go with step 1.
Link for the TWRP Alpha17 2.8.7.0 https://drive.google.com/file/d/0B-tlso-zNf9NMWlMMFpiYmYwTzA/view
I have gone through the same issue. In my case I only managed to get my phone working again with step one as I had flashed a custom ROM via the buggy recovery and ended up in a bootloop. As stated, others have managed to fix their phone with either option 2 or 3.
Link for the fixed TWRP is provided in the spoiler.
If you're not sure about something ask here first before you might brick your phone. If you know any other way to fix this issue feel free to post it here.