Develop Bugs

[Q] I may have bricked my phone

All,
I'm a NOOB, so bear with me here. I've recently rooted my phone and am trying to install syndicate ROM.
seemed pretty straight forward. I have clockworkMod Recovery v.2.5.1.0 I copied the zip file to my SD card.
Selected wipe data/factory reset
selected install zip from sdcard
selected choose zip from sd card
manually search for the zip file sydicatefro110-standard-signed.zip
seems to load fine and goes back to clockwork Mod menu
go back and select reboot now
phone stays at opening screen that displays Samsung title with samsungmobile.com
Any assistance you can provide is greatly appreciated.

You did not brick your phone in any way. A brick is when it will not turn on no matter what you do.
(One of my biggest pet peeves is people calling what isn't a brick, a brick.)
Follow these instructions and your phone will work perfectly: http://tinyurl.com/epicfix
EDIT: And next time you flash a ROM READ THE INSTRUCTIONS. If you go back to the SRF thread and take a look at what it says to do, you will know precisely why you ended up with a bad result.

davep785 said:
All,
I'm a NOOB, so bear with me here. I've recently rooted my phone and am trying to install syndicate ROM.
seemed pretty straight forward. I have clockworkMod Recovery v.2.5.1.0 I copied the zip file to my SD card.
Selected wipe data/factory reset
selected install zip from sdcard
selected choose zip from sd card
manually search for the zip file sydicatefro110-standard-signed.zip
seems to load fine and goes back to clockwork Mod menu
go back and select reboot now
phone stays at opening screen that displays Samsung title with samsungmobile.com
Any assistance you can provide is greatly appreciated.
Click to expand...
Click to collapse
Well your problem is the fact that Syndicate ROM is EXT4 only and you rooted using RFS. You need to use the root method that installs Clockworkmod 3.0.0.5 not the one that installs 2.5.1.0. Go ahead and do that, when it boots into clockwork let it convert everything to EXT4 and then install Syndicate again.

k0nane said:
(One of my biggest pet peeves is people calling what isn't a brick, a brick.)
EDIT: And next time you flash a ROM READ THE INSTRUCTIONS. If you go back to the SRF thread and take a look at what it says to do, you will know precisely why you ended up with a bad result.
Click to expand...
Click to collapse
WHY WON'T IT READ!?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

RandomKing said:
WHY WON'T IT READ!?
Click to expand...
Click to collapse
HAHA...what a great episode and shots at Apple!
Do you BONSAI?

Sponged! That is when an Epic will not boot fully and is waiting to absorb information. Not bricked....sponged.
Do you BONSAI?

[Q] Having difficulties getting custom recovery to work

Hey guys!
My friend asked me to root is HTC Wildfire S, it has S-OFF and an unlocked bootloader (yay!). then I flashed (supposedly successfully) a custom recovery, but when I select RECOVERY on the HBOOT screen the device is stuck at the HTC logo and does nothing. I tried putting the zip with the weird name that HBOOT recognizes and it installs with no error. I also tried to flash it with fastboot which also writes the recovery partition with no error, but it still won't load the recovery. (Although when I try to "fastboot erase recovery" it fails saying: "FAILED (remote: not allowed)". I also tried both CWM and TWRP and neither of them worked. Anyone could help me get the custom recovery working? I also attached a image of the HBOOT screen if that helps. USB debugging is turned on, and fastboot is disabled in settings.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ps.: I also tried to use the htc super tool to root the phone but it didn't work either

Longi94 said:
Hey guys!
My friend asked me to root is HTC Wildfire S, it has S-OFF and an unlocked bootloader (yay!). then I flashed (supposedly successfully) a custom recovery, but when I select RECOVERY on the HBOOT screen the device is stuck at the HTC logo and does nothing. I tried putting the zip with the weird name that HBOOT recognizes and it installs with no error. I also tried to flash it with fastboot which also writes the recovery partition with no error, but it still won't load the recovery. (Although when I try to "fastboot erase recovery" it fails saying: "FAILED (remote: not allowed)". I also tried both CWM and TWRP and neither of them worked. Anyone could help me get the custom recovery working? I also attached a image of the HBOOT screen if that helps. USB debugging is turned on, and fastboot is disabled in settings.
ps.: I also tried to use the htc super tool to root the phone but it didn't work either
Click to expand...
Click to collapse
As I can tell of "Feb 8 2012" your WFS is 2012 edition
You need another recovery modded for the WFS
1.Download this
2.Extract it
3.Install it using CMD

thanks, it worked

So, my phone is screwed, I am screwed someone pls help

I have ZE55ML 4gb version. Ok so, tried manually applying an ota update to my phone, i renamed it to MOFD_SUPDATE or whatever its supposed to be. I did not unroot or anything. It didnt work i got the error error executing updater binary in zip. So then I wiped my cach/dalvik, data, and system like a moron reboot into recovery and tried the update again... well it failed again... so I tried to just reboot my phone and now its stuck on the damn ASUS powered by android screen... I can turn it off by holding the power button and turn it on the same way and it will be stuck there. I would have been able to fix this by myself but I cant boot into bootloader/recovery. Power+volume up doesnt do and neither does Power+volume down.... So what do I do am I just ****ed?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

KnightmareZ3R0 said:
I have ZE55ML 4gb version. Ok so, tried manually applying an ota update to my phone, i renamed it to MOFD_SUPDATE or whatever its supposed to be. I did not unroot or anything. It didnt work i got the error error executing updater binary in zip. So then I wiped my cach/dalvik, data, and system like a moron reboot into recovery and tried the update again... well it failed again... so I tried to just reboot my phone and now its stuck on the damn ASUS powered by android screen... I can turn it off by holding the power button and turn it on the same way and it will be stuck there. I would have been able to fix this by myself but I cant boot into bootloader/recovery. Power+volume up doesnt do and neither does Power+volume down.... So what do I do am I just ****ed?
Click to expand...
Click to collapse
Hold power for about 10+ seconds and it will turn off.
Go to Original Android Developement and then find pre-rooted rom. The latest for the 551ML is 2.20.40.90, put the phone in bootloader mode and install the system.img file using fastboot.
Next time unroot...

Lol....

Bricked Z2 pro

Hello,
I have a z2 pro, and i wanted to change the ROM on it. Since it came with a modified ROM, i flash a stock ROM. I then unlocked bootloader sucessfully.
I transfered the new ROM to the phone and did a
Code:
fastboot flash recovery twrp.img
The phone booted with twrp correctly. I then did a wipe of system, cache and dalvik.
I tried to install the new ROM, but it prompted me the error "Unknown Command [log]". Having already installed a new ROM on another device, i remembered that disconnecting the usb cable or rebooting did the work, so i did both.
Now, the phone isn't recognized by my computer, so i can't redo the "fastboot flash", and when i go into recovery mode, it isn't TWRP that is loaded but this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How can i do to load TWRP again on the phone ?
Edit: I have shut down the phone and hold the power button, windows seems to recognize it as a cd drive. QFIL still doesn't change his status from "no port available"
Thanks

maxorus said:
Hello,
I have a z2 pro, and i wanted to change the ROM on it. Since it came with a modified ROM, i flash a stock ROM. I then unlocked bootloader sucessfully.
I transfered the new ROM to the phone and did a
The phone booted with twrp correctly. I then did a wipe of system, cache and dalvik.
I tried to install the new ROM, but it prompted me the error "Unknown Command [log]". Having already installed a new ROM on another device, i remembered that disconnecting the usb cable or rebooting did the work, so i did both.
Now, the phone isn't recognized by my computer, so i can't redo the "fastboot flash", and when i go into recovery mode, it isn't TWRP that is loaded but this
How can i do to load TWRP again on the phone ?
Edit: I have shut down the phone and hold the power button, windows seems to recognize it as a cd drive. QFIL still doesn't change his status from "no port available"
Thanks
Click to expand...
Click to collapse
This is Z2 Plus section.. please go to Z2pro section...
<Mod Edit>
Thread closed by OP request.

Flashed corrupted boot image and now can't can't boot into bootloader or recovery

Hi all.
Did a stupid thing.
I downloaded firmware file for my Galaxy S20 Ultra 5G (SM-G988B) Exynos as an MD5 file and extracted the file which came out as a .img file instead of .lz4 (which I overlooked until the damage was done!).
So not noticing the file was the wrong type, I used 7-Zip to tar it, copied it to my phone's SD card, then patched it with latest Magisk manager app. After this, I copied it back to my laptop and flashed this file using Odin.
Result: Phone goes to insecure boot warning screen but of course here it goes wrong:
It won't proceed to booting up
Power+volume up key combination or power alone do nothing no matter how long you hold them in
It boots to to same insecure boot warning screen if you use either power+volume down, or power+volume down+volume up key combination with cable unplugged. With cable plugged in it restarts to a charging icon, which promptly freezes, and stays on the screen even if you unplug the cable.
I have managed to get it into stock recovery by holding power+volume up+volume down randomly once in a while (usually it goes to insecure boot warning screen as usual), but if I select Reboot to bootloader, it does not manage to open download mode, and hangs on red text that says "entering fastboot mode"
QUESTION: If I can get it back into recovery, is there a way to re-flash stock firmware without download mode on this device using ADB (or any other method)?
Or is my phone a brick for good?

FIXED!
I managed to flash an Android 11 One UI 3.0 Beta via ADB sideload. While it didn't finish properly due to corrupted boot image and possibly not the prerequisite firmware, all was not lost. It ran okay right to the end, when it said "installation aborted".
Once I had got this far Download mode was working again, THANK HEAVENS!
Opened Odin, and flashed away. I'm now back on Stock firmware and didn't even lose my data thanks to the vbmeta_disabled file I flashed in USERDATA section.
Talk about getting out of Jail!

jesterpaul said:
FIXED!
I managed to flash an Android 11 One UI 3.0 Beta via ADB sideload. While it didn't finish properly due to corrupted boot image and possibly not the prerequisite firmware, all was not lost. It ran okay right to the end, when it said "installation aborted".
Once I had got this far Download mode was working again, THANK HEAVENS!
Opened Odin, and flashed away. I'm now back on Stock firmware and didn't even lose my data thanks to the vbmeta_disabled file I flashed in USERDATA section.
Talk about getting out of Jail!
Click to expand...
Click to collapse
will that method work on my note10+?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}