Database Develop

Galaxy Gear 1 Screen garbled after downgrade from Tizen

I've update my Gear to Tizen then tried to get back to stock state to install null_
I've followed this instructions:
http://forum.xda-developers.com/show....php?t=2776157
Did not work (process completed but unbootable).
Then tried installing TRWP
http://liliputing.com/2013/11/twrp-c...martwatch.html
Not I have it unbootable. ( it's stuck at Samsung logo, like the one from stock V1 android firmware )
When I tried to get into recovery I get a garbled screen like the one attached. Unresponsive device.
Ideas?

For some reason I cannot see the link you provided, it always gives me the 404 error, so is your 2nd link to liliputing.com.
The first link you provide is the correct thread with the correct instructions, I have done it to my gear with good results.
I do recommend that you don't jump the gun between flashing the old android rom and flashing twrp. Make sure you get the old android rom on you watch first, and make sure everything works first, including touch screen. If you don't see the setup wizard after you flashed the old android rom, please try flashing it again. You MUST make sure android is on there first before doing anything else.
Also, please do not use any other rom or twrp for this downgrade. The twrp for the gear is specific for the gear rom, and make sure you only use the files from that thread for the download.
As for your current BIG problem, try holding down the button until you see the screen with these words: " galaxy gear Rebooting", then quickly tap the button 4-5 times, you should see the simple menu with 3 options: reboot, download, and recovery. Then move to download and hold for about 3 seconds, you will then be in download mode and can flash thru odin. You can repeat the above as many times as you want in order to get to the rebooting screen and the 3 option menu screen. Hopefully you will see those screens and able to flash again. Good luck. :good:

bballengphd said:
As for your current BIG problem, try holding down the button until you see the screen with these words: " galaxy gear Rebooting", then quickly tap the button 4-5 times, you should see the simple menu with 3 options: reboot, download, and recovery. Then move to download and hold for about 3 seconds, you will then be in download mode and can flash thru odin. You can repeat the above as many times as you want in order to get to the rebooting screen and the 3 option menu screen. Hopefully you will see those screens and able to flash again. Good luck. :good:
Click to expand...
Click to collapse
That's my BIG problem. No "Galaxy gear Rebooting" like it used to have. Just that gargled screen instead of it.
If I try to turn it on normally ( without the long press ) it will show the samsung logo and play the samsung load music and animation. But then just stays at the [ SAMSUNG ] screen.

You may have already tried this, but when I see the samsung screen during normal boot, I can long press the button and bring the gear to the "galaxy gear rebooting" screen. If that still does not work, maybe your last option is to connect to Kies as the gear is booting and see if Kies will recognize it.

SM-N920W8 stuck on bootloop after flashing stock rom AND wiping data/factoryreset

Hi all, I am really at my wits end.
I have never unlocked, or rooted this phone. I was having random reboots/bootloops constantly on my phone so I decided to reset cache as per many people's instructions.
It seems that evena fter flashing stock roms and wiping the data/cache it remains in bootloop. After flashing with odin, it will say installing updates, go to 32% then will say "erasing", then say installing updates then bootloop.
Does anyone know how to fix this? I believe my DRK is okay, no errors there.
Should I try to root, unlock and install a custom rom? What are these kernels and should I try those too?
Please, if anyone has anything they think might work please, please please help me.
Thanks,
Tom

theodorelinux said:
Hi all, I am really at my wits end.
I have never unlocked, or rooted this phone. I was having random reboots/bootloops constantly on my phone so I decided to reset cache as per many people's instructions.
It seems that evena fter flashing stock roms and wiping the data/cache it remains in bootloop. After flashing with odin, it will say installing updates, go to 32% then will say "erasing", then say installing updates then bootloop.
Does anyone know how to fix this? I believe my DRK is okay, no errors there.
Should I try to root, unlock and install a custom rom? What are these kernels and should I try those too?
Please, if anyone has anything they think might work please, please please help me.
Thanks,
Tom
Click to expand...
Click to collapse
●Flash the latest 6.0.1 marshmallow firmware from sammobile.com for your specific model and country through Odin..After flashing if you face bootloop then i.e. stucked at Samsung logo, then press volume down and power button simultaneously untill screen turns off..Once screen turned off then immediately press volume up+power+home button simultaneously untill you see Samsung galaxy note 5 logo, release buttons..Now you will boot into stock recovery, from there choose wipe data/factory reset option..After wipe complete reboot your phone.Hope this will solve your issue..
Link for stock firmware
https://www.sammobile.com/firmwares/database/SM-N920W8/
* Download latest stock 6.0.1 firmware for model no and country, and assuming that you are familiar with odin flashing*
●IF This method not helps you then here is another one for you:-
1) Download Samsung smart switch for windows and install latest Samsung usb drivers for your phone
2) Now go into download mode by pressing volume down+home+power button simultaneously..From there select continue by pressing volume up button
3) Run smart switch as device administrator on your pc and connect your mobile to pc using original usb provided by Samsung
4) Let pc install your device drivers and let your devices to be connected to smart switch
5) In smartswitch select emergency recovery software update, smartswitch will ask for your device model number and serial number( Which you can find printed below on the back panel of your device)
6) After providing that info to smartswitch, it will locate latest official version available for your device and it will be installed in few time( Don't disconnect or let your phone switched off during process i.e. you should charge your phone atleast 60-70% before starting updating)
* Hope this will help you*

Sprint Note 5 Boot-looping trouble!?

This is my first post and I'm in need of some help that I can't seem to find anywhere when searching the internet. I'm not a developer nor am I close lol I just have tons of fun learning the development process - it's seriously one of my favorite things to do. Anyways I've messed up royally with my Galaxy Note 5 N910P and I'm stumped on what I should do next! So here's the issue: My Note 5 will not stop boot looping!!! I've flashed stock, almost every version that I'm able to and nothing has worked. The last thing I remember doing before it started this b.s is rooting with CF Auto root. I've always used twrp then flashed Supersu and the dm verity and never had issue! But after flashing the CF Auto root I kept getting kernel is not seandroid enforcing and then the dreadful boot loop issue that has been going on for three days now! Is there something i'm missing? or not doing right? Please message me and let me know, and if this is the wrong place to post about this, I dont mind if my post is taken down just at least help with my question some how! Thank you, XDA is my favorite place - you guys are awesome, I don't trust any other source!!!

saywhhaa33 said:
This is my first post and I'm in need of some help that I can't seem to find anywhere when searching the internet. I'm not a developer nor am I close lol I just have tons of fun learning the development process - it's seriously one of my favorite things to do. Anyways I've messed up royally with my Galaxy Note 5 N910P and I'm stumped on what I should do next! So here's the issue: My Note 5 will not stop boot looping!!! I've flashed stock, almost every version that I'm able to and nothing has worked. The last thing I remember doing before it started this b.s is rooting with CF Auto root. I've always used twrp then flashed Supersu and the dm verity and never had issue! But after flashing the CF Auto root I kept getting kernel is not seandroid enforcing and then the dreadful boot loop issue that has been going on for three days now! Is there something i'm missing? or not doing right? Please message me and let me know, and if this is the wrong place to post about this, I dont mind if my post is taken down just at least help with my question some how! Thank you, XDA is my favorite place - you guys are awesome, I don't trust any other source!!!
Click to expand...
Click to collapse
First of all you have entered wrong model no here note 5 model no should be SM-N920xx
1)Have you enabled Oem unlocking from developers option before flashing twrp and cf-autoroot using odin? If not then you done a mistake!!
2) Have you tried to flash latest stock firmware using odin with latest usb drivers installed on you pc and proper odin flashing guide?(Flash latest 6.0.1 for your device with latest usb drivers installed on pc and connect phone to main usb port using original usb cable) After flashing stock rom if your facing bootloop then you can try reset through stock recovery (Press volume down+power button to switch off your phone..When screen shuts off immediately press volume up+power+home key simultaneously untill you see Samsung galaxy note 5 logo, release keys..You are now in stock recovery from there choose wipe data/factory reset..After reset complete reboot your device)
3)If you can boot into twrp recovery normally then flash any custom rom suitable for your device i.e. for sm-n920p..Custom roms are pre-rooted so no need to flash cf-autoroot..Flash custom rom, if you successfully boot up the rom( It's difficult to boot custom rom though if you haven't enabled oem unlocking you will face custom binary is blocked by frp protection),then enable oem unlocking from developers option and try flashing stock rom again
4) Next option for you is download Samsung smart switch for pc, install latest usb drivers on your pc, connect your phone to pc in download mode(Press volume down+power+home button simultaneously),in smartswitch select emergency software recovery, it will ask you imei,model no and serial no which you can find either on box or back panel of your phone,smartswitch will detect latest stock firmware for your device, hit update now,give some time until update complete..Your device will be automatically reboot..If even you face bootlopp, then goto stock recovery(Press volume down+power button to switch off your phone..When screen shuts off immediately press volume up+power+home key simultaneously untill you see Samsung galaxy note 5 logo, release keys..You are now in stock recovery from there choose wipe data/factory reset..After reset complete reboot your device)
**IF SUGGESTION IN SECOND POST HELPS YOU THEN ITS DONE, AVOID NEXT SUGGESTIONS**

