Restoring 1 A0001 from two bad ones... - ONE Q&A, Help & Troubleshooting

Hi Fellow forum members!
I am trying to restore my doughters phone ( sat on it, bend the phone, and cracked glass+lcd ).
I, by odd luck, was sent a bricked A0001 for parts like ten days before that.
The bricked phone is in a very good shape.
It just did not respond to anything.
I tried to mount my doughters motherboard into the bricked phone, thinking that would unbrick it.
But not so....
It does wake up now, but only in Cyanogen Recovery mode.
I could rip out all and just go for the lcd but that is a repair that never has a good outcome, as you really are taking glued in parts out that never will fit back in a 100%
now ...
is that my only option?
i could try to reinstall thru cyanogen recovery ( thats the mode it is in right now )
adb sideload is something i have no experience with...
or is it simpeler to unbrick the bricked one?
All help is appreciated!
Marc.

Try the bacon root toolkit first, it will simplify sideloading a new rom, most important is that you have a recovery working.

amd-dude said:
Try the bacon root toolkit first, it will simplify sideloading a new rom, most important is that you have a recovery working.
Click to expand...
Click to collapse
Hi amd-dude!
tx for the intel.
i do not have a working recovery from neither the bent nor the bricked one.
i also own a oneplus one. ( if necessary i can retrieve one from there )
i will try try bacon root toolkit first.
your next virtual beer is on me!
// i find it odd that switching the motherboard puts the "combo- phone" in recovery mode...
// isn't the motherboard compatible?

amd-dude said:
Try the bacon root toolkit first, it will simplify sideloading a new rom, most important is that you have a recovery working.
Click to expand...
Click to collapse
i tried the bacon root toolkit.
stuck at no bootloader...

LabRatNo9 said:
i tried the bacon root toolkit.
stuck at no bootloader...
Click to expand...
Click to collapse
Just replace LCD display from bricked one.Use YouTube for DIY.

Mr.Ak said:
Just replace LCD display from bricked one.Use YouTube for DIY.
Click to expand...
Click to collapse
tx Ak!
gonna give it another hour to try to restore it
clean driver install
and hopefully the fastboot will be working
if not
then the screen replace is next ( yes i know youtube )
don't think it will make a difference as i wiped the working motherboard ...
tx again

LabRatNo9 said:
tx Ak!
gonna give it another hour to try to restore it
clean driver install
and hopefully the fastboot will be working
tx again
Click to expand...
Click to collapse
What's the issue with fastboot mode?

Mr.Ak said:
What's the issue with fastboot mode?
Click to expand...
Click to collapse
I can't see the correct google driver when i want to setup driver software for A0001.
even-thou i installed the google drivers and am showed the thumbs up for a good install.
i do get a 'google galaxy nexus ADB interface' option for driver
but when i use that, it wont get into fastboot.
the phone is completely empty btw....

LabRatNo9 said:
I can't see the correct google driver when i want to setup driver software for A0001.
even-thou i installed the google drivers and am showed the thumbs up for a good install.
i do get a 'google galaxy nexus ADB interface' option for driver
but when i use that, it wont get into fastboot.
the phone is completely empty btw....
Click to expand...
Click to collapse
Uh,no.To boot into fastboot press volup+power button.No need of drivers and stuff.

well actually you dont need to worry about glued in parts..
i had a broken screen too , and i found a screen with frame / bezel on ebay..
very easy to replace no glue , just click click click.
Just be carefull when you open the backplate.. especially in the sides as there are "ribbons" for the power button and volume button, those are easily destroyed with the tools you use ..
good luck

Related

help with toolkit

