Develop Bugs

Defy 2ndInit

Do this app install bootmenu? And it is safe to download? I'd like to have defy multi touch enables so I need thay first..
Send from my MB525 motodefy.

Yes.
Sent from my MB525 using XDA App

I installed it just to have a dabble. It seems to work well but once you set the boot back to default the only way i could get back in to clockworkmod was to uninstall 2ndinit and reinstall it so maybe i was doing something wrong.

I uninstalled it, but there is still blue light when boot. How to get rid of it?

Uninstalling the app wont remove Bootmenu. You have install the 2ndinit app and thereafter uninstall it from within the app itself.
Sent from Android 2.3.7

ryan8r said:
Uninstalling the app wont remove Bootmenu. You have install the 2ndinit app and thereafter uninstall it from within the app itself.
Sent from Android 2.3.7
Click to expand...
Click to collapse
Im not that stupido I uninstalled it with using 2nd init....

Motodefyuser said:
Im not that stupido I uninstalled it with using 2nd init....
Click to expand...
Click to collapse
Can you still enter the boot menu when the blue led goes on?
Sent from Android 2.3.7

ryan8r said:
Can you still enter the boot menu when the blue led goes on?
Sent from Android 2.3.7
Click to expand...
Click to collapse
Yes. But there reads some errors like missing something. And when I try to uninstall bootmenu from bootmenu it's still there after reboot..