Are you sure you can't install cf auto root again to solve it? IF not...
I did a search and got hits for twrp for N910P. Get it loaded, get it wiped and have another shot at success. Next way to get rid of the persistent rooter gone rogue, load up a factory BL + AP. If that doesn't work download another version and try again.

I've enabled OEM unlocking, flashed latest stock AP...BL.. And so on, factory reset in both factory and TWRP. I have also tried flashing CF Auto root again to see if that would fix it also custom ROMs bootloop except for CM13 and Lineage OS- Which is weird because the ROMs are for the SM N920C model and I'm and Sprint model, So I don't understand that. Weird!! Everything recognizes me as SM N920C except when I am in download mode. Also, having no imei or any back ups make its even harder since my computer completely crashed on me because I am unable to use Samsung smart switch due to the wrong model and null imei. So I'm completely stumped with this issue. Not sure if its a corrupted partition or folders not being in the correct folder locations along with wrong permissions, I've literally stressed everything to my knowledge about this and I'm all out of what issues this could be related to

TWRP soft brick?

After months of deliberation I finally decided to root my Note 9. It was the first time I've ever tried rooting and it seems to have gone horribly wrong. To root the phone, I followed the guide in the video titled 'How to Root Galaxy Note 9! [EASIEST METHOD]' on youtube which has an instruction link in the description. As a new user here, the forum doesn't allow me to post links yet, so please just type the title on youtube and it'll come up as the first result.
What I did was:
- unlocking bootloader
- Flash AP file with TWRP version 3.4.0
- Wipe data
- Since I was worried about using a software from an unknown source, I then flashed the official magisk v20.4 instead of the 'N9-S9_root_for_oem_issue_devices_v3' file recommended in the video.
After doing so, the note 9 restarted and showed the error message "Verification Failed, Unable to restart your device. The Integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data.". I allowed the phone to reset.
Following this, the phone restarted and showed exactly the same message of 'verification failed' and no amount of going through the rebooting process resolved the issue. I googled the issue and was advised to flash the phone with Odin by going into download mode. I then tried to go into download mode, but the phone will simply not go into it and tries to restart the normal way. I also tried to connect to my laptop to see if I can flash with odin but the phone was not recognised at all by the computer.
I then tried to reboot using the twrp key combo and this worked. I then decided to try flashing with the 'N9-S9_root_for_oem_issue_devices_v3' file in the tutorial. Yet, this led to the same issue as with the official magisk file.
Looking at some rooting tutorials, I see that some of them recommend flashing CSC, AP, BL and CP instead of just the AP in the tutorial I followed. I then thought that perhaps the issue is I need to install a ROM on the device. I therefore tried to load the lineage 17.1 ROM in the micro SD card and installed it (top left option on twrp 'install') as well as the magisk and disable_dm_verify_forceencrypt zip files.
In hindsight, this was a stupid move from me - I did so I was in full panic mode at that point and desperate for a solution.
After doing so, the phone rebooted and showed a booting animation of a single blue curved line stuck with a circle rolling from right to left on it.
I left it for a while, hoping that it meant the new ROM was booting. 30 min later it was still stuck on the animation!
I then tried to reboot the phone. Pressing power button did nothing. I then tried different combinations and eventually power + volume up + bixby allowed it to restart in TWRP mode.
As of now, the phone is still in TWRP mode. The phone is still not recognised by my laptop and will not enter download mode if I press volume down + bixby when restarting.
I am fully aware that I've screwed up the rooting process and feel awful about it. It was the first time I've ever tried rooting and I really hope it is only a 'soft brick' and that my phone can be saved. I would really appreciate if anyone here could advise what I can do to complete the root process correctly from here?
Many thanks,
Sam