hey guys i got my nexus 5 yesterday and i wanted to root it . so i downloaded toolkit and installed everything . but whe i tried to unlock the phone it said it couldnt find the adb . so i followed the guid and i did everything by the book and in device manager it recognized it as a samsung android phone > google nexus adb interface . so i retried the unlock a few times and i got nothing again .
if anyone can help me it would be great .
if you need more info just ask
I've had good luck with the android nacked usb drivers, Google them. Then follow this guide http://forum.xda-developers.com/showthread.php?p=47025283
jd1639 said:
I've had good luck with the android nacked usb drivers, Google them. Then follow this guide http://forum.xda-developers.com/showthread.php?p=47025283
Click to expand...
Click to collapse
how do i install them ?
danielbr14 said:
how do i install them ?
Click to expand...
Click to collapse
In Windows device manger you probably have a usb port when an "!" On it. Right click it then manual install the usb drivers. You'll have to browes to whet you downloaded the drivers
jd1639 said:
In Windows device manger you probably have a usb port when an "!" On it. Right click it then manual install the usb drivers. You'll have to browes to whet you downloaded the drivers
Click to expand...
Click to collapse
it said that the drivers are already installed so what should i do now ?
danielbr14 said:
it said that the drivers are already installed so what should i do now ?
Click to expand...
Click to collapse
Google "nexus 5 diagnosing usb drivers xda"
why use a toolkit on a nexus device? its easier to root your nexus without a toolkit.
1. "fastboot oem unlock" via fastboot unlocks the bootloader.
2. flash a custom recovery via fastboot
3. flash the su binaries(supersu) in your new recovery.
4. reboot and profit, thats it.
danielbr14 said:
hey guys i got my nexus 5 yesterday and i wanted to root it . so i downloaded toolkit and installed everything . but whe i tried to unlock the phone it said it couldnt find the adb . so i followed the guid and i did everything by the book and in device manager it recognized it as a samsung android phone > google nexus adb interface . so i retried the unlock a few times and i got nothing again .
if anyone can help me it would be great .
if you need more info just ask
Click to expand...
Click to collapse
I used this...http://www.youtube.com/watch?v=KnlUdjUaD3Q
and this....http://www.wugfresh.com/nrt/
with zero issues
P.s.
I was a first time noob.
simms22 said:
why use a toolkit on a nexus device? its easier to root your nexus without a toolkit.
1. "fastboot oem unlock" via fastboot unlocks the bootloader.
2. flash a custom recovery via fastboot
3. flash the su binaries(supersu) in your new recovery.
4. reboot and profit, thats it.
Click to expand...
Click to collapse
might want to add after you unlock the bootloader to boot into the device once.
jd1639 said:
Google "nexus 5 diagnosing usb drivers xda"
Click to expand...
Click to collapse
i still can find a good answer on how to solve my problem.
danielbr14 said:
i still can find a good answer on how to solve my problem.
Click to expand...
Click to collapse
Do you have usb debugging enabled in developer options on your phone?
jd1639 said:
Do you have usb debugging enabled in developer options on your phone?
Click to expand...
Click to collapse
yes i do .
Zepius said:
might want to add after you unlock the bootloader to boot into the device once.
Click to expand...
Click to collapse
why? i didnt. my nexus 5 never ever booted up stock. before i ever booted it, it got unlocked and flashed first.
simms22 said:
why? i didnt. my nexus 5 never ever booted up stock. before i ever booted it, it got unlocked and flashed first.
Click to expand...
Click to collapse
what does it have to do with anything ??
danielbr14 said:
what does it have to do with anything ??
Click to expand...
Click to collapse
You're probably going to have to go into device manager, view hidden, and delete each usb port that is not being used and start over. Don't have your phone connected when you do this. It's a pita. Then reboot your computer, than plug your phone in. Also make sure you're using the usb cable that came with your phone and usb ports in the back of your pc
simms22 said:
why? i didnt. my nexus 5 never ever booted up stock. before i ever booted it, it got unlocked and flashed first.
Click to expand...
Click to collapse
some people have reported issues if you didnt let the device 'reset' itself after you unlocked the bootloader so it could rebuild the data partition.
its more of a precautionary thing than anything else.
jd1639 said:
You're probably going to have to go into device manager, view hidden, and delete each usb port that is not being used and start over. Don't have your phone connected when you do this. It's a pita. Then reboot your computer, than plug your phone in. Also make sure you're using the usb cable that came with your phone and usb ports in the back of your pc
Click to expand...
Click to collapse
you mean uninstall everything in the universal serial bu controller tree ?
danielbr14 said:
you mean uninstall everything in the universal serial bu controller tree ?
Click to expand...
Click to collapse
Yep, that's not currently being used. You don't want to lose your keyboard, etc.
jd1639 said:
Yep, that's not currently being used. You don't want to lose your keyboard, etc.
Click to expand...
Click to collapse
i dont know how to find wich one is in use and wich one isnt.
danielbr14 said:
i dont know how to find wich one is in use and wich one isnt.
Click to expand...
Click to collapse
The ones that are grayed out are not in use the darker ones are

