Related
I flashed 33 and my phone is stock. I need paid apps plus this build is bugging out on me alot. Stuff freezes, its just a bad build. How do I undo this without rooting?
Pretty sure you have to root.
If its like FRF91. Then it wont let you downgrade because it sees FRF91 as an "old version."
Download ere27 as passimg.zip. place in your sdcard root. Boot into recovery. Restore. Let it do its work. Put frf91 into sd card. Boot into recovery and load from zip. Ta da. You are on Frf 91
Sent from my Nexus One using Tapatalk
Or, if you want a shorter and more correct route:
Nexus One Wiki, "Restore", PASSIMG.ZIP method, use FRF91 complete stock image found in one of the threads in Q&A from the last day (or Google).
Don't use FRF91 update, since it's only an update - it's not a complete image.
whatever. Just use a passimg.zip to clean out all the crap. its basically the "do-over" method. Think etch-a-sketch flip and shake.
i tried passimg from http://forum.xda-developers.com/showthread.php?t=717870
it said failure because it was an older version. If i find that ere one will it let me do it? i dont mind going way back and working my way back to froyo, but i dont think i can passimg anything since its considered "older"
search the forum for how to downgrade your hboot- it exists just search for the thread
http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=726258
androidjedi said:
http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=726258
Click to expand...
Click to collapse
Thank you. Looks like ill have to root for it which im sure ill find if i search how to root 33 so ill wait for a while to see if something else comes up but at least I know there's a way
There is no other way but to root.
Since you're erasing the system you're rooting anyway, why do you care?
The full guide is now in the Wiki, including reverting HBOOT for those that need it.
Jack_R1 said:
There is no other way but to root.
Since you're erasing the system you're rooting anyway, why do you care?
The full guide is now in the Wiki, including reverting HBOOT for those that need it.
Click to expand...
Click to collapse
i dont know, i did 1 click root a few times but every rom i tried- cyan, eno, modac, whatever were great but there was always some bug or something that was annoying enough that i just wanted stock instead. So i dont know how much i like the idea of permanent root, but theres probably a stock rom i can use so its not the end of the world. SDK/Terminal i did all that crap with my g1, personally i found it to be more of a hassle than it was worth. But not having protected apps is not going to cut it so ill cave soon im sure
Again, maybe this time it'll be understood:
There is no "permanent root". The only "permanent" thing is unlocking the bootloader, which you don't have to do - the guide doesn't require it. The system you root will be erased in the PASSIMG method and replaced with a completely stock system of your choice. So, what's exactly stopping you from rooting?
Jack_R1 said:
Again, maybe this time it'll be understood:
There is no "permanent root". The only "permanent" thing is unlocking the bootloader, which you don't have to do - the guide doesn't require it. The system you root will be erased in the PASSIMG method and replaced with a completely stock system of your choice. So, what's exactly stopping you from rooting?
Click to expand...
Click to collapse
the only way to go back from FRG33 is to unlock the bootloader at this stage, the PASSIMG method does not work
When you revert HBOOT, it should work fine. Just the same as it works with Korean FRF91 version, which also has a new HBOOT. People in the FRG33 thread don't know it?
Why people can't understand?At this moment,if you've flashed stock FRG33 rom,using PASSIMG method,you can't root anymore!The only method to roll back to FRF91 is to unlock your bootloader,which is permanent and can't be un-done!
Cheers
Did you see that?
http://androidforums.com/1533396-post14.html
Or is it the only report? (in that case, the guy probably didn't try to run root).
Anyway, being unable to root makes you unable to flash PASSIMG of anything with bootloader lower than 0.35 - but did anyone try PASSIMG with Korean FRF91? It has the same HBOOT as FRG33, so it shouldn't be reported "older".
Jack_R1 said:
When you revert HBOOT, it should work fine. Just the same as it works with Korean FRF91 version, which also has a new HBOOT. People in the FRG33 thread don't know it?
Click to expand...
Click to collapse
Code:
[HOW-TO] Revert HBOOT 0.35.0017 to 0.33.0012
I CAN'T RELOCK THE BOOTLOADER!!!
This only reverts your SPL/HBOOT back to 0.33.0012 after you've installed the Korean FRF91 files and ended up stuck with 0.35.0017 SPL.
Thanks to the guys in the Desire forums and help from the Nexus Q&A, I have reverted my phone to the original HBOOT so I can apply custom roms again.
First you need to root the Korean FRF91 that's on your phone using Paul's instructions for superboot FRF83.
If you are rooted already, skip this step.
http://android.modaco.com/content/go...the-nexus-one/
Code:
How to use Superboot - Windows, Linux and OSX
- Download the Superboot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then press and hold the trackball to enter the bootloader
- WINDOWS - double click 'install-superboot-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-mac.sh' followed by './install-superboot-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-linux.sh' followed by './install-superboot-linux.sh'
Note: If you are using a retail Nexus One, you may need to unlock the bootloader first, as detailed here.
Ok, let's make some order:
1) PASSIMG can flash versions with the same or higher HBOOT version - to check: will the same version flash? I believe so.
The official FRF91 has HBOOT 0.33.0012, the Korean FRF91 has 0.35.0017, and I suppose the FRG33 also has 0.35.0017 - correct?
2) Rooting isn't possible on FRG33 yet. 1 report doesn't count.
So, looking at this:
Using PASSIMG with the Korean FRF91 (complete with HBOOT 0.35.0017) will work over FRG33, if the HBOOT is indeed the same version.
Korean FRF91 is rootable.
Rooting Korean FRF91 allows to downgrade HBOOT, which in order allows to use PASSIMG method to flash official FRF91 with older HBOOT.
So, did anyone try PASSIMG with Korean FRF91?
Jack_R1 said:
Did you see that?
http://androidforums.com/1533396-post14.html
Or is it the only report? (in that case, the guy probably didn't try to run root).
Anyway, being unable to root makes you unable to flash PASSIMG of anything with bootloader lower than 0.35 - but did anyone try PASSIMG with Korean FRF91? It has the same HBOOT as FRG33, so it shouldn't be reported "older".
Click to expand...
Click to collapse
Downloading and testing, thanks for the tip, will report back.
My N1 on Rogers is currently at (unrooted) stock 2.3.6, with baseband version 32.41.00.32U_5.08.00.04.
My data connection constantly hangs and then drops. I'd really like to flash the radio to 32.50.00.32U_5.12.00.08, but I have no idea how.
I can only find guides which flash the radio along with Cyanogen, but I ONLY want to flash the radio, without any custom ROM (I want to stick with stock 2.3.6).
How do I go about doing this?
The recommended way to flash a radio is through fastboot (which you need an unlocked bootloader for) but you can also use a flashable zip through recovery but it is crucial that you check md5 sum because flashing a radio is the easiest way to brick you phone if it is corrupt us something.
Thanks, and this doesn't require rooting?
No sorry forgot to mention flashing a radio requires root and I don't recommend you flash a radio until you are comfortable with all the rooting stuff because like I said it's the easiest way to brick your phone.
I doubt your problems is with your radio anyway
Why do you say that?
I had no problems with my 3g data connection until after Gingerbread was pushed to my phone. I believe the new 5.08 radio was included 2.3.
The 5.08 radio is the radio that seems to have the least amount of issues. I am sure google did a lot of research and testing before they decided to send out the 5.08 with Gingerbread rather than the 5.12.
But, to flash a radio, you either need to have your bootloader unlocked so you can flash it with fastboot, or you need your phone rooted so you can flash it with a custom recovery.
It isn't possible to do it staying completely stock.
Is there a way he can reflash OTA
Did you double check your apn's
Pull or replace sim
Pull battery
Call carrier
Hi all.
I have a rogers HTC dream that I need to unbrick. It is rooted, but I have no recovery at all. Have tried several times to install a recovery, to no avail.
Maybe if I follow an unbrick instructions, I will be able to salvage this device.
Right now, it is still working properly, but I cannot do a factory reset because of no recovery. Need to do a factory reset because I am giving it to a family member.
Thanks
Heeter
Sent from my Nexus S using xda premium
Any help would be greatly appreciated.....
Thanks
Heeter
Heeter said:
Any help would be greatly appreciated.....
Thanks
Heeter
Click to expand...
Click to collapse
Is it a custom rom and you just want to reset the phones data (ie wipe your personal data)? This is prob best as long as the current custom rom worked well for you.
Regardless go into fastboot (turn on holding camera) tell us the radio/spl, then if possible tell us what rom you are using (if known) and more importaint are you rooted?
Edit: nvm about the rooted question, the rest applies
Good Morning ezTerry
It is a completely factory stock rogers Dream (factory ROM). I did use the one-click root and that worked.
I never had a chance to put in another recovery or spl/radio. Cannot at all boot into recovery.
I can boot into fastboot, and I will post what I see when I get home.
BTW, on a side note, I would like to say thanks for all your work, ezTerry, I have been using all your releases for my other HTC Dream.
Heeter
Heeter said:
It is a completely factory stock rogers Dream (factory ROM). I did use the one-click root and that worked.
I never had a chance to put in another recovery or spl/radio. Cannot at all boot into recovery.
Click to expand...
Click to collapse
If that's the case you just want to flash the rogers e911 patched nbh:
Information on the xda wiki
Of course if this phone is going to be used off the rogers network it might be kinder to root it, install the 2708+ radio SPL and my the MT3G ota froyo port to the dream.. As that is still quite stock but gets rid of the rogers e911 patched radio that has very unstable 3g support. (And the rom is easier to deal with)
If it will be used on rogers network there is not much to be done, rogers still scans once a month for those using any radio besides the new rogers one and cuts the data.
ezterry said:
If that's the case you just want to flash the rogers e911 patched nbh:
Information on the xda wiki
Of course if this phone is going to be used off the rogers network it might be kinder to root it, install the 2708+ radio SPL and my the MT3G ota froyo port to the dream.. As that is still quite stock but gets rid of the rogers e911 patched radio that has very unstable 3g support. (And the rom is easier to deal with)
If it will be used on rogers network there is not much to be done, rogers still scans once a month for those using any radio besides the new rogers one and cuts the data.
Click to expand...
Click to collapse
Hey, a million thanks for this, ezTerry.
I will post later today as to the outcome of this reflash.
As it is right now, it is getting the 3G from rogers right now, if this works out, I am going to root it, and install the 2708 and radio SPL as well as that froyo port. I am sending it to a family member in Montreal, also on Rogers.
Heeter
Well this is a kicker,
The Dream is saying "Fastboot USB" on the screen, but I cannot connect to it through fastboot.
I know my fastboot is working as my other phones are showing in the fastboot devices list.
I am using my terminal on my Linux workstation (LinuxMint12)
Maybe my fastboot is too new for the older devices?
Anyways, here is my Fastboot Info:
Code:
Dream PVT 32B SHIP S-ON d
HBOOT-1.33.0010 (DREA21000)
CPLD-4
RADIO-3.22.26.17
Jun 2 2009,21:33:16
Is there a way I can do this through the SDcard?
Heeter
as a DREAIMG.nbh on the root of the SD as usual will also work...
Never had a problem with older vs newer fastboot builds.. hope its not an indicator of a larger issue.
Thanks for sticking with me, ezTerry
I renamed it to DREAIMG.nbh, and now it is loading off sdcard.
Yahoo!! I got a recovery, and a factory reset.
I still can't fastboot into the phone still.
What now?
Thanks again,
Heeter
I will be bringing the Dream to work with me,
I will install the SDK on my Windows7 workstation, hopefully fastboot can work from there.
Which directions should I follow now for the flashing of the radio spl & cwm?
Thanks
Heeter
I am now into fastboot!
How do I turn off the security, because I cannot flash anything (Remote: not allow)
Thanks
Heeter
Heeter said:
I am now into fastboot!
How do I turn off the security, because I cannot flash anything (Remote: not allow)
Thanks
Heeter
Click to expand...
Click to collapse
You can't on the stock split, to flash the NBH you were supposed to first switch to RUU mode." (Via 'fastboot oem rebootRUU' as per the unrooting instructions on the xda wiki)
However if you flashed the nbh you no longer need fastboot yet, just check 'fastboot devices' to make sure its working
To root and follow the rooting instructions on the same xda wiki page I sent earlier, no shortcuts..
After you are rooted and 1.33.2005 is installedyou can install the extra memory radio by fastboot http://forum.xda-developers.com/showthread.php?t=831139 (again no shortcuts)
However since you are giving this to someone else on the rogers network I *DON'T* recommended changing the radio since their data will be blocked on the first business day of Jan unless they successfully sign the rogers e911 wavier. Because of this its best the recipient understand what this means.
Thanks, ezterry
I am leaving it stock and shipped it out today.
Thanks for all your help last couple of days.
Heeter
Hi everyone!
This is my first post, since I never had any trouble toying around with my device. I have a rooted Incredible S, that ran MIUI perfectly. I want to return back to stock (this is imperative) and use the official ICS by HTC. I tried putting back my nandroid backup, which didn't work (perhaps an incompatible radio? I have no idea...). That's when I downloaded a stock, cracked ROM from a thread I found here. This is a Gingerbread ROM with Sence 3.0 I think. Obviously, I can't get the OTA to work. I think the issue here is that my recovery is still CWM, and that OTA only works with the stock recovery (this is what I concluded from research).
This is where I'm having trouble. A RUU doesn't seem to recognise my device, so that's not an option right now. Windows recognises my SD card when I hook up my phone through USB, so I can install ROMs just fine. Is there any way to get the stock recovery and the stock ROM without using a RUU, while keeping my device rooted? I really want all of this to be stock, so no mods, hacks or tweaks. I want my phone to be in the same state as when I bought it and rooted it, before installing custom ROMS. Is this possible?
Many, many thanks in advance!
gladii said:
Hi everyone!
This is my first post, since I never had any trouble toying around with my device. I have a rooted Incredible S, that ran MIUI perfectly. I want to return back to stock (this is imperative) and use the official ICS by HTC. I tried putting back my nandroid backup, which didn't work (perhaps an incompatible radio? I have no idea...). That's when I downloaded a stock, cracked ROM from a thread I found here. This is a Gingerbread ROM with Sence 3.0 I think. Obviously, I can't get the OTA to work. I think the issue here is that my recovery is still CWM, and that OTA only works with the stock recovery (this is what I concluded from research).
This is where I'm having trouble. A RUU doesn't seem to recognise my device, so that's not an option right now. Windows recognises my SD card when I hook up my phone through USB, so I can install ROMs just fine. Is there any way to get the stock recovery and the stock ROM without using a RUU, while keeping my device rooted? I really want all of this to be stock, so no mods, hacks or tweaks. I want my phone to be in the same state as when I bought it and rooted it, before installing custom ROMS. Is this possible?
Many, many thanks in advance!
Click to expand...
Click to collapse
Hey mate, official welcome from me Second welcome from me today lol
I would advise against going s-on and fully stock.
You cannot run a ruu or ota with a custom recovery/root.
So the easiest way to get the stock experience you want is by flashing one of tpbklake's rooted stock roms. They are basically stock roms with root and can run on a custom recovery. No tweaks or anything
http://forum.xda-developers.com/showthread.php?t=1773520
http://forum.xda-developers.com/showthread.php?t=1756500
The link above (top one) is based off a newer ruu from asia, although there is not much difference
I would also suggest to try ARHD 3.0.x for the stock optimised rom
Also which bootloader version do you have?
gladii said:
Hi everyone!
This is my first post, since I never had any trouble toying around with my device. I have a rooted Incredible S, that ran MIUI perfectly. I want to return back to stock (this is imperative) and use the official ICS by HTC. I tried putting back my nandroid backup, which didn't work (perhaps an incompatible radio? I have no idea...). That's when I downloaded a stock, cracked ROM from a thread I found here. This is a Gingerbread ROM with Sence 3.0 I think. Obviously, I can't get the OTA to work. I think the issue here is that my recovery is still CWM, and that OTA only works with the stock recovery (this is what I concluded from research).
This is where I'm having trouble. A RUU doesn't seem to recognise my device, so that's not an option right now. Windows recognises my SD card when I hook up my phone through USB, so I can install ROMs just fine. Is there any way to get the stock recovery and the stock ROM without using a RUU, while keeping my device rooted? I really want all of this to be stock, so no mods, hacks or tweaks. I want my phone to be in the same state as when I bought it and rooted it, before installing custom ROMS. Is this possible?
Many, many thanks in advance!
Click to expand...
Click to collapse
Yes there a some ROMs in the Development section that are completely stock that you can flash through recovery.
The original GB 2.3.3/Sense 2.1, the GB 2.3.5/Sense 3.0 and the latest ICS 4.0.4/Sense 3.6
markj338 said:
Hey mate, official welcome from me Second welcome from me today lol
I would advise against going s-on and fully stock.
You cannot run a ruu or ota with a custom recovery/root.
So the easiest way to get the stock experience you want is by flashing one of tpbklake's rooted stock roms. They are basically stock roms with root and can run on a custom recovery. No tweaks or anything
http://forum.xda-developers.com/showthread.php?t=1773520
http://forum.xda-developers.com/showthread.php?t=1756500
The link above (top one) is based off a newer ruu from asia, although there is not much difference
I would also suggest to try ARHD 3.0.x for the stock optimised rom
Also which bootloader version do you have?
Click to expand...
Click to collapse
I'm going to sell my device so I need it back the way it was. I want to keep it rooted though, so that the next owner can decide for himself what he wants to do with it. If he he's no techie, he can enjoy the device in stock (including OTAs, or can this be done like you mentioned?). If whe wants to toy with it, he can do that too. If it's easier to just go back to stock entirely, that's fine too.
It seems that I can no longer get into hboot now? After installing that hacked gingerbread, my device just boots into Android when pressing volume down and power??
tpbklake, I'll try to flash one of those when I can get back into recovery
Weird.. Taking out the battery fixed my recovery issue. I'll flash that ROM
Btw I seem to have hboot 6.13.1002 and radio 3805.06.03.03_M. Is this the info you need?
gladii said:
Weird.. Taking out the battery fixed my recovery issue. I'll flash that ROM
Btw I seem to have hboot 6.13.1002 and radio 3805.06.03.03_M. Is this the info you need?
Click to expand...
Click to collapse
Yes
But since you want stock it won't matter
You CANNOT have both root and ota updates
Either one or the other unfortunately
You have to make a choice a rooted stock ROM will be identical to the official ota from htc but you will be able to keep root, but can't get ota updates
but unfortunately I think sense 3.6 4.0.4 is the last update
But, I have been proven wrong before
Sent from my Nexus 7
K then in my case a full stock device would be best. How do I get started with this? First install a stock ROM, then the stock recovery and then put It back in S-OFF? Which ROM should I install (would prefer the stock 2.3.3)? And where can I find the recovery? Sorry for the basic questions but those lists of ROMs can get a bit complicated..
Still getting nowhere If I flash a stock ROM in CWM, my recovery won't go back to stock, will it? Shouldn't I try to get the stock recovery first and then use a RUU? Problem is that I can't seem to find a stock recovery anywhere. And when I extract the ROM from a RUU, it's only about 180 MB, so that can't be right, can it?
gladii said:
Still getting nowhere If I flash a stock ROM in CWM, my recovery won't go back to stock, will it? Shouldn't I try to get the stock recovery first and then use a RUU? Problem is that I can't seem to find a stock recovery anywhere. And when I extract the ROM from a RUU, it's only about 180 MB, so that can't be right, can it?
Click to expand...
Click to collapse
Which ruu? Here's a good guide http://forum.xda-developers.com/showthread.php?t=1359555 but I find it faster to flash the alparev then run the ruu, 2 steps and done.
Nonverbose said:
Which ruu? Here's a good guide http://forum.xda-developers.com/showthread.php?t=1359555 but I find it faster to flash the alparev then run the ruu, 2 steps and done.
Click to expand...
Click to collapse
Sorry for the late reply. I've been busy with exams. I've tried the RUU RUU_IncredibleC_Verizon_WWE_1.22.605.0_Radio_1.00.03.04.06_release_161493_NoDriver (but I don't actually have a Verizon, could that be the problem?).
I really have no idea what all the info in the filename means, so it's difficult to find one that fits my needs. I'll take a look at your link right now and report back!
gladii said:
Sorry for the late reply. I've been busy with exams. I've tried the RUU RUU_IncredibleC_Verizon_WWE_1.22.605.0_Radio_1.00.03.04.06_release_161493_NoDriver (but I don't actually have a Verizon, could that be the problem?).
I really have no idea what all the info in the filename means, so it's difficult to find one that fits my needs. I'll take a look at your link right now and report back!
Click to expand...
Click to collapse
DO NOT attemtp to flash that one!!!! The Verizon DINC2 is a CDMA device and the radio is not compatible.
Please read the post that nonverbose referenced for you. That tells you all you need to do.
tpbklake said:
DO NOT attemtp to flash that one!!!! The Verizon DINC2 is a CDMA device and the radio is not compatible.
Click to expand...
Click to collapse
Wow, good thing it didn't succeed! How about this one:
RUU_Vivo_Gingerbread_S_HTC_ARA_2.30.415.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199399_signed.exe
(download link: http://www.filefactory.com/file/c0af340/n/RUU_Vivo_Gingerbread_S_HTC_ARA_2.30.415.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199399_signed.exe)
gladii said:
Wow, good thing it didn't succeed! How about this one:
RUU_Vivo_Gingerbread_S_HTC_ARA_2.30.415.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199399_signed.exe
(download link: http://www.filefactory.com/file/c0a...5AU_3805.06.03.03_M_release_199399_signed.exe)
Click to expand...
Click to collapse
What region of the world are you in? I would recommend the HTC WWE 2.30.405.1.
tpbklake said:
What region of the world are you in? I would recommend the HTC WWE 2.30.405.1.
Click to expand...
Click to collapse
Belgium (Brussels), western Europe. I bought the device here so it should be pretty local... I'll try that one. What does the WWE mean? (Just for the info)
gladii said:
Belgium (Brussels), western Europe. I bought the device here so it should be pretty local... I'll try that one. What does the WWE mean? (Just for the info)
Click to expand...
Click to collapse
World Wide English with support for most European languages
gladii said:
Belgium (Brussels), western Europe. I bought the device here so it should be pretty local... I'll try that one. What does the WWE mean? (Just for the info)
Click to expand...
Click to collapse
Ah, perfect! Canceled my download, but there's a 20 minute interval before starting a new one, so it'll take me at least an hour to download it.
I've encountered this issue before, but randomness seemed to solve it back then: a fastboot command just displays "<waiting for device>" and then keeps hanging there. "fastboot devices" returns an empty line, so that's consistent. Phone is in fastboot USB mode, so I'm not sure what could be the issue?
And then I have a question. In that guide, it says that I should extract HBOOT.img from the rom I installed. In my case, my rom only contains a file named "hboot_1.13.0000_CRC_8a731c6e_0401.img" (along with others of course, but I assume they are redundant in this step); will that one do?
gladii said:
I've encountered this issue before, but randomness seemed to solve it back then: a fastboot command just displays "<waiting for device>" and then keeps hanging there. "fastboot devices" returns an empty line, so that's consistent. Phone is in fastboot USB mode, so I'm not sure what could be the issue?
And then I have a question. In that guide, it says that I should extract HBOOT.img from the rom I installed. In my case, my rom only contains a file named "hboot_1.13.0000_CRC_8a731c6e_0401.img" (along with others of course, but I assume they are redundant in this step); will that one do?
Click to expand...
Click to collapse
Sounds like it may be a port issue, cable issue or driver issue on the PC.
Have you tried different ports or a different cable? Do you have HTC Sync running in the System Tray on the PC?
As for the hboot file, yes that is the one.
gladii said:
And then I have a question. In that guide, it says that I should extract HBOOT.img from the rom I installed. In my case, my rom only contains a file named "hboot_1.13.0000_CRC_8a731c6e_0401.img" (along with others of course, but I assume they are redundant in this step); will that one do?
Click to expand...
Click to collapse
I thought you wanted to go to stock ICS? Hboot 1.13 it a gingerbread hboot. If you just flash the vivo_downgrade.img then run the ruu, there will be no need to extract and flash the hboot from the ruu.
Nonverbose said:
I thought you wanted to go to stock ICS? Hboot 1.13 it a gingerbread hboot. If you just flash the vivo_downgrade.img then run the ruu, there will be no need to extract and flash the hboot from the ruu.
Click to expand...
Click to collapse
No I wanted it back the way I wanted it. Rom, recovery,... all stock. But surely I'll give ICS a testdrive via OTA
hi.
I was using HTC One with Android Revolution and I would like to go back to stock.
unfortunately I have lost my nandroid and radio back ups (updated radio to latest one)
I was able to get nandroid backup from xda (thank you)
and restore it. however when I try to OTA update or factory reset it says security warning in bootloader
researching through google I realized that updated radio prevents me from doing OTA update and factory reset.
Is it possible to get a radio back up for bell or does anyone know how to make it work?
Thank you!
bibliog daniona
jkpark17 said:
hi.
I was using HTC One with Android Revolution and I would like to go back to stock.
unfortunately I have lost my nandroid and radio back ups (updated radio to latest one)
I was able to get nandroid backup from xda (thank you)
and restore it. however when I try to OTA update or factory reset it says security warning in bootloader
researching through google I realized that updated radio prevents me from doing OTA update and factory reset.
Is it possible to get a radio back up for bell or does anyone know how to make it work?
Thank you!
Click to expand...
Click to collapse
I am in a similar situation... I found the stock OTAs, which apparently have the stock radios. The only difference is that I don't want to go back to stock everything, just stock radio. Maybe we can help each other out?
h t t p : / / bugsylawson.com/files/category/216-otas/ <-- remove spaces, I am not allowed to post URLs...
I assume OTA_M7_UL_JB_50_BM_1.29.666.17_R-1.29.666.5_release_318664_signeddb6wjtuapczkgotc.zip the BM stands for Bell Mobility (assuming you are in Canada also).
Do you (or anyone reading) have an way to just extract the radio firmware and keep the root/ROM portion of my phone alive?
Reason is, the radios in Android Revolution HD for Canada I think are the Rogers ones, and I lost my HSPA+. Meaning I go between 3G and LTE (which is not too often).
Thanks in advance!
Did you guys ever find a Bell Radio File?
I am also looking for a Bell Mobility Radio.
vinistois said:
Did you guys ever find a Bell Radio File?
Click to expand...
Click to collapse
Here is my radio.img from my BM__001 phone. It's in a CWM recovery flashable zip.
https://docs.google.com/file/d/0B3TzI9suqxcwbzFxRFVETUZoOHc/edit?usp=sharing
eradicator006 said:
Here is my radio.img from my BM__001 phone. It's in a CWM recovery flashable zip.
https://docs.google.com/file/d/0B3TzI9suqxcwbzFxRFVETUZoOHc/edit?usp=sharing
Click to expand...
Click to collapse
Thanks! Curious if you are using the radio with the stock BM firmware or with a newer version firmware. Also how can I backup my radio using CWM so I can restore it if the provided radio doesnt work out for me.
ams75 said:
Thanks! Curious if you are using the radio with the stock BM firmware or with a newer version firmware. Also how can I backup my radio using CWM so I can restore it if the provided radio doesnt work out for me.
Click to expand...
Click to collapse
I'm not using that radio anymore. That radio was taken from my One the day I got it a month ago. I have since done the full GPE conversion and am using the radio that it comes with.
You can't backup your radio directly using CWM. You have to use dd and manually dump the radio partition to a file.
eradicator006 said:
Here is my radio.img from my BM__001 phone. It's in a CWM recovery flashable zip.
https://docs.google.com/file/d/0B3TzI9suqxcwbzFxRFVETUZoOHc/edit?usp=sharing
Click to expand...
Click to collapse
Alas, this link is dead. Anybody has an alternate location?
esternin said:
Alas, this link is dead. Anybody has an alternate location?
Click to expand...
Click to collapse
All M7_UL (except some asian CIDs) are now using the same radio version on lollipop: 4T.35.3218.16_10.33Q.1718.01L including Bell Mobility
which you can confirm when looking at the Bell Mobility RUU name: PN07IMG_M7_UL_L50_SENSE60_MR_BM_7.17.666.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420193_signed.zip
and can be found here: https://www.androidfilehost.com/?fid=95916177934533840
Or can be extracted from any M7_UL 7.xx.xxx.x firmware. :good:
alray said:
All M7_UL (except some asian CIDs) are now using the same radio version on lollipop: 4T.35.3218.16_10.33Q.1718.01L including Bell Mobility
which you can confirm when looking at the Bell Mobility RUU name: PN07IMG_M7_UL_L50_SENSE60_MR_BM_7.17.666.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420193_signed.zip
and can be found here: https://www.androidfilehost.com/?fid=95916177934533840
Or can be extracted from any M7_UL 7.xx.xxx.x firmware. :good:
Click to expand...
Click to collapse
Thanks!
I already tried that one, and my ex-Verizon phone (S-off, MID & CID adjusted, appropriate LTE bands enabled, build.prop changed to Bell/302610) still would not connect with a Bell SIM. I am now contemplating finding an older hboot/radio and trying to revert to 4..2-4.3. Do you have an opinion on this idea?