so i spent the better part of the day trying to get my Photon unlocked so i could run CM9 on it... but didnt happen. I have been running stock rooted for a while, so i thought that i would just follow all the steps in Loki's post, the Compendium.
When I tried to flash derpUnlock.sbf in RSD it would fail with this message... "The "secure_motorola_flash" interface could not be found the super-file is secure and for re-flash, the phone needs a super-file that is not secure and for reflash. (0x7066)"
I tried two different versions if RSD, tried all the USB ports on my computer, tried rebooting the comp, SBF'd with the 198_7 and then back to 198_6 but neither worked... I completely killed my battery three times today trying this, but never got past that error with DerpUnlock.sbf....
any ideas?
That's strange. When I unlocked I used the same method and had success first try. Because it was ny first time unlocking my MoPho I watched qbking's video and used the download links referenced in his thread.
I'm a MoPho-er
I tried that to, but thanks to Sopa killing a couple download sites a lot of the links referenced are no longer working...
schollianmj said:
I tried that to, but thanks to Sopa killing a couple download sites a lot of the links referenced are no longer working...
Click to expand...
Click to collapse
I believe the sbf flash always fails it did for me I just continued with the rest of the steps and I was unlocked but if your phone bricks don't blame me
Sent from my MB855 using XDA Premium App
I found this in The2dcour's post....
the2dcour said:
1) Don't panic.
2) Stop panicing.
3). If you get the following error messages, try restarting the flash process from the start:
- The "secure_motorola_flash" interface could not be found the super-file is secure and for re-flash, the phone needs a super-file that is not secure and for reflash. (0x7066)
4) Just try and go through with the unlock process anyhow
5) Try a different USB port, this is most likely because windows will reinstall all the drivers.
6) Try a different version of RSD Lite.
7) Make sure you put your phone in to USB NONE before plugging it back in. If you do not do this your system will not install all the devices correctly. Alternately, try Motorola Phone Portal mode.
8) Last resort PM me with very specific information about your problem and if applicable screen shots from your computer or phone.
Click to expand...
Click to collapse
this is whats happening to me. it is NOT unlocking or getting to the point where I can use the fastboot commands...
If you didn't follow the instructions exactly something went wrong. Here is what I suggest:
- Charge your phone all the way
- factory reset
- boot into rsd
- sbf to 154_5
- let the phone update automatically to 198_6
- unlock using derpunlock.sbf after
Sent from my MB855 using xda premium
same here
Also tried unlocking my MoPho to no avail. Getting the same error message. I have just tried a factory reset and got exactly same results after factory reset.
I was on stock ROM, just rooted my phone.
After reset have to take away the battery to do anything to the phone. Is it the same for you?
Well, after studying the topic on unlocking the phone, I tried to continue with next step (boot in fastboot) and I was able to unlock the phone. Looks like this error can be [safely] ignored.
SAME HERE!
I get the same error message...I'm trying to flash back to _5, and update to _6... Hopefully that helps. Hopefully something comes of this cause I wanna push this Tegra2 to the limit!
You don't need the derplunk file, just get you device I'd through the boot menu options then choose rsd mode, from there type fastboot oem unlock, then it warns you about your warranty, then you type it in again with the device is and your done. I've done it to 3 photons and it's the simplest way, just like to xoom
Sent from my MB855 using xda premium
Yeah, I was getting errors, too and said screw it. I turned my Photon off and held power button + Volume down until it prompts you. Press volume down to scroll through til you see fast boot. Then finish the tutorial starting with "fastboot OEM unlock"
Sent from my Motorola Photon running ICS
JamesChilds said:
Yeah, I was getting errors, too and said screw it. I turned my Photon off and held power button + Volume down until it prompts you. Press volume down to scroll through til you see fast boot. Then finish the tutorial starting with "fastboot OEM unlock"
Sent from my Motorola Photon running ICS
Click to expand...
Click to collapse
Typing on the phone? Because stock on starting service
Sent from my MB855
FernBch said:
That's strange. When I unlocked I used the same method and had success first try. Because it was ny first time unlocking my MoPho I watched qbking's video and used the download links referenced in his thread.
I'm a MoPho-er
Click to expand...
Click to collapse
I also followed QBKings videos to do mine. When I got to a file that wouldn't download I just Googled and searched this forum until I found an exact match. And I probably still have all the files, so let me know if you need them.
Sent from my CM9 Photon using SwiftkeyX on xda premium
Yea, i kinda gave up on unlocking... few different people sent me the files they used, but I get the same error on all of them.
Related
my recovery never loads through.
Its there. however it sits on the dual core technology screen when plugged into the wall. i even tried the battery-less plug into wall -- trick, it is still sitting at that screen.
its been roughly 3 hours - i'd assume it should have gone through by now.
that aside the rom boots however it is at the initial setup page and doesn't allow me to process the initial setup due to spam force close.
i have the sbf file and know how to use it, what i don't know how to do is get my phone to allow me to use the sbf file when i can't control it. the phone can't be in charging mode without something ignoring the force closes briefly.
i had read somewhere to use launcher pro, using the "hold search and say the command"
it doesn't seem to do anything no matter what i say nor how long i hold it for.
So if my phone is completely screwed thats that. i guess it comes down to are there any options i haven't exhausted yet?
or. can you switch charge only mode through some other means other than the soft key press in a menu i can't access?
EDIT: i looked through a couple of the options in the regular recovery. BP SW Bypass RSD is at the moment letting me see it to use RSD on it. hopefully meaning i can just sbf and move on.
EDIT: Failed flashing process. Unable to retrieve initialization value from INI file (0x7029)
bah just when i thought i had something.
You have to hit INSTALL RECOVERY before you go into recovery mode.
Sent from my DROID X2 using XDA App
i did hit install recovery, this is how i installed the rom - eclipse 0.6 from sd which caused all of the problems in the first place.
I think you have to use the plain RSD mode not the one you are using.
Also the voice search thing is just to kick you into the browser so you can backdoor into the market and install a launcher. I installed zeam that way and I was off to the races.
Sent from my DROID X2 using XDA App
jeffgarret, i attempted this as well and i'm getting the same problem. it can't read my ini file or something of that nature...
Code:
Failed flashing process. Unable to retrieve initialization value from INI file (0x7029)
this is what it gives me for both modes.
i get this error before the above error (before i actually "start" it)
Code:
Chipset type 53 is not supported
I would try re-downloading the sbf file in case something is buggered with it. Also I believe it is zipped. Regardless of what zip program you have, download and use 7zip for it.
ryokox3 said:
I would try re-downloading the sbf file in case something is buggered with it. Also I believe it is zipped. Regardless of what zip program you have, download and use 7zip for it.
Click to expand...
Click to collapse
so what you're saying is -- what i'm using should work, but isn't due to some random issue somewhere....
Every time I flashed a rom I had to hit install again or it would sit at Motorola logo forever
Also that sbf error definitely sounds like you need to use 7zip like
other guy said. I tried winzip, winrar, and gzip and had errors with all 3, other people say they work but 7zip works for everyone
Sent from my DROID X2 using XDA App
i used universal unzip before (which acts sort of like 7zip... only different)
EDIT: it seems RSD is still giving me the same errors:
freshly downloaded sbf and i even used 7zip.
which probably means the error is actually the real error. so something is messy with my ini ... or something
P.S. i did use it as administrator (every time)
Can you get the rom to boot now? If not can you get to stock recovery and wipe everything then try to get the rom to boot.
Also you may know this but if you are on a desktop sometimes you have to use the back usb ports to RSD.
Sent from my DROID X2 using XDA App
Sometimes the drivers don't install right, I didn't have that problem but some people have uninstalled and reinstalled the driver when they get errors and it worked for them. What version of rsd are you using? I think 5.3.1 is the one I used. There are newer versions but I havnt used so I can't say if they work.
Sent from my DROID X2 using XDA App
Are you using power and volume up for RSD MODE on ur phone? I believe that is the way you need to do it. That is how I always have. And like evil Tim said. If u r using the newer RSD lite floating around then try old faithful 5.3.1
Sorry if my suggestions have been tried or mentioned. Its all I can think of for now
going to attempt your different version of RSD lite.
heh... i was using 4.8 from back when i would restore my Droid X
hopefully this is the final step i need to do...
EDIT: well it has started the process, i'd imagine i'm good to go.
i was able to get it into charge mode by restarting my phone a bunch of times and one of the times it happened to let me scroll the notification bar down (usually its blocked by the initial setup)
Thanks for everyone's support and ideas, i thought i was out of luck; but it looks like its all good.
Glad to hear it !!!
Thanks for the report back. I was wondering how ya made out.
Im assuming it was the RSDlite version that changed the outcome? Or was it u being able to get charged?
---------- Post added at 01:17 AM ---------- Previous post was at 01:10 AM ----------
SubVirus said:
going to attempt your different version of RSD lite.
heh... i was using 4.8 from back when i would restore my Droid X
hopefully this is the final step i need to do...
EDIT: well it has started the process, i'd imagine i'm good to go.
i was able to get it into charge mode by restarting my phone a bunch of times and one of the times it happened to let me scroll the notification bar down (usually its blocked by the initial setup)
Thanks for everyone's support and ideas, i thought i was out of luck; but it looks like its all good.
Click to expand...
Click to collapse
So far I have yet to see someone HARD BRICK their x2. I can't see it happening unless it's someone messing with bootloader partitions and signature and such. Though I've read that sbf isn't really a FULL partition included. I was a bit thrown off at how after I sbf first time when I complete deleted my build.prop and other things before I knew better, that I had the same wallpaper as before sbf. Lol
It was the version of rsdlite more than the getting it back to charge mode. Basically eclipse remix had a bug in their initial setup (which has been fixed) I just had all sorts of little problems here and there such as having the older rsdlite which I hadn't even thought about updating.
Sent from my DROID X2 using XDA App
YET ANOTHER UPDATE 1/9/2012:
MAJOR SUCCESS VIA THE FOLLOWING LINK: http://forum.xda-developers.com/showpost.php?p=21015556&postcount=6
THIS IS ACTUALLY A US CELLULAR SBF FLASH BUT I SUCCESSFULLY FLASHED THAT FILE TO MY PHOTONSTEIN AND MANAGED TO GET BOOTED ALL THE WAY INTO THE ANDROID/GOOGLE SETUP WIZARD.
NOW I AM ATTEMPTING TO FLASH A SPRINT 198_7 SBF.
UPDATE 1/9/2012:
I RECENTLY PURCHASED A EVO 3D FROM CRAIGSLIST TO REPLACE MY PHOTON. THEREFORE, I WILL KEEP MY PHOTON AS A LAB MOUSE TO TRY TO GET A HEART BEAT BACK INTO IT. THANKS FOR ALL THE EFFORT TO EVERYONE! I WILL KEEP THIS THREAD UPDATED UNTIL I EITHER GET MY "PHOTONSTEIN" WALKING AGAIN OR BURRIED IN THE BONE YARD WHICHEVER COMES FIRST.
UPDATE! I have had successful communication with the photon through android-sdk. I don't however have the correct img file to flash to the phone. Does anyone have any ideas?
Okay, I know I am somewhat of a newbee at this. But I followed all the steps and wound up with a brick. All I get is "Failed to boot 3" then "Starting RSD mode".
I tried flashing the "1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US.sbf" and it fails telling me that it failed to re-enumerate.
Am I screwed or does anyone have a suggestion?
Thanks.
try flashing the 198_7 sbf on rsd 5.5
Sent from my MB855 using XDA App
Jmaserang said:
try flashing the 198_7 sbf on rsd 5.5
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Thanks, I'm downloading now. I will repost if successfull.
treetolber said:
Okay, I know I am somewhat of a newbee at this. But I followed all the steps and wound up with a brick. All I get is "Failed to boot 3" then "Starting RSD mode".
I tried flashing the "1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US.sbf" and it fails telling me that it failed to re-enumerate.
Am I screwed or does anyone have a suggestion?
Thanks.
Click to expand...
Click to collapse
You may wish to consult this thread and completely read/watch everything.
http://forum.xda-developers.com/showthread.php?t=1250697
You may also want to reinstall the drivers for your photon. I had the same problem and a quick driver reinstall fixed it.
It appears that I have either damaged or deleted the bootloader. Sprint won't touch it with a 10 foot pole. Does anyone know how to get the bootloader back to the device?
I am able to connect to it with RSD Lite but I can't flash anything.
treetolber said:
It appears that I have either damaged or deleted the bootloader. Sprint won't touch it with a 10 foot pole. Does anyone know how to get the bootloader back to the device?
I am able to connect to it with RSD Lite but I can't flash anything.
Click to expand...
Click to collapse
Are you still getting "starting RSD mode"?
If you are, I think you're safe. I guess you're one of the many of us who flashed 2.3.5 pudding into their Photons. If that's the case you can follow a small tutorial i did here:
http://forum.xda-developers.com/showpost.php?p=21015556&postcount=6
Give it a shot and let me know how it goes.
You shouldn't need the bootloader at all actually. I had the same issue with my phone. I had to remove the SIM card and the SD card. Then when you put the battery back in Hold down the Power button and the Volume up button until it says RSD lite mode or something along those lines. Then connect it to your computer and run the RSD lite and select the proper factory ROM that you need to install back on your MOPHO. You will lose root access but your phone should be right back to all of the factory settings. I have done this multiple times to fix error that I got because I am new to Rooting my device and everything as well. I will give you links to where I was able to find some addition support as well.
http://forum.xda-developers.com/showthread.php?t=1373135
http://forum.xda-developers.com/showthread.php?t=1202666
If all else fails call sprint and ask for an advanced exchange from tech support
Sent from my MB855 using XDA App
treetolber said:
Okay, I know I am somewhat of a newbee at this. But I followed all the steps and wound up with a brick. All I get is "Failed to boot 3" then "Starting RSD mode".
I tried flashing the "1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US.sbf" and it fails telling me that it failed to re-enumerate.
Am I screwed or does anyone have a suggestion?
Thanks.
Click to expand...
Click to collapse
Where do you find build 154 for the photon?
Sent from my Nexus S 4G using Tapatalk
Has anyone had their photon just show the pulse Motorola logo and the power cycle it self back to the same screen?
Sent from my Nexus S 4G using Tapatalk
Wow there's been a **** ton of threads with "bricked" in the titles lately what are you guys doing lol.
Also not to be a douche but this isn't development. This thread should be in general or q&a next time.
I had the boot loop prob pwr+vol down get to stock recovery and wipe the phone worked for me
Sent from my MB855 using XDA App
TheGman125 said:
Where do you find build 154 for the photon?
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
I'm not sure. I followed a link somewhere in the threads on this forum.
firtermish said:
Are you still getting "starting RSD mode"?
If you are, I think you're safe. I guess you're one of the many of us who flashed 2.3.5 pudding into their Photons. If that's the case you can follow a small tutorial i did here:
http://forum.xda-developers.com/showpost.php?p=21003839&postcount=9
Give it a shot and let me know how it goes.
Click to expand...
Click to collapse
Well now my battery is dead and I don't have any way of charging it unless I take it to a Sprint store and have them charge it over night.
Thanks for all the help!
treetolber said:
Well now my battery is dead and I don't have any way of charging it unless I take it to a Sprint store and have them charge it over night.
Thanks for all the help!
Click to expand...
Click to collapse
You can cut the end off of a charger strip the wires red on pos+ black on neg- and plug it in but don't leave it on longer than 20 min at a time cuz battery might over heat
Sent from my MB855 using XDA App
I can start the flash process but after a while the following message appears on the screen of the Photon: "sec_exception: b655, eddt, eb".
Then the flas process out and displays the following:
"Failed flashing process. Phone(000): Phone did not re-enumerate after RAM-downloader was sent. (0x703E); phone connected.
Has anyone seen this and recovered from it?
P.S. This is all with or without the SIM card and SD card inserted or removed.
TheGman125 said:
Where do you find build 154 for the photon?
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
ShabbyPenguin has critical photon files hosted (and linked in his signature)
Photon Files
Download RSD Lite and 198_7 SBF from.
http://www.holylivingfuck.com/ACS/SBFs/
You should read this thread on more information about 198_7
http://forum.xda-developers.com/showthread.php?t=1202666
Make sure you have proper USB drivers for OS 64 or 32 bit installed, install RSD lite and follow the directions below.
Make sure your battery is greater than 50percent before doing any of this.
1) Fire off RSD lite, select the SBF you need 198_7 .
2) Hold down power and vol up till RSD mode comes up
3) Plug into usb then start the flashing sequence.. ( the whole process will take a while)
4) The process is done when RSD lite says manually power up the phone.. You may need to take the back off and pull the battery to restart it incase it doesnt power up on its own.
I wonder if you downloaded an incomplete sbf. Try flash 198-7sbf one more time or see if you can enter android recovery and wipe. Also. Check the motorola driver is installed correctly.
Sent from my Motorola Photon using XDA App
I have a motola photon that I believe is bricked due to and attempt to flash the electrified 2. 3. 5 without doing my research. The bootloader is unlocked but every attempt at a fastboot command freezes at waiting for device. I've flashed every sbf under the sun threw rsd with failure at the phone "re-enumerate" stage. I'm so stuck and very confused.. ive been using this stuff since my Android Leo, g 2 and many more.
ashirback said:
I have a motola photon that I believe is bricked due to and attempt to flash the electrified 2. 3. 5 without doing my research. The bootloader is unlocked but every attempt at a fastboot command freezes at waiting for device. I've flashed every sbf under the sun threw rsd with failure at the phone "re-enumerate" stage. I'm so stuck and very confused.. ive been using this stuff since my Android Leo, g 2 and many more.
Click to expand...
Click to collapse
If you flash a 2.3.4 Locked sbf via RSD after the flash failure what does the wcreen on your phone say?
I think I am in a similar situation but found a way to unbrick.
Failed flashing process. Failed flashing process. Phone [0000] "The Secure_Motorola_Flash" Interface could not be found. The super-file is secure and for re-flash; the phone needs a super-file that is not secure and not for re-flash. (0x7066)
The rsd fails at 98% when the phone attempts to switch to a BP passthrough.
Im baffled
have you tried booting even tho rsdlite fails? it "fails" for me everytime nd still boots xD
Sent from my MB855 using xda premium
it's supposed to fail, the phone still boots perfectly and if not try a battery pull or flashing a locked sbf
Guys of course I tried to boot the phone afterwards. It just sits at the Motorola logo, says unlocked in the upper left corner with 0 animation to the logo. I cant get into recovery either.. its back to the stock exclanation point one.
Anyone have an idea of what could be wrong? How am I supposed to do anything to the phone if Rsd continues to fail and I don't have access threw fastboot? Also the phone model in rsd is listed as NS Flash Sunfire, it lists my bootloader as ver v0x000007 but everything else is listed as N/A
ashirback said:
Anyone have an idea of what could be wrong? How am I supposed to do anything to the phone if Rsd continues to fail and I don't have access threw fastboot? Also the phone model in rsd is listed as NS Flash Sunfire, it lists my bootloader as ver v0x000007 but everything else is listed as N/A
Click to expand...
Click to collapse
What happens when you try to force the phone into fastboot mode by pulling the battery, putting it back in and holding the VOL down and POWER buttons?
Well it let's me get into fast boot with no problem after some fooling around today. however when I try to erase my data threw fast boot it says I don't have a product name. The device is listed in fastboot though as TA00.. (don't remember # off hand). I know the values for this is changeable but is it necessary or is that minor in this large issue.
From what you are telling me this should work...
Make sure that your phone says UNLOCKED at the top left corner..
Follow this: Go specifically to the ROOT instructions: and flash the system image
http://forum.xda-developers.com/showthread.php?t=1216143
Please let me know if it works.
That sounds perfect but the link for the system file is down. Anti piracy bull**** government hoopla. GARRRR ! Anyone by any chance have a copy of the file or a mirror to where i cant find it?
ashirback said:
That sounds perfect but the link for the system file is down. Anti piracy bull**** government hoopla. GARRRR ! Anyone by any chance have a copy of the file or a mirror to where i cant find it?
Click to expand...
Click to collapse
After going to the link have you tried the other sites besides mega downloads?
Yea I tried. The file has been deleted or moved from every file site there. =\ I'm going to continue to troll the net after I escape from work tonight. Hopefully with some luck I can find one that someone else has uploaded.
Fastboot attempts to flash the file but it fails stating "INFOImage is too big, use 0x10000000 bytes chunks"
ashirback said:
Fastboot attempts to flash the file but it fails stating "INFOImage is too big, use 0x10000000 bytes chunks"
Click to expand...
Click to collapse
Well!!! did you wipe before you had flashed the 2.3.5 SBF ????
If running in Win 7 make sure that you opened up the command prompt as administrator. Also make sure that you put the system.img in the fastboot folder/directory. So you should be doing:
1. fastboot erase system
2. fastboot flash system.img
3. fastboot reboot
Still wouldnt let me because the system image was too big.
But i managed to flash clockwork threw fastboot and was able to boot that up. I did a factory reset in clockwork rebooted and it was still frozen. But i was able to flash redROCKO 1.1.1 and then it booted and is now working flawlessly.
I've searched this thread, and google with no clear answer as to what to do to solve this problem, a similar thread exists but it looks just like troll answers so here is my issue! I've rooted and installed the CWM but now my Jetstream seems to crash everytime I press the power button to lock the screen, also when the screen locks itself. I've tried resetting to factory settings, nothing works. Any help would be greatly appreciated
Mitchface said:
I've searched this thread, and google with no clear answer as to what to do to solve this problem, a similar thread exists but it looks just like troll answers so here is my issue! I've rooted and installed the CWM but now my Jetstream seems to crash everytime I press the power button to lock the screen, also when the screen locks itself. I've tried resetting to factory settings, nothing works. Any help would be greatly appreciated
Click to expand...
Click to collapse
Are you still on the factory kernel or did you upgrade to the DoomKernel? I found the reboots happened with the DoomKernel but have not had a single reboot since I went back to the factory kernel.
ATT Intruder said:
Are you still on the factory kernel or did you upgrade to the DoomKernel? I found the reboots happened with the DoomKernel but have not had a single reboot since I went back to the factory kernel.
Click to expand...
Click to collapse
Im still on doomkernel, I don't know how to go back to normal, this is my first Android device haha I only got it because it was 169.99 on a one year term since I work for Rogers in Canada. I could fix my iPhone easily but this is proving to be a little more challenging
here's what you need to do:
backup whatever you can
Re-lock the bootloader. (using the instructiones at htcdev.com/bootloader)
download and run the RUU file from htc.com/us
it will update the version of the device and will clear all the data from it, including root access and kernels
now that the device is like new again - root it if you wish to, but do not flash the kernel by doomlord. its not stable.
Okay so to relock bootloader do I just plug it in and go to fastboot and use the command fastboot oem lock? I will try when I get home from work, I tried this before but got an error when I tried to use the RUU installer I cant remember what it was exactly, but ill post results when I have them
Mitchface said:
Okay so to relock bootloader do I just plug it in and go to fastboot and use the command fastboot oem lock? I will try when I get home from work, I tried this before but got an error when I tried to use the RUU installer I cant remember what it was exactly, but ill post results when I have them
Click to expand...
Click to collapse
Correct. Relock, run the Ruu and then root and install the doom recovery. I've done everything but put his kernel back on (not the insecure kernel, that gives you root) and am very pleased with how my Jetstream functions. Still needs a good custom ROM though.
Sent from my SAMSUNG-SGH-I777 using XDA App
Alrighty thanks! Will try it as soon as filefactory lets me download my ROM -.- are there any other download links available because the trouble I have trying to download this is ridiculous I've been trying for 2 hours and I keep getting All free download slots on this server are currently in use.
For immediate access, upgrade to FileFactory Premium. Alternatively, you can try again shortly.
Retry download
it says the rom update utility cannot update your phone please get the correct rom update utility and try again
there is a chance that there are two different RUUs. one for Rogers and one for at&t.
try searching rogers for an RUU..
Mitchface said:
it says the rom update utility cannot update your phone please get the correct rom update utility and try again
Click to expand...
Click to collapse
If you look through the forum you will find a link for the Rogers ROM.
Sent from my SAMSUNG-SGH-I777 using XDA
Ive tried all three roms found in the dev section! The first two were exes and didnt work and when i tried to flash the zip i get an error that says FAILED Remote: 12 signature verify fail -sigh
if u'r having crashes you need to flash the RUU from Rogers. RUU means Rom Upgrade Utility. it's an exe file published by htc/rogers.
you need to d/l the file, connect the device to the computer and run it, after relocking the bootloader.
the ROMs that are in the development section are very raw and pretty much neglacted by now. do not try to flash them, it will probably only make things worse.
Okay, so where would I find the Rom from HTC. I work for Rogers and we do not provide them.
try searching the forum for a rogers version.
if you can't find one - i'd try resetting the device first.
long press the power button.(20 sec).
than turning it on while holding Vol. down. there you can find the factory reset.
if that takes you to the recovery try wiping all the data (cach,data,delvik whatever)
if nothing works, try the link below. maybe it'll work on your version.
http://www.htc.com/us/support/jetstream-att/downloads/
Booo nothing works I give up my jetstream is a brick (((
UPDATE: http://forum.xda-developers.com/showthread.php?t=2461483
this thread can be closed.
i don't know how any one is getting any of this done. i've been able to root, several times, install CWM, several times, but i can not seem to figure out how to boot into the fastboot, or into the bootloader so that i can use fastboot, so that i can unlock my bootloader. is there some magical secret that every one else in the world knows, except me???
i'm running v20d. i've got fastboot and adb installed on linux (debian), and i can shell into the phone via adb, and then substitute user* as root and delete bloat ware and every thing else - but i can't figure out how to boot into bootloader... i've tried "adb reboot bootloader" and "adb reboot-bootloader" (yes, the 2nd one is valid), but both just reboot the phone, then i see the CWM flashing lights, then it continues to boot as normal - a few times i got the dead droid icon.
i can do all this http://forum.xda-developers.com/showthread.php?p=43401184 but i can't get into the danged bootloader... this can't be just me, but it seems like i'm the only one that has no clue how to get this right
bleh! thanks in advance.
* "su -" does not stand for superuser - that's a misgnomer, and since most of the mobile hackers are windows users, they never know that little detail - and you should include the dash after su, so that the shell assumes the root user's home directory and reads the root user's .bashrc env vars, etc
LG prevents rebooting in bootloader on most phones, including this one. Entering fast boot with the script and running the command fails BC its not an official fastboot its user compiled.
Sent from my LG-P769 using xda app-developers app
i've been rooting and putting CWM onto it before i bother with the bootloader, but i wonder if you have to unlock the bootloader FIRST, because CWM or rooting wipes out some thing that's needed to get the bootloader to allow fastboot??? i dunno, just taking stabs in the dark now...
I didn't have recovery or radio installed when I unlocked my bootloader
leolawliet said:
I didn't have recovery or radio installed when I unlocked my bootloader
Click to expand...
Click to collapse
that might be the "1 little detail" i've been missing - i'm going to try to convert mine back to stock, without windows...
sentientsystem said:
that might be the "1 little detail" i've been missing - i'm going to try to convert mine back to stock, without windows...
Click to expand...
Click to collapse
Dude, check my last post on the unlocking bootloader guide thread, I think step 13 that I posted might be the missing key,if it is please let me know because I haven't seen anyone try this at all.
leolawliet said:
Dude, check my last post on the unlocking bootloader guide thread, I think step 13 that I posted might be the missing key,if it is please let me know because I haven't seen anyone try this at all.
Click to expand...
Click to collapse
yeah, that was one of the other things i was going to keep in mind (i actually had seen it as soon as you posted it, and thought you might be correct on that detail).
sentientsystem said:
yeah, that was one of the other things i was going to keep in mind (i actually had seen it as soon as you posted it, and thought you might be correct on that detail).
Click to expand...
Click to collapse
*crosses fingers* good luck, if I find more suggestions I'll let you know. For now let's hope I'm right on this.
You're not the only one. I am also unable to unlock. I agree with omgbossis21 when he mentions that LG blocked access to fastboot. I tried several key combinations but none worked.
The bootloader is on this thing, though. The hidden menu shows the status. Has anyone tried asking LG tech support how to access official fastboot? It must exist in order for the techs to recover the damn thing.
Sent from my LG-P769 using XDA Premium 4 mobile app
peanut butter jelly time! http://forum.xda-developers.com/showthread.php?p=43401184 - now that it's unlocked, i don't know what to do next
sentientsystem said:
peanut butter jelly time! http://forum.xda-developers.com/showthread.php?p=43401184 - now that it's unlocked, i don't know what to do next
Click to expand...
Click to collapse
Wait so you managed to unlock it??
unlocked, flashed cyanogenmod tried to fix the inverted / screwed up screen, bricked it again, trying to unlock again...
LaDY Vengeance said:
You're not the only one. I am also unable to unlock. I agree with omgbossis21 when he mentions that LG blocked access to fastboot. I tried several key combinations but none worked.
The bootloader is on this thing, though. The hidden menu shows the status. Has anyone tried asking LG tech support how to access official fastboot? It must exist in order for the techs to recover the damn thing.
Sent from my LG-P769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Usually phones that don't have a key combo for fastboot you can delete main system partitions and it would start in official fastboot like my LG motion. Not on this phone though
Sent from my LG-P769 using xda app-developers app
Have you tried holding down the vol down button when the lights flash on boot?
villan.co said:
UPDATE: http://forum.xda-developers.com/showthread.php?t=2461483
i don't know how any one is getting any of this done. i've been able to root, several times, install CWM, several times, but i can not seem to figure out how to boot into the fastboot, or into the bootloader so that i can use fastboot, so that i can unlock my bootloader. is there some magical secret that every one else in the world knows, except me???
i'm running v20d. i've got fastboot and adb installed on linux (debian), and i can shell into the phone via adb, and then substitute user* as root and delete bloat ware and every thing else - but i can't figure out how to boot into bootloader... i've tried "adb reboot bootloader" and "adb reboot-bootloader" (yes, the 2nd one is valid), but both just reboot the phone, then i see the CWM flashing lights, then it continues to boot as normal - a few times i got the dead droid icon.
i can do all this http://forum.xda-developers.com/showthread.php?p=43401184 but i can't get into the danged bootloader... this can't be just me, but it seems like i'm the only one that has no clue how to get this right
bleh! thanks in advance.
* "su -" does not stand for superuser - that's a misgnomer, and since most of the mobile hackers are windows users, they never know that little detail - and you should include the dash after su, so that the shell assumes the root user's home directory and reads the root user's .bashrc env vars, etc
Click to expand...
Click to collapse
Have you tried holding down the vol down button when the lights flash on boot? Works for me to get into CWM recovery.
thanks man, but, i'm way past that point. this thread should actually be closed: http://forum.xda-developers.com/showthread.php?t=2461483