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] Return to stock rom issues

I have a Samsung Galaxy S4 i9505 and have installed various custom roms on it. A couple of days ago I used odin to reinstall the stock rom(4.2.2) package for my phone which worked fine and I then rooted using cf auto-root here: http://forum.xda-developers.com/showthread.php?t=2219803. This also worked fine and I had root access. I tried to do an OTA update and received a message saying that I couldn't receive updates on a custom rom. So I reinstalled the custom rom without root after formatting the data and cache and didn't reroot and still received the same error message(custom rom). Since then i've tried install CWM recovery to format /system, /data, /cache, dalvik cache e.g. After this I reinstalled the stock rom and apparently it is still custom. Need help to make the status official again.
Sorry for the really long explanation :/ Please help

TrenchDigger said:
I have a Samsung Galaxy S4 i9505 and have installed various custom roms on it. A couple of days ago I used odin to reinstall the stock rom(4.2.2) package for my phone which worked fine and I then rooted using cf auto-root here: http://forum.xda-developers.com/showthread.php?t=2219803. This also worked fine and I had root access. I tried to do an OTA update and received a message saying that I couldn't receive updates on a custom rom. So I reinstalled the custom rom without root after formatting the data and cache and didn't reroot and still received the same error message(custom rom). Since then i've tried install CWM recovery to format /system, /data, /cache, dalvik cache e.g. After this I reinstalled the stock rom and apparently it is still custom. Need help to make the status official again.
Sorry for the really long explanation :/ Please help
Click to expand...
Click to collapse
Just reset the device from your device accounts / backup and reset and see it should all be official
Make sure u have all internal data backup as all will be deleted

123hiten said:
Just reset the device from your device accounts / backup and reset and see it should all be official
Make sure u have all internal data backup as all will be deleted
Click to expand...
Click to collapse
Unfortunately I have just tried that and I still have a custom status in settings and still can't get OTA updates.

TrenchDigger said:
Unfortunately I have just tried that and I still have a custom status in settings and still can't get OTA updates.
Click to expand...
Click to collapse
I have 2 options u can work on
1, Once again flash stock using Odin and Reset the device and see it should come as Official ( Some time there is bug and shows )custom
2,
Galaxy S 4 (Snapdragon)GT-I9505DBTGermanyI9505XXUEMJ5
{
"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"
}
4.313.10.20131869009Unlockhttp://samsung-updates.com/details/14838/Galaxy_S_4_Snapdragon/GT-I9505/DBT/I9505XXUEMJ5.html
http://samsung-updates.com/device/?id=GT-I9505
Follow the link and flash the firmware using Odin

Ok, I managed to do it using these steps:
1.Install stock firmware(4.2.2)
2. Using cf-autoroot, root your device http://forum.xda-developers.com/showthread.php?t=2219803
3. After your device is rooted install triangle away https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway&hl=en
4. Read all of the instructions carefully and reset your status and flash count.
5. When the triangle away bootloader thing asks you to either reboot or reboot to bootloader select reboot.
6. Now factory reset your phone again from the accounts menu in the settings.
7. After that has finished you should have an official status and be able to recieve OTA's.
NOTE: When I did this process I still managed to keep the phone rooted.
This was testing on an i9505, have no idea whether this is working on other models.

[Q] TWRP/Rooted Nexus 10 w/Super SU in bootloop after OTA

My rooted/TWRP Nexus 10 w/ Super SU is stuck in a bootloop after receiving the OTA update.
I've tried the following:
Running Wug's and sideload the 4.4 update
Errors:
I was unable to get to the android with red exclamation point, even with Wug's.
I've looked around XDA and unfortunately either my searching capabilities are limited or I cannot find this exact problem that someone else had and fixed.
Does anyone have a suggestion on how I can fix this?
I have access to Wug's and the device has the TWRP 2.6.0.0 recovery.
What my screen looks like now after trying to sideload for 20 minutes:
{
"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"
}

Skullpuck said:
My rooted/TWRP Nexus 10 w/ Super SU is stuck in a bootloop after receiving the OTA update.
I've tried the following:
Running Wug's and sideload the 4.4 update
Errors:
I was unable to get to the android with red exclamation point, even with Wug's.
I've looked around XDA and unfortunately either my searching capabilities are limited or I cannot find this exact problem that someone else had and fixed.
Does anyone have a suggestion on how I can fix this?
I have access to Wug's and the device has the TWRP 2.6.0.0 recovery.
Click to expand...
Click to collapse
In order to sideload you will need to use factory recovery.img
There are several open threads iin this subforum already open that spell out in exact detail the process.
In a nutshell you will replace your recovery with 4.3 factory.img, boot to bootloader and go to new factory recovery and the dead droid and then sideload from there the OTA package

