Related
i know i think i might be at the wrong forum but i thought i might get help over here....i have unlock the boot loader fine, then i installed the super boot and flash the recovery image amran 1.6.2 fine, i backup my nan and now i like to flash it with cyanogen rom 5.0.4.1 do i need to update the radio or put the add on for this before i do continue...please help!!!! thanks
i have radio:4.03.00.21.2
do i?? or just flash it directly and how about addon???
xghostyxjokerx said:
i know i think i might be at the wrong forum but i thought i might get help over here....i have unlock the boot loader fine, then i installed the super boot and flash the recovery image amran 1.6.2 fine, i backup my nan and now i like to flash it with cyanogen rom 5.0.4.1 do i need to update the radio or put the add on for this before i do continue...please help!!!! thanks
i have radio:4.03.00.21.2
do i?? or just flash it directly and how about addon???
Click to expand...
Click to collapse
you do not need a new radio. I am still using stock radio! and maybe try this rom http://forum.xda-developers.com/showthread.php?t=639637 its a supermodified, sexy, feature-rich cyanogen rom
theres alot of deferent ones which is suggested for the most out of it???
if i decide to flash the desire rom do i need to update the radio then??? isnt it always is good to keep up with the radio??? if so how do i do the update i have it ere38 i beleive???
xghostyxjokerx said:
if i decide to flash the desire rom do i need to update the radio then??? isnt it always is good to keep up with the radio??? if so how do i do the update i have it ere38 i beleive???
Click to expand...
Click to collapse
Hi xghost. You dont have to update radio to flash desire roms.
You can update it if you want to but remember, flashing the radio is the "only" way to brick your phone. Not a high chance but higher then most other things you can do.
-Roger
okay thanks...so since it is my first time using the root for nexus one...im going to flash it with 5.0.4.1 do i flash it then flash the ere38 add on that is on the page or???
Ok so im trying to install froyo 2.2 and this is the page im doing it from http://forum.xda-developers.com/showthread.php?t=686627
So i have a nexus one with the Htc Desire Software on it and i didnt know which one should i download so i picked the tweaked version and this is what i did i wipe it then flashed the zip and it just froze on the unlock symbol in the beginning so i had to reflash the Desire rom i had before which works so can someone please help me out thanks in advanced i think i did something wrong.
The files Cyan posted are NOT Froyo. What he posted are the files to get ROOT on an existing install of Froyo. Look for the FRF50 thread posted by paulobrien, flash that first,then flash the files by Cyan.
FaJu said:
The files Cyan posted are NOT Froyo. What he posted are the files to get ROOT on an existing install of Froyo. Look for the FRF50 thread posted by paulobrien, flash that first,then flash the files by Cyan.
Click to expand...
Click to collapse
Paul has an already rooted version of the rom without the radio update i believe. he shouldn't need to flash cyan's mod. unless he wants the kernel tweaks.
I was having random reboots with it so i went to paul, no reboots so far. =)
(i think it had something to do with setcpu, my cpu settings were 1113 and i dont think the cpu was supposed to go to that frequency so that may be why it was acting up.)
so what am i soppose to do?
Go to this page:
http://android.modaco.com/content/g...ed-update-zip-no-radio-option-online-kitchen/
It's pretty self explanatory but you can flash either FroYo with or without the radio update.
Here's a basic tutorial I wrote up with all files needed to update to froyo... Enjoy! Working 100% if you follow instructions as listed (haven't heard of an issue from others yet that tried it this way)
thanks man that worked i have one little problem how can u check if u have flash bcuz i try and see a video and sometimes it says u need an update so...
Cramazin said:
thanks man that worked i have one little problem how can u check if u have flash bcuz i try and see a video and sometimes it says u need an update so...
Click to expand...
Click to collapse
look up adobe in the market and download flash beta... it shows up for anyone using 2.2 (froyo)
HI people. First of XDA Forum and Dev as you guy's are doing a great job.
Secondly i have this Motorola Milestone GSM version. I am stuck on Android 2.1, as every one how fast Motorola release Android updates for their smartphones. I have gone through lot of Rooting guides but i haven't tried one yet.
As there are lot of Rooting guides and ROM for Motorola milestone on XDA as well, i am kind confuse how to do rooting and how to use a ultimate ROM on Milestone.
If you guy's can look at my Moto version as given below and can suggest me some step by step guide and Some Good ROMS as well i will be very thankful to you guys'
I know there are lot of other users who have asked same question but i want it kind simple and crisp.
Model Number
Milestone
Firmware Version
2.1-update1
Firmware Configuration Versio n
GAS_EMEA_USASHLS00RTINT_P016
Baseband Version
3GSMEPU91A_U_91.07.56I
Kernel Version
2.6.29-omap1
Build Number
SHOLS_U2_02.36.0
Click to expand...
Click to collapse
Most one-click-rooters work fine with the Milestone and it doesn't get any easier then running an app .
That's how I did my at least.
I have used universal root, but that doesn't allow APP2SD and using custom ROMS. So i want complete rooting so that i can load custom roms.
gaggid said:
I have used universal root, but that doesn't allow APP2SD and using custom ROMS. So i want complete rooting so that i can load custom roms.
Click to expand...
Click to collapse
Yes it does...
The problem is that:
-for APP2SD you must have ext2 partition which you probably didnt create and for Custom ROMS you have to load the vulnerable recovery...which you probably didnt do...as well
Just my supposing...Corect me if I'm wrong!
First, ( I think) you have to flash vulnerable recovery, then root. There is also a beta 2.2.1 beta sbf available. after achieving root, you can google GOT TEAM ANDROID and click the first link which should lead to their blog - http://www.google.ca/url?sa=t&sourc...BQ82GR7pNmLJSfPpg&sig2=Jd4iM6Nov5eYhJa2yrZLGg and there should be further instructions there. Good luck ( remember I think these are true, not 100% sure)
mohitrocks said:
First, ( I think) you have to flash vulnerable recovery, then root. There is also a beta 2.2.1 beta sbf available. after achieving root, you can google GOT TEAM ANDROID and click the first link which should lead to their blog - and there should be further instructions there. Good luck ( remember I think these are true, not 100% sure)
Click to expand...
Click to collapse
Can you guide me through on how to do
Flash Vulnerable Reovery.
How to root Milestone
What is SBF and how to use it.
What GOT TEAM ANDROID and why i need them?
If your milestone is anything like mine (I use the milestone available from telus, in canada), then your service provider may have added an un-root and return-to-factory-bootloader check on every boot.
in which case, you would need to install the OpenRecovery backup tool onto your sd card (it's an update.zip file + OpenRecovery directory), then flash a vulnerable bootloader using spf. reboot the phone (as is necessary when doing this flash), and as the system is coming up, start up into recovery (by pressing+holding the camera button, waiting for the yellow triangle w/"!", then pressing vol+ and the camera button), then execute update.zip
drop to terminal, and depending on your model, the .sh file that's un-rooting your phone may be in a different location, and simply rename the file, delete it, or make it non-executable.
Good luck!
Mystik said:
If your milestone is anything like mine (I use the milestone available from telus, in canada), then your service provider may have added an un-root and return-to-factory-bootloader check on every boot.
drop to terminal, and depending on your model, the .sh file that's un-rooting your phone may be in a different location, and simply rename the file, delete it, or make it non-executable.
!
Click to expand...
Click to collapse
I just bought the telus milestone a few days ago and am looking to bypass the update.zip when I go into recovery by permanently replacing the stock recovery with a custom recovery, would disabling this .sh file aid me in this respect?
Where could I find it?
I think i found complete guide for doing this.
Hope it will work.
Which ROM is best for Milestone ?
I am not talking about jazzy ROMs, i want a ROM with all cool features + stable functionality
i always have a hard time rooting Milestones :/
Still not able to get any strong good references on Hacking Milestone.
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.
Probably a stupid question, but please remember I came from an HTC.... so be nice....
On a nexus 6 when I flash a rom, beit custom or stock does it flash the firmware as well?
Also, coming from an HTC I had to take the OTA to update the firmware and then flash my favorite rom based on said firmware to fully be updated.
Does this apply to nexus devices, specifically nexus 6?
k.s.deviate said:
Probably a stupid question, but please remember I came from an HTC.... so be nice....
On a nexus 6 when I flash a rom, beit custom or stock does it flash the firmware as well?
Also, coming from an HTC I had to take the OTA to update the firmware and then flash my favorite rom based on said firmware to fully be updated.
Does this apply to nexus devices, specifically nexus 6?
Click to expand...
Click to collapse
no. just flash the rom, it has everything you need, but the gapps(google apps), which is a second flash.
simms22 said:
no. just flash the rom, it has everything you need, but the gapps(google apps), which is a second flash.
Click to expand...
Click to collapse
I rarely use anyting not based on stock... if I flash a stock LRX22C will i get the firmware as well?
Same goes for when the 5.0.* update rolls out and someone makes a flashable stock rom based on that build. Firmware included?
There's no such thing as "firmware" on the nexus in regards to updates. In fact, theres no such thing on any of these phones, just some silly carriers decide to change things on HTC devices to be called "firmware" - incorrectly I might add... Sooooo short answer, forget about "firmware" as its not a thing.
rootSU said:
There's no such thing as "firmware" on the nexus in regards to updates. In fact, theres no such thing on any of these phones, just some silly carriers decide to change things on HTC devices to be called "firmware" - incorrectly I might add... Sooooo short answer, forget about "firmware" as its not a thing.
Click to expand...
Click to collapse
Thats what i wanted to hear, thank you.
k.s.deviate said:
Thats what i wanted to hear, thank you.
Click to expand...
Click to collapse
No probs.. But actually I'll elaborate a little more...
Full ROM flash from fastboot is also referred to as "flashing factory images) is the equivalent of flashing a HTC RUU. It will include a system.img (ROM), radio.img, boot.img (kernel), recovery.img and bootloader.img.
OTA update will include usually full radio.img, patches to multiple apks (and more) in system (ROM), patch to update recovery, boot loader and often a full boot.img or kernel patch.
Custom rom or converted stock ROM zip will usually be a system image and a boot image.
Hope this helps a little.
rootSU said:
No probs.. But actually I'll elaborate a little more...
Full ROM flash from fastboot is also referred to as "flashing factory images) is the equivalent of flashing a HTC RUU. It will include a system.img (ROM), radio.img, boot.img (kernel), recovery.img and bootloader.img.
OTA update will include usually full radio.img, patches to multiple apks (and more) in system (ROM), patch to update recovery, boot loader and often a full boot.img or kernel patch.
Custom rom or converted stock ROM zip will usually be a system image and a boot image.
Hope this helps a little.
Click to expand...
Click to collapse
So when an updated android version is released, in order to get the best possible performance (on whichever ROM i choose to use) I should just flash the factory image in order to get the latest radio, bootloader and kernel?
k.s.deviate said:
So when an updated android version is released, in order to get the best possible performance (on whichever ROM i choose to use) I should just flash the factory image in order to get the latest radio, bootloader and kernel?
Click to expand...
Click to collapse
If you're staying stock unrooted, ota is the easiest. You'll get latest everything. If you're rooted or have any modifications, standard ota will fail, in which case, factory image is best IMHO.
rootSU said:
If you're staying stock unrooted, ota is the easiest. You'll get latest everything. If you're rooted or have any modifications, standard ota will fail, in which case, factory image is best IMHO.
Click to expand...
Click to collapse
Thanks! I'm bouncing between CleanROM and Chroma..(Can't decide which i like better) so OTA is useless for me.
I do appreciate the help, I've been trying to figure it out myself ever since i got my Nexus but I couldnt find any solid info.
k.s.deviate said:
Thanks! I'm bouncing between CleanROM and Chroma..(Can't decide which i like better) so OTA is useless for me.
I do appreciate the help, I've been trying to figure it out myself ever since i got my Nexus but I couldnt find any solid info.
Click to expand...
Click to collapse
No worries. Well which ever you stick with, just flash a ROM.zip as and when updates are released by your dev. Forget about updating radio and bootloader unless you feel you need to.
rootSU said:
No worries. Well which ever you stick with, just flash a ROM.zip as and when updates are released by your dev. Forget about updating radio and bootloader unless you feel you need to.
Click to expand...
Click to collapse
Sounds good, thanks again!