Develop Bugs

[Q] Is it possible to resurrect partitions?

Hello.
I have a bit trouble with my Desire z.
A small story:
Two days ago, I've decided to flash xustom cm9-based rom to my phone, and I did it. I really like android 4, but rom has some bugs, so I decided to restore my cm7 rom. I've made a backup, before flashing cm9.
When I made a restore, I've noticed, that phone was not booting.
Problems:
1. Cwm can't read it's logs "log" and "log_last" from /cache/recovery/.
2. I can't flash any rom with cwm. It shows me error in archive and returns "status 1".
3. I can't format/mount/unmount /cache, /data, /system and other partitions. But it seems, that /data and /cache wipe works well.
It seems, that the main problem is trouble with partitions.
I've tried to flash stock rom 1.34 through hboot, but it seems that hboot canno't recognise rom, cos there are no lines such as "install update" or "install rom"…
So, question: how can I fix it and…can I really?
Detailed instructions in "step-by-step" form will be great
Thanks.
P.s: sorry for bad english.

I'm sorry to say but you are showing signs of a failed emmc,
All is not lost, hopefully you'll be fine. See here to find out for sure
http://forum.xda-developers.com/showthread.php?p=33917375
Sent from my Nexus 7 using xda premium

Thank you very much for the link. Ill try to get some system info later and post it here.
Now I can just confirm that I can boot to cwm and flash newer one via fastboot. Adb also works.

demkantor said:
I'm sorry to say but you are showing signs of a failed emmc,
All is not lost, hopefully you'll be fine. See here to find out for sure
http://forum.xda-developers.com/showthread.php?p=33917375
Click to expand...
Click to collapse
Khm, so...I read your topic, and find it very useful.
My logs:
Logcat
Recovery
Output of 'cat /proc/kmsg | grep 'mmc0:0001'
Code:
~ # cat /proc/kmsg | grep 'mmc0:0001'
<6>[ 4.772766] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
Checked eMMC in fastboot
I still can boot to recovery and hboot, but can't format /system and other partitions.
CWM Version: 'ClockworkMod Recovery v5.8.1.0'
So, is my eMMC damaged and I got to change it physically?
Thanks.
P.S: For addition, there is no bootloop. I just see HTC logo and that's all.

Well it looks like you have the bad emmc and it has failed. Replacing it yourself would be very tricky unless your are a master @ fine soldering
(I tried myself and you need a machine to do it)
You can try flashing one of the pc10img.zips from the thread, granted I don't think it will do anything. You can probably fine a broken dz out there on the cheap and replace logic boards?
Sorry to be the bearer of bad news but that's all I got...
Sent from my Nexus 7 using xda premium

demkantor said:
Well it looks like you have the bad emmc and it has failed. Replacing it yourself would be very tricky unless your are a master @ fine soldering
(I tried myself and you need a machine to do it)
You can try flashing one of the pc10img.zips from the thread, granted I don't think it will do anything. You can probably fine a broken dz out there on the cheap and replace logic boards?
Sorry to be the bearer of bad news but that's all I got...
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Oh, sad...
Well, it seems that I've got to bring phone to 'service center', and ask for changing a eMMC...okay...
Thank you for your answers and help.

[manta][CWM Advanced Edition] PhilZ Touch

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
To take a screen shot, just slide left
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Nexus 10 (manta)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse

Phil3759 said:
Flashing can brick your phone
This will be removed after people report it is booting fine without bricking their phone
Click to expand...
Click to collapse
But... my phone is across the room and isn't even Android. Maybe I should rip the battery out just to be safe though
This sounds pretty cool though.

espionage724 said:
But... my phone is across the room and isn't even Android. Maybe I should rip the battery out just to be safe though
This sounds pretty cool though.
Click to expand...
Click to collapse
I warn people when I release an untested recovery on a given device
Most noobs tend to forget that flashing is not a safe operation. It can always turn into a nightmare
You can check the list of currently supported devices from main thread here: http://forum.xda-developers.com/showthread.php?t=2201860
And browse into the different device support forums
Till now, the warning never became true except when some people flashed the wrong file in their phone
This warning should keep noobs away from testing it

Ah, yeah I have nothing against the warning, glad it's there even The Nexus 10 is a tablet though, not phone

espionage724 said:
Ah, yeah I have nothing against the warning, glad it's there even The Nexus 10 is a tablet though, not phone
Click to expand...
Click to collapse
LoL
It is a generic copy paste message
Well, will you be the first to give a feedback ?

Phil3759 said:
Well, will you be the first to give a feedback ?
Click to expand...
Click to collapse
Sure
I went to bootloader, erased recovery and flashed this one. Rebooted to recovery.
Battery meter at top-right says -1% (my tablet was on Pogo charge for hours prior to flashing). Get an error about being unable to create brightness sys file. During key test, randomly getting constant presses when holding 3 fingers on screen (probably a touchscreen-related issue).

