Develop Bugs

what does this mean?

can anyone tell me why my htc desire is stuck at this screen when i put in the battery?
-- 1 minute later --
well, i can't post a pic since not allowed to link until after 8 posts
it looks like a boot screen with 3 android dudes on the bottom.
any ideas?

Your stuck at the bootloader. Means that there is no boot.img. You've done something to it. Just flash a rom and it'll be fine. Don't forget to wipe data.

ok, thats positive news so far
the things is, i think its water damage but not much water at all really. just a bit from snowing while skiing.
the power and volume buttons do not seem to respond AND the ohone turns on by itself when i insert the battery.
is it still just a case of 'flash a ROM'? or is there more?

oh, and here is the image..... finally,
{
"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"
}

You don't have root or a custom recovery, correct? You just want to go back to the stock Froyo?

I think if the power buttons don't work it may be a bit of a problem selecting options in that menu, since the power button works as "select" in that menu.
I think you could boot to recovery using command prompt, but I am not 100% sure about that.
Also, are you rooted? Do you have a custom recovery installed?

What is 'Kali CM7 Apps2SD'? Is that just another name for S2E?

sonoftobit said:
What is 'Kali CM7 Apps2SD'? Is that just another name for S2E?
Click to expand...
Click to collapse
--- confusion ensues ---

my phone is NOT rooted NOR does it have anything custom.
i would simply like to go back to the original v2.2 that i had before this happened.
thanks for all suggestions and help

liquidmonkey said:
my phone is NOT rooted NOR does it have anything custom.
i would simply like to go back to the original v2.2 that i had before this happened.
thanks for all suggestions and help
Click to expand...
Click to collapse
Do you have a note of which rom was installed in your device? Is it carrier locked? Branded?

Select the newest RUU that fits your phone & carrier from http://shipped-roms.com/shipped/Bravo/. Extract the ROM, rename to PB99IMG.zip, place in root dir of sd-card and reboot. Should do everything else automatically.

don't really follow the whole ROM question?
my phone has android v2.2, is NOT branded, is NOT locked and NO rooting.

and i should add that i am sweden if that matters.

The file you download from shipped roms is an exe file. When you execute the file it will extract a couple of files to your harddrive. Among those is a file named ROM.zip. That's the one you're looking for.
When I extracted it the file was here C:\Users\*User Name*\AppData\Local\Temp\{722DC7D5-7B69-4EBC-B6FB-B63AE38C01DE}\{50F2F878-636A-496F-A7CB-544C067E0C4B}
The ROM on shipped ROMs are all the standard carriers version that are unmodified.

liquidmonkey said:
don't really follow the whole ROM question?
my phone has android v2.2, is NOT branded, is NOT locked and NO rooting.
Click to expand...
Click to collapse
Yeah but there are different versions of 2.2 depending on carriers etc, thats why I was asking!
I *think* any of the ROMS here with RUU at the beginning & WWE in the filename should work. (I am not 100% sure about this, as I have not had an official rom installed for AGES).
You will then have to follow sonoftobit's instructions I think, don't ask me how to extract the ROM though, as I don't know how to do it!
PS sonoftobit - Ignore this liquidmonkey!
If you go to the CM7 nightly thread and go to the 2nd post, Kali has a script for enabling Apps2SD. That is what I am running, tried to use S2E but it screwed things up royally and I had to restore a Nandroid!

Yeah, I had the same problems with S2E. I'm using DarkTremor App2SD now which has worked flawlessly ever since (both Sense Froyo and CM7). Also there's A2SDGUI for DarkTremor now which makes it even better.

StuMcBill said:
PS sonoftobit - Ignore this liquidmonkey!
Click to expand...
Click to collapse
why on earth would you write that?

so check it out!!!
i have had the phone off for a few more days and then put in the battery and BANG, it started up after a little while.
problem was that my battery only lasted 10 seconds so i was not able to fully test things.
then i put the battery in again and i was back where i started, crappy boot screen.
is there something in the phone that keeps memory of the boot screen and then disapates after a day which would explain why it started today.... or?

[Q] Defy is dead

I had a lot of issues this last days. I had Miui 2.3.7c froyo and I tried to free my defy from vodafone with this tutorial. Didn't work properly (probably my fault) and it brick my cell.
Trying lots of stuff I finaly booted it flashing to 2.3.6 (GB DEFY+). Everything was bugged and I tried to flash back to froyo, the only thing I could do was flashing to chinesse froyo rom with RSDLite.
Then the cell was working properly, but it was a horrible rom. So I flashed to CM9 ICS, it looked great. Unfortunately, my pc couldnt find my device while connected by USB, neither Wifi were working. I tried to free from vodafone flashing "ICS_Defy_softunlock_v1.3(EPU_U_00.59.01).zip" but didnt work.
Tired of making it worse for each time I try to fix it, I flashed to my original ROM (Vodafone 3.4.2) that totaly kill my cell.
Now I can only use bootloader (no recovery). All I want is to free my DEFY.
As you have seen, I'm not good at this things. All help will be appreciate
EDIT: now I've flash again to chinese rom, at least works.

