Develop Bugs

[Q] Rooted Wildfire S 2.3.5 stuck in bootloop...

Hi,
I've got a HTC Wildfire S, rooted and S-OFF.
But it's stuck in bootloop, I messed with the system/apps folder...
So now it's pretty much messed up.
Didn't install ROM-manager, I know it was kinda stupid.
How can I reïnstall a custom ROM?
Can anyone help me?

Go into recovery and flash from there, or if you backed-up then restore the rom. If you don't have any roms then you can also mount your sd card from CWM recovery. If you don't have any custom recovery then you'll have to flash it through fastboot. I would tell you the process but I'm really busy right now, but I'm sure someone will explain it to you.

Hi, thanks anyway... hopefully some other kind guy can help me
I don't have any custom recovery, only a ROM which I want to flash on to the device...

seanw712 said:
Hi,
I've got a HTC Wildfire S, rooted and S-OFF.
But it's stuck in bootloop, I messed with the system/apps folder...
So now it's pretty much messed up.
Didn't install ROM-manager, I know it was kinda stupid.
How can I reïnstall a custom ROM?
Can anyone help me?
Click to expand...
Click to collapse
Don't install custom ROM's from Rom Manager's Download list. None of them are for Wildfire S.
Install CWM Recovery either through Hboot as a PG76IMG.zip or using Eoghan2t7's Windoze tool.
From there you should make a backup of your working ROM before trying any new ones in case of times like this...

Hi,
yes if I install the CWM recovery... can I then install my ROM? It's just a slightly modified Wildfire S Stock Rom...
And, I'm sorry to ask... But how do you install CWM through the boot menu?

seanw712 said:
Hi,
yes if I install the CWM recovery... can I then install my ROM? It's just a slightly modified Wildfire S Stock Rom...
And, I'm sorry to ask... But how do you install CWM through the boot menu?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1431969
Download that and connect your WFS to your PC, follow the steps which are quite easy. Then boot into recovery (volume down + power button, choose recovery by the volume buttons and power button), then choose install zip from SD and you can install the zip file (the rom) by selecting that file.
Let me know if this works

I have the same problem when using OC ROMs.
What am I doing wrong?
Now it's loading for ages or simply stuck in the bootscreen.

I too have the same problem when using OC ROMs. Why?

Hi, thanks for the help!
But I'm not quiet through yet... so I downloaded the WFS Manager, then I connected up my phone to the pc.
It was switched on, and just doing the bootloop again, showing the "Quietly Brilliant" sign over and over again.
And then I ran the tool, and it said "Please connect up your device" after I ticked on the first option ("Root And Install Recovery").
I guess this is because the WFS was bootlooping, and so the pc didn't recognise it. I also tried with the HBOOT menu on, but still the pc didn't recognise my phone. Is there anything I did wrong?
My pc (Windows 7 Ultimate x64), showed a popup saying there couldn't be found any driver for "Android 1.0". However it did work before the bootloo

If you have a card reader, or a phone that can take your SD card, then just remove your SD card, place it in an SD card reader or a device which can take your SD card, plug that device into your PC, place the ROM you want to flash onto the SD card, place your SD card back into your Wildfire, boot into recovery and flash the ROM from there.
I had a similar situation where I had an invalid xxxxIMG.zip file on the root of my SD card and a ROM that kept rebooting my device. Naturally, I started panicking, but when I got myself together, I just realized I could remove my SD card and then go into recovery, then reinsert my card and flash a working ROM.
Hope this works for you

Hi, thanks for the help. But I don't think you fully understand my problem.
So I have a stock ROM, rooted. And I messed with the system/app folder.
Now it's stuck into bootloop.
What does recovery mean? is it the menu entry in the HBOOT menu?
Because if I go to "recovery" and click it, after a few seconds I get a phone icon with a red triangle above it.
I tried putting the PG76IMG.zip file on the root of my SD card, but then in the HBOOT Menu, I get the message:
"CID incorrect !
Update Fail!
Press <POWER> to reboot."
What do I have to do?

