Develop Bugs

[Q] another is it bricked thread after much research

hi folks, Well first time asking for help. Had jedi 8 installed and all was good. went to bed and plugged in the phone.
and bam! woke up and the phone wont boot. So those of you that are familiar with jedi rom it happens sometimes and
you just wipe data and restore your data backup per instructions. But here is the problem, it seems as though my twrp
mysteriously vanished by itself also! when i hold both buttons down and power i just get a black screen with the samsung
logo. it wont boot so i am stuck. i can get into download mode but odin will not see the phone tried a couple diff versions
and like six usb cords and all ports no go but when stuck on the boot screen then the computer does see it. any ideas itst mo version
by the way thanx

jamesh1979 said:
hi folks, Well first time asking for help. Had jedi 8 installed and all was good. went to bed and plugged in the phone.
and bam! woke up and the phone wont boot. So those of you that are familiar with jedi rom it happens sometimes and
you just wipe data and restore your data backup per instructions. But here is the problem, it seems as though my twrp
mysteriously vanished by itself also! when i hold both buttons down and power i just get a black screen with the samsung
logo. it wont boot so i am stuck. i can get into download mode but odin will not see the phone tried a couple diff versions
and like six usb cords and all ports no go but when stuck on the boot screen then the computer does see it. any ideas itst mo version
by the way thanx
Click to expand...
Click to collapse
odin that ish and start from scratch.
be thankful you can boot tho, S2s have a sticky power button issue that renders the phone useless.

T999 Won't boot/start

Didn't find anything similar on here so I had to post. My T999 no longer boots except for a vibrate when the battery is removed and re-inserted. Occasionally it will get to the CM boot logo and then the screen goes off. If I time the button presses right, I get to the Download screen but before I can hit the Up button to confirm download mode the screen shuts off. This happened all of a sudden yesterday, the last activity being to shut off the Alarm. Tried charging but it will not get past the initial battery icon before the screen goes off. Tried replacing the battery but that didn't help. I also tried to follow the debrick instructions but it didn't help. I was running Vanir AOSP 4.4.4 with no issues until yesterday. The device does not register when connected to the PC using USB and the charger LED does not light up when plugged into charger/PC. My feeling is that something went wrong with the boot but I am unable to get into any usable screen to do anything. I had managed to brick a Samsung Vibrant before but I didn't have to struggle as much to debrick and ODIN back to stock. Any help would be greatly appreciated, I'm now without a phone .

Mine is also acting like that. It wont boot to any rom even stock ones. But i noticed that if i connect my charger it will boot to the homescreen. Sounds like a battery issue right? I also thought that but when i go to recovery, it did not shutdown after leaving it for a couple of minutes. I'm also baffled why it wont boot. I'll try to borrow other battery to test if it still the same.

maelstromm said:
Didn't find anything similar on here so I had to post. My T999 no longer boots except for a vibrate when the battery is removed and re-inserted. Occasionally it will get to the CM boot logo and then the screen goes off. If I time the button presses right, I get to the Download screen but before I can hit the Up button to confirm download mode the screen shuts off. This happened all of a sudden yesterday, the last activity being to shut off the Alarm. Tried charging but it will not get past the initial battery icon before the screen goes off. Tried replacing the battery but that didn't help. I also tried to follow the debrick instructions but it didn't help. I was running Vanir AOSP 4.4.4 with no issues until yesterday. The device does not register when connected to the PC using USB and the charger LED does not light up when plugged into charger/PC. My feeling is that something went wrong with the boot but I am unable to get into any usable screen to do anything. I had managed to brick a Samsung Vibrant before but I didn't have to struggle as much to debrick and ODIN back to stock. Any help would be greatly appreciated, I'm now without a phone .
Click to expand...
Click to collapse
Remove battery snd put back in. Does the device try to turn on by itself? If so you probably have a bad power button.
LarsonJayz said:
Mine is also acting like that. It wont boot to any rom even stock ones. But i noticed that if i connect my charger it will boot to the homescreen. Sounds like a battery issue right? I also thought that but when i go to recovery, it did not shutdown after leaving it for a couple of minutes. I'm also baffled why it wont boot. I'll try to borrow other battery to test if it still the same.
Click to expand...
Click to collapse
Boot download mode and flash stock or root66 firmware with Odin. (You may need to factory reset too)

DocHoliday77 said:
Boot download mode and flash stock or root66 firmware with Odin. (You may need to factory reset too)
Click to expand...
Click to collapse
Done this using root66 but still the same. Now my phone went to worse. It wont get past the S3 logo in the boot screen and just shuts down followed by a vibrate. But if i connect my charger, it will continue and run as normal. My suspect might be a bad battery but the thing is it doesn't auto shutdown when is download mode or in recovery mode. Will try to borrow other battery and update if this fixes the problem.