With China ROM... restore nAndroid backup of ur stock rom and u should be good...
Sent from my MB525 using xda premium

nogoodusername said:
With China ROM... restore nAndroid backup of ur stock rom and u should be good...
Sent from my MB525 using xda premium
Click to expand...
Click to collapse
China recovery doesnt have that option (only wipe data, wipe cache and install update), I'll try installing 2ndinit.
Edit: Installed 2ndinit, dont have any option tu restore nAndroid backup from Custom Recovery (from 2ndinit).
Here a pic of the china recovery
{
"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"
}

Install 2nt init and press volume dn with th led on poweron. There go to custom recovery.

labsin said:
Install 2nt init and press volume dn with th led on poweron. There go to custom recovery.
Click to expand...
Click to collapse
I'm already in custom recovery, but nAndroid backup can only be done from Stock (not sure).
I've research and I think that installing Clockworkmod recovery will let me do nAndroid backup.
Help is appreciated, I'm noob at this.

I supose theres no way to go back to Vodafone 3.4.2. But I tried everything.
This are my choices:
Chinese Rom -> no google accounts(no market), no internet (only wifi), annoying sounds and interface.
Flashing to custom roms from chinese froyo (tried CM7 and CM9) -> no internet, no USB connection.
Upgrading to 2.3.6 -> no camera, no wifi (I have green len).
Flashing to custom roms from 2.3.6 -> no camera, no wifi, constant blocks.
What can I do? I only want a full working rom...

Best option is CM7 then. If you do it right you will have WIFI. probably forgot to wipe data/cache.
To get the best results: root, download cm7 (7.2.0rc cause it has latest kernel in it) and place on your sd, instal 2nt init (apk is in dev thread), reboot, power off, power on, press volume down when the led flashes, recovery > custom or latest (not stock). Then wipe data and cache from there, instal zip > the zip you downloaded earlier.
Reboot and off you go.
Sent from my MB525 using XDA

[Q]problem flashing custom roms