find the cwm recovery thread and download the PG76IMG.zip then copy it to your sdcard then reboot to hboot. when it asks you if you want to flash recovry press volume up. then when finish instead of rebooting take out your battery. wait for 25 secs reinsert it then boot to hboot then choose recovery see new ui instead of the old one.
---------- Post added at 03:19 PM ---------- Previous post was at 03:16 PM ----------
here you go forum.xda-developers.com/showthread.php?t=1213229

Hi, when I do what you say I get the error:
"CID incorrect!
Update Fail!
Press <POWER> to reboot."
This is my course of actions:
I download the PG76IMG.zip file from the CWM recovery thread.
I place it in the root of my SD-card.
I start my phone pressing the volume-down button.
It automatically finds the .zip file and tries to update, but then I get the error.
What should I do?

I got what you were trying to say, I just didn't realize you had no recovery installed. I had the same error message pop up when I tried to install the recovery. I think it had something to do with the hboot being newer than something, something, blah, blah, bliddity-blah.
Anywho, I think I had the recovery installed along with the root using SuperTool.exe, but that won't work for you, since you obviously can't boot up, so you can't connect to the PC. All I can remember is I had some sort of app on my PC that allowed me to push the CWM Recovery without going through all that hboot stuff, since the S-ON wouldn't let me install PG76IMG.zip. Again, this is useless to you
My best advice is to try another PG76IMG.zip file and just keep trying until you find one that'll work, which you'll place onto your SD card from another device, of course.
EDIT: Link to where I got CWM Recovery from.
In this post there's an auto-installer that I used to flash it onto my device.

The reason you are having bootloop problems with OC roms is because your phone doesn't support OC. Don't worry though it's not just you, even my phone doesn't support OC. The best ROM to go with right now is Alquez's CM7, but I'm sure other developers will make non-OC roms.

Hi, THANKS!
I used the auto installer, and now I have the CWM recovery!
Can someone tell me now which options I should use to install the new ROM?
Maybe an advice of which ROM would be the best one?
I'd like something fast and stable, it would be handy to have one which doesn't have any stock apps installed with it...

I'd go with Jikantaru's ROM, if I wanted a more Sense-ish experience (which I, personally, don't). It does away with the bloatware, but it keeps Sense UI. I couldn't use this one, since my SD card is only 2 gigs and I can't partition it correctly :\
Therefore, my pick would be Cyanogenmod 7, which gives you a pure Android experience (no trace of HTC's bloatware, spyware or crapware). It takes away everything you don't need or most likely don't use and keeps it all clean and speedy, since there's no Sense, MotoBlur, TouchWiz or any other company-created user interface, leaving you to run everything right on top of the Android system. However, I've had some trouble with this one. First I had no mobile data connection or WiFi, and when I finally fixed that problem, I noticed I had no phone app -.-
So, now I'm using m1ndh4x8r's ROM, and I'm pleased enough with it. It lets me overclock and stuff, though I fear I might have effed something up while reverting to it from my non-fully-working CM7 flash, and now I can't install most apps :\
Now I'm pretty much waiting for a fully-operational CM7 build to come out so I can finally use my phone's full potential.

white htc screen
Hey hey =)
I installed the cm7 by alquez (already tried the RC and the nightly build) and I'm stuck at a white boot screen - I don't know if this is the boot loop error - I only see the green HTC sign with white background
Yesterday, I unlocked the phone, rooted it and today, I installed the CWM and from there, resetted the phone, data, and installed the zip.
Now, the white screen doesnt go away, even after 15min or so
Is there a thing i'm missing?
Thanks in advance!

Saftpackl said:
Hey hey =)
I installed the cm7 by alquez (already tried the RC and the nightly build) and I'm stuck at a white boot screen - I don't know if this is the boot loop error - I only see the green HTC sign with white background
Yesterday, I unlocked the phone, rooted it and today, I installed the CWM and from there, resetted the phone, data, and installed the zip.
Now, the white screen doesnt go away, even after 15min or so
Is there a thing i'm missing?
Thanks in advance!
Click to expand...
Click to collapse
Wipe all data and cache including dalvik from within clockwork mod

