Develop Bugs

can't reboot into recovery

I, for some unknown reason, decided to flash CWM3.0.0.8 recovery through Rom Manager even though it was already on my phone. In theory that shouldn't hurt anything anyways. However when I went to reboot into recovery it gets stuck at the Splash1 screen...
I tried flashing CWM a few more times through recovery, still gets stuck.
I will try the "alternate recovery" now...
any other tips?

You said it was already on your phone so you could try and rename it PB31IMG.zip and place it on the root of your sd and flash it in hboot.
or
You could reboot your phone and downgrade your CWM to a more stable version and then flash it from your sd card?

Just flashing to a dif recovery should work
sent from my dinc

Yeah, try a different recovery. I had a couple issues, but my issue seemed to work itself out.
Sent from my ADR6300 using XDA App

[Q] Cant boot into Cyanogen/Stuck in Clockworkrecovery

I think ive bricked my phone and don't know what to do.... please help me
1) Ive root, downgrade and S-OFF my Desire Z using this instructions and everything went with no problem.afterwards I was able to boot into new ROM and confirm the changes.
2) I downloaded latest CM for my device, copied it on my SD card with Google pack and followed instructions here to flash CM(1).
I used Method via Recovery(2) and proceed every step with no error... after step 10 i select Reboot system now as instructed in the manual. BUT my phone boots into ClockworkMod Recovery AGAIN as if nothing happened.
I am unable to boot neither in CM nor previous ROM.
THANK U FOR HELPING ME
PS:
before copying CM files i formatted my SD card with windows in FAT32
I was not sure how can i boot into ClockworkMod Recovery. So, i did it by installing ROM manager application and selecting the option "Boot into ClockworkMod Recovery"
I am using ClockworkMod Recovery v3.0.2.4

omidz said:
I think ive bricked my phone and don't know what to do.... please help me
1) Ive root, downgrade and S-OFF my Desire Z using this instructions and everything went with no problem.afterwards I was able to boot into new ROM and confirm the changes.
2) I downloaded latest CM for my device, copied it on my SD card with Google pack and followed instructions here to flash CM(1).
I used Method via Recovery(2) and proceed every step with no error... after step 10 i select Reboot system now as instructed in the manual. BUT my phone boots into ClockworkMod Recovery AGAIN as if nothing happened.
I am unable to boot neither in CM nor previous ROM.
THANK U FOR HELPING ME
PS:
before copying CM files i formatted my SD card with windows in FAT32
I was not sure how can i boot into ClockworkMod Recovery. So, i did it by installing ROM manager application and selecting the option "Boot into ClockworkMod Recovery"
I am using ClockworkMod Recovery v3.0.2.4
Click to expand...
Click to collapse
Are you still able to boot into recovery?
If you are, try reflashing CM7 as it might have just not "stuck".
Also, check the md5 of the downloads to make sure they are intact.

OriginalGabriel said:
Are you still able to boot into recovery?
If you are, try reflashing CM7 as it might have just not "stuck".
Also, check the md5 of the downloads to make sure they are intact.
Click to expand...
Click to collapse
Yes! i am able to boot into ClockWorkRecovery and (apparently) it is working properly.
i also have access to ADB. but im such a noob i dont know what to do
I tried so many times to first wipe data/factory reset from the menu, then installing CM7 from Zip on SD and rebooted the device. but my phone boots to ClockWorkRecovery every time... and Md5, its correct.
Thanks for help

omidz said:
Yes! i am able to boot into ClockWorkRecovery and (apparently) it is working properly.
i also have access to ADB. but im such a noob i dont know what to do
I tried so many times to first wipe data/factory reset from the menu, then installing CM7 from Zip on SD and rebooted the device. but my phone boots to ClockWorkRecovery every time... and Md5, its correct.
Thanks for help
Click to expand...
Click to collapse
That's odd ... have you tried pulling the battery and booting that way as opposed to rebooting out of recovery?
Sent from my HTC Vision using XDA App

tried to install another rom? except cyanogen?

[Q] Help with brick?

