Hello Guys,
I'm new at XDA but I have a question:
A few months ago I've installed a custom rom to my S5830i.
The name is Mindcr. 2.8
That worked perfect, but now there is an update (newer version) of it.
And I went to recovery mode and went to Clockworkmod and deleted my dalvik cache and data and system memory.
After everything I've deleted I went to Apply zip from SD-Card and I choosed Mindcr. 2.9
After that It was 5 minutes like ''installing system'', after that it saidl, ''mindcr 2.9 fully installed.
After that I've rebooted my device and than you see the Samsung Galaxy Ace logo.
And I've waited about 2 hours and it still was like that.
I've unbricked my phone with odin and tried again, but it still stays there.
Why doesn't he just reboot normally?
If there's no answer, I just unbrick it and go further with normal android.
Related
I have a rooted galaxy tab 10.1 (Wifi) p7510 from the US
I wanted to flash the pershoot kernel on my galaxy tab so that I could over-clock my processor and so I used ROM Manager to create a back-up and then used CWM to install the kernel. The install went fine and the device booted an was working flawlessly.
Then I decided to go back to my previous stock kernel and thus I booted into CWM, and clicked Backup/Restore and picked the back up I created. At the point where it is restoring data, it quits and says error restoring data and when I tried to boot the tab, I got stuck at the Samsung Boot Logo.
I tried wipe data,cache,Dalvik and nothing work.
I even tried advanced restore and managed to restore all components of the backup except the data.. Still no luck.
I'm downloading a custom ROM now (starburst) but how will I even be able to place it in the root partition if the galaxy tab can't boot into a usable state..
P.S. You may have noticed, I'm a noob so very detailed guides would be very good
Thank you
minamfm said:
I have a rooted galaxy tab 10.1 (Wifi) p7510 from the US
I wanted to flash the pershoot kernel on my galaxy tab so that I could over-clock my processor and so I used ROM Manager to create a back-up and then used CMW to install the kernel. The install went fine and the device booted an was working flawlessly.
Then I decided to go back to my previous stock kernel and thus I booted into CMW, and clicked Backup/Restore and picked the back up I created. At the point where it is restoring data, it quits and says error restoring data and when I tried to boot the tab, I got stuck at the Samsung Boot Logo.
I tried wipe data,cache,Dalvik and nothing work.
I even tried advanced restore and managed to restore all components of the backup except the data.. Still no luck.
I'm downloading a custom ROM now (starburst) but how will I even be able to place it in the root partition if the galaxy tab can't boot into a usable state..
P.S. You may have noticed, I'm a noob so very detailed guides would be very good
Thank you
Click to expand...
Click to collapse
How long was it stuck on the samsung logo? If you didn't let it sit for at least 45 minutes, try that first.
So I left it for about 10-15 minutes and it worked.... Barely working though, almost everything crashes, very slow and choppy.. Looks like it's heavily corrupt.. At least now I can copy the custom ROM into the root folder. Is it safe to do so now??
And can you also post me a link to a .zip stock ROM for my tab??
Thanks a lot!
I had the exact same problem and I did following steps to get the tab working
1- find a stock from that flashable with Odin ( I used stock kl2 rom, can be found on tab 10.1 developer forum)
2 - flash the rom (.tar file) via Odin ( same as flashing cwm)
3 - after the flash I was still in boot loop no worries, go to recovery mod ( hold power + volume down then volume down and then volume up)
4 - wipe everything ( simply used very option that says wipe on it)
5 - restart and done! Everything is back to normal again
Only thing was I lost all my data pics etc but I got my tab working again
Btw not claiming these steps are essential, perhaps someone could come up with a more comprehensive method. This is just the way that I was able to restore my tab.
That's what I'm down to with my Tab. Flashing w/o CWM and/or unrooting to see if the /data error clears up. At least I'm not dead (I hope) to the point that I can't back up my SD card to external storage.
I can't restore any nandroid I have w/o the /data error and flashing custom ROMs gives the same result (everything FC's) except no /data error.
Wish I'd brought it to work today so I could tinker w/ it.
Hi there,
I got my SGS3 on Friday, it took two hours until I got bored and rooted it.
First everything was fine, I was using CWM (installed via ROM Manager) and tried some ROMS.
Today, when I wanted to flash CWM Touch via ROM Manager, the phone rebooted and since then in stuck in a boot loop.
There was no error during the process, according to ROM Manager the recovery was properly flashed. All I can do is entering the Download Mode.
I tried to flash two different stock images via ODIN3 (v3.07) but the phone keeps rebooting, even when i try to repartition it using "GT-I9300_mx_20120329.pit". I can boot the phone into recovery, I can see the recovery for a short moment and then the phone reboots. I made it to flash CWM 6.0.3.1 via ODIN, and when booting into recovery then I can see that it worked, but after a second the phone reboots.
Currently I'm downloading a 3-part/3-files factory image, hoping this can help. According to what I've read on the forums so far I don't think it will change anything, but who knows... Any other suggestions?
Greetz
// j_dee
rom manager is not supported on all the phones. probably that should have damaged your phone. hope you get your phone working. good luck :good:
I was using CWM (installed via ROM Manager)
Remove rom manager .
CWM says
Not compatible with ROM Manager !
That is if you recover from damaged pit .
jje
Hey guys,
thanks so far... According to the CWM homepage the SGS3 is supported, in fact there's current even a newer CWM version available for SGS3 than for GNEX.
Fortunatly I just made it to un-soft-brick the device:
- Removed the battery for a few minutes, then placed it back in the phone (for some reason the phone often booted as soon as the battery was back in its place, so I had to be quick).
- Tried to reboot into recovery again, holding "Vol+"+"Home"+"Power" until the recovery showed up, and the phone rebooted.
- Kept on holding "Vol+"+"Home"+"Power" until recovery showed up again, for some reason the phone didn't reboot this time, and then I released all buttons.
- Thanks to ODIN I could now use CWM 6.0.3.1 to flash S4 Revolution (by Elegant Team) from my internal storage, rebooted the phone and it worked. All my data was still in place, so it seems all my attempts to flash the stock images via ODIN did not succeed, save for the stock recovery.
Crap, I was really afraid of having my brand-new SGS3 hard-bricked only a few days after delivery. With my HTC Desire HD it took me almost 6 months to cause the first almost-brick.
There's only one thing I can image with ms SGS3 that might have affected the CWM / ROM Manager flash - I was running a S4-ported ROM ("S4 Revolution"), because this makes "TriangleAway" recognize it as "I9500" phone, so I cannot reset the counter at the moment.
But ROM Manager always showed "GT-I9300"... So in the end I've no clue what has happened so far.
Greetz
// j_dee
don't use rom manager
Mid year I decided to root and flash Cm 11 onto my little s3 mini (gt-i8190) and everything went great. Recently I read on the Novafusion website that they recommend using TWRP instead of CWM, searched on Google and saw it was safe to flash over custom recoveries. I used Odin to flash over the TWRP I downloaded from the Novafusion site. When odin completed its process my phone rebooted into TWRP and it all seemed fine, then I proceeded to flash the latest version of the Cm 11 4.4.4 rom. Again everything went great and my phone booted up normally.
I got the zip file for the Android L keyboard and I used Rom manager to reboot into recovery and showed the "Samsung Galaxy sIII mini gt-i8190 screen and just went black for 10 seconds, rebooted and continued going black then rebooting. I pulled the battery out and booted up my phone again then used rom manager to flash CWM again and it worked! I used CWM to flash the keyboard apk and it worked.
I was a little bit worried about the recovery bootloop and decided to make a nandroid backup. I couldnt reboot into recovery, manual way or with Rom manager.
I have used odin to flash CWM and TWRP a few times now without any luck. My phone just reboots normally when odin finishes.
If anyone could shed some light on this issue I would be grateful.
Thank you.
Ok so i went ahead and rooted my Samsung Galaxy S Duos 2 GT-S7582 with vRoot and all was fine and well.
Then I installed CWR and tried to instal the Gt-S7582 Extreme Lollipop V2 wich i found on xda and i did and after i did it prompted me to click either no or yes for stock reboot recovery or something and i pressed no. After that my phone constantly reboots in recovery mode and when i go in zip there are no files so i can reinstall the rom. What do i do pls tell me!! I have no problem in going back to stock version right now i can reroot later.
Hello everyone. This is my first thread on this XDA and I hope if somebody could help me. First of all, I know this phone was released in 2011 and it is considered old and outdated but I could really aprreciate help. I checked many threads and Youtube guides (I considered only those with good rating) and spent total of approximately of 16 or more hours in order to fix this but none of them were good for my case.
So here's the problem. Problem appeared about 20 months ago. First, I installed CM 11 on phone and everything was working fine except for the front camera. Then I tried flashing back to Stock ROM which I've downloaded from SamMobile. I used Odin for both times. After process was over, my problem appeared. Every time I turned on the phone it didn't get past Samsung Galaxy S+ logo. So I figured out it was Boot loop and that it can be fixed. I just couldn't find the working way.
Here are things I've tried: 1) Flashing Stock ROM via Odin without wiping cache first
2) Flashing CM 12 via Odin without wiping cache first
3) Flashing CWM Recovery via Odin, wiping cache and then flashing Stock ROM via Odin
4) Putting phone in Download mode, connecting it to PC and running Kies (Kies couldn't connect the phone because device wasn't responding)
From above mentioned only number 3 partially worked. CWM installed correctly but after I flashed Stock ROM I got same Boot loop problem again.