ok, shall I also format boot?
because I read it's pretty nasty deleting it if you don't install a new one, is that right? ^^
Dunno what has changed but thank you for your tip, it worked now!! =)
PS: didnt format boot ;-)

CM10.1 crashed and softbricked itself, can't access the file system

I have Cyanogenmod 10.1 (stable) installed; the other day it crashed while I was on Instagram, rebooted itself, and wouldn't go past the spinning circle screen. Tried rebooting it, now it won't go past the screen before that, with the blue Cyanogenmod man and the Samsung logo.
I have TWRP 2.5.0.0 installed with it, which I don't know how is possible being that the file systems are incompatible, so unless I used Odin to install CM10.1, I don't know how I did it without installing Clockworkmod Recovery over TWRP.
I've been trying to fix it for a couple days now (I'm kicking myself for not getting around to posting here sooner). When I go into TWRP it asks me for a password (which I've never set, I assume it's asking me because that's all it knows to do when the file system is incompatible), which I click cancel at every time, and when I try to do just about anything (including installing new ROMs or recoveries from within TWRP) it gets errors when trying to mount any partitions on the device, so I can't change anything on the phone at all.
I've tried re-installing TWRP AND Clockworkmod Recovery with Odin, and they succeed, but when the phone tries to reboot, the screen just turns off and nothing happens, and I have to take the battery out to do anything else.
So right now I'm totally screwed unless I can fix this thing. I'd like to not have to drop 200 on a Nexus 4 after only a year or having this phone I bought brand new, especially with the Nexus 5 already coming out later this year...can somebody help me???
EDIT: I should clarify that I can access recovery and download mode

If you can get into download mode you can flash a stock image to your phone and restart from scratch. Download the proper stock image from here http://forum.xda-developers.com/showthread.php?t=1968625 and flash it in odin.

FoxTrotz said:
If you can get into download mode you can flash a stock image to your phone and restart from scratch. Download the proper stock image from here http://forum.xda-developers.com/showthread.php?t=1968625 and flash it in odin.
Click to expand...
Click to collapse
I should've clarified that I've tried this with a bunch of roms, and it just shows SBA2 in the status box forever. I left it for a full hour before and it never changed.

According to this page http://www.alliance-rom.com/community/wiki/bricked-android/ reformating your external sd card may help. It also links to something I personally have never heard of but apparently this: http://forum.xda-developers.com/showthread.php?p=15330252 can help unbrick any samsung phone that's flashable with odin.

[Q] I made a huge mistake and I need help.

First of all, Sorry if I make any mistakes with the language as English is not my first language.
I rooted my HTC One M8 (Unlocked version) a month or two months ago, yesterday I received the Lollipop OTA update and I wanted to install it, I did as it said and it sent me to the The Win Project thing and as you all know, it failed. So I made a research on the internet and it said that it was impossible, either I needed to wait for the ROM or I needed to unroot my phone, So I as the noob that I am, went to the SuperSU program and clicked Unroot, then try it again, and from then on I started to make one mistake after another, I checked how to do a factory reset because I thought that even that I have my phone Rooted, I don't really exploit it as much, so it was okay to go back to basics and then afterwards install the official Lollipop update.
I went then to check some tips and I was unsuccessful, then I try to download the Candy5 version and try it and when I was "following instructions" I downloaded the Candy 5 and the gapps and everything and then I went to recovery mode, I wiped all the things that needed to be wiped and then I realized that I forgot to move the downloads from my PC to my HTC, so I clicked Reboot, it asked me to install the SuperSU and I clicked yes, then it rebooted, but it never went further away from the white screen with the green HTC logo in the middle and the "powered by Android" at the bottom. The HTC is frozen, I can't really do anything from there, I press the power button, the volume buttons, any combination between all these and nothing happens, when I connect it to my computer, the computer makes a sound as if detected an external device being connected but it doesn't really appear as a file.
What can I do? What should I do? I know I screwed up big time and you guys may hate people like me.
Thanks in advance.

You need to load a custom rom on the external SDCard, go to TWRP, select external SDCard, and install the rom.
But really you have made the situation worse from where you were.

Done...but...
SaHiLzZ said:
You need to load a custom rom on the external SDCard, go to TWRP, select external SDCard, and install the rom.
But really you have made the situation worse from where you were.
Click to expand...
Click to collapse
Thanks, I know I messed up. Now I have another problem. The SDCard is not working on the TWRP. What should I do?
I found this: http://forum.xda-developers.com/showthread.php?t=2318497
Should I do that?

gamorro said:
Thanks, I know I messed up. Now I have another problem. The SDCard is not working on the TWRP. What should I do?
I found this: http://forum.xda-developers.com/showthread.php?t=2318497
Should I do that?
Click to expand...
Click to collapse
If you are in twrp you can use the command "adb push filename.zip /sdcard/" and it will put the zip onto your Internal storage or wherever you tell it to put it. I believe /sdcard/ is internal storage and /sdcard2/ is ext sd card. just remember to have the zips for the rom in the same folder that the adb file is. after pushing you do not have to reboot your device and should be good to go as far as wiping/installing goes

I did something stupid yesterday a bit like whats going on with you see here I deleted the os got stuck on the white screen ect.
I used this rom and followed this guide
You may want to check to make sure it's the correct rom and that i'm not making things worse.

n910v unlocked boot, twrp, twrp reboots on any rom install

so i followed the recent bootloader unlock, i have the retail in developer mode, i got twrp installed, this i where it gets messy, it went into a bootloop, so i did a wipe on the cache and davk cach, didn't work. even pulled the battery, so i tried the format. same problem, did work, so i did a wipe again which i think i really broke it when i wiped all but the sdcard, so now, NO OS. so i'm trying to get files to reflash stock roms, i found downloads to the stock files btw, currently downloading.
so, i have twrp
no backup (i'ma idiot lol)
no OS installed
bootloader is confirmed to be in developer mode
can't get phone to access fastboot. via adb
only recovery and download avaible
[edit, i can move files onto my sd card by using another phone to move files]
so do i continue with trying to use idon to flash stock rom onto the phone? will twrp still be installed? and will i keep my developer unlocked booloader?
twrp is v2.8.5.0
(been working on this for about 14 hours now)
FIXED!!
ok, so i found a stock recovery file, md5.tar, i'll post a link below.
i used odin, put phone into download mode, connected with odin running as administrator.
selected the file i used in the AP button, (had to wait awhile for it to check md5, doesn't respond during that time)
it failed. so i pulled phone in battery and tried to turn on recovery, it sent me to the download screen and said the verizon update failed. tried to reinstall rom again. pulled battery. said same thing.
i reflashed the TWRP i was using with odin, doing the AP button with it too.
[[It will say failed on deviced and in odin]]
phone now boots up.
[btw the temp root i did was kingroot]
http://forum.xda-developers.com/devdb/project/dl/?id=12450
here is the original post for what i was doing
http://forum.xda-developers.com/note-4-verizon/general/note-4-verizon-bootloader-unlock-t3358913
the two walk throughs i found
1. http://forum.xda-developers.com/note-4-verizon/general/howto-converting-retail-note-4-to-t3358957
2. http://www.techtimes.com/articles/152037/20160421/modder-unlocks-verizon-galaxy-note-4-bootloader-heres-how-to-do-it.htm
the stock recovery( reason for old version is because a few can update from this one)
http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_146187538272120&key=f0a7f91912ae2b52e0700f73990eb321&libId=inkoi1eq01000n4o000DLb61t4tis&loc=http%3A%2F%2Fforum.xda-developers.com%2Fnote-4-verizon%2Fdevelopment%2Ffirmware-firmware-kernel-modem-recovery-t2942937&v=1&out=https%3A%2F%2Fwww.androidfilehost.com%2F%3Ffid%3D24052804347793292&ref=https%3A%2F%2Fwww.google.com%2F&title=%5BFirmware%5D%20%5BOfficial%5D%20Firmware%20%2F%20Kernel%20%2F%20Mo%E2%80%A6%20%7C%20Verizon%20Samsung%20Galaxy%20Note%204&txt=https%3A%2F%2Fwww.androidfilehost.com%2F%3Ffid%3D24052804347793292
this is the main page to find the stock roms
http://forum.xda-developers.com/note-4-verizon/development/firmware-firmware-kernel-modem-recovery-t2942937

i may have put the wrong title

dragont4 said:
i may have put the wrong title
Click to expand...
Click to collapse
Try adb push worked for me

axeldiks1 said:
Try adb push worked for me
Click to expand...
Click to collapse
for moving files right?

fixed!!

dragont4 said:
for moving files right?
Click to expand...
Click to collapse
Yes just download a rom and flash it after you push it to your storage

dragont4 said:
so i followed the recent bootloader unlock, i have the retail in developer mode, i got twrp installed, this i where it gets messy, it went into a bootloop, so i did a wipe on the cache and davk cach, didn't work. even pulled the battery, so i tried the format. same problem, did work, so i did a wipe again which i think i really broke it when i wiped all but the sdcard, so now, NO OS. so i'm trying to get files to reflash stock roms, i found downloads to the stock files btw, currently downloading.
so, i have twrp
no backup (i'ma idiot lol)
no OS installed
bootloader is confirmed to be in developer mode
can't get phone to access fastboot. via adb
only recovery and download avaible
[edit, i can move files onto my sd card by using another phone to move files]
so do i continue with trying to use idon to flash stock rom onto the phone? will twrp still be installed? and will i keep my developer unlocked booloader?
twrp is v2.8.5.0
(been working on this for about 14 hours now)
FIXED!!
ok, so i found a stock recovery file, md5.tar, i'll post a link below.
i used odin, put phone into download mode, connected with odin running as administrator.
selected the file i used in the AP button, (had to wait awhile for it to check md5, doesn't respond during that time)
it failed. so i pulled phone in battery and tried to turn on recovery, it sent me to the download screen and said the verizon update failed. tried to reinstall rom again. pulled battery. said same thing.
i reflashed the TWRP i was using with odin, doing the AP button with it too.
[[It will say failed on deviced and in odin]]
phone now boots up.
[btw the temp root i did was kingroot]
http://forum.xda-developers.com/devdb/project/dl/?id=12450
here is the original post for what i was doing
http://forum.xda-developers.com/note-4-verizon/general/note-4-verizon-bootloader-unlock-t3358913
the two walk throughs i found
1. http://forum.xda-developers.com/note-4-verizon/general/howto-converting-retail-note-4-to-t3358957
2. http://www.techtimes.com/articles/152037/20160421/modder-unlocks-verizon-galaxy-note-4-bootloader-heres-how-to-do-it.htm
the stock recovery( reason for old version is because a few can update from this one)
http://click.xda-developers.com/api/click?format=go&jsonp=vglnk_146187538272120&key=f0a7f91912ae2b52e0700f73990eb321&libId=inkoi1eq01000n4o000DLb61t4tis&loc=http%3A%2F%2Fforum.xda-developers.com%2Fnote-4-verizon%2Fdevelopment%2Ffirmware-firmware-kernel-modem-recovery-t2942937&v=1&out=https%3A%2F%2Fwww.androidfilehost.com%2F%3Ffid%3D24052804347793292&ref=https%3A%2F%2Fwww.google.com%2F&title=%5BFirmware%5D%20%5BOfficial%5D%20Firmware%20%2F%20Kernel%20%2F%20Mo%E2%80%A6%20%7C%20Verizon%20Samsung%20Galaxy%20Note%204&txt=https%3A%2F%2Fwww.androidfilehost.com%2F%3Ffid%3D24052804347793292
this is the main page to find the stock roms
http://forum.xda-developers.com/note-4-verizon/development/firmware-firmware-kernel-modem-recovery-t2942937
Click to expand...
Click to collapse
I'm glad that you fixed it, but I just wanted to say what I think your problem was so that other people can fix it with a little less pain.
The bootloader unlock writes files to your sd card during the process. That's why the instructions state to use an SD card that you can set aside later. If you leave that SD card in the phone when you boot, you will bootloop. Simply removing the SD card and putting in another one will work. You can also remove the SD card, format it, and put it back in.

ssj4gogeta2003 said:
I'm glad that you fixed it, but I just wanted to say what I think your problem was so that other people can fix it with a little less pain.
The bootloader unlock writes files to your sd card during the process. That's why the instructions state to use an SD card that you can set aside later. If you leave that SD card in the phone when you boot, you will bootloop. Simply removing the SD card and putting in another one will work. You can also remove the SD card, format it, and put it back in.
Click to expand...
Click to collapse
Yeah I was thinkong about that. I had pulled the sd card right after due to boot loop. Think it had to do with the sd card. I messed a step up I believe there at the end.
Sorry for the late reply guys

[Q] Phone Won't Boot - Possibly dead eMMC

Hello XDA,
Recently, a Samsung Captivate Glide was given to me to see if I could repair it. They told me the phone wouldn't turn on anymore, the screen remained black. Although they said they had just replaced the battery, I insisted that the battery was the problem. Upon hooking it up to a multimeter it became apparent that the battery was in deep sleep so I recovered it with a sliced USB cable. The phone then turned on to charge, but since I didn't feel like waiting for it to charge I inserted my S2 battery to boot it up.
Upon booting up the phone the Rogers screen came up (it's the Rogers model - sch-i927r), it adjust the brightness a bit and then proceeded to sit there forever. Since it wouldn't boot up I tried checking if Download Mode was still working. And it was! Same goes for the Android Recovery. Since this phone was never rooted or had a custom recovery it still had Gingerbread. Since the owner needed some files that were still on the phone I decided to flash TWRP, the CM11 compiled one, copy all the files to my PC and proceed to flash CM11 after making a backup.
However the phone refused to flash TWRP. I also tried CWM and going back to Stock but had no positive results. I even tried different Odin versions and different PCs. All of them gave out the same error that I have attached as a Picture. Upon googling it it seems like the storage is in read only mode, which I learnt from the Galaxy Tab 10.1 forums and also that the only solution would be to go back to Samsung.
Lastly I attempted to wipe from the built in recovery It asked for a password, however the original owner claimed he never had one. Upon forcing the flash by entering the wrong password the phone said it completed successfully but looking at the internal storage proves otherwise as all the files are still there. Trying to reboot to the system makes it either go to a black screen or corrupt the GPU memory (possibly - see attached pics.).
Looking around on the XDA forums I stumbled upon a thread by @steadfasterX which made a mod to boot the phone from an SD card. Since the eMMC of the phone is likely corrupt and causing this, could we use an SD card as the internal storage and boot up from there?
I am out of ideas. I don't have a backup of the EFS so I am being really cautious and fixing it wouldn't be worth it. So please help me! Any help is very much appreciated!
Thanks in advance!

chrismin13 said:
Hello XDA,
Recently, a Samsung Captivate Glide was given to me to see if I could repair it. They told me the phone wouldn't turn on anymore, the screen remained black. Although they said they had just replaced the battery, I insisted that the battery was the problem. Upon hooking it up to a multimeter it became apparent that the battery was in deep sleep so I recovered it with a sliced USB cable. The phone then turned on to charge, but since I didn't feel like waiting for it to charge I inserted my S2 battery to boot it up.
Upon booting up the phone the Rogers screen came up (it's the Rogers model - sch-i927r), it adjust the brightness a bit and then proceeded to sit there forever. Since it wouldn't boot up I tried checking if Download Mode was still working. And it was! Same goes for the Android Recovery. Since this phone was never rooted or had a custom recovery it still had Gingerbread. Since the owner needed some files that were still on the phone I decided to flash TWRP, the CM11 compiled one, copy all the files to my PC and proceed to flash CM11 after making a backup.
However the phone refused to flash TWRP. I also tried CWM and going back to Stock but had no positive results. I even tried different Odin versions and different PCs. All of them gave out the same error that I have attached as a Picture. Upon googling it it seems like the storage is in read only mode, which I learnt from the Galaxy Tab 10.1 forums and also that the only solution would be to go back to Samsung.
Lastly I attempted to wipe from the built in recovery It asked for a password, however the original owner claimed he never had one. Upon forcing the flash by entering the wrong password the phone said it completed successfully but looking at the internal storage proves otherwise as all the files are still there. Trying to reboot to the system makes it either go to a black screen or corrupt the GPU memory (possibly - see attached pics.).
Looking around on the XDA forums I stumbled upon a thread by @steadfasterX which made a mod to boot the phone from an SD card. Since the eMMC of the phone is likely corrupt and causing this, could we use an SD card as the internal storage and boot up from there?
I am out of ideas. I don't have a backup of the EFS so I am being really cautious and fixing it wouldn't be worth it. So please help me! Any help is very much appreciated!
Thanks in advance!
Click to expand...
Click to collapse
you can not boot from sd card, you can use sd card as system partition, but you still need place kernel+ramdisk on internal flash.
You can try to replace bootloader

bubor said:
you can not boot from sd card, you can use sd card as system partition, but you still need place kernel+ramdisk on internal flash.
You can try to replace bootloader
Click to expand...
Click to collapse
Thanks for the reply, I'll try updating the bootloader. Would it be risky though? I couldn't flash anything else and have no nandroid backup. Also, how would I go about using the SD Card as system?
EDIT: Risked it, flashed correctly but I still get the same error and I still have the Rogers bootloader. Any other ideas?

chrismin13 said:
Thanks for the reply, I'll try updating the bootloader. Would it be risky though? I couldn't flash anything else and have no nandroid backup. Also, how would I go about using the SD Card as system?
EDIT: Risked it, flashed correctly but I still get the same error and I still have the Rogers bootloader. Any other ideas?
Click to expand...
Click to collapse
maybe check "phone bootloader update" on the left side, I think I didnt check when I did update, and it worked without checking.
First try this pack: http://dualhoki.vim.hu/bubor/dev/I927UCLG9_OneClick.exe
Try to repartition with pit file ( put pit file in pit box, no other files, and check re-partition)
You can find an alternative of odin http://glassechidna.com.au/heimdall/ . I remember there are many other options in heimdall, maybe you can find usefull error messages.

bubor said:
maybe check "phone bootloader update" on the left side, I think I didnt check when I did update, and it worked without checking.
First try this pack: http://dualhoki.vim.hu/bubor/dev/I927UCLG9_OneClick.exe
Try to repartition with pit file ( put pit file in pit box, no other files, and check re-partition)
You can find an alternative of odin http://glassechidna.com.au/heimdall/ . I remember there are many other options in heimdall, maybe you can find usefull error messages.
Click to expand...
Click to collapse
Hello,
Sorry for the late response. I got around to trying most of that. First off the PIT File was something that I was looking forward to since it seemed the most likely solution. However it didn't work, giving out a similar message as everything else. The OneClick also failed with a similar message. As for heimdall I couldn't get the drivers to work but even if I had it wouldn't have helped anymore most likely.
I am out of ideas. I highly doubt this phone is recoverable at this point.
Thank you for all the help so far!

Anyone got any other ideas? I think it's safe to call it dead at this point, but I am willing to try anything to fix it!
Thanks.