This is pretty strange. Woke up to my phone with the Galaxy s3 boot logo. And it wouldn't go past it. Tried flashing different backups I had but none of them let me go past the boot logo. Flashed CM10 since my version of TWRP recovery is so old that it can't flash anything higher up, and it goes past the boot logo finally after 2 hours then goes to the cyanogen boot logo but doesn't go past that. I'm going to try with ODIN tonight.
Seems very strange that there are others that had this happen to them to. My phone has never done this before, and it happened randomly.

What does it mean if my phone doesn't boot past the logo with an odin to root66 file?
Edit: Nevermind seems to have worked... for now.
Edit 2: Okay so now it's stuck in an infinite loop where it boots past the logo, shows the android mascot then does an android is upgrading app 1 of 169 then goes back all over again. This is fun! Can anyone help?
Edit 3: Okay so I had to do a factory reset. Got it working now. Starting to get sick of the things I have to do to get updated firmware. Samsung needs to get their crap together!

LarsonJayz said:
Done this using root66 but still the same. Now my phone went to worse. It wont get past the S3 logo in the boot screen and just shuts down followed by a vibrate. But if i connect my charger, it will continue and run as normal. My suspect might be a bad battery but the thing is it doesn't auto shutdown when is download mode or in recovery mode. Will try to borrow other battery and update if this fixes the problem.
Click to expand...
Click to collapse
Hopefully its just the battery.
Download mode may work because of how the battery reports to the os. If its going bad and reporting incorrectly that its low, it may trigger a shutdown. Whereas in download mode the os isn't running so its not reading the battery info the same way. Just a guess.
crazexr7 said:
What does it mean if my phone doesn't boot past the logo with an odin to root66 file?
Edit: Nevermind seems to have worked... for now.
Edit 2: Okay so now it's stuck in an infinite loop where it boots past the logo, shows the android mascot then does an android is upgrading app 1 of 169 then goes back all over again. This is fun! Can anyone help?
Edit 3: Okay so I had to do a factory reset. Got it working now. Starting to get sick of the things I have to do to get updated firmware. Samsung needs to get their crap together!
Click to expand...
Click to collapse
Just for future reference, factory resetting solves about 98% of boot hangs.
Still for both of you, id take this as a sign that you should make sure your backups are up to date. If something is failing you'll be glad you did!

DocHoliday77 said:
Just for future reference, factory resetting solves about 98% of boot hangs.
Still for both of you, id take this as a sign that you should make sure your backups are up to date. If something is failing you'll be glad you did!
Click to expand...
Click to collapse
Yeah factory reset unfortunately didn't work for me when I needed it before I had to ODIN to root66. But I was able to do a nandroid after I couldn't get it to boot and extract my sms from Titanium backup. What an awesome app, super thankful to that dev for making it.

DocHoliday77 said:
Hopefully its just the battery.
Download mode may work because of how the battery reports to the os. If its going bad and reporting incorrectly that its low, it may trigger a shutdown. Whereas in download mode the os isn't running so its not reading the battery info the same way. Just a guess.
Click to expand...
Click to collapse
Turns out it was the battery sir. I've tested it with another battery from 2 different phones and it worked fine. While the phone i tested with the defective battery didn't event get passed the samsung logo. I've suspected it might be having the low voltage causing the phone to shut down.
Anyways, after that i bought a new battery immediately and everything seems ok. thanks for the reply doc.

DocHoliday77 said:
Remove battery snd put back in. Does the device try to turn on by itself? If so you probably have a bad power button.
Click to expand...
Click to collapse
I can confirm that it is likely a bad power button, I have tried everything including dismantling it and seeing if I could dislodge any dirt that may be causing the problem but it didn't work. Looks like I have to find a local repair shop or ebay to get it resolved. Anyone recommend a good place to get this fixed. Funds are limited

Im not sure exactly how difficult the repair is most people seem so do it themselves and have given indications that its pretty easy. You can find the part online for a few bucks.

Stuck in a reboot loop

It's in a loop of starting up, loading to the home screen and then shutting down a few seconds later. While booting, in red text, the words "Kernel is not seandroid enforcing" is in the upper left corner. I tried to root it and it didn't work. I've tried a factory reset and still nothing. Now it takes me to the setup screen, yet still looping. I don't know what else to do and I need help. I've later found out that the text is normal, but since it's appeared, it is in constant rebooting.
Currently, I have a G928T firmware downloading from Sammobile which I hope I can use Odin to recover my phone. That's still got an hour left and I don't know if it will even work.
If there's anything else I can do, please say so, and if the firmware downloading is the only option, could you describe the process? I'd prefer that I not mess that up somehow.
After posting this (in the correct forum this time), I've calmed down enough to realize that there is another thread about this incident. I'll try the solution posted there for now.
That solution worked. I guess there's really not much need for this thread anymore, but if someone else were to have the same issue and find this thread, click here to go to the thread that fixed it.

