Related
I have an unrooted hero I have had since launch day. I am now thinking about rooting my hero with use of the latest Sprint leak. my understanding is if you update to the leak of even the official builld whenever that may come out, it will close all current rooting holes available. I guess that doesn't mean in the future there won't be other possibilities. do these new build give the same sense of stability as the official roms because we can now use an official 2.1 kernal?
so from what I have been reading there appears to be only one Rom that is based on the current 2.1 leak and that is flipz Rom? I have a few questions or statements before I do anything to my phone. one, will this help get rid of the lag when typing? two, I need to make sure Bluetooth is still going to work as I have a home phone that I connect my cell to when I enter the door. if I decided to flash back to the official release, is that possible?
dbldown768 said:
I have an unrooted hero I have had since launch day. I am now thinking about rooting my hero with use of the latest Sprint leak. my understanding is if you update to the leak of even the official builld whenever that may come out, it will close all current rooting holes available. I guess that doesn't mean in the future there won't be other possibilities. do these new build give the same sense of stability as the official roms because we can now use an official 2.1 kernal?
Click to expand...
Click to collapse
As of right now; many people are cautious about testing the latest 2.1 leak; because of the concerns you expressed earlier -- having your phone unrooted by the 2.1 leak when you flash the new update. So, with that said; the current 2.1 ROM's are all pretty stable. This new leak, however probably is as well, but again... I don't know whose all tested it, for fear of loosing root access.
dbldown768 said:
so from what I have been reading there appears to be only one Rom that is based on the current 2.1 leak and that is flipz Rom?
Click to expand...
Click to collapse
No. Damageless ROM's are also based on the latest Sprint leaks. All ROM's you see should tell which ROM they are based off of. Almost all 2.1 ROM's are currently built from any of the Damageless ROM's -- just read the front page of the ROM you're looking into.
dbldown768 said:
I have a few questions or statements before I do anything to my phone. one, will this help get rid of the lag when typing? two, I need to make sure Bluetooth is still going to work as I have a home phone that I connect my cell to when I enter the door. if I decided to flash back to the official release, is that possible?
Click to expand...
Click to collapse
1. Possibly. The lag problem is relative to the person/device. Not everyone experiences this problem. However, turning off "Vibrate when typing" apparently helps with the lag issues. YMMV.
2. Please see first post I made.
Thanks for the quick reply. I'm investigating the best way of rooting my phone. I see there are a few ways listed on the wiki, but then i just ran across Fresh Kitchen (http://geekfor.me/new-release/fresh-kitchen-105)? This is suppose to root your phone for you? Is this a stable way of rooting or should i just use the command line mehods? Also, i have read that you should do a nandroid backup of your phone? Not sure if fresh is doing this for you? The other thing i should mention is that i just have a stock microSD card, so I dont plan on using app2sd, i dont think this is a problem correct?
I also see people load their roms using their microSD card and just putting some update.zip file on there. Is this the standard procedure once you root your phone and get a rom loaded?
Actually, Fresh 2.1, and 2.1.1 are the only ones as of right based off of the newest leak (signed with release keys rather then test), Damageless and Treve are currently working on improving DCUpdater, DConfig, and building a new ROM from the release-keys build.
As far as how to root, I recommend the command line method. While the auto-root methods are nice, actually doing it yourself will give you some experience with things you're gonna be using.
Yes, loading the update.zip to the root of the SDCard is the standard way to flash.
No, not using Apps2SD is not a problem, most people use it because they have a faster SDCard, which gives better performance when loading apps.
A Nandroid backup is something that you will do before you flash any update.zip (At least you're supposed to). It's basically an "Image" of your phone exactly how it was the point in time that you made it, so if you flash something and everything goes horribly wrong, you can restore said nandroid, and it will be like it never happened. (The exceptions are flashing a radio and screwing with the PRL/PRI, nandroid doesn't touch those.)
dbldown768 said:
Thanks for the quick reply. I'm investigating the best way of rooting my phone. I see there are a few ways listed on the wiki, but then i just ran across Fresh Kitchen (http://geekfor.me/new-release/fresh-kitchen-105)? This is suppose to root your phone for you? Is this a stable way of rooting or should i just use the command line mehods? Also, i have read that you should do a nandroid backup of your phone? Not sure if fresh is doing this for you? The other thing i should mention is that i just have a stock microSD card, so I dont plan on using app2sd, i dont think this is a problem correct?
Click to expand...
Click to collapse
Fresh's kitchen will allow you root your phone and yes it's stable. However, it's best you try doing it via ADB commands, as there will come a time when you'll want to create things for the community and wished you had prior experience using it. I recommend you trying to root via this tutorial HERE If you follow the directions, you shouldn't have any problems whatsoever.
Stock card is perfectly fine; you're able to use Apps2sd, but don't have to.
dbldown768 said:
I also see people load their roms using their microSD card and just putting some update.zip file on there. Is this the standard procedure once you root your phone and get a rom loaded?
Click to expand...
Click to collapse
To try out different ROM's -- the process is to download the file (which is a update.zip file in itself), but has been renamed to match the name of the ROM. All you have to do is; copy to your sd card, boot into recovery, flash ROM from the sd card, reboot.
abcdfv said:
Actually, Fresh 2.1, and 2.1.1 are the only ones as of right based off of the newest leak (signed with release keys rather then test), Damageless and Treve are currently working on improving DCUpdater, DConfig, and building a new ROM from the release-keys build.
Click to expand...
Click to collapse
There's your real answer. Thanks.
I'm having a hard time understanding why i would need the flash recover image in this tutorial (http://forum.xda-developers.com/showthread.php?t=583291)? I understand i would want to do a backup of the current phones state, but why would i flash anything before actually making this backup? Maybe i'm not understanding the process correctly, but i just want to get "su" ability and then do the nandroid backup? Is the nandroid backup an app i use?
Nandroid is built into the recovery image you're flashing. Before flashing the recovery image, there is no way for you to nandroid.
thanks! after watching the youtube video posting that mad more sense. So i know there is a chance of bricking your phone during all of this, where does that chance increase? Is it during the flashing of the customs roms, not so much the rooting process?
It is safe to say once the "official" 2.1 android comes out there will always be a custom rom based on it? meaning that if chosen by developers here there could be a build off the "official" 2.1 with the only difference is the rooted user is still allowed? I know that most dev are going to change the build in someway to "improve" on what the official build is done.
The only proven way to brick this phone is by flashing a GSM radio, or by having a failed RUU. I've never heard of anyone getting a "true" brick from rooting/flashing ROMs.
Yes, once the official build is released, all ROMs from then on are most likely going to be based of off it.
Ok, stupid question. I just followed the guide to rooting my phone, doing the nandroid backup and copying the backup to my pc. There are a lot of guide to root, but how to you actually flash the custom rom? I saw something about holding down the 'home' button when starting up? Does this bring you to the recovery image again? Do the roms have to be named something specifically?
Place the ROM in the root of your sdcard, and boot into recovery by holding Home+Power. From then select the "Flash update.zip" option and it will show all of the .zip files in the root of your sdcard. Just pick which one you want to flash.
great! thanks for all the help.
ok, so i decided to load damage's sprint leak that would still give me root access, well it doesnt boot. just goes to the "sprint now" screen and reboots over and over again? any ideas?
Did you wipe data and Dalvik?
Anytime you go from one ROM version to another (1.5 to 2.1, 2.1 to 1.6, 1.6 to 1.5, etc etc) you have to wipe, or if there's major changes between rom versions.
what do you wipe the data? i just picked the flash from zip file from sd card?
In recovery there's a catagory for wipe. Wipe data and Dalvik, then reflash and you'll be fine.
cool. thanks. trying that now.
so everything is working now. So i know one of the main benefits of having a rooted is phone is wifi teathering. Are apps like this in the market place or only on here?
There's Easytether and PDAnet. I haven't tried Easytether, since last I've heard it's x86 only, but PDAnet was a horrible experience. I just flashed an Eris based ROM, broke my PRI, and it enabled the built in USB tethering.
dbldown768 said:
so everything is working now. So i know one of the main benefits of having a rooted is phone is wifi teathering. Are apps like this in the market place or only on here?
Click to expand...
Click to collapse
go to market and download barcode scanner
open up barcode scanner and go here and then just point the camera at the qr code and it'll download to your phone.
remember to check 'unknown sources' > setting > applications
wifitether 1.6. works flawlessly on either fresh or damageless latest 2.1
my epic 4g was rooted and running perfect. the other day it lost root. set cpu, titanium. non of it works. i did a factory reset and flashed epic experience again and a few other roms. also cleared cach and dalvik. nothing has brought back my SU permissions. any o e encou tered this and know how to fix it?
Root it again? If you're using superuser, you have to keep the phone turned on and unlocked the first time you su in adb.
Same as me ROOT PROBLEM ON EVO 4g
Will someone please help me? I originally rooted on unrevoked 3, and I was finally granted superuser permission, now I tried reading up on flashing a rom and now lost my superuser guy, and ended up with a blue# sign saying superuser, but no access? I had bought this after a few had broke in the past with the port, being junk, and Firmware version is now 2.1-update 1 I just got this phone a month ago, anyway the Baseband version is 2.15.00.09.01 the kernal is 2.6.29-a2443432 [email protected] #1, and if that isnt bad engough build is RvU 1.3.2? software number 1.32.651.6 Browser version is still 3.1 PRI Version 177_003 PRL 60671 Help you can tweet me at smw5247 please been up all 2nights, first time I am asking?
i also tried rooting again but now my computer says it doesnt have the correct driver to reco ize the phone. i updated them to the newest drivers and still doesnt reconize it. any one got some ideas on getting windows 7 to see my pbone?
Did u try the USB ports on you're Motherbord? Try all the ports on the back of ur pc. The front ports on a lot of computers have problems with Devices like phones and GPSs on the under powered front ports. My one PC does not like my Epic or my Garmin GPS on the front
Why not just flash an already rooted kernel? Also make sure you didn't end up with superuser.apk in /data/app and /system/app, that can cause weird issues too
Sent from my SPH-D700 using Tapatalk
Hey, thanks for the ideas. I finally figured out part of my problem with the phone not being rooted, I did unrevoked again and flashes it, but I lost my Froyo 2.2, and have that kernal I mentioned earlier! My benchmarks R in the basement & I am not sure which rom or kernal to use? I lost my flashlight and when they took off the cap for FPS! Can someone recommend one I can just scan? I lost a lot of paid apps too!
flashing a new rooted kernel did the trick. over clocking to 1600MHZ. GOOD STUFF, THANKS FOR THE ADVICE
Excuse the long thread title lol..
I've been gently lowering myself into all this tampering with my phone as I've always been a bit of a tinkerer with everything i've ever owned.
So back in march my phone, an unbranded handset on o2 uk was on 2.2.1. My first foray into modifying my handset was to flash the jvk gb firmware. I then rooted it using cf root. All very simple. I then flashed it using cwm with Simply honey 3.2 and then the latest 3.5. No issue.
So this afternoon, I flashed it with the "unspoken ones" kernel just cos I could lol. Something didnt seem right though. There was a bit of lag and I got one or two forced closures so I decided to restore one of the cwm backups I had. Thing is, it hung upon reboot at the i9000 screen, for about 10 minutes so I pulled the battery. Now I couldnt get it restarted. Panic set in. This was my first proper issue and I just wished I was back in march on 2.2.1 again.
As said, couldnt get it started so went hunting some advice. Install a base stock rom with 3 files and a 512 pit. I struggled. Could I find 3 files ? Nope. Not on samfirmware. Every file I downloaded was one file. JP1 JPU JPY. All 1 file. So. As JPY was the firmware I was on originally, I chose the 1 file version, put the phone in download mode and flashed it via odin. It worked !!! And then I plugged it into kies and up popped the box, I have an firmware update ! JPO GB! So i installed that. I'm quite surprised that I got the update because you always see lots of threads regarding people being unable to update by kies once they have modified their phones. Why did mine work? Because the handset in unbranded perhaps ?
Anyway, I wanted to get back to the Simply Honey rom because it ran really well and the battery life is fantastic but Simone hasnt done a version based on JVO yet as far as I could tell so I thought, I know, I'll root with cf root, again and try that backup again using cwm. And it worked, and here I am back where I was earlier today ! Ace ! lol
Sorry about the essay but I'm sure that there are some questions in there worth answering.. ?...and also to serve as a bit of help to those that find themselves in a dodgy situation. Just calm down, search for the advice, it is out there and do as it says and everything will be cool
Posted from my restored and working handset...
the files you download from samfirmware are rar files (have a .rar extention). This means you need to decompress them into a folder and the "three files" will be in there. You need a rar extractor app. You can use 7-zip which is free.
You need odin (or ezodin or heimdal) to flash the stock rom but I am sure you know that already. There are a few guides around for all tools.
There is a lot of information here, especially in the "sticky" posts. If you feel like learning what you are doing rather than copy instructions (as I think you do), it may be a good idea to go through them.
Anyway you got your phone working in the end so that's good!
simple solution when an install hangs is only to reflash the kernel in odin: that restarts the phone.
cwm is not invincible and the restored rom is there but the phone hangs on the boot because of the kernel hiccup. Reflashing the kernel to the one you now want will allow the phone to boot and access the rom that matches -- you do have to ensure the recovery version rom and the kernel you are flashing are in sync.
Persist. You only really panic the first time this happens -- after that you know it is a possibility and how to fix it.
Worst case scenario: pull the battery, reinsert, go to download mode and reflash the kernel and base rom of your choice. At least now you have a clean phone!
Two things are important to remember: (1) always do a backup before installing a new rom or kernel and (2) use titanium backup for all applications -- easy to restore everything.
Also I find it easier to use google calender and my internet email as bases for dates, appointments and contacts -- that way if I loose everything on the phone I can quickly reload my data by sync with online accounts once I have the phone "rebuilt".
I've had the SGS2 for close to a month and in this time, i swear to honest God i've been more confused then i've been during my Symbian authoring days with my N95. I'm a tech savvy individual that reads up and researches things to death before acting but i'm just dumbfounded.
I have a Vodafone Romania SGS2 with the fallowing firmware: PDA: KE1 / Phone: KE1 / CSC: KE1 (CNX). I want to update to the KE5 firmware Kies is apparently showing me but due to a CTD Kies refuses to work and actually froze up my PC.
After repeaded tries, reinstalls, updates and tweaks i gave up on using Kies, especially after reading that it bricked some phones. So on i went to manually flashing it with Odin. I didn't get far because i've stumbled upon the thread with the official ROMS. So far i just want to install the official honest to god KE5 update for my network, to not mess anything up and still keep the warranty.
Romania
BUKE1:multiupload.com/7C3C2AOWGZ
Firmware info: PDA:BUKE1| PHONE:BUKE1| CSC:CNXKE1
BUKE1 Stock Kernel: Use the UK Kernel, it's the same.
BUKE5:multiupload.com/KHFWY2ZUOW
Firmware info: PDA:BUKE5| PHONE:BUKE1| CSC:CNXKE1
BUKE5 Stock Kernel:multiupload.com/EQ8RFFVB7A
Password: intratech XDA
Click to expand...
Click to collapse
So, i assume i need the BUKE5, which is the KE5 update, the full one, not the kernel alone? So i go there and the filename is: GT-I9100_VDC_I9100BUKE1_I9100BUKE1_I9100VDCKE1.exe (265.11 MB)
Am i just paranoid or is that not the correct firmware update? Also, upgrading the firmware needs to delete all my apps and app data. I backed them up using astro and the kies software to the best of my ability, but i ended up being stonewalled that doing anything, from firmware to rooting to etc, lands me with more work to be done restoring the apps and settings after i'm done with it.
I just had so many issues with the phone, and in the end it doesn't seem as 'smart' as i though it'd be. Everyone had high praise for it and to be honest, after beating around with it so much, i really wish people would have told me about the numerous issues it has before buying. Sadly, only glowing and positive reviews. -.-
In the end, can someone please help me atleast update the firmware?
LE: Forgot to mention in case of the Kies, Win7 Professional.
external sd card doesn't get wiped. Internal sd card doesn't get wiped.
You could try a no wipe root by just flashing a rooted kernel like chainfire rather than full rom. Then backup user apps using titanium.
Use odin for both and generally only use PDA file, and defaulted options like reboot and do on. See various kernel threads for that.
Look here http://forum.xda-developers.com/showthead.php?t=1103399
[29.06.2011][CF-Root v4.0] KE2/7/8, KF1/2/3/4 - su+bb+CWM4
Or here...
http://forum.xda-developers.com/showthread.php?t=1075278
[ROM + Guide]Official i9100 KE7/KE8/KF1/KF3/KF4/KF2/KF3 download and Root Guide.
The difference its that chain fire adds recovery tools but its only a kernel. You can add that later if you want.
After that, first full custom rom or rebranded rom does mean /data which are user app data directories may get wiped.
Sent from my GT-I9100 using Tapatalk
Edit I have ke7
Sent from my GT-I9100 using Tapatalk
Ok then, so i'm installing CF kernel to make a full backup for one thing. I get to the post, stumble around only on google with fake versions to see Odin at the bottom of the post attached. Get that, get the Zip, then get to the 'put your phone in download mode'. Ok i guess that's the USB mass storage? Two minutes later.. nope. More google. Realise it ment to reboot the phone in download mode by pushing Volume down, power button and the home key.
Right, finally i manage to install the CF kernel without issues. Now i accessed Titanium Backup and begin backing up all it can.
Will keep updated here.
After a bit of searching, i found Intratech actually put the wrong link up for the BUKE5 update on the vodafone network for Romania. I PM'd him and waiting for an update.
Good Luck. I'm sorry to hear you have had so many problems.
With regards to your warranty, you can always Odin the stock firmware and buy a USB Jig (devs are currently working on a software solution, should be cracked soon removing the need for the jig) from ebay to reset the custom ROM counter before you return the phone if needed.
The very next day, i got the BUKE5 firmware update and installed it succesfully. I will continue by rooting the phone with CF again and i should be done.
Atleast i got my 'totally painless easy-to-update firmware'.
Later edit: Seems there is no KE5 CF root. -.-
You probably do not need ke5 root.
So called insecure kernel only needed for two things.
1) flash secure rom (ke5) then insecure kernel (ke2 or ke7 kernel only) that you flash over your secured rom (ke5).
Insecure lets running one click root, that installs super user and busy box.
That is what you do I guess.
Then optionally you flash regular kernel (ke5) kernel only, not whole rom. You will keep super user and root but I lose adb root which you probably will not miss.
2) flash custom kernel. E.g. one like tegrak for cpu flexibility, or one like chain fire keep for custom recovery if you like
Cmw recovery
.
So get the latest that is compatible. New over old its often okay.
ke7 or kf2. Or do what some are doing and wait for ke9 (rumoured gingerbread upgrade release from samsung) that on my magic was a big upgrade in performance)
You get to do great stuff like tegrak over clock app with both 1 and 2.
Advantage of (1) is that flashing a genuine kernel after an insecure one used just too get root gets rid of that yellow ! you get with custom kernel when you boot the phone that could alert an engineer with a warranty claim.
Or stay on custom kernel and use a jig like previous poster said to clear the alert. Two pounds fifty well spent.
Advantage of (2) is that recovery installs are very convenient, and do not put the ! warning. Oh and updating phone on the train gets funny looks from fellow passengers looking over your shoulder.
On the other hand some people like using odin anyway "because that's what samsung engineers use"
Sent from my GT-I9100 using Tapatalk
I have been trying to root and change ROMs on my wife's Continuum. Thought root had taken. Still think it has. My question, is baseband and build supposed to have the same number in it? i.e. EC07 or EC06. Baseband is EC06 and build is EC07.
Is there a way to re-root and apply a new ROM using LinuxMint or Ubuntu? My Windows machine crashed and only discs I had that aren't packed away are Linux.
If this is covered elsewhere, I apologize but it is late and she needs her phone by Monday,
Thanks all.
Revs_ut said:
I have been trying to root and change ROMs on my wife's Continuum. Thought root had taken. Still think it has. My question, is baseband and build supposed to have the same number in it? i.e. EC07 or EC06. Baseband is EC06 and build is EC07.
Is there a way to re-root and apply a new ROM using LinuxMint or Ubuntu? My Windows machine crashed and only discs I had that aren't packed away are Linux.
If this is covered elsewhere, I apologize but it is late and she needs her phone by Monday,
Thanks all.
Click to expand...
Click to collapse
Actually, withvour Ron, ec06 is the proper baseband. You are good.
Ok, right baseband, why is she having so many problems I wonder? It will get hot when she charges it. It likes to randomly lose all the contacts. I can't get CWM to stay. Wish it was as easy as my Incredible was. That one just rocks on Cyanogen. Wish the Continuum was that easy and reliable now.
Oh, and when I turn on the wifi, it resets the phone and clears all the contacts. It will lock up for about 10 minutes or longer also.
Revs_ut said:
Ok, right baseband, why is she having so many problems I wonder? It will get hot when she charges it. It likes to randomly lose all the contacts. I can't get CWM to stay. Wish it was as easy as my Incredible was. That one just rocks on Cyanogen. Wish the Continuum was that easy and reliable now.
Oh, and when I turn on the wifi, it resets the phone and clears all the contacts. It will lock up for about 10 minutes or longer also.
Click to expand...
Click to collapse
What rom are you running? For the CWM, no, we don't have native recovery. You are goingvto have to apply update.zip every time. The other issues seem to be specific to your phone. A clean install from stock froyo may fix it. If not, possibly going back to stock éclair, then froyo, then the rooted rom. In order to help more, I'd need to know what all you have done to the phone.
It acts like I lost root. I swear I had Nuckin ROM on it. But when I pull up the phone info, it looks bone stock.
Firmware 2.2.2
Baseband is S:i400.0.6v.ec06
kernel is 2.6.32.9
Build is SCH-I400.ec07
That just looks like a stock setup to me.
What's the best way to root and upgrade using Linux? Is there a way? I had issues with Windows and its no more on my machines.
Revs_ut said:
It acts like I lost root. I swear I had Nuckin ROM on it. But when I pull up the phone info, it looks bone stock.
Firmware 2.2.2
Baseband is S:i400.0.6v.ec06
kernel is 2.6.32.9
Build is SCH-I400.ec07
That just looks like a stock setup to me.
What's the best way to root and upgrade using Linux? Is there a way? I had issues with Windows and its no more on my machines.
Click to expand...
Click to collapse
Well, nuckin's rom (and all of the others we have) are essentially debloated versions of stock,. We don't have any MIUI or AOSP ROMs. So, you really can't tell just by looking at the stats. Easiest way to tell if it's nuckin's rom is to look at the bloatware (or lack there of).
How hot is this thing getting when you charge it? These phones don't have very good ventilation. My battery will get up to 90 degrees when I charge, with my case on, while tethering. I've seen it get hotter, in the summer.
The contacts issue, I'm not sure about. That one is new to me. But, You might try pulling the contactsprovider.apk off of another of our roms and see if that fixes it.
As for upgrading using linux, I THINK Heimdall works with linux, but I'd get on the heimdall site and see if they have a front end. That would probably be your best bet.
If you do flash back to stock froyo, make sure you use the I500 PIT file found in the dev database under the development forum. And be sure to back up, first. Flashing that will do a data wipe.
EDIT: Yes, Heimdall does work with Linux
http://www.glassechidna.com.au/products/heimdall/
Heimdall works, just now I can't get the phone to reboot. keeps saying that it can't mount /dev/block/stl11 not sure why
Your cache might be corrupted. Did you use the proper pit file, with the stock production froyo? Those two must go together, and not with any other.
I seams at although we're having more and more people flashing and corrupting the cache partition. Ae there any similarities between the issues and what they are trying to flash?
pattielipp said:
I seams at although we're having more and more people flashing and corrupting the cache partition. Ae there any similarities between the issues and what they are trying to flash?
Click to expand...
Click to collapse
Its seeming to occur when people repartition, when they shouldn't. Or, more to the point, using the PIT file with one of the debloated roms (yours, nuckins, or clean)