Develop Bugs

What is this screen, and how do I stop this from happening?

I'm sure this has been asked a bunch of times, but I don't know what this screen is called, therefore I can't search for a solution.
When I first looked at my phone (used) before I bought it, it didn't do this. And then I brought it to the Verizon store to get a new SIM card. The salesperson reset the phone for me. The battery died on the way home while I was using it and it shut down. Now, every time I turn on the phone it shows this screen. If I pull the battery and boot into upgrade mode (volume down + power) it will boot, but it resets data (all of my stuff is gone). It will do this every time. I suspect the file system has become corrupted due to the improper shut down.
So, how can I solve this? Do I need to reflash everything through Odin, or can I sort of just push /system and /data to it via adb? I'd like to stick with stock ICS for now.
I'm coming from a Samsung Fascinate. I've owned a Galaxy Nexus before, but only for a few weeks. I have quite a bit of experience with all of this stuff, so any basic info should be easy for me to understand. I just don't know what this screen is and why it's appearing.
EDIT: It would probably help if I posted the photo
{
"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"
}

jmattp said:
I'm sure this has been asked a bunch of times, but I don't know what this screen is called, therefore I can't search for a solution.
When I first looked at my phone (used) before I bought it, it didn't do this. And then I brought it to the Verizon store to get a new SIM card. The salesperson reset the phone for me. The battery died on the way home while I was using it and it shut down. Now, every time I turn on the phone it shows this screen. If I pull the battery and boot into upgrade mode (volume down + power) it will boot, but it resets data (all of my stuff is gone). It will do this every time. I suspect the file system has become corrupted due to the improper shut down.
So, how can I solve this? Do I need to reflash everything through Odin, or can I sort of just push /system and /data to it via adb? I'd like to stick with stock ICS for now.
I'm coming from a Samsung Fascinate. I've owned a Galaxy Nexus before, but only for a few weeks. I have quite a bit of experience with all of this stuff, so any basic info should be easy for me to understand. I just don't know what this screen is and why it's appearing.
EDIT: It would probably help if I posted the photo
Click to expand...
Click to collapse
Its the stock Recovery screen. I would just do a fresh install using Odin
Sent from my Galaxy Nexus using XDA

That's the stock recovery screen? Funny.. I've never seen it. I've seen fastboot a bunch of times, and Clockwork recovery (and other recoveries) but I assumed that was some kind of looping loading screen or something.
I'm resetting it to stock through the terminal, pushing everything in fastboot. I want the OTA 4.0.4 update. I should be able to get that with the stock ROM and OEM locked bootloader right?
Thanks for telling me what that screen was. I had no idea.
EDIT: Oh, I was also wondering if the improper shutdown caused this problem, or if something could be wrong with the device that I should be worried about.

jmattp said:
That's the stock recovery screen? Funny.. I've never seen it. I've seen fastboot a bunch of times, and Clockwork recovery (and other recoveries) but I assumed that was some kind of looping loading screen or something.
I'm resetting it to stock through the terminal, pushing everything in fastboot. I want the OTA 4.0.4 update. I should be able to get that with the stock ROM and OEM locked bootloader right?
Thanks for telling me what that screen was. I had no idea.
EDIT: Oh, I was also wondering if the improper shutdown caused this problem, or if something could be wrong with the device that I should be worried about.
Click to expand...
Click to collapse
If you can get into fastboot and recovery then you don't have any serious problems.
Sent from my Galaxy Nexus using XDA

Thanks. After returning to stock, everything seems fine. I guess the battery dying borked something. I hope this doesn't happen every time the battery dies. (I don't plan on letting it die... but in the event that it does, it will suck)

jmattp said:
Thanks. After returning to stock, everything seems fine. I guess the battery dying borked something. I hope this doesn't happen every time the battery dies. (I don't plan on letting it die... but in the event that it does, it will suck)
Click to expand...
Click to collapse
It must've been something else, I've had the battery die a few times, its booted up fine. Glad you fixed it.
Sent from my Galaxy Nexus using XDA

[Q] Help please!

Hi guys... just flashed another ROM, as I have many times, but this time I'm stuck on the HTC screen. The phone doesn't boot past this and forcing a restart by holding the power key and volume down won't get the phone to boot into recovery. Does anyone know any way of forcing the device to boot into recovery. I've obviously cocked up somewhere. Any help would be much appreciated. Thank you.

grahamkdt said:
Hi guys... just flashed another ROM, as I have many times, but this time I'm stuck on the HTC screen. The phone doesn't boot past this and forcing a restart by holding the power key and volume down won't get the phone to boot into recovery. Does anyone know any way of forcing the device to boot into recovery. I've obviously cocked up somewhere. Any help would be much appreciated. Thank you.
Click to expand...
Click to collapse
have you flashed the boot.img!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?
{
"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"
}
god!! today i've repeated this step 100000 times!!! why fon't you read instead of asking every stupid single question explained in the rom thread!?

