Database Develop

[ON HOLD] Stuck in boot screen (not bootloader, rooted)

Hi, after searching through many posts and trying different things which didn't solve my problem for ours, I decided to just ask...
I have a rooted HTC (Switzerland / Europe version) and I tried to unroot it with different "europe" RUU's from this forum, none worked but I saw in the comments that some of those RUU's required S-OFF. So without any experience whatsoever my mastermind decided to just give it a try and turn S-OFF with the moonshine method. I guess I chose the wrong file (again?) and it didnt work, it always ran 10 restarts in the moonshine method at the end and then the error message "don't drink and shine" popped up. So I gave up and just started the phone.
After starting, I realised that the WIFI and the camera wasn't working anymore (tried all I could) and again I came to this forum and looked for solutions. I tried to wipe everything on the phone, including data wipe and all the wiped I found in twrp. After I did that, I chose the option reboot and well, the phone didnt shut off anymore and I was stuck in the starting screen ( HTC - quitly brilliant -- with the text below: this build is for development....) I tried all the shut down methods with sound button down and so on, also to keep a fleshlight on it (found: http://forum.xda-developers.com/showthread.php?t=2418404 )
I don't know what else to do and I'm pretty much lost. I shouldn't have tried all this without the knowledge damn -.-
please help!

Enion said:
Hi, after searching through many posts and trying different things which didn't solve my problem for ours, I decided to just ask...
I have a rooted HTC (Switzerland / Europe version) and I tried to unroot it with different "europe" RUU's from this forum, none worked but I saw in the comments that some of those RUU's required S-OFF. So without any experience whatsoever my mastermind decided to just give it a try and turn S-OFF with the moonshine method. I guess I chose the wrong file (again?) and it didnt work, it always ran 10 restarts in the moonshine method at the end and then the error message "don't drink and shine" popped up. So I gave up and just started the phone.
After starting, I realised that the WIFI and the camera wasn't working anymore (tried all I could) and again I came to this forum and looked for solutions. I tried to wipe everything on the phone, including data wipe and all the wiped I found in twrp. After I did that, I chose the option reboot and well, the phone didnt shut off anymore and I was stuck in the starting screen ( HTC - quitly brilliant -- with the text below: this build is for development....) I tried all the shut down methods with sound button down and so on, also to keep a fleshlight on it (found: http://forum.xda-developers.com/showthread.php?t=2418404 )
I don't know what else to do and I'm pretty much lost. I shouldn't have tried all this without the knowledge damn -.-
please help!
Click to expand...
Click to collapse
If you can restart and get into bootloader by holding power and vol. down, flash TWRP, put your RUU zip on your phone storage, and then flash it.

kibmikey1 said:
If you can restart and get into bootloader by holding power and vol. down, flash TWRP, put your RUU zip on your phone storage, and then flash it.
Click to expand...
Click to collapse
Hi, thanks for your advice. The problem is that, after recharging the phone again and trying several times, I just can't get into bootloader. When I hold the power button and vol. down the home and "arrow" touch-buttons at the bottom of the phone just start blinking. As long as I hold these two buttons the blinking doesn't stop, I did hold them for a full minute and nothing happend on the screen itself. After releasing the blinking stopped but the screen remained on it's state...

Enion said:
Hi, thanks for your advice. The problem is that, after recharging the phone again and trying several times, I just can't get into bootloader. When I hold the power button and vol. down the home and "arrow" touch-buttons at the bottom of the phone just start blinking. As long as I hold these two buttons the blinking doesn't stop, I did hold them for a full minute and nothing happend on the screen itself. After releasing the blinking stopped but the screen remained on it's state...
Click to expand...
Click to collapse
Blinking is good, just hold POWER + VOLDOWN with the phone sensors under a bright light (not kidding!!), it should reboot after 30sec to 2 minute. If it doesn't reboot, let go and try again; the bright light is important!!
Once it reboots, keep holding VOLDOWN so it reboots to bootloader.

Thank you guys, I tried it and it strangely worked (literally 2minutes with a light on it). I'm in the bootloader now and will try to
flash TWRP, put your RUU zip on your phone storage, and then flash it.
Click to expand...
Click to collapse
as kibmikey1 wrote. I hope I'll find the right files and manuals this time. Will report back

Enion said:
Thank you guys, I tried it and it strangely worked (literally 2minutes with a light on it). I'm in the bootloader now and will try to as kibmikey1 wrote. I hope I'll find the right files and manuals this time. Will report back
Click to expand...
Click to collapse
You can't flash a RUU zip through recovery.
Most important question: What's your final goal?? Where do you want to get with your phone??
also post a "fastboot getvar all" (remove IMEI and s/n), and date of bootloader.
PS: hit the thanks button if we helped

nkk71 said:
You can't flash a RUU zip through recovery.
Most important question: What's your final goal?? Where do you want to get with your phone??
also post a "fastboot getvar all" (remove IMEI and s/n), and date of bootloader.
PS: hit the thanks button if we helped
Click to expand...
Click to collapse
Didn't know about the thank you, my bad there.
My final goal is to have an up-to-date phone. I couldn't update my phone while it was rooted and therefore tried to unroot it and ran into all these complications.
I tried the command you wrote and the result was:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.161.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP110
(bootloader) battery-status: good
(bootloader) battery-voltage: 4218mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.062s
thanks!

Enion said:
Didn't know about the thank you, my bad there.
My final goal is to have an up-to-date phone. I couldn't update my phone while it was rooted and therefore tried to unroot it and ran into all these complications.
I tried the command you wrote and the result was:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.161.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH35xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP110
(bootloader) battery-status: good
(bootloader) battery-voltage: 4218mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.062s
thanks!
Click to expand...
Click to collapse
hey mate, edit your post and remove IMEI and s/n we don't need to see those.
can you confirm your hboot is dated before June 2013. I'll post your options after that

