How to root FRG33? - Nexus One General

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.

Related

Telus Hero Nandroid backup

Hey guys, I'd first like to thank everyone posting guides on the forums, has made my job a lot easier. I'm currently in the middle of trying to root my telus hero with the gold card method. I made the gold card, i think anyways, but before i go ahead and run the RUU file to downgrade, I want to make a nandroid backup of my phone. I downloaded the recovery image which is supposed to have nandroid v2.2 in it, but I'm not to sure how exactly to use it... I'm kind of a reallllly big nub.
chaosthebomb said:
Hey guys, I'd first like to thank everyone posting guides on the forums, has made my job a lot easier. I'm currently in the middle of trying to root my telus hero with the gold card method. I made the gold card, i think anyways, but before i go ahead and run the RUU file to downgrade, I want to make a nandroid backup of my phone. I downloaded the recovery image which is supposed to have nandroid v2.2 in it, but I'm not to sure how exactly to use it... I'm kind of a reallllly big nub.
Click to expand...
Click to collapse
From my understanding, as I saw it, I believe that the RUU's are safe, since they're HTC approved images, just that the gold card allows you to revert to a lower version of an HTC rom. Think of it as the RUU's as an official update, but an older official update, and the gold cards make your phone seen as a phone that can accept any update (new or old). So there will not be any harm when you run an official update like this unless your computer crashes midupdate or you pull the battery..or the cable gets unplugged.
Nandroid backups can be produced using the recovery image (i call it a menu since that's all you really see from it), which is covered later in a tutorial if you're reading one. This recovery image is applied after a downgrade (the downgrade gives you the ability to have root access, which is i believe necessary to get the recovery image installed), and thus be able to make these nandroid backups. The nandroid backups then get saved onto the SD card to which you can transfer to your computer for safe keeping. This ensures you can revert to an official rom with previous settings applied in case of an awry custom rom installation. The nandroid backups can also be used for nonofficial roms that you've deemed stable when you tested them, and this can be done as many times as you want.
I'm not sure if I'm entirely right, but I believe I have the gist of it. If anyone can correct me for any errors or can elaborate more, please feel free to share After all, we're all new at one point, hopefully veterans of this will chime in and allow us all to learn!
Also, welcome to the forums! Glad to have you!!
alright, so if I understand correctly, I first need to root my phone to gain root access to perform these nandroid backups?
I'm using this guide" Get started rooting Telus HERO130! (No need for QMAT!)", I'd post a URL but it seems that since I am a new member I'm not allowed to post URL's. I've gotten up to step 6. When I run that RUU file it says its going to erase everything on the phone, so I decided its probably best if I backed up my phone before I try this in the event that I mess everything up horribly.
Is this possible without having root access to use the recovery image with nandroid on it? or am I just having another noob moment?
thanks for the help!

[Q] All I want is Frodo 2.2 + root...but how???

All I want to do is upgrade to Froyo 2.2 and retain root so that I can use Wireless Tether. I've been reading several different EVO/Android forums but it seems like the more I read, the more confusing it gets. I'm still a noob, but here are my questions so I hope someone can lay it all out in the open for me.
Currently, my EVO has Unrevoked3 applied so I'm running on the "updated" 2.1, and I have root access and wireless tether is working as of now. Phone specs are:
Firmware version: 2.1-update1
Baseband version: 2.05.00.06.10
Build/Software number: 1.47.651.1
PRI version: 1.40_003
PRL version: 60665
1) What is the best/most reliable way for me to update to 2.2? Can I use Unrevoked Forever to do so? Or do I have to use some manual method? Toast's method? ROM Manager?
2) I read the steps for installing on the Unrevoked site, but I don't understand the terms it uses. It says to "flash from custom recovery". First of all, how do I access this custom recovery tool or whatever? Second, some ppl said they use a ROM Manager. Other sites say to "boot into recovery". Still, some instructions say boot into Clockwork....How do these method differ? Or are they the same? Which do I use???
3) One post says "After you unrevoke4, you can use your custom recovery image to flash a rooted 2.2 stock rom". I dont understand. A ROM is an image...so how can I use an image to flash another image?? makes no sense =\
4) Is "recovery" an app/tool that is already on the phone (or needs to be downloaded), and if so how do I access it? Or is it a ROM image?
5) After unrevoked is done, do I accept the OTA firmware update (i think it's the ugrade to Froyo update that keeps popping up)?
6) Which ROM needs to be installed? The zip that Unrevoked is going to install, or HTC Stock Froyo 3.26.651.6 [Rooted][Deodex'd], or both?
7) What is PRI and PRL and why are ppl so concerned about getting those updated? Will they get updated automatically once Frodo is installed?
8) Same deal with the Wimax and Radio updates. What do they do? Why do ppl want to retain them so badly, and if they are so important, why don't the updated ROMs or OTAs have them included?
9) What's the difference b/t a Nandroid backup and a Titanium backup? And which one should I do?
Please help! Thanks!
one does not simply walk into Mordor.
So I can identify with the OP. I don't know many of those same things, but I am slowly learning through reading these forums.........
However........that comment was quite amusing, also very accurate......... Ya that made my night
Sent from my PC36100 using XDA App
1) What is the best/most reliable way for me to update to 2.2? Can I use Unrevoked Forever to do so? Or do I have to use some manual method? Toast's method? ROM Manager?
Use Simpleroot to fully root. Then flash SteelH's 2.2 Stock Rooted ROM/
2) I read the steps for installing on the Unrevoked site, but I don't understand the terms it uses. It says to "flash from custom recovery". First of all, how do I access this custom recovery tool or whatever? Second, some ppl said they use a ROM Manager. Other sites say to "boot into recovery". Still, some instructions say boot into Clockwork....How do these method differ? Or are they the same? Which do I use???
Power + Volume Down while the phone is off boots your into the bootloader. You can then enter your custom recovery from there. Or you can use Rom Manager/Spare Parts to boot into recovery directly within your phone. Clockwork is a custom recovery; AmonRa is the other custom recovery. Use either one.
3) One post says "After you unrevoke4, you can use your custom recovery image to flash a rooted 2.2 stock rom". I dont understand. A ROM is an image...so how can I use an image to flash another image?? makes no sense =\
You need to install a custom recovery, ie AmonRa or Clockwork (an image) so you can flash a ROM (another image)
4) Is "recovery" an app/tool that is already on the phone (or needs to be downloaded), and if so how do I access it? Or is it a ROM image?
Recovery is already in your phone, but you need to flash a custom recovery after you root. Simpleroot will allow you to flash a custom recovery on the last step.
5) After unrevoked is done, do I accept the OTA firmware update (i think it's the ugrade to Froyo update that keeps popping up)?
Not relevant, when you are on 2.2, you won't be notified of OTA updates. After you root, NEVER accept any OTA. Wait for the updated rooted roms.
6) Which ROM needs to be installed? The zip that Unrevoked is going to install, or HTC Stock Froyo 3.26.651.6 [Rooted][Deodex'd], or both?
Don't use Unrevoked. Root using Simpleroot and flash your downloaded ROM afterwords.
7) What is PRI and PRL and why are ppl so concerned about getting those updated? Will they get updated automatically once Frodo is installed?
No one can really prove that an updated RPI/RPL affects your phone in positive ways. Your RPL will be updated. RPI will be 1.34 after Simpleroot, this forum just figured out how to get 1.40 RPI today (go read the dev forum)
8) Same deal with the Wimax and Radio updates. What do they do? Why do ppl want to retain them so badly, and if they are so important, why don't the updated ROMs or OTAs have them included?
Wimax and Radio updates improves your 4G/Radio/Data performance. They should be flashed after you flash your rom.
9) What's the difference b/t a Nandroid backup and a Titanium backup? And which one should I do?
Nandroid backup creates a complete image of your phone. Titanium backup only backs up your apps.
Speak friend and enter...
Speak friend and enter!
OK then, all the LOTR references aside, I was in your shoes not to long ago. You could have done a little more reading or googling (something like "how to root EVO"), as these forums usually contain a number of threads with titles something like "Moron-proof guide to....."
Anyway. Unrevoked seems to be considered a somewhat incomplete root according to most ROM threads (I don't know the details to speak intelligently on
the matter).
Here is what I did, and it worked well.
1) Get SimpleRoot. This will let you root your phone for real.
NOTE: I don't know if you need to get rid of unrevoked before this; maybe someone more knowledgeable can chime in on this one.
2) Step 2 of SimpleRoot is to flash recovery. There are two options; I chose RA. There are a few threads that talk about pros/cons of each.
For simplicity sake, I think of "recovery" as a program that lets you do lower lever system stuff, like flash files, do backups, etc. The general way to reach it is to hold VolDown while powering up you phone, then selecting "recovery".
Anyways, after you've flashed recovery, you'll be able to flash whatever ROM you want.
3)If you want stock 2.2 get THIS. Get the radios as well. Generally there are instructions with the ROMS, READ THEM.
You should have three zips. Put them on your sdcard. Then in recovery select flash from zip file (or something like that). Do that for all three with reboots in between.
You should now have the latest stock ROM and radios.
There are a ton of other ROMs out there. NO one will be able to tell you which one is the best, so don't ask.
Wireless Tether - the newest version is floating around here somewhere (pre7). It works well with the rooted stock 2.2
The PRL/PRI debate is still going on. You can read the million threads and see if you want to worry about it. I don't.
As far as backup goes, the more knowledgeable folks can speak to the details. A simple way of describing it is nand backup (from recovery) is like a ghost of your system, where as Titanium is more of an apps/settings kinda thing.
I strongly suggest reading the guide threads to gain more insight.
And, of course, I didn't come up with any of this stuff. If you find anyone's work helpful, then you should thank/donate to them.
EDIT: Hehe, looks like I was second in the helpful line.
That pretty much answers it all.
I can address #7.
Once Frodo is installed into mount doom he must cast the ring into the fiya.
Quickly though. For the creature gollum lays await in the shadows of every crevice left behind.
You must upgrade your puke ridden leggings and ingest some pain reducing ibuprofen for maximum connectivity with the force.
There I go switching epics again..
PLEEEASE STICKY!!!!!!!!
Then I could always find this thread in a hurry when I'm in a bad mood and need a pick me up.
This thread has brought great joy to my life. Expect me to bump it about once a week.
It's funny that I have no clue how to do this, because I full-rooted my EVO with the first firmware and never looked back. I've just been running custom recovery and custom roms ever since. I need to root a friends phone soon, so I guess I'll have to learn.
After much lurking and wiki reading I would like this stickied as well.
To get Frodo 2.2, you would have to write a novel, placing him in a setting similar to The Terminator. From there, create a back story on how his first version was inferior and lacking superior abilities, dubbing the need for a new version. After that have a fight scene of him going against his creator, thus needing to make him version 2.2. The non violent version. From there he would have the dramatic speech in a weird code of language.
Simple root, click click, RA, click. Power button volume down. Wipe, wipe. wipe. rooted rom zip, radio zip, reboot, power button volume down wimax zip, reboot.
After that Frodo will walk away into the sunset, in search of the future version of him, Frodo 3.0 - Fighting in the conquest of his arch nemesis, Apple Conner.
Quiksmage said:
one does not simply walk into Mordor.
Click to expand...
Click to collapse
Dammit Bilbo, you beat me to punch
Can I get frodo as well?will this give me wifis?
Sent from my HTC Evo using Tapatalk.

