Develop Bugs

[Q] Flashing Problem?

I looked around but could not find my problem - I sincerely apologize if it has been asked elsewhere.
Yesterday I attempted to install the newest root66 (4.3) on my telus GS3 using odin. Everything seemed to go ok, but the phone was sitting at the samsung logo for a long while (and vibrating every 5 or 10 seconds as well). The phone went through the normal boot process after the flash, including updating the apps, but then rebooted and just sat there. Thinking something was wrong I attempted to flash the root again and had the same problem. After that I used odin to flash the stock image and waited all night and day for it and it was still on the samsung logo. Tonight I went into the stock recovery and cleared the cache and attempted to flash the root66 again. The phone seemed to go through the normal upgrade boot again (after odin said pass) with the android upgrade spinning chest thing and all that.
I can still access download mode and the stock recovery, so I don't think I am in too bad of shape - part of me thinks it is just a matter of patience, which is fine if it is, but if not, I'd like to keep working on it. Any ideas?
In summery - in case that was confusing
1) flashed root66 4.3, odin indicated success, boot after upgrade was similar to what I have seen before
2) Waited for a couple hours
3) tried root66 again, and waited
4) flashed stock, odin indicated success and waited many hours
5) cleared cache, flashed root66, currently waiting again
6) maintain access to stock recovery and download mode
I'd like to not lose everything on the phone if possible, but if I have to so be it.
Any thoughts?

odin to stock 4.3 then root your phone using CF Autoroot by Chainfire... check always the model of ur phone and the file you are downloading if it is for your phone..

Flashing stock with odin just leaves me stuck at the same Samsung screen. Pulsing Samsung and whatnot

jaybeeee said:
Flashing stock with odin just leaves me stuck at the same Samsung screen. Pulsing Samsung and whatnot
Click to expand...
Click to collapse
Reboot into stock recovery and factory reset.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

[Q] Did I brick my SGH T889?

I am flashing this for my cousin. She woke me up out my sleep because she wanted her phone upgraded from 4.1.2 to 4.3 or kitkat. I downloaded a 4.3 ROM and didnt flash it correctly because Wifi nor data was working. It could be because I didnt flash the OTA first and/or didnt install the devil kernel.
Anyways I was walking her through how to restore the backup I made but she went into Download mode and here is when the problems started. i told her to battery pull and to go into recovery. There was already a backup ROM on her SD card, she flashed and it failed. Had her wipe twice and it failed again. Had her wipe again and restore and it failed. After 10 minutes of it failing I had her send me the phone.
I was unable to flash any ROM so i factory reset through recovery and still nothing. I then started flashing through ODIN the latest stock, deoxed stock, the MD4, I even flashed LJ1. Some of the ROMs will fail to flash and if a ROM does flash successfully I get no further than the Galaxy Note 2 screen.
So is this an indication that the phone is bricked or am I missing a step or two to finally get this phone to finally boot all the way up?

Bump
Sent from my SM-N900V using Tapatalk

Most likely the phone is on 4.3 bootloader which is why flashing 4.1.2 ROM via pc odin does not work.
You can either flash 4.1.x stock ROM via mobile odin pro or flash 4.3 stock ROM via pc odin.
Sent from my SGH-T889 using xda app-developers app

ciphercodes said:
Most likely the phone is on 4.3 bootloader which is why flashing 4.1.2 ROM via pc odin does not work.
You can either flash 4.1.x stock ROM via mobile odin pro or flash 4.3 stock ROM via pc odin.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Ok thanks didn't even think of that. I'm going to give that a shot
Sent from my SM-N900V using Tapatalk

Unable to flash stock ROM via PC odin
Hello
I am in almost the same situation as mo2002. I had original ROM that came with my note2 running android 4.3 then decided to try jedi master x2 also 4.3. After trying it out for a while I noticed poor battery performance and when phone was locked I had to press the menu button several times to see the screen. That was getting on my nerves. Yesterday my phone was booting up by itself. It did a couple times then got stuck with the samsung logo. Reboot again and again and the same stuff happened that's when I decided to flash stock rom from samsung.updates/device site using odin3 v3.09 however, I have not been successful. After it checks the md5 OK, it fails on the NAND write. Is it the case that the NAND memory is not unlocked? I am still able to boot into recovery though.
Thanks
G

gferreri said:
Hello
I am in almost the same situation as mo2002. I had original ROM that came with my note2 running android 4.3 then decided to try jedi master x2 also 4.3. After trying it out for a while I noticed poor battery performance and when phone was locked I had to press the menu button several times to see the screen. That was getting on my nerves. Yesterday my phone was booting up by itself. It did a couple times then got stuck with the samsung logo. Reboot again and again and the same stuff happened that's when I decided to flash stock rom from samsung.updates/device site using odin3 v3.09 however, I have not been successful. After it checks the md5 OK, it fails on the NAND write. Is it the case that the NAND memory is not unlocked? I am still able to boot into recovery though.
Thanks
G
Click to expand...
Click to collapse
Mines corrected itself so I can't give the exact instructions but I just kept flashing stock ROMS via odin but I used 3.07 I believe. Idk if that makes a difference but after X amount of attempts I power cycled (after it being stuck at the same galaxy note 3 screen) it booted successfully
Sent from my SM-N900V using Tapatalk

