Can someone please provide some help on this issue, I installed TWRP vid Odin, i flashed multiple different Roms but the phone never makes it to the android boot screen, just hangs at Samsung S6 Edge + powered by android boot screen.
I have also tried Clockwork mod recovery as well, Issue is the same, anyone else have this issue and resolve it, Maybe im missing the kernel some how? if so does anyone have one that can be flashed? I tried arter97 kernel, im in clear if it worked because it flashed clockwork mod recovery when i flashed the file.
I really want my phone back and on a nice Rom
UPDATE i got it working.
BIG THANKS TO jovy23!!!!!!! I used the kernel in his post
http://forum.xda-developers.com/tmo...ernel-stock-modified-kernel-touchwiz-t3229557
Sorry for the thread this can be deleted if needed.
Related
I was installing a font with a program named Font Manager on my Galaxy Note II and it told me to reboot, so when I rebooted, it got stuck on the Samsung Logo. I wanted to install the original fonts with ADB but then I saw that the android recovery is opening. I don't know why it doesn't open, I tried all combinations and only volume+ and power button did something(except for volume- and powerbutton that goes to download mode) and I'm pretty sure it has to open the recovery but it doesn't reach the Samsung Logo when I press those buttons, it goes to the Samsung Galaxy Note II GT-N7100 logo and then something weird happens. The logo gets disorted and another logo appears. then it gets restarted.
I am rooted.
I don't want to install a custom ROM, and I don't think I can either, because I can't go to any recovery.
I tried installing CWM and TWRP to reset from there, but, the same problem happens; I can't even reach the samsung logo.
And also, when I pull out the battery it automatically turns on so I have to do everything faaaaaaaaast.
I don't want to download the stock ROM because it's like 1GB and my net is very slow. Right now I'm getting the toolbox so maybe it can do something.
Can I do something like install the default fonts from Odin? PLEASE HELP
Sadra.. said:
I was installing a font with a program named Font Manager on my Galaxy Note II and it told me to reboot, so when I rebooted, it got stuck on the Samsung Logo. I wanted to install the original fonts with ADB but then I saw that the android recovery is opening. I don't know why it doesn't open, I tried all combinations and only volume+ and power button did something(except for volume- and powerbutton that goes to download mode) and I'm pretty sure it has to open the recovery but it doesn't reach the Samsung Logo when I press those buttons, it goes to the Samsung Galaxy Note II GT-N7100 logo and then something weird happens. The logo gets disorted and another logo appears. then it gets restarted.
I am rooted.
I don't want to install a custom ROM, and I don't think I can either, because I can't go to any recovery.
I tried installing CWM and TWRP to reset from there, but, the same problem happens; I can't even reach the samsung logo.
And also, when I pull out the battery it automatically turns on so I have to do everything faaaaaaaaast.
I don't want to download the stock ROM because it's like 1GB and my net is very slow. Right now I'm getting the toolbox so maybe it can do something.
Can I do something like install the default fonts from Odin? PLEASE HELP
Click to expand...
Click to collapse
Can anyone help me? I'm in a really bad situation.
Sadra.. said:
Can anyone help me? I'm in a really bad situation.
Click to expand...
Click to collapse
Please use PC ODIN and flash it with the so called original Rom where it can be downloaded here.
HTML:
http://www.sammobile.com/firmwares
as well as pc odin download link
HTML:
http://forum.xda-developers.com/showthread.php?t=1703998
Sadra.. said:
Can anyone help me? I'm in a really bad situation.
Click to expand...
Click to collapse
Only available option is download stock ROM and flash it and once done you will have to then ROOT and get custom ROM,
Even the tool kit wont be of any help in this situation.
I am getting the Stock ROM now, but, why doesn't recovery work on my phone?
Sadra.. said:
I am getting the Stock ROM now, but, why doesn't recovery work on my phone?
Click to expand...
Click to collapse
BUMP
Well the stock rom came corrupted. I am downloading a new one now.
But can anyone tell me what's wrong with my recovery?
Sadra.. said:
BUMP
Well the stock rom came corrupted. I am downloading a new one now.
But can anyone tell me what's wrong with my recovery?
Click to expand...
Click to collapse
This is a common issue most of the times if its in Bootloop you may not be able to get into recovery , Technically even i dont know reason behind this it could be that the stock recovery may be corrupted .
aukhan said:
This is a common issue most of the times if its in Bootloop you may not be able to get into recovery , Technically even i dont know reason behind this it could be that the stock recovery may be corrupted .
Click to expand...
Click to collapse
But not even CWM or TWRP works.
Hello all,
I've got a Tab 3 7.0 T210R stuck on the Samsung logo with pulsing blue background. I've read through several Samsung boot loop help threads as well as the general Loop noob helper but haven't found a fix yet.
For my stuck T210R, What I've done & can do:
Was rooted with a "patched" stock UK ROM from last March [sorry, don't recall which]
Was running fine until after I tried to install from Play the TWRP Manager, I obviously did something bad! like select wrong device maybe
I can get into Philz, TWRP, & use Odin
I don't have a recovery back up [i really don't care about restoring back to anything - just want it to work, clean slate, ya know]
Tried a couple of latest ROM's through Philz and a stock ROM XAC-T210RUEAMK1-20131122134958.zip though ODIN. They seemed to be successful but I still can't get past Samsung logo
I've tried these ROMS that seem to load but ixna on successful boot afterwards:
ODIN: KIES_HOME_T210RUEAMK1_T210RXACAMK1_1304745_REV00_user_low_ship.tar.md5
Philz: Stock.rooted.deodexed.T210R.zip
Philz: TAB3-T210-HASSAN-ROM-V1.0-kitkat-4.4.2-Aroma-Mods-all Languages.zip
Philz: cm-10.1-20131209(1)-UNOFFICIAL-lt02wifiue.mine.zip
What's killing me is that loading new or stock ROM's SEEM to work - no errors or anything obviously indicative that I'll still be boot looping as soon as I restart. I'm quite desperate and thinking I'm truly bricked.
I haven't yet tried using ADB but if I can use ODIN and TWRP or Philz, will ADB do anything better than what I've already done? I haven't tried anything with the kernel as I can't really understand what to do there. I read and read and read the kernel threads but with my experience its really not as straight forward as rooting or flashing a ROM or software, and I could conceivably screw up worse! I'm mildly experienced at following guides to have rooted and ROM loaded a 1st gen Kindle Fire, Samsung SII skyrocket, S4, Tab 2 7.0, Tab 3 7.0.
No replies or interest? Please help
I'm I in the wrong forum? Did I offend someone? Could really use some input, please.
Any one seen this before? If you've any experience LOSING this battle, please speak up and I'll know to just resign to now owning a pretty white Samsung brick.
Boot to customed recovery under wipe choose format this will zero all partitions then redo
thanks!
andynroid said:
Boot to customed recovery under wipe choose format this will zero all partitions then redo
Click to expand...
Click to collapse
if i could find the "thanks" button I'd use it.
I'm traveling now but definitely try your solution. By "redo" I presume you mean load a ROM. When I wipe I also presume I'll still have custom recovery? I should still be able to ODIN, too, if needed?
thanks again
Yes exactly recovery will not go away once you have formatted the partitions you can now flash a new customed ROM or reflash original FW using Odin..Cheers
Hey buddy wanted to know if you ever found a solution for your issue? I am in the same bind you were in. Can you help guide me. I tried installing the same files you did and to no avail. I bought a Tab 3 T210R from eBay that was stuck in boot loop, I am assuming that it isn't rooted as when I would I went into download mode, it said the firmware was official.
Ok so I have a samsung galaxy s3 att and I have been rooted for the past month or so, no issues. Then, I decide to install a custom rom so I get a stable cm11 and attempt to flash it and it says my cwm version is too low so the reboot my phone so I can update it. The phone starts to boot and gets stuck on the att globe logo with the blue light pulsing. I shut off the phone, pull out the battery and try again, still nothing. I start getting scared so I restore the nandroid backup I made right before this custom rom incident and boot it, still gets stuck at the same place. I really need my phone fixed so can someone help me please??
I was talking to @sd_shadow on another forum earlier and was wondering if he could help me?
supy99 said:
Ok so I have a samsung galaxy s3 att and I have been rooted for the past month or so, no issues. Then, I decide to install a custom rom so I get a stable cm11 and attempt to flash it and it says my cwm version is too low so the reboot my phone so I can update it. The phone starts to boot and gets stuck on the att globe logo with the blue light pulsing. I shut off the phone, pull out the battery and try again, still nothing. I start getting scared so I restore the nandroid backup I made right before this custom rom incident and boot it, still gets stuck at the same place. I really need my phone fixed so can someone help me please??
I was talking to @sd_shadow on another forum earlier and was wondering if he could help me?
Click to expand...
Click to collapse
this thread may help
http://forum.xda-developers.com/showthread.php?t=2549068
"all i can really do , is stay out of my own way and let the will of heaven be done"
Don't panic
Grab the latest version of philz touch recovery https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
The zips are made to be flashed from a recovery like cwm. Install it using cwm, reboot into recovery and philz should come up. You should be able to proceed with wiping and installing your custom rom at this point.
If the zip doesn't work out for some reason, you could also use Odin to flash a .tar.md5 from that link to update your recovery.
Try this: http://forum.xda-developers.com/showpost.php?p=60162192&postcount=2
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.
Hey guys,
So I've been trying for days to get a custom Ron installed on N975F.
Right now I'm on completely reflashed stock Rom. With stock recovery et al. No root.
I am able to flash Magisk with Odin. No trouble. And my phone continues as usual without issue.
However, once I install TWRP, no matter where or how I install it, once I restart my phone it will boot past the warnings without issue, then go to the screen that just says "SAMSUNG" and the phone will never actually boot up.
I can still boot into TWRP recovery without issue, but system itself will never boot, it will just sit on the "SAMSUNG" screen forever.
In fact, it seems like as long as TWRP is installed to recovery, my system will never boot with any Rom. It can be fixed by reinstalling stock recovery, or by reflashing stock in it's entirety (which I have now done before I try again).
Has anyone got any ideas why this might be occurring or how I can address it? I saw some threads about 'rollback protection' but it seems like that is for people who are not even able to boot into TWRP, or get stuck on the first "Samsung Note 10+", screen rather than the system booting "SAMSUNG" screen.
KiwiNote+ said:
Hey guys,
So I've been trying for days to get a custom Ron installed on N975F.
Right now I'm on completely reflashed stock Rom. With stock recovery et al. No root.
I am able to flash Magisk with Odin. No trouble. And my phone continues as usual without issue.
However, once I install TWRP, no matter where or how I install it, once I restart my phone it will boot past the warnings without issue, then go to the screen that just says "SAMSUNG" and the phone will never actually boot up.
I can still boot into TWRP recovery without issue, but system itself will never boot, it will just sit on the "SAMSUNG" screen forever.
In fact, it seems like as long as TWRP is installed to recovery, my system will never boot with any Rom. It can be fixed by reinstalling stock recovery, or by reflashing stock in it's entirety (which I have now done before I try again).
Has anyone got any ideas why this might be occurring or how I can address it? I saw some threads about 'rollback protection' but it seems like that is for people who are not even able to boot into TWRP, or get stuck on the first "Samsung Note 10+", screen rather than the system booting "SAMSUNG" screen.
Click to expand...
Click to collapse
i am guessing try ADB commands see this link! https://www.koskila.net/how-to-use-twrp-to-flash-an-android-device-that-refuses-to-boot-to-twrp/
Many N975 users have reported this issue and I have forwarded concerned to ian as well. What I believe is formatting on latest (last few) twrp causing issue.
If you have N975/N976 then, visit xda My rom thread - Download area - you will find a folder "for stock rom & bootlooped device" download instructions and follow it, I have wrote guide with or without flashing my rom
Edit :
here is direct link, you will find all required file
https://www.mediafire.com/#0urfw8g1gx630
This guide is stop solution to root/root with twrp/fix Samsung roll back bootloop everything. And yes you don't needs to patch anything yourself, all files available are ready to use
Hi Dr Ketan,
Thanks for the response.
I actually solved the issue simply by using the version of TWRP and following the install instructions on your basic "How to Root and Install TWRP" for Note 10+ guide.
So I think this is a problem relating to Ian's latest TWRP. TWRP linked from your thread
is working fine (but leads to issue with Camera in GSI/Lineage OS ROMs).
I will have a look at your special guide relating to Samsung logo/rollback stuff and see if it will allow me to install latest TWRP from Ian and bypass these issues! Thank you.
KiwiNote+ said:
Hi Dr Ketan,
Thanks for the response.
I actually solved the issue simply by using the version of TWRP and following the install instructions on your basic "How to Root and Install TWRP" for Note 10+ guide.
So I think this is a problem relating to Ian's latest TWRP. TWRP linked from your thread
is working fine (but leads to issue with Camera in GSI/Lineage OS ROMs).
I will have a look at your special guide relating to Samsung logo/rollback stuff and see if it will allow me to install latest TWRP from Ian and bypass these issues! Thank you.
Click to expand...
Click to collapse
Yes, As I said issue is related to newer TWRP only. If you use old TWRP, camera will not work. My above link guide is for latest base and you can get latest TWRP only (Included package are having latest available TWRP & Kernel)