[Q] Nexus 5 does is dead???

I installed latest CM rom and unfortunately xposed framework on top.
after that my device does not start and seems to stack in CM logo for ever.
I can get to recovery but does not find any backup files! Seems like scdard is empty or not recognizable.
I tried to push a new rom for with adb from fastboot but my pc does not seems to find the phone. Like adb debugging is not enabled on the phone.
I also fails when I try to erase the device from recovery.
Any help is welcome.
Boot in fastboot and flash a factory image. Best way to fix pretty much anything.
mortenmhp said:
Boot in fastboot and flash a factory image. Best way to fix pretty much anything.
Click to expand...
Click to collapse
does for find the device any more, so i cannot flash anything
Try to reinstall the universal drivers, and try different usb ports on your computer.
sprkrt said:
does for find the device any more, so i cannot flash anything
Click to expand...
Click to collapse
You need to make sure you're in the bootloader.
sprkrt said:
does for find the device any more, so i cannot flash anything
Click to expand...
Click to collapse
Hi, your phone is ok, just empty. the problem is on the computer. You need to fix the driver for nexus 5. You probably have them installed since you unlocked the phone. just keep your phone connected and on recovery mode.
go to device manager, look for nexus 5. Choose "update driver"
"Browse my computer for driver...,
"let me pick from a list of device drivers"
choose any ADB driver, and install it.
Many more ways to do it
sprkrt said:
does for find the device any more, so i cannot flash anything
Click to expand...
Click to collapse
If it can boot to the bootloader, and it still cant find the device, the problem is either with your computer(driver) or with the usb hardware on the phone(highly unlikely since it happened after you messed with software)
mortenmhp said:
If it can boot to the bootloader, and it still cant find the device, the problem is either with your computer(driver) or with the usb hardware on the phone(highly unlikely since it happened after you messed with software)
Click to expand...
Click to collapse
problem solved.
i tried the exact same process on my imac and worked perfectly!
( i had already reinstalled the drivers on my pc with no luck...)
sprkrt said:
problem solved.
i tried the exact same process on my imac and worked perfectly!
( i had already reinstalled the drivers on my pc with no luck...)
Click to expand...
Click to collapse
He he this deserves a headline
Apple recovered my nexus from death lmao
Glad that you worked it out.
Sent from my Nexus 5 using Tapatalk

[Q] Hard Bricked or not ??????

