Hi Guys, I have been following all the developments for the Wildfire from the past couple of days, and, finally, have decided to give it a go and take the plunge into rooting my wildfire and installing custom ROM's.
Now, I have watched the various tutorials (Thanks to all involved in making them!), and, have properly understood the entire process, however, seeing the section on Unrooting the phone again, it says that I have to get my Stock ROM from Shipped-ROM's website, and, this is where the problem lies. My ROM is not listed at SR.
Here are the specs:
Firmware Version - 2.1-update1
Baseband Version - 13.45.55.24H_3.35.15.31
Build Number - 1.25.720.1 CL227575 Release Keys
Software Number - 1.25.720.1
Since my ROM is not listed at SR, is there any way I can take a full backup of my ROM before I root it, so that, if I need to Unroot and get back to factory settings.
Alternatively, if this is not possible, can I just download another ROM from SR with the same Radio version? Will that work?
I would just like to keep a path open so that I can get back my WF in its factory shipped state, provided something goes wrong.
Thanks for reading.
Cheers
3xeno said:
Hi Guys, I have been following all the developments for the Wildfire from the past couple of days, and, finally, have decided to give it a go and take the plunge into rooting my wildfire and installing custom ROM's.
Now, I have watched the various tutorials (Thanks to all involved in making them!), and, have properly understood the entire process, however, seeing the section on Unrooting the phone again, it says that I have to get my Stock ROM from Shipped-ROM's website, and, this is where the problem lies. My ROM is not listed at SR.
Here are the specs:
Firmware Version - 2.1-update1
Baseband Version - 13.45.55.24H_3.35.15.31
Build Number - 1.25.720.1 CL227575 Release Keys
Software Number - 1.25.720.1
Since my ROM is not listed at SR, is there any way I can take a full backup of my ROM before I root it, so that, if I need to Unroot and get back to factory settings.
Alternatively, if this is not possible, can I just download another ROM from SR with the same Radio version? Will that work?
I would just like to keep a path open so that I can get back my WF in its factory shipped state, provided something goes wrong.
Thanks for reading.
Cheers
Click to expand...
Click to collapse
IMO, just root your phone and then do a nandroid backup of your stock rom, BEFORE you flash a new rom. So if anything goes wrong, just restore that backup.
It's not like they're going to check every piece of software on your phone, whether you have rooted or not.
Related
Hi,
I bought a Legend a couple of weeks ago and I been playing with it, I'm to afraid to try to root it and at the end I'm leaving this phone to my wife and getting something more high end for me.
Now I noticed that Froyo is out for the phone. But when I try to find the update OTA it says that my phone is up to date.
The specs are
Firmware version
2.1-update1
Baseband
47.39.35.09U_7.08.35.21
Software number
2.06.709.3
I don't want root access or anything (but if I need to root it I will), what I do is
Downloaded the debranded ROM
put it in the SD Card Root file.
Start the Phone in recovery mode
But I get a big red Triangle with a ! sign after that.
Do i need the "golden card" to be able to upgrade?
The Froyo update is not available to unbranded Legends yet. You just have to wait a few more days (maybe) for it to be released for unbrandeds or your specific carriers ROM.
If you really can't wait you can root your Legend to install the Vodafone Froyo ROM which is already available as rooted version here.
Here is a thread with a good overview of some important threads you might want to check:
Development FAQ
You will find the links to two threads you need to root your phone.
1. [HOWTO] DOWNGRADE to 1.31 which you can then root for Legend 2.1
2. [HOWTO] Rooting your Legend! Guide from MoDaCo!
after successfully rooting you can download "ROM Manager" from the Market and for example this rooted Froyo ROM:
[ROM]FroYo - Android 2.2 -Kernel 2.6.32.17 - Build on Vodafone release - ROOTED!. Just move the .zip to your SD Card and choose to install a ROM from SD in the ROM Manager menu.
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.
I rooted my HTC wildfire before xmas and now three have released the official update and i can not install this due to not backing up prior to rooting my mobile.
I was wondering if anyone has a CLEAN (not information on) nandriod back up of 2.1 i could please utilise to enable me to get the latest official three version
or a way to get the official update after rooting mobile would be great too
Thanks
Colin
There is an RUU at Shipped ROM's:
http://shipped-roms.com/index.php?category=android&model=Buzz
Look for this one:
RUU_Buzz_H3G_UK_1.16.771.2_Radio_13.45.55.24_3.35.15.31_release_131501_signed.exe
Remember though, you will not be able to root / install root apps / custom ROM's etc etc when you get the official 2.2.1 update.
Thanks
Thanks I did try this one this morning but it still wouldnt install for me I will however try again I have reset my wildfire back to factory setting and tried update which never worked either!
Just hope i manage to sort it out lol
Error on rom
When i try that RRU Rom i keep getting error [140]: BOOTLOADER VERSION ERROR
THe Rom update Utility cannot update your Android phone.
Please get the Correct Rom UPdate Utility and try again
I go into setting Software information
Firmware version
2.1 update1
Baseband vers
13.55.55.24h_3.35.20.10
Kernal Vers
2.6.29-6fb59e13
[email protected] #1
Build
1.26.771.1 CL231296 release-keys
Software number
1.26.771.1
Help!!
I did read the only way to get back to normal and be able to update OTA would be to go back to factory setting before root was enabled!
is there anyone with such a backup without number or software just as it is???
A while back, just before the 2.2 OTA update came out for ATT locked streaks I received a replacement streak from dell. I didn't have it long enough before I applied the update to remember if the compass or sensors were working, but I seem to remember the screen would auto rotate just fine.
After the update the screen would not auto rotate at all. I spent a while looking into fixing it, trying things like srchild.com's calibrate-sensor-on-upside-down-dell-streak-after-froyo-22-android-upgrade
But I have a slightly different version of the menu's than that tutorial shows and nothing I did fixed the auto rotate so I eventually just learned to live with it in landscape mode for a while.
Now I realize that no compass or sensor based apps work. I've installed sensor monitor apps and they show no data. The "Calibration" application that shows bubble levels doesn't move at all. I'm starting to think it is a hardware problem but like I said, I am almost sure that screen rotation worked before the upgrade on this device.
Is there a way to verify for sure before calling dell. Their support was a nightmare to deal with the first time.
TIA
Why go through the trouble? Why not root your Streak and flash a custom ROM. They perform much better.
If you don't like them then you could always use the QDL tool to get back to stock but everyone here knows the OTA updates wreak havoc for almost all Android devices
cdzo72 said:
Why go through the trouble? Why not root your Streak and flash a custom ROM. They perform much better.
If you don't like them then you could always use the QDL tool to get back to stock but everyone here knows the OTA updates wreak havoc for almost all Android devices
Click to expand...
Click to collapse
A new ROM, stock or custom, won't fix the problem if there is a hardware issue. Installing a different ROM might help troubleshoot the problem. I would suggest a stock ROM so that if the problem persists there is no questions concerning the warranty. 353 is the latest AT&T ROM and can be downloaded here.
You don't have to root and then install StreakDroid, you can install SD without rooting first.
The updates I have gotten for the Streak have been excellent. I run Stock 351. My streak was purchased unlocked from Dell. In addition the OTA update I got for my Moto Backflip was a huge improvement and the update on my wife's Inspire that enabled the setting to install non-market apps works fine. I would have to say that not everyone here agrees with your assessment of the OTA updates.
To the opening poster I would suggest a reset or reinstall of 353 and then test with no apps installed.
I should've specified the OTAs from DELL are notorious for causing issues.
And you are correct, not everyone here would agree with them, but if you like to tweak and play, then a stock ROM doesn't offer much flexibility, not to mention performance wise.
When I first got my Streak I bricked it, then I revived it with the QDL tool and then went to StreakDroid. Then I even went back to stock to have a baseline to compare with the StreakDroid beta I'm currently using, and I have to say, stock is just that, stock, it's two worlds, performance and battery on stock just don't compare to any of the custom ROMs.
I know this isn't the place for this discussion but I couldn't help but make my point. If you like the stock ROM, I'm happy for you, but I for one have never been much to settle for less, I'm always looking for the latest thing.
Having not looked into updating android a great deal I'd appreciate any corrections if I'm mistaken on this, but I do believe the over the air update that was installed is the 353 version.
My Streak currently reads:
Baseband version: GAUSB1A135331-US
Build number 15697
marvin02 if you still think downloading and installing the the 353 ROM you linked to would help diagnose the issue I'd be more than happy to, please let me know.
cdzo72 I do plan on installing custom rom's and even getting into Android development in the near future but I do not have time for it yet. I would like to make sure I do not have a hardware problem before installing any custom rom's because it will be easier (less time consuming for me) to make a warranty claim if I need to. Unfortunately right now functional and limited is better than cutting edge and time consuming for me when it comes to my Streak.
data_loss said:
. . .
My Streak currently reads:
Baseband version: GAUSB1A135331-US
Build number 15697
marvin02 if you still think downloading and installing the the 353 ROM you linked to would help diagnose the issue I'd be more than happy to, please let me know.
. . .
Click to expand...
Click to collapse
A fresh install would eliminate (mostly) the possibility that your problem is caused by software, not hardware. If you still have the stock recovery on your phone you can just download the .pkg file, put it on your SD Card, rename it to update.pkg and boot into recovery to install.
I do still have the stock recovery.
I downloaded and installed the 353 ROM. It appears that the sensors are not working (no auto screen rotation). I also tried a factory reset after the update just for giggles, no change.
If I'm not mistaken the Streak_104_4399_21.pkg that can be downloaded from the streakdroid site is the official att&t 1.6 ROM. Would it be worth downloading and downgrading to that to test?
Or at this point do I just endure the call to dell support?
Is there any kind of documentation available for the fastboot menu on the streak? There seems to be options available for sensor stuff in there but I don't want to be just clicking through them without knowing what they do.
One hour on the phone ( which was not much fun ) and a couple days later and I have a replacement. It is a refurb, but in good condition and it works. Thanks all for the help.
Sent from my Dell Streak using XDA App
I'm pretty new to the Android phones. I bought a Samsung Galaxy Note 8 tablet about a year ago, and I absolutely love it -- which was the only reason why I considered an Android phone when it came time to upgrade. That might have been a mistake.
The phone I chose was a Galaxy S5 from AT&T.
For many reasons I won't go into (and that many of you probably know) Kitkat is awful. Removing SD card access removed one of the most important reasons that I bought the phone. So, I decided to root the thing.
I read a bunch of info on how to root, and, eventually downloaded and tried to use towelroot only to discover that AT&T/Google have blocked all functionality of that program. My build is, unfortunately, the latest build -- July 22 2014 (or there abouts).
Now, I'm not sure if the phone was given to me with that update -- I only got the thing on Sunday. Maybe it was, maybe not. Dunno. So I have a couple of questions.
If I were to factory reset the phone, would that roll back these "Security" OTA updates that were pushed onto the phone? I'm pretty sure there was at least one after I got the thing. I've spent a fair amount of time setting the phone up, but I'll do it again if a factory reset would allow me to root the phone and return the SD card functions.
Is there a way to push an earlier version of the ROM onto the phone. I'm guessing not, since I think I read that AT&T helpfully locked the bootloader.
Finally, does anyone know of any way to root this device if neither of the two paths I presented above will work?
Thanks for any help. If I can't restore the SD card functionality, I'll probably just return the phone. That would be a bummer because I was really excited about it.
CKR83 said:
I'm pretty new to the Android phones. I bought a Samsung Galaxy Note 8 tablet about a year ago, and I absolutely love it -- which was the only reason why I considered an Android phone when it came time to upgrade. That might have been a mistake.
The phone I chose was a Galaxy S5 from AT&T.
For many reasons I won't go into (and that many of you probably know) Kitkat is awful. Removing SD card access removed one of the most important reasons that I bought the phone. So, I decided to root the thing.
I read a bunch of info on how to root, and, eventually downloaded and tried to use towelroot only to discover that AT&T/Google have blocked all functionality of that program. My build is, unfortunately, the latest build -- July 22 2014 (or there abouts).
Now, I'm not sure if the phone was given to me with that update -- I only got the thing on Sunday. Maybe it was, maybe not. Dunno. So I have a couple of questions.
If I were to factory reset the phone, would that roll back these "Security" OTA updates that were pushed onto the phone? I'm pretty sure there was at least one after I got the thing. I've spent a fair amount of time setting the phone up, but I'll do it again if a factory reset would allow me to root the phone and return the SD card functions.
Is there a way to push an earlier version of the ROM onto the phone. I'm guessing not, since I think I read that AT&T helpfully locked the bootloader.
Finally, does anyone know of any way to root this device if neither of the two paths I presented above will work?
Thanks for any help. If I can't restore the SD card functionality, I'll probably just return the phone. That would be a bummer because I was really excited about it.
Click to expand...
Click to collapse
For rooting, go there http://forum.xda-developers.com/showthread.php?t=2696537
or there http://forum.xda-developers.com/showthread.php?t=1980683
Follow tuto or ask here.
You have to give more info (S5 model, firmware...)
Good luck
Franky
Rooting Help?
fgth90 said:
For rooting, go there http://forum.xda-developers.com/showthread.php?t=2696537
or there http://forum.xda-developers.com/showthread.php?t=1980683
Follow tuto or ask here.
You have to give more info (S5 model, firmware...)
Good luck
Franky
Click to expand...
Click to collapse
I see that there are tutes here, and am wading through the 50+ pages of forum posts to find what I need. However, my worry is that none of this stuff will work because of the new firmware. Here is all the info that I have on my phone:
Galaxy S5 AT&T US version (SAMSUNG-SM-900A)
Android 4.4.2
kernel version 3.4.0-2178781 [email protected] #1 Tuesday July 22
Build # KOT49H.G900AUCU2ANG3
SE for Android Status
Enforcing SEPF_SAMSUNG-SM-G900A_4.4.2_0018 Tuesday July 22
Security Software version:
MDF v1.0 Release 3
VPN v1.4 Release 1
Thanks all the pertinent info, I think.
Because the update was so new, I don't think there's a way to root this anymore. People keep telling me to use ODIN and to download an earlier ROM (and I now have ODIN and an earlier ROM -- hopefully from a good source, but I have no idea if it is), but my impression is that this latest AT&T "security" update keeps you from reflashing the ROM because of the bootloader lockout.
Any further help would be appreciated.
Thanks
CKR83 said:
...
Any further help would be appreciated.
Thanks
Click to expand...
Click to collapse
Hello,
As I told you, the only method working for me (because of towelroot non working) is cf auto root.
Check periodicaly here http://autoroot.chainfire.eu/ to see if your model is listed.
I had just a look and it's not listed yet.
If it is, flash by odin and look if root works.
If not, you've got to flash by odin the same rom again (keep your original file on pc), you'll loose nothing, and report this fails on chainfire to test other solution.
Good luck
Franky
CKR83 said:
Here is all the info that I have on my phone:
Galaxy S5 AT&T US version (SAMSUNG-SM-900A)
Android 4.4.2
kernel version 3.4.0-2178781 [email protected] #1 Tuesday July 22
Build # KOT49H.G900AUCU2ANG3
SE for Android Status
Enforcing SEPF_SAMSUNG-SM-G900A_4.4.2_0018 Tuesday July 22
Security Software version:
MDF v1.0 Release 3
VPN v1.4 Release 1
Click to expand...
Click to collapse
Not only build number and kernel version, you need to check your Bootloader version with Phone INFO ★Samsung★ app (in the FIRMWARE INFO section).
Bootloader version is one of the important info to check when you are going to root or flashing custom rom.
vndnguyen said:
Not only build number and kernel version, you need to check your Bootloader version with (in the FIRMWARE INFO section).
Bootloader version is one of the important info to check when you are going to root or flashing custom rom.
Click to expand...
Click to collapse
Hey that looks like a great utility. Thanks! The bootloader is G900AUCU2ANG3
Does that help any? People keep telling me I need to use ODIN and flash this, that or the other thing. Those comments would probably be more helpful if I knew more about this stuff, but my reading has lead me to believe that ODIN won't work with certain version of the bootloader. Or is that wrong?
CKR83 said:
Hey that looks like a great utility. Thanks! The bootloader is G900AUCU2ANG3
Did you every get your post July 2014 AT&T GS5 rooted?
If so, please drop me an email.
Thanks
TPG
Click to expand...
Click to collapse
No unfortunately not....
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app