Database Users

[Q] FRG83D update on a rooted N1

Hi all, I'm quite new to this forum and I hope I dont break any netiquette with my question.
Now I have a N1 I bought on ebay, used, rooted and perfectly functioning.
I don't remember how, but I was able to update it to FRG83D downloading the rom, renaming it, copying on my sdcard etc ...
Now ...
I can't update to FRG83D.
I understood that having a rooted N1 NO OTA UPDATE shall ever work for me, not the manual update is available.
I was able to skip the "no signature verification" error suing clockwork mod, but i can't install the patch anyway, the system alway replies "assert failed: apply_patch_ckeck (" stystem app accountandsyncsetting . apk" ... then a serie of letters and number follows.
I know nothing about this, I must confess, but my suspect is that the update fails because something doesn't match between the update and the ROM which is working on my N1 (which is by the way the original one build frg83d
baseband version
32.36.00.28U_4.06.00.12_7
kernel
2.6.32.9-27240-gbca5320 android-build apa26 #1
Any sugestion ?
I mean and idea about where I can download a FRG83D version suitable for my phone ?

If you just want stock with very little tweaks, may i suggest Geo's Rom. It's basically the latest stock rom w/ superuser, busybox, trackball alert etc. Runs amazing too =)
As for breaking any netiquette, you're suppose to post this in the questions forum not the general. Have fun with your phone.

worked!
Thanks Mokurex!
It worked.
It's unbelievable.
I spent three nights in search of an answer, and then you solved it in few seconds.
I'm new to Android, and I must confess that I'm quite disoriented.
There hare hundred of versions, produced by individuals, companies, etc ... The one I used, I mean the one you suggested me, seems to be the fruit of an individual's work in the US.
It's ok to me, sounds and works good.
But It's not the original one, I mean the one released by ... Google ? or ... what ?
It doesn't matter, but I just want to say that it would be easier for us all, newbies, to have some clear guidelines on this, an online guide for dummies, something or somebody who would explain us the difference between a odexed or deodexed versions, what are the pro and cons of rooting a N1, the fact that rooted phones loose the OTA update (which is very VERY painful for us newbies, etc ...).
I understand that we can rely of forums and on kind people like you, but having some clear cut guidelines would be very useful.
... and looking at the future ... I guess I'll have the same problems when I'll have to update to Gingerbread.
I's very frustrating to search the web for a suitable ROM for your phone ...

stefanopelloni said:
[snip]
But It's not the original one, I mean the one released by ... Google ? or ... what ?
Click to expand...
Click to collapse
No, it's not the original. That one is deodexed, so any future OTA updates will not work (as Google's stock ROMs and updates and not de-odexed). You will have to wait until someone repacks the update, then apply it.
stefanopelloni said:
[snip]
It doesn't matter, but I just want to say that it would be easier for us all, newbies, to have some clear guidelines on this, an online guide for dummies, something or somebody who would explain us the difference between a odexed or deodexed versions, what are the pro and cons of rooting a N1,
Click to expand...
Click to collapse
Did you read the wiki? There are lots of posts/threads/guides available.
stefanopelloni said:
[snip]
the fact that rooted phones loose the OTA update (which is very VERY painful for us newbies, etc ...).
Click to expand...
Click to collapse
What are you trying to say? Phones running a rooted, but otherwise stock ROM will certainly received the OTA updates. Now if you use a non-stock ROM, you may or may not receive the OTA update. But whether you receive it or not, you will not be able to apply it as is, until someone repacks it (unless you are using the stock ROM, rooted or not).

I believe you have to use the stock recovery as well if you wanted to update via OTA.
If you want to get Gingerbread by way of OTA, then revert to stock rom and recovery. Everything you need is in the sticked thread in the development section.

Mokurex said:
I believe you have to use the stock recovery as well if you wanted to update via OTA.
[snip]
Click to expand...
Click to collapse
No, you do not. You just need a newer version of Amon_RA (1.9+) or CWM.

Thank you for the correction.

