Database Users

stuck at samsung logo

I went to replace framework-res.apk, and now it wont go past samsung logo, please tell me I didn't brick my phone?

Please Help [email protected][email protected]!

What did you flash?, theme kernel? Be specific

I went to flash some circular battery mod, and then it crashed and won't boot.

Never mind. Do you have cwm installed? if so, flash a rom that matches the one you are on. That'll fix that issue. Next time don't flash something that isn't for the rom version that you are on.

Specifially I renamed it framework-re.apk.bak, and then about to replace it it won't boot.

Which rom version are you on? DL09? DJ05? DI01?

Dont have cwm installed, did it through root explorer.

You probably flashed a file that wasn't compatible with our phone, or isn't compatible with the ROM you're running (DI01 mod on DJ05/DL09). Reflash the ROM you're running and it should fix the problem.

Just flash the rom that you are on again.

So there's no way out? I have to loose all my data?

Also next time flash a theme that it's compatible to your rom version.
You don't have to wipe!
you can flash dj05 theme on top of dl09, but remember to flash the dl09 theme fix.

tonu42 said:
So there's no way out? I have to loose all my data?
Click to expand...
Click to collapse
If you flash the same rom you're on now, you don't have to wipe data.

I'm going to win imnuts...

But doesn't odin delete all data?

tonu42 said:
I went to flash some circular battery mod, and then it crashed and won't boot.
Click to expand...
Click to collapse
By any chance, did you make a backup of your old framework-res.apk?
And what version are you on? DI01, DJ05, DL09?
If you have Clockwork, you can use ADB to push a new framework to your phone. Just reboot into recovery, connect to your computer and open up a command prompt (on Windows):
adb push framework-res.apk system/framework/framework-re
Here's mostly stock versions of the framework:
DI01
DJ05/DL09 (works for either, but you have to rename to framework-res.apk)
The only difference in these is that I did my own little battery mod:
{
"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"
}
If you had a theme installed, this will probably screw it up, reverting most stuff back to stock, but hopefully it'll at least get you booting again.

If I reboot into normal samsung recovery will adb work?

I am just gonna reflash with odin..........

tonu42 said:
I am just gonna reflash with odin..........
Click to expand...
Click to collapse
Not sure if ADB works with the stock recovery, I'm using a Voodoo kernel, so the stock recovery is gone.
But if you're flashing with Odin, you could just flash Clockwork recovery and then boot to it and use ADB. Might as well get Clockwork on your phone... with a backup, you could have been back up in just a few minutes.

Wow, this is a fascinating thread with so much confusion.

[Q] /system/etc/gps.conf