[Q] Okay, so I've got Permaroot and S=Off, now what?

So, I've read a lot about it, found a method I liked (used the visionary permroot from the Unlockr.com), and now I have successfully Permarooted and have S=Off on my MT4G.
Now what?
[Q. 1.]I know that seems dumb, but what is the FIRST thing I should do once I have root access? Should I set up the ADB through the Android SDK? Should I get CW3 to do a Nandroid backup? I know how to do those things, I just don't know which one I should do first.
[Q. 2.]Ultimately, I want to upgrade to custom ROM, preferably a Gingerbread port. Unfortunately, I've read that most of the ports have buggy wifi among other things, so here's another question, anyone know a good Stock mySense ROM with some extras like overclocking and such?
[Q. 3.] Although I'm very clear on what S=Off and Root access are, what they do, and why I want them, they steps beyond that are foggy. I'm not sure what the difference between a kernel and a ROM is or whether I need one or both to do what I want to do (see Q2). I also don't know/understand what flashing is/does. I'm not expecting anyone to explain all that in here (unless you want to), but could you point me to some resources where I can learn what those things are so I understand what the hell I'm doing?
corruptsmurf said:
So, I've read a lot about it, found a method I liked (used the visionary permroot from the Unlockr.com), and now I have successfully Permarooted and have S=Off on my MT4G.
Now what?
[Q. 1.]I know that seems dumb, but what is the FIRST thing I should do once I have root access? Should I set up the ADB through the Android SDK? Should I get CW3 to do a Nandroid backup? I know how to do those things, I just don't know which one I should do first.
[Q. 2.]Ultimately, I want to upgrade to custom ROM, preferably a Gingerbread port. Unfortunately, I've read that most of the ports have buggy wifi among other things, so here's another question, anyone know a good Stock mySense ROM with some extras like overclocking and such?
[Q. 3.] Although I'm very clear on what S=Off and Root access are, what they do, and why I want them, they steps beyond that are foggy. I'm not sure what the difference between a kernel and a ROM is or whether I need one or both to do what I want to do (see Q2). I also don't know/understand what flashing is/does. I'm not expecting anyone to explain all that in here (unless you want to), but could you point me to some resources where I can learn what those things are so I understand what the hell I'm doing?
Click to expand...
Click to collapse
1. I say flash a new recovery image (CWM 3.0.0.6) and make a full backup. I also copy my backups to my PC because it's happened to me before that the one on the sd card gets damaged and can't be restored from (aborts because of md5 checksum mismatch). I do recommend the android SDK and ADB because they can be quite handy. Also, while you're still on the stock kernel, you might consider doing the gfree stuff to unlock your SIM and get universal CID. You run it exactly the same way you did the root.sh in theunlockr.com method - easy as cake.
2. I don't know about any sense roms, so I'll let others suggest those. I honestly think you should drop Sense and go with CyanogenMod, but to each his own.
3. Try the XDA Wiki, link up at the top. I'll bet there's tons of stuff there that will make for great bedtime reading. Since you mentioned a few things specifically, I'll throw some stuff at you:
The ROM is all the system files that compose your phone's operating system. Flashing is the process of installing any sort of firmware image (a rom, a recovery image, etc). Basically, you're writing files to the system. As you probably know, this is usually done via CWM recovery. It can also be done through fastboot if you have the engineering bootloader and the android SDK.
The kernel is the central component of most operating systems. It is a bridge between applications and the actual data processing done at the hardware level. Every ROM has a kernel. When you flash a rom, the kernel files will be flashed with it. You can flash another kernel afterwards to replace the one already in the ROM, provided that it's compatible with the ROM.
jdkoren said:
1. I say flash a new recovery image (CWM 3.0.0.6) and make a full backup. I also copy my backups to my PC because it's happened to me before that the one on the sd card gets damaged and can't be restored from (aborts because of md5 checksum mismatch). I do recommend the android SDK and ADB because they can be quite handy. Also, while you're still on the stock kernel, you might consider doing the gfree stuff to unlock your SIM and get universal CID. You run it exactly the same way you did the root.sh in theunlockr.com method - easy as cake.
2. I don't know about any sense roms, so I'll let others suggest those. I honestly think you should drop Sense and go with CyanogenMod, but to each his own.
3. Try the XDA Wiki, link up at the top. I'll bet there's tons of stuff there that will make for great bedtime reading. Since you mentioned a few things specifically, I'll throw some stuff at you:
The ROM is all the system files that compose your phone's operating system. Flashing is the process of installing any sort of firmware image (a rom, a recovery image, etc). Basically, you're writing files to the system. As you probably know, this is usually done via CWM recovery. It can also be done through fastboot if you have the engineering bootloader and the android SDK.
The kernel is the central component of most operating systems. It is a bridge between applications and the actual data processing done at the hardware level. Every ROM has a kernel. When you flash a rom, the kernel files will be flashed with it. You can flash another kernel afterwards to replace the one already in the ROM, provided that it's compatible with the ROM.
Click to expand...
Click to collapse
Thanks for the info; yesterday I got my ADB working and today I'm going to use gfree to get radio S=Off, Super CID, and Unlocked SIM. After that, I'll probably do a backup, then get the engineering bootloader, then do another backup. After making copies of all pertinent files, I'll THINK about upgrading my kernel or ROM haha.

