Related
Hello, all. I hope someone can help me with my SGH-T959W. Right now I'm at the point where the phone has CWM installed, but will only boot into recovery no matter what I do. I've followed the N00b guide to Flashing/Fixing the SGS4G, but clearly I'm missing something.
I tried to follow the Windows-based procedure for the SGH-T959W, but was unable to get version 1.40 to execute, and was unable to locate version 1.31.
So, given that the SGH-T959W and SGH-T959V are the same phone except for the bootloader, I tried the Java-based Stock KJ-6 + Root. The first time I tried it, the upload failed after the PIT, and the phone was no longer able to boot into anything other than download mode. I eventually managed to get it to the point where it tried to flash the modem, but I was never able to get the modem to flash successfully. I tried both under Windows and Linux, using two different PCs and every USB cable I could find, since I know those tend to be dodgy. Still, I've never gotten past flashing the modem, though sometimes it's done worse.
But at this point, I had a phone that would dutifully boot into CWM, so I could change strategy anyway. So I grabbed the unofficial Cyanogenmod 10.1, copied it to the root of the SD card, and tried to load that via CWM. It failed the hardware check.
That's problem #1. Is it possible to modify Cyanogenmod to check for the 959W instead of only the 959V?
Now, problem #2. I decided to give Slim ICS a whirl, since it's light on requirements and a 512MB/1GHz device would probably appreciate a lighter load. The two packages claim to install, but the progress bar never reaches 100%, and when I try to boot the phone, it just boots into CWM. It's a newer version of CWM now, and the startup logo is different, so something worked, but clearly not everything.
When installing, I did mount UMMU, factory reset, wipe the cache and the Davlik cache, mount UMMU, install, then fix perms. But I still get that loop back to CWM.
So something critical didn’t take, however many times I tried (I've lost count, but I think I'm going on 10), and I don't know the architecture well enough to know where to start looking. I'm pretty comfortable with other operating systems, but this is only the second Android device I've tried to customize.
I suspect I can’t solve any other problem until I solve problem #2, regardless of which distro I end up wanting to run.
Sorry for the long-winded post, but I figured the more questions I answered up front, the better the chances of fixing this would be.
Thanks for any help you're willing to offer a n00b.
Dave F.
I think what you were doing with heimdall is the way to go except the t959w doesn't like modems and I think there's some way to leave out the modem part but eh.. I'm not that well versed. Anyway here's a link that may or may not be relevant
http://forum.xda-developers.com/showthread.php?t=1956025
Please read forum rules before posting.
Questions and request for assistance go in the Q&A section.
Thread has been moved.
Thank you for your future attention to this.
Have a great day!
dfarquhar said:
Hello, all. I hope someone can help me with my SGH-T959W. Right now I'm at the point where the phone has CWM installed, but will only boot into recovery no matter what I do. I've followed the N00b guide to Flashing/Fixing the SGS4G, but clearly I'm missing something.
I tried to follow the Windows-based procedure for the SGH-T959W, but was unable to get version 1.40 to execute, and was unable to locate version 1.31.
Click to expand...
Click to collapse
Look here for 1.3.1.
dfarquhar said:
So, given that the SGH-T959W and SGH-T959V are the same phone except for the bootloader, I tried the Java-based Stock KJ-6 + Root. The first time I tried it, the upload failed after the PIT, and the phone was no longer able to boot into anything other than download mode. I eventually managed to get it to the point where it tried to flash the modem, but I was never able to get the modem to flash successfully. I tried both under Windows and Linux, using two different PCs and every USB cable I could find, since I know those tend to be dodgy. Still, I've never gotten past flashing the modem, though sometimes it's done worse.
But at this point, I had a phone that would dutifully boot into CWM, so I could change strategy anyway. So I grabbed the unofficial Cyanogenmod 10.1, copied it to the root of the SD card, and tried to load that via CWM. It failed the hardware check.
That's problem #1. Is it possible to modify Cyanogenmod to check for the 959W instead of only the 959V?
Click to expand...
Click to collapse
Nope, not a CWM issue. Ever since TeamAcid and I started on CM9 (and I believe the last few CM7 builds) added support for T959W. Almost everyone (thankfully! ) has kanged those device trees and also support T959W. I'm sure other T959W users will chime in to tell you that 97% of all roms here work on T959W. (GB and forward)
dfarquhar said:
Now, problem #2. I decided to give Slim ICS a whirl, since it's light on requirements and a 512MB/1GHz device would probably appreciate a lighter load. The two packages claim to install, but the progress bar never reaches 100%, and when I try to boot the phone, it just boots into CWM. It's a newer version of CWM now, and the startup logo is different, so something worked, but clearly not everything.
When installing, I did mount UMMU, factory reset, wipe the cache and the Davlik cache, mount UMMU, install, then fix perms. But I still get that loop back to CWM.
Click to expand...
Click to collapse
Crazy mount setups shouldn't matter anymore. That was an oldschool Froyo/Early GB thing. Almost all new CWM install scripts do the right thing now.
dfarquhar said:
So something critical didn’t take, however many times I tried (I've lost count, but I think I'm going on 10), and I don't know the architecture well enough to know where to start looking. I'm pretty comfortable with other operating systems, but this is only the second Android device I've tried to customize.
I suspect I can’t solve any other problem until I solve problem #2, regardless of which distro I end up wanting to run.
Sorry for the long-winded post, but I figured the more questions I answered up front, the better the chances of fixing this would be.
Thanks for any help you're willing to offer a n00b.
Dave F.
Click to expand...
Click to collapse
I like the long posts! Especially when then they contain more detail for me to help you figure out your problem with. I'm also partial to the short posts that include logs!
TwitchyEye said:
I think what you were doing with heimdall is the way to go except the t959w doesn't like modems and I think there's some way to leave out the modem part but eh.. I'm not that well versed. Anyway here's a link that may or may not be relevant
http://forum.xda-developers.com/showthread.php?t=1956025
Click to expand...
Click to collapse
@TwitchyEye you're right That is the heimdall oneclick that should be used.
@dfarquhar I think using the heimdall oneclick that @getochkn made should be the right path for you. Make sure you use the right version of heimdall. Make sure you completely remove the old version (software and drivers), use zdiag to make absolutely sure!
If all else fails, post here again! (maybe with logs )
Thanks everyone. I grabbed v 1.3.1, so I'm getting ready to try it now.
If anything goes wrong, I'll look into where the logs are stored and how to retrieve them, and I'll be back. Assuming I can't use the logs to figure it out on my own of course.
dfarquhar said:
Thanks everyone. I grabbed v 1.3.1, so I'm getting ready to try it now.
If anything goes wrong, I'll look into where the logs are stored and how to retrieve them, and I'll be back. Assuming I can't use the logs to figure it out on my own of course.
Click to expand...
Click to collapse
Sometimes, it's just the output you see on your screen is a good enough log
bhundven said:
Sometimes, it's just the output you see on your screen is a good enough log
Click to expand...
Click to collapse
Got it working! Heimdall 1.3.1 was the key. I then turned around and flashed Slim ICS since I had it on the SD card already, and it worked. I'm debating whether to move on to Slim Bean, but maybe I need to leave well enough alone for a few days now that I have a working phone.
Thanks again,
Dave
Hey folks I'm looking for ideas to unbrick my OPO which is permanently stuck in a boot loop. It all began last Friday while flashing the lastest CM nightly and gapps. The flash executed successfully then entered a boot loop that refuses to be resolved. I've tried formatting and wiping all pertinent partitions including /persistent, fastboot flashing different version stock images, different radios... I don't know what else to try short of j-tag to rectify. Any and all advice appreciated. TIA
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Feb. 18th, 2016 Edit:
Well I'm happy to announce that after nearly 5 months of trying different tactics I was finally able to get my handset up and running this weekend.
The technique I used was to first flash the new official Oxygen OS following the directions from the oneplus forums. From there I was able to boot-up for the first time in months, but had no connectivity. I went to settings and saw I had no IMEI showing. Realizing this, I tried using the technique Heisenberg suggested below in this thread, but again I had no success.
Then I tried the instructions in this thread (which I had tried previously with no success) http://forum.xda-developers.com/oneplus-one/general/guide-efs-partitions-how-to-lost-t3307793 and viola! I got my radio back. It took me several attempts to get bluetooth and wifi back working, with rebooting in between, but alas I was able to get all fully functioning again.
Then I re-rooted and reinstalled TWRP (unofficial 3.0), backed up everything (including firmware and EFS partitions), then proceeded to flash the latest CM snapshot, then eventually the latest CM-12.1 unofficial CAF Sultanxda that I'm now happily running!!!
Thanks again to everyone who posted trying to help me get my handset working again. Now I have two fully functioning OPO's and am very happy!!!
Odysseus1962 said:
Hey folks I'm looking for ideas to unbrick my OPO which is permanently stuck in a boot loop. It all began last Friday while flashing the lastest CM nightly and gapps. The flash executed successfully then entered a boot loop that refuses to be resolved. I've tried formatting and wiping all pertinent partitions including /persistent, fastboot flashing different version stock images, different radios... I don't know what else to try short of j-tag to rectify. Any and all advice appreciated. TIA
Click to expand...
Click to collapse
You might have a corrupt persist partition. Download this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/view?usp=docslist_api
Then:
Code:
fastboot erase persist
fastboot flash persist persist.img
Heisenberg said:
You might have a corrupt persist partition. Download this:
https://drive.google.com/file/d/0B98G0KTJwnBFUnJCNldodGs2dE0/view?usp=docslist_api
Then:
Code:
fastboot erase persist
fastboot flash persist persist.img
Click to expand...
Click to collapse
Thanks it's greatly appreciated. I had tried this earlier with a download from another link, but tried again with your persist.img and unfortunately, it too didn't work.
This scenario that I'm currently experiencing is eerily like a common problem we had with the HD2, where over time and use NAND cells would get "stuck" and go bad. If the bad cells were located in the portion of the NAND allocated for the /system partition an unresolvable boot loop would result. To work around this developers added tools to HD2 recoveries that would allow reordering and resizing partitions so the /system partition would wholly reside in a contiguous healthy part of the NAND.
I'm wondering now if the hundreds of times I've flashed my beloved OPO has taken its toll, and created a similar situation where bad NAND cells now reside within the boundaries of my /system partition?
Anyone familiar or aware of any tools I can use from either recovery or fastboot that would allow checking the integrity of the NAND to determine if this is indeed the cause of my current dilemma or rule it out?
Again, any help or suggestions would be greatly appreciated. TIA
Odysseus1962 said:
Thanks it's greatly appreciated. I had tried this earlier with a download from another link, but tried again with your persist.img and unfortunately, it too didn't work.
This scenario that I'm currently experiencing is eerily like a common problem we had with the HD2, where over time and use NAND cells would get "stuck" and go bad. If the bad cells were located in the portion of the NAND allocated for the /system partition an unresolvable boot loop would result. To work around this developers added tools to HD2 recoveries that would allow reordering and resizing partitions so the /system partition would wholly reside in a contiguous healthy part of the NAND.
I'm wondering now if the hundreds of times I've flashed my beloved OPO has taken its toll, and created a similar situation where bad NAND cells now reside within the boundaries of my /system partition?
Anyone familiar or aware of any tools I can use from either recovery or fastboot that would allow checking the integrity of the NAND to determine if this is indeed the cause of my current dilemma or rule it out?
Again, any help or suggestions would be greatly appreciated. TIA
Click to expand...
Click to collapse
If that is the case it's the first time I've heard of it happening on this device. TWRP may have a feature like that but I'm not sure. Other than that I'm unaware of any tools of this nature.
Heisenberg said:
If that is the case it's the first time I've heard of it happening on this device. TWRP may have a feature like that but I'm not sure. Other than that I'm unaware of any tools of this nature.
Click to expand...
Click to collapse
Thanks again for responding. I'm just at my wit's end with this and out of ideas, which is why I even suggested the hypothesis in my previous post. Fortunately, I have another OPO backup, so I still have a phone, but it too is problematic. Whenever the capacitive buttons are activated I experience phantom touches of the menu button, and usually at the most inopportune time. OPO customer service is nonexistent and have insisted since I received the defective device that my problems are firmware related and refuse to investigate further. Nearly a year later and numerous updates the problem is still unresolved, which is why I took the device out of service and made it my spare.
Now with my daily driver malfunctioning I'm nearly ready to throw in the towel and give up on Oneplus altogether and get another device from a more reputable manufacturer. They've sent me several OP2 invites, that I've declined using. My horrible customer service experience with them and now two faulty devices leads me to never want to purchase their products again, no matter how affordable or feature packed they may be.
Anyhow, as previously posted, if anyone has ideas to resolve my boot loop, please chime in. TIA
Is it possible that my boot looping is being caused by a corrupt iemi partition? If so, I never backed it up, but have the number readily available from the packaging my OPO shipped in. I also have my backup OPO that I'm currently using, is it possible to clone that partition?
Any ideas on how to recover or clone my from my other device would be greatly appreciated. Basically anything to help get my daily driver back up and running would be a heaven send. TIA
Odysseus1962 said:
Is it possible that my boot looping is being caused by a corrupt iemi partition? If so, I never backed it up, but have the number readily available from the packaging my OPO shipped in. I also have my backup OPO that I'm currently using, is it possible to clone that partition?
Any ideas on how to recover or clone my from my other device would be greatly appreciated. Basically anything to help get my daily driver back up and running would be a heaven send. TIA
Click to expand...
Click to collapse
A corrupt EFS partition doesn't cause this to happen, the phone will still boot but will have no network because it has no baseband and no IMEI.
Still trying to resovle. I refuse to give up!
I'm still looking for help in resolving this bootloop issue. I refuse to give up as long as there is the slightest hope of getting it back up and working.
Being a longtime Linux user I know that by default there must be some type of logs generated in the boot-up process. I'm thinking that perhaps if I can extract the log(s) and post them maybe someone can point me in the right direction towards resolving this issue. I've noticed that after flashing back the stock recovery there is a section which contains several logs. Which do I need, where do they reside, how can I extract them from my device, and how should I repost (them) here so they can be properly deciphered? TIA
Why don't you hard brick your phone and unbrick it by flashing ColorOS ? Not joking .. You can try that .. anyhow you're facing a soft brick ..
Tried flashing with twrp 2.8.6 build instead of 2.8.7?
Sanjiv Kumar said:
Why don't you hard brick your phone and unbrick it by flashing ColorOS ? Not joking .. You can try that .. anyhow you're facing a soft brick ..
Click to expand...
Click to collapse
I thought about this as a possible solution, but the "hard unbricking guide" only contains solutions to use with various versions of Windows. Unfortunately, I have no access to a Windows computer (at least one that someone would allow me to use for the purpose of unbricking). I run Linux on my laptop and desktop, specifically Gentoo Linux ~AMD64. I haven't run Windows on any of my machines for over a decade. For the extremely rare instances where I need to use a Windows application I run it on WINE in Linux.
If someone knows how to run the ColorOS unbricking procedure on Linux, I'd be happy to try it out.
NoobInToto said:
Tried flashing with twrp 2.8.6 build instead of 2.8.7?
Click to expand...
Click to collapse
This device was already running TWRP-2.8.6 prior to getting stuck in the bootloop. Since then I've tried every version above 2.8.4, I've tried Phil's, and CWM and both the CyanogenOS and CM recoveries. All with the same result.
Bumb to bring back up this thread, now that I've resolved my problems. Hopefully it will help someone else who may be having similar issues.
First a few disclaimers to explain why I'm here.
- My secondary intention with this question is finding some answer as generic as possible to also help other people. Of course my primary intention is fixing my own issue, but the biggest part of it from what I can tell in the past 8 hours have been finding ROM files. All links are broken, except for 4.1.2 and none of those worked for me. In fact, they bricked my phone pretty hard.
- I'm on a mac. It's a nightmare finding tools for the mac, but I doubt any of them would really be any use for my case, one reason why I didn't even bother going for a windows vm. Another one is I'm traumatised by installing and running VMs. Finally this is for the challenge and learning a bit more.
- I've being trying to fix this through lots of research in the past 8 hours and I do know a few bits about going around and doing things (so sad this guide had no repercussion so far). But clearly, I'm dumb enough to brick my phone twice with no backups. At least could figure it out the first time (I had more time in hands as well). Please consider this. This means I've tried a lot of stuff you may wanted to advise, but it also mean I may have missed something obvious in the middle.
Okay...
By "bricked" I mean:
1. I can't go through the same process I did before to flash any CM image. CWM won't flash CM11 and CM12 recovery complains my bootloader isn't 4.4.
2. Both CWM and twrp recoveries should allow touch. None work, so I an't use twrp.
3. Battery keeps getting low and I've got no clue how to charge it to full again or even see how much it is at without installing twrp, which keeps getting uninstalled randomly at reboots, despite all of this topic about a solution. `fastboot getvar battery-voltage` doesn't show it. The mac script (which I was about to write myself based on op) also doesn't seem to help. In my case, I've removed the `./fastboot` because I've got it on my shell path.
I believe (1) happened, as I said on the disclaimer, right after I've flashed one of those 4.1.2 ROMs. By "flashed" I mean running the BAT file which mostly works on mac. ECHO of course wouldn't show the messages of progress there, but all fastboot commands do run.
And I also believe if only I could find 4.4 stock ROM files they might work or, at least, bring bootloader back to where it was so I could install CM12 again. And as far as I could notice without having Windows to try, no windows tool would really help here. That RSD Lite for instance, looks like it's just a GUI to run fastboot commands.
Above ALL
I just wanted to find a ROM stock file which I could fastboot flash into xt925 to reset it as hard as possible from zero and that the link will probably not break in the future for whoever may need it.
I figured THIS shouldn't be too hard to find, even for mac only, but it has been.
PS: Being able to fix the battery thing is also very important and quite a relevant follow up on the question! Right now I'm stuck with a ROM file that might work, but got no battery to try! ( 10 hours debugging now... )
only one stock kitkat rom for XT925 ! i'll upload this for you !
You know, if this works I'll have to, at least, go through some of your 187 posts and find a dozen or so to thank you way more than once!
I've now downloaded [this one](http://forum.xda-developers.com/showpost.php?p=63163078&postcount=6), which [he also posted again later on](http://forum.xda-developers.com/showpost.php?p=63272842&postcount=2), hoping it will do it! If it does, I'll try to upload in this post, as it looks like XDA hosted files last for much longer than anything else.
Only problem for flashing anything now is I can't seem to get enough battery!
Hello everyone, I hope I'm writing in the right section.
I'll go straight to the issue: after finally deciding to install a custom rom on my device (HUAWEI GX8), i decided to opt for this one: https://forum.xda-developers.com/moto-g4-plus/development/rom-aospextended-rom-v3-0-t3537792
The first problem i had to face was the "ERROR:7" (so the rom seemed to be made for a different phone than mine) that occured while installing the rom in the twrp, but being that the rom was specifically made for my phone I followed this guide: https://www.youtube.com/watch?v=wed03948gcg and fixed the issue, resulting in a perfect installation... or so I thought.
After rebooting, the phone didn't start the os but was stuck in the twrp (I tried rebooting multiple times and in different ways of course).
Being that I had made a backup before installing the new rom, I decided to restore that backup from the twrp... but still the phone is stuck in the twrp and I don't know what to do :crying:
I hope somebody can help me because I'm starting to panicking.
Cheers in advance.
PS: I'm a complete newb so this was the first time I installed a custom rom, I tried searching for this problem online but couldn't find a solution that fitted me. I hope I won't ask too many stupid questions.
SlimeAndroid said:
Hello everyone, I hope I'm writing in the right section.
I'll go straight to the issue: after finally deciding to install a custom rom on my device (HUAWEI GX8), i decided to opt for this one: https://forum.xda-developers.com/moto-g4-plus/development/rom-aospextended-rom-v3-0-t3537792
The first problem i had to face was the "ERROR:7" (so the rom seemed to be made for a different phone than mine) that occured while installing the rom in the twrp, but being that the rom was specifically made for my phone I followed this guide: https://www.youtube.com/watch?v=wed03948gcg and fixed the issue, resulting in a perfect installation... or so I thought.
After rebooting, the phone didn't start the os but was stuck in the twrp (I tried rebooting multiple times and in different ways of course).
Being that I had made a backup before installing the new rom, I decided to restore that backup from the twrp... but still the phone is stuck in the twrp and I don't know what to do :crying:
I hope somebody can help me because I'm starting to panicking.
Cheers in advance.
PS: I'm a complete newb so this was the first time I installed a custom rom, I tried searching for this problem online but couldn't find a solution that fitted me. I hope I won't ask too many stupid questions.
Click to expand...
Click to collapse
The ROM that you flashed was NOT made specifically for your device, you have HUAWEI GX8, the ROM was made for Moto G4 Plus. You would have know this if you had looked at the forum it was posted in. It was posted in in the Moto G4 forum, not in a Huawei forum.
The "fix" that you used didn't help.it successfully flash, it only help you "force" the ROM to flash. You bypassed a safety measure that was designed to keep you from flashing the wrong thing, now you're dealing with the results of forcing it to flash on a device it wasn't meant for.
Learn to pay attention to what you are reading.
You need to flash your stock firmware to fix this.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
The ROM that you flashed was NOT made specifically for your device, you have HUAWEI GX8, the ROM was made for Moto G4 Plus. You would have know this if you had looked at the forum it was posted in. It was posted in in the Moto G4 forum, not in a Huawei forum.
Learn to pay attention to what you are reading.
You need to flash your stock firmware to fix this.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I'm sorry I may have linked the wrong page, either way on the website of the rom I downloaded the right thing, I'm sure about it because I checked it multiple times (the error I made in writing the post may be cause by me panicking, sorry :crying: ).
While waiting for answers I installed a different twrp and it WORKS! I'm so happy I could cry. Thank you nonetheless for your help (Still dunno what the problem was though xD)
@SlimeAndroid as you installed ROM of different phone, it might not get installed as ROM zip contains script for Mobile verification.
I assume you had wiped /system and after installation of wrong ROM you rebooted your phone without reading if TWRP said you don't have any OS installed or what. (That means you have ran without any OS, that may be reason why you stuck with TWRP.)
But after Restoring Backup of Working ROM, it should boot your device, but it doesn't.
We (on G4 plus) have faced issue: when phone start, it always goes to TWRP/recovery instead of booting to system.
Are you facing similar ?
Solution for this problem was to clear bootloader data, by using fastboot commands (i assume you know how to do, otherwise ask for better explanation )
Run this two commands from Comand Prompt
-> fastboot oem fb_mode_set
-> fastboot oem fb_mode_clear
This worked for us. You can try, if doesn't work then flash Stock ROM.
____Mdd said:
@SlimeAndroid as you installed ROM of different phone, it might not get installed as ROM zip contains script for Mobile verification.
I assume you had wiped /system and after installation of wrong ROM you rebooted your phone without reading if TWRP said you don't have any OS installed or what. (That means you have ran without any OS, that may be reason why you stuck with TWRP.)
But after Restoring Backup of Working ROM, it should boot your device, but it doesn't.
We (on G4 plus) have faced issue: when phone start, it always goes to TWRP/recovery instead of booting to system.
Are you facing similar ?
Solution for this problem was to clear bootloader data, by using fastboot commands (i assume you know how to do, otherwise ask for better explanation )
Run this two commands from Comand Prompt
-> fastboot oem fb_mode_set
-> fastboot oem fb_mode_clear
This worked for us. You can try, if doesn't work then flash Stock ROM.
Click to expand...
Click to collapse
If you read the post above yours, you'll see they solved the issue.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
You always have to make sure the download is for your model of phone(settings -about) and always make sure the download has properly downloaded and I use md5 checksum as this verifies the download is not courupt.
Sent from my iPhone using Tapatalk
Ok, so there was a thread on here for this issue, but it has been dead for 5 years so I hope it's ok I open this new thread.
I have been given a Samsung Tab 2 GT-P5110 by a colleague of mine. At some point in time he managed to corrupt the firmware to get the black screen of death 'firmware has encountered a problem.......'. This will not have been from flashing ROMs or attempting to root the device (he's an elderly guy, who recently asked me for help resetting his Google passwords, so rooting is well beyond his expertise). I first thought this won't be an issue, I'll hook it up to Odin, flash a recovery, stick it in download mode and then flash a new ROM...... However this failed, Odin confirming the process was unsuccessful. I understand this may be because the corruption is seated deeper than just the level of flashing a new ROM and have read flashing a new kernel may go deep enough to make progress, however, I have only ever used Odin for flashing ROMs so this is all new to me.
I would be very appreciative if someone was able to point me in the right direction, I have found some kernels to download which I think would be compatible, but I'm a little foggy on the steps I should take. Alternatively, someone may know another route to go down, I am also not afraid to open this little guy up and do some DIY surgery if needs be, after all I didn't buy the thing so I have nothing to lose.
Any suggestions would be great and if you want some more info please feel free to ask.
Thanks in advance.
elboobio said:
Ok, so there was a thread on here for this issue, but it has been dead for 5 years so I hope it's ok I open this new thread.
I have been given a Samsung Tab 2 GT-P5110 by a colleague of mine. At some point in time he managed to corrupt the firmware to get the black screen of death 'firmware has encountered a problem.......'. This will not have been from flashing ROMs or attempting to root the device (he's an elderly guy, who recently asked me for help resetting his Google passwords, so rooting is well beyond his expertise). I first thought this won't be an issue, I'll hook it up to Odin, flash a recovery, stick it in download mode and then flash a new ROM...... However this failed, Odin confirming the process was unsuccessful. I understand this may be because the corruption is seated deeper than just the level of flashing a new ROM and have read flashing a new kernel may go deep enough to make progress, however, I have only ever used Odin for flashing ROMs so this is all new to me.
I would be very appreciative if someone was able to point me in the right direction, I have found some kernels to download which I think would be compatible, but I'm a little foggy on the steps I should take. Alternatively, someone may know another route to go down, I am also not afraid to open this little guy up and do some DIY surgery if needs be, after all I didn't buy the thing so I have nothing to lose.
Any suggestions would be great and if you want some more info please feel free to ask.
Thanks in advance.
Click to expand...
Click to collapse
flash a custom recovery, and install this, https://builds.unlegacy-android.org/aosp-4.4/espresso/ua_espresso-4.4.4-20171105172717.zip
Thanks for the reply. I have attempted to flash a recovery, however every one I've tried fails and tells me 'NAND write failed'. I tried the TWRP recovery and philztouch. You don't have a link to a recovery you think might work? I'm pretty sure I've been using recoveries that should work, but you never know.