Related
Hey guys, i've a big problem.
Yesterday, suddently my nexus s didn't boot. It was stucked on Google logo.
It's rooted and it has the cm7 rom.
I tryed to reflash with cw recovery but i have an issue.
I cannot copy nothing on the sdcard partition.
I mount it with recovery and correctly copy the img from my pc. After i sync and dismount but if i remount the sdcard i cannot see the file that i've copied before.
It seems strange because if i try to format sdcard from recovery it says "done" but the data still remain.
After that i tried to lock and reunlock my phone but it fail.
I launch the command fastboot oem unlock, correctly the two-choices window appear, i select yes but on my pc i see (erase fail) and bootload remain unlocked.
Please give me some advice to resurrect my phone.
Thanks for the support, and sorry for my bad english.
Emiliano
fastboot oem unlock wont lock it, use fastboot oem lock.
i need to unlock it. i've locked now i need to unlock.
But the procedure
fastboot oem unlock
fail with erase fail errore.
I had almost the exact same problem yesterday. Tried literally everything and nothing worked. In fact it kept getting a little worse with every battery pull/reboot.
I purposely re locked the boot loader, right before I went to Sprint and paid $38 for a working replacement.
Probably be a good long while before I root another phone.
Sent from my Nexus S 4G using Tapatalk
After 4.0.4 OTA update device is bricked.
I have experienced the same issue you are discussing here.
A couple of days ago I received an OTA update to android 4.0.4 for my Nexus S device, vodafone UK. My phone is NOT rooted or OEM unlocked. The update downloaded but fails to install on reboot. The phone just returns to the original state, with the update waiting to install.
Any app or software will not work on the device, force closes error. If I attempt to restore to any factory settings or wipe / format the phone by any method you can come up with in a google search!, once the device reboots this change is ignored. If I copy any file on the Mass storage via usb, after the phone reboots the file is gone.
I've attempted to unlock the oem to flash the device in an attempt to resolve this, however when using ./fastboot oem unlock I get the following error:
... FAILED (remote: Erase Fail)
It seems the device has been screwed some how after receiving this update. It can only be a hardware error now....
Who is now responsible to fix this? i have had this Nexus S over 1 year now, can I take to Samsung or Vodafone for these guys to get repaired?
Sounds like hardware issue. Have you tried formatting the sdcard in windows or running chkdsk /F.
I Have Same Problem how can i fix it?
LeeVidor said:
I have experienced the same issue you are discussing here.
A couple of days ago I received an OTA update to android 4.0.4 for my Nexus S device, vodafone UK. My phone is NOT rooted or OEM unlocked. The update downloaded but fails to install on reboot. The phone just returns to the original state, with the update waiting to install.
Any app or software will not work on the device, force closes error. If I attempt to restore to any factory settings or wipe / format the phone by any method you can come up with in a google search!, once the device reboots this change is ignored. If I copy any file on the Mass storage via usb, after the phone reboots the file is gone.
I've attempted to unlock the oem to flash the device in an attempt to resolve this, however when using ./fastboot oem unlock I get the following error:
... FAILED (remote: Erase Fail)
It seems the device has been screwed some how after receiving this update. It can only be a hardware error now....
Who is now responsible to fix this? i have had this Nexus S over 1 year now, can I take to Samsung or Vodafone for these guys to get repaired?
Click to expand...
Click to collapse
please anyone can help me how can i fix my mobile ...
You can't. It's a hardware common issue without any solution. Better sent it to repair. My two cents
Sent from my
( •_•)
( •_•)>⌐■-■
Nexus S
(⌐■_■)
YYYYYYYEEEEEAAAAAAAAAAHHHHHHHHHHHH
sammme problem har you fix it?
benazhack said:
i need to unlock it. i've locked now i need to unlock.
But the procedure
fastboot oem unlock
fail with erase fail errore.
Click to expand...
Click to collapse
please help me if u get the solution plz
zaherrrr said:
please help me if u get the solution plz
Click to expand...
Click to collapse
Already been posted, you can't, warranty repair or you need to replace the main board(guessing £100-200?)
Sent from my ice cream powered Nexus S
DarkhShadow said:
Already been posted, you can't, warranty repair or you need to replace the main board(guessing £100-200?)
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
Just figured something out, i had the same issues as described above, could only boot the phone with a hair dryer
The new update Jelly Bean 4.1.1 is more forgiving when it comes to booting (probably voltages of the internal SD!! I'm still testing, but as far as i can see now, the phone boots normally again now (no more stuck on the google logo)
My problems:
- Not able to unlock bootloader (erase failed).
- Not possible to boot normally due to faulty internal SD card (only able to boot with the 'hairdryer' trick).
What did i do:
- Just tried the same as the trick on booting: use the hairdryer when fastbooting!!!
- Have everything ready; cmd, fastboot files, drivers etc, phone connected to computer with USB.
- Try to boot it first after heating the phone with the hairdryer (get past the google logo) and then immediately remove the battery.
- Then boot into fastboot mode (power and vol. up).
- Immediately execute the 'fastboot oem unlock' command.
Voila, that did the trick for me. Status OKAY and my bootloader was unlocked.
Then ROOT and update the phone to 4.1.1 with the following instructions:
(not able to unclude link, see webtrickz dot com/guide-to-manually-update-nexus-s-i9020ti9023-to-android-4-1-1-jelly-bean)
That did the trick for me!
NO MORE HAIRDRYER FOR ME!!
OEM unlock FAILED (remote: Erase Fail)
Hi
I'm replying to this message to share my experience about the same issu i had.
I bought a broken nexus s on google, auction described the phone as messed up during some software update. When cell got here:
- Bootloader was loading and locked
- Bootloader was reporting no boot image and no recovery
- Recovery was flashed with cwm 6.0.1.0
When trying to oem unlock, I was getting "FAILED (remote: Erase Fail)" no matter what I try. My config was good i've unlocked many nexus s with the same setup.
In recovery I was not able to mount sdcard, system, boot, nothing was working as it should.
After many frustrating hours, i saw this post.. What a stupid idea.. But I have nothing to loose at this point.
I don't have a hair dryer but I do have an oven. I figured the idea was to get the phone really hot..
Set the oven to 170, convection on and cooked the phone without the battery and cover for about 5 minutes until it was really hot but not melting.
Did the oem unlock and guess what.. It worked on first try.
After that I was able to update bootloader, radio, recovery and installed latest cm10. I've wipped the phone a couple of time, tried everything I could think of to test if something is not working, but everything does..
No hair dryer?
Just cook you phone at 170 for 5 minutes.
Worked for me.. go figure..
hetile
TimeClypse said:
Just figured something out, i had the same issues as described above, could only boot the phone with a hair dryer
The new update Jelly Bean 4.1.1 is more forgiving when it comes to booting (probably voltages of the internal SD!! I'm still testing, but as far as i can see now, the phone boots normally again now (no more stuck on the google logo)
My problems:
- Not able to unlock bootloader (erase failed).
- Not possible to boot normally due to faulty internal SD card (only able to boot with the 'hairdryer' trick).
What did i do:
- Just tried the same as the trick on booting: use the hairdryer when fastbooting!!!
- Have everything ready; cmd, fastboot files, drivers etc, phone connected to computer with USB.
- Try to boot it first after heating the phone with the hairdryer (get past the google logo) and then immediately remove the battery.
- Then boot into fastboot mode (power and vol. up).
- Immediately execute the 'fastboot oem unlock' command.
Voila, that did the trick for me. Status OKAY and my bootloader was unlocked.
Then ROOT and update the phone to 4.1.1 with the following instructions:
(not able to unclude link, see webtrickz dot com/guide-to-manually-update-nexus-s-i9020ti9023-to-android-4-1-1-jelly-bean)
That did the trick for me!
NO MORE HAIRDRYER FOR ME!!
Click to expand...
Click to collapse
hetile said:
Hi
I'm replying to this message to share my experience about the same issu i had.
I bought a broken nexus s on google, auction described the phone as messed up during some software update. When cell got here:
- Bootloader was loading and locked
- Bootloader was reporting no boot image and no recovery
- Recovery was flashed with cwm 6.0.1.0
When trying to oem unlock, I was getting "FAILED (remote: Erase Fail)" no matter what I try. My config was good i've unlocked many nexus s with the same setup.
In recovery I was not able to mount sdcard, system, boot, nothing was working as it should.
After many frustrating hours, i saw this post.. What a stupid idea.. But I have nothing to loose at this point.
I don't have a hair dryer but I do have an oven. I figured the idea was to get the phone really hot..
Set the oven to 170, convection on and cooked the phone without the battery and cover for about 5 minutes until it was really hot but not melting.
Did the oem unlock and guess what.. It worked on first try.
After that I was able to update bootloader, radio, recovery and installed latest cm10. I've wipped the phone a couple of time, tried everything I could think of to test if something is not working, but everything does..
No hair dryer?
Just cook you phone at 170 for 5 minutes.
Worked for me.. go figure..
hetile
Click to expand...
Click to collapse
I'm speechless..hair dryer works for me too!!! THANK YOU GUYS!
i have a big problem
i buy a stock phone (I9020T)
but i cant unlock the phone with any method and cant root or flash and ...
phone random correctly boot and random (90%) hang on google logo
i cant do anything with phone when randomly boot on ! (many error)
i even cant erase and restore factory device (failed) in recovery mode (after press all keys i see standard menu)
i must 10 - 20 time pull battery and power again to ics boot up
but every thing back to a point (last user setting and photo-gallery and ...)
and dont save anything in next boot !!!
how can check internal memory for any damage ?
i thing have exact problem http://forum.xda-developers.com/showthread.php?t=993403
but phone is LOCKED and cant test that methods and cant return to samsung :'(
please helpppppppp me
Carrier TMB
LOCKED
Rom: ICS (no root, no mod, no customize)
bootloader ver: I9020XXKL1
Baseband ver: I9020XXKI1
i try every guid and tutorial to unlock and root, not work anyone !
FAILED (remote: Erase Fail) and many error like this Erase Fail or write failed
memory is readonly ? or phone was crashed ?
any solutions ????
tanx
i see same error in nexusshacks.com ics root guid :'(
please helpppppp ....
anybody any idea .......
Have you encrypted your phone?
Sent from my Nexus S using XDA
maybe your sdcard / internel memory is faulty?
jorim.tielemans said:
Have you encrypted your phone?
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
no i dont ! how can check it ?
mtothearkus said:
maybe your sdcard / internel memory is faulty?
Click to expand...
Click to collapse
some time when ics boot up and i can use usb storage mount i can work with memory and its ok.
but how can check internal ? its maybe readonly !
I am having the same exact issue. I have tried many different things. My ICS boots but everything force closes. When I installed fastboot, adb, sdk, etc., everything installs but when I run fastboot oem unlock i get the remote: erase fail error, even though the phones display gives me the unlock option screen. I also tried to do a wipe in stock recovery and that does not take. Once booted into ics, though nothing works, I can mount the phone to my computer but when I try to copy over a stock image to reflash the computer gets an error and won't copy. I would also appreciate anyones help with any new ideas. I don't think its a hardware issue, but maybe?
ninfragile14 said:
I am having the same exact issue. I have tried many different things. My ICS boots but everything force closes. When I installed fastboot, adb, sdk, etc., everything installs but when I run fastboot oem unlock i get the remote: erase fail error, even though the phones display gives me the unlock option screen. I also tried to do a wipe in stock recovery and that does not take. Once booted into ics, though nothing works, I can mount the phone to my computer but when I try to copy over a stock image to reflash the computer gets an error and won't copy. I would also appreciate anyones help with any new ideas. I don't think its a hardware issue, but maybe?
Click to expand...
Click to collapse
i found very good solution : recycle bin
but i see on it : don't recycle
-> ye shoare ghadimi hast ke mige samsung faghat lcd ! (khak too saret samsung)
i have same problem and i cant work with my mobile
ninfragile14 said:
I am having the same exact issue. I have tried many different things. My ICS boots but everything force closes. When I installed fastboot, adb, sdk, etc., everything installs but when I run fastboot oem unlock i get the remote: erase fail error, even though the phones display gives me the unlock option screen. I also tried to do a wipe in stock recovery and that does not take. Once booted into ics, though nothing works, I can mount the phone to my computer but when I try to copy over a stock image to reflash the computer gets an error and won't copy. I would also appreciate anyones help with any new ideas. I don't think its a hardware issue, but maybe?
Click to expand...
Click to collapse
i have same problem and i cant work with my mobile
I Have Same Problem how can i fix it?
ali.md said:
i have a big problem
i buy a stock phone (I9020T)
but i cant unlock the phone with any method and cant root or flash and ...
phone random correctly boot and random (90%) hang on google logo
i cant do anything with phone when randomly boot on ! (many error)
i even cant erase and restore factory device (failed) in recovery mode (after press all keys i see standard menu)
i must 10 - 20 time pull battery and power again to ics boot up
but every thing back to a point (last user setting and photo-gallery and ...)
and dont save anything in next boot !!!
how can check internal memory for any damage ?
i thing have exact problem http://forum.xda-developers.com/showthread.php?t=993403
but phone is LOCKED and cant test that methods and cant return to samsung :'(
please helpppppppp me
Carrier TMB
LOCKED
Rom: ICS (no root, no mod, no customize)
bootloader ver: I9020XXKL1
Baseband ver: I9020XXKI1
i try every guid and tutorial to unlock and root, not work anyone !
FAILED (remote: Erase Fail) and many error like this Erase Fail or write failed
memory is readonly ? or phone was crashed ?
any solutions ????
tanx
Click to expand...
Click to collapse
can u help me ? my mobile stop with google logo
i try to unlock with fastboot oem unlock but it doesnt work
i get feil ...
Help me please if u get the solution
[email protected] please send to me email if u get the answer thank you
zaherrrr said:
can u help me ? my mobile stop with google logo
i try to unlock with fastboot oem unlock but it doesnt work
i get feil ...
Help me please if u get the solution
[email protected] please send to me email if u get the answer thank you
Click to expand...
Click to collapse
I have same problem too,Any way to fix this ?
Paper Weight
My nexus s has the fail problem too and so does my daughters,nothing will fix this problem but a new motherboard.Its a result of a hardware failure.I have tried even reseating the chips.My fix was searching the net for people selling their phone due to broken screen.I found one so far for 50 bucks and bought it.Fixed my daughters with easy by changing the board.I have spent hours upon hours reading articles on this problem.The best article i read addressing the problem was the placement of chips too close to the edge of a circuit board.After looking at the placement of the memory chip in my nexus s,I fully understand why it fails.Just by upgrading your phone and causing the phone to over heat a bit could warp the BGA seating of a chip resulting in a paper weight so to speak.This is only my response to how i feel on this subject.The end result for those with no warranty.Search the resell sites for a phone with broken screen and fix.
any solution yet ?
i look at my phone every day on my desk and ... :crying:
my phone turn back on after full wipe but storage freezed
for example wen i copy file/ delete/ format / ... and turn usb storage off and on again (without restart) everything backed !!!!
storage locked and freezed or corrupted !
help us someone please
Hi, well it looks like i have probably hard bricked my phone. After updating to nougat i decided to do afresh clean install. I wanted my phone to as if i had just bought it and came with nougat/emui 5 installed. So i did a factory reset from within the settings menu. But then i thought i would completely erase everything and start from the latest build before nougat, so emui 4.1.2/ marshmallow. So after wiping all the partitions in twrp and then doing a volume up + power to do complete factory wipe followed by using the three button method to install the B130 UPDATE.APP in dload folder on my sdcard, all worked as expected. The update completed at 100% and then rebooted. So there i am waiting for my phone to boot to start the setup process as i have done dozens of times before...BUT...my phone will not boot to the initial setup wizard. It just stays stuck on the Honor logo pulsing animation for ever and ever and ever!!!!!!
So i do the volume up + power button to get to stock recovery and do factory wipe and cache wipe as well. It works as expected so i reboot and once again use the 3 button method to install the update.app on my sdcard. That works as expected and at 100% says its succeeded and reboots. Once again i wait for it to boot to the initial setup wizard but....ALAS...it stays on that DAMN pulsing Honor logo. Ive tried rebooting it several times, redoing the factory wipe and install several times, but nothing. Ive gone into fastboot mode (volume down + power) to try and flash the boot.img and system.img ive extracted from update.app but get the error message -- remote: command failed -- and the same if i try to unlock bootloader. Obviously its not going to work because my bootloader isnt unlocked and nor can i got in to developer settings to enable oem unlock and turn USB debugging on because my phone wont boot past that bloody honor logo.
The only thing i havent done yet is to use eRecovery but i dont have broadband and i doesnt seem to work over public wifi! So i will go to my friends tomorrow and use their broadband and hopefullly eRecovery will download/restore the latest firmware. The only other thing i can think of is to download the original nem-l51c432B102 that came with my phone when bought, extract the update.app file and replace the B130 i have on my sdcard dload folder at present.
Sorry for such a long post but i wanted to expalin evrything in detail to hopefully resolve my problem without going backwards and forwards with questions and answers and taking for ever.
So ANYONE and EVERYONE who managed to read the whole post, if you have even the slightest idea of how to get my phone working, please oh please share it with me. Also my phone is still under warranty so if i needed to send it to a huawei centre to get it fixed would they do it and do it for free??? because eseentialy all i did was a factory wipe/reset and install a frmware and it goes KAPUT!! thats not my fault right????!!???
Thank you to one and all for any wisdom you can share.
please....please.......help???
So sorry for my original long post people, i simply wanted to give as much detail and info as possible because being vague doesnt help anyone. It seems that might have worked against me.
Please,please any suggestions would be appreciated to the N'th degree! I have tried everything i can think of and i am truly desperate now. I dont understand why i cant get it to work...
I can go into stock recovery and wipe the cach and do factory reset and that works fine, no errors.
I can hold the 3 buttons down to install the firmware package(ive got update.app from B130 build) and that works fine, gets to 100% and says 'success' and then reboots, with no errors.
But either way the phone refuses to boot past the honor logo boot animation and ive left it for hours hoping,praying, it will work after the 32nd time...
I can access fastboot but that is useless because my bootloader is not unlocked and i cant get to developer options to enable 'usb debugging' and 'oem unlock'. So i just get error message 'remote: Command Failed' with any command i type.
But thats madness, i cant comprehend why it wont boot because everything seems to work!?!
There has to be a way to get my device functioning again.
I am pulling my hair out, i am at a complete loss, it doesn't make sense. PLEASE ANYONE ..... please help....
Thanks HONOR-able enthusiasts for any help, no matter how small!
First of all, I'm pretty noob this days on Android so I'm very sorry guys, also english is not my first language.
My nexus was working great until today. I ended a Whatsapp Call and get a black screen, phone looks frozen (happened before). Reboot it and works fine for 5-10 minutes, after that it started to reboot itself the whole time in bootlop, stuck in the rom intro, after the Google text. My rom is one of the very first roms from Slim Roms, I'm sorry I don't remember the Android Version, but is "old".
I can access to the recovery mode tho. I tried to wipe dalvik cache and the TWRP failed, wipe and factory reset, fail as well... I don't know what else to do. I don't have any image to install in the sd, or any backup. Windows 10 recognize an "android" but can't access to it so I can't copy any file to it.
Is my phone dead or can I do something? I love this phone :crying:
Any help please? I tried using ADB and get to copy some files into the phone but still every time I try to do a wipe cache, factory reset or what ever I get a Unable to mount Data / Cache / Storage... every time the same error.
I google it and found that some people could fix that error by repairing the file system and select ext4. But I can't do that, my TWRP build is quite old (v2.6.3.4) and doesn't have that option here. Any suggestions?
Thanks btw
Me again
I've been reading forums for more than 7 hours today and trying different solutions, and nothing. But found this guy here https://androidforums.com/threads/is-my-nexus-5-dead.1099076/
He basically had the same issue as me few years ago, exactly the same, He didn't find any luck apparently.
How is it possible that a phone that can get access to TWRP or copy/flash files via ADB/Fastboot can't be saved? Theoretically in this case this is not a hard bricked, right? So? This is so so weird
It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.
No OS but twrp working
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!
audit13 said:
It's possible that portions of the internal memory are damaged.
The only thing left to try is flash a stock ROM using ADB commands. I recommend trying a KK ROM.
Click to expand...
Click to collapse
I tried that already, it does the installation thing but always fail in the end
mevrik_007 said:
Hello friend.
If I have understood your problem correctly then you have twrp working but no os.
I found that there is an option in twrp to enable MTP. once you do that you will be able to access it. While the phone is in recovery mode connect it to the computer and it will get recognized and you can transfer zip file to it and then flash a new os.
Cheers!
Click to expand...
Click to collapse
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad
ekeixdurden said:
I tried that already, it does the installation thing but always fail in the end
Also tried that: new rom+ gapps via usb adb and the TWRP says Failed...
I mean I still have OS because every single time I try to turn on my phone the animation screen of the Slim Rom goes in. The problem is I can't install anything new, no new rom, no factory image, no new version of TWRP, I can't wipe data or cache or do a factory reset because I get a big red Failed always. Feelsbad
Click to expand...
Click to collapse
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.
audit13 said:
Try this: lock the bootloader and reboot back into the bootloader. If the bootloader remains locked, that's a good sign. If the bootloader is unlocked, that is a bad sign.
Click to expand...
Click to collapse
I tried that with the Nexus root tool kit and the bootloader still is unlocked
ekeixdurden said:
I tried that with the Nexus root tool kit and the bootloader still is unlocked
Click to expand...
Click to collapse
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.
audit13 said:
Tells me that the memory chip is defective and needs to be replaced.
Indicates to me that the chip had lost its write capability.
Click to expand...
Click to collapse
Shieeeet... So nothing to do I guess? I already ordered a new phone but if I can save this beauty would be great
It would be great to fix it but the simplest solution may be to buy a nexus 5 with a smashed screen and working motherboard. I've done this before and it's worked out well because the nexus 5 is pretty old by today's phone standards so I got it cheap.
hmm not a bad idea at all. Thank you!
After the most recent update my phone got put into a bootloop that wouldnt stop for some reason, it would boot and then after I wanna say less than 20 seconds it would reboot itself, and just kept going on in this cycle unless I powered it off when it was booted. Anyway I've been trying everything I can to get the damn thing working again so I can at the very least get my pictures off of it without factory resetting it and nothing is working, and I sorta feel like I've made things worse. I tried flashing with Odin but after that the thing just stopped booting alltogether so that kinda limited my options a lot. Now I'm trying to sideload an update from an sd card which might work if i can find the right thing to sideload onto it but before it gets anywhere it tells me error in /sideload/package.zip (status 7) so either I just need a different thing to sideload or something's broken. Either way I don't know how to get it working cause I have no idea what I'm doing here so now I need help.
My phone is SM-G970U SPR
Sounds like you are in a bad spot. If your pictures are on internal storage then flashing anything in Odin will wipe that.
I think you need to accept that they may be lost.
not so fast, i've used home_csc in all my flashes and when I finally got one working all my stuff was still intact. Now i just need to figure out how to get it to stop bootlooping.
Hello friends, I am currently crying in the same boat!
So, similar to Oske829 my phone ( Samsung Galaxy S10e ) has entered into a bootloop after a recent update that occurred roughly on February 06, 2021.
I am also experiencing the same symptoms as well:
My phone starts to boot up, then fails and Approximately 20 seconds after, it repeats that cycle. The phone continues to bootloop until drained of its battery then repeats this cycle again once if it is charged. **this is the current situation**
After playing around with the buttons, the only progress I've made is reaching the Download Mode. Ive yet to try odin or anything else and would like to ask for some help please! I really want to be able to save the data on there (pictures, music, apps, etc..)
Any help is appreciated, Thanks!
AlphaFeedback said:
Hello friends, I am currently crying in the same boat!
So, similar to Oske829 my phone ( Samsung Galaxy S10e ) has entered into a bootloop after a recent update that occurred roughly on February 06, 2021.
I am also experiencing the same symptoms as well:
My phone starts to boot up, then fails and Approximately 20 seconds after, it repeats that cycle. The phone continues to bootloop until drained of its battery then repeats this cycle again once if it is charged. **this is the current situation**
After playing around with the buttons, the only progress I've made is reaching the Download Mode. Ive yet to try odin or anything else and would like to ask for some help please! I really want to be able to save the data on there (pictures, music, apps, etc..)
Any help is appreciated, Thanks!
Click to expand...
Click to collapse
Download the latest official firmware with Frija tool (no download caps unlike websites like Sammobile etc). Just be aware that if you download and use Android 11 you wont be able to downgrade to Android 10.
After you have downloaded it unpack the zip and run Odin. In order to preserve your data flash the HOME_CSC file not the regular CSC... file. Once you unpack the files you will see.
The phone needs to be in download mode for flashing and battery is suggested to be at 40% or more.
Btw a good way to get out of bootloop and get the phone to shut down is to connect the USB cable (could be from charger or PC) and then press Volume Down+Power buttons to force a restart. It may be nessesary to do this a few times.
At one point you will not see the boot screen but instead it will show the lightning bolt charging logo and the percentage. After that you can simply unplug the cable and the phone will turn off.
In order to enter Download mode the best way is to start with phone turned off. Hold Bixby+Volume Down buttons and connect the USB cable from PC. Once you see the confirmation screen you can release the buttons and press Volume Up to continue.
AlphaFeedback said:
Hello friends, I am currently crying in the same boat!
So, similar to Oske829 my phone ( Samsung Galaxy S10e ) has entered into a bootloop after a recent update that occurred roughly on February 06, 2021.
I am also experiencing the same symptoms as well:
My phone starts to boot up, then fails and Approximately 20 seconds after, it repeats that cycle. The phone continues to bootloop until drained of its battery then repeats this cycle again once if it is charged. **this is the current situation**
After playing around with the buttons, the only progress I've made is reaching the Download Mode. Ive yet to try odin or anything else and would like to ask for some help please! I really want to be able to save the data on there (pictures, music, apps, etc..)
Any help is appreciated, Thanks!
Click to expand...
Click to collapse
So incredibly glad to hear I'm not a lone soul dealing with this issue. I've tried a whole bunch of things to fix this issue but nothing is getting me anywhere. I tried flashing android 10 but as that other lad said you can't flash older versions of android.
At this point I think my only chance of saving the phone is to wait for a new system update to release and flash that in case it somehow magically fixes the phone for some reason. I wouldn't recommend trying to flash atm because it doesn't seem to help currently and if you donk it up you'll lose your data which is not something either of us want to do.
I'll let you know what happens if I try flashing a future update.
Well i had an even bigger problem initially. Not only was my S10e bootlooping. My EFS partition was missing files (dont know how that happened). That meant that IMEI was blank and there was not network connectivity aside from Wi-Fi.
Unfortunately even the stock firmware flash does not fix EFS. Thankfully i had a backup (multiple actually) stored away including EFS. So with some fiddiling around in custom recovery file manager (TWRP) i manged to get that restored. I did lose bunch of pictures in intrernal storage tho. Thankfully it was nothing important. Now i keep everything on SD card and SD Cards backup in PC.
Now im trying to get the phone rooted with Magisk but the damn thing is not working.
This underscores the importance of regular (i had weekly TWRP) backups. I had backups of all partitions except internal data like pictures etc. Lesson learned i guess.
Hey RaXelliX thanks for lending a hand! Unfortunately I'm using a Mac Pro and Frija is a Windows exclusive *tears*
it seems that my next best alternative is to use Samloader instead of Frija, and JOdin3 instead of Odin. After some research ive realized that I am way out of my depth , but shall continue nonetheless. I'm gonna try your method with these alternatives and hope for the best, that sounds good in theory I was just curious to the thoughts of others more experienced.
And Oske829 your definitely not alone, stay strong and best of luck
Thanks!
There was a new firmware on Sammobile that I just tried flashing, didn't fix the problem, still bootlooping. I am officially out of ideas on how to fix this. I think there's something funky at the hardware/software level that's throwing a fit about having to run android 11 that's causing this, but I have no clue what it could be or how to resolve it. Not sure if there's anything i can do at this point to save my data.
Oske829 said:
There was a new firmware on Sammobile that I just tried flashing, didn't fix the problem, still bootlooping. I am officially out of ideas on how to fix this. I think there's something funky at the hardware/software level that's throwing a fit about having to run android 11 that's causing this, but I have no clue what it could be or how to resolve it. Not sure if there's anything i can do at this point to save my data.
Click to expand...
Click to collapse
You could try flashing a custom recovery (i suggest TWRP: https://eu.dl.twrp.me/beyond0lte/ S10e Exynos version) and the once in recovery connect USB cable to move the data off. If you succeed then you could wipe the phone and get out of bootloop.
When flashing recovery via Odin use the AP field and select the twrp-3.5.0_9-4-beyond0lte.img.tar file and make sure NAND Erase and Re-Partition are OFF. Auto-Reboot could be on or off.
This would touch only the recovery partition and will not wipe data unless you do it yourself inside TWRP.
There are a few caveats with this. The phone may complain about missing VBMETA header. If that's the case i will share a modified TAR file that includes that and TWRP itself. Or the phone could fail flashing custom recovery due to Vaultkeeper that prevents flashing unofficial binaries. This usually happens a day or two after flashing firmware. After that Vaultkeeper disengages.
Obviously your bootloader should be unlocked. You can do that by pressing Bixby+Vol Down before connecting the cable (with phone off) and then long press Vol Up to enter bootloader unlock mode. Bootloader can later be relocked again.
RaXelliX said:
You could try flashing a custom recovery (i suggest TWRP: https://eu.dl.twrp.me/beyond0lte/ S10e Exynos version) and the once in recovery connect USB cable to move the data off. If you succeed then you could wipe the phone and get out of bootloop.
When flashing recovery via Odin use the AP field and select the twrp-3.5.0_9-4-beyond0lte.img.tar file and make sure NAND Erase and Re-Partition are OFF. Auto-Reboot could be on or off.
This would touch only the recovery partition and will not wipe data unless you do it yourself inside TWRP.
There are a few caveats with this. The phone may complain about missing VBMETA header. If that's the case i will share a modified TAR file that includes that and TWRP itself. Or the phone could fail flashing custom recovery due to Vaultkeeper that prevents flashing unofficial binaries. This usually happens a day or two after flashing firmware. After that Vaultkeeper disengages.
Obviously your bootloader should be unlocked. You can do that by pressing Bixby+Vol Down before connecting the cable (with phone off) and then long press Vol Up to enter bootloader unlock mode. Bootloader can later be relocked again.
Click to expand...
Click to collapse
Is this exclusively for exynos phones or can I run twrp on a qualcomm device?
nevermind i found the snapdragon version of twrp
I'm trying to unlock the bootloader the way you described but that doesn't seem to be doing anything, and any guides I'm seeing on how to unlock it all involve doing something that resets the phone which isn't what I'm going for.
Oske829 said:
I'm trying to unlock the bootloader the way you described but that doesn't seem to be doing anything, and any guides I'm seeing on how to unlock it all involve doing something that resets the phone which isn't what I'm going for.
Click to expand...
Click to collapse
You might be out of luck as Snapdragon versions do not allow bootloader unlocks. At least as far as i know. I wrongly assumed you had Exynos version. If the data is important the last resort might be to contact some data recovery company. Im sure they have tools to access the internal memory even if the phone bootloops or flat out refuses to boot.
Flash 4 file firmware
Use Home_csc
If you want keep your data
Hucin44 said:
Flash 4 file firmware
Use Home_csc
If you want keep your data
Click to expand...
Click to collapse
I believe he already tried that and the phone is still bootlooping. Im betting that whatever causes the bootloop is in the data, the data he needs to access.
A bad situation all around because if he wipes the data it will likely fix the bootloop but he will lose the data. If he keeps the data the phone will keep bootlooping and he wont be able to access it. Although i would argue that the data you cant access is effectively lost anyway and that the proper functioning of the phone is more important.
I've heard that theres tools you can use to recover deleted data after resets and stuff since data doesnt get wiped when its deleted its just marked as stuff that can be written over. So I would think there would be a way for me to reset my phone to get it working and then recover the data with one of those programs, but the problem is from what I've heard you need a rooted device to do any of that and since I can't unlock my bootloader I don't think that can happen.
The one last thing I'm going to try before I seek out help from data recovery people is to try pushing the smartswitch apk onto the phone with adb and then hoping I have enough uptime to install it before the phone reboots cause I've heard you can use smartswitch in download mode to backup data, but I haven't found any guides anywhere about how this is done so I don't know if its actually doable.
Oske829 said:
I've heard that theres tools you can use to recover deleted data after resets and stuff since data doesnt get wiped when its deleted its just marked as stuff that can be written over. So I would think there would be a way for me to reset my phone to get it working and then recover the data with one of those programs, but the problem is from what I've heard you need a rooted device to do any of that and since I can't unlock my bootloader I don't think that can happen.
The one last thing I'm going to try before I seek out help from data recovery people is to try pushing the smartswitch apk onto the phone with adb and then hoping I have enough uptime to install it before the phone reboots cause I've heard you can use smartswitch in download mode to backup data, but I haven't found any guides anywhere about how this is done so I don't know if its actually doable.
Click to expand...
Click to collapse
Well I find myself here after 48 hours of s10e hell, with an almost identical issue. After a couple attempts and a trip to our local cell phone repair place, we ended up doing a factory reset, with the same hopes -- that the files were still there but the space marked as "free" and a 3rd party data recovery program could bring them back from the dead.
But they all require your phone to be rooted first - and this being my first venture into phone rooting I'm not really sure which route to go, or if it'll even be worth the effort. Does rooting the phone mean flashing it with a new OS, or simply unlocking superuser access so the recovery software can do its bit? (bear in mind, a lot of these products try to root the phones themselves, but none of them seem to work - I've tried about 4 different products thus far).
I'm convinced that if I can root this phone, the recovery software WILL find those lost sectors and recover the lost data, even after a factory reset -- there's plenty of youtube videos out there that say you can do this, but the rooting bit is what's got me tied up in knots!
huh.. jeah, latest update bricked my s10e too.
but my case, when power on phone, nothing happens, just black.. when conect cable to pc , then i can enter recovery and download mode..
till now nothing helped..
oem locked, frp locked, cant flash custom binaries!
hope next update will fix this madnes..
or need to find same firmware as update.zip what we can flash using stock recovery option (sadly saamsung dont give any update.zip files, i gues its money thing)
so, odin dont help, chimera tools dont help, and enginering combination file give some approval error to flash factory binaries!
houdini987 said:
I'm convinced that if I can root this phone, the recovery software WILL find those lost sectors and recover the lost data, even after a factory reset -- there's plenty of youtube videos out there that say you can do this, but the rooting bit is what's got me tied up in knots!
Click to expand...
Click to collapse
well ,as far as i know, thease all recovery lost data works with HDD type disks, flash memory are out of luck..
because, i easy restored deleted data from my HDD, if it wasnt multiple times formated or writed full hdd , deleted, writed full etc.. but with SSD that software isnt working, due flash memory.. but, maybe im just to old, and there are new softs who can do that, just, i have not seen any jet!