Database Info

[Q] Stuck at Boot/Starting Apps

Hey folks!
Again a problem with my little phone.
Today I got similar reboots, after about 5 it got stuck at the bootscreen.
Tried to wipe cache+dalvik, booting it up again, but after it prepared all apps it stucks at the "Starting Apps" window..
Also flashed another kernel and recovery. Nothing worked so far..
Any help, because I don't want to wipe data because I made some important photos today and I don't wanna miss then..
Thanks in advance,
RS

RestlessScreams said:
Hey folks!
Again a problem with my little phone.
Today I got similar reboots, after about 5 it got stuck at the bootscreen.
Tried to wipe cache+dalvik, booting it up again, but after it prepared all apps it stucks at the "Starting Apps" window..
Also flashed another kernel and recovery. Nothing worked so far..
Any help, because I don't want to wipe data because I made some important photos today and I don't wanna miss then..
Thanks in advance,
RS
Click to expand...
Click to collapse
First of all you connect your phone to PC and try to copy all the content of /sdcard to your PC. If it doesn't work reboot your phone to fastboot and connect it to your PC with CMD (in fastboot folder) running and enter the command "adb pull /sdcard C:/" without quotes, Also you can replace C:/ to any address where you would like to copy all your SD data.
After that you can flash any ROM to get your device in working condition.
If you have any query do ask or you may end up losing all your data.

forgotter said:
First of all you connect your phone to PC and try to copy all the content of /sdcard to your PC. If it doesn't work reboot your phone to fastboot and connect it to your PC with CMD (in fastboot folder) running and enter the command "adb pull /sdcard C:/" without quotes, Also you can replace C:/ to any address where you would like to copy all your SD data.
After that you can flash any ROM to get your device in working condition.
If you have any query do ask or you may end up losing all your data.
Click to expand...
Click to collapse
Thanks for your tips, but like I said it's stuck in bootloop and I can't access it through pc.
Also adb won't work an yes, I've installed all drivers :b

RestlessScreams said:
Thanks for your tips, but like I said it's stuck in bootloop and I can't access it through pc.
Also adb won't work an yes, I've installed all drivers :b
Click to expand...
Click to collapse
Why don't you try the fastboot method.
Put your phone into Fastboot by pressing volume down+power button. Connect it to your PC, fastboot would recognize it for sure. You then enter the command. You can even use adb from fastboot.

forgotter said:
Why don't you try the fastboot method.
Put your phone into Fastboot by pressing volume down+power button. Connect it to your PC, fastboot would recognize it for sure. You then enter the command. You can even use adb from fastboot.
Click to expand...
Click to collapse
It just says "device not found" when using adb.
with fastboot I can flash things but can't pull or?

RestlessScreams said:
It just says "device not found" when using adb.
with fastboot I can flash things but can't pull or?
Click to expand...
Click to collapse
Is your boot loader unlocked, if not you'll have to unlock it first (but doing so will void your warranty).
Assuming that you have a unlocked device follow the steps below to get all your data. (I myself tried and it worked, so it must work on your device also)
1. Make sure you have installed drivers for your Moto G, if not then do it.
2. Download the adb file to access your phone during fast boot.
3. Download the TWRP recovery 2.7.0.0 by dhacker for falcon (Moto G) on your PC and copy it in the adb folder.
4. Rename the downloaded file to "recovery.img" without quotes.
5. Connect you phone in fastboot mode to your PC and flash the recovery by command "fastboot flash recovery recovery. img" without quotes.
7. On your phone then go to recovery option and press volume up key until phone vibrates. The phone will then go to recovery mode.
8. On your PC, in command prompt(adb) enter command "adb pull /data/media/0/ C:\Moto" without quotes. The process will start and may take hours depending on no's of file and their size.
P.S. I won't be able to answer any more of your question as I won't have data connection any more. I'm sure if you will follow all the steps properly, you will get all your data. If you can't understand anything then just Google it.

