Related
Hello everybody here at XDA, ( this is my first post here so bare with me here)(english is not my native language either)
My device:
Nexus 5 - hammerhead D821(H) 16GB
BL version - HHZ12h
BB version M8974A-2.0.50.2.26
Secure boot enabled
lock state unlocked
today i got a "broken" nexus 5 that is in boot loop with the google logo and it wont boot into any .img
At the start i read the pinned posts and found this tutorial: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
followed it step by step. but unfortunatly it didnt help my situation. there werent any errors or such kind.
i also tried this tutorial with other images but nothing worked.
When i go to the recovery mode and press the power button the phone get into the google logo and i can see some sort of strange stripes in like a milisecond but then it just gets into the boot loop.
i really think ive tried everything accept for relocking the bootloader but cant imaging that this could be the problem.
If you guys need more info please just ask me.
Hope you guys can help me out here.
Martin
Really thought XDA forums would be able to help me.
Any admins or mods or any other veteran that could help me out?
If that's not working for you, you can try using the Nexus Root Toolkit just to be sure.
If that doesn't work, than it could be hardware related, and not much you can do about that.
Hi All,
I have boot-loop problem for Nexus5 as described earlier .
As I was able to boot in Fastboot
I went for factory reset, and saw FAILED (remote: flash write failure).
I have tried to flash countless time with same error.
Then I read this thread and considered phone memory is toasted.
LG service-center have quoted me around $180 for mother board replacement.
Today I tried twrp project to boot in openrecovery and start an adb shell.
I was able to see file system of my phone.
These following folders are empty:
/boot
/cache
/data
In system folder there is only bin folder and which is empty.
/system
I have gotten this far, is internal memory roasted
Any direction or suggestions welcomed :good:
mesh120673 said:
Hi All,
I have boot-loop problem for Nexus5 as described earlier .
As I was able to boot in Fastboot
I went for factory reset, and saw FAILED (remote: flash write failure).
I have tried to flash countless time with same error.
Then I read this thread and considered phone memory is toasted.
LG service-center have quoted me around $180 for mother board replacement.
Today I tried twrp project to boot in openrecovery and start an adb shell.
I was able to see file system of my phone.
These following folders are empty:
/boot
/cache
/data
In system folder there is only bin folder and which is empty.
/system
I have gotten this far, is internal memory roasted
Any direction or suggestions welcomed :good:
Click to expand...
Click to collapse
Are you sure your bootloader is unlocked?
When you boot the phone in Fastboot mode, does the "lock state" say UNLOCKED?
If so, then yeah, your internal memory could be huffed.
spookytay said:
Are you sure your bootloader is unlocked?
When you boot the phone in Fastboot mode, does the "lock state" say UNLOCKED?
If so, then yeah, your internal memory could be huffed.
Click to expand...
Click to collapse
It says Locked.
I unlock it using ./fastboot oem unlock
I just got my N5 and was messing around. Rooted it and loaded a rom, but it would just seem to hang at the spinning dots forever. Though I didn't wait THAT long like some users did and had success.
I can't find the link I used, but googling around should get you there. I ended up restoring a factory image via fastboot. I ended up using THIS PROGRAM to root the phone. This program also has a restore option and gives an option to check in case you are in boot loop status. Give it a shot.
Yes I do believe you have to unlock the bootloader as well.
Nurmi_CEO said:
I just got my N5 and was messing around. Rooted it and loaded a rom, but it would just seem to hang at the spinning dots forever. Though I didn't wait THAT long like some users did and had success.
I can't find the link I used, but googling around should get you there. I ended up restoring a factory image via fastboot. I ended up using THIS PROGRAM to root the phone. This program also has a restore option and gives an option to check in case you are in boot loop status. Give it a shot.
Yes I do believe you have to unlock the bootloader as well.
Click to expand...
Click to collapse
Yes the bootloader must be unlocked before you can do ANYTHING to the phone, it's what's there to protect it from being hacked/changed or whatever. So before you can write anything to your phone, you need to make sure you OEM UNLOCK the bootloader.
[Solved!] Nexus 5 boot loop at Google logo
I found a solution on Youtube comment (can't post url, too new user).
You just have to press quickly the Power button durint 1-2 minutes (continue untill the Android animation start, don't stop when the Google logo appear)3
As crazy as it sounds, IT WORKS
Wow .. i had the exact same problem (Startup loop on Nexus 5 that shows the Google logo and restarts, over and over), and i pressed the power button quicky about 30 or 40 time until after I saw the startup animation and my phone came back to life. I have been charging it with cables other than the one that came with the phone for a few months now, and it has been acting strangely while plugged in (randomly clicking things on the screen, and enabling my camera and taking pictures on its own, etc.). So, to avoid problems in the future, I think I'll invest in a wireless charger. Thanks JackNUMBER for the easy solution. I hope this works for others as well. Saved me a trip to the store.
Hello, I'm about to giving up,
Something happened to the phone and now it won't boot, it barely show the "ANDROID" logo when it restart itself. I can enter to the recovery menu, it doesn't have clockwork recovery nor twrp, just the basic recovery. So far I tried:
wipe data/factory - didn't work.
wipe cache partition - didn't work
apply update from adb: Adb just work with sideload and that's it, for everything else it shows closed. I tried sending the rom with sideload and it fails every time:
* failed to write data 'protocol fault (couldn't read status): Invalid argument' *
So I took my sdcard and copied the room there, so I tried
apply update from sdcard, it starts and in no time it says:
Installation aborted (APPLY_EXT).
I'm very frustrated right now, nothing works, it seems that the manufacturer did great effort on being the only one who can recover this phone, who appears to be from China, the MTK6582.
Fastboot? it doesn't show the device, it would be my last hope but no, since there is no adb, I cannot call fastboot, and the apply update from adb only work with sideload (yeah, f**k me).
The best course of action would be to throw it to the trash?
Thanks!
Hey, I'm in a similar position to you. However, I went about it with a slightly different route. The chip used in this phone is the MediaTek 6582 (I think?). I downloaded some tools from a thread on here that includes the 320 rom and the necessary software for flashing. I've flashed MediaTek devices before, the Huawei Ascend G610 and G700, both successfully. This one is giving me headaches, the damn device keeps disconnecting. HOWEVER, if you're lucky and you don't have the same problem with disconnecting hardware, you should be able to flash a new rom via the software. It'll take a while though. Also, I don't know what'll happen to your IMEI afterwards, so that's another possible headache (both the G610 and the G700 lost their IMEI info, but I'd taken steps to back them up beforehand so I could just restore them; here, there's no option to backup).
Here's the thread: http://forum.xda-developers.com/android/general/htc-mtk-cpu-flash-files-flashtool-t3114271
Let me know if you need help. I'm screwed in that the damn phone keeps disconnecting. Similar to you, no fastboot either. Plus, no RUU for this HTC. Hell, the internet barely knows this flipping phone.
Cheers, and good luck.
blitz9826
0Camus0 said:
Hello, I'm about to giving up,
Something happened to the phone and now it won't boot, it barely show the "ANDROID" logo when it restart itself. I can enter to the recovery menu, it doesn't have clockwork recovery nor twrp, just the basic recovery. So far I tried:
wipe data/factory - didn't work.
wipe cache partition - didn't work
apply update from adb: Adb just work with sideload and that's it, for everything else it shows closed. I tried sending the rom with sideload and it fails every time:
* failed to write data 'protocol fault (couldn't read status): Invalid argument' *
So I took my sdcard and copied the room there, so I tried
apply update from sdcard, it starts and in no time it says:
Installation aborted (APPLY_EXT).
I'm very frustrated right now, nothing works, it seems that the manufacturer did great effort on being the only one who can recover this phone, who appears to be from China, the MTK6582.
Fastboot? it doesn't show the device, it would be my last hope but no, since there is no adb, I cannot call fastboot, and the apply update from adb only work with sideload (yeah, f**k me).
The best course of action would be to throw it to the trash?
Thanks!
Click to expand...
Click to collapse
Ditto!!!
Hey guys I am having the exact same issue, luckily for me it is my Mrs who done her phone in and not mine . She has the HTC Desire 320, I believe she tried to root it on her own without even asking for advice, I think she used the app Kingo Root, she said she went to remove the root but when she uninstalled the app it didn't remove it. (LOL I told her well perhaps that's because there will be some way of removing it, aside from just uninstalling the app), anyway she proceeded not to care and carried on using her phone as normal for maybe a week or two at most, then about midnight one night, came down and said to me,
"my phone had an update and on restarting I just get a dead android, if you press the power button you get some options so I clicked erase"
Click to expand...
Click to collapse
I was like nice so basically you F***ed it!!!!, and for about 2 weeks now I have been endlessly reading post after post, forum after forum, trying rom after rom, RUU, all kinds of things.
Here is the situation, the phone will boot as far as the HTC logo, it will get stuck in a short loop and reset itself 4/5 times repeating the HTC logo, eventually it will end up at the dead android pic (the android on his back with the red exclaimation mark triangle) with the words 'no command'. From here I can press the power button once to get a list/menu of items (What I assume to be the recovery menu). I can backup data, I can restore the backed up data (both of which do nothing as I guess there is nothing really to back up), There is an option to restore from sd card (which I have tried numerous roms and to no avail have any been successful), I can erase the cache and I can also erase everything and recover, the erase side works fine, I did notice in each of these menu that if you press volume up to activate them and then press the power button once, then the writing dissapears and the android proceeds to have his moving atom type thing in his belly, saying 'erasing..', however even with them completed successfully, it still does not restore.
NOTE!!! If you choose the erase and restore method, once activated with volume up, press the power button to get the spinning atom and erasing... message, when this finishes the phone will reboot, it goes to the htc logo, resets itself, goes to the logo again and then just stays at a black screen (almost like a frozen state, I left it for quite some time and it never changed).
I should also note, which I didn't to begin with, but no matter how long I hold the volume down and power button, there is no such hboot/fast boot menu at all, if you hold the volume down and power button even after it displays the htc logo, the phone just proceeds to endlessly reset and loop through the same process forever.
The only thing I can seem to access with little success, is the ADB CMD prompt through the Android SDK,
Code:
adb devices
will indeed return the device (a set of numbers with the word sideload beside it)
Code:
adb usb
Apart from the odd fluke, this has seemed to fail everytime with either an error about a protocol or an error stating 'closed'
Code:
adb sideload "ROM_FILENAME.ZIP OR .IMG
Occasionally this will throw the protocol error, but generally succeeds and displays the 100% most of the time, however the phone doesn't even try, it just almost instantaniously returns the error message :
Code:
[B][I]Installation Aborted (APPLY_ADB_SIDELOAD)[/I][/B]
NOTE!!! That the android lays on his back with this error, but it only says error below not no command.
I am pretty sure that I already came across a solution very similar to the one you posted above, and I just couldn't get it to recognise the phone, the only way the RUU would work, was by completely removing the battery and plugging in the usb, however without the battery in the phone, it just constantly beeps via usb, so I guess it turns on, then off, then on, then off, forever!!! So the RUU fails everytime, if I leave the battery in and try, the RUU program does nothing whatsoever! So I am at a complete loss with it now.
Cheers
GunnerJnr
Any luck with unbriking the HTC?
Maybe this is the solution, good luck.
Search: How to Unbrick every MTK China Phone ! Preloader / SP Flashtool Fix [HD] on Youtube
Responds please.
http://forum.xda-developers.com/showpost.php?p=64659997&postcount=16
I think that you no tell true because I tried this method with volume keys and nothing. Flash tool still show error. Its impossible to write android without battery. I think really put your phone to rubbish or sell as lcd+digitizer parts I think just we must waiting for new custom rom flashable via stock recovery. 320 is still new model and developers no moke any custom rom. So maybe only HTC service may help, only in HTC Factory peoples know how install android and bootloader on hard bricked device.
Hello,
I've seen quite some threads relating to this fail on the tablet, but all of them were because they were installating some custom ROM or kernel or something like that.
In my case, the charger cable I was using broke, and the tablet ran out of battery. Until then all normal. I buy a new original cable in Amazon, charge it, and then when I turn it on it stays on this screen. I tried pressing the power button for some time, so that it'd turn off but it keeps rebooting. In one of the times, it kinda started up on a screen saying that the encripting could not be completly (I was doing nothing like that so I was like what the hell?) and telling me to return to stock the tablet, losing all the data I might have on it. I accepted so it'd maybe at least reboot normally even if I lost my data, but it keeps rebooting and haven't entered again on such screen. Just one time, it entered in recovery cause a bunch of files could not be loaded, or something like that from what I could read. Unluckily I pressed reboot now and now it wont go again into recovery so don't know which files were the ones giving trouble.
I've never tried any kind of custom ROM, kernel or anything on this tablet, just on my Galaxy Nexus phone, so no idea why it'd brick like this. Looks just so random.
Thanks in advance if anyone could give me a hand on this.
SilentVene said:
Hello,
I've seen quite some threads relating to this fail on the tablet, but all of them were because they were installating some custom ROM or kernel or something like that.
In my case, the charger cable I was using broke, and the tablet ran out of battery. Until then all normal. I buy a new original cable in Amazon, charge it, and then when I turn it on it stays on this screen. I tried pressing the power button for some time, so that it'd turn off but it keeps rebooting. In one of the times, it kinda started up on a screen saying that the encripting could not be completly (I was doing nothing like that so I was like what the hell?) and telling me to return to stock the tablet, losing all the data I might have on it. I accepted so it'd maybe at least reboot normally even if I lost my data, but it keeps rebooting and haven't entered again on such screen. Just one time, it entered in recovery cause a bunch of files could not be loaded, or something like that from what I could read. Unluckily I pressed reboot now and now it wont go again into recovery so don't know which files were the ones giving trouble.
I've never tried any kind of custom ROM, kernel or anything on this tablet, just on my Galaxy Nexus phone, so no idea why it'd brick like this. Looks just so random.
Thanks in advance if anyone could give me a hand on this.
Click to expand...
Click to collapse
Hi, you should be able to boot into recovery by holding volume down and power. When it gets to splash screen let go of power and continue holding vol. down. Should be able to clear data and cache then reboot. You will loose data, like apps and passwords but it should boot all the way and be ready for set up. Hope it goes well for you.
Sent from my GT-P5110 using Tapatalk
homephysician said:
Hi, you should be able to boot into recovery by holding volume down and power. When it gets to splash screen let go of power and continue holding vol. down. Should be able to clear data and cache then reboot. You will loose data, like apps and passwords but it should boot all the way and be ready for set up. Hope it goes well for you.
Sent from my GT-P5110 using Tapatalk
Click to expand...
Click to collapse
Hi homephysician,
I tried that, and I just got a green text on the top left corner of the screen saying: 'logo_espresso10.jpg' draw failed.
Edit: I could go into recovery again. Trying to wipe the data and cache.
Edit2: When I tried to wipe cache, it says error and rebooted to the same screen (green text saying 'logo_espresso10.jpg' draw failed.) Anways, when I'm inside the recovery, it says this:
E:failed to mount /cache (Invalid argument)
can't mount ' /cache' (Invalid argument)
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/lastrecovery
E:failed to mount /data (Invalid argument)
E:Can't mount /data/log/recovery_log.txt
E:failed to mount /system (Invalid argument)
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_locale
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (Invalid argument)
tried Download mode? the system can't mount, since you haven't done anything, so it looks like your tab emmc card is gone haywire.
billysam said:
tried Download mode? the system can't mount, since you haven't done anything, so it looks like your tab emmc card is gone haywire.
Click to expand...
Click to collapse
I've no idea on how to do that. Never tried installing another ROM on the tablet. Been looking around the forum, but can't find a tutorial about that so I'm kinda lost.
Gonna try to look for that around, but I'd really appreciate it if you could send me a link or tell me how to do that as well.
SilentVene said:
I've no idea on how to do that. Never tried installing another ROM on the tablet. Been looking around the forum, but can't find a tutorial about that so I'm kinda lost.
Gonna try to look for that around, but I'd really appreciate it if you could send me a link or tell me how to do that as well.
Click to expand...
Click to collapse
you can enter download mode by pressing volume up + power button, if it shows then you can connect it via a usb cable to your pc and try to flash a stock firmware from sammobile.com or find from here
http://forum.xda-developers.com/showthread.php?t=2203309 (this has pretty much good links)
or look for your respective firmware, and then use odin to flash it.
there are many guides, it will take time and patience, everything you need you will find it here, but you should be able to enter into recovery or download mode or even should be able to make your device detected atleast to your pc, hope it's not a corrupted card, then you will need local repairmen.
PS Dont forget to mention and check your device model number, don't use P5100 files on P5113.
billysam said:
you can enter download mode by pressing volume up + power button, if it shows then you can connect it via a usb cable to your pc and try to flash a stock firmware from sammobile.com or find from here
http://forum.xda-developers.com/showthread.php?t=2203309 (this has pretty much good links)
or look for your respective firmware, and then use odin to flash it.
there are many guides, it will take time and patience, everything you need you will find it here, but you should be able to enter into recovery or download mode or even should be able to make your device detected atleast to your pc, hope it's not a corrupted card, then you will need local repairmen.
PS Dont forget to mention and check your device model number, don't use P5100 files on P5113.
Click to expand...
Click to collapse
Thank you billysam, gonna look for a guide, try that and post the results here.
By the way, my model number is P5100. Guess I gotta install those (can't be any other model).
Edit: My PC can't detect the tablet. I tried entering the download mode, but it only wants to go in this screen saying: Reboot now, apply update from ADB, apply update from external storage, wipe data/factory reset, wipe cache, apply update from cache. Only way I get the "connected device sound" on Windows is in the 'logo_espresso10.jpg' draw failed. screen, and it doesn't connect really. Nor Kies nor Odin can detect. They get stuck at SetupConnection.
Could I get the firmware in a SDCard, and use the "install from external storage" option?
Edit2: To make it clear, it says: "Installing system update..." -> "No command" -> "Error!" and gets in the recovery screen.
Edit3: I tried from SDCard and nothing, says installing /sdcard but it reboots again into recovery displaying all the same errors as before... Don't know, I think my tablet just bricked itself somehow... :crying:
You have beeen in recovery not download mode. You can not flash files through stock recovery since there is no file signed from samsung.
somehow you're not bricked and it's good that you can enter recovery mode as well, but it's all messed up. don't worry. You should be able to get into download mode, though, maybe you're missing the part to get into download mode, try once again, try differently pressing both up and down + power..
have you installed latest samsung USB drivers?
youre on stock recovery, so it's hard to flash anything unless you're on custom recovery and to get custom recovery installed you need download mode or your tab os running. which is not, check your cable check your USB check your buttons, it should get detected.
billysam said:
somehow you're not bricked and it's good that you can enter recovery mode as well, but it's all messed up. don't worry. You should be able to get into download mode, though, maybe you're missing the part to get into download mode, try once again, try differently pressing both up and down + power..
have you installed latest samsung USB drivers?
youre on stock recovery, so it's hard to flash anything unless you're on custom recovery and to get custom recovery installed you need download mode or your tab os running. which is not, check your cable check your USB check your buttons, it should get detected.
Click to expand...
Click to collapse
Tried all that to get into download mode and nothing... Gonna try now to let the battery die, since I can't switch it off any other way and try from there. Maybe it's because of that. Will edit with the results. And thanks for the help guys, really appreciate it. :good:
Edit: OK, got the tablet into the download mode. Flashed the stock firmware from sammobile with Odin, it sais PASS in green, but the tablet just won't turn on. Dunno if I did something wrong or what. Got it charging, and hoping it's maybe loading the firmware or so...
Edit2: Nothing... Guess it's really bricked now. Doesn't react to any button. Nor gets detected by PC. Guess i ****ed up somewhere in the process...
SilentVene said:
Tried all that to get into download mode and nothing... Gonna try now to let the battery die, since I can't switch it off any other way and try from there. Maybe it's because of that. Will edit with the results. And thanks for the help guys, really appreciate it. :good:
Edit: OK, got the tablet into the download mode. Flashed the stock firmware from sammobile with Odin, it sais PASS in green, but the tablet just won't turn on. Dunno if I did something wrong or what. Got it charging, and hoping it's maybe loading the firmware or so...
Edit2: Nothing... Guess it's really bricked now. Doesn't react to any button. Nor gets detected by PC. Guess i ****ed up somewhere in the process...
Click to expand...
Click to collapse
if you've flashed the correct firmware meant for your specific device, in the right manner, and got success passed in Odin without interruptions, it should boot up eventually..maybe the battery has given up and is not charged up, you can't hard brick a device with a right firmware flash and no interruptions.
hard bricks happens by flashing wrong device firmware.
I would suspect, the battery or the charger? cause you drained it completely and had broken the wire and bought new from amazon, wonder if its really without any fault. ( if you look closely you can see there are 2 type of dark screen..one when the device is actually shut off, which will be complete dark, the second is when there is power, it will have little light to it, I have come across this situation where the device battery was drained out, and it took me a lot of hours to bring it back on charging state...yes, I had flashed custom rom, and battery got low pretty bad and closed, I thought it was bricked but it did turn on)
try keeping your finger on the tablet screen and press power on button.
if its not, then the device emmc has given up or something on your side. (just a guess, it maybe is not, don't be so sure no matter what)
billysam said:
if you've flashed the correct firmware meant for your specific device, in the right manner, and got success passed in Odin without interruptions, it should boot up eventually..maybe the battery has given up and is not charged up, you can't hard brick a device with a right firmware flash and no interruptions.
hard bricks happens by flashing wrong device firmware.
I would suspect, the battery or the charger? cause you drained it completely and had broken the wire and bought new from amazon, wonder if its really without any fault. ( if you look closely you can see there are 2 type of dark screen..one when the device is actually shut off, which will be complete dark, the second is when there is power, it will have little light to it, I have come across this situation where the device battery was drained out, and it took me a lot of hours to bring it back on charging state...yes, I had flashed custom rom, and battery got low pretty bad and closed, I thought it was bricked but it did turn on)
try keeping your finger on the tablet screen and press power on button.
if its not, then the device emmc has given up or something on your side. (just a guess, it maybe is not, don't be so sure no matter what)
Click to expand...
Click to collapse
I plugged it and it doesn't do anything (switched light off just to be sure if the tablet screen would turn on even a bit, but nothing). Gonna do as you say and leave it there for some hours. Sorry I'm just kinda pessimistic about it... But yeah will try to bring it back to life.
I downloaded the firmware from sammobile, from the P5100 page. The latest, and the one from my phone provider (Vodafone, Spain). Used Odin3 v3.07. It showed PASS in green after the process ended. Just that the tablet never rebooted. It should have rebooted alone, but it just switched off and never reacted to any button again. Strange really.
Edit: Well, still nothing. No more ideas on what to do. Kinda giving it up since it doesn't react at all. :/
Does the device react if you plug the cable/tablet in to a computer?? And does the computer react when you plug the tablet in?
Hi guys,
I think I've really made a mess of things. Hopefully someone can come to the rescue. This is for a Motorola Xoom Tablet that I've had for a long while now.
I did a root using Root Genius. All seemed well so I loaded up the TWRP Root Manager app and attempted to install a recovery. It came back with an odd error message, which I unfortunately don't remember. I rebooted and now it consistently gives me the following message every time I reboot it:
Failed Image SOS 0x0002
Starting RSD Mode 0
OneWire: Charger is not connected or battery is not being charged...
Battery charge level 100%
I've gone through the one click recovery pages from xoomforums, but the device is not connected.
Any hope of recovering from this amazingly brain dead error?
Thanks
Chris
Got it resolved. Did a hard reset which allowed me to get it into fastboot mode. I then unlocked it which reset it and it's booting normally now.
cheers
Chris
Okay, more fun.
I managed to get the TWRP BigPart recovery installed. Going through some testing, it does indicate that the big part partition has been created.
Initially I installed the Lollipop ROM from Schisu. Upon reboot it would display the boot icon and go no further.
I then flashed the KitKat ROB from Schisu. Same issue.
Doing some spelunking around in TWRP indicates that it cannot mount the /cache folder which seems to be an issue.
If nothing else, I would like to get back to a stock ROM and then start this procedure all over again, but am unable to do that as the tablet becomes unresponsive in bootloader mode.
Help?
Thanks
Chris
Hi all! I have exhausted every avenue I can think of, with now hitting a roadblock attempting to repartition the device.
I took this phone to get its physical structure repaired as well as the screen. It took them 6 hours. When I got the phone back they said the "software crashed" and that they attempted firmware flashes to no avail.
The phone is in a constant Boot Loop. It will sit on the Samsung splash screen for a minute, go to a blue screen which tells me it is installing a system update, then an Android figure comes up saying Error. It does this over and over again. I hit the power and volume up key to quickly look at the commands it was throwing out and saw it was unable to access certain directories which I assume is the reason for the failure.
So I reflashed this phone with my relevant firmware using Odin. No firmware or combination of files and methods has brought this phone back.
I was hoping for some help with this project. I want to resurrect this phone, it's a great phone. I would love the satisfaction of doing it myself than at a store.
lexlex121 said:
Hi all! I have exhausted every avenue I can think of, with now hitting a roadblock attempting to repartition the device.
I took this phone to get its physical structure repaired as well as the screen. It took them 6 hours. When I got the phone back they said the "software crashed" and that they attempted firmware flashes to no avail.
The phone is in a constant Boot Loop. It will sit on the Samsung splash screen for a minute, go to a blue screen which tells me it is installing a system update, then an Android figure comes up saying Error. It does this over and over again. I hit the power and volume up key to quickly look at the commands it was throwing out and saw it was unable to access certain directories which I assume is the reason for the failure.
So I reflashed this phone with my relevant firmware using Odin. No firmware or combination of files and methods has brought this phone back.
I was hoping for some help with this project. I want to resurrect this phone, it's a great phone. I would love the satisfaction of doing it myself than at a store.
Click to expand...
Click to collapse
Sometimes after flashing via Odin, it is necessary to boot into stock recovery and factory reset then wipe cache partition then reboot. This doesn't always solve bootloop after flashing via Odin but it is a common solution.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Sometimes after flashing via Odin, it is necessary to boot into stock recovery and factory reset then wipe cache partition then reboot. This doesn't always solve bootloop after flashing via Odin but it is a common solution.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I don't understand how to get into recovery mode. The phone, when the charger plugs in, attempts to boot all the time.
I know the Recovery mode key combo but I have no idea to power off this phone. I've let the battery run.