Related
Can we keep the shipped rom and add the kernels for overclocking once achieving s-off?
I have been flashing phones for a long time.. way back to original windows mobile and switched to blackberry for the last couple of years.
I am back to HTC(happily) and have rooted the phone, but I would prefer to stay shipped rom for now until I can research some of these roms out there.
BUT I WANT TO OVERCLOCK!!!!
Yes that's what I've done. You'll need to have full radio S=OFF and you'll need to flash the engineering bootloader, but once you have that done you can flash kernels that say they are made to work with rooted stock roms.
A good example is the faux123 kernels, which are usually updated every day. Unless something's changed though, on stock, you can't flash the .zip file in recovery, you'll have to manually flash the zImage in Fastboot and then push the Broadcom module to the phone in ADB to fix your Wifi.
i tried this and it put me in an endless boot loop.... good thing for dumb people at car toys to replace the phone... not sure what happened but it was not good and I could not do a recovery
You can flash an oc kernel to the stock rom. Look on page 14 of the stock smartass kernel thread by faux. I was having the same boot loop problem, but followed vinsane's advice and it worked. Sound like you need to flash a recovery and make a nandroid backup first though. You'll be able to flash from recovery.
Sent from my HTC Glacier using XDA App
Yup. Easy to do. Just follow the steps outlined.
I'm usually flashing 1-2 kernels a day....depending on release and going back and fourth for comparison.
Sent from my HTC Glacier using XDA App
Hi,
My warranty has just run out on my Nexus One so I've decided to unlock the bootloader.
My Aim is to get from stock non rooted Gingerbread to rooted Gingerbread with busybox, SU, and ultimately being able to boot into ubunto in chroot, I've been reading up on all this for a few days now but just need a small amount of help with Recovery, Gingerbread ROM choice, and the order that thing should be done, by someone who's done this before.
I take it the first thing is to install SDK and get The USB Driver working on PC, its running XP by the way.
Then I unlock the bootloader, !HELP! to do this do I enter hboot or fastboot, before connecting the phone to the PC? I have to copy 3 files somewhere and use ADB and run command for **** OEM unlock, can't remember the exact command, (I've got instructions for this) and then agree to void my warranty etc.
I then find and download the correct custom recovery image and copy this into the tools folder of the SDK. And install (got instructions for this to).
!HELP!
Which custom recovery image should I use? and which Rooted Gingerbread ROM is most popular ?
After installing the custom Recovery can I just flash a custom ROM? I've seen something about SU.zip mentioned, is this necessary?
If I can just flash a custom ROM, I do this by downloading and copying the custom ROM of choice to the root of my SD card. Start phone in recovery mode and install from SD? I then install the google add ons .zip (if required) using the same method.
Sorry for such a long post and so many questions but I can find all the information for what I'd like to achieve but not in one place and nowhere in any chronological order.
Any advice appreciated .
Please read the Wiki, "Root" guides, "Unlock bootloader and install custom ROM" thread. Execute until the point of installing custom ROM.
Look in "Recovery" section for recoveries, install the latest Amon_RA.
Ive Successfully Rooted Gingerbread by following this method http://chensun.net/android-development/root-nexus-one-with-android-2-3-3-gingerbread/8/
GB ROM
Im running CM7RC4 and am happy w/ it
MouseIdt said:
Ive Successfully Rooted Gingerbread by following this method http://chensun.net/android-development/root-nexus-one-with-android-2-3-3-gingerbread/8/
Click to expand...
Click to collapse
Thanks everyone, but this looks like the one for me, going to unlock bootloader now install custom recovery and flash su.zip.
I'll post back with how I went on. Wish me look
A apprehensive newbie ;-)
Flash this as well, otherwise you will lose your custom recovery...
http://db.tt/cp7De8G
Sent from my Nexus One using XDA Premium App
Good show with unlocking the bootloader, it's the best way.
However... looking at your flag, you're in the UK... this means your phone is still in warranty, as we get 24 months.
Nooooo
Rusty! said:
Good show with unlocking the bootloader, it's the best way.
However... looking at your flag, you're in the UK... this means your phone is still in warranty, as we get 24 months.
Click to expand...
Click to collapse
My understanding was 12 months but, your probably right. I've unlocked the bootloader now and fortunately my N1 is in good condition, funtioning correctly ( well at least for now, I'll have to cross that bridge if and when I get to it )
Getting on to custom recovery, I realised something wasn't quite right after my first attempt. I installed custom recovery but without su.zip on my SD card. I managed after rebooting my PC to complete the custom recovery with su.zip on the SD card and was successful in that I've got SU on my N1. However I am quite sure I do need to fix something with the recovery, can someone explain what method or how I do this now. I've unlocked the bootloader, I am rooted with gingerbread but with a dodgy recovery.
Or do I do exactly the same as I did with su.zip and push recovery from ADB and flash from SD card, making sure that fix-recovery.zip is indeed on the SD card.
Hope this makes sence?
Any help appreciated.
After I unlocked my n1 I used rom manager for everything else, first flashing clockwork mod, then selecting a stable cm 7 build and flashing that, since then I've done everything through recovery, flashing custom kernels and nightlie builds, I'm currently using cm7 rc4 highly recommend rover theme too!
Sent from my Nexus One using XDA Premium App
sparkyryan said:
After I unlocked my n1 I used rom manager for everything else, first flashing clockwork mod, then selecting a stable cm 7 build and flashing that, since then I've done everything through recovery, flashing custom kernels and nightlie builds, I'm currently using cm7 rc4 highly recommend rover theme too!
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
I've got ROM Manager installed and if I want to try anything it tells me I have to flash clockwork mod recovery, I was unsure if It was safe to do this after using a completely different recovery image to get where I am now.
Sorry for being such a paranoid newbie, but we all got to start somewhere ;-)
sparkyryan said:
After I unlocked my n1 I used rom manager for everything else, first flashing clockwork mod, then selecting a stable cm 7 build and flashing that, since then I've done everything through recovery, flashing custom kernels and nightlie builds, I'm currently using cm7 rc4 highly recommend rover theme too!
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
I think CM7 rc4 is next, I do want to get Linux up and running though, even if it's in a virtual environment (chroot). and deffinately would like to check some nice themes out, I've not even looked at themes yet, I suppose it's quite easy after unlocking bootloader, installing custom recovery then flashing su.zip though. But still any pointers where to start my quest wouldn't go a miss ;-)
Recovery
its safe to let rom manager flash clockwork,ive done it
I heared about amonRA but it seemed like clockworkmod was more commonly used so I went for that, but yeah it's fine to flash a new recovery, just remember that whilst it's rare things can go wrong, it's YOUR fault not anyone's here regardless of the advice you may get here if your phone gets bricked or screwed up.
That said I'm still new to this but I'm learning as I'm going, just remember to backup your phone using rom manager before doing anything major so that you can always recover your phone/rom.
I started out hacking my nokia 5800 so was keen to have a go with the android platform.
Sent from my Nexus One using XDA Premium App
CM7 stable
Have you upgraded to cm 7 stable? its a definate upgrade
Alright, I have had my Bravo since January, rooted and flashed the BravoX RC2 rom along with a theme. During the summer, my wife was eligible for her upgrade, so we decided for me to upgrade to the Atrix on the condition that she was able to get the Bravo.
The phone has always had some freezing issues since updating to 2.2, but I think lately she has been getting very annoyed with this.
I would like to return the phone completely to stock, but due to the time since I last worked on it I'm a little unsure on how to go about it.
I wasn't expecting to get the upgrade when I did, and it was time sensitive so I didn't have time to remove my modifications to the Bravo before I gave it to her as I was planning, but a factory reset had removed all of BandroidX's apps, but left root access, the rom, and theme.
So, I know I will need to flash the 2.2 SBF to the phone in order to reset it completely to stock.
Because the phone currently is rom'ed and themed, do I need to first try to reset the phone using the BravoX bootstrap recovery?
Or does flashing the SBF completely overwrite everything that I've done with the phone erasing the rom, icon theming, and will it remove root access?
If you flash the sbf your phone will be completely stock... fresh froyo. Root access and everything else will be gone.
So, there won't be issues/conflicts with flashing the SBF all the way after having rom'ed and themed?
roadkizzle said:
So, there won't be issues/conflicts with flashing the SBF all the way after having rom'ed and themed?
Click to expand...
Click to collapse
No, flashing the sbf will erase your custom rom and theme for you.
Do you know how to properly flash the sbf with RSD Lite?
Yes, I've done that a couple of times. Really just done it from stock, or close to stock though, and a little new to working within OS's so was wanting clarification how the sbf sets itself.
I've been able to bring a few "bricks" back to life with there .sbf files. Love the things when flashing roms that have a bad bootloader or something else. Saved my skin several times. So ya flashing a .sbf is a total wipe and fresh install of whatever one you use. Just make sure you have a full battery at the start
Just wanted to say thanks for the community here. It takes time to search through it all...but all the help you need is there. Took about 3-4 days of research and tinkering but I got everything I wanted.....I think lol.
1. Dinc Rooted S-On
2. Found out that sucked within about a day.....went to Dinc Rooted S-Off
3. Flashed Gingertiny Kernel
4. Fixed all sorts of FC's and updated a very old Super Permissions app that was thrown on from original root process.
5. Updated Radio to nice new EVO Radio
6. Installed Supercharger v6, Adrenaline Super-Shot, and ext4 Mods
7. Grinning ear-2-ear at the performance difference and apps I can use that needed root!
Thanks again peoples. I feel like I literally got a new phone....even though I've had my Dinc for more then a year easily.
Stupifier said:
Just wanted to say thanks for the community here. It takes time to search through it all...but all the help you need is there. Took about 3-4 days of research and tinkering but I got everything I wanted.....I think lol.
1. Dinc Rooted S-On
2. Found out that sucked within about a day.....went to Dinc Rooted S-Off
3. Flashed Gingertiny Kernel
4. Fixed all sorts of FC's and updated a very old Super Permissions app that was thrown on from original root process.
5. Updated Radio to nice new EVO Radio
6. Installed Supercharger v6, Adrenaline Super-Shot, and ext4 Mods
7. Grinning ear-2-ear at the performance difference and apps I can use that needed root!
Thanks again peoples. I feel like I literally got a new phone....even though I've had my Dinc for more then a year easily.
Click to expand...
Click to collapse
I agree with u man , when I got my droid incredible I really loved it for about a month . Then I hot suspended from school for fighting then I stayed at home and had nothing to do so I looked on YouTube and found out how to root my droid incredible . Then I learned how to flash roms and kernels and I REALLY loved my incredible. I love this community it taught me a lot
Sent from my ADR6300 using xda premium
what rom are you running Stupifier
I have not put any special ROM on my phone yet. Since I've owned my Dinc (not rooted) for over a year, I have become very attached to Sense and how its all setup. Just seemed like a lot of work to research a ROM I would like and set everything up....and I'm a little droid-exhausted after all the above I did.
I also spent ALOT of time setting up some real specific shortcuts on my old homescreens. I did not wanna lose all that work. For example, I easily have over 20 Evenghost shortcuts....and those take alot of time to setup individually. I don't have Titanium Backup Pro either since I'm cheap.
If anyone would like to try to WOW me with a specific ROM they use, I'll listen though.
I've been unrooted on this phone until just a few minutes ago. (rooted other android phones and tablets tho). I still got s-on because I dont wanna wipe my device right now, but I know i will eventually. I've been lurking inc development thread for a while and it seems like this will be the rom that i pick when i do decide http://forum.xda-developers.com/showthread.php?t=1558923. I may wait for it to stabilize a little tho. anyways what other benefits does s-off give? just the ability for custom roms and kernels? i see you updated the kernel and radio, does that work nicely with stock firmware? (im assuming 4.08.605.2)
Shano56 said:
I've been unrooted on this phone until just a few minutes ago. (rooted other android phones and tablets tho). I still got s-on because I dont wanna wipe my device right now, but I know i will eventually. I've been lurking inc development thread for a while and it seems like this will be the rom that i pick when i do decide http://forum.xda-developers.com/showthread.php?t=1558923. I may wait for it to stabilize a little tho. anyways what other benefits does s-off give? just the ability for custom roms and kernels? i see you updated the kernel and radio, does that work nicely with stock firmware? (im assuming 4.08.605.2)
Click to expand...
Click to collapse
How did you end up rooting? If you're rooted and have clockworkmod recovery you should actually be able to flash custom roms and kernels and even radios even with S-ON and especially if HBOOT is unlocked.
You should wipe to install custom roms anyways.
i used http://forum.xda-developers.com/showthread.php?t=1306400 and stopped before
3)prepare to downgrade
and yes i know to wipe before installing new roms i'm holding off on custom roms because i wont want to wipe right now
Shano, I used the exact same root guide you used. I would HIGHLY recommend continuing to step 3 and getting S-Off. I too stopped just before Step 3 and all it gave me was problems. From Force Closes, to unable to install certain important things like BusyBox and an Updated SuperUser app, and more. After about a day of that mess, I continued with that guide and got S-off. Looking back at it, I really wish the Author of that guide did not mention the possibility of stopping after Step 2. All it gave me was grief lol.
Also, once you finish the whole process in that guide....you can recover EVERYTHING you had previously (Apps, Settings, Data, Screen Layout, etc). Towards the end of Step 2, you are told to make a Backup. That backup is what you will recover once you are done. Then you got S-off Rooted without losing a dime.
well i already made a mistake and lost everything. im now on CM9 with s-on..however seem to still have some problems. i'll probably do that in the morning.
I just got a dinc a few weeks ago. I had a dx and the headphone jack crapped out on me. I snagged one one swappa for $70.
I was very active over at rootz (1300 posts), that's were the dx action seemed to be happening. Now, the dinc action is here.
Loving being able to flash kernels and having way more freedom than on the dx. I doubt i will ever go back to a moto phone, the locked bootloader really makes things difficult. The dinc will last me until my upgrade in Aug or longer.
Thanks to all who make flashing stuff on the dinc so easy.
One silly question. When we flashed a rom on the dx and it didn't boot for whatever reason, we would have to sbf the phone back to stock, there was no way to boot into recovery from power off. Is that a problem on the dinc? Or will holding vol down and power always boot you into recovery?
bobAbooE said:
One silly question. When we flashed a rom on the dx and it didn't boot for whatever reason, we would have to sbf the phone back to stock, there was no way to boot into recovery from power off. Is that a problem on the dinc? Or will holding vol down and power always boot you into recovery?
Click to expand...
Click to collapse
Correct. If the rom doesn't boot after flashing: pulling the battery and holding vol. down and power will take you to recovery. That's the typically suggested route if you waited say ten to fifteen minutes to no avail.
SlimSnoopOS said:
Correct. If the rom doesn't boot after flashing: pulling the battery and holding vol. down and power will take you to recovery. That's the typically suggested route if you waited say ten to fifteen minutes to no avail.
Click to expand...
Click to collapse
Thanks! That already bumps the dinc over the dx. Those locked bootloaders are a pain in the ass.
bobAbooE said:
Thanks! That already bumps the dinc over the dx. Those locked bootloaders are a pain in the ass.
Click to expand...
Click to collapse
I hear you, I've been spoiled with this phone since flashing anything is effortless. With the DX, were you able to install a new radio or update the kernel say when you went from froyo to gb? Was there only one kernel for froyo and one for GB or multiple per update?
bobAbooE said:
Thanks! That already bumps the dinc over the dx. Those locked bootloaders are a pain in the ass.
Click to expand...
Click to collapse
SlimSnoopOS said:
I hear you, I've been spoiled with this phone since flashing anything is effortless. With the DX, were you able to install a new radio or update the kernel say when you went from froyo to gb? Was there only one kernel for froyo and one for GB or multiple per update?
Click to expand...
Click to collapse
We just got what moto gave us. The radio would update once we received an update. There have been three updates for gb, 601, 605 and 621. 621 was pushed out and broke root. It was finally able to be rooted but your were stuck on 621 with no way to flash back to an older build. The sbf was our safety net. If you messed the phone up, who cares, just sbf and start over. Moto changed something in the bootloader that didn't allow that with the lastest update. Its since been fixed but it took about a month. The ones who tried before the fix were left with a permanent brick.
We do have something called "2nd init". It's a way to hijack the kernel and would allow us to flash cm7, miui, omfgb, cm9, aokp, gummy, etc. But it was still using the stock kernel.
Having this openness if fun. The guys who dev on the dx have done some amazing things with what they were stuck with.
bobAbooE said:
I just got a dinc a few weeks ago. I had a dx and the headphone jack crapped out on me. I snagged one one swappa for $70.
I was very active over at rootz (1300 posts), that's were the dx action seemed to be happening. Now, the dinc action is here.
Loving being able to flash kernels and having way more freedom than on the dx. I doubt i will ever go back to a moto phone, the locked bootloader really makes things difficult. The dinc will last me until my upgrade in Aug or longer.
Thanks to all who make flashing stuff on the dinc so easy.
One silly question. When we flashed a rom on the dx and it didn't boot for whatever reason, we would have to sbf the phone back to stock, there was no way to boot into recovery from power off. Is that a problem on the dinc? Or will holding vol down and power always boot you into recovery?
Click to expand...
Click to collapse
You should always be able to access hboot by pressing vol down and power, and then select recovery from there. This way you can just reflash a rom or restore a backup, instead of restoring the entire phone. We have something like sbf's but we call them ruu's, and they are flashed thru hboot and will return the phone to stock.
Sent from my ADR6300 using xda premium
just a technicality.... but vol - and power boots to Hboot. from Hboot you can boot to recovery.
if things go wrong (like rom does not boot or stuck in a bootloop) usually you can just re-flash a recovery, like clockwork, in Hboot. once your recovery works again, just flash another rom or do a restore.
Hboot should always be available... so there is no need to return to full stock again. if you can't get to Hboot, then you have real trouble. that would be very unusual.
edit-- wow am i slow typing with my phone
So i saw eariler in this thread, if the dinc is rooted, with su, and recovery i can flash roms? How so? I thought the bootloader had 2 b unlocked?
Sent from my s-off rooted htc rezound using Xparent ics blue tapatalk 2
My buddys dinc has root permissions, and clockworkmod recovery. So u r saying that he can flash roms with a locked bootloader, and s-on.
Sent from my s-off rooted htc rezound using Xparent ics blue tapatalk 2
zounduser said:
My buddys dinc has root permissions, and clockworkmod recovery. So u r saying that he can flash roms with a locked bootloader, and s-on.
Sent from my s-off rooted htc rezound using Xparent ics blue tapatalk 2
Click to expand...
Click to collapse
yes he can. however it seems to cause many problems. you must downgrade to froyo first to get s-off. back up all apps and data first
Shano56 said:
yes he can. however it seems to cause many problems. you must downgrade to froyo first to get s-off. back up all apps and data first
Click to expand...
Click to collapse
Its not really that it causes issues, its that it makes small issues much harder to diagnose and fix. Root and s-off are 2 different things, with root you can flash roms and most mods, with s-off you can flash directly from hboot, new hboots, radios, recoveries, unsigned ruus, and splash screens. If issues arise being able to flash from hboot is a big plus. I would also recommend downgrading and getting s-off.
Hi everyone!
I am having very strange problem with stock rom "JORDN _U3_6.36.0" from T-Mobile USA on standard Defy. Each time i power phone up, it starts booting up then restarts itself in to stock recovery and perform hard/factory reset. After that it boots normally, but all settings gone.
I am not using T-mobile sim or moto blur account , so i skip registration using "ebluroff" trick. Is that can be the cause of the problem?
Some backstory: when i bought the phone it had CyanogenMod 7 installed on it. I used it for 2-3 years,even updated it several times up to 7.2.
Then some time ago i started having issues with it, so i had to flash stock rom with 2.1 Android.
I decided not to do anything with the phone, until i got some advice, so i any help would be greatly appreciated.
What were the issues faced? Anyhow one of the things you can try is to upgrade to 2.2, via rsd lite
Sent from my Nexus 5 using Tapatalk
thekguy said:
What were the issues faced? Anyhow one of the things you can try is to upgrade to 2.2, via rsd lite
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Well, thing is i want to keep my downgrade ability. I rooted the phone with superoneclick and install 2ndInit 1.4.2, but the problem is that it doesn't see SD card because it is Eclair. How people installed nandroid backups on 2.1? There has to be the way to move to 2.2 without flashing full SBF, because as i already mentioned it had CyanogenMod 7 when i bought it, so it is possible.
DEN383 said:
Well, thing is i want to keep my downgrade ability. I rooted the phone with superoneclick and install 2ndInit 1.4.2, but the problem is that it doesn't see SD card because it is Eclair. How people installed nandroid backups on 2.1? There has to be the way to move to 2.2 without flashing full SBF, because as i already mentioned it had CyanogenMod 7 when i bought it, so it is possible.
Click to expand...
Click to collapse
Some update. After hours of digging i found out these thread http://forum.xda-developers.com/showthread.php?t=899450
So, i first flashed defy 2.2_boot_only FIXED FSB, then after reboot custom recovery started working, so restored Droid22 rom from it.
Phew, i knew it was possible. So now i have rooted chines (?) android 2.2.1 on my phone and working custom recovery. I am gona stick on it for a while until i find best 2.3.3. nandroid ROM.
Just wanted to clarify was it right order - first flashing fixed SBF then restoring nandroid backup? I couldnt get custom recovery working without updating bootmenu first.
I also wanted to add that i did custom recovery data|cash wipe before flashing fixed SBF, before AND after restoring nandroid backup.
I saw that lots of people had problem like me , hope my message will help.
Here is link to another forum which has working download links http://www.addictivetips.com/mobile...ed-rooted-android-2-2-froyo-on-motorola-defy/