Before anyone says anything I have searched the forms and have not found anything quite like my situation. My note two was running CM 11 and I flashed back to stock no problem. However once i was running on stock i tried to run an OTA update. That ran fine and after it was stuck at the Samsung Galaxy note 2 screen and would not load. I am only able to get into download mode. I have tried re flashing the rom multiple times with odin. However nothing seems to work. I am still Stuck in the boot loader. I have read some forums that suggested I try re flashing the pit file. But I am not very experienced in dealing with that. Anything helps Thanks.
tayjohns46994 said:
Before anyone says anything I have searched the forms and have not found anything quite like my situation. My note two was running CM 11 and I flashed back to stock no problem. However once i was running on stock i tried to run an OTA update. That ran fine and after it was stuck at the Samsung Galaxy note 2 screen and would not load. I am only able to get into download mode. I have tried re flashing the rom multiple times with odin. However nothing seems to work. I am still Stuck in the boot loader. I have read some forums that suggested I try re flashing the pit file. But I am not very experienced in dealing with that. Anything helps Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2618447
Related
I was trying to flash my phone (AT&T SGS3) back to stock today using this thread
http://forum.xda-developers.com/showthread.php?t=1739426
While I was downloading, I accidentally kicked the usb cable out of the phone.
I immediately pulled the battery and restarted the process.
Odin said it succeeded but when I boot I get stuck on a screen where it just says samsung. Like the first screen you see on boot but it happens a second time after the galaxy s logo and the at&t logo.
I don't know how to fix this. Can someone please help?
Also I was going to try the not rooted stock roms from this thread.
http://forum.xda-developers.com/showthread.php?t=1737848
But the downloads don't seem to be working. Anyone know where I can download the stock roms?
dmobbjr said:
I was trying to flash my phone (AT&T SGS3) back to stock today using this thread
http://forum.xda-developers.com/showthread.php?t=1739426
While I was downloading, I accidentally kicked the usb cable out of the phone.
I immediately pulled the battery and restarted the process.
Odin said it succeeded but when I boot I get stuck on a screen where it just says samsung. Like the first screen you see on boot but it happens a second time after the galaxy s logo and the at&t logo.
I don't know how to fix this. Can someone please help?
Also I was going to try the not rooted stock roms from this thread.
http://forum.xda-developers.com/showthread.php?t=1737848
But the downloads don't seem to be working. Anyone know where I can download the stock roms?
Click to expand...
Click to collapse
'
Maybe try going into recovery mode and do a factory wipe there.
That worked. Thank you, you just saved me in a big way
Glad it worked. Happened to me too. From what I learned when changing ROM types tw-> aosp you need to wipe data.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Device: Samsung Galaxy Note 8.0 WiFi Tablet ((GT-N5110))
-+-+-+-+-+-+-+-
Last night I started to attempt to return my GT-N5110 to the complete Stock ROM and everything however after spending HOURS looking for the Stock ROM files, I decided to try downloading the ROM directly from the Note 8.0 Toolkit. After it finished downloading and I installed it via ODIN like the toolkit asked, I tried to turn my tablet on and now it won't boot past the Samsung logo boot screen.
If someone could please give me the URL of the correct files needed as well as to a walk-through webpage so that I can fix this annoying problem and get my Note 8 up and running again, I'd greatly appreciate it.
Unfortunately I have been unable to find anything that even looks like it could work on my GT-N5110 on here so I have been rather hesitant to try using the stock files for a different model of the Note 8.0 rather than whichever is needed for the WiFi model. I've finally thrown in the towel and am asking someone, ANYONE, for some help.
Thanks guys!
you can get mostly all of stock firmware on sammobile.com
http://www.sammobile.com/firmwares/2/
Update
I downloaded the firmware from that site and followed the instructions that were provided with the firmware download however I'm still stuck at the Samsung boot screen. I tried leaving it alone for a while since I know that after installing a gapps file, the first boot may take a little bit but it stays on the same screen.
There has to be something I'm missing because I've never had this much trouble with any of my devices before. I thought to try an Emergency Firmware Restoration using Kies but my tablet doesnt show as being connected in Kies.
Anyone know what I'm unknowingly doing wrong?
Get into stock recovery and factory reset, should clear up the being stuck at Samsung boot.
CKrzacz said:
Get into stock recovery and factory reset, should clear up the being stuck at Samsung boot.
Click to expand...
Click to collapse
+1
CKrzacz said:
Get into stock recovery and factory reset, should clear up the being stuck at Samsung boot.
Click to expand...
Click to collapse
^^^^^This^^^^^
OR
Check this post out, http://forum.xda-developers.com/showthread.php?t=2289441 if CKrzacz's tip didn't work.
So This is my first time posting on any forum site for help, and i was refereed to XDA by my roommate. so what happened is a few months ago i asked my roommate to root my galaxy s3 SGH-I747, after he rooted it through odin and all seemed well, BUT we never could get the phone to recognize the root and was still unable to access any root functions. so after a few different attempts we gave up. i assumed that my roommate had removed the root (bad call) but never gave it any thought. a few days ago at&t started bugging me with a software update. i just hit ignore and it would pop up again in a few hours and the icon would never go away. so i gave in and started the update. i didnt pay the phone any attention while it "updated" but later that morning i went to turn it back on and it would get to the Samsung screen then the next screen but after that it goes black and vibrates. i showed it to my roommate and he informed me that it was never restored back to official frimware like i had previously assumed. and that it never should have received the update bc it was still on a custom frimware. we tried flashing the stock frimware back on the phone and every time it would fail the nand write. i believe it was updated to 4.4.2 before i received the update from AT&T and we tried many different ways too restore it i even tried the recovery in Kies 3 but all it says is "connecting" then connection failed. so far nothing has worked. i believe that the update contained android 5.0 and maybe that is the reason none of the other ways we tried worked. i have been researching for hours trying to find a similar case but nothing matches, and i cant find a single working solution that doesn't involve possible making it worse. i can access both the recovery and download modes. please any information or help would be greatly appreciated.
Flash a custom recovery such as Philz Touch via Odin, install cm10.2 via your custom recovery. This should get the phone booted so you can determine the bootloader version on your phone. The NAND error is due to the fact that you are trying to downgrade the bootloader in Odin. Don't flash anything with Odin until you determine the bootloader. Doing so could hard brick your phone.
audit13 said:
Flash a custom recovery such as Philz Touch via Odin, install cm10.2 via your custom recovery. This should get the phone booted so you can determine the bootloader version on your phone. The NAND error is due to the fact that you are trying to downgrade the bootloader in Odin. Don't flash anything with Odin until you determine the bootloader. Doing so could hard brick your phone.
Click to expand...
Click to collapse
firstly, thanks for the fast help. i did as you advised and flashed philz touch 6.15.4 which is the latest version from what i understand. that worked flawlessly. the problem now, is with cm10.2 every time ive tried to install it i get an error in /storage/sdcard1/cm-10.2.0-d2att.zip.
im sure im doing everything correctly. any ideas?
Try flashing an older CM11 ROM for the d2lte.
audit13 said:
Try flashing an older CM11 ROM for the d2lte.
Click to expand...
Click to collapse
thanks so much man youve been a big help that worked.
So my issue is pretty similar, see what you guys think. i been trying everything i can think of.
i updated from xtrestolite 2.1 to 2.2 with out wiping. everything worked fine except when i would make calls, the other people could not hear me. so i updated the bootloader and modem again (i had done it before) and the problem persisted. i flashed back to stock and was getting stuck at the s6 edge screen. the only way to get around this was and get my phone to boot was to flash aou kernel. i was still having a similar issue with calling so I download a modem from a diffrent server and all of a sudden, it was working again on stock firmware... AWESOME!
now that i had all that done and my phone working as it should, i reset my phone for the first time and i got the FRP lock, wont boot phone because custom kernel. GREAT
I then flashed stock of6 again, the tar ball, and the 4 piece version. no dice
i then found of8, tried to flash that still no dice.
id love to flash twrp and load a rom on, but FRP is a alsjdflajs.
the phone will flash successfully, but upon reboot, it will go into recovery, run its course, reboot, and get stuck that the galaxy s6 edge screen.
i use the vol and power click during recovery to see what its doing and everything seems to go fine. it will then say failed to mount /data. im hoping flashing this with the pit file will work, but i cannot download the pit file from my work computer (hahah its blocks on 4shard and mega).
anyone have any other advice? i will update if i figure it out.
Regards team,
-Mad
p.s. none of this is xtrestolite's fault, that rom has been nothing but good to me.. my phone has been picky though. after 5.1.1 i had to flash a custom kernel in order for the digitizer to function properly.... any help is appriciated guys.
SO UPDATE!
nothing good, i tried the pit with of6 and of8, no dice. still stuck.
anyone got a s6 edge w a broken screen? you can claim it lost for all i care.
no one?
i guess if anything past flash stock firmware people dont know? was hoping for alittle more insight.
im sure if i could flash a kernel i could get it to turn on, but FRP has be at bay...
no help for you bro...Samsung just needs to release there software fixing for this comunity...I'm looking a for a dev to answer my question in this section about just flashing zip files in twrp instead of using odin or whatever other methods that can avoid all these problems that are all similar...hopefully in next few months it will be addressed
Hey mate, try this...
http://forum.xda-developers.com/showthread.php?p=61531848
Sent from my SM-G925T using Tapatalk 2
holy... fu34%# /S45it.... IT BOOT?!
after flashing every firmware 100000 times...
THANK YOU!
I initially used odin to flash OI1 update, after a rom I was using caused problems and I got bootloop. It changed bootloader value to b:3 and I'm unable to downgrade now so I used smart switch which didn't recognize device so used emergency recovery and still bootloop. I have factory reset and wipe cache multiple times along with adb side load and individual flashes of bootloader, modem, kernel, flashed custom kernel and twrp to access fix permissions and to mount partitions with advanced wipe etc and still wont boot past logo. Also during one fix attempt phone said can't mount system.. Idk I'm not understanding where the problem is .everything says successful but I'm still in bootloop. Please help. I've spent hours everyday for the past week searching & trying different things that seem might help so open to any suggestions.
Well I am truly stumped, I'm not new to flashing phones I've been flashing rooting and repairing androids for 6 years but have never seen this happen. Came across a tmobile t889 note 2 that had Jedi Master on it and it was bootlooping. (not sure which jedi master I think x2) first I tried to boot into recovery, saw the twrp logo then it just rebooted went back to booting jedi. So I tried to reflash twrp through odin... Nothing, same thing. So then I tried to flash cwm, odin said success no errors but goes right back to twrp, tried philz, same thing. Tried the stock 4.1 rom, 4.3 rom basically every stock rom available, each time odin says success and yet each time jedi master and twrp remain. I tried every single version of odin from 1.85-3.12. I just don't know what else to try, I can't find any threds with even a similar problem except one from an s3 and the solution was only return to samsung... Anyone have sny ideas? Note:it's s not a power button issue the phone doesn't turn off when booting jedi master just syayscon the jedi master bootscreen indefinitely.
Just an update my problem remains, but I found the t889 pit that didn't work, tried to uncheck auto reboot and manually reboot that didn't work. Gave up on odin and tried heimdall with both the command line and the user interface, same thing flashed successfully but nothing really flashed. If anyone has ever used the windows program "deep freeze" It seems like as if that's what happened to the phone... No matter what you flash it just reverts back. I even went as far as trying to purposely brick it by flashing an impropper kernel, I know what that would have done but I just had to see, but nope... Didn't brick... Did nothing... Still has twrp still has jedi master still boot loops
If anyone is interested in seeing a visual of the problem I made a video https://www.youtube.com/watch?v=W3zL069w8io
were you able to solve this?
Just went through this
I was changing roms
And this happened.
Odin the latest Twrp for your phone and do all the rules
Flash the exact Rom that was on it before.
That worked on my t889
You'll probably get partition mount problems..wasn't an issue for me....couldn't flash anything but that Rom.
I'm on jedi x2
It probably had a dual boot