Hi, thanks for noticing, I removed it, please dit your post aswell
If you're talking about the date at the top of the bootloader, it says May 3

Enion said:
Hi, thanks for noticing, I removed it, please dit your post aswell
Click to expand...
Click to collapse
I already did when quoting you, changed them all to XXXXXXXXXXX, or is it showing up on your computer?
Enion said:
If you're talking about the date at the top of the bootloader, it says May 3
Click to expand...
Click to collapse
gimme a few minutes while I write down all the options
BTW: Easy on the thanks button, you only have 8 per day

nkk71 said:
I already did when quoting you, changed them all to XXXXXXXXXXX, or is it showing up on your computer?
gimme a few minutes while I write down all the options
BTW: Easy on the thanks button, you only have 8 per day
Click to expand...
Click to collapse
My bad again, it doesn't show up. I need to learn to read the forum rules first before posting stuff I guess.

Enion said:
My bad again, it doesn't show up. I need to learn to read the forum rules first before posting stuff I guess.
Click to expand...
Click to collapse
Code:
(bootloader) version-bootloader: 1.44.0000 (May 3)
(bootloader) version-main: 1.29.161.16
OK, so you have two primary choices:
A) Stay S-On
B) Get S-Off: with the above hboot and firmware, you can easily get s-off using revone
Now, with an unlocked bootloader but S-ON, you can
---- flash custom or stock ROM
---- flash different radios (ie baseband)
---- flash custom kernel
---- flash custom recovery
you cannot:
---- you cannot flash unsigned firmware
---- you cannot downgrade (firmware and hboot)
---- you cannot remove TAMPERED
---- you cannot LOCKED your phone, at best it will say RELOCKED
---- you cannot run a downgrade RUU
With S-Off, you can do ALL of these and more, e.g. you can reset your phone to 100% out-of-the box, and you can even change your phone from a Vodafone phone to ANY other variant (eg unbranded European, US Developer, 100% Google Play Edition, etc.)
I'm in no way encouraging you to go S-Off, unless YOU are comfortable with the thought and procedure.
If you're looking at always having the latest releases, then I personally would stick with custom ROMs, these get updated way quicker (even if sometimes based on a leak), than carrier dependent OTAs.
Should you stay S-On, the only way to upgrade the firmware, will be using an official Vodafone OTA, in one of two methods:
1- go back to stock rom & stock recovery, download and install, and then reinstall custom ROM
2- get your hands on the OTA file (either by downloading it yourself, or if you find it on the net), then extract "firmware.zip" and flash it in fasboot RUU mode (this will work cause the OTA contains a signed firmware specifically for your phone)
[and you cannot downgrade if for some reason you would want to]
On the other hand, if you are S-Off, you can use an unsigned firmware package found in various threads.
Ok, that's enough for now, even my head is spinning LOL.
Let me know what you think, and if you need more explanations. Then rethink your ultimate goal, and we can proceed from there.
(Now all this writing deserves a thanks )

nkk71 said:
Code:
(bootloader) version-bootloader: 1.44.0000 (May 3)
(bootloader) version-main: 1.29.161.16
OK, so you have two primary choices:
A) Stay S-On
B) Get S-Off: with the above hboot and firmware, you can easily get s-off using revone
Now, with an unlocked bootloader but S-ON, you can
---- flash custom or stock ROM
---- flash different radios (ie baseband)
---- flash custom kernel
---- flash custom recovery
you cannot:
---- you cannot flash unsigned firmware
---- you cannot downgrade (firmware and hboot)
---- you cannot remove TAMPERED
---- you cannot LOCKED your phone, at best it will say RELOCKED
---- you cannot run a downgrade RUU
With S-Off, you can do ALL of these and more, e.g. you can reset your phone to 100% out-of-the box, and you can even change your phone from a Vodafone phone to ANY other variant (eg unbranded European, US Developer, 100% Google Play Edition, etc.)
I'm in no way encouraging you to go S-Off, unless YOU are comfortable with the thought and procedure.
If you're looking at always having the latest releases, then I personally would stick with custom ROMs, these get updated way quicker (even if sometimes based on a leak), than carrier dependent OTAs.
Should you stay S-On, the only way to upgrade the firmware, will be using an official Vodafone OTA, in one of two methods:
1- go back to stock rom & stock recovery, download and install, and then reinstall custom ROM
2- get your hands on the OTA file (either by downloading it yourself, or if you find it on the net), then extract "firmware.zip" and flash it in fasboot RUU mode (this will work cause the OTA contains a signed firmware specifically for your phone)
[and you cannot downgrade if for some reason you would want to]
On the other hand, if you are S-Off, you can use an unsigned firmware package found in various threads.
Ok, that's enough for now, even my head is spinning LOL.
Let me know what you think, and if you need more explanations. Then rethink your ultimate goal, and we can proceed from there.
(Now all this writing deserves a thanks )
Click to expand...
Click to collapse
Thanks for the help. I will try to get S-Off then. I hope I can do it this time though. I'll report when I get it Off or need help again. Looking forward

Enion said:
Thanks for the help. I will try to get S-Off then. I hope I can do it this time though. I'll report when I get it Off or need help again. Looking forward
Click to expand...
Click to collapse
No problem mate, remember for revone to work your firmware is good ((bootloader) version-main: 1.29.161.16), but you will need a ROM based on 4.1.2 preferably (I have one - which worked for me and two others) in case you can't find one.
Also read here: http://forum.xda-developers.com/showthread.php?t=2431515
here: http://forum.xda-developers.com/showthread.php?t=2365506
and of course: http://forum.xda-developers.com/showthread.php?t=2314582
Let me know if you need any more help.
Once you are S-Off, you can easily upgrade/downgrade firmware in @vomer's guide (same as before, but down in the firmware section): http://forum.xda-developers.com/showthread.php?t=2365506

