[BOOTLOOP]Nexus 5 problem with persist partition - Nexus 5 Q&A, Help & Troubleshooting

Hi, i have a big problem for 4 months with my nexus 5:
A day, it starts bootloop and I take it at the LG center, one month afther they tell me that they can't repair the phone because i have rooted it. They said that i must pay a lot of money because i have to replace the motherboard.
I didn't pay anything and i got the device with a new problem: It is in bootloop, but i can access to the recovery but these are the problems:
1) the twrp recovovery says "Unable to mount /persist" and "unable to open "/cache/recovery/.version
2) I can't wipe and flash anything aside "boot.img" and "recovery.img"
3)I tried to use this command in the prompt:
e2fsck /dev/block/platform/msm_sdcc.1/byname/persist but it says "recovering journal superblock needs_recovery is clear but journal has data, run journal anyway?" i enter "y" and it says "unable to set superblock flags".
I have made many sacrifices to buy the phone and i can't get a new one, how can I solve this problem? (now it still in bootloop)
Sorry for my bad english

There's a whole guide to repair /persist in the general forum. Look in "sticky roll-up" thread.

rootSU said:
There's a whole guide to repair /persist in the general forum. Look in "sticky roll-up" thread.
Click to expand...
Click to collapse
Thank you for your answer
i followed the guide, but when i enter "make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist" to format the partition, the problem still persist...
:crying:

Hello
I had a similar problem a I did managed to make it work using this helpful post
http://forum.xda-developers.com/goo...l-06-03-14-one-click-factory-restore-t2513937
After that you can root again, and start to play.

Muaitai said:
Hello
I had a similar problem a I did managed to make it work using this helpful post
http://forum.xda-developers.com/goo...l-06-03-14-one-click-factory-restore-t2513937
After that you can root again, and start to play.
Click to expand...
Click to collapse
i haven't try it yet, but i have the writing error when i flash the stock image with wug fresh toolkit, are you sure that this can solve the problem?
EDT---
I have tried it but there is the same problem (write failure). Any solutions?

Can everyone help me?

#$wag said:
Can everyone help me?
Click to expand...
Click to collapse
try http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
this touches on partitions that normal factory images dont.

opssemnik said:
try http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
this touches on partitions that normal factory images dont.
Click to expand...
Click to collapse
Thanks for answer, but when I use this tool, there is an error with sending userdata and there is no change...

#$wag said:
Thanks for answer, but when I use this tool, there is an error with sending userdata and there is no change...
Click to expand...
Click to collapse
i bet your emmc is bad

opssemnik said:
i bet your emmc is bad
Click to expand...
Click to collapse
:crying:
Can I replace the emmc?

#$wag said:
:crying:
Can I replace the emmc?
Click to expand...
Click to collapse
by your own no. if you have warranty, lg covers that (or google depending on where you live/bought the device).
basicly you need to replace the whole motherboard

opssemnik said:
by your own no. if you have warranty, lg covers that (or google depending on where you live/bought the device).
basicly you need to replace the whole motherboard
Click to expand...
Click to collapse
I have already sent my phone to lg but they said that it is rooted and they can't help me.
how much does a new motherboard costs?

#$wag said:
I have already sent my phone to lg but they said that it is rooted and they can't help me.
how much does a new motherboard costs?
Click to expand...
Click to collapse
tbh no idea, but probably $150-$200

opssemnik said:
tbh no idea, but probably $150-$200
Click to expand...
Click to collapse
Sorry but I don't think that the emmc is bad, i've tried to make a directory with adb and it create the directory, so I think that i must to reset the partition (whith TWRP)... But i don't know the commands...

#$wag said:
Sorry but I don't think that the emmc is bad, i've tried to make a directory with adb and it create the directory, so I think that i must to reset the partition (whith TWRP)... But i don't know the commands...
Click to expand...
Click to collapse
just like hdds and ssds, flash memories can also get corrupted/ bad sectors, these are hardware defects only at certain part of the memory.
the command you are looking for is already done by lg flash tool, but it failed to do because your emmc is bad.
anyway if you want to
mkfs.ext4 /dev/block/platform/msm_sdcc.1/by-name/persist /persist
if gives command not found then try
mkfs_ext4 instead
if you willing to try something, pm me

Related

[Q] NEXUS 5 BRICKED TRYING TO ROOT WITH CF AutoRoot. HELP!?

