I rooted my phone successfully.
I installed a custom rom successfully.
I can still install custom roms via safestrap (The one I have can be installed).
BUT I cannot seem to flash the original ATT stock rom via odin or safestrap, for some reason. Ideas? I tried downloading the stock rom multiple times from different sources.
iLiberate said:
I rooted my phone successfully.
I installed a custom rom successfully.
I can still install custom roms via safestrap (The one I have can be installed).
BUT I cannot seem to flash the original ATT stock rom via odin or safestrap, for some reason. Ideas? I tried downloading the stock rom multiple times from different sources.
Click to expand...
Click to collapse
Did you flash the bootloader via Odin?
"All we know is...He's called the Stig!"
Sent from my G900A Rockin ClinchRomL
iLiberate said:
I rooted my phone successfully.
I installed a custom rom successfully.
I can still install custom roms via safestrap (The one I have can be installed).
BUT I cannot seem to flash the original ATT stock rom via odin or safestrap, for some reason. Ideas? I tried downloading the stock rom multiple times from different sources.
Click to expand...
Click to collapse
Try following this guide: [GUIDE] Soft-bricked, looking to unroot, or just looking to downgrade, or start over? by shortydoggg
I think you can apply your files to the methods shortydoggg explains and you should get the same results.
Related
Could anyone told me what's the relationship between Odin and Rom Manager
I wanna upgrade captivate from 2.1 to 2.2, so i read some guides
It seems that some guides told me use odin and need the adb shell or combine keys to enter downloading mode.And then flash the pit,and csc,phone,pda.
But meanwhile, some guides said just put the rom in sd card and reboot the phone by Rom Manager.
So i get confused,could anyone told me which should i listen?
By the way,if the phone is locked 3 keys, does rom manager still work?
Odin is the a flashing tool that is run from the PC. Rom Manager is a tool that is run from the phone itself. It depends on what rom you want to flash, some of them are built to be flashed from Odin, and as such won't flash with Rom Manager and vice versa. Other than they are both flashing tools they don't really have a connection.
As to the question regarding if rom manager will work with no-button-combo phones, I'm pretty sure it will, but don't quote me on it.
Trump211 said:
Odin is the a flashing tool that is run from the PC. Rom Manager is a tool that is run from the phone itself. It depends on what rom you want to flash, some of them are built to be flashed from Odin, and as such won't flash with Rom Manager and vice versa. Other than they are both flashing tools they don't really have a connection.
As to the question regarding if rom manager will work with no-button-combo phones, I'm pretty sure it will, but don't quote me on it.
Click to expand...
Click to collapse
Thanks,you means these two tools can do exactly the same thing,but the rom source is different?
The rom manager can use a .zip rom contains data/META-INF/system etc. folders?
And the Odin should flash the rom which contains *.pit,*.tar,*.tar.md5 ?
By the way, i saw the 2.1 don't support the recovery etc. from apps, does that means rom manager doesn't work in 2.1? (I already read the 2.2 guide, and it said just use the rom manager)
Yeah, both are tools used to flash roms to your phone. However a rom made to be flashed by odin can't be flashed with Rom Manager, and a rom made to be flashed by Rom Manager can't be flashed with Odin. Some developers make two versions of the same rom so that you can flash it with your preferred method.
The last thing you mentioned is backwards... 2.1 uses recovery 2e which allows for the use of self-signed update.zips (this is what RomManager uses to get into clockwork recovery which is a modified recovery that does the actual flashing). However 2.2 uses recovery 3e which doesn't allow for this.
This means that if your on 2.1 presently you can flash with RomManager (you can even use RomManager to flash from 2.1 to 2.2), but if your using 2.2 your only flashing option is to use Odin.
Once on 2.2 you can use Odin to flash a modified 2e recovery that works with froyo and you will once again be able to use self-signed zips. (some of the unofficial roms like cognition do this automatically so you don't have to)
Trump211 said:
Yeah, both are tools used to flash roms to your phone. However a rom made to be flashed by odin can't be flashed with Rom Manager, and a rom made to be flashed by Rom Manager can't be flashed with Odin. Some developers make two versions of the same rom so that you can flash it with your preferred method.
The last thing you mentioned is backwards... 2.1 uses recovery 2e which allows for the use of self-signed update.zips (this is what RomManager uses to get into clockwork recovery which is a modified recovery that does the actual flashing). However 2.2 uses recovery 3e which doesn't allow for this.
This means that if your on 2.1 presently you can flash with RomManager (you can even use RomManager to flash from 2.1 to 2.2), but if your using 2.2 your only flashing option is to use Odin.
Once on 2.2 you can use Odin to flash a modified 2e recovery that works with froyo and you will once again be able to use self-signed zips. (some of the unofficial roms like cognition do this automatically so you don't have to)
Click to expand...
Click to collapse
Hmmm, can this be the problem i got? Flashed from JH to Cognition 2.2B6 via rom manager, and made a backup before. Now when i'm trying to flash back the backed up JH (2.1) rom my phone is stuck on AT&T screen....
edit: with cognition 2.2 i still got 2e recovery and not 3e....
Thanks,I think i got it. It seems that developer in China always package the rom into Odin struct, so i didn't tried Rom Manager.
And dimab, I think what you need is search "Captivate JI6 kernel with "2e recovery" enabled" (I can't post link since i was new user)
rogerhe said:
Thanks,I think i got it. It seems that developer in China always package the rom into Odin struct, so i didn't tried Rom Manager.
And dimab, I think what you need is search "Captivate JI6 kernel with "2e recovery" enabled" (I can't post link since i was new user)
Click to expand...
Click to collapse
thanks
I've seen this topic, but i do actually got the 2e recovery running, so what's the point?
dimab said:
Hmmm, can this be the problem i got? Flashed from JH to Cognition 2.2B6 via rom manager, and made a backup before. Now when i'm trying to flash back the backed up JH (2.1) rom my phone is stuck on AT&T screen....
edit: with cognition 2.2 i still got 2e recovery and not 3e....
Click to expand...
Click to collapse
well first off you still have 2e because Cog 2.2 Beta 6 uses a modified 2e recovery (its modified to work with froyo)
I think that when you create a backup of your rom with RomManager it doesn't include a backup of the kernel. If so when you tried to flash your 2.1 backup it never switched your kernal back to a 2.1 compatible version. hence the not booting past the att screen.
You might want to try flashing just the kernal (not the whole rom) with ODIN... Or even easier if you have your backup on your computer you can odin 1click back to stock, put your backup back on your phone, and flash the backup again with RomManager.
Trump211 said:
well first off you still have 2e because Cog 2.2 Beta 6 uses a modified 2e recovery (its modified to work with froyo)
I think that when you create a backup of your rom with RomManager it doesn't include a backup of the kernel. If so when you tried to flash your 2.1 backup it never switched your kernal back to a 2.1 compatible version. hence the not booting past the att screen.
You might want to try flashing just the kernal (not the whole rom) with ODIN... Or even easier if you have your backup on your computer you can odin 1click back to stock, put your backup back on your phone, and flash the backup again with RomManager.
Click to expand...
Click to collapse
Woah, this did helped! HUGE thanks! First time used Odin 1Click and it was smooth, and then restored my 2.1 backup.
Didn't needed to backup on computer the rom backups, since everything was left the same...
Dima
The recently sold captivates(batch #1010) all cannot use the oneclick stock to Jf6 and get stuck in a bootloop when they use this so they have to do a more tedious process. This number is rising because every new captivate sold is 1010 and we need a stock jh7 one-click for easier rom flashing/de-flashing. Could some developer create a one-click to JH7?
DG made a flashable zip, but we can't use that to go from a custom rom to stock but maybe the files can be used? It can be found here:
http://forum.xda-developers.com/showthread.php?t=790080
joeshmoe08 said:
DG made a flashable zip, but we can't use that to go from a custom rom to stock but maybe the files can be used? It can be found here:
http://forum.xda-developers.com/showthread.php?t=790080
Click to expand...
Click to collapse
why can't it be used to go from custom to stock? it's essentially the same thing as all the custom ROMs out there except that it isn't modified. if my memory serves me right (and I'll download it just to check), it does a wipe, it applies a kernel and modem, and even includes the bloat.
ODIN is not a necessity, nor are one-clicks... they usually accomplish the exact same thing as this zip would, just with a third party program. and if you, for some reason, can't get into recovery but can get into download mode, just put JI6 on and then the 2e kernel and downgrade using this zip.
joeshmoe08 said:
DG made a flashable zip, but we can't use that to go from a custom rom to stock
Click to expand...
Click to collapse
lolwut?
I've done exactly that like 5-6 times now. It's totally cool, just run backups, disable your lagfix of choice, reboot recovery, flash, and you're using a (rooted) OTA UCJH7.
Edit: In fact, I keep a 'recovery' folder on my /sdcard/ and /sdcard/external_sd with a market-apps settings.db, efs-dev_block_stl3.img, efs.tgz, bootanimation.zip, Cognition.zip, FontPack-Storopia.zip, gps_fix_epic_signed.zip, gpsjm9.zip, JH7_OTA.zip, and update.ucjj4.modem.zip
I've only ever used Odin *once* and it was because I once tried to flash before disabling lagfix and bricked my dumb self.
Hey all, just revived my old captivate, was going to put ICS on it, was attempting to root, but the one click root program wasn't working, was hanging while rooting.
I tried factory wipe, and now I get stuck in a boot loop, it will boot the i896 bootscreen, the the Rogers screen, then reboot.
I've tried from there connecting to Kies, but it won't recognize it. I tried flashing stock Eclair to it using Odin, still bootloops, tried one click odin, still boot loops.
Any thoughts? Am I missing some obvious noob step? I don't have CWM or anything on it, just a stock 2.1 that won't boot.
Just tried flashing the AT&T firmware, same deal. Get past the ATT bootscreen, then the Galaxy S screen then it reboots.
Flashed Froyo, and it boots! But I can't root If I flash back to 2.1, back to bootloop.
Try to search around the forum for the stock recovery without signature checks. Once you have that, you can flash a rom. And most custom roms comes pre-rooted. You can also flash a kernel with Clockworkmod recovery built in, and flash the rom via CWM. Just read the Rom thread about installing.
Sent from my Serendipity VII flashed Captivate using xda premium
Limitz Cash said:
Try to search around the forum for the stock recovery without signature checks. Once you have that, you can flash a rom. And most custom roms comes pre-rooted. You can also flash a kernel with Clockworkmod recovery built in, and flash the rom via CWM. Just read the Rom thread about installing.
Sent from my Serendipity VII flashed Captivate using xda premium
Click to expand...
Click to collapse
Thanks, looking for that now, any idea where it might be to narrow my search? Hopefully this helps.
I think it should be in android development forum, in this captivate section. If your on a computer, you can search for it using the search box at the top.
Sent from my Serendipity VII flashed Captivate using xda premium
If you're on Froyo, look for the speedmod kernel. If you can flash that via Odin/Heimdall, you should have root and CWM on your Froyo build.
The other option would be to flash a stock Gingerbread rom with CWM baked in - I believe that 4-2ndtwin has a KK4-based one-click with CWM and Gingerbread bootloaders in the Stock Roms Collection thread.
jmtheiss said:
If you're on Froyo, look for the speedmod kernel. If you can flash that via Odin/Heimdall, you should have root and CWM on your Froyo build.
The other option would be to flash a stock Gingerbread rom with CWM baked in - I believe that 4-2ndtwin has a KK4-based one-click with CWM and Gingerbread bootloaders in the Stock Roms Collection thread.
Click to expand...
Click to collapse
Flashed the Kernel through Odin, but on reboot there was no sound and the touchscreen didn't work. Managed to get into CWM, so I'll see how things go.
The kernel worked, got to CWM and flashed CM9, thanks for the help!
Well, I tried flashing CWM on my T mobile Note 4, and it never worked. I used Odin, and while it said it worked, I still get stock recovery. HOWEVER, when I check for OTAs, my phone says it has been modified and I need to use Kies. I'm on stock firmware and haven't even rooted, so wold it be posible, much less safe, to update via Kies when lollipop rolls out? I haven't deleted any stock apps, and as previously stated am on stock firmware and recovery and am
not rooted.
I'm not that familiar with Kies, but for sure you will be able to update by Odin flashing the Lollipop firmware once it gets posted. Your CWM flashing may have worked but then the recovery got overwritten at boot by the stock ROM. But unfortunately that would trip your Knox flag and give you 'modified' status. If you try flashing CWM again, uncheck auto reboot, and then try booting straight into recovery.
Free T-Shirts said:
Well, I tried flashing CWM on my T mobile Note 4, and it never worked. I used Odin, and while it said it worked, I still get stock recovery. HOWEVER, when I check for OTAs, my phone says it has been modified and I need to use Kies. I'm on stock firmware and haven't even rooted, so wold it be posible, much less safe, to update via Kies when lollipop rolls out? I haven't deleted any stock apps, and as previously stated am on stock firmware and recovery and am
not rooted.
Click to expand...
Click to collapse
cwm works on the note 4?
Dang ive been out of the loop
Free T-Shirts said:
Well, I tried flashing CWM on my T mobile Note 4, and it never worked. I used Odin, and while it said it worked, I still get stock recovery. HOWEVER, when I check for OTAs, my phone says it has been modified and I need to use Kies. I'm on stock firmware and haven't even rooted, so wold it be posible, much less safe, to update via Kies when lollipop rolls out? I haven't deleted any stock apps, and as previously stated am on stock firmware and recovery and am
not rooted.
Click to expand...
Click to collapse
questions:
1.) How did you flash CWM without root? If you attempted this with ODIN you tripped KNOX and therfore voided the warranty and the abilitity to get an OTA.
2.) If you already have ODIN installed and know how to flash with it why bother with Kies and/or OTA's? You can use ODIN to flash the update as soon as it is posted only. With this dev community it shouldn't take too long.
Also if you are looking to use a custom recovery you should work with TWRP. Technically CWM and Philztouch are no longer being support. Finally if you already tripped KNOX by trying to flash custom recovery, why not just root the thing now. There really isn't much of a different now.
Sent from my SM-T900 using XDA Free mobile app
This is how you root:
http://forum.xda-developers.com/showthread.php?t=2903733
If you want an update later you can always odin to stock + factory reset.
Hey there, I need some help with my N910T Note 4.
I have tried to install a few custom roms. So far here is how it's gone:
1st Rom, Tried to install Tekxodus' rom, used odin to go to stock dok2 -> cf autoroot -> twrp -> booted up twrp and tried to install the rom's .zip.. And bootloops. I try it multiple times, it goes smoothly until I go to boot and it always bootloops.
At this point I give up on this rom and go to try firekat:
Try to odin ank4: odin gives me "FAIL (AUTH)"
I google and find that I am stuck with lollipop roms? Alright well I'll try Rapture then: Try to update my baseband and bootloader using raptures tutorial and files -> Odin "FAIL (AUTH)"
So I thought maybe I should start from scratch, I try the stock dok2 baseband and bootloader.. "FAIL (AUTH)"
What in the hell do I do now? The only rom I can succsfully install is the stock dok2 rom.
Would greatly appreciate any help.
EDIT: Another note: If I odin stock dok2 and then odin cf autoroot, it also goes into bootloop.
After a few hours of messing around with my phone I finally got Tekxodus to work.
I think the problem was with my kernel, I was using the kernel from the Tekx thread, instead I used Freeza's Beastmode Rage kernel and it finally booted. Thank you Freeza, great kernel.
I am still confused about which roms I can or can't run now. The threads I've read are pretty vague, am I stuck on Lollipop roms permanently now? Which roms are available for me now?
Yep, once you went to dok2, you are stuck on lollipop. Might try poprocks as an option if you like TouchWiz based roms. Same dev as firekat. Can't suggest others though as i haven't tried any others besides CM 12.1.
Sent from my SM-N910T using XDA Free mobile app