Related
So here's my deal... I tried gaining root access and followed all the steps perfectly, but for some odd reason it didn't work. I got as far as installing the radio update and still nothing changed. So what I decided to do was restart the process from the beginning. I put the dreaimg.nbh file on my sd card again and was ready to start all over, only this time at the rainbow screen it loaded all the way and I got the following screen:
00018003
DREAIMG.nbh - FAIL
BOOTLOADER - OK
RECOVERY - OK
BOOT -OK
SPLASH1 - OK
SYSTEMFail
USERDATA -
RADIO_V2-
Update Terminate
UPDATE FAIL
What happens is it gets all the way through the update process, hangs for awhile and then fails at system and locks up, the only way out is to pull the battery.
I've tried another SD card with a different copy of DREAIMG thinking it could be corrupted but no go, I tried it without the SD card as well as a blank SD but it always boots into the rainbow screen and there's no way past it that I can find.
Is my phone bricked?
Help please! Sorry if this has been answered before, I did a few searches and nothing came up.
I used the following video as a tutorial for everything I've been doing.
http://www.youtube.com/watch?v=xOo2V9qCauc&feature=channel_page
Like I said, I got through the whole process fine the first time with no problem except for the part where it didn't work. It's the 2nd time through that got me here...
been there
I know what you are going through...I haven't prayed so much in a long time. Try pulling the battery and then when you start the phone, press and hold the power and home buttons while the phone starts up. Just remember to breath...If you get the rainbow screen then that means that android is still installed and it should be able to be recovered...
If that doesn't work then reformat your sd card and try to redownload the Dream Img File.
Thanks for the help wm1, it's tough to breathe when your baby isn't working
Unfortunately I've tried both reformatting the SD card and installing a fresh dreaimg.nbh as well as the home/power button trick, neither yielded any results. I've even tried a different SD card... Thinking I'll just take it into t-mo, not sure how I'll explain this though haha
You made two mistakes;
1) Following a VIDEO -- totally retarded. If the person giving the instructions is so stupid that they give a video instead of a set of concise written instructions, then they definitely SHOULD NOT be giving instructions.
2) Failing to follow the instructions given. Some things you can't just abort in the middle of the procedure -- thats how you make a brick.
The device may still be recoverable, but because of your failure to follow procedure or to research the procedure before blindly following some retard's video, I doubt your ability to make it happen.
lbcoder said:
You made two mistakes;
1) Following a VIDEO -- totally retarded. If the person giving the instructions is so stupid that they give a video instead of a set of concise written instructions, then they definitely SHOULD NOT be giving instructions.
2) Failing to follow the instructions given. Some things you can't just abort in the middle of the procedure -- thats how you make a brick.
The device may still be recoverable, but because of your failure to follow procedure or to research the procedure before blindly following some retard's video, I doubt your ability to make it happen.
Click to expand...
Click to collapse
Clearly you didn't even read anything I wrote, thanks for attempting to be a dickhead though, really helpful.
Have you tried running a checksum on DREAIMG.NBH after it has been copied to sdcard? A fail might indicate file corruption or damaged sdcard.
I bricked my phone yesterday. I didn't know what to do when it keep loading at the android screen so I removed the battery to start over. I made it worst. Thankfully I have a friend who told me to call t-mo. Call the customer service line explained that your phone was updating and it froze. They will replace your phone even if you don't have insurance on it.
ETA: I got the same error as you when I was trying to add a theme.
Inhalent said:
Clearly you didn't even read anything I wrote, thanks for attempting to be a dickhead though, really helpful.
Click to expand...
Click to collapse
As much as you may be upset at lbcoder, I must say that I've never, ever bricked a phone. Considering that I run a small business on the side rooting g1's, I should have seen one if it's just random chance.
On the other hand, people write ****e directions in poor english, so you cant be faulted.
Can you reflash the spl using the fastboot binary?
Yes this video is ****ty, extremely ****ty. Instead of easy removing the flash disk with the icon near the clock, he is opening my computer, right click on drive and than select eject. I mean, if you don't know the better way to remove the flash drive why do you want to root your phone.
Just to say "hey my phone is rooted"
Or just select turn off USB storage from your G1 ( hate to call it phone ).
Hello, xda!
I've been around on the forums for some time, flashing and messing with ROMs before, but with an old HTC Touch Pro. So forgive me for seeming like a leecher.
I've come here to ask a few questions reguarding Andriod roms and flashing/upgrading procedures. I'm comfortable with using RUUs to upgrade, but who isnt...
I've had my HTC Hero for about 2 weeks now and I accidently bricked one already. I've rooted manually once, and got no signal on the stock Sprint ROM so I tried to go back to the original flash recovery but killed my phone instead.
Could someone help me out. I've read guides and been very, very anxious to upgrade and root but as you've read, I've already bricked my phone once so I'm pretty cautious now.
From what I understand, I need to root to 1.2.3, NAND backup, WIPE sd card & phone, then flash damage control's rom.....
So do I have it right or should I read a bit more?
Any help and tips from some experienced flashers would be much appreciated. Thanks!
mjones832 said:
From what I understand, I need to root to 1.2.3, NAND backup, WIPE sd card & phone, then flash damage control's rom.....
So do I have it right or should I read a bit more?
Any help and tips from some experienced flashers would be much appreciated. Thanks!
Click to expand...
Click to collapse
First off; we're happy you chose not to give up and came back a second time.
What you do need to do is; 1) Root and flash a Recovery image 2) Make a Nandroid back up, 3) Wipe ONLY your phone (not your SD Card, unless you want to do Apps2SD) and 4) Flash the ROM of your choice.
**The rooting guide I linked above is the way I prefer to do it; via adb commands. However, you could also you use Flipz's kitchen to do all of this for you.
.
For more information about Flipz's kitchen, please go here: Flipz's Kitchen
Also, do note -- for other tutorials/guides/references; go HERE
I was seriously nervous to start the process as well. As I told someone else, being nervous is a good thing. That just means you'll be careful.
I seriously recommend reading this thread and following instructions. Do not skip steps, do not pass go, do not collect $200. I've personally used the Windows guide and the Linux guide. Both are very well done and I can verify that they work.
Beyond that, the Search function is fantastic and provides lots of information. Don't be afraid to ask questions, either. Most of us are nice and like to help, even if we do call people n00bs.
WOW! Insanely quick replies. Thanks for that guys. This is what I wanna hear so I'll be doing the flash when I get home.
I'm using the 2.1update1 sprint beta ROM right now so should I revert back to the 1.56 and THEN do all this or can I just jump right in. I've always been confused as to which rom needs what flash rec root file or w/e.
And yes, I do want the A2SD thing as thats one problem I'm having right now. I've only got 16MB of storage left of my current storage area but my 8GB sd card is almost empty except for a few songs and pictures. Also, should I upgrade my sd card to a higher class if my 8GB is a class 2?
Thanks again guys!
Also, I mentioned that the last time I tried to root, I had no service after I did so. Why is that and what do I do to fix this? I couldn't find anything on this in google searches.
mjones832 said:
Also, I mentioned that the last time I tried to root, I had no service after I did so. Why is that and what do I do to fix this? I couldn't find anything on this in google searches.
Click to expand...
Click to collapse
Some people say to toggle airplane mode on and off. Some people say reboot. The last time this happened to me I just played a video game for ten or fifteen minutes and it fired up.
mjones832 said:
And yes, I do want the A2SD thing as thats one problem I'm having right now. I've only got 16MB of storage left of my current storage area but my 8GB sd card is almost empty except for a few songs and pictures. Also, should I upgrade my sd card to a higher class if my 8GB is a class 2?
Click to expand...
Click to collapse
I've not used apps2sd myself, but I'm told the higher class card the better, for obvious reasons.
Thanks, subcypher! I've got absolutely no reason to not do this. I'll be doing it as soon as I get home.
mjones832 said:
Thanks, subcypher! I've got absolutely no reason to not do this. I'll be doing it as soon as I get home.
Click to expand...
Click to collapse
Have fun! We'll be here when you get back.
yes.. a faster class sd card is highly recommended!!! other wise with a2sd, you might see more lag... and issues.
I personally, would not do a2sd at the same time as you upgrade. finish the upgrade first. make sure all is good...
then do the a2sd. and do a nandroid backup again before.
So I just tried to go back to 1.56 with the signed RUU that sprint gives out and it gave me an error. Failed to load bootloaded or something similar to that.
Remember, I'm on the 2.1update1 beta release of sprint's rom but I wanna root and flash to DamageControl's 2.1.
I've tried looking into how to root my current 2.1update1 beta ROM but I didn't come across anything worthwhile.
Anyone know whats going on???
mjones832 said:
So I just tried to go back to 1.56 with the signed RUU that sprint gives out and it gave me an error. Failed to load bootloaded or something similar to that.
Remember, I'm on the 2.1update1 beta release of sprint's rom but I wanna root and flash to DamageControl's 2.1.
I've tried looking into how to root my current 2.1update1 beta ROM but I didn't come across anything worthwhile.
Anyone know whats going on???
Click to expand...
Click to collapse
What steps did you take to use the Sprint RUU?
In order to run the Sprint RUU, you need to do:
**Make sure you have the appropriate drivers to detect HTC Sync**
1. Install HTC Sync on your computer
2. After install, open and leave the HTC Sync Window open
3. Connect your phone; and click on the sync option. You should be able to sync, if not - then you're having driver issues.
4. After you've successfully synced, NOW run the Sprint 1.5 RUU.
5. Upon a successful RUU, you'll have your phone back to its factory settings.
Now you can reroot, flash whatever ROM you like, and flash any/all add-ons.
As far as the signal goes, the following are from the Fresh 2.0d install page.
A reboot after the first bootup finishes is recommended, especially if you were previously having PRI/PRL problems.
Click to expand...
Click to collapse
If after flashing you end up with any data issues then first try rebooting. If that doesn’t resolve it for you then try updating your profile and PRL. This is a side effect of the different PRI’s and PRL’s that people have ended up on. You may actually need to update your profile and PRL a couple times to get everything going but I promise it will. You should end up on PRL 60663.
Click to expand...
Click to collapse
I personally had no problems, but I was flashing Fresh, not Damage.
Ok, I've got it rooted, and nand-backup stored on my PC.
DamageControl says to wipe before his install. Do I "wipe data/factory reset" or "wipe Dalvik-cache" or any other options?
If its the same as Fresh, they want you to do a Wipe data/factory reset
Thanks everyone! I'm installing DamageControl right now! I'll let you know how it goes.
Success! I've got the phone rooted, at least I think I do, and flashed to DamageControl v2.08.
My next task is I really want to get my apps to install to my sdcard. I've got a 8GB class 4 sdcard. Should and can I put my apps onto this? I've heard that the hero doesnt even read and write faster then 2Mbps so I'm good, right?
Not sure if I'm rooted. I've installed a few apps that require SU and when they try to do a "SU Request" the screen sits at a black screen with that title at the top.
Any idea on whats going on?
If you were able to flash a damage less rom you're rooted.
On the black window there should be am option on the bottom to allow, select it.
-------------------------------------
Sent via the XDA Tapatalk App
The black screen for SU is caused by not having USB Debugging turned on as it is required for superuser permissions. I have not tried A2SD because I only have a class 2, but have read that unless you have a class 6 it can be slow.
I've been ROM-hopping, trying Synergy, Alliance, Myn, and several others. On the last one, MikG 2.3, I had it loaded up and working fine. I started installing apps from the Android Market. That, too, was going fine, until it suddenly rebooted in the middle of an app download/install.
It went to the white screen with HTC EVO 4G on it, and then went black, then back to the white screen, over and over.
Six hours later, I'm still stuck in the loop. To make matters worse, I accidentally lost root (I see "S-ON" at the top). So now I'm stuck without root until GB is rooted successfully, which hopefully isn't tooooo far off in the future.
But that's the least of my concerns. I would be extremely happy with a stock install of any sort at this point, but I can't get anything to load. No recovery, no ROMs, but I can get into HBOOT so I'm able to try to load any PC36IMG.zip files. The last one I tried was the "PC36IMG_SuperSonic_GB_Sprint_WWE_4.24.651.1_Radio_2.15.00.05.02_NV_2.15_release_199233_signed.zip" (renamed to just PC36IMG.zip, of course). It appears to load just fine and in the end says "Update Complete... Do you want to reboot device?"
I choose yes, it reboots... and we're back in the loop. I have no idea what to do or try at this point. Any help anyone can provide would be greatly appreciated! My next step is to take it to the Sprint store, but that's over an hour away and will have to wait till the weekend.
Thanks everyone!! If you need any more information, let me know. Believe me, I'll be monitoring this thread closely!
/Kevin
I'm sure uve heard this before and prob won't work but worth a try....try reformatting ur SD card and then flashing the file in bootliader again. Could be a corrupt SD card
Papa Smurf151 said:
I'm sure uve heard this before and prob won't work but worth a try....try reformatting ur SD card and then flashing the file in bootliader again. Could be a corrupt SD card
Click to expand...
Click to collapse
Yeah, I tried. I have several SD cards of varying sizes (4GB, 8GB, and my primary 16GB). Formatted the 4- and 8GB ones and tried from each, but no go. Thanks for the try though!
/Kevin
Reset phone to recovery (stock), choose fastboot. Plug in USB to computer.
Look for the correct ruu exe file and ruu it via exe method
trim81 said:
Reset phone to recovery (stock), choose fastboot. Plug in USB to computer.
Look for the correct ruu exe file and ruu it via exe method
Click to expand...
Click to collapse
Just did it and the process went well, said it was successful... but it's still stuck in the same loop. I'm thinking the phone is beyond repair. Thanks for trying, though. It really looked like it might work for a second.
/Kevin
what was the app?
That's what I want to know and how do you get accidentally to S-On?
Put the phone in a refrigerator ... as crazy as it sounds, it might be the infamous overheating issue.
Put in refrigerator, for about 5min
The app was "Kid Zone" (Zoodles), but I'm not blaming the app by any means. I've used it for a long time, it's highly-rated in the market, etc. I'm sure it's just a coincidence.
As far as getting back to S-ON, I think it must have been when I flashed the stock recovery. I was flashing so many things out of desperation that I can't swear to that, but I'm pretty sure that's what did it. Now that it looks like I'm heading to the Sprint store tomorrow, I guess it's a GOOD thing it's back to S-ON. Heh.
Pretty sure it's not heat-related. My phone was off all night (since it's not usable) in an air conditioned room, so it's cool to the touch. I tried the RUU process again with the same results. (I'm not sticking it in the refrigerator, because I'm afraid of activating the water-damage sensor -- I don't want any excuses from Sprint when I bring it in tomorrow!)
Appreciate the help!!
/Kevin
That sucks, but tbh, I have yet to see one case of anyone at Sprint checking a bootloader to see if a phone is S-On. MOF, I bet if it doesn't boot at all, or is a stock ROM , they wouldn't even know the difference.
HipKat said:
That sucks, but tbh, I have yet to see one case of anyone at Sprint checking a bootloader to see if a phone is S-On. MOF, I bet if it doesn't boot at all, or is a stock ROM , they wouldn't even know the difference.
Click to expand...
Click to collapse
I hear ya. I haven't run into any techs at my local stores that are knowledgeable about this kind of stuff. (I know others have, so you never know, but I have yet to see one.)
/Kevin
To conclude this: I went to the Sprint store today where they assured me they would reload the software but it would take 1.5 hours. I came back 1.5 hours later... and they handed me a new (refurb) EVO. They said they weren't able to load anything on the phone.
So, no surprise with the outcome there. I was fairly certain they were going to have to replace the EVO, and they did.
Thanks to everyone who tried to help, but it was just beyond help!
/Kevin
I had that same problem with my phone back in November. Continues boot loop. Finally, having boot loop for 8hrs, I took it to Sprint and they replaced my phone. They called it a power cycle issue. $35 new refurbished phone works well. Never had a problem since.
I have been working on this for the past few days and for the life of me cannot figure out the problem. I'll start by just laying out a sequence of events.
Bought A500 about a month ago. OTA'd to HC 3.1 4.010.13_com_gen2
Decided not to wait for OTA 3.2 and rooted with iconiabreak.
Did not do a backup (like an idiot, i know)
Flashed Taboonay 2.0 with Thor's 2.1 kernal.
Saw awesome post to get rid of cell standby by deleting phone.apk and telephony.apk....do i did that.
Realize i am an idiot and then run a Nandroid backup.
Was happy for a few weeks when i see that Vache had updated taboonay to 2.1b and decided i wanted to do that.
Downloaded the files and started to flash with CWM. Factory, cache, dalvik wipe. Run Taboonay zip.
Get stuck in bootloop at Taboonay boot screen. $#!t......
Think "it's ok, ill just do an update.zip and go back to 3.1"
Try almost all the files on Vache's full package and update thread.
I put each one on an ext sd card and throw it into recovery boot. The Android guy with gears shows up and it looks like it is going to work.
The progress bar gets about 90-95% of the way when everything just stops. Gears animation, progress, everything.
It then reboots and gets stuck in a bootloop at the android screen. Load a different update.zip and same thing happens each time.
I try to just do a normal recovery boot, but CWM isnt there anymore and i get the ! android.
Normal reboot gives me a bootloop.
So i am stuck and asking if it is the phone and telephony apks that caused everything? if that were the case, how would i be able to load them back up since im totally locked out. I havent tried adb since im out of town for a few days. Thanks for any help that anyone can lend me. Ill try to answer any questions for any information that might be needed.
bumping for great justice~
I've tried decrypting update.zip files and vice versa.
still no luck..
try the fall back to 3.0.1
Check under development section for iconia a500. You'll see a thread for going from 3.2 to 3.0.1.
As i readd about this rom, it seems it's used in difficult cases (it removes the locks created by 3.2 stock), so it could be worth giving it a try.
rorohajj said:
Check under development section for iconia a500. You'll see a thread for going from 3.2 to 3.0.1.
As i readd about this rom, it seems it's used in difficult cases (it removes the locks created by 3.2 stock), so it could be worth giving it a try.
Click to expand...
Click to collapse
Thanks for the reply.
I don't think that will be a viable option for me since i'm not able to get my UID. i've plugged my tablet into the computer and gotten the "hardware found" bubble. It prompts me to look for drivers (which i havent be able to find) and, i assume because it's in a bootloop, wont show up on the computer.
Does anyone know why the update.zip files would fail at 90%? I think that's really the thing that boggles my mind and is most frustrating.
Did you at all have your A500 connected to your computer prior to this happening? If so then you can get the UID from by way of the Windows registry. Then you should contact SC2K and get him your UID he should be able to help you get your A500 back from the dead.
jeffw111 said:
Did you at all have your A500 connected to your computer prior to this happening? If so then you can get the UID from by way of the Windows registry. Then you should contact SC2K and get him your UID he should be able to help you get your A500 back from the dead.
Click to expand...
Click to collapse
Unfortunately, no I never plugged my A500 into my computer.
quick update:
I was able to use a different computer and found something interesting.
While trying to transfer or open a decrypted update.zip file, i get an error message saying, "Please insert the last disk of the Multi-Volume set and click OK to continue". Clicking OK just brings it back and i am forced to click cancel.
Anyone have any idea what that would mean??? It doesnt happen when I open or transfer the non-decrypted file. Only the decrypted file using Thor's Acer Update Decrypter application on HC 3.1 and 3.2 files.
While loading the decrypted update.zip on the A500, it almost instantly shows the ! android guy, while the non-decrypted files go 90-95% and then reboot into bootloop.
Any help would be greatly appreciated!
first off if you can get into recovery to flash anything.You are not bricked.
Take your SD card put in a android phone format it.
Put the card in your computer.copy a full update.zip file from dev section.likes on a post by Thor.put card.back in tab and flash.
If it stall fails repeat with a different SD card.seems smaller ones do best.
Good luck.
erica_renee said:
first off if you can get into recovery to flash anything.You are not bricked.
Take your SD card put in a android phone format it.
Put the card in your computer.copy a full update.zip file from dev section.likes on a post by Thor.put card.back in tab and flash.
If it stall fails repeat with a different SD card.seems smaller ones do best.
Good luck.
Click to expand...
Click to collapse
Thanks for your reply, first off.
I'm sorry I didn't make it clear that I had done all of those things during the events of the first post EXCEPT try a different sd card.
So I went out today and bought a PNY 2GB sd card as opposed to the SanDisk 4GB i was using. I formatted it in my Atrix 4G and threw a full update.zip file in there. The first file I tried (from Vache's http://forum.xda-developers.com/showthread.php?t=1113878 thread) was Acer_A500_4.010.38_COM_GEN1 (HC 3.1). Since I was able to open the .zip without decrypting it I loaded it only the sd card. It did the same thing as before (loaded to about 90% then freeze, reboot) except this time I got a "Boot verification failed..." message in bright red letters up at the top left of the Acer screen. Since it didn't work, I loaded Acer_A500_7.006.03_COM_GEN2 (HC 3.2) onto the sd card. Again, since I was able to open the .zip file, I assumed that there was no need to decrypt it. Loaded the sd card and put the tablet into default recovery (not CWM recovery which I no longer have). The same problem keeps happening: it loads to 90%, freezes then reboots. This time, however, it went into a bootloop at the "android" screen.
I've tried decrypted versions of those files, but I always get an error message while trying to open them and when trying to flash them in default recovery, it almost instantly goes to the ! android guy since I'm assuming those files are already decrypted and decrypting them again is bad.
Hopefully if I try enough files, I'll find the one that works...
Until then, if anyone has any ideas as to what I might be doing wrong or should be doing differently, please let me know!
Thanks.
there is a thread that has instructions on going from the OTA 3.2 to downgrade. To 3.1.look for that tthread and windows software. On that thread it talks about that error your getting.
Since I have not had this issue .can't say for sure if it will help.
Good luck sorry I can not do more to hhelp
Just a dingy blonde here.
erica_renee said:
there is a thread that has instructions on going from the OTA 3.2 to downgrade. To 3.1.look for that tthread and windows software. On that thread it talks about that error your getting.
Since I have not had this issue .can't say for sure if it will help.
Good luck sorry I can not do more to hhelp
Just a dingy blonde here.
Click to expand...
Click to collapse
Thanks for your suggestion.
I was able to find my UID from an old CWM backup file and tried this method. I attempted it last night with no success. I was actually in the middle of making a reply saying how heartbroken I was and that I was basically giving up. I decided to try it one more time and made a slight adjustment from my method last night. In the UID file, I had my UID in there as 0x0blahblahblah and kept getting the incorrect UID error in the program. When I tried taking out the first 0x in the program, it gave me an incorrect format error. That is where I was messing up.
Instead of 0x0, all i needed was 0blahblahblah in the UID file.
Attempted the upgrade utility again, and viola! It worked like a champ.
So thanks again to all that helped out and offered suggestions and to all the Devs for their outstanding work. I've definitely learned a lot from this experience.
search has not been my friend these days - Long story short, I eneded up with a new to me evo 4g. I replaced the screen and started her up. A few freezes and I did a factory data reset from the settings menu. Decided to root.
used the supertool method here :http://www.goodandevo.net/2011/12/new-htc-evo-rooting-method-now-available-htc-supertool.html
ran step 1(prep) and had success.
ran step 2 (attempt root) and it was unsucessful - I figured it was because I didn't have an sd card in, so powered down
re-ran step one and phone froze.
Half the time I could get to the bootloader, so I tried an RUU. Went to fastboot usb, had it registered with the computer as and HTC... and ran the ruu. Either my windoze machine froze or the phone did. It failed.
Now I can get to the bootloader 1 out of 25 tries. Otherwise the screen stays blank. Then the buttons don't work every other time I do get in. I have to leave the battery out about an hour(?) or more for a chance at success. IF the buttons work, it stays active for about 3 minutes. Then the phone freezes.
The phone does have charging lights on it, but that's about it.
What can I do here?
Somewhat of an update. If I wait long enough- like 3.5 to 4 hours, I get one shot at the bootloader screen. I tried to ruu with a 4.56? stock rom, but had issues again. then i saw a friends phone who had 4.53. So I'll try that in the morning. Crossing my fingers here.
wasilvers said:
Somewhat of an update. If I wait long enough- like 3.5 to 4 hours, I get one shot at the bootloader screen. I tried to ruu with a 4.56? stock rom, but had issues again. then i saw a friends phone who had 4.53. So I'll try that in the morning. Crossing my fingers here.
Click to expand...
Click to collapse
If your phone comes on and you see lights its not bricked. Once you cant get it to do anything then thats when you worry. I would find one of the the PC36IMG.zip files and when you get it to go into bootloader you can install the zip.
Does your bootloader say unlocked? Also I am confused because the methods on here for rooting is quite easy and have been established for some time now. Why would you try a relatively new method and especially something of the xda grid.
Dowload the PC36img file from this thread and go from there..
Yeah, getting to the bootloader is the problem. I manged 2x last night. Sat overnight and no lights or beeps or vibrations, but it charges (confirmed batt was charged on my friends evo).
I tried a pc36img file, several actually, but it wouldn't load them. S-on is listed in the bootloader - since I never actually got it rooted.
IF S-ON is in the bootloader, will it load a pc36img file?
Can I install the PC36... file on the removable sdcard, and it should recognize it and install it? It just reads the card, examines the file and goes to the normal bootloader screen. That's why I was trying RUU files.
playya said:
Also I am confused because the methods on here for rooting is quite easy and have been established for some time now. Why would you try a relatively new method and especially something of the xda grid.
Click to expand...
Click to collapse
If I recall, I was forwarded there by an xda thread. It's my fault for not checking my build first and making sure it was an acceptible root method for it. This phone is a year old, I assumed the method would work - I was wrong - and am now paying the price for the assumption.
wasilvers said:
Yeah, getting to the bootloader is the problem. I manged 2x last night. Sat overnight and no lights or beeps or vibrations, but it charges (confirmed batt was charged on my friends evo).
I tried a pc36img file, several actually, but it wouldn't load them. S-on is listed in the bootloader - since I never actually got it rooted.
IF S-ON is in the bootloader, will it load a pc36img file?
Can I install the PC36... file on the removable sdcard, and it should recognize it and install it? It just reads the card, examines the file and goes to the normal bootloader screen. That's why I was trying RUU files.
Click to expand...
Click to collapse
Yes. I believe you can install a signed stock ruu directly from HBOOT even with s-on. install the sd card with the ruu.zip directly on the root of the sd card (name must be pc36img.zip). When HBoot loads, it will scan the sdcard and find the zip and automatically run it. format the micro sd card first... maybe its corrupted or something.
Update
Update:
All options were a nogo- I got a pc36(whatever) file to read and a progress bar that paused (paused till the battery went dead). No RUU file would work. I read that some of the memory modules must have been written bad in the root and it would need jtag service. So I'm putting the screen on ebay and cutting my losses.
Moral of the story: Stick with XDA - search under your operating system, don't be lazy like me.
Now I am root shy, only rooted one phone in the last 2 weeks, and none for my friends. Glad this was mine and not a friends - that's probably why I got lazy.