Hi all
A bit new to posting in here but am really hoping to receive some help from you all. Last night I installed all the standard USB drivers i.e. Android SDK pack and followed them all as mentioned. Then using the root tool from ChainFire I got to the little android guy after going through the process of unlocking the bootloader and gaining root, but the phone never actually rebooted.
Now when I try to flash the original fastboot files using the WUG kit I get "FAILED: remote: flash write failure" The same is the case with writing the boot img and recovery img. See attached.
I can put the phone into Fastboot mode only and it says lock state is "unlocked" but it would seem that I can no longer write anything to the internal disk as nothing will work or boot. I also get a status on my PC saying that the driver QHSUSB_Bulk could not be found.
Has anybody had a similar problem to this? Is there any way to somehow get this working again? And if I RMA with Google will they say my warranty is voided now that it says the lock state in Fastboot is unlocked?
Many thanks in advance guys any help is appreciated.
Meakii said:
Hi all
A bit new to posting in here but am really hoping to receive some help from you all. Last night I installed all the standard USB drivers i.e. Android SDK pack and followed them all as mentioned. Then using the root tool from ChainFire I got to the little android guy after going through the process of unlocking the bootloader and gaining root, but the phone never actually rebooted.
Now when I try to flash the original fastboot files using the WUG kit I get "FAILED: remote: flash write failure" The same is the case with writing the boot img and recovery img. See attached.
I can put the phone into Fastboot mode only and it says lock state is "unlocked" but it would seem that I can no longer write anything to the internal disk as nothing will work or boot. I also get a status on my PC saying that the driver QHSUSB_Bulk could not be found.
Has anybody had a similar problem to this? Is there any way to somehow get this working again? And if I RMA with Google will they say my warranty is voided now that it says the lock state in Fastboot is unlocked?
Many thanks in advance guys any help is appreciated.
Click to expand...
Click to collapse
Try flashing the factory images manually.
http://forum.xda-developers.com/showthread.php?t=2513701
Method 2.
Does fastboot work properly? What output does 'Fastboot devices" have?
abaaaabbbb63 said:
Try flashing the factory images manually.
http://forum.xda-developers.com/showthread.php?t=2513701
Method 2.
Does fastboot work properly? What output does 'Fastboot devices" have?
Click to expand...
Click to collapse
Thanks have tried flashing them manually but still the same error saying FAILED: remote: flash write failure
It as if nothing can be written to the phone at all.
Yea fastboot seems to work fine but sorry what do you mean by what ouput does fastboot devices have?
Thanks a lot
Meakii said:
Thanks have tried flashing them manually but still the same error saying FAILED: remote: flash write failure
It as if nothing can be written to the phone at all.
Yea fastboot seems to work fine but sorry what do you mean by what ouput does fastboot devices have?
Thanks a lot
Click to expand...
Click to collapse
write "Fastboot devices" in CMD while phone is in fastboot.
What happens when you boot in recovery? Try that, and do a factory data reset.
abaaaabbbb63 said:
write "Fastboot devices" in CMD while phone is in fastboot.
What happens when you boot in recovery? Try that, and do a factory data reset.
Click to expand...
Click to collapse
Ok see attached. Also it doesn't allow me to boot into recovery at all. I used the WUG kit to temporarily boot into TWRP and tried a factory reset there but it says there's no ROM installed. It's like everything has been wiped and it can't write anything to the internals to read from. Thanks for you help so far. Any other suggestions?
Meakii said:
Ok see attached. Also it doesn't allow me to boot into recovery at all. I used the WUG kit to temporarily boot into TWRP and tried a factory reset there but it says there's no ROM installed. It's like everything has been wiped and it can't write anything to the internals to read from. Thanks for you help so far. Any other suggestions?
Click to expand...
Click to collapse
Just... stop using toolkits for a second here! These automated processes got you here in the first place.
Try this command:
fastboot erase userdata
Does it succeed?
abaaaabbbb63 said:
Just... stop using toolkits for a second here! These automated processes got you here in the first place.
Try this command:
fastboot erase userdata
Does it succeed?
Click to expand...
Click to collapse
Ok ummm see attached. I'm so gutted any further thoughts or advice?
Meakii said:
Ok ummm see attached. I'm so gutted any further thoughts or advice?
Click to expand...
Click to collapse
It seems like a brick. Something got corrupted. I searched far an wide on XDA and other forums, but no one with this problem has found the solution.
It seems that your last chance is RMA.
abaaaabbbb63 said:
It seems like a brick. Your internal memory got corrupted. I searched far an wide on XDA and other forums, but no one with this problem has found the solution.
It seems that your last chance is RMA.
Click to expand...
Click to collapse
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
Who knows? Try it!
I don´t think the reason was CF-auto root. There must be something wrong with the device´s flash from the beginning. My thoughts are that you´r flash has a corrupted area which surprisingly wasn´t used for the stock factory flash and CF-autoroot triggered it while flashing a specific partition. Maybe i´m completely wrong.
I hope you´ll get it exchanged :good:.
Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
I don't really know what happened. I guess there are always risks when using tools like this. That's why I always recommend rooting using the manual method.
I have no idea how google will react. In theory, a simple unlocked bootloader won't affect warranty. In reality, anything can happen. Good luck, and sorry!
Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.
abaaaabbbb63 said:
I don't really know what happened. I guess there are always risks when using tools like this. That's why I always recommend rooting using the manual method.
I have no idea how google will react. In theory, a simple unlocked bootloader won't affect warranty. In reality, anything can happen. Good luck, and sorry!
Click to expand...
Click to collapse
Absolutely gutted but thanks so much for your help. I'll report back with Googles response.
pert_S said:
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.
Click to expand...
Click to collapse
It will respond, but the memory won't flash. Major no-fix problem.
pert_S said:
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.
Click to expand...
Click to collapse
Hi nah it only boots into Fastboot mode where it says down the bottom in red "LOCK STATE - unlocked" . Have tried every trick posted on here but it seems that during the rooting process somehow corrupted internal storage meaning it can't write anything to the phone (therefore not being able to reset to factory etc etc).
What a disaster.
Would opening the command prompt window with administrative rights make a difference? Worth a shot.
Meakii said:
Hi nah it only boots into Fastboot mode where it says down the bottom in red "LOCK STATE - unlocked" . Have tried every trick posted on here but it seems that during the rooting process somehow corrupted internal storage meaning it can't write anything to the phone (therefore not being able to reset to factory etc etc).
What a disaster.
Click to expand...
Click to collapse
Oh I see.
Well like abaaaabbbb63 said, in theory it shouldn't affect warranty.
They would have to show that unlocking the bootloader caused the fault I presume.
Make sure you tell Google that this happened when using a toolkit and a script when asking for a new phone free of charge.
Sent from my Nexus 5 using Tapatalk
El Daddy said:
Make sure you tell Google that this happened when using a toolkit and a script when asking for a new phone free of charge.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
How would that help? I think pleading ignorance to how it happened would probably be best wouldn't it?
Thanks for all the replies.
It's sarcasm friend. ;3. Daddy isn't a fan of toolkits nor of people claiming new handsets after a problem occurs as a result of one.

