No, I'm not crazy! I'm actually attempting to use a home made program to see if I can unbrick it. Does anyone know how I could do this? Thanks!
Don't know sorry but it's so fun
We spend so much time to avoid that happen ...
Sent with my GT-P7500 CM10
corybantic said:
No, I'm not crazy! I'm actually attempting to use a home made program to see if I can unbrick it. Does anyone know how I could do this? Thanks!
Click to expand...
Click to collapse
Try flashing recovery in odin and disconnect it in the middle
...
Flash a rom with odin and use repartition.
This will brick your device.
Sent from my GT-P7500 using XDA Premium HD app
Flash a rom from another device works, too.
corybantic said:
No, I'm not crazy! I'm actually attempting to use a home made program to see if I can unbrick it. Does anyone know how I could do this? Thanks!
Click to expand...
Click to collapse
Well, the other ones pretty much covered your query. I want to ask what happens if your program fails? And you mean soft or hard brick?
Sent from my amazing 10.1 galaxy tab
Like all the folks before me, flashing wrong rom from other device probably would brick it... BUT to really, really brick it messing up the bootloader is always a good way to go.
Can you short it out?
Ooops,I guess I should've been clearer! I'm trying to brick it without rooting it, i.e., perhaps some code that I could input at the bootloader?
Panos_dm said:
Well, the other ones pretty much covered your query. I want to ask what happens if your program fails? And you mean soft or hard brick?
Sent from my amazing 10.1 galaxy tab
Click to expand...
Click to collapse
Well if it fails, then I guess I gotta try - or come up with - a different program. The thing is, I had two SGT 10.1, one recently went back to Best Buy after the ICS update started freezing up my internet (not tripping tho, I was able to get a raincheck for the Note 10.1! Good thing I got the Product Replacement Plan!: victory, so I have literally a spare SGT 10.1 to mess around with. I've already rooted it and flashed different roms as well as unrooted it back to factory settings. So, to be honest, I simply have a tablet for having a tablet's sake right now.
I'm actually trying to "hard" brick it. The thing is my little program works on a "soft" brick palette so it has (usually) been able to unbrick an inadvertantly bricked phone as well as the SGT 10.1. I'm trying to see if I can brick it without rooting it to see if I can resuscitate it back to working condition.
"hard"brick it means you'd have to produce an hardware faillure, You wouldn't be able to fix an hardware failure unless you change the part that failed.
IE: Your memory chip has fried, your CPU overheated FUBAR, this kinda things
Well mine is pretty screwed. Wish I knew how it happened so I can tell you, but I don't. Yesterday I watched a movie on it and put it on the table. Later when I wanted to use it, nothing happens.
If I plug it into my PC I can get it into APX mode, but thats all. The backlight doesn't even go on. On NVflash I get the rcm version = 0x4, which means I got a locked bootloader.
When on charge, also nothing happens. The camera flash just flashed about every 2 seconds. Same thing when I keep the power button held in.
I could try your app for you on mine if you want...
Hey folks! I have an Acer A500 that I have been working on "with" dibb_nz over the past week. I have no idea what was on it originally, it came to me nearly dead. After a TON of attempts and hard work from dibb, I now have Skrilax's bootloader and recovery installed. I flashed CM10-10 Flex_V6 ROM from Civato onto the device successfully. Here is the problem: no matter how I boot up, it either goes directly into "Power off - Shutting down" then vibrates and blanks out or, after a fresh install, it will say "Android is upgrading", "Optimizing apps", "Starting Apps", then on to the Power Off-shutting down thing.
Does anyone have any clue what may be going on here? I have tried earlier ROMS, all from Civato, but with the same Power OFF result.
Any help would be MUCH appreciated!
Thanks in advance,
Sharkguy
hey sharkguy, I've been combinf forums and threads with no joy at all, the only thing I haven't checked is the rom thread, might pay you to look thru that, just in case its rom related ( I doubt it really, but there maybe other reports such as yours ) If I ever come across something I'll be sure to get back to you, good luck m8
Calling @Moscow Desire---are you out there Mr Moscow?? Ever heard of something like this before, my friend, very strange....Hope you are well MD its been awhile
dibb_nz said:
hey sharkguy, I've been combinf forums and threads with no joy at all, the only thing I haven't checked is the rom thread, might pay you to look thru that, just in case its rom related ( I doubt it really, but there maybe other reports such as yours ) If I ever come across something I'll be sure to get back to you, good luck m8
Calling @Moscow Desire---are you out there Mr Moscow?? Ever heard of something like this before, my friend, very strange....Hope you are well MD its been awhile
Click to expand...
Click to collapse
Hey Dibb! Offhand, I think it may be the old power part that used to be flashed with stock ROMs. Forget what its actually called. Typically we removed this from the install as its generally not needed. That's a guess, but am at work for the night so can't check my stuff. Could explain the shutdown. But if it shuts down when updating the apps, then its probably bad memory partition.
But I'll lean more towards the power part. Will have to check a stock ICS ROM. Might need to make a separate flash install just for it. It it would boot to the display and it had horrible display and battery issues then that would be it.
Well, that sounds complicated. I should have the new battery by the weekend so let me at least try that before anyone gets all technical. Unfortunately I dont know anyone with another a500 to test batteries...
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Moscow Desire said:
Hey Dibb! Offhand, I think it may be the old power part that used to be flashed with stock ROMs. Forget what its actually called. Typically we removed this from the install as its generally not needed. That's a guess, but am at work for the night so can't check my stuff. Could explain the shutdown. But if it shuts down when updating the apps, then its probably bad memory partition.
But I'll lean more towards the power part. Will have to check a stock ICS ROM. Might need to make a separate flash install just for it. It it would boot to the display and it had horrible display and battery issues then that would be it.
Click to expand...
Click to collapse
Hey MD good to see u my friend
oh, the eec thing? Rings a bell...
The bad memory partition, do you mean the memory chip itself or just the partition.
I've just never heard of the faulty chip causing a spontaneous shut down, sure has me beat....and I Hate that, lol
But thanks for the response MD, if you can offer any solution from your archives of knowledge and wisdom, I know someone who'd be forever grateful
Have a great day all!!
rgds Donna
Yeah Dib, the eec thing. Just couldn't remember. Usually we just removed that command from the install script as usually once it was flashed at the factory, rarely did you ever have to flash it again. I will have to look and see in the next couple of days. Worth a shot though. Might be able to put it in a CWM install.
Oh, forgot to add @sharkguy
As with a damaged partition, if the memory got hosed in that particular partition, whichever, there's not a whole lot that can be done. Could try running babsector, but not sure if it would fix it or not. There's been success running it before, but only about 30% as I can tell. Devblks can get physically damaged. Usually the partitions are large enough to mark the bad spots as bad, and still be able to install things. That's what babsector did I think as near as I can tell.
A faulty chip "could" cause a shutdown, especially if it couldn't create the dalvak which is kind of the next step when "starting applications" If I guess right, although I would think it would bootloop rather than shut down. As you say, I've never heard of a power off before, unless the eec was bad and it thinks the battery is dead.
I'm just curious if the OP has done a full format on internal memory via CWM? Before installing. Not the usual wipes, but going into advanced, and triggering the full format. I used it after running that CM stuff awhile back, as it messed up everything (lots of testing). Needed a clean sweep of the internal memory.
As you see, I am still around Just with being a senior mod, not a lot of time for messing with things.
I'm still leaning towards eec pwr. (I'm using beer logic at this point)
Bear with me on this. Let's say the eec got hosed somehow. It happens on occasion. And you install several custom roms, which of course don't have eec pwr in the install script as we removed it. Here's what I know.
1) Battery won't charge and is always going to shut down
2) No response on the touch screen if indeed the OS starts.
3. Tab shuts down after OS start.
So you see why I am leaning towards this.
MD
EDIT: The reason why we removed eec from the custom roms to begin with, primarily as it really wasn't needed, but it "could" cause an issue if the flash went bad. But considering the OP has UID and NVFlash, that isn't an issue now.
dibb_nz said:
Hey MD good to see u my friend
oh, the eec thing? Rings a bell...
The bad memory partition, do you mean the memory chip itself or just the partition.
I've just never heard of the faulty chip causing a spontaneous shut down, sure has me beat....and I Hate that, lol
But thanks for the response MD, if you can offer any solution from your archives of knowledge and wisdom, I know someone who'd be forever grateful
Have a great day all!!
rgds Donna
Click to expand...
Click to collapse
Hey MD, thanks for thr insight on my issue. I worked closely with Dibb_nz for close to a week. I am not entirely sure if I did the wipe you mentioned, but believe me, if I could find a way to format, erase, wipe or clear memory I did. Everything you described as what you knew is correct with one exception: if it is relevant the touch screen works in recovery mode.
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
sharkguy said:
Hey MD, thanks for thr insight on my issue. I worked closely with Dibb_nz for close to a week. I am not entirely sure if I did the wipe you mentioned, but believe me, if I could find a way to format, erase, wipe or clear memory I did. Everything you described as what you knew is correct with one exception: if it is relevant the touch screen works in recovery mode.
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
Always works in recovery, as it is independent of the OS...
Righto. I figured it didnt matter in this case. But yes, the rest of the facts are as you understand them.
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
sharkguy said:
Hey MD, thanks for thr insight on my issue. I worked closely with Dibb_nz for close to a week. I am not entirely sure if I did the wipe you mentioned, but believe me, if I could find a way to format, erase, wipe or clear memory I did. Everything you described as what you knew is correct with one exception: if it is relevant the touch screen works in recovery mode.
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
The FULL wipes as stated in the guide m8 or via fastboot erase.
@Moscow Desire _bab sector was run and successfully, boot loader and recovery installed with no errors.
As far as the eec thing I do have a copy of that in my stash if that's any help, but no idea how to apply it????
Sent from my HTC_PN071 using Tapatalk
Well at this point I am open to anything. I just passed up on a steal of a deal on a Samsung Galaxy Tab 3 7" so im itching to know I made the right choice. I am at your mercy. Doesnt look like I will have that battery until saturday at the earliest, but so far all of the work I have done on it has been with AC power and has been successful.
Sent from my SGH-I317M using xda app-developers app
sharkguy said:
Well at this point I am open to anything. I just passed up on a steal of a deal on a Samsung Galaxy Tab 3 7" so im itching to know I made the right choice. I am at your mercy. Doesnt look like I will have that battery until saturday at the earliest, but so far all of the work I have done on it has been with AC power and has been successful.
Sent from my SGH-I317M using xda app-developers app
Click to expand...
Click to collapse
Well m8 I dunno if u made the right choice there, I guess only time will tell...there is this thread http://forum.xda-developers.com/showthread.php?t=2617196. I cannot recommend it but then my tab has never been in that state...and I'm not sure I could bring myself to put it in the oven lol...u nut wanna take a look at it any way
Sent from my HTC_PN071 using Tapatalk
Oh I've heard of ppl doing such things, but I'm luckily far mor fortunate than that. I am an electronics technician and have access to far for humane methods than an oven! Maybe I will see if I can still get the deal, then hack the a500 to pieces after geting the new battery in the mail. Lol
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
sharkguy said:
Oh I've heard of ppl doing such things, but I'm luckily far mor fortunate than that. I am an electronics technician and have access to far for humane methods than an oven! Maybe I will see if I can still get the deal, then hack the a500 to pieces after geting the new battery in the mail. Lol
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
Well, you'll be in your element then,lol...Yeh, your issue is rather unique...with babsector not returning any error its out of my area of expertise!!! But I do know that Acers build quality isn't the best....from power buttons falling out to the memory chip failure and their dodgy soldering techniques, i'm leaning towards a hardware fault 'somewhere'....
But then, it does seem strange the tab powers off during "updating apps" that points to software doesn't it???? Have look in the guide for fastboot commands (if you still have the unlocked bootloader on there) I'd erase all partitions, /system, /data, /cache etc....then run babsectot again to repartition -flash a rom and see what happens...or use tdv4 to do the same, but no rom flash needed for that as it comes with HC 3.2.1 rooted and cwm.
Anyways m8 keep us updated - and fingers crossed you end up with a positive resolution
rgds Donna
One of the last things I think I did was tdv4 without a rom flash. It still came up with the same issue. I did notice that when I took the battery out to charge on the equipment at work (closely monitored of course) to see if there was an issue with the charging circuit, that I could still do all of the same things as before with just the AC plugged in. No battery. This is why I bought a battery to try that out. The Galaxy 3 guy realized what a steal he was offering me and bumped up his price so it looks like I'm stuck woth the A500.
Thanks for the crossed fingers!!
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Well new battery us in and seems to charge just fine. In fact the tablet would not even attempt to power on before without AC so that is a plus. However, the same thing happens still. Boots up, and as soon as it enters the OS it gies straight to powering down.
What was the EEC thing you guys were discussing? Would it potentially help here?
Thanks again!
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Used all of the elements at my disposal at work to reflow the board without any change in the status of the tablet. Any ideas based on that EEC thing you guys discussed above?
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
sharkguy said:
Well new battery us in and seems to charge just fine. In fact the tablet would not even attempt to power on before without AC so that is a plus. However, the same thing happens still. Boots up, and as soon as it enters the OS it gies straight to powering down.
What was the EEC thing you guys were discussing? Would it potentially help here?
Thanks again!
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
sharkguy said:
Used all of the elements at my disposal at work to reflow the board without any change in the status of the tablet. Any ideas based on that EEC thing you guys discussed above?
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
Soz m8 been full on at work to even check emails let alone reply...phew!!!!
As MD pointed out above, the EEC file thing, devs have dealt with that particular issue, but b/c yours is a relatively unique issue I guess it can't be ruled out...
Have you managed to take a look at fastboot and using the erase command to delete EVERYTHING - at least u can be sure its as clean as can be, then using babsector with an appropriate rom and see what happens there.
In that "tab flu" thread there are links to another thread (somewhere) re: eec thing - If you find it can link it here in this thread and I'll track down the file -
Oh, just to be clear - when it boots into to the OS and powers off - is it completely shutting down i.e. power led is off or is it actually booting to apx mode, black screen power lite on...whats the chances of a vid so we can see exactly what it does???
rgds dibb
Sure I can video it for ya, but how should I link it? Can I link to YouTube on these forums?
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
sharkguy said:
Sure I can video it for ya, but how should I link it? Can I link to YouTube on these forums?
Sent from my SGH-I317M (Samsung Galaxy Note II) from Tapatalk
Click to expand...
Click to collapse
Ok, so new development, so to speak. As you can see from the crappy video I shot just now, I can boot the tablet into the start of the OS, but it hangs at Powering Down. The new part is that I had to manually shut it off, it did not do that itself this time. I showed you the power light (orange) and when I press it again, it does power on, but is still hung up on the same screen. I don't know if that helps any, but now you can see it. By the way, sorry it is upside down, it was the only way to show you the power button after it booted.
http://youtu.be/pG_efbq6DZg
I'm sorry for making this thread but i can't seem to find what im troubled for. And im pretty much a NOOB regarding this thing.. so please be understanding.. i have a samsung s4 sgh-i337 running mf3 4.2.2 (rooted) lately charging it took a lot of hours it took me 8 hours just to charge it from 5% to 100% i already closed all the background apps, wifi off, screen off, but still the same, so i think it must be the operating system i don't know if i just done something wrong or what, so I'm thinking to update my phone to the latest version (Kitkat) using samsung kies is it okay? because im rooted right now wouldn't it brick my phone? and does updating my phone correct or replace all the settings that i done wrong or deleted before? which is probably the cause of the slow charging? i really have no idea.. really noob here.. or is there any better way to resolve this? i hope someone can help me, and if there is links regarding answers to my question i would be happy if anyone could post it here.. thanks in advance..
Are you using the original charger? Does it charge faster if the device is off?
Sent from my Nexus 7 using XDA Premium 4 mobile app
cloverbits said:
I'm sorry for making this thread but i can't seem to find what im troubled for. And im pretty much a NOOB regarding this thing.. so please be understanding.. i have a samsung s4 sgh-i337 running mf3 4.2.2 (rooted) lately charging it took a lot of hours it took me 8 hours just to charge it from 5% to 100% i already closed all the background apps, wifi off, screen off, but still the same, so i think it must be the operating system i don't know if i just done something wrong or what, so I'm thinking to update my phone to the latest version (Kitkat) using samsung kies is it okay? because im rooted right now wouldn't it brick my phone? and does updating my phone correct or replace all the settings that i done wrong or deleted before? which is probably the cause of the slow charging? i really have no idea.. really noob here.. or is there any better way to resolve this? i hope someone can help me, and if there is links regarding answers to my question i would be happy if anyone could post it here.. thanks in advance..
Click to expand...
Click to collapse
Are you using the wall charger or the usb one? There's a big difference in charging rates of the two. If you want the official OTA update to Kit Kat 4.4.2, then you must be unrooted & all aps & files as original stock. Best & safest way is to Odin back to stock. Search Mf3 tar files on XDA.
http://forum.xda-developers.com/showthread.php?t=2616221
Red_81 said:
Are you using the original charger? Does it charge faster if the device is off?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i'm using the original charger, and i'm sure that the charger is not at fault because i tried it on my wife's phone and it worked great. i tried charging while the phone is off but still it really charge really slow..
John The Rhino said:
Are you using the wall charger or the usb one? There's a big difference in charging rates of the two. If you want the official OTA update to Kit Kat 4.4.2, then you must be unrooted & all aps & files as original stock. Best & safest way is to Odin back to stock. Search Mf3 tar files on XDA.
http://forum.xda-developers.com/showthread.php?t=2616221
Click to expand...
Click to collapse
i'm using the wall charger, at first it works really fine, then i noticed that it was charging slow, at first i thought that was normal, but now it is really slow. when i try to use it while charging it the battery drops rather than to increase because it is charging.. and btw thanks for the tip regarding updating to Kitkat i was about to try it using kies that could end up bad hehe. but is it wise to use stock? i have read other threads about using other roms. i don't know if i should use it too..
cloverbits said:
i'm using the wall charger, at first it works really fine, then i noticed that it was charging slow, at first i thought that was normal, but now it is really slow. when i try to use it while charging it the battery drops rather than to increase because it is charging.. and btw thanks for the tip regarding updating to Kitkat i was about to try it using kies that could end up bad hehe. but is it wise to use stock? i have read other threads about using other roms. i don't know if i should use it too..
Click to expand...
Click to collapse
I had to replace a charger that did exactly what yours is doing. New one is perfect. Difference is like night & day. Perhaps your battery is going? Go to an At&t store and have your phone & charger checked. The usual suspect for such problems is the charger. Start there. Be sure to read the guide before going all the way up to Kit Kat. Depends on what you want. if I were you I wouldn't update beyond MK2, which gives you 30+ JellyBean 4.3 roms & almost over 1/2 a dozen Kit Kat 4.4.2 roms.
Three mornings ago I woke up to find wifi couldn't start on my phone. Nothing I tried fixed it. It's a hardware issue. Verizon refused to fix it because I admitted it was rooted. The local repair shop is afraid of breaking the digitizer if they take it apart and besides, who knows what's wrong?
This is my last straw with Verizon. I have signed up with T-Mobile. My replacement Note 4 will be here today or tomorrow. I really loved this community. Yall are a great bunch of guys and I will miss you. But I refuse to take any more of Verizon's crap. I'll drop in to say Hi from time to time but for now I have to learn about the T-Mobile development community. Later.
Noooo. This is bitter sweet because you will enjoy yourself with all the Tmobile development. Frankly any Note 4 variant besides Verizon and AT&T you'll be happy. Good luck man and thanks for all your help.
jcip17 said:
Noooo. This is bitter sweet because you will enjoy yourself with all the Tmobile development. Frankly any Note 4 variant besides Verizon and AT&T you'll be happy. Good luck man and thanks for all your help.
Click to expand...
Click to collapse
Thanks man. You're one of the people who make XDA such a cool place. It ain't like this is goodbye forever. I'll be in here fairly often. Tapatalk keeps me notified of what goes on. See you later.
Sent from my SCH-I535 using Tapatalk
Sorry to hear you're leaving. You've been a great help to a lot of us. I share your feelings toward Verizon, they are just too big to care. So go on.... have some fun with the new toy....there's so much development over there... I'm actually over in the note4 snapdragon side more recently because I'm running all other than Verizon MM stuff. Anyways thanks Stuey for your contributions and help!
Sent from my SM-N920V using XDA-Developers mobile app
stueycaster said:
Three mornings ago I woke up to find wifi couldn't start on my phone. Nothing I tried fixed it. It's a hardware issue. Verizon refused to fix it because I admitted it was rooted. The local repair shop is afraid of breaking the digitizer if they take it apart and besides, who knows what's wrong?
This is my last straw with Verizon. I have signed up with T-Mobile. My replacement Note 4 will be here today or tomorrow. I really loved this community. Yall are a great bunch of guys and I will miss you. But I refuse to take any more of Verizon's crap. I'll drop in to say Hi from time to time but for now I have to learn about the T-Mobile development community. Later.
Click to expand...
Click to collapse
I'd be happy to do some low-level troubleshooting with you. That's a strange piece of hardware to fail, one that isn't very common. I think there might be something else going on.
ryanbg said:
I'd be happy to do some low-level troubleshooting with you. That's a strange piece of hardware to fail, one that isn't very common. I think there might be something else going on.
Click to expand...
Click to collapse
Nice.
Sent from my SM-N920V using XDA-Developers mobile app
ryanbg said:
I'd be happy to do some low-level troubleshooting with you. That's a strange piece of hardware to fail, one that isn't very common. I think there might be something else going on.
Click to expand...
Click to collapse
Ok. I reset it back to the condition it was when I got it. I odin'd the ANI1 modem and the ANJ5 stock restore. I don't know what else to do.
I don't have the new phone yet. Probably tomorrow evening or Monday. If I can fix it and don't decide to cancel TMo I could sell it. It shows a little wear around the USB port but other than that it's totally scratch free. It was always in an Otterbox case.
But I'd love to keep using it.
Sent from my SCH-I535 using Tapatalk
stueycaster said:
Ok. I reset it back to the condition it was when I got it. I odin'd the ANI1 modem and the ANJ5 stock restore. I don't know what else to do.
I don't have the new phone yet. Probably tomorrow evening or Monday. If I can fix it and don't decide to cancel TMo I could sell it. It shows a little wear around the USB port but other than that it's totally scratch free. It was always in an Otterbox case.
But I'd love to keep using it.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Just flash the full PBA1 tar first. Don't flash different bits and pieces, that could cause issues here.. Here's the link: Download
ryanbg said:
Just flash the full PBA1 tar first. Don't flash different bits and pieces, that could cause issues here.. Here's the link: Download
Click to expand...
Click to collapse
Isn't that going to overwrite the Dev Ed bootloader? I guess that's ok though because it's useless as a Developer Edition anyway right? And then I can do the unlock procedure.
It failed. It wants me to do the Verizon Software Repair Assistant. It probably failed because of the hardware issue right?
Update: On the second try it flashed and finished booting up. There were only 22 apps to optimize. Wifi still doesn't work. It did lose developer mode.
stueycaster said:
It failed. It wants me to do the Verizon Software Repair Assistant. It probably failed because of the hardware issue right?
Update: On the second try it flashed and finished booting up. There were only 22 apps to optimize. Wifi still doesn't work. It did lose developer mode.
Click to expand...
Click to collapse
We'll get DE back after you are stable. Uninstall Verizon Software Repair Assistant and Kies if you have it. To me, it looks like a USB/Driver/Software conflict going on preventing a successful flash. Try a different computer, and a different USB cable. Something is interrupting the write process.
I don't have access to another computer. Sometimes this computer does act up. That's M$ and their upgrade to W10 for you. Maybe after a fresh reboot?
I don't have the other stuff.
Update: Maybe I can borrow a computer. I don't know when though. I'll look into it.
stueycaster said:
I don't have access to another computer. Sometimes this computer does act up. That's M$ and their upgrade to W10 for you. Maybe after a fresh reboot?
I don't have the other stuff.
Update: Maybe I can borrow a computer. I don't know when though. I'll look into it.
Click to expand...
Click to collapse
That happened to me and I flashed back to stock full restore locked bootloader and that worked for me. My phone ended up craping out on me a couple weeks later< first i got a "failed to boot MMC read error" then when i tried to boot it, it as completely dead.
Dark_Plasma said:
That happened to me and I flashed back to stock full restore locked bootloader and that worked for me. My phone ended up craping out on me a couple weeks later< first i got a "failed to boot MMC read error" then when i tried to boot it, it as completely dead.
Click to expand...
Click to collapse
I flashed a ton of stuff through Odin and TWRP both. Everything seemed to flash correctly with the same result every time. Wifi wouldn't work. I can't help but think it's hardware. I think it baked this jumper wire that's right between the battery and the Wifi til it broke. Too many times heating it up by optimizing apps.
Sent from my SCH-I535 using Tapatalk
stueycaster said:
I flashed a ton of stuff through Odin and TWRP both. Everything seemed to flash correctly with the same result every time. Wifi wouldn't work. I can't help but think it's hardware. I think it baked this jumper wire that's right between the battery and the Wifi til it broke. Too many times heating it up by optimizing apps.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Sorry to hear that....hoped you could revive it. For sure these things get blistering hot! I've been flashing like crazy this past week thinking my phone is cookin! So I know what your saying could be the culprit. Still hoping you find a way!
Sent from my SM-N920V using XDA-Developers mobile app