Related
hi guys,
system win7x64, moto g retail uk
in order to root i unlocked the bootloader from motorola page. successfully unlocked and rooted but...
problem nr 1 - from that day i was unable to access recovery by any means. every time i accessed it the withe screen with the motorola warning after unlocking came and nothing happened. i discovered this thread forum.xda-developers.com/showthread.php?t=2585755 and was able to change the boot logo from that screen to a regular one, but the problem persisted. tried to solve the problem and came to this thread forum.developers.com/showthread.php?t=2037808. "There's a file in /system/etc/ called install_recovery.sh that may need to be deleted for the custom recovery to stick. You need root to remove it."
converted that install_recovery.sh to bak and rebooted.
problem nr 2 - no access to recovery. lost root privileges. no acess to bootloader. the phone does a full reboot everytime (goes on reding every android app).
tried to upload an new "install_recovery.sh" (the same but renamed) but have no privileges through airdroid.
any suggestions highly appreciated. can i push the file through adb or sanything else?
after opening /system/etc/install-recovery.sh with notepad it reads like this. i guess it was changing the name from .sh to .bak that broke rooting
#!/system/bin/sh
# If you're implementing this in a custom kernel/firmware,
# I suggest you use a different script name, and add a service
# to launch it from init.rc
# Launches SuperSU in daemon mode only on Android 4.3+.
# Nothing will happen on 4.2.x or older, unless SELinux+Enforcing.
# If you want to force loading the daemon, use "--daemon" instead
/system/xbin/daemonsu --auto-daemon &
# Some apps like to run stuff from this script as well, that will
# obviously break root - in your code, just search this file
# for "install-recovery-2.sh", and if present, write there instead.
/system/etc/install-recovery-2.sh
install-recovery.sh is altered by superSU. You lost root as this file is required for root.
The original file does flash stock recovery on boot (or at least after an OTA AFAIK)
Sounds to me like your original problem of not accessing recovery was maybe due to you using the power button to select recovery option in bootloader rather than volume UP which is the button used to select an option.
No idea why you can't now get to the bootloader at all, just renaming that file would not cause that. I guess altering the boot logo has caused an unknown issue somehow.
Putting back the install-recovery.sh file won't help at all with not being able to boot to bootloader. In actual fact I find it hard to believe you can't get to the bootloader, as if the bootloader was messed up you wouldn't even be able to boot the phone.
Anyway - without root the only way to get the file back in place is to flash the file (ie as a flashable zip) from custom recovery AFAIK. ADB won't work as you can't push a file to /system without using 'insecure ADB' which needs a rooted device.
Maybe search XDA and see if there is some other key combination to access bootloader.
scott_doyland said:
install-recovery.sh is altered by superSU. You lost root as this file is required for root. RIGHT! I altered its extension to .bak, rebooted and lost root access
The original file does flash stock recovery on boot (or at least after an OTA AFAIK)
Sounds to me like your original problem of not accessing recovery was maybe due to you using the power button to select recovery option in bootloader rather than volume UP which is the button used to select an option. Really dont know if that was the mistake. I lost recovery access (but not bootloader) immediately after unlocking the bootloader, when i saw the screen turning blue/violet i took the usb cable and it might have been the mistake.
No idea why you can't now get to the bootloader at all, just renaming that file would not cause that. I guess altering the boot logo has caused an unknown issue somehow. I altered the boot logo because everytime i tried to acess recovery the phone gave me the motorola warning and didn't go to recovery, just booted, after altering the logo the behaviour stayed the same, no recovery, juts normal booting.
Putting back the install-recovery.sh file won't help at all with not being able to boot to bootloader. In actual fact I find it hard to believe you can't get to the bootloader, as if the bootloader was messed up you wouldn't even be able to boot the phone. Yes, no bootloader by any means, the phoe just cold boots and checks every app (it takes a lot of time)
Anyway - without root the only way to get the file back in place is to flash from custom recovery AFAIK. ADB won't work as you can't push a file to /system without using 'insecure ADB' which needs a rooted device.
Click to expand...
Click to collapse
Right. Already tried different forms of adb (mount, remount, su, push, but NADA). Didint go for the custom recovery because i'm noob and dunno what it is (yet) but i'll try to find out. If you can guide me i any direction i really appreciate :good:
Despite all this mess, at least i hope this knowledge serves the community.
If you can't access bootloader and no longer rooted I don't think you are going to be able to flash a custom recovery anyway (custom recovery allows you to backup/restore entire device and flash ROMS).
Without bootloader access you are in a mess as can't access recovery and can't root.
You can't even reflash entire stock ROM inc recovery etc.
Basically unless you get bootloader access you are screwed AFAIK.
Hopefully someone else may have an idea.
As I mentioned before - search XDA and see if there are some button combos that may get you to bootloader rather than normal combos. Or any button combos to hard reset bootloader etc. It doesn't look good though.
screwed is the word scott. at least its a "normal phone", for now, it works normally, the only drag is the slow booting everytime i shut it down, oh and it doesnt shutdown, just reboots
scott
i have bootloader again, dontt know how but i do. can you point me how to root the phone again?
Have a read through this link, my posts in it should explain what to do
http://forum.xda-developers.com/showthread.php?t=2612195
scott_doyland said:
Have a read through this link, my posts in it should explain what to do
http://forum.xda-developers.com/showthread.php?t=2612195
Click to expand...
Click to collapse
Thanks Scott.
The situation got a little worse. Now SO (w7x64 and x32 i have both) do not recognize moto g. I connect usb cable and it only charges.
- if i connect it while off it reboots (every time rebuilds dalvik cache)
- if i connect it while on it only charges but windows doesn't make any sound (nothing at device manager)
- if i connect usb cable (while in bootloder screen) windows recognizes it only as android adb but not as media player (drivers installed). when i do 'adb devices' nothing comes although the phone says usb connected.
at settings i have USB-MTP, USB debugging enabled.
i can power off and acess bootloader screen but at that screen if i choose any option it just cold reboots. no recovery acess, nada! no adb acess.
In bootloader ADB doesn't work by design. Its fastboot you need.
So do in bootloader
fastboot devices
When booted to android AND if you turn on USB debugging in dev options you can do
adb devices
So one you have 'fastboot devices' working, ie PC recognizes device, then you are OK as if need be you can even download and flash complete stock images for everything inc /system, recovery etc to get it back to how it was out of the box.
scott_doyland said:
In bootloader ADB doesn't work by design. Its fastboot you need.
So do in bootloader
fastboot devices
When booted to android AND if you turn on USB debugging in dev options you can do
adb devices
So one you have 'fastboot devices' working, ie PC recognizes device, then you are OK as if need be you can even download and flash complete stock images for everything inc /system, recovery etc to get it back to how it was out of the box.
Click to expand...
Click to collapse
It was a good tip Scott, it kept me walking and this morning i was about to give up :good:
Below you can see what happened. I flashed cwm (for 4.4.2) successfully but when trying to access it phone cold reboots as usual. Is it because i don't have root access or its just problem with the 4.4.2 bootloader after unlocking it?
...\root motorola>fastboot devices
TA8830L7VY fastboot
...\root motorola>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (7604 KB)...
OKAY [ 0.266s]
writing 'recovery'...
OKAY [ 0.461s]
finished. total time: 0.728s
>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.267s]
booting...
OKAY [ 0.504s]
finished. total time: 0.772s After this it does a cold reboot
you said i could re-flash a stock image. the phone came with 4.3 but in the meanwhile upgraded to 4.4.2. can i flash 4.3 after having unlocked the bootloader and updated to 4.4.2?. i managed to download both firmwares.
Having read that 4.4.2 bootloader is having trouble with accessing recovery (my case also) i tried to upload 4.3 bootloader. this was the result
...>fastboot-moto-windows.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1940 KB)...
OKAY [ 0.095s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.836s]
finished. total time: 1.934s
...>fastboot-moto-windows.exe reboot-
bootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
i guess everything went right. the phone didnt a cold reboot and went right away to the bootloader. after selecting recovery in this new bootloader i finally managed to have acess to the last CWM 6.0.4.6 recovery. UFFFF!!!
After that i did a wipe cache partition and rebooted. Phone did a cold reboot. after that i follwed the post you mentioned and flashed SUper SU.through CWM
As seen before after renaming install-recovery.sh to .bak root was lost I checked and the file is there again along with the bak so i guess super su created it again.
Check list: Have bootloader. have recovery. have root, i'm on 4.4.2 with 4.3 bootloader. one thing thats not ok, everytime phone reboots android goes on with the following message "android is upgrading --- optimising app x of y" which takes a lot of time. even if i ask for a fast reboot. that was not the usual procedure, the phone just did a fast reboot and nothing more. any advice on this one?
What a enormous trip for someone that didnt knew much about this. Kudos to you for keeping the help!
Sounds like its pretty OK then apart from the 'android is upgrading' message. I would wipe dalvik cache from CWM. Im not 100% sure but I *think* 'android is upgrading' indicates its rebuilding the dalvik cache, although as I say Im not sure. Anyway wiping dalvik cache wont hurt. I'd wipe, reboot and you *may* still get the messages on first reboot, once all complete and phone is fully operational then reboot again and see if messages are gone.
You said you already wiped cache via CWM but may as well wipe that again as well.
If you still get the error go to 'settings/storage and click on 'cached data' and chose to wipe it (this is different from a cache wipe in CWM).
If messages still happen them Im afraid I dont know what else to do (factory reset of course is last resort).
To attempt to answer your other questions:
***************
** can i flash 4.3 after having unlocked the bootloader and updated to 4.4.2? **
I think so, if you have the entire firmware it includes recovery, bootlloader, android, radio images, kernel etc so flashing it in the correct sequence as can be found in other threads should give you complete 4.3 as it was out of the box. However please read other posts related to this as its not something I have done or have read much about.
If you have an entire 4.4.2 firmware (rather than just a 4.4.2 update) then same applies as above, ie flashing it will give you 4.4.2 entirely inc bootloader, recovery etc.
***************
Re bootloaders and recoveries - I havet followed the threads much regarding 4.4.2 and recoveries as its not that relevant to me right now but if 4.3 bootloader is working, ie you can get to recovery etc, I'd be inclined to stick with it.
fastboot boot recovery.img - all this does it boot the recovery.img direct from your PC, works for some people and not others - dont know why. Its not actually booting CWM from your phone.
When on 4.4.2 bootloader after flashing CWM (the 4.4.2 one I assume) did you try booting the recovery that was actually on the phone, eg booting up android then using ADB to issue
adb reboot recovery
OR just try selecting recovery from bootloader using VOL UP
or did you just 'fastboot boot recovery.img'
However as you have CWM on 4.3 bootloader and its working its irrelevant really, was just interested.
** Is it because i don't have root access or its just problem with the 4.4.2 bootloader after unlocking it? **
root and/or unlocked bootloader makes no difference to booting into recovery. Booting into recovery should work, Im assuming you did a 'fastboot boot recovery.img' and this is what failed (as I said just above) as opposed to actually booting into the recovery on the phone itself?
Hope the above makes some sense. And I hope wiping dalvik cache etc does the trick.
If you get any other 'funnies' I'd personally install 4.3 images entirely so its out of the box stock and start from there, ie flash 4.3, allow kitkat to do OTA, then flash CWM for 4.4.2 and hope it works, then root.
If CWM for 4.4.2 doesnt work then downgrade bootloader and flash CWM then root.
Im a bit OCD about these things so I'd probably start from scratch anyway to ensure its all 100% nice and clean but thats up to you
Good morning Steve, thanks for your helpful info, once again.
scott_doyland said:
Sounds like its pretty OK then apart from the 'android is upgrading' message. I would wipe dalvik cache from CWM. Im not 100% sure but I *think* 'android is upgrading' indicates its rebuilding the dalvik cache, although as I say Im not sure. Anyway wiping dalvik cache wont hurt. I'd wipe, reboot and you *may* still get the messages on first reboot, once all complete and phone is fully operational then reboot again and see if messages are gone. Again, the same messages.
You said you already wiped cache via CWM but may as well wipe that again as well.
At CWMR there's also these options besides dalvik cache, a) wipe data/factory reset and wipe cache partition. factory reset is pretty obvious, it cleans all your data but does not fully restore 4.4.2 functionality (or does it? and it goes back to 4.3). Wipe cache partition is the same as settings/storgae/cached data?
If you still get the error go to 'settings/storage and click on 'cached data' and chose to wipe it (this is different from a cache wipe in CWM).
If messages still happen them Im afraid I dont know what else to do (factory reset of course is last resort). Does it go back to 4.3?
To attempt to answer your other questions:
***************
If you have an entire 4.4.2 firmware (rather than just a 4.4.2 update) then same applies as above, ie flashing it will give you 4.4.2 entirely inc bootloader, recovery etc. It might not be "entire". What i have 4.3 is 400MB, 4.4.2 is 180 MB, might be an upgrade.
***************
Re bootloaders and recoveries - I havet followed the threads much regarding 4.4.2 and recoveries as its not that relevant to me right now but if 4.3 bootloader is working, ie you can get to recovery etc, I'd be inclined to stick with it.
fastboot boot recovery.img - all this does it boot the recovery.img direct from your PC, works for some people and not others - dont know why. Its not actually booting CWM from your phone. it didint in 4.4.2, now it does.
When on 4.4.2 bootloader after flashing CWM (the 4.4.2 one I assume) did you try booting the recovery that was actually on the phone, eg booting up android then using ADB to issue. I did, but without sucess.
adb reboot recovery
OR just try selecting recovery from bootloader using VOL UP
or did you just 'fastboot boot recovery.img'
However as you have CWM on 4.3 bootloader and its working its irrelevant really, was just interested.
** Is it because i don't have root access or its just problem with the 4.4.2 bootloader after unlocking it? **
root and/or unlocked bootloader makes no difference to booting into recovery. Booting into recovery should work, Im assuming you did a 'fastboot boot recovery.img' and this is what failed (as I said just above) as opposed to actually booting into the recovery on the phone itself? Both things failed, the phone just rebooted.
Hope the above makes some sense. And I hope wiping dalvik cache etc does the trick. it did not.
If you get any other 'funnies' I'd personally install 4.3 images entirely so its out of the box stock and start from there, ie flash 4.3, allow kitkat to do OTA, then flash CWM for 4.4.2 and hope it works, then root. I probably will take that road.
If CWM for 4.4.2 doesnt work then downgrade bootloader and flash CWM then root. Yes, at least i know that works.
Im a bit OCD about these things so I'd probably start from scratch anyway to ensure its all 100% nice and clean but thats up to you
Click to expand...
Click to collapse
In brief: Rebooting problem persists even when wiping dalvik cache twice. Now the device is not recognized in windows. Neither on desktop pc w7x64 nor laptop w7x32. have motorola drivers on both. It used to recognize device as mtp (media player xt1032) but not anymore. When connected in bootloader device manager recognizes as android adb. I feel the problem is from the phone and not SO. I'll try to fix it this morning.
If i reflash 4.3 do i have to do anything before? Wipe something? Do a nandroid backup? Do a normal backup? I have a few backup apps but never used any of them.
Great appreciation for your help Steve. Have a nice Sunday.
About the phone not being recognized as mtp, after a brief search it has to do with locking. If it's locked then windows explorer is denied any access for security reasons. As soon as i unlocked it windows recognized the device immediately. -1 problem. only the rebooting stuff now.
:good:
rebooting ptoblem
wyped dalvik and cache data several times
also wiped odex files
fixed permissions in rom manager
behaviour persists. after wiping, the phone goes "upgrading android - optimising 225 apps" after that when rebooting the phone goes "android is upgrading... - optimising 103 apps". factory reset as last resort sigh... i hate that :crying:
I am having the same issue with the phone being boot loader unlocked and when I try to get into recovery through fastboot it just reboots.
Do you have the stock files that you used along the way?
Thanks. I have never had a phone give me this much hassle before ??:'(
Hi!
So my Nexus 5 ran into a problem. In the morning it worked fine and I shut it off when I came to school. When I tried powering it back on it showed the PIN entry screen but soon shut off. I tried turning it back on for a couple of times and it showed just that boot animation with color circles. But every once in a while the screen turned white and then continued with the animation. It looked like it was missing a frame or something. Now it just won't boot to Android. It shows the Google logo but it stays there. If it is unplugged it will shut off soon, but if it is connected to my computer it is just stuck there.
I can access TWRP 2.6.3.4 I have on my phone through fastboot but that's kinda it. I searched for a while and found the best thing to do is to restore the phone. But first I want to do a backup (I don't have any, but I will have them from now on). I have some photos on my phone I want to keep. Here comes the next problem: I am unable to do a backup. When I tap backup in TWRP I have checked System, Data and Boot. I slide to back up but it shows some errors:
Updating partition details...
E: Unable to open '/cache/recovery/.version
Updating partition details...
E: Unable to mount '/system'
E: Unable to mount '/persist'
E: Unable to mount '/firmware'
E: Unable to mount '/system'
* Total number of partitions to back up: 3
* Total size of all data: 2651MB
* Availible space: 14544MB
[BACKUP STARTED]
* Backup Folder: /data/media/0/TWRP/BACKUPS/04
E: Unable to create folder: /data/media/0/TWRP
E: Failed to make backup folder.
The last three lines, except the last one are cut off (I think). If I tap on reboot system shown under this windows it asks me if I want to install Super-SU as if I wasn't rooted. It says so.
So, what to do? I want to keep everything the same (settings, apps, photos...) I have music on my computer so I don't need to back it up. Is that possible? What seems to be the problem?
I am running Android 4.4.2 Kitkat on my Nexus 5 32gb from Canada. I live in Europe and my uncle from Canada bought it, so warranty is no good for me.
First of all clear cache/dalvic cache and try rebooting the phone and see whether OS is booted or not. If that doesn't help, flash the lastet Philz touch recovery and see whether the partitions are being mounted or not...
Since you're able to get to the bootloader, it's a soft brick.. .
Ok, thanks... I am pretty new to android I have no idea how to clear cache. Do I go to wipe then to advanced wipe and check cache and dalvik cache and wipe it so? What if I also clear data? Does that delete everything on my phone?
Edit: So I did that. It says wipe was successful. Here is the log:
Updating partition details...
E: Unable to open '/cache/recovery/.version'
Wiping Dalvik Cache Directories...
Cleaned: /data/dalvik-cache...
-- Dalvik Cache Directories Wipe Complete!
Formatting Cache using make_ext4fs function.
E: Unable to mount '/cache'
Updating partition details...
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount '/persist'
E: Unable to mount '/firmware'
My phone still only shows the Google screen and turns off soon (10 seconds or so). What is that Philz thingy?
hofko said:
Ok, thanks... I am pretty new to android I have no idea how to clear cache. Do I go to wipe then to advanced wipe and check cache and dalvik cache and wipe it so? What if I also clear data? Does that delete everything on my phone?
Click to expand...
Click to collapse
Go to mount and check the cache and data. Then go to Wipe>advanced wipe>dalvik cache and cache
and if u clear data it will clear the apps but not what is in the internal memory.
Edit- do as @rootSU is saying.
Sometimes a simple fastboot flash cache.img fixes it
Sent from my Nexus 5 using Tapatalk
rootSU said:
Sometimes a simple fastboot flash cache.img fixes it
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
So, how do I do that? I tried googling it for a bit and I find everything a bit confusing. I want to be sure what am I doing with my phone when it is in this state.
Edit: I tried what varuntis1993 said and it showed that boot animation and shut off. It did that only once. I don't know.
@hofko this thread may help.
hofko said:
So, how do I do that?
Click to expand...
Click to collapse
If you're rooted, you should already know how to do this as you use fastboot during the rooting process.
Read the stickies in general and q&a. Together they contain all the information you need
Sent from my Nexus 5 using Tapatalk
Ok, I want through those threads and found out how to flash cache.img. But my phone is still not working. The first time it showed the boot animation with some white lines going through the screen sometimes as I described earlier. It shut off soon. Now it shows the boot animation for a bit, gets stuck on it and shuts off after a while.
When flashing it shows this:
erasing 'cache'
OKAY [ 0.480s]
sending 'cache' (133348 KB)...
OKAY [ 0.751s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 45.242s
Is there anything else I can do? Can I just get the pictures off my phone and install stock KitKat on it?
hofko said:
Ok, I want through those threads and found out how to flash cache.img. But my phone is still not working. The first time it showed the boot animation with some white lines going through the screen sometimes as I described earlier. It shut off soon. Now it shows the boot animation for a bit, gets stuck on it and shuts off after a while.
When flashing it shows this:
erasing 'cache'
OKAY [ 0.480s]
sending 'cache' (133348 KB)...
OKAY [ 0.751s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 45.242s
Is there anything else I can do? Can I just get the pictures off my phone and install stock KitKat on it?
Click to expand...
Click to collapse
can u access ur internal memory using the file manager of twrp?
Try using adb pull
or u can also use an otg cable and copy and paste the folder to usb.
hofko said:
Ok, I want through those threads and found out how to flash cache.img. But my phone is still not working. The first time it showed the boot animation with some white lines going through the screen sometimes as I described earlier. It shut off soon. Now it shows the boot animation for a bit, gets stuck on it and shuts off after a while.
When flashing it shows this:
erasing 'cache'
OKAY [ 0.480s]
sending 'cache' (133348 KB)...
OKAY [ 0.751s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 45.242s
Is there anything else I can do? Can I just get the pictures off my phone and install stock KitKat on it?
Click to expand...
Click to collapse
It is a dead flashchip. RMA it.
Tapatalk-kal küldve az én Nexus 5-el
bitdomo said:
It is a dead flashchip. RMA it.
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
Oh noo... Really??? I can't RMA it, I got it from Canada and I'm from Europe.
hofko said:
Oh noo... Really??? I can't RMA it, I got it from Canada and I'm from Europe.
Click to expand...
Click to collapse
Have you used toolkit for rooting? Because it's always better to root it manually using fastboot commands than using toolkits.
Also try this tutorial but I highly doubt if its will work for you
http://forum.xda-developers.com/showthread.php?t=2577447
hofko said:
Oh noo... Really??? I can't RMA it, I got it from Canada and I'm from Europe.
Click to expand...
Click to collapse
FAILED (remote: flash write failure)
I'm afraid this means that the flashchip has died. You could try flashing a new custom rom and see whether it boots or not, but I have my doubts.
Give it a few tries and in the mean time find a place where they repair the parts. If you give it to LG/google, they will most probably charge you for the whole mobo/battery which means you're better off buying a new device.
Now I really do think there's something wrong.with the chip. When I tried to adb pull it some pictures it gave me this message:
failed to copy: '/sdcard/DCIM/Camera' to 'C:/Users/.../Photos': I/O Error.
Is this what I think it is?
But I can find the actual pictures in the storage of the phone in twrp file manager. So...
hofko said:
Now I really do think there's something wrong.with the chip. When I tried to adb pull it some pictures it gave me this message:
failed to copy: '/sdcard/DCIM/Camera' to 'C:/Users/.../Photos': I/O Error.
Is this what I think it is?
But I can find the actual pictures in the storage of the phone in twrp file manager. So...
Click to expand...
Click to collapse
U said some of the files, so were some files copied?
No. None.
I am now trying to just flash stock Android using this guide http://www.droidviews.com/how-to-restoreunroot-nexus-5-by-flashing-factory-images/
When flashing the boot.img and system.img I got the same error I had before: FAILED (remote write failure). Everything else seemed okay. Now I am doing step 10 on the guide which is erasing the cache. This has been going on for quite some time and I presume I should just leave it do it's job as some people had some issues when ending this processby force.
What to do? I am getting a bit panicky.
hofko said:
Now I really do think there's something wrong.with the chip. When I tried to adb pull it some pictures it gave me this message:
failed to copy: '/sdcard/DCIM/Camera' to 'C:/Users/.../Photos': I/O Error.
Is this what I think it is?
But I can find the actual pictures in the storage of the phone in twrp file manager. So...
Click to expand...
Click to collapse
Whatt???? That's great.
How about you start from scratch? does you device come up with adb devices ?
Is Platform-tools and usb driver correctly installed?
Since you can access storage from recovery, why don't you download a custom rom and transfer the rom to your device via OTG cable and flash it?
You can even backup your data using the OTG cable!
Post it to Canada and ask your Uncle to RMA it.
vin4yak said:
Whatt???? That's great.
How about you start from scratch? does you device come up with adb devices ?
Is Platform-tools and usb driver correctly installed?
Since you can access storage from recovery, why don't you download a custom rom and transfer the rom to your device via OTG cable and flash it?
You can even backup your data using the OTG cable!
Click to expand...
Click to collapse
Well I can try starting from scratch, but my Nexus has been erasing cache for almost an hour. Can I just stop that?
My OTG cable just doesn't work for some reason. I works on my Nexus 7 2012 version.
I am already in the process of reinstalling stock android so i don't really know if I even have twrp installed now...
rootSU said:
Post it to Canada and ask your Uncle to RMA it.
Click to expand...
Click to collapse
Will they do that? I mean I have unlocked bootloader and a rooted phone...
Hi,
My phone started to fail and give me a lot of errors that it was stopping initiator, android.process.acore, etc... and got stuck in this errors, having to accept the error dialogs all the time and being impossible to make anything with it.
I tried to reset my moto G and wipe all user data. I entered fastboot mode (couldn't do it form phone normal menu) and made a factory reset. No changes after reboot.
Then I tried to reinstall firmware. I've made all the steps in several tutorials found here. The bootloader is unlocked, I put the last firmware , entered recovery mode and ask for wipe/reset user data, but when the phone reboots, there are no changes: I have again the personalized screen image and the gesture blocking, as if the user data remains there, and all the errors.
Is there any way to erase all user data and leave the phone as the first day? Am I making something wrong or need to make something more?
Thanks in advance
Sounds like you might have encrypted it?
BobbaLouie said:
Sounds like you might have encrypted it?
Click to expand...
Click to collapse
Not consciously, the phone had normal use....
If it was encrypted you'd have to enter a password before it even got to the boot logo, so it would be very obvious.
BobbaLouie said:
If it was encrypted you'd have to enter a password before it even got to the boot logo, so it would be very obvious.
Click to expand...
Click to collapse
Then, it is not encrypted.
thanks
Jorge BCN said:
Hi,
My phone started to fail and give me a lot of errors that it was stopping initiator, android.process.acore, etc... and got stuck in this errors, having to accept the error dialogs all the time and being impossible to make anything with it.
I tried to reset my moto G and wipe all user data. I entered fastboot mode (couldn't do it form phone normal menu) and made a factory reset. No changes after reboot.
Then I tried to reinstall firmware. I've made all the steps in several tutorials found here. The bootloader is unlocked, I put the last firmware , entered recovery mode and ask for wipe/reset user data, but when the phone reboots, there are no changes: I have again the personalized screen image and the gesture blocking, as if the user data remains there, and all the errors.
Is there any way to erase all user data and leave the phone as the first day? Am I making something wrong or need to make something more?
Thanks in advance
Click to expand...
Click to collapse
Are you rooted? If so, you might have to FORMAT your phone, which will erase even your storage. I used TWRP and my phone just factory reset after I formatted. I think there must've been some sort of corruption.
Jorge BCN said:
Hi,
My phone started to fail and give me a lot of errors that it was stopping initiator, android.process.acore, etc... and got stuck in this errors, having to accept the error dialogs all the time and being impossible to make anything with it.
I tried to reset my moto G and wipe all user data. I entered fastboot mode (couldn't do it form phone normal menu) and made a factory reset. No changes after reboot.
Then I tried to reinstall firmware. I've made all the steps in several tutorials found here. The bootloader is unlocked, I put the last firmware , entered recovery mode and ask for wipe/reset user data, but when the phone reboots, there are no changes: I have again the personalized screen image and the gesture blocking, as if the user data remains there, and all the errors.
Is there any way to erase all user data and leave the phone as the first day? Am I making something wrong or need to make something more?
Thanks in advance
Click to expand...
Click to collapse
Try clearing data,cache,dalvik cache and reflashing the ROM..if all fails try to clear data and flash the stock ROM through fastboot mode.
KVCmoto said:
Try clearing data,cache,dalvik cache and reflashing the ROM..if all fails try to clear data and flash the stock ROM through fastboot mode.
Click to expand...
Click to collapse
I've made it all, but when reboot, there is the same data there....
Neither can't root the phone, when I make adb sideload supersu.zip, I receive a installation aborted error after verification of the file....
Any Ideas?
Thanks in advance
Jorge BCN said:
I've made it all, but when reboot, there is the same data there....
Neither can't root the phone, when I make adb sideload supersu.zip, I receive a installation aborted error after verification of the file....
Any Ideas?
Thanks in advance
Click to expand...
Click to collapse
Flash the stock ROM once more through boot loader http://forum.xda-developers.com/showthread.php?t=2542219
If you have TWRP installed and your data backed up, I would highly suggest formatting your phone. My phone was having heaps of trouble, including random reboots, the inability for factory data reset, it was slow, having wake time issues, all sorts of shiz. One reformat and it was all better.
MoseIlla said:
If you have TWRP installed and your data backed up, I would highly suggest formatting your phone. My phone was having heaps of trouble, including random reboots, the inability for factory data reset, it was slow, having wake time issues, all sorts of shiz. One reformat and it was all better.
Click to expand...
Click to collapse
What do you mean with reformat? I can't boot into other recovery than stock, and it doesn't allow me erase user data, thats the problem.
When I try to flash other recovery (TWRP, Philz,..) it seems that has been flashed ok but when go to recovery from bootloader menu I have the old stock recovery menu...
Thanks in advance
Jorge BCN said:
What do you mean with reformat? I can't boot into other recovery than stock, and it doesn't allow me erase user data, thats the problem.
When I try to flash other recovery (TWRP, Philz,..) it seems that has been flashed ok but when go to recovery from bootloader menu I have the old stock recovery menu...
Thanks in advance
Click to expand...
Click to collapse
You unlocked the bootloader then, yes? How's your ROM behaving?
MoseIlla said:
You unlocked the bootloader then, yes? How's your ROM behaving?
Click to expand...
Click to collapse
Can you be more explicit?
Are you using the special mfastboot or the generic fastboot executable from the Android SDK?
Execute these commands with the phone in fastboot (bootloader menu):
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
liveroy said:
Are you using the special mfastboot or the generic fastboot executable from the Android SDK?
Execute these commands with the phone in fastboot (bootloader menu):
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Click to expand...
Click to collapse
Hi, the same after rebooting, I have all my user data... (I'm using mfastboot for OSX, but the same result with fastboot under Darwin subfolder of stock firmware)
no errors executing it, no errors in the phone, but no effect in phone user data
$ ./mfastboot erase cache
erasing 'cache'...
OKAY [ 0.017s]
finished. total time: 0.017s
$ ./mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.018s]
finished. total time: 0.019s
$ ./mfastboot reboot
Jorge BCN said:
Can you be more explicit?
Click to expand...
Click to collapse
I just reread your first post. When did your phone start giving you errors? Did you install any new apps, did you let it die completely? The errors had to have started somewhere. Perhaps we can undo a bit of the damage that lead to this and get you back to a somewhat usable state if we have that information.
MoseIlla said:
I just reread your first post. When did your phone start giving you errors? Did you install any new apps, did you let it die completely? The errors had to have started somewhere.
Click to expand...
Click to collapse
No idea. There was not anything special or new app. A month ago it started to give errors. Sometimes I can get 1 or 2 minutes working without errors, but can't delete user data or reset from phone menu (no result when touch the button).
Thanks
Jorge BCN said:
No idea. There was not anything special or new app. A month ago it started to give errors. Sometimes I can get 1 or 2 minutes working without errors, but can't delete user data or reset from phone menu (no result when touch the button).
Thanks
Click to expand...
Click to collapse
Does this coincide with a firmware update (Like Android 4.4.2 to 4.4.3)?
MoseIlla said:
Does this coincide with a firmware update (Like Android 4.4.2 to 4.4.3)?
Click to expand...
Click to collapse
Nopes, as far as I know
Here's what I know about the issue, perhaps it will give someone else an idea:
1. The issue is either caused by or is unaffected by previous factory resets.
2. The issue is either caused by or is unaffected by the installation of new and/or updated ROMs.
3. If it's the same issue I was having, and I believe that it least shares the same root cause, then it is something that gets worse over time; it causes system instability (system UI crashes in increasing number, random reboots, etc...), slowness, and refuses to allow you to hard reset after a while.
4. In the case that it is the same issue, it has different effects on different methods of factory resets. In TWRP the factory reset process just continues on forever, until you hard reboot the device or until the battery drains out. If you press the factory reset button in fastboot it just resets to system, making no changes.
5. In TWRP I used the reformat option and have since had no issues, including better than new performance with crDroid.
Based on my understanding of the Moto G partition tables, I believe that the issue may have to do with gradual data corruption, possibly on the storage partition. This may be because of a software bug in the firmware or maybe a hardware issue. Due to the ubiquity of the lock up/reboot issue, which is well documented and has several guides indicating that a factory reset is in order when this occurs, I'm thinking that it is safe to assume that some resource shared both with the system and storage partitions is to blame.
If that is the case, then I would think it's the cache or a bug with an updated system app that leaves traces in the device storage.
This is all assuming the issues are interrelated, so I may be way off base, but if my assumptions are correct, then the only suggestion I can think of is to completely clear the device storage and cache and then try to factory reset again, as it may be hanging up on removing something there and aborting when it runs into trouble.
Maybe someone has a better idea. Your device may be bricked and since you unlocked the boot loader AFTER the issues started, you voided your warranty with none of the advanced recovery tools that you'd have with a custom recovery.
In other words: You might have to get a new phone.
Hey guys,
So this morning I stupidly tried to update to 4.4.4 since the phone said it has an update available. I was rooted running a few xposed modules, so I did the update, everything was fine, then upon getting back into the OS system.ui kept crashing every 3 seconds.
"Okay, just go use your Nandroid back up and flash via TWRP like always" I thought. So I did exactly that - rebooted to recovery, and went to flash my backup and it just sat there at "writing system" and did nothing. Next I rebooted to recovery again and did a full wipe of the OS - userdata and all, then tried two different toolkits (Mac and PC) and THEY got stuck at the 'writing system' as well.
Now I'm trying to flash stock to get my damn phone working via fastboot, but when i use the command fastboot flash userdata userdata_64g.img I get my cmd window saying "target reported max download size of 536870912 bytes erasing 'userdata'..."
This has been displaying for about 25 minutes now and I don't know what to do... Do I just leave it? Clearly something's not working. If this is an issue, what do I do to get around it and get back to android? How can I make the phone work again? I've flashed and reflashed stuff before but why is it seemingly busted now?
Help....anyone?
(FYI Since I have no phone, replies might be very sparse throughout the day because I can't actually check this thread and have to now go to work.)
Talnoy said:
Hey guys,
So this morning I stupidly tried to update to 4.4.4 since the phone said it has an update available. I was rooted running a few xposed modules, so I did the update, everything was fine, then upon getting back into the OS system.ui kept crashing every 3 seconds.
"Okay, just go use your Nandroid back up and flash via TWRP like always" I thought. So I did exactly that - rebooted to recovery, and went to flash my backup and it just sat there at "writing system" and did nothing. Next I rebooted to recovery again and did a full wipe of the OS - userdata and all, then tried two different toolkits (Mac and PC) and THEY got stuck at the 'writing system' as well.
Now I'm trying to flash stock to get my damn phone working via fastboot, but when i use the command fastboot flash userdata userdata_64g.img I get my cmd window saying "target reported max download size of 536870912 bytes erasing 'userdata'..."
This has been displaying for about 25 minutes now and I don't know what to do... Do I just leave it? Clearly something's not working. If this is an issue, what do I do to get around it and get back to android? How can I make the phone work again? I've flashed and reflashed stuff before but why is it seemingly busted now?
Help....anyone?
(FYI Since I have no phone, replies might be very sparse throughout the day because I can't actually check this thread and have to now go to work.)
Click to expand...
Click to collapse
I would try to download another ROM like Cm m9 and see if that will boot.
Sent from my A0001 using Tapatalk
Dear friends, three days ago, my phone stoped (hang) working and I turn it off by pushing the power button for seconds. then turn on again and it stops on GOOGLE logo.
I tried all things I found here, flash with all software, flash with fastboot and ...
the thing is some times it accept some , for example
fastboot flash boot boot.img
fastboot erase system
and and and
but I couldn't do flash system or recovery. when I do it, it starts to send to file to device and sending will be ok, but in writing, it says FAILED <remote: flash write failure>
can anyone help?
please
Same problem here
I have the same problem.
I turned off the device by pushing the power button for seconds. Then the device bootlooped, so i decided to reflash the rom (cyanogenmod 12.1) but the recovery didn't recognize the internal storage, and when i tried to make some wipe an error saying impossible to mount /data and /cache appeared. So i decided to flash the stock rom but during the flashing process, i had the "FAILED (remote: flash write failure)" message.
I also tried
HTML:
mke2fs /dev/block/mmcblk0p28
via adb to format data, but nothing happened.
I think that the /data partition is corrupted (also /bootloader because i had the same problem), but the eMMC is not damaged (i also followed this guide), so there's hope .
P.S. Sorry for the bad english.
You might want to try using WUGfresh Nexus Tool Kit V2.05. You can easily find it if you check here. I does require USBdebugging is set to be on. You can easily do do this by turning on the builer options. this is done by tapping on the "Build Number" 7 times. I can be found by going to settings and selecting "About Phone"
I hope this helps. WUGfresh Nexus Tool Kit is a great tool
Blacksmith5 said:
You might want to try using WUGfresh Nexus Tool Kit V2.05. You can easily find it if you check here. I does require USBdebugging is set to be on. You can easily do do this by turning on the builer options. this is done by tapping on the "Build Number" 7 times. I can be found by going to settings and selecting "About Phone"
I hope this helps. WUGfresh Nexus Tool Kit is a great tool
Click to expand...
Click to collapse
Thank you. I had already installed that tool. What should i do? I tried lock/unlock bootloader but it didn't work. I also tried to change recovery, but although it seems to have worked, i'm still with twrp .