matt95 said:
have you flashed the boot.img!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?!?
god!! today i've repeated this step 100000 times!!! why fon't you read instead of asking every stupid single question explained in the rom thread!?
Click to expand...
Click to collapse
Never mind... I've sorted it and YES I've flashed the boot image - I'm not a complete knob head... just partially!

grahamkdt said:
Never mind... I've sorted it and YES I've flashed the boot image - I'm not a complete knob head... just partially!
Click to expand...
Click to collapse
oh finally somebody that did it, in that case sorry for ma inpatience so, which rom are you trying to flash?

Did you erase the cache via fastboot to fix it? I had the same issue.
Sent from my HTC One X using xda premium

stebsgb1 said:
Did you erase the cache via fastboot to fix it? I had the same issue.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
No... I kept the power button and volume down pressed even after the device restarted, and it then restarted again and booted into recovery. Never had an issue before trying to access recovery so thought it was a bit strange. It was probably just a fluke case. I understand why people jump to the "Did you flash the boot image / clear the cache" reply, but I'm not a novice here. I've been flashing ROM's since 2007!
Thanks for the replies any way

grahamkdt said:
No... I kept the power button and volume down pressed even after the device restarted, and it then restarted again and booted into recovery. Never had an issue before trying to access recovery so thought it was a bit strange. It was probably just a fluke case. I understand why people jump to the "Did you flash the boot image / clear the cache" reply, but I'm not a novice here. I've been flashing ROM's since 2007!
Thanks for the replies any way
Click to expand...
Click to collapse
I always have to keep the power button and volume pressed down even after the device restarted, else it just goes over to start the rom automatically. Probably that was ur problem too.

[Q] Did something very bad! OPPO FIND 7

I was going about flashing my Oppo Find 7 not 7A, succesfully rooted, flashed TWRP, booted into Cyanogenmod 11 successfully. I then went on and attempted to flash cyanogenmod 11s(one plus one system dump) on my Find 7, rebooted, One plus one was split into two on each side of screen, when attempting to go into recovery it was not there anymore and screen was just black. I tried putting back original recovery no luck and tried reflashing with TWRP but still no luck and phone does not boot into anything when turning on. Any help would be deeply appreciated since I can no longer use my new phone.

When completely off, hold power and up, that should put it in fastboot. Can you confirm whether this works or not?
Sent from my Find7 using XDA Premium 4 mobile app

Hey Chewbyte thanks for the response, I have managed to get CWM recovery on it but since I tried flashing CM 11s which wasnt made for the Find7, upon boot the screen is split and it says one plus and nothing occurs. I even tried reflashing cyano 11 but still nothing happens when i try to reboot. My fastboot is also the cyano little guys face. I am not sure what to try next

coscos17 said:
Hey Chewbyte thanks for the response, I have managed to get CWM recovery on it but since I tried flashing CM 11s which wasnt made for the Find7, upon boot the screen is split and it says one plus and nothing occurs. I even tried reflashing cyano 11 but still nothing happens when i try to reboot. My fastboot is also the cyano little guys face. I am not sure what to try next
Click to expand...
Click to collapse
Even if the graphics are messed up in fastboot, it still could work fine.
Download the AndroidSDKSlimCustom here https://www.dropbox.com/s/41p7peig4wt5kav/AndroidSDKSlimCustom.zip
Navigate into platform-tools, hold shift anywhere in that directory and right click while holding shift. Click 'Open command window here'
Turn off your phone completely, take the battery out to be sure, and hold power and volume up until you see something appear on the screen.
Connect the phone via usb, go back to the command window that opened and type
Code:
fastboot devices
If you're lucky you'll get something like 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"
}
This means you can then flash TWRP, get into that recovery, wipe everything and ADB sideload a fresh CM nightly (actually made for the find 7!) which you can find here:
http://download.cyanogenmod.com/?device=find7
Let me know how you get on.

I had done that before but still same result, even in recovery the screen looks like it was shifted.

GOT EM! SOLVED!
For anyone else who has this problem use this!
I cant post links cause i am a noob
but in oppo forums look for these
threads/find-7-x9076-bricked-need-help.18112/
/threads/brick-my-oppo-find-7-x9076-doesnt-load-any-recovery.17906/
com/threads/stock-recovery-for-find-7-7a.17397/
and when in stock recovery i flashed X9006&X9076ColorOS_V1.2.1i_full.zip
and BOOM it worked!
Once again thank you Chewbyte for taking the time to answer and try to help me I appreciate it!!