Enion said:
Thanks for the help. I will try to get S-Off then. I hope I can do it this time though. I'll report when I get it Off or need help again. Looking forward
Click to expand...
Click to collapse
Hey @Enion, you all good now?

nkk71 said:
Hey @Enion, you all good now?
Click to expand...
Click to collapse
Hi, sry for the late reply, didn't have much time today. I flashed the rom (4.2.1) that nkk71 gave me in a PM and the phone is working just fine now. I decided to just stay in this state for the moment and think about getting S-Off later. I want to thank everyone involved in this thread and especially nkk71, really quick & reliable message board.
//Enion

Enion said:
Hi, sry for the late reply, didn't have much time today. I flashed the rom (4.2.1) that nkk71 gave me in a PM and the phone is working just fine now. I decided to just stay in this state for the moment and think about getting S-Off later. I want to thank everyone involved in this thread and especially nkk71, really quick & reliable message board.
//Enion
Click to expand...
Click to collapse
I know what you mean, just got back from work myself, and didnt have a minute to scratch my head all day :silly:
Just for your info, it took me less than ten minutes to get S-Off using my setup (that ROM and firmware 1.28.61.7), worked like a charm from the first time.
Anyway, until you decide to do it, could you edit the main thread title to include something like [ON HOLD], I usually prefer [SOLVED], but [ON HOLD] should do for now, until you revive your thread

nkk71 said:
I know what you mean, just got back from work myself, and didnt have a minute to scratch my head all day :silly:
Just for your info, it took me less than ten minutes to get S-Off using my setup (that ROM and firmware 1.28.61.7), worked like a charm from the first time.
Anyway, until you decide to do it, could you edit the main thread title to include something like [ON HOLD], I usually prefer [SOLVED], but [ON HOLD] should do for now, until you revive your thread
Click to expand...
Click to collapse
I tried to set in "on hold" but I think I'm missing some rights in this forum, it just doesn't work. I tried http://forum.xda-developers.com/showthread.php?p=27117213 this method aswell.

Enion said:
I tried to set in "on hold" but I think I'm missing some rights in this forum, it just doesn't work. I tried http://forum.xda-developers.com/showthread.php?p=27117213 this method aswell.
Click to expand...
Click to collapse
didnt read the the link you sent, usually you just go to the first post, click EDIT then at the bottom of the edit window, click GO ADVANCED and it would show the main thread title.
anyway don't worry about, most people (unfortunately) never bother to [CLOSE] [SOLVED] etc. no wonder the forum is hard to navigate through
take care
---------- Post added at 07:29 PM ---------- Previous post was at 07:24 PM ----------
nkk71 said:
didnt read the the link you sent, usually you just go to the first post, click EDIT then at the bottom of the edit window, click GO ADVANCED and it would show the main thread title.
anyway don't worry about, most people (unfortunately) never bother to [CLOSE] [SOLVED] etc. no wonder the forum is hard to navigate through
take care
Click to expand...
Click to collapse
Thank you sir!

i need help i think my device is bricked

okk so i was trying to flash a rom for the first time and i really went at it the wrong way. i didin't backup my original RUU and now my device is stuck on the bootloader screen and i really have no idea what to do. i just want to get an OS running on my phone right now cause im freaking out. my company carrier is rogers and this is what my phone is showing right now:
***tampered***
***relocked***
m7_ul pvt ship s-on rh
hboot-1,55,0000
radio-4a.20.3263.16
opendsp -v32,120.274.0909
os-
emmc-boot 2048mb
i try looking for another ruu to flash in my phone but i cant seem to find one that works with my phone..even when i try using the flashboot getvar command to check for the version this is all i got.. : C:\Users\david\Desktop\sdk-tools>fastboot getvar version-main
version-main:
finished. total time: 0.001s
any help at this point would be greatly appreciated i need to get my phone up working so i can receive my calls
i have managed to bring back recovery mode by re-unlocking it via htcdev..now when the phone boots it goes to the google logo and then the language selecting screen then restarts after 10 secs everytime

Instead of the fastboot command you typed, write:
Code:
fastboot getvar all
Then look for "CID". Search for a RUU for that CID. If you can't find one, we'll discuss other solutions.

fenstre said:
Instead of the fastboot command you typed, write:
Code:
fastboot getvar all
Then look for "CID". Search for a RUU for that CID. If you can't find one, we'll discuss other solutions.
Click to expand...
Click to collapse
this is what i got from the fastboot getvar all command :
C:\Users\david\Desktop\sdk-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA346W904162
(bootloader) imei: 354439050131335
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4290mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-fe1214a4f2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.053s
cidnum says ROGER001? im i don't think ive seen cid what that number around
edit: could it be possible that this is what i need ? "M7 CWM Nandroid Backup / CID ROGER001 / 1.29.631.17"
since i did not make a backup is there a chance i can restore this ? ive tried the method that suggest sideloading but it didn't work or maybe i didin't do it right but it didn't wanna recognize my phone when i tried the command'
edit 2: also, im using twrp instead of cwm if that information can help in any way.

If you can let us know which rom you attempted to install and what you managed to do. Did you install custom recovery etc.

gffmac said:
If you can let us know which rom you attempted to install and what you managed to do. Did you install custom recovery etc.
Click to expand...
Click to collapse
well all i was trying to do was install the goole play edition rom (bigxie_m7_GPe_KRT16S_odexed-signed.zip) but after the installation it kept restarting after the language selection screen. i used twrp to flash the rom. right now all im able to do is cycle through the booloader, the recovery screen and to the language selection screen

