Database Info

[Q] Why does it do this?

Every ICS ROM that I have flashed on my phone has done this. I never hear anyone discussing this and I can't be the only one. Why and is there a fix?
{
"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 get it in the app drawer as well.

Have you done a full wipe and is hardware acceleration enabled?

Not So Strange...
Well,it backs to several things:
Did You Fully wipe?
What's device current Recovery?
What was your previous Firmware?
Did the Roms you use,support GPU rendering ?
How is your device like with official firmware?
And several other things...

peter_dizai said:
Well,it backs to several things:
Did You Fully wipe?
What's device current Recovery?
What was your previous Firmware?
Did the Roms you use,support GPU rendering ?
How is your devce like with official firmware?
And several other things...
Click to expand...
Click to collapse
Yes, I always do a full wipe when flashing roms.
5.0.2.0
It does it eventually, regardless of the previous firmware.
I believe so, all roms that I flash come from here.
I just flashed a root access version of the IMM76D ROM and it happened on that one.
It only happens every so often, and a reboot is in order to correct it.
Thanks guys.

Now,It's Better...
kazerak2 said:
Yes, I always do a full wipe when flashing roms.
5.0.2.0
It does it eventually, regardless of the previous firmware.
I believe so, all roms that I flash come from here.
I just flashed a root access version of the IMM76D ROM and it happened on that one.
It only happens every so often, and a reboot is in order to correct it.
Thanks guys.
Click to expand...
Click to collapse
Ok,first try to flash latest official firmware which I think is:
Ics 4.0.4
Baseband Version: D720SPRKH1
Build Number:IMM26
and here is a how to:
http://www.techzek.com/how-to-update-sprint-nexus-s-4g-on-android-4-0-4-ics-firmware/
Afterward flash following recovery:
http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.0.2-crespo.img
Then try to flash:
http://bigota.d.miui.com/2.3.30/miui_NS_2.3.30_c1e078377e_4.0.zip
or
a cyanogenmod 9 and report back please...

^ Is that the correct firmware to flash for the 4G nexus s?

That looks like a launcher problem to me. Are you using an aftermarket launcher or are you restoring it from a previous install?

wild1z said:
That looks like a launcher problem to me. Are you using an aftermarket launcher or are you restoring it from a previous install?
Click to expand...
Click to collapse
Stock launcher, I've never used a different launcher other than stock on all my ICS ROMs.

I Edit the firmware,check and flash it.

Update, my phone did it again and I thought I would check the launcher. I did a "force stop" on the launcher and that resolved it. I have always used the stock ics launcher what would cause the launcher to behave this way?

kazerak2 said:
Update, my phone did it again and I thought I would check the launcher. I did a "force stop" on the launcher and that resolved it. I have always used the stock ics launcher what would cause the launcher to behave this way?
Click to expand...
Click to collapse
See my signature for proper FULL wipe. Something tells me you're not wiping system.

I'm having the same problem with one of 2 Nexus S 4G's I flashed with IMM76D. I did a full proper wipe on both of them, but one seems to corrupt the text like in the picture. It happens after it's been running a while and a reboot fixes it temporarily.I wiped it fully again and reloaded the ROM and its still doing it.
Next thing to try is re downloading the ROM. Maybe a corrupt download? Any ideas?

[email protected] said:
I'm having the same problem with one of 2 Nexus S 4G's I flashed with IMM76D. I did a full proper wipe on both of them, but one seems to corrupt the text like in the picture. It happens after it's been running a while and a reboot fixes it temporarily.I wiped it fully again and reloaded the ROM and its still doing it.
Next thing to try is re downloading the ROM. Maybe a corrupt download? Any ideas?
Click to expand...
Click to collapse
I too have done a full proper wipe with that same rom and still have the issue from time to time. Next time you get it try to fore stop the stock launcher. That fixes it for me, until it happens again. But for me its something with the stock launcher.

[Q] Rooted Droid 2 Global issues

So I recently bought a Droid 2 Global off of ebay. I got the phone and it was relatively fine. It came with the android 2.3.3 system. I decided that I want to flash cyanogenmod onto it. I rooted it and that went fine. I then attempted to open up the cyanogenmod from clockworkmod recovery. This didnt work. I kept getting an error message. So I gave up and did a factory reset and wiped everything. Unfortunately this solved none of my problems. The phone would boot up only to get stuck at the motorola "m". I couldnt go into either the stock recovery or the clockworckmod. I thought maybe if I pull the battery, my sd card, and the sim card things would get better. Nope. The phone wouldnt even turn on after that. Maybe its a battery issue? I let it charge in the wall charger all night. Currently its on only when plugged into the wall and is still stuck at the "m".
I have no idea what to do anymore. Any help would be appreciated!!

reanjo said:
So I recently bought a Droid 2 Global off of ebay. I got the phone and it was relatively fine. It came with the android 2.3.3 system. I decided that I want to flash cyanogenmod onto it. I rooted it and that went fine. I then attempted to open up the cyanogenmod from clockworkmod recovery. This didnt work. I kept getting an error message. So I gave up and did a factory reset and wiped everything. Unfortunately this solved none of my problems. The phone would boot up only to get stuck at the motorola "m". I couldnt go into either the stock recovery or the clockworckmod. I thought maybe if I pull the battery, my sd card, and the sim card things would get better. Nope. The phone wouldnt even turn on after that. Maybe its a battery issue? I let it charge in the wall charger all night. Currently its on only when plugged into the wall and is still stuck at the "m".
I have no idea what to do anymore. Any help would be appreciated!!
Click to expand...
Click to collapse
Have you heard of "sbf" ing?
I'll try to find a link...
SBFing allows you to install a complete stock firmware image - should fix those problems. Factory data resetting only deletes all of your data (everything past the /data partition)
Your android system (OS, firmware, etc, etc) is in the /system partition
If you got an error while installing CM, you may have put it into a bootloop - depending on where the error was at. Installing a rom starts by formatting the /system partition, then copies the CM version of /system from the zip file. If you got an error after the format, then you don't have an os to boot from. Also that means your recovery is gone. That means your only choice is an SBF. (what you did is commonly called soft-bricking)
(any mods/devs may correct me as needed but I'm fairly sure this is right...
---------- Post added at 01:31 AM ---------- Previous post was at 01:09 AM ----------
Links can be found on a text file on my website. It's at ftp:// kd8rho (dot) net (slash) factory_reset_links.txt
I can't post links, so that's what I have to do... I hate these new member restrictions!
Link for rsdLite: link 1 on the text file
rsdLite is the program you need to use to sbf back to stock.
They have instructions on there, but you need to use the sbf file found at link 2 on the text file, instead of the one on their page.
Instructions:
Download rsdLite.
Install rsdLite
download the sbf file above (NOT THE ONE ON CYANOGENMOD'S SITE!!!!!)
use the instructions to flash the SBF
If you get an error or can't flash, follow the instructions on link 3 on the text file

if your phone is stuck at the m
most likely not charging
if battery gets too low, it will be unusable
try ezSBF
{
"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"
}
also lots of links sd_shadow's list of links for Droid FAQs, SBF, Rooting, ROMs.... https://docs.google.com/document/d/1Goawxdx_UBF4Y8lqzHYWf8Ha3yUcRK4faq0UWIlXLWA/edit
Sent from my DROID X2 using xda premium

Reference the DROID Wiki for instructions on re-flashing stock firmware and information about the different firmware versions available. Note that if your phone has ever had the newest firmware version installed (4.5.629/Android 2.3.4) it will not boot after flashing any older version.
If you are able to boot into ClockworkMod Recovery, you may still be able to flash CyanogenMod without first re-flashing a stock firmware. Be sure to select a CM build based on the same kernel version as the one installed on your phone (if your Motorola "M" logo during boot is red, you have a Gingerbread kernel; if it's white/silver, you have a Froyo kernel). Official builds of CM target the Froyo kernel only; unofficial builds work with the Gingerbread kernel and are generally better-adapted to the specific model handset you're using. Look in other threads on this forum or on RootzWiki for information on and download links for unofficial builds.

updating from software crash - cyangoen mod

got a samsung galaxy captivate i897
bought it rooted running cyanogen mod & miui
was fine for about a year then the software kept crashing (everything was force closing)
in the this time i didnt do anything that would have caused this issue. i didnt update anything the only thing i did was install or uninstall apps. so i dont know why it occured. i dont even know if it happened as a result of having been rooted (if something became unstable - i wouldnt have thought so since it worked for a year with no problems)
anyways i now have new phone since that one become unreliable but i'm now looking at how i could fix the issue so i can use it as a spare phone if needs be.
it runs cyanogen mod android version 2.3.7 and i'd be looking at how i could go about updating to ice cream sandwich or jellybean, whichever has a stable build.
how would i go about doing this? (in simple terms - i'm a noob!)

neonflash said:
got a samsung galaxy captivate i897
bought it rooted running cyanogen mod & miui
was fine for about a year then the software kept crashing (everything was force closing)
in the this time i didnt do anything that would have caused this issue. i didnt update anything the only thing i did was install or uninstall apps. so i dont know why it occured. i dont even know if it happened as a result of having been rooted (if something became unstable - i wouldnt have thought so since it worked for a year with no problems)
anyways i now have new phone since that one become unreliable but i'm now looking at how i could fix the issue so i can use it as a spare phone if needs be.
it runs cyanogen mod android version 2.3.7 and i'd be looking at how i could go about updating to ice cream sandwich or jellybean, whichever has a stable build.
how would i go about doing this? (in simple terms - i'm a noob!)
Click to expand...
Click to collapse
Im glad you asked for ICS or Jellybean, CM 11 (Kitkat) is terrible looking. if you still know how to flash roms, we should probably figure out what version of CWM you have. other than that, if you have CWM 5.x.x.x or higher you can go ahead and download the top version here first http://download.cyanogenmod.org/?device=captivatemtd&type=stable and This Gapps for CM 10.2 http://goo.im/gapps/gapps-jb-20130813-signed.zip and put them both on your External micro SD card. boot into CWM and flash CM 10.2 first and then the Gapps after.

Trozzul said:
Im glad you asked for ICS or Jellybean, CM 11 (Kitkat) is terrible looking. if you still know how to flash roms, we should probably figure out what version of CWM you have. other than that, if you have CWM 5.x.x.x or higher you can go ahead and download the top version here first http://download.cyanogenmod.org/?device=captivatemtd&type=stable and This Gapps for CM 10.2 http://goo.im/gapps/gapps-jb-20130813-signed.zip and put them both on your External micro SD card. boot into CWM and flash CM 10.2 first and then the Gapps after.
Click to expand...
Click to collapse
problem is i dont know how to flash!
yeah sorry i'm a total noob
if there's step by step instructions though that'd be great

neonflash said:
problem is i dont know how to flash!
yeah sorry i'm a total noob
if there's step by step instructions though that'd be great
Click to expand...
Click to collapse
so do you at least know how to boot into Recovery? i haven't touched my Captivate in awhile but i imagine that its (turn off your phone first) hold volume up first then power button until the Samsung logo apears and tell me all the information thats on the screen. when your done you can use the volume buttons to navigate to reboot phone.

vol up & down and power yep :]
here's the options:
reboot system now
apply update from sd card
wipe data/factory reset
insall zip from sd card
backup and restore
counts and storage
advance
power off
go back
i selected reeboot now & have been left with a hat like this on screen :/ (dunno if that's good or bad!)
{
"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"
}
it's just the hat nothing else and has been like that for about 30mins......
phone's ****ed isnt it ?
optop of the options it say cwm based recovery v5.0.2.7

Please help me! Freshly softbricked SGS7, SM-G930W8, No OS Installed

I have tried goddamn near everything and lurked everywhere.
This is just me trying to fix a huge mistake. I got this phone yesterday, everything was fine. I just wanted to install a custom recovery so I could back up the phone.
I flashed TWRP with Odin, I may have done it wrong or something... But I'm pretty sure I followed some directions. Odin did it in a snap, my device rebooted into TWRP... but then, I just barely noticed the "No OS installed!" message.
I have attempted, in no particular order:
- Using Kies 3 to initialize my device. It will download to 100% and then stick on 0% going to install the OS. Tells me the device is not supported.
- I then tried SmartSwitch because someone told me that's what you need for Android 4.3+. Same exact thing.
- Tried flashing my stock firmware, both 6.0.1 that it came with and the 7.0 that was available before it was bricked, with Odin 13.2 (I also tried others)
What's interesting here is when I add in the AP, BL, CP and HOME_CSC and press start, I get Odin's log to fail just after cm.bin - every time.
Here is a screenshot:
{
"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"
}
At that point, I am no longer able to re-attempt until I restart and re-enter DL mode, and a black-backgrounded red text appears on the Download Mode screen, that says:
SW REV. CHECK FAIL. DEVICE: 2, BINARY: 1
My device is the Canadian version, in the XAC region.
I have downloaded and attempted flashing firmwares G930W8VLU2BQB6_G930W8OYA2BQB6_XAC and G930W8VLU1APG1_G930W8OYA1APG1_XAC.
Both give the exact same errors and so I don't think the firmwares I got are the issue. I just have no idea what it could be, since the only problem with my phone is there's no OS installed.
Actually, I do have a problem with TWRP, as well.
TWRP is unable to do much. It cannot mount /data (among others), and those folders are all still there as I can adb push files to the device, and I attempted pushing the actual firmware to the /data folder and I could see the progress by pressing Install in TWRP and then looking in the /data folder... but that was the only file that told me "No space left on device" once it 100% completed, when there's obviously ~30GB.
The first error TWRP gives is that it cannot find the crypto footer.
Am I screwed here? Is this a harder softbrick? What am I missing? Please reply quickly, working by tomorrow would be very ideal.
Thanks in advance!

The last time I tried to flash stock - I got errors in Odin. Disconnected phone, restarted download mode and tried again. Don't know why but it took four tries before flashing complete - good luck
Sent from my SM-G930W8 using Tapatalk

bill_in_mtl said:
The last time I tried to flash stock - I got errors in Odin. Disconnected phone, restarted download mode and tried again. Don't know why but it took four tries before flashing complete - good luck
Sent from my SM-G930W8 using Tapatalk
Click to expand...
Click to collapse
I tried many more than four times. Should I be using CSC rather than HOME_CSC, just to wipe everything and maybe that'll work?
You say you got 'errors' in Odin, but it's always different for a different cause. You didn't get an error before cm.bin, did you?
EDIT: Attempting CSC rather than HOME_CSC for both v7 and v6 firmwares.
UPDATE: Ugh... I guess it's not the same every time. Using CSC with the Marshmallow md5s, I got Odin to err earlier this time, before even getting to cm.bin!:
UPDATE2: I have just tried flashing Nougat with Odin, using CSC instead of HOME_CSC, and IT'S WORKING??? WTF. Got past recovery, now going through system... Perhaps I posted too soon? Sorry for wasting anyone's time. I will update this thread if it doesn't work.
I'd say this thread isn't worth deletion because I think somebody could come by, take this information and help themselves with it.

I had similar issue - error would be different with every attempt until finally it just flashed and passed. Glad you got it working .
sent from SGH-1337M using Tapatalk

Yeah, that's the thing though... With this one, I got the same error no matter how many times I tried one specific way.
I suppose just never attempted the 7.0 firmware with CSC instead of HOME_CSC. Thanks anyway

Need help downgrading to Marshmallow

Hey guys, I'm a J7(2016) user. Recently I upgraded to Nougat, and just like everyone else, I don't like the update. My phone's battery life has taken a hit, and it's overall performance has gotten worse (compared to Marshmallow). Though by no means would I call it laggy, it's fairly smooth, but as I just mentioned, it's not as fast as Marshmallow. Things that really bother me are 1) Battery life isn't as good as it was on MM 2) Performance has degraded, Samsung's Official web browser (that came preinstalled) fails to keep two or three tabs in memory when I multitask (switch to other apps). So I wanted to downgrade it to MM. I looked it up and found out that there is a way to downgrade the OS, through ODIN (don't know anything about it). And from what I read, there's a possibility that it might brick my phone if I don't do it properly. Can you guys please guide me through the whole procedure? I'd be really grateful if someone does that. I'm too scared to do it without proper knowledge, I'm afraid I might end up with a bricked phone, which is only a month old.
And I never wanted to upgrade, I wanted to stay on MM since it was working flawlessly. One day I just tapped on upgrade accidentally (in the settings app). And it started to download the update, even though I turned off my wifi, it resumed when I turned it back on.
Btw, I'd like to know if downgrading it to MM will void it's warranty? Please guide me through the steps. I really want to go back to MM. Thanks in advance!

J710f(6) nougat 7.0
I update my phone to nougat and i have same battary problem how i can fix it
or i have back to v6 Marshmallow

I have run into this problem too. Even worse, downgrading to Marshmallow with stock rom has proved impossible.
It seems that the Nougat update updated the bootloader to version 2, and Marshmallow's ROMs use bootlader version 1.
The bootloader update was probably to update security (and prevent people from rooting), but it has made downgrading quite a puzzle.
I am currently working on it, on my J700P, using these as templates:
forum.xda-developers.com/galaxy-s6/help/guide-downgrade-sm-g920f-nougat-to-t3639253
androidfact.com/how-to-downgrade-android-firmware-and-versions/
If someone can help, I'd appreciate it.
Will update if I get results.
-Dro

SOLVED IT
I got my J700P back to Mashmallow (J700PVPU1APB7) from Nougat (J700PVPU2BQJ2). Tested it around for a whole day. So far no issues. But first some background (so you get an idea where I am coming from):
I got my phone brand new and rooted it while keeping stock rom. Went to custom rom. Softbricked it trying to go back to stock rom with root (so I could play Pokemon Go using Magisk). Succeded on my quest. Got some updates (both Marshmallow and Pokemon Go) which made it impossible to keep playing PokeGo. Softbricked it again trying to unroot. Succeded. Kept playing PokeGo. Got the damn Nougat update - which brought battery issues, network issues (calls/text), hated the settings menu, etc-. Tried to flash Marshmallow ROM through Odin. Failed. Softbrick it again through several attempts rooting, unrooting, reflashing and using Marshmallow TWRP backups. Fixed it by reflashing Nougat stock rom. Modify Marshmallow stock Rom. Flash. Succeded. ​
If there is a lesson, it is that J7 softbricks for any sh*t. But so far, there is always a way out.​
So... below are instructions that worked (starting from stock Nougat). Read fully to familiarise yourself. Think if it is worth it to follow the steps (of a possible lucky idiot) and adapt them for your phone at your own risk.
---------------------------------------------------- WHAT YOU NEED -------------------------------------------------------------------
Windows PC (Odin is meant to use on windows)
Marshmallow (6.x.x) stock rom (find at sammobile.com)
Nougat (7.x.x) stock rom (as a precation/ from sammobile.com)
7zip software (7-zip.org/download.html)
Samsung USB Drivers (developer.samsung.com/galaxy/others/android-usb-driver-for-windows)
Odin Flashing Tool
Unlock OEM (android.gadgethacks.com/news/psa-enable-hidden-setting-before-modding-anything-android-0167840/)
Allow USB debugging on your phone (recovery-android.com/enable-usb-debugging-on-android.html)
Fully charged battery
------------------------------------------------------- PREPARATION --------------------------------------------------------------------
Download 7zip and install.
Find your Model Number & current Software Version at "SETTINGS" --->"ABOUT DEVICE"
At the SamMobile website create a free account
Go to sammobile.com/firmwares/ while logged in and download your current Software version by searching Model number. KEEP IN MIND YOUR CSC (Country/Carrier). Nougat software is 7.x.x.
Download your target software. KEEP IN MIND YOUR CSC. Marshmallow software is 6.x.x.
Unzip both downloads to obtain a file ending on .tar.md5 for each software.
Download Samsung USB drivers and install
Download ODIN and unzip.
Backup ALL your data. We WILL factory reset the device.
If you'd never used ODIN, here is a how-to: progeeksblog.com/how-to-use-odin/
how-to Recovery and Download mode: fonepaw.com/solution/enter-samsung-recovery-download-mode.html​
------------------------------------------------------------- STEPS ------------------------------------------------------------------------
Use 7zip to decompress Marshmallow ...tar.md5 file. You will get a folder with several files.
Delete the aboot.mbn file
Select the remaining files, right-click, under 7-Zip, click on "Add to archive..."
On "Archieve format:" select "tar". Click OK
Go to ODIN folder, open Odin.exe
Set your device on Download Mode and plug in to your computer
Once recognised by Odin, click on AP, and select your modified ROM
Under the Options tab, uncheck Auto Reboot
Click "Start"
Once greenlit, pull of battery and exit Odin.
Go to Recovery Mode (might take some time)
Perform "Wipe data/factory reset"
Perform "Wipe cache partition"
Power off
Repeat steps 5-14 two more times.
Turn on phone.
Done! :good:
--------------------------------------------------- SOME WARNINGS ------------------------------------------------------------------
I had my phone SIM Unlocked by idoneapps. This process re-locked SIM. Idoneapps was able to re-unlock it.
If you debloated your device... You will get all that sh*t back.
The problem seems to be precisely the updated bootloader (now J700PVPU2BQJ2 in my case). This process will not downgrade to your previous bootloader, so from now on, you either upgrade back to Nougat software, or modify every stock room to accomodate the limitation.
Sprint's Hands Free Activation is back; driving me nuts every time I restart my phone. I Force Stop application and doesn't bother me as long as phone doesn't go off.
If phone softbricks, just reflash Nougat software, wipe data/factory reset and wipe cache partition, and you recover your phone.
You will lose root. But the CF-Auto-Root-j7ltechn-j7ltezm-smj7008.tar.md5 method still works after downgrading.
For anyone interested... the only reason I figure this was because each time I tried to flash Marsmalllow stock rom, Odin failed at aboot.mbn. So i deleted it and risk it all. Wabalubadubdub!!!
Let me know who risks it and whether I luckily stumble upon the answer... or I am an idiot. Or both?
-Dro
{
"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"
}