Note 3 stuck on Samsung logo - Galaxy Note 3 Q&A, Help & Troubleshooting

Is there a way to copy the data from the internal memory. My phone won't start (out of the blue), it's stuck on the Samsung logo. I tried Safe mode, Wipe cache partition but it didn't help.
I know I should have taken some backups but I didn't. Samsung authorized service didn't help me either.
Phone is not rooted and it's running Samsung ROM.

Search question posted multiple times.But if Samsung failed then its a waste .
Personally I would flash custom recovery and custom rom without wipe .
Sent from my SM-N930F using XDA-Developers Legacy app

What I read I need to have USB debugging enabled. I'm not sure whether it is enabled and if not how to proceed.

If you can boot to download mode, flash TWRP custom recovery using odin (pc). After that boot to TWRP and from there you can copy your files to memory card using twrp file manager.

I think I'm able to boot to download mode. I'm little bit worried not to mess anything up (such as delete the internal memory). Is there any step-by-step manual on how to do that? What about that USB debugging?

https://forum.xda-developers.com/showthread.php?t=2494245

Does the installation process wipe internal memory? I don't want to loose photos/videos that I didn't backup.

Flashing twrp should not wipe data.

I succesfully flashed TWRP but note 3 still boots in the "regular" recovery mode. What I read Samsung ROM's replace custom recovery with the stock one. How can I fix it?
Do I need to flash TWRP again?

This worked for me:
Before you flash the recovery, untick the Auto Reboot option in ODIN. Then flash the recovery. After flashing in done, reboot your device directly to recovery mode from download mode by pressing Vol up + Power + Home button together. Now you will see the TWRP recovery is booted in your device. Now you can reboot normally and your TWRP will be installed.

https://forum.xda-developers.com/showthread.php?t=2426426

Related

[Q] TWRP: "custom recovery" not working anymore, TWRP not starting

Hi there,
I wanted to install latest CM10.1 coming from 0526 yesterday on my Defy+.
Did a backup with TWRP first.
Then the flashing failed, so I wanted to recover from backup.
Phone now is stuck at Motorola M not booting anymore.
When I enter bootloader (vol down) and want to enter "custom recover" he just jumps back to the same menu. TWRP is not starting.
Choosing "stock recovery" is possible, but if I choose a CM10.1 zip file it's not accepted.
RSD Lite does not recognize the phone when it's in the bootloader menu or in the stock recover menu.
Help is very much appreciated, what can I do?
Thanks and best regards.
are edianKa
[Idiot mode=on]
Okay, I found out why I couldn't enter flash mode by using Vol+ when starting.
The phone powered already up when I put in the battery, so I always pushed Vol+ too late.
Pressing Vol+ WHILE inserting the battery did the trick, phone went into flash mode and I could re-flash 2.3.6 sbf using RSD lite.
[Idiot mode=off]
Still not sure why TWRP was messed up just by recovering from a TWRP-made backup...
Best regards
Same situation to me.
I opened Terminal Emulator, gained root access
then type below command to get recovery mode
# reboot recovery
Custom recovery not running
I have a similar issue.
I rooted my stock S4 and installed the proper TWRP.
Heres where my situation is a bit different from anything I have seen on the forum threads. All attempts—both hard and soft—to reboot into recovery, all direct the reboot to Odin Mode. Just to clarify I have not flashed any rom custom or stock, the only thing I have flashed has been TWRP and CWM recovery. And I only flashed CWM AFTER the Failings of TWRP.
When I attempt to boot into recovery, it flashes the blue characters then sends me into a Odin Mode loop until I hard-key the "download mode" and select restart to boot the os normally.
my phone works fine other than not being able to flash custom roms, which is a pain in the arse especially with all the s4 Bloatware.
Here's what I have done so far to help myself:
• install CWM recovery
• tried hard-key reboot recovery (power off/ press home/volume up/power)
• soft reboot recovery through both Goo, CWM and ROM Toolbox pro
• removed my sd card and tried reboot recovery
• removed battery and reboot recovery
• emulator reboot recovery
• reboot recovery both with and without usb cable
I looked into flashing stock with Odin but all tutorials i could find were of an older version and I didnt want to guess what I needed to get that to work,
Please let me know if theres anything I can do.
(Verizon) Samsung Galaxy S4 jfltevzw

S4 i9505 stuck at Samsung logo-can't access to recovery boot

