Related
Hello All
I purchased a phone from a friend of a friend so I don't have all the history of the phone. It looks like they attempted to root it and failed.
I only got it to boot op fully one time. (and I can't get it to boot up fully again) It goes to the htc incredible logo and starts over.) So here's what I know. I didn't see a superuser apk the one time I got it to boot. It has the radio that ends in 07.28. It has s-on. It has a recovery but not one that I'm used to (like on ogdroid)
Its says android system recovery <3e>
reboot
apply update.zip
wipe/factory
wipe cache partition
and at the bottom
E: Can't open /cache/recovery/command
I've tried the unroot method to try to get it going, but no luck. I'm stuck. Any thoughts? Thanks for any help.
You can follow this thread, part 2
http://forum.xda-developers.com/showthread.php?t=786436
Basically, download this file
http://www.fourty.net/~berzerker/stockstuff/PB31IMG_3.26.605.1_RUU.zip
Rename it to PB31IMG.zip, put it on the root of your SD card, boot the phone into the bootloader (hold vol + & pwr when turning on) and let it update. It should return it to a completely stock 2.2 with no root. From there you can go root it or do whatever you would like.
Ok I tried that. The update goes through successfully but I'm still stuck in the loop.
Is there a way to root or get s-off with out booting the phone? (I'm using a mac)
this happened to me recently - I reloaded RUU - hard reset - removed sd - left battery out for a while - used my wifes battery - power plugged in - Wiped everything possible in cwr (before ruu)
The phone is completely stock and wont stay on for more than 5 seconds if it even gets to the lock screen at all. In the end I had to put s-on and request a replacement
one thing I did notice though (hope this helps) I left my battery out of the phone overnight and in the morning without power connected it did boot all the way and I popped on to the market and used the browser for about 15 minutes - then fell back in to a boot loop and I wasn't able to reproduce that working state again.
Incredible
Try looking for a Ruu to return it stock,
make sure you wipe all.
Sometimes it helps to be patient and watch out for heat issues.
Not sure if this is related but My Hd2 on 2.3 and Mytouch 4g on 2.3 would boot loop when it got a little warm Remove the batter and let it sit for 10 minutes.
Ok
It's back to stock. I still have the same issue. It is the same problem that h0x90 had. This phone isn't activated and I'm not sure if it has a warranty or not. I would rather try to fix it if I can. Can I root it with adb or otherwise in its current state? I wonder if a rom would fix the problem. It seems to be software and not hardware, correct?
Before I was desperate enough to wipe everything (ruu) I loaded several different roms and loaded my backups - so in my case it was a hardware issue.
Verizon told me they cover the phone for 12 months from purchase date - and they're overnighting a refurb to me for free which is nice. Maybe if nothing else you can get a hold of the previous owner and attempt to get a replacement.
Best of luck though either way!
nothing0 said:
Ok
It's back to stock. I still have the same issue. It is the same problem that h0x90 had. This phone isn't activated and I'm not sure if it has a warranty or not. I would rather try to fix it if I can. Can I root it with adb or otherwise in its current state? I wonder if a rom would fix the problem. It seems to be software and not hardware, correct?
Click to expand...
Click to collapse
As the Incredible hasn't been on the market for a year yet, it's assuredly still within the warranty period.. As for trying to fix it yourself, I can all but guarantee that you cannot since what you're experiencing seems to be a relatively common hardware failure.
I finally gave up. I did find out that PCD at 1.800.229.1235 does warranty work for HTC. Maybe that information will help others. Thanks to all that helped.
Ok I'm lost. I'm working today and my phone tries to reboot for no apparent reason and is put into a boot loop that I cannot get out of no matter what. In boot loader I have no recovery. Downloaded amon ra recovery's PC36IMG.zip. Booted into bootloader it said it updated the recovery but after I've rebooted I still have no recovery. I don't think this is very good.
Bootloader asked you to update and reboot and it went through completely?
Yeah, it said update was succesful. Thats why I'm so confused.
So when you go into recovery from the bootloader, do you see the triangle?
Nope just back to white screen boot loop. Trying to flash sprint lovers with the pcm36img over it maybe that will bring me back to stock rooted stat.
Edit: Back to white screen boot loop.
this same thing happened to me a week ago. were u running a cm7 rom?
yeah ex10 i was going to switch last night guess its too late
Damn I feel bad for you
I had that same problem when i first rooted and flashed my evo. I suddenly got into an infinite boot loop where i no longer had a recovery. Sorry man i had to take it to a sprint store after i tried flashing a different bootloader and then retry flashing a different recovery from clockwork to amon. and then even tried to flash the stock rom none work. if none of those work then you most likely is going to have to go to a sprint store.
Well, you could try running an RUU. This will leave you unrooted and completely stock so you will need to root again.
Here's a how-to over on Android Central.
http://forum.androidcentral.com/htc-evo-4g-rooting-roms-hacks/19278-how-unroot-return-stock.html
when this happened to me last friday i looked around xda and i found a couple other people who had this problem as well. everyone i found (myself included) was running a cm7 rom. i still cannot get any farther than bootloader without a white screen loop. sprint sent me a replacement on warranty because i live too far from the sprint store for them to make me drive there but i have to send my old one back. its still s-off tho and even running the stock ruu does nothing to fix that. anyone know of how to get s-on without the ability to enter recovery or anything else? or a way to brick it completely so it wont boot to bootloader where they can see s-off?
Threw mine out of the window of my car and called sprint and told them I lost it. Cost me $100 to get a replacement and now I'm going to have to spend forever getting back to root and eng boot ect... sucks.
Has this only happened with the magnus cm7 or is the happening with the official cyanogen rc1 and nightlies? Because I'm really wanting to go to the CM7 nightlies but not if the chance this is going to happen again.
ChacocII said:
when this happened to me last friday i looked around xda and i found a couple other people who had this problem as well. everyone i found (myself included) was running a cm7 rom. i still cannot get any farther than bootloader without a white screen loop. sprint sent me a replacement on warranty because i live too far from the sprint store for them to make me drive there but i have to send my old one back. its still s-off tho and even running the stock ruu does nothing to fix that. anyone know of how to get s-on without the ability to enter recovery or anything else? or a way to brick it completely so it wont boot to bootloader where they can see s-off?
Click to expand...
Click to collapse
Does the bootloader let you run a PC36IMG.zip? If so, try running one (of a factory unrooted ROM), and when it goes to reboot and shows the green arrow facing down (if it gets that far) yank the battery at that point. I think that is when it's writing the radio image. If you can get it to that point, and then pull the battery, I'm pretty sure you'll have a brick. Aside from a battery pull during the radio flash, I'm not sure how to make a brick, without it being obvious of what you've done. You could rig your phone charger up to a 230 volt outlet from a drier or something, and plug it in. haha. maybe that would fry it, tell sprint you got a power surge when it was charging, and then it wouldnt turn on. (only 1/8 serious on that last part )
Has this only happened with the magnus cm7 or is the happening with the official cyanogen rc1 and nightlies?
Happened to me with official cm7 rc1
Does the bootloader let you run a PC36IMG.zip?
yes, but it doesn't actually do anything. it will go thru the whole update process but still goes back to a white screen loop and no recovery. tried a battery pull during the radio update a couple hours ago (i thought the same thing) but it did nothing. i think its because its not actually doing anything when u run the pc36img other than going thru the motions on the screen.
maybe i can microwave it hahaha
edit: after a couple battery pulls during the radio update in the pc36img im using, it will no longer go thru the full radio update when running the zip so i definately screwed up the phone. it still gets to bootloader no problem tho so ive accomplished nothing.
ChacocII said:
Has this only happened with the magnus cm7 or is the happening with the official cyanogen rc1 and nightlies?
Happened to me with official cm7 rc1
Does the bootloader let you run a PC36IMG.zip?
yes, but it doesn't actually do anything. it will go thru the whole update process but still goes back to a white screen loop and no recovery. tried a battery pull during the radio update a couple hours ago (i thought the same thing) but it did nothing. i think its because its not actually doing anything when u run the pc36img other than going thru the motions on the screen.
maybe i can microwave it hahaha
edit: after a couple battery pulls during the radio update in the pc36img im using, it will no longer go thru the full radio update when running the zip so i definately screwed up the phone. it still gets to bootloader no problem tho so ive accomplished nothing.
Click to expand...
Click to collapse
Damn, so you can still see s off? I have no clue how to get it to s on then, or make it so you can't even get to the bootloader. Yea, if you microwaved it (haha) i'm sure it wouldnt ever turn on again. However, whoever looks at it would be able to tell that something went very, very wrong, and it wasn't the phone's fault. ha. Maybe it won't even matter that it's s off. I've heard of people having luck with sprint looking at a phone that is s off, but I've also heard the oppositte (more often).
i actually told the sprint tech on the phone that i had rooted it and he still warranty replaced mine. im just hoping they dont change their minds when they get it back and see s-off and try to charge me 500 bucks for my new one.
Wow. Yeah, if it won't even run a PC36.img from bootloader, you're kinda SOL. That's pretty much a last resort. Granted, you should try a few different img's (different d/l sources) before assuming it's screwed. Sometimes, you can get a bad download. I had a stock Evo that wouldn't go into recovery, so I flashed a RUU from bootloader, and everything was fine. Best of luck with your replacement though, brother.
well i have 14 more days before i have to send it back. there must be some way to get it to not turn on at all without physical damage, just gotta figure it out.
Hi.
After I successfully installed the cyangen mod, i wanted to install swype and some google apps. that is when i flashed the nightly sbf...
Since then, I could not start my phone..., only the bootloader (no matter which volume key i pressed).
So I looked for a full sbf to flash and found one, with code 2.5... (jrdnem u3 2.51.1)
but now, I can not even enter the bootloader. the only surviving signal of my phone i get is the white led when i connect it to the pc...
the battery status was at. about 85 %...
I'm really sorry, but i would be very greatful to receive some help
ps. before i flashed the nightly sbf, i forgot to wipe this thing in the bootloader...
Well...in my desperate state I was not able to type in the right words into the search bar. I think I found the answer to my Problem... My only task now is to find a well working sbf 2.5...
I'm still confused. I thought I'm not, but- would it be a problem if i flash the nordic cynagenmod, sbf version 3.4.2?
I would not knwo why not, but after I have these problems, I dont want to do anything again without knowing the consequence...
If you could enter stock recovery. You can do full wipe and boot to bootloader to flash your previous working sbf. If only bootloader your get now, just flash the nordic sbf and boot it into stock recovery to perform the full wipe.
Sent from my awesome Moto Defy: Stock Rooted Gingerbread 2.3.3 - XDA Premium
Right now, I don't even see the Bootloader or any Motorola-Logo. It just nothing happening, when I press the power button.
Your battery may well have run out of juice (same happened to me once upon a time). Leave it off, stick it on charge. Go have a cup of tea or two, then try again.
Alright. Now I'v had the time to check again.
Even with charging, the phone is still not turning on.
But I've read somewhere :" Don't worry, as long as you "see" your device in RSD Lite you can still flash the firmware. My big question is: WHICH SBF will help me? I#m really afraid to flash anything, because I don't now the consequence...
About the Cyangenmod: It said, it is not downgradable... does this mean, that I must take the JRDNEM_U3_2.51.1 sbf?
Hope this tips shade some light in your quest of resurrection of your dying Defy.
1) Use RSDlite 4.9 or 5.0 as these program known to be stable on PC.
2) Use the latest Moto driver 5.0.0 ver. Google it and you find it easily.
3) Install both the above 1) and 2).
4) Take out your Defy's battery, plug in USB cable on both ends
5) launch the RSDlite and insert the battery. You'll get some drivers installing and have the connected status display on the RSDlite window.
6) Flash the phone to this file HERE.
7) After flashed completed (At this point you won't get a normal boot yet, screen still black or stuck in moto logo), reboot into stock recovery and do full wipe.
8) Reboot again and you should be seeing it alive again.
Note: If somehow your battery run flat. You must do the Mcguyver trick to flash your phone. Do it quickly to avoid your battery get fried and damaged. I would suggest you brigde the wire connection to a 100Kohm resistor to bring down the voltage/current, this will protect your battery from getting fried.
Wish best of luck this time around.
Wow. Thank you very much for this step-to step guide.
Now, before I get started I have one question left: Can I also use the 5.1 Moto Driver? Or should I downgrade it?
I have the RSDLite 5.0 now, (before it was the 5.33 or so).
Those drivers should work too..
Sent from my awesome Moto Defy: Stock Rooted Gingerbread 2.3.3 - XDA Premium
I tried what u said, it's just that RSD does not recognize my phone, so I cannot even flash. I want to believe this is because the battery has run flat (which I don't understand, it still had about 70 % 2 days ago, when the whole story started...)
Please tell me that this is just the symptom of a low battery?!
Is it possible that the flashing has wiped out all firmware and bootloader and chargin system availeble on the phone?
My defy has the same problem. I have changed battery and a universal charger but i dont to know as resolve
I used the Mac Giver trick to flash the sbf onto my defy. It worked, my Defy is working again. Thank you very much
Hi guys.
Last night has been a nightmare for me, I have to say. My Defy has been suffering recently from battery fatigue - the battery holds charge for about ½ an hour before I need to plug it in again. At the time, I was running CM9 (Epsylon's) so I thought I'd try downgrading to CM7 to see if it was software or hardware.
This is where the trouble began.
I faactory reset the phone and flashed the CM7 ROM I was going to use (http://forum.xda-developers.com/showthread.php?t=1604501) then hit reboot.
My phone got stuck on the M boot logo. Great. Back to recovery, I wiped all cache etc and rebooted. Still the same. Back to recovery and I tried the whole process again. Still the same.
By this point, my phone was losing charge, so I left it to charge a bit (plugging it in from 2% charge takes it instantly to 60%).
Then I retried the whole process again - still the same.
Okay, it's getting late now and I'm starting to panic. So I download a stock ROM (T-Mobile 2.2.2) and flash it using RSD Lite. Looks like it's going well, until it tries to reboot me - stuck at M Boot logo.
Now, I can't even switch my phone on to get it to the bootloader. I've tried a different battery too, and no joy.So now I have a well and truly broken phone.
From my knowledge, I have two options here:
1. Try the Macgyver fix method. I'm not confident doing this, and don't even know if it will work.
2. Take my phone back to T-Mobile and hope they don't notice what I've done.
I'd appreciate some help please if any one is able.
thanks.
simon211175 said:
Hi guys.
Last night has been a nightmare for me, I have to say. My Defy has been suffering recently from battery fatigue - the battery holds charge for about ½ an hour before I need to plug it in again. At the time, I was running CM9 (Epsylon's) so I thought I'd try downgrading to CM7 to see if it was software or hardware.
This is where the trouble began.
I faactory reset the phone and flashed the CM7 ROM I was going to use (http://forum.xda-developers.com/showthread.php?t=1604501) then hit reboot.
My phone got stuck on the M boot logo. Great. Back to recovery, I wiped all cache etc and rebooted. Still the same. Back to recovery and I tried the whole process again. Still the same.
By this point, my phone was losing charge, so I left it to charge a bit (plugging it in from 2% charge takes it instantly to 60%).
Then I retried the whole process again - still the same.
Okay, it's getting late now and I'm starting to panic. So I download a stock ROM (T-Mobile 2.2.2) and flash it using RSD Lite. Looks like it's going well, until it tries to reboot me - stuck at M Boot logo.
Now, I can't even switch my phone on to get it to the bootloader. I've tried a different battery too, and no joy.So now I have a well and truly broken phone.
From my knowledge, I have two options here:
1. Try the Macgyver fix method. I'm not confident doing this, and don't even know if it will work.
2. Take my phone back to T-Mobile and hope they don't notice what I've done.
I'd appreciate some help please if any one is able.
thanks.
Click to expand...
Click to collapse
ok mate
right the mcgyver trick works a treat and is surprisingly easy. i wasnt keen on it but it works and is not hard although it is fiddly and if you are anything like me it will take a few attempts to peel back the shielding and expose the wires and then get them in place.
i found the best way to get the wires in place was not put them under the battery as the guide suggests but instead just put the battery in as normal and have the wires in at the very end. you will understand what i mean when you start but i have decided to take a photo and you can see what i mean here
http://sdrv.ms/OPDczX
everything you need for that this section of the recovery is here.
http://forum.xda-developers.com/showthread.php?t=892026
then you need to flash the sbf again. the one you have already flashed is fine and is the one you need so use that. (if for some reason it doesnt work after what i am going to tell you then ask again on here before you choose another).
next follow the guide to un-bricking your phone (linked below). if the phone wont boot and gets stuck after you have flashed the sbf you need to boot into recovery and wipe the data/ cache. reboot and all should be ok.
so follow the guide to the letter but when/ if (the phone wont boot past the moto logo) follow step 8. however you will find that when you press power on/ volume down that instead of motorola recovery you get a droid with an exclamation mark (this is ok so dont panic). to get into stock recovery from this position you need to press and hold down both up and down volume buttons at the same time for about three seconds and viola. then you can wipe and you should (fingers crossed) be good to go. if you dont understand anything then ask but it is relatively straightforward and if you do what i suggest above then you should have a working phone in next to no time.
http://forum.xda-developers.com/showthread.php?t=1828639
good luck
Thanks for the prompt reply, I feel more confident doing this after reading that. Unfortunately I've no spare USB cable to try this with at the moment, but having looked further I've noticed my battery has a bulge in it, so I doubt there's much point in trying this with this battery.
I did however successfully manage to flash the sbf file (according to RSD Lite) using my friend's battery - but the phone still doesn't boot. Given that my phone isn't going to be right with the current battery - I think my best option now is to take it back to T-Mobile, tell them the battery has done some damage.
simon211175 said:
Thanks for the prompt reply, I feel more confident doing this after reading that. Unfortunately I've no spare USB cable to try this with at the moment, but having looked further I've noticed my battery has a bulge in it, so I doubt there's much point in trying this with this battery.
I did however successfully manage to flash the sbf file (according to RSD Lite) using my friend's battery - but the phone still doesn't boot. Given that my phone isn't going to be right with the current battery - I think my best option now is to take it back to T-Mobile, tell them the battery has done some damage.
Click to expand...
Click to collapse
did you wipe the cache/ data after you flashed the sbf? if you didnt you may want to give it a go before you send it off. it may spring to life once you have done that.
I don't get that option - the phone doesn't reboot. RSD Lite said it did, but all I actually got was a blank screen.
simon211175 said:
I don't get that option - the phone doesn't reboot. RSD Lite said it did, but all I actually got was a blank screen.
Click to expand...
Click to collapse
It looks real bad. You sure the battery didn't die in the flashing process.?
Also try booting into recovery and do a wipe.
It's entirely possible that the battery died during the flash.
I cannot boot in to recovery - the phone doesn't get that far!
I've sent it back to be repaired. hopefully they'll do it under warranty, but if not it's only going to cost around £60 to buy out the remainder of my contract so if the repair costs more I've got that as a backup option.
Thanks for all your help guys.
You can cut an old wall charger but if you can't measure the voltage to know what wire have 5 volts and 0 Volts , and you can hold the wires 5V to plus on akku and 0 to minus and the supply would load..... you can left the batt out of the device...
Wait 10 till 15 min ,for save check if batt getting hot, boot into stock recovery and factory reset your phone
If you can't enter recovery you should be able to enter boatloader
If there is battery low can not program ..load akku.. or ready to program which means .... flash rom with rsd, factory reset , reboot, have fun
i did this two times, flash with low batt one of with not loading batt in dev - i charged with Nokia wall charger cable
If only battery is too empt and briked batt loader.......
If boot loader is briked by bad flashing search Google......
But i mean ciao loved defy
And don't forget : factory reset is always after you changed your rom....
Wiping cache/dalvik cache in only installing new nightly
Sent from my MB526 using xda app-developers app
so, here's my update.
You will recall (see two posts up) that I gave my phone back to T-Mobile on 20th August for a repair. I got my phone back today (+18 days). Here's how it went:
Day 1
Took phone to T-Mobile store. Informed them my battery had a strange lump, which I suspect had fried my phone somewhere. They advised they would send it to the repair centre the following day. No courtesy phones available so I'd be living in the 1980s for a while.
Day 10.
Phone actually arrives a the repair centre. I have no idea where the repair centre is, but I'm guessing really really far away.
Day 15.
Repair centre advise my battery is faulty and to replace would cost me £26.40 for a genuine Motorola battery. Advised repair centre that I told them my battery was broken, and asked why it took them 15 days to repeat that back to me. Also advised them I would rather by my genuine Motorola battery from Amazon for £11.95. Gave them a link in case they want to update their price lists.
Day 17.
Repair started on actual phone.
Repair finished. Yep - the repair took less than 24 hours.
Day 18.
Phone returned to store. it took 24 hours to get there, so I'm assuming the post travels down hill only on the way back.
Picked up phone from store, all set to complain about poor service etc. Noticed brand new battery I hadn't paid for sitting in the returns package. Kept quiet. Left store promptly.
So now I have a working Defy once more (Hurrah).
Obviously I've rooted it already in order to get Titanium Backup to restore all my apps.
Now I have stock 2.2 Blur running on my phone (Boo!), and with only a few months remaining on my contract, I'm not sure if I want to risk loading a new ROM again (I'll reread this once I've loaded a new ROM next week, for sure).
Hey guys, anyone got a 2.17.61.3 stock nandroid backup for ORANG001 (Orange UK)?
Struggling to find it uploaded anywhere.
Need this or the custom ruu to use the downgrading trick to update my hboot.
Thanks!
Its in here
http://forum.xda-developers.com/showthread.php?t=1975140 :thumbup:
The dropbox link is broken sadly
Then you have to wait until its fixed, or when bugsy get the chance to host it on his sire
Yeah :s
Trying to update my hboot, because right now the phone randomly turns off and requires me to hold down the power button. Also gets stuck on optimizing apps.
Thought I'd ask here in case anyone had it floating around in their download folder.
Thanks though!
Maybe there is a JB firmware in the firmware collection thread to update the hboot and then restore the JB nandroid ?
Your cid and firmware is listed here + firmware download
http://forum.xda-developers.com/showthread.php?t=1957376
That could work! Would I flash the firmware in the same way as I would in the RUU/hboot upgrade guides, or can I skip locking the bootloader and stock recovery?
Like:
fastboot oem lock
reboot
fastboot oem rebootRUU
fastboot flash zip <zip>
re-unlock etc.
Yes thats it
Did all that, stock rom crashed, flashed IceColdJelly and that crashed after a while. Phone won't turn on now like before, might turn on after a while, I always have to hold down the button for a long time now.
Thinking maybe this is a hardware / battery problem although everyone was fine before I when from Carbon 1.3 -> 1.5, going back to 1.3 didn't help.
Not really sure what to do now :s
Do the firmware flash all over ! Then reflash the custom recovery, perform a real good wipe and install the rom again. Helped before when i suggested it with someone who experienced similar problems
Did all that, everything went fine until booting into system again, it crashed pretty much just after setup-up. The screen freezes and the button lights go to full brightness.
Would it be worth completely formatting the SD card too?
Trying to think of anything I'm doing wrong.. I do use the Motorola charger rather than an HTC one but I doubt that matters.
Thanks for helping thus far though!
Also for flashing ? Never use another cable then the original !
And yeah its worth the try. Did you perform a full wipe in the recovery....really all stuff ? Caches, dalvik cache....data, system, factory reset. Then install the new rom and flash the boot.img....also wipe cache after flashing the boot.img
Fastboot erase cache
It looks more like a not good wipe problem to me
OK I did a full wipe this time, system, sd card. I've got TWRP on there now which works fine. I flashed ICJ then the boot.img as well as wiping the cache.
Phone booted up fine was working for quite a while before it crashed again, the phone was plugged in using the Motorola plug charger when it crashed. I've been using a battery pack too which uses the power connection on the back.
The phone wouldn't turn on until I plugged it into USB for a while (no led) and held down power + volume down. I'm going to charge it up to full via usb in TWRP then see if it still crashes without charging and without the battery pack on.
I hope it doesn't because then it could just be I need to get the HTC plug/cable and stop using the case.
If it's a hardware problem then I'm not sure I'll be able to get it repaired as I bought this second hand (with a receipt, I could see if I can proof of purchase) and have unlocked the bootloader etc.
I suppose if the phone won't turn on though they can't know that.
Like i said ..... only use original stuff
Any update ?
It crashed in recovery while making a backup and I haven't manage to get it back on yet, I've ordered a HTC cable / plug though. If I get it on I'll just charge it then turn it off, as when I turn it off (as opposed to it crashing) it turns on normally.
Not really looking good though
Sorry to hear this
Got the HTC plug and nothing seems different, still totally dead.I think it is a hardware failure of some sort, as with all the different software combinations I tried it was crashing regardless. (At least that's what I tell myself.)
I'm going to see if I can get it repaired on warranty and hope they don't check the IMEI.
Thanks for all the help
Oke mate ! I hope you get it fixed soon
Good news! HTC have fixed it and sent it back, charging it for a few hours now before I turn it on.
I'm not sure what broke it but I was using the wrong charger for the phone and also a cheap battery case to prolong its daily usage. I'm not sure whether I want to risk flashing roms again but I really don't like sense, it depends if I bricked it or not.