Develop Bugs

I have a noob question about flashing custom ROMs

To unroot the phone what I usually do is after running the triangle away app, I do a complete wipe(all wipes on the phone from recovery) and flash the Stock ROM from the computer using Desktop Odin.
I was wondering what happens, if I have a stock unrooted phone, and I try flashing a custom ROM using desktop Odin?? WIll it work anyways or possibly brick the phone(or wont allow me to flash at all)?
The reason I ask is every thread talk abt flashing custom ROM's using custom recovery or mobile odin after rooting the phone.
Thanks

I also have a question I tryed to update my software on captivate glide att but I rooted my phone so I could not. Anyway I messed some things up reset the phone then I went to re install several apps and now my phone says device isn't compatible with this version when I just tryed to install from back up and it faild so I tryed from the market place and kept getting that error. Idk what to do.
Sent from my SAMSUNG-SGH-I927 using xda app-developers app

Odin flashes TAR files, not ZIP files. You should only need Odin to flash stock.
You shouldn't need Triangle Away if you rooted following the instructions that can be found on these boards.

From what I understand, you cannot flash a custom rom without having CWM installed.
I could be wrong... I flashed Blazin ROM to my phone yesterday but then reverted back to
the backup (Nandroid) I had made prior. Playstore wouldn't work and I can't figure out what
gapps I need to get it going.

I agree with the guys above. In order to flash custom ROMs you'll need CWM installed to do so. Once you boot into recovery it should take you to CWM. From there, you can flash the zip files only.

[Q] Phone says CWM is installed but always boots to stock recovery?

I'm totally boggled here, I've never had problems like this. I've rooted my T-999, no problems there, but when I install CWM, either the non-touch or touch versions, it doesn't boot into that recovery. When you recovery boot, either manual or through ROM Manager, it just boots to the stock recovery. I've tried re-installing through ROM Manager and through Odin, to no avail. I'm pulling my hair out...help!

Just use the the root 66 method and then use goomanager to install twrp recovery. Did this process for my brothers S III last night over the phone.

I had the same problem before. Tried multiple ways but the cwm recovery will not stick, even though it appears working in Odin. Only way I got cwm recovery to install is by going back to an earlier version os.
You need to find an earlier version of factory stock jelly bean or better yet ics and flash it with Odin. Make sure it's a factory image. After that just root and install cwm recovery with Galaxy s3 toolkit. Then just install whatever rom you like.
Sent from my SGH-T889 using Tapatalk 2

Ok, trying out these methods and will report back. Thanks.

whatsitsnamenow said:
I had the same problem before. Tried multiple ways but the cwm recovery will not stick, even though it appears working in Odin. Only way I got cwm recovery to install is by going back to an earlier version os.
You need to find an earlier version of factory stock jelly bean or better yet ics and flash it with Odin. Make sure it's a factory image. After that just root and install cwm recovery with Galaxy s3 toolkit. Then just install whatever rom you like.
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Why do all that when you can flash the latest through ODIN; and get the correct partition tables setup, and that has root, and then install the recovery via an app? Seems more logical to me.

mt3g said:
Why do all that when you can flash the latest through ODIN; and get the correct partition tables setup, and that has root, and then install the recovery via an app? Seems more logical to me.
Click to expand...
Click to collapse
I was not aware you can install the recovery through an app. I'm not familiar with the process so maybe you can talk the op through it.
When I had my problem with the cwm recovery not sticking from Odin, it was when the jelly bean update was just release for T-Mobile. Just letting the op know that I had the same problem and how I got it working.
Sent from my SGH-T889 using Tapatalk 2

Okay I thought I was missing something. Ya the new update surprised me as well last night with ODIN not working to flash a recovery. It's available in CWM app ROM manager I prefer TWRP though which is available in GooManager via menu>Install OpenRecoveryScript>yes> so long as it says "2.4.1.0" and "D2TMO" then yes and boot recovery to install from there.

I followed mt3g's advice and did the root66 method and then installed via ROM Manager and I had success. Flashing a new ROM now. Thanks!

Cool bro.

[Q] stock/no root phone won't boot, only DL mode works

