So i been using custom rom with custom recovery for long time since the phone came out i don't care about it be rooted anymore but would like to keep the custom recovery. just love that feature turn your phone into usb stick. I prefer to use the one in recovery because mounting and unmounting while computer is rebooting is annoying i can't usually boot from that device inless the phone is in constance usb mode. Yeah sure people might say just use a usb device I prefer not to carry one around. Why can't my phone be one?
Question is... If I flash to 1.6dmd64 image non-rooted will still get the ota without losing custom recovery. or do i have to flash to stock -_-
model mt3g black
recovery amon_ra
Related
Hi all,
I'm expecting my Galaxy S to arrive in the next couple of days, and I have a couple of questions about it.
I'm coming from an HTC Magic which I bought off eBay pre-rooted (see sig), so I'm not exactly up to speed with the process of rooting a phone for the first time.
Firstly, how hard is it to root the SGS? I've seen that it can be done with just an ADB command and an update.zip, is this right? Do I even have to use the ADB command? Is there a way to boot into recovery from the phone itself if I have an SD card I prepared earlier?
Secondly, what's the availability of custom ROMs like? One of the first things I want to do with the phone is nuke all the Samsung crapware from it and take it back to vanilla Android, if possible. The Magic has more ROMs available for it than you can shake a stick at, but I figure that the SGS is a much newer device, so won't have as many around at the moment. Is there anything precluding the production of custom ROMs? I've heard tales of encrypted drivers being the norm for Samsung, which sounds a bit crap.
Thanks in advance guys, I'm looking forward to my new phone (if not the bill for it, heh), and playing around with it in good old XDA fashion... and sorry if these questions have been asked before
whats your reason for wanting to root the phone immediately after you receive it?
I also thought through this, because i did it with my xperia. You can change the samsung touchWiz homepage via LauncherPro app
The only reason i would do it, would be to get froyo on a custom rom, but im going to wait and see if samsung do the good thing and give it to us via an update. As of yet there arent any custom roms for this anyway i dont think
It's easy to root the phone.
Download the update.zip file from this thread: http://forum.samdroid.net/f49/superuser-su-busybox-i9000-v-2-01-07-2010-a-1355/
Or direct link here
Copy the file to the internal storage card of the phone using Kies or whatever method you like.
Disconnect the usb cable
Turn off the phone
Press and hold these buttons at the same time: volume up+home+power, keep them pressed until you see the samsung logo.
Use volume rocker to navigate to update.zip and then press home to select.
Phone will reboot and you are now rooted with superuser.
The whole process takes less than 5 minutes.
I'm not responsible for anything
Cant you just have the latest firmware update added to update.zip?
rooting is only needed for custom roms etc?
TO OP
Rooting the phone is very easy and is a simple as flashing an update zip with SU + busybox with the stock recovery image, quite funny actually that they allow stock recovery to flash any signed zip .
As to the second question i am also very keen to know myself as i believe it should be very easy to create custom roms as i have edited /system directory mutlipul times myself and i believe i have came across a method to get JIT onto our device however i need the help of someone using a linux computer and as a few good skills with android .. PM ME.
sensi_ said:
whats your reason for wanting to root the phone immediately after you receive it?
Click to expand...
Click to collapse
So I can restore all my apps from my Magic... although now that I'm running CM6, that may not be as feasible as it was this morning
Just a stupid question ... do we need to root the phone each time we flash a new ROM ??
Well, given that all the stock ROM needs is a simple update.zip flashing, it looks like the stock bootloader has security off. Like "S-OFF" on the Dream/Magic HBOOT. All you need for root access is the su program and the superuser.apk thing. Awesome.
hey everyone, im having a problem after trying to flash a rom. in the middle of the flash my phone went to the stock recovery. Can't get into clockwork. error = "can't mount /dev/block/vold/179:1" and cannot verify whole-file signature. Does any one know how to fix this with out flashing back to stock with Odin? the reason being is that my phone will connect to comp thru usb but it will not read the sd card, cant mount. further more, device cant be recognized when in downloader mode. my question is, is there a way to get the to get the sd card mounted to flash eclair and start over...bty my phone wont boot, stuck at samsung screen...thanx
I am not sure there is any other way other than ODIN. You can try removing battery for a couple minutes and booting again, but it is likely that if your flash was interrupted that you wont have the ability to get into clockwork. I have had a few flashes interrupted and the only way I was successful was pulling battery and using ODIN. You shouldn't need to mount your SD when you are using ODIN. ODIN connects to the internal memory.
I don't think ODIN even looks for your driver. First time I used ODIN I didn't even have it installed. However, the root software definitely needed it.
Make sure your USB is connected directly to your motherboard USB port i.e. the back of the computer. Go into download mode, then connect your phone.
There is no way that I know of to apply clockwork from an update.zip. Does adb work in the stock recovery?
And have you seen if another computer with Odin will recognize the phone in download mode? We have a service computer thas has issues with epics, so our service people usually bring them to me when Odin isn't cooperating.
Your best bet is to Odin, if possible. If you can't get Odin to work from any computer and you can't access via adb, then there isn't much you can do.
thanks swanysto and DiGi760 for the replies. ima lurker that knows how to read and follow instructions. ive flashed multiple roms before, zips, ect. on the epic since ive got it without much problem at all...anyways i did like 4hrs of reading before i posted, hoping to not have to ask this question in this rude forum(the bickering of stupid replies) but i had to anyways.... i have tried to odin thru the motherboard in the back and that didnt work. i also tried adb but that didnt work either. so since the stock recovery came up, couldnt get into the phone, and i was able to do a factory wipe. i decide to take a shot at taking it to sprint repair. and guess what......they gave ya boy a new phone! i thank you guys for taking the time to reply! hopefully people will be more helpful like you guys( trying to be helpful answering question) than just starring at peoples posts and being uncommunicative. in the future if ur tired to repeating yourself because youve helped before, maybe u should make a note pad full of answers called "replies for noobie questions" so yall can cut and paste...
well lets just pray that sprint wont be able to see what u did and charge your account later......they did it to me for my evo, they added an extra $400 to my bill.
really? like the same exact issue?
even after i formatted everything(system, data, cache, sd card) then the stock recovery?
Hi there,
I had been umming and arring about rooting and installing a new ROM one of my familys HTC Heroes for some time now and finally after reading lots of "How to's" on lots of different forums I decided to take the plunge and give it a go using the guide on here.
Both my wifes phone and my sons phone are sim unlocked Orange HTC Heros running 2.1-Update 1.
Rooting it was easy. One press of a button and I was there. Its pretty much worked OK and I have sucessfully made three backups of the wifes Hero.
My main query and this is the bit I have not really been able to find much info about despite spending a day trawling through the forums looking for similar queries is this:
Having flashed my recovery image file, the first time I reboot I can get into the recovery mode just fine. From here I can make a backup of the current ROM after which the Hero reboots and goes back into the OS as it should.
If I then shut it down and reboot using the HOME key + POWER option It does not go into the recovery mode. I get the screen with an image of the phone next to a red triangle with an exclamation mark in it.
Using the advice from various forums whilst searching for further advice / hints I have left the phone for up to half an hour but it stays on this screen. The only way to get it out of this screen it to pull the battery.
If I then boot up the phone and reflash the recovery image, I can then get into the recovery mode once again but for ONE BOOT ONLY.
I have tried AmonRA Revcovery v1.7.01. and also the Clockwork Recovery 2.5.0.7 images and both produce the same results. I have tried flashing the images via ROM Manager and also via Android Terminal Emulator
My question is this: Do I have to flash the recovery image EVERY time I want to open the recovery mode or is there something I have missed? At present I have held back from installing a new ROM in case I go past a point of no return where I brick the phone. Neither my wife or son would be too pleased despite my son wanting a better ROM on his.
Apologies for writing "War and Peace" but I wanted to make sure I had covered all I could and hope this is a) not a query already posted elswhere which I have missed b)posted in the right place. Apologies to any forum mods if its not.
Regards
Rhinestone.
hmm look on the unlokr.com or something like that. They use some simple passes and it's the way i did it. the on;y difference is that my phone wasn't blocked on a carrier...
1.there is a program that roots the hero's rom
2.after that i recommend installing clockwork recovery mode (it doesn't need signed zips)
3.if you don't feel safe doing this, i recommend to stop... I know that the 2.1 rom is boring but you can end up with a bricked phone after this...
The official 2.1 update has a script that reflashes the stock recovery every time the phone is shut down.
Hunt about for a modified 2.1 rom, all of them have had that script removed. I'm not a huge fan of sense now, but when I did use it, I found villainrom to be a good 2.1 sense rom.
TheReverend210 said:
The official 2.1 update has a script that reflashes the stock recovery every time the phone is shut down.
Hunt about for a modified 2.1 rom, all of them have had that script removed. I'm not a huge fan of sense now, but when I did use it, I found villainrom to be a good 2.1 sense rom.
Click to expand...
Click to collapse
This, just flash a custom ROM and it will stick.
Hello,
Problem might be with rooting, possible it has not been rooted completely or anything messed up. You can try this for rooting.
http://unrevoked.com/
If you are sure its rooted completely, then check out Superuser apps, if its there, and you are rooted, if not then download terminal emulator and type "su" command, if its doesnt display any error then its rooted.
Other then this,
problem might be with the recovery images you are flashing, download droid explorer its a window application, its has an option of flashing recovery with one click, simply choose recovery image & flash it, clockmod recovery or amonr any of this you can get in xda.
Ok, i realize i have a different phone from this thread but it is close and my problems closely reflect the issues ive seen with the Galaxy S.
A little background. Im no perfect i know what im doing when it comes to rooting. I have an HTC Tbolt and rooted many of those, an older touch pro 2, and this is first time doing a samsung. I am getting the hang of ODIN (i wish everyone would just use this program instead of bouncing back and forth between heimdall and ODIn but whatever) Im liking ODIN cause it works well. I was successful at flashing a new rom into this Samsung phone. 95% of it worked, wifi i think didnt but everything else worked. While trying to fix the phones wifi somehow i have stopped the phone from booting into CMW recovery unless forced or booting into a rom. I can get into CMW but i must hold down the Vol Down button to get there, otherwise a clean basic boot takes me to the stock android system recovery screen and will not boot a rom.
I have something backwards or out of order. I am just trying to get the rom to identify the installed CMW and the installed ROM through CMW but it wont do it.
Any help would be appreciated, i dont want my GF to find out i jacked her phone lol
Which phone do you have? SGS? I can just talk about SGS+ but I guess its similiar.
Try to install CWM with Odin, normally it should replace the stock recovery (haven't heard of both running at once).
Once you have installed CWM you can install your custom ROM with CWM (look at the install instructions).
If you want to install stock ROM with Odin it will replace your CWM with stock Recovery.
Post the link of the thread/recovery you want to flash.
annqx said:
Which phone do you have? SGS? I can just talk about SGS+ but I guess its similiar.
Try to install CWM with Odin, normally it should replace the stock recovery (haven't heard of both running at once).
Once you have installed CWM you can install your custom ROM with CWM (look at the install instructions).
If you want to install stock ROM with Odin it will replace your CWM with stock Recovery.
Post the link of the thread/recovery you want to flash.
Click to expand...
Click to collapse
Its a stratosphere. Im using the root and / or stock files in the root method. I use ODIN to flash the StratCWMRecovery.tar.md5 and if i tick "reboot" then it reboots into CWM i install a rom or stock rom and it finishes. I reboot the phone and it instantly goes back to android system recovery. If you like ill make a short video to give you an idea of whats going on.
I will note that im close to making a jig but its not 100% bricked obviously. 3 button method still works (and unecessary at this point since all the phone does is go straight into the stock bootloader) and then after i install CWM i can force it in to CWM but it wont actualy boot into it.
From a programing standpoint i feel the pointers or partitions are incorrect. Its like booting a computer that has a hard drive with windows installed however getting the bios to tell it to boot from the hard drive isnt working. THats the easiest way to explain this.
One thing i want to note is the only errors i am getting are when i try to partition the SD card from CWM. I get an error saying sdparted is not found.
I am not getting a full understanding of how the root system works on this phone.
Again any help is appreciated.
Made a short video. Its uploading now. http://www.youtube.com/watch?v=tFZ5Adm5AdQ
So whatever i did i was able to fix. I think me being a very visual person and normally having access to all files i need or could use in a situation is always nice. Here, i didnt but i found them. Here's the link. Its obviously for stratosphere but i took about 10 minutes and let ODIN install all these files and it worked.
original posting but the link doesnt work for download
http://rootzwiki.com/topic/11183-eh2-full-factory-odin-restore/
where i downloaded it
http://www.fileswap.com/dl/t4D235pUTO/SCH-I405.EH2_rel.md5.html
Again this is for stratosphere. Since it really helped me return to stock and allow me to re root in about 15 minutes this thread should be moved but there is no stratosphere area
My phone suddenly had a momentary display malfunction (some of the text on the screen just turned into garbled pixels) and then entered into a boot loop. I didn't make any changes or updates to the phone recently. It no longer boots normally - just the Samsung logo and some of the Verizon logo animation, then it reboots and starts again. How do I pull my user data off (photos mainly) before trying a factory reset? The phone is totally stock. I haven't unlocked it, rooted it, or installed any custom recovery/ROM/bootloader/whatever. (I sound like I don't know what I'm talking about because I don't, haha.) The touchscreen is fully functional. I'm sure this has been covered here before, but I haven't found anything that totally explains how to do this in this particular situation, so I'd really appreciate any help anyone can provide.
The only time I can get the phone to show up under adb devices is when I boot it in recovery mode and select "Apply update from ADB". But it says "sideload" next to it in adb devices, and the push, pull, and shell commands return errors. I've read that this is normal. Wiping the cache partition didn't solve the boot loop problem.
If it helps, this is what the top of the recovery screen displays:
Android Recovery
Verizon/heroqltevzw/heroqltevzw
8.0.0/R16NW/G930VVRSBCTC1
user/release-keys
I'm no Android expert, clearly. I've heard it mentioned that I need to install a custom recovery in order for this to be possible. To be clear, I want to make sure I don't erase the user data before I have a chance to pull it off the phone. These are the questions that I still have after reading information elsewhere (some of which I'm just asking out of an abundance of caution):
Is it correct that I need to install a custom recovery before I can pull this data off the phone?
Do I need to have it unlocked/rooted/anything else in order to be able to install a custom recovery? Or is there anything else I should do before installing it?
Which custom recovery should I install?
Do I need a custom ROM, if that's a different thing?
Do I need a custom...bootloader, if that's also a different thing?
Should I use Odin or Samsung Smart Switch to install the custom recovery?
(Extra credit: Does it sound from my description of how the boot loop started that this phone has hardware problems and should be replaced ASAP?)
Thank you so much for any help you can provide! Any extra information beyond my questions will be very much appreciated, too, of course. You guys never cease to impress.
You have a B version bootloader like me, and so far no root/custom recovery has been made for our versions of bootloaders. If I were you, I would check if you had maybe like a previous backup, and if Google made an automatic backup of your apps and photos? If you didn't use a 3rd party backup, and if you don't want to wait, you might lose some files. I also think you might be able to flash a certain part of stock firmware to get your phone to boot again, but I'm not sure
Also, if you don't care about files that can't be get through automatic backups, might as well flash a whole stock firmware, which as far as I know, may be the easiest way to get out of one.
Please correct me if I'm wrong
Also to answer your bullet points:
1. I'm not sure if you need a custom recovery, but from my experience from a Verizon s5, that's probably a yes.
2. Since this is Verizon, you would need to unlock your bootloader in order to install a custom recovery, which in where I posted my first reply, the B version of the bootloader is still locked down without any known way to unlock it. You and me are stuck with this, as I also have the B version.
3. If the heavens line up and you somehow unlock the bootloader, try to flash a recovery Called TWRP under the name "Herolqte" (that's what I think). If that doesn't work, try to find one that works with the phone on XDA. If neither of those show up try to use another custom recovery like CWM.
4. If your trying to recover data on a phone, flashing a custom ROM is probably the last thing you want to do. A custom ROM is a modified version of Android, which may mean you'll have to format your device anyways so this is probably not what you want (even though it would be nice :[ )
5. As in post 2, all you would need to get a custom recovery is to unlock the bootloader. I'm not even sure if you CAN get a custom bootloader, as Odin won't even let me flash a stock bootloader to my phone that is the same exact Version >:[
6. You would need to use Odin if you were trying to flash something to your phone. Smart switch I think WOULD let you back up your device, but you would need to be on the home screen on your phone, which in turn, would probably need you to be out of that bootloop.
7. This is probably a software issue. If you don't care to much about the idea, try flashing some parts of a stock firmware. I was personally in a boot loop 2 days ago, but I flash a stock modem file (I think that was the second file slot from the bottom in Oden) and that got me out, but for some reason wiped my phone clean, and I'm not sure why.
Anyways. Goodluck in recovering your data. Also I'm not sure if a factory reset would even fix a boot loop
yaas
yaas