Related
Hi, I just need alot of help! I've been a rogers captivate owner for a year and i've rooted, sim unlocked, flashed many, MANY roms with success. I have also soft bricked my cappy a few times but odin restored it back to stock every time where i started over.
So basically, i soft bricked my cappy, used odin to restore to stock rogers gingerbread 2.3.3 , rooted, used odin to install corn kernel and now every time i wipe data and everything in recovery and flash a rom, it says successful but when i restart, it just gets stuck at the " samsung I896 " screen and doesn't go any further. I can't go into recovery or do anything, but i can succesfuly odin back to stock gb. I've used this same procedure many times before and it always worked but not this time. The only difference there was, was that when it got soft bricked this time, I was going from MIUI JB to Paranoid Android JB instead of ics or gb custom roms.
Can anyone please please help me out here? I really hate stock samsung roms and I LOVED JB when i had it, and i really want it back! I would really appreciate anyone's help! Thankyouuu !
[EDIT] Thankyou everyone who tried to help, i figured it out and resolved the problem, the problem was i was wiping data/factory reseting in cwm which i shouldn't have been doing.
What about using Odin to flash a kernel compatible with the Paranoid Rom, then flash the Rom through that kernel's recovery...
Sent from my SAMSUNG-SGH-I897 using xda premium
4-2ndtwin said:
What about using Odin to flash a kernel compatible with the Paranoid Rom, then flash the Rom through that kernel's recovery...
Sent from my SAMSUNG-SGH-I897 using xda premium
Click to expand...
Click to collapse
Yeah, but paranoid android comes with its own recovery, and oh i forgot to mention, i have tried many times, and sometimes after i flash the paranoid rom, and reboot, the phone will boot but directly to recovery when i normally boot it, so i can flash the rom through its own recovery but still it just boots into recovery directly nothing else, and then i go back to stock and i've been on stock for like a month now, but im really missing paranoid androidd.
Wait i think i found the solution guys please helpp ! on stock when im about to flash the new rom, do i clear user data/ wipe data whatever it is in cwm ? Im doing that with faliure, am i not supposed to?
My phone galaxy sl gt-i9003 was running was rooted and running on codename(android) when I flash some random kernel and bricked it. I then read though lots of xda-developers threads and followed whatever was said there. It goes into recovery and download mode. So i flashed the stock ROM( which i had downloaded from sammobile ). But after that it got stuck in boot loop. Then I tried flashing a few ROM suggestions given here in xda. But each time I either got back a bricked phone or boot loop problem. Help Please!!!:crying:
balaji.nataraj said:
My phone galaxy sl gt-i9003 was running was rooted and running on codename(android) when I flash some random kernel and bricked it. I then read though lots of xda-developers threads and followed whatever was said there. It goes into recovery and download mode. So i flashed the stock ROM( which i had downloaded from sammobile ). But after that it got stuck in boot loop. Then I tried flashing a few ROM suggestions given here in xda. But each time I either got back a bricked phone or boot loop problem. Help Please!!!:crying:
Click to expand...
Click to collapse
Hard brick or softbrick
install that firmware downloaded from samfirmware.com if they could all downloads mode or go into recovery mode then wipe data / factory reset
Or try install cwm recovery via odin
╔═╦═╦═╦═╦╗╔╗
║╚╣║║╚╣╚╣╚╝║
╠╗║║║║║║╠╗╔╝
╚═╩═╩╩╩╩╝╚╝
Bad english
Sent from my phone using xda app-developers app
since u have screwed your along the way to get boot. you better to flash xxkpe or xxkpq with pit
and repartition is amust cause you are on ext4
Sent from my Galaxy Nexus using Tapatalk 2
hmmp, i somehow recover on that situation by re partitioning through odin using pit from I9003DXKB2 stock rom froyo...
then flash a I9003DXKP9 gingerbread through odin also
I9003DXKB2 is my SL's original firmware since i bough it though
but might help you...
i did all those because i want my SL to run CM10 Alpha 4 jelly bean
i downloaded the stock roms from "[ROM] STOCK ROMS for GALAXY SL I9003" thread in the developers section...
yes its better to flash with xxkpe and then with xxkpq... me too experience the same problem...
follow this: http://forum.xda-developers.com/showthread.php?t=1133787
download firmware from here: http://forum.xda-developers.com/showthread.php?t=1004647
Thank you all for replying. I solved the problem. I had forgotten to factory reset after flashing stock rom. Now its as good as new. Also I had this doubt. Is it required that you factory reset after every flash?
Sent from my GT-I9003 using xda app-developers app
unbrick your phone
balaji.nataraj said:
My phone galaxy sl gt-i9003 was running was rooted and running on codename(android) when I flash some random kernel and bricked it. I then read though lots of xda-developers threads and followed whatever was said there. It goes into recovery and download mode. So i flashed the stock ROM( which i had downloaded from sammobile ). But after that it got stuck in boot loop. Then I tried flashing a few ROM suggestions given here in xda. But each time I either got back a bricked phone or boot loop problem. Help Please!!!:crying:
Click to expand...
Click to collapse
just download heimdall oneclick.jar and run it on windows,in phone go to download mode ,in pc click on oneclick.jar and run it then click on unbrick me and unbrick your phone its easy
APU KALITA said:
just download heimdall oneclick.jar and run it on windows,in phone go to download mode ,in pc click on oneclick.jar and run it then click on unbrick me and unbrick your phone its easy
Click to expand...
Click to collapse
HEIMDALL ONE-CLICK.....haven't heard this before?...
Hi – I have a stubborn issue with my Blaze 4G not working on CM roms, I would appreciate any help you guys can provide. Below are the details:
I recently bought a T-Mobile Samsung Galaxy S Blaze 4G, and did the following:
- Rooted it using the following guide (it now has ICS)
- SIM Unlocked it using the following guide (now it works on other networks)
- Updated to CWM 6.0.3.8, since JB roms needs it
- Flashed the T769-UVLH5 modem, since CM support it
And now when I flash CM 10 stable or 10.2 nightly it gets stuck in booting and displaying the CM logo animation screen, after few minutes it reboots and does it all over again.
I remember when I upgraded to CM JB on my SGS3 I needed to flash a JB stock rom on it to get the new boot loaders for JB, but I saw no mention of this on this forum. What else am I missing?
Thanks.
TINGEA said:
Hi – I have a stubborn issue with my Blaze 4G not working on CM roms, I would appreciate any help you guys can provide. Below are the details:
I recently bought a T-Mobile Samsung Galaxy S Blaze 4G, and did the following:
-Rooted it using the following guide (it now has ICS)
-SIM Unlocked it using the following guide (now it works on other networks)
-Updated to CWM 6.0.3.8, since JB roms needs it
-Flashed the T769-UVLH5 modem, since CM support it
And now when I flash CM 10 stable or 10.2 nightly it gets stuck in booting and displaying the CM logo animation screen, after few minutes it reboots and does it all over again.
I remember when I upgraded to CM JB on my SGS3 I needed to flash a JB stock rom on it to get the new boot loaders for JB, but I saw no mention of this on this forum. What else am I missing?
Thanks.
Click to expand...
Click to collapse
You wiped data/cache/system? Reinstall it. Anyways use the new 6.0.4.4 recovery.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
You wiped data/cache/system? Reinstall it. Anyways use the new 6.0.4.4 recovery.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom. I have to admit that I forgot to do the wipes. but even after doing the wipes (data/system/ factory rest/ cach/devalk) and reinstalling the CM nightly, I still have the same issue.
as for recovery, I updated to the latest version using the rom manager, and according to the official site clockworkmod[dot]com[slash]rommanager (can't post links) I have the latest version for Blaze. how do you get the 6.0.4.4 on blaze?
I still feel it's a ICS vs JB bootloaders issue, but not sure how to proceed next.
Thanks!
TINGEA said:
Thanks Somcom. I have to admit that I forgot to do the wipes. but even after doing the wipes (data/system/ factory rest/ cach/devalk) and reinstalling the CM nightly, I still have the same issue.
as for recovery, I updated to the latest version using the rom manager, and according to the official site clockworkmod[dot]com[slash]rommanager (can't post links) I have the latest version for Blaze. how do you get the 6.0.4.4 on blaze?
I still feel it's a ICS vs JB bootloaders issue, but not sure how to proceed next.
Thanks!
Click to expand...
Click to collapse
No boot loaders man. This is before Samsung's complications.
Recovery is here.
http://d-h.st/AFu
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Thanks Somcom3X, but still didn't work. When installing the CM room in recovery 6.0.4.4 I get a bunch of getprop assert failures. This used to work on the previous version (6.0.3.8). Now the Rom won't install.
Also, I'm curious what did you mean by this is before Samsung's complications?
Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
Thanks Somcom3X, but still didn't work. When installing the CM room in recovery 6.0.4.4 I get a bunch of getprop assert failures. This used to work on the previous version (6.0.3.8). Now the Rom won't install.
Also, I'm curious what did you mean by this is before Samsung's complications?
Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
After 2011 samsung began installing software and counters to try and prevent people from rooting and installing custom firmwares.
knox is an example of this.
These devices don't have any of that complicated security.
You handy with odin? Your recovery is not right. Just to be clear, what is your model number?
If it is T 7 6 9, your good to go to odin. I'd recommend going back to stock, and then install a recovery and you should be good to go.
Somcom3X said:
After 2011 samsung began installing software and counters to try and prevent people from rooting and installing custom firmwares.
knox is an example of this.
These devices don't have any of that complicated security.
You handy with odin? Your recovery is not right. Just to be clear, what is your model number?
If it is T 7 6 9, your good to go to odin. I'd recommend going back to stock, and then install a recovery and you should be good to go.
Click to expand...
Click to collapse
Thanks again, I use the guide here to convert the image into a tar.md5 to flash using odin, but after flashing successfully I still have the same issue when installing the CM zip file in recovery, and yes it is the T-mobile Samsung Galaxy S Blaze 4G T769.
any other possible causes?
BTW - when I was flashing via Odin my upload phone screen was showing that I have a custom rom and the counter was 1.... do I need to fix that?
TINGEA said:
Thanks again, I use the guide here to convert the image into a tar.md5 to flash using odin, but after flashing successfully I still have the same issue when installing the CM zip file in recovery, and yes it is the T-mobile Samsung Galaxy S Blaze 4G T769.
any other possible causes?
Click to expand...
Click to collapse
SOLUTION:
The reason your stock recovery system keeps getting overwritten at Android startup is because of a script that is being run.* All you need to do is either rename this script or simply delete it.
Please keep in mind that if you restore your stock ROM, this script will be restored with it so you will have to rename or delete it again.* Do the following:*
1.
Make sure your device is powered on and running normally,
2.
Make sure you have rooted your device and that you have all of the necessary permissions in order to manipulate system files.*
3.
In the root file system go to \system\etc
4.
Find the file named install-recovery.sh and either rename it or, as I did, delete it.*
That’s all there is to it.*
Please keep in mind that you will need to flash your custom system recovery one more time after modifying the script file.* After that, reboot away and you will always be able to get back into your new system recovery.
Good Luck and Happy Tweaking.
Click to expand...
Click to collapse
Try that.
Found it here http://mark.candleshoreblog.com/201...-factory-stock-roms-at-android-system-reboot/
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
Try that.
Found it here http://mark.candleshoreblog.com/201...-factory-stock-roms-at-android-system-reboot/
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom3X - but I'm not sure this is needed for my case. I read the original blog post and my recovery does not get overwritten. I actually rebooted multiple times into CWM recovery and each time it is the same 6.0.4.4.
I also went into the /system/etc folder and there is no install_recovery.sh file.
to clarify, here is where I'm stuck now:
- when I use CWM 6.0.3.8 CM install completes successfully, but then CM will not boot, and will keep on cycling on the boot logo screen.
- when I use CWM 6.0.4.4 I can't start to install CM as it complained that my phone is not t769.
in all cases I'm using CM 10.2 nightly for T769.
Thanks for the help.
You should delete assert lines at the top of the zip's updater-script and it will let you flash it.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
I removed the assert lines from the updater script, and it was able to complete the install process afterwards, however when I booted the new CM 10.0 system it got stuck on the cyanogenmod boot logo. I made sure I do a system/data rest, cleared cash, and cleared devalk.
I do not think it's an issue with my recovery as I'm getting the same result as I did with the official 6.0.3.8.
Something else is going on.
Any ideas?
Thanks.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
I removed the assert lines from the updater script, and it was able to complete the install process afterwards, however when I booted the new CM 10.0 system it got stuck on the cyanogenmod boot logo. I made sure I do a system/data rest, cleared cash, and cleared devalk.
I do not think it's an issue with my recovery as I'm getting the same result as I did with the official 6.0.3.8.
Something else is going on.
Any ideas?
Thanks.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Tar back to stock GB. Upgrade to ICS. Then root and install cwm. Flash away
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
You should delete assert lines at the top of the zip's updater-script and it will let you flash it.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom3X - but this is more trouble than what I wanted to put in - I'll stick with the rooted stock ROM I have. I was hoping the process was a little more straight forward, similar to my SGS3.
thanks for all your help thus far!
Somcom3X said:
Tar back to stock GB. Upgrade to ICS. Then root and install cwm. Flash away
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Ok, my rooted ICS stock is acting up (random shutdowns and such), so I need to give this another try and get this phone to CM.
I tared back to stock GB, skipped the upgrade to ICS (was not able to upgrade via the ROM software update option), flashed CWMR (5.0.4.x) via Odin, upgraded to CWMR 6.0.4.5, installed CM 11 nightly, and then wiped data/factory rest and Dalvik .... and ....
it is still stuck on the boot screen....
I seriously would appreciate a silver bullet right now!
TINGEA said:
Ok, my rooted ICS stock is acting up (random shutdowns and such), so I need to give this another try and get this phone to CM.
I tared back to stock GB, skipped the upgrade to ICS (was not able to upgrade via the ROM software update option), flashed CWMR (5.0.4.x) via Odin, upgraded to CWMR 6.0.4.5, installed CM 11 nightly, and then wiped data/factory rest and Dalvik .... and ....
it is still stuck on the boot screen....
I seriously would appreciate a silver bullet right now!
Click to expand...
Click to collapse
Hmm. Go back to stock ics, flash a 10.2 recovery, then flash whatever you desire.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
What is a10.2 recovery? Is it a certain version of CWMR? And do I need to flash it via Odin? Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
What is a10.2 recovery? Is it a certain version of CWMR? And do I need to flash it via Odin? Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
It would be cwm 6.0.2.7
You can flash the img through a zip or by terminal on the phone.
Odin needs a tar'd recovery img
Sorry been very busy.
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2577265
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Thanks Somcom3X - I looked all over this forum and the internet, and could not find a link for a 6.0.2.7 CWM for Blaze - I found it for other phones but not Blaze. can you please point me to a link if you happen to know of one. the official site does not have an archived list of previous versions.
as for the provided link, I did follow it through, and downloaded the recovery Tar (it was CWM 5.5.04) but that yielded the same results after installing CM 10 and 10.2 - stuck at boot screen logo. I'm reasonably confident now that it is not a recovery issue, as I flashed half a dozen different versions and none worked with CM 10, 10.2, or 11.... it has to be something else!
Thanks.
TINGEA said:
Thanks Somcom3X - I looked all over this forum and the internet, and could not find a link for a 6.0.2.7 CWM for Blaze - I found it for other phones but not Blaze. can you please point me to a link if you happen to know of one. the official site does not have an archived list of previous versions.
as for the provided link, I did follow it through, and downloaded the recovery Tar (it was CWM 5.5.04) but that yielded the same results after installing CM 10 and 10.2 - stuck at boot screen logo. I'm reasonably confident now that it is not a recovery issue, as I flashed half a dozen different versions and none worked with CM 10, 10.2, or 11.... it has to be something else!
Thanks.
Click to expand...
Click to collapse
I'm very sorry for the delay. Been very very busy.
https://www.dropbox.com/s/awp1zy4u3x34a2v/CWM-cm-10.2-Recovery-t769.zip
That is my personal 10.2 recovery. Works fine for me.
The author is me, but I was too lazy to change the lines.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Hey guys! Maybe I am really bad at finding stuff, but could someone clearly post the stock ICS software for the blaze? For all the recoveries to go back to stock, I keep finding the gingerbread ones. I currently am running CM 11, and if anything goes wrong, I know that I need to use the ICS recovery, rather than the gingerbread one. Thank you in advance for helping a helpless noob! XP
Sent from The Doctor's Nexus 7
This is what I used for a cwm flashable stock ICS ROM http://forum.xda-developers.com/showthread.php?t=2329081
For recoveries they should be listed in the blaze bible
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
champ784 said:
Hey guys! Maybe I am really bad at finding stuff, but could someone clearly post the stock ICS software for the blaze? For all the recoveries to go back to stock, I keep finding the gingerbread ones. I currently am running CM 11, and if anything goes wrong, I know that I need to use the ICS recovery, rather than the gingerbread one. Thank you in advance for helping a helpless noob! XP
Sent from The Doctor's Nexus 7
Click to expand...
Click to collapse
FOR EVERYONE HAVING ANY PROBLEMS RETURNING TO STOCK FIRMWARE READ THIS
So first register at www.sammobile.com, then search SGH-T769 under firmware and download the August 2012 ICS or The Feb 2013 ICS Firmware, wait for the download to finish (took me 30 minutes) then extract which ever firmware zip you downloaded then using Odin click on PDA and select the .md5 file which is located in the extracted ICS Firmware Folder that you've downloaded from sammobile.com
Download the PIT file here
http://forum.xda-developers.com/showthread.php?t=1919228
Click on PIT in Odin and then select the one downloaded from the link above
Edit: I believe the pit file download link at that thread no longer works but if I remember correctly the pit file isn't needed (it's not do or die) you can continue without it your phone will be fine
then make sure re-partition isn't checked and start the flashing process after it is done flashing and reboots you'll have stock ICS.
*IF YOU WANT TO ROOT IT READ BELOW*
to root it simply follow the instructions over at the root ics stock thread found here
http://forum.xda-developers.com/showthread.php?t=1919228
This will flash a custom recovery and once the recovery is flashed using Odin reboot into recovery and flash the superuser.zip then you'll have Rooted Stock ICS Firmware
*BOOT LOOP MIGHT OCCUR*
To fix boot looping after flashing stock ICS just boot into stock recovery and wipe data and cache then reboot or on custom recover wipe cache and dalvik cache reboot and you're good to go.
If I helped you in anyway don't be afraid to hit thanks!
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app
Thanks a lot man! I was rooting my mom's phone (we all got blazes... Go figure!) and ran into an issue when I ran into a bootloop the first time I tried rooting... When I tried undoing the softbrick, I accidentally loaded the gingerbread stock back on, rather than ICS, and found that her SD partition was inaccessible. Thankfully, using the stock ICS, I reverted back to it and then rooted again when done with that. She's now on ProvisionMod, and its running smooth as butter! I was hesitant to put her on Kitkat cuz I know the camera bug still needs to be worked out... But when that's fixed, I plan on putting her on something like CM 11 when its all said and done. Thanks to all the helpful developers who made all of this possible! You guys are the best!!!!!
Sent from The Doctor's Nexus 7
Ok, Ive unlocked my bootloader, installed CWM, rooted my device and checked that it worked, and when I go to the boot loader and select recovery it takes me to CWM. Ive made backups from it and and they restore fine. I even installed a custom kernel and it worked because noFrills let me OC/choose a different governor. Yet from the three ROMs Ive tried so far, they install fine, no errors from CWM, but when I boot up it just gets stuck booting forever. Ive tried wiping everything, Ive tried wiping some things, heck I even tried wiping nothing but I still get the same issue. Id really like to try a new ROM now that I went through the trouble of voiding my warranty, so please try to help me. Thanks in advance, alexbenh
Same here
Gonna try out this guy's method real quick except with CWM
http://forum.xda-developers.com/showpost.php?p=49668571&postcount=5
I know this seems obvious, but are the ROMs you are flashing specific for your device?
Sent from my ST18i using xda app-developers app
yes, I have the Moto G XT1034 and have flashed ROMs before on my old galaxy exhibit and never had any trouble with that
Join the club, same here, done everything right but no custom rom joy for me
Sent from my XT1032 using XDA Premium 4 mobile app
If you're flashing a kitkat ROM, make sure you're already running KitKat. If you're still on 4.3, then fastboot flash the stock 4.4.2 image first, then try custom roms
Sent from my XT1034 using Tapatalk
WOOOHOOO, I reinstalled the stock 4.4 firmware and everything, I couldnt root it with superboot so I just skipped the rooting step. Then I flashed CWM through the bootloader although I decided to take a risk and instead of "fastboot flash recovery recovery.img", I did "mfastboot flash recovery recovery.img" just to see if it would change anything. Not sure if thats why it works for me now, but its worth a try. Good luck to the rest of you who have this problem.
lowrider262 said:
If you're flashing a kitkat ROM, make sure you're already running KitKat. If you're still on 4.3, then fastboot flash the stock 4.4.2 image first, then try custom roms
Sent from my XT1034 using Tapatalk
Click to expand...
Click to collapse
Yes, I was already running the stock 4.4 ROM the only differences was that I had a custom kernel which could possibly be an issue, but I wouldnt think so
http://forum.xda-developers.com/showthread.php?t=2620060&page=2
BBOXPT said:
http://forum.xda-developers.com/showthread.php?t=2620060&page=2
Click to expand...
Click to collapse
huh, I had not tried using TWRP, but I thought CWM had a fix permissions command as well.
alexbenh said:
huh, I had not tried using TWRP, but I thought CWM had a fix permissions command as well.
Click to expand...
Click to collapse
My experience. I tried CWM then loaded a Rom, the first one I tried being CM11 = Bootloop, Then I tried several other Rom's and always the same result, spinning on Bootloop
I then put the phone back to stock firmware 4.4.2 and tried TWRP version TWRP2630, no joy even the bootloader wouldn't work right.
Finally put the phone back to stock AGAIN (now getting frustrated!) and tried installing TWRP2631 using fastboot. That did the trick, now all ROM's load and run fine. This version of TWRP appears to be working well. Backup/restore works, and no problems at all.
Other's report CWM works well, but not for me unfortunately.