Hello,
My unrooted At&T galaxy s3 will not go past the Samsung Galaxy SIII splash screen. When I enter recovery it just gives me a dead android guy.
I had this problem before and to fix it, I used odin to flash the stock 4.0.4, then I flashed 4.1.1 (I think these are the correct versions, I followed instructions here), then my phone wouldn't OTA update to touchwiz 4.3 so I flashed it using recovery mode using instructions and files I found here. The phone worked fine for a few weeks after that, but then started to reboot randomly and delete apps. Eventually it just stopped working all together which is where I am now.
I tried to install TWRP using odin which odin says worked but when I try to go to recovery mode I still just see the dead android guy. The phone did not have USB debugging mode turned on so I am not sure if I could install a custom recovery at all.
I tried the CF-auto root that I found here which got partway through and then failed.
Do you guys have any suggestions? Is there a stock touchwiz 4.3 rom that I could flash using odin??
Thank you very much, please let me know if you require any more information, I really want to get my phone working again.

korarchaeota said:
Hello,
My unrooted At&T galaxy s3 will not go past the Samsung Galaxy SIII splash screen. When I enter recovery it just gives me a dead android guy.
I had this problem before and to fix it, I used odin to flash the stock 4.0.4, then I flashed 4.1.1 (I think these are the correct versions, I followed instructions here), then my phone wouldn't OTA update to touchwiz 4.3 so I flashed it using recovery mode using instructions and files I found here. The phone worked fine for a few weeks after that, but then started to reboot randomly and delete apps. Eventually it just stopped working all together which is where I am now.
I tried to install TWRP using odin which odin says worked but when I try to go to recovery mode I still just see the dead android guy. The phone did not have USB debugging mode turned on so I am not sure if I could install a custom recovery at all.
I tried the CF-auto root that I found here which got partway through and then failed.
Do you guys have any suggestions? Is there a stock touchwiz 4.3 rom that I could flash using odin??
Thank you very much, please let me know if you require any more information, I really want to get my phone working again.
Click to expand...
Click to collapse
It almost sounds like you're dealing with a situation I'm having on my galaxy tab. It has the internal SD chip going bad. I had to use a rom specially made to boot from a partitioned external sd card. Sorry, I can't help more, but the symptoms seem similar.
Sent from my SCH-I800 using Tapatalk

Thank you for your reply. Where did you obtain a rom that could boot from the external sd card?
wrenhal said:
It almost sounds like you're dealing with a situation I'm having on my galaxy tab. It has the internal SD chip going bad. I had to use a rom specially made to boot from a partitioned external sd card. Sorry, I can't help more, but the symptoms seem similar.
Sent from my SCH-I800 using Tapatalk
Click to expand...
Click to collapse

Try flashing the TWRP again with Odin, but make sure the auto reboot option on the left is unchecked in Odin. After flashing, unplug the phone and then hold volume up + menu + power buttons at the same time until it reboots.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

shortydoggg said:
Try flashing the TWRP again with Odin, but make sure the auto reboot option on the left is unchecked in Odin. After flashing, unplug the phone and then hold volume up + menu + power buttons at the same time until it reboots.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just tried it with only F. Reset Time checked, it installs it and says a green Pass!. I then unplugged it, tried to hold volume up + menu + power buttons for a while but nothing happened. I pulled the battery and then did volume up + menu + power buttons and went straight back to dead android guy. Any ideas?

Only other thing right now is to make sure you have the latest odin, which is 3.09
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app

shortydoggg said:
Only other thing right now is to make sure you have the latest odin, which is 3.09
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Trying everything with the new version of Odin results in all the same results.
Does anyone know if there is a tar (Odin flashable) version of update43.zip found in this thread?
http://forum.xda-developers.com/showthread.php?t=2387423
Thanks!

korarchaeota said:
Trying everything with the new version of Odin results in all the same results.
Does anyone know if there is a tar (Odin flashable) version of update43.zip found in this thread?
http://forum.xda-developers.com/showthread.php?t=2387423
Thanks!
Click to expand...
Click to collapse
No there's no Odin flash-able there.
Sorry, we don't seem to have any answers for your problem. It seems like it may be more of a hardware issue than software.

Did you phone boot after flashing stock 4.04?

audit13 said:
Did you phone boot after flashing stock 4.04?
Click to expand...
Click to collapse
Yes it did, the first time that this started happening. But I was unable to do that again, I thought since I flashed all the way to 4.3 and I read that once you go to 4.3 you can't go back. Is that correct?
Thank you for your help. I was hoping to try an odin flashable touchwiz 4.3 but I can't seem to find one.

