Disclaimer: You may brick your phone. NOT for AT&T
Reminder: Make sure your phone has enough battery charge to flash this, it's larger than normal.Hi,
Here is a huge CWM zip that restores your Bell phone to stock 2.2.2. I have tested it on my phone several times and it worked perfectly, there is still the chance that something may go wrong, but I am feeling confident in it.
What this does is similar to my app or scripts, it puts my backup of Bell's 2.2.2 partitions on your phone, but instead of using dd, it uses tenfar's CWM and flash_image. Some partitions are HUGE, and take a while, your phone is not locked up.
This has been updated to include the Bell bootloader for 2.2.2 and the radio for 2.2.2.
EDIT: This has been updated again to ram fix the boot and recovery partitions if there is a ram problem.
It writes to partitions 1, 2, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 17. 3 is left out because it's your pds partition, and data and cache have no relevant content. You must factory reset after using this to clear those. So, that's your boot, recovery, system, webtop, cdrom, preinstall, and several other partitions. This is to get back to stock Bell 2.2.2, it's not just a boot/system replacement, if that is a fruitcake, this is a gobstopper.
Please note: This restores your Bell phone to stock condition, that means you won't be unlocked, CWM will be overwritten with the stock recovery. It will be just like you bought it. If you want to keep flashing things in CWM with the unlocked bootloader, then immediately after flashing the stock zip, flash the unlock and fix zip. If you don't then you will have to reflash an unlocked bootloader, and reflash CWM recovery, which is time consuming any annoying, it doesn't mean you will be permanently locked again. I had to spell that out to the folks that don't really understand this stuff. At all.
If you want root after installing this, just install Superuser.apk from the market.
Bell_FR_2.2.2.zip (Froyo not France)
(md5 e431b4cc3ba7e3a27b6aad6982a31066)
Cheers!Oh, I forgot to mention, this is not quite stock, there are su and sudo binaries in /system/bin. Just install Superuser.apk to be rooted. they haven't been a problem for doing an OTA yet, but they are easy enough to remove if it comes up.
unlocked-fixed-Bell-2.2.2.zip
Mirror: unlocked-fixed-Bell-2.2.2.zip
Damn, nice work as always, man! This should come in handy for lots of us Bell Atrix users that feel left out. Lots will appreciate this!
When you say without amnesia are you talking about the bootstrap or are you talking about a user who is using the bell_ihop and then installs cwm and then reboots and looses recovery?
So a 2.3.4 bootloader and radio will work find booting a 2.2.2 bell ?
Will you eventually be able to compile a zip for Bell gingerbread?
IrshaadH said:
Will you eventually be able to compile a zip for Bell gingerbread?
Click to expand...
Click to collapse
the problem would be hosting it, not sure how he would be able to do that.
akurit said:
When you say without amnesia are you talking about the bootstrap or are you talking about a user who is using the bell_ihop and then installs cwm and then reboots and looses recovery?
So a 2.3.4 bootloader and radio will work find booting a 2.2.2 bell ?
Click to expand...
Click to collapse
keeping in mind that this is only for the recovery with unlocked devices, what he means is that the CWM recovery that tenfar put out has a problem with int'l phones (pretty sure it's all int'l) where IN recovery (not just the normal ROM, like the problem we had before) only 300 and some mb of RAM is available. since this zip is over 300mb, it can't all load into your RAM properly with normal recovery.
NFH found this bug, and patched recovery for us so as to fix the RAM problem. the two files attached are fixed recoveries for the two separate MBR versions of int'l devices.
to find what version you should use, connect to phone via ADB and then
Code:
adb shell
su
cat /proc/cmdline
and then search for the part of the output where it says "tegrapart=mbr:" and read that. it should have either "1100" or "d00" somewhere in it, use the CWM zip attached that has your respective output.
hope that clears up your question, if you have any further ask them in here.
IrshaadH said:
Will you eventually be able to compile a zip for Bell gingerbread?
Click to expand...
Click to collapse
Hi,
I believe y2whisper may be working on something like that. The point of getting back to stock 2.2.2 is to be able to apply the final OTA for Bell GB. Certainly something similar can be done for any firmware you want to flash.
Cheers!
i flashed the d00 and I do maintain unlock however no cwm just stock recovery with no menus.
tried it again and it work
but seems like i have to fastboot flash it each time i want to use recovery
akurit said:
i flashed the d00 and I do maintain unlock however no cwm just stock recovery with no menus.
tried it again and it work
but seems like i have to fastboot flash it each time i want to use recovery
Click to expand...
Click to collapse
I know what you are talking about, but I got that with a stock bootloader.
If you are going to be using CWM recovery with this 2.2.2, then flash the boot file for d00 as well, it gives you the ram fix and for some reason it doesn't cause that issue.
Cheers!
Here is an international CWM recovery, it detects the 1100 vs d00 tegraparts and installs the right recovery for it.
CWM_INT_Recovery.zip
(Just use it with whatever CWM recovery you are using now, it will update it with the ram fixed one.)
NFHimself said:
I know what you are talking about, but I got that with a stock bootloader.
If you are going to be using CWM recovery with this 2.2.2, then flash the boot file for d00 as well, it gives you the ram fix and for some reason it doesn't cause that issue.
Cheers!
Here is an international CWM recovery, it detects the 1100 vs d00 tegraparts and installs the right recovery for it.
CWM_INT_Recovery.zip
(Just use it with whatever CWM recovery you are using now, it will update it with the ram fixed one.)
Click to expand...
Click to collapse
ohhh, that's a nicely scripted installer you got there. i think that would be quite handy for int'l users trying to flash custom kernels, is it possible to apply that script to select the correct boot.img out of two for the right tegrapart? if that's possible i think you should hit faux/edgan up with that script and let them apply it to their int'l kernels so users can just use on CWM to install it.
raybond25 said:
ohhh, that's a nicely scripted installer you got there. i think that would be quite handy for int'l users trying to flash custom kernels, is it possible to apply that script to select the correct boot.img out of two for the right tegrapart? if that's possible i think you should hit faux/edgan up with that script and let them apply it to their int'l kernels so users can just use on CWM to install it.
Click to expand...
Click to collapse
Hi,
Sure, it's just replacing the word recovery with boot and having the right boot images in the file.
Cheers!
yes its zipping now. off to bed but tomorrow I will back up my stuff and attempt to flash to see if it works.
@akurit
I forget off the top of my head but there is a file that you just have to delete to prevent that. the file just flashes the old recovery on every reboot. get rid of that and you will be fine.
Awesome work! This makes it much easier to get back to 2.2.2
Its installing now!
now at some point the install stopped and I think I saw it say status 0 and then recovery rebooted. so I am not sure what happened there.
ive rebooted with no problems. and its uploading now. if someone is willing to test this out (a bit difficult for me since I am already on 2.3.4) let me know. and will send you the link. would like to see a proper install before i share it with the masses.
This is why hehee
tenfar said:
......
Please Remove install_recovery.sh located in your /system/etc/ ,so that the recovery will not be overwrite to stock one.........
Click to expand...
Click to collapse
now it remains unlocked and I have recovery even if i reboot... but the ram issue still exists
y2whisper said:
Its installing now!
now at some point the install stopped and I think I saw it say status 0 and then recovery rebooted. so I am not sure what happened there.
ive rebooted with no problems. and its uploading now. if someone is willing to test this out (a bit difficult for me since I am already on 2.3.4) let me know. and will send you the link. would like to see a proper install before i share it with the masses.
Click to expand...
Click to collapse
i could test it for you, i should be able to tell if it works alright or not, since i'm starting from an AT&T build of 2.3.4. would i have to head back to stock Bell using Gobstopper before i use your package too? i got a whole buncha time on my hands this week, so i should be able to test it however you want.
anyone try flashing the bootloader and radio?
kevnb said:
anyone try flashing the bootloader and radio?
Click to expand...
Click to collapse
Hi,
I have tested it, no problems, but went back to IHOP and the ram-fixed bootloader for 2.2.2 in the OP so recovery will work.
Also, the file install_recovery.sh located in your /system/etc/ doesn't exist in the Gobstopper, so that isn't causing recovery to be generated by patching boot.
Cheers!
So its when flashing the webtop that the install stops with the error code. when i boot up all is ok but a reboot later and recovery is gone (as in you select it and it just boots into android). reflashing cwm recovery fixes that.
I have tried swapping the webtop files to no avail. going to keep trying. any ideas are welcome
y2whisper said:
So its when flashing the webtop that the install stops with the error code. when i boot up all is ok but a reboot later and recovery is gone (as in you select it and it just boots into android). reflashing cwm recovery fixes that.
I have tried swapping the webtop files to no avail. going to keep trying. any ideas are welcome
Click to expand...
Click to collapse
Hi,
What recovery are you using, if it's not ram fixed you are going to run into situations where you don't have enough space to flash it.
Cheers!
ahhhh.
you know i was wondering if that was it. I even repackaged the recovery thinking it would be the cause.
I don't believe I was ram fixed at the time of the backup. So I am thinking either, have custom recovery flashed in that spot, or change the order to where recovery gets flashed after.
Good afternoon all,
I have an HTC One PN072. I've flashed the phone from Sprint to Cricket. They were very adamant about me not "resetting" the phone as it will remove the information, or flash they've added.
I've done several searches and can't seem to find a thread indicating 1) if this is possible and 2) a guide to doing so. The phone already is rooted and has TWRP on it as well.
If anyone knows of a thread I would love a link to a guide.
heartspains88 said:
Good afternoon all,
I have an HTC One PN072. I've flashed the phone from Sprint to Cricket. They were very adamant about me not "resetting" the phone as it will remove the information, or flash they've added.
I've done several searches and can't seem to find a thread indicating 1) if this is possible and 2) a guide to doing so. The phone already is rooted and has TWRP on it as well.
If anyone knows of a thread I would love a link to a guide.
Click to expand...
Click to collapse
I have a Sprint One fully flashed to Verizon and I flash custom ROMs all the time without any problems. I have never lost any settings and I don't even have to re-activate my phone. I would think that as long as you dont use Bootloader to flash a complete RUU image you should be fine. Goin s-off if your not already might cause issues here as well. (If someone knows for sure please correct me) I would say just download a ROM and install it with TWRP. I have updated firmware as well with no issues as well, however the firmware I upgraded with did not contain a radio update, which I am hesitant to do since I imagine that will effect my flash. I did my flash myself but it seems like a headache re-doing it.
electroblood said:
I have a Sprint One fully flashed to Verizon and I flash custom ROMs all the time without any problems. I have never lost any settings and I don't even have to re-activate my phone. I would think that as long as you dont use Bootloader to flash a complete RUU image you should be fine. Goin s-off if your not already might cause issues here as well. (If someone knows for sure please correct me) I would say just download a ROM and install it with TWRP. I have updated firmware as well with no issues as well, however the firmware I upgraded with did not contain a radio update, which I am hesitant to do since I imagine that will effect my flash. I did my flash myself but it seems like a headache re-doing it.
Click to expand...
Click to collapse
The wipes in TWRP usually recommended before flashing a custom rom don't remove their flashed data?
heartspains88 said:
The wipes in TWRP usually recommended before flashing a custom rom don't remove their flashed data?
Click to expand...
Click to collapse
Not that I have ever experienced. That was true on my EVO LTE and has so far been true on my One. I have the newest TWRP and in the past two days I have flashed EclipticOne, Elegencia and Insert Coin. On my old Droids Clockwork recoveries reset worked fine as well. DONT do a factory reset from inside the ROM. I have not tried it on my One, but on my EVO and my Droid 1/2/3 phones that would undo parts of a flash and I would have to reactivate. If I were you I would just work within my current firmware and flash what was available.
It is possible for you to flash your phone back to Cricket for free but its requires a lot of setup and can be a real pain in the ass. Getting 3G on Verizon was particularly painful and I have many screen shots and pages of notes on the actual procedure. When I upgraded from my EVO to the One I managed to get it right the first time by following my notes but it was still a serious hassle.
electroblood said:
Not that I have ever experienced. That was true on my EVO LTE and has so far been true on my One. I have the newest TWRP and in the past two days I have flashed EclipticOne, Elegencia and Insert Coin. On my old Droids Clockwork recoveries reset worked fine as well. DONT do a factory reset from inside the ROM. I have not tried it on my One, but on my EVO and my Droid 1/2/3 phones that would undo parts of a flash and I would have to reactivate. If I were you I would just work within my current firmware and flash what was available.
It is possible for you to flash your phone back to Cricket for free but its requires a lot of setup and can be a real pain in the ass. Getting 3G on Verizon was particularly painful and I have many screen shots and pages of notes on the actual procedure. When I upgraded from my EVO to the One I managed to get it right the first time by following my notes but it was still a serious hassle.
Click to expand...
Click to collapse
i was thinking about getting my one flashed to verizon but how does it work?? say i get my phone flashed.. is it verizon pre paid?? does that come with unlimited data?? text & talk?? how much would my bill be a month? sorry for all the questions
I apologize, so just to be as clear as possible, if you follow all of the wipes that roms usually ask you to perform in TWRP then you should be fine? However, do not perform a factory reset in the rom itself once loaded?
Doing a wipe through TWRP's wipe feature is fine as long as you dont go into 'Advanced' and mess with settings. Do not do the factory reset within the ROM once the ROM is loaded. If, while installing a ROM, the installer wants to do a wipe, that is fine as well.
I have a verizon HTC one. Rooted, Unlocked, and TWRP installed. Ive tried installing numerous roms, the only two that have fully worked are NuSenceSIX and tiKtak Google Edition Plus. If you have any roms you suggest for HTC one on verizon shoot them my way.
ones that dont work are Android revolution HD wont boot at all, until i flash the ElementalX Kernel, then it flashes but i dont get any data what so ever. During instalation on it international version which may be the issue. And ViperOne wont boot at all, just boot loops.
CM11, Slimkat, and Liquid smooth wont even flash. Ive redownloaded each rom several times and MD5 has matched
Before every flash i wipe data, then flash 2.10.605.1 firmware, then the rom, then i boot. ANy idea why they wont work?
First off. Stop flashing kernels/firmware left right and centre just because a rom/roms won't boot up.. that's a sure way to get into a mess..
What RUU was your phone originally shipped with. Have you changed your cid/mid. If so what was your original cid/mid.
What TWRP Version are you running..
Did you make a backup of your original system
What kernel are you on at this moment.
Post a fastboot getvar all and a screenshot of your bootloader.
Sent from my HTC One using XDA Premium 4 mobile app
Bad boyz current rom
Updated firmware
Super CID
Rooted (obviously)
S-off
adb reboot-works
adb reboot recovery-works
adb reboot bootloader-works
Fastboot reboot- works
fastboot oem rebootRUU- works
RUU-no worky, says usb device not attached even with current htc drivers
Google unable to connect to server after wipe cuz i turned blinkfeed back on and had to push OK a gizzilian times due top FC and did factory reset.
I can go to dropbox thru browser and install app backup/restore and than restore all apps, but it still fails to connect to google servers as i input info from new device (custom rom) and want to start fresh. I dont care if it wipes internal storage (learned long ago how to keep nothing on device that can't be restored off device)
Yes i wiped everything twice (except system and storage, been there done that nightmare)
So.... Bone stock (any version) rom that can be flashed in recovery......
Barebones back to stock is going to require an RUU. Did you make a nandroid of stock before you rooted the phone or is that how you got it?
If you're looking for rooted stock for most recent 5.03.651.3 rom, go here: http://forum.xda-developers.com/showthread.php?t=2766604
MFOsaka said:
Barebones back to stock is going to require an RUU. Did you make a nandroid of stock before you rooted the phone or is that how you got it?
If you're looking for rooted stock for most recent 5.03.651.3 rom, go here: http://forum.xda-developers.com/showthread.php?t=2766604
Click to expand...
Click to collapse
Nope, i'm looking for 100 persent stock RUU bone stock RUU flasable in recovery.
I'm going to go back to roots (and i don't mean ROOTED)
Let's say htc evo. You could take the RUU and extract it in rar, now adays it would be 7zip, take the rom and name it to pmg.3400(example) and put it on sd card, then flash it in bootloader. That no longer exists. I have the vary first bone stock htc one sprint rom, and have extracted rom.zip from it, and it wont flash from recovery. I need to.
Looking for old timers who know what to do with this. I don't want rooted version that will flash in recovery, i have that already and fighting to pull stock OTA update out of it to flash in recovery. There has to be someone here that has had the 1st edition sprint android (hero, or evo 1st edition) that knows what i'm talking about.
Yeah, that's the unfortunate side effect of these phones and no longer have an SD slot. And believe me, I remember the Supersonic days. OG EVO was my first HTC device. EVO LTE after the fact and now this phone. Tinkered with other HTC models for other folks as well.
There is an offchance that having SuperCID not matching for Sprint could be a culprit too. I was checking out a few threads about that after I read your reply. As far as some help from someone that is savvy with the M7... BD619 knows his stuff. PM him.
Hi,
I recently made the mistake of wiping my system partition trying to just do a factory reset. I was running a stock rooted 4.4.2 rom and TWRP recovery.
I've tried the latest RUU from HTC but it says it can't find my phone. Using the generic FUU and a 1.54.651.8 (the same version I was previously running) zip I found looks like it's starting to work - it finds the phone and everything but seems to be stuck forever on "Updating (0/7) Sending...."
I was able to get a custom rom installed, but some things weren't working quite right (couldn't send texts, kept making a weird sound, and a couple others) so I was hoping for a stock rom - rooted or not, I'm fine either way.
The bad news is that the old threads with the stock rom of that version seem to have broken links so I can't get them that way. I tried contacting a couple of people who posted them but they didn't hang on to them either.
Unfortunately, the SD reader on this phone has broken so I can't get to my old backup from before I originally rooted way back when. So what I had to do to install the custom rom was boot into TWRP Recovery, ADB push the .zip over to /tmp and flash it from there. Which seems to work fine as far as that goes, I just need a stock rom (or nandroid backup, I suppose) that is compatible with my firmware since the RUUs don't seem to want to cooperate.
As an alternative, is there a way of pulling just the rom out of that 1.54.651.8 RUU I have in some format that would be flashable under TWRP Recovery?
I know it's an older phone and I'm on an old firmware (once I was rooted I never wanted to do any updates for fear of breaking something), but any help would be greatly appreciated since all the links I can find seem to be outdated/dead.