Annoying update message on my dev phone (JF 1.41) - G1 General

Hi @all,
I installed the latest Jesus Freke's build of the firmware (ADP 1.1). No I have the problem that my phone shows an update message every few minutes.
If I try to get into the "System Update" configuration I get a force close.
Does anyone know how to turn this off else? I think if I let it update via the automatic updater I will get into trouble or is it safe to upgrage? (used jesus freke's firmware to set symlinks to my sdcard and install the apps there).
Would be nice if someone could help me sorting that out!
Regards,
Markus

download jf1.42 and install it the standard way..

Thanks for the tip! Just did the update as usual (following the steps described here http://android-dls.com/wiki/index.php?title=Keeping_Root).
Now my phone is looping at the boot sequence (the droid is showing over and over again).
Bricked?

TheKoelnKalk said:
Thanks for the tip! Just did the update as usual (following the steps described here http://android-dls.com/wiki/index.php?title=Keeping_Root).
Now my phone is looping at the boot sequence (the droid is showing over and over again).
Bricked?
Click to expand...
Click to collapse
did you move your apps to the SD card before you upgraded?

sure, I already did that when I installed the 1.41 a few days ago

oops...I tried to redo the upgrade and noticed that there are no test keys options...**** should have watched out for that.
would a wipe help? and if it would help where does the built in nandroid put the image?

****, just cant anything now. flash_image doesnt work in recovery mode and falling back to 1.41 or previous doesnt work also.
where does nandroid store the image?

In /sdcard/nandroid/

Related

loaded wrong rom, stuck on boot screen

Apologies for this stupid question resulting from a stupid mistake. Hoping somebody will be able to walk me through getting out of this.
I successfully rooted my sprint hero, then loaded modaco 3.0 (yes now I know that was bad). On reboot, the phone hangs on the black htc screen, and will respond to nothing.
The only thing I've been able to do is remove the battery, then turn it on in recovery mode. There, I did a wipe data/restore factory setting. Then I rebooted - and got the same boot screen, same problem.
Second try: wiped, toggled to usb, and replaced the 3.0 update.zip with the 1.1 for CDMA, tried to flash it, got this:
can't open /sdcard/update.zip (bad)
When I try to restore, I get these:
(bart) error: run bart via adb
(nandroid) can't open file
Please help! I am out of ideas. Thanks very much in advance.
you'll probably have to take it back to the very beginning......
Get the Sprint RUU stock rom (a couple of posts below this one) and run that
then re-root your hero
Flash one of the roms ON THIS BOARD ONLY!!! Any other Hero rom is meant for the GSM version so it will give you the same headache again.
thanks
Thanks for the quick response! I'll try that.
Hmm, not looking good here. When I tried to install the stock hero RUU I got this error:
no signature
verification failed
which I presume is related to the htc sync requirement for that rom in the unrooting procedure that I did earlier.
Any idea for working around that?
So you used RUU_Hero_C_Sprint_1.29.651.1_signed_release.exe? If not, here is a link to it: link.
david.danaan said:
Second try: wiped, toggled to usb, and replaced the 3.0 update.zip with the 1.1 for CDMA, tried to flash it, got this:
can't open /sdcard/update.zip (bad)
Click to expand...
Click to collapse
Don't use 1.1, grab a later one.
Which recovery? 1.5.x won't let you go back to the main menu without disabling USB-MS again... I don't remember what 1.2.3 did. If worse comes to worst, reboot the phone after copying the file.
gu1dry said:
So you used RUU_Hero_C_Sprint_1.29.651.1_signed_release.exe? If not, here is a link to it: link.
Click to expand...
Click to collapse
Yes, that's the one.
Using recovery 1.5.1. I can try a later rom, see if that works. I think I downloaded 1.3.
So first off yes, you aren't booting past the HTC screen because you flashed the wrong rom. However you aren't bricked. It's almost impossible to do once you're rooted and have RA's recovery installed unless you flash radios and stuff which you shouldn't.
Explanations for your other problems:
1. RUU doesn't work on the phones that are coming from the factory with 1.56. http://geekfor.me/news/sprint-ruu-fails/
There is a possible work-around but it's pretty detailed and I haven't gotten it to work. But you don't need to RUU if you can get in to RA.
2) (nandroid) can't open file is likely caused by RA 1.5.1. It had a bug that corrupted the backups. 1.5.2 is out. But for now don't worry about that cause your backup already sounds corrupted, nothing you can do.
3) can't open /sdcard/update.zip (bad). To me that sounds like your update was just corrupted.
How to fix it:
1. Boot in to recovery. With phone powered off hold your home button and then power.
2. Download fresh rom from http://geekfor.me/new-release/fresh-rom-1-0/ (what can I say... I'm partial. )
3. Within RA enable USB toggle and copy fresh rom to the root of your sdcard. Don't worry about renaming it to update.zip
4. Disable usb toggle. Go to flash zip from SD and choose fresh. That should be it. If you get the error saying the zip is bad then compare your downloaded copy with the md5 hash check on the download page (google it if you aren't sure how). If it matches then it's possible you have a bad sdcard. If it doesn't match then your downloads are crappy.
working!
Got it working by flashing the modaco v1.3a - must have been a bad update.zip before like you said. Thank you so much for the help and clear explanations, I was really worried I had bricked it.
David, now that it is working, I would recommend updating your recovery to 1.5.2.
I just want to thank everyone that posted to this reply I honestly thought that I bricked my phone and thank to you guys I was able to revive it. Thank you again.

[Q] Lost root after OTA update.

This is my situation...
I recently rooted for my Wildfire using Unrevoked3, have no installed any custom roms whatsoever.
To install the new firmware (Update 1.25.405.1) i followed a guide which involved renaming it to update.zip and used clockmodrecovery to install update.zip from the SD card.
Update was successful however i lost the root (as expected)
I tried to rerun unrevoked 3 to reroot but all it does is reboot my device and it remains unrooted.
On the HBOOT recovery menu i now get a red triangle with an exclamation mark against a black background. i do power + volume up and it says android system recovery and in yellow 'E: Cant open/cache/recovery command'
How can i reroot my phone so i can use apps such as titanium backup once again? (and yes ive tried to install busybox and i get a failed error message)
I have looked around the forums and made lots of searches some of which address this question but i am yet to find a solution which works... Im sorry if this question is redundant as i am new to this sorta thing.
Thanks.
Did you follow this guide?
Update: What I did to succesfully install the update on a rooted phone
- unplug phone from USB, let it download update (it's about 13 Mb in size)
- phone will ask to reboot -> update will fail, you will be dumped in clockworkmod
- As always, do a Nandroid backup before doing anything that might possibly render your phone unusable.
- Select update from zip/sdcard (or similar), navigate to zip in downloads folder
- the update process will start
- reboot (this can be a longer boot than usual, took 10 minutes on my phone)
- phone will notify you that the update has succeeded! If you've upgraded from your stock ROM (like I did), the phone info screen should look similar to that in the attached image.
- (reflash needed for root)
It doesn't say to rename the file though.
I'm going to do this now (im guessing youre on TM too?)
thanks for the info, i'm just about to do the same thing, after trying [ROM][04/10] WildPuzzleROM v8.0.5; until i realised there are still problems, got scared and restroed nandroid backup Couldn't get marketplace to load?
when phone reboots after downloading the update, i guess its supposed to be installed by the recovery program, but i have clockworkmod, I tried apply sdcard:update; get error back with failed to open update.zip and sig veri failed.
Not sure what to do? Will try booting normally, checking sd theres a file called 'OTA_Buzz_TMO_UK_1.25.110.1_R-1.14.110.1_R_release31o90ome6fwgje76.zip' on the sd card under download folder. will try renaming to update.zip and placing in \sdcard root folder
otherwise i'm thinking rom manager to install, but mobilism is down it seems and can't get hold of it
EDIT: Just rename the update put it in the \sdroot. Boot into recovery and install update.zip. works fine, takes ages, very scarey process.
Will try going back to puzzle when i have more time! Lets hope 1.25 don't crash as frequently!
Yes, i did follow all those instructions and it still didnt work. However i have managed to reroot my wildfire haha so problem is resolved. It was a stupid problem, after i rooted the first time, i reinstalled htc sync to sync some stuff but forgot to uninstall. After uninstalling it again i was able to reroot.
Sorry guys... very silly mistake by me.

[Q] Update to 3.2 failed

Dear all,
I got a update notification today. I was so happy to see that.
I spent 20 mins on downloading this firm, but after the unzipping procedure,
it exit Andriod OS and reboot to a DOS-like system.
I saw a bee on the screen, there was a ProcessBar under this bee.
When the process went to around 20%, the process was failed and a "!" was shown up.
I installed Acer Recovery Installer on my tablet and I have Recovery on it as well.
Is it the reason why I cannot update my OS?
Help!!!!!
Easier way to get official OTA updates from acer is to be full stock :
- stock rom
- stock recovery / bootloader
Remember that updating to stock 3.2 will makes you lose root
franva said:
Dear all,
I got a update notification today. I was so happy to see that.
I spent 20 mins on downloading this firm, but after the unzipping procedure,
it exit Andriod OS and reboot to a DOS-like system.
I saw a bee on the screen, there was a ProcessBar under this bee.
When the process went to around 20%, the process was failed and a "!" was shown up.
I installed Acer Recovery Installer on my tablet and I have Recovery on it as well.
Is it the reason why I cannot update my OS?
Help!!!!!
Click to expand...
Click to collapse
Must remove root and all mods and reflash stock recovery. Maybe not all, but that should work.
shaun298 said:
Must remove root and all mods and reflash stock recovery. Maybe not all, but that should work.
Click to expand...
Click to collapse
Are there instructions on how to do this?
Update 3.2 failed
Hello, I have the same problem, I can install the stock with CWM? if so, where can I download? the ROM?
(sorry for my bad english)
My device is Acer Iconia Tab A501
I am having quite a bit of problem updating my A500. After the update downloaded the first time, it gave me an error saying update is invalid. After that it is constantly trying to download. As soon as 357 MB is downloaded, instead of asking me whether to install now or later, it just goes ahead and tries to re-download all over again. As you know it takes some 20 mins to get the whole 357MB over wifi, so I went ahead and unchecked the automatic update checkbox in system update. Does anyone know where the downloaded file ends up? I could just try to run it from that location.
My system was rooted, but once I got the last ROM update (3.1), the tablet was unrooted and none of the rooted apps work anymore. So I don't think I should be having root related issues unlike some of you who are having problems. Any help is appreciated.
Fix for "Invalid Update" problem .....
Samaruf,
I suggest that you have a look at Post #4 in the following thread......
http://forum.xda-developers.com/showthread.php?p=18132338#post18132338
This thread appears to be focused on a different problem. The resolution to your problem is at the above thread. Good luck....

[Q] HowTo disable OTA 4.5.141 Update ?

I downloaded the OTA 4.5.141 on my unlocked and rooted Atrix, when I was advised to do this (only a few days ago), but stopped the installation of it.
After reading all the threads here in xda forum, this might be the best idea. I do not see the advantages of 4.5.141, only a lot of the disadvantages. Loosing root, high possibility of a brick ... ... better to wait for ICS as my Atrix is running perfect. Really love this little masterpiece.
But since I downloaded the OTA my Atrix advises my hourly that I should install the download. This annoing, how can I disable this ? Please help.
Use a root file manager and go to the /system/app folder and freeze the "Updater.apk " by adding a ".bak " to the end of it and rebooting.
If you have the paid version of the TiBu then you can freeze it with that.
1.ATRIX-in-PT said:
I downloaded the OTA 4.5.141 on my unlocked and rooted Atrix, when I was advised to do this (only a few days ago), but stopped the installation of it.
After reading all the threads here in xda forum, this might be the best idea. I do not see the advantages of 4.5.141, only a lot of the disadvantages. Loosing root, high possibility of a brick ... ... better to wait for ICS as my Atrix is running perfect. Really love this little masterpiece.
But since I downloaded the OTA my Atrix advises my hourly that I should install the download. This annoing, how can I disable this ? Please help.
Click to expand...
Click to collapse
What's wrong with 4.5.141? I installed it and just rerooted/unlocked/flashed
Hi live4nyy !
Thanks. The file is /system/app/Upgrader.apk ?
Hi ericc191 !
Probably you are right and nothing is "wrong" with 4.5.141 and "no risk, no fun". But it seems, that it includes just some little improvements.
It's not a real system update, so I am not very much in the mood for all this struggle to get my Atrix back to normal after the update (rooted, unblocked and not bricked).
Yeah, upgrader or updater. One of those
1.ATRIX-in-PT said:
Hi live4nyy !
. The file is /system/app/Upgrader.apk ?
Click to expand...
Click to collapse
If you're freezing it through a root file manager, then look for BlurUpdater.apk; do not change the "Upgrader."
If you're in Titanium Backup, then it's called Updater 2.3.4.
If you've already downloaded the update, then you might also need to boot into recovery and wipe the cache partition to erase the update file.
live4nyy said:
Use a root file manager and go to the /system/app folder and freeze the "Updater.apk " by adding a ".bak " to the end of it and rebooting.
Click to expand...
Click to collapse
this didnt work for me
das8nt said:
If you're freezing it through a root file manager, then look for BlurUpdater.apk; do not change the "Upgrader."
Click to expand...
Click to collapse
this did the trick
Yesss! No more annoying notifys!
hi all,
since the update was popping up from time to time and never really researched how to turn it off today, I friggin accidentally pressed on "install update" and automatically tried to reboot the phone, when I realized the mistake, I quickly pulled the battery out and waited for a few minutes then switched it back on.
it booted up fine but once it completes its bootup sequence, it would again prompt for an auto restart and try to install the update. Seems like the update is on the auto startup items (if there's such a thing).
I tried booting into safemode but can't get to do it maybe because I'm using an Alien build rom.
Any ideas on how to solve the problem? Please note that the phone boots but it tries to restart as soon as I can use it.
I have booted up now to recovery and will try to delete the updater apk and see if that will work. thanks in advance!.

Question [FIXED] Rooted phone(1) freezes about 30 seconds after boot after failed update.

Hey, this is my first post on this forums so excuse me if there are some issues with the way I'm posting.
I have a rooted Nothing Phone (1) at version 1.1.4 (EEA). I got notified about the update to 1.1.6 and of course I wanted to update.
I don't have much experience at phone tinkering and after searching I tried these steps to update my phone. Step 1 and 2 were succesfully done. On step 3 the Updater in settings gave an error saying it couldn't update. I was stupid enough to reboot my phone at this point. At first I thought it booted normally but after 30 seconds or so the phone freezed up, resulting in a soft reboot about a minute later. It's stuck in this loop.
[EDIT] Not actually stuck as I can still use the phone until it freezes and it doesn't freeze in bootloader or recovery
What I've already tried:
- sideloading the update manually via Recovery/ADB. threw an error.
- using fastboot to boot with the rooted image. I thought maybe there is something that is expecting root that is freezing up the phone. Phone still freezed up.
- sideloading the 1.1.6 full update package. threw an kinstalldeviceopenerror
I'm a bit out of ideas how to save my new device. Does anyone have any suggestions?
Make sure you have the right update for your device version.
Nothing Phone 1 update tracker: Here are all the official Nothing OS builds to download and install
We tracked down all the Nothing Phone 1 updates so you don't have to.
www.xda-developers.com
You can try to install a magisk patched boot img
b_5.4.147-qgki-g3e5c6bfc5f18
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
How to unbrick Nothing Phone 1 fastboot bootloop
Welcome to this unbrick tutorial NB: I state immediately that i'm not responsible for any damage that occurs on your phone. This process worked for my Nothing Phone on 1.1.3, but maybe not on yours. I do not suggest following this tutorial if...
forum.xda-developers.com
You will loose all data un your phone doing this.
xtcislove said:
Make sure you have the right update for your device version.
Click to expand...
Click to collapse
In recovery I found out that I have the SKQ1.211230.001/1663771117 (1.1.4 global hotfix) version even though I'm on a European device. Is it okay to try to update to 1.1.5 and then 1.1.6 or will ik mess with any settings?
xtcislove said:
You can try to install a magisk patched boot img
b_5.4.147-qgki-g3e5c6bfc5f18
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Click to expand...
Click to collapse
Done. Didn't change anything except bring my root back. Phone still freezes up.
xtcislove said:
You will loose all data un your phone doing this.
Click to expand...
Click to collapse
Isn't available for this version from what I know and I wanna first get the region problem sorted out.
The thing I find weird here is. The problem started after turning off all magisk modules, and removing the patched boot file via magisk. I reset root and turned on all modules again and the phone still freezes up. I don't know where to search.
EDIT: While pulling /sdcard/ with ADB I found that the command still pulls data while the phone freezes which I find very weird
JDeVries said:
In recovery I found out that I have the SKQ1.211230.001/1663771117 (1.1.4 global hotfix) version even though I'm on a European device. Is it okay to try to update to 1.1.5 and then 1.1.6 or will ik mess with any settings?
Done. Didn't change anything except bring my root back. Phone still freezes up.
Isn't available for this version from what I know and I wanna first get the region problem sorted out.
The thing I find weird here is. The problem started after turning off all magisk modules, and removing the patched boot file via magisk. I reset root and turned on all modules again and the phone still freezes up. I don't know where to search.
EDIT: While pulling /sdcard/ with ADB I found that the command still pulls data while the phone freezes which I find very weird
Click to expand...
Click to collapse
I guess there is something mixed up in your phone.
Since you can use adb pull, simply backup everything and do a reset.
I backup my phone daily do Google Drive, which is maybe not the case for you. I would simply follow the unbrick tutorial and go back to 1.1.3 EEA (You need to flash the super.img first). This will give you a clean device again so you can exclude that the freezing is a hardware error.
There is only one thing you can try:
Flash flash boot 1.1.6 and vendor_boot 1.1.6 and adb sideload full 1.1.6 eea via recovery.
I would go back to EEA.
There was something mixed up. I couldn't fix by sideloading 1.1.6 via recovery. I factory reset my phone via recovery which fixed the freezing. Then I pushed the 1.1.6 EEA rom to /sdcard/ota and dialed *#*#682#*#*. Installed the update from there and everything works again!

Categories

Resources