As I read through your post I was getting ready to go and retrieve the copies of the files that I have and post them for you but I see that you've corrected your issues one thing I'd like to say to everyone if you do get into a situation where the phone is stuck since we don't have the battery pool anymore if you press the volume up/down home and power button the phone will briefly restart and then you can decide if you want to go into download mode from there or recovery or just let it try to boot up. Put that helps glad you got your issue fixed brother

Note 2 boot load loop fix - cause System Memory full

Hi everyone. This is the first time ive posted anything on here. I will try to fully describe my problem that i really need help to fix.
My wife got my old Note 2 is rooted and she got my
Dad's old unrooted Note 2. After deciding that she didnt want a rooted phone she decided to use my father's unrooted phone. Due to apps updating and the internal memory getting full she ingored the warning message not really realising the outcome. The phone eventually shut itself down and is stuck on the Samsung logo (boot loop). So i gave her my old rooted phone back because she said that it just died. The same happened to the rooted phone too.
I asked before what she did and i was told nothing it just died. So i had nothing to go on. It wasn't until a week later when I tried to sort the problem out she said the System Memory was getting full and a message came up warning of this. So now I believe the problem is that the on board memory has got full and the phone seized. Much like what happens to a PC when the main hard drive gets full!
When i attempt to boot the phone up the Samsung logo show and stays on, never booting up. This happens with both phones. When i hold the Home key, Power button and Up volume switch. The phone loads the first Part of the boot up and at the moment it goes to the system screen it goes blank for a split second and back to the start of the boot. No matter how many times i try it fails. So I can't Factory reset or erase anything because i can get to it that screen.
So I try something else. I press the Home button, Power button and the Down on the volume to access the Download mode. This works fine. So i used Odin to try to put Rom onto the phone hoping this will solve the problem. Both phones connects to Odin alright and I can set up ready to load a rom onto it, however when i press start on Odmin to do its job everthing starts ok but then it goes red with a Failed error message. This happens when i try this on both phones, I seem to be stuck no knowing what to do. I have tried using all the ports on my laptop (window 7) and that makes no difference. The same happens on both devices.
I think i need to clear the memory somehow but have no idea how to do it when i can only access Download mode. I would be very grateful for any help on this but if all else fail I will try to build up static on a ballon and see if putting the near will wipe the memory, lol. Only joking. Im desperate to sort this out.
Any ideas?

try to flash twrp with Odin and download mode. Then enter recovery, connect it to PC and make some space.
But I really doubt it, apps won't install even when you have 500Mb free, so I think it might be hardware problem

Razer phone stuck on boot screen after attempted root

I followed this guide:https://forum.xda-developers.com/razer-phone/how-to/twrp-magisk-fullproof-guide-razers-wifi-t3756137 to root my razer phone. This was the first time I tried, so I used the steps all the way at the bottom. After rebooting around step 7, it has stayed on the logo for around 3 hours now. It's not detected by ADB, so I cant flash anything or reboot it, and the buttons are not responding. I've tried holding the power button with volume down, and other combinations but it just doesn't work. I'm wondering, is there any solution for this? Or do I just need to wait for the battery to die? Thanks in advance for any responses.