So you had 4.04 on your phone and you used OTA updates to get to 4.3? If this is correct, then you can't flash a stock AT&T 4.3 ROM because it has never been made available to the public; therefore, the only 4.3 ROMs that may work are based on the leaked AT&T 4.3 ROM or compiled from an OTA update.
Once of these ROMs may get your phone going again: http://forum.xda-developers.com/showthread.php?t=2498233

audit13 said:
So you had 4.04 on your phone and you used OTA updates to get to 4.3? If this is correct, then you can't flash a stock AT&T 4.3 ROM because it has never been made available to the public; therefore, the only 4.3 ROMs that may work are based on the leaked AT&T 4.3 ROM or compiled from an OTA update.
Once of these ROMs may get your phone going again: http://forum.xda-developers.com/showthread.php?t=2498233
Click to expand...
Click to collapse
Thank you for your suggestion, all the ones I tried there need recovery to flash...not odin. Is it possibly to make an odin file from a recovery flash file??
Thanks!

korarchaeota said:
Thank you for your suggestion, all the ones I tried there need recovery to flash...not odin. Is it possibly to make an odin file from a recovery flash file??
Thanks!
Click to expand...
Click to collapse
Did you try installing Philz Touch from Odin? As was suggested earlier, don't use auto reboot. Once Philz has been installed and you see Reset in the window, disconnect the USB cable, remove the battery, replace the battery, boot into recovery, wipe and flash a custom ROM. This may help you get your phone working for now.

audit13 said:
Did you try installing Philz Touch from Odin? As was suggested earlier, don't use auto reboot. Once Philz has been installed and you see Reset in the window, disconnect the USB cable, remove the battery, replace the battery, boot into recovery, wipe and flash a custom ROM. This may help you get your phone working for now.
Click to expand...
Click to collapse
Thank you for your suggestion, but I still get the dead android guy after flashing and trying to go into recovery. Any other ideas??

korarchaeota said:
Thank you for your suggestion, but I still get the dead android guy after flashing and trying to go into recovery. Any other ideas??
Click to expand...
Click to collapse
Did you try philz or cwm? I am not sure why stock recovery is not being overwritten.

audit13 said:
Did you try philz or cwm? I am not sure why stock recovery is not being overwritten.
Click to expand...
Click to collapse
I tried twrp and philz, I haven't tried cwm yet, should I? Is it not working because I didn't enable USB debugging before it stopped working?
Thanks for your help!

korarchaeota said:
I tried twrp and philz, I haven't tried cwm yet, should I? Is it not working because I didn't enable USB debugging before it stopped working?
Thanks for your help!
Click to expand...
Click to collapse
Nope, USB debugging will not make a difference.
The latest Philz Touch is based on the latest CWM. After your flash Philz, are you letting the phone auto reboot on its own after flashing in Odin?
I know of no way to convert a custom ROM so it can be flashed in Odin.

[Q] TWRP 2.6.3.1 Asks for password

I woke up this morning to my phone perpetually rebooting.
I was running a nightly of CM 11.
Now when I try to go into Recovery I get a screen that asks for a password. I have no idea what that password is as I did not set one. I tried wiping data to no avail. I tried flashing a new recovery via Odin this did not work (Odin said successful but the screen on the phone never showed the transfer of the file). No matter what wipe method I use in recovery it just says fail, doesn't work at all and hangs or will say it can't mount. I have searched and searched and tried and tried and I'm stuck. I even tried ADB that didn't work either. Please help!

Try flashing Philz Touch (based on CWM) over TWRP via Odin. I have always had good luck with CWM and Philz.
Download the tar version: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att

audit13 said:
Try flashing Philz Touch (based on CWM) over TWRP via Odin. I have always had good luck with CWM and Philz.
Download the tar version: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att
Click to expand...
Click to collapse
I tried this already. I cannot flash ANYTHING via ODIN. Odin states that the process completed but the bar on the phone on the download screen never shows up to show that it has accepted a file.

therecker said:
I tried this already. I cannot flash ANYTHING via ODIN. Odin states that the process completed but the bar on the phone on the download screen never shows up to show that it has accepted a file.
Click to expand...
Click to collapse
Did you unchecked F . reset and unchecked auto reboot when you flashed recovery in Odin? After you flash the file you have to pull the battery then replace it and boot to recovery do not allow the phone to boot to OS or you have to flash again as your recovery will only stick if you pull the battery and boot to recovery after flashing it. After you get into it the first time all will be well with the world again you can flash your heart out.
I had twrp ask me for a password once I hit the back arrow key and told it to mount my external SD card then flashed my rom, bootloader, kernel and modem then rebooted no problem.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

