Alright, here we go.
I am trying to install a custom ROM on my Galaxy Note 4. I bought it refurbished a year ago and in the past few days it has been pissing me off. The Note lags like crazy and reboots often (Usually in the process of opening an app)
If anyone has a direct fix, awesome. But I tried and gave up. This led me to factory reset, but the issue persisted. I hope its not a hardware issue.
The seller said it was never rooted, but with the issues that the stock recovery has, I have my suspicions.
So now I'm at trying to root the Note. I've already rooted a Galaxy S4, but that was a few years ago.
This is my issue. I have tried many things. I tried to root with CF auto root on Odin, but it is always stuck at recovery.img. It reaches that point and just stops.
I also tried just flashing CWM or TWRP through Odin, but it also stops at recovery.img.
I tried to flash TWRP through adb, but although the device was recognized in "adb Devices" nothing comes up later on when I type "Fastboot Devices".
Any Ideas how to fix these issues or any new solutions? I know this is an old issue, but I love the Note 4.
Sorry for the weird Capitalization,
Samsung SM-N910T
Running Marshmallow 6.0.1
"Never rooted" (Probably previously rooted)
Running Windows 10 PC (With very capable specs)
Installed Samsung USB Drivers
Odin 3.12
Using the original cable
Related
So I tried two ways one was directly from Odin and my watch rebooted into standard recovery and then wiped something then rebooted and I had to activate and pair it all over again, then I tried SkipSoft's method and it just led me around in circles, because of the reboot to recovery flash permanent-recovery zip and not actually in TWRP just in standard recovery again.
Someone help or point me to another method if there is one, I wanna flash Null_ rom and fully unlock this watch.
Once I got custom recovery installed and sticking I could root and everything else on my own.
On firmware version V700XXUAMK7
Did you run the adb command from the little box thingy underneath 'note 2' in the instructions?
The adb cmd line? Don't think tried that yet, but it was rooted beforehand, so I thought I'd be safe it did say it happens if ya aren't rooted, now I'm fighting tooth and nail after custom recovery failed to connect it to my phone again, sadly you'd have thought samsung would've made pairing easier than this crap, I might as well be trying to pair a iWatch to a Samsung that's how full of fail their pairing procedure is. It shouldn't take 30 damn minutes of trying and fails and a few reboots of each device to do this.
That's the one! I think I thought the same as you when I flashed twrp. The install bit of the statement must refer to twrp not root and it should read probably won't install if you don't run this command.
Gear manager is, in my opinion, a POS. From reading it doesn't like being updated. I think that there's some corruption in the data or cache of one of the components that make up gear manager when it updates which can cause problems like connection and massive battery drain. The method I've used before is to use es file explorer to clear the cache and data of all gear component apps (9 on my phone) and delete them, leaving gear manager proper to last. Then reinstall gear manager again. This is a big pain on null because it wipes a lot of stuff of the watch so it's a good idea to have titanium backup on your watch.
Although I'm about ready to give up on this POS and resell it I've never seen something so dammed complicated to pair up and sync I'm still trying and the monkey developed thing is so behind its giving me old pair codes minutes after trying to pair then reporting incorrect pair code, well no duh.
Sent from my SM-N915T using XDA Premium 4 mobile app
Rather wait till the end of the year and get the Rufus Cuff, at least it wouldn't be ruined by Samsung failed coding.
Sent from my SM-N915T using XDA Premium 4 mobile app
Now it seems as though I'm stuck decided to try the latest UK Version of Tizen OS loaded it in Odin 3.09 into the AP Slot pressed started and then damn Odin decided to pop up with a error and close out in Windows, now if I try anything still download mode and reopened Odin 3.07 or 3.09, but it never fully installs I'm in the emergency download kies recovery screen.
Is it possible to install a Odin'ed firmware from here, from what I've learned of the screen/area of recovery, it's the same thing as download mode. I tried the latest Tizen OS again and all it did was sit forever at zImage area of flashing.
Just TWRP installed and to stick, dunno how, but I sideloaded SuperSU since I was already rooted and had KingUser then I tried ADB which didn't appear to work so I tried SkipSoft's custom recovery method and I guess that seemed to work for me, cause now I'm happily on Null_ 23.
I wanted to try and hopefully learn little about rooting. Have been reading forumposts and tutorials for hours before I started.
Then I got this problem that I have been trying to solve for hours. But my conclusion is I need help solving it.
Tested on this phone that just were collecting dust.
Samsung Galaxy S5 Mini (SM-G800F) and I think it was running 4.4.2. (this is all I remember off the top of my head)
Problem / What happend (long version):
Rooted phone. Downloaded SuperSU and Flashify and installed TWRP 3.0.0 (http://forum.xda-developers.com/galaxy-s5-mini/orig-development/recovery-twrp-3-0-0-t3313775). I had no SD-card so I skipped doing a backup. Everything worked fine (for a normal user). Downladed a Root Uninstaller app also Debloater-setup-v3.90.exe (http://forum.xda-developers.com/devdb/project/dl/?id=12623). Did not freeze or uninstall anything before checking in this forum that it was OK. But after a while I could not access my homescreen it just turned up blank but I could still use other functions/apps. Rebooted the phone in order to get it to work but got stuck at the bootscreen. Tried to fix it via TWRP but the program freezes after a while or just reboots the phone back into Samsung bootscreen.
Problem / What happend (short version):
Rooted - got Flashify and SuperSU
TWRP 3.0.0 installed (no backup made)
Debloater-setup-v3.90.exe and some Root Uninstaller app used (searched on this forum before doing any changes)
Homescreen just blank, other functions/apps worked
Rebooted the phone and got stuck at Samsung bootscreen
TWRP access but the program freezes/reboot after short time
I did try "Factory reset". But the screen froze and the phone slowly started to heat up.
Later on I searched about it and it might have something to do with KNOX?
Any solution is fine since I don't have anything thats need to be saved. I can try any working stock/custom ROM (just not sure how to get it into the phone, yet).
Yes I am a novice so the simplest thing might even work.
Have you tried to flash stock ROM for your device using Odin? If it fails you may want to check this:
http://forum.xda-developers.com/galaxy-s5-mini/help/g800f-failed-odin-firmware-upgrade-fail-t3131782
If it doesn't fix your phone you may have a hardware problem.
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
So I have a very odd problem, and I'm fairly experienced with repairing, rooting, and reverting phones to stock which have custom roms, in this case I have a completely stock note 5 which was experiencing a boot loop error at the note 5 model number screen. Going through the motions I normally would, hard reset, nope, safe mode, nope, wipe cache, nope, master reset, nope, so I flash the firmware with a stock rom, which worked, but resulted in the same problem, rebooting at the model number screen just before the samsung logo every few seconds, tried 3 other firmware versions and downloads, also no. Not sure whats up with this thing, but anyone have any ideas? I personally know the user, family, phone wasnt physically damaged or exposed to water. I'm also getting no command just before entering recovery and failed to mount/ preload (no such file or directory) during the master reset. Its been forever sense I've meddled with a note 5 and cannot remember if these are normal, or related to the issue, I dont ever remember seeing these with my own note 5.
I ran into this exact same problem weeks ago on my S7. I tried flashing 7.0 on my 930V and for whatever reason the phone went into the exact same bootloop showing the Samsung logo every few seconds, vibrating, etc. I got back into download mode but wasn't able to fix it. Then went into Recovery and it only said in blue letters in the top left "Recovery rebooting" and kept flashing that message. Lucky for me I was under warranty and sent it to Samsung. They replaced it free of charge. I ended up trading for a Note 5. I kept running into issues with my S7 and network issues so I traded it.
Anyway, I'm like you in the fact I'm pretty comfortable rooting, repairing devices etc. But I still don't know what I did to mess up that S7 in Odin. Just wanted to share that I had a similar situation. Hope you were able to get a new phone or fix your issue.
sinkableelk said:
So I have a very odd problem, and I'm fairly experienced with repairing, rooting, and reverting phones to stock which have custom roms, in this case I have a completely stock note 5 which was experiencing a boot loop error at the note 5 model number screen. Going through the motions I normally would, hard reset, nope, safe mode, nope, wipe cache, nope, master reset, nope, so I flash the firmware with a stock rom, which worked, but resulted in the same problem, rebooting at the model number screen just before the samsung logo every few seconds, tried 3 other firmware versions and downloads, also no. Not sure whats up with this thing, but anyone have any ideas? I personally know the user, family, phone wasnt physically damaged or exposed to water. I'm also getting no command just before entering recovery and failed to mount/ preload (no such file or directory) during the master reset. Its been forever sense I've meddled with a note 5 and cannot remember if these are normal, or related to the issue, I dont ever remember seeing these with my own note 5.
Click to expand...
Click to collapse
My suggestion is this..
Download the latest version of TWRP
Boot to Download Mode
Odin flash TWRP
Boot to TWRP Recovery
Full wipe including internal storage x 2
Format DATA x 2
Odin flash the latest firmware for your device
(All 4 - BLUE, AP, CP, CSC)
OR
Use Smart Switch Emergency Recovery to restore the firmware.
Hope this helps. Good luck and happy flashing! Let's us know what happens.
Sent from my Samsung SM-G955U using XDA Labs
Ive been lurking on this forum for a while but ive finally hit a wall I cant find an answer to
I successfully rooted my tablet using magisk and TWRP about 4 months ago, everything was going great. about 2 months ago my tablet booted up into TWRP and would not get out, no matter what I tried. eventually I fixed it by wiping everything and reflashing stock ROM from ODIN and going through the root process again, not a big deal. cut to 2 days ago, my tablet restarts and boots into TWRP again and wont boot into system, basically seemed like the same as before, until I plugged it into my computer
For some reason, my tablet no longer connects to ODIN or my laptop at all. Ive used the same cable and different device and same usb port and it worked just fine, ODIN picked up the connection and everything. Ive updated and unistalled and reinstalled drivers for all the USB ports and I dont think that is the issue. I even deleted and reinstalled ODIN but still nothing.
I thought maybe there was some setting on the tablet that might be preventing a connection to ODIN, so I wiped the rooted ROM off the tablet (im new to this, dont know if this was a bad idea) and tried again but got nothing. now with a soft bricked tablet I got a micro SD card, put a TWRP flashable version of the ROM onto it and plugged that into the tablet and flashed this new ROM onto the tablet, and that worked from what I can tell (system folder went from like 8mb to 17000 or something) but I still cannot get the tablet to boot into system.
I can access download mode (there appears to be two versions, one where it just says downloading and another where a bunch of text appears on the top left, some of it mentioning ODIN) and all the functions of TWRP, but ODIN does not connect and I cant get it to boot into the system.
TWRP version 3.1.0.1_ashyx
link to the post where I got the stock lite version of the ROM currently flashed to my tablet:
https://forum.xda-developers.com/tab-s2/development/rom-nougat-stock-lite-v1-t3746583
any help would be greatly appreciated, sorry for the wall of text.
Wish I had something useful to add. I'm having the same issue. TWRP 3.4.0.0 and LineageOS. I've had this issue forever. I flash a clean ROM, it works for a week or two, then I come back to it and all I get is recovery.
I can access Odin however.
Usually it takes wiping and installing a ROM to get the device working again, in fact it issue takes several rounds of that. But of course, in all of that I've lost my setup and some files.
Is there an actual solution to this?
On my T810 I'm having TWRP 3.3.1-0 with this ROM https://forum.xda-developers.com/tab-s2/development/rom-aospextended-rom-v6-7-t3979381
plus Magisk and Pico Gapps.
Of course it's only Pie and not Q, but working well.
3.4.4-0 not tested yet.
Once had an issue with black screen, but at that time I was using case with a screen cover.
Since that I've switched to TPU case only covering the back.
No more issues after that, perhaps it was a problem with FlipFlap like on other devices.