Is there a "download" or "bootloader" option when you press the reboot button in TWRP? My Note9 is on stock, so I'm not 100% certain myself. However if there is, that should take you to Samsung's download screen. This way you can send yourself back to stock if you give up on rooting your device.
BTW, I do recommend following a note9 rooting guide on XDA (it's not too hard to find) over a youtube video, since YouTube videos can often be out of date or a little sketchy.

Bootlooping Stuck in Maintenance Boot Mode can't access TWRP recovery or Download Mode at times

No matter what 9 out of 10 times I can no longer access TWRP recovery and Odin Download mode.
I'm currently on GA Lineage 7.1.2, rooted G900V. I have magisk 20.3 installed.
I've been having to change roms android 7.1-10 constantantly over the past couple years due to instability. Today the rom I was on I could not close the screen manually with power button otherwise the advanced power options would show. It's a bug!
Now all of a sudden after doing a full wipe and installing another rom I went to back it up and got the maintence boot mode rather than TWRP. I have already done factory resets, flashed other roms, re-flashed TWRP and my firmware. All of this several times over!
When I do mange to get TWRP I do wipe everything and restore backups of roms. Sometimes in download mode it wont stay and within a few seconds it bootloops into maintence mode.
I have no idea why this is happening again but now it seems it might be permeanent? Ive seen this maintence boot mode thing before but switching to another rom and or getting rid of bad modules stopped it. But not anymore.
Any ideas what is causing this and what can I do? Is my S5 done for? I guess at this moment I should stay on the buggy rom I was trying to get rid of until I can do regular backups again.

Droid9684 said:
No matter what 9 out of 10 times I can no longer access TWRP recovery and Odin Download mode...
...Today the rom I was on I could not close the screen manually with power button otherwise the advanced power options would show. It's a bug!
Click to expand...
Click to collapse
Well a bad power button could explain all 3 problems.
Or are you saying that even when using the advanced Power menu it will not reboot in Recovery or Download mode?
Droid9684 said:
Now all of a sudden after doing a full wipe and installing another rom I went to back it up and got the maintence boot mode rather than TWRP. I have already done factory resets, flashed other roms, re-flashed TWRP and my firmware. All of this several times over!
Click to expand...
Click to collapse
That never happened on my S5 G900M. I'm curious: could take a photo of it using an other device and post it here please?
Using this XDA site search: site:forum.xda-developers.com/ sm-g900v maintenance mode you can find other G900V users with a similar problem.
One user posted this:
I ONLY
GET "Maintenance Mode Recovery Menu" Which has 3 options
1 Normal Boot
2 Factory Reset
3 Safe mode Boot
But Sadly and STRANGELY I CANNOT GET THEM TO WORK EITHER!!!
Click to expand...
Click to collapse
A troubleshooting step could be to flash the most recent stock Samsung for your G900V which will re-lock the bootloader, test thoroughly to make sure it works properly then unlock the bootloader following one the numerous threads on XDA about it.
FWIW my Galaxy S5 G900M LineageOS 17.1 build 2020-11-29 + Open GApps Pico build 2020-11-05 + Magisk 21.0 + Magisk Manager 8.0.3 + TWRP 3.4.0 recovery is running smoothly without any major bugs.
See [OFFICIAL] LineageOS 17.1 for Galaxy S5 klte + Variants
***

Sorry for late reply I been busy. So the problems are happening again off and on. I'm going to have to switch roms again because mine keeps soft rebooting itself and dropping SIM card at times.
Next time I get maintenance boot screen i'll try to take a picture of it. The thing is from the restart menu I have the option to boot into recovery. When I do it only sometimes goes into TWRP otherwise goes into the maintenance boot mode and I have seconds to make a choice Boot normal, safe mode and factory reset. None of which options work. Within seconds my phone boots itself. I have the same issue in download mode if i'm able to get into it within seconds reboots itself. So it's very hard to do anything with ODIN. I've re-flashed twrp and my firmware a few times but it takes hours sometimes to be able to due to the self rebooting phone. There is also the problem of when I power off the phone in menu options it shuts off then powers itself back on again. I may have a bad power button its been a couple years that I can remember changing it. But it broke to where I couldnt power off my phone. When trying to lock the phone the reset menu pops up sometimes other times it locks phone as it should. It would be a ton of work for me to switch to a stock rom and do all that crap over again. I mean I wasnt having this problem this constant until recently.
I'm staying on 7.1.2 because bluetooth and music are working. I was on 8.1+ bluetooth would always drop and music would stop working in background due to how background foreground processes changed after 7.1.2. Also the camera file location is messed up and not in DCIM it's located in a lineage file. Whenever I take pictures they are auto uploaded into my dropbox. It doesnt work on newer android versions after 8.1. I have the G900V Verizon maybe thats why i'm having all these problems. I know for sure the No sim is one of them on this device.
I dont plan to buy a new phone until next year and it will be a 5G one. It's too early to invest in one at this time since 5G is just slowly rolling out.

@curiousrom here are two photos of the S5 booting into recovery / maintence boot mode.

Droid9684 said:
@curiousrom here are two photos of the S5 booting into recovery / maintence boot mode.
Click to expand...
Click to collapse
Thanks for the photos.
So it seems it's a Bootloader Maintenance Mode, not recovery.
The first splash screen is the bootloader's which is named Aboot in the S5. See the attachments.
You installed a custom bootloader to unlock your S5 G900V & that's probably why it's acting up.
Ask in S5 G900V unlocking threads & includes those photos.
***

curiousrom said:
Thanks for the photos.
So it seems it's a Bootloader Maintenance Mode, not recovery.
The first splash screen is the bootloader's which is named Aboot in the S5. See the attachments.
You installed a custom bootloader to unlock your S5 G900V & that's probably why it's acting up.
Ask in S5 G900V unlocking threads & includes those photos.
***
Click to expand...
Click to collapse
Odd because I really dont have this problem often and yes that was the only way to unlock the bootloader on 6.0.1. Anyhow I ordered a new power button should arrive soon. That might help with it being sensitive it does look a bit pushed in. I noticed it seems to not boot into TWRP if I choose to go to advanced restart menu and choose to boot into recovery. When I manually do it after powering off i'm not having the problem. So maybe it's a bug with all the ROMs out there when choosing recovery from advanced restart menu options.