hey I need help with flashing custom roms,
I tried to go through different guides but everytime i flashed a rom (jj's hybrid/CM9 fxp134) my device just kept restarting itself only showing the "SONY" logo and the "ANDROID" logo one after the other....
im currently using the LT18i 4.1.B.0.431 Generic World Greece (photo attached)
{
"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"
}
Forgot to mention the my device is not rooted, because every method i tried for rooting, seemed to fail....
couldnt find a similar thread in the xperia arc forum
would appriciate your help......
if you need any other information, that will help you to help me, tell me what it is and i'll let you know
thnx

looks like you havent flashed any kernel if your still getting sony logo
flash the kernel recommended in ROM thread
connect phone to PC via usb while holding menu button and you should get a blue led on the side
bootloader unlock is required for this
also root is kind of important for all this so your best off figuring that out first

But if I already have The Stock kernel, why do i need to flash it again?

yotamson said:
But if I already have The Stock kernel, why do i need to flash it again?
Click to expand...
Click to collapse
Have you unlocked your bootloader? If not, you cannot flash custom ROMs, most custom ROMs require you to unlock the bootloader.
Also some custom ROMs require custom kernels to work. Hence, being on the stock kernel just doesn't help

Abhilesh7 said:
Have you unlocked your bootloader? If not, you cannot flash custom ROMs, most custom ROMs require you to unlock the bootloader.
Also some custom ROMs require custom kernels to work. Hence, being on the stock kernel just doesn't help
Click to expand...
Click to collapse
sounds like its the problem... what custom kernels do you recommend?
and how should i do it? flash kernel first and then the rom? or the opposite way?
i should mention again, that my bootloader is UNLOCKED.... but my device is not rooted, just cant seem to be able to root it... what do you think?

yotamson said:
sounds like its the problem... what custom kernels do you recommend?
and how should i do it? flash kernel first and then the rom? or the opposite way?
i should mention again, that my bootloader is UNLOCKED.... but my device is not rooted, just cant seem to be able to root it... what do you think?
Click to expand...
Click to collapse
Well, the threads with the custom ROMs would generally have a kernel they recommend to be used with the ROM. Use that kernel. Flash kernel through fastboot. Generally first the kernel is flashed and then the ROM, but in principle it doesnt matter since the phone looks for the kernel only at the time of boot.
Root doesn't have to do anything with ROMs. Most of the custom ROMs available are pre-rooted, so by flashing that ROM, you get root access. Similarly, if you flash stock ROM on a pre-rooted ROM, you will lose root access and will have to root using other methods.
Happy Flashing.
Tell me if you could successfully flash.

Abhilesh7 said:
Well, the threads with the custom ROMs would generally have a kernel they recommend to be used with the ROM. Use that kernel. Flash kernel through fastboot. Generally first the kernel is flashed and then the ROM, but in principle it doesnt matter since the phone looks for the kernel only at the time of boot.
Root doesn't have to do anything with ROMs. Most of the custom ROMs available are pre-rooted, so by flashing that ROM, you get root access. Similarly, if you flash stock ROM on a pre-rooted ROM, you will lose root access and will have to root using other methods.
Happy Flashing.
Tell me if you could successfully flash.
Click to expand...
Click to collapse
a long time has past since we discussed the issue, I just wanted to let you know, that I finally worked it out,
I downgraded my FW and kernel from .431 to .562... then, but only then i managed to root my device successfully, then i followed a guide of how to flash the CM9.1
and now Im happy to announce that Im the proud owner of an xperia arc s thats running CM9.1 fluently!
thanx to whoever tried to help!
next up, flashing the JJ's hybrid............

[Q] Wifi not working after CM10

I have been having wifi issues since I moved up to CM10/JB. I'm able to boot up just fine, but when I attempt to turn on wifi one of two things happens. Either the slider returns to off immediately or the wifi attempts to connect to no avail. The wifi worked just fine for a week or so after jump to JB, then it dropped out while I was travelling. I've seen some older, similar posts, but haven't seen any concrete solutions.
I have tried a variety of things, but nothing has seemed to work.
• Updated TWRP, FFF using smirkit
• Total wipe/unroot, flash back to stock
• Re-rooted
• Flashed different ROMS, kernels
Sorry if I come off a little noobish. I'm a bit out of practice. I haven't touched my kindle in a while, but now have a 13 year-old who would like to use it.
Could it be a hardware failure? Any suggestions, solutions or commiseration is greatly appreciated. Thank you!

monteith said:
I have been having wifi issues since I moved up to CM10/JB. I'm able to boot up just fine, but when I attempt to turn on wifi one of two things happens. Either the slider returns to off immediately or the wifi attempts to connect to no avail. The wifi worked just fine for a week or so after jump to JB, then it dropped out while I was travelling. I've seen some older, similar posts, but haven't seen any concrete solutions.
I have tried a variety of things, but nothing has seemed to work.
• Updated TWRP, FFF using smirkit
• Total wipe/unroot, flash back to stock
• Re-rooted
• Flashed different ROMS, kernels
Sorry if I come off a little noobish. I'm a bit out of practice. I haven't touched my kindle in a while, but now have a 13 year-old who would like to use it.
Could it be a hardware failure? Any suggestions, solutions or commiseration is greatly appreciated. Thank you!
Click to expand...
Click to collapse
"the slider returns to off immediately" or say "Turning Wi-Fi On..." forever,
Actually, the WiFi switch is grayed out (but still can push on/off)
The problem was started after the second day that I have flashed "cm-10.1-20130223-0102-otter-sgt7.zip".
I was using my File to play online game, all network connection was drop suddendly. I turn off the Wifi and try to reconnect and then my Wifi goes death up to now.
I tried to flash other build of CM-10/10.1, stock rom, apkp, etc. Wipe even external storage. The wifi still not work.
I am unable to confirm that is hardware problem or rom problem at this point.
.....or say.....a Kindle File with dead wifi is worse than a bricked one
{
"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"
}

Resetting battery stats helped with Wi-Fi (SGS II)
wunit said:
"the slider returns to off immediately" or say "Turning Wi-Fi On..." forever,
Actually, the WiFi switch is grayed out (but still can push on/off)
The problem was started after the second day that I have flashed "cm-10.1-20130223-0102-otter-sgt7.zip".
I was using my File to play online game, all network connection was drop suddendly. I turn off the Wifi and try to reconnect and then my Wifi goes death up to now.
I tried to flash other build of CM-10/10.1, stock rom, apkp, etc. Wipe even external storage. The wifi still not work.
Click to expand...
Click to collapse
fatbuccha said:
I also experience this before, i tried to reset fuel gauge if you're on siyah or dorimanx, problem went away after doing that. Try if it will also work on you, im on wanam lite leaked version of jb and never encounter the problem again
Sent from my GT-N8000 using xda app-developers app
Click to expand...
Click to collapse
As found in another forum, I desperately tried one last thing: booted to recovery and cleared battery stats. My Wi-Fi can be turned on and works! What a magic...
Things had broken after first time flashing rooted kernel and ROM (currently Kernel_Siyah-Dorimanx-V9.0-[17-39]-[05-03]-JB-CM-AOKP-SGII-PWR-CORE and cm-10.1-20130304-NIGHTLY-i9100)

This is hella old thread, but it slightly helped me when converting a Kindle to cm11. Flashing none of the recent 2015 nightlies had wifi. Flashed the M12 from 2014 and wifi worked, then dirty flashed the newest and wifi still worked.

[Q] OS takes ages to boot

Hello, I'm new to the forum as a user but i read lots of information in here.
Thank you for all your help over the years =]
Unfortunately, now i met a problem i can't fix on my own.
My friend bought HTC One m8 in china and everything was in Chinese so he installed some app that made some of it in english.
he asked me to install gapps. After i had installed the wrong gapps most of the os didn't work.
Re-installing the right gapps didn't help so i decided to flash it with Mike1986's custom rom. it took the phone 10 minutes to boot, maybe even more since it got stuck in recovery for a while.
everything looked ok, worked fine and i decided to reboot it again to see if the rebooting time is ok.
it took it 5 minutes to reboot, and all the time it showed the chinese company's logo (first picture).
I thought it might be a recovery problem so i installed PhilZ Touch recovery. It didn't solve it.
After minor research i found that similar problem can occur due to wrong rom and firmware relations.
i tried to find what is my firmware now but couldn't.
so i ask for your help. what are the implication of not updating the firmware, and what can i do to update the firmware.
i tried returning to stock but i don't know how to find the right RUU.
I'm open to options, even leaving the current firmware and flashing a rom which works with it.
PS. additional information:
before flashing the new rom the phone did OTA and the file name is:
OTA_M8_UHL_K44_SENSE60_HTCCN_CHS_CU_1.83.1402.12-1.60.1402.3_release_385801.zip
Click to expand...
Click to collapse
I couldn't install it for some reason. failed every time.
{
"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"
}

