So here's what happened:
I had a desire running 2.2, rooted with unrevoked. I then decided to apply an OTA update (I figured I didn't really need root anymore) so I selected the OTA zip in clockworkmod recovery and applied it. There was a signature detection error so I disabled signature detection (smart move, I know) and installed it anyway. The result was my phone got stuck in an endless reboot cycle.
I then got it into recovery, cleared all cache + factory reset, and applied the OTA update from there (had to rename it to update.zip first) Surprisingly it worked, sort of. The phone works and the software version is that of the OTA.
However:
1) Whenever I try to install an app through the market, it downloads the app, and as soon as the installation starts the phone instantly reboots. I've tried clearing cache on the market app but no effect.
2) The Superuser Permissions app is still there. I thought by installing the OTA it would be gone but apparently not.
So now I've got a factory defaults phone that is unable to install any app. Does anyone know how I could fix this, possibly by doing a clean install of the android system entirely?
Many thanks in advance, your help is greatly appreciated.
Related
One of most successful ROMs for Galaxy Y, The JellyBlast v3 developed by xda dev avijit has known to encounter few problems while flashing the OTA updates provided by the dev. This post is about how to flash the OTA updates correctly and how to troubleshoot if you encounter any problems after flashing any of the updates without flashing the ROM itself to solve the problem. So here is the installing+trouble shooting [GUIDE]. I assume that you are fresh on JB v3 without any OTA updates installed. Dont worry if you already had just read on we will most probably come across your problem and you can also check if you did something wrong while flashing OTA updates. Now to the Guide..
First of all download all the OTA updates 1,2,3,4.1 and 5 (there is a 6th update but it has not been tested by me yet as it is not yet available to download as .zip). Place the updates in a folder for easy access. You probably have CWM (5+) if not, download a compatible version and place it in your sd card root(i.e just in your sd card and not inside any folder). Now Boot your phone to recovery mode. Select 'apply update from sd' and select cwm.zip (assuming that you were on stock recovery, if you have cwm recovery as ur default just carry on). Now in CWM recovery 'wipe cache partion' and select 'mounts and storage' and mount everything (you might experience "unable to mount error" if you have a wrong version of CWM). Now go back and take a backup of your phone (assuming that you are fresh on jb v3 if not, its still good to have a backup). This is to save you from flashing the stock/JB v3 again if you encounter a boot loop (boot loop is the state when your phone keeps on rebooting not going beyond the boot animation). Now back to the guide.. Now after taking backup select 'install zip from sd' and now open the folder that has the OTA updates (if you had put em in any). Select the OTA update 1(the name of the file will be something like "JBV3OTA1.signed.zip", i will be mentioning it as OTA update #). Flash the update 1. Reboot your phone. You should enter your phone's android interface(home screen/launcher) for the updates to take effect. You can check your ROM version from your settings to see if the update was successful. This OTA update is known to crash the notification bar. Dont worry the next OTA updates will fix this. Now again reboot your phone to recovery, go to cwm like before and this time you have to flash the OTA update 2 directly without clearing cache and taking backup but it would be a good idea to mount everything. Now as i told flash the update 2 and reboot, enter your launcher. Again reboot to recover do the same for 3, 4.1 and 5 aka pre-nemesis. You noticed that the 4th update is 4.1. It is the revised version of the 4th update which had some serious problems. So be careful which update you download. And after flashing all OTA updates you can check your ROM version from settings. And now to the troubleshooting part.
I already mentioned the first common problem, the crashing of notification bar. This will be fixed after flashing the second update. The next common problem that can occur anytime during the flashing of updates is bootloop. This is something that can occur randomly and not everyone experience this everytime and the chances are rare enough but if you do encounter this, no worries if you have taken the backup of your phone with JB v3 without updates. Just boot to recovery then CWM then Advance Restore then select the backup file and restore 'system' alone. This will solve the problem. But you have to flash all the updates again from first and thr chances are very very low that you will get into a boot loop again. And another tip is you dont have to pull thr battery if u got into a bootloop. Just keep pressing the power key till the phone switches off. Then boot to recovery by pressing home+volume up+power key for few seconds till phone starts. The next most common problem experienced is the disappearing and crashing of settings app after flashing the 5th update. This can be solved pretty easy. All you got to do is open the OTA update 3 with a archiving app like 'easy unrar lite' and look for system/app/settings.apk extract this settings.apk and install it using system installer. This will solve the problem. These were the most common problems experienced while flashing ota updates. It is recommended to flash the updates one by one because each update is a continuation of the previous. So the guide ends here. Hopes that your ROM works perfectly. For any other trouble you have come across feel free to ask.
The latest YouTube app is not installing on jellyblast....notice please
Sent from my GT-S5360 using xda app-developers app
sulavbk said:
The latest YouTube app is not installing on jellyblast....notice please
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
Make sure that you have enough memory free in your 'system' and 'internal'. I would recommend you to use link2sd and convert Youtube you already have on your system to User app. Then link the app. This will free your memory. And try installing it now, using package installer. And link the app using link2sd if its not linked after update. Hopes this will help.
Okay....I have done! But the video is not playing and I can't able to add my account in it...something is going wrong.......
Samsung Galaxy Y-Jellyblast
sulavbk said:
Okay....I have done! But the video is not playing and I can't able to add my account in it...something is going wrong.......
Samsung Galaxy Y-Jellyblast
Click to expand...
Click to collapse
Well.. Then you can try installing it again or install the old version or.. use some app like Tubemate or something like that till you get another update of Youtube. Coz m not yet much of a dev to tweak and fix errors within app right now.
Okay...thanks for the suggestions
Samsung Galaxy Y-Jellyblast
TTS and voice search setting is still missing on nemesis Titanium! please notice....!!!
galaxy y-Nemesis Titanium
sulavbk said:
TTS and voice search setting is still missing on nemesis Titanium! please notice....!!!
galaxy y-Nemesis Titanium
Click to expand...
Click to collapse
Well.. As far as i have known, the nemesis series is still in a developing stage. I have already bricked my phone twice while flashing stuff. So this time i would say that we must wait for a fully functional and reliable nemesis rom. Or till i start tweaking it myself..
ota 5 problem
haridevil99 said:
One of most successful ROMs for Galaxy Y, The JellyBlast v3 developed by xda dev avijit has known to encounter few problems while flashing the OTA updates provided by the dev. This post is about how to flash the OTA updates correctly and how to troubleshoot if you encounter any problems after flashing any of the updates without flashing the ROM itself to solve the problem. So here is the installing+trouble shooting [GUIDE]. I assume that you are fresh on JB v3 without any OTA updates installed. Dont worry if you already had just read on we will most probably come across your problem and you can also check if you did something wrong while flashing OTA updates. Now to the Guide..
First of all download all the OTA updates 1,2,3,4.1 and 5 (there is a 6th update but it has not been tested by me yet as it is not yet available to download as .zip). Place the updates in a folder for easy access. You probably have CWM (5+) if not, download a compatible version and place it in your sd card root(i.e just in your sd card and not inside any folder). Now Boot your phone to recovery mode. Select 'apply update from sd' and select cwm.zip (assuming that you were on stock recovery, if you have cwm recovery as ur default just carry on). Now in CWM recovery 'wipe cache partion' and select 'mounts and storage' and mount everything (you might experience "unable to mount error" if you have a wrong version of CWM). Now go back and take a backup of your phone (assuming that you are fresh on jb v3 if not, its still good to have a backup). This is to save you from flashing the stock/JB v3 again if you encounter a boot loop (boot loop is the state when your phone keeps on rebooting not going beyond the boot animation). Now back to the guide.. Now after taking backup select 'install zip from sd' and now open the folder that has the OTA updates (if you had put em in any). Select the OTA update 1(the name of the file will be something like "JBV3OTA1.signed.zip", i will be mentioning it as OTA update #). Flash the update 1. Reboot your phone. You should enter your phone's android interface(home screen/launcher) for the updates to take effect. You can check your ROM version from your settings to see if the update was successful. This OTA update is known to crash the notification bar. Dont worry the next OTA updates will fix this. Now again reboot your phone to recovery, go to cwm like before and this time you have to flash the OTA update 2 directly without clearing cache and taking backup but it would be a good idea to mount everything. Now as i told flash the update 2 and reboot, enter your launcher. Again reboot to recover do the same for 3, 4.1 and 5 aka pre-nemesis. You noticed that the 4th update is 4.1. It is the revised version of the 4th update which had some serious problems. So be careful which update you download. And after flashing all OTA updates you can check your ROM version from settings. And now to the troubleshooting part.
I already mentioned the first common problem, the crashing of notification bar. This will be fixed after flashing the second update. The next common problem that can occur anytime during the flashing of updates is bootloop. This is something that can occur randomly and not everyone experience this everytime and the chances are rare enough but if you do encounter this, no worries if you have taken the backup of your phone with JB v3 without updates. Just boot to recovery then CWM then Advance Restore then select the backup file and restore 'system' alone. This will solve the problem. But you have to flash all the updates again from first and thr chances are very very low that you will get into a boot loop again. And another tip is you dont have to pull thr battery if u got into a bootloop. Just keep pressing the power key till the phone switches off. Then boot to recovery by pressing home+volume up+power key for few seconds till phone starts. The next most common problem experienced is the disappearing and crashing of settings app after flashing the 5th update. This can be solved pretty easy. All you got to do is open the OTA update 3 with a archiving app like 'easy unrar lite' and look for system/app/settings.apk extract this settings.apk and install it using system installer. This will solve the problem. These were the most common problems experienced while flashing ota updates. It is recommended to flash the updates one by one because each update is a continuation of the previous. So the guide ends here. Hopes that your ROM works perfectly. For any other trouble you have come across feel free to ask.
Click to expand...
Click to collapse
i have a problem that the recent apps list is not exiting tasks,,i have to totally go inside the task manager and clear recent appsss..! plz give a quick response.!
Why does the status bar crash?
haridevil99 said:
One of most successful ROMs for Galaxy Y, The JellyBlast v3 developed by xda dev avijit has known to encounter few problems while flashing the OTA updates provided by the dev.
Click to expand...
Click to collapse
And one of them is the crashing Status Bar, in update 6 nemesis.
hand set configration error
i installed jelly bean blast v3 .
my sim card is 2G.
when phone is turned on it shows requesting hand set conformation and when i click OK it shows temporary error cannot connect to network
so i cannot make or receive a call .
when phone was in stock rom i used the same sim card but now it shows temporary error
so i tried putting sim on other phone and it worked fine and i under stood that the problem was not with the sim card but it was with the rom i just installed
I have a rooted galaxy s3 on straight talk pre paid. Wanted to try slim kat so I flashed it with cwmt. Delvik, fact reset , cache and /system. Didn't like the random reboots so flashed back to stock backup. When I install something from google play it won't download to phone. From within phone it works. Device manager can't locate device. Tried cleaning data on play store app. Play services looks like it's stuck in app manager, and can't delete data. Any suggestions?
Update: Factory reset through Samsung's stock OS resolved issue. Device actually booted into CWM which scared me. Then it rebooted and started updating apps. I maintained root.
Hello All.
I have OnePlus One with CM12 on it. I use CyanDelta to make fetch the nightlies from the server and install. This is working since the day i bought the phone. However, for some reasons i was unable to update the My phone using CyanDelta from some time.
I downloaded the latest "cm-13.0-20151130-NIGHTLY-bacon.zip" from official download page of cynogemod and imported the same on CyanDelta and installed it.
After the installation as per normal process it ran the updates and rebooted the phone.
after a long process of rebooting it gave an errors "SystemUI Crashed" and it is stuck there only.
i am unable to use my phone now as i can't see excpet this error. I have 2 options, "report" and "ok". whatever i press it is the same.
I have Very Very very important data and apps installed on my phone and i don't want to loose anything from there. As reinstalling app again will cause loss of very important data too. I don't know what to do but need to get my phone started.
Please help. I really really need steps to recover.
what if i go to recovery mode and select that same or another "*.*. NIGHTLY-bacon.zip" of version 12 and install from there.. will that remove all my Apps ?
Please advise.
So I'm definitely not an expert at all, but I am going through a similar situation as you. I believe the problem is from the fact that CyanDelta installed android 6.0 (marshmallow), but it didn't install the gapps 6.0, the gapps compatible for android 6.0. This is what maybe causing the crashes (Conformation of this would be appreciated). As for what to do about restoring your data I'm currently trying to figure out what to do my self. I was able to get in to twrp and I backed up my data then I connected my phone to my computer via usb and transferred the back up to my pc. I'm not sure if I can get back my data specifically my sms through the twrp back up, but I'll update you if I can so you can follow the process if you have twrp.
Edit: Solved, see bottom
ROM (D6633_Customized HK_1290-5630_23.4.A.0.546_R6C_HK_SuperSU2.46_XZDR2.8.21-signedv2)
Bit of a dumb move on my part. It all started when my snapchat stopped working, I updated, and then Titanium Backup wouldn't restore the data properly (giving me "parse error"). I was trying to fix that and read online that sometimes this is caused by improper permissions, so I booted into recovery mode, couldn't find the option, but somehow decided "hey, maybe my root permission (?) is wrong slash it's 6am and I just watched a wild 2016 election end" and I hit the button. Now my phone is stuck in a bootloop.
So my question:
1) What exactly does re-root phone do (in CWM), and why would that have messed me up? Is it because I have a pre-rooted rom?
2) I wiped cache and delvik and it doesn't help
3) How do I fix this? I was thinking of loading a SuperSU zip on the SD card from my computer and flashing that, assuming somehow a corrupted root is at fault. I can't seem to get the thing in ADB mode as a side note.
3b) If that seems like a good idea, does it matter what one I use?
4) If I reflash the ROM, it should keep my apps and stuff, ya? I don't actually care if my phone is crippled, I just need it to work long enough to properly back up some media, and mainly get my whatsapp over to my new SIM card. If I can't get in it's forever stuck on my old number which I don't have the SIM for anymore.
Any help would be GREATLY appreciated.
Edit: I don't know how to delete this. Anyways, with other resources I found out that because I used a pre-rooted ROM, there were issues with using CWM to try to do the rooting with its built in functions, softbricking the phone. Reflashing the original pre-rooted ROM worked fine.
Galaxy s8 on Verizon, a standard update notice kept appearing past few days, finally installed it. The minute it finished, it is now in an endless restarting loop. The phone does unlock and show my homescreen. I can get into it, but I only get about 10 seconds to do stuff then it freezes/restarts. Tried Clear Partition Cache in the recovery mode. Tried Safe Mode. No luck.
When I rush over to Settings>Software Update, and click it, it says "Software update in progress"....so it makes me think it is the remnants of the new software update completing itself, and that causes the rebooting. The final stages perhaps? Is there a way to CEASE that the second I unlock my phone? To stop all the background stuff.
Or maybe wouldnt make a difference. Any ideas besides factory reset? Way to revert back?
Wanted to backup a few recent pictures first.
A factory reset is the last resort to fix this.
Maybe it's theme related. Try toggling the button layout (settings -> display -> navigation bar) a couple of times.
If you have substratum installed, try disabling it.
If you want to back up your pictures;
Have you tried accessing the phone using a computer? Either just through a file explorer or by using ADB? To use ADB, you may need to get into settings -developer mode
I tried plugging into a computer, but I only have about 10 seconds, so I dont get enough time to access the files. I get into the phone drive on windows Samsung Galaxy>DCIM> CAMERA> ...then it reboots.
Developer mode is already enabled. Can ADB be used while on the recovery mode screen? I can access that command line looking screen as long as needed.
But accessing the phone normally like turning it on and unlocking the screen would not work, I would keep losing the connection when it reboots.
halfhumble said:
Galaxy s8 on Verizon, a standard update notice kept appearing past few days, finally installed it. The minute it finished, it is now in an endless restarting loop. The phone does unlock and show my homescreen. I can get into it, but I only get about 10 seconds to do stuff then it freezes/restarts. Tried Clear Partition Cache in the recovery mode. Tried Safe Mode. No luck.
When I rush over to Settings>Software Update, and click it, it says "Software update in progress"....so it makes me think it is the remnants of the new software update completing itself, and that causes the rebooting. The final stages perhaps? Is there a way to CEASE that the second I unlock my phone? To stop all the background stuff.
Or maybe wouldnt make a difference. Any ideas besides factory reset? Way to revert back?
Wanted to backup a few recent pictures first.
Click to expand...
Click to collapse
Try downloading that same version of Odin flashable stock firmware from the internet, the same version as the update that you received, then flash that via Odin. As long as the update does not upgrade your bootloader or your binary, it will not wipe your user data(pics).
But first....
If you can get to the homescreen and unlock the device, don't touch anything else once the device opens, just connect it to PC and retrieve your photos from the internal storage, then factory reset the device.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Try downloading that same version of Odin flashable stock firmware from the internet, the same version as the update that you received, then flash that via Odin. As long as the update does not upgrade your bootloader or your binary, it will not wipe your user data(pics).
Click to expand...
Click to collapse
I dont know what version the update was that caused it or how I would find out. But I ended up getting it fixed.
I just downloaded the most recent version firmware from SamFW.com, and used that one. The First flash, the phone was worse! It was now stuck at the samsung logo looping. I flashed it a second time, then it worked! Phone back to normal and backed up my pictures. I had used the home CSC file too, and none of my user data was wiped. I thought it was supposed to wipe that, got lucky
I assume once that OTA update comes back and tries to install, I may have this problem all over again. I can't go forever without the security updates.
Droidriven said:
If you can get to the homescreen and unlock the device, don't touch anything else once the device opens, just connect it to PC and retrieve your photos from the internal storage, then factory reset the device.
Click to expand...
Click to collapse
^
I had tried that a couple times, it lasts about 15 seconds then restarts. Not enough time, I would get to the DCIM folder but before pics loaded, it froze and restarted.
halfhumble said:
I dont know what version the update was that caused it or how I would find out. But I ended up getting it fixed.
I just downloaded the most recent version firmware from SamFW.com, and used that one. The First flash, the phone was worse! It was now stuck at the samsung logo looping. I flashed it a second time, then it worked! Phone back to normal and backed up my pictures. I had used the home CSC file too, and none of my user data was wiped. I thought it was supposed to wipe that, got lucky
I assume once that OTA update comes back and tries to install, I may have this problem all over again. I can't go forever without the security updates.
^
I had tried that a couple times, it lasts about 15 seconds then restarts. Not enough time, I would get to the DCIM folder but before pics loaded, it froze and restarted.
Click to expand...
Click to collapse
The most recent version that you downloaded might be the same update. The OTA updates and the Odin flashable updates are the same thing, the OTA update is just more automated. Flashing the same version as the OTA update via Odin, yields the same results. I think the Home CSC is the one that doesn't wipe user data. I think the Home CSC is intended for users that intend on keeping the device and using it in the same region/network and the other CSC is intended for users that want to sell the device or use the device in a different region or if you have a custom ROM and custom recovery on the device and you want to restore to stock. I could be wrong though.
If you do get a prompt for an OTA update, backup your data then factory reset the device then allow the device to update. That should prevent any further issues with updating via OTA.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
The most recent version that you downloaded might be the same update. The OTA updates and the Odin flashable updates are the same thing, the OTA update is just more automated. Flashing the same version as the OTA update via Odin, yields the same results. I think the Home CSC is the one that doesn't wipe user data. I think the Home CSC is intended for users that intend on keeping the device and using it in the same region/network and the other CSC is intended for users that want to sell the device or use the device in a different region. I could be wrong though.
If you do get a prompt for an OTA update, backup your data then factory reset the device then allow the device to update. That should prevent any further issues with updating via OTA.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Okay, I see.
Well when the phone did boot back up normally after the 2nd flash, there was a pop up that said software update unsuccessful. So I'm not sure if the same OTA update actually updated per se. But yeah, next time Im ready, I've got everything backed up!
Thanks so much!
halfhumble said:
Okay, I see.
Well when the phone did boot back up normally after the 2nd flash, there was a pop up that said software update unsuccessful. So I'm not sure if the same OTA update actually updated per se. But yeah, next time Im ready, I've got everything backed up!
Thanks so much!
Click to expand...
Click to collapse
I always prefer updating via Odin instead of OTA, it is much better and less chance of issues such as bootloop or random reboot. These are the issues you were having. I actually suggest using Odin or Smart Switch on PC the next time an update is available. Or, on older devices, use Odin or Samsung Kies to update. OTA is frequently unreliable, it commonly causes bugs, especially if the update is a newer android version than what is already on the device, it usually causes conflicts due to user data from your previous system apps and user settings conflicting with the new system because of differences between the older system apps and the newer system apps or differences in settings in the older system conflicting with changes in how the newer system settings are handled. Systems don't like using system data that was created by another system when there are differences between the two systems.
Another method that can be used is if your manufacturer/carrier releases a stock update.zip that can be flashed via stock recovery, they are made specifically for flashing via stock recovery ONLY, they are not the same as the stock firmware file that is flashed via Odin. These can be downloaded to the phone's internal/external memory then you boot into stock recovery then factory reset/wipe cache in recovery(backup data before wiping) then you can flash the update.zip. Alternatively, you can flash the update.zip without resetting/wiping(this is called a "dirty" flash), in theory, a dirty flash is useful when you don't want to wipe data or lose data. But that comes with a chance of causing bugs, as you have discovered for yourself during your update process.
Sent from my SM-S767VL using Tapatalk