[Q] current rooting/2.3 instructions

As the thread title states, I'm looking for info on the steps to root my stock MT4g, and install the new ROM that's floating around. I'm pretty technically capable, but the info I've found looks slightly dated. When I was active in the iPhone jailbreak scene, using old directions could brick a phone pretty easy, or prevent future jailbreaking. I haven't kept up with this scene enough to be able to know what's dated and what isn't.
This is my current plan, please correct it if I'm missing anything or have it wrong.
(based on wiki.cyanogenmod.com/index.php?title=TMobile_myTouch_4G:_Full_Update_Guide)
I've got ADB going
I need a backup solution for app data right? What's my best option here?
Once backed up, I plan to install busybox, Superuser package & Temporary Root package via ADB
Use gfree to make that root permanent
Install ClockworkMod recovery
Reboot into recovery, and install faux123's ROM
Does that sound correct, and did I skip anything? Any input at all is welcome, I'd like to stand tall on the backs of giants.
There are two popular methods floating around
You can either use the Root.sh method [ Found Here ]
Or the ./gfree method [ Found here ]
Either method will work perfectly. I've used both and can say with confidence they work.
The Cyanogen method can be goofy at times. I've see alot of people say they cannot get it working for them. I'd rock one of the two above. You shouldn't have a problem either way.
Thanks a ton for the info, I'll go at it this evening. As far as backup process, I do the temporary root, use ASTRO to make a zip? Most of the data on my phone lives at google, but I'm wondering the best way to retain apps, or should I just make a list and reinstall from the store after flashing?
lars.oakland said:
Thanks a ton for the info, I'll go at it this evening. As far as backup process, I do the temporary root, use ASTRO to make a zip? Most of the data on my phone lives at google, but I'm wondering the best way to retain apps, or should I just make a list and reinstall from the store after flashing?
Click to expand...
Click to collapse
For backing up apps and data, use titanium backup. for backing up your whole phone, use the backup feature in clockworkmod recovery after you've flashed it via rom manager after permarooting.
lars.oakland said:
Thanks a ton for the info, I'll go at it this evening. As far as backup process, I do the temporary root, use ASTRO to make a zip? Most of the data on my phone lives at google, but I'm wondering the best way to retain apps, or should I just make a list and reinstall from the store after flashing?
Click to expand...
Click to collapse
The best way to back up your Data and Applications is like mentioned above is Titanium Backup. The free version will work well but i recommend the paid one.
as far as a snap shot of the entire ROM incase you want to go back to it. reboot into recovery > backup/restore > backup. And it will do the rest.
Well I made it halfway there, but didn't nail the whole thing. I've got permanent root access (yay) now, and was able to make backups via Titanium. I then rebooted the phone into "recovery" using the ROM Manager from Clockwork. First boot had a red exclamation mark, I unplugged the handset from the USB and tried a second time. After that, I was greeted with the Orange and black interface, and selected "restore to factory". I then started searching for the cache clearing, which changed verbage between 3.x and 4.x releases of Clockwork. After exploring the menus a little, the phone reboots itself from this screen. My blood-pressure goes up, and I worry my toy just became a b-word. Not all was lost though, and the phone happily booted into the stock t-mobile welcome wizard.
I still have superUser installed, and still have root (S=OFF I guess?). I install ROM Manager again, and do the "Flash ClockworkMod Recovery" (which now shows both current and latest recovery as ClockworkMod 3.0.2.4). When I choose Reboot into Recovery however, it reboots back to the MyTouch 4G logo screen (non-animated one), and hangs. After some reading I tried to force recovery boot via ADB, which produced the same result as the soft reset from ROM Manager. After that I tried doing it the manual way with holding the volume button, which launched me into what I believe is a stock recovery console (white with colored options, uses vol +/- and power to navigate). Choosing "recovery" from that screen *also* produces the white logo screen hang.
So my question now is, in it's current state; how can I get to the Clockwork recovery again? From there I bet installing the image will be easy street, but I believe I'm stuck for now.
Side-note: the phone functions fine on regular boots and pure vanilla mode; I just don't want to stop here when I'm pretty close to my 2.3 goal
Well good news and bad news. I was able to get Clockwork going by reverting it to 3.0.0.5 and just using that version. Was able to install ROMs, tested a few. Phone started freezing after/during installing packages. Started the clear cache/install ROM process, ran into this:
Code:
Flashing Kernal ...
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/download/virtuous_fusion-glacier-rom-v1.0.9.zip
(Status 7)
Installation aborted
http://forum.xda-developers.com/showthread.php?p=14389074
Totally stuck at boot screen, but able to get into Clockwork. All ROM zips off the sdcard produce this or an invalid zip error.
Other guy smight tell you what a status 7 might be, but with the flurry of flashing youre doing, you may have gotten some corruption on your sd
try formatting your sd card in the pc, or use another one so you dont have to back everything up on this one. put one rom zip on the root and see if that helps
also, i would make super sure you wiped/factory resetted every possible data/cache in CWM before flashing the zip
lastly, i would md5 test the download to make sure it matches the web page. Plus, after it's transferred to the cleanly-formetted sd, check it again either thru adb, or do the trans on the pc using an sdcard reader and check it once it's on the sdcard, then pop it into back your phone.
good luck
Thanks a ton for the uber fast reply. When I format on the PC, what format do I use, or is there a specific tool to properly format it for the phone?
When I'm wiping /data it's taking forever and I get the following message back:
Code:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log/last_log
E:Can't open /cache/recovery/log/last_log
Don't have an adapter at the office today for the sdcard, but I guess I can just grab a new one at lunch? All it would need is a fresh format then the .zip of the ROM in question at the root?
Looks like your partitions are corrupted. Flash PD15IMG to restore the phone to stock, and progress from there.
When you format the SD card, just format it regularly in the PC.
Jack_R1 said:
Looks like your partitions are corrupted. Flash PD15IMG to restore the phone to stock, and progress from there.
When you format the SD card, just format it regularly in the PC.
Click to expand...
Click to collapse
So I use the same PD15IMG.zip i did to start, flash it using Clockwork, then start the root > rom process over? I think that it currently tells me it can't find that zip anymore on the white screen pre console, is that expected? I just xfer it to the sdcard prior to fixing?
Yes, that's the right procedure. Move it to the card and start from scratch. Beware not to use the newer Panache/MT4G Gingerbread RUU, otherwise you'll be left with no way to root, or at least harder way.
Ok, so I didn't have a PD15IMG.zip to begin with, I see this thread:
http://forum.xda-developers.com/showthread.php?t=1059347
and that's proper that I'm flashing the radio itself for this process? Which of those images do I want to grab? I always like to double check when I read warnings that are pretty specific about bricking the device
No! You're flashing a stock recovery image called a pd15img.zip
The radio does not do a restore to stock, the reason you're confused is that in order to flash a radio for those who nmwish to do that, you rename it to the same name as the recovery zip, but it's really just a radio. It just happens to be the filename that the system looks for to restore. Look for the thread posted by either jjackson or football. That's the full image, just over 300 megabytes, or that neighborhood.
acsi007 said:
No! You're flashing a stock recovery image called a pd15img.zip
The radio does not do a restore to stock, the reason you're confused is that in order to flash a radio for those who nmwish to do that, you rename it to the same name as the recovery zip, but it's really just a radio. It just happens to be the filename that the system looks for to restore. Look for the thread posted by either jjackson or football. That's the full image, just over 300 megabytes, or that neighborhood.
Click to expand...
Click to collapse
Jesus, glad I asked before getting in there.
So I was going to offer you a beer sometime, I think I owe you a few rounds at this point...
Edit: this one right http://forum.xda-developers.com/showthread.php?t=924923 ?
Yup. Read the whole thread. Also look for football,s thread. There are a couple of mentions of undoing gfree first then doing the pd15img. I think jjackson tries to automate those two steps, and football thread just gives you a january-dated pd15img. I can't remember if you rooted gfree or not. Read read read. This is an important step but hundreds have gone back to stock this way without a hitch. That is if you have a good emmc, you have a better chance of avoiding problems...
acsi007 said:
Yup. Read the whole thread. Also look for football,s thread. There are a couple of mentions of undoing gfree first then doing the pd15img. I think jjackson tries to automate those two steps, and football thread just gives you a january-dated pd15img. I can't remember if you rooted gfree or not. Read read read. This is an important step but hundreds have gone back to stock this way without a hitch. That is if you have a good emmc, you have a better chance of avoiding problems...
Click to expand...
Click to collapse
I rooted gfree originally, and think I may be in the bad place
Fail-PU errors running the update from pd15img. Do I have any options at this point? I bought the phone from Wirefly.com, and since I can't get a recovery image going, I may be fuct here on a return eh?
looks like i'm moving to: http://forum.xda-developers.com/showthread.php?p=14487111#post14487111
Good luck Lars. Let us know that they did and if you had to pay.

