[Q] Return to stock rom issues - Galaxy S 4 Q&A, Help & Troubleshooting

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.

Related

[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

[Q] How to wipe / (root directory)

Hello, i have LG G2 with TWRP recovery and im asking how to wipe root directory of phone because i have there files from twrp and superuser and i wanna send my phone to RMA.. Full wipe (/system, /data, /cache, /sdcard) will not wipe /.. Ty for answers
Michalko5896 said:
Hello, i have LG G2 with TWRP recovery and im asking how to wipe root directory of phone because i have there files from twrp and superuser and i wanna send my phone to RMA.. Full wipe (/system, /data, /cache, /sdcard) will not wipe /.. Ty for answers
Click to expand...
Click to collapse
Follow this thread to restore your phone to stock.
http://forum.xda-developers.com/showthread.php?p=45293512
This will wipe everything (including internal SD card) and return your phone to the same state as if you were pulling it out of the box for the first time.
Not exactly... After this method the phone status remains "rooted" when booted in download mode. Couple of users reported this problem...
Edit: here's the fix http://forum.xda-developers.com/showthread.php?p=52991286
jake.the.cake said:
Not exactly... After this method the phone status remains "rooted" when booted in download mode. Couple of users reported this problem...
Edit: here's the fix http://forum.xda-developers.com/showthread.php?p=52991286
Click to expand...
Click to collapse
That tool does not unroot your phone. All it does it trip the root flag so when you boot into download mode it says unrooted. It is meant to be used so that if you take your phone into your carriers store and an associated wants to check if its rooted, it will say its unrooted when the associate puts it in download mode, but it is in fact still rooted. This DOES NOT unroot the phone.
See attached screen shot:
{
"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"
}
Sure. But after you flash kdz file with flashtool the phone isn't rooted anyway, although in DLM it states "rooted"...
As I undrstand it, somehow after you flash kitkat kdz it misses some files and status "rooted" appears in DLM. Explained here: http://forum.xda-developers.com/showthread.php?t=2703501
Tapatalk na LgG2
jake.the.cake said:
Sure. But after you flash kdz file with flashtool the phone isn't rooted anyway, although in DLM it states "rooted"...
As I undrstand it, somehow after you flash kitkat kdz it misses some files and status "rooted" appears in DLM. Explained here: http://forum.xda-developers.com/showthread.php?t=2703501
Tapatalk na LgG2
Click to expand...
Click to collapse
Interesting. I never had that happen when I used it. I'll keep an eye on this thread in case something's happens. Thanks for sharing.

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

[Q] Galaxy s5 {sm-g900h} exyons custom recovery not working

Hi everyone,
i have a galaxy s5 the international version (sm-g900h) and i wanted to flash a custom recovery but when i flash cwm recovery and run it the recovery can't mount the partitions so i keep rebooting into recovery untill it mount the partitions properly but this is annoying i want to work with my recovery from the first run
{
"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 i flash twrp or philaz recovery and run it the phone get stuck at the samsung logo, so is there any solution for this ??
Does anybody know the solution ?
Reinstall your original firmwere and use advanced philztouch 6.41 for kg3xx works fine form my in 900h used .tar
Try, try and try
moham_96 said:
Hi everyone,
i have a galaxy s5 the international version (sm-g900h) and i wanted to flash a custom recovery but when i flash cwm recovery and run it the recovery can't mount the partitions so i keep rebooting into recovery untill it mount the partitions properly but this is annoying i want to work with my recovery from the first run
if i flash twrp or philaz recovery and run it the phone get stuck at the samsung logo, so is there any solution for this ??
Click to expand...
Click to collapse
I have the same problem, I tried to reinstall recovery, reinstall rom, baseband, bootloader, but I always get the same result.
But it's always a hope, if you try a lot of times to enter into recovery, and if you're lucky, you will get access to partitions, for example, I have to reboot into recovery for 20 to 30 times, and I get access to partitions in 1 of that 20 or 30 attempt. In that attempt that I got access to partitions I installed a custom rom, just try a lot of times, you're going to be lucky in one, it's all that you need :good:
jah2110 said:
Reinstall your original firmwere and use advanced philztouch 6.41 for kg3xx works fine form my in 900h used .tar
Click to expand...
Click to collapse
I tried but the mounting problem didn't change at ll
frankclaros said:
I have the same problem, I tried to reinstall recovery, reinstall rom, baseband, bootloader, but I always get the same result.
But it's always a hope, if you try a lot of times to enter into recovery, and if you're lucky, you will get access to partitions, for example, I have to reboot into recovery for 20 to 30 times, and I get access to partitions in 1 of that 20 or 30 attempt. In that attempt that I got access to partitions I installed a custom rom, just try a lot of times, you're going to be lucky in one, it's all that you need :good:
Click to expand...
Click to collapse
This is what i do now but it's kinda annoying don't you think ??
moham_96 said:
This is what i do now but it's kinda annoying don't you think ??
Click to expand...
Click to collapse
Yes it is!!!
But I've read about it and I didn't find any solution
frankclaros said:
Yes it is!!!
But I've read about it and I didn't find any solution
Click to expand...
Click to collapse
so let's wait, maybe someone can help us

Please Help Stuck on Samsung Logo After Flash Super Su Or Flash Custom Rom

2 days ago i have flashed @travis82 Nougat Rom that was working fine then i install emoji switcher application to change emoji that app was wanting root permission as soon as I tapped to grant that app message came up that your device is not Rooted, after that i checked Magisk that was saying Magisk is not installed in this device, then i reboot my C9 Pro to twrp mod to flash again Magisk Or Super Su after flashed Su i reboot my device So my mobile was stuck on Samsung C9 Pro Logo, i have waited 30 minutes to see device will start but i t was stuck, then i was coming back to my Stock rom backup so twrp was not showing backup but i was seeing that backup in my laptop, then i flashed C9000ZHU1AQG2 firmware by odin then flashed twrp then SuperSu but same i stuck on Samsung logo screen device not turned on i tried it 3 times flashed firmware/twrp/SU but same issue stuck on Samsung logo now I'm using stock C9000ZHU1AQG2 rom i want to Root again my device can anyone guide me what should i do..? I also tried to flash again @travis82 Nougat and Marshmallow Custom Rooted rom but same issue device is not turning on just stuck on Samsung C9 Pro Logo after flash ??
you format data so encryption is removed? after that install rom? should boot just fine.
travis82 said:
you format data so encryption is removed? after that install rom? should boot just fine.
Click to expand...
Click to collapse
Yes @travis82 before to flash Rom or Super Su i formated data and also swiped to factory reset then i flashed but after flashed when I'm rebooting my device so its not turning on, stuck on Samsung C9 Pro Logo screen to start device i have to flash stock firmware its a problem ?
Maibe you flashed wrong twrp
criszz said:
Maibe you flashed wrong twrp
Click to expand...
Click to collapse
After working very hard and very difficult now Thank God Super Su has Flashed in my mobile by twrp and @criszz I'm using twrp 3.1.1-0 c9ltechn which i downloaded from official twrp.me website twrp maintainer is @travis82 but now I'm getting issues in twrp sometimes format data or factory reset Failed and I'm not able to make backup And restore my Rom its always failed when i tap to make backup and restore and also installing failed sometimes but this twrp was working fine before to this problem which i described in my Post it was working fine since last 3 months but now i don't know why its getting problem with this twrp @travis82 do u know why its getting problem i have downloaded twrp from here which i was using before that time everything was working fine ??
{
"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"
}
cant restore? let me see the recovery log. Maybe the emmc chip is going bad or you need to make sure odin re partitions your phone when you go back to stock.
travis82 said:
cant restore? let me see the recovery log. Maybe the emmc chip is going bad or you need to make sure odin re partitions your phone when you go back to stock.
Click to expand...
Click to collapse
I didn't tick repartition when i flashed the stock rom i just ticked f.reset and auto reboot its just a twrp problem i think @travis82 because in twrp factory reset Failed format data failed sometimes and backup always failed and restore not showing backup files i installed super su with very difficulty because also the installation option not working fine, su or custom rom dirty install
twrp 3.2 has issues dont touch it stay on 3.1
travis82 said:
twrp 3.2 has issues dont touch it stay on 3.1
Click to expand...
Click to collapse
I didn't touch 3.2 twrp and never touch till u will tell me that now touch it but also I'm seeing issues in twrp 3.1 too now what should i do which twrp should i use..? @travis82 issues which I'm getting in twrp 3.1 i described u in my thread
might be having a hardware failure than.

Categories

Resources