Phone doesn't proceed from boot animation!
Guys!
This would be my 1st time here. I've never faced any sort of problem with any of my android devices but this one.
My phone got lost a week back. So, I used "android device manager" to wipe/lock the phone but I think it didn't as the phone was switched off all this while.
So, some gentleman found my phone and returned it to me just today. I put it up for charging. It popped up 0% battery screen and turned on after 10-15min.
As soon as the boot animation(earth/buildings) finished it jumped to a black screen.
It has been on charging for last 3 hours.
So my questions are
1) Can I make back up of the data without turning it on/formatting it?
2) How can I make it to work?
Thanks a lot in advance!

vjsharma89 said:
Guys!
This would be my 1st time here. I've never faced any sort of problem with any of my android devices but this one.
My phone got lost a week back. So, I used "android device manager" to wipe/lock the phone but I think it didn't as the phone was switched off all this while.
So, some gentleman found my phone and returned it to me just today. I put it up for charging. It popped up 0% battery screen and turned on after 10-15min.
As soon as the boot animation(earth/buildings) finished it jumped to a black screen.
It has been on charging for last 3 hours.
So my questions are
1) Can I make back up of the data without turning it on/formatting it?
2) How can I make it to work?
Thanks a lot in advance!
Click to expand...
Click to collapse
@vjsharma89 :I have posted the answer in your thread.
And after you had backuped your data, factory reset your phone from fastboot by choosing factory option and then reboot it. Or should work fine.

delete this pls, wrong thread

Need help transferring files in fastboot mode

So I forgot and did a dirty flash to the final version of Lollipop without wiping data. I should have moved my data over but now I'm stuck with a black screen and a back arrow once I boot up the OS.
I know that in order to fix this, I need to flash again and do a full wipe, however, I need to get my files (pics and music) off the phone. I am unable to put a custom recovery on the phone. When I flash TWRP to the phone, it says it succeeded but then I just get the open android with the red thing on it when I try to go to recovery mode.
I've tried adb pull in fastboot mode, but I am unable to get my computer to recognize my device in fastboot mode through adb (fastboot works of course).
When I've booted up, my lock is on the phone so I cannot use adb to pull files without getting into the OS (which is impossible at this point).
I'm running out of ideas on how to get the files, but I'm sure that someone here must have run into the same issue.
Any assistance would be appreciated.

wangkomi said:
So I forgot and did a dirty flash to the final version of Lollipop without wiping data. I should have moved my data over but now I'm stuck with a black screen and a back arrow once I boot up the OS.
I know that in order to fix this, I need to flash again and do a full wipe, however, I need to get my files (pics and music) off the phone. I am unable to put a custom recovery on the phone. When I flash TWRP to the phone, it says it succeeded but then I just get the open android with the red thing on it when I try to go to recovery mode.
I've tried adb pull in fastboot mode, but I am unable to get my computer to recognize my device in fastboot mode through adb (fastboot works of course).
When I've booted up, my lock is on the phone so I cannot use adb to pull files without getting into the OS (which is impossible at this point).
I'm running out of ideas on how to get the files, but I'm sure that someone here must have run into the same issue.
Any assistance would be appreciated.
Click to expand...
Click to collapse
theres no adb in the bootloader, just fastboot.
i dirty flashed from kitkat(rastakat rom) to lollipop, didnt have any issues at all. what did you dirty flash from? you could just flash the factory img via fastboot, but not flash the userdata.img, which would let you keep your data.

When you're in bootloader and try to flash TWRP (try the latest), make sure you hit reboot bootloader to see if that helps.

I went from the last pre-release to the official release. of lollipop.
I'm going to try twrp again see what I get.
Thanks

wangkomi said:
I went from the last pre-release to the official release. of lollipop.
I'm going to try twrp again see what I get.
Thanks
Click to expand...
Click to collapse
somebody posted a thread today about how to dirty flash from the preview to lollipop. it appears normally you cant.

How to save my media files from a bootlooping OnePlus One?