Bought an Australian model galaxy S4 off ebay which was stuck at Samsung Logo with a hope I can unbrick it.
I have tried to flash with an official firmware twice. ODIN confirmed flashing Passed. But the phone still could not boot pass Samsung logo with model number.
+ Pressed volume up + Home + power button to enter into recovery mode but the phone still stuck at recovery mode with blue text "recovery booting ". Have tried to take battery out and redo few times. . All I can do is go to download mode to flash official firmware again. However I do not want to mess thing up as I have tried twice without success.
Please help me out if you have any idea how to fix it. I am much appreciate.
I am not sure if it will help or not but you can try flashing TWRP via Odin and then boot into that one (maybe recovery is corrupted as well?)
Clear cache / dalvik cache from TWRP and try booting to system again
magnavn76 said:
Bought an Australian model galaxy S4 off ebay which was stuck at Samsung Logo with a hope I can unbrick it.
I have tried to flash with an official firmware twice. ODIN confirmed flashing Passed. But the phone still could not boot pass Samsung logo with model number.
+ Pressed volume up + Home + power button to enter into recovery mode but the phone still stuck at recovery mode with blue text "recovery booting ". Have tried to take battery out and redo few times. . All I can do is go to download mode to flash official firmware again. However I do not want to mess thing up as I have tried twice without success.
Please help me out if you have any idea how to fix it. I am much appreciate.
Click to expand...
Click to collapse
Good idea of @th3cr0w.
I will add: It's important know what firmware had before you start to flash things. I supose you don't know it. What you can do is:
1. Flash TWRP recovery in DOWNLOAD MODE via ODIN unticking "Auto reboot". Take out the battery when the process finish. Wait 30 sec. and push it in again.
2. Boot in TWRP and wipe all (Wipe -> Advanced Wipe -> Select system, data, cache and dalvik cache).
3. Reboot in DOWNLOAD MODE and now yes, flash the firmware you wish via ODIN normally.
Same happens with my Galaxy s3 while ago, Problem was the EMMC chip was corrupted, And the problem was solved after replacing it from a local shop.
Joku1981 said:
Good idea of @th3cr0w.
I will add: It's important know what firmware had before you start to flash things. I supose you don't know it. What you can do is:
1. Flash TWRP recovery in DOWNLOAD MODE via ODIN unticking "Auto reboot". Take out the battery when the process finish. Wait 30 sec. and push it in again.
2. Boot in TWRP and wipe all (Wipe -> Advanced Wipe -> Select system, data, cache and dalvik cache).
3. Reboot in DOWNLOAD MODE and now yes, flash the firmware you wish via ODIN normally.
Click to expand...
Click to collapse
Thanks for your and TH3cr0w's suggestion. I will try it tonight and let you guys know. Hope I will fix it. A quick question before I do, once I install TWRP it is anyway I can remove it and reinstall official receovery?
I am using this firmware:
PDA I9505XXUGNH6
CSC I9505XSAGNH1
i have tried to install TWRP with this file twrp-2.8.6.0-jfltexx.tar 9.9M. However my phone still stuck and can not boot into recovery. up the top of screen i have following messages:
Recovery booting...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
Have i done anything wrong? Thanks
What you're seeing is normal, but recovery not installing isn't. I know you don't want to try it again, but flash your stock ROM through Odin. Do it this time with the following changes:
Add a PIT file (easily found on the forum).
Make sure "Re-partition" is selected.
The combination of the PIT file and the re-partition function should wipe the S4's internal storage and partition it properly. If there is no physical damage to the internal storage you should then be able to boot into the device. Otherwise you may have no choice but to have this beast repaired.

Trouble flashing TWRP

Hi, everyone.
I have a galaxy s8 SM-G950FD. I have once flashed TWRP and rooted the device successfully.
Then I tried to install a custom ROM but I got bootloop.
After that, I flash official ROM to unbrick my device. But since then, whenever I tried to flash TWRP again I got this 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."
My device is still working fine but I want to try to flash a new ROM (even if I may brick my device forever). I don't know what to do. Can you guys give me some advice ?
Thank you!
It's quite a simple fix I think: You need to make a backup of the Data partition and then do a wipe using TWRP. This happens because TWRP cannot handle Samsung's Encryption; the only way to bypass this problem is by formatting once again.
MikeTheTechSavvy said:
It's quite a simple fix I think: You need to make a backup of the Data partition and then do a wipe using TWRP. This happens because TWRP cannot handle Samsung's Encryption; the only way to bypass this problem is by formatting once again.
Click to expand...
Click to collapse
But I cannot boot into TWRP. How can I do that ?
If you're stuck in the bootloop you should press the force reboot key combination: Power Down + Home + Power. After the device restarts switch the Volume Down key for the Volume Up key right after the screen goes blank. That should get you into TWRP (if it's correctly installed), otherwise directly into the stock recovery.
MikeTheTechSavvy said:
It's quite a simple fix I think: You need to make a backup of the Data partition and then do a wipe using TWRP. This happens because TWRP cannot handle Samsung's Encryption; the only way to bypass this problem is by formatting once again.
Click to expand...
Click to collapse
MikeTheTechSavvy said:
If you're stuck in the bootloop you should press the force reboot key combination: Power Down + Home + Power. After the device restarts switch the Volume Down key for the Volume Up key right after the screen goes blank. That should get you into TWRP (if it's correctly installed), otherwise directly into the stock recovery.
Click to expand...
Click to collapse
I cant flash/get into TWRP. I tried to boot into stock recovery and do a system wipe/factory reset. Then I flash TWRP again but nothing seem to happen. I tried to boot into recovery and it get me to the stock recovery not TWRP.I did unlock OEM, used Odinv3.12, twrp-3.1.1-2-dreamlte.img.tar.
I had the same issue.
After Odin has flashed the Recovery it performs an auto reboot (if checked in Odin). So at this reboot hold Vol up + Home + Power as soon the screen goes of. You need to be quick. Then it should boot into TWRP.
True, Samsung's stock recovery is very persistent lately and if you tick the auto-reboot you have to be very fast in switching to Recovery mode combo.
Otherwise you can choose not to tick auto-reboot, force restart the device after the TWRP flashing was successful and immediately switch to the Recovery combo.
Here you go: two ways of doing this.