Efrant, Mokurex,
perhaps it's my problem.
My original plan was to restore my phone is a status capable of receiving OTA updates. Considering that I'm not an IT expert it would be easier for me ho have such a phone.
Wandering on the web, I discovered that rooted phones are not eligible for OTA updates.
And most important of all, I'm not eligible to manually update is as well using the patches on the net (signature verification errors ... and many others seen above).
Mokurex helped me a lot (actually, solved my problem by now) suggesting that version of the ROM (I mean Geo's one) but it's the fruit of a work of an individual. I'm very grateful to him as well, but who knows about the future. Will Geo provide a similar version of Gingerbread as well ? Because without him I can't upgrade.
Efrant, got your remark.
I have CWM, latest version, I also bought the premium version (in oder to show to the programmer of it my appreciation) but in my case it just doesn't work.
With it, I can bypass the signature issue, but then I got stuck at assert failed: apply_patch_ckeck (" stystem app accountandsyncsetting . apk
Oh, by the way, I also tried to go back to ERE27 or something like that (unrooted version etc ...) but the mobile just doesn't work at all ...
I understood that the only way to unroot my phone (actually, any phone) and qualify for the OTA is via SDK.
... but I'm afraid it's just a bridge too far for my poor knowledge.

Geo has been quick to update his rom to the newest version. To upgrade to gingerbread, i'd assume that it would be like flashing any other custom rom, but there might be a bit more steps involved.
If you want completely stock, no root whatsoever, go here.

stefanopelloni said:
[snip]
Wandering on the web, I discovered that rooted phones are not eligible for OTA updates.
And most important of all, I'm not eligible to manually update is as well using the patches on the net (signature verification errors ... and many others seen above).
Click to expand...
Click to collapse
I said it before, and I'll say it again: rooting has no bearing on the phone's ability to receive and install OTA updates -- what matters is which ROM you have. I rooted my phone when I bought it, and it had Eclair on it. I have received EVERY OTA update without any problem.
stefanopelloni said:
[snip]
Efrant, got your remark.
I have CWM, latest version, I also bought the premium version (in oder to show to the programmer of it my appreciation) but in my case it just doesn't work.
With it, I can bypass the signature issue, but then I got stuck at assert failed: apply_patch_ckeck (" stystem app accountandsyncsetting . apk
Click to expand...
Click to collapse
That is probably because you were not using a stock ROM...
stefanopelloni said:
Oh, by the way, I also tried to go back to ERE27 or something like that (unrooted version etc ...) but the mobile just doesn't work at all ...
I understood that the only way to unroot my phone (actually, any phone) and qualify for the OTA is via SDK.
... but I'm afraid it's just a bridge too far for my poor knowledge.
Click to expand...
Click to collapse
If you want a stock ROM, you can go here: http://developer.htc.com and download a Nexus One image to your sdcard, rename it to PASSIMG.zip and boot the phone into bootloader (by holding the trackball and powering up the phone). It should automatically detect the file and allow you to flash it.
Files from the site are official. If you get them from anywhere else, you can't really know what's been modified.

Dear Efrant,
if you were a girl, and in Italy, I would probably kiss you.
Now I have a bright-clear picture of the situation.
During the next holiday, I'll try and flash a stock version of the OS and then try the OTA update.
By now, the version mokurex suggested me work brilliantly and after so many nights wasted in a desperate search of an answer my myself i'm going to have a break.
... but thanks a lot. thanks indeed !!!

Sorry to disturb you again Eftant.
The fact is that today decided eventually to follow your step, but encountered another unexpected problem.
downolaed the original HTC rom - done
renamed it passimg.zip - done
turned on the N1 pressing trackball - done
expected detection of PASSIMG.zip - done
opening passimg.zip - done
checking passimg.zip - done
and then .. nothing
once the N1 load the passimg.zip file (i notice it from a loading bar on the upper right conder of the phone) it just allow me to
1)run bootloader agan
2) lock sim
3) restore something ...
... and that !
No possibility to "flash" rom as you wrote.
Did I miss anything ?
I see from the web that a lot of people bring back the N1 to the stock image using SDK from PC (MAC in my case) but the steps are not so clear considering the fact that I'm not that comfortable with the shell and the Android SDK is not intuitive (... to me).
Thanks in any case for your attention!

Try wiping your device then download the FRF91 image from the same site, rename it to PASSIMG.zip and save it to the root of your sdcard. Put your sdcard back into your device, and boot into the bootloader (by holding down the trackball as you push the power button). Once it flashes, wait for the OTA to FRG83G. Some users have said that the later images don't work using, particularly if you have updated to the 0.35 version of the bootloader.

Need some help with rooting/updating (UK wifi)