Unless you have another rom (4.3 rom) copied onto the storage on your phone you will probably have to flash stock recovery and recover by installing a stock RUU for your carrier/CID version.
---------- Post added at 11:59 AM ---------- Previous post was at 11:54 AM ----------
Out of curiosity try going into twrp and doing a factory reset (wipe) and reboot see if you have the same issue.

is there such thing as a stuck RUU for rogers in canada? ive been looking on the internet but i can't seem to find anything that could works for my phone. maybe you could point me in a direction so i could look ?

deerome said:
is there such thing as a stuck RUU for rogers in canada? ive been looking on the internet but i can't seem to find anything that could works for my phone. maybe you could point me in a direction so i could look ?
Click to expand...
Click to collapse
Cant see any for rogers
Just found this http://htconeroot.com/htc-one-tutorials/how-to-copy-files-to-htc-one-using-twrp-mount-and-adb/ if you can copy a rom to the phone it will probably work.
A nandroid backup for rogers is here http://forum.xda-developers.com/showthread.php?t=2207874 or you could flash a pre 4.4 rom. CWM needed to recover a CWM backup and backup would need to be in right directory.
You would need to unlock bootloader to do these things.
If I was you I would download a custom rom like Android Revolution HD 40.3 copy over via above process, do a wipe and install, without s-off you probably have to flash kernel via fastboot.

gffmac said:
Cant see any for rogers
Just found this http://htconeroot.com/htc-one-tutorials/how-to-copy-files-to-htc-one-using-twrp-mount-and-adb/ if you can copy a rom to the phone it will probably work.
A nandroid backup for rogers is here http://forum.xda-developers.com/showthread.php?t=2207874 or you could flash a pre 4.4 rom. CWM needed to recover a CWM backup and backup would need to be in right directory.
You would need to unlock bootloader to do these things.
If I was you I would download a custom rom like Android Revolution HD 40.3 copy over via above process, do a wipe and install, without s-off you probably have to flash kernel via fastboot.
Click to expand...
Click to collapse
thanks for your answers
i definitly am gonna try installing the android revolution hd rom to see if i can at least get an OS running on my phone. what command do i have to use to flash the kernel ?
also, i have tried sideloading/pushing the nandroid backup before but that didint seem to work, not sure if i did something wrong.

deerome said:
thanks for your answers
i definitly am gonna try installing the android revolution hd rom to see if i can at least get an OS running on my phone. what command do i have to use to flash the kernel ?
also, i have tried sideloading/pushing the nandroid backup before but that didint seem to work, not sure if i did something wrong.
Click to expand...
Click to collapse
To flash a kernel via fastboot 'fastboot flash boot boot.img'. Make sure the boot.img (if thats what its called) is in the same folder as fastboot. The corresponding kernel(boot.img) is inside the zip file of most roms.

gffmac said:
To flash a kernel via fastboot 'fastboot flash boot boot.img'. Make sure the boot.img (if thats what its called) is in the same folder as fastboot. The corresponding kernel(boot.img) is inside the zip file of most roms.
Click to expand...
Click to collapse
thanks to your help i was able to install an earlier version of android hd so after many hours of headache i somehow managed to install the android hd rom by sideloading it with cwm. what a pain in the arse -_-. nonetheless that was a great help, what should i do now so something like this don't happen again? i wanted to have the google edtion on my htc but i think im gonna wait until im better at this thing.
anyways thanks again man i really appreciate you have no idea how frustrated i was lol :good:

deerome said:
thanks to your help i was able to install an earlier version of android hd so after many hours of headache i somehow managed to install the android hd rom by sideloading it with cwm. what a pain in the arse -_-. nonetheless that was a great help, what should i do now so something like this don't happen again? i wanted to have the google edtion on my htc but i think im gonna wait until Im better at this thing.
Anyways thanks again man i really appreciate you have no idea how frustrated i was lol :good:
Click to expand...
Click to collapse
No probs glad you got it working again.
If you really want to try a Google Edition rom you would need to s-off your phone which is trickier than what you have done so far so may want to read up some more.

I had the exact same problem while i was flashing a GEdition ROM. The problem here is that my volume Keys dont work and i cant manage to enter recovery/bootloader over ADB. Tried all usb cords and porta. Still giving me Device not found. Any tricky way to access bootloader or recovery?
I've already sent it to warranty but without the original software.... Blablabla they told me that it would only work
with a board replacement... 180€
Any help?
Sent from my Desire HD using Tapatalk

deerxmoose said:
I had the exact same problem while i was flashing a GEdition ROM. The problem here is that my volume Keys dont work and i cant manage to enter recovery/bootloader over ADB. Tried all usb cords and porta. Still giving me Device not found. Any tricky way to access bootloader or recovery?
I've already sent it to warranty but without the original software.... Blablabla they told me that it would only work
with a board replacement... 180€
Any help?
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
You can get to bootloader and recovery via adb commands but thats from a running rom I presume http://forum.xda-developers.com/showthread.php?t=1853159
How come your volume keys dont work, did it come that way? I presume you have tried holding power and volume down for a prolonged length of time??

gffmac said:
You can get to bootloader and recovery via adb commands but thats from a running rom I presume http://forum.xda-developers.com/showthread.php?t=1853159
How come your volume keys dont work, did it come that way? I presume you have tried holding power and volume down for a prolonged length of time??
Click to expand...
Click to collapse
For no reason they stop working. And i think its a hardware malfunction. Besides that, i cant manage to enter bootloader or recovery to instala other ROM.
I guess with Samsung Phones there is a doubletap on the screen to enter bootloader.
Im really stressing here.
Sent from my Desire HD using Tapatalk