So, I'm pretty sure I bricked my phone. Any help turning this around would help greatly. Here's how I got here. Plan was to Flash CyanogenMod 10. I rooted with no problems. Installed clockwork Mod on my phone. Created a backup of the stock Rom through ClockWork. Then backed up data to my removable SD card. I moved the CM-10 zip to the phone. Launched into recovery. Ran zip and it completed. On first boot got stuck on the CyanogenMod splash screen. After toying around with it (I believe clearing data in recovery). I finally got it to boot and went to install the Google apps zip the same way. That's when the real trouble started, now I can only get it to show the Samsung boot screen and then a blank screen.
I have attempted several How-to unbrick threads. However, the same thing happens to each one. I'll get them to work through Odin, but the phone will restart and go back to the same screen.
Thank you in advance for any help!

Just factory reset/wipe cache and dalvik and flash cm10 again, if I understand correctly you did not follow those steps when you flashed first time and those steps are necessary to be stable.
Sent from my SGH-I747 using Tapatalk 2

Krazex2005 said:
Just factory reset/wipe cache and dalvik and flash cm10 again, if I understand correctly you did not follow those steps when you flashed first time and those steps are necessary to be stable.
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Did all that and attempted to run the CM zip in recovery can up with an error and stopped installation. Error is right after Installing update it say,
"asset failed: get prop("ro.product.device") == "d2att"
E: Error in /sdcard/CyanogenMod 10/cm-10-20121012-NIGHTLY-d2att.zip
(Status 7)
Installation aborted."
I've been trying to move a new copy the CyanogenMod to the phone but I can't because it won't connect to the computer now. I can get it to download mode but don't know what to use. I attempted to use a stock file but the phone just reboots into black screen.
Thank you.

If you can get to download mode just use Odin to flash your stock rom
Sent from my SGH-I747 using xda app-developers app

What recovery are you using?
Sent from my SGH-I747 using xda premium

Soup7892 said:
Did all that and attempted to run the CM zip in recovery can up with an error and stopped installation. Error is right after Installing update it say,
"asset failed: get prop("ro.product.device") == "d2att"
E: Error in /sdcard/CyanogenMod 10/cm-10-20121012-NIGHTLY-d2att.zip
(Status 7)
Installation aborted."
I've been trying to move a new copy the CyanogenMod to the phone but I can't because it won't connect to the computer now. I can get it to download mode but don't know what to use. I attempted to use a stock file but the phone just reboots into black screen.
Thank you.
Click to expand...
Click to collapse
When I first tried flashing CM9/10 on my phone I got the same error. Weird thing is I didn't do anything special to fix it... I just went through a couple Touchwiz roms then a couple weeks later I tried a couple different AOSP ROM's and all of a sudden CM10 works now :s
Try a factory reset through recovery and see if you can flash any other ROMs or something.

did u try restoring your backup that you made?
Sent from my PC36100 using xda app-developers app

Have you tried using kies? I was able to repair a bootloop with kies. I was able to get into download mode and then had kies to what i believe was referred to as initiating the firmware. solved.

[Q] Boot Looping SPH-L900 Trying to downgrade from 4.3 to custom rom or remove KNOX

Early this morning I decided to try to get root and flash a custom rom, either CyanogenMod or Omni. I was able to flash touch recovery and wiped system files and cache. All custom firmwares failed to load. Now when the phone boots up, it goes into OTA activation, activates, does a PRL update, and reboots. Touch recovery repeats the system restore, unattended, and the loop repeats infinitely.
I am looking for a process that will help me cure the reboot loop to let me return to using the stock 4.3, but because of some bugginess I was experiencing, I would prefer a method that rids the knox bootloader and other protections so that I can gain root access and load custom firmwares.
I found a similar thread for a different model number, but I'm sure I'll need specific instructions for this model. Any help is greatly appreciated, as I'd rather not have to figure out a way to destroy the phone to get an insurance replacement. I'm also 23 days away from my upgrade date.
I am offering a $50 bounty for now, and when I upgrade, if possible to retain my phone while getting the upgrade price, you can have the note 2 that you helped fix.

