So I rooted my s4 using towelroot and stupidly tried to install a custom recovery. First CWM then TWRP (not sure if this has anything to do with it, likely not?). Now it has no power, and wont charge...
Events leading up to the dead s4:
I "rebooted to recovery" and it brought me to the DOWNLOADING! screen instead of a recovery manager, I held down power and then it shut off and it turned back on again and brought me to another screen asking me to continue or boot normally.
I booted normally.
Then I deleted a few of the annoying apps that were preinstalled, nothing that was listed as essential to the Kernel/OS using Root App Delete. Finally I went to work with the battery dying, and it died on the way.
I tried to charge it the following morning and it would not charge. No LED light, no vibrate that usually happens. I left it alone with the battery out for 2 days, switching back to my s3. Tried again, still nothing.
Wont charge, computer wont recognize. Tried 3 different cables, a samsung charger and my asus tablet charger. Apparently it is a brick.
Thought it might be the USB port, and from a previous screen swap I performed, I still had the old USB assembly, so I swapped them, and it still will not respond. I even tried the older screen, nothing.
Anyone have the slightest clue what happened? I bought another battery to try, but doubt it will resolve the problem.
daveyp225 said:
So I rooted my s4 using towelroot and stupidly tried to install a custom recovery. First CWM then TWRP (not sure if this has anything to do with it, likely not?). Now it has no power, and wont charge...
Events leading up to the dead s4:
I "rebooted to recovery" and it brought me to the DOWNLOADING! screen instead of a recovery manager, I held down power and then it shut off and it turned back on again and brought me to another screen asking me to continue or boot normally.
I booted normally.
Then I deleted a few of the annoying apps that were preinstalled, nothing that was listed as essential to the Kernel/OS using Root App Delete. Finally I went to work with the battery dying, and it died on the way.
I tried to charge it the following morning and it would not charge. No LED light, no vibrate that usually happens. I left it alone with the battery out for 2 days, switching back to my s3. Tried again, still nothing.
Wont charge, computer wont recognize. Tried 3 different cables, a samsung charger and my asus tablet charger. Apparently it is a brick.
Thought it might be the USB port, and from a previous screen swap I performed, I still had the old USB assembly, so I swapped them, and it still will not respond. I even tried the older screen, nothing.
Anyone have the slightest clue what happened? I bought another battery to try, but doubt it will resolve the problem.
Click to expand...
Click to collapse
simple research you could have avoided all this....unless you have a MDK bootloader you CAN NOT install any custom recovery like TWRP of CWM without messing your phone up. Safestrap is your ONLY option. The link below is where you should have started your research. Most likely now you will have to try odin a clean image tar of your phone's firmware base
http://forum.xda-developers.com/showthread.php?t=2606501
decaturbob said:
simple research you could have avoided all this....unless you have a MDK bootloader you CAN NOT install any custom recovery like TWRP of CWM without messing your phone up. Safestrap is your ONLY option. The link below is where you should have started your research. Most likely now you will have to try odin a clean image tar of your phone's firmware base
http://forum.xda-developers.com/showthread.php?t=2606501
Click to expand...
Click to collapse
thank you. I know i messed up, have rooted/installed cfw on like 10 android phones but they always packaged root and unlocked the bootloader at once, which I never noticed.
Also, how can I connect the phone to odin if it wont connect to a PC? or charge for that matter
daveyp225 said:
thank you. I know i messed up, have rooted/installed cfw on like 10 android phones but they always packaged root and unlocked the bootloader at once, which I never noticed.
Also, how can I connect the phone to odin if it wont connect to a PC? or charge for that matter
Click to expand...
Click to collapse
I can't help you that
daveyp225 said:
thank you. I know i messed up, have rooted/installed cfw on like 10 android phones but they always packaged root and unlocked the bootloader at once, which I never noticed.
Also, how can I connect the phone to odin if it wont connect to a PC? or charge for that matter
Click to expand...
Click to collapse
Re install your drivers then try again
Sent from my SCH-I545 using XDA Free mobile app
Sounds like a total brick to me. There are jtag services. I bought the equipment myself to jtag for a hard brick but my warranty company decided the replace my phone after all so I didn't have to use the equipment. Mine did the same exact thing. Wouldn't even get warm when plugged into the charger.
Related
I really suck at installing custom ROMs.
I hard bricked because of low battery while flashing (I think, screen won't turn on, green light only comes on when plugged into a computer with no battery in, and a couple of posts I read made it sound like I'm screwed). So I'm going to AT&T tomorrow and hopefully getting a new phone. My main question is...
Can someone point me in the direction of a very comprehensive guide to installing a custom ROM on a stock Atrix brand new from the store?
I have poured over these forums for five days obsessively trying to figure out why I am so stupid and can't make it work, and have probably tried ten different methods of everything to get it to work, hoping that one of them had whatever I was missing already taken care of.
I rooted and unlocked my bootloader just fine. Even installed the Gingerblur rom (but that's a P-ROM right?). I think my problem is the custom recovery. Yes I deleted the recovery_install file. I tried flashing tenfar's CWM (the newest one I think, I sideloaded a different one to get Gingerblur) with fastboot but it said something like "flash:recovery is not a known command." (Sorry I don't remember completely, this was very early this morning before I went to sleep) I thought at the time that once you unlocked the bootloader you didn't have to do it again, but I read a thread an hour ago that said you just have to flash the unlock image after an RSD reset. So I was going to try to re-unlock, then try and flash with fastboot. Unfortunately I never got to try.
I am sorry for my obnoxiously long post, but I figured the more info I gave the higher chance there would be that someone could point at the obvious for me.
Thanks for your time.
when you plug the phone to wall-charger...wt happens?..do you see anything on the screen..
No. Also nothing happens when I press the power button. The green light ONLY comes on when I plug it into my computer with no battery, not when I plug it into an outlet.
Not entirely the right person to give advice but I guess it's worth a shot trying.
I'm a bit confused as to what you actually did. You're rooted and unlocked (100% sure on this?) Had gingerblur installed (guessing you were unlocked on 1.8.3?) and then wanted to install CMW, correct?
From the error you got you probably didn't cd (folder fastboot is in) flash fastboot recovery (path of recovery-en-goapk.img). Deleting the stock Android recovery folder most likely left you without any recovery. (Someone correct me if I'm wrong )
Entirely sure NOTHING happens while being plugged in into a computer? Can you get into fastboot at all? When connected via USB, does RSD show your device?
xscottishx27 said:
Not entirely the right person to give advice but I guess it's worth a shot trying.
I'm a bit confused as to what you actually did. You're rooted and unlocked (100% sure on this?) Had gingerblur installed (guessing you were unlocked on 1.8.3?) and then wanted to install CMW, correct?
From the error you got you probably didn't cd (folder fastboot is in) flash fastboot recovery (path of recovery-en-goapk.img). Deleting the stock Android recovery folder most likely left you without any recovery. (Someone correct me if I'm wrong )
Entirely sure NOTHING happens while being plugged in into a computer? Can you get into fastboot at all? When connected via USB, does RSD show your device?
Click to expand...
Click to collapse
The screen will not turn on. Nothing, no moto symbol, nothing. I did cd, I got an interface, fastboot said it was going to install a recovery, but then it failed, and that is the message the phone gave me. I was rooted, because I had superuser. I WAS unlocked,, because it had said unlocked on boot, though not at the time of fastboot, but then I used rsd after I was stuck in boot after trying to install a custom rom. After that it didn't say unlocked, so I unlocked again, and while doing so it said I was already unlocked. I failed to install a custom rom again with the same result, so I rsd'ed again back to 1.2. I never unlocked after that because I figured I didn't need to. I tried to install a custom rom many times with pretty much the same result after trying several different things, including flashing CWM with fastboot. Then I read that I had to re unlock after RSDing, so I was in the process of that when my screen shut off in the middle of it. I assume it didn't have enough charge and died (or that is what it sounds like according to what I have read)
mediocrepiracy said:
The screen will not turn on. Nothing, no moto symbol, nothing. I did cd, I got an interface, fastboot said it was going to install a recovery, but then it failed, and that is the message the phone gave me. I was rooted, because I had superuser. I WAS unlocked,, because it had said unlocked on boot, though not at the time of fastboot, but then I used rsd after I was stuck in boot after trying to install a custom rom. After that it didn't say unlocked, so I unlocked again, and while doing so it said I was already unlocked. I failed to install a custom rom again with the same result, so I rsd'ed again back to 1.2. I never unlocked after that because I figured I didn't need to. I tried to install a custom rom many times with pretty much the same result after trying several different things, including flashing CWM with fastboot. Then I read that I had to re unlock after RSDing, so I was in the process of that when my screen shut off in the middle of it. I assume it didn't have enough charge and died (or that is what it sounds like according to what I have read)
Click to expand...
Click to collapse
sounds like hard brick bro...
You need to find a way to charge your battery. It sounds like your battery is dead. Try to find a someone with the same phone as you.
Sent from my MB860 using XDA Premium App
To charge your battery,
Take ANY USB cable and cut one end of it off.
Strip the outer layer and strip the Black and red wires exposing the wire itself.
Starting with the black wire, tape that end to the NEGATIVE sign on the battery
Then take the red wire and tape it to the POSITIVE side of the battery.
Make sure you check it every few minutes so it does not over heat because it WILL get hot due to no regulations
I would charge it for approximately 30 min or so then put the battery back into your phone and boot it up
AND NO YOU DID NOT HARDBRICK BECAUSE YOU DID NOT HAVE HAVE THE RIGHT CWM IN ORDER TO FLASH THE OTA THAT WOULD CAUSE YOU TO HARDBRICK IF GOING BACKWARDS
ClearFire said:
To charge your battery,
Take ANY USB cable and cut one end of it off.
Strip the outer layer and strip the Black and red wires exposing the wire itself.
Starting with the black wire, tape that end to the NEGATIVE sign on the battery
Then take the red wire and tape it to the POSITIVE side of the battery.
Make sure you check it every few minutes so it does not over heat because it WILL get hot due to no regulations
I would charge it for approximately 30 min or so then put the battery back into your phone and boot it up
AND NO YOU DID NOT HARDBRICK BECAUSE YOU DID NOT HAVE HAVE THE RIGHT CWM IN ORDER TO FLASH THE OTA THAT WOULD CAUSE YOU TO HARDBRICK IF GOING BACKWARDS
Click to expand...
Click to collapse
If this works I will give you many thanks, and my firstborn child.
It didn't work. Walked into an AT&T store and said "It broke, I don't know what to do" and they gave me a new one under manufacturers warranty. I am going to try again, but if someone could point me towards a comprehensive guide that may be able to solve my problems, I would be appreciative.
I figured out my issue with not being able to install custom recovery, it was the fact that I hadn't unlocked again after flashing an sbf. I am now running Aura ROM, and so far I've been geeking out nonstop. Thanks everyone who tried to help me.
My friend is having some problems charging his Atrix. Basically, the phone will not charge or recognize a charger at all except for under certain circumstances.
Some background info: I helped him unlock his bootloader and install 4.5.91 way back when it came out. No problems there, it went well. All was fine until the 4.5.141 OTA update came around. He got the OTA notification and clicked update because he didn't know anything bad would happen. Luckily it didn't brick him like it did a lot of people, but he said it gave him an error message during the install and it would not boot after that, stuck at the Motorola dual core screen. I took a look at it and managed to get into recovery and flash back to 4.5.91. All was fine until it was time to charge the phone. It wouldn't recognize any charger. I tried flashing to tons of different roms, wiping everything, even restored a full nandroid recovery from my working Atrix on it. His phone will charge and will be recognized by a computer immediately after we flash a new rom, and will continue to charge for as long as we leave it plugged in, but if we unplug it then after a short time (like under 30 mins) it will not recognize a charger if we plug it in again. Wiping data alone will not make it start charging again, only actually installing a new rom will. Deleting battery stats does nothing. The closest we have gotten to fixing it was when I made a nandroid on my Atrix and then restored it on his (my backup was from Joker's CM9); after the restore, it would charge for a while, and we unplugged it and waited to see if it would do the same thing as it always did and stop recognizing a charger after a few minutes. About 30 minutes later it stopped recognizing the charger as usual. We played with the USB debugging setting (enable, plug in, see if it recognized the charger, disable, plug in, see if it recognized it, etc) and after messing with that setting a lot it recognized the charger once, but then when we unplugged it the phone wouldn't recognize the charger again. We could not reproduce this again.
To summarize what we have tried and found to work:
-flashing a rom will let the phone charge/let a computer recognize it for as long as we leave it plugged in after the first boot (we have tried every rom under the sun, they all do the same thing)
-restoring from a nandroid backup will have the same effect as flashing a rom
What we have tried that didn't work:
-different cords; have tried them all, both OEM cord and third party, this is not the problem
-wiping all data/factory reset doesn't do anything
-cache wipe doesn't do anything
-wiping battery stats doesn't do anything
I have also tried fastboot flashing back to 4.5.91, CWMing back to 4.5.91, using the unbrick scripts and stock restore scripts people have made, nothing will fix it.
If anyone has any suggestions or can refer me to anywhere with more info on this I would appreciate it, I have searched high and low and can't find anyone with a problem quite like this one. I don't even know if it's a hardware or software problem, if you guys know a way to determine this it would be helpful.
Have you tried a wall charger?
Yeah, both the stock one and a different one I have, neither work.
No one has any advice or ideas on this? Does anyone know if Moto does repairs in this type of situation with a voided warranty because of an unlocked bootloader, or does anyone know who may be able to fix this if I can't get any help from the forums or figure it out on my own?
Hey all, this is my first android and I'm not the smartest sometimes. I tried restoring back to factory rom, and watched a bad how to vid. Basically i cleared data, system, cache and now realize i shouldn't have.
I'm not able to connect to the phone through usb. I have the drivers, but I can't see the phone.I can boot into cwm, and that is it. When i start it, it basically pulls up the LG screen, then a black screen.
I have a backup on cwm but get the md5 error.
Is it possible to put the sd card in my computer and download what i need straight to the card? Im also not sure what i need to download, if that does work.
Please let me know if there is any other info I can provide. Like i said im not the smartest sometimes, so dont be afraid to respond like im slow.
Cat Rancher said:
Hey all, this is my first android and I'm not the smartest sometimes. I tried restoring back to factory rom, and watched a bad how to vid. Basically i cleared data, system, cache and now realize i shouldn't have.
I'm not able to connect to the phone through usb. I have the drivers, but I can't see the phone.I can boot into cwm, and that is it. When i start it, it basically pulls up the LG screen, then a black screen.
I have a backup on cwm but get the md5 error.
Is it possible to put the sd card in my computer and download what i need straight to the card? Im also not sure what i need to download, if that does work.
Please let me know if there is any other info I can provide. Like i said im not the smartest sometimes, so dont be afraid to respond like im slow.
Click to expand...
Click to collapse
Can you install the Rom "The base .5". I assume so if you can get to cwm. I had this problem when flashing this Rom The first time. It did the same thing with the LG logo then go black. If that happens just reboot to cwm(May take awhile) and reflash "the base" again. That should allow it to boot the phone fully so you can at least use it till you can get all the way back to stock. I hope this helps. I have to crash now tho. I'll check back in the morning to see how it's going.
Sent from my UNLOCKED LG-E970 using xda premium
Are you trying to get back to factory settings or just get your phone running with the stock rom?
You should be able to just put the ROM on your sd card via computer if you have an SD card sleeve.
If you wiped your phone, it's my understanding that you're not supposed to when flashing the provided rom in development.
There's a posting in development, I believe, about restoring your phone to stock if you messed it up. LGNST or something.
Cat Rancher said:
Hey all, this is my first android and I'm not the smartest sometimes. I tried restoring back to factory rom, and watched a bad how to vid. Basically i cleared data, system, cache and now realize i shouldn't have.
I'm not able to connect to the phone through usb. I have the drivers, but I can't see the phone.I can boot into cwm, and that is it. When i start it, it basically pulls up the LG screen, then a black screen.
I have a backup on cwm but get the md5 error.
Is it possible to put the sd card in my computer and download what i need straight to the card? Im also not sure what i need to download, if that does work.
Please let me know if there is any other info I can provide. Like i said im not the smartest sometimes, so dont be afraid to respond like im slow.
Click to expand...
Click to collapse
The recovery won't generate a md5 sum (known bug). You have to generate it yourself. Connect your phone to adb and go to #4 in the FAQ here.http://forum.xda-developers.com/showthread.php?t=2006946
Note that there is no way to tell of the backup is corrupt since you are generating a valid code regardless of integrity.
Sent from my LG-E970 using xda premium
Murasakiii said:
Are you trying to get back to factory settings or just get your phone running with the stock rom?
You should be able to just put the ROM on your sd card via computer if you have an SD card sleeve.
If you wiped your phone, it's my understanding that you're not supposed to when flashing the provided rom in development.
There's a posting in development, I believe, about restoring your phone to stock if you messed it up. LGNST or something.
Click to expand...
Click to collapse
I tried re-installing .4 base which is what I had originally used. It let me choose the apps to instal, and made it to the "X" screen, but appeared to be stuck in a boot loop. I am going to try and download and install .5 via the sd card and see if that works. I'm not sure if LGNPST will work since I can't see the phone via usb. I will download it and give it a try though.
I also saw the guide in the general Optimus G forums for unbricking it.
http://forum.xda-developers.com/showthread.php?t=2010624
Since i cant really connect via usb, ill probably have to use a different method. Im hoping the usb issue is due to the computer im using and the original computer i used to root and unlock will work.
Cat Rancher said:
I tried re-installing .4 base which is what I had originally used. It let me choose the apps to instal, and made it to the "X" screen, but appeared to be stuck in a boot loop. I am going to try and download and install .5 via the sd card and see if that works. I'm not sure if LGNPST will work since I can't see the phone via usb. I will download it and give it a try though.
I also saw the guide in the general Optimus G forums for unbricking it.
http://forum.xda-developers.com/showthread.php?t=2010624
Since i cant really connect via usb, ill probably have to use a different method. Im hoping the usb issue is due to the computer im using and the original computer i used to root and unlock will work.
Click to expand...
Click to collapse
The method in that link is for phones that don't have official firmware to use with lgnspt. If you san get into download mode (power off phone ,connect usb,hold volume down and up plus power ) you should be able to lgnpst back to stock.
adfurgerson said:
The method in that link is for phones that don't have official firmware to use with lgnspt. If you san get into download mode (power off phone ,connect usb,hold volume down and up plus power ) you should be able to lgnpst back to stock.
Click to expand...
Click to collapse
Alright. I was able to get into download mode. I downloaded lgnpst. Do you have an idea where i would find the other necessary files? Again, total noob. Sorry for all the hand holding. You guys have been great!
Cat Rancher said:
Alright. I was able to get into download mode. I downloaded lgnpst. Do you have an idea where i would find the other necessary files? Again, total noob. Sorry for all the hand holding. You guys have been great!
Click to expand...
Click to collapse
You need to go to the IRC channel to grab the new version of lgnpst and the correct files.
Sent from my LG-E970 using xda premium
Cat Rancher said:
Alright. I was able to get into download mode. I downloaded lgnpst. Do you have an idea where i would find the other Didnecessary files? Again, total noob. Sorry for all the hand holding. You guys have been great!
Click to expand...
Click to collapse
Did you get your phone straightened out?
adfurgerson said:
Did you get your phone straightened out?
Click to expand...
Click to collapse
I'm traveling for work and on a work computer, so the IRC channel is blocked. Of course. I'm heading home tomorrow so hopefully I can get everything back to normal when i get on my home computer. (not having a phone sucks)
Do you all think it would be worth putting the base .5 on my sd card and flashing that, or do you think that wouldnt work? .4 is on there now from my original flash, but that won't work. Just curious.
Well is your phone up and running?
I would think it wouldn't cause harm to try and flash .5 onto it, your phone shouldn't get bricked from it.
i agree with Murasakiii
should be fine to run .5
DraginMagik said:
i agree with Murasakiii
should be fine to run .5
Click to expand...
Click to collapse
Welp, I think i earned the title of first bricked phone. It was able to get into recovery and download mode a couple days ago, but now it wont charge it seems. So i cant get it into any mode to do anything. Ive had it on the charger, wall and usb for a couple hours and nothing is happening. I wonder if i can take it back to my att store and try get a replacement. It is within my 14 day window, and there are "hardware" warranties. I have a feeling they will ask what happened and while i may not initially divulge everything, i sadly cant lie. And since its all my fault, i may chalk it up to learning.
i'd say the device started having issues with the USB. unable to see the device when plugged into the computer and the device won't take a charge. don't hear of too many authentic "bricking's" anymore...it can almost always be resurrected. but if the device won't take a charge your time to resolution is rather limited. good luck.
Cat Rancher said:
Welp, I think i earned the title of first bricked phone. It was able to get into recovery and download mode a couple days ago, but now it wont charge it seems. So i cant get it into any mode to do anything. Ive had it on the charger, wall and usb for a couple hours and nothing is happening. I wonder if i can take it back to my att store and try get a replacement. It is within my 14 day window, and there are "hardware" warranties. I have a feeling they will ask what happened and while i may not initially divulge everything, i sadly cant lie. And since its all my fault, i may chalk it up to learning.
Click to expand...
Click to collapse
Before you leave to go to the store hook it up to a set up jumper cables and then attach the other end to your car battery. Then just tell them when you tried to charge it that it started smoking and wont turn on any more.
The only lie you have to tell them is it happened on the stock charger.
Im on the same boat. Tried going back to stock for a warranty return, and i ended up bricking the phone. Im able to get it to download mode and was able to run the lg tool but it keeps failing on me. And when it does complete it still wont load. Im going to try to make my self a powerd usb cable too see if i can get it to work. Have like 2 or 3 days to try to figure it out. Or elese im out 550 bucks.
Sent from my LG-E970 using xda app-developers app
Other option is just telling them you clicked install for the ota update it rebooted and never came back on. They just wipe them at the repair center anyway if they get them to boot up.
Cat Rancher said:
Welp, I think i earned the title of first bricked phone. It was able to get into recovery and download mode a couple days ago, but now it wont charge it seems. So i cant get it into any mode to do anything. Ive had it on the charger, wall and usb for a couple hours and nothing is happening. I wonder if i can take it back to my att store and try get a replacement. It is within my 14 day window, and there are "hardware" warranties. I have a feeling they will ask what happened and while i may not initially divulge everything, i sadly cant lie. And since its all my fault, i may chalk it up to learning.
Click to expand...
Click to collapse
It took 12 hrs to get a clean download of the stock ROM (AT&T internet sucks in my area). The entire time the screen on my phone was on with the LG splash screen displayed. By the time I got the ROM ready for flash, the battery was dead. I was however able to plug in to the USB on my computer and get enough juice to get into download mode. Ran LGNPST (v2.2.3) and the stock ROM installed with no prob. You might try plugging it in then trying to get into download mode.
EDIT: now that I think about it. You need to have it plugged in to the USB before download mode anyway, so you won't be doing anything different than you already did.
I have a Samsung Galaxy S2 SCH-R760.
What happened: Tried to update phone from standard IceCreamSandwich to Jelly Bean via Samsung provided SimpleUpgradeTool. Very new to flashing phones, forgot to check model number, first attempt failed. Eventually got the right one (difficult to do with my model apparently), and the mobile network wouldn't work. Was told to reset APN, could not find it anywhere in the system.
Got fed up and decided to revert back to original OS, which failed. Waited overnight (it was late) with the phone off. Found the right file (just going to go back to Jelly Bean), however whenever I attempted to get into recovery mode it told me there was not enough power and to charge the phone. Phone was plugged in, this happened a couple of times. Now after the phone has been plugged in for well over 3 hours I cannot get the phone to power on or anything, it absolutely will not respond. Attempted to use Kies, will not recognize my phone model and is waiting for the phone to be connected anyway. When plugged in (trying/using various different cords) I have a little faint blue light flashing in the top left corner of the phone (not the phone screen).
The phone has been in excellent condition up until this point, and I have little reason to believe that my battery just suddenly went 100% bad after showing no signs of decay in recent weeks. Any suggestions?
How did you try to revert? But kind of sounds like it might be hard bricked. If you can't get get into Download mode by Vol Down and Power and it isn't charging not even sure if this would work: http://forum.xda-developers.com/galaxy-s2/general/ref-usb-jig-faq-frequently-questions-t1402286
But unless you try another battery or something like that jig, and it does not power up to any screen, then your only hope would be a JTAG service. I recommend these guys:
http://mobiletechvideos.mybigcommerce.com/
es0tericcha0s said:
How did you try to revert?
Click to expand...
Click to collapse
Just tried to use the samsung quicktool program and just install the old OS back onto the phone.
Aquaserge said:
Just tried to use the samsung quicktool program and just install the old OS back onto the phone.
Click to expand...
Click to collapse
I'm not familiar with the QuickTool. Why not use Odin? It's the preferred method for most popular Samsung phones.
Hi guys, sorry if I posted this at the wrong place.
I have a Lenovo s860 and it went into a bootloop. It was stock and all so I thought that I can have my files recovered if I just bring it to a service center so they can get the files first before wiping it or maybe even fixing the bootloop without wiping the device. Well, the thing is, the guy at the service center screwed up and now, when I try to turn it on, I still see the boot screen (Lenovo, powered by Android) but the next screen is like an television with bad signal.
I'm familiar with rooting and flashing ROMs, I've tried it on my Galaxy S2 (yeah I know, it was way back), but I think things are still more or less the same: I need to be able to boot into recovery mode in order to root the device. However, when I tried the Power Button + Volume Up, or any combinations of the Power Button and the Volume Buttons, it just goes straight to the dead screen, I get no response whatsoever.
I also tried to check if adb can detect it, however, it didn't seem to be able to do so. I'm using a MacBook Pro so I know I don't have to install any drivers, I also code Android Apps so I have a background on this.
I think my only option would be to flash the ROM on this dead device but I don't know how to do that. I've also seen some posts that suggest doing some things (I forgot the specifics) while the battery is drained, so what I'm doing for the mean time is to leave the phone open and let it drain which might take ~2 days.
Does anyone know how to flash a ROM on a bricked device? Thanks for any leads.