deerxmoose said:
For no reason they stop working. And i think its a hardware malfunction. Besides that, i cant manage to enter bootloader or recovery to instala other ROM.
I guess with Samsung Phones there is a doubletap on the screen to enter bootloader.
Im really stressing here.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
I would contemplate opening the phone up to check the behind the volume buttons but that is very risky.

gffmac said:
I would contemplate opening the phone up to check the behind the volume buttons but that is very risky.
Click to expand...
Click to collapse
Before trying that ill prefer to try Any other solutions. Anyone?
Sent from my Desire HD using Tapatalk

There is no bootloader in Samsung phones, and no doubletap. You need to hit the buttons as well. If you are able to boot into the phone and adb devices shows the device, you can do
adb reboot-bootloader or adb reboot recovery

SaHiLzZ said:
There is no bootloader in Samsung phones, and no doubletap. You need to hit the buttons as well. If you are able to boot into the phone and adb devices shows the device, you can do
adb reboot-bootloader or adb reboot recovery
Click to expand...
Click to collapse
Tried that over and over and it keeps saying device not found.
Sent from my Desire HD using Tapatalk

Then you should fix your computer/adb issues.

[Q] HTC One Bootlooping after Google Edition ARHD 6.0 installation

At this time I am pretty much hopeless... Seriously, nothing works, but if a miracle happens and I get my HTC One back to life it will be thanks to you guys.
So... This is my story:
Today I was using my HTC One M7_UL like any other day, I had Android OneDroid BETA 15 (a CyanogenMod with a few tweaks) installed and I got bored of it, so I decided to flash a Google Edition ROM. Came to the forum and looked for the thread with most replies on "Custom Android HTC One ROMs" and found the winner of the Google Edition ones, the ARHD 6.0 Google Edition. Fine, I thought, let's flash this [email protected]%#. So I started by downloading the latest version (roughly 550 MB) and connecting my HTC One to my Windows 8.1 Pro computer. The HTC drivers don't work with my 8.1 Pro Windows but since I only needed it to send the .zip file to my Internal Storage I gave it a shot. Copied everything, disconnected and proceeded to my recovery (TWRP) where I Wiped it up and flashed ARHD 6.0 GE. After installing, still on the recovery, restored the phone to factory presets and rebooted it. A Google logo appeared and some Nexus-like balls started to spin, some weird sh%t. Until there, everything absolutely fine, but it stood there with the balls spinning for 3~4 minutes and I thought it was normal because it was the first boot after flashing the new ROM. Got to Language Settings on the Android Welcome screen but then it quickly turned black and reeboted. HTC Logo appeared for roughly 1 second and it got black and rebooted again, this time starting back up but when I got to the Language setup it would do the same thing, over and over again.
So I started looking into it and didn't find many answers, then I decided to try and flash another Google Edition ROM, SkyDragon, but as I am a COMPLETE NOOB in this rooting and wobbly wobbly thingies I had no idea how I would get the .zip file to the Internal Storage, since the HTC One HAS NO SD CARD!!! I researched a bit and found sth called ADB Sideloading, which I am certain you know what it is, but the thing is, since my computer doesn't quite work with HTC Drivers I had to use my sister's PC, with Windows 7 and HTC One All-in-One kit. I could access my bootloader and recovery despite of the bootloop, which I think is a good thing, so I put it to fastboot mode, connected the cable to her computer and on the phone it changed from "fastboot" in red to "fastboot usb" in red also, so I thought, oh ok, it will work now. But when I tried ADB commands or tried any of the commands on the All-in-One thing it would just say "NO DEVICES FOUND" or something among those lines.
Anyway, if someone got this far I already thank you for trying to help but I am pretty certain I got a bricked device. I don't even now what to do, should I try to ADB Sideload this other ROM or should I try a Sense ROM, cuz I read somewhere that Google Edition ROMs only work when migrating from Sense ROMs, and if I am supposed to flash a Sense ROM how would I do so? Please try to be as simple as possible, I don't know much and I am pretty noob, anyways, thank you so much, and I hope you can help me!
(Also, before this bootloop it was S-OFF and now it shows as S-ON)
Waiting for a response,
John B.

You need TWRP 2.6.33 or newer.
You need to be S-Off.
You need to have wiped cache and dalvik and probably a full format (except sdcard) wouldn't go amiss before installing. It sounds to me like it wasn't wiped properly.
The device doesn't S-On on its own, you probably did it with the toolkit or something.
ADB doesn't work in fastboot mode, fastboot mode is for fastboot command, such as flashing recovery.
Are you still unlocked?
Give us the output of
fastboot getvar all
Without IMEI and Serial Number.

BenPope said:
You need TWRP 2.6.33 or newer.
You need to be S-Off.
You need to have wiped cache and dalvik and probably a full format (except sdcard) wouldn't go amiss before installing. It sounds to me like it wasn't wiped properly.
The device doesn't S-On on its own, you probably did it with the toolkit or something.
ADB doesn't work in fastboot mode, fastboot mode is for fastboot command, such as flashing recovery.
Are you still unlocked?
Give us the output of
fastboot getvar all
Without IMEI and Serial Number.
Click to expand...
Click to collapse
Yeah I am unlocked and untempered.
Here is my fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4309mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.077s
And I am ABSOLUTELY SURE that before all of this it was S-OFF, ABSOLUTELY!

BenPope said:
You need TWRP 2.6.33 or newer.
You need to be S-Off.
You need to have wiped cache and dalvik and probably a full format (except sdcard) wouldn't go amiss before installing. It sounds to me like it wasn't wiped properly.
The device doesn't S-On on its own, you probably did it with the toolkit or something.
ADB doesn't work in fastboot mode, fastboot mode is for fastboot command, such as flashing recovery.
Are you still unlocked?
Give us the output of
fastboot getvar all
Without IMEI and Serial Number.
Click to expand...
Click to collapse
Also my TWRP is 2.6.3.3 so I should be good about that right?