cjkline83 said:
Early this morning I decided to try to get root and flash a custom rom, either CyanogenMod or Omni. I was able to flash touch recovery and wiped system files and cache. All custom firmwares failed to load. Now when the phone boots up, it goes into OTA activation, activates, does a PRL update, and reboots. Touch recovery repeats the system restore, unattended, and the loop repeats infinitely.
I am looking for a process that will help me cure the reboot loop to let me return to using the stock 4.3, but because of some bugginess I was experiencing, I would prefer a method that rids the knox bootloader and other protections so that I can gain root access and load custom firmwares.
I found a similar thread for a different model number, but I'm sure I'll need specific instructions for this model. Any help is greatly appreciated, as I'd rather not have to figure out a way to destroy the phone to get an insurance replacement. I'm also 23 days away from my upgrade date.
I am offering a $50 bounty for now, and when I upgrade, if possible to retain my phone while getting the upgrade price, you can have the note 2 that you helped fix.
Click to expand...
Click to collapse
Try this
Flash twrp recovery zip
Custom wipe system, data, cache
Install this http://forum.xda-developers.com/showthread.php?p=36388145
Install the root zip located in that op
Do not wipe anything else
Reboot it should act weird then reboot
After about 5-10 mins it will finish booting
Now flash philz 6.07.9 recovery via odin
Then boot into recovery factory reset/clean for new rom
Under mounts format data/media (internal sd)
Reboot into recovery
Flash your 4.4 rom
Sent from my SPH-L900 using XDA Premium 4 mobile app

