Related
Okay, so I was unrooting my droid incredible and it brought it to stock 2.1 i was trying to install the update.zip to update it to 2.2, but it wasnt working...so i tried installing the 2.2 RUU onto it...and now when i try to turn on my phone it always boots into the Bootloader...what should i do?
Note: LED charging light still comes on, and i can still go into recovery(stock recovery though since my phone is no longer rooted)
If theres no way to fix it, can i just play dumb and tell verizon its not starting up, because doesnt HTC have to reflash everything anyway for security purposes....the only downside though is they would probably send me an SLCD Incredible
First and foremost, your phone is not bricked... not even close.
Simply try reinstalling the 2.1 RUU. Being that it's signed by HTC, you should be able to do what you need to in the stock recoveryThat being said, your update.zip probably failed because your phone was restored to a state prior to the May OTA. Without being at the correct software version, you cannot use the update.zip to install Froyo.
If you get the bootloader, you should be ok. I think the zip has to be on the root of the SD and named update.zip for the stock recovery.
Sent from my DInc
Look in the android development forum for "the ultimate back to stock thread". download the "PB31IMGxxxxx" file there, rename it to just PB31IMG.zip and put it on the root of your sd card. Go into the bootloader and let it run the update. This will bring you back to a 2.2 stock. From there you can re-root and do whatever else you like.
Sent from my ADR6300 using XDA App
Okay, well it was the get back to stock thread that i followed...and i know that i was trying to do the update.zip from a version of android that was too old, because i was the one who posted a thread a few months back with the update.zip in it. However, i was obviously stupid enough to not save teh "May" OTA and now the link is dead. Some people were reporting however that it still worked without it, so i wanted to see for myself.
In any case, it seems that a 5 hour battery pull seemed to do the trick, go figure. Can someone explain to me what a battery pull on this kind of stuff makes a difference and why the length of time sometimes makes a difference as well?
Okay, so here's what happened:
I was minding my own business, listening to Pandora at work. Out of nowhere, the music had an increasing amount of pauses due to bad music loading, or so I though. I figured it was just the crappy Sprint network around here, but I figured I would restart it and hope it would work again.
Boy, was I wrong. At the first reboot, it got stuck in a bootloop where it would start my boot animation all the way from the start after it got into it's little animation loop for a while. So I pulled the battery and tried it again. This time, it made it through and loaded up to the lock screen.
Once I unlocked it, I got an error message that said something along the lines of "hardware UIC doesn't match, please wipe your data partition" (can't pull the exact wording out of it anymore, I can't reproduce it) I acknowledged that message and then I got a ****LOAD of FC's left and right for just about everything under the sun, and then some. All of my system apps were FC'ing, and it was just one after the other after the other, and it would even loop them around and the same system apps would pop up FC's again.
Okay...maybe I can fix this by wiping my data like it said. Nope. Maybe I can flash my ROM again and fix it... Nope. Now it loads up to the setup screens, and then about halfway through, the sytem just locks up on me.
****. Alright, let's try flashing a stock ROM back to it. Well, this doesn't work either. Same results.
I have no idea why it started doing this, and I really don't want to have to go get myself another phone, since I don't have any kind of warranty on my phone.
So does anybody out there have any other ideas on what I can try to do to fix this? It's been driving me crazy all night.
Run stock ruu
Sent from my nike hating evo!
Before you run the RUU, reformat your SD Card, I don't know what recovery you have, but use Amon Ra to wipe EVERYTHING Except the option for SDCard:, dalvik cache and cache 2 times, then flash your ROM in recovery.
If that doesn't work, try running RUU
Additional details about my phone:
HBOOT 6.16.1002
ClockworkMod Recovery v5.0.2.2
Also, I can't seem to find an RUU that my phone will take... They've so far been failing on me, but I'll keep looking...
Also, wiping, flashing ROMs, wiping again, has not produced anything fruitful. Will be going the RUU route. I seem to have found one that *should* take, fingers crossed.
Problem number 1. Clockwork Recovery Mod. Get rid of it and get Amon Ra and do as I posted above.
Here, download this, rename it to PC36IMG.zip, out it on the root of your SD Card, not in any folders, and reboot to Hboot (Vol dwn-pwr til hboot comes up).
It'll scan and ask you to update, say yes, it will flash Amon Ra. Now go back to Recovery, go to Wipe and do as I said above.
http://www.mediafire.com/download.php?v453e5wg0on3pzt
[RESOLVED] [Q] Epic failure... Any ideas?
CM REcovery hasn't led me wrong yet, but I have tried both of them... Personal preference, I think.
The RUU took and the phone is usable again for the most part. The only issue I have now is an error that pops up after every boot... "SD card unexpectedly removed" But I'll be digging around to figure that one out.
Thank you guys for your help, I was beginning to think it was a hardware issue for a while there.
CWM is leading you wrong and you just don't know it. For one, you can't do a proper wipe before flashing a new ROM. Also, there are issues with flashing Radios, if you ever need to upgrade.
There's a reason why the majority of users use Amon Ra. Your choice, though.
Maybe you need to reformat that card, or try a different card.
Wound up going back to work before I could finish everything I wanted to, however I was able to get S-OFF, and I went and flashed RA Recovery. The sd card issue was caused due to a bad sd card. Unfortunately I was unable to save everything from it, but I should be able to get most of my files back relatively quickly. Should be able to have Synergy flashed on it again before I go home in the morning.
Sent from my PC36100 using XDA App
A few days ago while flashing a new rom, my Evo quit booting. I wouldn't consider myself a n00b, but I'm out of ideas. Here is what I have done:
* used unrevoked3 and unrevoked-forever to obtain root and s-off at least a year ago
* used CM7.1 stable as my daily driver
* used stock to update radios around the time CM7.1 went to stable
* flashed deck's ICS preview4 to test an app on 4.0, after doing a nandroid and wiping in cwm 5.0.22 (I think that was the version)
* the phone refused to boot, vibrating 5 times and flashing the green notification light
* going into hboot, s-on is back somehow
* recovery could only be reached if the usb was plugged in
* recovery could not mount the sdcard, so no nandroid restore
* tried several stock PC36IMG.zip until 4.24.651.1 finally flashed in hboot
* the phone still won't boot, either vibrating 5 times or showing the red ! triangle
* the 4.24.651.1 RUU tells me my battery is < 30% even though I let my phone charge all night
Any ideas would be greatly appreciated. I don't really want to pay $450 for a new Evo. Thanks in advance.
Custom rom name it the same as img and see if that works if all else fails ruu and revolutionary
Sent from my PC36100 using Tapatalk
VaughnOnix said:
A few days ago while flashing a new rom, my Evo quit booting. I wouldn't consider myself a n00b, but I'm out of ideas. Here is what I have done:
* used unrevoked3 and unrevoked-forever to obtain root and s-off at least a year ago
* used CM7.1 stable as my daily driver
* used stock to update radios around the time CM7.1 went to stable
* flashed deck's ICS preview4 to test an app on 4.0, after doing a nandroid and wiping in cwm 5.0.22 (I think that was the version)
* the phone refused to boot, vibrating 5 times and flashing the green notification light
* going into hboot, s-on is back somehow
* recovery could only be reached if the usb was plugged in
* recovery could not mount the sdcard, so no nandroid restore
* tried several stock PC36IMG.zip until 4.24.651.1 finally flashed in hboot
* the phone still won't boot, either vibrating 5 times or showing the red ! triangle
* the 4.24.651.1 RUU tells me my battery is < 30% even though I let my phone charge all night
Any ideas would be greatly appreciated. I don't really want to pay $450 for a new Evo. Thanks in advance.
Click to expand...
Click to collapse
I had this happen to me a little less than a month ago and it ruined my weekend. I fortunately have a repair plan with Sprint as a "just incase" practice, so I just flashed stock and removed root, then brought in my phone claiming it just "restarted" and the software crashed, breaking my USB and SD card controller. The people at Sprint thought it was just "lint in my MicroUSB port," I laugh and told them to turn it on and they looked at my with a puzzled "wtf did you do to it!?" look.
What caused my problem was my SD card was full when I attempted to backup my ROM. This caused CWM fail at a backup and bricked my phone. Is this what happened to you by any chance?
I never did "fix" my phone's usb/SD management issue, but was able to temporarily boot it, but was plagued with random restarts. I'd like to throw in some links but I'm pinched for time seeing as I need to leave for work. (Search XDA) There was a Android 2.2 image that was I able to flash in the bootloader that let boot fully. But it will erase all traces of root. - Before you try and do anything else, research into if there is ANYTHING you can do with adb over WiFi, because that was the one thing that I didn't try. What I'm saying is to do a lot of reading before you start flashing anything, plan out your attack before you execute it. Because I ended up digging myself a deep hole by just randomly flashing images.
Wish you luck man, sorry I wasn't of much help.
nrm5110 said:
Custom rom name it the same as img and see if that works if all else fails ruu and revolutionary
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Hboot finds the renamed CM7.1 zip and checks it, but does not offer to flash it. I assume this is because s-on is back. Also, I mentioned that RUU is claiming my battery is too low to flash.
OMGWTF_BBQ said:
I had this happen to me a little less than a month ago and it ruined my weekend. I fortunately have a repair plan with Sprint as a "just incase" practice, so I just flashed stock and removed root, then brought in my phone claiming it just "restarted" and the software crashed, breaking my USB and SD card controller. The people at Sprint thought it was just "lint in my MicroUSB port," I laugh and told them to turn it on and they looked at my with a puzzled "wtf did you do to it!?" look.
What caused my problem was my SD card was full when I attempted to backup my ROM. This caused CWM fail at a backup and bricked my phone. Is this what happened to you by any chance?
I never did "fix" my phone's usb/SD management issue, but was able to temporarily boot it, but was plagued with random restarts. I'd like to throw in some links but I'm pinched for time seeing as I need to leave for work. (Search XDA) There was a Android 2.2 image that was I able to flash in the bootloader that let boot fully. But it will erase all traces of root. - Before you try and do anything else, research into if there is ANYTHING you can do with adb over WiFi, because that was the one thing that I didn't try. What I'm saying is to do a lot of reading before you start flashing anything, plan out your attack before you execute it. Because I ended up digging myself a deep hole by just randomly flashing images.
Wish you luck man, sorry I wasn't of much help.
Click to expand...
Click to collapse
My sdcard has over 4gb available space. I flashed stock 2.3 in the bootloader but it still refuses to boot (as mentioned in the original post). As far as I know, you need to be able to boot to use adb. The only images I have tried to flash are stock images and CM7.1.
This is starting to look bleak...
I appologize I didn't see it man
Sent from my PC36100 using Tapatalk
VaughnOnix said:
My sdcard has over 4gb available space. I flashed stock 2.3 in the bootloader but it still refuses to boot (as mentioned in the original post). As far as I know, you need to be able to boot to use adb. The only images I have tried to flash are stock images and CM7.1.
This is starting to look bleak...
Click to expand...
Click to collapse
Sorry, my previous post was in a rush. (As is this one, lol)
Really? So your phone just screwed up out of no where while flashing the ICS alpha4 rom? Were you using CWM? Because if so, I'm switching to Amon RA asap.
Moving on, I know how you're feeling right now. But, I still have hope.
As previously stated, after ruining my EVO I was able to flash a PC36IMG.zip that allowed me to boot my EVO. I had to do some serious digging, but I found the thread I used with the ROM that worked http://forum.xda-developers.com/showthread.php?t=884060.
None of the old Megaupload links work, but this filesonic one does. Download it and flash it in your bootloader. Its signed, it should work. Try to flash it twice if anything. If it still doesn't work, try one of the newer ROMs. I'm only guessing that's the one that worked for me.
The only problem is that I don't think that's a 2.3 ROM, and we need a 2.2 ROM. Because the only root method that doesn't use a USB/SD Card is this: http://forum.xda-developers.com/showthread.php?t=701004 If you can get
If you can get your EVO rooted again with S-Off, follow this guide here: http://forum.xda-developers.com/showthread.php?t=695243 (Original) and you might be home free. But as of now, your goal is to find a stock 2.2 PC36IMG. Hopefully someone else can help here.
I sadly have to get to bed. Just got off work and I need to get some rest, another long day tomorrow. Good luck! I'll be back here next chance I get.
Same thing here
I'm having the exact same issue - flashed ICS alpha 4, now I can't mount my SD card. I don't have the red triangle of death, but I am getting the 5 vibrations on trying to boot - can get to hboot, and was able to *almost* get the SD card to mount using this:
http://forum.xda-developers.com/showthread.php?t=695243
but that only yielded ICS "preparing SD card" and "checking SD card for errors" indefinitely. I backed up and formatted my SD card, and this at least let me browse the empty sd card in Clockwork Recovery - I am in the process of copying my cwm backups back to the sd card in the hopes of being able to restore them from cwm. I'll keep you posted on what happens, and will most likely try to RUU when I get home from work. Puzzling that my s turned back on again as well, it's been off for well over a year...
Update on previous post
spoonydx said:
I'm having the exact same issue - flashed ICS alpha 4, now I can't mount my SD card. I don't have the red triangle of death, but I am getting the 5 vibrations on trying to boot - can get to hboot, and was able to *almost* get the SD card to mount using this:
http://forum.xda-developers.com/showthread.php?t=695243
but that only yielded ICS "preparing SD card" and "checking SD card for errors" indefinitely. I backed up and formatted my SD card, and this at least let me browse the empty sd card in Clockwork Recovery - I am in the process of copying my cwm backups back to the sd card in the hopes of being able to restore them from cwm. I'll keep you posted on what happens, and will most likely try to RUU when I get home from work. Puzzling that my s turned back on again as well, it's been off for well over a year...
Click to expand...
Click to collapse
*** Update ***
Ok, so after all that, I was able to restore my backup from within recovery, copy all of my data back to the sd card, and now I'm back in business...mostly. I still get the 5 vibrations on boot *unless* i'm plugged into the computer, and even then it's not a sure thing (usually takes 3 or 4 tries to get it to boot). At least I have a functioning phone again. Next step - RUU and factory reset, and see what happens. Again, I'll post back with my results. Hope this helps someone
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)
Well I finally made the leap back to Android from iOS (Had a Nexus One & S back in the day) and got an S3 that I went about rooting yesterday. After finally getting it rooted and adding CWM, I flashed the nightly build of CM10, and that's when it all went downhill. The phone was taking forever to boot, and as a fairly impatient person, I led to my own doom. I rebooted into CWM thinking that an erase and reinstall would do the trick. The kicker, I literally formatted every option as far as formatting goes... Don't ask. Clearly didn't think about what I was doing. At this point when attempting to boot the phone, it shows Samsung for a sec, then black. I can still access CWM, but when I attempt mounting anything, my Mac (Yes, don't judge) does not see it. I do have access to a PC if needed, I just need to get this phone working again, preferably with a custom ROM. Someone, anyone.. Help this poor idiot.
Adnando said:
Well I finally made the leap back to Android from iOS (Had a Nexus One & S back in the day) and got an S3 that I went about rooting yesterday. After finally getting it rooted and adding CWM, I flashed the nightly build of CM10, and that's when it all went downhill. The phone was taking forever to boot, and as a fairly impatient person, I led to my own doom. I rebooted into CWM thinking that an erase and reinstall would do the trick. The kicker, I literally formatted every option as far as formatting goes... Don't ask. Clearly didn't think about what I was doing. At this point when attempting to boot the phone, it shows Samsung for a sec, then black. I can still access CWM, but when I attempt mounting anything, my Mac (Yes, don't judge) does not see it. I do have access to a PC if needed, I just need to get this phone working again, preferably with a custom ROM. Someone, anyone.. Help this poor idiot.
Click to expand...
Click to collapse
The best advice I can give you is to not worry about ROM or root right now. Best bet is to get on the PC and ODIN back to stock. Once you're back up and running, then root to your hearts content.
I've found (the hard way) that this phone is hard bricked very easily. You don't want to do that, just start fresh.
From this link you can get a stock jellybean rom with root injected into and flash it through odin. But as with anything read carefully.
http://forum.xda-developers.com/showthread.php?t=1739426
If you have a MicroSD card, you can shove a rom inside there and install it by launching into Recovery mode. Works for me everytime.
laserlight959 said:
If you have a MicroSD card, you can shove a rom inside there and install it by launching into Recovery mode. Works for me everytime.
Click to expand...
Click to collapse
Came to say the same. If you can still boot into recovery then just insert sdcard with a rom and flash. Then make a backup so it doesn't happen again lol.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app