Related
I flashed CM7 last night, loaded GAPPS, and the market was updating my apps, when I noticed none of the apps were updating. updates were all failing. I went into recovery and restored BAMF 1.5 remix. Now I have a problem. I can not download or update anything from the Market, all attempts fail. I cannot access CW recovery, the HTC white screen is as far as I get. I deleted rom manager, and tried to access CW recovery and still failed. I tried to do a factory reset, and still only get white HTC screen. Tbolt is functioning, I just can't fix my issue. Please help. Thanks.
You can't get in CW recovery or stock recovery?
Sent from my ADR6400L using Tapatalk
Did you try reflashing CW through ROM Manager?
Yep. very strange. I even tried to wipe the phone with factory reset, and just get stuck on white HTC screen. I had deleted rom manager because of something else I read, and can't get it back, But I can't even get to recovery from bootloader.
You can get to recovery through the bootloader by shutting off the phone and turning it back on holding down the volume button and pressing power toggle down to the recovery option and press the power button
Sent from my ADR6400L using XDA App
Orio56 said:
I flashed CM7 last night, loaded GAPPS, and the market was updating my apps, when I noticed none of the apps were updating. updates were all failing. I went into recovery and restored BAMF 1.5 remix. Now I have a problem. I can not download or update anything from the Market, all attempts fail. I cannot access CW recovery, the HTC white screen is as far as I get. I deleted rom manager, and tried to access CW recovery and still failed. I tried to do a factory reset, and still only get white HTC screen. Tbolt is functioning, I just can't fix my issue. Please help. Thanks.
Click to expand...
Click to collapse
Actually I spent a good few hours yesterday trying to help Orio out and we attempted a quite a few things to try and fix the recovery issue, this post should offer a bit more insight to the methods used;
adb reboot recovery failed
Reinstall latest Rom Manager apk and Flash CWM
flash latest rom manager via fastboot (CWM only)
(fastboot flash recovery /sdcard/recovery-clockwork-3.0.2.5.img)
**did not do fastboot erase recovery first**
"return to stock safely and properly" XDAthread by jcase
return to stock image [RUU], reroot, try again
try to boot into recovery via hboot
manually installed fix_permissions.sh script and busybox on rooted stock, ran.. didnt fix
tried to see if flash_image method would work, didn't
All of the above have failed and we basically tried almost all combinations. Never once would this phone get back into recovery, even after flashing the appropriate RUUs which include either stock android or CWM recovery. The only thing we have not currently attempted which might be the last thing left is to do is manually install the nandroid.sh script and do an advanced restore of the recovery image only from a nandroid backup on SD. I would rather not go down this method as it could have an undesired result, I have done it to restore a G1 back in the day but not 100% if its gonna work on a tbolt. Thankfully his phone boots, and we can get into hboot, but yea.. pretend recovery just doesnt exist at all...
Curious if anyone has any knowledge above what we have already tried.
SUCCESS !!!
I fixed it !
Apparently, when I loaded up cm7, files showed up about the same time on my sdcard in clockworkmod download file. I deleted those files, and reflashed clockworkmod in rom manager, (which this time took like 3 - 4 minutes), and rebooted into recovery and it worked...did it again, just in case it was a fluke and it worked.
All is well now...the planets are realigned !!!
Thanks everyone for your ideas and especially thanks to mattgyver83 who helped me for something like 4 hours yesterday. Exceptional kindness !!
mods...you can close this thread.
I am running 2.2.2 Froyo with 1.77 build.
I unlocked and rooted via Gingerbreak.
I went into CWM Recovery, erased all cache and flashed Alien Rom v3 and immediately flashed the Alien theme over it (I think that is where I made my booboo). The Rom appeared to load perfectly yet when the phone restarted the Moto logo animation appeared to run then the screen would go dark. This process repeats every few seconds non stop.
I can get into Android Recovery, RSD, everything. I tried flashing the 1.8.3 sbf through RS Lite 5.3.1 and while it said "PASS" it still hangs at the Moto animation.
I have no idea what to do. I think I can get out of it as I have done A LOT of searching through the forums and google but I am terrible with CMD.
Any helpful and/or useful advice?
Try restoring a backup, if not try to flash a fruitcake
http://forum.xda-developers.com/showthread.php?t=1163009
Sent from my MB860 using XDA App
Thanks for the thread. However it looks like I need CWM Recovery in order to flash a fruitcake? I cant get the phone to boot past animation so this wont work...
Also I didnt create backups
noxlo said:
Thanks for the thread. However it looks like I need CWM Recovery in order to flash a fruitcake? I cant get the phone to boot past animation so this wont work...
Also I didnt create backups
Click to expand...
Click to collapse
Are you unlocked and flashed cwm through fastboot, or did you use the system recovery app?
Sent from my MB860 using XDA App
System recovery app. I can access Androids recovery (obviously) but not many options...
Did you unlock your bootloader?
I ran into the same issue the first time I tried to flash Alien. Since you're flashing Alien, I assume your bootloader is unlocked (As it's required for Alien).
If you have an unlocked bootloader, do this:
EDITED: Apparently, I'm a new user and can't post links. Go to the address bar and replace the number with 1163342
Use Fastboot to flash the boot.img and the system.img files. This will give you Gingerbread/Motoblur like it comes out of the box. (It's a start!)
Thanks for the link. Will try when I get home. If I can just get past cmd...
I have a Evo 3d, hboot 1.50 latest radios, prl, pri. I had OMJ's latest Rom, and used Flash Image Gui to flash a custom Kernel package; I flashed Tiamuts "Tiamat_E3D-v1.1.0-Sense" http://downloads.tiamat-dev.com/8x60/110/Tiamat_E3D-v1.1.0-Sense.zip, and rebooted, then my phone was locked up on just the HTC screen.
I can still access the Bootloader, and Fastboot, and Recovery. I tried rolling back to my nandroid backup, and also reflashing the stock kernel through recovery (as the Rom won't ully load), and now all I get is a black screen after the HTC logo, and the phone is responsive to power and capacitive buttons, but no display at all.
Tried full wipe, and reflash of OMJ, even CleanRom.... Just black screen after HTC logo.... Any Ideas ? With Bootloader, Fastboot, and Recovery, you'd think I could unbrick, but no luck.
I'm sorry... I'm not a complete noob, I've been on the scene since early TP2s, and always rooted and custom rom’ed my Evo 4g.... Please help guys. Thanks in advance.
blckout99 said:
I have a Evo 3d, hboot 1.50 latest radios, prl, pri. I had OMJ's latest Rom, and used Flash Image Gui to flash a custom Kernel package; I flashed Tiamuts "Tiamat_E3D-v1.1.0-Sense" http://downloads.tiamat-dev.com/8x60/110/Tiamat_E3D-v1.1.0-Sense.zip, and rebooted, then my phone was locked up on just the HTC screen.
I can still access the Bootloader, and Fastboot, and Recovery. I tried rolling back to my nandroid backup, and also reflashing the stock kernel through recovery (as the Rom won't ully load), and now all I get is a black screen after the HTC logo, and the phone is responsive to power and capacitive buttons, but no display at all.
Tried full wipe, and reflash of OMJ, even CleanRom.... Just black screen after HTC logo.... Any Ideas ? With Bootloader, Fastboot, and Recovery, you'd think I could unbrick, but no luck.
I'm sorry... I'm not a complete noob, I've been on the scene since early TP2s, and always rooted and custom rom’ed my Evo 4g.... Please help guys. Thanks in advance.
Click to expand...
Click to collapse
Since you're on the HTC unlock method, in order for the custom recovery to properly work, i.e. flash all partitions including the kernel/boot partition, you have to access the custom recovery differently than the traditional method.
The proper command and method to access the custom recovery in order for the HTC unlock method to grant it write access to the kernel/boot partition is through fastboot. The full command is: fastboot boot c:\cwm-recovery.img . Once you've temporarily fastboot booted the custom recovery, you can then properly flash a ROM or restore a nandroid as both will be allowed write access to the kernel/boot partition.
Appreciate your support in using my application! Hope that helps!
Deleted my own question. I think I found a thread where it will be more appropriate.
Like joeykrim stated, you must access the recovery from fastboot to be able to flash kernels, nandroids and what not from recovery if you used HTC's method to unlock you phone. You are not bricked. It is fully fixable.
I have Clockwork Recovery flashed, always have (the only version compatible with Hboot 1.50, v4.0.1.4). I still have full access to the Bootloader, Customer Recovery, and Fastboot. But despite reflashing a fresh Rom (2 in fact), full wipes, reflashing boot.img with stock kernel; all the phone will do is boot past the HTC screen, vibrate, and the screen goes black. Capacitive buttons are responsive, and so is the power button, just no display. ...... Idk what else to Flash to get this phone booting again, any ideas ?
I had same problem I have 1 file name PG86IMG.zip I don't remember from where I downloaded 1st Iplaced this on SD root folder and turn on phone with volume down and power button and it care of everything
Sent from my PG86100 using XDA App
blckout99 said:
I have a Evo 3d, hboot 1.50 latest radios, prl, pri. I had OMJ's latest Rom, and used Flash Image Gui to flash a custom Kernel package; I flashed Tiamuts "Tiamat_E3D-v1.1.0-Sense" http://downloads.tiamat-dev.com/8x60/110/Tiamat_E3D-v1.1.0-Sense.zip, and rebooted, then my phone was locked up on just the HTC screen.
I can still access the Bootloader, and Fastboot, and Recovery. I tried rolling back to my nandroid backup, and also reflashing the stock kernel through recovery (as the Rom won't ully load), and now all I get is a black screen after the HTC logo, and the phone is responsive to power and capacitive buttons, but no display at all.
Tried full wipe, and reflash of OMJ, even CleanRom.... Just black screen after HTC logo.... Any Ideas ? With Bootloader, Fastboot, and Recovery, you'd think I could unbrick, but no luck.
I'm sorry... I'm not a complete noob, I've been on the scene since early TP2s, and always rooted and custom rom’ed my Evo 4g.... Please help guys. Thanks in advance.
Click to expand...
Click to collapse
You arent bricked if you can still get into fastboot, recovery, etc. I would recommend using this app called Flash Image GUI on the market, it's only $0.99 and I am (as we speak) flashing ziggy's dual core kernel. Oh wait my phone rebooted now. Its fast as all get out and my WiFi works (yay). But like I said this method is the EASIEST way to flash kernels!
up7up said:
I had same problem I have 1 file name PG86IMG.zip I don't remember from where I downloaded 1st Iplaced this on SD root folder and turn on phone with volume down and power button and it care of everything
Click to expand...
Click to collapse
I think the file you're referring to is the RUU (ROM Update Utility) file which can be placed in the root of the sdcard as PG86IMG.zip and flashed to competely reload all stock software (radios, system, kernel, etc) on the device.
These files are available at http://goo-inside.me/shooter/ruu.
blckout99 said:
I have Clockwork Recovery flashed, always have (the only version compatible with Hboot 1.50, v4.0.1.4). I still have full access to the Bootloader, Customer Recovery, and Fastboot. But despite reflashing a fresh Rom (2 in fact), full wipes, reflashing boot.img with stock kernel; all the phone will do is boot past the HTC screen, vibrate, and the screen goes black. Capacitive buttons are responsive, and so is the power button, just no display. ...... Idk what else to Flash to get this phone booting again, any ideas ?
Click to expand...
Click to collapse
Seems as if there is some issue with the display. If you confirm you have adb access to the device, I would think the issue lies in the android /system. If you don't have adb access, I would think the issue lies in the kernel/ramdisk.
Either way, if you want to eliminate both issues, reflash my Stock ROM - [ROM] joeykrim-original-1.2.0 Odex *Stock Rooted 2.08.651.2*, which will reload the stock kernel and the stock system with only adding in root access. I run this ROM as my daily ROM and it works great for keeping the phone stock but allowing root access.
Make sure to access the custom recovery through, fastboot boot c:\android\cwm-recovery.img . If you load the custom recovery through adb reboot recovery, or bootloader and selecting recovery from the menu, the HTC unlock method will not grant recovery write access to the kernel/boot partition.
Worse case, my stock ROM with stock Kernel doesn't resolve the display issue, you should flash the stock RUU files at http://goo-inside.me/shooter/ruu . If that doesn't resolve the issue, you'll prob need to exchange/return the device as it would seem to be a hardware issue.
Hope that helps! Good luck!
I rolled back from MMROM to NOTTACHTRIX Today and now my phone is stuck in CWM. (Cold Boot Android by selecting Boot Anroid NO BP option doesnt work either).
I have flashed MROM, Neutrino, NOTTACHTRIX, CM10.120120720 and all ended up into clockwork mod recovery. Kindly tell me an alternative -.- I am stuck with this from past 12 hours and no luck.
Update
I have managed to boot into android using Cold Boot without BP (i-e GSM radio will be disabled). I am recharging my phone battery and experimenting.
Before flashing NOTTACHTRIX, my phone had SKT version of 2.3.5 v167. I directly went for unlocking bootloader blabla recovery to get the NOTTACHTRIX working (thats like 4 months ago when I bought this phone)
So I tried going back to a version near 2.3.5 or higher. So going for 141 AT&T version didnt seem a problem for me except the .91 version bricks the device if u downgrade from 2.3.5 or above.
RSD Lite gave me 0x703e error and I couldn't flash the stop sbf.
Second resort I did was flashing 2.3.5 and 2.3.6 fruitcakes and still ended up in recovery.
I can only coldboot into android with Neutrino ROM other roms give me rebootloop when I choose coldboot.
I am suspecting a corrupted system or some kind of corrupt script in boot which keeps me in a loop into recovery. I did try adb script for ASUS TF101 to exit recovery bootloop but to no luck.
Also, I tried exitrecovery.zip flashable and still couldnt get into regular android OS.
This device is a headache for me now -.- and seemingly no one bothers to reply or to help me solve this issue >_>
Thanks for reading atleast
Update 3
Fixed it myself.
I downloaded fastboot, 2.3.6 fruitcake (system and boot), the older clockwork mod recovery, the one comes with Bootloader unlocking not some 5.0 version.
All I did was erased RECOVERY from fastboot, then boot and system. Frasled boot and system. Rooted with the bootloader unlocker package. Installed the old recovery and flashed NOTTACHTRIX.
Did all rom u flash succesfull..or fail mount?
Can u mount/unmount system..data etc..
If no..then yr cwm was not fr yr models..try another version
Yr detail on process but without the error msg..if flash ok then should be boot if not it must giv aome error while falshing even its completed
Sent from my e2001v21_v89_jbl1a698_2g using xda app-developers app
mynonama said:
Did all rom u flash succesfull..or fail mount?
Can u mount/unmount system..data etc..
If no..then yr cwm was not fr yr models..try another version
Yr detail on process but without the error msg..if flash ok then should be boot if not it must giv aome error while falshing even its completed
Sent from my e2001v21_v89_jbl1a698_2g using xda app-developers app
Click to expand...
Click to collapse
It was the bug of rebooting into CWM recovery and yes I was using right recovery for my Atrix i-e Rom Racers. Right now I am 4.x recovery and that works 100% to my needs on NOTTACHTRIX
And I flashed the fruitcake using fastboot. No flashing of stock sbf
Please help...recovery bootloop
dark_prince said:
It was the bug of rebooting into CWM recovery and yes I was using right recovery for my Atrix i-e Rom Racers. Right now I am 4.x recovery and that works 100% to my needs on NOTTACHTRIX
And I flashed the fruitcake using fastboot. No flashing of stock sbf
Click to expand...
Click to collapse
I have the same problem and tried several CWMs, and TWRP.
I can only boot to recovery, unless I try to boot with the BP HW Diag & Boot AP. Then I can cold-boot into Android, but with no USB support (so no ADB or charging capabilities).
I should have left my phone alone...I was running Nottachtrix just fine. Tried to flash CM 7 and then encountered this problem.
I have tried to restore, flashed new Roms, flashed new recoveries, flashed new boot.img, etc. No luck yet.
Tried the exitrecovery.zip, scripts to reset boot flags, full wipe and reload nottachtrix, flash radio, etc.
Still no luck.
Tried CWM version 4.xxx following instruction above, flashed fruitcake, rooted...still no luck.
Anyone have any advice?
Thanks in advance.
noobButStudying said:
I have the same problem and tried several CWMs, and TWRP.
I can only boot to recovery, unless I try to boot with the BP HW Diag & Boot AP. Then I can cold-boot into Android, but with no USB support (so no ADB or charging capabilities).
I should have left my phone alone...I was running Nottachtrix just fine. Tried to flash CM 7 and then encountered this problem.
I have tried to restore, flashed new Roms, flashed new recoveries, flashed new boot.img, etc. No luck yet.
Tried the exitrecovery.zip, scripts to reset boot flags, full wipe and reload nottachtrix, flash radio, etc.
Still no luck.
Tried CWM version 4.xxx following instruction above, flashed fruitcake, rooted...still no luck.
Anyone have any advice?
Thanks in advance.
Click to expand...
Click to collapse
did you try the updated and usually standardly used CWM, 5.0.2.6?
palmbeach05 said:
did you try the updated and usually standardly used CWM, 5.0.2.6?
Click to expand...
Click to collapse
Yes, thanks for the reply. I tried this one, and the CWM touch version advertised as designed for this phone model. No luck.
Aaaand.....I got impatient and tried to flash an sbf. Stupid, I know. Now, I have a shiny new brick.
Oh well, I ordered a new one from ebay, and I will spend my free time learning about possible ways to unbrick a phone.
noobButStudying said:
Yes, thanks for the reply. I tried this one, and the CWM touch version advertised as designed for this phone model. No luck.
Aaaand.....I got impatient and tried to flash an sbf. Stupid, I know. Now, I have a shiny new brick.
Oh well, I ordered a new one from ebay, and I will spend my free time learning about possible ways to unbrick a phone.
Click to expand...
Click to collapse
What's the msg that your brick is giving you? did you try flashing the pudding sbf and then trying to flash a custom ROM?
Resolved!
palmbeach05 said:
What's the msg that your brick is giving you? did you try flashing the pudding sbf and then trying to flash a custom ROM?
Click to expand...
Click to collapse
So here's the full story:
It would boot up and say "failed to boot 1"
It would not boot into fastboot(power on while pressing vol down). When I tried to boot into RSD(power on while pressing vol up), it would give the same error and say "PWR REASON PWR KEY PRESS" and then say Fastboot Protocol Support.
Using RSD, it would recognize the phone as being in fastboot mode, and any flashes would fail...including pudding.
Using fastboot, it would connect but give errors if I tried to flash or erase anything, like it was locked. When I tried to unlock again, it would say " OEM unlock not implemented."
This is why I figured it was bricked...the bootloader seemed hosed. Couldn't use RSD, and fastboot was useless.
But...after screwing around with it (battery pulled and re-inserted while holding various buttons) while connected to RSD, I noticed that the same error was there but somehow RSD recognized it! (I think the magic combo was to hold power and vol up while actually inserting the battery.)
So I flashed pudding, and it worked! Re-rooted, loaded CWM (using auto unlock 4.2), and the phone booted to stock config. It was still acting flaky (I don't think the sbf had loaded right), and it was unable to boot back into recovery, but I flashed CWM again using rom manager and was able to do a full recovery!
Yay!! I am ridiculously happy right now!
Anyway, when my ordered phone comes in, I will have a spare to play with. This one is staying as is from now on. (until I get bored again)
noobButStudying said:
So here's the full story:
It would boot up and say "failed to boot 1"
It would not boot into fastboot(power on while pressing vol down). When I tried to boot into RSD(power on while pressing vol up), it would give the same error and say "PWR REASON PWR KEY PRESS" and then say Fastboot Protocol Support.
Using RSD, it would recognize the phone as being in fastboot mode, and any flashes would fail...including pudding.
Using fastboot, it would connect but give errors if I tried to flash or erase anything, like it was locked. When I tried to unlock again, it would say " OEM unlock not implemented."
This is why I figured it was bricked...the bootloader seemed hosed. Couldn't use RSD, and fastboot was useless.
But...after screwing around with it (battery pulled and re-inserted while holding various buttons) while connected to RSD, I noticed that the same error was there but somehow RSD recognized it! (I think the magic combo was to hold power and vol up while actually inserting the battery.)
So I flashed pudding, and it worked! Re-rooted, loaded CWM (using auto unlock 4.2), and the phone booted to stock config. It was still acting flaky (I don't think the sbf had loaded right), and it was unable to boot back into recovery, but I flashed CWM again using rom manager and was able to do a full recovery!
Yay!! I am ridiculously happy right now!
Anyway, when my ordered phone comes in, I will have a spare to play with. This one is staying as is from now on. (until I get bored again)
Click to expand...
Click to collapse
The RSD issue and not being able to do anything. you are the 4rd person that i've dealt with to have that issue. we had a guy on here a few wks ago that me and andresrivas were trying to help. he wasn't getting the bootloop you were getting, but he had a very similar issue and had the RSD issue. like a wk later, i ended up having the RSD issue as well. Andresrivas also has experienced this issue. All i know is flashing that pudding is what saved us as well.
Idk what ROM you're going to put on there, but i would definitely keep that spare around. if your digitizer dies, you have a backup digitizer
So I'd been having some problems lately with my phone hanging on the Samsung screen on boot. Been running CM11 1/1/2014 nightly most recently. Decided to try using TWRP instead of CWM. That didn't seem to help my issue, so I tried installing CWM again. I used an app called Recovery Tools to download the touch version of CWM. After it said it installed, I tried to boot into recovery and got the error "Unauthorized software found. Please contact Verizon." (paraphrased a little).
Doing some research it looks like that error typically comes up when the bootloader is locked. Now, obviously I had my bootloader unlocked (well, Loki'd) because I was running CM11. Any help fixing this? I'm able to bypass the warning screen on boot if I hold down vol up + power like I'm going into download mode, but then hit vol down to cancel to boot up the phone. Once booted everything is ok, but any reboot just brings that up again. Using ROM manager to flash CWM recovery seems to work ok and it says its installed, but same issue. So does trying to flash TWRP from Goo.
If I were to run this tool that I used to root and loki before (http://forum.xda-developers.com/showthread.php?t=2301720) to install a recovery, would I be able to get everything going again? I think that somehow the recovery I installed wasn't Loki'd, although I picked the right one for my device.
Thank you in advance for any replies.
The fix I found was by pure dumb luck. I ended up trying to flash a recovery with Odin. Odin failed but reboot back into the os. I then used the twrp manager app from the playstore (mainly because goomanager wasn't downloading the recovery at the time) to flash the latest twrp recovery and all was good. Even though Odin failed at flashing the recovery I still think it helped somehow. I haven't thought much about why but I might have to now.
Sent from my SCH-I545 using Tapatalk
You could probably try using ODIN to get back to stock MDK and then Re-Root and install a recovery after.
Edit: And then flash CM11 again.
Sent from my SCH-I545 using Tapatalk
Will this one-click stock ROM work?
http://www.rwilco12.com/downloads.p... S4 (Verizon) (SCH-I545)/Stock ROMs/One-Click
or, which of the files on this page are what I would want? (about 1/3 of the way down for SCH-I545)
http://www.droidviews.com/how-to-install-latest-official-firmware-on-samsung-galaxy-s4-all-models/
I was actually able to reflash TWRP w/ their app from the Play Store. Still get a lot of boot hangs on the Samsung logo though. Seemed to happen less with CWM, but now I'm too scared to try to install a different recovery. I appreciate all your help guys.