Hi
to get to another mode you need to have the phone connected to a PC or Mac, so plug it into the usb and power off, once it is off hold volume down, this should make it go into download mode from there follow this link ( https://forum.xda-developers.com/razer-phone/help/razer-phone-os-t3772424 ) and you should get back to stock and you can retry to root from scratch or leave your phone as stock
Hope this helps

adroit14 said:
I followed this guide:https://forum.xda-developers.com/razer-phone/how-to/twrp-magisk-fullproof-guide-razers-wifi-t3756137 to root my razer phone. This was the first time I tried, so I used the steps all the way at the bottom. After rebooting around step 7, it has stayed on the logo for around 3 hours now. It's not detected by ADB, so I cant flash anything or reboot it, and the buttons are not responding. I've tried holding the power button with volume down, and other combinations but it just doesn't work. I'm wondering, is there any solution for this? Or do I just need to wait for the battery to die? Thanks in advance for any responses.
Click to expand...
Click to collapse
If you got it to download mode but cannot communicate with the phone check your fastboot and drivers. You need Google USB drivers and the absolute latest fastboot. There are other posts here that can help you find the right stuff

adroit14 said:
I followed this guide:https://forum.xda-developers.com/razer-phone/how-to/twrp-magisk-fullproof-guide-razers-wifi-t3756137 to root my razer phone. This was the first time I tried, so I used the steps all the way at the bottom. After rebooting around step 7, it has stayed on the logo for around 3 hours now. It's not detected by ADB, so I cant flash anything or reboot it, and the buttons are not responding. I've tried holding the power button with volume down, and other combinations but it just doesn't work. I'm wondering, is there any solution for this? Or do I just need to wait for the battery to die? Thanks in advance for any responses.
Click to expand...
Click to collapse
I assume your phone looks just like mine at the moment.
Happened to mine after running the ODP flash_all.
What's odd is I had run it multiple times because trying the different GSIs and going back to nougat once.
The last time I ran it, it resulted in this.
I've tried multiple computers and cables to no avail.

incinandseril said:
I assume your phone looks just like mine at the moment.
Happened to mine after running the ODP flash_all.
What's odd is I had run it multiple times because trying the different GSIs and going back to nougat once.
The last time I ran it, it resulted in this.
I've tried multiple computers and cables to no avail.
Click to expand...
Click to collapse
Mine was stuck like that months ago. I let it run the battery dry, charged it full, and followed the instructions from Razer to flash stock files. It worked for me

tabletalker7 said:
Mine was stuck like that months ago. I let it run the battery dry, charged it full, and followed the instructions from Razer to flash stock files. It worked for me
Click to expand...
Click to collapse
That was my next thing.
Seems mine ran out of juice earlier.
It's automatically kicking to that screen once plugged in.
Completely dead, the charging light blinks red for a minute to get it on, then jumps to the logo screen, charging light turns off.
Kind of thinking mine is toast :-/

incinandseril said:
That was my next thing.
Seems mine ran out of juice earlier.
It's automatically kicking to that screen once plugged in.
Completely dead, the charging light blinks red for a minute to get it on, then jumps to the logo screen, charging light turns off.
Kind of thinking mine is toast :-/
Click to expand...
Click to collapse
Hi follow the link from my comment above and give yours a try, don't think yours is toast just think it's in a boot loop cycle
My comment is second one down

incinandseril said:
I assume your phone looks just like mine at the moment.
Happened to mine after running the ODP flash_all.
What's odd is I had run it multiple times because trying the different GSIs and going back to nougat once.
The last time I ran it, it resulted in this.
I've tried multiple computers and cables to no avail.
Click to expand...
Click to collapse
I´ve got this Screenproblem with the Oreo Update with sideload, it flash but then only this Screen, i found my mistake.
My solution was to do an critical unlock for Bootloader, than install 7.1 and than sideload 8.1 OTA, now it works very fine and much smother than before

[EDIT] After letting the battery run dry again last night, plugging my phone back into my laptop booted into download mode, again with the same display as below. Fastboot again recognised the device & after doing some searching, I'd seen another suggestion somewhere else I hadn't yet tried, which was forcing the phone to partition a (to be honest I couldn't even remember which partition I'd left it in from the attempted root)
The command is "fastboot set_active a && fastboot reboot"
I did this as soon as I was able to, rather than leaving it charging (this may be unrelated, but worth considering if you're still stuck)
after this, I got to the Razer logo screen lock (instead of the blank screen lock below), I was then able to follow Razer's instructions - which are linked in one of the comments on the link from the 2nd post here (hope that makes sense)
Now I'm happy to report everything is working, back to factory
I hope this can help someone else [EDIT]
I'm unfortunately in the same position, did you have any luck flashing back to factory?
I also tried following the guide from the 2nd link, these were the steps I took:
(I can confirm my bootloader is unlocked & critical also unlocked)
1. allowed battery to run dry
2. plugged into laptop whilst holding volume -
3. phone now in download mode with battery charge symbol on screen, I left it some time to charge but noticed it got stuck as per the screenshot (for approx. 6 hours)
4. device not recognised by adb, but recognised by fastboot
5. phone not accepting any fastboot commands, when attempting 'flash_all.bat' just hangs on the first line (flash partition:0 gpt_both0.bin), I have to close command line & reopen to try anything else, however whatever I try I get the same result, so basically the only responses I'm getting from fastboot are that it is aware of the device and confirms the bootloader incl. critical is unlocked
My next thought was the perhaps the phone attempted to boot once it reached the picture charge level and therefore locked in the same way it had initially on the razer logo. Should I attempt flashing the factory image immediately once the phone enters download mode, rather than allowing it to continue charging until it's flashed? Any ideas would be greatly appreciated!
Cheers

Been a while since anybody posted, I know... but did anyone who had this problem end up figuring it out? I am in the same situation and am freaking out a little bit, I JUST got this phone...

Just try this and should solve your problems
https://s3.amazonaws.com/cheryl-factory-images/cheryl-p-release-7083-user-full.zip