Hi,
I am totally lost and need help to get my personal data (images, videos most important) back from my bootlooping phone.
I browsed the privacy guard settings and disabled some boot and caller rights for google services and google play (with the intention to prevent it from looking up for updates constantly and drain my battery).
Then it restarted itself as I plugged it in for charge and is bootlopping since.
I have no root, the latest official CM update and a the build in Cyanogen recovery, since it came out of nowhere no usb bugging enabled (I believe).
When I try to enter the phone via ABD sideload from the CM Recovery "pull" my folders it says error:closed. adb backup wont work either.
It tells me: adb: unable to connect for backup: closed
This whole topic is kind a new for me - I never was in that situation and for now all I want is my images and videos back from my phone at least. I will try any method to save them.
I hope some can help me - I don´t know what to do anymore

This should theoretically work.
Flash TWRP by fastboot, then boot into this newly installed TWRP, then connect the device to your PC, as TWRP natively supports MTP, your Internal & External SD (If any) should be visible and you can copy your data over.

Thank you so much for this hint!
I will try that.
So I Just change my recoverer with this method right? This is possible without root and usb debugging?

Joshwin Aranha said:
This should theoretically work.
FlashTWRP] by fastboot, then boot into this newly installed TWRP, then connect the device to your PC, as TWRP natively supports MTP, your Internal & External SD (If any) should be visible and you can copy your data over.
Click to expand...
Click to collapse
It says:
writing recovery
FAILED (remote: Device not unlocked cannot flash or erase)
Is this game over?

Sore6 said:
It says:
writing recovery
FAILED (remote: Device not unlocked cannot flash or erase)
Is this game over?
Click to expand...
Click to collapse
Well no, it means your device has a locked bootloader, and you'll have to unlock it, the problem there is unlocking bootloader formats the device. Not always, but there's a good chance that you might lose your data, still thought give this a try,
fastboot devices (to confirm that your One is detected by the PC)
fastboot oem unlock (to unlock the device)
fastboot flash recovery recovery.img (to flash the recovery)
if this succeeds, disconnect the device and manually boot in to recovery, not to system, this is important because system will overwrite the TWRP with CYNGN recovery, so boot into recovery and try connecting your device to PC, see if MTP works.
PS - sorry for the late reply, i slept the whole sunday
EDIT - Wait, did you say that USB debugging is disabled ? then i think it might not work, give it a shot anyway tho.

Joshwin Aranha said:
Well no, it means your device has a locked bootloader, and you'll have to unlock it, the problem there is unlocking bootloader formats the device. Not always, but there's a good chance that you might lose your data, still thought give this a try,
fastboot devices (to confirm that your One is detected by the PC)
fastboot oem unlock (to unlock the device)
fastboot flash recovery recovery.img (to flash the recovery)
if this succeeds, disconnect the device and manually boot in to recovery, not to system, this is important because system will overwrite the TWRP with CYNGN recovery, so boot into recovery and try connecting your device to PC, see if MTP works.
PS - sorry for the late reply, i slept the whole sunday
EDIT - Wait, did you say that USB debugging is disabled ? then i think it might not work, give it a shot anyway tho.
Click to expand...
Click to collapse
Thanks for your help here - I guess I can´t win here with all my preconditions :/
One last question is:
Is there any method to wipe or flash the phone with a higher chance of keeping data even if little?

Try booting a recovery.img instead of flashing it.
Get the latest TWRP, copy the img file to the fastboot folder, enter fastboot mode and type fastboot boot twrp_file.img. It might work even with a locked bootloader.

Sore6 said:
Thanks for your help here - I guess I can´t win here with all my preconditions :/
One last question is:
Is there any method to wipe or flash the phone with a higher chance of keeping data even if little?
Click to expand...
Click to collapse
I was just about to say to try booting into the recovery, follow @nitrobg's instructions, get the recovery and instead of flashing the recovery, just try booting into it, command is
fastboot boot recovery.img
Hope it helps you, the pain of losing precious data isn't unknown to the best of us
EDIT - What caused the bootloop ? Who knows, maybe we manage to fix that