[Q] Nexus 5 Flash Write Failure

Hey guys,
I have a rooted Nexus 5 and on Saturday it suddenly froze and when I restarted the phone it was stuck on a boot loop. I tried to go into my TWRP recovery and it asked for a password and it says that the internal storage is 0 MB. I have tried to flash stock rom using fastboot manually and it keeps saying (remote: flash write failure). Will someone please help me on this? I can't figure out what to do.
Thank You
sounds like your internel memory went bad. youll need to replace it.
amalthomas994 said:
Hey guys,
I have a rooted Nexus 5 and on Saturday it suddenly froze and when I restarted the phone it was stuck on a boot loop. I tried to go into my TWRP recovery and it asked for a password and it says that the internal storage is 0 MB. I have tried to flash stock rom using fastboot manually and it keeps saying (remote: flash write failure). Will someone please help me on this? I can't figure out what to do.
Thank You
Click to expand...
Click to collapse
Try to flash back only cache.img.
And if that doesn't work probably ur internal memory has some problem.
Nexus 5
varuntis1993 said:
Try to flash back only cache.img.
And if that doesn't work probably ur internal memory has some problem.
Click to expand...
Click to collapse
Hey, when i do that it says (remote: failed to erase partition)
I am dying here i have been trying to fix this since Saturday.
Is there anything else I can try?
Thank You.
Nexus 5
simms22 said:
sounds like your internel memory went bad. youll need to replace it.
Click to expand...
Click to collapse
Hey, where would I be able to buy that?
Thank You
this??
http://forum.xda-developers.com/showthread.php?t=2577447
going to search .. if i'll find something will post here
amalthomas994 said:
Hey, when i do that it says (remote: failed to erase partition)
I am dying here i have been trying to fix this since Saturday.
Is there anything else I can try?
Thank You.
Click to expand...
Click to collapse
Sorry to say it seems like ur internal memory partition has gone corrupt.
U will need to send ur device back to google or to lg service center.
Nexus 5
varuntis1993 said:
Try to flash back only cache.img.
And if that doesn't work probably ur internal memory has some problem.
Click to expand...
Click to collapse
By the way, what is the actual command to flash only cache.img, just making sure I did it correctly.
amalthomas994 said:
By the way, what is the actual command to flash only cache.img, just making sure I did it correctly.
Click to expand...
Click to collapse
Fastboot erase cache
Fastboot flash cache cache.img
Nexus 5
enricocid said:
this??
http://forum.xda-developers.com/showthread.php?t=2577447
going to search .. if i'll find something will post here
Click to expand...
Click to collapse
Hey, thank you, I tried that but this is what i get when i get to the adb part
e2fsck: unable to set superblock flags on /dev/block/platform/msm_sdcc.1/by-name
/userdata
amalthomas994 said:
Hey, where would I be able to buy that?
Thank You
Click to expand...
Click to collapse
no no no.. get your whole phone replaced. you wont have any issue doing it, its a known issue.
simms22 said:
no no no.. get your whole phone replaced. you wont have any issue doing it, its a known issue.
Click to expand...
Click to collapse
But since it is rooted and i can't relock the bootloader, will they replace it?
amalthomas994 said:
But since it is rooted and i can't relock the bootloader, will they replace it?
Click to expand...
Click to collapse
yes. if you bought it through google, they will generally replace rooted phones especially if its a hardware issue(has nothing to do with root). and if its not google, they wont boot it up anyways(i dont think).
amalthomas994 said:
But since it is rooted and i can't relock the bootloader, will they replace it?
Click to expand...
Click to collapse
did you try flashing userdata and cache via fastboot?
Nexus 5
simms22 said:
yes. if you bought it through google, they will generally replace rooted phones especially if its a hardware issue(has nothing to do with root). and if its not google, they wont boot it up anyways(i dont think).
Click to expand...
Click to collapse
Ok, thanks a lot, that atleast gives me some kind of hope lol
Nexus 5
samersh72 said:
did you try flashing userdata and cache via fastboot?
Click to expand...
Click to collapse
Yep, no luck, keep getting write errors
thanks anyways
Nexus 5
Hey everyone,
I am able to get to adb and fastboot, so is there any way I can fix the corrupted files or anything?
amalthomas994 said:
Hey everyone,
I am able to get to adb and fastboot, so is there any way I can fix the corrupted files or anything?
Click to expand...
Click to collapse
no, your storage is physically broken.
Nexus 5
simms22 said:
no, your storage is physically broken.
Click to expand...
Click to collapse
Ok thanks for the reply.
But WOW.. how can something like that even happen..
I know it was not a mistake I did
amalthomas994 said:
Ok thanks for the reply.
But WOW.. how can something like that even happen..
I know it was not a mistake I did
Click to expand...
Click to collapse
its actually a sorta common issue with the nexus 5. at least ive seen more than enough nexus 5 here with that issue. its a hardware issue, nothing you did.