Soft-bricked? Odin passes but still stuck on loadup

AT & T Galaxy Note 2 SGH-13I7
So I'm at a loss on what to do with my phone at this point..
Everything was running great until yesterday, I attempted to root it, the root attempt was unsuccesful but the phone still worked just fine and It even got shut off and turned on a few times after the failed attempt. But one time it froze up after installing an app and after that the phone got stuck on the boot screen.
So this morning I flashed the stock 4.1.2 Rom and it worked again, then I updated the phone on the device itself. OTA is what you would call it I believe. And now I'm back to where I started. The phone gets stuck on the galaxy note 2 loading screen and it wont start.
I cannot enter recovery mode in order to wipe the settings and clear the cache.
I can enter download mode however, and my attempts at flashing the stock firmware PASS on Odin but the phone only gets stuck on the loading screen again afterwards
Does anyone know what I should do?
Your help is greatly appreciated. Thanks a bunch
Is there any way I might be able to enter a recovery mode using an micro SD card?

To which rom you updated? Know that from newest version there is no going back.
Sent from my GT-N7100

note2nooby said:
To which rom you updated? Know that from newest version there is no going back.
Edit : there's a way(maybe) to get to download mode. But not sure if it will work on your phone. There is a thing called jig kick USB. You can build one yourself.
Sent from my GT-N7100
Click to expand...
Click to collapse
Thats probably my problem then. I was running 4.3 and the stock firmware I installed was 4.1.
Is jig kick USB used to get into download mode, if thats the case then I am already able to do that. Just not get into recovery mode.

Yes I noticed later that you can access download mode. So try to flash the rom you updated to but for your carier as your phone is from at&t you should use their rom. I don't have carrier phone so I speak theoretically. But I guess you understand what I mean.
Sent from my GT-N7100

note2nooby said:
Yes I noticed later that you can access download mode. So try to flash the rom you updated to but for your carier as your phone is from at&t you should use their rom. I don't have carrier phone so I speak theoretically. But I guess you understand what I mean.
Sent from my GT-N7100
Click to expand...
Click to collapse
I just got the AT & T ROM from sammobile and flashed it with Odin, it says it passes, but once the phone reboots it just gets stuck on the loading screen again
Thanks for your help by the way

BicyclingSloth said:
I just got the AT & T ROM from sammobile and flashed it with Odin, it says it passes, but once the phone reboots it just gets stuck on the loading screen again
Thanks for your help by the way
Click to expand...
Click to collapse
newest at&t rom is mk6 you will find it in the at&t Dev section an odin one pre rooted is available.
Sent from my GT-N7105 using Tapatalk

cnote74 said:
newest at&t rom is mk6 you will find it in the at&t Dev section an odin one pre rooted is available.
Sent from my GT-N7105 using Tapatalk
Click to expand...
Click to collapse
mine is the same n7105, so how did this go, did it worked?
mine n7105 says passed and once rebooted don't pass n7105 logo, i can only enter download mode,

I'm having the exact same issue, 7100 Sprint. Odin flashes pass but still stuck on SGNII screen, can't flash recovery or ROM. Had 4.1.2 and accepted OTA mistakenly.

I literally just had this problem with my SGH-I317 and fixed it with this:
http://forum.xda-developers.com/showthread.php?t=2589891 go down to where it says "If you are running the official *MK6* firmware"

ive had something similar. had odin pass. no cwm / twrp access only stock recovery and stock downloader mode.
you need to flash a stock rom to get it back, then boot into it. connect pc. (a different usb port sometimes) get ODIN to reboot it into downloader mode. I had major problems getting to that point. but got it from flashing a stock rom. I have also had this old CM10 rom that fix's all partitions etc. i cant remember the name of it now.
a couple of times ive had issues getting into custom recovery. when you hold power +vol up + home key. when u do keep holding power. it loops boot and loops back again. when u release. make sure you hold power for like 1-2 seconds on logo. dont release power button before logo appears. wait a second after it appears. get it every time now.

Try to flash latest TWRP trough ODIN and check if you can boot in to recovery after that.

Need serious help unrooting/fixing my Samsung Galaxy S3 SGH-1747

