Hi guys, I finally decided to root my G1. I'm writing apps so I was going to leave it stock but sipdroid was released and I wanted to get a 1.5 image on there. I was following the tried and true downgrade to RC29 method to gain root when I ran into problems. I have read and read and read, searched high and low, but it may have to come to an end.
I "successfully" flashed RC29 onto my G1 (retail). Using a fat32 formatted 4GB card containing only the RC29 DREAIMG.NBH. It verivied the image, got through 100% progress, OK'd each item, gave me the successfull / complete message, asked to hit action key, great. Reboot.
Now, every time it hangs on the G1 screen. It still has the stock SPL and no recovery mode. I can still get to the bootloader mode if I want to flash again, or another image. I can also perform a wipe (and have).
Things I have tried:
-performing successfull wipes through booting with home+back
-reformat sd card, fat32.
-verify and compare md5sum of NBH image to same image from other sites
-tried RC29 image from multiple sites / sources
-check md5sum of image after copying it to card (using card reader)
-updating with recovery.img and update.zip but either it doesn't boot far enough or I can't yet because of the image or stock SPL.
-found an RC30 image and flashed it, same problem.
-Swapping my fido and tm sim cards, and without one
Things I need to try:
-another sd card, I may run out and get a 1 GB.
-look for a RC33 image but I don't think there's one leaked. I have seen updates to apply as update.zip but I can't do that in my phone's state.
Maybe there's something in pre-RC33 that tickles a problem with my phone?
Maybe something just messed up when I flashed RC29 for the first time, even though it got OKs all around.
I'm doing everything from my linux laptop as that's all I use. I'm in Canada, had to get my phone from ebay which cost me over $400 CAD. I would have gotten an ADP1 but the handling fees to here are rediculous. Expensive paperweight. I don't know if I'll have any luck getting a warranty replacement.
I was lucky enough to have JF and other's offering suggestions over IRC last night but as you see I'm still stuck.
Any other suggestions?
Thanks!
Interesting, I've just read something from the list of changes in RC33, which I was running:
# G1 hanging at the G1 Screen
* Symptom(s): A small number of G1 devices hanging at the G1 screen during the initial power up.
I guess another option would be to wait / keep searching for a leaked RC33 DREAIMG.NBH.
Is there a way to generate one using nandroid on a phone with stock RC33 or is my imagination too wild?
You need root to create a nandroid backup...
Wait how long do you let it sit on the G1 screen? I've had an instance or two I believe when I first got root where when first booting up it took forever.
Senorkabob said:
Wait how long do you let it sit on the G1 screen? I've had an instance or two I believe when I first got root where when first booting up it took forever.
Click to expand...
Click to collapse
I've probably left it at most for about 20 minutes. I've head of G1's hanging on the flashing android screen then recovering, but not on the G1 screen. I also don't want to drain my battery, even though I have two. I'm not sure my batteries will charge in this state and I don't have a seperate bettery charger (maybe time to get one).
HockeyDadNinja said:
I've probably left it at most for about 20 minutes. I've head of G1's hanging on the flashing android screen then recovering, but not on the G1 screen. I also don't want to drain my battery, even though I have two. I'm not sure my batteries will charge in this state and I don't have a seperate bettery charger (maybe time to get one).
Click to expand...
Click to collapse
I would venture to say that it would... mine charges on recovery mode, off, in boot loader... even when hooked up via USB and the laptop is OFF
In fact despite the lack of time on the battery I've been impressed how easy it is to get power to it... I just carry around a micro usb cable, 15-30 mins power here and there keeps me going round the clock
HockeyDadNinja said:
-another sd card, I may run out and get a 1 GB.
Click to expand...
Click to collapse
Over lunch I got a 1 GB card, found a windows box to format it fat32, copy RC29 DREAIMG.nbh to it, flashed my G1 with is, success, reboot, still hangs.
I'd love to get my hands on an official RC33 image, or a diag image that will work on this phone. I found the service manual also, it has links to images on the HTC site but of course they're password protected.
If I can't RMA this thing maybe another option is to get one for parts and build a hybrid.
Format the card for FAT (not 32)
Load the IMG file on there and try it again. I've seen problems with a Fat32 formatted card.
It is not a card problem if your update is found and flashed. Wish i had more answers for you, but at least you can stop looking down that road.
JF said to try getting into recovery and applying an official update to see if that works. The updates can be found on my wiki (links in my sig) if yo need them.
Also he just told me that there might be a RC30 nbh file floating around on these forums. If so you might try that. I would look for yo but I have to head off to work
Thanks, I do have an RC30 image, and have tried it with the same results. I also have an official RC30 to RC33 update but haven't been able to get into recovery mode to apply it. I'm crazy busy at work for the next few hours but will try again avter that.
Thanks.
I've tried a zillion times to get into recovery mode, not gonna happen.
Also, now I can't even perform a wipe by holding home+back+power on boot.
I can still flash nbh images but nothing available to me will work. When I load DREADIAG.nbh every time it does something with the radio it hangs until I hit end to cancel it.
It is my current theory:
As in my second post to this thread my G1 suffers from a problem that was fixed in RC33. This is causing my G1 to hang since I now have RC29 (and RC30, etc). It is likely that the problem has to do with the radio (or radio image).
There's no way for me to update the radio image right now. I need a newer (>= RC33) nbh to load.
Suppose my G1 is hanging on the radio device. As in the service manual, page 22, I unplug the UMTS coaxial cable to disconnect the device.
Is the UMTS the radio or is it just for 3G?
If it IS the radio, and I disconnect it, maybe it won't hang on boot. I could get running, root, update the radio image, reconnect the radio.
It's a long shot but what do you think?
In my opinion, you should restore to rc29 nbh and send it to t-mobile for repair..
Related
I had the unofficial wm6 upgrade on my device for a while and i wanted to unlock it so i used the unlocker program provided here and i could not get past the second step it kept giving me this really long erorr every time. I downloaded the real ATT wm6 upgrade and it erorrs out after the phone resets to the color screen boot loader, i tried the SD card method and the bootloader won't boot from the card. The card is formatted in fat 32 and i downloaded the official sd card setup and also tried the cheeimg.nbh method. The phone is stuck with no ability to be flashed, i tried all the versions of wm6 on here and i get stuck at the bootloader every time nothing happens. PLEASE PLEASE can somebody help me? All I want to do is put the factory wm6 on that just came out.
I flashed using SD method but It still read v2.23 so i used the palm Updater, same thing with me it would get to boot loader then stop and I noticed that the Palm update program would crash, I tried several times but same thing happened. I finailly went to another PC installed AS 4.5 got that working then tried the Palm updater again (edited the payloads file) and i guess 3rd time was a charm up date took that time.
Is your device currently functioning at all or??
I would try another PC if you can run the palm updater and remember to edit the payloads.xml file.
If your going to use the Palm Updater take out the SD card and leave it out just to be safe.
vista
yeah my device works but the radio isn't right due to the unlock tool failing and whatever other error the ungrade has cuase by not finishing 5 or 6 times.... I'm using vista, but shouldn't the sd card method work? when i enter bootloading via ptt button and reset it flashes for a nano sec a white loading screen then goes to color screen and sits there, i mean it flash's by super fast you have to be watching it without blinking to see it. you think the pc update will work if i go to a win xp computer?
Dam honestly I dont think the swapping PC will help you I think the Unlock fugged up your device somehow by not finishing the unlock process.
But yes the SD method should work. Im no expert in this but i havent bricked my device yet. You may have to call att, but dont tell them you tried to unlock it nor that you have a hacked WM6. just tell them you tried to flash with the latest up date and my device get stuck...in other words LIE so they send you a new device. If you are able to get a new device from ATT I
would screw up your current one so it doesnt load WM at all so they cant check the Version on it. in any event GL.
Now your sure your SD is fat32 formatted?
format
yes i'm sure it's fat 32, i can prolly get a replacment but it will be a referbished one. Yay then it will have some other problem.... oh well thanks anyway, i shouldn't have tried to do the unlock. don't know why it didn't work everybody else says it was easy.
for sale
Know anybody that might want it, that might fix it? it works just need a radio update i guess. $120.
not off hand no, you can try ebay.
warranty
ok i got a replacement phone coming via warranty, How would i go about messing it up so it won't boot windows????
I decided to try and root my stock G1 this morning. The bootloader does not allow me to flash down to RC29. It gives the "Update Terminate" after it fully flashes it, but before it checks the flash. Then it only loads into the bootloader and stops.
However i just successfully flashed to RC30. None of the guides on here specify that I had to load another spl or bootloader first.... Am I missing something?? Thanks for your help.
Bootloader:
DREA100 PVT 32B RUUNBH
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
SEP 2 2008
Solved!!!: Apparently I was on the right track. My US T-Mobile G1 was locked somehow to only accept only RC30 and above. I made a goldcard for my SD card and the image no longer failed (same sd, same image file) at the flashing the .nbh. If anyone has been having issues flashing a US G1... try a goldcard... It instantly fixed the problem! I guess its not only for German and UK?!
BTW.. thanks to pk at codeandroid.org for his guide to make the goldcard without a WM device or linux... http://www.codeandroid.org/forum/?wpforumaction=viewtopic&t=9.2 (in broken english... lol)
Thanks to Viper and revskills.de for their work on goldcard images
Thanks to JesusFreke for this bada$$ ROM (1.5)
Thanks to Haykuro for his android 101 guide.
Great work everyone really...
you need to make sure that your sd card is formatted fat32 and checksum on the DREAIMG.NBH
then try again. should work.
thanks for replying did that. The md5 checksum matched perfectly I have 3 different sd cards all formatted in fat32 only. still no go. I have tried 3 different links to the dreaimg.nbh. made sure it was in all caps and everything. nothing.
It will find the file.
It will flash the file to 100%.
When it would normally check the integrity of each portion it says...
"dreaimg.nbh - FAIL"
"Update Terminate"
"Update FAIL".
The odd part is it will flash the RC30 nbh just fine... same sdcard, same instructions.
try a different sd card- my stock one didnt flash either, same error over and over.
use this nbh -
http://www.mediafire.com/?sharekey=78b87e4b3d9bce857f7ec40ada4772a691de501fd3b9a6eb5be6ba49b5870170
tried all 3 cards with your file. same thing. Why will it so willingly let me flash rc30 the exact same way?
you got me.....
this was the confusing part. so im sitting on rc 30 right now for the 5th time. i have had 30 or so unsuccessful flashes of RC29 and EVERY flash of RC30 was successsful... this is my barrier to Haykuros and/or JF roms...
The file names are case sensitive. It must be DREAIMG.nbh . All caps for the prefix, no caps in the suffix.
thanks for your response... i tried both ways. most of my 30 attempts was changing caps... no caps... on file name and extension. reformatting... downloading from new sources... clearing my temp folder so windows wasn't transferring the same file every time since they are names the same (trust me windows does that with same named and same sized files...)
The only thing I can come up with is a modded bootloader. My G1 is not the one i had from launch date... so this phone never had any lower than RC33 (got the phone 5 weeks ago, came pre-loaded with RC33). This maybe one of T-Mo's tactics in the "War on Root".
That may not be the issye... I had RC30 when I bought the phone. I was able to get to RC29 with no issues... I don't think tmobile did anything to the phone.
i wish it wasnt but how can this phone reject rc29 but accept rc30. does anyone have a rc28, rc19, or below .nbh?
Can you try flashing the engineering Bootloader or HARDSPL first, then fastboot?
I'm not sure if you can use those without having root first though.
ICBM said:
Can you try flashing the engineering Bootloader or HARDSPL first, then fastboot?
I'm not sure if you can use those without having root first though.
Click to expand...
Click to collapse
no i cant. from what i've seen the first step to installing any bootloader is accessing SU... which is root... which means i'm shot down again... getting depressed.
Has anyone tried loading HardSPL without root?
crushsuitandtie said:
no i cant. from what i've seen the first step to installing any bootloader is accessing SU... which is root... which means i'm shot down again... getting depressed.
Has anyone tried loading HardSPL without root?
Click to expand...
Click to collapse
You are right, you need root to be able to load a different boot loader. I got a replacement sent to me from T-Mobile with RC33 on it maybe 3 weeks ago and i had no problems with obtaining root. If i were you i would call up T-Mobile and tell them the Menu button is not working every time on your replacement. They may send you an express replacement...
makes me wish i had kept my launch phone... I got it with RC17 or 18... but i remember getting rc19 ota... this sucks. The only reason i traded it in is because GPS wouldnt ssync anymore unless i did a wipe... so i knew it was a software problem... if i had just rooted it I bet i wouldnt be in this crap. i couldbe on haykuros... right now...
Sounds like a hardware issue to me. The data from the SD card isn't being written to flash properly so the SPL can't verify it. I would try calling T-Mobile to see if they can send you another unit. Obviously don't tell them you tried to flash an unsupported ROM, just make up a story and they will likely believe it.
Just to exclude the obvious. Shouldn't the file be called DREAMIMG.nbh not DREAIMG.nbh as you've written.. Or is that just a typo in your posts?
crushsuitandtie said:
thanks for your response... i tried both ways. most of my 30 attempts was changing caps... no caps... on file name and extension. reformatting... downloading from new sources... clearing my temp folder so windows wasn't transferring the same file every time since they are names the same (trust me windows does that with same named and same sized files...)
The only thing I can come up with is a modded bootloader. My G1 is not the one i had from launch date... so this phone never had any lower than RC33 (got the phone 5 weeks ago, came pre-loaded with RC33). This maybe one of T-Mo's tactics in the "War on Root".
Click to expand...
Click to collapse
ok i received my phone like a month ago an it came with Rc33 install and my phone when try to flash Recovery, i get a error EveryTime, look at all My Topic you see
I just keep on trying and i get it on my 7th try lol I'm not lien
bp8575 said:
Just to exclude the obvious. Shouldn't the file be called DREAMIMG.nbh not DREAIMG.nbh as you've written.. Or is that just a typo in your posts?
Click to expand...
Click to collapse
The correct image name is DREAIMG.nbh. looks wrong but its right... I think it IS a hardware issue. The is writing but not verifying certain images... and its now giving me checksum errors on rc30 after 8 successful loads, but when i retried without doing anything to the file it completed. I would say its my card but I have 3 different cards...
bump for anyone else having trouble...
First of all please be gentle! I am a complete novice and this is my first post. I have a Touch Pro on a Vodafone contract. I downloaded the recent ROM software upgrade from the Vodafone web site and began the transfer to my phone having followed all the advice. However, the download got stuck at 12% and no matter how many times I start over again it will not go past that point. Worst still the phone is now locked on a red/green/blue/white screen with the message "Upgrade ROM code error Please try again". the error message on the Vodafone software download is No 302. I have tried Vodafone technical help but as I was due for a new phone anyway they have sent me a Touch Pro 2 but don't seem to want to help me resolving the problem with my "old" phone. It is only 5 months old (replacement insurance phone) and in good condition but useless if it can't be made to work.
Can anyone help with simple instructions on how to download a ROM that will work. If not does anyone want to make me an offer for the phone? Currently locked on Vodafone but I am sure you guys out there have the skill to resolve that one.
Many thanks,
Hollybeau
So, they aren't asking you to send it back, I take it? If that's the case, then the first thing I would try would be to flash with the stock rom, if you can find it (not the upgrade that quit on you). If that doesn't work, then just try to flash hard spl. If hard spl goes through ok, you're golden and can flash any raphael rom you want. If it doesn't, the phone is probably toast. You got a new one, so just use the old one as artwork.
Thanks Farmer Ted,
Unfortunately I do not know the orginal stock ROM. It is not on the Vodafone web site and the HTC site keeps telling me that all the likely candidates are "not suitable" ( I assume this is beacuse it is some sort of Vodafone variant). I am afraid that "flash hardspl" means nothing to me - I told you I was a novice! Can you direct me to what and where please.
What bugs me is that here is a phone worth £200? but for a problem caused by Vodafone's buggy software upgrade.
Hollybeau
Start Here.
Best way to find everything you want to know about flashing ROMs.
Lol.
Hard SPL is a bootloader that allows you to flash any rom you want (not just vodaphone). It also has over-write protection, so if you get into the situation you're currently in, the phone won't be bricked. If you can flash it (make sure you flash the gsm version in the raph rom forum), you are fine and dandy.
If you can't find the stock rom online, you may be able to flash the upgraded rom off of your sd card (I believe this will work with a stock rom and stock spl, but am not 100% sure). Re-name the .nbh image file to RAPHIMG.nbh. Format your sd card (1-2 gb works best) to FAT32, and put the image on the root of the card. Go into bootloader (well, you're already there, you may not need to) by holding volume down and soft resetting. Hold vol. down until the tri-color screen appears. At the prompt, press the power button, and let the flash run its course. Soft reset when it says that the update was a success. Let the phone boot up until it gets to the the alignment screen, the hard reset and boot it up.
If you don't have an .nbh file, and instead have a .exe file from vodaphone/htc, then you should be able to extract the contents with either winrar or 7-zip (google) to get at the .nbh image file. I've done this before, and it works fine.
Many thanks to all who have replied. I have fixed the problem. It turns out that it was the download to my PC that was at fault. I downloaded the Vodafone software to my lap top and ran it from there and it has recovered the phone. I now have a spare, and working, Touch Pro. I may try the HardSPL and other ROMS just to use the phone as a test bed. Alternatively, anyone out there want to make me an offer?
Hollybeau
Hollybeau said:
Alternatively, anyone out there want to make me an offer?
Click to expand...
Click to collapse
Ask in market place and you will probably get some takers
G1 DREAM (really is a dream, right now, a little bad one a little embarrassing)
been 5 mos since I took root via Cyanogenmod's latest G1 stable and last theme was PHRASh Then I thought about checking out
some other themes and clockwork orange caught my eye... Orange is my favorite color, so wehen I saw there was some Orange theme I must've had a dare encounter with myself-- i recall actually installing the Orange theme..... when i asked the phone to flash the theme, it went into permanent G1. Gave it about 12 minutes. Rebooted into recovery (home menu power) and then did what I think got me in deep droid doo doo -- I attempted to restore to my last backup whch was the day before (and ironically the BEST backup i ever made I had it all humming so nice and fast) Guys -- instead of hitting restore to last backup... I actually hit nandroid backup. I know. That was a really bad day and its been a worse 50 hours. I know -- and Ive learned -- OK?
Since that time.... 50ish hours Ive lost track of what Ive done, but its a potpourri
bootloader is dev spl skateboarding, recovery is Cyanogenmod JesusFreke 1.4 recovery.
DREAM DREA100 PVT 320
HSPL10.95.3000
CPLD-4
RADIO 2,22.19.361
OCT 29 2008
SERIAL0 -- (fastboot i have fastboot as well)
at first flash of bootloader it says "NO IMAGE FOUND!"
If I press Home when it restarts in perpetual cyclical hell I get into CMJF recovery. I have executed every single option numerous times -- and have not been able to successfully flash anything else -- and now I dont know WHAT to flash. I even tried to go back to root!
If I dont press Home or Camera, I get this....
the awful permanent G1 screen. Forever and ever.
I have Wiped backed up, tried to get update.zip and just about ANYTHING into my sdcard but I dont think they have been successful installations to flash. I am not ADB enabled yet. Surely someone knows what this is all about and I am willing to take a flame for posting in the wrong forum if I can get something out of this, I will pitch in later and help y'all keep these forums in workin' order!
every optioon on the recovery screen which is recovery CM and JF 4.2
When I try to load files according to the instructions in xda and cm i cannot get it in fast enough on the g1 running on the frozen G1 screen because I dont known the time of mount the SDCARD has and when it begins (I know it opens for a while and then closes)
So i got droidexplorer and its almost impossible to get the file in there. I can get it in, and see it, and reboot the phone (and computer)( restore usb connection and I see the update.zip on the sdcard. Then I unmount the phone and reflash and it says something about not being able to find the file.
Whats next? Please dont assume I know what I am doing, I am sure you can tell -- but I am really good at following instructions!
Hello anyone?
I have been up all night trying to fix this phone and i am still not able to do so. I
I cannot get into recovery anymore ------
i am stuck on the hardspl and I have found fastboot again. But I cannot use frastboot if I cannot get any commands into it. Anyone?
ok i get it -
thanks for the help guys! I now have my phone working at a blitzing pace and i am leaving it alone for now. I dare myself to leave it unchanged for a week. Thanks mostly to one of the Dudes on Cyanogenmod.com -- who helped me piece together the missing parts.
Actually -- let me summarize even if only I am reading this
Androids levels of defenses are 1. HardSPL 2. Recovery and 3. normalcy. Lose normalcy (Ok, a beauty of a ROM) you have recovery to get the ROM back -- but the trick is -- can you get the necessary IMG file on your SDcard to update.zip with? Can you figure out ADB and push the update.zip? Can you figure out Fastboot and what it REALLY does and what you can and cannot do with FB? If you can do any of these or FB with ADB, then you have a good chance. Just dont lose the HardSPL. If you give up after frustration and while grinding your teeth waving a white flag, flash the DREAIMG.img file, then you have given up root and FB. But at least you are at RC29, the level where the froot can be found. It is weird hanging out in Android 1.0 lemme tell ya. Feels so 1980'ish with bellbottoms in late decline.
But now its android time at CM with Phrash.
Later
ROGERS RUU RECOVERY METHOD FOR ROGERS EVO 3D PHONES
Hello, I am new to XDA and I don't know much about rooting, but unlike most noobs, I am not here to ask for help.
A few days ago I was trying out rooting and was pretty pleased with what I could do, so I went ahead and tried to flash my stock rom to VIPER rom. This did not work as planned, as I tried to flash my phone with a CDMA rom, and not a GSM rom. My phone is a GSM phone. This obviously left my phone hanging at the HTC screen, and I thought I wrecked my beautiful 500$ phone. After 5 hours of frantic research, at 3 o'clock in the morning, I discovered something called an RUU. Unfortunately, most of them were for US phone providers, and me being from Canada, I had a rogers phone. After trying a few(and failing), finally, I found an RUU that could work, but it was an executable, and would not connect to my phone. As I had access to REVOLUTIONARY, I could still access my files on my sd card, and wondered if I could extract the PG86IMG.zip and put it on my sd card to do a factory reset and reinstall everything. Luckily, it actually worked and my phone was brought from the dead and ran as if I just bought it.
So in the next few posts I will explain how to do it for the few who are in the same situation as me with a ROGERS EVO 3D. This most likely will not work for any other phone. It might work for another supplier's GSM EVO 3D, but I have not tested it and I don't recommend it unless you have nothing else to try or you really want rogers bloatware.
Procedure
PROCEDURE
This procedure SHOULD work if you have a ROGERS EVO 3D phone, as I imagine they are all the same. However if it doesn't, you must realize that you are doing this at your own risk and I am not responsible if your phone gets damaged in any way.
NOTE: This will set the phone back to its original state when you first bought it.
If your phone was SIM Unlocked, it will not remove the Unlock.
1. Make sure your phone is charged. I don't know what could happen if you run out of juice when flashing back to stock ROM but I don't want to and I have a feeling that neither do you. Just leave it plugged in to the wall for two hours just to be safe.
2. Before you do anything, make sure that you can get into the HBOOT. This is fairly easy, just take out the battery, put it back in and then hold both the power button and the volume down button until the HBOOT shows up. If it does show up, great, shut off your phone and move on to the next step. If it doesnt show up, keep trying. After 3 tries if it doesnt work, there are three reasons for this.
A) Your phone isn't charged. Plug it into the wall for two hours.B) Your HBOOT is screwed up and you cant reach it. I can't help you with that. Look somewhere else or take it in to your warranty/provider.C) You are having hardware problems. Faulty battery, phone charger not working, power button not working, volume button not working, all things you might want to check if you can. Look somewhere else or take it in to your warranty/provider.
3. Access your/a microSD. You might have noticed when you went inside your HBOOT that it was searching for a file. That file is actually the file that we need that will allow us to reset the phone to provider default. There are two different ways to access this.
A) Take out the card and connect it to the computer using a adapter. This is probably the easiest way and is almost guaranteed to work.
B) Since you have rooted your phone (and are in this unfortunate position) you might be familiar with a tool called REVOLUTIONARY (Previously called ClockWorkMod). Note this is only available if you have REVOLUTIONARY installed. You can access it in the HBOOT by scrolling down using the volume buttons to RECOVERY, hitting the power button to select, in REVOLUTIONARY going to mounts and storage and then select mount USB storage. Connect the usb adapter in both your phone and in your computer. It will show up in My Computer as if it is a flash drive. I used this method.
4. Download this file: http : //www . filefactory . com/file/49tsgwxc6bd3/n/FACTORY_RECOVERY_File_For_ROGERS_EVO_3d_zip (Remove the spaces. I am not allowed to post links till 8 posts in total so I must do this.)
Mirror:
5. Put the attached file onto the hard drive. Extract the "FACTORY_RECOVERY_File_For_ROGERS_EVO_3d.zip" and place the "PG86IMG.zip" on the root of the microSD. Plop the card back in the phone, turn off the phone once again and re-enter into HBOOT. The phone will find the PG86IMG.zip file and then ask if you would like to update. Scroll to yes, press the power button to select it, and watch. This process should take up to 3 - 6 minutes.
6. Once everything is said and done, it might reboot, but if it doesn't you can reboot it yourself. Start up your phone, and watch in amazement when your ROGERS screen appears and the phone comes back to life.
RE-ROOTING
This guide is pretty much a slightly modified version of zedomax's guide on youtube, and should work for any CDMA phone (but I can't confirm it) and certain GSM phones, including Rogers.
Re-rooting is a bit more sketchy as rooting for the first time (at least it was for me).
This guide is only for windows computers (Since the mass population of people only use windows, and if you have a mac, you probably have an iPhone. If you have Linux, you probably know how to make a unicorn pop out of the phone, so you don't need a guide.)
Before you do anything, you need to check the HBOOT version. This is absolutely crucial. Some HBOOT's are not supported, so if you try with the wrong HBOOT, you might totally destroy your phone. For good this time.
To be continued...
I realise that there may not be many people in the same position as me for a while, so feel free whenever to send me a message if you need help. I will most likely keep the files for a few years on my external hard drive.
Android 4+ after recovery
Hello!
Is this a recovery for Android 4? If not, were you able to update back to 4 after recovery?
mike134981320 said:
Hello!
Is this a recovery for Android 4? If not, were you able to update back to 4 after recovery?
Click to expand...
Click to collapse
No unfortunately, but then I didn't attempt to fix it either. I just stayed with the stock OS because I didnt feel like I needed to update it that badly.
Link is dead
The link is dead, could someone please post a mirror? Thanks!
EDIT:
Found a copy and mirrored for anyone else:
http://shipped-roms.com/download.ph...00U_11.25.3504.06_M_release_262715_signed.exe
djparent said:
The link is dead, could someone please post a mirror? Thanks!
EDIT:
Found a copy and mirrored for anyone else:
http://shipped-roms.com/download.ph...00U_11.25.3504.06_M_release_262715_signed.exe
Click to expand...
Click to collapse
shooter v pvt ship s-on rl
hboot 1.53.0007
emmc-boot
may 22 2012
is what i have in hboot
update failed
main version is older