planet_x69 said:
In order to sideload you will need to use factory recovery.img
There are several open threads iin this subforum already open that spell out in exact detail the process.
In a nutshell you will replace your recovery with 4.3 factory.img, boot to bootloader and go to new factory recovery and the dead droid and then sideload from there the OTA package
Click to expand...
Click to collapse
I found the problem with files not transferring, I was using my phone USB cable instead of the Nexus 10 one. Unfortunately, I had to use Wug's and flash + unroot to get my device back. Although I can almost guarantee there was another way without losing the data partition. Anyway, I've now rooted my device and backup is restoring. The only thing I lost was my pictures, movies, themes, tones, saved pinball high scores, etc. It's quite a big loss so I think I will read up before applying the OTA next time and do some data backups.

OnePlus One July OTA Update Android 4.4.4

Yep it's out.
For those of you in need to manually update read below.
Download: cm-bacon-d22b777afa-to-0428073396-signed.zip (KTU84P, XNPH30O)
Install: To install the update, flash a custom recovery (TWRP recommended), boot into it, then sideload using adb sideload - if you've ever updated a Nexus device before, then you'll feel right at home, as the steps are exactly the same. TWRP will ask if you want to re-root at the end.
{
"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"
}

Wtf is this thread....anyways has anyone tried a clean flash yet?

just flashed it. thanks man!

Why can you flash the zip, why do you have to sideload it ?

Mine keeps failing some sort of verification check, on both cm recovery and twrp.

I flashed it through TWRP, NO ISSUES

doalittledanse said:
Mine keeps failing some sort of verification check, on both cm recovery and twrp.
Click to expand...
Click to collapse
Are you sure you're installing with "adb sideload" as instructed? You can't install from the "install" button in TWRP.

clipcarl said:
Are you sure you're installing with "adb sideload" as instructed? You can't install from the "install" button in TWRP.
Click to expand...
Click to collapse
yep. on both the stock cm recovery and twrp i get this error:
Code:
assert failed: apply_patch_check("/system/framework/apache-xml.jar","44e4.........","eab54.........")

If you've flashed any mods or made any changes to the system. It will fail.
Exclusive Member of the OnePlus One Club

If you guys flashed my Smooth Scrolling Mod, flash the revert and then try the OTA
http://forum.xda-developers.com/one...scrolling-mod-mahdi-rom-t2840934/post54762296
Basically when you're on stock ROM and if you did any changes to your /system/ then it will not update because its been modified.

does this include removal of apps ? Mine failed to sideload as well.+
Edit 1: I did do some modding of the build.prop as well this morning.

I had a feeling that the system partition was a problem, so i wiped it and then reflashed the previous build from cyngn.com and the update still fails.

doalittledanse said:
I had a feeling that the system partition was a problem, so i wiped it and then reflashed the previous build from cyngn.com and the update still fails.
Click to expand...
Click to collapse
Same problem here, fails at:
assert failed: apply_patch_check("/system/framework/apache-xml.jar","44e4.........","eab54.........")
Everything is stock, except Recovery. Tried with original recovery and it still fails...

Got mine to update even though the system partition was updated with a modified updater-script.
I will upload the entire zip with the updated script. For those that know what they are doing the updater-script is attached.
Edit 1: Note you do loose root. You have to install supersu again if you did have it previously (if you modified system then you did)

I have a louder sound mod. So basically I have to reflash to pure stock to use this? That sucks.
Sent from my One using xda premium

Anyone tried custom kernels with ota?
Sent from my A0001 using XDA Free mobile app

C-4Nati said:
I have a louder sound mod. So basically I have to reflash to pure stock to use this? That sucks.
Sent from my One using xda premium
Click to expand...
Click to collapse
look at my post.

I guess the update.zip factory image from the official site isn't truly stock. so i went with the nuclear option and just reflashed everything via fastboot. update worked perfectly now haha.

Please go to the thread here to continue the conversation....http://forum.xda-developers.com/oneplus-one/general/cm-11s-30o-ota-slowly-rolling-t2844689

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