Hello,
I'm not new to rooting, but the Xoom scene is very confusing at the moment and I just need somebody to direct me to the proper guides and confirm that I'm not going to blow up my Xoom and/or tear a hole in the space time continuum.
Situation is this: I have a stock UK wifi Xoom and want to get to Android 3.1. I'm not willing to wait until 2013 for Motorola to pull the finger out and give their European customers an update.
SO
Obviously I need to root and apply the update manually.
I'm willing to risk the one-click method (I've seen other UK Xoomers have had some success with it).
Where do I go from there? One-click method says it will install tiamat kernel... but I've read that this isn't compatible with 3.1. So is there a guide that will take me from tiamat to 3.1? Do the update methods replace that kernel anyway? Am I going to go completely f*cking crazy if I have to trawl through another 50+ page thread full of conflicting info? (Yes.)
Any help would be appreciated.
Thanks.

Im not an expert at any of this, just a regular user but heres the guide i followed to get my uk wifi xoom updated. Http://forum.xda-developers.com/showthread.php?t=1074609
However you need to be aware that this software is the us version and you will ony have access to American English. You will lose all the European languages.
Also you need to be aware that if you unlock your bootloader with "fastboot oem unlock" you can not relock it. Trying will brick your zoom. (Currently)
If you could do a full system dump of your xoom as is with the UK wifi software that would be awesome as currently nobody has uploaded one and im trying to get back to stock and Motorola have only posted the us images

Thanks. I don't mind losing the languages. I'm using SwiftKey so I can just download any language modules I need.
I would certainly be willing to upload that if I had the faintest idea of how to do it! If I can get a step by step guide I can give it a go... and as long as I know I'm not also uploading my personal details and authorisation tokens etc along with the software!
Any particular reason you're going back to stock? Bugs or anything?
Edit: the canadian system image has the full set of languages if that's what you're looking for...

Sorry, didn't have time to wait for a reply, going out in a while.
I did a factory reset and then an adb pull so I've got all the system files etc on my PC. Not quite sure what to do with them, though. They're not in .img format, just in a folder?
Anyway, now rooted and running 3.1. Cheers for the link above.

Is anyone else getting a 4.0 OTA notification?

This may be a known issue but my wife's (non-rooted, completely stock) A500 has been getting a 4.0 OTA notification since yesterday. It says it's invalid, after downloading it, so I ASSUME it's not actually for this device but is that the case? If it is for the A500, do I need to do a factory reset to get it to update?
Thanks, and Merry Christmas!

What version is it running currently? 7.014.02
I have not seen anything since the 7.014.01/02 releases a few days back.
It would be nice to see Acer taking the lead on releases but I will believe it when it happens. The. 02 release did have a new to me update screen when it installed....
Wowsher

