Hi Trev here,I am a New member and hope this is posted in the correct place,I have a HTC ONE S S3 Version chip,No SD card version,has OPTUS AU Firmware on it with CID OPTUS_001,My system stopped booting when i tried to get Nova 3 game working,at the moment its not compatible for my device,but i read on the forums if i edited my Build prop I could get it working again,but sadly enough,it stopped booting the OS and i can sometimes get into the boot loader,Now the only way i can see to fix this is to get the original optus ruu and flash it but i cant find it any where,and i cannot install any of the other stock s3 roms because i don't have super CID,do you guys have any ideas,cheers Trev.
Do you know exatcly what you have changed in build.prop? You could try to boot your phone into bootloader. Adn than try to access it with adb shell. Pull the build.prop, change it back the way it was, and push it back on the phone, replacing the not working one. This might work.
+1 to the above, and if you can't remember your edits maybe grab a build.prop from one of those S3 roms. Also are you sure you can't get supercid on your phone just because it doesn't boot, are there even steps needing to be done while booted?
adb shell
qzem said:
Do you know exatcly what you have changed in build.prop? You could try to boot your phone into bootloader. Adn than try to access it with adb shell. Pull the build.prop, change it back the way it was, and push it back on the phone, replacing the not working one. This might work.
Click to expand...
Click to collapse
Thanks for your reply,how do i change the build prop through adb shell,cheers.
build prop from one s s3 ruu
frdd said:
+1 to the above, and if you can't remember your edits maybe grab a build.prop from one of those S3 roms. Also are you sure you can't get supercid on your phone just because it doesn't boot, are there even steps needing to be done while booted?
Click to expand...
Click to collapse
how do i get the build prop from RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.110_Radio_16.12.20.02U_16.05.20.16_M2_release_263510_signed as i dont know how to access the file within the ruu,cheers.
trevor3737 said:
Thanks for your reply,how do i change the build prop through adb shell,cheers.
Click to expand...
Click to collapse
Code:
adb pull /system/build.prop c:\wherever
edit build.prop
adb remount
adb push c:\wherever\build.prop /system/
adb reboot
trevor3737 said:
how do i get the build prop from RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.110_Radio_16.12.20.02U_16.05.20.16_M2_release_263510_signed as i dont know how to access the file within the ruu,cheers.
Click to expand...
Click to collapse
You have to be on Windows to run RUU, if you are just click it and let it run for a while. It'll make a zip file in a new random-named folder, similar to c:\users\username\{*******-*******-*******-*******-*****}\rom.zip check here for build.prop
re build prop
frdd said:
Code:
adb pull /system/build.prop c:\wherever
edit build.prop
adb remount
adb push c:\wherever\build.prop /system/
adb reboot
You have to be on Windows to run RUU, if you are just click it and let it run for a while. It'll make a zip file in a new random-named folder, similar to c:\users\username\{*******-*******-*******-*******-*****}\rom.zip check here for build.prop
Click to expand...
Click to collapse
Does the phone have to be connected in fastboot while the ruu is running to find the zip file,because i started the ruu up without the phone connected and i cannot find the zip file,so i can look at the build.prop,cheers.
trevor3737 said:
Does the phone have to be connected in fastboot while the ruu is running to find the zip file,because i started the ruu up without the phone connected and i cannot find the zip file,so i can look at the build.prop,cheers.
Click to expand...
Click to collapse
You just try the first method with pulling and pushing. It is to complicated to extract build.prop from ruu.
re adb pull
qzem said:
You just try the first method with pulling and pushing. It is to complicated to extract build.prop from ruu.
Click to expand...
Click to collapse
is where ever the place i send the build prop to,and when i run adb it say device not found,cheers.
Go into recovery hopefully adb will work there, if not you're limited to fast boot commands. You have to be in bootloader for fastboot to work, it'll say fastboot USB on screen if cable is plugged in. Maybe you have to have phone connected for RUU to run, and also click a few times until the "View readme" button appears until the zip is extracted to the temp dir. When I wrote wherever I mean anywhere you want the stuff
re
frdd said:
Go into recovery hopefully adb will work there, if not you're limited to fast boot commands. You have to be in bootloader for fastboot to work, it'll say fastboot USB on screen if cable is plugged in. Maybe you have to have phone connected for RUU to run, and also click a few times until the "View readme" button appears until the zip is extracted to the temp dir. When I wrote wherever I mean anywhere you want the stuff
Click to expand...
Click to collapse
Hi thanks for your time on this,i am so frustrated with this,When i go into recovery,i get the white screen with the Htc logo,Quietly brilliant logo and red writing about being used by developers,and it stays on there and nothing else happens,I did flash try a recovery Team Win Recovery Project but i found out it was for s4 devices only so i bet that screwed my recovery up,I am limited to fast boot commands,I suppose i will have to wait till a recovery comes out for the one s s3 chip or i find the correct optus ics branded ruu.
trevor3737 said:
Hi thanks for your time on this,i am so frustrated with this,When i go into recovery,i get the white screen with the Htc logo,Quietly brilliant logo and red writing about being used by developers,and it stays on there and nothing else happens,I did flash try a recovery Team Win Recovery Project but i found out it was for s4 devices only so i bet that screwed my recovery up,I am limited to fast boot commands,I suppose i will have to wait till a recovery comes out for the one s s3 chip or i find the correct optus ics branded ruu.
Click to expand...
Click to collapse
Hmm tricky one this...
Just so we're talking about the same things, this is what the bootloader looks like:http://www.geeky-gadgets.com/wp-content/uploads/2012/05/bootloader-unlock-htc-one.jpg
I have no idea how the HTC recovery looks, flashed CWM in a heartbeat on my VilleU...
You have read the "The Ville C (HTC One S with S3 chips) and development" thread I guess? Some guys there apparantly flashed S4 recovery and got boot issues that were fixed. check on page 5 http://forum.xda-developers.com/showthread.php?t=1719911&highlight=ruu+help&page=5
Have you unlocked the bootloader via htcdev.com? I guess so since you flashed that S4 recovery... I dont think you need more than fastboot access to do it anyways IIRC. http://htcdev.com/bootloader/preview_unlock_process
If you have, you could try paulobriens boot.img that roots your S3 device, which is neat and all but more importantly it might perhaps hopefully maybe god willing if Cthulu allows it let your phone boot once and that time it'll have insecure adb access...
http://www.modaco.com/topic/355509-testing-villec-superboot/
Also I havent run an RUU myself for a long time so dont remember if you have to be on stock recovery but I think you have to relock your bootloader, this can be done in fastboot. I think you can run any RUU no matter what CID you have, but also you have to have phone running, or else flash it in stock recovery somehow...
re recovery
frdd said:
Hmm tricky one this...
Just so we're talking about the same things, this is what the bootloader looks like:http://www.geeky-gadgets.com/wp-content/uploads/2012/05/bootloader-unlock-htc-one.jpg
I have no idea how the HTC recovery looks, flashed CWM in a heartbeat on my VilleU...
You have read the "The Ville C (HTC One S with S3 chips) and development" thread I guess? Some guys there apparantly flashed S4 recovery and got boot issues that were fixed. check on page 5 http://forum.xda-developers.com/showthread.php?t=1719911&highlight=ruu+help&page=5
Have you unlocked the bootloader via htcdev.com? I guess so since you flashed that S4 recovery... I dont think you need more than fastboot access to do it anyways IIRC. http://htcdev.com/bootloader/preview_unlock_process
If you have, you could try paulobriens boot.img that roots your S3 device, which is neat and all but more importantly it might perhaps hopefully maybe god willing if Cthulu allows it let your phone boot once and that time it'll have insecure adb access...
http://www.modaco.com/topic/355509-testing-villec-superboot/
Also I havent run an RUU myself for a long time so dont remember if you have to be on stock recovery but I think you have to relock your bootloader, this can be done in fastboot. I think you can run any RUU no matter what CID you have, but also you have to have phone running, or else flash it in stock recovery somehow...
Click to expand...
Click to collapse
I have uploaded a pic of the boot loader,i have root access via pauls super boot,boot loader is unlocked and i know how to re lock if i have to ,cheers.
trevor3737 said:
When i go into recovery,i get the white screen with the Htc logo,Quietly brilliant logo and red writing about being used by developers
Click to expand...
Click to collapse
Are you sure this is when you go into recovery? Thats how it looks when trying to boot, and where the phone gets stuck when your boot.img is f-d up or you flash a new ROM and forgot/failed to flash boot.img or TWRP randomly fails to do this for you... try
Code:
fastboot boot boot.img
(replace boot.img with actual filename), you must be in the directory on PC where you have downloaded a boot.img for the VilleC2, or use the one I linked before from paulobrien, just extract the boot.superboot.img from the superboot.zip. This is of course the same thing as just running install-superboot-windows.bat now that I think about it, duh time for coffee here it seems. Good luck!
(you could also just send it in for service to HTC, and not take unnecessary risks with your expensive new hardware... root what? Whats a recovery? Fix my iphone damnit I just bought it and its already broken??)
---------- Post added at 05:20 PM ---------- Previous post was at 05:16 PM ----------
Yup thats a bootloader Maybe try pauls again, did it boot normally last time you ran it?
re recovery
[/ATTACH]
frdd said:
Are you sure this is when you go into recovery? Thats how it looks when trying to boot, and where the phone gets stuck when your boot.img is f-d up or you flash a new ROM and forgot/failed to flash boot.img or TWRP randomly fails to do this for you... try
Code:
fastboot boot boot.img
(replace boot.img with actual filename), you must be in the directory on PC where you have downloaded a boot.img for the VilleC2, or use the one I linked before from paulobrien, just extract the boot.superboot.img from the superboot.zip. This is of course the same thing as just running install-superboot-windows.bat now that I think about it, duh time for coffee here it seems. Good luck!
(you could also just send it in for service to HTC, and not take unnecessary risks with your expensive new hardware... root what? Whats a recovery? Fix my iphone damnit I just bought it and its already broken??)
---------- Post added at 05:20 PM ---------- Previous post was at 05:16 PM ----------
Yup thats a bootloader Maybe try pauls again, did it boot normally last time you ran it?
Click to expand...
Click to collapse
thats what happens when i hit recovery from the bootloader screen.
that is because you flashed wrong recovery. Here in this rar file it is original stock recovery for your phone (ignore othere files). Flash recovery_signed.img one just like you did twrp! And the attached build.prop from my HTC One S (S3), if it is any help. Juste remove the .txt ant the endo of build.prop. I had to add it to make it "valid" upload file.
re flash recovery
qzem said:
that is because you flashed wrong recovery. Here in this rar file it is original stock recovery for your phone (ignore othere files). Flash recovery_signed.img one just like you did twrp! And the attached build.prop from my HTC One S (S3), if it is any help. Juste remove the .txt ant the endo of build.prop. I had to add it to make it "valid" upload file.
Click to expand...
Click to collapse
it says remote not allowed
re
trevor3737 said:
it says remote not allowed
Click to expand...
Click to collapse
C:\Android>fastboot boot recovery_signed.img
creating boot image...
creating boot image - 6103040 bytes
downloading 'boot.img'...
OKAY [ 1.188s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.188s
Try fastboot flash recovery recovery-signed.img instead if you want to flash new recovery, fastboot boot will just boot from the image assuming its a boot.img with a ramdisk and kernel inside it
re flash recovery
frdd said:
Try fastboot flash recovery recovery-signed.img instead if you want to flash new recovery, fastboot boot will just boot from the image assuming its a boot.img with a ramdisk and kernel inside it
Click to expand...
Click to collapse
C:\Android>fastboot boot recovery_signed.img
creating boot image...
creating boot image - 6103040 bytes
downloading 'boot.img'...
OKAY [ 1.172s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 1.188s
C:\Android>fastboot flash recovery recovery-signed.img
error: cannot load 'recovery-signed.img'
the fastboot boot recovery_signed.img way and the fastboot flash recovery recovery-signed.img way
Related
I attempted to place a ROM on the phone using CWM recovery and something messed up. Now, I can boot into screen that says fastboot, recovery, etc. However, when I select recovery, nothing happens. Anyone point me in the right direction...im back to using my Blackberry!
From fastboot try and reflash recovery I would highly suggest twrp over cwm since twrp officially supports the one x.
Sent from my Nocturnalized Beast
E.Cadro said:
From fastboot try and reflash recovery I would highly suggest twrp over cwm since twrp officially supports the one x.
Sent from my Nocturnalized Beast
Click to expand...
Click to collapse
This is where I am stuck. Unfortunately, I'm not all that familiar with Fastboot. When connecting the phone to the PC with a USB, I see that the phone says Fatboot USB. From there I'm lost. I've not been able to find a guide that describes how to install a ROM using fastboot. Lots of posts says that it can be done, but none describing how its done. Anyone pointing me in the right direction?
http://forum.xda-developers.com/showthread.php?t=1754018
gunnyman said:
http://forum.xda-developers.com/showthread.php?t=1754018
Click to expand...
Click to collapse
Im still having difficulty loading a recovery via fastboot...
I get to the point where I enter the following line in command prompt...fastboot flash recovery twrp.img and the response I get is "error: cannot load 'twrp.img"
Any suggestions?
rpritch said:
Im still having difficulty loading a recovery via fastboot...
I get to the point where I enter the following line in command prompt...fastboot flash recovery twrp.img and the response I get is "error: cannot load 'twrp.img"
Any suggestions?
Click to expand...
Click to collapse
My Bad...didnt have the img file in the platform-tools folder.
So I've tried flashing the TRWP img and when I reboot into recover, I get the blue and black Teamwin splash screen. then it reboots and stays permanently on the HTC splash screen.
After I flash the clockwork img file and reboot into recovery, it reboots and stays permanetly on the HTC splash screen.
Any suggestions?
rpritch said:
My Bad...didnt have the img file in the platform-tools folder.
So I've tried flashing the TRWP img and when I reboot into recover, I get the blue and black Teamwin splash screen. then it reboots and stays permanently on the HTC splash screen.
After I flash the clockwork img file and reboot into recovery, it reboots and stays permanetly on the HTC splash screen.
Any suggestions?
Click to expand...
Click to collapse
I am having this same exact issue! Did you figure it out? I installed TWRP as well and now get the Teamwin screen before it reboots the the HTC screen with the legal disclaimer. Please help1
veritas2884 said:
I am having this same exact issue! Did you figure it out? I installed TWRP as well and now get the Teamwin screen before it reboots the the HTC screen with the legal disclaimer. Please help1
Click to expand...
Click to collapse
Sounds like a bad flash or corrupt recovery inage. Go to the play store and download goo manager and install twrp from goo manager instead. See if that fixes the problem.
Sent from my Nocturnalized Beast
E.Cadro said:
Sounds like a bad flash or corrupt recovery inage. Go to the play store and download goo manager and install twrp from goo manager instead. See if that fixes the problem.
Sent from my Nocturnalized Beast
Click to expand...
Click to collapse
Our devices will not boot. All we can get is either the white HTC Screen or get into the menu that allows fastboot/recover/ect...
Relock bootloader, run real stock ruu for your carrier, reunlock, reroot, reflash recovery. Flash your desired Rom. You will lose all data on phone!
Sent from my HTC One XL using xda app-developers app
c5satellite2 said:
Relock bootloader, run real stock ruu for your carrier, reunlock, reroot, reflash recovery. Flash your desired Rom. You will lose all data on phone!
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
That is what I am doing now. I did not relock the boot loader first it is in the process of running the RUU. Did I just fry my phone even more?
---------- Post added at 04:04 AM ---------- Previous post was at 03:56 AM ----------
Thanks c5satellite2 ,
For my AT&T One X I fixed it as you stated
Booted into fastboot
Used command window to relock bootloader:
fastboot devices <enter>
fastboot oem lock <enter>
Restarted and rebooted into fastboot again
Ran Stock Rom RUU Program from http://forum.xda-developers.com/showthread.php?t=1649658
Put me back to a working stock phone.
Re-rooted and re-unlocked bootloader
Installed TWRP this time! Thanks for the help! :good:
Recommended process for fixing strange issues like what you were experiencing. Glad it helped you guys out!
Sent from my HTC One XL using xda app-developers app
veritas2884 said:
That is what I am doing now. I did not relock the boot loader first it is in the process of running the RUU. Did I just fry my phone even more?
---------- Post added at 04:04 AM ---------- Previous post was at 03:56 AM ----------
Thanks c5satellite2 ,
For my AT&T One X I fixed it as you stated
Booted into fastboot
Used command window to relock bootloader:
fastboot devices <enter>
fastboot oem lock <enter>
Restarted and rebooted into fastboot again
Ran Stock Rom RUU Program from http://forum.xda-developers.com/showthread.php?t=1649658
Put me back to a working stock phone.
Re-rooted and re-unlocked bootloader
Installed TWRP this time! Thanks for the help! :good:
Click to expand...
Click to collapse
How exactly did you do this part "Ran Stock Rom RUU Program from http://forum.xda-developers.com/show....php?t=1649658"? What command did you use?
rpritch said:
How exactly did you do this part "Ran Stock Rom RUU Program from http://forum.xda-developers.com/show....php?t=1649658"? What command did you use?
Click to expand...
Click to collapse
It's just an exe. Boot your phone into fastboot mode. Your computer will recognize that it is plugged in in fast boot mode if you have the HTC driver installed. Then open the exe on your computer and follow the instructions on the screen. It will take about 15 mins for the whole process and your phone will reboot several times.
Also make sure you use twrp recovery instead of clockwork if you re-root!
veritas2884 said:
It's just an exe. Boot your phone into fastboot mode. Your computer will recognize that it is plugged in in fast boot mode if you have the HTC driver installed. Then open the exe on your computer and follow the instructions on the screen. It will take about 15 mins for the whole process and your phone will reboot several times.
Also make sure you use twrp recovery instead of clockwork if you re-root!
Click to expand...
Click to collapse
I cant seem to find a stock Rogers Ruu...will continue searching. Anyone out there have it?
http://http://forum.xda-developers.com/showthread.php?p=27882810#post27882810
Finally got it working...the above link is what worked. Here is the summary...
I was having this same problem and it took a while before I could get it to work. Try opening a command window in the same location of your adb tools.
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
Hopefully this helps you out!
Berserk87 said:
I'm stock right now (rooted) , but the updates keep failing, so i want to reflash stock rom.
I'm lost as to how to do this.
I downloaded ARUwizard and the stock rogers rom (PJ83IMG) but its still failing. I dont get all this adb tools stuff.
Click to expand...
Click to collapse
do this:
1.Put Rogers stock zip (keep it in zip form) in your platform-tools folder (you need to download Android SDK). This is the rogers file I downloaded...http://rapidlibrary.com/files/pj83i...elease-254934-signed-zip_ulc8eyefx8i89on.html
2. Boot phone into fastboot (hold power button and volume down key)
3. Used command window to relock bootloader by doing the following:
use command window to get to location on your computer where you have saved SDK stuff, continue with command window to the platform-tools folder then enter the following commands:
fastboot devices <enter>
fastboot oem lock <enter>
Phone will restart and reboot into fastboot again
4. type 'fastboot oem rebootRUU'.
5. Next, make sure you have the .zip RUU file in the same folder (see step 1) and type 'fastboot flash zip XXX.zip' (replace XXX with whatever the rogers stock zip is called, I changed it to "rogersstock.zip")
Phone will reboot to a HTC screen. If you see "re-flush image immediately", repeat fastboot flash zip XXX.zip command. You may have to do this 2 or 3 times.
After doing this, I was able to download and install the Rogers firmware update
BTW...I didn't discover any of this stuff on my own...I researched a bunch of different posts and put it together. Hopefully, someone else finds have all this in one post useful.
Hey guys, AT&T One X unlocked
I'm having a similar problem, been following the wiki exactly and when I flashed CWM recovery and it says it was successful:
F:\Users\Ryan\AppData\Local\Android\android-sdk\platform-tools>fastboot flash re
covery recovery-clockwork-touch-5.8.4.0-endeavoru.img
sending 'recovery' (5742 KB)...
OKAY [ 0.890s]
writing 'recovery'...
OKAY [ 1.480s]
finished. total time: 2.380s
When I select recovery it brings up the HTC logo and says in red text "This build is for development purposes only. Do not distribute without HTCs written permission... etc" after about 10 seconds the device boots up as normal.
Not sure what I'm doing wrong.
slash178 said:
Hey guys, AT&T One X unlocked
I'm having a similar problem, been following the wiki exactly and when I flashed CWM recovery and it says it was successful:
F:\Users\Ryan\AppData\Local\Android\android-sdk\platform-tools>fastboot flash re
covery recovery-clockwork-touch-5.8.4.0-endeavoru.img
sending 'recovery' (5742 KB)...
OKAY [ 0.890s]
writing 'recovery'...
OKAY [ 1.480s]
finished. total time: 2.380s
When I select recovery it brings up the HTC logo and says in red text "This build is for development purposes only. Do not distribute without HTCs written permission... etc" after about 10 seconds the device boots up as normal.
Not sure what I'm doing wrong.
Click to expand...
Click to collapse
What you are doing wrong is flashing the recovery for the wrong phone. Any file with "enveavoru" in it is for the international (Tegra3) version. Our phone is "evita".
Only install things in our Dev forum:
http://forum.xda-developers.com/forumdisplay.php?f=1541
To see everything in an organized list, go to my index: http://forum.xda-developers.com/showthread.php?t=1671237
Also, TWRP is recommended. CWM does not officially support our device, and therefore is just a port, and buggy. TWRP officially supports our device.
im getting the same error and im using the recovery ending on evita
Hello, all. I've spent the last four hours trying update my AT&T HTC One X running Android 4.1.1 to 4.2.2 and I failed hard!
First, I used the all-in-one toolkit to unlock my bootloader, flash clockwork recovery, and root the phone. The first guide I was following gave me error status 7 when I tried to flash the ROM so I wen to this guide:
update-htc-one-x-cm101-android-422-jelly-bean-custom-firmware/2/ (from team android website)
I got to the step below using the SDK I downloaded from dev.android.com and now my phone is dead! The HTC logo appears and then it goes to a black screen. Luckily, I can still reach my fastboot and clockwork recovery menu but nothing I try makes the phone boot.
Step 8 - Type the following command and press Enter.
fastboot flash boot boot.img
Step 9 - Then, type the following command and press Enter.
fastboot reboot
I just want my phone back to normal please! I don't care about rooting anymore. Thank you.
zenkix said:
Hello, all. I've spent the last four hours trying update my AT&T HTC One X running Android 4.1.1 to 4.2.2 and I failed hard!
First, I used the all-in-one toolkit to unlock my bootloader, flash clockwork recovery, and root the phone. The first guide I was following gave me error status 7 when I tried to flash the ROM so I wen to this guide:
update-htc-one-x-cm101-android-422-jelly-bean-custom-firmware/2/ (from team android website)
I got to the step below using the SDK I downloaded from dev.android.com and now my phone is dead! The HTC logo appears and then it goes to a black screen. Luckily, I can still reach my fastboot and clockwork recovery menu but nothing I try makes the phone boot.
Step 8 - Type the following command and press Enter.
fastboot flash boot boot.img
Step 9 - Then, type the following command and press Enter.
fastboot reboot
I just want my phone back to normal please! I don't care about rooting anymore. Thank you.
Click to expand...
Click to collapse
Alright, the ROMs you've been trying to flash are for the quad core One X... please stay in this forum and you should be good to go!
Any ROMs and kernels from here http://forum.xda-developers.com/forumdisplay.php?f=1541 and here http://forum.xda-developers.com/forumdisplay.php?f=1726. Try to flash something from there and report back (you'll still need to flash boot.img
RollTribe said:
Alright, the ROMs you've been trying to flash are for the quad core One X... please stay in this forum and you should be good to go!
Any ROMs and kernels from here http://forum.xda-developers.com/forumdisplay.php?f=1541 and here http://forum.xda-developers.com/forumdisplay.php?f=1726. Try to flash something from there and report back (you'll still need to flash boot.img
Click to expand...
Click to collapse
Thank you very much for your help? Could you please point me to a ROM to flash? I looked through those links and have no idea which to pick/what to do. It doesn't even have to be 4.2...I just want a working phone again. Thanks again!
zenkix said:
Thank you very much for your help? Could you please point me to a ROM to flash? I looked through those links and have no idea which to pick/what to do. It doesn't even have to be 4.2...I just want a working phone again. Thanks again!
Click to expand...
Click to collapse
Well... What would you like? Completely stock? Sense with tweaks? 4.2 with minor tweaks? 4.2 with a ton of tweaks?
RollTribe said:
Well... What would you like? Completely stock? Sense with tweaks? 4.2 with minor tweaks? 4.2 with a ton of tweaks?
Click to expand...
Click to collapse
4.2 with minor tweaks sounds great! Although right now I kinda just want to the stock "boot.img" to verify that my phone is still usable and not totally bricked.
zenkix said:
4.2 with minor tweaks sounds great! Although right now I kinda just want to the stock "boot.img" to verify that my phone is still usable and not totally bricked.
Click to expand...
Click to collapse
Alright then CM10.1 http://forum.xda-developers.com/showthread.php?t=2064621 and AOKP http://forum.xda-developers.com/showthread.php?t=2064724 will both suit you. These have the different boot.img than stock, but just extract and fastboot flash boot boot.img and you should be good to go!
RollTribe said:
Alright then CM10.1 http://forum.xda-developers.com/showthread.php?t=2064621 and AOKP http://forum.xda-developers.com/showthread.php?t=2064724 will both suit you. These have the different boot.img than stock, but just extract and fastboot flash boot boot.img and you should be good to go!
Click to expand...
Click to collapse
Quick update...I flashed boot.img of the first link (CynogenMod) and my phone got passed the "HTC Quietly Brilliant" screen! But now it seems stuck on HTC One (Beats Audio at the bottom) screen. I'll give it a few minutes...
I'm really worried that I did major damage to my phone in the bootloader and clockwork recovery menus. I literally tried every single option there trying to get my phone to boot earlier.
Oh man...it seems stuck. Maybe I should just flash the completely stock boot.img file. If that works, I will factory reset my phone just to make sure everything is back to how it was before.
Dude it sounds like you're trying to flash a cm boot.img with a Sense ROM, that ain't gonna work. You can't just extract a boot.img and flash it with a different ROM.
You need to extract the boot.img from the ROM you're about to flash, then flash that ROM, then flash the boot.img you just extracted.
Sent from my Evita
timmaaa said:
Dude it sounds like you're trying to flash a cm boot.img with a Sense ROM, that ain't gonna work. You can't just extract a boot.img and flash it with a different ROM.
You need to extract the boot.img from the ROM you're about to flash, then flash that ROM, then flash the boot.img you just extracted.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for your help man. If what you're saying is correct, does that mean my phone is hopeless? I deleted/wiped everything using the ClocworkMod Recovery menu. When I choose "install zip from sdcard" I get "E: Can't mount /sdcard/" and when I try to mount an sdcard I get "Error mounting /sdcard". I don't think I can flash any ROMs right now unless install zip from sideload is an option (I don't know how sideloading works).
Try using TWRP recovery instead, you'll find it here:
http://goo.im/devs/OpenRecovery/evita
Download it, check md5 is correct, then:
fastboot flash recovery filename.img
(Filename = exact TWRP recovery filename)
Then issue this command:
fastboot erase cache
Then:
fastboot reboot-bootloader
Now you should be able to select recovery on your phone screen and it should boot into TWRP. Next go to mount and mount usb storage. See if it comes up in Windows, it might need to be formatted from the sounds of it. If it doesn't show up as a usable drive, format it to fat32.
Once that's done you should be able to copy a ROM to your phone to flash. So copy it over, then extract the boot.img from the copy on your pc, then put the boot.img in your fastboot folder.
Do a full wipe in recovery (cache/dalvik/factory reset/system), then install the ROM, then reboot to bootloader, make sure phone is connected by usb, make sure fastboot usb comes up on your phone screen then issue the following command:
fastboot flash boot boot.img
Make sure it's the boot.img from the ROM you just flashed. Now once that's done you should be able to reboot into the ROM.
Sent from my Evita
timmaaa said:
Try using TWRP recovery instead, you'll find it here:
http://goo.im/devs/OpenRecovery/evita
Download it, check md5 is correct, then:
fastboot flash recovery filename.img
(Filename = exact TWRP recovery filename)
Then issue this command:
fastboot erase cache
Then:
fastboot reboot-bootloader
Now you should be able to select recovery on your phone screen and it should boot into TWRP. Next go to mount and mount usb storage. See if it comes up in Windows, it might need to be formatted from the sounds of it. If it doesn't show up as a usable drive, format it to fat32.
Once that's done you should be able to copy a ROM to your phone to flash. So copy it over, then extract the boot.img from the copy on your pc, then put the boot.img in your fastboot folder.
Do a full wipe in recovery (cache/dalvik/factory reset/system), then install the ROM, then reboot to bootloader, make sure phone is connected by usb, make sure fastboot usb comes up on your phone screen then issue the following command:
fastboot flash boot boot.img
Make sure it's the boot.img from the ROM you just flashed. Now once that's done you should be able to reboot into the ROM.
Sent from my Evita
Click to expand...
Click to collapse
This sounds like a good plan. I will give it a try tomorrow after work. Thank you guys for your help!
I couldn't sleep...so I followed your steps and my phone is now alive! Thank you!
I think now I need to flash GApps, right? I have this ---> gapps-jb-20130301-signed.zip
Any chance that's the wrong zip file? Do I need a special one for CM10.1?
That's the right gapps zip, it's the most recent one so yeah you're good to flash it.
And no problems, you're welcome
Sent from my Evita
Hi i have rooted and flashed the phone it got stuck on the htc screen so i tried factory reset bad idea now my phone will just go into the bootlader menu i can enable fastboot usb but it dont show up on computer but the computer makes a noise to say ive connected it i cant enable usb debugging because the phone wont come on i have tried to flash another boot img through fastboot with no luck im hoping its not bricked
please any help would be appreciated thanks
pl4yb0y78 said:
Hi i have rooted and flashed the phone it got stuck on the htc screen so i tried factory reset bad idea now my phone will just go into the bootlader menu i can enable fastboot usb but it dont show up on computer but the computer makes a noise to say ive connected it i cant enable usb debugging because the phone wont come on i have tried to flash another boot img through fastboot with no luck im hoping its not bricked
please any help would be appreciated thanks
Click to expand...
Click to collapse
Hmm. so you probably need to flash a recovery first.
then you will be able to use the recovery to mount usb and put a new rom on your "sd card"
Then you can flash the rom on your new recovery and don't forget to fastboot flash the boot.img.
edit: the all in one toolkit is great for things like this. It will put a new recovery on your phone with just a click of the button.
http://forum.xda-developers.com/showthread.php?t=1604677
tivofool said:
Hmm. so you probably need to flash a recovery first.
then you will be able to use the recovery to mount usb and put a new rom on your "sd card"
Then you can flash the rom on your new recovery and don't forget to fastboot flash the boot.img.
Click to expand...
Click to collapse
Thanks for the reply but i dont know how to do this ?
could you please explain it ?
pl4yb0y78 said:
Thanks for the reply but i dont know how to do this ?
could you please explain it ?
Click to expand...
Click to collapse
I just edited my original post. just in case you didn't know how. I guess I was a little slow.
Also I can't remember if a bootloader factory reset relocked your phone but you might want to check that too. up on top it would say locked or relocked. If it still says unlocked you don't have to do that step again. Like you did when you first rooted the phone.
(all in one tool kit is great for unlocking and relocking too) just put a copy of that bin file in all in one tool kit (data file i believe, but it says what to do in that thread)
tivofool said:
I just edited my original post. just in case you didn't know how. I guess I was a little slow.
Also I can't remember if a bootloader factory reset relocked your phone but you might want to check that too. up on top it would say locked or relocked. If it still says unlocked you don't have to do that step again. Like you did when you first rooted the phone.
(all in one tool kit is great for unlocking and relocking too) just put a copy of that bin file in all in one tool kit (data file i believe, but it says what to do in that thread)
Click to expand...
Click to collapse
hi i have got the tool kit run twrp s3 now i have a black htc logo screen on what next
pl4yb0y78 said:
hi i have got the tool kit run twrp s3 now i have a black htc logo screen on what next
Click to expand...
Click to collapse
Your phone is an s3?
My phone is an S4 as are I would guess the majority of users. I think the s3 is the international version. If you are on T mobile then it's a s4.
Ok,,,
so .... if your phone is an s3 version then you will have to check that the Rom you download is specific for your phone as most of the Roms on this site are for the s4 version.
you need to go to your recovery. press the volume down button and hold it. Then press the power button (don't hold it). That will get you to recovery.
when in twrp recovery you will see a mounts button. hit that then the next screen will have mount usb. then you will be able to move a rom you downloaded on your computer to your phone.
then you can install the rom zip in twrp.
then from your computer, I assume you know how to flash a boot.img
put a boot.img in your fastboot folder, open up a comand prompt.
fastboot flash boot boot.img
if you wanted a different recovery than you are using, find the download the recovery. *I would rename the recovery to recovery.img
fastboot flash recovery recovery.img
(I only mention a different recovery because in some of the Rom threads you might read that you can only install a particular rom with an older version of twrp.)
I'm not sure of your skill or experience with all of this. If you are very new to it (then you are probably really frustrated) have no fear there is a little bit to learn but not that much. Just keep reading the development thread and the guides in it.
tivofool said:
Your phone is an s3?
My phone is an S4 as are I would guess the majority of users. I think the s3 is the international version. If you are on T mobile then it's a s4.
Ok,,,
so .... if your phone is an s3 version then you will have to check that the Rom you download is specific for your phone as most of the Roms on this site are for the s4 version.
you need to go to your recovery. press the volume down button and hold it. Then press the power button (don't hold it). That will get you to recovery.
when in twrp recovery you will see a mounts button. hit that then the next screen will have mount usb. then you will be able to move a rom you downloaded on your computer to your phone.
then you can install the rom zip in twrp.
then from your computer, I assume you know how to flash a boot.img
put a boot.img in your fastboot folder, open up a comand prompt.
fastboot flash boot boot.img
if you wanted a different recovery than you are using, find the download the recovery. *I would rename the recovery to recovery.img
fastboot flash recovery recovery.img
(I only mention a different recovery because in some of the Rom threads you might read that you can only install a particular rom with an older version of twrp.)
I'm not sure of your skill or experience with all of this. If you are very new to it (then you are probably really frustrated) have no fear there is a little bit to learn but not that much. Just keep reading the development thread and the guides in it.
Click to expand...
Click to collapse
Thank you for the reply yes i am getting stressed at this and i am new had a break before i smashed the phone now ive just got to find out what my phone is s3 or s4 ? google will help
when i connect my phone to the computer in recovery or flashboot it does not let me see it so i can not put rom on the hdd
(tried restart phone no luck tried restart comy no luck, cant get it to show phone ) all drivers installed
can i use the tool kit to flash recovery ?
phone on orange uk ,is it a s4 ?
thanks for the help guys with your knowledge i will get it working i pray!
pl4yb0y78 said:
when i connect my phone to the computer in recovery or flashboot it does not let me see it so i can not put rom on the hdd
(tried restart phone no luck tried restart comy no luck, cant get it to show phone ) all drivers installed
can i use the tool kit to flash recovery ?
phone on orange uk ,is it a s4 ?
thanks for the help guys with your knowledge i will get it working i pray!
Click to expand...
Click to collapse
do you have your box the phone came in?
Z520e is S4
Z560e is S3
So were you able to put twrp on your phone? when you are in boot loader and click on the recovery does it take you to twrp? Yes the all in one toolkit will flash a recovery for you. but you have your boot loader unlocked first.
tivofool said:
do you have your box the phone came in?
Z520e is S4
Z560e is S3
So were you able to put twrp on your phone? when you are in boot loader and click on the recovery does it take you to twrp? Yes the all in one toolkit will flash a recovery for you. but you have your boot loader unlocked first.
Click to expand...
Click to collapse
yes i now have the twrp in recovery it says enter password and cancel i tried both it was the s4 one that worked so im guessing its an s4
what will the next step be? (if i need anything please could you leave a link)
thanks for all the help starting to feel i might win lol
in twrp when you press "mounts" then press "mount usb", does your computer finally see your phone?
I was looking at your first post, you say that you rooted and flashed your phone. What do you mean by that? Did you download a ROM and attempt to flash it? Or did you "fastboot flash boot boot.img"?
If you are able to access your phone via computer it is as simple as downloading a rom on your computer moving it to your phone then in twrp "install from zip". Then fastboot flash the boot.img.
http://forum.xda-developers.com/showthread.php?t=1583427
how to flash fastboot
http://forum.xda-developers.com/showthread.php?t=1752270
if you are just fed up and want your phone back to stock then you will need to run an RUU.
http://forum.xda-developers.com/showthread.php?t=2094414
To run a RUU you would need to relock your bootloader.
in console type "fastboot lock oem" or use your all in one toolkit to relock it.
if that fails you will need to put your stock recovery back. (you need to have boot loader unlocked to do this)
on the clockworkmod recovery page the stock recovery is the second download link.
http://www.modaco.com/topic/353006-...ch-recovery-for-the-htc-one-s-stock-download/
Ok i am now really confused nothing works downloaded recovery roms they wont install always says failed tried to adb sideload it after google it failed again tried 3 recovery roms all fail what is going wrong icant get it to work
so far ive put twrp on it pressed mount so i can put rom on phone worked
pressed install pressed zip failed
pressed adb sideload then start on comy sent rom 100% install failed
reeboot phone still no os
tried this 3 times different roms all failed
please help
pl4yb0y78 said:
Ok i am now really confused nothing works downloaded recovery roms they wont install always says failed tried to adb sideload it after google it failed again tried 3 recovery roms all fail what is going wrong icant get it to work
so far ive put twrp on it pressed mount so i can put rom on phone worked
pressed install pressed zip failed
pressed adb sideload then start on comy sent rom 100% install failed
reeboot phone still no os
tried this 3 times different roms all failed
please help
Click to expand...
Click to collapse
Do you know how to FASTBOOT FLASH boot.img which is present inside the ROM.ZIP?
Try wiping data, cache, dalvik. Then reinstall.
Sent from my Nexus 7 using Tapatalk HD
khan.orak said:
Do you know how to FASTBOOT FLASH boot.img which is present inside the ROM.ZIP?
Try wiping data, cache, dalvik. Then reinstall.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
thanks and yes i can do that i will try and get back to you
C:\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>fastboot boot boot.img
creating boot image...
creating boot image - 16779264 bytes
downloading 'boot.img'...
OKAY [ 1.890s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 1.926s
this is what i get when i try tried 3 imgs
pl4yb0y78 said:
C:\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>fastboot boot boot.img
creating boot image...
creating boot image - 16779264 bytes
downloading 'boot.img'...
OKAY [ 1.890s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 1.926s
this is what i get when i try tried 3 imgs
Click to expand...
Click to collapse
The command is:
Code:
fastboot flash boot boot.img
khan.orak said:
The command is:
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
ok i try this i am only learning but getting there lol
So I flash the stock rom on it without thinking and now it wont let me flash a recovery to the tablet threw fastboot or goomanager and it wont update throguh asus update but its booting fine and wont take any updates at all i need help being pointed in the right direction!
I flashed the wrong bootloader i think and how do i flash the correct bootloader without a recover?
in fastboot im getting the error: cannot load 'file name' :no error weather its cm or twrp it wont load it and i dont know what to do please help
First of all it would be important to know what bootloader you are actually on. You do not want to flash a recovery that is not compatible with your bootloader!
So boot into the bootloader with Volume Down and POWER and read the tiny script. From there select the Android with Volume Down and boot back to system with Volume Up.
And then please report in detail what you are trying to do in fastboot, which commands you use etc.
Without knowing what you are doing we cannot tell you what you are doing wrong.....
First step: In fastboot command: fastboot devices - Do you see the serial number of your tab?
berndblb said:
First of all it would be important to know what bootloader you are actually on. You do not want to flash a recovery that is not compatible with your bootloader!
So boot into the bootloader with Volume Down and POWER and read the tiny script. From there select the Android with Volume Down and boot back to system with Volume Up.
And then please report in detail what you are trying to do in fastboot, which commands you use etc.
Without knowing what you are doing we cannot tell you what you are doing wrong.....
First step: In fastboot command: fastboot devices - Do you see the serial number of your tab?
Click to expand...
Click to collapse
bootloader version is us_epad-10.4.4.20-20121026
with a stock rom of 4.1.1
and trying to undo the rom cause im trying to put a stock 4.2.2 on it to get the drivers back on it from the stock rom.
in fastboot i just need to get a twrp installed and i can undo my mess
Skittleskitty said:
bootloader version is us_epad-10.4.4.20-20121026
with a stock rom of 4.1.1
and trying to undo the rom cause im trying to put a stock 4.2.2 on it to get the drivers back on it from the stock rom.
in fastboot i just need to get a twrp installed and i can undo my mess
Click to expand...
Click to collapse
So you are on an ICS bootloader with a JB rom... How the hell did you manage to do that?
You did not answer my question about fastboot. What you tried and what did not work.
But anyway, how I would proceed, just to get you back into safe territory, is to download the latest Asus firmware 10.6.1.14.10, unzip the downloaded file once and copy the resulting zip to the root of your internal SD.
Reboot, and hopefully the stock recovery will recognize the update file and flash you to JB 4.2.1 (which BTW is the latest version for our tabs - there never was, and probably never will be a 4.2.2). Flashing the stock firmware will replace the bootloader.
So from there you just have to get fastboot working, flash the latest TWRP and then the custom rom of your choice COMPATIBLE with your bootloader and recovery.
If that doesn't work we have to try something else. But try this first and report.
berndblb said:
So you are on an ICS bootloader with a JB rom... How the hell did you manage to do that?
You did not answer my question about fastboot. What you tried and what did not work.
But anyway, how I would proceed, just to get you back into safe territory, is to download the latest Asus firmware 10.6.1.14.10, unzip the downloaded file once and copy the resulting zip to the root of your internal SD.
Reboot, and hopefully the stock recovery will recognize the update file and flash you to JB 4.2.1 (which BTW is the latest version for our tabs - there never was, and probably never will be a 4.2.2). Flashing the stock firmware will replace the bootloader.
So from there you just have to get fastboot working, flash the latest TWRP and then the custom rom of your choice COMPATIBLE with your bootloader and recovery.
If that doesn't work we have to try something else. But try this first and report.
Click to expand...
Click to collapse
thank you so much that fixed it!!
ok i did all that but it removed fastboot what do i do to get it back?
Skittleskitty said:
ok i did all that but it removed fastboot what do i do to get it back?
Click to expand...
Click to collapse
Read the text in the upper left corner - current bootloaders enable fastboot in the bootloader menu automatically.
ok i got fastboot working and now it says when i got to flash the recovery it says error cannot open twrp.blob even though its the correct file.
Skittleskitty said:
ok i got fastboot working and now it says when i got to flash the recovery it says error cannot open twrp.blob even though its the correct file.
Click to expand...
Click to collapse
Then maybe it's not in your current directory.
Skittleskitty said:
ok i got fastboot working and now it says when i got to flash the recovery it says error cannot open twrp.blob even though its the correct file.
Click to expand...
Click to collapse
I think your tablet would be a lot safer if you did some reading here: http://lmgtfy.com/?q=fastboot+tutorial
berndblb said:
I think your tablet would be a lot safer if you did some reading here: http://lmgtfy.com/?q=fastboot+tutorial
Click to expand...
Click to collapse
i found that and have been reading it but fastboot still cant read the twrp.blob even though its in the directory with fastboot.
ok ive re installed fastboot and adb sdk and did the environment variable path and it still wont recognize the blob it wont recognize cwm .img files ether and what does key driver not found..booting os
Skittleskitty said:
i found that and have been reading it but fastboot still cant read the twrp.blob even though its in the directory with fastboot.
Click to expand...
Click to collapse
It has to be in your *current* directory.
_that said:
It has to be in your *current* directory.
Click to expand...
Click to collapse
thankyou it moved directorys on me that was the issue
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: