Story, in key point format:
-Just moved, no internet at home yet (in fact I've been using tether since I only check e-mail and use FB anyway)
-At cafe... Already closed, but they agreed to let me stay about 5 minutes past closing time, no time to search. NO N00B/"SEARCH FIRST" COMMENTS PLEASE.
-Don't have any old phones
-Just got a new girlfriend and didn't think much about emergency expenses and spent most of my $ on wine n' dine with her (but at least I got some worthy "dessert", but that's another story).
-Just lost my job a week after meeting her (I stayed up all night, eventually gave into a "food coma" [see above] and came into work late) LOLOL... Woulda had a new phone budget if I was around for another 2 weeks, but noooo....
Anyway:
-Tried to install CM5 onto G1
-Installed it with the CM bootloader (or something like that, it had an orange font)
-Downgraded to RC29, successfully loaded AMON_RA
-Installed DangerSPL, rebooted per the instructions
-Stuck on the boot screen for almost exactly half an hour (5 mins after 8PM until 8:30PM), said "WTF" and pulled battery out
-According to the first few search results, my phone is "fully bricked", as in end+back/home/camera/whatever doesn't work (although when you push end+trackball the blue light turns on, whatever that means)
With that in mind, what should I do? Any hope?
Hmm well Im not an expert like most of these other guys by ANY means, but in my experience I've learned that removing the battery during a percieved "hangup" is a sure fire way to brick a G1. Trust me Ive done it, not fun.
If you can make it to the recovery screen somehow, theres still hope. On the Cyanogen Wiki, I believe theres a type of method for reflashing a rom, by booting while holding the camera button. I would recommend researching that.
Pulling the battery had nothing to do with it. The combination of 1.33.2005 SPL + 1.x radio is incapable of booting any known kernel. The misc partition was configured to boot-recovery, which overrides any key presses. So when it starts up, it figures it should launch recovery, which boots far enough for the SPL to think that its booted (otherwise it would force you into fastboot).
Your only hope right now is to jtag the thing and either wipe your misc partition or load a compatible SPL that allows fastboot.
You forgot to flash a compatible radio!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BoomBoomPOW said:
You forgot to flash a compatible radio!
Click to expand...
Click to collapse
The funny thing is that if he had done the first sensible steps of installing an engineering bootloader (one with fastboot) and wiping the recovery partition (to force it into fastboot when recovery failed due to being wiped), he'd be fine.
DAMNITS!! I only read the "steps" portion of the instructions on the Cyanogen Wiki, which didn't even include the "radio" portion of the equation (I edited it just to avoid other people having the same problems).
lbcoder said:
Pulling the battery had nothing to do with it. The combination of 1.33.2005 SPL + 1.x radio is incapable of booting any known kernel. The misc partition was configured to boot-recovery, which overrides any key presses. So when it starts up, it figures it should launch recovery, which boots far enough for the SPL to think that its booted (otherwise it would force you into fastboot).
Your only hope right now is to jtag the thing and either wipe your misc partition or load a compatible SPL that allows fastboot.
Click to expand...
Click to collapse
Jtag? Sounds horribly hard; baking it and taking out a ROM chip? Wow.
Acecalibur said:
...by booting while holding the camera button. I would recommend researching that.
Click to expand...
Click to collapse
"-According to the first few search results, my phone is "fully bricked", as in end+back/home/camera/whatever doesn't work"
lbcoder said:
The funny thing is that if he had done the first sensible steps of installing an engineering bootloader (one with fastboot) and wiping the recovery partition (to force it into fastboot when recovery failed due to being wiped), he'd be fine.
Click to expand...
Click to collapse
Well, I was (somewhat) following the steps of the Cyanogen wiki.
EdWaRdW818 said:
Jtag? Sounds horribly hard; baking it and taking out a ROM chip? Wow.
Click to expand...
Click to collapse
Your information is wrong. There's no baking, there's no removing chips. There is just interfacing with the board. If you're handy with a soldering iron, its a cakewalk.
Well, I was (somewhat) following the steps of the Cyanogen wiki.
Click to expand...
Click to collapse
Finding all your information in one location? What makes you think that your SINGLE SOURCE of information was accurate or correct? For all you know, it was written with the INTENTION of screwing you up.
Related
Something screwed up today after installing that ApptoSD application from the market and I had to downgrade to RC29 again. That was all fine.
Now I was in the process of upgrading to CM 4.0.4. I already installed the old HardSPL, and realized I needed to install the 'new' one. I did this, and upon reboot my phone is stuck at the G1 screen.
Home+Power and Camera+Power do absolutely nothing.
Am I ****ed? This sucks.
jackaz said:
Something screwed up today after installing that ApptoSD application from the market and I had to downgrade to RC29 again. That was all fine.
Now I was in the process of upgrading to CM 4.0.4. I already installed the old HardSPL, and realized I needed to install the 'new' one. I did this, and upon reboot my phone is stuck at the G1 screen.
Home+Power and Camera+Power do absolutely nothing.
Am I ****ed? This sucks.
Click to expand...
Click to collapse
Yes, its gone. You need to install the radio update before the SPL update. Don't know why you would install the update that kills so many phones without reading up on it...
for the record: cm4.0.4 and all cyanogen mods do not require the DangerSPL, hardspl works fine.
Wow you get a big ol' F for not doing your homework and thinking that you needed the newest thing, good job screwing yourself
Just like everyone else said your toast. I was first thinking why would you need to go back to rc29 because of an apps2sd issue or really any issue, you should have just reflashed a rom. Second (like the others said) you didn't need the new spl.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WTB - spare batt and batt cover!
Whoa, didn't need to jump down my throat - I already flashed the new radio after HardSPL, but I suppose it doesn't matter anyway.
The phone bricked after installing that app, and upon restart it was stuck at the G1 screen, I had to leave the office so I reflashed to RC29 (as it was the only ROM I had on my laptop) while I was on the road (so no internet access) because I desperately needed my phone for a job I was attending. When I got back to the office I must have mixed up my update.zip files somewhere in the process.
Thanks for the help from the people that weren't dicks about it, at the end of the day it's only a phone. Time for a shiny new one.
It is pretty common knowledge that the DangerSPL will not work with older radio versions BUT I believe flashing RC29 downgrades your radio to an earlier version, therefore bricking your phone. If you decide to use DangerSPL or Haykuro's SPL (the same I think) in the future, make sure you flash HardSPL BEFORE restoring to RC29.
I would play the stupid card with TMO and see if they will send you a new one.
And if you don't already, use Cyanogen's 1.4 Recovery. You can backup and restore via Nandroid from the recovery image so you can have a working version on your SD card at all times and not need a computer to access it.
Just for my own knowledge,
A phone with the hard spl can be safely downgraded back to rc29 (if you needed to send it back to tmo for instance) correct?
It's the danger spl that can brick your system if you downgrade to earlier radio right?
dcorrea said:
Just for my own knowledge,
A phone with the hard spl can be safely downgraded back to rc29 (if you needed to send it back to tmo for instance) correct?
It's the danger spl that can brick your system if you downgrade to earlier radio right?
Click to expand...
Click to collapse
Correct......
downgrading by using rc also downgrades the radio and spl, does not matter what spl you are using. it takes it back. you will not brick by using the rc dreaimg.nbh
r4d14n7 said:
It is pretty common knowledge that the DangerSPL will not work with older radio versions BUT I believe flashing RC29 downgrades your radio to an earlier version, therefore bricking your phone. If you decide to use DangerSPL or Haykuro's SPL (the same I think) in the future, make sure you flash HardSPL BEFORE restoring to RC29.
I would play the stupid card with TMO and see if they will send you a new one.
And if you don't already, use Cyanogen's 1.4 Recovery. You can backup and restore via Nandroid from the recovery image so you can have a working version on your SD card at all times and not need a computer to access it.
Click to expand...
Click to collapse
Thanks for that information.
I'd play the stupid card but I'm guessing that being in Australia makes that pretty difficult eh?
hey you guys have an awesome prime minister
He gave use all $900 just for the fun of it. Great guy.
I guess I can try contacting HTC and see if they'll repair it, I'm expecting to pay for it but i guess it's better than paying for a new phone.
i was talking about his policies, like telling everyone that this is our country and that we will not bend over backwards to appese you and if you don't like it then get the **** out. we need someone like that guy here instead of ass kissing obama
sorry small rant
yeah you could call htc
Haha I know you were
I've got in contact with the repair center in my area and they're going to 'get back to me'.
I mixed up my update files trying to update my radio and spl and installed the spl before the radio. And now it is stuck on the "t-mobile G1" screen. recovery won't work, fastboot won't work. Is there anything that I can do or is it gone for good?
Babyche43 said:
I mixed up my update files trying to update my radio and spl and installed the spl before the radio. And now it is stuck on the "t-mobile G1" screen. recovery won't work, fastboot won't work. Is there anything that I can do or is it gone for good?
Click to expand...
Click to collapse
lol......its gone....call tmobile and tell them your phone said it had an update and you said to update it and that you left it there for a while and when you came back it wouldn't get past that.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just another brick in the wall.
How did you mix up the ordering of the files? Sounds like you know which should come first...
Oh well. Thanks for the advice. I just call T-mobile and they are going to send me a new phone and give me a loaner phone until the new one arrives. Great.
I did know but I'm new to this rooting thing I just started Monday. I had my phone rooted but I messed up when i was switching roms. I didn't know I had to wipe everything when you switch to a hero rom. So I started over and picked the wrong spl from all the different files that I downloaded on my computer to do the root. Then combine that with all the different guides that I have been reading I was doomed. The funny thing is that as soon as I hit update I knew I messed up.
Babyche43 said:
I did know but I'm new to this rooting thing I just started Monday. I had my phone rooted but I messed up when i was switching roms. I didn't know I had to wipe everything when you switch to a hero rom. So I started over and picked the wrong spl from all the different files that I downloaded on my computer to do the root. Then combine that with all the different guides that I have been reading I was doomed. The funny thing is that as soon as I hit update I knew I messed up.
Click to expand...
Click to collapse
You don't need to reroot the phone to go to a hero ROM from another modded rom. You only need to flash the newest radio and then the special SPL (in that order)
Babyche43 said:
I did know but I'm new to this rooting thing I just started Monday. I had my phone rooted but I messed up when i was switching roms. I didn't know I had to wipe everything when you switch to a hero rom. So I started over and picked the wrong spl from all the different files that I downloaded on my computer to do the root. Then combine that with all the different guides that I have been reading I was doomed. The funny thing is that as soon as I hit update I knew I messed up.
Click to expand...
Click to collapse
Yessir the ol gut feeling.
that's the worst when you ****ed up and there is nothing that you can do to stop it. well unless you are like me and don't care and just do it anyway
Diceman4 said:
You don't need to reroot the phone to go to a hero ROM from another modded rom. You only need to flash the newest radio and then the special SPL (in that order)
Click to expand...
Click to collapse
I know but something happen when I went from a Cyanogen mod too a Drizzy hero rom to were it would work and kept boot looping (if that is a word) so since I don't know that much about flashing roms and all that I figured I would just start over and just install the hero rom from the beginning and that's were I installed the wrong update.
Babyche43 said:
I mixed up my update files trying to update my radio and spl and installed the spl before the radio. And now it is stuck on the "t-mobile G1" screen. recovery won't work, fastboot won't work. Is there anything that I can do or is it gone for good?
Click to expand...
Click to collapse
How would you know if you bricked your G1?will it be stuck in a certain logo it'll be stuck at?
will it be stuck in a certain logo it'll be stuck at?
hahahahahahaha yes. The very first one.
you will know your phone is bricked by the fact that it no longer wants to cuddle with you when your press power, or when it no longer gets in the mood when you press home and power, and you know all hope is lost and you will never get to the g-spot on your g1 when camera and power no longer does anything.
yes all the answers are in there lol
Hi, all,
my radio refuses to upgrade on my G1 so im desperately trying to get adb and fastboot working to i can use hard spl to flash the newest radio (since im on the oldest one right now).
Im on a Windows 7 64-Bit HP Laptop and after using the usb drivers that came with the latest SDK, I managed to get adb working for literally 1 minute before it automatically shut off and the system stopped recognizing it and throwing out a Code 10: Device cannot start error. I downloaded USBDeview and uninstalled the usb drivers then I went through the registry and deleted all 'vid_0bb4&pid_0c02' keys values and folders...except one that keeps throwing this error for me:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Even when i set permissions to delete it, i still get that error.
Even though i deleted all the values but that one, i managed to install it successfully once i used DroidExplorer, and i managed to get it working for literally 1 minute before the driver stops sensing the phone. Any suggestions?
Uninstalling the driver in device manager and installing it from device manager always worked for me. But I havn't used Windows for the past month+ so there could have been an update or something that breaks ADB.
ive tried that a thousand times =/
no i dont think they made an update that prevents it.. ive been trying off and on to install adb for a few months now but now that i flashed hard spl in hopes of fixing my stupid radio, ive been aggressively trying for the past 2 weeks lol
Anyone have any suggestions? I was thinking of formatting the whole hard drive on the computer but that's extremely painstaking and a little extreme...anyone have any ideas?
speedysilwady said:
Anyone have any suggestions? I was thinking of formatting the whole hard drive on the computer but that's extremely painstaking and a little extreme...anyone have any ideas?
Click to expand...
Click to collapse
You shouldn't format for something as small as installing a single driver, the headache that comes with setting up countless progs or accs and what not isn't worth it, at least for me. i had dual-booted vista instead since it worked with the DL'd driver. I haven't tried in 7 though haven't looked for the driver yet.
Yeah you're right formatting would be a huge pain, that's why I'm wondering if anyone can help me remove that registry key cuz I think that's what's been screwing up my install.. I can't dual boot an earlier OS because I don't have the disc for vista or xp. =/
You get this error when you plug in your phone?
And how are you trying to flash your radio? When you're in recovery, you can't flash the require update.zip? Maybe give some other information, like what ROM are you on, what recovery?
tehseano said:
You get this error when you plug in your phone?
And how are you trying to flash your radio? When you're in recovery, you can't flash the require update.zip? Maybe give some other information, like what ROM are you on, what recovery?
Click to expand...
Click to collapse
I am currently on Super D 1.9.2 (modified to fit on Any SPL)
Amon_RA Recovery 1.6.2
Yes Ive had this problem forever, i used to be stuck on the .11 radio, it refused to update to 26i or the latest radio whenever I used amon_RA or cyanogen's recovery image, whether i used button shortcuts to flash or if i manually selected the radio update with the trackball. It would flash with no error message but everytime i held power and camera itd be the .11 radio, and the baseband displayed the same thing...then I was advised to make a goldcard and use DREAIMG.nbh to downgrade to .29 and reroot...which i did, and after trying again to upgrade the radio it wont even go up to .11 and above now.. even after flashing Hard SPL. So now Im trying to get ADB set up so I can fastboot a radio update. I have no idea why it wont work through recovery.
bump anyone?
Try a system restore? I can't really help you, all I have is vista
Can anyone give me the link to a guide to get fastboot drivers and fastboot.exe working on 64-bit windows 7? XDA search is down at the moment and I'm searching like crazy on google and not finding the results. I want to flash a new recovery on my Tab 10.1, thanks!
OneStepAhead said:
Can anyone give me the link to a guide to get fastboot drivers and fastboot.exe working on 64-bit windows 7? XDA search is down at the moment and I'm searching like crazy on google and not finding the results. I want to flash a new recovery on my Tab 10.1, thanks!
Click to expand...
Click to collapse
Here you go sir:http://www.youtube.com/watch?v=Bg-cGTZE2XI&feature=related
I've searched Google quite a bit, and found others that had a similar issue, but I notice that they experienced slightly different outcomes (mostly not fixing the problem for them). I'm going into this assuming that the phone may just have to be jtag'd to be fixed... but as a last ditch effort I'd like to lay out my issue in as much detail as possible to see if anything can be done to salvage this thing.
How I broke it: I recall about a year ago, I tried flashing an SPL (was it DangerSPL? Maybe...). The phone was already rooted, but I think I was trying to gain S-OFF with it. Whatever it was, it was stupid to do.
How it behaved after that (and as of right now): Turning on the phone shows the Rogers logo, and it does nothing. For a very long time.
Power key combinations and their results: I notice that 3 work. Here they are:
1st) Hold wheelbutton+POWER - it illuminates the led (Blue colour).
2nd) Hold BACK+POWER: Takes me to a rainbow screen that has HBOOT text. The text is:
DREA210 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
Sep 2 2008
Also, inside the green part is a white line that says "Serial0"
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3rd) Hold CAMERA+POWER: Takes me to the same rainbow screen mentioned above, BUT - it turns into a grey screen that tries to load something. Research toldme that this is where it tries to load an NBH file (it's like a system image... like a rom I assume). I found 3 different NBH files.
First NBH file I tried was a "Rogers" one - which I thought would be perfect for me, since it's a Rogers phone. I made sure to rename it to DREAIMG.nbh, put it on a freshly-formatted MicroSD card, popped it in, and turned the phone on by holding CAMERA+POWER. It got to the grey screen, "loading..." and then "checking..." and then it said "00028002 not allow". It then returned me to the rainbow screen.
I then tried 2 other NBH's (the standard US one - RC29? and then the UK one - RC7?) with no luck - still got the "not allow" message.
So I think that's it. I'm glad that I can actually get SOME kind of screen up... as that is a sign of hope...
If anyone can contribute to this, it would be greatly appreciated. Thanks for reading.
a) you need to make a goldcard to flash any nbh other than the rogers ones.
b) 0.95.0000 will not net you flash the rogers firmware (I think an issue with the ebi1radio)
This means you must make a goldcard, borowing someone elses phone if needed to get the CID of a micro sdcard.
After you have a gold card I recommend you flash the orange nbh from my 2708+ thread http://forum.xda-developers.com/showthread.php?t=831139
(rename to DREAIMG.nbh and place on the root of the gold card)
Once the orange nbh is flashed you can flash and slash screen you want if any (only reason for a full s=off spl) then use the fastboot instructions to install the 2708+ radio and a rom. also on that thread)
_--
Ezterry to the rescue! Lots of info there. Thanks a lot - i will let u know of the results!
Sent from my XT860 using XDA App
ezterry thank you thank you thank you!!! Dream is up and running!!!!
Sent from my XT860 using XDA App
Good morning, I made the downgrade tutorial correctly following the Ansar.
But when you install the HSPL, and now I got an error when I activate the Bootloader, I have no available USB MODE / SERIAL.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The phone is working properly. My current version is 7720.68 and the boot loader: 5.10.225.0 Is there a different solution to the Gold Card? thank you very much
I am preparing a tutorial with pictures step by step from the jailbreak downgrade to end and I was in this error.
If I can help, I promise to raise them the tutorial.
This night when Spain, I'll upload the tutorial step by step with pictures that complements this:
http://forum.xda-developers.com/showthread.php?t=1196183
http://mobiletechvideos.mybigcommerce.com/htc-hd7-jtag-brick-repair/
I was in the same boat. This did the fix for me. Been flashing just fine.
Thanks, but I'd rather go to the Gold Card method. I have read most of the forum and have not found solution to this failure.
What exactly did you downgrade? You tried flashing HSPL with the 5.10 bootloader. It is plastered all over these forums and is also included as a warning to not flash if you have this bootloader or higher in most of the flashing tools available...Unless I'm missing something, the guide you're referencing is how to downgrade your phone to a lower bootloader version to allow you to flash custom roms to your phone without problems... Since your bootloader version is 5.10, what exactly are you talking about when you say you "made the downgrade tutorial correctly following the Ansar" ??? If you followed the downgrade tutorial correctly then your bootloader should not show up as version 5.10...
U flashed HSPL on 5.10 bootloader. Doing so will brick it
THe DFT tool warned u not to do it.
Thanks for the backup.
Hello, you have a half brick and can fix it by the Goldcard method.
The JTAG is used when a brick is complete, ie, the display of four colors only the color red will be written as "PD 29100 SS-BC (4K)" only.
http://forum.xda-developers.com/showthread.php?t=1597837
PS: Sorry for my bad English and do not forget to thank MarysFetus
rubensaf said:
Thanks, but I'd rather go to the Gold Card method. I have read most of the forum and have not found solution to this failure.
Click to expand...
Click to collapse
GoldCard is incredibly simple. So much so, that I made two videos - one instructing how to make a home-made USB-Y cable and the other demonstrating the GoldCard method. I was very much afraid of doing such a thing until I was forced into it. It turns out to be significantly easier than text-based descriptions let on.
You should not fear the GoldCard (all-in-all, it cost me $11 and about an hour). What you should fear is JTAG. In every situation, JTAG is the "horror movie" of hardware mods. You get scared by unexpected things around every corner and occasionally, loud, frightening noises will grace you with their presence.
May I ask why you want to avoid GoldCard?
GameDr04 said:
GoldCard is incredibly simple. So much so, that I made two videos - one instructing how to make a home-made USB-Y cable and the other demonstrating the GoldCard method. I was very much afraid of doing such a thing until I was forced into it. It turns out to be significantly easier than text-based descriptions let on.
You should not fear the GoldCard (all-in-all, it cost me $11 and about an hour). What you should fear is JTAG. In every situation, JTAG is the "horror movie" of hardware mods. You get scared by unexpected things around every corner and occasionally, loud, frightening noises will grace you with their presence.
May I ask why you want to avoid GoldCard?
Click to expand...
Click to collapse
I also agree, that using the home made usb-y cable is very,very easy. I had exactly the same problem as the opening poster, i actually bought the phone with it half bricked. After making the cable and flashing a shipped rom i was then able to downgrade and am now on a Deepshining custom rom.
scousemartin said:
I also agree, that using the home made usb-y cable is very,very easy. I had exactly the same problem as the opening poster, i actually bought the phone with it half bricked. After making the cable and flashing a shipped rom i was then able to downgrade and am now on a Deepshining custom rom.
Click to expand...
Click to collapse
Made the y-cable yesterday and followed the procedure but still not working. Usb host mode got stuck at "loading..."
PLS HELP!!
rubensaf said:
Good morning, I made the downgrade tutorial correctly following the Ansar.
But when you install the HSPL, and now I got an error when I activate the Bootloader, I have no available USB MODE / SERIAL.
The phone is working properly. My current version is 7720.68 and the boot loader: 5.10.225.0 Is there a different solution to the Gold Card? thank you very much
I am preparing a tutorial with pictures step by step from the jailbreak downgrade to end and I was in this error.
If I can help, I promise to raise them the tutorial.
This night when Spain, I'll upload the tutorial step by step with pictures that complements this:
http://forum.xda-developers.com/showthread.php?t=1196183
Click to expand...
Click to collapse
Fix! without Goldcard HERE.