Ok, so... this is gonna be quite long to tell, but I need to explain the situation as carefully as possible because the problem I have seems to be very specific and potentially solutionless.
So, a week ago my Samung Galaxy Tab S6 Lite (SM-P610, CSC: ITV, which is the Italian Country Code and it's for unbranded devices, since my model is Wi-Fi only), suddenly started to restart itself and it's been stuck for days in a bootloop (i.e. it's stuck on the logo and if I hard restart it with Volume Down + Power, it gets stuck there again). Yesterday I found out that it's most likely a software problem, so re-installing the Android version should fix everything up... right? Well, I did just that but the device is still stuck on the bootloop.
Here I want to be more detailed: firstly, I'm 100% positive that the problem I have is NOT due to a virus, as I've never done ANYTHING that could potentially lead me to taking a virus (such as downloading apps outisde Google Play, visiting risky sites etc.); secondly, I followed a procedure that was supposed to repair my device without losing data. That's because I've stupidly never made a backup and I can't afford to make a factory reset. The procedure I followed consisted in finding the Android update I needed with Frija, and then downloading everything in the tablet with Odin. Also, I'm 100% positive that I made NO mistakes during the installation procedure. The only step that I did differently is HOW I installed the update: I did it with Download Mode, not with fastboot, because when I go into Recovery Mode and reboot the device into bootloader, the PC doesn't recognize my Tab, even if the PC does recognize that it's connected, as it makes the typical sound of when you plug something in a USB port (I have the USB drivers installed in my PC, I think it doesn't work because I never unlocked bootloader). What I get when I reboot into bootloader is "entering fastboot..." stuck screen and the PC and Odin aren't able to recognize it.
My questions are therefore these:
Is there a way to make a backup of the data of my device if I can't boot it (maybe via Download Mode)?
Is there a way to make fastboot work if I can't boot my device?
Is there some other way to repair my tablet that I can try?
Thank you for any help, this is my last hope to find a solution for my problem.
neo4458232 said:
When your device is stuck on an Android boot loop issue then you can fix it by simply doing a soft reset. Turn off your device and the problem will be resolved.
Here are the steps to follow:
First, switch off your device and take out your battery from the phone.
If your battery is non-removable then turn off the phone for 3 to 5 minutes and again turn it on.
This method works effectively to fix the error of the boot loop issue. But if a soft reset does not work for you to fix Android phones stuck in the boot loop issue then you should follow the next method.
Method 3: Reboot System in Recovery ModeRebooting a phone in the Recovery Mode is known for fixing several errors and issues on your Android phone. So, if you are unable to start your phone in normal mode or your Android is stuck in a reboot loop, then restart your phone in Recovery Mode.
Method 4: Remove and Reinsert SD CardYou may also try to remove the SD card to fix the boot loop in Android. According to several user reports, this trick worked for them. So, you should try this.
First, turn off your phone > remove the SD card > turn on your phone normally, and check if your phone is out from the boot loop or not.
If it is still stuck in the boot loop, then go for the other solution.
Method 5: Reboot the Phone in Safe ModeThis problem may also occur due to problematic 3rd party apps. If you have recently installed an app on your phone and then you started facing this issue, then remove it from your device.
Or, if you are not sure which app is responsible, then try rebooting your phone in safe mode. Doing this will disable all the third-party apps on your Android phone and then you can easily find out if this is the reason behind this issue or not.
To do this, you need to follow these steps:
Start rebooting your phone.
When the device logo appears on the screen, long-press the volume-down button at the same time.
Now, your phone will automatically switch to Safe mode.
If your phone is no more getting into the boot loop, then it means one of the third-party apps installed on the device was causing this issue.
Now, find out the problematic app and uninstall it to fix the Android boot loop without losing data.
Method 6: Use Custom Recovery ModeWhen you find your Android is stuck on the startup screen due to the boot loop issue, then you must try to restart the phone in the Custom Recovery mode. Here is the guide to do so:
To enter into the Custom Recovery mode press the Power + Volume down buttons simultaneously.
Select the “Advanced” option in the Custom Recovery menu.
Next, choose “Wipe Dalvik Cache”. Choose “Yes” when prompted for confirmation.
Move to the “Mounts and Storage” option and choose “format/cache”. It will clear the cache files completely.
Restart your device.
Method 7: Fix Android Bootloop Error Via CWM Recovery [For Rooted Phone]Maybe you are not aware of this method but it’s a useful way to fix the boot loop issue on Android after the update. Remember that this method is only for rooted phones. Here CWM means ClockworkMod and if your phone is stuck on the Android boot loop then it must be downloaded and installed on phone. Read me
Click to expand...
Click to collapse
Thanks for replying but I already tried every method listed here.
At this point it sounds like you need to bring it in to a local repair shop & see if they have a fix.
The solution is to wait on the turned on screen until the battery dies completely. Then put it to charge and after a bit using the reset combo (pwr+volume down) once the circular battery charging indicator with the green border comes. (It's a matter of luck, this keeps happening to my tablet and even the official samsung store can't fix it even though they took money to do the same)
Related
Hi,
Just wanted to share my experience getting JPC Rom installed and rooted.
Prior to upgrade, I had the JP3 Rom, rooted with clockwork and 1-click lag fix.
I had some major issues installing JPC. In fact, I ended up with the dreaded USB logo a few times.
This is not a complete guide, but hopefully it will help avoid the problems I had.
1) Before installing the new rom, I strongly suggest that you Factory Reset the phone.
2) Install the JPC Rom using the other guides on this page. I used Odin and choose Repartition to get a clean install.
3) Here is where the problems started. After the rom installed cleanly and the phone rebooted, it would get stuck on the second Samsung logo and eventually go black. This happened to me twice. The fix I found out, is to go into Rececovery mode (Vol Up, Home, Power) after the install and clear the cache, reformat SD and factory reset. After you do this the phone will boot normally.
4) After that I followed the rooting guide on this forum, but ended up with the dreaded USB logo. If this happens to you, just go back into DOwnload mode and reflash with Odin again (following the guide in this forum)
IMPORTANT: I have TWO galaxy s phones. The strange thing is, one of them is VERY easy to get into Download or recovery mode. The other is almost impossible. For those of you that have a similar model to me that seems like it does not have a 3 button download or recovery mode you probably do.
I thought I was bricked, and tried for over an hour to get my second phone into download mode (take out battery, hold three buttons, put in battery, over and over again). I was about to give up, but found I was able to get the phone into download mode if I ....
1) Take Battery Out. Put it back in.
2) Plug phone into USB on computer (do not turn it on)
3) Now try to do the 3 button Download mode. Press all three buttons at one time and release power about 1 second after seeing Samsung logo.
Again my second phone I can very easily get to download mode 100% of the time. I am really not sure why the two phones would be any different. I hope this helps people that have a stubborn phone like mine.
P.S. I did not install Clockwork on JPC, but I did root the phone and installed 1 click lag fix. Phone is running VERY stable and all features seem to work (including Mobile AP).
I hope this helps others like me who tried to install update.zip as explained in some posts & got the dreaded USB logo on boot & didn't know what to do because I am sharp but no programming & all that. I got mine to go ahead ONLY after I put in my SIM & External SD card. With both OUT, I get the USB logo 100% of the times.
I hope this helps.
Ive installed jpc a few time now and a factory reser after flashing did it for me every time
Hi, im in the process of selling my phone and am following the tutorial on here about turning the phone back onto stock. The flash with flashtool was successful but im forever stuck on the boot screen? with now no way to go into custom recovery? i installed the correct rom for the phone so why hasnt it worked? thanks in advance.
dav08094194 said:
Hi, im in the process of selling my phone and am following the tutorial on here about turning the phone back onto stock. The flash with flashtool was successful but im forever stuck on the boot screen? with now no way to go into custom recovery? i installed the correct rom for the phone so why hasnt it worked? thanks in advance.
Click to expand...
Click to collapse
The only way I could get it to work was the following; however there is one thing to try before you try my way because mine did this also - after the wipe and flash with flashtool etc. The only way I found to get out the bootloop was to do a factory restore after when its looping. So from the boot screen loop hold the power button until it goes off then on then off again.
Then do the process to get into the recovery so hold down and power then release power as soon as the lg logo appears (first one) then press it again immediately that SHOULD get ya to the grey factory reset screen. Press the power button 3 x and it should do a factory restore and boot up this time. First boot may take a minute it should eventually start up.
Failing that try this - Open the lg mobile support tool and connect the phone in download mode (volume up and power with plugged in usb on mine) then go to options and upgrade recovery. it will download a file usually about 2GB then install it, the phone will reboot at 100% on the phone and 80ish% on the lg tool it will then start into the setup feature,
DO NOT disconnect the phone until it gets to 100% and finishes. This way you shouldn't need to do an extra factory reset.
I understand for this the phone needs to be seen on com 4 (it shows on the phone screen) so if necessary go into device manager with the phone still plugged in in download mode and select com ports then select the phone com port then right click >properties> advanced and change the com port to 4. It may tell u its already being used but don't worry it is fine. Save and exit device manager.
please bare in mind these are just my experiences on MY LG D802 however its worked every single time for me without fail and ive done it a good few lol.
HTH:good:
Hello all,
Any help with this would be seriously appreciated. I rooted my Nexus 10 a while back, maybe two years ago. I'm not very proficient with this stuff. Anyhow I decided to do the OTA upgrade to 5.0...I was concerned something would go wrong unless I went to stock first, but I read that the only thing that would happen is root would be removed.
Anyhow, the tablet appears stuck while booting. I see the Google screen first with the unlocked indicator on the bottom. A few seconds later is the Android logo on its back, a red triangle over it with an exclamation point and "no command" written below". It stays that way for a minute or so, tries to reboot and goes back to the no command screen. I can't even power off, when I try to do so it just powers back on by itself and ends up at the no command screen again.
I tried booting into recovery (power, volume up, volume down). My options from here are either Start, Restart Bootloader, Recovery Mode or Power Off. Every option I choose leads to the No Command Screen (except power off, which powers off). No idea what to do from here.
Any help at all would be appreciated. As you can probably tell I don't have much experience with this and just wanted to go back to unrooted stock. If you have advice, please be clear. I can follow directions well enough, just don't have much experience here. Thanks in advance.
Same here, bootloop.
Same thing here. A seemingly short download of Lollipop (even though I have 50Mbs internet). Installation, reboot, and now it loops endlessly. I can get to the bootloader or into Download mode, but that's all. Recovery mode just reboots. I was rooted and had TWRP installed. Other than that, I was running stock 4.4.4.
I've rooted all my devices, and installed various ROM's on several devices. I have the full ADB installation. I have the Nexus Root Toolkit installed. The problem is, the device will not show up under "Devices" on the computer itself. I've installed every USB driver there is (and uninstalled each one after it does not work, so no I do not have several USB drivers installed). Of course nothing shows up using "adb devices" either. Nexus Root Toolkit also cannot find any devices. I've read everything on this subject I can find, and there are no answers out there. Anyone have ANY ideas??
Thanks
Guys, if your device is connected in fastboot (try "fastboot devices") then you can flash roms or recovery (and then flash rom) from there. There are multiple threads with the same problems out there which were fixed. E.g: http://forum.xda-developers.com/nexus-10/help/bricked-t2948546
In my example, I flashed TWRP recovery from fastboot, then installed custom ROM from recovery (official ROM failed to install for some reason). Try this, it might help.
danweis said:
Same thing here. A seemingly short download of Lollipop (even though I have 50Mbs internet). Installation, reboot, and now it loops endlessly. I can get to the bootloader or into Download mode, but that's all. Recovery mode just reboots. I was rooted and had TWRP installed. Other than that, I was running stock 4.4.4.
I've rooted all my devices, and installed various ROM's on several devices. I have the full ADB installation. I have the Nexus Root Toolkit installed. The problem is, the device will not show up under "Devices" on the computer itself. I've installed every USB driver there is (and uninstalled each one after it does not work, so no I do not have several USB drivers installed). Of course nothing shows up using "adb devices" either. Nexus Root Toolkit also cannot find any devices. I've read everything on this subject I can find, and there are no answers out there. Anyone have ANY ideas??
Thanks
Click to expand...
Click to collapse
Go to Fastboot mode (pwr+both volumes), Than select recovery after a while an android with Exclamation mark appears which is a stock recovery screen. To access the stock recovery menu press and hold power than press one of the volume keys so the menu will appear. Than do a factory reset and clear caches. You can than reboot and wait for boot animation to finish (it wont take long this time) and you will boot.
If this doesnt work you can flash a stock factory image easily from fastboot again.
Aresmar said:
Go to Fastboot mode (pwr+both volumes), Than select recovery after a while an android with Exclamation mark appears which is a stock recovery screen. To access the stock recovery menu press and hold power than press one of the volume keys so the menu will appear. Than do a factory reset and clear caches. You can than reboot and wait for boot animation to finish (it wont take long this time) and you will boot.
If this doesnt work you can flash a stock factory image easily from fastboot again.
Click to expand...
Click to collapse
I also had the same problem... I followed these instructions and now my Nexus 10 can boot normally (it took a long time to boot).
Only problem is all my data was deleted.... stup*d f*cking sh*t!!!!!!!
Hi all!
Here is a little problem that i didn't solved.
i have a N910F Note 4 that likes to boot loop . I received it as it is and don't know what caused it(i suppose that was a rooting issue because had the knox value 1)
During the all time, PC and MAC were unable to recognize the Note 4, despite of repeatedly reinstalled drivers(older and newer versions) , Keys and Smart Switch were unable to recognize the device, PC is failing to install the MTP driver for some reason. I changed the USB ports,restarted,updated drivers,updated windows etc. -NO RESULT. BUT : Somehow Keys is able to run recovery and initialization and install it on the device while saying Connecting device... , phone also doesn't appear in device manager or file explorer as external drive.NOTHING! Odin and Jodin says ''added!'' and starts the job with no comments
1. I tried different versions of boot loaders with different versions of ROM (all for my specific model) with no result.
The end of the boot is when Samsung logo ,sound and graphic appears but freezes before actually starting OS, then restarts. IT keeps restarting until battery goes off(even while connected to pc by usb!!! ). Then starts to charge the battery normally.
It boots in recovery and download mode with no problems, it did every time i flashed it…
2. I tried different versions of boot loaders with stock roms , custom kernels etc...and the problem was the same
3. I tried to flash with Odin the stock 4.4.4 without problems but….the problem was the same
4.I tried Device recovery and initialization with Keys and here something interesting happened:
First time when i did it, it went over the samsung logo and booted. I selected language,i skipped wifi network selection and i accepted the user agreement. No matter how fast i was moving, the boot loop didn't went over the user name selection which is after the user agreement. Then freeze and boot again.
Second time when recovered with Keys (tried more stuff in the mean time) it went over the logo and started to update like…''updating applications 2of 17'' the max reach point was ''3 apps of 17'' and then freeze and reboot
I am out of ideas so i suspect that the battery might be dead because it gets empty even if is charging while phone is ''boot looping''. I ordered a battery,should arrive soon.
If that don't work…i am gonna spend some cash and sent it to Samsung for repairs (i bet that it won't be cheap because they will probably tell me that is the motherboard fried so they make you pay for being a bad boy and tried to root). Far as i know is not a brick as long as download mode and recovery works just fine.
Is here someone that has any new ideas for bringing this phone to life? Any help is well received , maybe i skipped something….
Thank you in advance.
Boot into recovery and perform a factory reset, it will wipe the internal storage.
Battlehero said:
Boot into recovery and perform a factory reset, it will wipe the internal storage.
Click to expand...
Click to collapse
That was the first thing i tried , cache wiped also. After every rom when booting failed.
UPPME said:
That was the first thing i tried , cache wiped also. After every rom when booting failed.
Click to expand...
Click to collapse
Uninstall Kies, and install Samsung USB drivers: https://www.androidfilehost.com/?fid=24052804347849220
Take the battery out, leave it for approximately 10 seconds, enter the battery back in.
Hold volume down key + Home key and power on the device.
Then plug the mobile phone into the computer.
Run Odin as Admin: https://www.androidfilehost.com/?fid=24052804347851815
Then flash the firmware in the AP section.
Make sure that the firmware is for your region, you can download it from Sammobile or SamFirm.
i have the same problem, but mine doesn't let the samsung logo finish when it shows the letter S on samsung logo it goes restart again no sound or anything, recovery is accesible, download mode is also accessible, i can flash official firmware and factory reset but nothing change, still stuck in bootloop no one here in xda knows how to fix it i think.. or they just never encounter something like this
i know how to fix an ordinary bootloops or soft bricked.. but this one is different.. i think there's something with note 4 that causes this..
kerbiii said:
i have the same problem, but mine doesn't let the samsung logo finish when it shows the letter S on samsung logo it goes restart again no sound or anything, recovery is accesible, download mode is also accessible, i can flash official firmware and factory reset but nothing change, still stuck in bootloop no one here in xda knows how to fix it i think.. or they just never encounter something like this
i know how to fix an ordinary bootloops or soft bricked.. but this one is different.. i think there's something with note 4 that causes this..
Click to expand...
Click to collapse
Yes, it doesn't go after the Samsung graphics , mine does sound. Goes to app updates only after Kies recovery but doesn't go more far than updating apps 3/17 for ex…crushes there and starts over….weird.
One time i managed to actually go to setup menu, choose country,wifi, device name, and there crushed and started over…. So i am thinking now that the battery might be wasted because i saw posts saying that after the 5.0.1 update many Note 4's went to boot loop and the battery change solved the problem. Now i have new battery coming by post.
Hi I had a similar problem but I do not know if that works but always worth a try
1. download recovery - "twrp-2.8.1.0-trltexx"(.tar) cant post link fresh in forum
2. flash recovery through Odin (AP) ( run as administrator)
3. unplug the cable
4. Reboot to Recovery (home+power+wolume up)
5. Then go to Wipe/Advanced Wipe/check the boxes - Dalvik Cache,System,Data,Cache and Swipe to Wipe
6. Reboot to Download Mode
7. Open Odin ( run as administrator) choise the rom to flash
8 Connect the phone
7. Flash Your Stock Rom
8. Reboot
always in Odin load the file first to flash and then connect the phone
sorry for my English
UPPME said:
Yes, it doesn't go after the Samsung graphics , mine does sound. Goes to app updates only after Kies recovery but doesn't go more far than updating apps 3/17 for ex…crushes there and starts over….weird.
One time i managed to actually go to setup menu, choose country,wifi, device name, and there crushed and started over…. So i am thinking now that the battery might be wasted because i saw posts saying that after the 5.0.1 update many Note 4's went to boot loop and the battery change solved the problem. Now i have new battery coming by post.
Click to expand...
Click to collapse
if you can stay in recovery mode and download mode for more than 10mins i think its not battery problem, i think i have corrupted system files, i left my note 4 to samsung service center a while ago i will get it tom, i just hope they wont charge me too much for it,
uldyzjan said:
Hi I had a similar problem but I do not know if that works but always worth a try
1. download recovery - "twrp-2.8.1.0-trltexx"(.tar) cant post link fresh in forum
2. flash recovery through Odin (AP) ( run as administrator)
3. unplug the cable
4. Reboot to Recovery (home+power+wolume up)
5. Then go to Wipe/Advanced Wipe/check the boxes - Dalvik Cache,System,Data,Cache and Swipe to Wipe
6. Reboot to Download Mode
7. Open Odin ( run as administrator) choise the rom to flash
8 Connect the phone
7. Flash Your Stock Rom
8. Reboot
always in Odin load the file first to flash and then connect the phone
sorry for my English
Click to expand...
Click to collapse
nah it doesnt work thats the first thing I do, that only work on ordinary bootloop
I was stuck in a boot loop the other day trying to flash a stock ROM to get rid of encryption. I tried all the stuff mentioned in this thread which is just standard procedure but I couldn't get past the samsung logo. What it turned out to be was that you need to go to stock recovery after flashing the stock ROM via odin and do a factory data reset then it will boot to the OS. It worked in my case, maybe you can give it a try.
guts100 said:
I was stuck in a boot loop the other day trying to flash a stock ROM to get rid of encryption. I tried all the stuff mentioned in this thread which is just standard procedure but I couldn't get past the samsung logo. What it turned out to be was that you need to go to stock recovery after flashing the stock ROM via odin and do a factory data reset then it will boot to the OS. It worked in my case, maybe you can give it a try.
Click to expand...
Click to collapse
if you read the above post you will know that we already wipe and factory reset,
btw since i was not able to fix it, it brought it to samsung service center and they also cant fix it so they are changing the motherboard, so far they are not charging me anything and just asking to bring my receipt of purchase so it will be under warranty
kerbiii said:
if you read the above post you will know that we already wipe and factory reset,
btw since i was not able to fix it, it brought it to samsung service center and they also cant fix it so they are changing the motherboard, so far they are not charging me anything and just asking to bring my receipt of purchase so it will be under warranty
Click to expand...
Click to collapse
I read the post; however, it did not appear as though you did a factory reset after flashing the stock ROM only before. At any rate at least you're getting a new mobo out of it and problem solved.
guts100 said:
I was stuck in a boot loop the other day trying to flash a stock ROM to get rid of encryption. I tried all the stuff mentioned in this thread which is just standard procedure but I couldn't get past the samsung logo. What it turned out to be was that you need to go to stock recovery after flashing the stock ROM via odin and do a factory data reset then it will boot to the OS. It worked in my case, maybe you can give it a try.
Click to expand...
Click to collapse
guts100 said:
I read the post; however, it did not appear as though you did a factory reset after flashing the stock ROM only before. At any rate at least you're getting a new mobo out of it and problem solved.
Click to expand...
Click to collapse
yes thats the good thing and its under warranty even though im already rooted, with knox 01 and custom binary haha, i was already expecting to pay a huge amount of money but they said they will cover it, so its a blessing, but i hope the OP fixed his problem.
Hi!
I used my S7 Edge for a couple of years and now I am afraid it may have died on me. As always, backups of f.e. pictures are not up to date.
During the night, it lay on my Qi charger. When I took it in hand, the screen was extremely dark and stuck in the "loading Lineage" screen. I tried to reboot. It was stuck on the "Samsung Galaxy" screen.
I wanted to boot into recovery and wipe the cache and see if it works again. But I can't boot into recovery mode. No matter if I connect it to a USB cable, the button command does not work.
Switching the device off also isn't possible. The only way to switch it off is disconnecting the battery (I have opened it to do so).
The only thing I can do is booting into download mode (so I know my volume up button works...).
Several times the screen was stuck on the "empty battery" symbol - which did not change no matter how long I had it in the charger. I can't really replicate how I got to the battery screen. I installed another battery just to see if if by some magic this would change something, but nothing changed about my issue. No boot possible and no booting into recovery.
I thought to myself: Well, maybe if I reinstall TWRP I can get into Recovery again. But when I try Odin I get the error message: "there is no PIT partition"
I know you will want additional info:
sadly, I cant' say which version of lineage I had running. I would have to look into my phone - which I can't.
I installed Lineage a couple of years ago, the phone was rooted and had TWRP recovery. I changed my USB port and Audio port several months ago.
But everything was running fine - I did not change or do anything recently. It happened overnight.
Do you have any ideas what I can do? I am brooding for two days now over this issue and I am at the end of the line here.
Did my memory just die on me? Is it an unfixable hardware issue?
Or software-related and potentially salvageable?
thanks in advance for anybody that bothers with my problem.
PinkElf said:
Hi!
I used my S7 Edge for a couple of years and now I am afraid it may have died on me. As always, backups of f.e. pictures are not up to date.
During the night, it lay on my Qi charger. When I took it in hand, the screen was extremely dark and stuck in the "loading Lineage" screen. I tried to reboot. It was stuck on the "Samsung Galaxy" screen.
I wanted to boot into recovery and wipe the cache and see if it works again. But I can't boot into recovery mode. No matter if I connect it to a USB cable, the button command does not work.
Switching the device off also isn't possible. The only way to switch it off is disconnecting the battery (I have opened it to do so).
The only thing I can do is booting into download mode (so I know my volume up button works...).
Several times the screen was stuck on the "empty battery" symbol - which did not change no matter how long I had it in the charger. I can't really replicate how I got to the battery screen. I installed another battery just to see if if by some magic this would change something, but nothing changed about my issue. No boot possible and no booting into recovery.
I thought to myself: Well, maybe if I reinstall TWRP I can get into Recovery again. But when I try Odin I get the error message: "there is no PIT partition"
I know you will want additional info:
sadly, I cant' say which version of lineage I had running. I would have to look into my phone - which I can't.
I installed Lineage a couple of years ago, the phone was rooted and had TWRP recovery. I changed my USB port and Audio port several months ago.
But everything was running fine - I did not change or do anything recently. It happened overnight.
Do you have any ideas what I can do? I am brooding for two days now over this issue and I am at the end of the line here.
Did my memory just die on me? Is it an unfixable hardware issue?
Or software-related and potentially salvageable?
thanks in advance for anybody that bothers with my problem.
Click to expand...
Click to collapse
Hi, try to flash the stock firmware otherwise I really don't know :/
I guess I will lose my data when I install stock firmware, don't I?
What I ask myself is: Is the reason for not being able to boot into recovery that my device always thinks my battery is empty?
Is the fact that I can boot into download mode a sign that my memory and/or motherboard is still intact?
PinkElf said:
I guess I will lose my data when I install stock firmware, don't I?
What I ask myself is: Is the reason for not being able to boot into recovery that my device always thinks my battery is empty?
Is the fact that I can boot into download mode a sign that my memory and/or motherboard is still intact?
Click to expand...
Click to collapse
Are you using Lineage OS? If yes, then definitely yes. On my Xiaomi, I couldn't get into fastboot mode or into recovery, I don't know why and somehow I got there, I don't even know how I think I held the power mode for a long time and when the phone turned on I held the volume up button to get into recovery finally succeeded on the umpteenth attempt and from recovery I restarted the phone in fastboot mode and flashed the stock firmware. And yes, being able to boot your phone into fastboot is a good sign. It would be worse if it wasn't possible.
I am still stuck with the problem. I can boot into download mode. I can't find a way to boot into recovery.
Is there anything I can do in download mode?
If I find the lineage version I originally installed on my device, could I install it via ODIN and get my phone back without data loss? I have only ever installed ROMs via TWRP.
Just an idea, but as of now I get the error "could not find PIT partition" anyway while trying to reinstall TWRP.
PinkElf said:
I am still stuck with the problem. I can boot into download mode. I can't find a way to boot into recovery.
Is there anything I can do in download mode?
If I find the lineage version I originally installed on my device, could I install it via ODIN and get my phone back without data loss? I have only ever installed ROMs via TWRP.
Just an idea, but as of now I get the error "could not find PIT partition" anyway while trying to reinstall TWRP.
Click to expand...
Click to collapse
Yes, you can use download mode to install the firmware via Odin. Look
That means giving up hope for my personal data...
But even if I want to do this, I run into the problem, that I can't install anything due to "could not find PIT partition"...