No problem friend, I'm glad you managed to fix it.
Sent from my Find7 using XDA Premium 4 mobile app

just one more thing i need some help with. When i struggled with the recoverys I think i wiped everything. So now when I open the camera it says storage unavaible? any ideas?

coscos17 said:
just one more thing i need some help with. When i struggled with the recoverys I think i wiped everything. So now when I open the camera it says storage unavaible? any ideas?
Click to expand...
Click to collapse
I googled your issue around a bit. Try factory reset/clear cache.

Rooted Elephone P8000 stucks at Boot Logo after OTA Update

Hi there,
The phone is rooted.
I've proceeded with the latest update today (~12mb size), don't remember the exact version.
It said it fixes some system bugs, etc.
After the update installed the phone won't load, stucks on the changing color logo.
Cannot access the recovery mode option in the boot menu (Vol+Power), says "no command", if press and hold Vol+ and Power again the phone restarts and enter the boot logo again.
Has anyone ideas how this can be fixed?

vagifn said:
Hi there,
The phone is rooted.
I've proceeded with the latest update today (~12mb size), don't remember the exact version.
It said it fixes some system bugs, etc.
After the update installed the phone won't load, stucks on the changing color logo.
Cannot access the recovery mode option in the boot menu (Vol+Power), says "no command", if press and hold Vol+ and Power again the phone restarts and enter the boot logo again.
Has anyone ideas how this can be fixed?
Click to expand...
Click to collapse
See http://forum.xda-developers.com/elephone-p8000/help/boot-loop-ota-upgrade-t3246203.
Post #16 describes how get into recovery from the 'no command' screen, and my post #12 describes how I managed to get it flashed using the SP Flashtool.
(Note my point no,5 - all I needed to do is press 'Download' first, THEN attach the powered off phone.)
Good luck!

kevvyboy said:
See http://forum.xda-developers.com/elephone-p8000/help/boot-loop-ota-upgrade-t3246203.
Post #16 describes how get into recovery from the 'no command' screen, and my post #12 describes how I managed to get it flashed using the SP Flashtool.
(Note my point no,5 - all I needed to do is press 'Download' first, THEN attach the powered off phone.)
Good luck!
Click to expand...
Click to collapse
Thanks a lot fot pointing this out.
Managed to get the recovery options menu.
However wiping the cache didn't help.
After doing the "root integrity check" got 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"
}
do you think this can be fixed w/o reflashing an entire rom?

Oooh. Brighter minds than mine might correct me, but I think the bootloop is only fixed with a ROM flash

kevvyboy said:
Oooh. Brighter minds than mine might correct me, but I think the bootloop is only fixed with a ROM flash
Click to expand...
Click to collapse
Sad... anyway would you please direct me to where I can download the flash tool and stock ROM? Thanks.

kevvyboy said:
Oooh. Brighter minds than mine might correct me, but I think the bootloop is only fixed with a ROM flash
Click to expand...
Click to collapse
Actually, what you need to do is format the data partition or write the empty data.img file over the data partition which in effect does the same thing. And the later one is also what happens when your download entire rom using sp flash.

pitrus- said:
Actually, what you need to do is format the data partition or write the empty data.img file over the data partition which in effect does the same thing. And the later one is also what happens when your download entire rom using sp flash.
Click to expand...
Click to collapse
I've proceeded with "wipe data/factory reset" option - no effect...or are we talking about different things?

vagifn said:
I've proceeded with "wipe data/factory reset" option - no effect...or are we talking about different things?
Click to expand...
Click to collapse
In that case you probably need to flash the system.img and maybe even the boot.img from the latest rom. Elephone really should stop sending out these broken OTAs...

pitrus- said:
In that case you probably need to flash the system.img and maybe even the boot.img from the latest rom. Elephone really should stop sending out these broken OTAs...
Click to expand...
Click to collapse
I believe the case is that my phone is rooted and this is not the Elephone team's fault...anyways thanks for trying to help me.

vagifn said:
I believe the case is that my phone is rooted and this is not the Elephone team's fault...anyways thanks for trying to help me.
Click to expand...
Click to collapse
You belive this b***** that feed you on official forum? OTA should work on any device software config.

ruonim said:
You belive this b***** that feed you on official forum? OTA should work on any device software config.
Click to expand...
Click to collapse
I didn't read official forum. However you do loose your warranty if device is rooted, thus the device manufacturer owes you nothing. OTA worked fine before I rooted my device.
Btw, I got my phone back to life by re-flashing the entire ROM, just in case.