adb sideload the kitket update zip is fails with following error:
Verifying current system...
"/system/etc/gps.conf" has unexpected contents.
Click to expand...
Click to collapse
{
"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 anyone upload for me the original gps.conf from Nexus 4 JWR66Y?

alexroz said:
adb sideload the kitket update zip is fails with following error:
View attachment 2408712
Can anyone upload for me the original gps.conf from Nexus 4 JWR66Y?
Click to expand...
Click to collapse
look here:
http://forum.xda-developers.com/showthread.php?t=2525947
you MUST reflash a kind of stock/not gps moddified version :/

Getting this same issue on wifes Nexus 4. Its stock with the 4.3 JB OTA no mods or root since that OTA. Can't understand why GPS.conf could be changed.
If I root and TWRP could a factory image update.zip with the -w wipe removed work to get her to KitKat without wiping and redoing her phone? I am used to flashing custom roms this stock ota stuff is giving me a headache.

EvilAaron said:
Getting this same issue on wifes Nexus 4. Its stock with the 4.3 JB OTA no mods or root since that OTA. Can't understand why GPS.conf could be changed.
If I root and TWRP could a factory image update.zip with the -w wipe removed work to get her to KitKat without wiping and redoing her phone? I am used to flashing custom roms this stock ota stuff is giving me a headache.
Click to expand...
Click to collapse
You do not use custom rom or custom recovery to flash factory image. Use the links in my signature for instructions.

eksasol said:
You do not use custom rom or custom recovery to flash factory image. Use the links in my signature for instructions.
Click to expand...
Click to collapse
I understand that, she is stock ROM, with stock recovery and not rooted when she is having this issue. No root TWRP or custom rom involved. Since it wasn't working with stock recovery was looking for options without wiping device during factory image flash to fix GPS.conf file thats buggered.
She got the OTA normal way on her phone this afternoon, but it failed. Will check out your sig links when I get home and see if I can solve this without spending all night setting her phone back up from a factory image wipe :/ Thx for feedback and any pointers

EvilAaron said:
I understand that, she is stock ROM, with stock recovery and not rooted when she is having this issue. No root TWRP or custom rom involved. Since it wasn't working with stock recovery was looking for options without wiping device during factory image flash to fix GPS.conf file thats buggered.
She got the OTA normal way on her phone this afternoon, but it failed. Will check out your sig links when I get home and see if I can solve this without spending all night setting her phone back up from a factory image wipe :/ Thx for feedback and any pointers
Click to expand...
Click to collapse
The flashing will required an unlocked bootloader, so if its not unlocked you will lose all data when unlocking it. (Doing a factory reset in stock recovery also wipe everything.)
I don't really know what else you can do, if there were never any modifications, then the problem is due to Google having too much protections and issues for their OTA packages.

Unlocked so can do the method in your guide. But she says she wants to clean up her phone so a clean start will probably perform better and she gets the clean slate she wants, problem solved Though OTA checks annoy me now lol
thx for the feedback and guides

Android 5.0.1 flashed - changes?

I've literally just flashed 5.0.1, currently "Android is Upgrading".
If I see any changes, I will be sure to post! Please feel free to do the same!!

OTA or ADB flashing?
Sent from my Nexus 9 using XDA Free mobile app

team56th said:
OTA or ADB flashing?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Neither - fastboot!
Yeah, manually did it via factory image!
Seems a bit snappier so far, but that might just be a placebo, or just because I have freshly rebooted it!

I flashed the new image and then flashed twrp and SuperSU and so far everything seems fine. Stock, rooted seems as fast and stable as the previous build if not more so....

What was your previous firmware level?
Changes are relative

What's the kernel version/date?

I was on the latest version of 5.0 before this (can't remember exactly what it was. Ha ha).
Here is the about 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"
}

This version is 5.0.1_r1 (LRX22C).

Ok, downloaded the 501 image, unzipped all IMG files and flash then manually, individually.
system.img
recovery.img
cache.img
boot.img
vendor.img
even performed a fastboot -w to wipe
After reboot it does some more reboots, show android robot once.
But finally i get the google logo and thats it. Nothing.
edit: oops typo . used wrong commands.

I only flashed the system.img, the rest is the same as the previous build.
I have to say, boot pretty fast after I installed SuperSU again (you'll never know) wipe cache and Dalvik and then done.
Tablet worksfine

Dalvik? Lollipop changed to ART afaik. Lol.
Just restored Q factory image. Booted right away!
During setup i get a message 'your tablet needs to download an update and restart'.
17.9Mb
Will be the q-to-r i guess. < 5 minutes later > Yep, got R now.
Flashing 501 system.img... takes 3 minutes or so.
Ah, reboot. Got the flying dots. Finally. "android is upgrading".
Checking 'about' ... On LRX22C now. Thanks.

reijndert said:
C:\android-sdk\platform-tools>fastboot flash system Nexus9-501-C-factory\recovery.img
Click to expand...
Click to collapse
You flashed everything as system.
The correct way would be:
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img

reijndert said:
Dalvik? Lollipop changed to ART afaik. Lol.
Click to expand...
Click to collapse
Well, TWRP offers only wipe cache and dalvik, no matter whether there is only ART

I flashed it and it works fine. I dont notice any apparent changes though.
Sendt fra min Nexus 5 med Tapatalk

Finished flashing it and have found nothing new so far.
Sent from my Nexus 9 using Tapatalk

Does it still heat up like crazy when you browse with Chrome?

clubtech said:
Does it still heat up like crazy when you browse with Chrome?
Click to expand...
Click to collapse
To me it doesn't seem to, might be newer version of Chrome Beta though?

Are there instruction for updating N9? I am rooted, unlocked and have custom recovery.

GatorsUF said:
Are there instruction for updating N9? I am rooted, unlocked and have custom recovery.
Click to expand...
Click to collapse
Flash the images in fastboot
Sent from my Nexus 9 using XDA Free mobile app

The DNS bug is not fixed. Local addresses are still not resolving to internal addresses, but the external IP. Annoying. The bug is marked as fixed but apparently not a part of 5.0.1

Help with error flashing system

Hi all, well I think I have all but fubarred my 16gb shield tv. I unlocked bootloader, installed twrp and rooted, all was working fine. Then I decided to flash the full android rom that is on the forum . before doing so, i used twrp and made a backup. I installed the full android rom, although it seemed to work fine, i was not crazy about it and decided to go back to the original OS, so I booted up in twrp and went to the restore function, there were no backups to restore , I guess when I installed the system img for the full android it erased my backup somehow. anyway, moving right along, I next went to nvidia website and downloaded the restore image for the 16gb shield tv, i booted in to bootloader and was following the instructions to restore the shield. all seems to go fine until I try to flash the system img, then I get the error "invalid sparse file format at unknown block 0000" it tries to continue but fails, afterwards the system will not boot at all, I can get back to twrp recovery an flash the full android rom just fine, but am not able to flash back the original os without that error. any suggestions would be greatly appreciated, as I am stuck at this point as what to attempt next. thanks

Here is an image of the error I get, I am no longer able to write to the system partition,
{
"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"
}

cdsn99 said:
Here is an image of the error I get, I am no longer able to write to the system partition
Click to expand...
Click to collapse
Just going to go out on limb here, but are you sure the downloaded image isn't corrupted? You could try to download it again, if available do a MD5 hash check to verify it downloaded correctly and then retry flashing it.

d-dragon said:
Just going to go out on limb here, but are you sure the downloaded image isn't corrupted? You could try to download it again, if available do a MD5 hash check to verify it downloaded correctly and then retry flashing it.
Click to expand...
Click to collapse
thanks d-dragon, I re downloaded the image from nvidia and was able to successfully flash it, thanks for the reply and help

Glad to hear my suggestion helped you out Enjoy the shield!
Sent from my Nexus 5 using Tapatalk

send the link
cdsn99 said:
thanks d-dragon, I re downloaded the image from nvidia and was able to successfully flash it, thanks for the reply and help
Click to expand...
Click to collapse
can send the link for stock rom

ahm3336 said:
can send the link for stock rom
Click to expand...
Click to collapse
https://developer.nvidia.com/gameworksdownload

Galaxy A700FD bootloop after updating SuperSU

Hi there, I've been having problems with the Titanium Backup recently and tried some troubleshooting method such as unticking Mount namespace separation in SuperSU. They didn't work until i get to the point on updating the SuperSU from Play store. Then asked me to update the binary which i selected TWRP and it rebooted. After the installation from TWRP, it only boots to recovery. Tried turning off the phone and it still go to recovery even if i select reboot system.
Now i tried re-flashing the 'CF-Auto-Root-a7lte-a7ltexx-sma700fd.tar' via Odin3. It completed but then it's only boot looping. Sure i know it would reset multiple times but it has been more than 30mins doing like that over and over again. Tried to flash the TWRP again via Odin and wiped data/system/cache. And tried installing the Ressurection rom but it fails it gives me error "E:Error executing updater binary in zip '/external_sd/A7 Root and all/Roms/RessurectionRemix........"
Error flashing zip........
Then tried rebooting system. It said no OS installed proceed to reboot then saying device does not appeared to be rooted and asked me to install SuperSU which I did and it just restarted and still on boot loop....
Any help, please? TIA

{
"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 is what happen when i try to flash the firmware that i downloaded from sammobile... please help.
On the recovery, whenever i try to reboot, it says No OS installed. Then SuperSU installation. Whenever i try to install a custom rom, it fails. Giving me error: error executing updater binary in zip...

gsmtec said:
flash latest version for you model, should work
Trimis de pe al meu SM-G920F folosind Tapatalk
Click to expand...
Click to collapse
which one? CF auto root? firmware? thanks for replying..
btw im flashing the latest ones. except the SuperSU which I will try later. But the No OS installe would be the problem i think?

gsmtec said:
flash latest 6.0.1 version for your region or for the one that phone came
Click to expand...
Click to collapse
not sure but when i clicked earlier it was all china versions. and on first click on something it selects other something like samsung camera. but now i was able to see the firmwares. guess the site have some bugs. imma try it.
there's no 6.0.1 on my region. only 5.0.2 and lower versions.. i take the 5.0.2?