I have an AT&T HTC One that was converted a Developer Edition, so it is S-OFF and has an unlocked bootloader, otherwise it is running completely stock non-rooted Lollipop firmware. I want to flash a custom recovery, but the safer side of my mind always tests it by doing "fastboot boot recovery.img" first before flashing it. The problem is on this phone it will load, I can see the green bar on the side of the Hboot screen go up, and fastboot says it sent the file successfully, but it just locks up and does nothing, I have to long-press power for 15 seconds or so to get it to shutdown to get it to respond again.
I have tried several versions of TWRP from here: http://techerrata.com/browse/twrp2/m7 and all have the same results. I am very familiar with using fastboot and adb, so I don't think I am doing anything wrong, but I am scared to flash the recovery image if I can't boot it.
Any ideas?
acejavelin said:
I have an AT&T HTC One that was converted a Developer Edition, so it is S-OFF and has an unlocked bootloader, otherwise it is running completely stock non-rooted Lollipop firmware. I want to flash a custom recovery, but the safer side of my mind always tests it by doing "fastboot boot recovery.img" first before flashing it. The problem is on this phone it will load, I can see the green bar on the side of the Hboot screen go up, and fastboot says it sent the file successfully, but it just locks up and does nothing, I have to long-press power for 15 seconds or so to get it to shutdown to get it to respond again.
I have tried several versions of TWRP from here: http://techerrata.com/browse/twrp2/m7 and all have the same results. I am very familiar with using fastboot and adb, so I don't think I am doing anything wrong, but I am scared to flash the recovery image if I can't boot it.
Any ideas?
Click to expand...
Click to collapse
Only hboot 1.44 will boot recovery .. all the others need to be flashed
TWRP 2.6.3.3 is the most stable
TWRP 2.8.4.0 is what I use with no problems
clsA said:
Only hboot 1.44 will boot recovery .. all the others need to be flashed
Click to expand...
Click to collapse
OK, that makes sense then... I am on 1.61 I think, and when I got it it was on 1.5 something.
Seems odd that being S-off and unlocked prevents fastboot booting to occur... wonder why?
acejavelin said:
OK, that makes sense then... I am on 1.61 I think, and when I got it it was on 1.5 something.
Seems odd that being S-off and unlocked prevents fastboot booting to occur... wonder why?
Click to expand...
Click to collapse
it was patched in the hboot to not allow it
clsA said:
it was patched in the hboot to not allow it
Click to expand...
Click to collapse
I guess I can see why they would do that, sort of, not that I agree... On my old HTC Rezound you could boot recovery and backup, wipe caches, etc, as long as you didn't write to boot/system/etc, without triggering the TAMPERED flag, you had to flash recovery or write to a system partition in order to set that flag. Oh well, Ill flash it up soon and play with it. I am actually kind of liking the stock lollipop Sense ROM, might just leave it like that for a bit though. Just came back from the range and had a little time before work so I was playing with it and it kind of frustrated me.
Thanks for your help and info.
Related
Hi all,
Got a sensation XL here which isn't rooted, nor has it been altered in anyway, not sure what happened to it to be honest and it's not actually mine either.
It's still s-on, I can get to the bootloader no problem, but factory reset just doesn't do anything, it just puts it back in the boot loop.
Any ideas?
Thanks.
PS: I'm thinking it's bricked.
Lock the bootloader (if that's been unlocked) and then try flashing the RUU to put it back to factory.
You're in england, so unless it's branded, the RUU you need is in the RUU thread in the dev forum, and it's 1.05.401.x that you want.
MinecraftZombi.es said:
Lock the bootloader (if that's been unlocked) and then try flashing the RUU to put it back to factory.
You're in england, so unless it's branded, the RUU you need is in the RUU thread in the dev forum, and it's 1.05.401.x that you want.
Click to expand...
Click to collapse
It's not been unlocked, it's just a stock handset, not branded, so with the official ruu, how do i flash it?
Thanks for replying m8.
make sure htc sync is installed on a PC (just for the drivers, you don't want to actually use it)
Plug the phone in via the USB (Direct, not through a hub)
Run RUU file on PC.
that should be it.
Thanks pal, fingers crossed eh.
Will let you know if it worked.
It didn't work
Tried both of the Europe RUU's but it still hasn't worked, says signature error?
Both of the files took an hour to download each.
Seriously hating this now
Any other ideas??
Thanks.
if that hasn't worked, next thing i'd try is to flash a custom ROM.
Can it get into fastboot?
If so, i'd unlock the bootloader, install the recovery and see if you can flash one of the custom ROMs.
MinecraftZombi.es said:
if that hasn't worked, next thing i'd try is to flash a custom ROM.
Can it get into fastboot?
If so, i'd unlock the bootloader, install the recovery and see if you can flash one of the custom ROMs.
Click to expand...
Click to collapse
Yea i went ahead and unlocked it but it's not letting me into the recovery, any ideas?
dladz said:
Yea i went ahead and unlocked it but it's not letting me into the recovery, any ideas?
Click to expand...
Click to collapse
Actually no i didn't i just used the HTC method.
What can i flash to get this thing working man, it's killing me, even factory reset doesn't work? That's just not normal, i'm s-on, i don't think theres an s-off method for the XL yet? Maybe there is.
But i'm really restricted as to what i can do, i've got fastboot and it works fine but besides that i'm lost.
factory reset uses the recovery partition. if that's chuffed, so's your hard reset.
I have attached the stock recovery from 1.05
go into fastboot.
when there, enter
Code:
fastboot flash recovery recovery.img
That should re-flash the recovery as long as your bootloader is unlocked. that might bring it back to life.
if it fails, flash the CWM recovery and then use a custom ROM
download the paul o'brien recovery and then use the same command as above, but using the name of the modaco recovery file
Code:
fastboot flash recovery r1-recovery-clockwork-5.0.2.7-modaco-runnymede.img
that should then allow you to flash a custom ROM
Ok so it's not bootlooping now on factory reset, it's just stopped on the white HTC screen after hitting factory reset.
I'll leave it there for a bit and see how it goes, i don't think it's going to progress though.
The device is defo unlocked.
Going into recovery brings it back to the bootloop.
It's different on factory reset just not recovery and neither are progressing, i'll give the other recovery a whirl.
Lol failed battery low
MinecraftZombi.es said:
factory reset uses the recovery partition. if that's chuffed, so's your hard reset.
I have attached the stock recovery from 1.05
go into fastboot.
when there, enter
Code:
fastboot flash recovery recovery.img
That should re-flash the recovery as long as your bootloader is unlocked. that might bring it back to life.
if it fails, flash the CWM recovery and then use a custom ROM
download the paul o'brien recovery and then use the same command as above, but using the name of the modaco recovery file
Code:
fastboot flash recovery r1-recovery-clockwork-5.0.2.7-modaco-runnymede.img
that should then allow you to flash a custom ROM
Click to expand...
Click to collapse
Nah m8, none of them worked or changed anything, the only difference being that factory reset on the stock recovery just stayed on the white htc screen, no change besides that.
Any other ideas? and thanks for taking the time to help me too.
I appreciate it.
I'm really not sure what else to suggest. if recovery just isn't loading after being flashed, then it suggests some sort of brick i think...
Even if there's no ROM installed, once a recovery is flashed, you should be able to at least access the recovery and from there install some sort of rom.
I'm beginning to suspect that it is indeed bricked, as you did in the first post.
MinecraftZombi.es said:
I'm really not sure what else to suggest. if recovery just isn't loading after being flashed, then it suggests some sort of brick i think...
Even if there's no ROM installed, once a recovery is flashed, you should be able to at least access the recovery and from there install some sort of rom.
I'm beginning to suspect that it is indeed bricked, as you did in the first post.
Click to expand...
Click to collapse
well i've been looking for some official ruu's to flash, one up from the one i'm on would do it i reckon, or at least give me a starting block.
I tried the test rom from a thread and now i can't find it
Will look again, find it and flash it, the test one didn't work, so i'm going to try a slightly older one.
fingers crossed, again.
im a HTC one user. Currently on a formatted sd card. that is, no android rom or software. All I have right now on my phone is an unlocked bootloader 1.54
CWM Recovery Touch v6.0.3.6
I am familiar with pushing roms from mac through adb commands on the sd card. learnt that when i bricked it last time. this time, i cant understand the problem. Umm.. I updated my ARHD rom to 4.3 stock google one from 4.2.2 sense based roms. After that, i remember, going through several roor related issues. So i tried switching roms. i tried flashing various roms but i couldnt get any of em to work. i tried flashing roms after wiping cache and everything recommended, but every rom got stuck on reboot. except the nandroid backup. nandroid backup worked fine. so i tried formatting the sd card as well and flashing a rom after pushng it by adb commands. i think i have problems with my root access. i tried flashing cwm recovery all over again through fastboot, but it still boots up randomly. and im still stuck on the google splashup screen. it keeps rebooting and getting stuck on the splashup screen and doesnt get past that to the htc reboot screen. I dont know what to do. splash up screen doesnt let me access adb commands. and i think i have improper root access as whenever i try to reboot from cwm recovery, it warns me about the su binary and then gets stuck stuck in a loop again.
please help me guys?
:crying:
ayeyokp said:
im a HTC one user. Currently on a formatted sd card. that is, no android rom or software. All I have right now on my phone is an unlocked bootloader 1.54
CWM Recovery Touch v6.0.3.6
I am familiar with pushing roms from mac through adb commands on the sd card. learnt that when i bricked it last time. this time, i cant understand the problem. Umm.. I updated my ARHD rom to 4.3 stock google one from 4.2.2 sense based roms. After that, i remember, going through several roor related issues. So i tried switching roms. i tried flashing various roms but i couldnt get any of em to work. i tried flashing roms after wiping cache and everything recommended, but every rom got stuck on reboot. except the nandroid backup. nandroid backup worked fine. so i tried formatting the sd card as well and flashing a rom after pushng it by adb commands. i think i have problems with my root access. i tried flashing cwm recovery all over again through fastboot, but it still boots up randomly. and im still stuck on the google splashup screen. it keeps rebooting and getting stuck on the splashup screen and doesnt get past that to the htc reboot screen. I dont know what to do. splash up screen doesnt let me access adb commands. and i think i have improper root access as whenever i try to reboot from cwm recovery, it warns me about the su binary and then gets stuck stuck in a loop again.
please help me guys?
:crying:
Click to expand...
Click to collapse
Flash stock recovery, then run it to flash stock.
ayeyokp said:
im a HTC one user. Currently on Renoir atted sd card. that is, no android rom or software. All I have right now on my phone is an unlocked bootloader 1.54
CWM Recovery Touch v6.0.3.6
I am familiar with pushing roms from mac through adb commands on the sd card. learnt that when i bricked it last time. this time, i cant understand the problem. Umm.. I updated my ARHD rom to 4.3 stock google one from 4.2.2 sense based roms. After that, i remember, going through several roor related issues. So i tried switching roms. i tried flashing various roms but i couldnt get any of em to work. i tried flashing roms after wiping cache and everything recommended, but every rom got stuck on reboot. except the nandroid backup. nandroid backup worked fine. so i tried formatting the sd card as well and flashing a rom after pushng it by adb commands. i think i have problems with my root access. i tried flashing cwm recovery all over again through fastboot, but it still boots up randomly. and im still stuck on the google splashup screen. it keeps rebooting and getting stuck on the splashup screen and doesnt get past that to the htc reboot screen. I dont know what to do. splash up screen doesnt let me access adb commands. and i think i have improper root access as whenever i try to reboot from cwm recovery, it warns me about the su binary and then gets stuck stuck in a loop again.
please help me guys?
:crying:
Click to expand...
Click to collapse
If you are unlocked but still S-ON...use revone to make it S-OFF
Than:
1) hold power button until the phone force reboots and in the meantime press vol - button to get into bootloader
2) now go to fastboot and plug the phone to the pc
3) through command line "fastboot writecid 11111111"
4) reboot bootloader
5) now you have supercid, flash any RUU and start using again your HTC one
I think it should work, sorry for my bad english
OsarcotL said:
If you are unlocked but still S-ON...use revone to make it S-OFF
Click to expand...
Click to collapse
He's on 1.54, he can't go s-off.
OsarcotL said:
If you are unlocked but still S-ON...use revone to make it S-OFF
Than:
1) hold power button until the phone force reboots and in the meantime press vol - button to get into bootloader
2) now go to fastboot and plug the phone to the pc
3) through command line "fastboot writecid 11111111"
4) reboot bootloader
5) now you have supercid, flash any RUU and start using again your HTC one
I think it should work, sorry for my bad english
Click to expand...
Click to collapse
i have a unlocked bootloader. and i have a s-off too! i achieved s-off through revone only!
OsarcotL said:
If you are unlocked but still S-ON...use revone to make it S-OFF
Than:
1) hold power button until the phone force reboots and in the meantime press vol - button to get into bootloader
2) now go to fastboot and plug the phone to the pc
3) through command line "fastboot writecid 11111111"
4) reboot bootloader
5) now you have supercid, flash any RUU and start using again your HTC one
I think it should work, sorry for my bad english
Click to expand...
Click to collapse
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?
ayeyokp said:
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?
Click to expand...
Click to collapse
i know that with supercid you can flash any RUU beacuse it bypasses the normal country control during the istallation of the program...
now, i don't know if you cant flash anything with the 1.54 hboot, but i dont think so. according to me, you can try to flash and in the worst case the istallation wont start...but obviously is your phone and your decisone, just as it is your responsability
ayeyokp said:
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?
Click to expand...
Click to collapse
Since you're S-Off and SuperCID you can flash any RUU, so just go ahead and you won't loose S-Off either.
The 1.54 restrictions only apply if you're not S-Off, because S-On won't allow you to downgrade. Since you're S-Off it will allow the RUU downgrade.
ayeyokp said:
i did some research on xda again before flashing the RUU !! I just wanted to know if i can flash any RUU or should i look for my area's RUU, that is, asia or worldwide one. and i have s-off, HBOOT-1.54, and i have superCID too! already! should i go ahead with flashing the RUU? some threads stated that i cant do it on 1.54?
Click to expand...
Click to collapse
Being s-off means you can flash anything, even stuff not for this phone. So be careful.
Ruu.exe for Asia
http://www.androidruu.com/getdownlo...50.13_10.33.1150.01_release_311678_signed.exe
Or Europe
http://www.androidruu.com/getdownlo...31.27_10.31.1131.05_release_310878_signed.exe
Download the Ruu of your choice to your pc.
Connect phone via usb2 to pc with phone in fastboot usb mode
Run ruu you downloaded , answer questions as appropriate
Approximately ten minutes to have stock Rom and stock recovery
Will retain s off . Can accept ota updates without losing s off
Sent from my HTC One using xda app-developers app
Tried a new ROM but it froze on me. Then tried my back up and it would reboot after like a minute. So decided to do a full wipe but it deleted everything. I can get into the bootloader screen and TWRP but Windows can't read the phone and when it tries to install the drivers some of them fail. I have a copy of my recovery but need to know how to push it back to my phone and get the drivers installed right so that my PC can read my phone. Help.
TWRP seems to now act funny too where it'll like go to sleep and I have to press the home button or power button for a while before it turns the screen back on. Sometimes though I have to do the button combo to get back into recovery.
RUU
So I RUU'd the phone and it's working now, thanks. But it still shows unlocked and with S-OFF. So at this point can I just proceed with rooting it or do I have to lock it and put it back to S-ON before trying to re-root it? Or can I just try rooting it and putting a recovery image on it? It's been a while since I rooted it and obviously there was no 4.3 out at that time.
No need to re-lock or s-on just flash recovery and flash a rooted rom
bigdaddy619 said:
No need to re-lock or s-on just flash recovery and flash a rooted rom
Click to expand...
Click to collapse
Thanks for taking the time to help me out. So I installed v.2.5 of TWRP that I had instead of the newer version and it just freezes at the main screen. I can reflash it but it does the same thing. I get an error when trying to flash the newer version. How can I remove/delete the recovery image to flash the latest version?
QuiQNeZZ said:
Thanks for taking the time to help me out. So I installed v.2.5 of TWRP that I had instead of the newer version and it just freezes at the main screen. I can reflash it but it does the same thing. I get an error when trying to flash the newer version. How can I remove/delete the recovery image to flash the latest version?
Click to expand...
Click to collapse
You should be able to flash right over the older version make sure you download a fresh version of 2.6.3.0 from here http://techerrata.com/browse/twrp2/m7wls
Also remember after flashing the recovery.img type fastboot erase cache
The other thing is go into settings/screen and disable screen timeout that should take care of the "freezing" problem
Hi all.
I tried to flash my HTC one from recovery (twrp) after doing a factory reset within twrp. (I thought at the time a had stock recovery, I didn't. I had twrp.
Now my phone won't boot. Gets stuck on splash screen. If i enter the bootloader (which works no problem) and choose recovery, it starts recovery, pops up with twrp splash screen for second, then reboots to frozen htc splash screen.
Fastboot is working.
I've tried clearing the cache using fastboot. samething
I've tried flashing other recoveries,. nothing samething. (others in different predicaments have been able to do this successfully)
I've been reading that returning back to stock using RUU.zip method is the only way to go.
I want to try that, but before I do, I must make sure I understand it correctly and I've done all I can.
Relock the bootloader? Can I unlock it again?
Find a RUU.Zip that matches my OS version
Flash using fastboot.
I've been looking through HTC1GURU at his collection of ruu.zip but can't find anything that really matches my OS.
Any suggestions and advice will be most welcome.
Thanks in advance
Phone info.....
my Original CID was....orang001
profixit said:
Hi all.
I tried to flash my HTC one from recovery (twrp) after doing a factory reset within twrp. (I thought at the time a had stock recovery, I didn't. I had twrp.
Now my phone won't boot. Gets stuck on splash screen. If i enter the bootloader (which works no problem) and choose recovery, it starts recovery, pops up with twrp splash screen for second, then reboots to frozen htc splash screen.
Fastboot is working.
I've tried clearing the cache using fastboot. samething
I've tried flashing other recoveries,. nothing samething. (others in different predicaments have been able to do this successfully)
I've been reading that returning back to stock using RUU.zip method is the only way to go.
I want to try that, but before I do, I must make sure I understand it correctly and I've done all I can.
Relock the bootloader? Can I unlock it again?
Find a RUU.Zip that matches my OS version
Flash using fastboot.
I've been looking through HTC1GURU at his collection of ruu.zip but can't find anything that really matches my OS.
Any suggestions and advice will be most welcome.
Thanks in advance
Phone info.....
my Original CID was....orang001
Click to expand...
Click to collapse
There isn't any ruu for orange (.61 base) only a nandroid backup which require a working recovery to be flashed. if you don't really care about staying with the orange sw, you could simply restore your phone to international EU version (.401 base). You already have s-off and the proper mid, so it will only require to downgrade hboot to 1.44, change cid to HTC__001 and run the 1.29.401 ruu.exe. you can use this guide
Thanks for the quick reply and the guide.
I don't care about orange sw. I'll do some reading. I do have a nandroid backup. No good to me, unless I get recovery working.
Not too confident about downgrading the Hboot, but i'll read and read.
profixit said:
Thanks for the quick reply and the guide.
I don't care about orange sw. I'll do some reading. I do have a nandroid backup. No good to me, unless I get recovery working.
Not too confident about downgrading the Hboot, but i'll read and read.
Click to expand...
Click to collapse
downgrading hboot is pretty easy
just follow the steps under ''If you’re on hboot which is above 1.44'' from nkk71's guide
then change cid
then run ruu.exe
but do not use a win 8.1 computer (compatibility issue with hboot 1.44)
Thanks for that last bit, what about Win8.
I've spotted the steps that apply to me, just playing them out in my head.
Out of curiosity after a downgrade the HBoot, will it be locked and s-on?
profixit said:
Thanks for that last bit, what about Win8.
Click to expand...
Click to collapse
windows 8.0 should be fine, but definitively not 8.1
alray said:
There isn't any ruu for orange (.61 base) only a nandroid backup which require a working recovery to be flashed. if you don't really care about staying with the orange sw, you could simply restore your phone to international EU version (.401 base). You already have s-off and the proper mid, so it will only require to downgrade hboot to 1.44, change cid to HTC__001 and run the 1.29.401 ruu.exe. you can use this guide
Click to expand...
Click to collapse
I noticed that particular 1.29.401 ruu exe has a different model ID, gonna course problems?
profixit said:
I noticed that particular 1.29.401 ruu exe has a different model ID, gonna course problems?
Click to expand...
Click to collapse
sry my bad
use this one: http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_htc_europe_1-28-401-7_radio_4a-13-3231-27_10-31-1131-05_release_310878_signed-exe/
1.28.401
No worries, Thanks.
Can you try fastboot erase cache from fastboot menu and re enter recovery?
Tried that, thanks
Sent from my HTC One using Tapatalk
OK, a little lucky positive progress.
I managed to flash clockworkMod recovery, don't ask me how, maybe erasing the cache lots of times did it, i'm sure it was a recovery I had already tried. I checked my download list and confirmed I did download it., so i would of tried to flash it two days ago. Funny.
Still stuck on splash screen, but can boot into recovery. (clockworkmod)
Please, what is the best way to proceed, I'm thinking nandroid backup, but like I said, I couldn't care less about orange. I would love to put Mike1986 stock rom 4.3 or 4.4
I'm unable or don't know how to get folders or files on the phone's internal SD card, because it doesn't boot up a rom any more. Y-cable?
I'm concerned with all the "can't" at the bottom of recovery screen.
my htc m7 got bricked and stuck in a bootloop after two days of being OTA updated to lollipop, knowing that it's S-on and bootloader locked, now when i try to unlock it through HTCDEv everything goes well but when the phone reboots it would still be locked and won't enter recovery! and when trying to flash a stock firmware instead of rebooting to bootloader (fastboot oem rebootRUU) the phone would reboot to system and stuck in boot loop, any solution to flash the phone back to normal?
If you are using Clockwork Mod, then there should be a way to get back into the rom flash option. Go into your "Power/Volume Down" page, and look for the option to flash from zip. Find the zip you used when ORIGINALLY flashing to your custom rom. Do not try to go to stock at first, work your way backwards. If you can get back to the working custom rom, from there you can use on screen functions to repair the phone back to stock.
yakie47 said:
my htc m7 got bricked and stuck in a bootloop after two days of being OTA updated to lollipop, knowing that it's S-on and bootloader locked, now when i try to unlock it through HTCDEv everything goes well but when the phone reboots it would still be locked and won't enter recovery! and when trying to flash a stock firmware instead of rebooting to bootloader (fastboot oem rebootRUU) the phone would reboot to system and stuck in boot loop, any solution to flash the phone back to normal?
Click to expand...
Click to collapse
Looks like you are having firmware or hardware issue. We often see this problem (not being able to unlock the bootloader) when the phone was relocked with a custom recovery still installed. But it doesn't seem to be your case since your phone is s-on and locked unless you tell me that you did re-locked the bootloader with a custom recovery installed...
Unfortunately the only walk around for this issue is to flash the same version stock firmware.zip in ruu mode which is not accessible in your case.
Why you can't access the ruu mode, I really don't know, it might confirm an firmware issue, maybe with the bootloader. Your not the first one stuck in that situation (not unlockable + ruu mode broken), its not common but you are not the first.
Btw is your phone a GPE or Sense variant? GPE variant have a well known bug which will prevent the bootloader to be unlocked. Does not apply to Sense variants.
I'm afraid there is nothing to do if you can't unlock or access ruu mode. Maybe a jtag repair could work or you'll have to send it for repair.
Sorry
ethanvallivue said:
If you are using Clockwork Mod, then there should be a way to get back into the rom flash option.
Click to expand...
Click to collapse
OP said he was bootloader locked so he can't use a custom recovery.
Go into your "Power/Volume Down" page, and look for the option to flash from zip.
Click to expand...
Click to collapse
There is no such option for HTC devices. To flash stock zip on the M7 you must access RUU mode, OP said RUU mode is broken...
Find the zip you used when ORIGINALLY flashing to your custom rom. Do not try to go to stock at first, work your way backwards. If you can get back to the working custom rom, from there you can use on screen functions to repair the phone back to stock.
Click to expand...
Click to collapse
Don't understand why you are talking about custom roms, did you read the OP?
I appreciate your responds guys and i believe the only option left is the jtag i guess..