ok after i have installed a bricked kernel the other day, and last night i put the sense 4.5 rom on that everyone is using. I did a bootloader relock. and installed the stock ATT ruu. it all went smoth.
I just went and used my old unlock code to unlock boot loader again
and this pops up as normal.
{
"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"
}
and then the phone turns black and the charge light is on... now what? it seems to be stuck. been sitting for 10 minutes. if i hit power it shuts off and back on to the rom but if i reboot in bootloader it says relocked and not unlocked.. and i now relocked permnantly?
2 years and you don't now the rules ? is it really that freaking hard to post in the correct section ?
is this a rom ? NO this should not be in the dev section !!!
Related
I wanted to bring my Desire S back to its original state as a "last resort", because although the Stock-GPS-Performance is not known to be the best, it surely must be better than nothing. And if not, I might send it to repair.
So I have flashed ENG-HBOOT and run the RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed.exe. Now the device is back on stock with HBOOT 2.00.0002, locked, and S-ON.
When I now try to enter Android Recovery, I get an error-Picture at first, then an error-message "E: can't open cache/recovery/command" (see pics).
Is that the "regular" message for a unrooted, S-ON, locked phone?
{
"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"
}
Can't see the pic, but sounds right.
Edit.
Yip, that's normal. (Same on mine)
Now the pictures are there, the link was broken. Maybe a second view? Thanx.
hi No-new-phone.......
Can u help me in restoring the Orignl state..i have been trying hard....
http://forum.xda-developers.com/showthread.php?t=1467351
Please see ma thread
I'm rooted. It looks all fine to me. You need not worry!
I decided to root me Nexus S i9020a. I successfully rooted and unlocked it, then when I tried to put my backup on it did not work. So I then decided I might as well just attempt to manually update the phone to 4.1.2. I was unsuccessful with this, I could not put the 4.1.2 image onto me phone and then us CWM to install it. Now my phone will not start, it just has the Google logo displaying when I try to start it up, with the unlocked lock at the bottom. i am still able to remove the battery to turn off the phone and then put it the CWM screen. Any help would be very much appreciated.
Vol+up and flash a new ROM.
JellyB-TSM v16 / Apex Pro
{
"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"
}
Yeah flash a new rom and see how it goes... Then try to flash your backup... Did you like updated your cwm during that process?
Sent from my Nexus S using xda premium
Hello guys,
I have HTC One M9, I am not sure what software version it is currently running but it should be
the most updated one for this device (this device is not rooted).
A few days ago I launched the camera app and suddenly the phone crashed and restarted.
Now, when I try to power it on back again, the device gets stuck on the HTC boot up screen
and stays that way, until the battery dies.
I have tried to format the partition and the cache through the bootloader menu. So now
the device does go through the HTC boot up screen, but stays stuck on the following screen:
{
"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"
}
Is there any way to install a new fresh software over this device? What are my options to fix this
problem?
Thank you guys.
Reposted in the correct section
http://forum.xda-developers.com/one-m9/help/htc-one-m9-stuck-startup-screen-t3495198
Thread closed
I have a Samsung Note 10 (N971N) which was rooted and on Android 10. I flashed TWRP but it didn't work and I don't exactly remember what I did because my phone has been down since the past 36 hours. I've tried everything, downloaded and flashed 3-4 stock firmware for my phone but nothing seems to work. My phone automatically boots to this screen that is shown in the picture. I've tried connecting it on Smart Switch as well as it says on the screen (in Korean) but that doesn't work either. Whichever firmware/recovery I flash using Odin, it gets stuck on Recovery.
I've tried flashing HOME_CSC and CSC both but nothing works. I was trying to save my data but now I just want to get my phone back up again. Googled and found nothing useful, would really appreciate some help!
At the top it says:
VOLTAGE LEVEL (4148)
SECURE CHECK FAIL : (PIT)
{
"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"
}
Hello, I've been searching for the past 4 hours on this problem and seems like most of people's Pixels were forced into EDL mode.
However, mine was flashing with Android 9 bootloader (walleye-pq3a.190801.002) from my local drive (I assume it was corrputed) when I was downgrading from Android 11 stock rom, it was a successful flash (walleye-rp1a.201005.004.a1)
Before it can flash the radio partition. It got bricked immediately. Hold buttons only twitches the OLED screen up. Nothing pretty much outputs the screen or recognized by computer.
I wonder how because like it was flashed successfully with the bootloader with the walleye-pq3a.190801.002 build while the zip file doesn't have CRC error when it was extracting.
Below was the progress of the flash.
{
"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"
}