I think I know what one of the issues is- This must have been some really old stock (bestbuy.com) because it's running 3.0.1 and the kernal version is 26.36.3-00001-g9b3ce2b. Is it possible that it's somehow "skipping" the OTA updates in the correct order (or maybe they aren't available OTA anymore?) and thus giving me the "invalid" message?

yep would not surprise me at all... you should be able to download from a thread in the rom area a thread by vache has links to almost all of them.
You should probably change the thread title if you can.
Wowsher

There have been others with similar issues.Seems like acer did not and is not pushing the updates to some devices.
I would first call acer if you. Not likely to help but would atleast let them know they have issue.
For a right now fix.
Get iconiaroot. Root tablet.
Get acer recovery installer. Install custom recovery.
Look on forums for a stock 3.1 or 3.2 rom.
You can get a ore rooted rom if you wish but would kill all updates in future.
There are lots of information in the dev forums on step by step instructions and downloads.
Be careful fallow instructions.
Good luck.

The 4.0.xxxx update, is an update for UI. It should come in 2 notifications for stock tablets.
The first, is a preparatory update. The second, is the actual update.
Note, if you have a rooted tab, as some people can tell, it is not advisable to take any OTA update from acer.
In the forum, if you want to take the update, there is a thread which has rooted versions of these updates.

[INFO]-Root-Unroot-Restore-Lessons learned

I originally posted this on the Asus TransformerForums. Still no update from .13
__________________________________
Root-Unroot-Restore-Lessons learned
Hello all. I've had my TF now since September or October and enjoying every minute of it. Bought mine in Japan so it was HTKXX.JP_epad-version B70 model. Like so many of us the first thing I wanted to do was root it and install custom ROMs. Being the B70like many I had to wait until Razorclaw was released but as soon as it was I was ready to root.
Let me say I'm not well versed in rooting, intalling, and troubleshooting Android devices...and like many the tablets are new to me. So, to help me figure it out I search and read the forums, re-read, and search again. Notice I said "search the forms", that is very important before posting questions as most of our questions have already been asked and answered. That being said, its ok to post a question, I've found the admins, mods, and other people with experience, problems, and solutions all willing to help. Don't forget, these people do this freely so always respect them even if you dont like the answers or advice they give you. Many of us would have some very shiny paper weights if not for the help from the many on here.
Now..to continue my little adventure. And root I did, Prime! 2.1.0, Revolver, Revolutions HD, and back to Prime! when I had questions I turned to the forums, and sometimes was even able to give a little advice myself. With ICS on the horizion and the latest OTA I thought I should look at unrooting and returning my device back to stock. So, again I turned to the forum for information. Because my TF was the JP model I was concerned there may be something with the build that would prevent this or I wouldnt be able to get the right firmware. You see...there isnt a lot of information related to JP models on the forum. I didnt realize they are all "pretty much the same".
Either way, I eventually posted a question and right away was helped with information or unrooting and reflashing back to stock. All the information however was to restore the US model. After some discussions with one of the RS guys I decided what the heck...gonna try it anyway. (the tinker/challenger in me)
Very good instructions for everything I wanted to do were there. If you think I'm joking, check the signature of RS Team Lead Frederuco. It's all there.
End result my TF was unrooted and now have ver 3.2.1 US.epad-8.6.5.13-20110925 kernel ver [email protected]#1. hmmm...I was worried because everyone was talking about ver.19 and .21...am I in trouble? I've tried various things to get caught up even with a version that I could possibly re-root. Oh boy....even trying to go back and get the JP update from ASUS didnt work, my device is now a US.epad device. My thoughts were...well, at least its still working.
Then I decided to do a bit more investigation, so i went to one of the local computer stores and checked the build and kernel version. I was suprised to see that the only difference in what I now have and what's in the stores is the JP & US. So, maybe what I'm waiting for hasnt gotten to Japan yet...or the ones in the store just haven't been updated. (more likely the case)
Either way, the point and advice here is this. if you decide to unroot and restore I dont recommend to the weak hearted to use a SKU other than what came on your device. It worked yes but not sure where I'm going from here. For me, it doesnt matter as I can always manually update when the versions are on the ASUS site. Worse case, I would have just bought another device and ....yep probably rooted it right away
We all know the risks we take when rooting, tinkering, etc. If you take the plunge, search, read, asks. And respect the people helping.
I hope this in someway helps someone
Update:
I've been able to get my TF from US.epad-8.6.5.13-20110925 to WW_epad-8.6.6.19-20111101 If nothing else I can at least root again. Will probably wait to see if I am actually getting OTA or not. The steps followed can be found in dev post "possible fix for lost root with 8.6.5.21" Sorry, I cant post links yet...
Note that I've changed the SKU on my device from JP to US to WW. So far I haven't seen any problems because of this. (still, if you aren't sure I recommend you dont)

RFA: SM-T510 - Sourcing the factory image(s)?

New to Samsung platforms, excuse any ignorance..
Tried to source the factory image for a new-out-of-box SM-T510 with the following details:
==
T510XXU3BTFN
samsung/gta3xlwifixx/gta3xlwifi
10/QP1A.190711.020/T510XXU3BTFN
build date jun302020
buildid QP1A.190711.020.T510XXU3BTFN
Secpatch 2020-07-01
Android 10
Bootloader U3
==
If there's anything I'm missing let me know.
The usual suspects seem to list packages *later* than that reported on the device (from recovery anyway).
It hasn't yet been fully booted yet - in case there's a way to pull the factory image from recovery/download as a clean image.
I'm looking for that factory image assuming it would be needed in case my modding and experiments (as per our kind of thing) causes breakage.
I wouldn't ask if my efforts had been successful - posting is a last resort
Ta
EDIT:
Is the device ID "T510XXU3BTFN" a constant regardless of software revision/build?
Insofar as; the designator describes the platform; and all software applicable for the platform is referred to by this ID - regardless of software version/revision.
Where software is referred to by a platform designator, I assume there's no proper case where it is applicable to a different platform ID.
If I can get confirmation on this assumption it would help me narrow down exactly what I can use from what I can find on the source sites I have located.

benryanau said:
New to Samsung platforms, excuse any ignorance..
Tried to source the factory image for a new-out-of-box SM-T510 with the following details:
==
T510XXU3BTFN
samsung/gta3xlwifixx/gta3xlwifi
10/QP1A.190711.020/T510XXU3BTFN
build date jun302020
buildid QP1A.190711.020.T510XXU3BTFN
Secpatch 2020-07-01
Android 10
Bootloader U3
==
If there's anything I'm missing let me know.
The usual suspects seem to list packages *later* than that reported on the device (from recovery anyway).
It hasn't yet been fully booted yet - in case there's a way to pull the factory image from recovery/download as a clean image.
I'm looking for that factory image assuming it would be needed in case my modding and experiments (as per our kind of thing) causes breakage.
I wouldn't ask if my efforts had been successful - posting is a last resort
Ta
EDIT:
Is the device ID "T510XXU3BTFN" a constant regardless of software revision/build?
Insofar as; the designator describes the platform; and all software applicable for the platform is referred to by this ID - regardless of software version/revision.
Where software is referred to by a platform designator, I assume there's no proper case where it is applicable to a different platform ID.
If I can get confirmation on this assumption it would help me narrow down exactly what I can use from what I can find on the source sites I have located.
Click to expand...
Click to collapse
That is not the latest by far. Use frija.exe to get the latest stock ROM.

lewmur said:
That is not the latest by far. Use frija.exe to get the latest stock ROM.
Click to expand...
Click to collapse
Thanks for the response
Yes it's the as-shipped build, but before I try to work out which of the newer builds is appropriate and won't lock-out what I'm palnning to do with Ithe device..
I need (I expect so) that factory ROM as a file - to roll back to or restore if(when) I stuff something up in my next steps (TWRP/CWM, bootloader, magisk/root, rom version upgrade and/custom rom etc)
The earliest I can find seems like the latest, which isn't what I'm seeking

benryanau said:
Thanks for the response
Yes it's the as-shipped build, but before I try to work out which of the newer builds is appropriate and won't lock-out what I'm palnning to do with Ithe device..
I need (I expect so) that factory ROM as a file - to roll back to or restore if(when) I stuff something up in my next steps (TWRP/CWM, bootloader, magisk/root, rom version upgrade and/custom rom etc)
The earliest I can find seems like the latest, which isn't what I'm seeking
Click to expand...
Click to collapse
The latest is what you need to do all of the things you want. Earlier versions won't work. The only time you need an earlier version is when a new one has just come out and the devs haven't caught up with it yet. When you do, you can often find them on Sammobile.
edit: Also, if you let it, your tablet should update itself to the latest version. So if something goes wrong, the latest is what you'd need to get it back working.

Ah cheers, my concern was a new(er) release would block the ability to do some things to the device.
I kind of expected it AFAIK it's not uncommon and mostly assumed there's be issues with rollback fuses etc and stuff you can no longer do beyond version x.xx release (BL AP etc)
I might have seen reference to this being the case in the various info's I've read - basically if you want to do XYZ (multiboot, PXE, TWRP I don't know) you have to do it before a certain release.
**lwmr** I take it unlike other mfg's platforms I've worked on it's not an issue here so I can crash on ahead and it won't bite me?
edit:: I also found it strange I guess that the FW release history seems incomplete, Sammobile doesn't IIRC even list versions from around 2019 on these tabs. Unless samsung's volume of products and releases are too much to track I wonder dunno

benryanau said:
Ah cheers, my concern was a new(er) release would block the ability to do some things to the device.
I kind of expected it AFAIK it's not uncommon and mostly assumed there's be issues with rollback fuses etc and stuff you can no longer do beyond version x.xx release (BL AP etc)
I might have seen reference to this being the case in the various info's I've read - basically if you want to do XYZ (multiboot, PXE, TWRP I don't know) you have to do it before a certain release.
**lwmr** I take it unlike other mfg's platforms I've worked on it's not an issue here so I can crash on ahead and it won't bite me?
edit:: I also found it strange I guess that the FW release history seems incomplete, Sammobile doesn't IIRC even list versions from around 2019 on these tabs. Unless samsung's volume of products and releases are too much to track I wonder dunno
Click to expand...
Click to collapse
LOL, yeah, Samsung isn't like Amazon where they are constantly trying to find ways to keep you from blocking their advertising. Trying to downgrade to previous versions can be a problem, but only because of security issues. With these ROMs and recoveries, the devs attempt to keep up with the latest stock releases and will normally specify in the OP which stock ROM they are based on. So long as you aren't attempting to install an older version of a custom ROM based on Android 9 or earlier, having the latest stock version shouldn't be a problem.

(sigh) yep it's not just Amazon
Righto I got ya thanks for the info's I'll roll with that
cheers