Related
I have been running on stock 2.2 for a week or so now (SBF'd and was running with no issues)...not rooted or modified in any way. I did the OTA update for 2.3 and now my phone boots to the droid boot animation, and hangs. The boot animation completely freezes up, and the phone is unresponsive. Tried SBFing the 2.3 over and according to RSD that was completed successfully...but got the same thing on startup.
I got my phone the week it came out and have SBF'd many times, had rooted, ran all sorts of roms (as long as your counting different versions)...and of all things...an OTA update bricked it. Awesome.
I'll be heading to my local Verizon store in a few hours. Just thought I'd let you guys know.
That sucks Let us know how it goes at the store
With all the bootloader lockdown crap motorola put on these phones its just a matter of time before their own updates cause problems... anything strong enough to keep out hackers is also strong enough to cause serious problems when legit updates mess up...
Boot into stock recovery (power and hold X, then press the search key at the ! In the triangle)
Wipe data and cache
Reboot
karnovaran said:
Boot into stock recovery (power and hold X, then press the search key at the ! In the triangle)
Wipe data and cache
Reboot
Click to expand...
Click to collapse
^+1 this. Quite often when restoring the phone via an SBF it results in a bootloop which is corrected by performing a cache and data wipe through the stock recovery on the phone. It seems this can happen because the SBF doesn't actually wipe or replace /data and /cache
Another WIN for karnovaran!
karnovaran said:
Boot into stock recovery (power and hold X, then press the search key at the ! In the triangle)
Wipe data and cache
Reboot
Click to expand...
Click to collapse
Wow. Thanks! Worked like a charm.
Anybody that might have my same issue after installing the OTA, follow above steps, and wipe data in the stock recovery. My phone booted right up afterwards.
Thanks guy!
scsione889 said:
Wow. Thanks! Worked like a charm.
Anybody that might have my same issue after installing the OTA, follow above steps, and wipe data in the stock recovery. My phone booted right up afterwards.
Thanks guy!
Click to expand...
Click to collapse
Can I close this???
This may "wreak of non-search" and I am sorry if it does. While I have searched, the overall panic that one experiences when you suspect a brick and cannot afford to have a brick.... (that, plus a friend purchased this Glacier for me to help me get back on my feet with respect to career/employment, etc., so a good amount of guilt is thrown into this mix)... all prevents me from rationally and methodically searching thread after thread to figure out why I am having the problem I am having.
I will be as precise as possible.
1. Back in Feb., I perm rooted with visionary... then about 2 weeks later, I read that this root was not true radio s=off perm root, so I used adb and the scripts to perm root again--using the wiki as a guide. Saved a copy of the partition 7 bin on my laptop as an added precaution. Also, BTW, I never flashed the engineering HBOOT. It didn't seem essential to do so... PLUS, in almost every guide it warned that this was the most likely chance for one to f*ck up and brick, so in the interest of erring on the side of caution, I skipped that.
2. I kept stock ROM for several weeks after that... just enjoying root and freezing bloatware with Ti, and doing other root-enabled mods... nothing too involved.
3. About 1 week ago, I finally decided to flash my ROM. I had Rom Manager (paid version), and had flashed ClockworkMod Recovery 3.0.0.5. Further, as an FYI, I had/have numerous nandroid backups on the SD, plus several Ti backups of apps/data... even sync'd this with dropbox, so I can access those now (which are not of any help obviously).
4. I first flashed a CM7 nightly build--wiped data and cache, and as far as I know followed the guides precisely. All was well...new ROM worked alright... some bugs, but it was nice to have the new features, etc.. And of course the mental gratification of having 2.3.3 (GB) instead of 2.2.1 (boring old froyo). I updated the nightly maybe 2 times... in each case, I simply flashed without backing up those ROMS or wiping data/cache as they didn't seem necessary, plus I still had all my stock rom nandroid backups on the SD.
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Since I cannot get into the phone... I am of course panicked... I have ADB on my laptop if needed, but I really am at a loss as to why this happened, and what I can do at this point....
Please, please advise. My utmost appreciation and sincerest gratitude in advance for any assistance.
Thank you!!!
syntropic
syntropic said:
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Click to expand...
Click to collapse
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
should come up to a white screen.
take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Sent from my HTC Glacier using XDA App
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
Click to expand...
Click to collapse
No... that is what I meant when I said tried to "boot into recovery". And I got the 3 vibrate alerts and a blank screen, and nothing........
take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Click to expand...
Click to collapse
Will do... Thank you. DO you have any idea of where I f*cked up here??
Could be a number of things. Like wipe didn't go through completely , bad download, or just random crap out like a few others. Even flashing with the wrong cwr version can less to your issues. Lol like I said could be a number of things. Sorry I couldn't be more helpful.
Sent from my HTC Glacier using XDA App
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Sent from my HTC Glacier using XDA App
syntropic said:
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
Click to expand...
Click to collapse
What recovery are you using? 3.0.0.5? and you're trying to flash a 2.2 ROM. Thats where the problem lies. See my post regarding this. It's in my signature, the green one.
I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Click to expand...
Click to collapse
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
EDIT: MUSTKll20... Well, you were right... This is not ROM specific. I tried Re-Flashing RC3, which previously worked fine. Now, since I have CWModRec 3.0.0.5, I need to use a 2.3 ROM.... So I thought I would start with this idea. So, I guess, I need to get whatever is corrupt deleted... So my only question thus remains: How do I wipe everything except the SD from within CWR?
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
syntropic said:
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
Click to expand...
Click to collapse
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
and android phone have a method of using a section of the SD card for their memory banks. I'm not really sure how it works either, but it does. You can wipe the internal w/o wiping the SDcard.
Wiping the phone from with in the recovery image will not touch the SDcard, it will only wipe the internal. You can format the SD card from the Recovery Image, but i'll leave that dog sleep so we do not it accidentally.
last little clean-up question.
Sorry to bump this... last LAST question...
Mustkll20: I realized that you were correct to suggest to wipe everything except the SD... Something is corrupt.
But I am not real sure exactly how to wipe EVERYTHING except the SD, from within CW recovery... Since that is the only mode I have available to me. Once I wipe, I will reinstall CM RC3, then update Clockworkmod Recovery to 3.0.0.6, and then try and download RC4 again using another method, and re-flashing.
I would trial and error this, but do not want to wipe the SD.
Thanks guys... seriously.
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
Click to expand...
Click to collapse
I didn't see your reply... ummm. and I do need to wipe.. Because I have tried to re-flash both RC3 and RC4, and I get what must be a "bootloop": During the CM splash, it stops and then reboots---over and over. It never did that before.... so my problem is something else...
I don't know what else there is besides the SD and the ROM, but whatever it is, I need to delete it. So should I do a factory reset???
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
lowandbehold said:
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
Click to expand...
Click to collapse
Yep... I know the thread is not for thrillseekers (i.e., its boring), but I mention that I discovered this phenomenon... so I really wasn't in all that bad a spot to begin with.
I still need to figure out how to fix my current problem.... all CM RCs (I can only flash 2.3 ROMs because of CW 3.0.0.5) go into what I guess is a bootloop. In other words, they do not ever boot, just crash and restart. And the RC3 ROM I used worked fine before this... so something else is causing this problem. I need to wipe everything I guess, but I just don't know how... without touching the SD card and from within Clockwork Recovery.
Ok. Go into recovery.
1. Wipe data/factory reset
2. wipe cache partition
Both of these are on the main screen.
Go to advanced
3. Wipe Davlik Cache
Go back to main screen
Go into mounts and storage
4. format boot
5. format system
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
lowandbehold said:
Ok. Go into recovery.
{...}
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
Click to expand...
Click to collapse
Thank you for the concise and thorough response!!!!!!! Id thank you, but have used up my allotment. get ya tommorow!!
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
syntropic said:
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
Click to expand...
Click to collapse
You can thank the Google c&d order for that. Go to cyanogenmod.com. there is a link there for the gapps zip.
Sent from my HTC Glacier using XDA App
OK... I thoght Gapps.zip was just Google Docs. Luckily, I had that on my SD card from one of my many ROM downloads. I see why they had to make it separate.
But I am installing it, and everything is great... And I learned a lot too... Which can only mean trouble.
Thanks!
I had my Iconia working well with OTA 3.1 unrooted and it all started when I decided to update it 3.2 and then root it but after updating i realised that there was no root for 3.2 so i searched for a way to do so and i found the "downgrade to 3.0.1(unstable) then root" way and followed it and got my Iconia with the 3.0.1(unstable) downgrade and rooted it with "gingerbreak" and downloaded "acer recovery installer" and got "virtuous galaxy 1.0.5" rom and that's when every thing went wrong after i flashed it with the recovery mode it booted but was unusable it kept on force closing and lagging and nothing worked it didn't even respond to my touches.
I reseted the device many times but in vain so i decided to reflash the downgrade file "3.0.1(unstable)" and remove the root and re-update to 3.2 as if nothing happened but just when i reflashed the downgrade it booted but didn't even give me the chance to do anything it became really "unstable" it kept on force closing the launcher as if i'm stuck in a loop and i don't know what to do as i don't have that much knowledge so i left it closed as it is (so as not to ruin it more ) and want anyone to PLZ HELP me to return back to stock 3.2 (totally stock as if i just bought it) with no roms or root .
Thanks in advance to anyone who did or didn't help
I solved it i managed to get to settings in the 1 second interval between the successive force closes and then pressed factory default and like magic every thing was good as new at last.
Thanks to everybody helped me ...... no one even replied
Well 46 minutes isn't that long in forum-reply terms
Anyways. Good you got it fixed. Did you install Clockworkmod from Acer Recovery Installer, a full wipe followed by a fresh ROM from here flashed using CWM would likely have fixed it.
i think your mistake is , you didnt wipe data before lashing virtuous galaxy
interqd said:
i think your mistake is , you didnt wipe data before lashing virtuous galaxy
Click to expand...
Click to collapse
Exactly but I learned the lesson and now I rooted and wiped and got everything right with virtuous galaxy rom flashed and working
Peter Baher said:
I solved it i managed to get to settings in the 1 second interval between the successive force closes and then pressed factory default and like magic every thing was good as new at last.
Thanks to everybody helped me ...... no one even replied
Click to expand...
Click to collapse
Next time, you can reset your tablet by going: power button + right volume button (when held landscape with power button on top left corner)
power button + left volume button boots to recovery.
I have rooted my phone and flashed custom firmware b4... when i installed 2int to flash again.... it won't boot up the OS instead it keeps booting 2int... how do i boot into my os again... thx in advance
I am running android 4.1.1 jellybean
hotshot545 said:
I have rooted my phone and flashed custom firmware b4... when i installed 2int to flash again.... it won't boot up the OS instead it keeps booting 2int... how do i boot into my os again... thx in advance
I am running android 4.1.1 jellybean
Click to expand...
Click to collapse
Unfortunately, you cannot flash 2ndinit if you've already installed cyanogenmod, since it already has a bootloader. Goes for all versions of CM. I made the same mistake and had to flash the sbf.
I'm assuming that when you reboot normally you get stuck at the "red M" screen and your capacitive touch buttons might flicker. If that's the case, you will have to flash the sbf, because your bravo is boot looping. Go to this post here and follow the tutorial to the letter.
http://forum.xda-developers.com/showthread.php?t=1559109
If you are having further trouble, post it there.
And don't forget to say thank you to josuearisty
dr. Orange said:
unfortunately, you cannot flash 2ndinit if you've already installed cyanogenmod, since it already has a bootloader. Goes for all versions of cm. I made the same mistake and had to flash the sbf.
I'm assuming that when you reboot normally you get stuck at the "red m" screen and your capacitive touch buttons might flicker. If that's the case, you will have to flash the sbf, because your bravo is boot looping. Go to this post here and follow the tutorial to the letter.
http://forum.xda-developers.com/showthread.php?t=1559109
if you are having further trouble, post it there.
And don't forget to say thank you to josuearisty
Click to expand...
Click to collapse
thank u sooo much
hotshot545 said:
thank u sooo much
Click to expand...
Click to collapse
ok i just wanted to know is there a way to charge phone b4 doing this
hotshot545 said:
ok so if i flash it using sbf lite... will it run stock android 2.2 or will it's still run 4.1.1 and also will it still be rooted or will i have to restore root. and btw b4 i do this can i charge my phone in this "boot loop mode"... srry i am not the best at this kind of stuff... so I would greatly appriciate if you assisted me step by step if you could... thx in advance again..
**don't wanna brick my bravo xD
Click to expand...
Click to collapse
It will run stock 2.2.1 yes. If you follow the instructions from the tutorial, and you have at least a little battery left you should be fine, since you will have your phone plugged into your computer. You will have to re-root as well. When you sbf, you have to start all over, including rooting. Just make sure you follow the tutorial step by step. It does a much better job explaining how to fix everything.
Dr. Orange said:
It will run stock 2.2.1 yes. If you follow the instructions from the tutorial, and you have at least a little battery left you should be fine, since you will have your phone plugged into your computer. You will have to re-root as well. When you sbf, you have to start all over, including rooting. Just make sure you follow the tutorial step by step. It does a much better job explaining how to fix everything.
Click to expand...
Click to collapse
ok thx sooooo much.. approximatly how long will this take
hotshot545 said:
ok thx sooooo much.. approximatly how long will this take
Click to expand...
Click to collapse
Maybe an hour to get you back to jelly bean. It's worth it to take your time before each step so you don't mess anything up.
Dr. Orange said:
Maybe an hour to get you back to jelly bean. It's worth it to take your time before each step so you don't mess anything up.
Click to expand...
Click to collapse
Dude thx a bunch... i'm up and running jelly bean again using 2nd init btw next time i flash how would i do it without 2nd init
hotshot545 said:
Dude thx a bunch... i'm up and running jelly bean again using 2nd init btw next time i flash how would i do it without 2nd init
Click to expand...
Click to collapse
To reboot into recovery, hold the power/hold button down til that menu pops up, then select reboot, then select recovery. It was my pleasure helping. If you have any other questions just ask in the bravo general section and eventuality someone will help. Everyone with bravo is very supportive.
Edit: in recovery you will have options like reboot, wipe cache, wipe data, flash zip, backup/restore, that sort of thing. Usually I backup first just as a precaution, before wiping data and cache and then flashing a new rom. For other zips like gapps, cpu governors, or anything else you can just flash the zip without wiping.
Dr. Orange said:
To reboot into recovery, hold the power/hold button down til that menu pops up, then select reboot, then select recovery. It was my pleasure helping. If you have any other questions just ask in the bravo general section and eventuality someone will help. Everyone with bravo is very supportive.
Edit: in recovery you will have options like reboot, wipe cache, wipe data, flash zip, backup/restore, that sort of thing. Usually I backup first just as a precaution, before wiping data and cache and then flashing a new rom. For other zips like gapps, cpu governors, or anything else you can just flash the zip without wiping.
Click to expand...
Click to collapse
I'm gonna add, since the recovery option in the power button menu doesn't always access 2nd-init recovery (depends on the rom), nor is that option available in all roms, you just need to push the volume up button when the led light turns green when booting up to access the bootmenu. I've had cases where reboot menu recovery went to stock recovery instead of 2nd-init.
Its also a good idea to wipe cache\dalvik cache when flashing things like lockring mods, framework themes, and most theme related mods in general.
skeevy420 said:
I'm gonna add, since the recovery option in the power button menu doesn't always access 2nd-init recovery (depends on the rom), nor is that option available in all roms, you just need to push the volume up button when the led light turns green when booting up to access the bootmenu. I've had cases where reboot menu recovery went to stock recovery instead of 2nd-init.
Its also a good idea to wipe cache\dalvik cache when flashing things like lockring mods, framework themes, and most theme related mods in general.
Click to expand...
Click to collapse
When i start the phone up the led turns blue a few seconds before the boot animation appears... its that when i want to press the volume up key
hotshot545 said:
When i start the phone up the led turns blue a few seconds before the boot animation appears... its that when i want to press the volume up key
Click to expand...
Click to collapse
My fault, its Volume Down, and yes, the green blink before the blue is when you push it.
I got it confused with Stock Recovery, which is Power Button+Volume Up while turning on the phone.
I'm running a completely stock nexus 10. yes, it has been rooted before, but it got the full wipe/load from factory image for 4.4.3.
I am able to flash twrp and cwm touch for recovery.. which I'd normally not care about BUT it needs to go in for warranty work.. its battery draw is faster than the charger can push (expect it to be hardware failure.. same issue with 4.4.2)
I am unlocked. After I do my fastboot.exe flash recovery recovery.img ... and then I try to boot into recovery.. I just get that droid laying on his back with a red triangle with a ! in it..
suggestiona?
scythefwd said:
I'm running a completely stock nexus 10. yes, it has been rooted before, but it got the full wipe/load from factory image for 4.4.3.
I am able to flash twrp and cwm touch for recovery.. which I'd normally not care about BUT it needs to go in for warranty work.. its battery draw is faster than the charger can push (expect it to be hardware failure.. same issue with 4.4.2)
I am unlocked. After I do my fastboot.exe flash recovery recovery.img ... and then I try to boot into recovery.. I just get that droid laying on his back with a red triangle with a ! in it..
suggestiona?
Click to expand...
Click to collapse
I am thinking that is the stock recovery, let me look into this but im pretty sure that is the OEM recovery....
Thx Josh
lj50036 said:
I am thinking that is the stock recovery, let me look into this but im pretty sure that is the OEM recovery....
Thx Josh
Click to expand...
Click to collapse
I dont believe so unless they changed it from 4.2 that it shipped with. That recovery (which I also tried) allowed me to install stuff from .zip while in recovery (how the nexus was rooted..), wipe cache, wipe device, wipe delvik, etc... It was ugly, but it worked. I dont go into recovery very often, but I know this dead android isn't what I should be seeing on this device... or it wasn't the same one that I saw when I first got it. After sitting at the dead droid for a bit, it then continues to boot into the system and that works all fine.
I gave up for the time being.. I just flashed 4.4.2 on it, left recovery dead, and re-locked the bootloader. I'm shipping it off to samsung for charging issues, and they said first and foremost they'll flash it.. I'll let them discover the issue for themselves. IF they dont just swap out the device all together. I first noticed my charging issue with 4.4.3, so I flashed back to 4.4.2 (never had problems using this image before...) and the problem persists using different charging bricks.. so I think its a hardware issue. WAS plugged in during some power flickers.. wonder if that passed through to the device.
I'm assuming Samsung will use a proper flash vs. what we're trying to use.. and they should be able to do it with a locked bootloader.
scythefwd said:
I dont believe so unless they changed it from 4.2 that it shipped with. That recovery (which I also tried) allowed me to install stuff from .zip while in recovery (how the nexus was rooted..), wipe cache, wipe device, wipe delvik, etc... It was ugly, but it worked. I dont go into recovery very often, but I know this dead android isn't what I should be seeing on this device... or it wasn't the same one that I saw when I first got it. After sitting at the dead droid for a bit, it then continues to boot into the system and that works all fine.
I gave up for the time being.. I just flashed 4.4.2 on it, left recovery dead, and re-locked the bootloader. I'm shipping it off to samsung for charging issues, and they said first and foremost they'll flash it.. I'll let them discover the issue for themselves. IF they dont just swap out the device all together. I first noticed my charging issue with 4.4.3, so I flashed back to 4.4.2 (never had problems using this image before...) and the problem persists using different charging bricks.. so I think its a hardware issue. WAS plugged in during some power flickers.. wonder if that passed through to the device.
I'm assuming Samsung will use a proper flash vs. what we're trying to use.. and they should be able to do it with a locked bootloader.
Click to expand...
Click to collapse
FYI, as @lj50036 said, that is the stock recovery for 4.4. When you see that screen, you have to hit Power + Volume Up (or Volume Down) simultaneously to bring up the recovery menu. like factory wipe, clear cache, etc.
charesa39 said:
FYI, as @lj50036 said, that is the stock recovery for 4.4. When you see that screen, you have to hit Power + Volume Up (or Volume Down) simultaneously to bring up the recovery menu. like factory wipe, clear cache, etc.
Click to expand...
Click to collapse
Like hit them and let go, or till it reboots again?
scythefwd said:
Like hit them and let go, or till it reboots again?
Click to expand...
Click to collapse
Just push them both at the same time and let go. It usually takes a few taps before they show, but they eventually do. There's no reboot or anything. The blue words just show up in the top left corner of that screen with the Android laying on it's back with the exclamation mark over it. This was how it is on my N5 and N7 (2013) as well, or was before I flash Philz Recovery on all my devices.
charesa39 said:
Just push them both at the same time and let go. It usually takes a few taps before they show, but they eventually do. There's no reboot or anything. The blue words just show up in the top left corner of that screen with the Android laying on it's back with the exclamation mark over it. This was how it is on my N5 and N7 (2013) as well, or was before I flash Philz Recovery on all my devices.
Click to expand...
Click to collapse
Hrmm, no blue text on mine.. but I'll give it a shot when I get home.
scythefwd said:
Hrmm, no blue text on mine.. but I'll give it a shot when I get home.
Click to expand...
Click to collapse
Well, the blue text shows up after successfully pushing the buttons. Before you push the buttons, all you'll be seeing is the Android laying on his back with the red exclamation mark over it.
charesa39 said:
Well, the blue text shows up after successfully pushing the buttons. Before you push the buttons, all you'll be seeing is the Android laying on his back with the red exclamation mark over it.
Click to expand...
Click to collapse
well I'll be danged if it do...
Thanks gents. Last time I entered into recovery it was the original rom.. 4.2. I rooted, installed cwm, and hadn't returned. Odd that they made this change, but I'm cool with it lol. actually, I may have never actually gotten into the recovery mode before I flashed cwm to it now that I think about it.
Its there. I found that if I hit power , held it down, and then hit VOL- it let me in... just had to be quick bout it.. like less than a 1/2 second. sweet.. she's all factory fresh and ready to run at samsung. Yall rock.
cant imagine why they would do that..
She's only charging from 23-25% in 2 hours, at idle, no use on a vanilla install.. so something is definitely wrong! We'll see if its the brick or the device, either way I'm good to go.
scythefwd said:
well I'll be danged if it do...
Thanks gents. Last time I entered into recovery it was the original rom.. 4.2. I rooted, installed cwm, and hadn't returned. Odd that they made this change, but I'm cool with it lol. actually, I may have never actually gotten into the recovery mode before I flashed cwm to it now that I think about it.
Its there. I found that if I hit power , held it down, and then hit VOL- it let me in... just had to be quick bout it.. like less than a 1/2 second. sweet.. she's all factory fresh and ready to run at samsung. Yall rock.
cant imagine why they would do that..
She's only charging from 23-25% in 2 hours, at idle, no use on a vanilla install.. so something is definitely wrong! We'll see if its the brick or the device, either way I'm good to go.
Click to expand...
Click to collapse
No problem. Hope your issue gets fixed quickly.
Sent from my Nexus 5 using XDA Free mobile app
charesa39 said:
No problem. Hope your issue gets fixed quickly.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
ran it charging and idle from 6 till a little after 3pm today.. 25% more on the charge meter.. using the micro usb and the factory wall brick...
she's all boxed up and ready for ups though, should get her back like new in a couple weeks.. Thank GOD samsung will back their product.
Dont know whats the deal.. but its gonna be all good. Thanks again folks for educating me on why the stock recovery sux lol.
scythefwd said:
ran it charging and idle from 6 till a little after 3pm today.. 25% more on the charge meter.. using the micro usb and the factory wall brick...
she's all boxed up and ready for ups though, should get her back like new in a couple weeks.. Thank GOD samsung will back their product.
Dont know whats the deal.. but its gonna be all good. Thanks again folks for educating me on why the stock recovery sux lol.
Click to expand...
Click to collapse
Thx for taking the time to learn mate, Let us know when you get it back
Thx Josh