Hello my friend
vagifn said:
Hi there,
The phone is rooted.
I've proceeded with the latest update today (~12mb size), don't remember the exact version.
It said it fixes some system bugs, etc.
After the update installed the phone won't load, stucks on the changing color logo.
Cannot access the recovery mode option in the boot menu (Vol+Power), says "no command", if press and hold Vol+ and Power again the phone restarts and enter the boot logo again.
Has anyone ideas how this can be fixed?
Click to expand...
Click to collapse
The only thing you need to do is reinstall the añl the system with spflashtool. Never and remember never you can update any android with a ota if you are a rooted user.
If you speak spanish you can search in the youtube channel AndroidMxL to ser how you can reinstall the original ROM on your android.

allianzcred said:
The only thing you need to do is reinstall the añl the system with spflashtool. Never and remember never you can update any android with a ota if you are a rooted user.
If you speak spanish you can search in the youtube channel AndroidMxL to ser how you can reinstall the original ROM on your android.
Click to expand...
Click to collapse
Already did, thanks. Will never combine Root and OTA together again

Can't enter bootloader

Two weeks back I tried to manually update my phone to 2.40.168, since i am missing the "system update" option in the settings. I installed a new recovery.img boot.img and droidboot.img and it update the recovery to WW-2.40.168 :good:. I still couldn't update the firmware though and decided to quit trying.
Now I want to put CM13 on it and wanted to change the recovery. BUT when i press Power Up + Volume Up, release the power up this shows up.
{
"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"
}
I can restart it by long pressing the power button but that is about it.
Also i searched for fixes but didn't find anything hence made a post.

Ok so basically what he is saying is that his phone does NOT even have recovery mode. Where we get the dead android guy he gets this and is thus unable to flash his phone with new recovery or system.
That happened to a friend of mine a long time ago but he threw away his phone ( sold it for cheap ) without trying much.
Are there any ACTUAL solutions ?
Again Power + vol up keys DO NOT bring up recovery mode/fastboot or however you want to call it.

Anyone ?

yeah - think this is just a soft brick afaik
you should be able to see the device as moorefied in windows and go from there

debully said:
yeah - think this is just a soft brick afaik
you should be able to see the device as moorefied in windows and go from there
Click to expand...
Click to collapse
"moorefied" ?? Can you explain ?

xRanker said:
"moorefied" ?? Can you explain ?
Click to expand...
Click to collapse
just read some soft/hard brick threads - download the shizzle, install it properly on your machine and follow the instructions.
you have a good chance.
Personally I have no chance as the device wont even turn on. Asus support are absolutely useless and I WILL NEVER, EVER BUY ANOTHER PRODUCT FROM THEM AGAIN - and I'd advise you to do the same. These forums are littered with soft/hard bricks.

debully said:
just read some soft/hard brick threads - download the shizzle, install it properly on your machine and follow the instructions.
you have a good chance.
Personally I have no chance as the device wont even turn on. Asus support are absolutely useless and I WILL NEVER, EVER BUY ANOTHER PRODUCT FROM THEM AGAIN - and I'd advise you to do the same. These forums are littered with soft/hard bricks.
Click to expand...
Click to collapse
That is mostly because people touch where they are not supposed to ^^
But um thanks for reply.

With respect, you don't know what you're talking about.
I've been flashing since the HTC canary. I've never once had a bad flash. Nor here. The phone is prone to hard bricking way in excess of the norm and you only need to look at these forums to see that.
But thanks, your response was greatly valued and added to the weight of knowledge.

debully said:
With respect, you don't know what you're talking about.
I've been flashing since the HTC canary. I've never once had a bad flash. Nor here. The phone is prone to hard bricking way in excess of the norm and you only need to look at these forums to see that.
But thanks, your response was greatly valued and added to the weight of knowledge.
Click to expand...
Click to collapse
Not so sure of that, I really think its more user error than anything else, especially when it comes to fastboot. Copy and paste isn't your friend and it seems most people overwrite their boot or fastboot partitions with system files because they use the same command but change the img file name.
Have never had an unrecoverable brick, and those soft bricks I've had were my fault by not reading properly or skipping through steps quickly.

XepouH said:
Two weeks back I tried to manually update my phone to 2.40.168, since i am missing the "system update" option in the settings. I installed a new recovery.img boot.img and droidboot.img and it update the recovery to WW-2.40.168 :good:. I still couldn't update the firmware though and decided to quit trying.
Now I want to put CM13 on it and wanted to change the recovery. BUT when i press Power Up + Volume Up, release the power up this shows up.
I can restart it by long pressing the power button but that is about it.
Also i searched for fixes but didn't find anything hence made a post.
Click to expand...
Click to collapse
Find your answer here