espionage724 said:
Sure
I went to bootloader, erased recovery and flashed this one. Rebooted to recovery.
Battery meter at top-right says -1% (my tablet was on Pogo charge for hours prior to flashing). Get an error about being unable to create brightness sys file. During key test, randomly getting constant presses when holding 3 fingers on screen (probably a touchscreen-related issue).
Click to expand...
Click to collapse
Thank you for the feedback (reached my daily limit for :good
Brightness:
Do you by case know the path for your device brightness file?
Not a big deal though as I can search / look for it in rc files. I used Samsung usual path, but it seems they used a different one for google devices
Battery:
Will check for the battery path used
Touch
It is supposed to be one finger to use
Interesting though...

Can any one run this in adb shell while in recovery
Or you can use the console terminal in aroma file manager while in recovery
Code:
find /sys/. -name '*bright*' >/sdcard/brightness.txt
Then
Code:
find /sys/. -name '*battery*' >/sdcard/battery.txt
And attach the resulting brightness.txt and battery.txt files on sdcard
About multi touch: i will look to allow only slot 0 to ignore second finger
Sent from my GT-I9100 using Tapatalk 2

Forget it. I found path in source
Sent from my GT-I9100 using Tapatalk 2

Ok, still would need battery info it seems
Code:
find /sys/class/power_supply/ -name '*' >/sdcard/battery.txt
And as described above, attach resulting battery.txt file here
Please do this in recovery, not main system
Sent from my GT-I9100 using Tapatalk 2

Phil3759 said:
Ok, still would need battery info it seems
Code:
find /sys/class/power_supply/. -name '*' >/sdcard/battery.txt
And as described above, attach resulting battery.txt file here
Please do this in recovery, not main system
Click to expand...
Click to collapse
see attached - is this what you're looking for?

Ok,
Can you do this now:
Code:
ls-l /class/power_supply/android-battery >/sdcard/battery.txt
And attach the file
Many thanks

Phil3759 said:
Ok,
Can you do this now:
Code:
ls-l /class/power_supply/android-battery >/sdcard/battery.txt
And attach the file
Many thanks
Click to expand...
Click to collapse
Sorry I'm a bit out of sync with you -- but I've attached the one you asked for just before revising your post.
find /sys/class/power_supply/ -name '*' >/sdcard/battery.txt
Result is attached. I'll run the other command in a moment.

Phil3759 said:
Ok,
Can you do this now:
Code:
ls-l /class/power_supply/android-battery >/sdcard/battery.txt
And attach the file
Many thanks
Click to expand...
Click to collapse
OK -- re-learning linux command line as I go (it's been many years!). Good to wake up that part of the brain again...
Had to modify command above: needed a space between ls and -l, and I'm assuming you want "/sys" up front in the fully qualified file name... Assuming that's all good, the new result is attached as battery2.txt
Let me know if this is what you need, or if anything else is needed. I've got some time to squeeze in a few of these today as needed. Also REALLY looking forward to trying this out on my N10 (and would love to see this on the Galaxy Nexus if ever possible!).

Sorry for the time I make you loose
Was at work, on a hurry, typing using tapatalak mess
I am at home and I could test before posting this. The symlinking is a small issue to first traverse folders wthout going into tons of links
Anyway, here's what should find the needed files
Code:
ls -l /sys/class/power_supply/android-battery/* >/sdcard/battery.txt
Thank you for your patience :good::good:

Phil3759 said:
Sorry for the time I make you loose
Was at work, on a hurry, typing using tapatalak mess
I am at home and I could test before posting this. The symlinking is a small issue to first traverse folders wthout going into tons of links
Anyway, here's what should find the needed files
Code:
ls -l /sys/class/power_supply/android-battery/* >/sdcard/battery.txt
Thank you for your patience :good::good:
Click to expand...
Click to collapse
Try the attached...

jonstrong said:
Try the attached...
Click to expand...
Click to collapse
bingo :good:
Code:
/sys/class/power_supply/android-battery/capacity

Phil3759 said:
bingo :good:
Code:
/sys/class/power_supply/android-battery/capacity
Click to expand...
Click to collapse
Great -- let me know if you need anything else -- I'm home today, and can pull some more if needed.

Does this recovery support USB OTG?

I must be in stupid mode today !!
Have been running Galaxy S3 with PhilZ Touch for some time now .... superb :good:
Got a new Nexus 10 last week and want it on there as well ..... stupid bit coming now
Downloaded latest version from this thread - but it shows as "philz_touch_5.00.7-manta.img"
Not a zip or a tar file for Odin ..... what am I missing from under my nose?
Homer

interal sdcard not mounting?

I flashed franco kernel nighltie r364 on a JB 4.2 stock rom on a Galaxy Nexus, now the internal SD won't mount..
Have I permanently lost all the data? can someone please explain how I can recover/resolve this.
I've tried to mount it in TWRP and it's unselected (default set to mount), yet after a reboot I still can't access the internal sdcard.
Also, no apps work, I guess it's cause they're all on the internal sdcard.
Finally the name 'legacy' appears under the sdcard0 folder (it actually looks like a file now with a golden star against it), I see this using root explorer; the only app that works.
If anyone can help it would be appreciated...
---
smash'n
SGS2 GT-I9100

Paste the output of 'adb shell ls /sdcard/' and 'mount'.
a maguro wrote this.

beekay201 said:
Paste the output of 'adb shell ls /sdcard/' and 'mount'.
a maguro wrote this.
Click to expand...
Click to collapse
I'll pm you, if you don't mind
---
smash'n
SGS2 GT-I9100

beekay201 said:
Paste the output of 'adb shell ls /sdcard/' and 'mount'.
a maguro wrote this.
Click to expand...
Click to collapse
Thanks for poiting me in the direction of adb!
I swear I'll never mess with a Nexus again.
I resolved all I needed but took 12hrs and no sleep to get adb to recognise (with a bit of tom foolery) and pull the files we needed.
I"m just gona wipe the whole phone and start a fresh.
Now time to enjoy the rest of our hols.
At least we saved our child's photos.
Thanks again.
---
smash'n
SGS2 GT-I9100 (and never will be Galaxy Nexus)

UPDATE.
I just want to update this thread regarding my experience.
Firstly, this problem occured again!!
This is how I solved it;
[SOLVED]
Well I spent allnight/day (18hrs really)reading and conducting a whole host of procedures, from; using adb too resorting back to stock.
Needless to say nothing worked correctly!!
What I eventually did was to use WUGFRESH Galaxy Nexus Toolkit v1.6.4 and it stripped (reformatted) the phone and placed a clean stock firmware back.
I say reformatted hestitantly, as all other methods that I used and know of (from my time modding my S2) didn't work, at all (when applied to this phone) as each time the internal storage 'could not be mounted or accessed', I can only imagine something was severely corrupted.
WUGFRESH downloaded the necessary files and during its running, automatically indicated that some files could not be accessed or weren't present on the phone (I read this via the cmd screen on WUGFRESH), it then tx and loaded the necessary files (what I can describe as a reformat) and after all processes I rebooted and vola! access to internal storage regained.
Also, just to add, [before I started the process] the same WUGFRESH SW also allowed me to pull files from the internal storage (personal family photos and videos), even though adb wouldn't mount the storage or push or pull files from the phone, all other procedures/methods I tried wouldn't work either! WUGFRESH was the only one that worked.
After everything, I conducted a nandroid! what a headache, and it aint even my phone (it belongs to my fiancè).
Thanks for all the support in the thread, needless to say I hope all my experience in the last 18hrs helps someone else.
---
smash'n

You're holding it wrong. You should have read the stickies, but your goal wasn't to learn anything anyways so..
and another thing: not that I use it, but it's WUGFRESH toolkit - at least get the name right. It bothers me when people don't call stuff by their names.
don't create 2 threads for the same issue. Reported.

soz on the wrong naming of WUGFRESH.
REPORTED? Why? my two threads were ligit!, all posted in Q&A, based on the same issue but within two areas
1. stock recovery
2. this thread
---
smash'n
SGS2 GT-I9100

So it took you 18 hours and you never tried ADB or Fastboot by itself?
toolkits are nothing more than a front end hiding the commands from the user by using ADB and Fastboot...congrats on learning nothing in the process? I see nothing in your resolution that indicates that the GOOGLE provided tools would not work.
Sigh....another toolkit thread. YAY!

Pirateghost said:
So it took you 18 hours and you never tried ADB or Fastboot by itself?
toolkits are nothing more than a front end hiding the commands from the user by using ADB and Fastboot...congrats on learning nothing in the process? I see nothing in your resolution that indicates that the GOOGLE provided tools would not work.
Sigh....another toolkit thread. YAY!
Click to expand...
Click to collapse
YES, I tried adb cmds and bootloader/fastboot (as I mentioned above) same as I would on a S2, each time reverting back to stock on this nexus never gave access to the internal storage; this was the problem.
Hence I used a toolkit, and it worked.
I'm not an expert in modding android but I know some stuff, and this nexus wasn't playing to a rule book, as all the adb cmds and methods I found online (and are basic) never worked, no thread gave a solution that worked, similar google searchers.
I didn't go into this blind, but I never expected so much hassle modding this phone, as I rooted it and flashed a stock ROM weeks/months ago without problems.
As for learning anything (you're the 2nd person to mention it), I've learned a lot from the xda community (personally) and through threads.. though the issue I experienced was never written about in the sense I experienced it and had to resolve it.
---
smash'n
SGS2 GT-I9100

Can only boot into any 4.3rom ONCE after that any reboots get stuck at Google screen

Anybody else had this issue? I tried it on Shiny Rom and now CM 10.2 nightly. Get in one time with no issues, if I reboot I get stuck at the Google screen. The one way to get the phone usable is to do a completely factory data wipe and start all over.
I'm using TWRP, I've flashed tons of roms and I'm doing it no different than any of them. I do a complete wipe, install CM, GApps, reboot I get in one time. Do a reboot and then get stuck at Google screen.
This happened with both ShinyROM and 10.2 both are 4.3. They both had a valid MD5.
I have flashed PRIMEMD04_Bootloader-signed - One that came from Shiny ROM bootloader-toro-primelc03 - Stock (I believe)
Nothing worked, got the same issue.

GiZiM said:
Anybody else had this issue? I tried it on Shiny Rom and now CM 10.2 nightly. Get in one time with no issues, if I reboot I get stuck at the Google screen. The one way to get the phone usable is to do a completely factory data wipe and start all over.
I'm using TWRP, I've flashed tons of roms and I'm doing it no different than any of them. I do a complete wipe, install CM, GApps, reboot I get in one time. Do a reboot and then get stuck at Google screen.
This happened with both ShinyROM and 10.2 both are 4.3. They both had a valid MD5.
I have flashed PRIMEMD04_Bootloader-signed - One that came from Shiny ROM bootloader-toro-primelc03 - Stock (I believe)
Nothing worked, got the same issue.
Click to expand...
Click to collapse
The only time I get persistent Google screen is when I have a corrupt /userdata partition.
Try running e2fsck on mmcblk0p12 if you have one of those devices that get emmc corruption by changes in sdcard free space.
In case you need more information on this :
1. In TWRP Mount options, unmount Data. The command won't work on mounted partition.
2. In Advanced > Terminal Command, select the /dev/block folder. Then type in
Code:
e2fsck -n mmcblk0p12
("-n" option will cause no changes to your filesystem, it just shows a simulation of the file system correction tool's result.) If the result says the filesystem is "clean", then you have something else to worry about and its not corrupted /userdata.
3. If it starts checking for errors (there's a KILL button while running the command), your filesystem has errors. You can kill it, and then run
Code:
e2fsck -f -C 0 -y mmcblk0p12
(-f is for forced run, -C 0 will give you progress of completion of task, -y will say yes to all prompts (necessary), and mmcblk0p12 is the /userdata partition)
4. Let the command run until you don't see the KILL button (shouldn't be more than a couple of minutes). On running
Code:
e2fsck -n mmcblk0p12
again, it must show you a "clean" filesystem.
5. Just reboot to System. If your /userdata was corrupt, running this will mostly solve your problem.
Damn, I wish I had found such instructions to get over my horrendous time with corrupt partitions over six months from November 2012-April 2013.

Thank you! I will look into this but I would love to fix the cause.
I'm sure this is the issue because I cannot get the phone back into a working state until after doing a full factory wipe.
What would be causing 4.3 roms to corrupt my /userdata? Whatever it is it is happening after the first reboot after I get into the rom.
desktopfusion said:
The only time I get persistent Google screen is when I have a corrupt /userdata partition.
Try running e2fsck on mmcblk0p12 if you have one of those devices that get emmc corruption by changes in sdcard free space.
In case you need more information on this :
1. In TWRP Mount options, unmount Data. The command won't work on mounted partition.
2. In Advanced > Terminal Command, select the /dev/block folder. Then type in
Code:
e2fsck -n mmcblk0p12
("-n" option will cause no changes to your filesystem, it just shows a simulation of the file system correction tool's result.) If the result says the filesystem is "clean", then you have something else to worry about and its not corrupted /userdata.
3. If it starts checking for errors (there's a KILL button while running the command), your filesystem has errors. You can kill it, and then run
Code:
e2fsck -f -C 0 -y mmcblk0p12
(-f is for forced run, -C 0 will give you progress of completion of task, -y will say yes to all prompts (necessary), and mmcblk0p12 is the /userdata partition)
4. Let the command run until you don't see the KILL button. On running
Code:
e2fsck -n mmcblk0p12
again, it must show you a "clean" filesystem.
5. Just reboot to System. If your /userdata was corrupt, running this will mostly solve your problem.
Damn, I wish I had found such instructions to get over my horrendous time with corrupt partitions over six months from November 2012-April 2013.
Click to expand...
Click to collapse

Whatever my phone faces is not limited to 4.3. It has been happening since 4.1. Something to do with the eMMC of the phone itself. Gets corrupt too easily when the decreasing free sdcard space approaches 3 GB. Sometimes a battery pull can also cause it, sometimes a random reboot can cause it. Technically, 4.3 is supposed to solve this issue with TRIM execution in the background, but it hasn't helped me definitively yet.
It has been documented on these forums for this to happen to phones produced in August, September, October 2012.
In my case, I am quite sure that adding and/or deleting files larger than say 500 MB (for example Nandroid backups) causes this problem to happen at any time afterwards without notice (preceded by random reboot straight into stuck Google screen). I guess new ROMs can cause such issues if there is a large amount of app data deleted everytime, but this is just uninformed speculation.
I've setup Tasker profiles to autorun e2fsck through TWRP every morning before I wake up so I don't have these issues while awake. And one more profile to tell me every 8 hours if my sdcard has changed by a lot.
I hope this is all there is to your phone's problem!

Thanks this is very helpful, I will work on this tonight after work and see what I can come up with.
Right now it is showing as CLEAN but i'm running 4.2.2. Is there anything special to go from 4.2.2 to 4.3?
desktopfusion said:
Whatever my phone faces is not limited to 4.3. It has been happening since 4.1. Something to do with the eMMC of the phone itself. Gets corrupt too easily when the decreasing free sdcard space approaches 3 GB. Sometimes a battery pull can also cause it, sometimes a random reboot can cause it. Technically, 4.3 is supposed to solve this issue with TRIM execution in the background, but it hasn't helped me definitively yet.
It has been documented on these forums for this to happen to phones produced in August, September, October 2012.
In my case, I am quite sure that adding and/or deleting files larger than say 500 MB (for example Nandroid backups) causes this problem to happen at any time afterwards without notice (preceded by random reboot straight into stuck Google screen). I guess new ROMs can cause such issues if there is a large amount of app data deleted everytime, but this is just uninformed speculation.
I've setup Tasker profiles to autorun e2fsck through TWRP every morning before I wake up so I don't have these issues while awake. And one more profile to tell me every 8 hours if my sdcard has changed by a lot.
I hope this is all there is to your phone's problem!
Click to expand...
Click to collapse

Nothing special really.
Was the result Clean after a stuck Google logo?
You could pull battery at the stuck logo and go to TWRP and then check if it is clean. If it is indeed clean, then there's something else wrong that is completely different!

I'm going to give it a go tonight when I get home.
1. So pretty much backup everything, do a complete factory wipe of all data.
2. I'll do a adb push of the .zip for the rom and everything.
3. Flash rom and any other packages needed
4. Run that command see if it comes back clean
5. Reboot go into the rom
6. Reboot, if i get stuck at the Google screen run that script if it's not clean just keep running it?
desktopfusion said:
Nothing special really.
Was the result Clean after a stuck Google logo?
You could pull battery at the stuck logo and go to TWRP and then check if it is clean. If it is indeed clean, then there's something else wrong that is completely different!
Click to expand...
Click to collapse

It's running, it says "clone multiply-claimed blocks? <yes>"
How long does this normally run?
Edit: Running now for 4hrs

GiZiM said:
It's running, it says "clone multiply-claimed blocks? <yes>"
How long does this normally run?
Edit: Running now for 4hrs
Click to expand...
Click to collapse
Hey, sorry.
4 hours?! I've not had it run for more than 2 minutes, ever!
Did you run the -n option and let it say whether there is a corrupt partition? If yes then there may be a problem with the eMMC since its taking so long.
As a last resort, you could go completely stock via fastboot. [Formats /userdata partition, erases SDcard as well - take backup]

Lifesaving string of code.
desktopfusion said:
The only time I get persistent Google screen is when I have a corrupt /userdata partition.
Try running e2fsck on mmcblk0p12 if you have one of those devices that get emmc corruption by changes in sdcard free space.
In case you need more information on this :
1. In TWRP Mount options, unmount Data. The command won't work on mounted partition.
2. In Advanced > Terminal Command, select the /dev/block folder. Then type in
Code:
e2fsck -n mmcblk0p12
("-n" option will cause no changes to your filesystem, it just shows a simulation of the file system correction tool's result.) If the result says the filesystem is "clean", then you have something else to worry about and its not corrupted /userdata.
3. If it starts checking for errors (there's a KILL button while running the command), your filesystem has errors. You can kill it, and then run
Code:
e2fsck -f -C 0 -y mmcblk0p12
(-f is for forced run, -C 0 will give you progress of completion of task, -y will say yes to all prompts (necessary), and mmcblk0p12 is the /userdata partition)
4. Let the command run until you don't see the KILL button. On running
Code:
e2fsck -n mmcblk0p12
again, it must show you a "clean" filesystem.
5. Just reboot to System. If your /userdata was corrupt, running this will mostly solve your problem.
Damn, I wish I had found such instructions to get over my horrendous time with corrupt partitions over six months from November 2012-April 2013.
Click to expand...
Click to collapse
Holy mother of god.
This was a lifesaving string of code. I was convinced that I was going to have to buy a brand new phone. Kudos to you DesktopFusion. Thanks a lot!

Explanation as to why a corrupt userdata partition causes this issue
So, in case anybody was wondering, I would like to explain how I see the issue at hand (corrupt userdata partition).
Upon first boot, the ROM is getting set up and doesn't have any orders to check /userdata because well, there is none on the device. So why waste precious time being redundant (smart coders, right?). So the userdata partition is not checked.
However, now that the second boot is being performed, there is, by default in the system's repertoir, data put in by the user, so the bootloader is told to check the partition containing user data. Since the partition is corrupt, and the free space is technically "modified", it errors up and gets stuck.
I could be wrong, I'm not a developer of any sorts. Just a dude giving my point of view.

I got this trouble too last night. I'm flashing elia's 4.3 custom rom with under 5 gb free space. Got it boot twice,then got stuck at google's logo after trying flashing slim bean gapps. Flashing whole 4.3 stock firmware finally solve this. Maybe there is correlation between upgrading from 4.2.2 without upgrading the bootloader with this problem.
Sent from my Galaxy Nexus using Tapatalk 4

It ended up running for 6hrs and never finished, I did do the -n and it said it was CLEAN but still could not boot into the 4.3 ROM.
So ran it any way for 6hrs and no change as of right now I am unable to boot into ANY 4.3 ROM.
If eMMC was screwed up why can 4.2.2 roms work fine but not 4.3 roms? what's the difference?
desktopfusion said:
Hey, sorry.
4 hours?! I've not had it run for more than 2 minutes, ever!
Did you run the -n option and let it say whether there is a corrupt partition? If yes then there may be a problem with the eMMC since its taking so long.
As a last resort, you could go completely stock via fastboot. [Formats /userdata partition, erases SDcard as well - take backup]
Click to expand...
Click to collapse

BUMP still no 4.3 love

GiZiM said:
BUMP still no 4.3 love
Click to expand...
Click to collapse
Still not resolved?
Have you tried flashing completely stock factory image via fastboot?
Consider checking your flash memory with this app, "eMMC Brickbug Check"
Could you also put in here what Type and Date the eMMC chip was made as per the application?

desktopfusion said:
Still not resolved?
Have you tried flashing completely stock factory image via fastboot?
Consider checking your flash memory with this app, "eMMC Brickbug Check"
Could you also put in here what Type and Date the eMMC chip was made as per the application?
Click to expand...
Click to collapse
Sane chip
Ran memory check no issues
Type: SEM32G
Date: 10/2011
FW: 0x90

GiZiM said:
Sane chip
Ran memory check no issues
Type: SEM32G
Date: 10/2011
FW: 0x90
Click to expand...
Click to collapse
Rats. Falling short of ideas.
I might have missed your answer on whether you've tried flashing a stock Nexus image through fastboot, though.

I had basically the same problem coming from 4.2.2 to 4.3. I'm not sure if it was the bootloader upgrade, 4.3 CM alpha from early August, or the small amount of free space under 5GB, but it was definitely userdata corruption like desktopfusion is saying. I was finally able to fix the problem after a "fastboot -w" userdata and cache*format. This has to be done in fastboot, so hook your computer to your phone in twrp, run "adb pull /sdcard "drive:\pc_backup_location"" to backup your sdcard data (grab what you can if errors come up from badly named or corrupted files). Make sure you got md5verified recovery & bootloader images renamed to recovery.img & bootloader.img, and a rom.zip in your adb folder on the computer. Reboot to bootloader, still connected. **And make sure you're not forgetting any sdcard backup, or twrp backup if still functional, before this erase and format. Run "fastboot -w". Then "fastboot flash recovery recovery.img" and you should be good to reboot, adb transfer ROM.zip and other files to fresh sdcard, etc. There's info on this around to double check, and I just posted a little more detailed walkthrough on this a couple days ago. This definitely saved me though with an identical problem, so if the emmc error check doesn't pan out, I would give this a try. May the fastboot gods be with you.
@desktopfusion -Thanks for your post on the previous page! Copied and saved to mygiant android useful infos text file ... which will one day end up corrupting my userdata partition with my luck.

7175 said:
I had basically the same problem coming from 4.2.2 to 4.3. I'm not sure if it was the bootloader upgrade, 4.3 CM alpha from early August, or the small amount of free space under 5GB, but it was definitely userdata corruption like desktopfusion is saying. I was finally able to fix the problem after a "fastboot -w" userdata and cache*format. This has to be done in fastboot, so hook your computer to your phone in twrp, run "adb pull /sdcard "drive:\pc_backup_location"" to backup your sdcard data (grab what you can if errors come up from badly named or corrupted files). Make sure you got md5verified recovery & bootloader images renamed to recovery.img & bootloader.img, and a rom.zip in your adb folder on the computer. Reboot to bootloader, still connected. **And make sure you're not forgetting any sdcard backup, or twrp backup if still functional, before this erase and format. Run "fastboot -w". Then "fastboot flash recovery recovery.img" and you should be good to reboot, adb transfer ROM.zip and other files to fresh sdcard, etc. There's info on this around to double check, and I just posted a little more detailed walkthrough on this a couple days ago. This definitely saved me though with an identical problem, so if the emmc error check doesn't pan out, I would give this a try. May the fastboot gods be with you.http://forum.xda-developers.com/images/smilies/highfive.gif
@desktopfusion -Thanks for your post on the previous page! Copied and saved to mygiant android useful infos text file ... which will one day end up corrupting my userdata partition with my luck.
Click to expand...
Click to collapse
7175 nailed it. I tried flashing all sorts of different ROMs/gapps/Super SU combinations and tried different wipes/formats to no avail. I wish I would have found the instructions to "fastboot cleanse" the phone 4 or 5 hours ago. I have been reading through forums for several hours today and every suggested fix failed. 7175's fix was spot on for me. My phone was locking up at the Google screen with the lock every time I rebooted after installing a 4.3 ROM.
:highfive:

7175 said:
I had basically the same problem coming from 4.2.2 to 4.3. I'm not sure if it was the bootloader upgrade, 4.3 CM alpha from early August, or the small amount of free space under 5GB, but it was definitely userdata corruption like desktopfusion is saying. I was finally able to fix the problem after a "fastboot -w" userdata and cache*format. This has to be done in fastboot, so hook your computer to your phone in twrp, run "adb pull /sdcard "drive:\pc_backup_location"" to backup your sdcard data (grab what you can if errors come up from badly named or corrupted files). Make sure you got md5verified recovery & bootloader images renamed to recovery.img & bootloader.img, and a rom.zip in your adb folder on the computer. Reboot to bootloader, still connected. **And make sure you're not forgetting any sdcard backup, or twrp backup if still functional, before this erase and format. Run "fastboot -w". Then "fastboot flash recovery recovery.img" and you should be good to reboot, adb transfer ROM.zip and other files to fresh sdcard, etc. There's info on this around to double check, and I just posted a little more detailed walkthrough on this a couple days ago. This definitely saved me though with an identical problem, so if the emmc error check doesn't pan out, I would give this a try. May the fastboot gods be with you.
@desktopfusion -Thanks for your post on the previous page! Copied and saved to mygiant android useful infos text file ... which will one day end up corrupting my userdata partition with my luck.
Click to expand...
Click to collapse
Thanks for this...
First thought it was an issue with SlimRom, tried different kernels, problem wouldn't go away, then realised it was happening with every rom I flashed...

One of the BEST things you can do to Moto Z Play XDA Community (Takes a while! ;) )

EDIT: THE DEVDB PROJECT HAS RISEN UP!
https://forum.xda-developers.com/moto-z-play/development/project-real-unbrick-hard-bricked-moto-t3927107
This is so easy to do, and can be sooo helpful if one day You will end with hard-brick.
If you have any questions send me a private message. :good:
Hey! My name is Jacob and I must tell you that there is one common problem with Moto Z Play - OTA after downgroading results in hardbrick :silly:
I have also bricked my device some days ago, since then I have gathered interesting info, probably all old and not so old blankflash files (these were used in the past to unbrick, but don't work now) and two tools, that allowed me to make proper rawprogram0, patch0 and gpt_main0.bin needed for making files, that will allow everyone to unbrick.
But this can be worth nothing without your help. Problem with unbricking, is that last OTA, updated chip security making unable to flash older chip firmware rendering all flashfiles useless. To make new one, I must get some files that are not present in the internet, but are present in ALL working phones. All I need is full mmcblk0 backup. If you want to help follow these easy-peasy instructions:
INFO: Procedure bellow excludes EFS, MODEMST1, MODEMST2, FSG, BACKUP partitions from backup. These are your phone specific partitions, that contain sensitive information like IMEI, serial numbers etc, but this guide shows how to avoid them while backing up so you don't have to worry about it
Prerequisites:
1. Your phone might be rooted (but doesn't have to be), definitelly should be working and not messed up too much.
2. You must have at least 32 GB micro sd card
3. Any ROM, even custom will be good, but if you have stock, you get +1 point
Steps:
1. If you have TWRP recovery, boot into it and go to step 2.
If you don't have, here is official one https://eu.dl.twrp.me/addison/ - rename it to "twrp.img" and boot to it with
Code:
fastboot boot twrp.img
2. Backup your /data partition and keep it in safe place
3. Format sdcard in ext4 (it is more robust and failsafe) or FAT32/exFAT (if you are on windows).[/URL]
4. Wipe /data on your phone and insert sdcard. Under "Mount" tab in TWRP, check box next to SD-CARD.
5. Open TWRP terminal emulator (It is in advamced tab), type "su" and run these command:
If you trust me that I won't do bad things with your IMEI:
Code:
dd if=/dev/block/mmcblk0 of=/[U][I]"Ext sd location here"[/I][/U]/Loader.img bs=4096
This just makes full-backup of your all partitions from Qualcomm chip.
OR
If you don't trust me:
Code:
dd if=/dev/block/mmcblk0p[B][COLOR="Red"]X[/COLOR][/B] of=/[B][COLOR="DeepSkyBlue"]Y[/COLOR][/B]/mmcblk0p[COLOR="Red"]X[/COLOR] bs=4096
Where X is number of partition from 1 to 54 BUT NOT: 27 (modemst1), 28 (modemst2), 29 (fsg)
and Y is location of your SD-CARD. This will only back up partitions without IMEI, and other phone-specific info.
6 Generated files will be HUGE (~27GB). Copy them to pc and upload to cloud. Maby https://mega.nz/ - probably only they have enough space for that file for free.
7 Post link here or send it to me via Private Message.
8 That's all! If you managed to get here, all comunity is grateful, :highfive: you will be included as biggest contribuor to the new thread I will make in near future!

If I find the time I will throw my old Z Play back to stock and try this. But can take a while before I have that time. Especially uploading that amount of data which would take me at least 12 hours. So if I do that, I will most likely get it into a split archive

Unfortunately I don't have a 32Gb sdcard. If there's another way to do this, I'm willing to help

Camarda said:
Unfortunately I don't have a 32Gb sdcard. If there's another way to do this, I'm willing to help
Click to expand...
Click to collapse
The only other way I know would be a USB C OTG adapter and a USB stick...

Artim_96 said:
If I find the time I will throw my old Z Play back to stock and try this. But can take a while before I have that time. Especially uploading that amount of data which would take me at least 12 hours. So if I do that, I will most likely get it into a split archive
Click to expand...
Click to collapse
Camarda said:
Unfortunately I don't have a 32Gb sdcard. If there's another way to do this, I'm willing to help
Click to expand...
Click to collapse
Thank you very much guys! You don't even know how much did you motivated me to continue research when I got your responses. If you will have any problem, ask me for advice - I will try to help. :highfive:
In case of Artim_96, you probably know this one, but to split dd image, you can use (obviously) "skip" parameter, for example:
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_1.img bs=4096 count=10GB
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_2.img bs=4096 skip=10GB count=10GB
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_3.img bs=4096 skip=20GB count=10GB
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_4.img bs=4096 skip=30GB
In case of Camarda: ...
Code:
adb -d shell su -c busybox dd if=/dev/block/mmcblk0 bs=4096 > D:\mmc.bin
... should do the job, where "D:\mmc.bin" can be any other valid location on your pc.
To make this work, you must have root and busybox installed.

Bobernator said:
In case of Artim_96, you probably know this one, but to split dd image, you can use (obviously) "skip" parameter, for example:
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_1.img bs=4096 count=10GB
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_2.img bs=4096 skip=10GB count=10GB
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_3.img bs=4096 skip=20GB count=10GB
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0_4.img bs=4096 skip=30GB
Click to expand...
Click to collapse
that would be a solution, but I guess it's way easier to create one image, zip it and let it get split to about 5 GB chunks, and probably creating a check sum for each before upload
---------- Post added at 17:02 ---------- Previous post was at 16:56 ----------
but what I don't get: I should make a backup of /data, for what? And then I should connect the phone to my PC, but the following commands look very much like linux commands, so the connection to PC seems unneccessary. Plus, for what reason does the SD Card need to be ext4? the commands should work with exFAT too plus no windows system can read ext4. And there is no program to read it for Windows that's slow as hell

Artim_96 said:
that would be a solution, but I guess it's way easier to create one image, zip it and let it get split to about 5 GB chunks, and probably creating a check sum for each before upload
---------- Post added at 17:02 ---------- Previous post was at 16:56 ----------
but what I don't get: I should make a backup of /data, for what? And then I should connect the phone to my PC, but the following commands look very much like linux commands, so the connection to PC seems unneccessary. Plus, for what reason does the SD Card need to be ext4? the commands should work with exFAT too plus no windows system can read ext4. And there is no program to read it for Windows that's slow as hell
Click to expand...
Click to collapse
Sorry, I was in a bit hurry when I was writing tutorial. I have just corected misteakes in it. :silly:
That part with backing up /data and wiping it is just for Your comfort - You probably don't want to include all you photos, videos contacts etc, in the backup, I am wrong?
EDIT: You are right, solution with splitting archive is clearly better, becouse of smaller size and auto merging archives

Bobernator said:
Sorry, I was in a bit hurry when I was writing tutorial. I have just corected misteakes in it. :silly:
That part with backing up /data and wiping it is just for Your comfort - You probably don't want to include all you photos, videos contacts etc, in the backup, I am wrong?
EDIT: You are right, solution with splitting archive is clearly better, because of smaller size and auto merging archives
Click to expand...
Click to collapse
Would it help you to get /data too? It's my old phone, screen is quite damaged so there is nothing worth looking for on it. Plus it was completely wiped twice by flashing the firmware with flashfile and unlocking the bootloader again since flashing the firmware locked it.

Data partition is absolutely not needed, but thanks for asking!

zip compressing was totally worth it. It went from 29.1 GB to just 2.58 GB?

Artim_96 said:
zip compressing was totally worth it. It went from 29.1 GB to just 2.58 GB?
Click to expand...
Click to collapse
Thanks for support!
@Camarda - You are from Brasil, so you probably have different version of software, so if you will upload it, phones outside of Europe can be safed too. Do you still want to help?

Bobernator said:
Thanks for support!
@Camarda - You are from Brasil, so you probably have different version of software, so if you will upload it, phones outside of Europe can be safed too. Do you still want to help?
Click to expand...
Click to collapse
I just sent you the file, tell me if everything is ok

Thank you! Artim's backup is not working on my phone, and I suddenly realised that my exam ending my school are in less than month (!), so I didn't have time neither to write a thread, nor to reverse engineer the file, but I will try to find time and test your backup!
Ps. Don't worry about me beeing temporiarly inactive, this thread is my current target and I won't give up!

Bobernator said:
Thank you! Artim's backup is not working on my phone, and I suddenly realised that my exam ending my school are in less than month (!), so I didn't have time neither to write a thread, nor to reverse engineer the file, but I will try to find time and test your backup!
Ps. Don't worry about me beeing temporiarly inactive, this thread is my current target and I won't give up!
Click to expand...
Click to collapse
Bobernator, I'm just posting to let you know that I am very thankful for your efforts and to take as long as you need. I have a LATAM XT1635-02 that got bricked by an automatic update quite a few months ago. It's in fastboot state. If there is anything I can do to help, let me know.
I now own a XT1710-06, so if you think the files from it could be useful, let me know.

Welcome again! My exams have just ended (I hope they went well) I am temporally at my uncle's house so I don't have access to files and info I've gathered, but I will return to home at friday and even Easter will not stop me, becouse I have decided to start DevXDA project!
Stay with me guys

Fulcano said:
Bobernator, I'm just posting to let you know that I am very thankful for your efforts and to take as long as you need. I have a LATAM XT1635-02 that got bricked by an automatic update quite a few months ago. It's in fastboot state. If there is anything I can do to help, let me know.
I now own a XT1710-06, so if you think the files from it could be useful, let me know.
Click to expand...
Click to collapse
I think I you can easly fix your phone, since fastboot works. You will need factory update zip, it is pinned somewhere in this forum, but if you feel unsure (you can brick phone even harder with this method if it goes wrong), I can assist you during the weekend and share a link with correct zip.
And thanks for support!
Device which you have is Moto Z2 Play (albus) that have next version of the chip in Moto Z Play (addison). My plan is to fix addison by combining some of the firmware from it and albus, but these files are available freely and you don't need to send them.

Bobernator said:
I think I you can easly fix your phone, since fastboot works. You will need factory update zip, it is pinned somewhere in this forum, but if you feel unsure (you can brick phone even harder with this method if it goes wrong), I can assist you during the weekend and share a link with correct zip.
And thanks for support!
Device which you have is Moto Z2 Play (albus) that have next version of the chip in Moto Z Play (addison). My plan is to fix addison by combining some of the firmware from it and albus, but these files are available freely and you don't need to send them.
Click to expand...
Click to collapse
Thanks for the reply! Sorry, i've been quite busy with exams as well.
It's been a while since the phone is bricked, and i think fastboot was the wrong word. When it is plugged in it appears as a qualcomm device and the LED blinks, but other than that the phone does absolutely nothing. I remember being unable to unbrick it because of needing a `programmer.pem` file specific to the version of android that was installed.
The phone had an unlocked bootloader, twrp and supersu. It got stuck during an OEM update from 7.1.1 (i think) to 8.0.0. It was stuck for over four hours, I turned it off by force and then it never turned on again .
With regards to the Moto Z2 files, that's fantastic to hear. If there's anything else I can do to help, please say so. I've configured email alerts now so i'll get notified when you reply .
Thanks for the effort!