I have a Samsung Galaxy S3 AT&T and for about a year and a half always wanted to root it but had no idea how. I had an iPhone a while back and used to jailbreak it I became an expert at it. Rooting is not so easy compared at least with the problems I've been experiencing
I started by watching hundreds of root videos and ended up rooting it with Odin and Kit Kat tar file im not sure of the specific file but I'm almost 100% it was my version 4.4.2 that I flashed.
After I did this I downloaded the basics and tried to get TWRP but gooManager wasnt working for some reason.
I tried to flash the Cyanongen 11 onto my phone using the installer for the comp and on google play store and it worked up until the end I got the dead droid symbol for a bit and it finished downloading to show the "ROM may flash stock recover on boot. Fix?" error message and I selected no and "Root Access Possibly Lost Fix?" I also selected no. My phone booted with no custom rom still rooted and most of my apps are unresponsive and close randomly except facebook and youtube.
I decided I wanted to return it to stock rom and try again but when I downloaded the stock tar file and tried to flash it I got this
I'm not sure what to do because I cant return it to stock rom, clockmod recovery has stopped working, and every video I watch about how to fix it is only making it worse.
If you have any idea what I can do or what I'm doing wrong let me know.

Odin failed because you cannot flash older firmware. Your best bet is to reflash recovery via Odin, then if you want stock go to enewman17's stock rom/system dump thread in development and flash the rom and factory reset.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

DocHoliday77 said:
Odin failed because you cannot flash older firmware. Your best bet is to reflash recovery via Odin, then if you want stock go to enewman17's stock rom/system dump thread in development and flash the rom and factory reset.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I tried to flash cwm recovery onto my phone usb debugging selected and now odin doesnt even show that my phones recognized. This is so frustrating.

I suggest installing Philz Touch recovery via Odin and using Philz to flash a custom ROM to at least get your phone up and running.

devito35 said:
I tried to flash cwm recovery onto my phone usb debugging selected and now odin doesnt even show that my phones recognized. This is so frustrating.
Click to expand...
Click to collapse
If Kies is on your computer, remove it. Have you tried reinstalling drivers?
Sent from my SAMSUNG-SGH-I747 using Tapatalk

[Q] Note 4 sprint

Hello crew, I've recently gotten a Note 4 through sprint. I've been rooting devices since the HTC Magic and have had no bricks. I rooted my Note 4 via Odin 1.85. I flashed the latest twrp and It worked great. This morning my phone was frozen and when I pulled the battery, it boot looped. Figured it was a stock kernel issue with xposed installer. I went back into twrp and it refused to mount the system partition. I can't flash a rom, I can't recover from any of the images I created. I went through the unroot process and flashed the stock recovery back with odin. Now it boots but hangs up at the samsung splash screen for a while then loops. Any ideas? Thank you in advance.

Flash twrp again.

Note 4
w7excursion said:
Flash twrp again.
Click to expand...
Click to collapse
Thank you for the fast response. I did. I tried an older version too just in case it was a bug. No luck. When I used Odin to flash the stock recovery and rom back it starts to boot past the black and white Note 4 screen then gets to the samsung splash screen and it just hangs there. I cleared the cache and did a factory reset in the stock recovery.

If its got oel inside your stuck bro

pbedard said:
If its got oel inside your stuck bro
Click to expand...
Click to collapse
OEL? I don't understand why It won't mount the system partition in twrp. I had no initial issues at all. I even flashed a Cyanogenmod nightly. It's still early and wasn't very stable so I went back to a backup I made. worked fine. I was back to rooted stock. Then the next day it froze and here I am.

pbedard said:
If its got oel inside your stuck bro
Click to expand...
Click to collapse
Yep... OE1... Samsung's latest bit of terrorist activity.
Read through the general and help threads... You'll see.
Try notarized rom (search) and then wait for the next official release (5.1.1?) .

jhill110 said:
Yep... OE1... Samsung's latest bit of terrorist activity.
Read through the general and help threads... You'll see.
Try notarized rom (search) and then wait for the next official release (5.1.1?) .
Click to expand...
Click to collapse
Yea bro I'm on of5 now

And any backups to share hmmmm

Ill see what i csn do

tjgr17 said:
OEL? I don't understand why It won't mount the system partition in twrp. I had no initial issues at all. I even flashed a Cyanogenmod nightly. It's still early and wasn't very stable so I went back to a backup I made. worked fine. I was back to rooted stock. Then the next day it froze and here I am.
Click to expand...
Click to collapse
Flash CF Auto Root through Odin and it will put you back on your last rom that booted.

xxSTARBUCKSxx said:
Flash CF Auto Root through Odin and it will put you back on your last rom that booted.
Click to expand...
Click to collapse
Yes, also noticed OP's Odin 1.85 is old.
To OP: CF Auto Root comes bundled with the recommended Odin. I think we're using 3.07 or 3.09 but 3.07 is recommended to uncheck the auto-boot so user can pull USB and battery after flashing custom recovery over OE1 so it sticks.
I also recommend flashing root tar and rebooting as chain fire recommends. "If you don't get to the red Android logo, boot into recovery manually ("adb reboot recovery", or boot while holding Power+VolUp+Home)."
Once booted, see what build you have.
Sent from my SM-N910P using Tapatalk