Until yesterday,my nexus 5 16GB (Imported from Canada to India) runs fine, but it give some error after rebooting a device. "UID's inconsistent Error (I'm feeling Lucky)" .
I searched on XDA Forum and find a solution that it needs to fix permission through TWRP recovery.
The error had gone but my internal SD storage shows empty in any file manager but works fine on PC (it shows all files and folders on PC).
I got this storage problem second time in last two months and it happens when i do some task through TWRP like cleaning cache,Dalvik cache etc.
Last time i fixed it by simply re-installing the firmware.
But this time i read somewhere to use a command "dd if=/dev/zero of=/dev/block/mmcblk0" in Terminal emulator app.
So i go for this solution.But after this when i reboot my device,it never turns ON.
No combination of button works to get in recovery or bootloader.
It is detected as " Qualcomm hs-usb qdloader 9008" port in device manager.
and if i press and hold volume up then connect it via usb to pc ,it shows unknown device.
other than this, nothing works and no screen activity.
i had already tried LG flash Tool,but it says device is in unknown mode.
Please tell me if my device is Hard Bricked or not?
If Yes ,how much it will cost to get repaired here in INDIA?
Device Details:
Nexus 5 16GB Android L LPV81C (rooted with custom TWRP recovery)
Bootloader Unlocked.
Looks like you nuked your eMMC...
Where did you find that command?
Bhupideol said:
Until yesterday,my nexus 5 16GB (Imported from Canada to India) runs fine, but it give some error after rebooting a device. "UID's inconsistent Error (I'm feeling Lucky)" .
I searched on XDA Forum and find a solution that it needs to fix permission through TWRP recovery.
The error had gone but my internal SD storage shows empty in any file manager but works fine on PC (it shows all files and folders on PC).
I got this storage problem second time in last two months and it happens when i do some task through TWRP like cleaning cache,Dalvik cache etc.
Last time i fixed it by simply re-installing the firmware.
But this time i read somewhere to use a command "dd if=/dev/zero of=/dev/block/mmcblk0" in Terminal emulator app.
So i go for this solution.But after this when i reboot my device,it never turns ON.
No combination of button works to get in recovery or bootloader.
It is detected as " Qualcomm hs-usb qdloader 9008" port in device manager.
and if i press and hold volume up then connect it via usb to pc ,it shows unknown device.
other than this, nothing works and no screen activity.
i had already tried LG flash Tool,but it says device is in unknown mode.
Please tell me if my device is Hard Bricked or not?
If Yes ,how much it will cost to get repaired here in INDIA?
Device Details:
Nexus 5 16GB Android L LPV81C (rooted with custom TWRP recovery)
Bootloader Unlocked.
Click to expand...
Click to collapse
Try this: download android driver,change usb port ad use nexus root tolkit http://forum.xda-developers.com/goo...olkit-wugs-nexus-root-toolkit-v1-8-3-t2517778 . The software has a system to try to recover bricked nexus. Sorry for my incomprensible english, i'm italian
All Bricks are hard.
If you cant fix with LG flashtool, yes it's bricked
Hi,
Try this [bootloader] [unbrick] Second Bootloader on Nexus 5
With those instructions I was able to recover my nexus 5.
ZammyHedgeFox said:
Looks like you nuked your eMMC...
Where did you find that command?
Click to expand...
Click to collapse
Somewhere a post on androidforums.com
manolito1998 said:
Hi,
Try this [bootloader] [unbrick] Second Bootloader on Nexus 5
With those instructions I was able to recover my nexus 5.
Click to expand...
Click to collapse
He destroyed mmcblk0 which is the entire eMMC partition...
So, no second bootloader.
manolito1998 said:
Hi,
Try this [bootloader] [unbrick] Second Bootloader on Nexus 5
With those instructions I was able to recover my nexus 5.
Click to expand...
Click to collapse
I had tried this but no luck....
Bhupideol said:
I had tried this but no luck....
Click to expand...
Click to collapse
Man, if your phone enter in fastboot mode, download theka first firmware from google site, maybe 4.4, and install it via fastboot, i didn't read all the thread but it save me when something similar happens to me, but if your phone didn't enter in fastboot, soo I think it's hard bricked
eng.Colombo said:
Man, if your phone enter in fastboot mode, download theka first firmware from google site, maybe 4.4, and install it via fastboot, i didn't read all the thread but it save me when something similar happens to me, but if your phone didn't enter in fastboot, soo I think it's hard bricked
Click to expand...
Click to collapse
Ok Thanks!
as none of the method works, I assumed phone is hard bricked.
Should i go for a warranty claim in Canada (i can manage to send it to canada through relative to my brother (who live in canada) for this purpose)????
Or just give here in India to LG service center for repair or motherboard replacement ????
Anyone knows how much motherboard replacement will cost ???
Bhupideol said:
But this time i read somewhere to use a command "dd if=/dev/zero of=/dev/block/mmcblk0" in Terminal emulator app.
So i go for this solution.But after this when i reboot my device,it never turns ON.
Click to expand...
Click to collapse
This here alarms me... You read "Somewhere? where exactly? you obviously didn't know what it was or what it could have done, so why do it?
Yeah, seems it's hard bricked, but you've been taught a lesson here.. make sure you know what you're doing... and don't just "read" something and try it..
If in doubt, read, then read again, then read some more.. if you are stuck. Ask.
radicalisto said:
This here alarms me... You read "Somewhere? where exactly? you obviously didn't know what it was or what it could have done, so why do it?
Yeah, seems it's hard bricked, but you've been taught a lesson here.. make sure you know what you're doing... and don't just "read" something and try it..
If in doubt, read, then read again, then read some more.. if you are stuck. Ask.
Click to expand...
Click to collapse
Yep because what he has done here is overwrite the entire partition layout.
Bhupideol said:
Ok Thanks!
as none of the method works, I assumed phone is hard bricked.
Should i go for a warranty claim in Canada (i can manage to send it to canada through relative to my brother (who live in canada) for this purpose)????
Or just give here in India to LG service center for repair or motherboard replacement ????
Anyone knows how much motherboard replacement will cost ???
Click to expand...
Click to collapse
LG in indai will not do anything because the D820 variant sold in canada and the D821 variant sold in india. It does not matter if you have LG warranty or not. Maybe they will offer you to replace the D820 board with a D821 board, but you have to pay the costs of the repair and motherboard change. The price can go above 100 USD.
If you facing this "UID's inconsistent Error (I'm feeling Lucky)" problem in the future then you have to make a factory reset. You get this error if you dirty flash roms
Bhupideol said:
But this time i read somewhere to use a command "dd if=/dev/zero of=/dev/block/mmcblk0" in Terminal emulator app.
Click to expand...
Click to collapse
somewhere... sounds fishy
Actually when I saw this I was reminded of how I used to tell folks on MMO's that I played that pressing ALT+F4 was how you pick up rare items when they drop and that you had to press it repeatedly so no one else got it...
Dude i had the same problem and fixed it with TWRP ( Fix Permissions ). Sorry for your phone btw. Looks like a nuked emmc as others said...
If it turn on I recommend you try nexus toolkit
I use that for my N7
MasterX007 said:
If it turn on I recommend you try nexus toolkit
I use that for my N7
Click to expand...
Click to collapse
Dude, it doesnt turn on. It's hard bricked. You do the dd command he did and I guarantee it'll hard brick it every time.
Sent from my Nexus 5 using XDA Free mobile app
Ok
Ok,
I got all of this.
Thanks for your replies.
Learned a lesson from my stupidity.
Now,I am sending it back to Canada.
It's kinda said that you can wipe the most important partition of the device without it warning you about the possible outcome.
Tapatalk-kal küldve az én Nexus 5-el