Pending Testing
jlmancuso said:
Try this
Flash twrp recovery zip
Custom wipe system, data, cache
Install this http://forum.xda-developers.com/showthread.php?p=36388145
Install the root zip located in that op
Do not wipe anything else
Click to expand...
Click to collapse
Yeah, I wiped everything when I got home from work (don't know what I was thinking, really). TWRP even warned me no OS was installed, and I was like "so?". Anyway, as soon as it got stuck on the Samsung Galaxy Note II screen, I started the download of that rom you linked to. Still has 10 minutes left (big file is big). I'll come back with an update once I complete these first set of steps.
[Pending:]
Reboot it should act weird then reboot
After about 5-10 mins it will finish booting
Now flash philz 6.07.9 recovery via odin
Then boot into recovery factory reset/clean for new rom
Under mounts format data/media (internal sd)
Reboot into recovery
Flash your 4.4 rom
====================================

ADB Sideload
Since the device is not bootable, and I don't have an adapter to copy to my SD card via a usb reader, I struggled, but got the ADB Sideload function of the Android Development Toolkit to work once I upgrade to Team Win Recovery 2.7.0.0 via ODIN.
sideload log is as follows:
Code:
Updating partition details...
Full SELinux support is present.
Starting ADB sideload feature...
Installing '/data/media/0/sideload.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
UnRooted MC2 Stock Restore by blizzard412
Formatting /system and installing..
This will take a while
...Flashing temp special recovery
...Again just in case
Installing Radio...
Flashing firmware...
Flashing garwrnn & -EViL-KoNCEPTz- carrier partition fix...
You will automatically reboot to twrp to finish up...
[COLOR="Red"]E:Unable to mount '/preload'[/COLOR]
Should I be worried about the preload error?
Edit: rebooted but currently in a reboot loop without the startup sound. I'm going to let this go for about 10 minutes before I try to wipe and re-sideload? Before TouchWin rebooted it asked me if I wanted to install SU-SuperUser for root. Should I not install the root at this time?
Edit 2 THANK YOU!
[Pending:]
Reboot it should act weird then reboot
After about 5-10 mins it will finish booting
Now flash philz 6.07.9 recovery via odin.
Click to expand...
Click to collapse
I could not get this to flash via ODIN. The stock recovery kept loading instead
Decided to just try and move down the list.
Then boot into recovery factory reset/clean for new rom
Under mounts format data/media (internal sd)
Click to expand...
Click to collapse
Phone is now out of reboot loop once I cleared the data and cache. Text messages immediately came in after OTA activation and PRL update. I am now running stock rooted 4.1.2 without KNOX.
Reboot into recovery
Flash your 4.4 rom
Click to expand...
Click to collapse
Might wait on that for a minute. So thankful to at least have a working device again. Thanks for your help. Would you like the bounty? Please PM me a paypal address or your preferred methods.

The preload error is normal with twrp and is not an issue. Now you have lots going on so let me ask you this. Do you have a custom recovery and/or root as of now?
Sent from my SPH-L900 using XDA Premium 4 mobile app

Systems nominal
jlmancuso said:
The preload error is normal with twrp and is not an issue. Now you have lots going on so let me ask you this. Do you have a custom recovery and/or root as of now?
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, I had a rooted stock rom, replied to my texts from the day, then loaded rom manager, installed clockwork recovery. downloaded omni directly to the phone from their website, rebooted into clockwork, flashed, and things were fine. Booted into rooted kitkat 4.4.2, and now I'm flashin the gapps update to enable google services. network and wifi working fine under omni.
Can't thank you enough for helping me out of that hole from earlier.

In case you dont know omni rom does not come rooted.
Sent from my SPH-L900 using XDA Premium 4 mobile app

jlmancuso said:
In case you dont know omni rom does not come rooted.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep, I flashed SuperSU in CWM and fixed that. Things are running great. Just need to see what the battery life is like now on a new rom.

ZE551KL keeps rebooting into Twrp

I was fooling around with my phone and decided to try to update to MM. I downloaded the update to my sd card and fastbooted into stock recovery. I selected apply update from sd card and then selected the update file. It stuck on verifying update package for about 40 minuets at which time I was thoroughly pissed and pulled the battery. It booted into twrp when I restarted it. I selected one of my backups which twrp said was installed successfully. When I reboot it comes right back to twrp every time. what can I do to fix this.
Edit: Twrp is permanently installed on my phone, the use of stock recovery was a one time deal.
My Phone: ZE551KL-ZOOTD
Rooted: Yes
Bootloader unlocked: Yes

You stopped it mid-install... 40 minutes is not a long time. Rule number one of updating firmware, ALWAYS let it finish.
You've corrupted the system and probably boot. You'll need to download and reflash system through ADB.

willcall said:
I was fooling around with my phone and decided to try to update to MM. I downloaded the update to my sd card and fastbooted into stock recovery. I selected apply update from sd card and then selected the update file. It stuck on verifying update package for about 40 minuets at which time I was thoroughly pissed and pulled the battery. It booted into twrp when I restarted it. I selected one of my backups which twrp said was installed successfully. When I reboot it comes right back to twrp every time. what can I do to fix this.
My Phone: ZE551KL-ZOOTD
Rooted: Yes
Bootloader unlocked: Yes
Click to expand...
Click to collapse
First you said you use stock recovery. And then you said it reboots into TWRP. Which one is it?
Sent from my ASUS_Z00AD using Tapatalk

kenbo111 said:
First you said you use stock recovery. And then you said it reboots into TWRP. Which one is it?
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
Twrp is installed on my phone. I used fastboot to temporarily boot into stock recovery using the command "fastboot boot recovery.img" where the stock recovery is in my adb and fastboot folder. After I pulled the battery and restarted the phone it booted into twrp and that is where I am now

The problem has been solved. Apparently Twrp handles the factory reset differently than the stock recovery. I tried the factory reset in Twrp two or three times with no luck. I figured what the hell, before I wipe the everything and reinstall I would give stock recovery a try.
Fastbooted stock recovery, wiped the cache, did a factory reset, and when I rebooted my phone had been magically restored. I don't know how to delete this thread so if the moderators will, delete it. Thanks

hi i have a same problem . im stuck in my twrp . i already have a custom rom. but accidentally wipe my fone using restore factory data after that istuck on twrp.. i dnt have idea what should i do . i already put another custom rom but nothng happens still in twrp after rebooting.. btw im using asus zenfone 2 laser z00ld.. thank you plss help me

Fix for bootloop in twrp
Had the same issue earlier than i came to this simple trick(by experimenting).
Follow the steps:
1. Extract the boot.img from any rom zip file you have.
2. Move that boot.img to memory card and plug that memory card to the phone having reboot problem.
3. Now boot in twrp and click install--> image--> and locate the boot.img file in memory card.
4. Finally select boot option in twrp install screen, and finally slide to install.
Hope it will fix ur problem. Cant post the link. I am new to xda so.