Hey all, sorry if this seems like other questions being posted, but I can not get my phone to work even after attempting the other fixes posted on the forums. I rooted my phone and was running the stock rom that came preloaded with it. I attempted to install CM10 through Rom Manager to no success, so I then tried to manually flash it as well as Gapps. My phone initially got stuck at the CM10 bootloader, but i could still go into CWM Recovery 5.8.3.1. After trying to get the rom to work more, it seems as if all I can access is CWM Recovery and nothing else. My phone wont even boot into the bootloader anymore and all i have access to is CWM Recovery.
I am not the most tech savvy individual when it comes to this since it has been ages since i tinkered with roms, but I would really like to fix this. So heres the facts since my post is so long (sorry!):
-Phone WILL NOT go into bootloader
-Can ONLY ACCESS ClockworkMod Recovery (5.8.3.1)
-SD Card wont mount (I get error "E:Unable to open ums lunfile (No such file or directory)")
I really just want to go back to stock and root again from scratch to reduce any errors like this from occurring in the future and ANY help would be appreciated because I am totally lost and without a phone now. To make things even more difficult, I only have access to a Mac running Lion....although i do have Windows 8 through the use of a bootcamp program, so I CAN run windows programs. Thank you all for any information you may have!
Do you have NANDROID backup,if yes do NANDROID restore and see what happens
Sent from my HTC One S using xda app-developers app
luxandroid said:
Do you have NANDROID backup,if yes do NANDROID restore and see what happens
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
I do NOT have a nandroid backup. I dont even have access to my SD Card since my phone wont recognize it. I dont know where to even start in terms of fixing this. Any additional information anyone needs who thinks they can help me can be provided.
Porgress (Sort of)
I can now access my bootloader if this helps with anyone answering my issue! As I said before, any additional information from me about my phone that can help can and will be provided...just ask if you think you may be able to help!
fragkiller1 said:
I can now access my bootloader if this helps with anyone answering my issue! As I said before, any additional information from me about my phone that can help can and will be provided...just ask if you think you may be able to help!
Click to expand...
Click to collapse
Well since you in bootloader flash TWRP and then boot.img and then reflash the rom just to make sure.
Progress!
Darknites said:
Well since you in bootloader flash TWRP and then boot.img and then reflash the rom just to make sure.
Click to expand...
Click to collapse
Here is the inexperienced flasher in me asking this: How would I go about doing that? Is there a simplified way you could explain this to me, or even a guide? Thanks so much for the reply!
fragkiller1 said:
Here is the inexperienced flasher in me asking this: How would I go about doing that? Is there a simplified way you could explain this to me, or even a guide? Thanks so much for the reply!
Click to expand...
Click to collapse
Sorry. Best would be the All-In-One Toolkit, TWRP is a recovery to replace CWM because its that what's messing you up and also TWRP is better. Toolkit will also flash the boot.img too.
Darknites said:
Sorry. Best would be the All-In-One Toolkit, TWRP is a recovery to replace CWM because its that what's messing you up and also TWRP is better. Toolkit will also flash the boot.img too.
Click to expand...
Click to collapse
Okay, will do! Also, where would I find the Boot.img?
And on a side note; my phone says S-ON...I thought when rooted it was supposed to be S-OFF. Could that be causing problems as well?
fragkiller1 said:
Okay, will do! Also, where would I find the Boot.img?
And on a side note; my phone says S-ON...I thought when rooted it was supposed to be S-OFF. Could that be causing problems as well?
Click to expand...
Click to collapse
Boot.img is in the rom zip. S-On is not the reason its CWM thats messing you up with getting into the bootloader but also not flashing boot.img is not helping too.
Darknites said:
Boot.img is in the rom zip. S-On is not the reason its CWM thats messing you up with getting into the bootloader but also not flashing boot.img is not helping too.
Click to expand...
Click to collapse
The toolkit isnt working for me. Im not sure why... It seems like ill never get this phone up and running again
fragkiller1 said:
The toolkit isnt working for me. Im not sure why... It seems like ill never get this phone up and running again
Click to expand...
Click to collapse
Does the bootloader say fastboot usb?
Darknites said:
Does the bootloader say fastboot usb?
Click to expand...
Click to collapse
Yes it says fastboot USB, but i can not access it on my computer. Also, every time I try to run the toolkit you mentioned earlier... it says something along the line on "command not recognized" in CMD Prompt.
fragkiller1 said:
Yes it says fastboot USB, but i can not access it on my computer. Also, every time I try to run the toolkit you mentioned earlier... it says something along the line on "command not recognized" in CMD Prompt.
Click to expand...
Click to collapse
Hmm not sure have you tried redownloading it or reinstalling the HTC drivers and if that dont work best ask in the toolkit thread.
Darknites said:
Hmm not sure have you tried redownloading it or reinstalling the HTC drivers and if that dont work best ask in the toolkit thread.
Click to expand...
Click to collapse
That was the problem. the toolkit now works (in terms of doing what its supposed to do), but I can no longer access fastboot....just my recovery. any advice on how to get fix this?
fragkiller1 said:
That was the problem. the toolkit now works (in terms of doing what its supposed to do), but I can no longer access fastboot....just my recovery. any advice on how to get fix this?
Click to expand...
Click to collapse
I see that you got the toolkit and bootloader working but did you end up using the RUU?
Success!
Darknites said:
I see that you got the toolkit and bootloader working but did you end up using the RUU?
Click to expand...
Click to collapse
Yes, i ran the RUU and my phone reverted to its stock factory state, no problems at all! Im going to unlock the bootloader again as well as root and install CM10. Thank you for all your help!
fragkiller1 said:
Yes, i ran the RUU and my phone reverted to its stock factory state, no problems at all! Im going to unlock the bootloader again as well as root and install CM10. Thank you for all your help!
Click to expand...
Click to collapse
Np but this time use TWRP as your recovery and once you up and running with CM10 you can use Flash Image GUI to flash the boot.img if you ever update the rom.
Related
Apologies in advance if this is the wrong forum.
Today I successfully perm rooted my Doubleshot...
Then I tried to flash CM9 Alpha 5 using CW recovery.. downloaded the .zip...
Flashed it.. hit reboot... and it wont get past the mytouch splash screen.
I've tried flashing other roms, and other alphas.. but they all don't reboot into the rom.
I can still boot into recovery and get into ClockWork..
Any ideas on what I can flash or do to at least get any rom running on here... I'm not even picky at this point... I just wanted something like CM7 or some AOSP.
Thanks in advance.
sinistersai4d4d said:
Apologies in advance if this is the wrong forum.
Today I successfully perm rooted my Doubleshot...
Then I tried to flash CM9 Alpha 5 using CW recovery.. downloaded the .zip...
Flashed it.. hit reboot... and it wont get past the mytouch splash screen.
I've tried flashing other roms, and other alphas.. but they all don't reboot into the rom.
I can still boot into recovery and get into ClockWork..
Any ideas on what I can flash or do to at least get any rom running on here... I'm not even picky at this point... I just wanted something like CM7 or some AOSP.
Thanks in advance.
Click to expand...
Click to collapse
when you say perm root you mean s-off right?
im assuming he's s on....remember to take the boot.img out of the cm9 zip and flash it using fastboot. You can find out more info on how to do it here. Also apology accepted (this should be in general)
Over 500 posts and people still don't know what threads to post questions in...
Thread reported
Yes, perm root using the root tool. I believe that's S-off... but I'm not certain.
sinistersai4d4d said:
Yes, perm root using the root tool. I believe that's S-off... but I'm not certain.
Click to expand...
Click to collapse
its not s-off, go here to get s-off
http://forum.xda-developers.com/showthread.php?t=1576672
my HTC MyTouch 4G Slide using Tapatalk 2
gtmaster303 said:
Over 500 posts and people still don't know what threads to post questions in...
Thread reported
Click to expand...
Click to collapse
Badass
Sent from my myTouch_4G_Slide using xda premium
Let me take advantage of this newb. I got my new device, S-On Unlocked. I restored my modded version of stock and using blues UV 5% kernel. Wifi wont work, and my camera has weird lines on it. But the pics are still good. I just needa fastboot the boot.img righ'?
sinistersai4d4d said:
Apologies in advance if this is the wrong forum.
Today I successfully perm rooted my Doubleshot...
Then I tried to flash CM9 Alpha 5 using CW recovery.. downloaded the .zip...
Flashed it.. hit reboot... and it wont get past the mytouch splash screen.
I've tried flashing other roms, and other alphas.. but they all don't reboot into the rom.
I can still boot into recovery and get into ClockWork..
Any ideas on what I can flash or do to at least get any rom running on here... I'm not even picky at this point... I just wanted something like CM7 or some AOSP.
Thanks in advance.
Click to expand...
Click to collapse
1) This goes in General. I don't know why the mods can't just add a Q&A board to remove the n00b confusion.
2) Fastboot the ROM's boot.img before booting up.
blackknightavalon said:
1) This goes in General. I don't know why the mods just don't add a Q&A board to remove the n00b confusion.
2) Fastboot the ROM's boot.img before booting up.
Click to expand...
Click to collapse
Ok, I'm def S-ON but unlocked and nperm rooted.
Can someone walk me through what to do? How can I fastboot the rom's boot.img?
I'm sorry I'm new to this, that's why I'm using my secondary device to learn. I've been googling anything I can find and it got me to through the root process but now I'm stuck.
xmc wildchild22 said:
im assuming he's s on....remember to take the boot.img out of the cm9 zip and flash it using fastboot. You can find out more info on how to do it here. Also apology accepted (this should be in general)
Click to expand...
Click to collapse
This something I have to do with a PC (as opposed to Mac)? No way to unbrick this thing without methods like this? Just asking, before I try and commandeer a pc.
sinistersai4d4d said:
This something I have to do with a PC (as opposed to Mac)? No way to unbrick this thing without methods like this? Just asking, before I try and commandeer a pc.
Click to expand...
Click to collapse
Did you not read the stickies?
You have to take the bootimage from the rom that you are using and put in a folder and name it so you can reconize it. You follow the command prompt instructions they give in this thread. You have to have some knowlege of a PC in order to be successful. I had the same problems as you did. You can get it to work... Do you know how to use the command prompt for your PC?
Sent from my SGH-T959V using Tapatalk 2
wesomatic said:
You have to take the bootimage from the rom that you are using and put in a folder and name it so you can reconize it. You follow the command prompt instructions they give in this thread. You have to have some knowlege of a PC in order to be successful. I had the same problems as you did. You can get it to work... Do you know how to use the command prompt for your PC?
Click to expand...
Click to collapse
Not really. But I guess I'll start there...
And thanks for everyone's help. Here goes nothing.
sinistersai4d4d said:
Not really. But I guess I'll start there...
And thanks for everyone's help. Here goes nothing.
Click to expand...
Click to collapse
You can just flash back to stock to fix it. Learn to fastboot, then run CM9.
Sent from my Galaxy Nexus using Tapatalk 2
AgentCherryColla said:
You can just flash back to stock to fix it. Learn to fastboot, then run CM9.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks again for all your help...
Last question before I fastboot, is it necessary to have the SDK or ADB to fastboot? Can I fastboot/flash the kernel using Hasoon's all-in-one-kit (the app I used to attain root)? Or is it too late since now the device wont boot and Hasoon "can't find the device"?
I have the boot.img I want in a place where I can locate it. Can I use the command prompt without the SDK/ADB?
Interestingly enough I was able to mount using recovery, and boot a new kernal... phone won't boot but at least it's stuck at a different splash screen lol "mikroms"..
I'm calling this progress.
*UPDATE*
Ok, got it!
I mounted the phone to my computer using recovery and used the Hasoon kit to flash the CM boot image.. then I rebooted and got the mikroms splash screen. That was because the last zip i flashed wasn't CM.. it was the MikRom..
so I went back into recovery, flashed CM.. now I'm good!
sinistersai4d4d said:
Thanks again for all your help...
Last question before I fastboot, is it necessary to have the SDK or ADB to fastboot? Can I fastboot/flash the kernel using Hasoon's all-in-one-kit (the app I used to attain root)? Or is it too late since now the device wont boot and Hasoon "can't find the device"?
I have the boot.img I want in a place where I can locate it. Can I use the command prompt without the SDK/ADB?
Click to expand...
Click to collapse
Of course not. 'Fastboot' is an 'ADB' command. BUT if Hasoon's tool 'can't find device'....that's an ADB error message and you probably don't have all the drivers installed that you need but he has the necessary files included for what you need for 'Unlocked" & recovering from a mess-up. You may as well go ahead & install ADB tho....you'll eventually need it.
---------- Post added at 10:12 AM ---------- Previous post was at 09:59 AM ----------
sinistersai4d4d said:
Interestingly enough I was able to mount using recovery, and boot a new kernal... phone won't boot but at least it's stuck at a different splash screen lol "mikroms"..
I'm calling this progress.
Ok, got it!
I mounted the phone to my computer using recovery and used the Hasoon kit to flash the CM boot image.. then I rebooted and got the mikroms splash screen. That was because the last zip i flashed wasn't CM.. it was the MikRom..
so I went back into recovery, flashed CM.. now I'm good!
Click to expand...
Click to collapse
I believe what you did is 'Flash' a ROM from MikROMs but the kernel didn't go because you have S-On. Take that same '.zip' you just flashed, look inside it and put the file named 'boot.img' where you can find it in the windows 'path' and THEN
'fastboot flash boot boot.img' http://forum.xda-developers.com/showthread.php?t=1508556
You should boot up fine then.
Hi,
I had before the OTA for Jelly Bean an ICS unlocked and rooted.
I tried to use ShabbyPenguin to get it rooted again but now I have a broken recovery.
So not sure what do I need to get it rooted again.. Is it possible?
Thanks!
Not positive, but could u flash cwm through adb? Then just flash a rooted ROM, or supuser.zip. Is the bootloader is still unlocked?
Haven't heard good stuff about root toolkits, its actually really easy to do for our phones.
Not sure if it is possible to flash cwm trough adb... However I will try it later today...
And yes, bootloader is still unlocked...
rustyjay said:
Not positive, but could u flash cwm through adb? Then just flash a rooted ROM, or supuser.zip. Is the bootloader is still unlocked?
Haven't heard good stuff about root toolkits, its actually really easy to do for our phones.
Click to expand...
Click to collapse
Yeah, I am positive u could use adb fast boot to flash a recovery, cwm or twrp u just need the image.
hhhmmmm... no luck yet...
I tried to flash a recovery and it keeps giving me a message
<waiting for device>
After that it seems like stuck..
I read somewhere else that maybe because of the drivers, but I already tried a couple of versions 1.3.8 and 1.5.6 with the same result...
btw I'm using a Windows 7 64 bit machine...
Not sure if use a Linux machine will have any benefit...
rustyjay said:
Yeah, I am positive u could use adb fast boot to flash a recovery, cwm or twrp u just need the image.
Click to expand...
Click to collapse
Well...
Also tried the google usb drivers with no luck....
I guess that I will try it with some other windows/linux version later today...
Off but on topic. Describe what you call a broken a recovery please.
When I try to run the recovery it appears a dead android with a red exclamation mark on the screen....
After that it takes some time to reboot again...
albundy2010 said:
Off but on topic. Describe what you call a broken a recovery please.
Click to expand...
Click to collapse
That is stock recovery. It is not broken.
Yes I was saying it was broken because before the OTA update I had twrp as recovery, and now I can't flash any recovery
albundy2010 said:
That is stock recovery. It is not broken.
Click to expand...
Click to collapse
When you flash/install a ota your recovery gets wiped back to stock once it boots up due to the flash recovery script in the stock ROM.
Nothing is wrong with your device. Just follow a real guide on how to unlock and root. Real meaning using the SDK. Or even use one of those stupid one click crap. should not have a issue.
Guides are in the forum stickies.
Hi Guys,
Well not sure what the problem was.... maybe the drivers, maybe Win7 64 bits or I don't what...
I used a WinXP machine with the pdanet installed and it worked like charm...
I succesfully installed the recovery and root again.
Anyway... thanks for your time.
Glad to hear that.
I unlocked the boot loader of my HTC One XL, flashed TWRP, wiped cache, dcache, did a factory reset. Booted in factory default, copied ROM and GAPPS to folder, booted in TWRP, installed the ROM zip, installed the GAPPS zip. Rebooted into system. Now my phone wont turn on, there's no charging light. I can't boot into recovery - pressing power and volume down does nothing. I'm not even getting a charging light.
Did I brick this thing?
Does anyone have any suggestions?
Was my mistake not to have flashed the boot img?
BTW, I posted in "general" - sorry - didn't know - but now I can't figure out how to delete the thread.
Not a good day...:crying:
i don't see why your phone would be messed up.
you do need to "fastboot flash boot boot.img" though. what rom did you flash?
not sure now...
DvineLord said:
i don't see why your phone would be messed up.
you do need to "fastboot flash boot boot.img" though. what rom did you flash?
Click to expand...
Click to collapse
i'm thinking now maybe it was the wrong ROM. looks like aokp_endeavoru_unofficial_Oct-10-12-v3.0
guess its not looking good...
trueblueinpw said:
i'm thinking now maybe it was the wrong ROM. looks like aokp_endeavoru_unofficial_Oct-10-12-v3.0
guess its not looking good...
Click to expand...
Click to collapse
I believe your boot.img got overwritten with the endeavoru's /system partition.
You can fix it on a linux computer.
Can you get into recovery at all?
how would i fix w/ linux?
absolutelygrim said:
I believe your boot.img got overwritten with the endeavoru's /system partition.
You can fix it on a linux computer.
Can you get into recovery at all?
Click to expand...
Click to collapse
is there nothing that linux does not make better?! how would i fix this on linux?:good:
trueblueinpw said:
is there nothing that linux does not make better?! how would i fix this on linux?:good:
Click to expand...
Click to collapse
Well first.. Can you get into Recovery?
and second.. Is your device listed in windows as "QHSUSB_DLOAD"?
if it is recognized as "QHSUSB_DLOAD" try this
http://unlimited.io./qhsusbdload.htm
you will need linux
if it works, hurry up and go flash a boot.img and then the ROM for the AT&T one X, no more internationals ok?
didn't work...
absolutelygrim said:
Well first.. Can you get into Recovery?
and second.. Is your device listed in windows as "QHSUSB_DLOAD"?
if it is recognized as "QHSUSB_DLOAD" try this
http://unlimited.io./qhsusbdload.htm
you will need linux
if it works, hurry up and go flash a boot.img and then the ROM for the AT&T one X, no more internationals ok?
Click to expand...
Click to collapse
dang - can't believe i flashed the wrong rom - what a moron i am!
alright - so i tried that on ubuntu - didn't work - thought that might do the trick - looked promising...
trueblueinpw said:
dang - can't believe i flashed the wrong rom - what a moron i am!
alright - so i tried that on ubuntu - didn't work - thought that might do the trick - looked promising...
Click to expand...
Click to collapse
Is your phone listed in device manager as QHSUSB_DLOAD?
it is...
absolutelygrim said:
Is your phone listed in device manager as QHSUSB_DLOAD?
Click to expand...
Click to collapse
is that good?:laugh:
no
trueblueinpw said:
is that good?:laugh:
Click to expand...
Click to collapse
Uhh, no. You now have a very expensive paper weight. For now. I think there is a way to fix by linux and adb. Sorry bro
Sent from my HTC One XL using xda app-developers app
trueblueinpw said:
is that good?:laugh:
Click to expand...
Click to collapse
DvineLord said:
no
Click to expand...
Click to collapse
It is bad.. But it is 'good' because unlimited.io tool should have fixed it
I'm sure he won't want to.. but you can PM beaups.. He knows how to fix it manually, if he is willing to help.
There is a way to fix this on Linux. It is lengthy and difficult. But I think the solution was to push a new hboot while in QHSUSB_DLOAD, not partition 4 (which is your issue)
alright...
absolutelygrim said:
It is bad.. But it is 'good' because unlimited.io tool should have fixed it
I'm sure he won't want to.. but you can PM beaups.. He knows how to fix it manually, if he is willing to help.
Click to expand...
Click to collapse
thanks for the help. i might still have some hope as my unbuntu was version 11 and the u.io.tool specs version 12. (not sure why that would matter as the tool seemed to run okay). if that doesn't work i'll try to pm beaups.
i do appreciate the help.:good:
trueblueinpw said:
thanks for the help. i might still have some hope as my unbuntu was version 11 and the u.io.tool specs version 12. (not sure why that would matter as the tool seemed to run okay). if that doesn't work i'll try to pm beaups.
i do appreciate the help.:good:
Click to expand...
Click to collapse
no. go update to Ubuntu 120.4, it should work then.
updating to 12 now...
absolutelygrim said:
no. go update to Ubuntu 120.4, it should work then.
Click to expand...
Click to collapse
hope it works... :fingers-crossed:
trueblueinpw said:
hope it works... :fingers-crossed:
Click to expand...
Click to collapse
You can also dd the partitions back to your phone.
You would need someone to give you a partition 4, and you would have to rewrite it back to your phone through emmc mode, I suggest reading up on this incase the unlimited.io tool doesn't resolve your problem
Sent from my HTC One XL using xda app-developers app
dd?
absolutelygrim said:
You can also dd the partitions back to your phone.
You would need someone to give you a partition 4, and you would have to rewrite it back to your phone through emmc mode, I suggest reading up on this incase the unlimited.io tool doesn't resolve your problem
Is there any information about how to "dd the partitions"? Before I flashed the [wrong] ROM, I copied the backup I made with TWRP. So I have the files on my Windows computer (boot.emmc.win, boot.emmc.win.md5, etc.). Would these backup files be at all helpful?
I'm just not sure what to do now. Any help?
Click to expand...
Click to collapse
trueblueinpw said:
absolutelygrim said:
You can also dd the partitions back to your phone.
You would need someone to give you a partition 4, and you would have to rewrite it back to your phone through emmc mode, I suggest reading up on this incase the unlimited.io tool doesn't resolve your problem
Is there any information about how to "dd the partitions"? Before I flashed the [wrong] ROM, I copied the backup I made with TWRP. So I have the files on my Windows computer (boot.emmc.win, boot.emmc.win.md5, etc.). Would these backup files be at all helpful?
I'm just not sure what to do now. Any help?
Click to expand...
Click to collapse
omfg, if you have a nandroid backup and can get into recovery just push you nand backup to your phone and restore it from recovery.
start there before you start dd'ing partitions.:silly:
Click to expand...
Click to collapse
I can't get into recovery mode...
Crappyvate said:
trueblueinpw said:
omfg, if you have a nandroid backup and can get into recovery just push you nand backup to your phone and restore it from recovery.
start there before you start dd'ing partitions.:silly:
Click to expand...
Click to collapse
I can NOT get into recover. My phone is unresponsive - push power and volume down does nothing - no charge light - tried plugging into wall charges, etc.
So, I don't know how to dd the partition information to my phone. I'm looking through the threads now but I haven't found anything.
I have a linux machine (Ubuntu v.12) windows 7 (where I have the backup files) and a Mac (like that's going to help...). I'm obviously new to the whole ROM flashing thing - but I'm pretty good with computers otherwise.
I guess what I'm looking for is a way to push the backup files I have from my TWRP to the heretofore brick HOX? I just don't know where to start.
Click to expand...
Click to collapse
Beaups is the man to ask. But I wouldn't count on a friendly reply as I'm sure he's been bombarded with this same question. He's pretty much the only one that could point you in the RIGHT direction. Although 18th.abn is also very good with that and more forgiving lol
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
im trying to get back to complete stock to start over again because i cant get help with my 'no signal problem' but it wont start my factory restore even though i am using the right img.
the issues started when i tried to install Cataclysm (http://forum.xda-developers.com/showthread.php?t=2518660) they have a thing in there saying that its a known problem to not get signal when flashing twrp
(My mobile signal/radio isn't working anymore!
- There's a bug with TWRP that remove/corrupt your baseband during flash. Please refer to the twrp team for a fix.)
no link and i cant find it on google so any help would be appreciated
image attached its the error when trying to restore the factory image.
dudekiller said:
im trying to get back to complete stock to start over again because i cant get help with my 'no signal problem' but it wont start my factory restore even though i am using the right img.
the issues started when i tried to install Cataclysm (http://forum.xda-developers.com/showthread.php?t=2518660) they have a thing in there saying that its a known problem to not get signal when flashing twrp
(My mobile signal/radio isn't working anymore!
- There's a bug with TWRP that remove/corrupt your baseband during flash. Please refer to the twrp team for a fix.)
no link and i cant find it on google so any help would be appreciated
image attached its the error when trying to restore the factory image.
Click to expand...
Click to collapse
You can always try the second method for the "BACK TO STOCK" guide from here:
http://forum.xda-developers.com/showthread.php?t=2513701
Even better you can use the instructions from the second post of that thread to wipe clean all your partitions prior to flashing them via fastboot.
quendil said:
You can always try the second method for the "BACK TO STOCK" guide from here:
http://forum.xda-developers.com/showthread.php?t=2513701
Even better you can use the instructions from the second post of that thread to wipe clean all your partitions prior to flashing them via fastboot.
Click to expand...
Click to collapse
im still getting invalid bootloader img
dudekiller said:
im still getting invalid bootloader img
Click to expand...
Click to collapse
have you extracted all the images on C:/image-hammerhead-krt16m like the example?
Have you renamed "bootloader-hammerhead-XXXXXX.img" to "bootloader.img" and "radio-hammerhead-XXXXXX.img" to "radio.img"?
quendil said:
have you extracted all the images on C:/image-hammerhead-krt16m like the example?
Have you renamed "bootloader-hammerhead-XXXXXX.img" to "bootloader.img" and "radio-hammerhead-XXXXXX.img" to "radio.img"?
Click to expand...
Click to collapse
yes, it seems that twrp corrupted something and it doesnt recognize the device anymore.
dudekiller said:
yes, it seems that twrp corrupted something and it doesnt recognize the device anymore.
Click to expand...
Click to collapse
Oh damn...
On bootloader when you give the command fastboot devices does it show you anything?
i wonder if the TWRP bug is why i was getting bootloop when flashing Bootanimations the other day?
Wug's Nexus toolkit has been my lifeline with 4 nexus devices.
alright guys i figured it out i did a oem lock and unlock and then the factory image worked so im stock right now... it might stay that way for a bit.. lol
comicbookguy72 said:
Wug's Nexus toolkit has been my lifeline with 4 nexus devices.
Click to expand...
Click to collapse
and this is the problem with pretty much everything. people relying on toolkits, then when something screws up, they have no idea what happened.
Zepius said:
and this is the problem with pretty much everything. people relying on toolkits, then when something screws up, they have no idea what happened.
Click to expand...
Click to collapse
his first priority is fixing it. his second priority is possibly finding out why he borked it and not making the same mistake again. i've borked stuff learning and fixed it with toolkits.
not everyone wants to learn ADB or fastboot commands, or install the SDK, and NOT EVERYONE HAS TO. not everyone is a would-be developer
dudekiller said:
they have a thing in there saying that its a known problem to not get signal when flashing twrp
(My mobile signal/radio isn't working anymore!
- There's a bug with TWRP that remove/corrupt your baseband during flash. Please refer to the twrp team for a fix.)
Click to expand...
Click to collapse
So why did you flash via TWRP then?
Han Solo 1 said:
So why did you flash via TWRP then?
Click to expand...
Click to collapse
i didnt go through the faqs before installing, i looked at the rom and what it offered. it said stable so i wasnt to worried about bugs since i was coming from cm11
I am trying to unlock my photons Q bootloader on the Motosite which is well known. I check it now a million times if I have a typo and I Dont.
The button with the "request unlock key " comes up, I hit it, and didnt recieve any mail. And I started last week doing it.
The Photon q has a GSM mod done by the almighty CornholioGSM, and I am using a connection from Germany. Since it is a Sprint photon, I thought that it might be discarded, because the ip it comes from is german ?..
Would be great to have someone telling me if there is another solution to this ..
I tried to flash with the locked bootloader the recovery, but get the message "invalid image size" on CWM or TWR.
I hope this Q is not too noob for all of you.
I would try motochopper or whatever the exploit was to unlock without Moto's assistance.
It may have been unlocked previously, (relocked for warranty swap) in which case I'm not sure you can use the site to re-unlock the device...
arrrghhh said:
I would try motochopper or whatever the exploit was to unlock without Moto's assistance.
It may have been unlocked previously, (relocked for warranty swap) in which case I'm not sure you can use the site to re-unlock the device...
Click to expand...
Click to collapse
First of all thank your for your answer ! Most likely you are right. Now my Q, I did read Motochopper just install SU and also gives root, but without touching the bootloader. Dont I need to unlock the bootloader if I want to install Cyanogen or any other Mod ? Maybe I understood that wrong.
x11-nice said:
First of all thank your for your answer ! Most likely you are right. Now my Q, I did read Motochopper just install SU and also gives root, but without touching the bootloader. Dont I need to unlock the bootloader if I want to install Cyanogen or any other Mod ? Maybe I understood that wrong.
Click to expand...
Click to collapse
Ok, motochopper did its job. Thank you for that ! ! ! I guess now I have to go on with Goomanager. :good:
x11-nice said:
Ok, motochopper did its job. Thank you for that ! ! ! I guess now I have to go on with Goomanager. :good:
Click to expand...
Click to collapse
If you're wanting to install TWRP, I think they have a new app now... TWRP Manager?
I've always installed recovery using fastboot on the Q, so I'm not very familiar with the apps .
arrrghhh said:
If you're wanting to install TWRP, I think they have a new app now... TWRP Manager?
I've always installed recovery using fastboot on the Q, so I'm not very familiar with the apps .
Click to expand...
Click to collapse
I tried the TWRP Manager, the manager shows me success for installing the TWRP recovery, but I cant access it. It switches back into Fastboot telling me flash failure. Actually I would like to install CM11. Well I will try to install the latest nightly and see whats happening. Hopefully it doesnt brick. :silly: Thanks for your help, I will let you know about success or fail.
x11-nice said:
I tried the TWRP Manager, the manager shows me success for installing the TWRP recovery, but I cant access it. It switches back into Fastboot telling me flash failure. Actually I would like to install CM11. Well I will try to install the latest nightly and see whats happening. Hopefully it doesnt brick. :silly: Thanks for your help, I will let you know about success or fail.
Click to expand...
Click to collapse
You need to install some sort of custom recovery in order to flash a custom ROM.
Open Recovery or TWRP are both fine. CWM is really old for our device, I can't recommend it.
arrrghhh said:
You need to install some sort of custom recovery in order to flash a custom ROM.
Open Recovery or TWRP are both fine. CWM is really old for our device, I can't recommend it.
Click to expand...
Click to collapse
So yesterday Motorola send me the messages with the codes which I apllied for almost 2 weeks ago... I guess the next days will arrive more.
Ofc I tried to unlock and it worked as expected. Now with fastboot flashing tto recovery 2.8.0.1 of TWRP went flawless. Actually I am really impressed how easy it worked, unlike using all the other tools like motochopper and TWRP Manager, which actually didnt solve the problem at all not having a unlocked bootloader.
Now my last Q: Which CM11 is the preferable choice for using it with the Photon. I dont care so much about Nightly or not. What I need is stable VPN and WIFI, and working mail and messenger like Cypher.
And! Thank you so much arrrghhh for all your advice and help. This forum and its users are really a great help to the community of android !
All DONE
Ok used TWRP 2.8.0.1 to install cm-11-20141012-NIGHTLY-moto_msm8960_jbbl and the PA-Gapps-Modular for 4.4.x. Great work on everyone who participated making this possible and developing the necessary tools.
Thanks again to Arrrghhh and Cornholio !