Jvov said:
Also my TWRP is 2.6.3.3 so I should be good about that right?
Click to expand...
Click to collapse
Yes, but as far as I know, you need to be S-Off for GPE KitKat ROMs.
Do you really have no version-main?
If your hboot is 1.44 and dated prior to June, you should be able to use revone to S-Off, but you'll need a booting ROM of Android 4.2.2.

BenPope said:
Yes, but as far as I know, you need to be S-Off for GPE KitKat ROMs.
Do you really have no version-main?
If your hboot is 1.44 and dated prior to June, you should be able to use revone to S-Off, but you'll need a booting ROM of Android 4.2.2.
Click to expand...
Click to collapse
Can you explain exactly how can I do that?

Just flash back to another ROM for the moment that has root then use rumrunner to get S-OFF then flash ARHD GPE again. You'll be fine then.
Sent from my One using XDA Premium 4 mobile app

Also don't do a reset after flashing the rom. It will boot loop every time.
Bat cave One

zelendel said:
Also don't do a reset after flashing the rom. It will boot loop every time.
Bat cave One
Click to expand...
Click to collapse
Solved, thanks to all!

Phone is soft bricked, attempts to fix haven't work

Yesterday, I attempted to install a new rom. I had been using CM11 nightlies up till this point, and after being annoyed about certain aspects of my phone not working. I wanted to try something new.
I found ViperOne, and went to install it, thinking that it'll be the standard, run-of-the-mill install with no problems to be had. After getting through the install procedure and attempting to reboot to system, my phone dropped me back off at the bootloader. Thinking that I had forgotten to wipe something, I went into the recovery, wiped data, dalvik cache, and the cache, and attempted the install again. Once again, my phone dropped me off at the bootloader.
I thought, maybe I had a bad download. Re-downloaded the rom, same result. "Oh, I'll just try something else then". I found a Google Play Edition rom for my device, and decided to try that. It got stuck in a bootloop. After some googling, I attempted wiping the data/cache/dalvik cache again hoping it would help. Nope, still stuck in bootloop.
At this point (and after having running into a very similiar situation before) I decided to go for broke. I did a full wipe of the phone, and sideloaded CM10.1.3 (only stable CM rom for this device afaik). As it was installing, I noticed an error. "Unable to mount /data". I've had this problem before, and the way I fixed it last time was to install and run a stock rom. At this point in time, I was also getting frustrated and decided to put the stock rom back on my phone so it would at least be functional.
I found a stock rom and installed it just fine. The phone didn't even get stuck in a bootloop either. However, once the phone had finally booted up, I found that the touchscreen was unresponsive. I remember having this issue the last time I tried to use a stock rom. After a little bit of research, I had found that the problem stems from installing the wrong version of the rom. It was suggested on one of the websites to put "fastboot getvar version-main" into adb to find out what version I needed. It returns "version-main: ".
It was at this point that I remembered that I had made a backup of my phone before I attempted rooting. After some searching around, I managed to find it. That being said, I have no idea what to do with it. The folder where I made the backup contains a handful of .win files and some md5 checksums.
Since then I have been attempting seemingly random RUU versions in hopes of stumbling across the right one. It's been 5 hours, and I haven't had any success.
I would greatly appreciate any and all help that can be provided. If you guys need additional information (I'm not sure what I should include), let me know. I know some of the more basic ADB commands and their functions, so bear with me if I ask some questions about how to do certain things.

Boot into bootloader/fastbootusb and type the below command and post the readout here.
fastboot getvar all

BD619 said:
Boot into bootloader/fastbootusb and type the below command and post the readout here.
fastboot getvar all
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4323mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-005bf6a40e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

You can try one of the RUU's found here or follow the guide
Sidenote: don't use the 4.06.651.4 RUU unless you flash the 4.06.651.4 s-on firmware first.
BTW I removed
serialno:
imei:
meid:

BD619 said:
You can try one of the RUU's found here or follow the guide
Sidenote: don't use the 4.06.651.4 RUU unless you flash the 4.06.651.4 s-on firmware first.
Click to expand...
Click to collapse
I've tried several different RUU's, including the one's I could find here, and none of them have worked. Not sure if it really matters, but I attempted the 4.06.651.4 RUU earlier, but it failed.
BD619 said:
BTW I removed
serialno:
imei:
meid:
Click to expand...
Click to collapse
Why shouldn't those be shared? Are they considered sensitive information?

Ooops for got the link
http://forum.xda-developers.com/showthread.php?t=2503646
Yes they could be considered sensitive.

BD619 said:
Yes they could be considered sensitive.
Click to expand...
Click to collapse
I have no idea what those numbers represent. Why are important?

crazy-asian said:
I have no idea what those numbers represent. Why are important?
Click to expand...
Click to collapse
I have always been told not to include those...could be a way for someone to hack your device but that's just my guess.
http://en.wikipedia.org/wiki/Mobile_equipment_identifier

I had this happen to me also. Ends up i had to flash a new firmware on the phone and it booted right up. Also make sure you are using twrp recovery when you flash this rom. I used cwm and think that is where all my problems started. Hope ya get it worked out and may not be your problem but is exactly what happened to me and have i fixed it.

BD619 said:
http://forum.xda-developers.com/showthread.php?t=2503646
Click to expand...
Click to collapse
I had tried all but one of those in that list. That one that I hadn't used yet appears to be working. Thank you so much for the help.

Oh god, now I'm back on the stock rom... Any recommendations for a good rom? I enjoy the stock look and feel of android, but running the CM nightlies has been giving me a headache.

crazy-asian said:
Oh god, now I'm back on the stock rom... Any recommendations for a good rom? I enjoy the stock look and feel of android, but running the CM nightlies has been giving me a headache.
Click to expand...
Click to collapse
I'm running BadSeed Sixth Sense
But it's all personal preference everyone will have a different opinion.

Fastboot, on the phone side, isn't connecting to my computer.

crazy-asian said:
Fastboot, on the phone side, isn't connecting to my computer.
Click to expand...
Click to collapse
Are you in bootloader?

BD619 said:
Are you in bootloader?
Click to expand...
Click to collapse
Yes, and it is in fastboot mode.

crazy-asian said:
Yes, and it is in fastboot mode.
Click to expand...
Click to collapse
When you type fastoot devices you don't get a response?

BD619 said:
When you type fastoot devices you don't get a response?
Click to expand...
Click to collapse
correct

crazy-asian said:
correct
Click to expand...
Click to collapse
Ok go back to my guide and you can get the proper drivers and instructions to get them installed correctly

BD619 said:
Ok go back to my guide and you can get the proper drivers and instructions to get them installed correctly
Click to expand...
Click to collapse
Didn't solve the problem, phone still isn't in "fastboot USB"

crazy-asian said:
Didn't solve the problem
Click to expand...
Click to collapse
Try a different port(usb2 are best)
Try a different cable
Different PC
If you have android sdk setup try updating it.

Htc One stuck on Logo, need 1.29.666.17 RUU to flash or another solution

EDIT: This is the Htc One (M7) btw. Guess it was obvious because of the version it came with out of the box, but just to clear any confusion.
EDIT 2: Meant to say my Device was S-On* NOT S-Off. Sorry.
So I'm completely new to Android, and yesterday was the day I got my first ever Android device.
It came with Sense 5 and android 4.1.2 out of the box.
After a while of playing around with my new phone I started checking for updates to get it to the latest version. When I first check it showed that a small update was available and I started downloading it. I noticed that when this update was installing it would first go into that screen where it shows that phone with a green arrow and a download bar, and then all of a sudden it would restart and go back to the Htc One Logo. It did this a few times before finally completing the upgrade.
I checked for updates again and this time it showed me Android 4.3 + Sense 5.5. I downloaded and started installing the upgrade. It did the same thing as last time but I decided I'd power off the device (Figured out later this was what caused this whole problem) and power it on again. After I did that it was stuck on the Htc Logo.
I went on the bootloader and tried factory resetting but it just brought me back to the Htc Logo again.
I found a few threads telling me to hook up my device to the computer, load up fastboot and use cmd to clear the cache and it should work. That failed too however.
After talking with a few of my friends who happen to be android experts, they told me that I because I had turned off the device in the middle of the update I had somehow corrupted some system partition thing and I'd need to flash the stock rom on once again.
After almost 24 hours of research, I've gotten to a point where I've almost figured it out but I hit a bump. My device is not rooted and is S-On (Bootloader used to be locked but in the process of fixing it).
According to my friends because my device is S-On I won't be able to flash Custom roms and need a RUU file that is specific to my carrier. I found out that I basically need the RUU file that has the same number as 1.29.666.17
This apparently is almost non-existent on the web. This is the bump I've hit and I have no idea what I can do now.
Any help would be appreciated.
Also note that I am incredibly new to android. Never rooted or anything in my life before. I've had quite the learning curve in the past day though.

Can you post a fastboot getvar all using command prompt and remove your imei and serial no please?
Sent from my HTC One using xda app-developers app

stovie_steve said:
Can you post a fastboot getvar all using command prompt and remove your imei and serial no please?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.666.17
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4319mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.047s

Als26 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.666.17
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4319mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.047s
Click to expand...
Click to collapse
you phone is not s-off
your going to have to unlock the bootloader and flash custom recovery and a rom to attempt to get s-off so you can convert your phone to the international or developer version
instructions on how to convert here >> http://forum.xda-developers.com/showthread.php?t=2356401

clsA said:
you phone is not s-off
your going to have to unlock the bootloader and flash custom recovery and a rom to attempt to get s-off so you can convert your phone to the international or developer version
Click to expand...
Click to collapse
That was my mistake, I did mean to say S-On.
I did try to get the S-Off using an Htc One Toolkit (http://forum.xda-developers.com/showthread.php?t=2364445)
However right after Step 1a (downloading Firewater), I moved to step 1b (rebooting my device) it kept saying "adb reboot
error: device not found"
I googled this and it told I had to enable USB debugging, which I can only do through the settings of the phone apparently. And I can't access it so I'm not sure if I can still S-Off my device.

When you enable USB debugging does a pop up box come up on your phone when connecting to your computer to allow the computer to connect?
Sent from my HTC One using xda app-developers app

stovie_steve said:
When you enable USB debugging does a pop up box come up on your phone when connecting to your computer to allow the computer to connect?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
See that's the thing, I can't enable USB Debugging because my phone is stuck on the bootlogo.
I don't think there's a way for me to enable USB debugging without having access to there phone, or is there?

Als26 said:
See that's the thing, I can't enable USB Debugging because my phone is stuck on the bootlogo.
I don't think there's a way for me to enable USB debugging without having access to there phone, or is there?
Click to expand...
Click to collapse
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7ul
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_31.6.zip
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot

clsA said:
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
Click to expand...
Click to collapse
Alright so did what you said, successfully flashed the new recovery.
Sideloading seems to be giving me some trouble though.
After I "swiped to sideload" I get this
Updating partition details...
E: Unable to mount '/cache'
Full SELinux support is present.
E: Unable to mount '/cache'
E: Unable to mount '/cache'
Starting ADB sideload feature...
Been stuck at that for about 15minutes now.
About 5 minutes in I thought I was maybe supposed to use my pc to sideload, but cmd said "error: device not found".
Thanks again for your help by the way.

Als26 said:
Alright so did what you said, successfully flashed the new recovery.
Sideloading seems to be giving me some trouble though.
After I "swiped to sideload" I get this
Updating partition details...
E: Unable to mount '/cache'
Full SELinux support is present.
E: Unable to mount '/cache'
E: Unable to mount '/cache'
Starting ADB sideload feature...
Been stuck at that for about 15minutes now.
About 5 minutes in I thought I was maybe supposed to use my pc to sideload, but cmd said "error: device not found".
Thanks again for your help by the way.
Click to expand...
Click to collapse
Your going to have to get your drivers fixed on the pc
Try and install these
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe

clsA said:
Your going to have to get your drivers fixed on the pc
Try and install these
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
Click to expand...
Click to collapse
Didn't work. Ran the file, used device manager to manually locate the files in Program Files (x86) and double clicked "HTC". Just keeps saying it couldn't find the driver software for my device.
But if I understand correctly, all I have to do is find a way to update the drivers and I'll be able to sideload the Rom, and hopefully I'll have a working HTC One once again?

Als26 said:
Didn't work. Ran the file, used device manager to manually locate the files in Program Files (x86) and double clicked "HTC". Just keeps saying it couldn't find the driver software for my device.
But if I understand correctly, all I have to do is find a way to update the drivers and I'll be able to sideload the Rom, and hopefully I'll have a working HTC One once again?
Click to expand...
Click to collapse
yes or use a usb otg cable to load a rom to your phone from TWRP

clsA said:
yes or use a usb otg cable to load a rom to your phone from TWRP
Click to expand...
Click to collapse
Gave up trying to install new drivers and instead opted to pay a small fee to get it fixed.
Thanks again for the help, may have worked if I got those drivers installed.

Als26 said:
Gave up trying to install new drivers and instead opted to pay a small fee to get it fixed.
Thanks again for the help, may have worked if I got those drivers installed.
Click to expand...
Click to collapse
ok

clsA said:
ok
Click to expand...
Click to collapse
A few quick questions.
The rom will work even if I'm S-ON right?
Also if I do fix my phone using this method, is there a way for me to return it to the stock rom?

Als26 said:
A few quick questions.
The rom will work even if I'm S-ON right?
Also if I do fix my phone using this method, is there a way for me to return it to the stock rom?
Click to expand...
Click to collapse
Sounds like you haven't read anything about, rooting, S-Off, firmware,hboots,roms, etc..
Suffice to say most people on this forum have more trouble going back to full out of the box stock than anything else.. compared to that, unlocking bootloader, rooting and flashing roms is a doddle(very easy). Suggestion...Read first.
Sent from my HTC One using XDA Premium 4 mobile app

bored_stupid said:
Sounds like you haven't read anything about, rooting, S-Off, firmware,hboots,roms, etc..
Suffice to say most people on this forum have more trouble going back to full out of the box stock than anything else.. compared to that, unlocking bootloader, rooting and flashing roms is a doddle(very easy). Suggestion...Read first.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have not :/
I usually do my research before attempting to do anything to any of my devices, but since I had no intention of rooting/S-ff/Unlocking bootloaders I'm just incredibly clueless. Did some reasearch and it does look like sideloading Roms work on S-On devices. :good:
I have a question for you, or anyone else that knows, but the guy I sent my phone to repair told me the following:
Since I couldn't find the RUU specific to my device, I tried using a Nandroid backup that someone uploaded (This was for Bell Mobile). According to him, he says I must have tried flashing a corrupt rom or something so it's no longer an easy fix. He wants me to pay $130 so he can send it back to some factory to get it fixed. He's telling that this is no longer a soft-brick, but a hard-brick (note that the phone can still access the bootloader, recovery, etc).
I'm pretty sure this guys trying to milk me out of my money, so I told him I'd pick it up tomorrow and get back to him later.
I just want to make sure that what he's saying isn't true though, since I'm not exactly knowledgeable about this and I have a pretty good chance of being wrong.

Als26 said:
I have not :/
I usually do my research before attempting to do anything to any of my devices, but since I had no intention of rooting/S-ff/Unlocking bootloaders I'm just incredibly clueless. Did some reasearch and it does look like sideloading Roms work on S-On devices. :good:
I have a question for you, or anyone else that knows, but the guy I sent my phone to repair told me the following:
Since I couldn't find the RUU specific to my device, I tried using a Nandroid backup that someone uploaded (This was for Bell Mobile). According to him, he says I must have tried flashing a corrupt rom or something so it's no longer an easy fix. He wants me to pay $130 so he can send it back to some factory to get it fixed. He's telling that this is no longer a soft-brick, but a hard-brick (note that the phone can still access the bootloader, recovery, etc).
I'm pretty sure this guys trying to milk me out of my money, so I told him I'd pick it up tomorrow and get back to him later.
I just want to make sure that what he's saying isn't true though, since I'm not exactly knowledgeable about this and I have a pretty good chance of being wrong.
Click to expand...
Click to collapse
Sure sounds like a scam to me, I'm pretty sure we can get your phone working if your willing to read and learn

clsA said:
Sure sounds like a scam to me, I'm pretty sure we can get your phone working if your willing to read and learn
Click to expand...
Click to collapse
Definitely am. Going to pick up the phone tomorrow and try out sideloading through a USB Otg cable. I'll report back with the results. Really hoping this will work.

clsA said:
Sure sounds like a scam to me, I'm pretty sure we can get your phone working if your willing to read and learn
Click to expand...
Click to collapse
Fixed it!
I sideloaded the rom you linked me through a USB Otg Cable. Thanks a lot for your help!
Now I just want to get it back completley to stock.
If I backup my phone through this rom and then go back to stock, I'm assuming my backup file will restore all my contacts/settings/photos etc?