Hello world!
I just got this TV box and I think I broke it.
Looking for some advice please.
It comes with Android 7.1.2 and already rooted
I installed SuperSU and it asked if I wanted to update the binaries. So I did. Now the device won't boot at all.
I pressed the reset pin and wiped the system cache as well as done a factory reset. However it still won't boot.
I don't really know where to go from here as I don't know where to get the ROM from and reinstall it. Or even how for that matter.
The logo that comes up when it tries to boot is MBOX.
I would appreciate any suggestions and help.
Thank you for reading!
Any ideas anyone please?
Hi!
I did do the very same on mine MBOX H96 Pro+ 3g/32g/9377 , and
I've used the USB flash utility (you need a strange male-male usb cable) to flash this firmware:
https://androidtvbox.eu/new-firmware-h96-pro-tv-box-3gb-ram-amlogic-s912-20170602-release/
By using this utility:
https://mega.nz/#!k8hkBDxK!6RVuhh089bT_C_Bdn_LmbicenlIEFYj61OoDMsVqH8A
With these license files:
https://mega.nz/#!o8w0nKYR!J4_6kjS3j6TsgE1Ytl12OnnHnu8aCHb1AKppmh8xVD0
It is 7.1.1, I think, but it made the box boot again. For the moment I'm keeping SuperSU WITHOUT updating SU, and it works well in asking for Root rights when apps require them, but I'm searching for roms which can be rooted with Magisk, and I found this, which seems interesting BUT I haven't tested it:
http://freaktab.com/forum/tv-player...6-scv4a-7-1-2-ddr3-ddr4-and-9377-wifi-chipset
Hope this helps!
Where is the reset button or i have to use toothpick and press thru the av hole then sinultaneously power on the power plug to get into recovery mode ..please help...i am also stuck at boot when updating the binaries of the supersu
The same thing happened to me, I installed Supersu and did not start again.
I burned an image on an SD card and used a toothpick but had an added problem: If I removed the toothpick, the process stopped.
I stayed the whole process by pressing the toothpick.
If I stopped pressing with the toothpick the process stops .
When finished, remove the toothpick quickly or start again.
Same to me, today installed super su and now won't boot. Thanks, tomorrow I will try this solution. I have another box, the same. It's possible to clone the box upon the broked one?
Glad I skipped installing SuperSU on my device
7.1.2 firmware
https://drive.google.com/file/d/1x0rkkYRrmtKke1QiN21-0KqLsXc30v16/view?usp=drives there is no su but is rooted, do not update su
Help. I think my 4 mths old H96+ is dead. I tried updating the firmware using SD card burn method. I pressed the reset button and inserted power. The green Android robot appeared showing it was flashing and immediately I stopped pressing the button. The screen went blank and the blue light went off. Thereafter the H96 won't turn on. No blue light but there is light at the optical out connector. Is the H96 fit for the bin.
Mine is MBox too BTW Have you tried booting to recovery I managed to by pressing reset 3x then held for 10 secs around ten secs no sure which side of 10 tho soz cus one way will go update one to fastboot and one to recovery
---------- Post added at 01:10 PM ---------- Previous post was at 01:08 PM ----------
Here is the firmware I've been using...
Stock: https://drive.google.com/file/d/1x0rkkYRrmtKke1QiN21-0KqLsXc30v16/view?usp=drivesdk
Supercelerons ATV http://freaktab.com/forum/tv-player...b-scv7a-7-1-2-ddr3-ddr4-and-9377-wifi-chipset
curiou5 said:
Help. I think my 4 mths old H96+ is dead. I tried updating the firmware using SD card burn method. I pressed the reset button and inserted power. The green Android robot appeared showing it was flashing and immediately I stopped pressing the button. The screen went blank and the blue light went off. Thereafter the H96 won't turn on. No blue light but there is light at the optical out connector. Is the H96 fit for the bin.
Click to expand...
Click to collapse
What a shame. It is good box but didn't last. It was having some issues before I decided to give it an upgrade.
curiou5 said:
What a shame. It is good box but didn't last. It was having some issues before I decided to give it an upgrade.
Click to expand...
Click to collapse
Sorry i only seen your post today you need to get the right image for your box and then flash it it appears that you are flashing a different software and its conflicting your ram thas way it turns off aftwr flashing the boot, get the right firmware and you iwll be fine, same happend to me but know all is well sd card flashing is the safest one good luck
Enviado do meu GT-N8000 através do Tapatalk
PTHugo said:
Sorry i only seen your post today you need to get the right image for your box and then flash it it appears that you are flashing a different software and its conflicting your ram thas way it turns off aftwr flashing the boot, get the right firmware and you iwll be fine, same happend to me but know all is well sd card flashing is the safest one good luck
Enviado do meu GT-N8000 através do Tapatalk
Click to expand...
Click to collapse
Thanks.
I have open up the box and printed on the circuit board is 2017-02-10 which I am assumed is the date. The other info is H96-S912-TVBOX(DDR4)-VO.2. Does it mean that the RAM is DDR4 RAM and not DDR3 RAM as stated in the market place.
Update : Found firmware for DDR4 RAM and managed to flash the original H96 Pro+ firmware.
I followed the steps found here http://freaktab.com/forum/tv-player...k-gt1-ultimate-scv2-atv-android-tv-ddr4/page3 post #37.
Edit :
First I tried the Super Celerons Standard Android firmware from http://freaktab.com/forum/tv-player-...l-android-ddr4 but my wifi could not connect. Then I download and flashed the firmware from https://mega.nz/#!74hSDb5A!nkqPR4tnp...bvCDquoJ5BJok0 and the box is back to how it was when I first bought it.
Man I wish I saw this thread before installing supersu... totally bricked my box. Tried a bunch of firmwares & sd cards, it's not going so well
pete.xda said:
Man I wish I saw this thread before installing supersu... totally bricked my box. Tried a bunch of firmwares & sd cards, it's not going so well
Click to expand...
Click to collapse
You must first find out whether your RAM is DDR3 or DDR4. As I have learned there are a few versions of this H96 Pro+. Flashing DDR4 firmware on DDR3 version and vice versa will not work.
How I unbricked mine after an age!!
What worked for my Banggood H96 Pro plus box to unbrick it. First - it says on the back of the green board in the box CZ-S32-V2.2/ 3+32/9377 DDR3. I was trying to update the firmware with the burncard method connected to the TV with HDMI and reset button and power connect like I'd done many times before with one of the Tanix 8 Max roms (well it had worked before), only not this time and it bricked hard. Nothing was working to put life back into the box with either different roms with burncard method or that USB burning tool method (what disastrous software that is). My box did have the front blue light and back red one on when I plugged the power in and something I had read said that if that was the case I should be able to get the box resurrected. Then I saw this segment on Youtube - https://www.youtube.com/watch?v=CUfKNNgxb9E
So, I moved back to my TV with my sdcard done by burn card maker with this rom - aml_7.1_s912_q9377-H96PROPLUS_KDMC_mac-20171129_Shonk.img. I don't remember which pin combo tripped the wonderful pic of the android robot on screen (first time in over 2 months that I saw anything visual from my H96) with the UPGRADING below it (I had the power in, the reset button activated, and of course the HDMI plugged in when I was routing around for the the correct pin combo)(I was not looking at the screen because those tiny pins required my attention but the sound caused me to look up at the screen). As soon as I saw the little robot I pulled the paper clip from the box and let it run on it's own to completion. A check mark came on the little robot and I pulled the power and put it back in and it took off with that H96 Pro + splash screen and finished the set up. To finish - it's seems like a wonderful rom so far. Wifi works great and I have not run into any problems so far after 2 days - it is faster than my Nexbox A1 2gb/16gb s912. Did I miss anything? Just ask.
McGiles said:
What worked for my Banggood H96 Pro plus box to unbrick it. First - it says on the back of the green board in the box CZ-S32-V2.2/ 3+32/9377 DDR3. I was trying to update the firmware with the burncard method connected to the TV with HDMI and reset button and power connect like I'd done many times before with one of the Tanix 8 Max roms (well it had worked before), only not this time and it bricked hard. Nothing was working to put life back into the box with either different roms with burncard method or that USB burning tool method (what disastrous software that is). My box did have the front blue light and back red one on when I plugged the power in and something I had read said that if that was the case I should be able to get the box resurrected. Then I saw this segment on Youtube - https://ru-clip.com/video/CUfKNNgxb9...in-method.html
So, I moved back to my TV with my sdcard done by burn card maker with this rom - aml_7.1_s912_q9377-H96PROPLUS_KDMC_mac-20171129_Shonk.img. I don't remember which pin combo tripped the wonderful pic of the android robot on screen (first time in over 2 months that I saw anything visual from my H96) with the UPGRADING below it (I had the power in, the reset button activated, and of course the HDMI plugged in when I was routing around for the the correct pin combo)(I was not looking at the screen because those tiny pins required my attention but the sound caused me to look up at the screen). As soon as I saw the little robot I pulled the paper clip from the box and let it run on it's own to completion. A check mark came on the little robot and I pulled the power and put it back in and it took off with that H96 Pro + splash screen and finished the set up. To finish - it's seems like a wonderful rom so far. Wifi works great and I have not run into any problems so far after 2 days - it is faster than my Nexbox A1 2gb/16gb s912. Did I miss anything? Just ask.
Click to expand...
Click to collapse
the video is not there anymor can you post a picture please
Sent from my ATVXperience using Tapatalk
Hey Shores,
please, provide another download link. The source from the link you provided is infected heavily.
Zoli
Hi,
For the second time no more signal from the h96 pro plus hdmi output the front blue led don't light on. I have returned the box to the Chinese supplier and after 2month the box come back with no defects found....
This time after 6 month same problem.
But I have connected the USB output from the box to the PC. (Idea was reload firmware). But suddenly the blue LED light on. Now the box is working properly by using one TV USB port without the external power supply.
Is there any other way for solve the problem?
If not I hope this message will help others h96 user's ..[emoji6]
Envoyé de mon MI 4S en utilisant Tapatalk
New Link to try
PTHugo said:
the video is not there anymor can you post a picture please
Sent from my ATVXperience using Tapatalk
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=CUfKNNgxb9E
Related
Hello to all.
I tried to find an answer for my troubles here by a few hours but unfortunatelly i didnt. So I wonder to find help here thanks to XDA specimens society.
Problem symptoms
1 I bought One mini in USA. Seller provided a photo with bootloader screen which I attach below.
2 When received device, it didnt boot up at all. Only a HTC logo appeared at white background and screen began black.
Than when I press a power button, a touch buttons under screen flash 10 times and stop. Again press of power button gives one short vibration and nothing later happens.
I noticed that alu cover at down side (battery area) becomes warm and it is working till battery power goes to 0%
3 When "working", mobile is detected by Windows system connected by usb. It show mass storage, modem and not recognized device.
4 Also it shows a battery charging animation if power button was not pressed before and battery is charged from 0%.
After a two weeks in my desk it still shows 99% what means that battery is mint condition and mobile is not working when not powered on before.
Serviceman said that I have broken bootloader and it should be repaired.
Finally I found out that I can install a new ROM.
So I downloaded a
drivers (recommended here at another article)
TWRP recovery file 2 7 0 5 m4kk
customized Rom by CodenameLungo version CM 11
What I should do now? What tools install? How to putt all these into phone memory if I have not acces to bootloader screen?
If you know article which solve my problem than I will be thankfull for a link.
I know that for most of you these questions are stupid but I m not a pro and will be thankfull for a little help
THX in advance for all who will try to help me.
LukeKaz said:
Hello to all.
I tried to find an answer for my troubles here by a few hours but unfortunatelly i didnt. So I wonder to find help here thanks to XDA specimens society.
Problem symptoms
1 I bought One mini in USA. Seller provided a photo with bootloader screen which I attach below.
2 When received device, it didnt boot up at all. Only a HTC logo appeared at white background and screen began black.
Than when I press a power button, a touch buttons under screen flash 10 times and stop. Again press of power button gives one short vibration and nothing later happens.
I noticed that alu cover at down side (battery area) becomes warm and it is working till battery power goes to 0%
3 When "working", mobile is detected by Windows system connected by usb. It show mass storage, modem and not recognized device.
4 Also it shows a battery charging animation if power button was not pressed before and battery is charged from 0%.
After a two weeks in my desk it still shows 99% what means that battery is mint condition and mobile is not working when not powered on before.
Serviceman said that I have broken bootloader and it should be repaired.
Finally I found out that I can install a new ROM.
So I downloaded a
drivers (recommended here at another article)
TWRP recovery file 2 7 0 5 m4kk
customized Rom by CodenameLungo version CM 11
What I should do now? What tools install? How to putt all these into phone memory if I have not acces to bootloader screen?
If you know article which solve my problem than I will be thankfull for a link.
I know that for most of you these questions are stupid but I m not a pro and will be thankfull for a little help
THX in advance for all who will try to help me.
Click to expand...
Click to collapse
Do you know how to enter bootloader? When the phone is off, you hold the Volume Down Button and the power button until phone boots up (several seconds). If you can access bootloader this way, we have a chance to help you out.
Yes I read about this method. Unfortunatelly it didnt work. Or i tried power+vol up.
Today I visited another specialist and left it for diagnostic purposes. They suppose that bootloader is damaged and should be reconstructed (if I can name it this way).
They were listening to me carefully before said that wold try to connect it with computer.
I hope they know what to do. Will call them on Friday and post here what s going on in their opinion.
LukeKaz said:
Yes I read about this method. Unfortunatelly it didnt work. Or i tried power+vol up.
Today I visited another specialist and left it for diagnostic purposes. They suppose that bootloader is damaged and should be reconstructed (if I can name it this way).
They were listening to me carefully before said that wold try to connect it with computer.
I hope they know what to do. Will call them on Friday and post here what s going on in their opinion.
Click to expand...
Click to collapse
OK. Good luck with it.
Bootloader was reconstructed and now it is running to the boot menu. But serviceman has a problem with flashing ROM. He said that during instalation system cant rebuild certificate and all proces fails at 3%.
May anyone point me any link with instructions what should be done at this situation? We have a deal that on Monday i take mobile back, even if rom will not be flashed correctly...
He confirmed that this phone comes from ATT broadband and is not sure if that change anything or not.
Also suggest that previous owner tried to modify ROM by himself and thats why bootloader was damaged...
Hello. I have problems with my device, a Motorola Razr xt925 HD. It doesn't start, it just keeps the green led blinking when connected to wall charger, and when I plug the USB, makes a sound of a new device detected but only for a few seconds then it makes a sound of an unplugged device, and so on. It doesn't respond to any combination of buttons. I let it charging overnight, even though the battery was nearly full before this happened. Don't know if this is relevant but before this happened, I was going to flash stock Retail Brazil firmware by fastboot and got a flash failure. I turned it off and then it wouldn't turn on again. I never had this happened, I had problems but I always solved them all. Not this time hopefully you guys can help me or tell me what it could be, because I doubt it was the battery. I leave you a video showing my case.
i dont know for certain but the only time i see that green light is when battery is ou and i put it to chrge. Could your phone be in apfastboot and can t charge. It is a bit of a tough situation to troubleshoot.
Did you try keys combo to put it in fastboot, and test it by flashing
or maybe use rsd lite see if it shows you device connected? maybe then you can flash stock
i am sure there are other possibilities, let s hear from you
There's no way to enter in Fastboot by key combos and RSD lite doesn't show my device :/ maybe I need a factory cable, just in case that the battery is empty. I need more suggestions please
me paso lo mismo
did you find any solution?
im having this problem after i start using KK 4.4.2 seems like the phone go to sleeping mood by it self while my screen is locked so i have to keep clicking at power and volume up and down to restart the device now im looking for an update or a fix for this problem, another problem is the device WIFI do not catch my house signal while im away 10 feet from the house the software have bugs
I've been using CM 11 (KK 4.4.4) with no issues. This is a flash problem or maybe the battery. My phone is still dead btw I see that two more people are having the same problem here... we need a solution please.
chuYxP said:
I've been using CM 11 (KK 4.4.4) with no issues. This is a flash problem or maybe the battery. My phone is still dead btw I see that two more people are having the same problem here... we need a solution please.
Click to expand...
Click to collapse
i think your your device is dead.
this exact thing happened to me.
it happened on september, i was forced to get a new device.
i love this phone but it was dead.
i hope a fix comes through i would like to have it back
I ll take one of your hand, I need parts if interested
Any update with this? Did you try with a factory cable?
I'm going through the same thing , I read the other day that and the driver installed and nothing more .
keep trying to revive my device.
I'm going through the same thing. When I plug it into my pc , under device manager it shows "Human Interface Device" then it unmounts itself then remounts itself then unmounts. Over and over..... I've even replaced the battery.
I was running stock rom with just root, phone was working great. phone rebooted, screen never came back on but when i connect it to my computer it sees it in adb..........
Any advice would be great.
Thank you
kilroy1stcav said:
I was running stock rom with just root, phone was working great. phone rebooted, screen never came back on but when i connect it to my computer it sees it in adb..........
Any advice would be great.
Thank you
Click to expand...
Click to collapse
This thread for the droid Ultra might interest you: http://forum.xda-developers.com/droid-ultra/general/droid-ultra-maxx-brick-recovery-t2830806
There is some discussion of the Razr HD in this thread. It looks like someone with an unlocked device would need to dd their bootloader partition for this method to work.
A few years later .... Any solution? rsrsrs
any update on this scenario?
i have this situation too and the time could give us an answer, i am searching again, i took my device to some 'phone repair stores' and in less than 5 minutes they told me that the phone was dead, but i have my last doubts
Just to add an update here
I ended up with the Green light only and blank screen after trying to fix a battery issue, despite getting a number of batteries my phone wasn't accepting the batteries.
I remembered a battery issue a long while back, so went to reflash my phone to see if it resolved it.
I ended up with the green light and blank screen and no matter what buttons, it would just make a noise then keep rebooting.
I ended up using the Unbrick bat file.
RSD Lite was briefly showing a Medfield device of something starting with Med, but since the phone kept rebooting I couldn't reflash it again.
I did the Pwr and Vol down and as soon as I saw the device, I clicked the UnBrick bat and it managed to get my Moto logo up.
I then booted to Fastboot mode and reflashed and my phone is back,
See this link for the UnBrick, but when you do it, you have to be fast to catch it while the device is seen, otherwise the phone reboots after 4s or soo.
Softely Unbrick XT890 Razr i - Really Unbrick the Zombie
Well do not think that this thread is one among others. It's my experience when i messed up with my Razri. I wish I had this before, so I'm sharing it with you ! Every has his experience and a way to do it, so this is mine First I searched...
forum.xda-developers.com
Hello,
Today I tried to sideload the OTA update to Android 5.0.1 (because my Nexus is root and it would not let me update normally), but there was an error saying missing file in system.img. So, after that, I got stuck at Google logo screen. I entered stock recovery (I never installed a custom recovery) and wiped cache, with no luck. Did a data wipe. No luck. So I tried flashing the factory image for Android 5.0, but right after flashing the bootloader, the device turned off (or it appeared to), the script showed "waiting for device", and the phone never came back. Now it won't turn on at all. I don't know what to do
Thank you for your help
cool1007 said:
Hello,
Today I tried to sideload the OTA update to Android 5.0.1 (because my Nexus is root and it would not let me update normally), but there was an error saying missing file in system.img. So, after that, I got stuck at Google logo screen. I entered stock recovery (I never installed a custom recovery) and wiped cache, with no luck. Did a data wipe. No luck. So I tried flashing the factory image for Android 5.0, but right after flashing the bootloader, the device turned off (or it appeared to), the script showed "waiting for device", and the phone never came back. Now it won't turn on at all. I don't know what to do
Thank you for your help
Click to expand...
Click to collapse
I had the same problem today and i thought that i'll post how i fixed it.
My wife left her N5 charging overnight, this morning the phone was dead, kaput, it won't turn on or show the battery icon. I ended up opening the phone and disconnecting the motherboard and battery following the "Nexus 5 Battery Replacement howto" from ifixit.com.
Long story made short, open the phone, remove the 6 screws holding the motherboard, disconnect the daughterboard and battery connector, wait a few minutes and reconnect them again (Steps 1 to 4, no need to continue), the phone should power on now, if it does, put everything back together and keep enjoying your N5.
The only trick is opening the case , use your nails or a plastic opener tool to pry open the latches then carefully pull out the case, in my N5 there was some light glue applied on the lower part of the case, not a showstopper at all.
Necrosis
works for me too
elfarto said:
I had the same problem today and i thought that i'll post how i fixed it.
My wife left her N5 charging overnight, this morning the phone was dead, kaput, it won't turn on or show the battery icon. I ended up opening the phone and disconnecting the motherboard and battery following the from ifixit.com.
Long story made short, open the phone, remove the 6 screws holding the motherboard, disconnect the daughterboard and battery connector, wait a few minutes and reconnect them again (Steps 1 to 4, no need to continue), the phone should power on now, if it does, put everything back together and keep enjoying your N5.
The only trick is opening the case , use your nails or a plastic opener tool to pry open the latches then carefully pull out the case, in my N5 there was some light glue applied on the lower part of the case, not a showstopper at all.
Click to expand...
Click to collapse
i had some similar experience this morning, phone wont turn on, no charging notifications nothing, and i followed ur instructions and its works fine now, no idea how it happens, but when i open the back i got some burning smell too, anyway the device is working fine now!
anyways thanks
Okay, this one seems slightly different, so anyone who has had the problem and found a solution, I'm all ears. While reflashing the second Q beta (over the second Q beta - I was getting Play Services FCs and rebooting didn't fix it) everything went fine until the command window closed and the phone stayed in the bootloader. After that the PC didn't recognize anything being plugged in or our, it's stuck on slot b, which is unbootable, I can't change it and I can't boot from it, because I can't talk to it. I've removed and replaced the driver, I'm using a USB 2.1 connection, the computer recognizes other phones on that cable, I've used the same combination to flash factory versions and sideload updates all year using exactly the same thing, so ...
Google recommended an RMA, so they did, and Fedex has it on the truck today for delivery but ... has anyone found a way to get this to work without changing the motherboard? (I've treated this battery well, and the phone's been a case since day 1 - who knows what I'm getting.)
Rukbat said:
Okay, this one seems slightly different, so anyone who has had the problem and found a solution, I'm all ears. While reflashing the second Q beta (over the second Q beta - I was getting Play Services FCs and rebooting didn't fix it) everything went fine until the command window closed and the phone stayed in the bootloader. After that the PC didn't recognize anything being plugged in or our, it's stuck on slot b, which is unbootable, I can't change it and I can't boot from it, because I can't talk to it. I've removed and replaced the driver, I'm using a USB 2.1 connection, the computer recognizes other phones on that cable, I've used the same combination to flash factory versions and sideload updates all year using exactly the same thing, so ...
Google recommended an RMA, so they did, and Fedex has it on the truck today for delivery but ... has anyone found a way to get this to work without changing the motherboard? (I've treated this battery well, and the phone's been a case since day 1 - who knows what I'm getting.)
Click to expand...
Click to collapse
I would try skipsoft Android toolkit. It might not recognize your phone right off. Try uninstalling and reinstalling USB drivers through the toolkit with phone plugged in. Downloading and installing firmware, etc. It got me out of a bind once. Worth a try.
Hi, I got to this "not bootlable" situation for second time when I was downgrading from Q beta 2 back to Pie. But I am probably lucky one Same situation like you, only bootloader screen and PC didn't see my phone, but I was able to fix it I was in bootloader, connected to PC and I hold power button for long time (2 minutes maybe more). Phone was still restarting, bootlader screen, black screen, bootlader, black.....sometimes it vibrated. After this 2 minutes I just tried "flash-all.bat" command and phone arose from the dead and is working.
somin.n said:
Hi, I got to this "not bootlable" situation for second time when I was downgrading from Q beta 2 back to Pie. But I am probably lucky one Same situation like you, only bootloader screen and PC didn't see my phone, but I was able to fix it I was in bootloader, connected to PC and I hold power button for long time (2 minutes maybe more). Phone was still restarting, bootlader screen, black screen, bootlader, black.....sometimes it vibrated. After this 2 minutes I just tried "flash-all.bat" command and phone arose from the dead and is working.
Click to expand...
Click to collapse
This should work. Had something similar happen to me, keep holding power for about 10 seconds or so while it keeps rebooting until you feel the phone vibrate. Release the power button, connect to the computer and it should detect it then.
https://forum.xda-developers.com/showpost.php?p=78744315&postcount=31
somin.n, I just wanted to thank you for rescuing my phone. After a lot of problems with Q, I decided to go back to Pie and bricked the bootloader. I tried your trick and it came back - but ... I flashed Pie, it rebooted and hung on the "G" screen. So I did a factory reset and resigned myself to use the refurb they sent me. This morning I tried once more and flashed Pie. Voila! The phone works. The original, non-refurb, phone. So now, since the refurb they sent me has the "bootloader unlockable flag = '1', but the bootloader won't unlock" problem, which seems to be common, there's another refurb on its way. So on Tuesday, I'm returning two refurbs to Google.
But you saved my phone so, again, thank you.
Rukbat said:
somin.n, I just wanted to thank you for rescuing my phone...
Click to expand...
Click to collapse
Hey, you are welcome I was really lost when it happened to me, because google is not selling phones in our country officialy, so no RMA and secondly, my pixel is my bussiness phone so I can't tell to my boss that my phone is broken because of flashing beta builds Yeah, I had to find a solution
Metro variant on latest OTA
OEM unlocked
flashed twrp.img
installed magisk 21.4.zip
dog got in confrontation with phone in my hand and in twrp I hit a bunch of crap.
now i have brick -- no power on, no usb trigger, no vol dn+power....nothing
adb and fastboot dont see it.
possibilities....may have restored the SELinux
May have selected the slot b
anything else in twrp advanced tab......
android and linux knowledge at beginner to intermediate levels if im honest
what are my options?
2clacaze said:
Metro variant on latest OTA
OEM unlocked
flashed twrp.img
installed magisk 21.4.zip
dog got in confrontation with phone in my hand and in twrp I hit a bunch of crap.
now i have brick -- no power on, no usb trigger, no vol dn+power....nothing
adb and fastboot dont see it.
possibilities....may have restored the SELinux
May have selected the slot b
anything else in twrp advanced tab......
android and linux knowledge at beginner to intermediate levels if im honest
what are my options?
Click to expand...
Click to collapse
On the computer Under device manager does anything pop up when phone is plugged in?
JimmyJurner said:
On the computer Under device manager does anything pop up when phone is plugged in?
Click to expand...
Click to collapse
nothimg
2clacaze said:
nothimg
Click to expand...
Click to collapse
Not even showing this : Qualcomm HS-USB QDLoader 9008????
JimmyJurner said:
Not even showing this : Qualcomm HS-USB QDLoader 9008????
Click to expand...
Click to collapse
Not a thing under devices, removable our otherwise
You said that it won't power on? Correct? "No power on".. I'm assuming that's what you meant.
If that's the case, it's obvious why nothing shows up when you connect to the computer. I mean, it sounds like you have a fried unit.
I'm not even sure how you could do that in twrp. Lol.
The only phone I've ever had that wouldn't power on, was due to water damage (sweat damage actually). Which I'm still fired up about. I had a pixel 3a. Just 6 months old. Had a case on it.. was walking and talking to my niece, and pouring sweat as I walked/hiked. We hung up, and I noticed I had phantom touches all over the screen. I wiped the phone down, powered it down, sat it in rice for 12 hours. Turned it back on, and it was worse than before. So many phantom touches that I couldnt even power it down. Then volume down and power wouldn't take me to recovery so I could power it off.
I literally just had to sit there for 2 hours as it fried itself alive from water damage. Next morning, I noticed no warming on quick charge. No screen paper. No vibe on startup. Plugged into laptop, nothing registered.
It wasn't bricked. It was gone.
I know it's not a waterproofed phone. But sweat? Destroying a $400 phone? Give me an effin break.
Luckily, I pay my verizon bill with mastercard.. and all mastercard users (even debit cards) have phone insurance built into it. I called them, submitted the paperwork. (Copy of phone bill, copy of bank statement showing I used the mastercard, and a copy of the estimate showing it was a total loss. $349). The deductible was $50.. so 4 business days later, they deposited $299.99 in my account. And I bought the g stylus with it. And when I went to Walmart to buy it, it wouldn't ring up. It was supposed to be $299.99. I found a price match of $249.99. and when he was trying to ring it u, it wouldn't show up on their system. They did a search for it on their website, and he didn't know the difference between a g stylus and a g fast. I got it for $129.99. unlocked. (Was $179.99 on the website, and I had found a 50 off price match for the 299 priced phone earlier, so they gave me the 50 off 179.99. so needless to say -- I got a heckuva deal.
The g stylus is basically a pixel 3a. Except a bigger screen, better battery, and a stylus. The 665 actually performs better on multi ore than the 670 does. Because the 665 has 4 cores at 2ghz, rather than just 2 like the pixel. And the gpu is over closed to almost 1ghz on this phone. So no complaints other than picture quality. The pixel 3a is among the best camera phones ever made to this day. But with the g stylus, running a heavily tweaked and microtuned gcam mod.. its not a huge huge difference unless you are zoomed in. Then it's obvious.
It's possible you tried to boot into a different slot. Hold power and volume down until the phone boots into recovery. Unless you deleted the recovery image, it should still boot into recovery. From recovery you can flash a fresh install of Android or attempt to boot into twrp. I.e. "fastboot boot c:/'location-of-twrp.img'" as to attempt to boot into slot a. I had the same problem and just installed Android one from lollinets site. The variant of Android 11 that works for our metro moto g pro is "11 rprs31.q4u-20-28".
Volume up and power should take you to fastbootd. If hard ware keys aren't working it's either a dead battery or hard bricked. In which case, be careful with the next one.
ok heres the deal .... i came into this thread late but i have made every mistake possiable with this device and have dang near any file to fix the mistakes most of which were on purpose ... i pulled a couple noob reinforced actions tho like flashing sofiar instead of sofiap .... if you still need help brotha hit me up we will team viewer and ill teach you how to correct your issues no prob
sings ..... one of these things is not like the others .......
Vampire Lord said:
ok heres the deal .... i came into this thread late but i have made every mistake possiable with this device and have dang near any file to fix the mistakes most of which were on purpose ... i pulled a couple noob reinforced actions tho like flashing sofiar instead of sofiap .... if you still need help brotha hit me up we will team viewer and ill teach you how to correct your issues no prob
Click to expand...
Click to collapse
I have similar issue. When i connect to charger the white led flashes for exactly one minute then stops. Plug to computer i get nothing. Installed qualcomm drivers still nothing. Tried edl cord no change.
Im not sure what caused this. I was going to root so i unlocked bootloader. Flashed cwm. After flashing cwm its had errors mounting a couple partions. I powerd off and started digging here and on google, found couple options to try. When i tried to power up it was dead. No responce, no conection to computer... just one min of flashing led when i plug into wall charger. Any help would be greatly appreciated
Can you hard reset into recovery
If not does adb recognize your device
If it does you can always force boot twrp from debug
Shane8705 said:
I have similar issue. When i connect to charger the white led flashes for exactly one minute then stops. Plug to computer i get nothing. Installed qualcomm drivers still nothing. Tried edl cord no change.
Im not sure what caused this. I was going to root so i unlocked bootloader. Flashed cwm. After flashing cwm its had errors mounting a couple partions. I powerd off and started digging here and on google, found couple options to try. When i tried to power up it was dead. No responce, no conection to computer... just one min of flashing led when i plug into wall charger. Any help would be greatly appreciated
Click to expand...
Click to collapse
I did exactly this. But I get no flashing LED when I plug into wall charger.
I've tried holding vol down + power for 20+ seconds, nothing.
I've tried holding vol up + power for 20+ seconds, nothing.
When I connect to my computer I no longer see the 9008 in device manager.
abense said:
I did exactly this. But I get no flashing LED when I plug into wall charger.
I've tried holding vol down + power for 20+ seconds, nothing.
I've tried holding vol up + power for 20+ seconds, nothing.
When I connect to my computer I no longer see the 9008 in device manager.
Click to expand...
Click to collapse
Hardbricked mine - I have the metro G Stylus 2021. |
Switched to slot B and now I have nothing.
acrinym said:
Hardbricked mine - I have the metro G Stylus 2021. |
Switched to slot B and now I have nothing.
Click to expand...
Click to collapse
This section is for the 2020 G Stylus.