Hello,
I'm trying to load LineageOS onto my Galaxy Tab S2. I'm using Oden to flash TWRP, but the issue is that after successfully flashing, I'm unable to boot into twrp. I tried to turn off auto-reboot in Oden, but when I then exit download mode on the tablet, it starts to boot again directly into the default os. Unlike a phone, I'm not able to remove the battery to force a power off and then a recovery boot. Anyone also run into this?
Thanks.
xd21 said:
Hello,
I'm trying to load LineageOS onto my Galaxy Tab S2. I'm using Oden to flash TWRP, but the issue is that after successfully flashing, I'm unable to boot into twrp. I tried to turn off auto-reboot in Oden, but when I then exit download mode on the tablet, it starts to boot again directly into the default os. Unlike a phone, I'm not able to remove the battery to force a power off and then a recovery boot. Anyone also run into this?
Thanks.
Click to expand...
Click to collapse
I had the same problem on my T810 and bypassed it holding button combo while it was rebooting.
Wasn't always successful so I had to flash TWRP several times until it worked.
Related
Hello,
I have a GT-N7000 which I am only able to access via download mode. Recovery mode does not work at all.
Odin 3.09 runs the following successfully:
1. Flashing a stock rom: N7000JPLSB_N7000OJPLSB_N7000XXLSO_HOME.tar.md5
2. Flashing a pit file: Q1_20110914_16GB.pit
3. Flashing a safe kernel: PhilZ-cwm6-JPLSB-UAE-4.89.4.tar.md5
These steps however have not solved the problem.
I have read that I need to flash a bootloader, but I don't know how to do that.
Any help would be highly appreciated.
GT2020 said:
Hello,
I have a GT-N7000 which I am only able to access via download mode. Recovery mode does not work at all.
Odin 3.09 runs the following successfully:
1. Flashing a stock rom: N7000JPLSB_N7000OJPLSB_N7000XXLSO_HOME.tar.md5
2. Flashing a pit file: Q1_20110914_16GB.pit
3. Flashing a safe kernel: PhilZ-cwm6-JPLSB-UAE-4.89.4.tar.md5
These steps however have not solved the problem.
I have read that I need to flash a bootloader, but I don't know how to do that.
Any help would be highly appreciated.
Click to expand...
Click to collapse
On a successful kernel flash, enter into recovery mode and flash raw kernel and its corresponding rom.
Unfortunately recovery does not work at all. The phone reboots when I attempt to enter recovery.
GT2020 said:
Unfortunately recovery does not work at all. The phone reboots when I attempt to enter recovery.
Click to expand...
Click to collapse
My phone has this thing where upon pressing the buttons for recovery, it will show the Samsung Galaxy Note screen twice before entering recovery. That means pressing the buttons until it finishes showing twice, or it will just reboots normally. Did you try it?
What I tried now was flashing the stock rom again. After Odin successfully flashed the rom, it went into a boot loop that lasted approximately 20 minutes, but I just let it loop without disturbing it. Eventually it stopped and switched itself off.
I tried to enter recovery and and it rebooted a few times as you mentioned, but eventually I now see the stock Recovery screen, but the Android is on his back with the red triangle on his chest.
I then performed a factory reset.
Phone reboots, I see the Samsung logo, I hear the jingle and then the phone switches off.
Edit:
Switch phone on: See message Android is upgrading. Reaches 33 of 73 apps and phone switches off.
Switch on again: Android is upgrading 1 of 41. Completes. Switches off.
Switch on again: See setup screen. Switches off.
Switch on again: Same thing.
Recovery still broken and can't setup phone as it switches itself off.
GT2020 said:
What I tried now was flashing the stock rom again. After Odin successfully flashed the rom, it went into a boot loop that lasted approximately 20 minutes, but I just let it loop without disturbing it. Eventually it stopped and switched itself off.
I tried to enter recovery and and it rebooted a few times as you mentioned, but eventually I now see the stock Recovery screen, but the Android is on his back with the red triangle on his chest.
I then performed a factory reset.
Phone reboots, I see the Samsung logo, I hear the jingle and then the phone switches off.
Edit:
Switch phone on: See message Android is upgrading. Reaches 33 of 73 apps and phone switches off.
Switch on again: Android is upgrading 1 of 41. Completes. Switches off.
Switch on again: See setup screen. Switches off.
Switch on again: Same thing.
Recovery still broken and can't setup phone as it switches itself off.
Click to expand...
Click to collapse
You need the stock recovery. Flash your rom in, reboot to stock recovery, then update with the corresponding Philz for your phone. If it works you should reboot and see philz recovery and your rom is unusable. Just flash raw kernel and any other rom after that
So all the random reboots were caused by a faulty battery.
I bought a new battery, followed steps 1,2 and 3 in my original post and my phone is working perfectly again.
I recently got a new ATT galaxy s5 (G900A). Upon setting it up, I used OTA to take it from stock to the latest version which was 5.1.1 I believe.
I then failed to do thorough research and attempted to downgrade it to 4.4.2 which started causing problems.
I retracted my actions in chronological order to help in troubleshooting this situation:
Upgraded via OTA to 5.1.1
used odin 3.10.7 in AP mode with file "AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5"
Odin reported a failure after a few moments of me pressing the "start" button. for the above AP file. On the phone's screen (whilst in download mode) , it showed the progress bar as not being completed and also not progressing after Odin Failed. I had to pull battery to restart the phone.
restarted phone and it threw a splash screen saying to use kies recovery due to a firmware error.
entered download mode, used odin in AP mode to flash "G900A_OC4_Stock_Partitions.tar.md5"
phone rebooted and hung on Samsung Galaxy S5 logo
entered recovery mode (vol up, home, power) to reset the cache, still hung up on samsung logo
entered recovery mode again to do factory reset/wipe, still hung on samsung logo
pulled battery, used odin in AP mode to flash file "G900A_OC4_Stock_Kernel.tar.md5"
phone rebooted and hung on Samsung Galaxy S5 logo
I did quite a bit of searching around and have employed a few attempts at fixing the issue as listed above. I am still hanging on the Samsung logo though.
Could anyone offer me some insight on how to go about resolving this situation?
Thanks for your time!
guy2020 said:
I recently got a new ATT galaxy s5 (G900A). Upon setting it up, I used OTA to take it from stock to the latest version which was 5.1.1 I believe.
I then failed to do thorough research and attempted to downgrade it to 4.4.2 which started causing problems.
I retracted my actions in chronological order to help in troubleshooting this situation:
Upgraded via OTA to 5.1.1
used odin 3.10.7 in AP mode with file "AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5"
Odin reported a failure after a few moments of me pressing the "start" button. for the above AP file. On the phone's screen (whilst in download mode) , it showed the progress bar as not being completed and also not progressing after Odin Failed. I had to pull battery to restart the phone.
restarted phone and it threw a splash screen saying to use kies recovery due to a firmware error.
entered download mode, used odin in AP mode to flash "G900A_OC4_Stock_Partitions.tar.md5"
phone rebooted and hung on Samsung Galaxy S5 logo
entered recovery mode (vol up, home, power) to reset the cache, still hung up on samsung logo
entered recovery mode again to do factory reset/wipe, still hung on samsung logo
pulled battery, used odin in AP mode to flash file "G900A_OC4_Stock_Kernel.tar.md5"
phone rebooted and hung on Samsung Galaxy S5 logo
I did quite a bit of searching around and have employed a few attempts at fixing the issue as listed above. I am still hanging on the Samsung logo though.
Could anyone offer me some insight on how to go about resolving this situation?
Thanks for your time!
Click to expand...
Click to collapse
Same problem here. Really need a solution
Jsorren said:
Same problem here. Really need a solution
Click to expand...
Click to collapse
Totally ran into exactly the same issue...I am trying to sort out the details of it today and will post up what I find...I believe the answer lies somewhere in getting back to stock OF3 firmware + OF3 kernel without root via ODIN .tar file but we shall see. Also ..I am currently running ODIN v3.09
Get the phone up and running
Ok this is what I did to get my phone back up and running,
What happened was I did what it said on the downgrade thread here on xda, it didn't work. But of course it left my phone stuck on download mode.
I used a program from z3x to download the pit file, that usually takes it out of download mode. Then I booted into recovery, I had the 4.2 recovery on a 5.0 rom.
So I was stuck un bootloop, but there is a way to get it out.
downloaded the update and sent it with adb sideload.
so in other words
things you need
1. easy adb http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
2. update file for S5, from my google drive http://*******/1TjDwb
Steps I took
1. go to recovery mode by booting with volume up + home + power
2. select apply update from adb
3. install easy adb http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
4. go into any command shell ( cmd or windows powershell) and send the file by adb
in my case it was "adb sideload 2400258.cfg"
5. wait for the phone to apply the update and restart.
I have a long browsing history (about 7 devices and various browsers), I don't really have time to look up the thread I got the update from.
Hi guys, I got a note 8 that was stuck in upload mode, i did the volume up and down button but it kept booting into the upload mode, so i ended up loading the latest SW thru ODIN on the phone, now the phone is in an infinite boot loop and wont into recovery to wipe the cache. I have reloaded the software twice to make sure its not the problem, it will go to the samsung screen, then vibrate twice and reboot.
anyone else run into this issue?
Hi. Any update on your phone?
Install old stock firmware through ODIN
I tried installing a custom ROM and rooting my Tab A 10.1 2019 and now it is stuck in a bootloop and will not turn off. What happens:
1. I get the Galaxy Tab A screen
2. Get a message about boot loader unlocked
3. Tablet starts showing the Samsung logo loading screen
4. Tablet restarts
I can't get it to break this loop, it won't even turn off., just keeps looping. Any advice?
When you see the boot-up logo quickly use adb to reboot into recovery and re-flash
Hi. How did manage the problem.? I have mine at the same behavior. Cable was dettached while flashing with Odin.
Can you still boot-up at all? i.e. does any boot screen show up? If the screen turns on make sure its plugged in and then use ADB reboot recovery to get back into recovery if it hasn't been overwritten. From there you can mount storage if its TWRP and push files to your device for the ROM, and then flash from recovery. Also you could try to find an app that can fully restore your device to factory, I know there are apps that can do that. Good luck bro. Try drfone?
Hello, I could not install normal Xposed because the SDK version is 26 so I followed rova89's method to flash Xposed framework via recovery mode. I put this in cmd adb sideload xposed-v90-sdk26-arm64-beta1.zip and it installed correctly but after a reboot I cannot get out the Samsung loading screen. I can only go to the Downloading target... page with POWER+VOLUME DOWN+HOME and cannot boot into recovery mode (TWRP) anymore. I tried using Samsung Smart switch to initialize the device but it said SM-A520F cannot be initialized.
On Samsung A5, you cant take out the battery so I cant power off the phone either. I tried flashing TWRP again using odin and its still stuck on "SAMSUNG" loading page. Would be great if someone can help me with this. Thanks!
Thank you @hainguyenthao for fixing the issue. It was a long run but a successful one.
staz74 said:
Thank you @hainguyenthao for fixing the issue. It was a long run but a successful one.Hi
Click to expand...
Click to collapse
What was the solution? Im stuck at samsung logo on my old tab A after installing xposed.
TESEKURLER