Related
Hey people!
I read a few posts dealing with same error below, but the descriptions of the problem was a bit different so I wanted to be sure.
I'm quite new to this so bear with me. I got an EVO last month (dec 24) and have since wanted to root. I've been reading up on it, and finally decided to root using Unrevoked earlier today. The root process worked perfectly, so I proceeded to create a nand backup and flashed the CM6 Mod using Clockworkmod rom manager app.
I was a bit excited played around with it a bit, and decided to flash the Miui ROM. I placed it on the root of my SD card, and this is where I lost control. I tried to flash using the ROM manager and it never completed, citing an error. I tried to reboot phone but I didnt get past the white HTC EVO 4G screen. I entered bootloader, and I tried to restore my original Nand backup but I keep getting this error, "Error while flashing boot image."
What would be the appropriate (or least risky) course of action? I can mount my SD card on computer through ClockworkMod recovery, should I try placing stock ROM zip or cm6 zip file and try to flash?
I do not think this is a battery issue, I had my phone plugged to charger while trying to flash nand.
I appreciate the help, I know I probably sound like a noob, but for almost a month I was reading, learning and trying to be careful (obviously not enough), once I rooted I got overzealous.
MOD Version is 2.5.0.1
Thanks for all your help,
DJ
I flashed a the recovery, after a few issues...my phone is back up and running...DISREGARD. Sorry for the noob ?.
Hi guys, I've had a Bell-branded Desire Z (on AT&T's network) for some time now, but I've never gotten around to rooting / flashing a different ROM on it. Since I have some free time this weekend, I figure I'll finally tackle it. Have a few general questions though:
1) Is the method listed in the guide: http://forum.xda-developers.com/showthread.php?t=928160 still the best method for rooting a desire Z? I've heard bad things about visionary, but every rooting method I've read seem to involve it in some way.
2) with S-OFF, am I free to flash any Desire Z / G2 ROM? or will only certain ROMs work with a Bell Desire Z? Any specific recommendation on ROMs? I'm planning on trying out CM7, then going from there
3) What is the best method for backing up my current image + a few other things (mostly contacts and SMS)? Titaniumbackup gets thrown around a lot, but I only have a handful of apps, and really would rather just redownload them then go through the trouble of backing them up
Thanks
http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting
that is going to be your safest way to root your vision. eventhough this is longer, there is a lot less chance of bricking your phone. the one you listed is very simple to do, but runs a high risk of turning your phone into a paper weight.
when you do have your phone completely s off, you now have every right to flash kernels, roms, and other things. you can find all of the things i just listed over in the development forum on the g2/desire z. download rom manager from the market. that allows you to back up your current rom, flash the latest recovery and so on. it just allows you to not have to manually install everything. it has the popular g2 roms under the "download rom section".
in terms of backing up everything, there are a few different options. every contact to save is linked to your gmail account, so whatever rom you flash and load youll always have those contacts coming with you. thats the beauty of google and gmail on a android device! but with rom manager, you can back up your current rom and image with that app and save it to your sd card. BEFORE YOU FLASH ANY ROM, OR BEGIN TO START TRYING OUT ROMS, BACK UP YOUR STOCK ROM. whenever i got my g2 when it first came out, i made a nandroid backup of my stock rom and i still have it. when i originally backed it up, i just named it "stock" and havent messed with it since. i just know that i have the stock image(it helps me sleep at night). jk, heh. for your text messages and stuff, download sms backup from the market and you can back everything up through that. all of the apps that you download, including the paid ones of course, travel with you between roms, etc.
i hope i helped ya out, and i wish you luck. if you have any other questions, just shoot me a private message!
Thanks for that;
I actually went ahead and used that method in the guide since upon further research, it seems that visonary was only causing issues when it was use for perm root; temp root, which is what that method uses visionary for seems to work fine.
So did that, reboot into the bootloader, confirmed that I had S-OFF on the first line.
Installed ROM manager from the market
Flashed Clockwork recovery
Booted into recovery and did a system backup to SD card
Rebooted and decided to download the Virtuous ROM from ROM manager
Told it to reboot into recovery and flash that image, wiping all data and settings
Got stuck on an bootup loop (HTC logo + start up sound -> black screen -> HTC logo + startup sound ad infinitum)
Rebooted into recovery, and did a restore from the backup (whew)
Phone seems to be working fine now
Now I'm trying to figure out what went wrong... any ideas?
K, I redownloaded virtuous from XDA, checked the MD5, and tried to flash it again.
Same problem, infinite loop on startup screen.
Do i need to flash the engineering hboot? I was under the impression that that wasn't necessary for using custom ROMs.
Still can't figure out what's wrong.
did you debrand? http://forum.xda-developers.com/showthread.php?t=835777
Have you tried flashing through CWM directly? I really don't like ROM Manager for flashing new ROMs and seems to oversimplify the process to allow green users to get on the flashing wagon.
I would boot into CWM (camera + power i think) and do a complete wipe + flash from in there. I have never had an issue with doing things directly from recovery and I have a Bell DZ as well. It's long since lost it's blue and white colours, but that was it's origin
Have fun!
Im new to this stuff here, and i DO want to learn about it as this stuff is very interesting to me! Technology is something i learn very quickly if im directed in the correct direction
The question i have here is about my Desire Z ( Bell Cannada ).
A few months ago we received a OTA update. So its currently running on Android 2.2.1 : Build - 1.84.666.2 CL322105, and its SUPER slow! Is it still possible to root this version?
I want to install the Gingerbread version on my phone, but i cant find instructions to root this OS version to be able to do so.
Or should i wait till the Official gingerbread Os to come out for our phones?
Ive been searching every where's for this info and everything i find is all back dated to last yr and nothing up-to-date after the OTA.
I hope this question is not TOO n00bish as i tried to search every where for it, and ether i could not find it or i did not enter the correct word search to get a result i needed.
Thanks in advance!
Andrew
Edit: NVM my question here.... i have finally found an update post within the wiki ( April 1 2011 )
Sorry for a useless post!
Thank you all for your efforts in posting in this forum! Very informative!
Athrun88 said:
Have you tried flashing through CWM directly? I really don't like ROM Manager for flashing new ROMs and seems to oversimplify the process to allow green users to get on the flashing wagon.
I would boot into CWM (camera + power i think) and do a complete wipe + flash from in there. I have never had an issue with doing things directly from recovery and I have a Bell DZ as well. It's long since lost it's blue and white colours, but that was it's origin
Have fun!
Click to expand...
Click to collapse
heh. that actually worked. Flashed directly from CWM recovery and it booted up with no issues.
Guess I know not to flash from ROM manager anymore
Thanks.
deaththeorist said:
did you debrand? http://forum.xda-developers.com/showthread.php?t=835777
Click to expand...
Click to collapse
You do not need to debrand to flash custom ROMs to the Bell Canada Desire Z.
makken85 said:
heh. that actually worked. Flashed directly from CWM recovery and it booted up with no issues.
Guess I know not to flash from ROM manager anymore
Thanks.
Click to expand...
Click to collapse
Interesting, I've flashed many ROMs from ROM Manager on my Bell Canada DZ, and never had an issue. That said, flashing from recovery is really not any harder, so if it works, it works.
redpoint73 said:
Interesting, I've flashed many ROMs from ROM Manager on my Bell Canada DZ, and never had an issue. That said, flashing from recovery is really not any harder, so if it works, it works.
Click to expand...
Click to collapse
Yeah, I assumed that flashing from ROM manager just meant that it rebooted to recovery and flashed it from there. I guess there is a difference.
Either way, been playing with Virtuous 1.0.2 for a few days now, really like this ROM, but I'm itching to try out something different now. Man, I can see this is going to develop into a time consuming hobby.
Plus, I'm going to need a bigger SD card to store all of these ROMs + backup =X
Oh, another noob question; I've come across a few zip files that included a system folder and an META-INF folder. How exactly do I install these?
G2 only works with at&t
alright here it is my t-mobile G2 won't connect to the t-mobile network at all, I've went through 3 SIM cards because this thing use to kill the SIM card from working on other t-mobile phones and it works perfectly fine on at&t network. so I've unlocked so it will work on at&t just to see if it would work. so i gave p and bought a MT 4G, but i still want to know if the G2 is fixable because I'm just about ready to throw in the towel this is what I've tried to resolve the problem called t-mobile they ended up saying just return the phone but i can't since i didn't buy it from them. Called them again got the unlock code. I've flashed the radio a few times. I've also just got the leaked 2.3.3 update and nothing has worked. It find t-mobile network but says your SIM card isn't allowed to connect to this network then after trying again it says unable to connect to network please try again later.
Just so frustrating i don't know what to do just about to say forget it. this thread is my last resort.
also i still have S-OFF
i used this method on my G2 just yesterday and put on CM7.0.3. the only issues i came across were because i restored everything (should have just done apps and app data) using Titanium, which put me in a boot loop. I'm dumb, so i did it twice before i figured out what was the problem. the thread has a comment about how Visionary is dangerous, but the OP responded that since it is only used to gain temp root, there should be no problems.
Hello everyone.
I enjoyed the noob video and also look forward to being pasted no doubt.
I have a wildfire running 2.2 android which I understand means I am running the latest firmware, which I also understand is going to make it difficult for me to root easily.
Never the less not being one to be beaten I have tried with EVO3, which no matter what I tried would not work, constantly asking if my firmware was too new. I even wiped it but no luck.
So I struck upon revolutionary, which yes I understand is beta.
This is perhaps where my lack of understanding comes in. Would I be right in thinking that custom roms require a specificly rooted device?
The thing is I have apparently been successfull with revolutionary. I can boot into it and I was able to instaly cryongena rom which worked OK until I installed google apps where by it constantaly showed the spinning blue arrow, round and round, rebooting and rebooting.
Thing is all other roms I have tried, everyone, has failed, with either script being old 'error 6' etc etc.
I found I needed a different kind of rom, which a few were offering however these also failed with error 6 which apparent was something to do with not being pure unix or something.
Sorry I am not up on the language, but I think I have tried all the popular ones, puzzle etc and none will install.
When I start up with the volume button pressed it shows the screen then says something about failing to load image, but goes away to quick to read pc4diag.img or something.
Is it possible I have not loaded revolutionary correctly, and have I gained 'root'
Thanks for reading, and please feel free to tear me a new one.
- Yes, I am sure you have Revolutionary installed correctly. You got a bootloop while installing GApps, in which case I would recommend performing a full wipe in Clockworkmod and try to install again. (Install the CM ROM first, then the GAPps Zip. Also, I hope you are using a filename called gapps-gb-2011xxxx.zip)
- If you want to install other ROMs, Sense and Android 2.2.1 ROMs require Clockworkmod 2.x. Attempting to flash them in Clockworkmod 3.x/4.x will give you the "Scripting not supported" error. The workaround to this is to download this attachment:
http://forum.xda-developers.com/attachment.php?attachmentid=662193&d=1311319218
Flash this in your new Clockworkmod Version, which will give you temporary 2.5, then proceed as normal.
- When you boot into the HBoot Mode, it will automatically perform a search for the files PC49IMG.diag and .nbh. It's normal, and theres nothing to worry about. After the search is over, and, it has not found the files, you can navigate properly again.
Oh, and I think you are being too paranoid about the video and everyone here trying to tear you a new one.
Good Luck
Thanks very much for your answer.
Honestly I spent 2 hours on google last night trying to get my head around it.
To be honest all I want is a quick phone, and I am not getting that with stock software on my wildfire, I get very frustrated when trying to scroll but it reads it as me tapping an app icon, and there are loads of them I don't want in here, footsteps and tweets and the likes, I am simply not interested and neither am I allowed to remove them. The cynogenmod looked amazing, but I can see even more processor intensive than the stock software.
I will have a look at what you have suggested and thanks for your help!
In that case, I think you might want to stick with the Stock ROM, and, get an app like 'Root Uninstaller' or 'Titanium Backup' which allows you to uninstall (Or, to be more correct - 'freeze') any apps you wish - Including System Apps.
Not trying to advertise Cyanogenmod here, since I understand ROM preference is a personal thing, but, I would recommend giving it one more try, after a full wipe. Also, go with the latest nightlies rather than the Stables. I have been using it since it was released back in January, and, honestly, I am never going back to Stock / Sense based ROMs.
Don't get me wrong it looks awesome. But the boot up time was just shy of 4 minutes (although I now understand it may have been because of first boot) and two attempts at install failed.
I shall look at how to fully wipe, but to be honest, being very new to hacking my phone I am quite happy having the back up there to revert too.
Well I tried to install anything but nothing works so I shall revert to my original back up and see about these tools for removing unwanted apps.
Thanks for the help, but something is not right. All roms either get as far as the twinkly noise on the HTC screen then do it again and again, and cynogen gets to the rotating arrow, then eventually an android zips across the screen and back to the arrow
Well I don't think I have root on this device. I tried to install busybox and titanium and both tell me my phone is not rooted.
Sigh.
If you are on the Stock ROM, you will have to flash this additionally:
http://bit.ly/su2361ef
This will install Superuser, which is what will give you "root". If you are on Custom ROMs, flashing this additional file is not required, since, they include the Superuser Binary already,. So, flash that, and then try installing Busybox / Ti Backup. (make sure you get a "superuser" icon in your app drawer after flashing that zip)
EDIT:
- Are you on Clockworkmod 3.0.0.6 incidentally? That version has caused bootloops for many users when installing ROM's.
- First boot time is extremely long (Upto 7-8 mins), and its normal.
Hello thanks for the info.
I am not confident I know what mod I am on, I just went to the revolutionary website and downloaded the latest beta.
When you say it can take 7-8mins to load up would this include the boot loops though? Thats all I get on all of them
I shall install the super user bit see if that helps.
No, not including bootloops. BTW, I am referring to the Clockworkmod Version, not Revolutionary,
When you enter the Recovery to flash something, at the bottom, you will "Clockworkmod Version x.x.x.x". It is that version I was asking.
Sadly I am not getting anywhere here, every single rom just goes round in circles in one way or another.
The version say revolutionary CWM v4.0.1.4
I was unable to get the standard revoked installed as I am runnning the latest android firmware and it just kept failing.
Something I am getting rather used to!
I cannot see a clockwork mod number anywhere, although it must be there as I have clockwork folder on the SD card.
Sorry, I am being a muppet here.
Hey folks,
Thanks for taking the time to read/assist. I don't typically do these kinds of posts and am at my wit's end!
Phone's Previous Setup - MIUI Gingerbread, Rooted (but with S-ON after the fact).
What happened:
My HTC Incredible finally got to the point of being practically unuseable with laggy behavior and random restarts and the like, so I decided to complete a reset to factory settings or wipe.
I completed my backups using Titanium (apps) and ClockworkMod Recovery (full backup). After this, I went ahead and opened up Settings and directed the phone to complete a Reset to Factory Settings. It ran through the process, rebooted, and came up jelly. While no custom apps were installed (expected), my folder settings on my main home page were saved, along with some previous text messages. I was pleasantly surprised.
From here, I wished to wipe the SD Card so as to make sure it was clean of any residual folders/files that might cause conflict down the road (based on advice from others). So, headed to the SD card part of the settings. Had to unmount the SD card to format, proceeded to do so.
Here's where things went wonky: Despite receiving a confirmation that the SD card format had proceeded, nothing else ever happened. I attempted to mount the card again w/o luck (kept getting a msg that it was now unmounted). Eventually, I decided to go ahead and restart the phone and see if that helps. Big mistake.
From this point forward, the phone refuses to fully start up into any Android ROM. Initially, it hung on the white HTC Incredible splash screen (yes, even w/ giving it an hour+ of time). I tried wiping and reflashing different ROMS over the period of the day yesterday to no avail.
Doing a full recovery via ClockworkMod (from my backup that I made before and copied back onto the SD card via USB) leaves me stuck on the HTC Incredible white splash screen.
MIUI - 2.2.10
Hangs on white splash screen
No go w/ or w/o SD card installed
MIUI - 2.2.17
Loads past white and MIUI splash screens
Instead of loading into Android homescreen, immediately loads up "Encryption" error and directs to "reset phone."
Repeated restart and attempts of resetting phone don't work
No go w/ or w/o SD card installed.
MIUI - 1.12.9
Hangs on white splash screen.
No go w/ or w/o SD card installed.
CM - 7.1.0
Hangs/loops on CM splash screen.
No go w/ or w/o SD card installed.
CM - 6.1.0
Hangs/loops on CM splash screen.
No go w/ or w/o SD card installed.
I looked into HBOOT options, getting PB31IMG.ZIP and PG86IMG.ZIP.img thinking maybe I could try reverting to stock at a friend's suggestion. HBOOT sees the files and "checks" them, even briefly showing a small vertical blue loading bar at the top-right corner, but never attempts to run/update them as I am lead to expect from all the instructions/encounters I've found on the net suggest. The screen info flashes by so quickly, I can barely read it, but I confirmed that it said "checking" and not updating or such. x.x
I considered trying to flash an updated copy of ClockworkMod Recovery, but I cannot do that w/o being able to load up the phone into Android.
I cannot run anything desktop-side, like ADB, as they all require the phone started up and put into USB-debugging mode.
I've looked into and tried all this and more, but nothing seems to be working.
My next idea is to try to forcibly downgrade the phone. Reasoning being that I read that the HBOOT will not try to update if it senses that the ROM is newer than its default settings(?). So, I need a good choice of "old" ROM that I can attempt to install via the HBOOT or CWM Recovery, and verify I have the correct files for HBOOT to try updating/running.
Again, this is a speculative attempt, but I'm willing to try whatever might work! Otherwise, I've got a fancy brick and my well-being on the line w/ no $$ to replace the phone. x.x
Thanks again for reading and hopefully offering some wonderful assistance! Sorry it's so long!
Feel free to ask Qs if you need clarification on stuff.
wigmuke said:
Hey folks,
Thanks for taking the time to read/assist. I don't typically do these kinds of posts and am at my wit's end!
Phone's Previous Setup - MIUI Gingerbread, Rooted (but with S-ON after the fact).
What happened:
My HTC Incredible finally got to the point of being practically unuseable with laggy behavior and random restarts and the like, so I decided to complete a reset to factory settings or wipe.
I completed my backups using Titanium (apps) and ClockworkMod Recovery (full backup). After this, I went ahead and opened up Settings and directed the phone to complete a Reset to Factory Settings. It ran through the process, rebooted, and came up jelly. While no custom apps were installed (expected), my folder settings on my main home page were saved, along with some previous text messages. I was pleasantly surprised.
From here, I wished to wipe the SD Card so as to make sure it was clean of any residual folders/files that might cause conflict down the road (based on advice from others). So, headed to the SD card part of the settings. Had to unmount the SD card to format, proceeded to do so.
Here's where things went wonky: Despite receiving a confirmation that the SD card format had proceeded, nothing else ever happened. I attempted to mount the card again w/o luck (kept getting a msg that it was now unmounted). Eventually, I decided to go ahead and restart the phone and see if that helps. Big mistake.
From this point forward, the phone refuses to fully start up into any Android ROM. Initially, it hung on the white HTC Incredible splash screen (yes, even w/ giving it an hour+ of time). I tried wiping and reflashing different ROMS over the period of the day yesterday to no avail.
Doing a full recovery via ClockworkMod (from my backup that I made before and copied back onto the SD card via USB) leaves me stuck on the HTC Incredible white splash screen.
MIUI - 2.2.10
Hangs on white splash screen
No go w/ or w/o SD card installed
MIUI - 2.2.17
Loads past white and MIUI splash screens
Instead of loading into Android homescreen, immediately loads up "Encryption" error and directs to "reset phone."
Repeated restart and attempts of resetting phone don't work
No go w/ or w/o SD card installed.
MIUI - 1.12.9
Hangs on white splash screen.
No go w/ or w/o SD card installed.
CM - 7.1.0
Hangs/loops on CM splash screen.
No go w/ or w/o SD card installed.
CM - 6.1.0
Hangs/loops on CM splash screen.
No go w/ or w/o SD card installed.
I looked into HBOOT options, getting PB31IMG.ZIP and PG86IMG.ZIP.img thinking maybe I could try reverting to stock at a friend's suggestion. HBOOT sees the files and "checks" them, even briefly showing a small vertical blue loading bar at the top-right corner, but never attempts to run/update them as I am lead to expect from all the instructions/encounters I've found on the net suggest. The screen info flashes by so quickly, I can barely read it, but I confirmed that it said "checking" and not updating or such. x.x
I considered trying to flash an updated copy of ClockworkMod Recovery, but I cannot do that w/o being able to load up the phone into Android.
I cannot run anything desktop-side, like ADB, as they all require the phone started up and put into USB-debugging mode.
I've looked into and tried all this and more, but nothing seems to be working.
My next idea is to try to forcibly downgrade the phone. Reasoning being that I read that the HBOOT will not try to update if it senses that the ROM is newer than its default settings(?). So, I need a good choice of "old" ROM that I can attempt to install via the HBOOT or CWM Recovery, and verify I have the correct files for HBOOT to try updating/running.
Again, this is a speculative attempt, but I'm willing to try whatever might work! Otherwise, I've got a fancy brick and my well-being on the line w/ no $$ to replace it. x.x
Thanks again for reading and hopefully offering some wonderful assistance! Sorry it's so long!
Feel free to ask Qs if you need clarification on stuff.
Click to expand...
Click to collapse
You need to gain s-off again before flashing with clockwork. How come you turned it back on?
"In a nutshell, S-OFF means that the NAND portion of the device is unlocked and can be written to. The default setting for HTC’s devices is S-ON, which means that neither can you access certain areas of the system nor can you guarantee a permanent root. Furthermore, signature check for firmware images is also ensured by the S-ON flag."
edit:
gain s=off boot into CMW wipe data, and factory reset. Flash a new rom of your choice and then boot. should get you back to a working phone.
synisterwolf said:
You need to gain s-off again before flashing with clockwork. How come you turned it back on?
"In a nutshell, S-OFF means that the NAND portion of the device is unlocked and can be written to. The default setting for HTC’s devices is S-ON, which means that neither can you access certain areas of the system nor can you guarantee a permanent root. Furthermore, signature check for firmware images is also ensured by the S-ON flag."
edit:
gain s=off boot into CMW wipe data, and factory reset. Flash a new rom of your choice and then boot. should get you back to a working phone.
Click to expand...
Click to collapse
The first time my phone was rooted/flashed, my bf did it for me. He used Unrevoked to root it and install CWM Recovery (v2.5.1.2 presently). I recall conversation being that having S-On would be better security with regards to the cell carrier (e.g., good to leave on, bad if off as they can see you rooted). So I agreed to having it put back to S-On, which I understood he then took care of.
Fast-forward a year and he now tells me he didn't actually end up running the other Unrevoked (Forever) tool to put S-On back in place, but that it simply *was*, so he left it that way. o.o;
Keep in mind, I've flashed 3 different ROMs since he originally rooted and flashed, w/o issues.
I pulled up everything to try re-rooting it again (to gain S-Off), but the instructions required having the phone loaded up and in debugging mode, which I cannot do as I cannot start up the phone past recovery in the first place.
Did I miss something that allows it via recovery? Going to check again in the meantime.
wigmuke said:
The first time my phone was rooted/flashed, my bf did it for me. He used Unrevoked to root it and install CWM Recovery (v2.5.1.2 presently). I recall conversation being that having S-On would be better security with regards to the cell carrier (e.g., good to leave on, bad if off as they can see you rooted). So I agreed to having it put back to S-On, which I understood he then took care of.
Fast-forward a year and he now tells me he didn't actually end up running the other Unrevoked (Forever) tool to put S-On back in place, but that it simply *was*, so he left it that way. o.o;
Keep in mind, I've flashed 3 different ROMs since he originally rooted and flashed, w/o issues.
I pulled up everything to try re-rooting it again (to gain S-Off), but the instructions required having the phone loaded up and in debugging mode, which I cannot do as I cannot start up the phone past recovery in the first place.
Did I miss something that allows it via recovery? Going to check again in the meantime.
Click to expand...
Click to collapse
actually its better to keep it s=off so this type of situation wont happen. Your carrier cant see your hboot from my understanding on how this phone works. They dont care if you have root or not, unless you are trying to exchange the phone for another one from them or for insurance reasons. With root you only void your warranty on the phone and not your contract or anything to do with VZW. S=off is just a NAND lock, meaning you cant add your own custom recover to the phone, and you are limited to builds that come from VZW themselves (ie the security signature check).
If you ever want to take the phone back to them because its defective or call insurance then you need to remove root and S=on. but thats the only time you need to toggle the NAND lock.
ok so you will need to ruu to stock, downgrade then gain s=off over again:
for the ruu for GB:
http://forum.xda-developers.com/showthread.php?t=1227279
a guide to do this all after you ruu:
http://forum.xda-developers.com/showthread.php?t=1306400
OMG I may've gotten it!
So I decided to give things another go with attempting to revert to stock again, as at this point, nothing is going to work other than via HBOOT.
I completed another reformat of the SD Card (Fat32) to be on the overcautious side and copied over ONLY the PB32IMG.zip file and restarted into HBOOT.
(Ah.. new user, so not allowed to post the link of where I got it.)
This time, much like before, it scanned, found the file, and did a parsing/loading. However, THIS TIME it actually prompted me to update! I chose yes (Vol+) and let it do its thing.
At this time, I am happy to announce that it actually is back up stock!
Wooohoo! Now to get it back to how I like it again. XD
If nothing else, hope this information helps someone else later on.
wigmuke said:
OMG I may've gotten it!
So I decided to give things another go with attempting to revert to stock again, as at this point, nothing is going to work other than via HBOOT.
I completed another reformat of the SD Card (Fat32) to be on the overcautious side and copied over ONLY the PB32IMG.zip file and restarted into HBOOT.
(Ah.. new user, so not allowed to post the link of where I got it.)
This time, much like before, it scanned, found the file, and did a parsing/loading. However, THIS TIME it actually prompted me to update! I chose yes (Vol+) and let it do its thing.
At this time, I am happy to announce that it actually is back up stock!
Wooohoo! Now to get it back to how I like it again. XD
If nothing else, hope this information helps someone else later on.
Click to expand...
Click to collapse
You might have lost root if you did the ruu from hboot. to check download the app "super user" from market that will tell you if you still have root or not.
Alright, now that I'm back to stock and runnin' smoothly, I need to figure out what route to take for rooting and flashing. Everyone talks about Unrevoked3, but I've heard there're other newer tools, too.
What would you recommend?
....also, sorry for the weird delay/disjointed/incomplete responses. I keep forgetting that XDA severely limits my posting capabilities. I wanted to say super thanks wolf, for all your help and sticking with me! Your input is appreciated. And yes, I'm pretty sure I lost all root, etc. It is back to "out-of-the-box" stock as far as I can tell.
wigmuke said:
Alright, now that I'm back to stock and runnin' smoothly, I need to figure out what route to take for rooting and flashing. Everyone talks about Unrevoked3, but I've heard there're other newer tools, too.
What would you all recommend?
Click to expand...
Click to collapse
unrevoked3 is the easiest way. but you will need to downgrade to android 2.2 for the security exploit.
http://forum.xda-developers.com/showthread.php?t=1306400
Edit: fixed link
---------- Post added at 10:44 AM ---------- Previous post was at 10:35 AM ----------
wigmuke said:
....also, sorry for the weird delay/disjointed/incomplete responses. I keep forgetting that XDA severely limits my posting capabilities. I wanted to say super thanks wolf, for all your help and sticking with me! Your input is appreciated. And yes, I'm pretty sure I lost all root, etc. It is back to "out-of-the-box" stock as far as I can tell.
Click to expand...
Click to collapse
lol now worries. easiest way to get to the 10 limit is just pad the count in here. ie just say something 10 times and you are good to go.
synisterwolf said:
unrevoked3 is the easiest way. but you will need to downgrade to android 2.2 for the security exploit.
http://forum.xda-developers.com/showthread.php?t=1306400
Edit: fixed link
Click to expand...
Click to collapse
Good news, I'm on 2.2 stock right now (just checked to confirm). So should be able to just go ahead and run Unrevoked3 then.
Also, the most popular recovery I'm aware of is ClockworkMod Recovery. I found that it's up to version 5.0.2.0. Would you recommend anything else or know of a newer version?
Figure if I'm going to do this, might as well do it right.
wigmuke said:
Good news, I'm on 2.2 stock right now (just checked to confirm). So should be able to just go ahead and run Unrevoked3 then.
Also, the most popular recovery I'm aware of is ClockworkMod Recovery. I found that it's up to version 5.0.2.0. Would you recommend anything else or know of a newer version?
Figure if I'm going to do this, might as well do it right.
Click to expand...
Click to collapse
Nope I'm RunNing that one and it works well.
Sent from my sexy assistant. (AMOLED HTC Incredible)
Ok so I have been trying to mess around with my S3 for the last few days, I just converted over after 6 years of using iOS products and have absolutely no knowledge of Android at all, most of the info I can find that pertains to my device is limited to very basic instructions that make no sense to me having no droid background, I tried following information from other devices and that didn't change any of my issues. I have rooted the phone successfully and with no issues; however my next step of installing a custom rom has had me hit a brick wall.
I have gotten as far as installing the rom onto my phone (CM10) yes I was trying to use the proper d2att version of the nightly updates, most current one. I have CWM running fine, created a nandroid backup, booted back to stock, wiped all the cache's, wiped the phone. But any time I try to install the rom it gives me some BS status 7 error, which from all the searching I did came back with an issue of it not being the correct rom for my phone. But according to everything blasted on this site and on CM's site my phone (Rogers GS3) uses all the d2att stuff, thats what I used to root my phone and as mentioned that went flawlessly, 10 minutes maybe. Big thanks to the people here that put the Toolkit package together.
If it makes any difference I was trying to install via CWM via the install from zip on SD
Terribly sorry if this is the wrong spot for this but its been three hours of horrible frustration on something that people do in a 6 minute video on YouTube, followed one to the word and still had this status 7 error.
TL;DR - Help a converted apple noob with his perpetual status 7 error from hell!
First thing, you posted in the sprint section and as for status7 error I want to say you have a bad download, try downloading it again.
epic4GEE said:
First thing, you posted in the sprint section and as for status7 error I want to say you have a bad download, try downloading it again.
Click to expand...
Click to collapse
Ah crap! Thats what I get for going on a flurrey of cross board reading, could have sworn I was still in the AT&T section, probably wait a day or two for a new download or possibly try and older version. Thanks for the heads up.
Meola said:
Ah crap! Thats what I get for going on a flurrey of cross board reading, could have sworn I was still in the AT&T section, probably wait a day or two for a new download or possibly try and older version. Thanks for the heads up.
Click to expand...
Click to collapse
Won't hurt to try an older version, or another ROM to make sure your phone runs that ATT coding properly. If a different/older ROM works, then I would chalk it up under the bad download/bad update for that ROM and wait for the next increment. As long as you have the Nandroid (without getting crazy) you should be free to explore different things.