Motodefyuser said:
Yes. But there reads some errors like missing something. And when I try to uninstall bootmenu from bootmenu it's still there after reboot..
Click to expand...
Click to collapse
Boot
System
Recovery
Tools
Reboot system
___________________________________________
E:Missing bitmap icon_error
(Code -1)
E:Missing bitmap indeterminate1
(Code -1)
E:Missing bitmap indeterminate2
(Code -1)
E:Missing bitmap indeterminate3
(Code -1)
E:Missing bitmap indeterminate4
(Code -1)
E:Missing bitmap indeterminate5
(Code -1)
E:Missing bitmap indeterminate6
(Code -1)
E:Missing bitmap progress_empty
(Code -1)
E:Missing bitmap progress_fill
(Code -1
That's what there reads on yellow color.

try to install it again and uninstall it after a restart. it could fix the problem.

Motodefyuser said:
I uninstalled it, but there is still blue light when boot. How to get rid of it?
Click to expand...
Click to collapse
You need to flash a full SBF to get rid of the blue light and boot menu bits that are left over

[UNBRICK][GUIDE][Q&A] How to solve a "Brick" for n00bs

{
"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"
}
Since the GS3 has become a popular device, the need to root and install custom firmware has risen!
We have a lot of user who dont take the time to read and sometimes make an oopsie when flashing
Knowing terms and acronyms is a MUST for XDA users. Users are also advised to take precaution when flashing.
Enough with the chit-chat here is what you should know about "bricked" phones.
IS MY PHONE BRICKED??
Lets identify YOUR brick :highfive:
1.SOFT-BRICKED : An operable phone. Boots up, but either stuck on the splash screen or the boot animation.
2.HARD-BRICKED :A hard brick describes a smart phone, with corrupted firmware or a hardware problem, that can no longer function.
This means it doesnt function at all. It doesnt boot up or does anything, just like a brick.
Now that you've identified your phone lets look below for a fix
IF YOUR PHONE MATCHES OPTION 1 LOOK HERE!!
A soft brick is easily fixed in most cases, here is what you can do to fix your phone!
-Boot into Recovery (Vol Up + Home Button + Power Button) and wipe your data/cache/delvik cache and factory reset and start all over.
-If Recovery fails, try booting into Download Mode (Vol Down + Home Button + Power Button) and use Odin to get into stock firmware and start again.
(if youre using a Mac, Linux or Ubuntu Heimdall can be used to flash stock firmware)
-Also make sure the downloaded ROM/GApps are not corrupt when youre flashing. You can do this by checking the MD5.
-If youre getting a "STATUS 7" error, please update your recovery, or update your bootloader.
More info on Root/ROMs/Mods Here
IF YOUR PHONE MATCHES OPTION 2 LOOK HERE!!
A Hard Brick.... the death of a phone.
-If you flashed international firmware, there is one guide that might help you found HERE .
-If that guide doesnt get your phone back up the only service available is JTAG found HERE
Please search before posting, there is 5 million users on XDA, someone else has had your problem and likely posted about it.
Everyting can be found in Q&A section on XDA or by using the search feature.
This guide was made to be read or be directed to for "bricked" phone threads. If mods feel the need it is not necessary please close
​

OP updated

1st. boom.
nicely done.

xBeerdroiDx said:
1st. boom.
nicely done.
Click to expand...
Click to collapse
2nd is the new first!
(Actually pm'd instead of posting in thread but now feel forced to )
Sent from my SGH-I747 using xda app-developers app

If I brick a phone with a brick...I'm option 3 ???

hednik said:
If I brick a phone with a brick...I'm option 3 ???
Click to expand...
Click to collapse
Hahaha!!!!
That leaves you with no option lol :thumbup:
Sent from my SGH-I747 using Tapatalk 2

Thanks:good:

my phone dont even go to download mode it cant do nothing

barla88 said:
my phone dont even go to download mode it cant do nothing
Click to expand...
Click to collapse
Mine too, take a brick and the broken

Help! In mid unbricking
I have a rooted Galaxy S3. Rooted it a few years ago when it came off warranty. Samsung pushed a software update last night that totally froze my phone - won't get past the Samsung splash screen on boot. AT&T kindly offered to sell me a new phone but declined any other help. I went to trusty XDA and found this page. The phone is plugged into my work laptop for power via USB. I did down volume - home - start and it booted and asked if I wanted to boot a custom OS or standard. I clicked volume up for custom (because it was rooted) and it now shows a few lines of status, the android logo, "downloading ...", "Do not turn off target !!" My laptop does not show anything on USB. It is not prepared to do anything with the phone. It has been like this for half an hour. Is it doing anything? Wait how long? The "Do not turn off target!!" is ominous. What to do now?

What operating system is on your laptop? Did you install the proper USB drivers for the phone?
Do you see anything about warranty bit in the screen where it says "Do not turn off..."?
I recommend that you unplug the phone, remove the battery, replace the battery, and charge up the phone completely.
When you have the USB drivers installed, open Odin 3.07, put the phone in download mode, and make sure it appears in Odin on a com port. It could be com4,5,6, etc.

Soft Bricked
I got a notification for a software update from ATT, I was dumb and downloaded it without thinking and installed it, then when my phone went to reboot it would boot past the Samsung logo to the Samsung Galaxy S3 logo and then just shuts off. I booted into Recovery mode, and when I did that, it displayed red text before the normal Manual mode stuff -
Code:
E: failed to mount /data (Invalid argument)
E:Can't mount /data/fota/ipth-muc.prop
E:failed to mount /data (Invalid argument)
E:Can't mount /data/fota/ipth-muc.prop
E:failed to mount /data (Invalid argument)
E:Can't mount /data/fota/ipth-muc.prop
Unfortunately I can't remember if it was giving me this error before I started trying to fix the problem.
When I attempted to wipe the cache, it says the wipe is successful, but before rebooting it gives me "E: failed to mount /data (Invalid argument)" again. My problem isn't solved and it continues to shut off after the Samsung Galaxy S3 logo.
I then have tried multiple times to do a Factory Reset, and what displays is -
Code:
-- Wiping data...
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p15
Formatting /cache...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p17
Data wipe complete.
E: failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E: failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E: failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E: failed to mount /cache (Invalid argument)
And again, it will only boot to the Samsung Galaxy S3 logo.
I've revisted it a few hours later because I had work, now I don't get any of the red text but I have the same problems.
I would try using Kies/Odin to repair this, but the MicroUSB port does not work. Would I be able to put new firmware/OS on my SD card to repair it? Or am I **** out of luck until my contract goes up in November?

Optimus G Pro (E980) can't use SD or ADB

I got this phone updated to 4.4.2 about a month ago. I followed the root guide immediately and got root. Since then it is no longer recognized by any of my computers. I have a Vista 32, XP, Windows7 64, and I even tried Ubuntu Live! CD. Nothing recognizes this device. When I insert an SD card, it shows "SD Card Inserted" but will not mount. I tried the NextApp SDFix and it didn't help. Also, the stock "Home" launcher crashes and the phone only runs because of Nova Launcher that i loaded from play store.
I couldn't get custom recovery to load so I am in stock recovery and when I reboot to stock it gives me this message:
E:missing bitmap stage_empty
(Code -1)
E:missing bitmap stage_fill
(Code -1)
I am on rooted stock 4.4.2
Kernel 3.4.0
Software Version E98020g
Many thanks peoples.

Same here.. cant get any custom recovery to work running stock kit kat.. would be nice to get some help on this.. can it be done?

Tried to go back stock, and got stuck. Sprint variant

As the title says. I tried to go back to stock and got stuck. I was new, and still am to this whole thing to a degree. I had a friend who helped me unlock, root, and slap on a custom rom. I learned about it in the process, but here is my problem. I tried to go back to stock, and locked my bootloader before I slapped on the stock rom. And I wiped the phone, cache, and dalvik etc.. well the OS is gone too. I would like to be able to use my SD card to load the stock rom but it wont read the Ext sd card. Brand new, 3rd diff card. I tried to use adb, but it wont see the device in the command prompt. I have the sdk dev installed and universal adb drivers as well as htc sync. I've rebooted multiple times to make sure drivers are useful. The apk installer can see my phone, adb commands do NOT. So for the moment my m9 is a paper weight, I've tried to read and follow the searches I've run across on here but I seem to be stuck. Phone boots, and stops at the white boot screen. I am S-ON and relocked.
This is the info it shows me
Radio-1.11
OS 1.32.651.30
When I reboot it goes into a white screen. gives options to reboot into bootloader, reboot to recovery etc... If I reboot to recovery it shows it is missing items
E:missing bitmap oem_unlock_bg
(Code -1)
E:missing bitmap oem_unlock_bg_yes
(Code-1)
E:missing bitmap oem_unlock_bg_no
(Code-1)
handle_cota_install: install cwpkg to /data/cwtemp/cwpg.zip
handle_cota_install: install cwprop to /data/data/cwtemp/cwprop
E: fail to open file: /sys/devices/platform/android_usb/hostmode
Write host_mode error
handle_cota_install: No CW files. Skip installation
I can't access my drive on the phone to store files, the only thing I can use is my sd card since adb wont see devices. And my phone wont read from the SD card ( Tried 3 diff ones ). And if I goto apply from sd card I get
E: Find no match PARTITION: for package path /sdcard/ptt.zip
E: Unknown volume for path []
E: Can't mount
E: failed to open last_install: No such file or directory
Finding update package....
Opening update package....
E: Failed to map file
-----------
But if I goto download mode, the pc will see the phone though APK Installer through taskbar notification. But not adb.:silly:
Sorry if I caused some of you do go "Seriously dude??!!" This is a headache, this I do know. I just want to either get this phone working again through stock ) Right now it's just a bunch of load up to bootloader screen and stop. No OS. And once again, wont read rom from sd card, wont even see sd. Says it can't access it.
And if I goto recovery mode it tells me that same junk about No CW files. skip installation. Am I as screwed as it sounds?

aimjewels said:
As the title says. I tried to go back to stock and got stuck. I was new, and still am to this whole thing to a degree. I had a friend who helped me unlock, root, and slap on a custom rom. I learned about it in the process, but here is my problem. I tried to go back to stock, and locked my bootloader before I slapped on the stock rom. And I wiped the phone, cache, and dalvik etc.. well the OS is gone too. I would like to be able to use my SD card to load the stock rom but it wont read the Ext sd card. Brand new, 3rd diff card. I tried to use adb, but it wont see the device in the command prompt. I have the sdk dev installed and universal adb drivers as well as htc sync. I've rebooted multiple times to make sure drivers are useful. The apk installer can see my phone, adb commands do NOT. So for the moment my m9 is a paper weight, I've tried to read and follow the searches I've run across on here but I seem to be stuck. Phone boots, and stops at the white boot screen. I am S-ON and relocked.
This is the info it shows me
Radio-1.11
OS 1.32.651.30
When I reboot it goes into a white screen. gives options to reboot into bootloader, reboot to recovery etc... If I reboot to recovery it shows it is missing items
E:missing bitmap oem_unlock_bg
(Code -1)
E:missing bitmap oem_unlock_bg_yes
(Code-1)
E:missing bitmap oem_unlock_bg_no
(Code-1)
handle_cota_install: install cwpkg to /data/cwtemp/cwpg.zip
handle_cota_install: install cwprop to /data/data/cwtemp/cwprop
E: fail to open file: /sys/devices/platform/android_usb/hostmode
Write host_mode error
handle_cota_install: No CW files. Skip installation
I can't access my drive on the phone to store files, the only thing I can use is my sd card since adb wont see devices. And my phone wont read from the SD card ( Tried 3 diff ones ). And if I goto apply from sd card I get
E: Find no match PARTITION: for package path /sdcard/ptt.zip
E: Unknown volume for path []
E: Can't mount
E: failed to open last_install: No such file or directory
Finding update package....
Opening update package....
E: Failed to map file
-----------
But if I goto download mode, the pc will see the phone though APK Installer through taskbar notification. But not adb.:silly:
Sorry if I caused some of you do go "Seriously dude??!!" This is a headache, this I do know. I just want to either get this phone working again through stock ) Right now it's just a bunch of load up to bootloader screen and stop. No OS. And once again, wont read rom from sd card, wont even see sd. Says it can't access it.
And if I goto recovery mode it tells me that same junk about No CW files. skip installation. Am I as screwed as it sounds?
Click to expand...
Click to collapse
Use the full 1.32.651.30 RUU here
(originally from this thread)
I highly recommend you use the 1.32.651.30 one and NOT the newer 2.xx ones, because in the 2.x.xxx.x ones, (Android 5.1), a new setting has been implemented "Settings -> Developer Options -> OEM unlocking", if that is not checked, and it's not by default (and this can only be done during the booted ROM), you will not be able to unlock your bootloader again!! (so be careful!!)
EDIT: oh, and as far as I know, the M9 (unlike it's predecessors) doesnt need a relocked bootloader for RUU, even with S-ON

nkk71 said:
Use the full 1.32.651.30 RUU here
(originally from this thread)
I highly recommend you use the 1.32.651.30 one and NOT the newer 2.xx ones, because in the 2.x.xxx.x ones, (Android 5.1), a new setting has been implemented "Settings -> Developer Options -> OEM unlocking", if that is not checked, and it's not by default (and this can only be done during the booted ROM), you will not be able to unlock your bootloader again!! (so be careful!!)
EDIT: oh, and as far as I know, the M9 (unlike it's predecessors) doesnt need a relocked bootloader for RUU, even with S-ON
Click to expand...
Click to collapse
Well now the problem is that everything goes fine up until it comes time to update the rom. I get an error code of 155 an unknown error. It tells me to use the correct ROM Utility and try again. But This is the correct one I'm using. I am a bit confused now. I have tried even reinstalling some drivers and such all over again just to make sure. And rebooted. It gives an error on the same part every time. It doesn't even get to Step 2/4
But on the plus side it does still respond to the reboot to bootloader command. The screen the phone gets stuck on otherwise...is the install screen. The arrows are not spinning and the progress bar has no progress. That is usually when I get a fastboot.exe error

Boot loop on stock firmware?

My phone is on official software and has been stuck in a boot loop for probably nearly a year. It's been collecting dust and I'm looking to use it as at least a media player. I don't know why or how this happened, since I haven't even flashed a custom ROM on it (this isn't the one in my sig, I broke that one and this is the replacement).
Anyways, to get to the point. How can I make this phone usable again? It's S-ON, HBOOT 3.19.0.0000.
Can I still use ODIN to flash a stock rom, even though it's S-ON and not rooted?

Also, if it helps, in the stock recovery it says:
Android system recovery <3e>
LRX22G release-keys
E: missing bitmap oem_unlock_bg
(Code-1)
E: missing bitmap oem_unlock_bg_yes
(Code-1)
E: missing bitmap oem_unlock_bg_no
(Code-1)
Write host_mode success
handle_cota_install: Can't mount /sdcard, 1 times
handle_cota_install: Can't mount /sdcard, 2 times
handle_cota_install: Can't mount /sdcard, 3 times
handle_cota_install: Can't mount /sdcard, 4 times
handle_cota_install: Can't mount /sdcard, 5 times
Factory resetting doesn't do anything at all.

xLoveHateLegend said:
Can I still use ODIN to flash a stock rom, even though it's S-ON and not rooted?
Click to expand...
Click to collapse
ODIN is Samsung specific, it doesn't work on HTC devices.
The most you can probably do is run the RUU, if there is one for your M8 version. If RUU doesn't fix it, you are probably looking at a hardware (emmc) failure. Which the symptoms also suggest to me.

redpoint73 said:
ODIN is Samsung specific, it doesn't work on HTC devices.
The most you can probably do is run the RUU, if there is one for your M8 version. If RUU doesn't fix it, you are probably looking at a hardware (emmc) failure. Which the symptoms also suggest to me.
Click to expand...
Click to collapse
Crap! You're right. Can you tell I've switched devices way too many times? Haha.
I'll give RUU a shot tonight. I'm hoping it's not hardware failure, because I feel like with Sprint, it's way too late to make a claim now (also screen has a hairline crack, so they wouldn't replace it due to physical damage).

If its the Sprint version M8, the RUU is here (near the bottom of the webpage): http://www.htc.com/us/support/htc-one-m8-sprint/news/
Unless you have the Harman Kardon Edition, in which case, its here: http://www.htc.com/us/support/htc-one-m8-harman-kardon-edition-sprint/news/