Sorry if this is the wrong place to post this. I had to unroot my work phone because my firm said the servers identified my phone as having an operating system not supported by our security system and they suspended my server access.
So I uninstalled most of the "root" apps, thawed all the bloatware I froze in Titanium, disabled all the crap in Startup Auditor and then unrooted with Z4root. It literally took a minute for Z4root to unroot the phone.
I then brought my phone to IT to do a factory reset/wipe with one of our IT people so they can put me back on the server and I took my phone back.
The problem is whenever I start my phone, I get the Clockwork Mod screen (see attached). FYI I did not delete Bootstrap just in case I needed to restore for some reason.
BTW I did wipe data/factory reset in Bootstrap and when I rebooted the screen still came up and I'm definitely not rooted since immediately after unrooting with Z4root, Superuser was gone and Titanium said I didn't have root.
Any thoughts how to get rid of Bootstrap?
Thx!
The easy way is to flash SBF. The hard way is to root again and manually remove the bootsrap point. Then unroot again. SBF is much faster and convenient. Edit: much faster no - but much more convenient yes
Edit: if you want to go the long way, once you rooted again from PC mount system in RW mode, delete /system/bin/logwrapper then rename /system/bin/logwrapper.bin to /system/bin/logwrapper. Reboot and custom recovery should be gone. Unroot with Z4root and you are done.
leobg said:
The easy way is to flash SBF. The hard way is to root again and manually remove the bootsrap point. Then unroot again. SBF is much faster and convenient.
Click to expand...
Click to collapse
Thanks. I was afraid someone was going to say that. Is SBFing n00b-proof like z4root was with rooting my phone?
Edit: if you want to go the long way, once you rooted again from PC mount system in RW mode, delete /system/bin/logwrapper then rename /system/bin/logwrapper.bin to /system/bin/logwrapper. Reboot and custom recovery should be gone. Unroot with Z4root and you are done.
Click to expand...
Click to collapse
What does that mean??
jjdavola said:
Thanks. I was afraid someone was going to say that. Is SBFing n00b-proof like z4root was with rooting my phone?
What does that mean??
Click to expand...
Click to collapse
Huh, I was afraid you would say that Edit - I am sorry - I was about to put the commands you need to type using ADB from PC, but decided it will be confusing. ('from PC' to be scratched)
Well - SBF-ing is the easier way for you then. Simply make sure all pre-requirements are fulfilled (proper drivers installed, software loaded) and it is as easy as the Z4root. Read these instructions and follow them carefully and you will be set in no time
leobg said:
Huh, I was afraid you would say that Edit - I am sorry - I was about to put the commands you need to type using ADB from PC, but decided it will be confusing. ('from PC' to be scratched)
Well - SBF-ing is the easier way for you then. Simply make sure all pre-requirements are fulfilled (proper drivers installed, software loaded) and it is as easy as the Z4root. Read these instructions and follow them carefully and you will be set in no time
Click to expand...
Click to collapse
Thanks again!
OK. I flashed the SBF , it said PASS so I unplugged the phone and rebooted and Bootstrap didn't appear when I booted back up. What I believe to be a problem is that everything appears to be exactly the same as it just was (e.g. no apps were deleted, LauncherPro and my settings were still there etc.). Plus the System Updates option is not clickable anymore and my phone number was changed.
FYI I was thinking that the SBF would have just totally erased everything and I'd have to start from scratch installing apps etc.
Any thoughts?? Should I do another factory reset?
Yes - SBF will not erase data partition (user data). It is recommended you do factory reset once SBF is complete to clear up all the stuff that customizations before might have caused. At least you should clear cache partition to avoid wired behaviour from the phone. To delete cache - boot phone in stock recovery (power up while pressing X button - when you get the triangle with the android guy - press the magnifying glass button on the keyboard - menu will show up. Use the arrows and OK button to navigate. Options in menu are self explanatory I believe. Deleting cache will not delete your data, but deleting cache & data will delete data (factory reset)
To fix the phone programming (CDMA Verizon) - dial *228 option 1
leobg said:
Yes - SBF will not erase data partition (user data). It is recommended you do factory reset once SBF is complete to clear up all the stuff that customizations before might have caused. At least you should clear cache partition to avoid wired behaviour from the phone. To delete cache - boot phone in stock recovery (power up while pressing X button - when you get the triangle with the android guy - press the magnifying glass button on the keyboard - menu will show up. Use the arrows and OK button to navigate. Options in menu are self explanatory I believe. Deleting cache will not delete your data, but deleting cache & data will delete data (factory reset)
To fix the phone programming (CDMA Verizon) - dial *228 option 1
Click to expand...
Click to collapse
I cleared the cache and did the activation earlier. If I really need to, I'll do another factory reset some other day since unrooting, reseting and flashing wore me out for today.
Thanks again for your patience and assistance. I greatly appreciate your help.
i had the same problem and i figured out why it does it generally. Though it is weird for your case. When you have anything that requires root set to launch at boot (e.x SetCPU for me) for some reason it boots into the recovery. But when you disable these things it boots regularly.
Ever since the Jelly bean update my battery life has been awful. This issue isn't happening all the time however, a restart seems to resolve the issue. When my battery drains really fast Android OS is using anywhere from 30%-50%.
Anyone else having this?
richport29 said:
Ever since the Jelly bean update my battery life has been awful. This issue isn't happening all the time however, a restart seems to resolve the issue. When my battery drains really fast Android OS is using anywhere from 30%-50%.
Anyone else having this?
Click to expand...
Click to collapse
Have you tried to Wipe Data and Cache???? (Not through configuration, inside android. Wipe data and cache turning your phone on with 'vol +' and 'vol -' pressed.) When you see the black screen with white letters, scrool down using 'vol -' to 'RECOVERY' and press 'vol +' to select. When the green android appears, press 'vol +' and 'vol -' at the same time and you will have the option to wipe data and cache.
Then, reboot your phone and it will start as a new phone with jelly bean.
I saw a significant difference on my phone after this.
=p
zilian28 said:
Have you tried to Wipe Data and Cache???? (Not through configuration, inside android. Wipe data and cache turning your phone on with 'vol +' and 'vol -' pressed.) When you see the black screen with white letters, scrool down using 'vol -' to 'RECOVERY' and press 'vol +' to select. When the green android appears, press 'vol +' and 'vol -' at the same time and you will have the option to wipe data and cache.
Then, reboot your phone and it will start as a new phone with jelly bean.
I saw a significant difference on my phone after this.
=p
Click to expand...
Click to collapse
Are you rooted, and if so, did you maintain root? I was looking at the build.prop file and noticed a comment that one of the props is to allow the mounting of /system on the data partition which implies that it could be an image on the data partition or block of the data partition. I would like to wipe my data and cache so long as it didn't reinstall the entire OS causing me to lose root.
PantsDownJedi said:
Are you rooted, and if so, did you maintain root? I was looking at the build.prop file and noticed a comment that one of the props is to allow the mounting of /system on the data partition which implies that it could be an image on the data partition or block of the data partition. I would like to wipe my data and cache so long as it didn't reinstall the entire OS causing me to lose root.
Click to expand...
Click to collapse
Actually I'm on ICS rooted. But I know that if you wipe data and cache on JB, unfortunately ur gonna loose root. =/
I read people saying that there is a file that if you clear its data, everything gets back to normal and the battery drain stops. I just don't remember which one is. Do a little search here at the forum that you will find. =]
Thanks for both replies; the answer and the instructions.
I'm about to take the leap into the uncertainties surrounding an unlocked boot-loader, I think. Its been inevitable at some point, I guess...
It turns out that I'm one of the incredibly lucky ones. It wiped my internal sd but su was unaffected. All my rooted apps, except for a modifiaction to build.prop, a backup of build prop, and the su binary, were simlinked into root from a folder in data which I can restore from the tarball I'de made. The symlinks are still there, as was the modification to build.prop which meant I had no buttons at the bottom of the screen to start with. Perhaps because of this; no extra apks detected or something, and with the supersu.apk on data. I don't know if having the reinject root option of supersu previously checked mattered or not. In any case, bootloader still locked and everything wiped. Now I have to put it all back to how it was but that was a given, either way.
This had nothing to do with the rootkeeper app btw. When I installed it, it still had the same settings as prior; didn't have re-insert root or anything.
Sorry for posting a useless comment since I don't know what made my situation differant than what other people have had happen, keeping the binary but losing proper file permissions on it from what I had read last night, but I'm happy that it worked out for me and telling my wife would be futile.
Also, I cleared cache and did a wipe data/system restore... twice. The first time, I made it most of the way through the initial Android setup and it popped me back a few selections; opting not to enable to turn on Google+ and then the screen flickered and it pulled me back to entering my Google account again so I powered off and did the clear cache and wipe again. What luck!
Bringing this thread back. Lately I've been getting some poor battery life on my maxx HD. I used to be able to get through the day with around 50% battery left at the end of the night. Now that number has been steadily decreasing over time. Does the recovery method mentioned also wipe my apps? I would love to finally root the phone to remove all the crapware but everything seems to be for the 925 and not the 926.
Sent from my DROID RAZR HD using Tapatalk 2
hello xda. i need your help. im desperate. i dont know what else to do with my moto g here's what happened:
first of all, i dropped my moto g into the water.
right after i got it out, it startet bootlooping. then it turned off by itself after almost an hour had passed.
i put it in a bag full of rice for the rest of the night and almost the whole following day. then i plugged it into the wall charger, and it wouldnt charge at all. the only sign of life was the blinking led.
so i took it to Movistar-Peru for repair, and told me the obvious: water damage was not covered in the warranty, then my phone was returned to me.
so i decided to tear it down by myself.
everything was looking fine. the water indicators were red, but everything was clean except for the battery socket: there was mineral condensation around it. i wiped it out, cleaned it away and then the phone would actually charge the battery icon displayed normally.
so i let it charge for 3 hours and after it was completely charged i turned it on. just to run into a black screen after the bootnimation.
good news is it actually can boot into fastboot mode and can access recovery menu.
i did some research here, and seemed like my phone needed a full stock flash (that´s what i thought). i decided to unlock the bootloader, using motorola unique code. (i thought it may be needed for flashing, but it seems it is not necessary)
in recovery, my sdcard folders display normally, i can wipe data/factory reset it normally, BUT when i try to erase cache partition, the phone reboots.
so i started flashing my device through fastboot. i should mention that before i dropped it into the water, i had installed 4.4.2 ota update. but whenever i tried to flash a 4.4.2 rom, i got hab check failed for sysyem, for recovery and sometimes for boot.
now, i've tried several official motorola signed jelly bean roms (nextel br, movistar sp, claro ar, etc etc) including original Movistar Pe jb rom (which ive already flashed uncountable times) with no errors on flashing, but neither of them got me passed the black screen after bootanimation. (the phone is not off, cause the backlight remains on). the only way of getting out of it is rebooting into fastboot mode again (volume- and power).
i've also tried relocking the bootloader, and the process gives me no errors (the word "locked" displays by the end, though the phone then reboots into the "warning bl unlcked" screen) , but regardless of that and the relocking process turning out okay, status code 3 is displayed in menu, meaning the bl wasnt really relocked..?)
in short:
-dropped into water, started bootloop, then it turned itself off.
-next day it would display black screen after bootnimation, no matter what i did.
-if i choose wipe cache partition, the phone reboots.
-i've flashed it "sucsessfully" several times, still runs into a black screen after bootnimation.
-i've unlocked the boootloader
-if i try to reclock: process turns out okay("locked" word by the end), but status code remains being 3.
-i dont care about backups, i had nothing important in my phone (gdrive ftw)
my concearns are:
-possible hardware unrepairable damage
-bootloader got corrupted
-mineral condensation is still there deep inside the components
-maybe gpu? emmc corrupted? semi brick? idk..
my questions are:
-what can i do from now?
-i've read that a new bootloader can be flashed into the phone. risk of bricking my phone?
-if the bootloader is the problem, flashing a new one would solve it?
-in general, what am i doing wrong in all of this? has my phone any chance of functioning normally, at all?
please help me , i miss my phone, i got it for christmas, it is my first smartphone and i woudl like to bring it back to life if possible. thank you for reading.
I can help!
My girlfriend dropped her Moto G in water too, and it also started showing a black screen after the boot animation. I just managed to fix it.
Even if you have done some of this stuff, do it again anyway.
1-Power phone off
2-Press and hold volume down key for 3 seconds, then press the power key, then release both
3-You will see the boot options menu
4-Press the volume down key to scroll to RECOVERY, then press volume up to select it
5-You will see the Motorola logo, then after 10-30 seconds (maybe longer), you will see a Android logo with an exclamation symbol
6-Press and hold the Volume Up key for 10 seconds, then tap the power button
7-You will see a new menu
8-Use the Volume down key to scroll to Wipe data/factory reset, and then press the power key to select it.
9-Then use the volume down key to select yes, and use the power button to confirm
10-Let the phone format, then press the power key to reboot.
Once the phone has switched back on, wait and see what happens. If the Motorola logo comes on and then stays on for ages WAIT! It takes ages, but the phone will come back to life normally and be working in a few minutes! If you see a black screen again:
Repeat steps 1-7
When you see the new menu again, this time select the cache wipe option (it's the last option on the list)
Let the phone wipe and then it should reboot
This time you will defo see the Motorola logo on the screen for ages. Just keep waiting and press nothing. Hopefully after a minute or 2 it will then take you to the welcome screen
Hope this helped. I couldnt find any advice so had to experiment haha
Thank you for replying to my problem
i have already done your steps uncountable times.
every time i try to wipe cache, the phone reboots. it does not wipe anything at all, it just instantly reboots. then bootanimation, then black screen again, but nothing happens. not even after 2 minutes, after 5 or 10. nothing. just black screen until battery drains completely from continously powering the backlight. do you think maybe the water hardware-bricked my phone? also, im ocassionally getting blue screens out of a sudden, then the phone powers itself off.
Ah, ok, sorry my suggestion didn't help. I had exactly the same problem, so surprised this didn't help you. After being dropped in water, all I got was a black screen after the initial start animation. I don't really know much about phones tbh, I just managed to fix mine through trial and error. My girlfriends phone was initially sent to a shop for repair, and although the guy couldn't fix it, he said there was no signs of water damage. Not really sure then why the phone stopped working, but the method I suggested did work for me. I don't think there was anything else I tried. It's worth mentioning maybe that it took 6 weeks before I could fix the phone. Maybe it took that long to fully dry out? Straight after the accident though the phone was put in a bowl of rice for days so it should have been dried pretty quick. Don't really know what else to suggest, sorry I couldn't be more help. Have faith though, I reckon it'll come back to life soon
thank you for posting a reply and thank you for your advice. i appreciatte the attention given. i will further try some other methods in hope of a solution.
Your bootloader is working fine, dont touch it.
Unlock the bootloader and try to install cwm or twrp recovery, mount and format /data , /cache , /system through the recovery (if you manage it get recovery working ofc).
After that download mfastboot and flash stock rom with it.
Btw if you ever put anything into bag of rise, DON'T CLOSE the bag, you`ll probably do more damage than good this way.It should be done in open-air conditions.
liveroy said:
Your bootloader is working fine, dont touch it.
Unlock the bootloader and try to install cwm or twrp recovery, mount and format /data , /cache , /system through the recovery (if you manage it get recovery working ofc).
After that download mfastboot and flash stock rom with it.
Btw if you ever put anything into bag of rise, DON'T CLOSE the bag, you`ll probably do more damage than good this way.It should be done in open-air conditions.
Click to expand...
Click to collapse
are you sure it has nothing to do with the bootloader? now that you mention this.. can a 4.4.2 bl load a 4.3 rom successfully? and moreover, if i flash another bl, it will overwrite my original one right? is there eny problem on that? i am asking because no matter what i do, regardless of the "locked!" message, the menu keeps showing code status 3.
what happens if i flash the recovery and cant mount or flash any rom? or if the black screen persist after that?
and i wish i had known the rice trick before, cause i kept the bag closed for almost a day :s
grahameaddicott said:
My girlfriend dropped her Moto G in water too, and it also started showing a black screen after the boot animation. I just managed to fix it.
Even if you have done some of this stuff, do it again anyway.
1-Power phone off
2-Press and hold volume down key for 3 seconds, then press the power key, then release both
3-You will see the boot options menu
4-Press the volume down key to scroll to RECOVERY, then press volume up to select it
5-You will see the Motorola logo, then after 10-30 seconds (maybe longer), you will see a Android logo with an exclamation symbol
6-Press and hold the Volume Up key for 10 seconds, then tap the power button
7-You will see a new menu
8-Use the Volume down key to scroll to Wipe data/factory reset, and then press the power key to select it.
9-Then use the volume down key to select yes, and use the power button to confirm
10-Let the phone format, then press the power key to reboot.
Once the phone has switched back on, wait and see what happens. If the Motorola logo comes on and then stays on for ages WAIT! It takes ages, but the phone will come back to life normally and be working in a few minutes! If you see a black screen again:
Repeat steps 1-7
When you see the new menu again, this time select the cache wipe option (it's the last option on the list)
Let the phone wipe and then it should reboot
This time you will defo see the Motorola logo on the screen for ages. Just keep waiting and press nothing. Hopefully after a minute or 2 it will then take you to the welcome screen
Hope this helped. I couldnt find any advice so had to experiment haha
Click to expand...
Click to collapse
It worked for me, Thanks
liveroy said:
Your bootloader is working fine, dont touch it.
Unlock the bootloader and try to install cwm or twrp recovery, mount and format /data , /cache , /system through the recovery (if you manage it get recovery working ofc).
After that download mfastboot and flash stock rom with it.
Click to expand...
Click to collapse
ok i did what you said, i tried to flash cwm and fastboot presented no problems, (output is "okay"), but un the phone screen there's a message "mismatched partition size (recovery)", and when i enter recovery, it boots normal STOCK recovery!! i donw know whats happening. i renamed the cwm image to cwm.img and typed in these commands:
fastboot erase recovery
fastboot flash recovery cwm.img
then i clicked recovery option in the bootloader menu... but it booted into stock recovery!! this is so confusing
Now
mfastboot flash partition gpt.bin
mfastboot flash fsg fsg.mbn
at first since it seems you got partitions a bit messed for some reason.
Then flash everything in order, skip those 2
Also if you are really suspcious about the bl is not working fine, just flash motoboot.img from the same version of android you need.
thank you i will proceed to try what you said. though i have a question: is it possible for the bootloader to be overwritten with a previous version?
and what does it mean when the phone outputs "hab check failed for boot/recovery/system (etc)" ? i sometimes get those errors when flashing other region (official) roms
liveroy said:
Now
mfastboot flash partition gpt.bin
mfastboot flash fsg fsg.mbn
at first since it seems you got partitions a bit messed for some reason.
Then flash everything in order, skip those 2
Also if you are really suspcious about the bl is not working fine, just flash motoboot.img from the same version of android you need.
Click to expand...
Click to collapse
i tried what you said and it is all the same. i choose "recovery" after flashing a custom recovery image, but it boots into stock recovery. any ideas on what might be going on?? is it possible for water damage to cause this behaviour ?
tenjou_89 said:
i tried what you said and it is all the same. i choose "recovery" after flashing a custom recovery image, but it boots into stock recovery. any ideas on what might be going on?? is it possible for water damage to cause this behaviour ?
Click to expand...
Click to collapse
Hmm, maybe leave the recovery aside for now and try to boot a 4.3 ROM (stock one).
Also you cannot downgrade to bootloader afaik, but the newer ones work fine with 4.3 ROMs.
I don't think that the eMMC got damaged, cos nothing will work then.I really can't say if your problems are coming from the water dip or it's just the Moto G being stubborn if you do even one thing the wrong way.
PS. How do you flash the recovery?
fastboot erase recovery
fastboot flash recovery recovery.bin
fastboot reboot bootloader
This way?
what about the ram? a guy on some other forum said that maybe the ram got damaged to a point where only a part of it is now writable, and it gets flooded just before the complete boot up of the system, wichi is why the phone would then crash and display a black screen. what do you think about that theory?
i am going to try with 4.3 roms now. oficial and custom and post the results.
liveroy said:
PS. How do you flash the recovery?
fastboot erase recovery
fastboot flash recovery recovery.bin
fastboot reboot bootloader
This way?
Click to expand...
Click to collapse
yes, exactly that way.
edit: except i have images instead of bins, so:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot bootloader
Typo of mine, should be .img
About that RAM theory, it really doesn't sound viable to me, but who knows.
If I have to guess, I would say it's probably some crucial component failing to initialize properly and the kernel halts the system.
hmmm do you know of a method of checking for the conditions of individual hardware componets through a pc? like probing or running a full check of everything, not just the emmc..?
These seem not to work.
But if you find the correct details, maybe there is something to test in the service menu.
I have the same problem without water damage. I guess its the 4.4 OTA bug.
Tried reflashing the firmware i already have but of no use.
Mine shows the Blue Motorola logo and then doesn't show the boot animation.
Please can anyone help me out :'(
Installed the newest patch from Google April. I restarted the device after install and it wouldnt go through.
DEVICE IS NOT ROOTED
So I went into recovery mode
I tried clearing partition... it didnt work (did that 5 times)
I tried reboot system (didnt work)
I turned it off and on like 10 times and it didnt work
I tried Wipe data/factory reset....lost everything (which sucks because I had photos that never got backed up)
I am official lost, can someone help me? I am not sure what to do next!
I have a macbook, if someone can help me I will greatly appreciate it!
agentjucey said:
Installed the newest patch from Google April. I restarted the device after install and it wouldnt go through.
Click to expand...
Click to collapse
Hello. I have this same problem.
I can't start my phone.
I have no idea what happened. Phone was connected to charger and everything looked ok, but this s**t happend ...
On error screen I've pushed power + volup button
Wipe cache
wipe device ...
nothing helped ...
Still getting this same error ...
Are you getting an error message on the screen or is the phone stuck at the boot animation?
audit13 said:
Are you getting an error message on the screen or is the phone stuck at the boot animation?
Click to expand...
Click to collapse
Android with red triangle and exclamation mark inside ...
Same problem here. This was after applying OTA latest security patch for April.
Would try to boot ("Google" word) 2x then go back to Android bot with red "!" - no command.
Tried wiping cache; factory reset - both multiple times. Still the same.
Tried also draining battery, then full re-charge, still the same problem.
Hope somebody could figure this out.
Thanks in advance.
The red triangle screen is what you see before entering recovery. To get into recovery, press the power button and press volume up.
audit13 said:
The red triangle screen is what you see before entering recovery. To get into recovery, press the power button and press volume up.
Click to expand...
Click to collapse
I did that ...
wiped cache - no result
reset to factory - no result
Flash the factory image. If your phone is not bootloader unlocked do that first
GtrCraft said:
Flash the factory image. If your phone is not bootloader unlocked do that first
Click to expand...
Click to collapse
I never did that before ... is there any tutorial for absolute beginners which you could recommend?
tupper said:
I never did that before ... is there any tutorial for absolute beginners which you could recommend?
Click to expand...
Click to collapse
Yeah its here in the general section
Flash factory images from NRT tool
1 Unlock ur bootloader
2 flash latest factory image and clear ur internal memory also! Coz the tool has an option to clear internal memory or not to clear internal memory!
3 Done!
So i wanted to try out this custom android 5.1.1 i folowed every step but i didnt do one *clear the old system cache* i didnt found it in the recovery so i thought deleting delvik cache will be enough,
The only thing the mobile does, when i press power button it vibrates once and still black screen, cannot entry recovery or anything.
I ve read somewhere this is not a bricked phone so it should be fixable but i have no idea how, somebody told me the old system is still in the phone and it causes errors so it does not boot up.
Strataios said:
So i wanted to try out this custom android 5.1.1 i folowed every step but i didnt do one *clear the old system cache* i didnt found it in the recovery so i thought deleting delvik cache will be enough,
The only thing the mobile does, when i press power button it vibrates once and still black screen, cannot entry recovery or anything.
I ve read somewhere this is not a bricked phone so it should be fixable but i have no idea how, somebody told me the old system is still in the phone and it causes errors so it does not boot up.
Click to expand...
Click to collapse
Try going into fastboot mode.
Then flash a custom recovery and this time clear everything
Nikhil kuttu said:
Try going into fastboot mode.
Then flash a custom recovery and this time clear everything
Click to expand...
Click to collapse
Was wondering about the same but it wont let me to get in haha,