Related
I did a PaSSIMG FRG33 version, but I can not root with universal androot also can not return to the version of PASSIMG FRF91, indicates that it is old version. Anyone know?
As it stands, if you want root you're back to having to unlock the bootloader.
You could try: http://forum.xda-developers.com/showthread.php?t=726258 and seeing if you can revert to FRF91 afterwards.
Try?
But someone made with good results?
You should have rooted FRF91, installed a custom recovery, and then used an update.zip format of FRG33 to update to update the system and boot.
kam187 said:
You should have rooted FRF91, installed a custom recovery, and then used an update.zip format of FRG33 to update to update the system and boot.
Click to expand...
Click to collapse
No work recovery with update.zip. Android exclamation!
Also, i can not install passimg frf91, indicat that is a old version
Androith said:
No work recovery with update.zip. Android exclamation!
Also, i can not install passimg frf91, indicat that is a old version
Click to expand...
Click to collapse
Android exclamation is STOCK recovery. Kam is saying "custom recovery" like Clockworks or RA.
Ok,
I got it, but unlocking fastboot to install the superboot. Now I have total control
Now we have to wait to close lock
Thanks!!
Which version of superboot should we be using to root this frg33?
The superboot FRF91
http://www.mediafire.com/?4nnez0uddqk519r
Thanks a lot. I opted not to wait for a new 1-click version. Unlocked the bootloader by cmd prompt. It was weird though. I thought when I was reading about superboot that all you had to do was dbl-click it from windows, but I ended up having to run it for cmd prompt, too. Either way, I'm rooted now. My only remaining question has to do with the custom recovery stuff. I flashed the "latest clockwork recovery" in ROM Manager. Then I flashed the modaco rooted/deodexed/busybox/etc. version of frg33. Is that all I need for my phone to be "safe" at this point? I guess ROM manager let's me flash just about any of the custom ROMS, but if one hangs on load, I just wanna make sure everything is restoreable.
BTW....Android clearly has the best and most helpful community of users that I have ever seen!!!
makelegs,
Glad you got it all worked out and are truely unlocked and rooted. As long as you nandroid, you are safe on what ever yoy wan to do. The dreaded, botched radio flash is probably the only way to get hurt. At least that is my understanding.
That's the funny thing.... I am completely confused about "nandroid." I can't figure out if nandroid is a general concept or something very specific. I have a couple of complete backups performed with clockwork, but nowhere in my "recovery" area have I seen the word NANDROID. So I'm pretty sure, at this point, that if the fit hits the shan I have a plan-b, but nobody ever says "be sure to 'some other kind of' backup." They always say "be sure to nandroid." Am I taking this too literally??? or have I overlooked a step in this process?
I even paid for the premium Rom Manager upgrade so that I could try out different ROM's, but I have this sneaky suspicion that I oughta get closure on the whole "nandroid" thing before I get too carried away.
You've been a lotta help.
makelegs said:
That's the funny thing.... I am completely confused about "nandroid." I can't figure out if nandroid is a general concept or something very specific. I have a couple of complete backups performed with clockwork, but nowhere in my "recovery" area have I seen the word NANDROID. So I'm pretty sure, at this point, that if the fit hits the shan I have a plan-b, but nobody ever says "be sure to 'some other kind of' backup." They always say "be sure to nandroid." Am I taking this too literally??? or have I overlooked a step in this process?
I even paid for the premium Rom Manager upgrade so that I could try out different ROM's, but I have this sneaky suspicion that I oughta get closure on the whole "nandroid" thing before I get too carried away.
You've been a lotta help.
Click to expand...
Click to collapse
Can't speak for Clockwork but on Anom the backup goes in /sdcard/nandroid/DEVICEID/dated-subdir
Each time you make a backup using nandroid, it's a new directory.
And you can NOT restore a nandroid made from a different recovery from what I've read. If you make it with Clockwork you gotta restore it with Clockwork.
makelegs,
It has become a general term with the advent of Rom Manager/ClockworkMod. If you look at the top of the Clockwork screen when in recovery, it say nandroid. The term generally means a full image backup of your phone as opposed to just backing up apps/data. In the nandroid the OS and all else is backed up. So, I wouldn't give it a second thought.
What khaytsus said is the only important thing. Restore thru whichever recovery you backed up with. Clockwork to Clockwork or Amon to Amon.
Amon is put into the nandroid file on your sd and Clockwork is put into Rom Manager under Backups. Although, you can get to them a couple different ways in Clockwork. Thru Install Rom From SD Card or Manage and Restore Backups. Also by booting into Clockwork Recovery. You probably already know that if you use Clockwork.
Ken
Is it actually probable that 1 click might be made to work for 33? It doesn't seem like there are many other users with stock/33 like myself. I feel like a horses ass for flashing it and screwing up my protected apps. All through the incremental updates that led us from 2.1 to froyo went thru easily with no paid apps issues so I didn't have my guard up for this one. (Unless they all had a modded fingerprint status which I starting to think I may remember them having, whatever, this is a bummer...)
Maybe it will be updated, but the folks on frg22 (i think) have been waiting even longer. I was just too busy and OCD to wait it out.
It was probably only ever a matter of time before I went the unlocked bootloader/root route. This was just the catalyst for me. I learned an awful lot in the process. Alas, my phone is back to "normal", but running modaco's rooted/deod/busy/frf91 finger/etc... version of FRG33. And I now realize that if I had just flashed the clockwork recovery to begin with, when I was 1-click rooted on frf91, then this whole thing would've been substantially less of a PITA for me.
Good luck!
FRG33
I got caught out i had 1 click root with cm6
But then installed FRG33 not realising i would lose root if i reverted to it after i had done a backup of cm6 .
I had a lot of things including adfree working on FRG33 prior to recovery .
I think the universal androot app uses the "exploid" method which indeed was patched in FRG versions. But I believe someone on the forum reported that FRG22 or FRG33 was still vulnerable to the "rageagainstthecage" root exploit.
Can someone here verify whether FRG83 is still rootable using "rageagainstthecage"?
You can try the instructions for rooting FRG33 in the Wiki on FRG83.
Hey people im having A huge problem (took me ALL afternoon to get here) ok so i flashed a bad ROM, Odin'ed back to stock (but when i did that it always said "wipe data failed", and now im trying to restore a backup in recovery and it keeps on freezing at "pcsync_stream" and it also froze one time at "HALGPS_conf.cfg", i replied on a post that had a similar problem but no one answered so i made my own, here is the link to the other post if you need more info:
PLS REPLY AND THANK YOU!
I ran into the same problem today. I'll keep an eye on this post and let you know if I come up with anything.
WAudette...
Did your bad ROM also flash a new kernel? Nandroid doesn't flash the kernel back, so you might need to do that as well. I have no idea if this is THE problem, but it is a common problem.
Good luck.
I've run into this before myself, when I forgot to disable the Voodoo lagfix before flashing something. You could try disabling it using ADB if you know how to do that, but that didn't work in my case. You're likely going to have to use ODIN. The instructions are here: http://forum.xda-developers.com/showpost.php?p=8129898&postcount=1 under "Did you flash something before disabling Voodoo?", Fix 1.
I just noticed that there seems to be some worried about rooting if you ran the verizon DL09 odin package. Don't worry. d2 root method for fascinate found on XDA works just fine. http://forum.xda-developers.com/showthread.php?t=779238
Have not found a one click root that works yet though. If you find one, post it!
**UPDATE**!!!
Looks like there are some that are hit or miss... may have to run them a few times and wait upwards of 5-10 minutes for some.
if you don't want to wait use perm d2 method. happy rooting!
I actually used the one click root method that is found on android central after i upgraded to DL09. Worked for me. It was strange because i had to do it 3 times until it finally ran.
To get it to run it needed over 5 mins (which the once click says if it takes more than 5 mins try again) I had run it then lost track of what i was doing because i was at work. Then next thing i know it completed itself. So i can confirm it does work.
jselden said:
I actually used the one click root method that is found on android central after i upgraded to DL09. Worked for me. It was strange because i had to do it 3 times until it finally ran.
To get it to run it needed over 5 mins (which the once click says if it takes more than 5 mins try again) I had run it then lost track of what i was doing because i was at work. Then next thing i know it completed itself. So i can confirm it does work.
Click to expand...
Click to collapse
Looks like patience is the key here people... if you are familiar with adb, you could probably root it faster. i ran z4 and let it run quite a few times myself before i said screw it (i actually got a FC or 2 as well) and just ran the perm d2 method.
thanks for the heads up!
Possible reason why
I'm gonna look for the page I got my 1 click method from, but it worked for me on the first time. I rooted immediately after flashing the odin file. Then I screwed something up before I pout clockwork on so I reflashed since I lost everything (not really, thanks to Titanium Backup). Then I immediately flashed the clockwork after and then the 1 click failed twice. Reflashed the official dl09 then 1 click and, boom, rooted on the first try.
After doing a little searching, apparently the clockwork.tar flashes a DI01 kernal. So if people are flashing clockwork before rooting, this could be the culprit. I use this method found here
http://m.forum.androidcentral.com/showthread.php?t=33899
Hope this helps some people out.
one click root worked for me
The one click root method from android forums worked for me (said it completed) but none of my root access apps are getting root access.
I rooted through the manual adb method.
I'm having trouble booting into clockwork though.
After grabbing clockwork recovery from ROM manger, it goes to stock recovery where it errors with "signature verification"
do I have to push the original clockwork.tar through odin?
edit: http://forum.xda-developers.com/showthread.php?t=913470 <<< fixed the issue. push through odin
I used the adb method from android central and I had to wait 5-10 minutes to be kicked back out to the windows command prompt after running rage.bin.
It's not just 1 click methods that sometimes take a long time to complete.
i used the 1 click method from dirkk. i had problems with my phone reading as a media driver(trying to sync to my pc) so that was causing the 1 click method to fail at first. once i disabled the media sync it was sucessful first try.
Today I installed my first rom, it was called dl09_supah_clean_04. That worked ok but I could not receive text messages. I thought maybe I'd try another rom. So I downloaded one called hamsters rom. Once I booted the phone up with that rom I got a bunch of errors. So I restarted and now get nothing but the samsung logo flashing. I go into recovery mode, click on update.zip to load clockwork recovery and get a message saying:
e:can't mount /dev/block/vold/179:9
(no such file or directory)
e:can't mount sdcard:update.zip
Installation aborted
I'm just wondering if I am screwed here. I'm about to plug the sdcard into my computer and copy update.zip again in hopes of getting clockwork recovery to work.... just wondering if anyone has any ideas in case this doesn't work.
You need to put it on the phones internal sd card plus sometimes you need to put text message setting yourself like message centres number .
Sent from my GT-I9000 using XDA App
Is this a troll?
mdisaac said:
Today I installed my first rom, it was called dl09_supah_clean_04. That worked ok but I could not receive text messages.
Click to expand...
Click to collapse
That's because you have to install a DL09 kernel and modem as well.
I thought maybe I'd try another rom. So I downloaded one called hamsters rom.
Click to expand...
Click to collapse
How clueless are you?
That's a i9000 ROM. Or Captivate port.
Every single flashing thread warns
DO NOT FLASH ANYTHING NOT SPECIFICALLY FOR THE VERIZON FASCINATE
You flashed a GSM ROM onto a CDMA phone. That's just asking for a brick.
Now download this (and since you can't figure obvious things out, flash it into *PDA* of Odin, NOT NOT NOT NOT NOT "phone"), and pray it works.
THANK YOU, THANK YOU, THANK YOU!!
My phone is back and working on the stock rom. I am definitely clueless when it comes to this but I am not giving up. I am going to get the dl09_supah_clean_04 rom working. I'll be more careful this time though.
Thanks again!
s44 said:
Is this a troll?
That's because you have to install a DL09 kernel and modem as well.
How clueless are you?
That's a i9000 ROM. Or Captivate port.
Every single flashing thread warns
DO NOT FLASH ANYTHING NOT SPECIFICALLY FOR THE VERIZON FASCINATE
You flashed a GSM ROM onto a CDMA phone. That's just asking for a brick.
Now download this (and since you can't figure obvious things out, flash it into *PDA* of Odin, NOT NOT NOT NOT NOT "phone"), and pray it works.
Click to expand...
Click to collapse
not trying to be a d!ck but, you really need to stop before you do brick your phone. read, read, and read some more. its clear you dont understand what your doing and are going to end up screwing up even worse. read EVERYTHING dealing with ONLY the VZN fascinate. if it says anything other that VZN fascinate DO NOT READ IT. your in to big of a hurry and will brick your phone. hell, i have been hacking phones for years and am still not comfortable with android yet. i have rooted but not installed a rom because i dont want to mess it up. hell, i havent even done the new update from VZN. im waiting for more reports to come in. just take your time and read, then worry about flashing to another rom.
If you mess your phone up just use odin and the official stock DL09.md5 to return the phone to normal. Easy.
mdisaac said:
Today I installed my first rom, it was called dl09_supah_clean_04. That worked ok but I could not receive text messages. I thought maybe I'd try another rom. So I downloaded one called hamsters rom. Once I booted the phone up with that rom I got a bunch of errors. So I restarted and now get nothing but the samsung logo flashing. I go into recovery mode, click on update.zip to load clockwork recovery and get a message saying:
e:can't mount /dev/block/vold/179:9
(no such file or directory)
e:can't mount sdcard:update.zip
Installation aborted
I'm just wondering if I am screwed here. I'm about to plug the sdcard into my computer and copy update.zip again in hopes of getting clockwork recovery to work.... just wondering if anyone has any ideas in case this doesn't work.
Click to expand...
Click to collapse
You also need to odin the DL09 modem. or SMS and other things WILL be broken.
1.4hitachi said:
If you mess your phone up just use odin and the official stock DL09.md5 to return the phone to normal. Easy.
Click to expand...
Click to collapse
When people take Odin for granted, they end up with bricks.
Odin can be your friend...as long as you use PDA and not Phone...which is counter intuitive
adrynalyne said:
When people take Odin for granted, they end up with bricks.
Click to expand...
Click to collapse
Shouldn't you say, 'when people use Odin incorrectly"? I mean, as long as he follows the instructions and un-does and kernel changes beforehand the device will be returned back to stock. Also with the official DL09.md5 package it has inside all necessary operating parts. It sounds to me like all he did was attempt a rom flash twice. Odin with the "offical" DL09.md5 will return his Fascinate to stock.
Thanks everybody! I got back to stock and let phone receive the ota update of DL09. Figured that would take care of the kernel and modem and I could install dl09_supah_clean_04. Worked like a champ. I think I learned a lot in this process as well... time will tell.
Mods, if this is the wrong place I apologize! This just might help someone else though.
I just rooted a new NST. I've had it for two days now, so it is quite new.
As I cannot post in the dev section I will put my observation here.
At first I tried the touchnooter, the first one. I failed, was stuck in a boot loop. I had checked the version number before beginning. It said it was updated properly. I figured it was just me and went to try another root method.
I then used MinimalTouch 1.1beta5. Same thing, boot loop after the first step.
After restoring the NST using the restore zip and de-registering/re-registering it.. I rechecked (for the 5th-6th time) the version number. Still correct.
And then, just for poos and giggles.. I applied the update anyways. It did its little thing... and then I was able to root the dratted thing.
I am unsure as to why this worked, but it did. So.. if everything else fails... update anyways.
katsrevenge said:
Mods, if this is the wrong place I apologize! This just might help someone else though.
I just rooted a new NST. I've had it for two days now, so it is quite new.
As I cannot post in the dev section I will put my observation here.
At first I tried the touchnooter, the first one. I failed, was stuck in a boot loop. I had checked the version number before beginning. It said it was updated properly. I figured it was just me and went to try another root method.
I then used MinimalTouch 1.1beta5. Same thing, boot loop after the first step.
After restoring the NST using the restore zip and de-registering/re-registering it.. I rechecked (for the 5th-6th time) the version number. Still correct.
And then, just for poos and giggles.. I applied the update anyways. It did its little thing... and then I was able to root the dratted thing.
I am unsure as to why this worked, but it did. So.. if everything else fails... update anyways.
Click to expand...
Click to collapse
If you restore, you must allways update again to the 1.1, as restoring brings you back to 1.0 (except on some newer devices that are shipped with 1.1.0 and also contain 1.1.0 on the Factory partition) , anyway glad you sorted it out .
eded333 said:
If you restore, you must allways update again to the 1.1, as restoring brings you back to 1.0 (except on some newer devices that are shipped with 1.1.0 and also contain 1.1.0 on the Factory partition) , anyway glad you sorted it out .
Click to expand...
Click to collapse
Well, that's the funny thing. It was 1.1 out of the box. Or so it said??
But I will remember that and just 'update' it anyways.