IMEI Unknown

Hi guys! I've looked all around and tried the fixes that people recommended, which is basically going back to stock.
So this is what happened to my brother's phone:
Was using the phone and all a sudden the phone freezes (He was on Android L) and he rebooted it. After rebooting, the phone went into bootloop. He downloaded some program that supposedly fixes softbrick and bootloop (by flashing stock ROM) Nexus Root Toolkit v1.8.7.
The phone was fixed.. Kinda.. He couldn't get any cell signal. Turns out his baseband and IMEI read unknown. He has the box the phone came in, to we know the physical IMEI number.
Is there a fix for this? I've tried this thread http://forum.xda-developers.com/google-nexus-5/help/lost-imei-please-help-t2529103 but it didn't work.
Any ideas?
You_got_owned123 said:
Hi guys! I've looked all around and tried the fixes that people recommended, which is basically going back to stock.
So this is what happened to my brother's phone:
Was using the phone and all a sudden the phone freezes (He was on Android L) and he rebooted it. After rebooting, the phone went into bootloop. He downloaded some program that supposedly fixes softbrick and bootloop (by flashing stock ROM) Nexus Root Toolkit v1.8.7.
The phone was fixed.. Kinda.. He couldn't get any cell signal. Turns out his baseband and IMEI read unknown. He has the box the phone came in, to we know the physical IMEI number.
Is there a fix for this? I've tried this thread http://forum.xda-developers.com/google-nexus-5/help/lost-imei-please-help-t2529103 but it didn't work.
Any ideas?
Click to expand...
Click to collapse
Try to run the "fastboot earease cache" command in fastboot. Read the sticky thread in the general forum.
bitdomo said:
Try to run the "fastboot earease cache" command in fastboot. Read the sticky thread in the general forum.
Click to expand...
Click to collapse
Sad to say, I've already tried that.. Even tried to flash stock cache image.
You_got_owned123 said:
Sad to say, I've already tried that.. Even tried to flash stock cache image.
Click to expand...
Click to collapse
Also you said the baseband is unknown. Have you tried to reflash the radio/modem image?
bitdomo said:
Also you said the baseband is unknown. Have you tried to reflash the radio/modem image?
Click to expand...
Click to collapse
I've flashed radio, but modem I have not. I'll have to try that!
You_got_owned123 said:
I've flashed radio, but modem I have not. I'll have to try that!
Click to expand...
Click to collapse
It's the same thing!
restore fully to stock using LG Flashtool. See if that fixes...
rootSU said:
It's the same thing!
restore fully to stock using LG Flashtool. See if that fixes...
Click to expand...
Click to collapse
Can you by any chance give me a link? Did a quick Google search and didn't find anything official.
You_got_owned123 said:
Can you by any chance give me a link? Did a quick Google search and didn't find anything official.
Click to expand...
Click to collapse
See my signature
Sent from my Nexus 5 using Tapatalk
You_got_owned123 said:
Can you by any chance give me a link? Did a quick Google search and didn't find anything official.
Click to expand...
Click to collapse
Or check my signature.
Someone calls it modem and someone calls it radio.
rootSU said:
See my signature
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hey! I was reading on a thread where you helped someone fix their phone!
Did a stock flash do it for them? I got the factory images and ran the flash-all scrip and still nothing.
You_got_owned123 said:
Hey! I was reading on a thread where you helped someone fix their phone!
Did a stock flash do it for them? I got the factory images and ran the flash-all scrip and still nothing.
Click to expand...
Click to collapse
I help a lot of people. I cannot pick out individual instances.
Use LG flashtool
Sent from my Nexus 5 using Tapatalk
You_got_owned123 said:
Hey! I was reading on a thread where you helped someone fix their phone!
Did a stock flash do it for them? I got the factory images and ran the flash-all scrip and still nothing.
Click to expand...
Click to collapse
Also check if wifi mac address is changing after each reboot. Corrupted persist partition can cause problems like that and also other things like crasing apps
Check out my thread about it http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576. It worths a try. If it does not help then you have to buy a new motherboard or claim your warranty if you have any.
bitdomo said:
Also check if wifi mac address is changing after each reboot. Corrupted persist partition can cause problems like that and also other things like crasing apps
Check out my thread about it http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576. It worths a try. If it does not help then you have to buy a new motherboard or claim your warranty if you have any.
Click to expand...
Click to collapse
Perist will not mount. I hasn't seen factory image for persist partition.
You_got_owned123 said:
Perist will not mount. I hasn't seen factory image for persist partition.
Click to expand...
Click to collapse
Because there arent any. It is unique for every device like efs.
bitdomo said:
Because there arent any. It is unique for every device like efs.
Click to expand...
Click to collapse
So is that a problem?
You_got_owned123 said:
So is that a problem?
Click to expand...
Click to collapse
If you see that /persist cannot be mounted then it could be.
bitdomo said:
If you see that /persist cannot be mounted then it could be.
Click to expand...
Click to collapse
I tried wiping cache and then it gave me a bunch or partitions that were errors. With persist being one of them. After a while, I was able to clear cache with no errors.
You_got_owned123 said:
I tried wiping cache and then it gave me a bunch or partitions that were errors. With persist being one of them. After a while, I was able to clear cache with no errors.
Click to expand...
Click to collapse
Then it is up to you what are you going to do with the persist partition. You will lose nothing but time by formating the persist partition. If it not fix your problem then you have to buy a new motherboard for the phone to make phone calls either way because you dont have any efs backup.
bitdomo said:
Then it is up to you what are you going to do with the persist partition. You will lose nothing but time by formating the persist partition. If it not fix your problem then you have to buy a new motherboard for the phone to make phone calls either way because you dont have any efs backup.
Click to expand...
Click to collapse
Persist was the problem. Fixed that partition and was golden. Thank you so much all of you. Took 3 hours. So much Google.
You_got_owned123 said:
Persist was the problem. Fixed that partition and was golden. Thank you so much all of you. Took 3 hours. So much Google.
Click to expand...
Click to collapse
It would be nice if you would post how did you solve your issue. Some will learn and it could help others having the same issue.