mkuts said:
Hello, I'm new to the forum as a user but i read lots of information in here.
Thank you for all your help over the years =]
Unfortunately, now i met a problem i can't fix on my own.
My friend bought HTC One m8 in china and everything was in Chinese so he installed some app that made some of it in english.
he asked me to install gapps. After i had installed the wrong gapps most of the os didn't work.
Re-installing the right gapps didn't help so i decided to flash it with Mike1986's custom rom. it took the phone 10 minutes to boot, maybe even more since it got stuck in recovery for a while.
everything looked ok, worked fine and i decided to reboot it again to see if the rebooting time is ok.
it took it 5 minutes to reboot, and all the time it showed the chinese company's logo (first picture).
I thought it might be a recovery problem so i installed PhilZ Touch recovery. It didn't solve it.
After minor research i found that similar problem can occur due to wrong rom and firmware relations.
i tried to find what is my firmware now but couldn't.
so i ask for your help. what are the implication of not updating the firmware, and what can i do to update the firmware.
i tried returning to stock but i don't know how to find the right RUU.
I'm open to options, even leaving the current firmware and flashing a rom which works with it.
PS. additional information:
before flashing the new rom the phone did OTA and the file name is:
I couldn't install it for some reason. failed every time.
Click to expand...
Click to collapse
If i'm correct the issue is
a. Takes to long to boot 6min - 10min first boot.
and b.flash failure
okay, flash back to TWRP, you have a chinese version i believe that's the international variant.
You might have Android 4.4.2 installed and you flashed 4.4.3 ROM which requires the updated firmware.
The effect of that will be LONGER bootup times up to 10minutes, this isn't new.
Try this ROM, comes pre loaded with a GUI that you select what phone you have and on bootup you select the Carrier you own/have.
>Link Related: http://forum.xda-developers.com/showthread.php?t=2743524
Let me know how it goes. It has the GAPPS preloaded.

i4GS said:
If i'm correct the issue is
Click to expand...
Click to collapse
Please don't quote long posts (especially with photos).

Yeah , i kinda noticed why afterwards. Sorry about that.

mkuts said:
so i ask for your help. what are the implication of not updating the firmware, and what can i do to update the firmware.
Click to expand...
Click to collapse
You have old firmware, and this can be confirmed since you are on hboot 3.16.
Updating firmware is discussed on the following post, including a link to detailed instructions on how to flash firmware.
http://forum.xda-developers.com/showpost.php?p=54408500&postcount=9592

thanks
Thank you both for the comments.
Eventually i decided not to mess with his phone and just installed the latest Cyanogenmod that, for some reason, worked perfectly.
I Will though use it on my phone =]
So thanks again

mkuts said:
Eventually i decided not to mess with his phone and just installed the latest Cyanogenmod that, for some reason, worked perfectly.
Click to expand...
Click to collapse
The reason CM works is because the firmware issue you were experiencing (causing long boot time) only affects Sense ROMs.