Related
I don't read well, apparently, and flashed the Electrify 2.3.5 file in hopes of unlocking my bootloader.
Has anyone else (I have read that a handfull of people have been stupid like me) had any luck unbricking the device?
I have access to RSD protocol and Fastboot.
Thanks in advance.
EDIT: The only thing my phone says now is:
SUF: 108:1:2
Failed to boot 3
----------------------------------------------------------------------
EDIT #2: Downloaded someones CWM flashable kernel and flashed to boot.img via moto-fastboot. Not I have an "Failed to boot 2", which people have recovered from. I am currently flashing (198_7)-1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-198_7-CM-release-keys-signed-Sprint-US.sbf and it's 55% completed, which is higher than it got before........
EDIT #3: It failed.... waiting for re-enumeration...
Have you tried this?
http://www.youtube.com/watch?v=J94VcWk-CJc
I fixed it by flashing the electrify 2.3.5 rom thru rsd.
Now all I have to do is get it back to Sprint.
Sent from my A500 using xda premium
npaulseth said:
I fixed it by flashing the electrify 2.3.5 rom thru rsd.
Now all I have to do is get it back to Sprint.
Sent from my A500 using xda premium
Click to expand...
Click to collapse
Not gonna happen until the new boot-loader is cracked... Sorry
Flashing ROMS Via Bootstrap doesnt work.
Its not that big of a deal. Everything works except 4G and MMS.
I can wait.
Sent from my Motorola Electrify using xda premium
npaulseth said:
Its not that big of a deal. Everything works except 4G and MMS.
I can wait.
Sent from my Motorola Electrify using xda premium
Click to expand...
Click to collapse
Try go sms pro. Put mms settings in advanced settings. Should make mms work.
now just a clarification but is it possible to, without Motorola files, to unlock the boot loader our selves? Is there any coding work to unlock this boot loader on our own?
Sent from my Full Android on Wingray using xda premium
You have to flash something to gain the abilty to unlock the bootloader thru fastboot.
npaulseth said:
I don't read well, apparently, and flashed the Electrify 2.3.5 file in hopes of unlocking my bootloader.
Has anyone else (I have read that a handfull of people have been stupid like me) had any luck unbricking the device?
I have access to RSD protocol and Fastboot.
Thanks in advance.
EDIT: The only thing my phone says now is:
SUF: 108:1:2
Failed to boot 3
----------------------------------------------------------------------
EDIT #2: Downloaded someones CWM flashable kernel and flashed to boot.img via moto-fastboot. Not I have an "Failed to boot 2", which people have recovered from. I am currently flashing (198_7)-1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-198_7-CM-release-keys-signed-Sprint-US.sbf and it's 55% completed, which is higher than it got before........
EDIT #3: It failed.... waiting for re-enumeration...
Click to expand...
Click to collapse
I haven't found the file yet, but apparently right now the only way to fix this is to flash the 2.3.5 Electrify rom.
http://forum.xda-developers.com/showthread.php?t=1394982&highlight=stuck+in+fastboot
http://forum.xda-developers.com/showthread.php?p=20713504
Edit #2: confirmed working. I made a small tutorial for those on this same situation here: http://forum.xda-developers.com/showpost.php?p=21015556&postcount=6
Have a good life!
firtermish said:
I haven't found the file yet, but apparently right now the only way to fix this is to flash the 2.3.5 Electrify rom.
http://forum.xda-developers.com/showthread.php?t=1394982&highlight=stuck+in+fastboot
http://forum.xda-developers.com/showthread.php?p=20713504
Edit #2: confirmed working. I made a small tutorial for those on this same situation here: http://forum.xda-developers.com/showpost.php?p=21015556&postcount=6
Have a good life!
Click to expand...
Click to collapse
Just a quick question: Where you able to flash back to:
1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-198_7-CM-release-keys-signed-Sprint-US.sbf
or are you runningL 2.3.5?
Thanks,
RJR
rrusek said:
Just a quick question: Where you able to flash back to:
1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-198_7-CM-release-keys-signed-Sprint-US.sbf
or are you runningL 2.3.5?
Thanks,
RJR
Click to expand...
Click to collapse
I haven't personally tried it, but as far as I know you can't. You are stuck on 2.3.5 until someone releases a new bootloader unlocker.
firtermish said:
I haven't personally tried it, but as far as I know you can't. You are stuck on 2.3.5 until someone releases a new bootloader unlocker.
Click to expand...
Click to collapse
That's what I figured.. I quess it is better to be stuck unlocked than to be stuck locked!
---------- Post added at 07:25 PM ---------- Previous post was at 07:23 PM ----------
Has anyone been able to get the Sprint data profile pulled down on this so I can use on Sprint?
I had a similar problem this weekend I flashed electrify 2.3.5 on my photon lost root and recovery and was able to get both back. First I flashed the sunfire 2.3.4 thru rsd then one click root and then bootstrap app to flash cwn and am able to flash roms again.
Sent from my MB855 using Tapatalk
js11222 said:
I had a similar problem this weekend I flashed electrify 2.3.5 on my photon lost root and recovery and was able to get both back. First I flashed the sunfire 2.3.4 thru rsd then one click root and then bootstrap app to flash cwn and am able to flash roms again.
Sent from my MB855 using Tapatalk
Click to expand...
Click to collapse
Are you currently locked or unlocked? If I lock my device I will get the Failed to Boot 1 error. If I unlock then everything works.
When I flashed the 2.3.5 rom It locked my phone u have to re unlock it
Sent from my MB855 using Tapatalk
rrusek said:
Are you currently locked or unlocked? If I lock my device I will get the Failed to Boot 1 error. If I unlock then everything works.
Click to expand...
Click to collapse
After flashing the 2.3.5 rom it locked my phone I had to re unlock it I used the unlock sbf thru rsd I am currently unlocked back on jokers stock rom
Sent from my MB855 using Tapatalk
js11222 said:
After flashing the 2.3.5 rom it locked my phone I had to re unlock it I used the unlock sbf thru rsd I am currently unlocked back on jokers stock rom
Sent from my MB855 using Tapatalk
Click to expand...
Click to collapse
But if you wanted to re-lock your phone to get 4g could you do it or would you also get the Failed to Boot 1 error?
Point being is that I think it relocks your phone and does not allow for a downgrade.
rrusek said:
But if you wanted to re-lock your phone to get 4g could you do it or would you also get the Failed to Boot 1 error?
Point being is that I think it relocks your phone and does not allow for a downgrade.
Click to expand...
Click to collapse
Yes it did lock my phone then I unlocked it again and am on stock 2.3.4 so I did downgrade
Sent from my MB855 using Tapatalk
js11222 said:
Yes it did lock my phone then I unlocked it again and am on stock 2.3.4 so I did downgrade
Sent from my MB855 using Tapatalk
Click to expand...
Click to collapse
If you would not mind can you please outline what you did?
This is what I did:
1. Installed regular pudding
2. Installed cwm recovery
3. Installed 2.3.5 for Electrify/Photon via cwm
Then did:
1. Installed stock recovery
2. Installed nopudding4g
After that I started getting the Failed to Boot 1
No matter which locked 2.3.4 I try to flash via RSD it fails on first flash pass when it tries to put the phone into BP bypass.
First to get my phone back to normal in rsd mode I flashed the sunfire sbf then to unlock my phone I used pudding unlock sbf then to get recovery I had to do the one click root then got the bootstrap app to flash cwm zip then I installed jokers stock rom
Sent from my MB855 using Tapatalk
We are attempting to unlock the bootloader of a device on factory stock 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US and need some help..
The sbf in this link is dead [UNLOCKED BOOTLOADER] released!!! 8/14/11{WILL KILL 4G}
Tried this guide: how to have unlocked fastboot without flashing. File flashes ok but "unlocked" does not display on top of the screen. Also attemped "fastboot oem unlock" but get error "infooem unlock is not implemented"
Any input on how to successfully get this device's bootloader unlocked would be very much appreciated!
Update.. Bootloader unlocked using pudding thread.. Thanks myself!!
Hey buddy... how did you unlocked boot loader.....
I got the same error....as u got....
Sent from my MB855 using xda app-developers app
We would all like to know how you pulled it off. Are you on ota 2.35? And if so, what steps did you take?
Sent from my Magical mopho using xda premium
JohnH4 said:
We would all like to know how you pulled it off. Are you on ota 2.35? And if so, what steps did you take?
Sent from my Magical mopho using xda premium
Click to expand...
Click to collapse
He's not on 2.3.5 ota. Sounds like he's on .4 or shipped .5.
Howeverrr, read motorolas latest post on unlocking the boot loader for photons....think you may find something rather interesting, I'm too lazy to go hunt down a link for you.
Sent from my Motorola Electrify using Tapatalk 2
We are flashing back to stock 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US and using this thread to unlock the bootloader.
After step 1 in the thread we usually get an error in RSD but we disregard it as instructed, finish the steps and it's successful every time.
Would that work on 2.3.5 version 45.1.190.MB853.UsC.EN.US ?
Bought the phone used, not sure if it got the OTA update.
All I know it's 2.3.5 and the phone hasn't been used since march...
Thx
brunomcf said:
Would that work on 2.3.5 version 45.1.190.MB853.UsC.EN.US ?
Bought the phone used, not sure if it got the OTA update.
All I know it's 2.3.5 and the phone hasn't been used since march...
Thx
Click to expand...
Click to collapse
no clue for sure. you'll just have to try and unlock it. you can't mess anything up by attempting to do so.
" infooem unlock is not implemented "
That's the error message I get when trying to unlock the bootloader.
The guy who sold it to me said that "hadn't updated it in a while".
So I'm not sure if it's SV1 or SV2 in it. How can I check that?
Anyway, think I'll try the process again to be sure I haven't done anything wrong...
Thx
ps:Can't flash the Slim cause my device is lower then 254_13. And can't flash the Ish rom cause probably it was done the OTA update.
Or wasn't it cause I'm 2.3.5 version 45.1.190? I?m a bit confused right now...
MOF 2.3.5. Slim {locked} De-Blur 4.5.1A-1_SUN-254_13
MOF 2.3.5.ish {locked} - Bootstrap Optimized 7/4/12 - Beta For 2.3.5. Users 7/23/12
na7q said:
no clue for sure. you'll just have to try and unlock it. you can't mess anything up by attempting to do so.
Click to expand...
Click to collapse
http://www.motosunfire.com/2-3-5-bl/
I have tried ur website tutorial to unlock the bootloader. Everything works fine until I get to the 1º fastboot comand. It tells me (command write failed(unknown error))
It's a diferent error from the one I got when tried out with the pudding method.
Could that mess up this process right now? How can I roll it back?
Just to be sure, this device is already rooted with superuser installed too.
The way I see the device was already shiped with 2.3.5 (have no longer contact with previous owner). But there's something I'm clearly missing out...
brunomcf said:
" infooem unlock is not implemented "
That's the error message I get when trying to unlock the bootloader.
The guy who sold it to me said that "hadn't updated it in a while".
So I'm not sure if it's SV1 or SV2 in it. How can I check that?
Anyway, think I'll try the process again to be sure I haven't done anything wrong...
Thx
ps:Can't flash the Slim cause my device is lower then 254_13. And can't flash the Ish rom cause probably it was done the OTA update.
Or wasn't it cause I'm 2.3.5 version 45.1.190? I?m a bit confused right now...
MOF 2.3.5. Slim {locked} De-Blur 4.5.1A-1_SUN-254_13
MOF 2.3.5.ish {locked} - Bootstrap Optimized 7/4/12 - Beta For 2.3.5. Users 7/23/12
Click to expand...
Click to collapse
I'm not sure how you can check what you have. You can flash the locked ROMs above regardless. Or any locked ones really. As for it having 2.3.5 on it, it doesn't mean it was shipped with it. It could have been flashed with the only known 2.3.5 SBF that permanently locks it for good just like the OTA update.
Sent from my MB853 using XDA
---------- Post added at 09:09 AM ---------- Previous post was at 09:05 AM ----------
brunomcf said:
http://www.motosunfire.com/2-3-5-bl/
I have tried ur website tutorial to unlock the bootloader. Everything works fine until I get to the 1º fastboot comand. It tells me (command write failed(unknown error))
It's a diferent error from the one I got when tried out with the pudding method.
Could that mess up this process right now? How can I roll it back?
Just to be sure, this device is already rooted with superuser installed too.
The way I see the device was already shiped with 2.3.5 (have no longer contact with previous owner). But there's something I'm clearly missing out...
Click to expand...
Click to collapse
Do you mean the first fastboot command? Do you have files in the right folder? Did you point command prompt to the folder?
Sent from my MB853 using XDA
"Now to see if you can do a ramboot to unlock your device. Run these commands in order.
If that worked then your screen will have the Motorola logo with dual core technology underneath.
fastboot flash rdl.bin RDL3_unlocked.smg"
This step has worked perfectly. But the next hasn't "fastboot oem unlock".
It tells me (command write failed(unknown error)).
I've realized Rom manager Premium 5028 is instaled and flashed into the phone. Tried to reboot recovery but it doesn't work. Tells me "Error 2" I think.
Could Rom Manager be blocking this process somehow? I'll unistall it cause its no good for me at this point...
edit: Just removed the Clockworkmod, and I keep getting the same error.
If the boot loader was unlockable, it wouldn't pass "fastboot flash rdl.bin RDL3_unlocked.smg" command sucessfully right?
brunomcf said:
"Now to see if you can do a ramboot to unlock your device. Run these commands in order.
If that worked then your screen will have the Motorola logo with dual core technology underneath.
fastboot flash rdl.bin RDL3_unlocked.smg"
This step has worked perfectly. But the next hasn't "fastboot oem unlock".
It tells me (command write failed(unknown error)).
I've realized Rom manager Premium 5028 is instaled and flashed into the phone. Tried to reboot recovery but it doesn't work. Tells me "Error 2" I think.
Could Rom Manager be blocking this process somehow? I'll unistall it cause its no good for me at this point...
edit: Just removed the Clockworkmod, and I keep getting the same error.
If the boot loader was unlockable, it wouldn't pass "fastboot flash rdl.bin RDL3_unlocked.smg" command sucessfully right?
Click to expand...
Click to collapse
i think i know the problem! my info was courtesy of teamuscellular. i did not fully verify it.
so try it like this. good luck!
5. fastboot flash rdl.bin RDL3_unlocked.smg
6. From a command prompt navigate to the fastboot folder extracted from the zip file and run the command.
fastboot.exe oem unlock
This will display device unique id if found.
7. Now run the the same command adding your device id.
fastboot.exe oem unlock UniqueIdHere
8. Now issue the command.
fastboot.exe reboot
---------- Post added at 12:18 PM ---------- Previous post was at 12:10 PM ----------
na7q said:
i think i know the problem! my info was courtesy of teamuscellular. i did not fully verify it.
so try it like this. good luck!
5. fastboot flash rdl.bin RDL3_unlocked.smg
6. From a command prompt navigate to the fastboot folder extracted from the zip file and run the command.
fastboot.exe oem unlock
This will display device unique id if found.
7. Now run the the same command adding your device id.
fastboot.exe oem unlock UniqueIdHere
8. Now issue the command.
fastboot.exe reboot
Click to expand...
Click to collapse
let me know if you get anything. be sure all files are in the C:\electrify directory (if that's what you're using). be sure the phone is in fastboot mode.
"6. From a command prompt navigate to the fastboot folder extracted from the zip file and run the command.
fastboot.exe oem unlock"
You mean C:\electrify on command prompt?
I've hit shift + right mouse button and then open command prompt to get into that location
I still get the same error. Starting to think it really got an Rsd or OTA update before coming into my hands.
Just wounder why does it go through step 5 and not the rest of them...
brunomcf said:
"6. From a command prompt navigate to the fastboot folder extracted from the zip file and run the command.
fastboot.exe oem unlock"
You mean C:\electrify on command prompt?
I've hit shift + right mouse button and then open command prompt to get into that location
I still get the same error. Starting to think it really got an Rsd or OTA update before coming into my hands.
Just wounder why does it go through step 5 and not the rest of them...
Click to expand...
Click to collapse
maybe typing the command incorrectly. corrupt files? could be something along those lines.
only have found one person with an unknown error. still looking at that. it's entirely possible you are locked.
here's the error most users get.
"1c10d60
SVF:106:1:2
sec_exception: b655, eddc, eb"
That's exactly what I was getting on the phone.
Thought you were refering to the command prompt window.
As it shown the dual core logo, thought I was fine on this step.
Seems that my phone is permalocked, right?
Sorry for wasting your time. Thanks
ps: will try the Peetr’s 2.3.5 Hybrid (Stock/CM7) cause I had no service with none of the Mof's roms. Neither the Sim, or Ish worked ok. Had no wireless service in any of them...
na7q said:
maybe typing the command incorrectly. corrupt files? could be something along those lines.
only have found one person with an unknown error. still looking at that. it's entirely possible you are locked.
here's the error most users get.
"1c10d60
SVF:106:1:2
sec_exception: b655, eddc, eb"
Click to expand...
Click to collapse
after this thread http://forum.xda-developers.com/showthread.php?t=2105017 i used one of the sbf in this sites http://www.das8nt.com/sbffiles.html
and flash it with RSD now i am trying agin to use fastboot and flash once more cwn and i get this message 'error cannot load recovery.img'
and when i tryd to erase and then flash and i got the same thing.
moreover when i start the phone somehow after i flash the sbf the tuch screen works funny (its not dead pixel) its like the touch screen moved one half inch lower
After flashing sbf, in order to flash a custom recovery, you first need to flash a pudding sbf file to unlock the bootloader. After unlocking the bootloader, running the command "fastboot oem unlock" and then repeating the command with your device's ID, you can flash CWM to your recovery.
Sent from my MB860 using xda app-developers app
palmbeach05 said:
After flashing sbf, in order to flash a custom recovery, you first need to flash a pudding sbf file to unlock the bootloader. After unlocking the bootloader, running the command "fastboot oem unlock" and then repeating the command with your device's ID, you can flash CWM to your recovery.
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
did it still dont work
igalc87 said:
did it still dont work
Click to expand...
Click to collapse
Seeing as your device is a non-ATT device, did you flash a pudding sbf or the IHOP sbf?
Sent from my MB860 using xda app-developers app
palmbeach05 said:
Seeing as your device is a non-ATT device, did you flash a pudding sbf or the IHOP sbf?
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
i flashed to my original sbf Partner (Orange) Israel 2.3.4 / 45.33.0
Ok. After you flash that, you have to flash another sbf file over that one. http://forum.xda-developers.com/showthread.php?t=1136261 will get you to the instructions on what to do. Since Orange is what is considered international, you need the IHOP sbf on the page.
Sent from my MB860 using xda app-developers app
palmbeach05 said:
Ok. After you flash that, you have to flash another sbf file over that one. http://forum.xda-developers.com/showthread.php?t=1136261 will get you to the instructions on what to do. Since Orange is what is considered international, you need the IHOP sbf on the page.
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
i got a message its already unlock
and it still dont let me flash with fastboot
so do you any answer?
After seeking advice from a dev, this is the response i was given:
Could also be the recovery is in fact in that directory but is not named recovery.img. Or, if fastboot actually managed to load the file but still reports that error, it could be that his bootloader is either not unlocked or is having issues (the fastboot protocol is implemented in the bootloader AFAIK).
Sent from my MB860 using xda app-developers app
palmbeach05 said:
After seeking advice from a dev, this is the response i was given:
Could also be the recovery is in fact in that directory but is not named recovery.img. Or, if fastboot actually managed to load the file but still reports that error, it could be that his bootloader is either not unlocked or is having issues (the fastboot protocol is implemented in the bootloader AFAIK).
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
i looked agin my i got in the left up corner message unlock(i did all the steps after flashing the sbf)
i redownload recovery and put it in the same dirctory
and still i got errors when i try to flash recovery.img (or system.img boot.img)
so maybe my bootloader fuked how do i fix it?
and tell me if i will flash other sbf file iy will make it worse?
I'm not sure what the heck is going on with your phone or how to fix it, but I'm going to advise you to stay far far away from SBFs from now on.
ravilov said:
I'm not sure what the heck is going on with your phone or how to fix it, but I'm going to advise you to stay far far away from SBFs from now on.
Click to expand...
Click to collapse
ok will do but i will be glad to find an answer
igalc87 said:
i looked agin my i got in the left up corner message unlock(i did all the steps after flashing the sbf)
i redownload recovery and put it in the same dirctory
and still i got errors when i try to flash recovery.img (or system.img boot.img)
so maybe my bootloader fuked how do i fix it?
and tell me if i will flash other sbf file iy will make it worse?
Click to expand...
Click to collapse
I'm going to recommend you ask one of the devs about how to fix it. You can flash another sbf file, but make sure it is the same version as what you have. So if you flashed a 2.3.6 sbf, you need to flash a sbf that is 2.3.6 or risk bricking your phone.
Sent from my MB860 using xda app-developers app
---------- Post added at 09:47 AM ---------- Previous post was at 09:34 AM ----------
One other thing. I'm about to head off to basic training and will be offline for about 10 wks starting next wk. Any one of the atrix dev's should be able to help you further with your phone. I'll do what i can until i leave.
Sent from my MB860 using xda app-developers app
---------- Post added at 09:50 AM ---------- Previous post was at 09:47 AM ----------
ravilov said:
I'm not sure what the heck is going on with your phone or how to fix it, but I'm going to advise you to stay far far away from SBFs from now on.
Click to expand...
Click to collapse
I didn't see this post when i first logged in. Seeing as this comes from one of the atrix devs, i'm going to stand behind this bit of advice, but i still will stand behind what i said before, ask the devs for help.
Sent from my MB860 using xda app-developers app
So I bought an Evo 3D from a friend, he said he played with it quite a bit. Wifi (says error) and cell data is not working, haven't tried Bluetooth. Phone is supposedly from Rogers, so I'm trying to reflash the stock ICS rom that was linked from this site.
First off, the recovery wasn't doing anything, so I flashed cwm-4.0.1.4-shooteru. Now I've got a recovery at least.
Phone refuses to flash either
RUU_SHOOTER_U_ICS_35_S_Rogers_WWE_3.28.631.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262715_signed (obtained from the repository)
also tried to run the .exe version. The flash through CWM says Image Verification Failed or (bad), depends if I get it to actually check the signature. I have redownloaded and tried again with no success.
Hell, even the OTA update doesn't work, says the phone has been tampered with (duh).
Here's what my HBOOT says:
Code:
*** UNLOCKED ***
SHOOTER_U PVT SHIP S-OFF RL
RADIO-10.13.9020.08_2M
eMMC-boot
Jul 12 2011, 15:29:51
I have no idea how he obtained S-OFF or did the unlock, and I have no idea of the phone has the stock radio/software/anything. All I want to do is use the stock ICS rom from Rogers, as I'm lending this phone from a friend. I'm hoping the wifi and cell data will be fixed with proper software.
if your using the zip file then you need to rename it to PG86IMG.zip and place it on the root of your sdcard. then boot into bootloader and accept the update.
if this doesnt work then relock the bootloader and then try running exe version from your pc.
btw what is your hboot?
EM|NEM said:
if your using the zip file then you need to rename it to PG86IMG.zip and place it on the root of your sdcard. then boot into bootloader and accept the update.
if this doesnt work then relock the bootloader and then try running exe version from your pc.
btw what is your hboot?
Click to expand...
Click to collapse
Trying to PG86IMG.zip autoload, also my HBOOT is HBOOT-1.49.0007. Will get back to you when I'm done trying these steps.
zeropaladn said:
Trying to PG86IMG.zip autoload, also my HBOOT is HBOOT-1.49.0007. Will get back to you when I'm done trying these steps.
Click to expand...
Click to collapse
Sooo, it started to update everything with the PG86IMG (i renamed the ICS SHOOTERU rom mentioned above) and about halfway through updating various things it powered off. It won't boot now, it gets stuck in a reboot loop, but I can still get into recovery and HBOOT. Going to try the exe while it's in HBOOT, see if that works (since I can't get the phone to fully power on.)
EDIT: So, since it's stuck in the bootloop now, I can't get the S-ON done. The RUU won't detect the phone now, either. (ERROR[170]: USB CONNECTION ERROR.
So I think I may have just bricked my phone.
Rerun the PG86IMG.zip
Sent from my PC36100 using xda app-developers app
jlmancuso said:
Rerun the PG86IMG.zip
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
Re-ran the PG86IMG.zip, CID is incorrect, the update failed. Do I have the incorrect ROM, or was the file I downloaded bad?
Not exactly sure. I am on a CDMA but most times I have to run the zip twice. Make sure you have downloaded the latest version. Also most sites post md5sums so you can check to make sure the download is correct.
Sent from my PC36100 using xda app-developers app
---------- Post added at 11:24 PM ---------- Previous post was at 11:19 PM ----------
The file was a zip or exe?
Sent from my PC36100 using xda app-developers app
jlmancuso said:
Not exactly sure. I am on a CDMA but most times I have to run the zip twice. Make sure you have downloaded the latest version. Also most sites post md5sums so you can check to make sure the download is correct.
Sent from my PC36100 using xda app-developers app
---------- Post added at 11:24 PM ---------- Previous post was at 11:19 PM ----------
The file was a zip or exe?
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
I've MD5 checked both the Rogers Gingerbread and ICS ROMs from http://www.androidruu.com/index.php?developer=Shooter, they're good. Both get checked then tell me the CID incorrect!!! error. The radio currently installed matches the Gingerbread (WWE) ROM, but that's the first one I've tried (3 times each, just to be sure after reading above. Also, I am using the .zip files, the .exe files are the ones you run on your computer, right? (If I'm using the wrong files I'll be so pissed.)
Yes zip is for sdcard and exe for PC. Was the phone unlocked (htcdev or s-off) before?
Just reread your op. Got an idea but I have to find the files. You can still get into recovery right?
Could not find zip files right away but here is a thread with more info. Should have the zips in it.
http://forum.xda-developers.com/showthread.php?t=1970252
The zip locks bootloader so you can run the pg86img. I forgot that it has to be locked because I use custom hboots that are locked but don't show **locked** or **relocked**.
Sent from my PC36100 using xda app-developers app
Any luck?
Sent from my PC36100 using xda app-developers app
jlmancuso said:
Any luck?
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
Just checked back now, lots of technical stuff that's beyond my knowledge scope, but I did find the zip you referenced. I can still get into cmw so I should be able to do this, ill edit this post when I have results (or not XD)
EDIT: Bootloader is now ***RELOCKED***, after running the query then the relock, now trying the PG86IMG.zip again.
EDIT2: CID is still incorrect. Going to see if I can hit the ***LOCKED*** status instead of ***RELOCKED***, see if that makes a difference.
EDIT3: CID is still incorrect. Must I have the wrong image?
maybe the phone isnt rogers. try an European RUU
---------- Post added at 08:18 PM ---------- Previous post was at 08:15 PM ----------
and if you just aren't able to run a RUU then just flash a stock rom in recovery. you might also have to update your firmware. put on root of sdcard, boot into bootloader and accept update
What CID has the phone actually got right now? (in fastboot, type "fastboot oem readcid").
emulsification said:
What CID has the phone actually got right now? (in fastboot, type "fastboot oem readcid").
Click to expand...
Click to collapse
I've tried fastboot to query the device if it won't boot. I've tried doing many other things with fastboot and it just says <waiting for device>.
zeropaladn said:
I've tried fastboot to query the device if it won't boot. I've tried doing many other things with fastboot and it just says <waiting for device>.
Click to expand...
Click to collapse
Are you sure that the bootloader says "Fastboot USB"?
When you boot the phone into the bootlader, you have to choose the "fastboot" option (select by pressing the power button). It will go into fastboot mode (and display "Fastboot"). Then, when you connect your phone to your PC via USB cable, it should connect to your computer (assuming you have the HTC drivers installed), and "Fastboot" will turn into "Fastboot USB".
Then in the command prompt on your PC, type "fastboot devices". If your phone is detected, it'll show you it's serial number.
You can also verify it's connected by checking Device Manager on your computer.
in case you dont have the latest drivers installed, I suggest you do that first.
emulsification said:
Are you sure that the bootloader says "Fastboot USB"?
When you boot the phone into the bootlader, you have to choose the "fastboot" option (select by pressing the power button). It will go into fastboot mode (and display "Fastboot"). Then, when you connect your phone to your PC via USB cable, it should connect to your computer (assuming you have the HTC drivers installed), and "Fastboot" will turn into "Fastboot USB".
Then in the command prompt on your PC, type "fastboot devices". If your phone is detected, it'll show you it's serial number.
You can also verify it's connected by checking Device Manager on your computer.
Click to expand...
Click to collapse
Bah, I wasn't going into fastboot menu in the bootloader. Go me. It says HTC__001, which means it should be taking anything I throw at it.
EDIT: Changed the CID to ROGER001, the CID for Rogers devices using this information:
http://htcevohacks.com/htc-evo-3d-hacks/how-to-change-cid-on-rooted-htc-evo-3d-gsm/
Threw the RUU at it, worked like a charm! I have a Rogers ICS HTC Evo 3D now! YAY!
Thanks for everyone!
EDIT2: Wi-fi still doesn't work... Probably a hardware issue at this point.
zeropaladn said:
Bah, I wasn't going into fastboot menu in the bootloader. Go me. It says HTC__001, which means it should be taking anything I throw at it.
EDIT: Changed the CID to ROGER001, the CID for Rogers devices using this information:
http://htcevohacks.com/htc-evo-3d-hacks/how-to-change-cid-on-rooted-htc-evo-3d-gsm/
Threw the RUU at it, worked like a charm! I have a Rogers ICS HTC Evo 3D now! YAY!
Thanks for everyone!
EDIT2: Wi-fi still doesn't work... Probably a hardware issue at this point.
Click to expand...
Click to collapse
Glad you got it. Try a couple custom roms and you might get WiFi if your lucky.
Sent from my PC36100 using xda app-developers app
Whoo! Congrats. :highfive:
jlmancuso said:
Glad you got it. Try a couple custom roms and you might get WiFi if your lucky.
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
I agree - WiFi is one of the most integral and most used features of a smartphone. Would be good if you can get it working.