Hi gals and guys, I bought a new galaxy ace s5830D (gingerbread) from Telus and decided to unlock it the following way:
1. root using Universal_GB_ROOT_v10.zip
2. installed SuperOneClickv2.1.1-ShortFuse.zip on PC
3. installed Root Explorer (File Manager) v2.19.apk
4. used ADB shell on PC to read ST5L for unlock code
here is where the problem begins:
-- upon reboot phone goes in a bootloop (screen lights for a sec without Samsung logo)
-- I CANNOT put phone in recovery via home + power
--I CAN put phone in 'download' via power + home + vol dwn; or to RamDump with vol Up; or to Emergency Dload Mode by holding both up and dwn
I have tried the following:
-- flash stock telus rom S5830DTLKI4_S5830DTLSKI4_S5830DTLKI4_HOME.tar using ODIN. The flash goes successful but upon reboot goes back to bootloop? And still cannot enter 'recovery'
-- tried to flash cwm-recovery-ace.tar.md5 using ODIN. The flash is successful but on reboot goes to bootloop. Still no acess to 'recovery'
-- tried QtADB but cannot connect to phone
-- tried OneClickUnbrick but it will not recognize connection to phone either
-- tried AndroidSDK however cannot get to recognize device
So any ideas considering the main thing is I cannot get to 'recovery' and flashing with ODIN still results in bootloop.
Thanks for any advice
tedxdadevelopers said:
Hi gals and guys, I bought a new galaxy ace s5830D (gingerbread) from Telus and decided to unlock it the following way:
1. root using Universal_GB_ROOT_v10.zip
2. installed SuperOneClickv2.1.1-ShortFuse.zip on PC
3. installed Root Explorer (File Manager) v2.19.apk
4. used ADB shell on PC to read ST5L for unlock code
here is where the problem begins:
-- upon reboot phone goes in a bootloop (screen lights for a sec without Samsung logo)
-- I CANNOT put phone in recovery via home + power
--I CAN put phone in 'download' via power + home + vol dwn; or to RamDump with vol Up; or to Emergency Dload Mode by holding both up and dwn
I have tried the following:
-- flash stock telus rom S5830DTLKI4_S5830DTLSKI4_S5830DTLKI4_HOME.tar using ODIN. The flash goes successful but upon reboot goes back to bootloop? And still cannot enter 'recovery'
-- tried to flash cwm-recovery-ace.tar.md5 using ODIN. The flash is successful but on reboot goes to bootloop. Still no acess to 'recovery'
-- tried QtADB but cannot connect to phone
-- tried OneClickUnbrick but it will not recognize connection to phone either
-- tried AndroidSDK however cannot get to recognize device
So any ideas considering the main thing is I cannot get to 'recovery' and flashing with ODIN still results in bootloop.
Thanks for any advice
Click to expand...
Click to collapse
What ROM are you trying to flash with ODIN, because I couldn't find any on SamFirmware. Also in order to use ADB, you need the drivers, make sure you have them installed (they automatically install when you install Kies).
tedxdadevelopers said:
Hi gals and guys, I bought a new galaxy ace s5830D (gingerbread) from Telus and decided to unlock it the following way:
1. root using Universal_GB_ROOT_v10.zip
2. installed SuperOneClickv2.1.1-ShortFuse.zip on PC
3. installed Root Explorer (File Manager) v2.19.apk
4. used ADB shell on PC to read ST5L for unlock code
here is where the problem begins:
Click to expand...
Click to collapse
The stl5 method might damage the efs partition. It's a coinflip, with 3 outcomes:
-all goes well and you get an unlocked ace.
-your imei becomes 00000000000000 in which case you get aa working ace, but many carriers deny service to that imei, so no calls, no sms, no movile data.
-completely f****d up efs partition. You loose your imei. That's it, you're toast. No amount of flashing fixes this, it's not a hardbrick, but no rom will boot appropriately.
Try and flash a full package with odin. Make sure you use the correct odin version for your model and have the correct firmware. Then go into recovery and wipe everything, see if it boots. If it boots, open up your call app and dial *#06#* to see your imei (to make sure its still there).
If you have successfully flashed with odin before, and still won't boot or go into recovery, then maybe your efs partition got messed up.
Return the phone to telus, just don't tell them what you did.
thanks for the suggestions.. few more questions
-- any suggestions as to what to tell telus that is believable that happened? (phone is 3 days old and i bought it outright)
-- also re Efs partition damage, is there any way to repartition the phone and rewrite imei (isn't it on the stickers behind the battery)?
with ODIN i flashed (several times - all successfully) the stock rom made for the TELUS D version on the Ace. Its someone that build it from a stock Ace. Its available if u google it and many ppl have returned their Telus phones to stock telus\koodoo status via that rom with proprtietary carrier startup screen and all. The Model D of the Ace is not at all available on the SamFirmware site.
I also flashed only the CWM Recovery - sucessfully and still no access to 'recovery' menu.
ODIN i am using is the right version according to all i have read (4.42); and the .ops file is made, as I understand it, for partitions of the D version of the Ace. (odin + ops + rom was all one package that many ppl from telus have said to have used sucesfully to return their phones to stock.)
-- should i try to flash with odin a cyannogen mode 7.2.0; could that make a difference vs stock rom, or does the cyannogen just go on top of the stock rom; ie will not function without a proper stock rom? (i guess what i am asking is cyannogen a complete self contained os?)
--If the efs partition is damaged does it make sense then, that the ADB, oneclick unblock etc.., will not recognize the phone? Am i supposed to be able to even connect to ADB when phone is in 'download mode'? or its made to work only when phone is already booted up?
thanks guys again.. T
tedxdadevelopers said:
thanks for the suggestions.. few more questions
-- any suggestions as to what to tell telus that is believable that happened? (phone is 3 days old and i bought it outright)
-- also re Efs partition damage, is there any way to repartition the phone and rewrite imei (isn't it on the stickers behind the battery)?
with ODIN i flashed (several times - all successfully) the stock rom made for the TELUS D version on the Ace. Its someone that build it from a stock Ace. Its available if u google it and many ppl have returned their Telus phones to stock telus\koodoo status via that rom with proprtietary carrier startup screen and all. The Model D of the Ace is not at all available on the SamFirmware site.
I also flashed only the CWM Recovery - sucessfully and still no access to 'recovery' menu.
ODIN i am using is the right version according to all i have read (4.42); and the .ops file is made, as I understand it, for partitions of the D version of the Ace. (odin + ops + rom was all one package that many ppl from telus have said to have used sucesfully to return their phones to stock.)
-- should i try to flash with odin a cyannogen mode 7.2.0; could that make a difference vs stock rom, or does the cyannogen just go on top of the stock rom; ie will not function without a proper stock rom? (i guess what i am asking is cyannogen a complete self contained os?)
--If the efs partition is damaged does it make sense then, that the ADB, oneclick unblock etc.., will not recognize the phone? Am i supposed to be able to even connect to ADB when phone is in 'download mode'? or its made to work only when phone is already booted up?
thanks guys again.. T
Click to expand...
Click to collapse
Hey again, changing IMEI is illegal in some countries:
Here is a link on how to change it though.
when I go to repair my phone, they normally don't ask why does this happen, they just ask what's the problem. ALso, you have to pretend you are really angry, because the phone broke just 3 days after buying it. That's all. Just be sure that the boot animation is from the stock ROM, as well as the currently installed ROM.
Good deal, had phone exchanged for a new one. That should serve as a lesson to those trying to screw with their efs/ that sometimes it may actually NOT work!!
Thanks guys Cheers!
Related
Hello,
I verified that I am able to enter download mode by plugging in the USB cable while pressing both volume buttons with the device turned off. I also verified that I can enter recovery mode by pressing both volume buttons and the power button. So I am pretty sure that I know how to enter the modes.
I then ran the Odin version from http://forum.xda-developers.com/showthread.php?t=731989 (by mistake, I didn't know it differed from the one in http://touristinparadise.blogspot.com/2010/11/samsung-galaxy-s-how-to-install.html). I assume that simply overrode everything with the stock ROM instead because I did not get the chance to select the SpeedMod kernel.
However, after that the hotkey method was no longer working. I was only able to enter download and recovery mode using adb. I used this to flash SpeedMod using the correct Odin version from the SpeedMod page.
Then I proceeded by going into recovery mode and extracting captivate-efsbackup.zip. I went into download mode (again with adb, keys still didn't work) and flashed cm7-captivate-initial-kernel.tar.
Now, however, I'm in real trouble. I can enter neither recovery nor download mode. No matter if I use hotkeys or adb, the system reboots, but then just shows the "Galaxy S\n cyanogen^(mod)" image.
Anyone able to help? Why aren't the hotkeys working anymore after running Odin?
I have no explanationas to why buy do have a suggestion. Try the AIO tool box. If the phone boots, just enable usb debugging and follow instructions. You should probably use the 3 button fix option.
I recently had done a clean up of my cappy because after tons of flashes it had become a mess. After flashing back to stock I lost dl mode and recovery. Whipped out the AIO...ver.2.5 , booted phone, put in debug.. Reformated with 3 button and boom!, back in business. Be sure your net framework is current 4 version, install the C++ lib as siggested.
Took a likely pain in the ass and turned it into an inconvenience. Just follow the instructions...
Sent from a Captivate on Bluedipity 6.2, SP#59, JQ1 with Xda App
First of all, what model of Captivate do you have (the model number is underneath your battery, on the phone itself. It will be a number between 1006-1014).
And I hope you do realise that CM7 is a particularly difficult (than standard) ROM to flash, and if you don't know what you're doing (or miss a step), you can perma-brick your phone easily.
If you can't get into Download Mode by any means, then the only last suggestion I can give you is to try a USB Jig (search around in the Captivate Forum here, you'll see what I mean).
Thanks for the suggestions. Here is how I recovered:
Download SpeedMod Kernel
Create a nandroid backup on a working phone, copy that over to the broken one
Copy zImage from SpeedMod kernel to SD on broken phone with adb
Enter shell mode on phone
Look into misc/recovery.fstab to figure out the name of the sdcard block device
Mount sdcard with `mount [blockdev] /sdcard`
Flash zImage with `flash_image boot /sdcard/zImage`
Flash nandroid backups with `flash_image {system,cache,datadata} /sdcard/{system,cache,datadata}.img` (but not data)
Leave the phone without battery for at least 1 and at most 6 hours (my phone appeared completely dead after this operation, not even adb shell access, so I went to bed frustrated)
Now you can boot into download mode again using "adb reboot download" (which didn't work when running the CM7 kernel)
Use One Click Odin to revert to stock firmware
Install 3ButtonFix to get combos working again
Note that the original problem that caused all the trouble was that flashing the stock ROM with Odin One-Click disables the 3 Button combos. You have to use the 3ButtonFix to get it working again.
Nikratio please help me i was updating samsung galaxy 5 2.1 eclair to 2.2 froyo but when i was using odin then it stops working and i unplug the device the after that phone is not getting switched on and even not getting is recovery mode ... m very sad and even dnt have the backup of any phone and none of my frnd have android phones so that i have backup please help me bro m afraid of my mom too coz i just bought it few time back please hem me bro
Hey All,
So I'm in the process of helping a friend with his Galaxy Ace from Koodo. As it turns out the phone looks like it's semi-bricked but we may be mistaken all together so here goes:
My buddy tried using SuperOneClick to root his device however half way through the process, it froze and when he restarted his device, it hangs at the Samsung logo during the startup boot sequence.
1. When using a combination of UP Arrow + Home button + Power, he receives a message stating:
"RAMDUMP Mode
(ARM9 mode)"
In this mode he cannot do very much however his PC does recognize the device. Odin does not work in this mode.
2. When using a combination of DOWN arrow + Home button + Power, he received 2 different screens. The first is a bright pink colored screen that states:
"Warning!
A custom OS can cause critical problem in phone and installed applications. If you want to download a custom OS, press Volume UP key. Otherwise, press Volume DOWN key to cancel."
Pressing the down arrow brings him back to the frozen Samsung logo on startup however when pressing the UP arrow, the phone goes into "Downloading..." mode. In this mode, Odin DOES work.
-----------------------------------------------------------------------------
Now for the troubleshooting we've done. We managed to find a few articles online that asked us to use the Odin tool. We downloaded a few different sets of the files needs (Cooper.ops, CODE, MODEM, CSC & BOOT). Odin then detects the phone in 'Downloading..." mode and proceeds to installing the rom. It completes successfully however it does not reboot. The screen simply flashes with the Samsung logo again.
The original firmware build before the device stopped working ended with TLKI4.
-----------------------------------------------------------------------------
1. Can anyone suggest anything else we can try?
2. Do you know if the bootloader needs to be flashed first and if so, how?
Note: We can not take the device back to Koodo as it was purchased on Kijiji and no receipt was provided. It's the GT-S5830D.
Thanks in advance,
1- boot into recovery and try to wipe data and cache. u can enter recovery mode by pressing home+power.
2- it doesnt matter, u already flashed new bootloader by flashing the phone via odin.
btw does the "D" in "GT-S5830D" bring any different in hardware with international regular GT-S5830 that most of us here use?
if its different by somehow, u shouldnt flash generic international GT-S5830 rom into it. i know for sure that galaxy ace korean version cannot use generic rom from international galaxy ace.
yep there are some 5830D specific roms on sammobile.. try them instead of generic ace
madman_amit said:
yep there are some 5830D specific roms on sammobile.. try them instead of generic ace
Click to expand...
Click to collapse
Can you point me to a certain rom/boot loader to download from sammobile? I was there earlier this morning however I didn't see any mention of Canada anywhere and I left before I messed things up further.
Even if you could just tell me which one it is I have to download, I'll do the rest myself.
Thanks a bunch!
an0nym0us_ said:
1- boot into recovery and try to wipe data and cache. u can enter recovery mode by pressing home+power.
2- it doesnt matter, u already flashed new bootloader by flashing the phone via odin.
btw does the "D" in "GT-S5830D" bring any different in hardware with international regular GT-S5830 that most of us here use?
if its different by somehow, u shouldnt flash generic international GT-S5830 rom into it. i know for sure that galaxy ace korean version cannot use generic rom from international galaxy ace.
Click to expand...
Click to collapse
There is no option to wipe the device. In fact, I have had other Galaxy S models and I'm pretty familiar with the screen however the Ace does not load into that recovery. Either it goes to "Downloading.." or "RAMDUMP (Arm9 mode)".
Thanks
well seems like sammobile haven't got for 5830L
but not to worry alternative site has one specifically rare rom of "D"
download it from this link
http://hotfile.com/dl/137128537/a629597/GT-S5830D_TLS_S5830DTLKI4_S5830DTLSKI4_S5830DTLKI4.rar.html
which you originally were using.. no other things for D
password : sampro.pl
Happy Flashing
---------- Post added at 12:10 AM ---------- Previous post was at 12:09 AM ----------
merrybob said:
There is no option to wipe the device. In fact, I have had other Galaxy S models and I'm pretty familiar with the screen however the Ace does not load into that recovery. Either it goes to "Downloading.." or "RAMDUMP (Arm9 mode)".
Thanks
Click to expand...
Click to collapse
he was talking about recovery menu which can be accessed pressing down home button while booting.. if device is in bootloop then try to wipe data from recovery first as that might help
madman_amit said:
well seems like sammobile haven't got for 5830L
but not to worry alternative site has one specifically rare rom of "D"
download it from this link
http://hotfile.com/dl/137128537/a629597/GT-S5830D_TLS_S5830DTLKI4_S5830DTLSKI4_S5830DTLKI4.rar.html
which you originally were using.. no other things for D
password : sampro.pl
Happy Flashing
---------- Post added at 12:10 AM ---------- Previous post was at 12:09 AM ----------
he was talking about recovery menu which can be accessed pressing down home button while booting.. if device is in bootloop then try to wipe data from recovery first as that might help
Click to expand...
Click to collapse
Thanks buddy! I tried that exact ROM however it didn't seem to work either. I used the 'Coopers_V1.0.ops" file under the "OPS" option in Odin and the "S5830DTLKI4_S5830DTLSKI4_S5830DTLKI4_HOME.tar.md5" file under the "One Package" option. Like I said before, the flash went through in "Downloading..." mode, and Odin said "PASS" however, when it came time for the phone to reboot itself, the screen started flashing and did nothing new. Same Samsung logo appears and it seems to hang right there.
Also I dont think the device has a same recovery menu anymore because even though I hold down the Home + Power buttons, it does nothing. It simply flases the screen at the Samsung logo screen.
Any other tips for me to try? Thanks again!
wierd that u cannot enter recovery mode while u can enter download mode and successfully flash it using odin.
even if u messed up recovery when u first use superoneclick earlier, flashing via odin should also flash it with new fresh recovery. so how long did u hold the home+power? i'm asking just to be sure. maybe u not hold it long enough for recovery mode to kick in.
an0nym0us_ said:
wierd that u cannot enter recovery mode while u can enter download mode and successfully flash it using odin.
even if u messed up recovery when u first use superoneclick earlier, flashing via odin should also flash it with new fresh recovery. so how long did u hold the home+power? i'm asking just to be sure. maybe u not hold it long enough for recovery mode to kick in.
Click to expand...
Click to collapse
I held it down for more than a minute just to make sure. As soon as I put the battery back in and try and restart the phone, it goes into an infinite loop at the Samsung screen.
Even I find it odd that the phone will go into Downloading mode but not recovery.
Any other suggestions?
try to install qtadb (google for it). connect the phone with pc via usb, launch qtadb and boot the phone. qtadb should display some logcat. paste the logcat output here. maybe we might have a clue whats wrong by looking into the logcat
but even if phone still stuck, just wait a few moment. if qtadb had access to the phone system via its native filemanger, it means u can use adb. use adb to reboot phone into recovery
an0nym0us_ said:
try to install qtadb (google for it). connect the phone with pc via usb, launch qtadb and boot the phone. qtadb should display some logcat. paste the logcat output here. maybe we might have a clue whats wrong by looking into the logcat
but even if phone still stuck, just wait a few moment. if qtadb had access to the phone system via its native filemanger, it means u can use adb. use adb to reboot phone into recovery
Click to expand...
Click to collapse
As far as I can tell QtADB isn't even detecting the phone. I have tried to complete the procedure over and over however no show. I may not have installed ADB correctly though so I'll give it a shot again a little later.
Thanks!
edited due to same soloution already posted.
tengo uno en las misma ay solucion
This WAS the situation before the problems:
Rooted Gingerbread rom, all working fine. Decided to unroot and install the full version of the official German ICS rom by using PC Odin. All went fine and used my Note for over two days. Because of the lags en slow responses I decided to reflash the ICS rom. From that moment on I messed it up. I've been reading and searching hundreds of posts for almost a day but didn't find a solution.
This IS the current situation:
I can get into download mode
I can get in recovery mode
However, in recovery mode I can not install a rom, every flash (CWM, both ICS and GB - even using chainfire's rom needed for rooting) stops on a random moment...but never gets it to the end, even if I wait several hours. Installing is very...very....very slow.
In recovery mode i can not restore a Nandroid backup, both ICS and GB. Every backup stops when /system has te be installed. errormessage.
In download mode I can connect my Note to PC Odin. I can select a rom and start flashing. However, after appr. 80% installation halts during "nand write start", no error message. The flashing does not finish, even after hours.
Funny is, i can install a kernel like Abyss.
So, I can't restore, i can't flash using cwm in recovery and I can't flash using PC Odin. My device seems not fully bricked. The max I get when rebooting (knowing that the process has not finished) is the triangle screen.
Any advise is appreciated.
Do not flash thru CWM... Flash a good GB kernel like "franco.Kernel" but thru PC Odin then u can flash whatever u want from franco's CWM... Good luck
Don't need help anymore
Note is officially bricked. After several attempts to recover from a softbrick the screen of my Note didn't turn on anymore. No button or button combination works, no recovery and no download mode, just a black screen.
Ce said:
Don't need help anymore
Note is officially bricked. After several attempts to recover from a softbrick the screen of my Note didn't turn on anymore. No button or button combination works, no recovery and no download mode, just a black screen.
Click to expand...
Click to collapse
Flat battery? It's also possible that it's just the screen that's not working. Try entering download mode "blind". So hold power+home+vol down for ~10 seconds, then press vol up. Hook it up via usb and see if Odin can recognize it.
Thanks, didn't think of that. But unfortunately no response from the device.
So now that it looks like your phone is officially bricked, I think you should just take it to Samsung and make up a story. Like you were updating your software with Kies and something happened and the phone is just not booting up.
I am sorry you bricked your note though..
try AMORA Filemanager.. flash via recovery and you have a file manager,,, take a look on your partitions
just my idea, you got nothing to lose
musashiro said:
try AMORA Filemanager.. flash via recovery and you have a file manager,,, take a look on your partitions
just my idea, you got nothing to lose
Click to expand...
Click to collapse
I would like to but it's very hard when you can't see anything on the screen...
Maybe it's just the battery, try to charge it externally and try a JIG also
Sent from my GT-N7000 using XDA
Just a quick, final, update.
My Note was superbricked. Had to send it to a Samsung Service Center. No additional questions were asked. Samsung replaced the mainboard. Didn't have to pay anything.
Great service!!!
try this out buddy, do it on your own risk!!! anyways you have messed it up.
Ce said:
This WAS the situation before the problems:
Rooted Gingerbread rom, all working fine. Decided to unroot and install the full version of the official German ICS rom by using PC Odin. All went fine and used my Note for over two days. Because of the lags en slow responses I decided to reflash the ICS rom. From that moment on I messed it up. I've been reading and searching hundreds of posts for almost a day but didn't find a solution.
This IS the current situation:
I can get into download mode
I can get in recovery mode
However, in recovery mode I can not install a rom, every flash (CWM, both ICS and GB - even using chainfire's rom needed for rooting) stops on a random moment...but never gets it to the end, even if I wait several hours. Installing is very...very....very slow.
In recovery mode i can not restore a Nandroid backup, both ICS and GB. Every backup stops when /system has te be installed. errormessage.
In download mode I can connect my Note to PC Odin. I can select a rom and start flashing. However, after appr. 80% installation halts during "nand write start", no error message. The flashing does not finish, even after hours.
Funny is, i can install a kernel like Abyss.
So, I can't restore, i can't flash using cwm in recovery and I can't flash using PC Odin. My device seems not fully bricked. The max I get when rebooting (knowing that the process has not finished) is the triangle screen.
Any advise is appreciated.
Click to expand...
Click to collapse
i was not a member when i commited this mistake. but then big thanks to this community it helped me back from softbrick.
first you do is install a stock kernel of ics on your note go into recovery and just clear cache partition, thats it no wipe/data factory reset.
then,
install the pit file from this thread, also read it completely before proceeding. http://forum.xda-developers.com/show....php?t=1667886 , hoping yours is 16gb version and also read this thread for additional info but its quite complicated for me so im just telling you the direct method and hopefully itll get your note back to work. so once you download the 16gb pit file unzip it and in the unzip folder you will find a separately lying pit of 16gb stating patched-standard thats the one you want.
then,
goto samfirmware and download the latest ics firmware(i downloaded the indian one as it is in file .tar),
unzip it till you get .tar file.
open odin- click pit-select 16gb patched standard pit- check wether repartion is ticked- click pda-select the .tar file you extracted connect your phone and start. this time i wont stop at factory.fs.....
NOTE THAT AFTER THIS PROCEDURE IS COMPLETED SUCCESSFULLY YOUR INTERNAL STORAGE WOULD BE ONLY 8GB INSTEAD OF 11 GB STOCK WHICH YOU WERE GETTING.
I REVIVED MY NOTE THROUGH THIS PROCEDURE. PROCEES AT YOUR OWN RISK.
one your phone is working you'll be able to reset the counter with a jig and get your phone under warranty and get your motherboard changed by teliing at the Samsung Service that you are getting only 8gb instead of 11gb you used to get earlier(warranty only if you had any).
hope this helps mate.
BEST OF LUCK!!
A BIG HUGE THANKS TO hg42.....
My i9000 respond to Downloading Mode (Volume Down+Home+Power) but it doesn't boot...the logo stay on and on until I decided to take off the battery.
Is there a foolproof method to recover my phone? It was locked to T-Mobile and has been unlocked to all networks and rooted - the ROM was Gingerbread 2.3 and working perfectly until I decided to "upgrade" to Jelly Bean...:silly:
I did backup the previous ROM via CWR but right now I can't access any partition...
Help!
with gazbil
Does ODIN recognize your phone when you're in download mode? If so, you should be able to flash gingerbread without losing all your data.
Skire90 said:
Does ODIN recognize your phone when you're in download mode? If so, you should be able to flash gingerbread without losing all your data.
Click to expand...
Click to collapse
thanks for your reply....
Yes Odin recognize my phone and I've tried to update using "JW4" (these 3 letters represent the end of a ROM file which isn't Gingerbread - I've followed this tip from another thread) - Odin says PASS (green box) but when I try to reboot the phone get stuck in Recovery mode (3?) - there are some errors, related to Data and Cache which I believe need to be erased from previous install but still no luck...
I'll try to post a picture of the error messages (or maybe I just copy the text here). At least the booting gives some signals now - there is a logo loop while before there was no boot whatsoever - so, things seems to improve a bit.
solved!
I've solved the problem by installing dbdata.rfs:
hope this helps others....
in the end I got into troubles because I didn't wipe data and cache before flashing the new ROM.
I have a Samsung Galaxy Mini and I succesfully rooted it, however it seems to be impossible to add cyanogen to it cause ii need clockworkmod recovery
1. I tried downloading it from the stock loader (on the update from sdcard place thing ) and it will just freeze when it comes to Replacing stock recovery with ClockWorkModRecovery. I have tried severall versions of it, including the one that came from the clockworkmod website but all of them just freeze
2. I tried connecting them to the pc but samsung kies can't see my phone and i can't even find all the files needed to use them on Odin
so what do I do????
MrRootGuy said:
I have a Samsung Galaxy Mini and I succesfully rooted it, however it seems to be impossible to add cyanogen to it cause ii need clockworkmod recovery
1. I tried downloading it from the stock loader (on the update from sdcard place thing ) and it will just freeze when it comes to Replacing stock recovery with ClockWorkModRecovery. I have tried severall versions of it, including the one that came from the clockworkmod website but all of them just freeze
2. I tried connecting them to the pc but samsung kies can't see my phone and i can't even find all the files needed to use them on Odin
so what do I do????
Click to expand...
Click to collapse
First of all make sure you installed drivers in Samsung Kies. After, make sure to have working version of odin. Tried connecting the booting into download and see if it detects it?
MrRootGuy said:
I have a Samsung Galaxy Mini and I succesfully rooted it, however it seems to be impossible to add cyanogen to it cause ii need clockworkmod recovery
1. I tried downloading it from the stock loader (on the update from sdcard place thing ) and it will just freeze when it comes to Replacing stock recovery with ClockWorkModRecovery. I have tried severall versions of it, including the one that came from the clockworkmod website but all of them just freeze
2. I tried connecting them to the pc but samsung kies can't see my phone and i can't even find all the files needed to use them on Odin
so what do I do????
Click to expand...
Click to collapse
Make sure your mini has gingerbread and samsung drivers installed on your pc/laptop.
Before you begin please make sure your battery has at least 70% of charge.
1. Download Odin Multidownloader v4.38 for GTS5570, Tass_v1.ops and Clockwork Mod Recovery v4.0.0.5(tass-recovery-cwm.tar) if you do not have them already. (Attachments)
2. Run Odin Multi downloader v4.38 and select the Tass_v1.ops by clicking OPS button.
3. Select One Package Option and Click One Package button and select the tass-recovery-cwm.tar file you downloaded.
Leave other settings to default (i.e. don’t change any other options/settings)
4. When you are done reboot your phone in download mode (Press Volume Down + Home + Power button to go to download mode)
5. Connect your phone in download mode to your computer via USB Cable.
6. When Odin detects your phone (If you see a com port number written in yellow background at the top left, then your phone is detected. View image.), click Start button.
7. Wait till Odin finishes the job (approx. 3-5 minutes) and when it reports ‘PASS’, you can disconnect your phone.
Go to the recovery mode (Press Home + Power button) and see your new recovery with tons of useful options. Now that you have CWM recovery you will be able to do just more than nandroid backups. You can also partition your sdcard as well as flash a custom rom on your galaxy pop. Go ahead and experiment with various options. But, be careful playing with your device’s recovery is very risky task if you lack appropriate information or skill.
Please help me i want to install cwm on my rooted gts5570 froyo using mobile odin lite..
send from my GT s5570 froyo..
Please any body answer...how to install cwm or upgrade my froyo gts5570 without computer...i have odin mobile lite also installed
send from my GT s5570 froyo..