Important/Urgent: Who has a STOCK Verizon tab 7.7 (SCH-i815)

I need help! I need a stock, unmodified recovery partition image.
Anyone here with a vzw tab who DOES NOT yet have CWM installed?.
PLEASE contact me.
Thanks!
electron73 said:
I need help! I need a stock, unmodified recovery partition image.
Anyone here with a vzw tab who DOES NOT yet have CWM installed?.
PLEASE contact me.
Thanks!
Click to expand...
Click to collapse
I have one that hasn't been moded but have no idea how to get you what you want. PM me if you know how to download and send to you and I'll do my best to help.
I'll check my laptop at home tonight. I believe I kept my heimdall backup before flashing cwm
Sent from my DROID BIONIC using Tapatalk 2
Just checked, mightve deleted it. Sorry man
aximtreo said:
I have one that hasn't been moded but have no idea how to get you what you want. PM me if you know how to download and send to you and I'll do my best to help.
Click to expand...
Click to collapse
Oh that would be awesome! Are you rooted? Let me find the commands in the meantime, I read somewhere it's a simple one command in terminal to extract the recovery partition into a file on sd card...
WHAT AN ORDEAL !!!!
But in the end: SUCCESS!
I managed to get my tab updated with the Verizon OTA update.
The problem is definitely CWM !!! A rude awakening is in store for everyone with the P6800 CWM installed, because it a) fails to verify the checksum of OTA files correctly on the i815, b) it thinks the tablet is a P6800, so the OTA file fails to run if it assert checks for "SCH-i815" hardware AND lastly c) modem updates don't work because the device /dev/cdma_update doesn't exist, so the modem.bin firmware_update call fails !!!
In short, I had to fumble the OTA file apart and do the update manually in two runs:
First file, kick the checksum, hardware check and modem update out, then manually run the ZIP through CWM. The zip subsequently (LUCKILY) updated the stock recovery and overwrote CWM with a new fresh stock recovery.
Second file had everything kicked out BUT the modem udpate and LTE patch, so with the STOCK recovery this file ran through just fine, updated the modem and then applied the LTE delta patch.
Phew!!!
Of course I had to manually restore root after the update, had backed up with voodoo, auto restore failed, so terminal and hacking it was...
Now I have the tab running on clean stock FD01, baseband and LTE FD01, rooted and stock recovery.
No more CWM, no more "hacking" with the ROM until some dev finally releases a "correct" CWM and at least ANY factory ODIN image is available to bring the tab back to stock if needed!!!
Kinda sick of the non-support for this tab. So much going on for the Galaxy Note and pretty much every other device. I'm starting to regret having bought this "special" Verizon version
Awesome find and great to know for whenever ics does come out. Could you please post the recovery img you got?
Sent from my DROID BIONIC using Tapatalk 2
OK after getting so many responses I decided to just post everything here in hopes that it will help others, too:
All files are here:
http://www.mywo.org:88/XDA/sch-i815/index.php
Step by step procedure to update the Verizon Tab from ..FA02 to ..FD01 build IF YOU ARE stuck with CWM installed on your tab and the original OTA fails with errors:
Upload the SCH-I815_FA02c_To_FD01.1.zip to the INTERNAL(!) SD card. This is important because CWM contains a bug that will only allow you to install from ZIPs stored on the INTERNAL SD storage.
Upload the SCH-I815_FA02c_To_FD01.2.zip to the EXTERNAL(!) (micro SD) card. This is important, because after the factory recovery is restored, it will correctly (and only) look for ZIPs on the EXTERNAL card.
Best way just copy both files to both locations
Fire up CWM and do "install from ZIP" and select SCH-I815_FA02c_To_FD01.1.zip
It should run (takes a while) and eventually tell you all is done. BOOT the tab. It should boot fine but in system it will show the new Android build FD01 but the baseband (radio) will still be the "old" one.
Now press and hold power and vol up again until you see the default Samsung recovery menu. Choose install from ZIP and select SCH-I815_FA02c_To_FD01.2.zip. This will now upgrade the baseband only. When done, reboot and enjoy being back on the "factory upgrade path" with the tab.
I hope someone more savvy than me can "fix" CWM to work properly with VZW tabs (accept the checksum, not fail the check for "SCH-i815" and provide the correct /dev file links for radio upgrades). Until then, I recommend just leaving the tab as-is and not tinkering with the ROM. Not that there is any custom ROM available anyway :-(
I also pulled the NEW factory recovery image FD01_recovery.img with the following command:
dd if=/dev/block/mmcblk0p6 of=/sdcard/FD01_recovery.img bs=4096
So in case anyone with a botched recovery wants to restore factory (Samsung 3e) recovery. This was actually the reason I had to go through all this... There is NO factory recovery image ANYWHERE to be found. I can't believe that I should be the first one ever to post one?? Anyway, hope it will help
I'm still quite new here, so I do really appreciate every click on that "thanks" button
P.S. for tinkerers and devs I also uploaded the original, untouched OTA file (0559c0e4e08e.update_SCH-I815_FA02c_To_FD01.bin) as it came from Samsung or Verizon or whatever and ended up in the /cache partition.
THANK YOU!
Electron,
You sir, are a BOSS! Thank you so very much for doing the work, and sharing it. You just made things one hell of a lot easier on me, and anyone else that follows.
Regards,
-Rob
Also want to say thanks. You rock, dude. I wouldn't have known how to revert **** on my own.
Also, I feel like we need a sticky or something for sch-i815 owners to go to for device specific stuffs, especially since there is little knowledge/info out for this device.
Sent from my Galaxy Nexus using xda premium
hmm i only ever installed ROM manager ... but i did root it ... problem is ... now i don't have a CWM recovery to flash the file ... any ideas?
phigmeta said:
hmm i only ever installed ROM manager ... but i did root it ... problem is ... now i don't have a CWM recovery to flash the file ... any ideas?
Click to expand...
Click to collapse
You're in luck! You don't need to go through the whole ordeal because you do NOT have CWM! You can just update the regular intended way. Go into settings, about phone and then click check for system updates. If it presents you the OTA update, just do it the regular way.
My complicated "hack" is only necessary if you DO HAVE CWM installed.
Im sorry I did not explain well what my issue is.
I do not have CWM installed, however i did delete a few appilcations using titanium backup. This causes updates to not take. I would really like to just take it back to factory and start over (this time with less stupidity on my part)
I of course would assume that once its at factory i can then install updates again.
Right now when i try i get the "!" droid sign and a reboot
phigmeta said:
Im sorry I did not explain well what my issue is.
I do not have CWM installed, however i did delete a few appilcations using titanium backup. This causes updates to not take. I would really like to just take it back to factory and start over (this time with less stupidity on my part)
I of course would assume that once its at factory i can then install updates again.
Right now when i try i get the "!" droid sign and a reboot
Click to expand...
Click to collapse
Hey
OK unless someone can tell us how to "make" an ODIN flashable ROM for you, here is what I would do (and please don't get scared because it sounds a bit convoluted).
First, you need to be rooted. This is obviously the case.
IMPORTANT since you don't have CWM installed yet, SAVE your factory restore.img before proceeding, this saves you a lot of hassle later!
Open the android terminal, type su (accept the prompt) and then type (or copy/paste)
dd if=/dev/block/mmcblk0p6 of=/mnt/sdcard/factory_recovery.img bs=4096
Check that you have a "factory_recovery.img" file on your sd card now it should be about 8M big.
Now you're safe to install CWM from the forum, look for the other thread(s) where this is being discussed and follow the instructions for the P6800 "international" version with 3G. CWM Thread here:
http://forum.xda-developers.com/showthread.php?t=1613638&highlight=cwm&page=3
Then (thanks to nicduim!) there is a full factory (rooted) CWM image floating around on the forums here:
http://forum.xda-developers.com/showthread.php?t=1613638&page=6
Which I used to restore my tab to "almost factory" with the missing bloat apps back in place.
I have a copy on my server here: http://ww.mywo.org:88/XDA/sch-i815/ it's the "2012-05-06.22.48.58.ZIP"
unzip that and put the contents on your INTERNAL SD card in the folder clockwordmod. So on your internal SD you should have /clockworkmod/2012-05-06.22.48.58 and inside there the files boot.img, recovery.img etc.
Use CWM recovery to restore this backup. If you never used CWM before. Press power button and volume up and hold both until you see the menu screen with text. You can go up/down with the volume buttons (go slow, it's very laggy) and with the power button you "select" an option. Select the "restore from backup" option and point it to the only folder being offered, the 2012-05-06.22.48.58.
The restore takes a while, then reboot the tab. Now you're back to stock! Last thing you need to do is get rid of CWM again because in the end it's still a bit buggy and will prevent the OTA update from running properly.
Since you luckily have a backup of the factory recovery in form of that factory_recovery.img file, just install and open terminal again, type su and then type (or copy)
dd if=/mnt/sdcard/factory_recovery.img of=/dev/block/mmcblk0p6 bs=4096
This overwrites CWM with your original Samsung Android recovery.
Now you just reboot as usual, connect to the internet and wait until the popup message shows up that a system update is ready, accept it and enjoy
If you don't want to wait for the automatic OTA, you can also stop before killing CWM and use my convoluted 2-step manual update which will get you to the exact same condition as the official OTA.
Hope all this makes sense
I was already on stock FD01 when I tried installing CWM for the P6800 that's floating around here somewhere. Odin said it was a success, but it looks like it didn't take. I've done it a few times, but still ended up w/ the stock recovery. However, after reading through your thread, I do not see a /dev/cdma_update in my I815 either. Is it possible that my attempt to install CWM (although unsuccessful) wiped out this file, among others?
Right now, I'm still at stock FD01 (rooted) and everything seems to be working. When I tried doing an OTA update, it just tells me that I have the latest update and no newer update is available.
One other thing, if I have to, I only have the stock recovery right now since CWM didn't take, can I simply flash both zip's using the Samsung stock recovery to put everything back in stock?
SCH-I815_FA02c_To_FD01.1.zip
SCH-I815_FA02c_To_FD01.2.zip
AlpineMan said:
I was already on stock FD01 when I tried installing CWM for the P6800 that's floating around here somewhere. Odin said it was a success, but it looks like it didn't take. I've done it a few times, but still ended up w/ the stock recovery. However, after reading through your thread, I do not see a /dev/cdma_update in my I815 either. Is it possible that my attempt to install CWM (although unsuccessful) wiped out this file, among others?
Right now, I'm still at stock FD01 (rooted) and everything seems to be working. When I tried doing an OTA update, it just tells me that I have the latest update and no newer update is available.
One other thing, if I have to, I only have the stock recovery right now since CWM didn't take, can I simply flash both zip's using the Samsung stock recovery to put everything back in stock?
SCH-I815_FA02c_To_FD01.1.zip
SCH-I815_FA02c_To_FD01.2.zip
Click to expand...
Click to collapse
Oh wait, so you are saying that in "About device" your Android is 3.2
Baseband i815.04 V.FD01 I815FD01
and your Build number is already at HTJ85B.I815FD01.SCH-I815.I815FD01 ?
That would mean you are already updated. In this case, it should be pretty easy to fix your problem. Which apps did you delete with Titanium? I can back them up from my system and make them available for you. All you'd need to do is drop the backup files into your Titanium backups folder and then fire up titanium and restore them!
The /dev/cdma_update node is only required WITHIN CWM recovery, so that is nothing for you to worry about. The zip files above won't help you because they are incremental updates requiring your system to be at FA02, not FD01 !
Yes... I'm already in the latest update. I already backed up the bloatware using Titanium Backup before uninstalling. So I just need to restore them back in order to receive and apply OTA updates in the future?
Sent from my SPH-D710 using Xparent ICS Blue Tapatalk 2
Please Help
Hi. I'm rooted and removed all sorts of bloatware with Titanium. I did this a long time ago and did not back anything up because I'm used to running hardware with custom ROMs available, and not relying on OTA updates.
Since there aren't any custom ROMs for the i815, I'd like to get ready for the upcoming ICS update. To do so, I want to get FD01 loaded onto my device, but I can't update because I've apparently removed too much of the required bloatware.
Does anyone know WHAT pieces of bloatware I'd need to reinstall in order for the OTA update to apply? I'd assume I can restore them and then apply the update and re-root.
If anyone can help pinpoint what missing APKs might help, I'll give them a shot. And, to the extent I figure anything out, I'll repost here in the hopes that it helps someone else.
electron,
Your instructions worked ... thank you so much
@jkrell... the failed attempt at installing the update should return an error message(s). You just have to read through them until you find the culprit(s). Apparently I uninstalled a few odexed files that were needed. I couldn't update until i hunted them down and restored them.
I guess we all jumped at the opportunity to install the cwm recovery image, that we didn't even think about cmda updates....ooops. So far i had to do a complete factory restore after the update. I was getting soft bricked to the point where I had no choice. Good thing I sent all titanium backups to actual sd card, i was able to salvage 97% f my data..... with the exception of a few downloads i forgot to move.
Gamecih doesn't work anymore (either version). No more automative data hacks I'm not sure what's going on. I uninstalled adfree..used titanium backup to uninstall both versions and reinstalled both several times. Oh well.
It really sucks not having nandroid backups but it's not worth the trouble of having to do this everytime an OTA modem update gets pushed to my tab. Needless to say, I won't be odining the cwm based recovery image again.
I'm with the O.P. I wish i hadn't wasted my money on this tab. No true cwm for this tab, so no dev will ever waste thier time with this tab. The sch i815 will soon be forgotten about and some other tablet will be all the hype before summer ends....that's just how it is. 21 months left on my contract.... [email protected]#k my life. Lol
Thanks Smitty.
When I try to update, I just see the "!" logo and then the device reboots. Is there a log file somewhere I can look at to see what the errors are?
I hear ya on the gloom and doom, but this device has only been out for just over 3 months now. I'd expect a recovery and some custom ROMs to come eventually. I doubt I'll go the custom ROM route unless CyanogenMod is supported, because I have no complaints about the tablet's performance thus far. It's speedy, smooth and the battery lasts forever.
In my book, this is a great tablet and I'm satisfied with the purchase.

Categories

Resources