*Help* Phone keeps on booting into TWRP and then doesn't respond.

I just flashed TWRP for the first time but it comes up with "Unmodified System Partition" but touchscreen doesn't work for some reason so I cant select anything. I tried removing the battery and rebooting my phone (Galaxy S4 19505) But it just boots back into recovery for TWRP in the "Unmodified System Partition" . Please Help, thanks.
Edit: Should I delete the TWRP disk image from my pc? (My phone also keeps vibrating while turned off). I have also noticed that there is a non physical home back and menue button, did I download the wrong version? I used the TWRP app to download and flash the image.
Hi,
Download the latest image or tar from here: https://dl.twrp.me/jfltexx/ and flash it with either Odin or Heimdall.
Not quite sure about the notice, is it on the screen that asks you if you want to keep the system partition read-only? Then you either need to swipe or click ok.
Normally flashing a recovery should not produce the problems you are describing, did you only flash the recovery?

[SOLVED]"No Command" error in recovery mode after flashing TWRP via ADB

What i did stepwise -
1. Unlocked bootloader of my g5 plus
2. Flashed twrp-3.2.3-1-potter.img via adb
3. Booted to TWRP
4. Wiped to decrypt phone
5*. Booted to system to enable usb debugging, enabled it . Transfered magisk , arrow 9.0 rom , gapps to my internal storage of phone
6. Open bootloader , selected recovery mode and got nothing except error "No Command"
So i cannot flashed anything what i wanted to
What and Where i made the mistake ?
How can i get TWRP back?
Thanks all in advance
Solution
1. Flashed magisk17.1 and lazyflasher
2. Updated magisk manager and got root
3. Installed official TWRP app , granted root and downloaded same TWRP.img from which i decrypted the phone.
4. Flashed twrp fom the official twrp app.
5. No irritating No Command error again
The no command screen is that of the stock recovery (that's a normal screen). From your steps, it seems like you booted to system in step 5 rather than back to recovery. It seems that after flashing TWRP, you may have to boot to recovery to fix TWRP as your recovery (else the stock recovery overwrites TWRP). Afterwards, you should be able to boot as normal with TWRP still present.
Easiest way to recover would be to repeat step 2 and 3. Then reboot to recovery in TWRP and that should retain TWRP. Back up your existing system, then flash the ROM, GApps and magisk as desired.
echo92 said:
The no command screen is that of the stock recovery (that's a normal screen). From your steps, it seems like you booted to system in step 5 rather than back to recovery. It seems that after flashing TWRP, you may have to boot to recovery to fix TWRP as your recovery (else the stock recovery overwrites TWRP). Afterwards, you should be able to boot as normal with TWRP still present.
Easiest way to recover would be to repeat step 2 and 3. Then reboot to recovery in TWRP and that should retain TWRP. Back up your existing system, then flash the ROM, GApps and magisk as desired.
Click to expand...
Click to collapse
Thanks for your answer sir , but it didn't work
What I did again
1.I flashed same twrp from adb
2. Booted to recovery , but this time TWRP didn't asked password and I could see internal storage in twrp but not on my PC
3*.However I took the whole backup of stock nougat and cross check from restore option as there was backup in TWRP folder. I wanted copy that backup to my PC . But PC cannot detect my phone while in recovery
4. So booted to system and my PC detected my phone but there was no backup in TWRP folder.( But around 6gb(backup) of storage was used but I couldn't see it)
5.Again booted to recovery mode but "No Command" showed again .
I tried several times but I keep losing TWRP and couldn't see the backup which I make
Same problem. Resolved by flashing alternately several times twrp-3.2.1-0-potter.img and twrp-3.2.1-1-potter_persist.img and finally updated twrp-3.2.3-1-potter.img
It's because of dm-verity. You have to flash something like magisk or a custom kernel that disables it *before* you reboot into stock.
NZedPred said:
It's because of dm-verity. You have to flash something like magisk or a custom kernel that disables it *before* you reboot into stock.
Click to expand...
Click to collapse
I flashed magisk 17.1 and lazyflasher ,i got magisk and root but cannot install modules may be becoz of f2fs bug . By the way i lost twrp after booting to system again and No command still present in recovery mode . I am frustrated Moto software is just pain in head :silly:

Categories

Resources