EDIT - What caused the bootloop ? Who knows, maybe we manage to fix that
Click to expand...
Click to collapse
I disabled some google play and google services from booting via the official cm privacy settings
Reason was to disable the battery drain by play when searching constantly for GOOGLE android updates...
Needed to disable that in cm12 back then and it helped.

nitrobg said:
Try booting a recovery.img instead of flashing it.
Get the latest TWRP, copy the img file to the fastboot folder, enter fastboot mode and type fastboot boot twrp_file.img. It might work even with a locked bootloader.
Click to expand...
Click to collapse
I will try that! Thank you.
I get back here with the result.

nitrobg said:
Try booting a recovery.img instead of flashing it.
Get the latest TWRP, copy the img file to the fastboot folder, enter fastboot mode and type fastboot boot twrp_file.img. It might work even with a locked bootloader.
Click to expand...
Click to collapse
Unfortunately it gives me this in the commandline:
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.430s

That's unfortunate.
Do you have adb access to your phone in the CM recovery? If you do, try removing/renaming com.google.android.gms from both system and data partitions. You might have to play around trying to get root or to remount the partitions but it could work.

nitrobg said:
That's unfortunate.
Do you have adb access to your phone in the CM recovery? If you do, try removing/renaming com.google.android.gms from both system and data partitions. You might have to play around trying to get root or to remount the partitions but it could work.
Click to expand...
Click to collapse
Sadly no - all adb commands end in "error:closed"

Try this:
Power Down the OnePlus One
Hold the Power Button Until Android Starts to Boot Up
As Soon as Android Starts Booting Up, Let Go of the Power Button
Then Immediately Start Holding Both the Volume Up and Volume Down Buttons
Continue Holding Both Volume Buttons Until Android is Fully Booted
If you did everything correctly, Android *should* boot up just fine and show "Safe mode" on the lower left corner of the screen.

nitrobg said:
Try this:
Power Down the OnePlus One
Hold the Power Button Until Android Starts to Boot Up
As Soon as Android Starts Booting Up, Let Go of the Power Button
Then Immediately Start Holding Both the Volume Up and Volume Down Buttons
Continue Holding Both Volume Buttons Until Android is Fully Booted
If you did everything correctly, Android *should* boot up just fine and show "Safe mode" on the lower left corner of the screen.
Click to expand...
Click to collapse
Didnt work because as far as i know one has to be in the android ui - hold pwer off key and then hold the restart menu item and then the volume buttons + power buttons code should work.
Thanks anyway - i wiped it now.
it works but all data is gone

Not really, you hold volume buttons while the OS is booting and it should force a safe mode boot with all apps disabled.
Well, too bad now. It could've worked.

nitrobg said:
Not really, you hold volume buttons while the OS is booting and it should force a safe mode boot with all apps disabled.
Well, too bad now. It could've worked.
Click to expand...
Click to collapse
Honestly - I held it for 4 Minutes. There was a Vibrate Signal everytime it wanted to boot up into android but it didnt. Then it kept the cynogenmod loader til the next little vibration. It was a loop with no entry to android GUI