[Q] Real HELP NEEDED..Everythings dead

Guys I REALLY NEED your HELP.
Here's What I did..
1. Installed CWM on my NOKIA X
2.Got into Recovery mode(It's Cool actually)
3.Thought of installing minirom kitkat on it..(I had already copied it to my removable sd card.)
4.Went through all the menus,,, did nothing,,, and somewhere I saw advanced,, got into it (I didn't know what I was thinking) I cleared every option that it had including cache, memory,sd card, emmc and also some boot related stuff..
5.All of a sudden I couldn't move the options so I just removed the battery and tried to power it on....(**** Happens)-Phone is not powering on.... no boot no light just A DEAD PHONE.
plz gus I Really NEED HELP. How Can I Solve this Problem.........................................................................................Plz plz plz plz.......:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
I think this is hard brick.(very hard to fix) are you able to open factory mod now? if no then wait for developers to help you to fix hard brick. or if your device showing on pc then you can flash stock rom...
•axe• said:
I think this is hard brick.(very hard to fix) are you able to open factory mod now? if no then wait for developers to help you to fix hard brick. or if your device showing on pc then you can flash stock rom...
Click to expand...
Click to collapse
no my phone's not powering up and i'm not able to open factory mode....... Plz help
Aztile said:
no my phone's not powering up and i'm not able to open factory mode....... Plz help
Click to expand...
Click to collapse
download and open ADB driver installer
is your device showing here? or download and open adb shell and type adb devices
is your device listed here?
if yes then download stock rom for nokia x
and flash is with any flash tool (like odin)
(make sure you have installed your phone to the same pc before means you have drivers)
if your device not showing then contact nokia care (dont tell them your story otherwise your warrenty will over tell them only that your mobile is not turning on )
•axe• said:
download and open ADB driver installer
is your device showing here? or download and open adb shell and type adb devices
is your device listed here?
if yes then download stock rom for nokia x
and flash is with any flash tool (like odin)
(make sure you have installed your phone to the same pc before means you have drivers)
if your device not showing then contact nokia care (dont tell them your story otherwise your warrenty will over tell them only that your mobile is not turning on )
Click to expand...
Click to collapse
Sorry buddy...... Tried it... but no use
All we can do is to refer you to a service center. Sorry.
Moderators, please verify my account. I am sick of the five-minute post wait.
Sent from my XT1022 using the XDA Premium 4 app.
Try this..power the phone off, wait 5 mins, then press and hold power for 60 seconds, and check if you see any signs of the phone coming back to life. If not, then the next option is the service center
that too is not working.................Is there no one inthis whole XDA Universe who can help me..... come on guys there must be someone................:crying::crying::crying:
tech_master said:
Moderators, please verify my account. I am sick of the five-minute post wait.
Click to expand...
Click to collapse
The five-minute post limit is lifted once you have reached 10 posts. The moderators have nothing to do with it, as the process is automated to lift the wait after you post 10 times.
The reason for this wait is to keep new users from rapidly posting uselessly just to achieve 10 posts.
Dude This is crazy
thenookieforlife3 said:
The five-minute post limit is lifted once you have reached 10 posts. The moderators have nothing to do with it, as the process is automated to lift the wait after you post 10 times.
The reason for this wait is to keep new users from rapidly posting uselessly just to achieve 10 posts.
May I have a post thank for helping?
Click to expand...
Click to collapse
Dude this is really crazy....... I thought it was someone trying to help me there and now this............................................ AAAhhhhhhh:crying::crying::crying:
Aztile said:
Dude this is really crazy....... I thought it was someone trying to help me there and now this............................................ AAAhhhhhhh:crying::crying::crying:
Click to expand...
Click to collapse
Oops, sorry to get your hopes up.
I do actually have a few things to say about the real problem here:
1. Are you sure that your device is charged up? If not, make sure to plug it in to charge.
2. If charging isn't the problem, I'm going to give it a safe bet that your device is bricked. Like, turned into nothing more than a brick. (That's what "bricked" actually means ) If the device doesn't respond to the power button (which your posts have led me to believe), then there is no way to revive your device.
aah come on
thenookieforlife3 said:
Oops, sorry to get your hopes up.
I do actually have a few things to say about the real problem here:
1. Are you sure that your device is charged up? If not, make sure to plug it in to charge.
2. If charging isn't the problem, I'm going to give it a safe bet that your device is bricked. Like, turned into nothing more than a brick. (That's what "bricked" actually means ) If the device doesn't respond to the power button (which your posts have led me to believe), then there is no way to revive your device.
Post thank for the real answer?
Click to expand...
Click to collapse
Jesus!!!! Did you just say "NO WAY" come on buddy don't do this to me..................................................... It's like i'm half dead...... there must be some way to unbrick it.........................Come on PLZ plz plz:crying::crying::crying::crying::crying::crying::crying:
aah come on
thenookieforlife3 said:
Oops, sorry to get your hopes up.
I do actually have a few things to say about the real problem here:
1. Are you sure that your device is charged up? If not, make sure to plug it in to charge.
2. If charging isn't the problem, I'm going to give it a safe bet that your device is bricked. Like, turned into nothing more than a brick. (That's what "bricked" actually means ) If the device doesn't respond to the power button (which your posts have led me to believe), then there is no way to revive your device.
Post thank for the real answer?
Click to expand...
Click to collapse
Jesus!!!! Did you just say "NO WAY" come on buddy don't do this to me..................................................... It's like i'm half dead...... there must be some way to unbrick it.........................Come on PLZ plz plz:crying::crying::crying::crying::crying::crying::crying:
Aztile said:
Jesus!!!! Did you just say "NO WAY" come on buddy don't do this to me..................................................... It's like i'm half dead...... there must be some way to unbrick it.........................Come on PLZ plz plz:crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
You said you've cleared eMMC and also some boot related stuff.
Well, messing with your eMMC and boot partition isn't a good idea, if you wiped your entire eMMC partition it means you've also wiped bootloader stuff...
I'm sorry but looks like your phone is totally bricked....
First of all stop shouting...!
Are you sure you choose "advaneced menu" and not "mount and storage" ....?
Also me too I think your device is bricked...
If you can't recognise it from fastboot and adb and you can boot to bootloader and recovery mode it is bricked...
root-expert said:
First of all stop shouting...!
Are you sure you choose "advaneced menu" and not "mount and storage" ....?
Also me too I think your device is bricked...
If you can't recognise it from fastboot and adb and you can boot to bootloader and recovery mode it is bricked...
Click to expand...
Click to collapse
Ooops Sorry.....
Ok I understood..... IT'S BRICKED..........
Well then how to unbrick it
Aztile said:
Ooops Sorry.....
Ok I understood..... IT'S BRICKED..........
Well then how to unbrick it
Click to expand...
Click to collapse
If your phone won't turn on at all, it's totally bricked. Only a motherboard replacement will fix it...
As you know your phone has hard bricked buddy
then you should also know you cant fix it
try odin and flash bootloader (if u can without open download mode)
or Nokia care is the best way...

Moto G only booting into fastboot mode (system and recovery not working)

Hello,
I bought a used Moto G osprey, european version with 2GB of RAM.
It only boots into fastboot mode, normal boot or boot into recovery don't work. When I try to start the phone normally, it gets stuck at the "M" logo, restarts after a few seconds and does the same again. It's bootlooping.
What I already tried:
- Going back to stock according to https://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750 throws a 'Preflash validation' error, probably because the installed system is a newer Android version
- Flashing TWRP 3.3.1-0 via fastboot works, but I can't seem to get into it after installation. When I try to get into recovery mode through the fastboot menu, I come back into the same bootloop.
Any help on what could be going wrong?
Can you see the phone using ADB Fastboost on a PC?
R1ffR4ff said:
Can you see the phone using ADB Fastboost on a PC?
Click to expand...
Click to collapse
No. It's really strange.
I have some experience with flashing, did some on a Galaxy S, S2, S5 and HTC One M7, but never encountered such an error.
Could it be an hardware failure? If so, how could I confirm this?
snowmotion said:
No. It's really strange.
I have some experience with flashing, did some on a Galaxy S, S2, S5 and HTC One M7, but never encountered such an error.
Could it be an hardware failure? If so, how could I confirm this?
Click to expand...
Click to collapse
I think only a Moto Service center could help but have you tried these Motorola USB drivers just in case?
https://support.motorola.com/us/en/drivers
R1ffR4ff said:
I think only a Moto Service center could help but have you tried these Motorola USB drivers just in case?
https://support.motorola.com/us/en/drivers
Click to expand...
Click to collapse
Well, I'm using Linux, so not using any drivers at all.
How do the Moto Service centers work if I do not have a guarantee?
snowmotion said:
Well, I'm using Linux, so not using any drivers at all.
How do the Moto Service centers work if I do not have a guarantee?
Click to expand...
Click to collapse
I don't know how they work just that they are there. Alternate idea.Phone around for a local small phone repair shop.They should be able to help and or borrow a Window's Laptop?
R1ffR4ff said:
I don't know how they work just that they are there. Alternate idea.Phone around for a local small phone repair shop.They should be able to help and or borrow a Window's Laptop?
Click to expand...
Click to collapse
Thanks for your tip, going to try that out and report back.
snowmotion said:
Thanks for your tip, going to try that out and report back.
Click to expand...
Click to collapse
I wrote a guide in a reply on how to recover from this in an XDA forum post located HERE.

Categories

Resources