Phone Details...
CleanRom 1.3
Faux Kernel
Tried a different ROM today instead of CleanRom and didn't care for it. Restored back to CleanRom with TWRP 2.5.0.2. Ran fine until I did a reboot. Stuck on S4 splash screen. I can get into recovery and wipe everything and reflash a fresh copy and it'll boot fine until I do a restart, then stuck again. Tried twice.
I'm assuming I revert back to stock via this method http://forum.xda-developers.com/showthread.php?t=2301259 then reroot and reflash to ROM of choice. Sound like I'm on the right track?
Uggh. Still does it after all that. Just hangs on the splash screen after booting up initially then rebooting.
I am having the same problem anyone have a thought?
Try OUDhs recovery here: http://forum.xda-developers.com/showthread.php?t=2291976 See if that helps
Jonezy2166 said:
I am having the same problem anyone have a thought?
Click to expand...
Click to collapse
Solved. Had to fix permissions in TWRP. I guess when you format data you have to fix permissions.
rustynutzz said:
Solved. Had to fix permissions in TWRP. I guess when you format data you have to fix permissions.
Click to expand...
Click to collapse
I didn't even think of that... Rookie mistake by me haha
Thanks!
rustynutzz said:
Solved. Had to fix permissions in TWRP. I guess when you format data you have to fix permissions.
Click to expand...
Click to collapse
Very much appreciate fix. I have been fighting this (even soft bricked, restored and rerooted) for the last day... several hours of attempting. Thanks again.
rustynutzz said:
Solved. Had to fix permissions in TWRP. I guess when you format data you have to fix permissions.
Click to expand...
Click to collapse
Hi,
How did you change the permission?
I used TWRP to wiped. Then it didn't boot with cyanogemod, so I used ODIN updated the ROM.
Now it hangs at the spalash screen.
I saw this link but it talks about ROOM manager and I don't know what it is.
http://forum.xda-developers.com/showthread.php?t=2291976
Please help
Thanks
Thank you for your post
I just upgraded to Galaxy S4 from Epic 4G Touch yesterday. I have flashed different ROMs and tried various versions of CWM and TWRP on my old phone for the last two years so I am not exactly a rookie on this subject. So imagine my shock when I found my new Galaxy stuck on the Samsung boot screen after I did a backup on TWRP. At the time I didn't know what was causing the problem. Was it the root, was it TWRP or CWM, was it the ROM? I finally had to use Odin to flash the original stock ROM after hours of trials and errors just to get the phone to work (and in case I want to return it to the store). Until I read the posts in this thread, I had narrowed down the source of the problem to the backup process on CWM. The phone always got stuck after the backup. I thought to myself if this was something I had to live with, I might just return the new phone and switch back to E4GT. Then I found this thread, downloaded and flashed the PhilZ Touch recovery. Did the "Fix Permissions" thing and the phone rebooted OK. I didn't do the backup this time as I have spent way too many hours on it this long weekend. I am going to try it later this week when I have more time just in case things go wrong again. At least this time I know how to reset the phone to the factory ROM. I just want to say thank you to all who have posted your solutions on this forum.
Reboot frozen
Jonezy2166 said:
I didn't even think of that... Rookie mistake by me haha
Thanks!
Click to expand...
Click to collapse
I have an MDK based verizon galaxy s4 with TWRP. I installed the Hyperdrive RLS10.2 rom and then rebooted, but it only shows the Samsung custom boot screen and never gets back to teamwin or the OS. It seems to loop every 5 seconds showing the boot screen. I don't see how to fix permissions if I can't get to the device. Can someone help?
wally44 said:
I have an MDK based verizon galaxy s4 with TWRP. I installed the Hyperdrive RLS10.2 rom and then rebooted, but it only shows the Samsung custom boot screen and never gets back to teamwin or the OS. It seems to loop every 5 seconds showing the boot screen. I don't see how to fix permissions if I can't get to the device. Can someone help?
Click to expand...
Click to collapse
If you can't boot into recovery either then you have to use ODIN.
Still fails to go to recovery
joshm.1219 said:
If you can't boot into recovery either then you have to use ODIN.
Click to expand...
Click to collapse
I used odin and flashed the MDK ROM, but the phone still won't go into recovery. I get the Samsung sign with custom showing, but it won't go past that point. It seems to keep trying every 5 seconds or so, but that is it.
---------- Post added at 04:22 PM ---------- Previous post was at 03:24 PM ----------
joshm.1219 said:
If you can't boot into recovery either then you have to use ODIN.
Click to expand...
Click to collapse
I tried to install TWRP with ODIN and get the following failure:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone it says
SECURE CHECK FAIL : recovery
wally44 said:
I used odin and flashed the MDK ROM, but the phone still won't go into recovery. I get the Samsung sign with custom showing, but it won't go past that point. It seems to keep trying every 5 seconds or so, but that is it.
---------- Post added at 04:22 PM ---------- Previous post was at 03:24 PM ----------
I tried to install TWRP with ODIN and get the following failure:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone it says
SECURE CHECK FAIL : recovery
Click to expand...
Click to collapse
That'll happen if you're not flashing a Loki'd recovery. The SECURE CHECK FAIL is the bootloader rejecting the unsigned recovery.
so how do you resolve this then?
k1mu said:
That'll happen if you're not flashing a Loki'd recovery. The SECURE CHECK FAIL is the bootloader rejecting the unsigned recovery.
Click to expand...
Click to collapse
Hi, I am having a similar problem with my verizon mdk unlocked phone that has twrp. I tried installing kitkat and now it won't boot into twrp but hang on the Teamwin screen. Trying to just turn on it will hang on the unlock symbol with Samsung. Is there a way I can flash recovery via ODIN? It's already rooted and like I said, had TWRP. Some how it appears the recovery is now broken. Thanks in advance!
Fix without having to ODIN back to stock.
rustynutzz said:
Phone Details...
CleanRom 1.3
Faux Kernel
Tried a different ROM today instead of CleanRom and didn't care for it. Restored back to CleanRom with TWRP 2.5.0.2. Ran fine until I did a reboot. Stuck on S4 splash screen. I can get into recovery and wipe everything and reflash a fresh copy and it'll boot fine until I do a restart, then stuck again. Tried twice.
I'm assuming I revert back to stock via this method http://forum.xda-developers.com/showthread.php?t=2301259 then reroot and reflash to ROM of choice. Sound like I'm on the right track?
Click to expand...
Click to collapse
I also had this happen to me recently running the same version of TWRP. I had some corrupt files on my internal storage so I formatted it to get rid of them, fixed permissions, and loaded hyperdrive 13. Everything booted up fine until I rebooted and then I was stuck on the splash screen. So I went through the steps of booting back into recovery (which my phone would boot into recovery no problem so I knew I did not lose root), factory reset, wipe cache and davlic, and reflash the rom but it still would not boot. I even tried to restore from a back up and it kept getting a failed message. I could only get the phone to boot when I reformatted and reinstalled the rom. But yet again after I rebooted it would get stuck at the splash screen. There is a fix that I found and you do not have to ODIN back and start fresh. Reformat your phone and load the rom to get it to boot. Download goo manager from the playstore. Open goo manager and go to "browse all files". Then go to "devs". Scroll down until you find "philz_touch" and open it. Open "CWM_Advanced_Edition" and find your device. Download the latest recovery zip and install it through goo manager. Your phone should automatically reboot into recovery and install it. Make sure you when your phone reboots you reboot back into recovery and you should now have Philz touch CWM recovery installed. Now reformat your phone to fix whatever files TWRP corrupted and load your rom. Now your phone will be good to go and no more issues being stuck on the splash screen upon reboot. You can also reflash TWRP for your recovery but make sure to only do a factory reset and not reformat because you will be stuck back at square 1. Hope this helps everyone because I could not find any other fix to this other than ODIN back to stock which is hard for me because I do not have a windows computer.
uknowme4me said:
I also had this happen to me recently running the same version of TWRP. I had some corrupt files on my internal storage so I formatted it to get rid of them, fixed permissions, and loaded hyperdrive 13. Everything booted up fine until I rebooted and then I was stuck on the splash screen. So I went through the steps of booting back into recovery (which my phone would boot into recovery no problem so I knew I did not lose root), factory reset, wipe cache and davlic, and reflash the rom but it still would not boot. I even tried to restore from a back up and it kept getting a failed message. I could only get the phone to boot when I reformatted and reinstalled the rom. But yet again after I rebooted it would get stuck at the splash screen. There is a fix that I found and you do not have to ODIN back and start fresh. Reformat your phone and load the rom to get it to boot. Download goo manager from the playstore. Open goo manager and go to "browse all files". Then go to "devs". Scroll down until you find "philz_touch" and open it. Open "CWM_Advanced_Edition" and find your device. Download the latest recovery zip and install it through goo manager. Your phone should automatically reboot into recovery and install it. Make sure you when your phone reboots you reboot back into recovery and you should now have Philz touch CWM recovery installed. Now reformat your phone to fix whatever files TWRP corrupted and load your rom. Now your phone will be good to go and no more issues being stuck on the splash screen upon reboot. You can also reflash TWRP for your recovery but make sure to only do a factory reset and not reformat because you will be stuck back at square 1. Hope this helps everyone because I could not find any other fix to this other than ODIN back to stock which is hard for me because I do not have a windows computer.
Click to expand...
Click to collapse
Thank you for this! I had several hours of frustration earlier with this exact problem and your solution worked for me.
urklegrue said:
Thank you for this! I had several hours of frustration earlier with this exact problem and your solution worked for me.
Click to expand...
Click to collapse
Glad I could help! I was stuck for 2 days trying to figure it out lol.
Sent from my SCH-I545 using Tapatalk
Related
Hi guys,
So I tried to root my phone today - I dont know what happened or what I did wrong, but my phone now is locked constantly into a boot cycle. It'll turn on, boot into the lockscreen for maybe 20 seconds, then reboot itself. Nothing i do seems to help. I tried flashing back to the stock rom, flashing back to stock rom + root, but to no avail. Ive been desperately trying to find a solution that will at least allow me to get to the data on the phone (i have some pictures that i haven't backed up that are absolutely essential) and then i have no problem doing a complete data wipe or whatever is necessary.
Someone PLEASE help! phone is completely unusable at this point!
Yes, I can enter download mode
re: Boot Looping
victor3063 said:
Hi guys,
So I tried to root my phone today - I dont know what happened or what I did wrong, but my phone now is locked constantly into a boot cycle. It'll turn on, boot into the lockscreen for maybe 20 seconds, then reboot itself. Nothing i do seems to help. I tried flashing back to the stock rom, flashing back to stock rom + root, but to no avail. Ive been desperately trying to find a solution that will at least allow me to get to the data on the phone (i have some pictures that i haven't backed up that are absolutely essential) and then i have no problem doing a complete data wipe or whatever is necessary.
Someone PLEASE help! phone is completely unusable at this point!
Yes, I can enter download mode
Click to expand...
Click to collapse
When you flashed the STOCK rom was it a ZIP or a TAR file?
Before I can help I need to know.
Zipfiles require CWM Recovery for flashing and TAR files require ODIN for flashing.
I flashed the TAR file in ODIN 1.85, PDA.tar from the unzipped file UCKH7_stock_odin.7z
So I just tried it again, for something like the 4th or 5th time. I checked only "AUTO REBOOT" and "RESET TIME" in Odin, selected PDA as PDA.tar from UCKH7_stock_odin, got the following sequence from Odin
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> factoryfs.img
<ID:0/006> NAND Write Start!!
<ID:0/006> zImage
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!!
<ID:0/007> Added!!
<ID:0/007> Removed!!
<ID:0/007> Added!!
<ID:0/007> Removed!!
where I'm locked into the bootcycle again. It does boot up into my lock screen, I can interact with the screen for maybe 10 seconds, and then it just reboots. I've let it run for a little while to see if it can figure itself out, but after the third or fourth time i get nervous and pull the battery.
victor3063 said:
I flashed the TAR file in ODIN 1.85, PDA.tar from the unzipped file UCKH7_stock_odin.7z
Click to expand...
Click to collapse
ok, here is what to do.
Download this stock rooted rom: http://www.multiupload.com/PNQC9KOD4D
and download the MODEM file for the rom: http://www.multiupload.com/VWTSCXE5L0
After you extract both TAR files flash both of them at the same time by
putting the PDA tar file into the PDA slot in ODIN and the MODEM tar file
in the PHONE slot in ODIN then start flashing.
Don't check or uncheck any checkboxes in ODIN.
When its done flashing, it should boot into the STOCK ROOTED rom.
Before, or after doing the above boot into recovery and do a data wipe/factory reset
Sent from my SAMSUNG-SGH-I777 using XDA App
Didn't work. Still stuck in the same boot pattern. Redownloaded ODIN, redownloaded all the links again just to guard against any kind of corrupted files, but same end result, constant reboot cycle.
Samsung galaxy s2 --> at&t rethink possible --> preparing usb storage/lock screen --> reboot
You probably need to do a wipe data/factory reset.
Since you apparently have files that you want - enter CWM recovery and adb pull them.
re: try this
victor3063 said:
So I just tried it again, for something like the 4th or 5th time. I checked only "AUTO REBOOT" and "RESET TIME" in Odin, selected PDA as PDA.tar from UCKH7_stock_odin, got the following sequence from Odin
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> factoryfs.img
<ID:0/006> NAND Write Start!!
<ID:0/006> zImage
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/006> Removed!!
<ID:0/007> Added!!
<ID:0/007> Removed!!
<ID:0/007> Added!!
<ID:0/007> Removed!!
where I'm locked into the bootcycle again. It does boot up into my lock screen, I can interact with the screen for maybe 10 seconds, and then it just reboots. I've let it run for a little while to see if it can figure itself out, but after the third or fourth time i get nervous and pull the battery.
Click to expand...
Click to collapse
Try this first if you have not tryed it yet, it looks like odin flashed the PDA
file sucessfully, but did not flash the modem.
So put the modem into the PDA slot in ODIN and flash it.
If that don't work then do it vica versa and only flash the
PDA file in the PDA slot in ODIN.
This way you will know for sure which TAR file is not flashing.
(if you only have one TAR file to flash at a time with ODIN always put it in PDA slot)
If that don't work then try the method below.
Try this, turn off the phone or pull the battery, turn the phone back on or
replace the battery and go into CWM recovery and select
"Wipe Data/Factory Reset" Don't worry, it will NOT delete any pictures
or videos, or anything which you personcally have saved into a folder
you have created and it will not even touch the external sdcard if you have one.
It will however delete all the apps which you have installed in the phone prior
to having the problems you have now..
Is the data wipe / factory reset going to delete pictures off my phone? thats really my last resort.. I have a couple dozen pictures that I took on my phone since i purchased that I haven't had a chance to backup.
Does anybody have any ideas?
victor3063 said:
Is the data wipe / factory reset going to delete pictures off my phone? thats really my last resort.. I have a couple dozen pictures that I took on my phone since i purchased that I haven't had a chance to backup.
Does anybody have any ideas?
Click to expand...
Click to collapse
Its not going to delete any pictures, videos or even music you have
on the phone.
Anything which YOU have SAVED to the phone will not be touched
except usernames or passwords, credit card #'s might be deleted.
But actual files or folders you created will stay intact as well as
the external sdcard if you have one will not even be touched.
I think the reboot is occurring due to corrupted settings of network or files ystem. You can try this. pull out the battery, remove sim and sd card if you have any, then try booting..
Factory reset or data wipe should not theoretically wipe your pictures.. It basically wipes only /data partition. I have done factory reset which retained my pictures..
But to be on safer side, try the above step to see, if you can get the phone running..
Had same issue trying to factory restore with Odin. Wipe from e3 did the trick.
Sent from my SAMSUNG-SGH-I777 using XDA App
victor3063 said:
Is the data wipe / factory reset going to delete pictures off my phone? thats really my last resort.. I have a couple dozen pictures that I took on my phone since i purchased that I haven't had a chance to backup.
Does anybody have any ideas?
Click to expand...
Click to collapse
Those SHOULD be on /sdcard, but I can't guarantee it. Also, if you use 3e recovery, there's a chance that might hit /sdcard.
MJ, you should never guarantee something like that to someone.
Make sure you have ADB set up - I suggest Googling Droid Explorer if you're on Windows
Flash a CWM-enabled kernel
Enter CWM using the three-finger trick (this should work fine)
In CWM, go to Mounts and Storage and mount /sdcard and /data if they are not mounted
Connect to your phone using ADB and start looking for your files - I think Droid Explorer makes this MUCH easier by providing a nice graphical frontend to ADB push/pull
so this is what i'm doing right now.
Obviously my problem is constant rebooting.
1. Flash UCKH7 stock odin PDA.tar and UCKH7 modem via odin onto phone via odin
2. flash CWM recovery ClockworkMod Recovery 5.0.2.3 via odin as PDA
3. both these step pass OK, now Samsung Galaxy S2 I9100 bootscreen with yellow triangle shows up + at&t logo, however constant reboot problem is still present
4. pull battery unplug usb replugin battery and attempt to enter cwm recovery via holding down volume up+volume down+power button
5. CWM based recovery 5.0.2.3 flashes up for a brief second after bootscreen, then immediately reboots and reenters boot cycle
REALLY stuck here. i spent the whole day looking through the forum and i'm really not sure where i went wrong. the only thing that doesnt have the reboot cycle is download mode.
im basically trying to reach the step where i can enter cwm recovery and attempt to do a factory wipe, but it still reboots the enter i enter cwm recovery and enters the normal reboot cycle. i have NO IDEA how i couldve corrupted the file system this badly, perhaps the usb cable got bumped during the initial root? who knows. all i know is i cant even bring the phone to any form of usable status right now. any ideas?
re: boot looping
victor3063 said:
im basically trying to reach the step where i can enter cwm recovery and attempt to do a factory wipe, but it still reboots the enter i enter cwm recovery and enters the normal reboot cycle. i have NO IDEA how i couldve corrupted the file system this badly, perhaps the usb cable got bumped during the initial root? who knows. all i know is i cant even bring the phone to any form of usable status right now. any ideas?
Click to expand...
Click to collapse
You really do have a problem.......
I remember before getting this new SGS2 when I had the Samsung Infuse.
There was a thread in the Infuse forum called "The Ultimate Unbrick", I know
that there is a simular thread here for our SGS2 however the unbrick here is
lacking the PIT file.
I am 100% sure that if you could get a hold of something like the
Ultimate Unbrick which included the *.PIT file that it would solve the
problem you have.
The Ultimate Unbrick for the Samsung Infuse consisted of a
PDA*.TAR, PHONE*.TAR and the *.PIT file and it came with ODIN too.
The PIT file repartitions the sdcard to stock which fixes any partition
errors the phone may have due to flashing a non-compatible rom or
due to the flashing process being interupted while odin was flashing.
You might want to ask around the forum here if anyone has a stock
ODIN rom which includes PDA, MODEM and the PIT file for SGS2 i777.
I know for a fact that for the Infuse phone a complete stock package like
that always worked for fixing and solving problems like yours.
The only problem a package like this could not fix was if the phone
was hard-bricked meaning that it would not turn on at all no matter what.
Good luck with it..........
wow, the thought that i might be completely bricked is genuinely terrifying. really frustrating too, as i definitely consider myself fairly tech savvy.
Are you getting any indication that any of your capacitive buttons are acting like they are continually being pressed?
Did your phone at any time get wet?
The reason I ask is it almost seems like a hardware problem at this point. I would pull your battery and check the water indicators and see if there are any signs of moisture.
If there are no signs of moisture and you are pretty positive the phone is dry I would put the battery back in, don't turn it on, plug it into a wall charger and let it charge for a few hours. Then try to get into recovery again.
If after that you are still getting boot loop even in recovery we will link you to a .pit file and have you try a re flash to stock with a re partition.
Sent from my SAMSUNG-SGH-I777 using XDA App
thanks for the advice dayv.
I'm 100% sure theres been no water damage. I've barely had the phone for a week, and everything was working fine up until now. Other than that, I guess i'm going to have to go for the pit method - going to charge the phone overnight, see if it boots into cwm one last time, and then i'm going to use the following pit file from paulyhoffman
http://forum.xda-developers.com/showthread.php?t=1286218
so just to go over the procedure one last time - download mode on phone (only thing that seems to be working correctly so far)
flash PIT (I777UCKH7.pit), PDA (PDA.tar) and PHONE(UCKH7_modem.tar) at the same time, with REPARTITION, AUTO REBOOT, and RESET TIME checked in Odin?
Hi guys,
I've owned android phones since the G1, motocliq, nexus, sgs2 (intl), motodroid, all rooted, custom rom, etc etc... So when a friend asked me to unlock (for which i had to root) his i777 I thought I could handle it.
I followed the guide: http://forum.xda-developers.com/showthread.php?t=1286220
Went into download mode (could only do it with the VOL+-USB trick) and flashed CWM on Odin. Flashed fine, no problem, rebooted and only showed SAMSUNG letters on the bootup, nothing more. Tried going into CWM Recovery, no luck, Download mode, works fine. So I went over and re-flashed it, worked, but still can't get it to boot, or Recovery to work.
So then I started trying to flash other PDA's thinking i could do it, and maybe cwm was bugged, every time I try to flash ANYTHING that's not that specific CWM it says Write error, FAILED. When i reboot, the phone is softbricked (computer-phone logo saying connect recovery on kies). After this nothing at all will flash, except that CWM, which gives me download mode again... Which doesnt matter because the softbrick screen is a download mode in itself.
Im running out of options, im not sure where I should keep looking, Heimdall, installed, tried to flash, it transfers, at 99% says error writing and cancels. Tried flashing a new .pit and repartitioning, same story, wont let me.
Any suggestions would be more than welcomed :/
Sincerely,
Rodo
See if you can go back to out of box:
http://galaxys2root.com/att-galaxy-s2/how-to-unroot-att-galaxy-s2-sgh-i777/
Rodocopz said:
Hi guys,
I've owned android phones since the G1, motocliq, nexus, sgs2 (intl), motodroid, all rooted, custom rom, etc etc... So when a friend asked me to unlock (for which i had to root) his i777 I thought I could handle it.
I followed the guide: http://forum.xda-developers.com/showthread.php?t=1286220
Went into download mode (could only do it with the VOL+-USB trick) and flashed CWM on Odin. Flashed fine, no problem, rebooted and only showed SAMSUNG letters on the bootup, nothing more. Tried going into CWM Recovery, no luck, Download mode, works fine. So I went over and re-flashed it, worked, but still can't get it to boot, or Recovery to work.
So then I started trying to flash other PDA's thinking i could do it, and maybe cwm was bugged, every time I try to flash ANYTHING that's not that specific CWM it says Write error, FAILED. When i reboot, the phone is softbricked (computer-phone logo saying connect recovery on kies). After this nothing at all will flash, except that CWM, which gives me download mode again... Which doesnt matter because the softbrick screen is a download mode in itself.
Im running out of options, im not sure where I should keep looking, Heimdall, installed, tried to flash, it transfers, at 99% says error writing and cancels. Tried flashing a new .pit and repartitioning, same story, wont let me.
Any suggestions would be more than welcomed :/
Sincerely,
Rodo
Click to expand...
Click to collapse
Use my return-to-stock packages from dev forum.
Hi Entropy, I've tried but I can't seem to find an Odin flashable .tar, they're all CWM flashes and my CWM is screwed.
> http://forum.xda-developers.com/showthread.php?t=1289460
Oh and I tried flashing http://forum.xda-developers.com/showthread.php?t=1286432 with heimdall too. write error
Did you try this?
http://forum.xda-developers.com/showthread.php?t=1286432
This has the back to stock odin files, Thanks to Entropy!
This has UCKH7_stock_odin_noroot.7z which is flashable by odin. Try this.. You have to use 7zip to get the tar file..
Yup.. no luck :/
Error writing
Changed drivers, installed heimdall, used a different computer, no luck. (and works just fine with my other phones so I doubt its that.)
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> factoryfs.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Try installing Entropy's stock, or stock + root using one of these Odin3 One-Click Downloaders. That will take some of the variables out of the equation. If that doesn't go, you need to figure out if the problem in in the pc or the phone. Let us know your results.
I don't guess you need instructions, but if you do, they are in the flashing custom binaries guide linked in my sig.
Tried at least two previously, they report the same error. giant FAIL in red. I tried another computer previously, and this computer flashes my i9100 just fine (which i presume are the same drivers). In any case I installed the heimdall drivers for USB (on windows, which ruins Odin, but works fine after you uninstall those drivers) included in the package.
Still having no luck with this issue... Anyone know what could be causing that write error on download mode Odin? Perhaps I could flash a different recovery console?
Have you installed Samsung kies just to make sure you have proper drivers? Can make all the difference in the world.
Some people have a tough time getting the wrong drivers uninstalled. Easy check if that is the problem, go to a different pc that you haven't plugged your phone into and first install the right version of kies that you need.
Then plug your phone in and flash through Odin, transfer files over or redownload, hopefully all will be well.
Sent from my SAMSUNG-SGH-I777 using XDA App
Im still stuck with this issue and apparently after a few extra flashes it now shows:
Custom binary download: NO
Current Bunary: Samsung Official
Which isnt true, but w/e. It will still only flash SGH-1777 clockwork recovery and it will now not even show the samsung logo and become unresponsive as soon as you put the battery in. (the phone heats up, even if i dont try to turn it on, drains the battery dead in a couple hours)
So, I want to give it a try with heimdall and a full repartitioning, but I do not have the necessary files. Ive been looking and I cant find all the partition files, aka
PDA/Code:
FactoryFS=factoryfs.frs
Kernel(zImage)=zImage
Param.lfs=param.lfs
Primary Bootloader=boot.bin
Secondary Bootloader=slb.bin
CSC:
Cache=cache.rfs
Database Data=dbdata.rfs
In Other:
Modem=modem.bin
Recovery=recovery.bin
Could someone dump these files for me? Thanks!
A good day to all you fellow developers, trouble shooters and geeks from other corners
I wanted to create my account here some time now, but now it's been kind of necessary.
You see, i (lightly) bricked my phone... i like to call it "clayed".
I honestly thought i had done my research and everything went ok... until i used EZ-Unlock to unlock my bootloader.
I remember pressing the "unlock" button 3 times or so because the status above said "Unknown" while a small temporary message beneath said "Bootloader unlock: successful".
The next morning, when my phone shut down due to an empty battery (forgot to charge my phone, so no excessive drain or anything), i plugged it into the wall for battery charging.
Then it went directly in download mode, which i can't get past.
The screen ONLY consists of a plain android in front-view with underneath the text: Downloading... Do not turn off target!!"
So no extra text as within Odin mode.
However i CAN get into Odin mode and CWM recovery mode.
I think that the bootloader got corrupt in some way myself.
But what should i do?
Flash it with a new one? And what is the best way?
I don't have a recovery at hand... but i don't care if the whole storage needs to be wiped if needed.
====================================
INFO:
- Samsung Galaxy S GT-i9300
- Rooted
- Bootloader unlocked (Houston, we have...)
- Odin mode = possible
- CWM recovery mode = possible
====================================
Thanks for reading!
Greetings
Well for a start, the international doesn't have a locked bootloader.......and that unlock app is for gs3 Verizon, which I assume does have a locked bootloader, so either you don't have an international and are in the wrong section, or, as per most posts here, you have failed to read and understand what you are doing
Thanks for the quick response.
I apparently didn't catch the parts about not having a locked bootloader, and the fact that the app is for Verizon.
My phone is the international version.
So, i know it's my fault although i really thought i knew enough while not even being close.
There is so much to rooting (and around it).
Do you, or anyone else, perhaps know what is going on with my phone from this point... and what to do about it?
Well the best bet would be to flash a stock firmware with Odin and pray like hell, what country are you in, and have you used Odin before?
slaphead20 said:
Well the best bet would be to flash a stock firmware with Odin and pray like hell, what country are you in, and have you used Odin before?
Click to expand...
Click to collapse
Oof that doesn't sound too good.
I did use Odin (version 3.07) before to root my phone. I understand it's this desktop application which allows to flash/inject software to portable devices.
I am from the Netherlands, where i got my phone from T-Mobile.
With stock firmware, you mean like flashing my current state with the original TouchWiz ROM?
yes, then factory reset
Firstly I'd suggest downloading latest bootloader and patching it with odin even before patching anything else. You can't be sure that it's stable and won't cause any further issues after flashing.
JustArchi said:
Firstly I'd suggest downloading latest bootloader and patching it with odin even before patching anything else. You can't be sure that it's stable and won't cause any further issues after flashing.
Click to expand...
Click to collapse
Luckily i've got patience, so i waited a bit before taking action.
Patching the latest bootloader through odin first seems a good idea indeed.
But should i do only that and then try to reboot since everything else still is untouched...
or would it seem better to setup odin with the new bootloader AND the stock ROM all in 1 go?
I'd suggest starting with bootloader, then rebooting. Then on the second go flashing custom recovery and on the last step flashing rom but not through odin but through recovery.
You can find my guide on flashing custom recovery in my ArchiDroid topic if you wish.
JustArchi said:
I'd suggest starting with bootloader, then rebooting. Then on the second go flashing custom recovery and on the last step flashing rom but not through odin but through recovery.
You can find my guide on flashing custom recovery in my ArchiDroid topic if you wish.
Click to expand...
Click to collapse
Thanks so much for the help already!
I'm going to read your guide and then get to work.
I'll place the outcome here of how it went and if there were any unusual hickups along the way as feedback to potential other unfortunate tweakers like myself... although i hope other people won't be as clumsy as me.
And the last one. Flashing with odin is nearly the same but if you're flashing bootloader then download latest bootloader and place it as "Bootloader" in Odin.
JustArchi said:
And the last one. Flashing with odin is nearly the same but if you're flashing bootloader then download latest bootloader and place it as "Bootloader" in Odin.
Click to expand...
Click to collapse
Well, i've done what you specified.
And there's just a slight improvement on the bootup.
The difference with the previous experience is, that there is now a quick glimpse of the Samsung logo... but then immediately the plain download screen pops up.
I did flash a custom recovery though (Philz recovery).
I haven't tried flashing a custom ROM yet, but something tells me that that's not going to help since it's just the upper layer of everything.
Here is my Odin output:
==================
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> bootLoader_I9300XXEMC3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
If you've flashed bootloader and actually you CAN enter recovery (through combination vol-up+home+power) then everything is fine and don't worry. Just don't forget to clean your old system.
If however you're unable to do it then we'll try to repartition your phone using PIT file. But please firstly make sure that it's absolutely necessary.
JustArchi said:
If you've flashed bootloader and actually you CAN enter recovery (through combination vol-up+home+power) then everything is fine and don't worry. Just don't forget to clean your old system.
If however you're unable to do it then we'll try to repartition your phone using PIT file. But please firstly make sure that it's absolutely necessary.
Click to expand...
Click to collapse
Yes i am able to enter recovery through vol-up+home+power.
But alright, i should then go into recovery and do:
- Wipe cache partition
- Wipe Dalvic Cache (?)
- Wipe Data/Factory Reset
- Install Zip (being the custom ROM like CyanogenMod for instance)
Firstly make sure that you have working .zip on your internal/external sdcard as it will be required.
From the recovery move to "mounts and storage" tab and click on format /system /data /cache /preload and if you have .zip on external sdcard also /sdcard.
Now you can install rom and everything should be fine.
BTW I suggest to stick with Samsung Base first, as it's proven to be stable and working. But it's up to you.
Ok, i will use the format method like you said.
I have no external sdcard so there's nothing to be done there.
One thing that's bothering me is that i should flash a new rom (Samsung's stock TouchWiz which i'm going to download) right from the recovery.
But, from how i see it, there's no way around than doing it from odin since i can't just put something onto my phone's storage like you do with the folder app inside the system.
Yeah I totally forgot that you can't connect internal sdcard with pc while being in recovery.
So basicly yes, you should flash some original soft from Samsung through Odin and eventually later put anything on your internal sdcard.
BTW it's much easier if you could find any external sdcard actually. You don't have to flash through odin then.
I had the same problem here on my galaxy s 3...
And here is what i did:
1) go to sammobile.com and download the latest firmware fot your country.
2) download odin.
3) turn your phone on and connect to your pc.
4) remember to have kies instaled (just download it from samsung's website.).
5) extract the file you donloaded from sammobile.com.
6) open odin and select PDA.
7) navigate to where you extracted the fitmware and click start.
8) thats it you are done.
It should take 4/5 minutes to complete.....
Please hit Thanks
Sent from my GT-I9300 using xda premium
Mindu99 said:
I had the same problem here on my galaxy s 3...
And here is what i did:
1) go to sammobile.com and download the latest firmware fot your country.
2) download odin.
3) turn your phone on and connect to your pc.
4) remember to have kies instaled (just download it from samsung's website.).
5) extract the file you donloaded from sammobile.com.
6) open odin and select PDA.
7) navigate to where you extracted the fitmware and click start.
8) thats it you are done.
It should take 4/5 minutes to complete.....
Please hit Thanks
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Where do i need Kies for? I'm not using it.
Digitalstone said:
Where do i need Kies for? I'm not using it.
Click to expand...
Click to collapse
KIES is the best bet to install phone drivers.
Ensure it is stopped in the Windows Task Manager before starting ODIN! Else it's a one way ticket to la-la-land for your phone. Good luck, mate! :thumbup:
Sent from my GT-I9300 using xda app-developers app
Hello,
My Galaxy s2 is stuck in boot loop, I can see only the GS2 logo.
It went into this situation after holding down power button trying to turn it off.
Tried to remove battery and nothing changed.
Entered recovery mode and did wipe cache and then reboot.
It went past the initial logo, showed samsung animation and then it went back to samsung logo boot loop. It never went to samsung animation again.
From that point on it does not boot to recovery mode, it shows the android robot with the spinning cog for a while and then it goes back to the samsung logo boot loop.
The phone can go to download mode without problem. I have not tried to install a stock firmware through odin, since I would like to get a backup of the sms messages from the phone first. I already have backup of pics, contacts, etc so I dont care about anything else besides the sms.
The phone was running the latest spanish stock JB version
GT-I9100 Galaxy S II
PDA: I9100XWLSD
CSC: I9100FOPLS4
MODEM: I9100XXLS8
Added: 2013-02-03
The only modifications to stock were
. Root when it was running ICS
. CSC change from EUR to FOP (so that it auto upgraded to JB from ICS)
The phone retained root after the auto JB upgrade
Do you know if there a solution to this situation? I am still under warranty so I can take it back to samsung so I would like to avoid installing CWM recovery kernel that would make them immediately reject service due to warranty void.
thank you in advance!
Yes, you can keep trying to flash a stock firmware in Odin. Click the link in my signature if you're having troubles with the flash failing. Flash the JB version you were on before, that's got the most chance of working with out having to wipe.
Personally, I think you're going to have to get a working recovery and factory reset to be honest.
Sent from a galaxy far, far away
Hopper8 said:
Yes, you can keep trying to flash a stock firmware in Odin. Click the link in my signature if you're having troubles with the flash failing. Flash the JB version you were on before, that's got the most chance of working with out having to wipe.
Personally, I think you're going to have to get a working recovery and factory reset to be honest.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
thank you for answering, so if I install the same version through Odin, it will not wipe out the current phone contents by default?
Toliver said:
thank you for answering, so if I install the same version through Odin, it will not wipe out the current phone contents by default?
Click to expand...
Click to collapse
Correct. A 1-part firmware will not wipe by default. If you flash a 3-part firmware (JB leak, LSJ for instance) that WILL wipe by default.
If you flash something other than the firmware you were on directly before the bootloop, you've got pretty much no chance of getting out of the bootloop without a factory reset. If you flash the same firmware you were on before the bootloop, then there's a chance of getting it to boot up with all your data.
If that (flashing with the same stock ROM) doesn't work, then I'm afraid its down to a factory reset, sorry.
Hopper8 said:
Correct. A 1-part firmware will not wipe by default. If you flash a 3-part firmware (JB leak, LSJ for instance) that WILL wipe by default.
If you flash something other than the firmware you were on directly before the bootloop, you've got pretty much no chance of getting out of the bootloop without a factory reset. If you flash the same firmware you were on before the bootloop, then there's a chance of getting it to boot up with all your data.
If that (flashing with the same stock ROM) doesn't work, then I'm afraid its down to a factory reset, sorry.
Click to expand...
Click to collapse
Ok then, I will give it a try and see how it goes. Another solution that I was thinking about is to try to install CWM through odin (i'm not sure if it's possible though) then boot into CWM and get backup through it. Then if I apply a stock firmware through odin, this would remove CWM and install the stock recovery kernel back, correct?
Yes, that's possible. You can flash Philz kernel via Odin, it's stock kernel only with root CWM. Other than that its the same. You could do that procedure using his kernel. When you flash stock rom via Odin then yes, you'd get rid of the custom recovery.
Depending on what you want to do (warranty etc) read up about the flash counter and then triangle away.
Sent from a galaxy far, far away
regarding the 1-part firmware, I downloaded from sammobile the I9100XWLSD_I9100FOPLS4_FOP.zip.
The zip archive contains a tar.md5 file I9100XWLSD_I9100FOPLS4_I9100XXLS8_HOME.tar.md5 and a dll file SS_DL.dll.
So I should use only the tar.md5 in the PDA section of odin, right? should I keep this dll in the same folder as the tar.md5 in case odin needs it?
Also does it make any difference which odin version should I use?
thaks again
Well I suppose it can't hurt to put it in the same directory, but I don't know if it really does anything. Yes, flash it in the pda section.. Which version? Take your pick. I usually use 3.0.4 but have also used others. Click my signature if you want a zip file with a few versions.
Sent from a galaxy far, far away
I tried flashing the same rom as it was installed but nothing changed, after the first boot I see the robot with the cog, a thin progress bar filling below it and then it goes to boot loop. No luck getting into recovery, still the same symptom... Besides the sms backup I am thinking about how to recover it, should I try installing 4.0.3 that was the factory default? Any more ideas??
thanks again
The odin log seems clean though, no error or anything else
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSD_I9100FOPLS4_I9100XXLS8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> cache.img
<ID:0/007> NAND Write Start!!
<ID:0/007> factoryfs.img
<ID:0/007> hidden.img
<ID:0/007> modem.bin
<ID:0/007> boot.bin
<ID:0/007> param.lfs
<ID:0/007> Sbl.bin
<ID:0/007> zImage
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/007> Removed!!
And can you try a factory reset from the stock recovery? You're not on 4.0.4 so it'll be safe.
@gastonw, can you have a look here? I know that I've seen Odin passing but still no boot... I just can't remember how on earth it was fixed. It seems I didn't bookmark it either.
Sent from a galaxy far, far away
Hopper8 said:
And can you try a factory reset from the stock recovery? You're not on 4.0.4 so it'll be safe.
@gastonw, can you have a look here? I know that I've seen Odin passing but still no boot... I just can't remember how on earth it was fixed. It seems I didn't bookmark it either.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
Could you provide more details on how to do a factory reset from stock recovery? Do you mean to flash 4.0.3 via odin? Or is it some options in odin that would enforce factory reset?
More details are to search for it mate. It's covered so many times that it's just plain spoonfeeding if I'm to post it.
Sent from a galaxy far, far away
Eventually I made it work by installing the 4.0.3 EUR via odin. I did not allow it to boot into the OS, as soon as it finished flashing via odin, I rebooted into recovery mode. This time it went in successfully. Then I used the CWM recovery kernel that just runs from the sd (it does not install) and got the full backup. Later on by using nandroid manager I recovered the sms messages + more (apps, etc). Thanks for all the help!
Hello, i've been broking my head with this cellphone ...
First than all i can acces Download Mode (Volume up - Volume down - Power buttom) but i can't not acces Recovery Mode as i try the key combination (Volume Up - Menu buttom - Power buttom) it gets stuck on Samsung Galaxy Ace GT S583M logo and never even reach Samsumg boot logo.
I tried flashing usign several odins and firmwares from M and I.. On sammobile. also with different versions of odin it keeps getting stuck on bootscreen. But sometimes when i flash with some roms it pass the Boot Screen logo and gets to a screen that i think is recovery.. it says something like
Looking for Updates
Appliing Update Package
Succeed
Appliing Multi CSC
Suceed
Reboot
and after that it keeps getting on bootscreen.
Can anyone help?
Buckstrat said:
Hello, i've been broking my head with this cellphone ...
First than all i can acces Download Mode (Volume up - Volume down - Power buttom) but i can't not acces Recovery Mode as i try the key combination (Volume Up - Menu buttom - Power buttom) it gets stuck on Samsung Galaxy Ace GT S583M logo and never even reach Samsumg boot logo.
I tried flashing usign several odins and firmwares from M and I.. On sammobile. also with different versions of odin it keeps getting stuck on bootscreen. But sometimes when i flash with some roms it pass the Boot Screen logo and gets to a screen that i think is recovery.. it says something like
Looking for Updates
Appliing Update Package
Succeed
Appliing Multi CSC
Suceed
Reboot
and after that it keeps getting on bootscreen.
Can anyone help?
Click to expand...
Click to collapse
Once you flash the stock rom back using odin, try doing Wipe data/ factory reset and Wipe cache partitions from Recovery Mode. Do post the result. Hope I Helped
mahithm said:
Once you flash the stock rom back using odin, try doing Wipe data/ factory reset and Wipe cache partitions from Recovery Mode. Do post the result. Hope I Helped
Click to expand...
Click to collapse
I can't access recovery even after flashing :C just tried it.
Buckstrat said:
I can't access recovery even after flashing :C just tried it.
Click to expand...
Click to collapse
Are you getting bootloops or is it stuck at the bootscreen?
mahithm said:
Are you getting bootloops or is it stuck at the bootscreen?
Click to expand...
Click to collapse
Stuck at bootscren as appointed in first thread.. sometimes it goes after bootscreen to recovery (after flashing) and show the things listed in first post.
Buckstrat said:
Stuck at bootscren as appointed in first thread.. sometimes it goes after bootscreen to recovery (after flashing) and show the things listed in first post.
Click to expand...
Click to collapse
Use the following guide to flash the stock rom back. You can find all the necessary files here,
[Guide] Know your Device:Galaxy Ace GT-S5830i ~Root~Odin~CWM~ROM LIST
Do post the result. Hope I Helped
mahithm said:
Use the following guide to flash the stock rom back. You can find all the necessary files here,
[Guide] Know your Device:Galaxy Ace GT-S5830i ~Root~Odin~CWM~ROM LIST
Do post the result. Hope I Helped
Click to expand...
Click to collapse
Just re-downlaoded everything flashed (Always succesfull on Odin) and still stuck and boot screen.
Buckstrat said:
Just re-downlaoded everything flashed (Always succesfull on Odin) and still stuck and boot screen.
Click to expand...
Click to collapse
Try using the following guide. This should work. Here is the link,
Unbrick/Firmware restore | Flash GUIDE
Do post the result. Hope I Helped
mahithm said:
Try using the following guide. This should work. Here is the link,
Unbrick/Firmware restore | Flash GUIDE
Do post the result. Hope I Helped
Click to expand...
Click to collapse
Already tried this one i think is first one i followed.. Still nothing :C
Logg from Odin:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_S5830M_WHLA1.tar.md5 is valid.
<OSM> MODEM_S5830M_WHLA1.tar.md5 is valid.
<OSM> CSC_S5830M_UUBLA1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> BcmBoot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> HEDGE_NVRAM8_RF_LE.bin
<ID:0/003> sysparm_dep.img
<ID:0/003> boot.img
<ID:0/003> param.lfs
<ID:0/003> system.img
<ID:0/003> sbl.bin
<ID:0/003> userdata.img
<ID:0/003> BcmCP.img
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response form LOKE
<ID:0/003> csc.rfs
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
EDIT:
Managed to get into recovery mode 2 times, one of them wipe cache data/partition/factory reset.. Reboot and still stuck and boot screen, the second time did the wipes and flashed the same rom right after.. Still stuck at bootscreen can't manage to get into recovery again.
Buckstrat said:
Already tried this one i think is first one i followed.. Still nothing :C
EDIT:
Managed to get into recovery mode 2 times, one of them wipe cache data/partition/factory reset.. Reboot and still stuck and boot screen, the second time did the wipes and flashed the same rom right after.. Still stuck at bootscreen can't manage to get into recovery again.
Click to expand...
Click to collapse
Try the instructions from here. Do post the result. Hope I Helped
I think I have encountered this issue before . I just flash everything i can flash in it. Nothing worked. But some guys recommended me this firmware. I think it's like 'Open Australia'. I think it's ATO_Repacked. And I flashed it. And It Worked like magic .
Sent from my GT-S5830i using XDA Free mobile app
mahithm said:
Try the instructions from here. Do post the result. Hope I Helped
Click to expand...
Click to collapse
Done, i'm not making mistakes in flashing :C
eiPeiDweP said:
I think I have encountered this issue before . I just flash everything i can flash in it. Nothing worked. But some guys recommended me this firmware. I think it's like 'Open Australia'. I think it's ATO_Repacked. And I flashed it. And It Worked like magic .
Sent from my GT-S5830i using XDA Free mobile app
Click to expand...
Click to collapse
Just tried this one nothing :crying:
Update:
I've got into recovery, rooted and flashes cwm. Did the wiped and flashed again, stil nothing also flashed a rom from CWM and still nothing... Come on guys this cellphone is from my gf and i'm a poor virgin guy who wants to have sex.
Buckstrat said:
Done, i'm not making mistakes in flashing :C
Click to expand...
Click to collapse
The link was mainly intended to provide you the split stock firmware. Please download all the necessary files from the "Required Things" section of the above link and perform flashing again. Hopefully it works this time
mahithm said:
The link was mainly intended to provide you the split stock firmware. Please download all the necessary files from the "Required Things" section of the above link and perform flashing again. Hopefully it works this time
Click to expand...
Click to collapse
Still nothing bro :crying:.. I just noticed i got over 3gb on different firmwares for the S5830 :cyclops::cyclops:
Bump
Update
Buckstrat said:
Bump
Click to expand...
Click to collapse
Buckstrat said:
Update
Click to expand...
Click to collapse
As much as I want to help you, I'm out of idea's But I'm sure the following people will be able to help you @Hitesh2626 and @amolgosavi (sorry for tagging you two but this guy needs your help).
Buckstrat said:
Hello, i've been broking my head with this cellphone ...
First than all i can acces Download Mode (Volume up - Volume down - Power buttom) but i can't not acces Recovery Mode as i try the key combination (Volume Up - Menu buttom - Power buttom) it gets stuck on Samsung Galaxy Ace GT S583M logo and never even reach Samsumg boot logo.
I tried flashing usign several odins and firmwares from M and I.. On sammobile. also with different versions of odin it keeps getting stuck on bootscreen. But sometimes when i flash with some roms it pass the Boot Screen logo and gets to a screen that i think is recovery.. it says something like
Looking for Updates
Appliing Update Package
Succeed
Appliing Multi CSC
Suceed
Reboot
and after that it keeps getting on bootscreen.
Can anyone help?
Click to expand...
Click to collapse
Just download one new firmware of your model only
And while spliting it do make wipe packages dont make non-wipe package and just flash them and see the result , i hope these will work because it erase all data /partitions of the Phone.
Hitesh2626 said:
Just download one new firmware of your model only
And while spliting it do make wipe packages dont make non-wipe package and just flash them and see the result , i hope these will work because it erase all data /partitions of the Phone.
Click to expand...
Click to collapse
I've tried a lot of different firmwares who seems to work in another cellphones.. on intener (havn't tried on my another ace 'cause i'm afraid of bricking it too) but i will split the firmware my self this time.
I'll post the results.
Buckstrat said:
I've tried a lot of different firmwares who seems to work in another cellphones.. on intener (havn't tried on my another ace 'cause i'm afraid of bricking it too) but i will split the firmware my self this time.
I'll post the results.
Click to expand...
Click to collapse
Don't flash Ace's firmware it will hard brick then you can't restore it by your self you need to give it to Service Center,
And do split by your self and make a wipe package and flash it follow these video