It's sad that you had to lose your data
Anyway, Take a lesson from this, weekly nandroid backups
(That's what I do)

Joshwin Aranha said:
It's sad that you had to lose your data
Anyway, Take a lesson from this, weekly nandroid backups
(That's what I do)
Click to expand...
Click to collapse
Thanks man - jeah I took care of such case beforehand now and rooted, bought titaniuam backup and enabled usb debugging instantly...
Also I am now using TWRP.
Lesson learned.
Thanks to you all for helping me!
I am really thankful for your effort.
Kind regards

Some kind thanks on my replies maybe ?
Haha, anyway. Take care.

I somehow broke TWRP

I haven't really touched this tablet in a while, but i wanted to start using it again. I was running BlissPop. It was slow, and kept giving me an error when it was trying to update, so I decided to try a different ROM. So I downloaded the lineageOS ROM and tried to flash it.
However, TWRP kept giving me an error when I tried to flash the ROM. I don't remember exactly what the error was.
So, I thought that I needed to update TWRP. I tried through the "Official TWRP" app, but after doing so I was unable to boot into recovery mode at all. I could still get to the bootloader, but when I tried to select recovery mode it would give me an error and dump me back out to the bootloader menu.
I tried installing twrp through "TWRP Manager" app, but it just says "something went wrong"
I tried doing this using ADB. I connected the tablet, enabled USB debugging. If i do the ">adb devices" command, I can see the tablet. Then I did >adb reboot bootloader - which works, it reboots the device into the bootloader. But then I try and flash recovery and nothing happens, it just says <waiting for device>. And if I do > fastboot devices it doesn't list any devices.
If I reboot to the bootloader and select "Recovery Mode' i just get the nvidia boot logo and it stays there forever.
I don't know what else to try at this point.
I think I could get this to work if I could just get fastboot to recognize my device, but I'm not sure what's preventing that from happening.

mattlokk said:
I haven't really touched this tablet in a while, but i wanted to start using it again. I was running BlissPop. It was slow, and kept giving me an error when it was trying to update, so I decided to try a different ROM. So I downloaded the lineageOS ROM and tried to flash it.
However, TWRP kept giving me an error when I tried to flash the ROM. I don't remember exactly what the error was.
So, I thought that I needed to update TWRP. I tried through the "Official TWRP" app, but after doing so I was unable to boot into recovery mode at all. I could still get to the bootloader, but when I tried to select recovery mode it would give me an error and dump me back out to the bootloader menu.
I tried installing twrp through "TWRP Manager" app, but it just says "something went wrong"
I tried doing this using ADB. I connected the tablet, enabled USB debugging. If i do the ">adb devices" command, I can see the tablet. Then I did >adb reboot bootloader - which works, it reboots the device into the bootloader. But then I try and flash recovery and nothing happens, it just says <waiting for device>. And if I do > fastboot devices it doesn't list any devices.
If I reboot to the bootloader and select "Recovery Mode' i just get the nvidia boot logo and it stays there forever.
I don't know what else to try at this point.
I think I could get this to work if I could just get fastboot to recognize my device, but I'm not sure what's preventing that from happening.
Click to expand...
Click to collapse
Did you set:
Allow oem unlock in dev opt.
Fastboot protocol into BL?
Twrp app & manager need root to work.

Just flash the latest stock ROM first, lineageos requires having latest firmware.
I wrote a little guide not long ago about that (obviously, you can skip the F2FS steps if you don't need F2FS and just flash ROM after flashing latest TWRP)
Link

thanks for the help, i'll try and work through this soon.

fpozar said:
Just flash the latest stock ROM first, lineageos requires having latest firmware.
I wrote a little guide not long ago about that (obviously, you can skip the F2FS steps if you don't need F2FS and just flash ROM after flashing latest TWRP)
Link
Click to expand...
Click to collapse
I had seen your thread, and was intending on following it. nice post. 2 quick questions though
1) this is a shield tablet that was supposed to be remotely bricked by nvidia after the warranty claim. Will that happen if I flash the official recovery ROM?
2) how would I even flash that rom if I can't get recovery mode to work in trwp?
I think the root problem that I'm having is that I can't seem to connect to the device via fastboot (i'm sure i used the wrong terminology somehow)
edit: well I downloaded the USB driver for the shield tablet from nvidia, and i was able to install that (rather than the google usb driver). Fastboot finally recognized my device after that. I'm trying to flash the recovery now, but it doesn't seem to be doing anything, just been stuck on this screen for a while now: https://i.imgur.com/BUwj3Hx.png guess I'll continue to wait a while.
edit 2: well, finally got TWRP to flash over fastboot (https://i.imgur.com/tV1DqDv.png) however I still can't enter recovery mode. I just get the nvidia boot logo and then nothing happens. TWRP manager still says i don't have it installed either.
i'm about ready to give up on this... i've spent like 6 hours on this crap already and I feel like I keep getting further away from it.

mattlokk said:
I had seen your thread, and was intending on following it. nice post. 2 quick questions though
1) this is a shield tablet that was supposed to be remotely bricked by nvidia after the warranty claim. Will that happen if I flash the official recovery ROM?
2) how would I even flash that rom if I can't get recovery mode to work in trwp?
I think the root problem that I'm having is that I can't seem to connect to the device via fastboot (i'm sure i used the wrong terminology somehow)
edit: well I downloaded the USB driver for the shield tablet from nvidia, and i was able to install that (rather than the google usb driver). Fastboot finally recognized my device after that. I'm trying to flash the recovery now, but it doesn't seem to be doing anything, just been stuck on this screen for a while now: https://i.imgur.com/BUwj3Hx.png guess I'll continue to wait a while.
edit 2: well, finally got TWRP to flash over fastboot (https://i.imgur.com/tV1DqDv.png) however I still can't enter recovery mode. I just get the nvidia boot logo and then nothing happens. TWRP manager still says i don't have it installed either.
i'm about ready to give up on this... i've spent like 6 hours on this crap already and I feel like I keep getting further away from it.
Click to expand...
Click to collapse
Okay so I'm guessing you have stock ROM.
To flash TWRP you have to enter fastboot mode (vol down + power I believe) and flash the twrp image with fastboot flash recovery twrp.img (rename the shield tablet twrp to just twrp.img and place it into your easy adb and fastboot folder)
And DON'T reboot into OS, rather use your volume buttons to navigate to "restart to recovery" or just use hardware keys again directly from TWRP (vol up + power).
Good luck

fpozar said:
And DON'T reboot into OS, rather use your volume buttons to navigate to "restart to recovery" or just use hardware keys again directly from TWRP (vol up + power).
Good luck
Click to expand...
Click to collapse
Agreed. This is probably what is happening (as described on the TWRP webpage here:
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Alternately, immediately rooting (flash SuperSU or Magisk) right after flashing TWRP, will prevent TWRP from being replaced with stock recovery.
Although the inconsistent fastboot connection, and how much trouble you had flashing TWRP initially, is a bit worrisome. Try using a different cable (maybe the one you are using is not connecting well?) try another USB port on the computer, and don't use a USB hub (connect direct to the PC).

Well, like they say: persistence is key. I kept pushing and trying new things until eventually.... I bricked the device. No, not really, it's working great now on LineageOS.
Thanks again to everyone who helped me out :good:. I'm still not sure exactly what caused TWRP to stop working on my device, however following this guide helped me fix it: https://forum.xda-developers.com/shield-tablet/help/help-stuck-nvidia-boot-screen-t3076462
The "flash-all.bat" restored everything to stock (including the recovery mode) and after that I was able to flash the latest TWRP and install Lineage.

S7 G930T Booting issue (Even after upgrading OS via Odin)

Hello Everyone,
I hope you are doing good, Cant run my S7 G930T mobile.
I have upgraded OS via Odin, it passed but phone is not getting work.
Sometimes it doesn't open recovery boot and gets stuck at Recovery Booting.....
Sometimes it restart from the installing applications screen.
If you have any files for binary 11 (B) or anything i need to do before flashing OS via Odin.
Please help me
I'd be very thankful to you.
Thanks!
[email protected]

sabeel43 said:
Hello Everyone,
I hope you are doing good, Cant run my S7 G930T mobile.
I have upgraded OS via Odin, it passed but phone is not getting work.
Sometimes it doesn't open recovery boot and gets stuck at Recovery Booting.....
Sometimes it restart from the installing applications screen.
If you have any files for binary 11 (B) or anything i need to do before flashing OS via Odin.
Please help me
I'd be very thankful to you.
Thanks!
[email protected]
Click to expand...
Click to collapse
Can you be more specific about your booting issues?
Is the device boot looping? How far through the booting process do you get before failure? and what happens after failure?
Can you get your phone into recovery mode or download mode?

ReboundGuy said:
Can you be more specific about your booting issues?
Is the device boot looping? How far through the booting process do you get before failure? and what happens after failure?
Can you get your phone into recovery mode or download mode?
Click to expand...
Click to collapse
Sometimes it gets ON normally and after some time it reboots itself and then it keeps doing it again and again, and sometimes it gets on and goes straight to the recovery mode, and yes i can get my phone into download mode too.

If you have precious data you want to keep, then you should create a back up of your phone, if you haven't already done so.
If you're unconcerned about data or have created a backup, then you could factory restore from recovery mode.
Alternatively, if you haven't got the latest version of Odin, then you could try downloading the latest Odin software and attempt another flash.
Another thing you could try, is to sideload the update via adb. You will of course need the latest adb software which is easy to find. You can follow this xda guide here (https://www.xda-developers.com/install-adb-windows-macos-linux/), or if you prefer it you could download Android Studio from here (https://developer.android.com/studio).
To sideload the update you will have to:
1. Boot phone into recovery mode. Hold the volume up, home, and power buttons, and then let go of the power button when it power on.​2. When in recovery mode, select the option, "Apply update from ADB."​3. With your phone plugged into the computer, open the cmd/terminal and type "adb devices". The cmd should start up adb and display something like:​List of devices attached​[device id] sideload​4. Navigate to the folder that contains the update file. It needs to be a .zip file.​5. Type in the command, "adb sideload [file name]".​
To make things easy you can set up adb so you can run its commands from any directory, the steps for this are covered at the end of the xda guide I have linked.

ReboundGuy said:
If you have precious data you want to keep, then you should create a back up of your phone, if you haven't already done so.
If you're unconcerned about data or have created a backup, then you could factory restore from recovery mode.
Alternatively, if you haven't got the latest version of Odin, then you could try downloading the latest Odin software and attempt another flash.
Another thing you could try, is to sideload the update via adb. You will of course need the latest adb software which is easy to find. You can follow this xda guide here (https://www.xda-developers.com/install-adb-windows-macos-linux/), or if you prefer it you could download Android Studio from here (https://developer.android.com/studio).
To sideload the update you will have to:
1. Boot phone into recovery mode. Hold the volume up, home, and power buttons, and then let go of the power button when it power on.​2. When in recovery mode, select the option, "Apply update from ADB."​3. With your phone plugged into the computer, open the cmd/terminal and type "adb devices". The cmd should start up adb and display something like:​List of devices attached​[device id] sideload​4. Navigate to the folder that contains the update file. It needs to be a .zip file.​5. Type in the command, "adb sideload [file name]".​
To make things easy you can set up adb so you can run its commands from any directory, the steps for this are covered at the end of the xda guide I have linked.
Click to expand...
Click to collapse
I tried to update from ADB but it said, unauthorized access!
and I also think it is a hardware issue

Can you start in safe mode?

ReboundGuy said:
Can you start in safe mode?
Click to expand...
Click to collapse
Yes if it boots normally and then i can go safe mode too.

Just so you know, I'm running out of ideas. Can you try the other suggestion that I mentioned above?
The one where I suggested flashing through Odin again?
I'm kind of assuming that USB Debugging and OEM Unlock were turned on as well.

ReboundGuy said:
Just so you know, I'm running out of ideas. Can you try the other suggestion that I mentioned above?
The one where I suggested flashing through Odin again?
I'm kind of assuming that USB Debugging and OEM Unlock were turned on as well.
Click to expand...
Click to collapse
now Its not turning on , not even on charging

Ikes! Are you able to try and downgrade to your original stock firmware? Seems like the issues began with trying to update.

where can I download original stock firmware from the internet? Can you provide me the link kindly? Last time I used Frija (desktop app) to download firmware.

Pretty much everyone on xda (including me) uses this website for firmware: https://www.sammobile.com
You have to create a free account but it's worth it for all the firmware they have available.
I believe you already know this, but I'm just going to cover the bases anyway, make sure to download firmware for your specific model G930T.