theramsey3 said:
Did you unchecked F . reset and unchecked auto reboot when you flashed recovery in Odin? After you flash the file you have to pull the battery then replace it and boot to recovery do not allow the phone to boot to OS or you have to flash again as your recovery will only stick if you pull the battery and boot to recovery after flashing it. After you get into it the first time all will be well with the world again you can flash your heart out.
I had twrp ask me for a password once I hit the back arrow key and told it to mount my external SD card then flashed my rom, bootloader, kernel and modem then rebooted no problem.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This did not work. When I use ODIN all that is happening is that ODIN says it has succeeded but the little progress bar that usually shows up on the phone when you are in download mode never comes up. I did try this method though and it didn't work.
I restarted the phone in ODIN mode then opened ODIN then connected the USB cable then unchecked the two boxes you mentioned then flashed a new non TWRP recovery then waited for ODIN to say successful then the phone never showed the progress bar so I waited 2 mins until I pulled the battery then I restarted phone directly to recovery and still have the password prompt. Even after hitting cancel I cannot interact with recovery because every option I choose just says fail. I cannot even mount external sd card.

What phone do you have? What was the most recent stock ROM on your phone? Maybe you can flash a stock ROM.

There is a copy of the stock Samsung 3e recovery (which we can't use to flash zips with) I'm curious if maybe it can overwrite what you have going on? On the password screen I wasn't hitting cancel I was simply hitting the back arrow key. I will see if I have a copy of the stock recovery, just maybe you can flash it then flash another recovery after that so you can fix your phone.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

I have Samsung Galaxy S 3 At&T (d2att) SGH-I747 whichever one of those you want. The most recent stock rom on the phone was when I bought it brand new a few months after it came out. I tried installing a stock rom. I tried this using ODIN and it failed. The issue here is that TWRP somehow encrypted the entire file system so NOTHING at all in recovery works. When I use ODIN mode it never shows on my phone that it is accepting a transfer from the computer. When I tried the stock rom via ODIN method it actually failed in ODIN instead of telling me it succeeded and then just not work. It failed at the point when it says Firmware Update Start...aboot.mbn...NAND Write Start!...Complete(Write) operation failed. I am up for any suggestions but I need them to be detailed instructions because I have tried so many things I need to know what exact steps to follow.

I believe the aboot file is a bootloader. Did you ever have a stock 4.3 ROM on the phone? If you did, it probably has the stock 4.3 AT&T bootloader which cannot be downgraded without bricking the phone which means you cannot flash a ROM with an older bootloader via Odin.

audit13 said:
I believe the aboot file is a bootloader. Did you ever have a stock 4.3 ROM on the phone? If you did, it probably has the stock 4.3 AT&T bootloader which cannot be downgraded without bricking the phone which means you cannot flash a ROM with an older bootloader via Odin.
Click to expand...
Click to collapse
To my knowledge I never had a stock 4.3 ROM on the phone. The only stock ROM to touch this phone was the one that came on it. So be specific what are you actually suggesting in this post that I do?

therecker said:
To my knowledge I never had a stock 4.3 ROM on the phone. The only stock ROM to touch this phone was the one that came on it. So be specific what are you actually suggesting in this post that I do?
Click to expand...
Click to collapse
I am surprised that the aboot file was giving you a problem because the bootloader can be downgraded as long as it is not a 4.3 bootloader.
Do you recall exactly which ROM was on the phone when you got it? Where did you get the stock ROM?

audit13 said:
I am surprised that the aboot file was giving you a problem because the bootloader can be downgraded as long as it is not a 4.3 bootloader.
Do you recall exactly which ROM was on the phone when you got it? Where did you get the stock ROM?
Click to expand...
Click to collapse
It was a CM11 Nightly ROM from the very beginning of February. And before that it was a CM10.2 Stable ROM.

Which stock ROM was on your phone before you loaded a custom ROM?

audit13 said:
Which stock ROM was on your phone before you loaded a custom ROM?
Click to expand...
Click to collapse
I have no idea. It was when I first got the phone in November of 2012.

Sounds like your phone may be running a 4.3 bootloader which means your bootloader is locked and cannot be downgraded. This may explain why you are getting errors when trying to flash Odin. There is no stock AT&T 4.3 ROM that can be flashed via Odin.

Help! Sprint Note 4 stuck in boot loop. COG5, rooted. ODIN not seeing phone

Hi everyone,
I'm on COG5, rooted stock ROM. I've been using it fine for weeks and today I had to restart my phone. It just went into a boot loop instead of restarting.
I've restarted into TRWP and did a factory restore, but still boot loop.
I grabbed the COG5 TAR and tried to use ODIN to flash the unrooted version. However, now ODIN won't recognize my phone when I'm in download mode. For some reason it sees the phone when the phone is connected but powered off. Once I try to turn it on in download mode, everything just seems to disconnect. So I can't get it to flash the TAR. I've tried this on ODIN 3.10 and 3.07.
Is there anything else I can try? Am I doing something wrong in ODIN?

Try flashing Beastmode kernel in recovery with a cache and dalvik wipe.
If that doesn't work, Odin once worked on that PC for TWRP, right? Have you verified your Samsung driver? Uninstall and reinstall it?
Have you tried KIES to recover it?
Some PC's setup the driver incorrectly. Mine had the same issue on Windows 8.1 Pro. Read this thread OP and pay particular attention to post 14. It helped my PC see my phone in recovery.
http://forum.xda-developers.com/showpost.php?p=34864154&postcount=14
May actually help KIES to recover your phone.
The boot loop is concerning, did you recently swap a kernel or flash something in recovery like a ROM from an older Android release? Any kernel flashed on OG5 rooted should have the kernel exploit like Beastmode has.
Sent from my SM-N910P using Tapatalk

It is a new PC I'm working on (actually same PC, but upgraded to Win10). So I had to redo all drivers, Kies, Odin download.
But since I was still able to boot to TRWP, I just grabbed an OG5 ROM and flashed it. Everything worked, and thank goodness for my Titanium backups I was up and running with almost all my settings and stuff.
Thanks for replying though!
edit: regarding boot loop, I don't think I've needed to reboot in awhile and haven't changed anything recently. The phone needed to reboot after my kids played with it and somehow opened Adaway and in the end Adaway said a reboot was necessary. After said reboot, it was bootloop. I am running several mods in place of Xposed, so who knows if something crossed at some point.

Glad to hear you got your phone back up and running. The reason download mode wouldn't flash the stock OG5 rom onto your phone was because of the kernel currently detected.
For future reference, when using odin to restore your phone with the official OG5 tar, it looks for the stock unrooted kernel. I "think" freeza's stock root permissive "beastmode" kernel will let odin do it's thing but if not then you would need to flash a pure stock OG5 kernel and that would do the trick. I'm not sure but I think somebody made a flashable zip for the stock unrooted OG5 kernel. I may have also... I can't remember. LOL. Anyway if you have this problem again in the future keep this in mind.

tx_dbs_tx said:
Glad to hear you got your phone back up and running. The reason download mode wouldn't flash the stock OG5 rom onto your phone was because of the kernel currently detected.
For future reference, when using odin to restore your phone with the official OG5 tar, it looks for the stock unrooted kernel. I "think" freeza's stock root permissive "beastmode" kernel will let odin do it's thing but if not then you would need to flash a pure stock OG5 kernel and that would do the trick. I'm not sure but I think somebody made a flashable zip for the stock unrooted OG5 kernel. I may have also... I can't remember. LOL. Anyway if you have this problem again in the future keep this in mind.
Click to expand...
Click to collapse
Hey thanks! Your signature looked familiar. I checked and sure enough I'm using your ROM! :good:

sorry im a noob...just wondering....do you need to have root access to install obar? im considering taking the leap.... (sorry again if this is the wrong thread btw....just thought it might be relevant)

AnimaulKing said:
sorry im a noob...just wondering....do you need to have root access to install obar? im considering taking the leap.... (sorry again if this is the wrong thread btw....just thought it might be relevant)
Click to expand...
Click to collapse
If your phone is updated to OG5 or later, all you need to do in order to root and flash OBAR3 ROM is Odin TWRP recovery in download mode with auto reboot option unchecked. Wait for success...0 failed and pull USB and battery and boot to recovery and follow OBAR3 install directions.
https://dl.twrp.me/trltespr/twrp-2.8.7.0-trltespr.img.tar
Sent from my SM-N920P Note 4 via Tapatalk