Hey, so I was trying to get this thing rooted and somehow screwed up. So I got adb and fastboot set up, unlocked the bootloader, flashed the modified A9 boot image, flashed TWRP, and booted into recovery. I tried to mount data as the rooting guide said but when I pressed it it would not check it in. So I went and did a factory reset. Idk what happened but I guess I must have formatted the system partition as well because now TWRP gives me the No OS Installed message and will not boot past the splash screen. The splash screen does however have the red writing about the modded boot img so I know that part worked. I can get into download, bootloader, AND TWRP just fine, they all work and adb devices shows the phone listed as recovery mode when in TWRP. I've tried to sideload CM13 but it gives me Error: Closed on the pc side in cmd prompt. I've tried formatting internal sd through terminal in TWRP as well as many other data resets and they all fail. I've tried installing CM13 zip file straight from the sdcard in TWRP but that fails as well. At this point I'm not quite sure what to do. I'm currently downloading a stock RUU but it is going to take 5 hours because the download source has a slow connection. Should I relock the bootloader and try to sideload the RUU? Is there a way to install a rom through fastboot? I'm fairly new to fastboot but not new to adb and cmd prompt. Any help would be GREATLY appreciated!
UPDATE: So I flashed stock boot, system, and recovery images linked from another post in the A9 forums... and it now boots but it is definitely images from a Japanese version of the phone. So I tried to flash the correct RUU for my phone and it gives me an error message "os-version in android-info missing or invalid". Not sure what that means. I tried flashing the RUU by renaming it to 2PQ9IMG and putting it in the root of my SD card, then booting into download mode. That's where I got the error. So now I'm not quite sure what my next step is. Ultimately I'm just trying to be on a stock rooted ROM. Can anyone help me figure out what to do next?
http://www.htc.com/us/support/rom-downloads.html
Find your firmware here and try flashing it.
d34thbl00m said:
UPDATE: So I flashed stock boot, system, and recovery images linked from another post in the A9 forums... and it now boots but it is definitely images from a Japanese version of the phone. So I tried to flash the correct RUU for my phone and it gives me an error message "os-version in android-info missing or invalid". Not sure what that means. I tried flashing the RUU by renaming it to 2PQ9IMG and putting it in the root of my SD card, then booting into download mode. That's where I got the error. So now I'm not quite sure what my next step is. Ultimately I'm just trying to be on a stock rooted ROM. Can anyone help me figure out what to do next?
Click to expand...
Click to collapse
Hello there. If you want to just revert back to a stock rooted rom I recommend just flashing over Captain Throwbacks Rom he posted in the One A9 Development. If your phone is not S-Off that should be fine. Having the unlocked bootloader and TWRP is already good. If you have $25 bucks I recommend doing S-Off so you can crossflash any firmwares you want without bricking the phone.
The only way to use RUU flashing is to put the phone in download mode and naming it a certain name and it does all the flashing on its own not via twrp. So whatever phone model you have go find the zip.
1. I'm guessing your on the AT&T variant so for example download 1.27.502.5 AT&T. Once you have the zip file downloaded have it on your computer desktop ready.
2. Boot into recovery/TWRP. Goto Wipe. Do an advanced Wipe and delete out system/data/dalvik. Once you do that click on Format Data and type in Yes. Doing those 2 formats will clean the phone up.
3. Now plug in your phone into any available USB 2.0 slots and make sure you have htc drivers installed verifying the phone pops up in my devices in your computer. Once you plug in your phone into your computer hit Mount. It should pop up like a USB stick. Now goto your HTC device internal storage. Make a folder called 0 or download. Place the zip into that folder. Once that ONE zip is copied over go back home and hit Install from Zip and find it on the internal storage. It should flash over successful and let it boot. First boot sometimes can take 5-10 minutes.
4. profit
vang2k said:
Hello there. If you want to just revert back to a stock rooted rom I recommend just flashing over Captain Throwbacks Rom he posted in the One A9 Development. If your phone is not S-Off that should be fine. Having the unlocked bootloader and TWRP is already good. If you have $25 bucks I recommend doing S-Off so you can crossflash any firmwares you want without bricking the phone.
The only way to use RUU flashing is to put the phone in download mode and naming it a certain name and it does all the flashing on its own not via twrp. So whatever phone model you have go find the zip.
1. I'm guessing your on the AT&T variant so for example download 1.27.502.5 AT&T. Once you have the zip file downloaded have it on your computer desktop ready.
2. Boot into recovery/TWRP. Goto Wipe. Do an advanced Wipe and delete out system/data/dalvik. Once you do that click on Format Data and type in Yes. Doing those 2 formats will clean the phone up.
3. Now plug in your phone into any available USB 2.0 slots and make sure you have htc drivers installed verifying the phone pops up in my devices in your computer. Once you plug in your phone into your computer hit Mount. It should pop up like a USB stick. Now goto your HTC device internal storage. Make a folder called 0 or download. Place the zip into that folder. Once that ONE zip is copied over go back home and hit Install from Zip and find it on the internal storage. It should flash over successful and let it boot. First boot sometimes can take 5-10 minutes.
4. profit
Click to expand...
Click to collapse
Well therein lies the problem, I've tried flashing zip files but they always return with an error, same with trying to do ANY wipe of any kind... it returns with the error that it is unable to mount storage...in all the reading and research I've been doing it sounds like somehow the internal sdcard became corrupted. There are many guides on how to fix this for older HTC phones but nothing current for the One A9. I'm going to give the RUU that was posted above a shot, if that fails then I guess my only option is to magically figure out how to manually format my internal sd?
Ive had that probel occur for me before on my htc one m8 flashing google play editions over the sense firmwares. It will say no internal data. Your best bet would be to put the phone in download mode and put the file in a microsd and the phone will auto correct the correct firmware and data partitions. Go look on youtube i think its called ruu m8 or m9 download mode. Too bad htc doesnt have odin or rsd where you just click restore.
---------- Post added at 06:27 PM ---------- Previous post was at 06:26 PM ----------
Did you do the format data and typing in yes? Do that twice and reboot inton recovery
d34thbl00m said:
Well therein lies the problem, I've tried flashing zip files but they always return with an error, same with trying to do ANY wipe of any kind... it returns with the error that it is unable to mount storage...in all the reading and research I've been doing it sounds like somehow the internal sdcard became corrupted. There are many guides on how to fix this for older HTC phones but nothing current for the One A9. I'm going to give the RUU that was posted above a shot, if that fails then I guess my only option is to magically figure out how to manually format my internal sd?
Click to expand...
Click to collapse
No dice on the RUU exe file. Anyone have a link to the 1.27.502.5 zip file? If I can try that it might work, other than that maybe someone has the boot, system, and recovery image files for 1.27.502.5?
To ruu youll have to relock the phone and also make sure the phone id matches the ruu.
---------- Post added at 06:45 PM ---------- Previous post was at 06:44 PM ----------
d34thbl00m said:
No dice on the RUU exe file. Anyone have a link to the 1.27.502.5 zip file? If I can try that it might work, other than that maybe someone has the boot, system, and recovery image files for 1.27.502.5?
Click to expand...
Click to collapse
Htc website has the files hosted if you cant find the zip.
vang2k said:
To ruu youll have to relock the phone and also make sure the phone id matches the ruu.
---------- Post added at 06:45 PM ---------- Previous post was at 06:44 PM ----------
Htc website has the files hosted if you cant find the zip.
Click to expand...
Click to collapse
Phone is already relocked...lack of knowledge is definitely not the problem here. When I run the RUU exe file it gets to the point where I accept the terms and agreements and then once I hit next it disappears and doesn't do anything. So that's why I need to find the zip file to rename and attempt to flash in download mode.
http://www.htc.com/us/support/htc-one-a9-att/news/ scroll to download very bottom. Hopefully that works.
Sorry, I've tried that one 3 times now :/ It starts running and then just quits on me. Not sure why, as I'm sure it works for hundreds of other people. Going to try a flashable zip next, if that doesn't work then I have no idea what to do.
At a complete loss here. Cannot find any way to get the internal SD to mount so I can flash ANYTHING!!! It's driving me nuts. I can't data wipe or do anything I need to get on the right track. Can't even root. So unless anyone else has any final suggestions I'll be getting a warranty replacement.
d34thbl00m said:
Sorry, I've tried that one 3 times now :/ It starts running and then just quits on me. Not sure why, as I'm sure it works for hundreds of other people. Going to try a flashable zip next, if that doesn't work then I have no idea what to do.
Click to expand...
Click to collapse
Have you tried flashing the ruu via fastboot into bootloader than running adb command. You should be able to flash the ruu even with s-on. It won't let you flash if your flashing the wrong one
fastboot oem rebootRUU htc_fastboot flash zip <file_name>.zip
I can't seem to find the correct zip file for the exact RUU for this phone...I can find the exe file no problem but can't get it to work. Does anyone at least have the 1.27.502.5 stock boot and system images? If I can locate the RUU in a zip file I'll give your suggestion a shot.
Try this zip it's for your same model but an older zip for the ruu in a zip file. At least it will format your data and get your phone back on track and you can always update the phone once your running sense or get s-off and flash the region free firmware. https://www.androidfilehost.com/?fid=24269982087001291
So I downloaded that one, threw it in my fastboot folder, ran it through HTC_fast boot, and this is the output I got:
EDIT: I did a getvar all and it said I was on 1.27.502.5, but HTC Sync Manager says I'm on 1.27.709.15 because of the system image I flashed. SOOOO I just need to flash the system.img from 1.27.502.5 or older in order to get my numbers straightened back out and flash the correct RUU to wipe my data. Please, anyone out there happen to have an AT&T A9 that can upload the system.img?
d34thbl00m said:
So I downloaded that one, threw it in my fastboot folder, ran it through HTC_fast boot, and this is the output I got:
Click to expand...
Click to collapse
it looks like you didn't run the fastboot oem rebootRUU command first? try running that command first than follow the flashing. the reason that zip doesn't want to update is because one of two things keeps happening. the phone won't update because not on stock recovery/wrong MID/CID. To install that zip this is the method I would use. Normally those RUU things don't want to flash if the recovery isn't stock or something doesn't match up. Rename the file that you downloaded from android filehost to firmware.zip first.
1. Reboot to bootloader
2. run the command fastboot oem rebootRUU
3.now once it reboots into that mode it kind of will look like a grey screen with a HTC sign and a green meter bar
4. run the command fastboot flash zip firmware.zip , than run it again and should say 100% complete and than run fastboot reboot
If all those fail do the RUU update via in download mode. Start the phone with volume down and than choose download mode. Rename the zip file into 2PQ9IMG.zip and copy that into a microSD card formatted fat32. Once the phone reads it, it will being a automated update process. Once its all done the phone might keep asking to update the softare via volume up. Take the microSD out and let the phone completely start up.
Make sure all your PC drivers are correct, then get rid of HTC Sync Manager if installed. Boot the phone into download mode and run the latest RUU file for your version of the phone. Repeat these steps until the RUU works properly. In my experience if the RUU doesn't work either the file is corrupt or the person flashing it is.
Thanks for the replies guys. I've literally done all of that several times and get the same errors every time. I assure you these are NOT user errors. The problem most certainly lies in that in phone settings my version number is 1.27.502.5, but in fastboot and HTC sync manager my version number is 1.27.709.15. So when I flash literally anything RUU it has no flipping clue what version my phone is. All I need to fix my problem is a copy of the stock system img file for 1.27.502.5. Once I flash that my versions will match up and the RUU should work just fine.
Related
My first post here so go easy on me
Anyway, I got an Evo Shift, I do not know its history, but its stuck in some sort of a boot loop, on the white screen with green HTC logo.
Things I know:
****UNLOCKED****
SPEEDY XE SHIP S-ON
HBOOT -0.99.0001
RADIO - 1.08.01.0111
Clockwork Recovery v5.0.2.0
I did not get an SD card with it, no recovery image.
RUU says version is 2.77.651.3
I know the S-on is a problem.
I have tried all 4 of the RUU versions - failed.
Tried RUU with Gold Card - failed.
Tried rom.zip from each RUU renamed to PG06IMG.zip - failed.
I have tried custom roms of all sorts, every methoud I found - failed.
Where do I go from here? Is there a way of manually flashing all the partitions from a ROM.zip file via fastboot? Is there a way of disabling a version check in RUU? Or is there a way of disabling MD5 sum in Clockwork so I can try flashing a restore image from another Shift?
I have spent 3 days on this phone, and I would hate to admit defeat, so I am reaching out to the genius minds here. Thanks in advance!
Okay, I fixed it. did a write up on how I did it in case someone else fubars their phone.
Things you will need:
Android SDK
HTC Drivers
7-zip
RUU_Speedy_Sprint_WWE_1.17.651.1_Radio_1.07.00.112 9_NV_SPCS_1.52_1103_release_160079_signed.exe
On your computer, search for ROM.ZIP. Include system locations and hidden files.
Delete any instances of it that you may find.
Take the SD card out of the phone.
Put your Shift into fastboot (vol/down + power)
Run the RUU, let it get stuck.
On your computer, run a search for ROM.ZIP while the RUU is running. Its gonna show up in some temp folder.
Copy it to your desktop.
Use 7zip to extract it (for whatever reasons Windows can't extract it).
Open the extracted rom.zip folder.
Copy all files and place them in your SDKs platform tools folder.
Shut down the RUU, reboot the phone into recovery (vol/down + power).
Run CMD and change directories to your platform tools folder.
Type the command "fastboot flash recovery recovery.img" (without the quotes) - this gets rid of any custom recovery like Clockwork, etc.
Reboot the phone into recovery again, you should have a triangle with an ! next to it on black background.
Go back to CMD and your platform tools, and start flashing the following:
fastboot flash boot boot.img
fastboot flash dzdata dzdata.img
fastboot flash partition partition.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Reboot the phone.
After 30 seconds of white HTC screen, your phone should boot up fine and you will be in Android 2.2.
Let me know if it worked out for you, I just fixed mine less than an hour before writing this up.
Also, if anyone out there sees anything redundant, or can help me clean this process up a bit, I welcome your input.
gzetski said:
Okay, I fixed it. Please delete the thread. Unless someone wants me to do a write up on how I did it in case someone else fubars their phone.
Click to expand...
Click to collapse
Did you unlock the bootloader with htcdev tool?
The bootloader was already unlocked when I got the phone.
Thanks for this. I will test it and add it to my guide.
VICODAN said:
Thanks for this. I will test it and add it to my guide.
Click to expand...
Click to collapse
You're welcome... I figured I'd just go hard since it was bricked already.
Speaking of guides though, can I get a bit of clarification on something?
http://forum.xda-developers.com/showthread.php?t=1357157
2.3.4 step 15,
Place misc.img and PG06IMG.zip on sdcard using windows explorer or "adb push /sdcard/file.xxx" via usb
Click to expand...
Click to collapse
Where is the MISC.IMG coming from, and what is ( rom? which one? etc.)in the PG06IMG.zip?
Thanks!
And BTW, I am now rooted, but with S-ON... Grrr. Superuser works, rom manager works, pretty much anything requiring root access works. I have rebooted the thing like 20 times to see if it goes away, and its sticking just fine, but I am afraid of trying to flash a custom rom with the S-ON.
All attempts to flash ENG bootloader fail, both by flashing via fastboot (all my MD5 sums match, the process is flawless from start to finish, when I reboot, still same bootloader with S-ON), or using ShiftRR.
Any ideas?
gzetski said:
You're welcome... I figured I'd just go hard since it was bricked already.
Speaking of guides though, can I get a bit of clarification on something?
http://forum.xda-developers.com/showthread.php?t=1357157
2.3.4 step 15,
Where is the MISC.IMG coming from, and what is ( rom? which one? etc.)in the PG06IMG.zip?
Thanks!
Click to expand...
Click to collapse
shift-rootkit.rar
Read the prereqs.
Okay, got it.
Too many things floating through the intertubes with similar filenames.
gzetski said:
Okay, got it.
Too many things floating through the intertubes with similar filenames.
Click to expand...
Click to collapse
Yep, I've finally got the thread pinned, and I created 2 videos on how to do it the right way. They are uploading to youtube now.
S-off?
Did you ever figure out how to get S-Off? I seem to be right where you were a few days ago with the phone appearing to have root, but S-on still there. I'm also running HBOOT -0.99.0001 and unlocked via the HTC Dev tool. Is there anyway to downgrade to .93 or to turn S-Off. My ultimate goal is to get Cyanogenmod on this Shift.
Thanks in advance!
I have not messed with the phone for a few days. I am gonna try to go back to 2.3.4 then downgrade again. Most likely what I ended up having is a bunch of borked files, hopefully the latest RUU will fix that. This was really intended as a brick fix and not a legitimate 2.2 downgrade. When I mess with it, I will post the results for you though.
Omg thank you! I accidentally bricked one of my evo shifts and spent 3 hours trying to figure out how to fix it. I'm so glad I ran into this thread. Worked like a charm for me.
MTsol said:
Omg thank you! I accidentally bricked one of my evo shifts and spent 3 hours trying to figure out how to fix it. I'm so glad I ran into this thread. Worked like a charm for me.
Click to expand...
Click to collapse
Its not a brick if you can fix it... Bricked phones are permanent paperweights, nothing more, nothing less...
Sent from my PG06100 using Xparent Blue Tapatalk 2
drob311 said:
Its not a brick if you can fix it... Bricked phones are permanent paperweights, nothing more, nothing less...
Sent from my PG06100 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Yes Sir . Been there done that. Had a HERO that somehow got " water damaged " after it was BRICKED .
signature verify fail
gzetski said:
Okay, I fixed it. did a write up on how I did it in case someone else fubars their phone.
Things you will need:
Android SDK
HTC Drivers
7-zip
RUU_Speedy_Sprint_WWE_1.17.651.1_Radio_1.07.00.112 9_NV_SPCS_1.52_1103_release_160079_signed.exe
On your computer, search for ROM.ZIP. Include system locations and hidden files.
Delete any instances of it that you may find.
Take the SD card out of the phone.
Put your Shift into fastboot (vol/down + power)
Run the RUU, let it get stuck.
On your computer, run a search for ROM.ZIP while the RUU is running. Its gonna show up in some temp folder.
Copy it to your desktop.
Use 7zip to extract it (for whatever reasons Windows can't extract it).
Open the extracted rom.zip folder.
Copy all files and place them in your SDKs platform tools folder.
Shut down the RUU, reboot the phone into recovery (vol/down + power).
Run CMD and change directories to your platform tools folder.
Type the command "fastboot flash recovery recovery.img" (without the quotes) - this gets rid of any custom recovery like Clockwork, etc.
Reboot the phone into recovery again, you should have a triangle with an ! next to it on black background.
Go back to CMD and your platform tools, and start flashing the following:
fastboot flash boot boot.img
fastboot flash dzdata dzdata.img
fastboot flash partition partition.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Reboot the phone.
After 30 seconds of white HTC screen, your phone should boot up fine and you will be in Android 2.2.
Let me know if it worked out for you, I just fixed mine less than an hour before writing this up.
Also, if anyone out there sees anything redundant, or can help me clean this process up a bit, I welcome your input.
Click to expand...
Click to collapse
First, I want to thank you for posting this even though it hasn't yet worked for me. I'm in essentially the same position you started in. Phone will not boot past the green-on-white HTC logo. I boot to recovery and can get to fastboot mode with USB detected. I flashed recovery.img and boot.img with no problems, but trying to flash dzdata onwards gives me the same error every time: "(bootloader) signature checking... FAILED (remote: signature verify fail)" and will not flash the other components from ROM.ZIP.
Any thoughts on how to proceed? This thing is rapidly approaching permanent brick status.
You need to unlock your bootloader and then flash the rom. zip files through fastboot
The "failed" message means that your bootloader is locked
to get S-off the easiest method is to downgrade your device from 2.3.4 to 2.2 and then FOLLOW THE SAME INSTRUCTIONS AS OBTAINING S-OFF ON 2.3.4. i had the same issue when i first unlocked my Shift bootloader.
Hi,
i came to the screen install form zip on sdcard
but then it starts installation
and shows : installation aborted
now i cant start the phone i always get tothis screen
with the red text this build is for ....
what can i do?
edit: now i am again there where i can install zip from sdcard, but now it doesnt recognize the sdcard. What can I do, because i the phoen does not take a microsdcard where I could put a new rom.
how can i get access to the internela storage now wihtour a os?
How did this happen ? Selecting a ROM to flash in recovery cant really cause so much damage if it fails. They usually fail because of a md5 mismatch or something.
try to mount the sd card and you can use adb to push files to it..
you could also try a full wipe..
I did several things. I rooted and unlocked the device
and now it does not boot.
Everytime I tired to flash leedroid or stock rom with choosing install form zip
installation get aborted.
I am only able to get into the boolloader and into the recovery.
how can i restore the phone?
wipe and recovery is not possible i always end in this screen
with the red text.
edit: i think i try to get into booloader and copy another file version with adb to the sd card and hope it was a download error.
but why the hell then did both the leedroid 'AND the stock rom fail?
did you flash the boot.img BEFORE flashing leedroids ROM ??
If not i suggest trying that, If that fails, Just run an RUU and start from the beginning
Thanks for the Idea,
my problem is that i cant get access to the memory wihtout a working rom
on it And now i also dont get into the recovery CWMS.
I thouzhg power+vol up would do it but it doesnt work
I think i destroyed my brand new phone.
but thanks for helping.
It's not broken.
Try Power + Vol. down. Possibly you need to retry this several times to get into the bootloader.
its not destroyed dont worry..
Run an RUU and all will be good again. Whats your CID ?
That is the problem I cannot put up software on the device
so how should i run a ruu?
Where can i get the CID from wihtout starting the phone?
I hope you have a trick how I can save the device.
angeloski said:
That is the problem I cannot put up software on the device
so how should i run a ruu?
Click to expand...
Click to collapse
You run it from your Windows desktop. Download your appropriate RUU here for example (as it takes a loooooong time).
Connect your phone to your computer via USB.
Double Click the RUU-file.
Answer the Questions and the update will start.
Remember: Your device will be reset to factory default and your data on sd card will be gone so.
Edit: You will still have to start it with power + vol. down buttons pressed (as far as I remember).
angeloski said:
That is the problem I cannot put up software on the device
so how should i run a ruu?
Where can i get the CID from wihtout starting the phone?
I hope you have a trick how I can save the device.
Click to expand...
Click to collapse
To get into the bootloader try this.
Press and hold volume down, then power. Hold both down together for 5 secs, let go of the power button then press the power button several times. This always works for me.
If this works then your phone is easy to fix.
Maybe you could try to reflash the boot.img from leedroid via fastboot.
Then flash a proper recovery.img via fastboot (I use clockworkmod)
As I heard you could then push the rom.zip via Adb the sdcard while in recovery. Last step would be install zip from sdcard.
Sent from my HTC One S using XDA
Have you installed supersu via install ZIP from sdcard? I think this needs go be installed before installing the Rom. I Don't Know it exactly. But like this it worked for me when coming from stock rom. Thats how it worked for me:
1. Unlock bootloader via HTCDev
2. flash recovery image via fastboot
3. Install SuperSU from zipfile in recovery
4. Flash boot.img from Leedroid
5. Install Leedroid from sdcard
So maybe you missed one of the steps.
Sent from my HTC One S using XDA
to get CID go into fastboot and type in cmd window ''fastboot getvar cid''
If your phone is branded, you will need that branded RUU, So i assume you will need o2 Germany RUU
Reflash recovery in fastboot, should give you access to sdcard back.
Sent from my HTC One S using xda premium
i did the same thing to my one s yesterday... followed all the steps for leedroid n got same frustration u have...
theres a nandroid file in the dev section... fastboot the boot.img and the recovery.img
ya phone WILL boot back up
ok guys ty for cheeering me up.
i wil try it with a ruu, where can i find a ruu for my htc one s.
the link in the previuos post ist offline.
i think it was 1.78.407.x when i looked the last time in my handy.
thanks
so my cid is
C:\Android\android-sdk\platform-tools>fastboot.exe getvar cid
cid: O2___102
finished. total time: 0.003s
Like i said it is a O2 i hope this helps finding the ruu
well check the Shipped ROM thread.. If its not there you can ask the OP Football if he has it or can get it..
Some RUU's cost $13 so if you know someone else who wants it, you could split the cost ?
so far, now am in the recovery flash but it is the same
count mount /sdcard
how can i put a file onto the sdcard when i have no access?
partionoing sdcard doesn't help
i was looking for this boot.img and recovery.img which was posted before
i dont find it can someone link me to it if he knows what was meant?
thanks
edit: i was desperate and tried:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
but the second order was not successful
ist there another way to fix this usb brick
and to get access to /sdcard
new edit: now i write also in the help thread (noob friendly) i hope that is ok.
Did you already try this
http://forum.xda-developers.com/showthread.php?t=1667929
Or this
http://forum.xda-developers.com/showthread.php?t=1630459
Sent from my HTC One S using XDA
Something went wrong which I am not gonna explain too much.
Now My phone doesn't have an OS.
I have Unlocked Bootloader,
I have CWM installed. However, the USB storage Mount isn't working. "No UMS error"
I can still use CWM, but I don't have any rom in the SDCARD.
I can boot into boot loader, I can see fastboot USB.
I want to install a rom, any rom for now. but I don't have access to the SDcard. I couldn't mount it.
Is there a way to write a file or put a rom on the SDCard?
of course the SDCARD is build-in so yea....
Please help~!!!
i could be wrong, but if you can get to fastboot, cant you flash via RUU? i mean its obviously not a custom rom, but a hell of a lot better than a brick.
most RUU is exe file...
I can flash a stock rom. but I need a .zip rom.
I tried using the one of the custom rom. but it says something about a .txt file missing.
Right, RUUs are exe files intended to be flashed via windows. I thought that you could plug your phone in when in fastboot mode, or maybe its after you select bootloader, and then run the RUU and it would flash the phone. Is that not the case? Those are just my thoughts so i could be wrong. This is my first real HTC experience so i may be way off base.
boot into recovey
flash use.adb
adb push rom.zip /sdcard/rom.zip
Sent from my Galaxy Nexus using XDA
niceppl said:
boot into recovey
flash use.adb
adb push rom.zip /sdcard/rom.zip
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
When u say boot into recovery do you mean CWM?
sorry i am so new this
I have try using ADB to push it.
But seems like without an OS already install... and WHEN I AM IN CWM, ADB doesn't recognize the phone.
The only thing that seem to recognize the phone is FAstboot,
jzhang0818 said:
I have try using ADB to push it.
But seems like without an OS already install... and WHEN I AM IN CWM, ADB doesn't recognize the phone.
The only thing that seem to recognize the phone is FAstboot,
Click to expand...
Click to collapse
flash this cwm
http://forum.xda-developers.com/showthread.php?t=1677304
if you are on windows, make sure you have the adb driver installed for the phone...check the device manager...make sure it's not a question mark
I have flashed the new CWM you gave me.
ADB works now.
but the weird thing is. Afert i did
adb push rom.zip /sdcard/rom.zip
I reboot to recovery
and try using install zip from sdcard. There was no file in it.
I am not sure what went wrong.
Please HELP.
I am using a MAC...
jzhang0818 said:
I have flashed the new CWM you gave me.
ADB works now.
but the weird thing is. Afert i did
adb push rom.zip /sdcard/rom.zip
I reboot to recovery
and try using install zip from sdcard. There was no file in it.
I am not sure what went wrong.
Please HELP.
I am using a MAC...
Click to expand...
Click to collapse
...good mac
try this..
adb push rom.zip /sdcard/Download/rom.zip
or
adb push rom.zip /sdcard/download/rom.zip
IT all works now...
Thank you very much.
I learn so much from this error.
Thank you very very much
jzhang0818 said:
IT all works now...
Thank you very much.
I learn so much from this error.
Thank you very very much
Click to expand...
Click to collapse
nice..lol...
A very similar problem
Hi all,
I've gotten myself into a very similar problem, but the solution posted here hasn't fixed my issue.
I have an HTC One X 2.20 on AT&T. I used the X-Factor exploit to root my phone successfully. I have TWRP 2.3.1 recovery. I have a Mac.
While in TWRP recovery, I pressed "Factory Reset", "Wiped System", and wiped "External Storage." My phone now doesn't have an OS.
I tried the listed solution "adb push rom.zip /sdcard/Download/rom.zip" and the newly flashed ROM would be on my SDcard, but as soon as I rebooted, it would disappear. ALSO, when I tried to "Install" the ROM before rebooting, I get "Failed- unable to mount /sdcard".
Any advice on how to proceed?
Thanks so much!
ayhindot said:
While in TWRP recovery, I pressed "Factory Reset", "Wiped System", and wiped "External Storage." My phone now doesn't have an OS.
Click to expand...
Click to collapse
Well, wiping /system = wiping the OS, so that is logical.
Doing factory reset in recovery means you need to reformat your SD card before doing anything else.
ayhindot said:
Hi all,
I've gotten myself into a very similar problem, but the solution posted here hasn't fixed my issue.
I have an HTC One X 2.20 on AT&T. I used the X-Factor exploit to root my phone successfully. I have TWRP 2.3.1 recovery. I have a Mac.
While in TWRP recovery, I pressed "Factory Reset", "Wiped System", and wiped "External Storage." My phone now doesn't have an OS.
I tried the listed solution "adb push rom.zip /sdcard/Download/rom.zip" and the newly flashed ROM would be on my SDcard, but as soon as I rebooted, it would disappear. ALSO, when I tried to "Install" the ROM before rebooting, I get "Failed- unable to mount /sdcard".
Any advice on how to proceed?
Thanks so much!
Click to expand...
Click to collapse
Can you get into TWRP? If so, just mount the USB via TWRP and put the ROM on your SD card and install it.
pside15 said:
Can you get into TWRP? If so, just mount the USB via TWRP and put the ROM on your SD card and install it.
Click to expand...
Click to collapse
I'm having the same problem with no OS being installed and I am unable to get to either the bootloader or recovery. When rebooting I can't get past the HTC quietly brilliant splash screen. I've been using the tool here: http://forum.xda-developers.com/showthread.php?t=1952426 but it can't reach the phone. What are my options now?
ltjska04 said:
I'm having the same problem with no OS being installed and I am unable to get to either the bootloader or recovery. When rebooting I can't get past the HTC quietly brilliant splash screen. I've been using the tool here: http://forum.xda-developers.com/showthread.php?t=1952426 but it can't reach the phone. What are my options now?
Click to expand...
Click to collapse
Have you successfully unlocked your bootloader using that tool?
---------- Post added at 04:14 PM ---------- Previous post was at 04:08 PM ----------
ayhindot said:
Hi all,
I've gotten myself into a very similar problem, but the solution posted here hasn't fixed my issue.
I have an HTC One X 2.20 on AT&T. I used the X-Factor exploit to root my phone successfully. I have TWRP 2.3.1 recovery. I have a Mac.
While in TWRP recovery, I pressed "Factory Reset", "Wiped System", and wiped "External Storage." My phone now doesn't have an OS.
I tried the listed solution "adb push rom.zip /sdcard/Download/rom.zip" and the newly flashed ROM would be on my SDcard, but as soon as I rebooted, it would disappear. ALSO, when I tried to "Install" the ROM before rebooting, I get "Failed- unable to mount /sdcard".
Any advice on how to proceed?
Thanks so much!
Click to expand...
Click to collapse
I think you need to uncheck "Unmount sdcard" under "Mount" in TWRP recovery.
Tried everything... still not working
niceppl said:
nice..lol...
Click to expand...
Click to collapse
Hi, Brand new Noob here, but hoping someone can help…I’ve had a good scour around and can’t find the answer. We have a Htc one x from orange uk (cid orang001) stuck at “quietly brilliant” screen following an attempt to load ViperX 2.6.0. After downloading, the MAC unzipped the ROM so this was just rezipped back up and transferred over to the SD card, without any special conditions. ( I’ve since read somewhere that this might cause issues)
USB debugger was enabled but its not possible to enable it now.
Fastboot works ok, and we’ve flashed the boot ok, but ADP isn’t working, so it isn’t possible to push the correct ROM.ZIP to the SDcard. CWM is installed.
We’ve seen the post for an updated CWM with ADP enabled on this here but that states its only for at&t models. If we could get ADP working we’d be able to push the correct ROM over, so this would seem the easiest way if possible.
I wanted to avoid doing a RUU in case the phone would end up bricked, but I can’t get the correct version anyway.
Command ./fastboot getvar version-main returns
version-main: 3.16.61.6 and the noob guide at
http://forum.xda-developers.com/showthread.php?t=1859714 says we can’t use a lower version….the nearest RUU I can find is 1.29.061.11 (released on 31/01/2013).
Any ideas on how best to recover this phone? The issue might not be anything to do with the zipping of the ROM, but then I have no idea why its not working…I’m hoping it’s a simple procedure, but I fear it may not be! Please Help!
LiamKenny said:
Hi, Brand new Noob here, but hoping someone can help…I’ve had a good scour around and can’t find the answer. We have a Htc one x from orange uk (cid orang001) stuck at “quietly brilliant” screen following an attempt to load ViperX 2.6.0. After downloading, the MAC unzipped the ROM so this was just rezipped back up and transferred over to the SD card, without any special conditions. ( I’ve since read somewhere that this might cause issues)
USB debugger was enabled but its not possible to enable it now.
Fastboot works ok, and we’ve flashed the boot ok, but ADP isn’t working, so it isn’t possible to push the correct ROM.ZIP to the SDcard. CWM is installed.
We’ve seen the post for an updated CWM with ADP enabled on this here but that states its only for at&t models. If we could get ADP working we’d be able to push the correct ROM over, so this would seem the easiest way if possible.
I wanted to avoid doing a RUU in case the phone would end up bricked, but I can’t get the correct version anyway.
Command ./fastboot getvar version-main returns
version-main: 3.16.61.6 and the noob guide at
http://forum.xda-developers.com/showthread.php?t=1859714 says we can’t use a lower version….the nearest RUU I can find is 1.29.061.11 (released on 31/01/2013).
Any ideas on how best to recover this phone? The issue might not be anything to do with the zipping of the ROM, but then I have no idea why its not working…I’m hoping it’s a simple procedure, but I fear it may not be! Please Help!
Click to expand...
Click to collapse
Wrong forum. This is for the S4 One XL. You have a Tegra 3 One X. Anything you flash from here may brick your phone.
iElvis said:
Wrong forum. This is for the S4 One XL. You have a Tegra 3 One X. Anything you flash from here may brick your phone.
Click to expand...
Click to collapse
oops, sorry :/
Hi Everyone,
So i followed all the steps to temp root 2.20 including successfully installing TWRP (Team Win Recovery Project). I then downloaded the CM10 rom and extracted the boot.img as per posts and rebooted into the bootloader and flashed the boot.img from CM10 via Fastboot. However after doing then rebooting to Recovery mode in order to flash the ROM, i get stuck in the red text where it gives you a warning about it being in development mode or something.
I am able to successfully boot into the bootloader via Power+down volume. Additionally I am able to boot into the TWRP recovery just fine, however I am lost and have no clue how to restore my phone to either the CM10 ROM or most importantly at least to stock working condition.
When i got to mount the SDCARD via twrp normally i would get a pop up on my screen and allow me to access my SD card, now i get a pop up just telling me that i need to format my SD card first. I'm afraid some how my SD card got wiped or something.
Can someone please walk me through the steps on how to restore my phone. Please if possible i would appreciate using LAME terms as i do not have any experience as you can tell i screwed up :/ Can you please listed step by step instructions including commands for Fastboot/adb etc etc if needed. Thank you very much for your help and support.
I've typed and retyped a response to help. I'm so tired and my brain is mush. (More so than normal) if you can't find any resolution by morning? Pm me and I'll try and help. Something about pluggin the USB in The back of your pc something something....... snore
Sent from my One X using xda premium
subarudroid said:
I've typed and retyped a response to help. I'm so tired and my brain is mush. (More so than normal) if you can't find any resolution by morning? Pm me and I'll try and help. Something about pluggin the USB in The back of your pc something something....... snore
Sent from my One X using xda premium
Click to expand...
Click to collapse
I know you tried to help, but it appears now I have bricked the phone. Hopefully i can fix it as i still have access to Bootloader and TWRP recovery. I'll PM you in the morning, thank you.
dont factory reset in bootloader. only factory reset in twrp. sometimes evita has a hard time getting into recovery from bootloader. just keep trying to get into recovery from bootloader. also even if your phone doesn't boot all the way adb sometimes still works. so try "adb reboot recovery" while its trying to boot.
if you did corrupt your sdcard try this method to get it fixed without having to run ruu.
[How to] Fix corrupt/unmountable internal storage on the HTC One X/XL
when you get your sdcard fixed remember to wipe everything and then copy cm10 and gapps to your sdcard and flash. since boot.img is already flashed you shouldn't need to do it again.
you did flash boot.img as "fastboot flash boot boot.img"? i made the mistake of flashing boot.img to recovery instead of boot. i was freaking out. just to make sure flash recovery again "fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img"
DvineLord said:
dont factory reset in bootloader. only factory reset in twrp. sometimes evita has a hard time getting into recovery from bootloader. just keep trying to get into recovery from bootloader. also even if your phone doesn't boot all the way adb sometimes still works. so try "adb reboot recovery" while its trying to boot.
if you did corrupt your sdcard try this method to get it fixed without having to run ruu.
[How to] Fix corrupt/unmountable internal storage on the HTC One X/XL
when you get your sdcard fixed remember to wipe everything and then copy cm10 and gapps to your sdcard and flash. since boot.img is already flashed you shouldn't need to do it again.
you did flash boot.img as "fastboot flash boot boot.img"? i made the mistake of flashing boot.img to recovery instead of boot. i was freaking out. just to make sure flash recovery again "fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img"
Click to expand...
Click to collapse
Yes i did fastboot flash boot boot.img from within the Bootlader. FYI that boot.img was from inside the CM10 zip file. I belive my SD card is corrupt i will check out that link. FYI I am able to get into Recovery mode form the Boatloader if i chooser recovery. However since the SD card seems messed up i can't access it currently. Also I tried to use the method to install the CM10.zip file using TWRP recovery. That recovery has a GUI and you can click on the INSTALL button and choose the zip file you want to install, however it errors out.
What is the proper way to flash a rom when i am in the TWRP recovery? Can you provide me with the commands/steps? Thanks for all your support guys.
movadoevo8 said:
Yes i did fastboot flash boot boot.img from within the Bootlader. FYI that boot.img was from inside the CM10 zip file. I belive my SD card is corrupt i will check out that link. FYI I am able to get into Recovery mode form the Boatloader if i chooser recovery. However since the SD card seems messed up i can't access it currently. Also I tried to use the method to install the CM10.zip file using TWRP recovery. That recovery has a GUI and you can click on the INSTALL button and choose the zip file you want to install, however it errors out.
What is the proper way to flash a rom when i am in the TWRP recovery? Can you provide me with the commands/steps? Thanks for all your support guys.
Click to expand...
Click to collapse
install/install from zip/browse to your zip/slide to flash (they really should patent that)
now most of us, to do a clean flash, we'd go into the "wipe" menu in TWRP before flashing , factory reset, wipe cache, wipe dalvik cache, wipe system. then we flash our rom.
hope that cleared it up!
Sent from my One X using xda premium
You won't be able to flash anything until you fixed your sdcard using the method in that link.
Ptesmoke where have you been? DvineLord is the only one been helping here. The Q&A thread is a mess. where is edditsync chongo, rohan and the other superhero's. I feel like Hawkeye trying to shoot sh#@ down with a bow and arrow. Waiting for ironman, hulk, Thor and the other avengers to get real sh#@ done. I'm tired going to sleep now.
Sent from my One X using xda premium
ptesmoke said:
install/install from zip/browse to your zip/slide to flash (they really should patent that)
now most of us, to do a clean flash, we'd go into the "wipe" menu in TWRP before flashing , factory reset, wipe cache, wipe dalvik cache, wipe system. then we flash our rom.
hope that cleared it up!
Sent from my One X using xda premium
Click to expand...
Click to collapse
I tried to fixed corrupted SD card as per video. however after flashing the recovery.img via fastboot when it wants me to do a factory reset instead of doing the factory reset it just goes back to the HTC brilliant screen with the red warning text and sits there. If i go to twpr recovery and click on install i can't access me zip currently due to sd card issues.
Is there a way to format via PC since it lets me as long as I am in twpr and just put stock files/folders onto the SD card? Or is it possible to install the 2.20 ruu again? I re-downloaded it form HTC's site while I am in twrp however I cannot install it won't detect my phone. Thanks for your help.
"fastboot oem lock" then run ruu. ruu gets run in fastboot.
after the ruu, reunlock bootloader and flash twrp, copy cm10 and gapps to your sdcard, flash boot.img in fastboot, wipe everything except for external storage in twrp, flash cm10 and gapps in twrp, then reboot.
If you can get into twrp and go to mount, mount usb storage and connect your phone windows should prompt you to format the SD card.
Once that's done you can drag and drop the rom you want to flash then boot into fastboot and flash the boot.img.
If you want to run the ruu you need to relock the bootloader first.
To do that you must go into fastboot usb and then type fastboot oem lock.
Sent from my HTC One XL using xda premium
DvineLord said:
"fastboot oem lock" then run ruu. ruu gets run in fastboot.
after the ruu, reunlock bootloader and flash twrp, copy cm10 and gapps to your sdcard, flash boot.img in fastboot, wipe everything except for external storage in twrp, flash cm10 and gapps in twrp, then reboot.
Click to expand...
Click to collapse
I'm sorry i'm not too tech savy. Can you clarify how to Fastboot OEM lock. Assuming i just need to be in fastboot mode and run a command in command prompt?
Also once that is done how can i run RUU via fastboot? Right now i have HTC RUU for 2.20 from august that i downloaded from their site and not sure how i can have it detect my phone. If you could clarify and explain those steps in Lame terms i would greatly appreciate it, thanks in advance.
movadoevo8 said:
I'm sorry i'm not too tech savy. Can you clarify how to Fastboot OEM lock. Assuming i just need to be in fastboot mode and run a command in command prompt?
Also once that is done how can i run RUU via fastboot? Right now i have HTC RUU for 2.20 from august that i downloaded from their site and not sure how i can have it detect my phone. If you could clarify and explain those steps in Lame terms i would greatly appreciate it, thanks in advance.
Click to expand...
Click to collapse
That's the command you do and the ruu is an exe file so get into fastnoot on your phone from bl and run the ruu after you've locked the bootloader
Thank you both will try that now.
Hey guys thanks for all your help and your support it worked. I had the wrong CM10 file instead of Evita i had the other one :/ That was the issue all along ugh... but all resolved could of not have done it without your support. Thanks!! I can now finally go to bed.. been at it since 10pm, now 3:11am
Maybe you can help me . I'm having the same problem. The problem is, everytime I try to use any fastboot commands, it'll say "waiting for device". I'm stressing out.
marcur12 said:
Maybe you can help me . I'm having the same problem. The problem is, everytime I try to use any fastboot commands, it'll say "waiting for device". I'm stressing out.
Click to expand...
Click to collapse
Make sure you have the right drivers installed, download the latest htc sync from htc's website.
Install HTC sync connect phone and let the drivers install, then make sure you close htc sync from the system tray and try again.
Like DvineLord said below make sure you're in the bootloader then select Fastboot once selected it should say in red writing Fastboot USB.
fastboot only works in bootloader btw
Hit the thanks button for the people helping you fix your boo boos.
If you can type it, click it for them, least you can do in return.
WR
Sent from my HTC One X
Sent from my HTC One XL using Tapatalk 2
Okay I was flashing a ROM for the S4 version and the phone began rebooting in the middle of the flash. I realize my error so lets not focus on that Im just trying to fix the boot loop issue. Im trying to use fastboot to fix it but when the phone is connected to my windows 7 PC it makes the connected sound but the device cannot be found by fastboot and it is not shown in the sidebar tree. I cannot get into recovery the TRWP splash screen is displayed for 10 seconds then it goes to the HTC developers use only screen. Please help. Are there any options to repair the damage?
sideshow03 said:
Okay I was flashing a ROM for the S4 version and the phone began rebooting in the middle of the flash. I realize my error so lets not focus on that Im just trying to fix the boot loop issue. Im trying to use fastboot to fix it but when the phone is connected to my windows 7 PC it makes the connected sound but the device cannot be found by fastboot and it is not shown in the sidebar tree. I cannot get into recovery the TRWP splash screen is displayed for 10 seconds then it goes to the HTC developers use only screen. Please help. Are there any options to repair the damage?
Click to expand...
Click to collapse
Okay so can someone confirm then that I am out of luck on this one:?
sideshow03 said:
Okay so can someone confirm then that I am out of luck on this one:?
Click to expand...
Click to collapse
What is device manager showing when your phone is connected to pc while in bootloader (fastboot USB)
for example here is mine:
tivofool said:
What is device manager showing when your phone is connected to pc while in bootloader (fastboot USB)
for example here is mine:
Click to expand...
Click to collapse
It looks the same as yours. But Im not able to connect to the pc to transfer the ROM over. What do I need to do please and thank you?
sideshow03 said:
It looks the same as yours. But Im not able to connect to the pc to transfer the ROM over. What do I need to do please and thank you?
Click to expand...
Click to collapse
well don't give up then, it isn't bricked.
I'm guessing the way you worded it, you have a villeC2 (S3) version and you flashed (S4) ROM? So just make sure you have the S3 version of TWRP flashed and flash a boot.img and rom. wipe caches and you should be fine.
Never mind that if your phone is S4 and I misinterpreted that.
With phone in Bootloader, (fastboot USB) try and check fastboot devices again. Opening your folder with fastboot in it and shift right click, pick open command window.
fastboot devices
(should show a serial #)
flash recovery again, since it was bootlooping. That will probably allow it to be stable again so you can mount USB storage.
If you are in bootloader (fastboot USB) and command window on pc is ran from the correct folder but it still shows device cannot be found then reinstall fastboot drivers. That should fix it for you.
tivofool said:
well don't give up then, it isn't bricked.
I'm guessing the way you worded it, you have a villeC2 (S3) version and you flashed (S4) ROM? So just make sure you have the S3 version of TWRP flashed and flash a boot.img and rom. wipe caches and you should be fine.
Never mind that if your phone is S4 and I misinterpreted that.
With phone in Bootloader, (fastboot USB) try and check fastboot devices again. Opening your folder with fastboot in it and shift right click, pick open command window.
fastboot devices
(should show a serial #)
flash recovery again, since it was bootlooping. That will probably allow it to be stable again so you can mount USB storage.
If you are in bootloader (fastboot USB) and command window on pc is ran from the correct folder but it still shows device cannot be found then reinstall fastboot drivers. That should fix it for you.
Click to expand...
Click to collapse
Im on the S4 variant my error was not flashing the boot.img separately
Im needing to run the cmd as admin so Im opening it up from the start button and changing the directory to the folder fastboot is in. I did get a serial # HT251W408295 fastboot. as shown
Just to confirm my next step is to flash recovery so my command line should be C:\Android fastboot flash recovery twrp2.1.6-ville.img
Correct?
Im using an older twrp cause I read that the newest one is not the best for HTC one S devices.
Thanks
sideshow03 said:
Im on the S4 variant my error was not flashing the boot.img separately
Im needing to run the cmd as admin so Im opening it up from the start button and changing the directory to the folder fastboot is in. I did get a serial # HT251W408295 fastboot. as shown
Just to confirm my next step is to flash recovery so my command line should be C:\Android fastboot flash recovery twrp2.1.6-ville.img
Correct?
Im using an older twrp cause I read that the newest one is not the best for HTC one S devices.
Thanks
Click to expand...
Click to collapse
That would work, BUT:
I see Maximus HD in that pic. For Maximus and any other ROM that uses 2.16 HBoot you can only use the recovery provided in the Maximus original post. It has been modified to work with the new partitions.
If you have moved back to or are still on HBoot 2.15 older firmware, then yes go ahead and flash like you are.
---------- Post added at 07:07 PM ---------- Previous post was at 07:04 PM ----------
oh, and usb storage (mount sd card) will not be available on this new recovery.
Easy way to move a ROM onto the phone while in this recovery is adb push
put ROM.zip in the adb folder and type in command window:
adb push filename.zip /sdcard
tivofool said:
That would work, BUT:
I see Maximus HD in that pic. For Maximus and any other ROM that uses 2.16 HBoot you can only use the recovery provided in the Maximus original post. It has been modified to work with the new partitions.
If you have moved back to or are still on HBoot 2.15 older firmware, then yes go ahead and flash like you are.
---------- Post added at 07:07 PM ---------- Previous post was at 07:04 PM ----------
oh, and usb storage (mount sd card) will not be available on this new recovery.
Easy way to move a ROM onto the phone while in this recovery is adb push
put ROM.zip in the adb folder and type in command window:
adb push filename.zip /sdcard
Click to expand...
Click to collapse
Ok I have both packages now but when I try to flash twrp is shows FAILED (remote: image error! (BootMagic check fail)).
I have verified the md5 with HASHCALC.
Im lost but feel like Im getting somewhere
sideshow03 said:
Ok I have both packages now but when I try to flash twrp is shows FAILED (remote: image error! (BootMagic check fail)).
I have verified the md5 with HASHCALC.
Im lost but feel like Im getting somewhere
Click to expand...
Click to collapse
Is your bootloader locked? Can't install recoveries with locked bootloader.
tivofool said:
Is your bootloader locked? Can't install recoveries with locked bootloader.
Click to expand...
Click to collapse
No I am Unlocked S-off CID 11111111
sideshow03 said:
No I am Unlocked S-off CID 11111111
Click to expand...
Click to collapse
Sorry, you need to extract that zip on your pc and put the recovery.img in your folder. Or I guess just extract it in that same folder you are using.
then depending on the name of the recovery.img flash that. But I think that extracts to recovery.img
so
fastboot flash recovery recovery.img
tivofool said:
Sorry, you need to extract that zip on your pc and put the recovery.img in your folder. Or I guess just extract it in that same folder you are using.
then depending on the name of the recovery.img flash that. But I think that extracts to recovery.img
so
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Ok Ive completed that and the phone went into recovery, i can see the ROM when I click on the install tab. But when I trying to install the ROM i get E: Unable to open zip file Error flashing zip
sideshow03 said:
Ok Ive completed that and the phone went into recovery, i can see the ROM when I click on the install tab. But when I trying to install the ROM i get E: Unable to open zip file Error flashing zip
Click to expand...
Click to collapse
One of the possibilities with that error is a bad download. You may have to redownload the ROM.
Another is if you change the name of the rom, just in case you did that.
Solved
tivofool said:
One of the possibilities with that error is a bad download. You may have to redownload the ROM.
Another is if you change the name of the rom, just in case you did that.
Click to expand...
Click to collapse
Yes it was a bad download. Thanks for all of your help I really appreciate your time to help me get back up and running. :victory: