I deleted the launcher that came with the phone to save space because I had nova launcher installed, it is a mtk phone and I dont have recovery. It was acting up this morning so I did a factory reset, stupid Chinese mtk people decided not to put a setup on this thing so I am not signed into my google account, my sim is not activated and spflashtools cant see my phone i cant use mtkdroidtools as i use linux. PLEASE HELP
Your phone can turn on or not
It turns on but stays at the boot screen as the launcher has been deleted
did you enabled usb debugging if so you can use a pc to solve this problem
and i do not get what no usb debug sim not working means
ndemon said:
I deleted the launcher that came with the phone to save space because I had nova launcher installed, it is a mtk phone and I dont have recovery. It was acting up this morning so I did a factory reset, stupid Chinese mtk people decided not to put a setup on this thing so I am not signed into my google account, my sim is not activated and spflashtools cant see my phone i cant use mtkdroidtools as i use linux. PLEASE HELP
Click to expand...
Click to collapse
If you can go into recovery you can use USB Debugging. Then go to recovery. Plug your phone into the computer and get the stock launcher. Now do
Code:
adb root
adb push launcher.apk /System/App
Now reboot. Make sure that you have root and that you have the right launcher file (the one you got with the phone)
He has no recovery by the way
Fastboot? Bootlader? Anything?
Yes you can use fastboot and your pc android debugging bridge to push any launcher apk to your system.
But for that you have to setupbyoue adb and fastboot driver on your pc
---------- Post added at 02:30 PM ---------- Previous post was at 02:29 PM ----------
Can you tell me which device you have
droid_god said:
Yes you can use fastboot and your pc android debugging bridge to push any launcher apk to your system.
But for that you have to setupbyoue adb and fastboot driver on your pc
---------- Post added at 02:30 PM ---------- Previous post was at 02:29 PM ----------
Can you tell me which device you have
Click to expand...
Click to collapse
I have this http://www.amazon.com/ZGPAX-Android-1-54inch-Multi-point-Bluetooth/dp/B00OPO984G it runs android 4.4.2 and there’s no recovery and I have no idea how to get into fastboot, ADB wont even see the device.
EDIT: And I use linux, so I wont have to set up drivers because the linux kernel includes them.
Did that watvh have a volume hard keys on it or not
i can do any thing except damaging your device. GOD DOES NOT DO THAT
droid_god said:
Did that watvh have a volume hard keys on it or not
i can do any thing except damaging your device. GOD DOES NOT DO THAT
Click to expand...
Click to collapse
It has a volume up key, a power key and a soft home button, menu button and back button. But no volume down.
Just power off and press both hard keys and see what happens
i can do any thing except damaging your device. GOD DOES NOT DO THAT
droid_god said:
Just power off and press both hard keys and see what happens
i can do any thing except damaging your device. GOD DOES NOT DO THAT
Click to expand...
Click to collapse
It starts booting and then gets stuck, as always
I cant even see notifications
The device is having a sence that an sd card is inserted and oops it reboots.
This is happening with every sd card
i can do any thing except damaging your device. GOD DOES NOT DO THAT
Lmfao sucks for u xD
Hmm than its a hardware problem can nly be reapired
i can do any thing except damaging your device. GOD DOES NOT DO THAT
droid_god said:
Hmm than its a hardware problem can nly be reapired
i can do any thing except damaging your device. GOD DOES NOT DO THAT
Click to expand...
Click to collapse
It isn't a hardware problem as I explained in the first post.
Related
So recently my phones been acting up. I had just installed the TEUV kernel from trinity and began noticing some irregularities.
1) the home button started to open the desk clock
2) the power button stopped turning off the screen
3) in bootloader, the up and down volume rocker doesn't work
So naturally i tried to wipe the rom and start new again. However, the phone won't boot up and most far i can go is bootloader. I cant do anything here because the volume rockers don't respond. I tried doing it manually throught ADB but the computer doesn't see the device.
any help guys? I'm really out of ideas so any would be great.
baolongn said:
So recently my phones been acting up. I had just installed the TEUV kernel from trinity and began noticing some irregularities.
1) the home button started to open the desk clock
2) the power button stopped turning off the screen
3) in bootloader, the up and down volume rocker doesn't work
So naturally i tried to wipe the rom and start new again. However, the phone won't boot up and most far i can go is bootloader. I cant do anything here because the volume rockers don't respond. I tried doing it manually throught ADB but the computer doesn't see the device.
any help guys? I'm really out of ideas so any would be great.
Click to expand...
Click to collapse
besides for the home button opening the deskclock, i experience everything else. but for me, its because my power button is broken. sometimes it partially works but acts like its stuck even though its not. in bootloader the volume keys dont work unless i flick the phone with my fingers right by the power button. then every so often the volume buttons work in bootloader. i use the twrp recovery btw, because it has on option to not use the power button to select.
anything else i can do?
my computer cant even recognize the phone for some reason.
baolongn said:
anything else i can do?
my computer cant even recognize the phone for some reason.
Click to expand...
Click to collapse
do you have the drivers installed? what i meant was did it recognize your phone before?
simms22 said:
do you have the drivers installed? what i meant was did it recognize your phone before?
Click to expand...
Click to collapse
Yeah it did when I unlocked the phone.
baolongn said:
Yeah it did when I unlocked the phone.
Click to expand...
Click to collapse
try updating the drivers, or uninstalling then reinstalling the drivers.
---------- Post added at 05:31 PM ---------- Previous post was at 05:28 PM ----------
baolongn said:
Yeah it did when I unlocked the phone.
Click to expand...
Click to collapse
also, try this.. pull your battery for two minutes, then put it back in and try booting. if it boot, you can boot into recovery via the terminal.
via terminal? is that command prompt? oh and what drivers do you think ill need? thanks man.
simms22 said:
try updating the drivers, or uninstalling then reinstalling the drivers.
---------- Post added at 05:31 PM ---------- Previous post was at 05:28 PM ----------
also, try this.. pull your battery for two minutes, then put it back in and try booting. if it boot, you can boot into recovery via the terminal.
Click to expand...
Click to collapse
baolongn said:
via terminal? is that command prompt? oh and what drivers do you think ill need? thanks man.
Click to expand...
Click to collapse
you can install the nexus s driver via pdanets website, thats the easy way http://www.junefabrics.com/android/index.php
download and install the free program(its a tethering app) onto you desktop/laptop, then open it and follow the onscreen instructions. it will install the right nexus s driver for you. you might have to uninstall the other driver, if you had it installed.
about the terminal, yea, its a command prompt right from your phone. if you dont have the terminal emulator installed, you can get a free one from the android market. open the terminal and type..
su(press enter)
reboot recovery(press enter)
i dont use adb at all, i use the terminal emulator instead. there are lots of cool things that you can use it for. for example, i flash/update my recovery through the terminal and sometimes also push boot.img through it to my phone too. plus lots of other stuff
Thanks Simms!
the one problem is I can't turn on my phone either. Its stuck on a bootloop. That is why i'm trying ADB. I'm trying to install PDAnet but its still not locating it. I'm going to try on another computer and check back in a bit.
simms22 said:
you can install the nexus s driver via pdanets website, thats the easy way http://www.junefabrics.com/android/index.php
download and install the free program(its a tethering app) onto you desktop/laptop, then open it and follow the onscreen instructions. it will install the right nexus s driver for you. you might have to uninstall the other driver, if you had it installed.
about the terminal, yea, its a command prompt right from your phone. if you dont have the terminal emulator installed, you can get a free one from the android market. open the terminal and type..
su(press enter)
reboot recovery(press enter)
i dont use adb at all, i use the terminal emulator instead. there are lots of cool things that you can use it for. for example, i flash/update my recovery through the terminal and sometimes also push boot.img through it to my phone too. plus lots of other stuff
Click to expand...
Click to collapse
baolongn said:
Thanks Simms!
the one problem is I can't turn on my phone either. Its stuck on a bootloop. That is why i'm trying ADB. I'm trying to install PDAnet but its still not locating it. I'm going to try on another computer and check back in a bit.
Click to expand...
Click to collapse
you pulled the battery for two minutes before powering on this time?
yeah, endless bootloop
other computer is the same problem
simms22 said:
you pulled the battery for two minutes before powering on this time?
Click to expand...
Click to collapse
baolongn said:
yeah, endless bootloop
other computer is the same problem
Click to expand...
Click to collapse
:-\ ......
is there nothing i can do?
simms22 said:
:-\ ......
Click to expand...
Click to collapse
baolongn said:
is there nothing i can do?
Click to expand...
Click to collapse
does fastboot recognize your phone? not adb but fastboot.
what do you mean by that?
simms22 said:
does fastboot recognize your phone? not adb but fastboot.
Click to expand...
Click to collapse
baolongn said:
what do you mean by that?
Click to expand...
Click to collapse
The fastboot program you run in command line. Like ADB but for flashing img's real quick.
im not sure. maybe im not doing it right but on bootloader mode, under device manager, the phone doesn't show up so im guessing USB debugging doesnt work? thanks so much for the responses guys!
any more suggestions?
BlackHawkA4 said:
The fastboot program you run in command line. Like ADB but for flashing img's real quick.
Click to expand...
Click to collapse
holy crap, it suddenly moved in bootloader. it went to recovery but then it automatically pressed reboot -_-
back to square 1 folks
simms22 said:
besides for the home button opening the deskclock, i experience everything else. but for me, its because my power button is broken. sometimes it partially works but acts like its stuck even though its not. in bootloader the volume keys dont work unless i flick the phone with my fingers right by the power button. then every so often the volume buttons work in bootloader. i use the twrp recovery btw, because it has on option to not use the power button to select.
Click to expand...
Click to collapse
baolongn said:
holy crap, it suddenly moved in bootloader. it went to recovery but then it automatically pressed reboot -_-
back to square 1 folks
Click to expand...
Click to collapse
thats how i was the first time i saw it move after i knew the power button was broken now i can get it to move within a few minutes by flicking the back, with the cover removed, between the battery and speaker, when pressing on the volune keys.
Haha i got it to work! went right to recovery and quickly restored my last backup!
finally, the nexus is back. thanks everyone!!!
simms22 said:
thats how i was the first time i saw it move after i knew the power button was broken now i can get it to move within a few minutes by flicking the back, with the cover removed, between the battery and speaker, when pressing on the volune keys.
Click to expand...
Click to collapse
Is anyone else having issues while in recovery? I am running CWM and I can't see my tablet properly. Windows tells me it can't identify the device and when I try to make it use nvidias drivet (or any driver) it tells me it's not compatible and something about it not being 64bit even though there are x64 drivers available. Works perfect everywhere else, just looking to see if anyone else has dealt with that.
Sent from my One M8
Keithn said:
Is anyone else having issues while in recovery? I am running CWM and I can't see my tablet properly. Windows tells me it can't identify the device and when I try to make it use nvidias drivet (or any driver) it tells me it's not compatible and something about it not being 64bit even though there are x64 drivers available. Works perfect everywhere else, just looking to see if anyone else has dealt with that.
Sent from my One M8
Click to expand...
Click to collapse
Figured out my issue in a way. While in CWM it doesn't appear to report to windows properly, stock recovery works fine.
Keithn said:
Figured out my issue in a way. While in CWM it doesn't appear to report to windows properly, stock recovery works fine.
Click to expand...
Click to collapse
Could you send me stock recovery so I can take a look inside the init.rc
Yeah, I'll do that today
Sent from my One M8
Keithn said:
Yeah, I'll do that today
Sent from my One M8
Click to expand...
Click to collapse
I found it inside the stock nvidia images for testing on the k1 board thanks.
This appeared to be the issue https://github.com/cm-ardbeg/androi...b4fd46180/rootdir/etc/init.recovery.ardbeg.rc
Unjustified Dev said:
I found it inside the stock nvidia images for testing on the k1 board thanks.
This appeared to be the issue https://github.com/cm-ardbeg/androi...b4fd46180/rootdir/etc/init.recovery.ardbeg.rc
Click to expand...
Click to collapse
If you want me to test anything out with it let me know. Maybe this will help pinpointing the issues for the touch driver if I can pull logs while in recovery.
Keithn said:
If you want me to test anything out with it let me know. Maybe this will help pinpointing the issues for the touch driver if I can pull logs while in recovery.
Click to expand...
Click to collapse
I compiled this one earlier let me know if it works. It doesn't have touch support but I can add it once adb is confirmed working
Unjustified Dev said:
I compiled this one earlier let me know if it works. It doesn't have touch support but I can add it once adb is confirmed working
Click to expand...
Click to collapse
Still having issues in windows it shows up as "Unknown USB Device (Configuration Descriptor Request Failed)" and gives me
Code:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB configuration descriptor failed.
for device status.
I'll give it a try in Linux but if it is not reporting properly then I don't think it will work there either.
__________________________
Nothing in Ubuntu either, even lsusb doesn't list it.
Keithn said:
Still having issues in windows it shows up as "Unknown USB Device (Configuration Descriptor Request Failed)" and gives me
Code:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB configuration descriptor failed.
for device status.
I'll give it a try in Linux but if it is not reporting properly then I don't think it will work there either.
__________________________
Nothing in Ubuntu either, even lsusb doesn't list it.
Click to expand...
Click to collapse
This is crazy does adb work in the recovery you compile from their git?
Unjustified Dev said:
This is crazy does adb work in the recovery you compile from their git?
Click to expand...
Click to collapse
I can't even get the menu to pop up. On stock it's just vol + and power and then you can see the menus and select adb sideload etc. On my compiled one it just sits at the No Command screen even after pressing those buttons, and it shows up as the same thing in my PC as CWM did.
Keithn said:
Is anyone else having issues while in recovery? I am running CWM and I can't see my tablet properly. Windows tells me it can't identify the device and when I try to make it use nvidias drivet (or any driver) it tells me it's not compatible and something about it not being 64bit even though there are x64 drivers available. Works perfect everywhere else, just looking to see if anyone else has dealt with that.
Sent from my One M8
Click to expand...
Click to collapse
I am having same issue
---------- Post added at 02:50 AM ---------- Previous post was at 02:46 AM ----------
Keithn said:
I can't even get the menu to pop up. On stock it's just vol + and power and then you can see the menus and select adb sideload etc. On my compiled one it just sits at the No Command screen even after pressing those buttons, and it shows up as the same thing in my PC as CWM did.
Click to expand...
Click to collapse
I have same issue but have a boot loop so I am bricked at the moment
---------- Post added at 02:55 AM ---------- Previous post was at 02:50 AM ----------
Okay now when I also enter recovery mode I have a blank screen can not boot into the system because of a boot loop, does anyone have any surgestions ?????????
MRobbo80 said:
I am having same issue
---------- Post added at 02:50 AM ---------- Previous post was at 02:46 AM ----------
I have same issue but have a boot loop so I am bricked at the moment
---------- Post added at 02:55 AM ---------- Previous post was at 02:50 AM ----------
Okay now when I also enter recovery mode I have a blank screen can not boot into the system because of a boot loop, does anyone have any surgestions ?????????
Click to expand...
Click to collapse
go into fastboot and flash a recovery then boot into recovery
Just tested stock recovery and the device doesn't even show as being connected until I select sideload then all I get is sideload.
Keithn said:
go into fastboot and flash a recovery then boot into recovery
Just tested stock recovery and the device doesn't even show as being connected until I select sideload then all I get is sideload.
Click to expand...
Click to collapse
My screen is black I can not see any options I am using the custom new cwm
Did you try what I said? Can you at least get into the boot loader?
Sent from my SHIELD Tablet
Keithn said:
Did you try what I said? Can you at least get into the boot loader?
Sent from my SHIELD Tablet
Click to expand...
Click to collapse
sorry not sure how to boot in to fastboot?
MRobbo80 said:
sorry not sure how to boot in to fastboot?
Click to expand...
Click to collapse
I meant to say boot into the bootloader so you can use fastboot. From Nvidia
Code:
HW method:
Turn off the device
Press "Volume Down" -> "Power", hold "Volume Down" and leave Power buttons till device boots
So basically just hold vol - then press power and keep the vol button held but not the power. Should give you a black screen with some words on it and you can select a few different things. When you are there use fastboot like you would adb. Get a cwm image and give it the command
Code:
fastboot flash recovery cwm.img
Put what ever name and location you have for your recovery image in place of cwm.img.
Keithn said:
I meant to say boot into the bootloader so you can use fastboot. From Nvidia
Code:
HW method:
Turn off the device
Press "Volume Down" -> "Power", hold "Volume Down" and leave Power buttons till device boots
So basically just hold vol - then press power and keep the vol button held but not the power. Should give you a black screen with some words on it and you can select a few different things. When you are there use fastboot like you would adb. Get a cwm image and give it the command
Code:
fastboot flash recovery cwm.img
Put what ever name and location you have for your recovery image in place of cwm.img.
Click to expand...
Click to collapse
Thanks for your fast reply here is whats happening I have been working with a dev to get acip up and running, I have cwm recovery and have fully wiped the device and installed acip which currently is bootlooping. Now my problem is when I try to enter fastboot holding down -volume key and pressing the power it just splashes to the boot logo so no luck there but when I hold down volume + and power key I can hear the sound of a usb connecting to my computer but have a black screen only. So when I check device manager under windows I can see a yellow caution mark APX unknown device so at the moment trying to find a driver that will work so that's where I am really
MRobbo80 said:
Thanks for your fast reply here is whats happening I have been working with a dev to get acip up and running, I have cwm recovery and have fully wiped the device and installed acip which currently is bootlooping. Now my problem is when I try to enter fastboot holding down -volume key and pressing the power it just splashes to the boot logo so no luck there but when I hold down volume + and power key I can hear the sound of a usb connecting to my computer but have a black screen only. So when I check device manager under windows I can see a yellow caution mark APX unknown device so at the moment trying to find a driver that will work so that's where I am really
Click to expand...
Click to collapse
Grab theses and see if they work. They are included with Nvidias tegra development tools.
Nvidia Drivers (shouldn't be much different than googles drivers but here they are.)
I don't think you are going to want it in APX anyways. I noticed it can be a pain to get the bootloader try keeping vol - held and only pressing power for a couple of seconds at most and give it a second for the screen to turn on. If you hit the splash screen then you missed the bootloader.
Keithn said:
Grab theses and see if they work. They are included with Nvidias tegra development tools.
Nvidia Drivers (shouldn't be much different than googles drivers but here they are.)
I don't think you are going to want it in APX anyways. I noticed it can be a pain to get the bootloader try keeping vol - held and only pressing power for a couple of seconds at most and give it a second for the screen to turn on. If you hit the splash screen then you missed the bootloader.
Click to expand...
Click to collapse
M8 IM IN MASSIVE THANK YOU :good::good::good::good::good::good::good::good::good::good::good::good::goodAM THAT TEXT IS SMALL HONESTLY thank you very much :good:
---------- Post added at 12:18 AM ---------- Previous post was at 12:07 AM ----------
MRobbo80 said:
M8 IM IN MASSIVE THANK YOU :good::good::good::good::good::good::good::good::good::good::good::good::goodAM THAT TEXT IS SMALL HONESTLY thank you very much :good:
Click to expand...
Click to collapse
My tablet is now fully restoring my backup in cwm as I speak have one big grin on my face at the mo.
MRobbo80 said:
M8 IM IN MASSIVE THANK YOU :good::good::good::good::good::good::good::good::good::good::good::good::goodAM THAT TEXT IS SMALL HONESTLY thank you very much :good:
---------- Post added at 12:18 AM ---------- Previous post was at 12:07 AM ----------
My tablet is now fully restoring my backup in cwm as I speak have one big grin on my face at the mo.
Click to expand...
Click to collapse
No problem good to hear :good:
When I try to boot the phone, either through the power button or bootloader, it tries to get into recovery over and over again but can never get in (to TWRP recovery). It always just gets to the TWRP splash screen but then goes black and repeats. The bootloader is unlocked. I am not sure what state the actual OS is in. ADB doesn't recognise the phone (adb devices shows nothing). Oh, and I can't get into recovery through bootloader either.
Can anyone offer any advice?
Thanks in advance
Possible power button issue? ADB commands do not work in fastboot mode. Is the phone detected in fastboot mode? Did you try re-flashing TWRP?
audit13 said:
Possible power button issue? ADB commands do not work in fastboot mode. Is the phone detected in fastboot mode? Did you try re-flashing TWRP?
Click to expand...
Click to collapse
Definately not a power button issue, it was fine before. What is fastboot mode and how would I get into it?
The power button issue can appear out of nowhere, at least it did for me. The constant reboots are also an indication.
To get into fastboot, power off the phone, hold volume up, volume down, and press power button.
I had the adb issue once .. Connect the phone to your PC then go to device manager and select your phone .. Click on update drivers and click browse your PC instead of the internet if I am correct you will see two driver options . select the USB component driver and install it .. Should work now ...
---------- Post added at 04:06 PM ---------- Previous post was at 03:30 PM ----------
Corneliusvinyo said:
I had the adb issue once .. Connect the phone to your PC then go to device manager and select your phone .. Click on update drivers and click browse your PC instead of the internet if I am correct you will see two driver options . select the USB component driver and install it .. Should work now ...
Click to expand...
Click to collapse
Disregard this . I assumed you could get it into recovery . sorry
Hi, my phone is hard bricked. I dont know why but phone is completly dead. It douesnt react on power button or vol + - and power buton etc. Only if I connect it into the PC I will get QHSUSB_BULK driver installing and after that care suite emergency connectivity is installed. Can you help me with unbricking? I have another one running OK. I have bricked by flashing I think.
The story
1. phone is telling me something about no boot / bootloader / partitions
2. I download "dload" folder with "update.app" to the SD card and start flashing - OK (B189 I think)
3. trying to testing and after that I use wipe/factory reset
4. reboot
5. unplug battery
6. plug battery in
7. next day phone is completly dead
I will apriciate any help. Thank you
I also try a others battery but there is no charging led light. Phone doesnt react on any button. Can you help me please?
Wow, this is a tough one. I'm pretty good with restoring phones and this has me baffled. I don't understand how you managed to do this. Fill me in on what you were doing at the time you bricked the device.
Sent from my SAMSUNG-SGH-I747 using XDA-Developers mobile app
---------- Post added at 10:41 AM ---------- Previous post was at 09:53 AM ----------
Hold together:*Power Button + Volume Up Button*for several seconds. And tell me if that does anything to the device (must be decently charged to work)
Sent from my SAMSUNG-SGH-I747 using XDA-Developers mobile app
TechGuyAnthony said:
Wow, this is a tough one. I'm pretty good with restoring phones and this has me baffled. I don't understand how you managed to do this. Fill me in on what you were doing at the time you bricked the device.
Sent from my SAMSUNG-SGH-I747 using XDA-Developers mobile app
---------- Post added at 10:41 AM ---------- Previous post was at 09:53 AM ----------
Hold together:*Power Button + Volume Up Button*for several seconds. And tell me if that does anything to the device (must be decently charged to work)
Sent from my SAMSUNG-SGH-I747 using XDA-Developers mobile app
Click to expand...
Click to collapse
Nothing. I pplug in into the charger 5V 2.1A for 4 hours, after that try another charger with another USB cable. But there is no notification (LED or information on LCD) about charging. Phone is completly dead. It doesnt react on any button or any combination (try to hold for 1 minute every combination). But if I plug in into the PC that I see care suite emergency connectivity
Ya. I've had a phone like this before. There was nothing I could to revive it. Start considering replacements... [emoji13]
Sent from my SAMSUNG-SGH-I747 using XDA-Developers mobile app
Thank you for your support. On the second phone which I repair by firmware upgrade is no IMEI in system. How can I recover IMEI on this phone?
bajlek said:
Thank you for your support. On the second phone which I repair by firmware upgrade is no IMEI in system. How can I recover IMEI on this phone?
Click to expand...
Click to collapse
Re-flash by dload and everything is now fine
How do you solved? My phone won't start.
msm8210 files needed
I have the same problem...
Does anyone could provide the unbrick files for Y530-U00 to use with QFIL ??
We need
MPRG8210.HEX
8210_msimage.mbn
rawprogram0.xml
patch0.xml
Click to expand...
Click to collapse
Thank you!
Did u find a solution?
---------- Post added at 05:55 PM ---------- Previous post was at 05:54 PM ----------
I need some files if someone wants to extract that files for me
bajlek said:
It doesnt react on any button or any combination
Click to expand...
Click to collapse
So that means, that the preloader is bricked. Because if it would react on any button (Volume Up, Volume Down, Power), then it would normally react. For those buttons are being handled by the preloader partition file. If you either flashed the preloader from a wrong ROM (Like I did one time on Wiko Lenny 3), then no button will react. Those buttons are being handled by their ID's (I think, not sure). Preloader handles the Button ID if it is pressed. If yes, preloader will detect the clicked button and handle the action (for example: Clicking the power button when Display is off → Makes the Display to go on).
If the preloader is bricked, then either you need a new phone or reflash the preloader.
Huawei Y530 Bricked too
So heres what happened:
Phone didnt boot and showed a recovery, boot image verify failed.
-i copied original firmware for this model (i used right one) to sdcard and updated from it.
When the update was finishing the phone was stuck.
-I tryed to turn on the phone but i cant.
Plugged it into PC, reflashed but still its dead.
Anyone, help please
I (stupidly) decided to repartition my Moto G3 using this guide. Now, when trying to turn my phone on, the screen stays blank and there's no indication that it's working but it reboots once every two to five seconds or so (telling you how I can tell it's rebooting would be a long story and I'm sure it's irrelevant to the issue).
Am I just hooped or is there hope?
Can you boot in to bootloader?
If yes just flash stock firmware (should include partition layout)
HelpMeruth said:
Can you boot in to bootloader?
If yes just flash stock firmware (should include partition layout)
Click to expand...
Click to collapse
Nope, all attempts to get into the bootloader fail. The screen just stays blank with no indication that it's doing anything at all (although behind the scenes it's actually rebooting once every few seconds). My (uneducated) guess is it can't even access any of the partitions.
sensi277 said:
Nope, all attempts to get into the bootloader fail. The screen just stays blank with no indication that it's doing anything at all (although behind the scenes it's actually rebooting once every few seconds). My (uneducated) guess is it can't even access any of the partitions.
Click to expand...
Click to collapse
Try to connect it to your pc and see if adb/fastboot sees the device.
michkost858 said:
Try to connect it to your pc and see if adb/fastboot sees the device.
Click to expand...
Click to collapse
adb shell doesn't see anything.
sensi277 said:
adb shell doesn't see anything.
Click to expand...
Click to collapse
Hey, since according to what you say your device is currently stuck in a boot-loop, I suggest you first take out the battery out for a few seconds and then put it back then enter recovery mode using the device buttons right after. only then connect your device to PC and use adb...
Jewshua said:
Hey, since according to what you say your device is currently stuck in a boot-loop, I suggest you first take out the battery out for a few seconds and then put it back then enter recovery mode using the device buttons right after. only then connect your device to PC and use adb...
Click to expand...
Click to collapse
Or, since the battery is not officially removable, wait till the battery dies and then try to boot into bootloader.
Volume down broken
Hi! My mom's phone started to heavily slow down with its stock firmware so I tried to install a custom firmware since I installed one on mine and we both have Moto G3s.
Thing is, it bricked and the volume down button is dead since a few month so I don't have access to the bootloader, otherwise I would just flash the stock firmware. Only buttons working are volume up and on/off buttons.
Is there any way to access the bootloader with this button or am I screwed on this one ?
tyty48 said:
Hi! My mom's phone started to heavily slow down with its stock firmware so I tried to install a custom firmware since I installed one on mine and we both have Moto G3s.
Thing is, it bricked and the volume down button is dead since a few month so I don't have access to the bootloader, otherwise I would just flash the stock firmware. Only buttons working are volume up and on/off buttons.
Is there any way to access the bootloader with this button or am I screwed on this one ?
Click to expand...
Click to collapse
Can you boot the ROM?
If so, you should be able to turn on usb debugging and run 'adb reboot recovery' and reflash from there
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
sensi277 said:
adb shell doesn't see anything.
Click to expand...
Click to collapse
what about fastboot devices (with admin/root privileges) ?