[Q] Help me Unbrick my Moto G...please

Sorry for posting this, but please just try to understand me and help solve my problem. I know there is Threads for this, Please... I am just nowhere, my phone just treason me when I needed it most, It is very hard Bricked, nothing working, contacted support and they told me it need Replace (but I can't send to service #close this question)
My Story:
Constant restart loop, on Motorola logo. It can go in Bootloader when press Vol Down and Power Button, but that's it, (actually when going in recovery it goes to Broken Android sign, but than restart again)... so how it happened?? I do not know as u do not, I am just normal user, never done anything to crash system, never Rooted, even not installed any kind Launcher, nothing, just some normal Apps and only two game, and lot of music listening, that's it that's all (also physically it's like new, never ever droped or water splashed even). and one day come home, plug in for charging in my PC as always and boom, some strange app crashes and it restarted for EVERRR, wtf is this just do not understand, WHYY?????? so disappointed and so bored...
Question:
so Can it be Helped? Unbricked? I do not care Contacts or any kind Data, just work again....And if it can please step by step I will follow, and do not redirect me to other thread, just help me out here please
And if it cant be Helped, just say frankly and I will capture video how I am splashing it on REAL BRICK wall and will post it on this thread...this will be closing and **** sending of Motorola
My Spec:
Moto G (16GB Global GSM, no SD card slot, single SIM) - KitKat 4.4.4 (it bricked so I cant see Falcon version or other spec, but I have original Box)
I searched everywhere and seen lot, but all of them are 4.4.2 or 3 and also US versions, strange languages and so on. also here on XDA but as I'm Noob I do not know if it will work for me, and before destroy it completely I wanted to know from people who knows much more then me, what can do and what not, so please be patient for my Noobety, Thanks and Sorry...
help_me_if_u_can said:
Sorry for posting this, but please just try to understand me and help solve my problem. I know there is Threads for this, Please... I am just nowhere, my phone just treason me when I needed it most, It is very hard Bricked, nothing working, contacted support and they told me it need Replace (but I can't send to service #close this question)
Click to expand...
Click to collapse
Do you use Windows, Linux, Mac?
EDIT: Have you tried this yet? http://forum.xda-developers.com/showthread.php?t=2542219
StrangerWeather said:
Do you use Windows, Linux, Mac?
EDIT: Have you tried this yet? http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
I have Windows 8 x64, I did not tryed anything yet, want to know what would be clever and correct to do in my situation...which one should I download ???? from here
have no idea, all I know is before It bricked it was on 4.4.4 and I do not have US version, it is GLOBAL GSM
and it is Locked, never Unlocked Bootloader
help_me_if_u_can said:
I have Windows 8 x64, I did not tryed anything yet, want to know what would be clever and correct to do in my situation...which one should I download ???? from here
have no idea, all I know is before It bricked it was on 4.4.4 and I do not have US version, it is GLOBAL GSM
and it is Locked, never Unlocked Bootloader
Click to expand...
Click to collapse
Dual sim or single sim? What region?
StrangerWeather said:
Dual sim or single sim? What region?
Click to expand...
Click to collapse
Single Sim, Georgia (not in US)
help_me_if_u_can said:
Single Sim, Georgia (not in US)
Click to expand...
Click to collapse
Ok, is it XT1032?
Don't worry, we'll get there...
StrangerWeather said:
Ok, is it XT1032?
Click to expand...
Click to collapse
I do not remember, is there any way to check it? I will do that if so, thanks
help_me_if_u_can said:
I do not remember, is there any way to check it? I will do that if so, thanks
Click to expand...
Click to collapse
Not sure. Just one thought, why don't you try a factory reset? https://www.youtube.com/watch?v=LoTAsuPey_E
StrangerWeather said:
Not sure. Just one thought, why don't you try a factory reset?
Click to expand...
Click to collapse
Remember with Support Team I already did that, but not worked.
I will try again as in this video after couple hours and share results quickly.
StrangerWeather said:
Not sure. Just one thought, why don't you try a factory reset?
Click to expand...
Click to collapse
so, I can reach to wipe manu and wiped it also wipe cache from there but not like in this video, my device is laggin on every step and after I wiped it steel when restart it normaly stuckes on Motorola
one thing to add, my device is not Power Off, it constatnly restating, if I will try to power off it will power on again
help_me_if_u_can said:
so, I can reach to wipe manu and wiped it also wipe cache from there but not like in this video, my device is laggin on every step and after I wiped it steel when restart it normaly stuckes on Motorola
one thing to add, my device is not Power Off, it constatnly restating, if I will try to power off it will power on again
Click to expand...
Click to collapse
Ok, don't worry, just follow the tutorial to reflash stock firmware and it will work again.
You need this: http://www.filefactory.com/file/1dw..._4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml.zip
The only thing to say is that when you reach:
Code:
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
you may have to try this instead if it doesn't work:
Code:
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
Let us know how it goes!
okey I will try it right now, thaanks
StrangerWeather said:
Let us know how it goes!
Click to expand...
Click to collapse
I tryed but no result, I think because that my bootloader is locked....here I made screenshot of whole process and every command gives me [OKEY] but after that is failure....it I think is permissions problem because locked bootloader
So, I need to unlock it right?????? I already have key from motorola, just get... I will wait your answer...
StrangerWeather
??????????????
help_me_if_u_can said:
StrangerWeather
??????????????
Click to expand...
Click to collapse
Oops, sorry, I forgot... It's up to you about unlocking bootloader. If you do, you can't send your phone back for them to sort out the problem. However, if you root your phone, you'll be able to install a custom recovery such as TWRP, sideload a rom, and hopefully all will work. But of course I can't guarantee that it will work, so it's a risk. If it were me, I would send it back as you haven't rooted it and really it shouldn't brick itself on its own for no reason.
StrangerWeather said:
Oops, sorry, I forgot... It's up to you about unlocking bootloader. If you do, you can't send your phone back for them to sort out the problem. However, if you root your phone, you'll be able to install a custom recovery such as TWRP, sideload a rom, and hopefully all will work. But of course I can't guarantee that it will work, so it's a risk. If it were me, I would send it back as you haven't rooted it and really it shouldn't brick itself on its own for no reason.
Click to expand...
Click to collapse
tell me, if I want to install this stock firmware I need to unlock bootloader??? and because it not installing? or my device is problematic and it can be installed on locked bootloader?
help_me_if_u_can said:
tell me, if I want to install this stock firmware I need to unlock bootloader??? and because it not installing? or my device is problematic and it can be installed on locked bootloader?
Click to expand...
Click to collapse
This what the op says:
I have only tested this on a UK Retail Moto G with an unlocked bootloader, however as these are the original stock signed image files from Motorola it should work on all devices.
[. . .]
Edit: tkm89 reports that he was able to use this guide to restore Stock Retail British firmware on a bootloader locked Tesco-mobile Moto G
Click to expand...
Click to collapse
StrangerWeather said:
This what the op says:
Click to expand...
Click to collapse
I unlocked BOOTLOADER but steel geting Fail after OKEY, what could be reason? can I do something??? any ****ing thing to start this device working??
help_me_if_u_can said:
I unlocked BOOTLOADER but steel geting Fail after OKEY, what could be reason? can I do something??? any ****ing thing to start this device working??
Click to expand...
Click to collapse
I'm not sure what the reason is but if I were you I would now try to root my device, install TWRP, sideload a rom, and hope for the best.
To root, use: http://www.theandroidcop.com/how-to-root-motorola-moto-g/
Hope it goes well!
no help....
on every step, I am getting Fails....What could be Problem??? drivers??? or what?????? ANYONE????????
Unlocked Bootloader

[SOLVED] Nexus 5 32Gb won't go back to full internal storage. Tried everything!

So after a few weeks after the launch of the Marshmallow uptade, I flashed the stock image with fastboot using a Mac and everything gone flawlessly, until I saw my internal storage. My 32Gb nexus became a 16Gb model.
I search in EVERY Forum I found on the internet, and I have good skills on recovering android phones with software problems, all the "how-to's" I found were with very easy instructions, but NONE of then worked for me.
Ive tried EVERYTHING I found on the internet. Do a factory reset, tried to resize the partition using TWRP, flashed manually all the partitions, flashed the stock image again and again many times, flashed customs roms, tried to erase the userdata, cache and system partitions tons of times using flashtool on windows, mac and linux and NOTHING worked. In all the process my phone started with no problems, but my internal storage stayed 12,55gb. My Bootloader shows 32Gb model, the IMEI on LG database shows 32Gb model AND the logic board indicates a 32Gb model... I really don't know what to do! Anyone can save me???? Thanks!
In advance information, I followed every step on this guide at least 10 times, and didn't work:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
I was thinking in the possibility of an custom Userdata partition, only for the 32Gb model, that I can flash manually or a program, like GParted, that I can manually resize the data partition.
I'm really desesperate here, so sorry for any english mistakes, since I speak portuguese, or any dumb idea.
Thanks for any help!
-------------------------------------- FOUND THE SOLUTION! ----------------------------------------------
After WEEKS trying to realize what the hell happened and rethinking every possible form to regain my full storage, I've found the solution.
Fiddling with the partitions on the phone, i learned that there is a partition on the system, that "informs" the userdata that the phone is a 16Gb or a 32Gb variant, and it's called "Primary GPT".
I realized that the guy who sold to me, recovered the phone from an brick it suffered, but he used a 16Gb model GTP partition to reinstall the bootloaders and the system, so, no matter how many different process I tried, I would NEVER recognizes the 32Gb, because THIS partition was telling the system that it was a 16Gb model.
(Little of a noob explain but that was the way I got it...)
So all I had to do was use this thread to reflash the correct GPT partition:
http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
And then, reflash the complete system image file, and after the boot, my phone recognized the 32Gb internal storage again!
Thank you guys for the effort in sorting out any way to help me, I hope this thread can help someone else facing the same problem in the future!
Peace!
Did you flash the userdata.img file too?
audit13 said:
Did you flash the userdata.img file too?
Click to expand...
Click to collapse
Tried everything I could do... Flashed userdata partition, erased the partition with fastboot then entered in recovery mode (stock and custom) and then format the userdata from there, doing that by doing a factory reset and wiping cache partition and nothing...
Any other idea what it could be?
Unfortunately, I have no idea why this happened or how to fix it as I only have the 16 GB version.
seriously guys, anybody to save my day?
audit13 said:
Unfortunately, I have no idea why this happened or how to fix it as I only have the 16 GB version.
Click to expand...
Click to collapse
Thanks anyway bro!
Have you tried factory reset and wiping cache from STOCK recovery? That always works for me.
Try using flash-all.bat in Windows. Part of the stock favor image. Make sure to take backup before doing it though
Had this happen once and had to factory reset from stock recovery like he said above. Worked like a charm!
redsmith said:
Have you tried factory reset and wiping cache from STOCK recovery? That always works for me.
Click to expand...
Click to collapse
shri_chanakya said:
Try using flash-all.bat in Windows. Part of the stock favor image. Make sure to take backup before doing it though
Click to expand...
Click to collapse
Nevermindthelabel said:
Had this happen once and had to factory reset from stock recovery like he said above. Worked like a charm!
Click to expand...
Click to collapse
Ive tried with stock recovery, custom recovery, CWM, TWRP Resize partition and no use...
I lost the count of times Ive tried to flash manually, flash-all.bat in windows, flash-all.sh on mac and linux, really nothing work.
There is no toolkit, even knowing its a bad idea to use those things but, since Im out of options, anyone can tell me one that can help me?
Thanks guys btw!
I had this problem with a couple devices on lollipop, typing the command below in a terminal fixed it. Reboot afterwards.
su
restorecon -FR /data/media/0
lynnux said:
I had this problem with a couple devices on lollipop, typing the command below in a terminal fixed it. Reboot afterwards.
su
restorecon -FR /data/media/0
Click to expand...
Click to collapse
can you explain what is the function of this line? Tried here and everything stayed the same
Thanks!
Damn... that's weird.
Is it possible to format userdata? Like, for example, "fastboot format userdata"? I don't really know, just shooting in the dark by this point now.
nameless-- said:
can you explain what is the function of this line? Tried here and everything stayed the same
Thanks!
Click to expand...
Click to collapse
I believe it's a way of restoring data or storage to it's original configuration. Also had this problem on my 32gb N5 early on, unfortunately I can't remember what I did that time to get it back.
redsmith said:
Damn... that's weird.
Is it possible to format userdata? Like, for example, "fastboot format userdata"? I don't really know, just shooting in the dark by this point now.
Click to expand...
Click to collapse
Yes, I did this process three times I think, format userdata and erase userdata, none of then resolved the issue
lynnux said:
I believe it's a way of restoring data or storage to it's original configuration. Also had this problem on my 32gb N5 early on, unfortunately I can't remember what I did that time to get it back.
Click to expand...
Click to collapse
I tried this code using the terminal on the phone, rebooted and the storage stayed the same, I'll try to do the same process using adb shell from my windows computer, since I have the "light"version of adb and fastboot installed on my mac and the adb shell comand is giving me the "offline" error...
I'll get back here with any updates.
thanks in advance guys! Hope this comand works! :highfive:
Well... Tried with my windows computer, and next with my Mac, with the command line given and.... Nope. Nothing changed.
I know it's not great but if your desperate....
I've always done things manually but there comes a time when your willing to try whatever to fix your phone as they don't come cheap, so if I could recommend a toolkit that has saved my ass more than once and has worked flawlessly for me every time maybe it could help you too.
http://www.wugfresh.com/nrt/
It's called Nexus Root Toolkit and its by the developer wugfresh. Try this if you'd like, if not I hope you find a solution. This kit has everything you can think of that could help you with rooting, or returning to stock and relocking. Best of luck with your journey!
MechanicalMecca said:
I've always done things manually but there comes a time when your willing to try whatever to fix your phone as they don't come cheap, so if I could recommend a toolkit that has saved my ass more than once and has worked flawlessly for me every time maybe it could help you too.
http://www.wugfresh.com/nrt/
It's called Nexus Root Toolkit and its by the developer wugfresh. Try this if you'd like, if not I hope you find a solution. This kit has everything you can think of that could help you with rooting, or returning to stock and relocking. Best of luck with your journey!
Click to expand...
Click to collapse
I'll try this as soon as possible, thanks!
Hey Nameless--,
I tried everything possible as you did, but when i tried your steps i am facing an issue. I cannot see Qualcomm HS-USB QDLoader 9008 under device manager
Can you help me?
Dhaval Raichura said:
Hey Nameless--,
I tried everything possible as you did, but when i tried your steps i am facing an issue. I cannot see Qualcomm HS-USB QDLoader 9008 under device manager
Can you help me?
Click to expand...
Click to collapse
The wrong size memory issue, 16 Gb instead of 32, is an old issue. It can be solved by booting into the stock recovery then clearing cache and then doing a factory reset. Note, this will wipe your device.
Sent from my Nexus 9 using XDA Free mobile app

Categories

Resources