This is long, but it's nice for noobs because it's detailed. It's honestly kind of fun, I promise. I'm assuming you have WINDOWS. This is based off of the guide by torxx!. It's modified because some of the info is outdated (you don't have to flash the boot.mg separately, for example). If you are NOT a noob you can just look at the "overview" for each step.
UNLOCKING YOUR DEVICE WILL WIPE YOUR DEVICE. THIS IS A SECURITY FEATURE. BACKUP FIRST.
Part 1- gaining unlock token
Overview: go to htcdev.com and unlock bootloader
Be sure you've turned off fast boot option in power menu; usb debugging should be on (settings -> developer options).
Go to http://www.htc.com/www/software/htc-sync-manager/[1] and install HTC SYNC. Alternatively, if you know what you're doing, you can install these drivers:
x86 http://www.mediafire.com/?qabo1tue2v1ky75 x64 http://www.mediafire.com/?8dl8s3l9mr6ggr9
Go on http://www.htcdev.com[4] and create yourself an account on HTCDEV.
Download these adb/fastboot files: http://d-h.st/RvD
Make a new folder anywhere. We'll use C:/fastboot as an example.
Extract the zip downloaded to the new folder
Go Here http://www.htcdev.com/bootloader/[6] and select "All Other Supported Models" and "then begin unlock bootloader" (check the boxes, click proceed, all that good stuff). YOU CAN IGNORE THE DIRECTIONS THAT THEY TELL YOU (and follow this guide instead).
Power off your phone. Power your phone on by holding power and volume down.
Highlight 'Fastboot' the volume buttons then press power to "select".
Plug your phone into your PC and open a Command Prompt. (windows XP - Click Start > Run > type CMD in box then press OK; Windows 7 - Click Start > type CMD in search box then press Enter) Change directory to your folder where we put fastboot files by typing cd c:\fastboot for example.*
*Alternatively, you can just hold down shift and right click in the folder and select "open command window here". Neat huh?
Type this into your command prompt window: fastboot oem get_identifier_token
Select & copy the text as per step 9 on the HTCDev website
Paste your identifier token into the box at the bottom and submit
You Will Very Shortly Receive an email from HTCDev with a link to the second part of the instructions and your "Unlock_code.bin" attached
Download the "Unlock_code.bin" from the email and save it to the same folder that we extracted fastboot files
Type this into your command prompt window: fastboot flash unlocktoken Unlock_code.bin
The Display Will change on your phone, press Vol+ to accept and power to confirm.
Part 2
Overview: flash your recovery. Boot into recovery. Turn phone off if it boots into OS. Boot into back into recovery. You're done!
Download a recovery:
TWRP (the one I use): http://forum.xda-developers.com/showthread.php?t=2173870
CWM 2: http://forum.xda-developers.com/showthread.php?t=2172979
CWM: http://forum.xda-developers.com/showthread.php?t=2173863
Place the Recovery file to the folder where the fastboot.exe is.
Same thing as above- boot (volume down + power) into the bootloader and highlight 'Fastboot' the volume buttons then press power to "select".
Do the same thing as with the command prompt above. This time, however, you'll be typing:
fastboot flash recovery "name_of_the_recovery.img"
For example:
fastboot flash recovery openrecovery-twrp-2.5.0.0-m7.img
then type:
fastboot erase cache
From the menu, boot into recovery (use volume to move up and down, power to select). The phone might boot to the OS instead of recovery, don't worry!
Turn off phone then turn on (while holding volume down) to boot back into the bootloader.
TAMPERED shows up, boot into recovery and now your recovery should be working!
Part 3- obtaining root
Overview: flash a super tool
Download a super user tool for root:
SuperSU (I use this one): http://forum.xda-developers.com/showthread.php?t=1538053
SuperUser: http://download.clockworkmod.com/superuser/superuser.zip
Alternatively, download this: http://forum.xda-developers.com/showthread.php?t=2252959. This is a stock rooted rom for ATT. If you download and flash this instead of the super user tool, you're done. (This rom includes super user) Or you can download a custom rom such as this one: http://forum.xda-developers.com/showthread.php?t=2183023
Turn on your phone again (and disable usb debugging) and connect to computer, copy the .zip super user tool to a location you remember ON the phone.
Flash it with the Recovery: Power off your device and then hold the VOL DOWN + Power to boot into the Bootloader Navigate with VOL and Power to Recovery Now flash the .zip:
- install zip from sdcard
- choose zip from sdcard
- select the downloaded SuperSU/SuperUser zip file and flash it
- Reboot now
You're not out of the woods yet! The stock kernel is system write protected, so you still can't modify it (changes won't "stick"). You'll have to flash a custom rom or a kernel if you want stock instead.
I recommend these kernels: http://forum.xda-developers.com/showthread.php?t=2255900 or http://forum.xda-developers.com/showthread.php?t=2233665&highlight=menu
Download it.
Installing custom rom/kernel ("flashing a rom")
Overview: Download Rom, boot into recovery and wipe and then flash.
According to Shenye, even though your device is s-on, you can still flash boot now. So just do this:
Turn on your phone again (and disable usb debugging) and connect to computer, copy the .zip kernel/cutom rom to a location you remember ON the phone.
Flash it with the Recovery: Power off your device and then hold the VOL DOWN + Power to boot into the Bootloader Navigate with VOL and Power to Recovery Now flash the .zip:
- install zip from sdcard
- choose zip from sdcard
- select the downloaded SuperSU/SuperUser zip file and flash it
- Reboot now
I feel like this title should be changed to clarify that it's unlocking the bootloader, not the SIM lock.
Just wanted to say this tutorial was 100% dead on and what I used to unlock bootloader and root/rom my One.
Oddity - Did everything, I've got root but I -AM- out of the woods. Was installing bulletproof mod through recovery but it kept failing due to missing a MD5 file or something -- Trying to work that out through that thread atm but anyway, rebooted the phone a couple of times now and I still have root, Tit back up works OR are we talking about things like CPU clocking won't work since it can't rewrite?
Sticking this.
Excellent tutorial. One thing to add:
If you flash the TWRP recovery you link to, after TWRP boots for the first time, if you reboot into System, TWRP will offer to install SuperSU for you; no need to find another to flash. Once the system reboots, you can launch the GUI installer to finish the SU install (it will boot into TWRP and back one more time to do the actual flash).
Does anyone know if this will work on the Rogers HTC One?
Thank you. Followed this last night. Worked flawlessly. The only thing that threw me was rebooting into recovery. It took maybe 3 or 4 reboots for it to say "TAMPERED" at the top. When it didn't say tampered, it would not boot to recovery.
TELUS?
DannySmurf said:
Excellent tutorial. One thing to add:
If you flash the TWRP recovery you link to, after TWRP boots for the first time, if you reboot into System, TWRP will offer to install SuperSU for you; no need to find another to flash. Once the system reboots, you can launch the GUI installer to finish the SU install (it will boot into TWRP and back one more time to do the actual flash).
Click to expand...
Click to collapse
Did you happen do run this tutorial on a TELUS device?
Viceroy_N said:
Does anyone know if this will work on the Rogers HTC One?
Click to expand...
Click to collapse
Yes it does. I have a Rogers phone, and it worked perfectly.
richnanaimo said:
Did you happen do run this tutorial on a TELUS device?
Click to expand...
Click to collapse
No, I have a Rogers device. But the procedure should not be any different.
followed step by step and got an error that says submitted token wrong length
I'm on ubuntu 13.04 and I get stuck at getting the token. I type in fastboot oem get unlock_identifier_token and it says waiting for device. Tried it with sudo and it says error and sudo ./fastboot and it says no such command.
Sent from my HTC One using xda app-developers app
Having a really odd problem. I flash the twrp recovery per instructions. I try to reboot to recovery and it seems to try and then, blam, the att boot.
I have tried this from the bootloader, selecting Recovery, as well as from a booted stated using "adb reboot recovery".
Any hints for me? I originally had a silver One and today got my Black One replacement,. Had no issues on the original one. Hmm. Guess I will try CWM.
FYI: Yes I unlocked the bootloader and it says Unlocked in there
-I also notice that I seem to go right into fastboot, when I boot the bootloader. Now, I believe that is normal if you have the usb cable attached, but this happens regardless.
-flashed stock recovery back and can get into it. trying twrp again, renaming the file to "recovery.img" just because...and it worked on that stock recovery file
-Also, very hard to get into bootloader from powered off state. I may flash RUU_M7_UL_JB_50_Cingular and see if it helps me.
OK, maybe it is the phone or ATT has done something screwy on the latest. I can not even get the RUU install to pass inspection. Wants me to check the connection. I know all my stuff is in order, as I did this all on the previous one. grrr
-Just noticed mine does say Unlocked but it does not say Tampered.
-Crazy. I decided to get a new Unlock token and redo the unlock with it. Now, the bootloader finally says Tampered and I got into TWRP. I have no idea why, since I would think that if the original Unlock token was incorrect, it would not have unlocked the phone.
So, rather than providing worthwhile information for anyone else having problems, I think this post is probably deletable and that is fine by me should the powers so decide.
How would one go back to locking the device for a return?!?
Sent from my Nexus 4 using xda premium
tacotino said:
How would one go back to locking the device for a return?!?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
fastboot oem lock
but, it will say relocked. nobody cares or seems to check. also, it will say tampered until you restore a stock ruu to flash. I used RUU_M7_UL_JB_50_Cingular.exe for mine when switching from silver to black. it is the right one for att. sorry, don't have the link to the download anymore.
great writeup! quick comment though, just helped my brother unlock his phone. i had a similar issue to @Barsky above so I decided to try to reflash the recovery. The first time I used the line fastboot erase cache after flashing the recovery and I think that's what caused it to not boot into recovery. The second time I flashed TWRP, I didn't enter that line and voila it worked on the first try!
can anyone post a mirror of the dev host files? devhost seems to be down.
nice...
help please
I seem to be stuck in recovery after installing super su/ rom. I messed up the order and did the rom then su. Any ideas on how I can get it to boot? I tried installing clean rom 2.5 and used the su file i found here ----> http://www.teamandroid.com/2013/03/17/root-htc-one-supersu-android-41-jelly-bean-tutorial/2/
any help is greatly appreciated... I just want my phone back
---------- Post added at 09:44 AM ---------- Previous post was at 09:36 AM ----------
also, i did hit factory reset under bootloader/fastboot screen (where it says tampered/unlocked),
mbroch89 said:
I seem to be stuck in recovery after installing super su/ rom. I messed up the order and did the rom then su. Any ideas on how I can get it to boot? I tried installing clean rom 2.5 and used the su file i found here ----> http://www.teamandroid.com/2013/03/17/root-htc-one-supersu-android-41-jelly-bean-tutorial/2/
any help is greatly appreciated... I just want my phone back
---------- Post added at 09:44 AM ---------- Previous post was at 09:36 AM ----------
also, i did hit factory reset under bootloader/fastboot screen (where it says tampered/unlocked),
Click to expand...
Click to collapse
I think the last bit was your problem. You can't factory reset from bootloader. Try to push twrp again in fastboot then load/flash clean romantic, then boot up. It already has root so you don't need to push su.
Sent from my HTC One X using xda app-developers app
Related
Preamble
This is the S-OFF upgrade from GingerBread to HoneyComb
Do not perform this procedure if you have the official HTC hboot, it will not work. You must have a revolutionary hboot (see prerequisites).
***If you performed this procedure with previously and have hboot version 6.14.5555 please update to the new hboot, 6.14.5555 is no longer supported***
Upgrade instructions at the bottom of the procedures.
Prerequisites
You must have performed Revolutionary S-OFF
If running on windows you will need these fastboot drivers
If running the procedure on Linux or MacOS you must have fastboot working.
There are no other software prerequisites for this procedure, it does not matter what ROM/Kernel or recovery you are using.
Don't bother asking for help if you try to do this on a virtual machine, you won't get any.
Run on a real machine.
Windows Instructions
Download this file MD5=c62cc1d0453799a7277abfea444d20e4
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Extract the large zip file downloaded in step 1
Navigate to the RUU_Express_B02 directory
Double-click ARUWizard.exe and proceed like any other RUU, ticking the boxes and pressing next the screen as required.
Postinstall
Reboot to recovery
Flash the SU zip file copyed in instruction 3
Linux/MacOS Instructions (Also works on windows, use if ARUWizard.exe crashes for you)
Download this file MD5=5ef525038a3b8b0af2f214098fd80252
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Boot your view to fastboot mode.
Run the following commands:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip RUU_Express_B02_RAW.zip
[COLOR="Red"][I]***This will fail first time with error 90, repeat the command[/I][/COLOR]
fastboot flash zip RUU_Express_B02_RAW.zip
[COLOR="Red"][I]***Ignore the on-screen progress bar, the flash is complete when fastboot completes[/I][/COLOR]
fastboot reboot
Postinstall
Reboot to recovery
Flash the SU zip file copyed in instruction 3
Alternative Installation Instruction (Any OS)
Download this file MD5=5ef525038a3b8b0af2f214098fd80252
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Rename the RUU_Express_B02_RAW.zip file PG41IMG.zip and place on the root of your (external) sdcard
Copy the superuser zip file to the root of your SDCARD
Boot your view bootloader, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update
***This will fail after completing part of the update, don't worry it's expected***
Boot your view bootloader a second time, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update again.
Postinstall
Reboot to recovery
Flash the SU zip file copyed in instruction 3
Do not mirror files from this post.
No discussion of Honeycomb content or changes or the relative merits of Gingerbread and Honeycomb. This thread is for the procedure and support thereof only! Also please don't quote the first post because your post becomes an automatic TLDR.
Update Instructions
Use these instructions if you currently have hboot 6.14.5555 - Your data should be preserved but take a backup first just in case.
Method 1
Download this file MD5=20fd6e7546ac2fc422c5a9a5b366f77c
Copy the file to the root of your external SDCARD
Boot your view bootloader, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update
Method 2
Download this file MD5=20fd6e7546ac2fc422c5a9a5b366f77c
Boot your view to fastboot mode.
Run the following commands:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip PG41IMG.zip
[I][COLOR="Red"]***Ignore the on-screen progress bar, the flash is complete when fastboot completes[/COLOR][/I]
fastboot reboot
[Revision History]
B02 - updated full version: hboot 6.14.5556
New bootloader to patch bugs with fastboot flashing
- Fastboot flashing splash1 fixed
- Fastboot flashing hboot fixed
Patch for upgrading from a previous version added.
B01 - Initial full version: hboot 6.14.5555
BETA- Developer preview
Special thanks: contradude for the early and riskiest testing, and Maine_Coon for all the ongoing testing
Downgrade to Gingerbread
Preamble
This is the S-OFF downgrade from HoneyComb to S-OFF GingerBread if you are not S-OFF and have a HTC (not revolutionary) hboot then do not do this it will not work.
The full versions of these files will give you a fully functional Gingerbread installation with S-OFF, CWM recovery and boot image with the secure flag turned off.
Windows Instructions
Download this file MD5=f5afc4b457a17f88cc611b40e6c7cdc8
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Extract the large zip file downloaded in step 1
Navigate to the Express_Downgrade directory
Double-click ARUWizard.exe and proceed like any other RUU, ticking the boxes and pressing next the screen as required.
Postinstall
Reboot to recovery
Flash the SU zip file copied in instruction 3 if using the full version.
Linux/MacOS Instructions (Also works on windows, use if ARUWizard.exe crashes for you)
Download this file MD5=7cfbaf099d80d899b13848a3ed3fd66a
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Copy the superuser zip file to the root of your SDCARD
Boot your view to fastboot mode.
Run the following commands:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip Express_dg.zip [colour=blue](or Express_dg_lite.zip as appropriate)[/blue]
[COLOR="Red"][I]***This will fail first time with error 90, repeat the command[/I][/COLOR]
fastboot flash zip Express_dg.zip [colour=blue](or Express_dg_lite.zip as appropriate)[/blue]
[COLOR="Red"][I]***Ignore the on-screen progress bar, the flash is complete when fastboot completes[/I][/COLOR]
fastboot reboot
Postinstall
Reboot to recovery
Flash the SU zip file copied in instruction 3 if using the full version.
Alternative Installation Instruction (Any OS)
Download this file MD5=7cfbaf099d80d899b13848a3ed3fd66a
Download the superuser zip file MD5=69f81ca292f14f71b081bb45a556a3e3
Rename the file downloaded in step1 to PG41IMG.zip and place on the root of your (external) sdcard
Copy the superuser zip file to the root of your SDCARD
Boot your view bootloader, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update
***This will fail after completing part of the update, don't worry it's expected***
Boot your view bootloader a second time, it will detect the PG41IMG.zip file and ask you to confirm update, confirm the update again.
Postinstall
Reboot to recovery
Flash the SU zip file copied in instruction 3 if using the full version.
Do not mirror files from this post.
wow you are really fast, excellent men.
One for me please
reserved 2
Great response time!
For us newbs, I'd like to clarify... This isn't an alternative HoneyComb, yet. Just an attempt to make the OTA honeycomb "unlockable", right?
vancraft said:
Great response time!
For us newbs, I'd like to clarify... This isn't an alternative HoneyComb, yet. Just an attempt to make the OTA honeycomb "unlockable", right?
Click to expand...
Click to collapse
This is an attempt to make downgrading easier for us.
spartan1987 said:
This is an attempt to make downgrading easier for us.
Click to expand...
Click to collapse
Right. That's the "recovery" part.
But its also described as "root, and all". I'm wondering if this allows the installer to root the OTA Honeycomb? Or will more work be required before the install can be further changed (i.e. s-off, eventually upgraded to ICS, etc.)?
It works
I can confirm this works with root flashed and all. I now have a rooted HC. tyvm globatron
risb577 said:
I can confirm this works with root flashed and all. I now have a rooted HC. tyvm globatron
Click to expand...
Click to collapse
so, does that mean you could, in theory, flash a custom HC rom once we get one?
Throw up some screenshots or a video would you?
edit: oh and test rom manager and titanium backup if you don't mind.
I have a rooted CWM backup of the stock.
Do I need to restore and then unroot before proceeding with HC?
stuck on soft brick..
Hey Guys
how do you do the step 6?
I am in cmd and kept telling me command not recornized or something...
I guess I need to know how to flash that RUU-mini zip...
thanks for all your help...
Maine_Coon said:
I have a rooted CWM backup of the stock.
Do I need to restore and then unroot before proceeding with HC?
Click to expand...
Click to collapse
No, as it says in the OP, You MUST be s-off and THEN run an RUU. Accept all updates to include the HC update and the view will be soft bricked. THEN use fastboot to push the mini ruu.
---------- Post added at 10:09 PM ---------- Previous post was at 10:07 PM ----------
myowin said:
Hey Guys
how do you do the step 6?
I am in cmd and kept telling me command not recornized or something...
I guess I need to know how to flash that RUU-mini zip...
thanks for all your help...
Click to expand...
Click to collapse
If it says it's an unrecognized command, then either you do not have fastboot installed, or you haven't gone into environment variables (assuming it's a windows box) and added those commands to the path. try that first (google is your friend and you can google in XDA). Good luck.
A quick question here. Once it is the soft brick mode, I hold down power and volume down to get back to fastboot mode. Is this correct? And I know the ruu will wipe my data but nothing here should wipe the internal sd, correct?
thank you so much for quick respond..
I think I found it here how to do that.. (for someone like me... )
http://forum.xda-developers.com/showthread.php?t=532719
root
Im not sure what this method of rooting will do for us, but I am under the impression that this will help if we need to go back to GB, or flash another custom HC rom when someone else cooks one up. I have not tested downgrading.
I can report that clockwork is installed with the option to flash from zip, mounts, etc just like the old clockwork. And I still have S-OFF. I installed ROM manager, but it gave me the "you don't have clockwork installed" message. I'm not sure if that is normal, because I don't use ROM Manager. Titanium did see root. Check out the screens.
ElAguila said:
A quick question here. Once it is the soft brick mode, I hold down power and volume down to get back to fastboot mode. Is this correct? And I know the ruu will wipe my data but nothing here should wipe the internal sd, correct?
Click to expand...
Click to collapse
I haven't done this yet, but I'm dling the RUU right now to do it and help people troubleshoot.
To answer your question, if you hold down the power button long enough, the view will power off, then you can hold power + vol down to get back into the bootloader and select fastboot mode, then open cmd, type fastboot devices and check to make sure yours shows up, then proceed with pushing the mini-ruu. If I'm wrong guys, correct me. Hope it works out for you.
ElAguila said:
A quick question here. Once it is the soft brick mode, I hold down power and volume down to get back to fastboot mode. Is this correct? And I know the ruu will wipe my data but nothing here should wipe the internal sd, correct?
Click to expand...
Click to collapse
Im not sure if this matters, but when I was in soft brick, I rebooted a few times and could not get into the bootloader. It just seemed to ignore the vol down keypress. I then unplugged the usb, powered off from soft brick, and held the vol. down button down even before I hit the power button as I was turning it on. Once I was in bootloader, I just plugged the usb back in.
EDIT: More tips:
1.After I flashed the initial stock ruu, and before I accepted any updates, I turned off fastboot in the power options and enabled usb debugging.
2. I did this from a Windows 7 laptop. When I initially tried to perform the softbrick steps, I got an access denied error message. The files were sent ok, but errored on saving. I closed the command prompt, and re-lauched the command prompt as administrator. The commands sent successfully.
3. Also, once you send the mini ruu over, the Tablet sat in the the oem loader with a 70% full progress bar after I successfully sent the mini ruu. I waited about 10 minutes because I was unsure how to proceed. I finally issued:
fastboot reboot-bootloader
Once back into bootloader, I mounted usb storage, copied SU to the card, and flashed from zip
risb577 said:
Im not sure what this method of rooting will do for us, but I am under the impression that this will help if we need to go back to GB, or flash another custom HC rom when someone else cooks one up. I have not tested downgrading.
I can report that clockwork is installed with the option to flash from zip, mounts, etc just like the old clockwork. And I still have S-OFF. I installed ROM manager, but it gave me the "you don't have clockwork installed" message. I'm not sure if that is normal, because I don't use ROM Manager. Titanium did see root. Check out the screens.
Click to expand...
Click to collapse
Yeah, rom manager won't work bc we don't have official support from Koush for CWM recovery so that's no issue, I was just curious is all lol. I'm glad to hear titanium detects root, as that was an issue initially for the view. Try to backup your apps, test radios (3g, 4g, wifi, bluetooth, GPS, ETC), run quadrant. I don't know how familiar you are with honeycomb to test out all of it's functions, but we are going to need a few people to test this out for globatron so he can make fixes and/or adjustments as necessary, which is why he specifically asked for devs and people familiar with troubleshooting to do this first. That's the beauty of open source, we're all guinea pigs.
I forgot to ask this earlier. What does the soft brick state look like? Is it just the white screen the the green HTC on it? I want to make sure I don't power it off while it is still flashing HC.
soft brick screen
ElAguila said:
I forgot to ask this earlier. What does the soft brick state look like? Is it just the white screen the the green HTC on it? I want to make sure I don't power it off while it is still flashing HC.
Click to expand...
Click to collapse
It looks like this pic. Plus another clue you are soft bricked is it stays here longer than 10 minutes if you care to wait lol
So I just bought an HOX+ a couple of hours ago, and I used the HTC all-in-one kit to unlock it. I then flashed CMW through the same program flawlessly.
The problem occurred when I flashed boot.img from the Android Revolution HD ROM, which your supposed to do before you flash the ROM he says. Well, after I did that, I rebooted the phone to transfer the custom ROM to the phones storage to install through CWM, but it now boot loops at the htc boot screen. This makes sense because the boot.img is not the original one for the stock ROM. However, there is no way of installing the custom ROM onto the device. Seems as though I missed to put the ROM on the phone's memory before flashing that boot.img....stupid of me
I can not install the custom ROM because:
- There is no mount USB storage in CWM, which on my previous phone there was....
- adb push command does not work because it can't find the device. Only fastboot finds the device, and there are no commands I see that install a zip.
- sideload also does not work as it says its 'out of date' and then cannot find the device
- I can't boot into the OS to copy the file because of the boot.img and boot looping.
- I tried flashing this stock boot.img file found Here: http://forum.xda-developers.com/showthread.php?p=29173294; all that did was shut down the device instead of looping after the HTC quietly brilliant bootup screen.
- All the stock RUU's are .exe that you install when your in the phone's OS, which doesn't work for me...right? Or can they work in the bootloader/recovery...
I find it weird that I didn't see anything about rooting the device at all after unlocking, but whatever....
So now I am stuck because I cannot install the custom ROM, but I also don't have the original boot.img of the stock ROM.
I am using an ATT htc one X+ quad core. I can still boot into CWM.
How do I fix this?
First thing, you just flashed an INTERNATIONAL ROM on your AT&T/TELUS phone, this the bootloop reason. (If your profile is up to date)
Second thing, you should have taken TWRP Recovery over CWM because all aptions are tested and approved working with TWRP Recovery + HOX+
Third thing you didn't mention that your SDK/ADB/HTC's Drivers combo tools are installed.
Fourth and nonetheless you didn't read enough before proceeding with all the unlocking+rooting process.
Now, can you access your bootloader and is your phone recognized when plugged?
Thanks so much for the reply. I'll answer in order to make it more concise:
First thing, you just flashed an INTERNATIONAL ROM on your AT&T/TELUS phone, this the bootloop reason. (If your profile is up to date)
Click to expand...
Click to collapse
I did not actually flash any custom ROM yet to the phone. After unlocking and flashing CWM to it using the all-in-one kit, all I did next was flash a boot.img file that your supposed to flash before installing the custom ROM (Android Revolution HD). I even forgot to put the custom ROM on my phone before flashing the boot.img, let alone install it.
Second thing, you should have taken TWRP Recovery over CWM because all aptions are tested and approved working with TWRP Recovery + HOX+
Click to expand...
Click to collapse
I will try to flash the TWRP recovery to it then.
edit:I used fastboot flash recovery to flash TWRP to it. I will wait for a response to continue from there.
Third thing you didn't mention that your SDK/ADB/HTC's Drivers combo tools are installed.
Click to expand...
Click to collapse
I originally had an motorola ATrix 4g, so I assume I have them all, but I did download all of it before I started. I downloaded the HTC drivers and the android SDK before I started, and I had an ADB package before. Maybe its the adb package that's giving me difficulties?
Now, can you access your bootloader and is your phone recognized when plugged?
Click to expand...
Click to collapse
I can access the bootloader, fastboot, and CWM recovery fine. However, the device is only recognized under fastboot, and not under adb in both fastboot and CWM. There is no 'mount usb storage' like I had on my Atrix, and adb commands like 'sideload' and 'push' do not work as the device is not found ever under adb. Again, it seems as though usb debugging is off because I factory reset it through the bootloader, but I can not get into the OS to change that.
All right, if your phone is still with the original ROM installed (you didn't say you had full wiped the phone) the only thing you have to do is to flash the original boot.img for HTC ONE X+ not the HTC ONE X like you did.
Please do take the right TWRP Recovery for the HTC ONE X + (EVITARE_UL) HERE for your AT&T / TELUS phone.
Rename this file like this TWRPrecovery.img (it's only easier to flash)
Put it in your platform-tools folder of SDK
Reboot in bootloader and put your phone in fastboot USB by plugging your USB cable
If your phone can be recognized with : fastboot devices (serial number validation) proceed with this : fastboot flash recovery TWRPrecovery.img (Enter)
If the result is Success, type : fasboot erase cache (Enter)
Done.
Unplug the USB cable hit Power button one time
Select Recovery (Volume down)
Power button one time
Rebooting in Recovery
You can try to sideload an AT&T/TELUS ROM
Try this, I will found you an original boot.img for your ROM version.
Lucky Thirteen said:
All right, if your phone is still with the original ROM installed (you didn't say you had full wiped the phone) the only thing you have to do is to flash the original boot.img for HTC ONE X+ not the HTC ONE X like you did.
Please do take the right TWRP Recovery for the HTC ONE X + (EVITARE_UL) HERE for your AT&T / TELUS phone.
Rename this file like this TWRPrecovery.img (it's only easier to flash)
Put it in your platform-tools folder of SDK
Reboot in bootloader and put your phone in fastboot USB by plugging your USB cable
If your phone can be recognized with : fastboot devices (serial number validation) proceed with this : fastboot flash recovery TWRPrecovery.img (Enter)
If the result is Success, type : fasboot erase cache (Enter)
Done.
Unplug the USB cable hit Power button one time
Select Recovery (Volume down)
Power button one time
Rebooting in Recovery
You can try to sideload an AT&T/TELUS ROM
Try this, I will found you an original boot.img for your ROM version.
Click to expand...
Click to collapse
Thank you for the response, I will try to sideload a compatible ROM now using TWRP. I actually see a newer version of TWRP on their thread, and it installed fine also.
eurosport360 said:
Thank you for the response, I will try to sideload a compatible ROM now using TWRP. I actually see a newer version of TWRP on their thread, and it installed fine also.
Click to expand...
Click to collapse
That is fine. Do consider that sideloading can take some time, patience is the key. I will gave you the original AT&T boot.img in a few.
Here it is, this an original boot.img for AT&T (EVITARE_UL)
Put it in your platform-tools folder of SDK
Reboot in bootloader and put your phone in fastboot USB by plugging your USB cable
If your phone can be recognized with : fastboot devices (serial number validation) proceed with this : fastboot flash boot ATTboot.img (Enter)
If the result is Success, type : fasboot erase cache (Enter)
Done.
Unplug the USB cable hit Power button one time
Select Reboot (Volume down)
Power button one time
Rebooting
If this is good, your phone will reboot and be fully functional.
Lucky Thirteen said:
That is fine. Do consider that sideloading can take some time, patience is the key. I will gave you the original AT&T boot.img in a few.
Here it is, this an original boot.img for AT&T (EVITARE_UL)
Put it in your platform-tools folder of SDK
Reboot in bootloader and put your phone in fastboot USB by plugging your USB cable
If your phone can be recognized with : fastboot devices (serial number validation) proceed with this : fastboot flash boot ATTboot.img (Enter)
If the result is Success, type : fasboot erase cache (Enter)
Done.
Unplug the USB cable hit Power button one time
Select Reboot (Volume down)
Power button one time
Rebooting
If this is good, your phone will reboot and be fully functional.
Click to expand...
Click to collapse
You are a GOD. Thank you so much, that worked. I can now boot into the stock ROM.
Alright, if you have the time, one very last question.
I want to make sure I am correct with this process. I want to install the Elegancia AT&T version. Here is what I would do.
1) Transfer the ROM.zip to root of phone memory
2) extract and install the boot.zip to the phone first through fastboot flash boot 'file'
3) Then without rebooting install the ROM.zip through TWRP
I assume the ROM comes with SU which roots the device.
That is a good news!
Yep! To flash your intend ROM simply transfer the file to your storage.
Reboot in fastboot, flash the Elegancia boot image like you did for the sock one (simply rename the modded boot image i.e. EleganciaBoot or Eboot.img) Simply download the Kernel flasher then Copy/Paste the boot.img inside the folder.
If your phone can be recognized with : fastboot devices (serial number validation) proceed with this : fastboot flash boot EleganciaBoot.img (Enter)
Again if the result is Success, type : fasboot erase cache (Enter)
Done.
Unplug the USB cable hit Power button one time
Select Recovery (Volume down)
Power button one time
Rebooting in Recovery
Do a FULL BACKUP of your actual ROM and keep it in a safe place on your computer once rebooted
Full wipe Factory reset, system, cache & Dalvik
Flash your new ROM
Reboot Enjoy!
All ROM you will flash are already rooted, so no extra step for this.
Before I get into the gist of my current problem I think it might be relevant to provide some backstory. I decided I wanted to try and root my phone so I could install a new custom ROM. I had done some jailbreaking back when the iPod touches came out, back when jailbreaking was extremely ghetto and unreliable, so I figured I could teach myself this fairly easily. I unlocked bootloader using the htcdev method without an issue, and, following a guide, downloaded something called Rootboot to flash the phone. There was only one step to this portion, so I assumed it would be easy. Running the rootboot started rooting my phone, however after a couple of lines in the command prompt it said something about the adb, failed, and the phone was stuck in a boot loop with no roms on it at all. I stayed up all night with the damn thing attempting to fix it, and at one point, actually got it to load up the stock ROM from the computer using some combination of RUU's and fastboot commands. I have no clue how I did it, all I know is that it was not through adb sideload because the recovery I had at the time wouldn't work with adb sideload for whatever reason. It was the recovery that came with the All-In-One toolkit, for the AT&T / TELUS version. At this point I figured since the phone was working I would just install the VenomROM, and after a few hours of playing around with fastboot and the bootloader trying to get a ROM loaded, I figured I was familiar enough with all of them to load the ROM.
Which is what brings me to my current issue. I KNOW the boot.img is flashed to the device because I used the All-In-One Toolkit to do it, erased the cache, did it again using fastboot commands in the command prompt, erased the cache, and continued to use recovery to install the ROM. I got it to load and install, cleared the darvik cache, data, and cache, but when booting, the phone would get to the lock screen, upon which sliding to unlock, presented me with a white screen that says "htc" on it instead of a launcher. After a couple of seconds of waiting, it says, "setup has quit responding" and gives me the option to close or to wait. Either option results in the phone rebooting wherein I only see a black screen with the notification bar at the top displaying my battery and no internet/network connection. I have gone back and flashed the boot.img again and cleared cache, darvik cache, and data several times and just have no clue what I'm doing wrong to not get this phone to boot with the ROM. I can reflash at any point from my sideload.zip file and the installation process has an option to flash the kernel (boot.img) because it is included in the zip. Any help would be much appreciated. I highly doubt theres anything wrong with the ROM or boot.img, it is probably me just not doing it right.
I am using (or attempting to use) the 1.2.7 version of VenomXL+ on the HTC One X+ along with TWRP 2.5 as the recovery.
Hi patarrfwifwi,
This should help you getting your phone back, make sure your SDK/ADB tool is perfectly installed (see in my signature if you need a guide) on your computer, this is the manual procedure to achieved a custom recovery, installing root and transferring a ROM via sideload to your phone to allow an installation.
Download this recovery HERE
Move this file in your platform-tools folder
Press and hold the Shift key and right click on a empty space of that folder and select Open Command Window Here
In the command window with your phone in FASTBOOT USB mode
Type>fastboot flash recovery TWRP2500.img
(Success)
Type again>fastboot erase cache
(Success)
Unplug your USB cable
Hit one time Power
Select Recovery (Volume down)
Hit Power to Reboot in Recovery
Your phone should reboot in Recovery
(!! The following instruction are with TWRP Recovery installed !!)
Select Advanced -> ADB Sideload -> swipe to activate
Download this file SuperSU and transfer this file again in platform-tools folder
Press and hold the Shift key and right click on a empty space of that folder and select Open Command Window Here
Type>adb sideload SuperSU.zip (Enter)
(Success)
Once done select Install menu of the Recovery
Locate sideload.zip and select it.
Swipe to confirm.
You are done rooting your phone.
Stay in Recovery and delete the sideload.zip file
Select Advanced -> ADB Sideload -> swipe to activate
Download this file ViperXL+ 1.2.7 JB and transfer this file again in platform-tools folder
Press and hold the Shift key and right click on a empty space of that folder and select Open Command Window Here
Double click on the ViperXL+-1.2.7.zip file and locate the boot.img and drag it to the platform-tools folder.
Type>adb sideload ViperXL+-1.2.7.zip (Enter)
(Success)
Once done select Wipe menu and wipe (factory reset and format system)
Select Install menu of the Recovery
Locate sideload.zip and select it.
Swipe to confirm.
Aroma installer will start leave everything by default and install the ROM.
Once done select Reboot-> Bootloader
Make sure FASTBOOT USB is highlighted
In bootloader via the command window type>fastboot flash boot boot.img (Enter)
(Success)
At the prompt type>fastboot erase cache (Enter)
(Success)
Finally at the prompt>fastboot reboot (Enter)
Rebooting
Give your phone ~5-10 minutes to complete the installation.
Tell me how that went please.
Thank you very much for the extensive reply. I am going to start on this right away. Quick update: I tried installing a different ROM named elegancia and got the same problem at the lock screen with it saying system process not responding. Might be irrelevant at this point, but I thought I'd throw up the update.
Starting this now, I'll get back to you when I'm done.
Unfortunately, this ended in the same problem. White screen with htc, system process stopped running. boot loop.
The only differences between this and what I was doing is that I never had that SuperSU step before and I was running everything from the data folder of the All-In-One toolkit instead of the sdk.
Try fixing permissions in recovery.
sixcarnage said:
Try fixing permissions in recovery.
Click to expand...
Click to collapse
Ok, did that. It just enters a black screen with the notification bar at top, then goes black. The keys respond to hitting the lock/power button, but the notification bar goes away permanently, then phone goes back and reboots again.
What boot.img are you flashing? Is it the one inside the .zip?
sixcarnage said:
What boot.img are you flashing? Is it the one inside the .zip?
Click to expand...
Click to collapse
Yes
Try the one in the forum under the downloads. I know it's the stock but give it a shot.
Where would I find that?
If that doesn't work try the Beast Mode Kernel.
Download: http://db.tt/aGV3WhR2
Extract the boot.img from .zip and then flash the .zip in recovery.
Does this work?
---------- Post added at 10:39 PM ---------- Previous post was at 10:37 PM ----------
patarrfwifwi said:
Where would I find that?
Click to expand...
Click to collapse
Don't get cocky that was an accidental thanks
Here is the stock boot.img from the Viper thread
Download: http://www.androidfilehost.com/?fid=9390248398092764372
I don't really need a custom ROM, if I could just get the phone back to stock that would be good too. Basically, I don't care what I do to get it to work again, I just want to be able to use my phone. I've been out a cell since Sunday night and if going back to stock is easy and simple I'll just do that. If custom ROMs are the easiest option at this point I'll stick with that too; whatever gets my phone working the fastest.
Any luck with the above?
I flashed the boot.img from the beastmode, adb sideloaded the zip, installed the zip, did a wipe (darvik cache and whatnot) and after the Viper startup screen, it brought me to a screen that said upgrading apps (260 of them) and my hopes were up so much, but then it just started with the black screen. went into recovery and wiped the cache and darvik cache again, restarted, same problem with the htc screen.
I flashed the stock boot onto it and restarted. No luck,
I'm going to bed for the night. I'll be back on around 3 PM EST tomorrow.
patarrfwifwi said:
I'm going to bed for the night. I'll be back on around 3 PM EST tomorrow.
Click to expand...
Click to collapse
I'd go back to stock for now.
What I would do is get the att latest ruu and adb it to the phone to install. This happened to me and all I got was a black screen with the noti bar on top and nothing else. And then i send the latest ruu zip through adb and installed it. And now I have a working phone
Seems like we can't downgrade right now..
Sent from my SoftBank AQUOS PHONE Xx 203SH using XDA Premium
can you give me a link to this? i found the latest ruu, but its an exe file instead of a zip
RUU is always under an *.exe type file. It must be flash in bootloader mode (fastboot) via your computer with your phone plugged in.
Can you tell which HBOOT version you have (you can check this in bootloader mode)?
So I tried to flash a rom and hit some problems, now when I try to restart my phone it gets stuck on the "verizon 4g lte" screen and wont load past there. When I open bootloader there are 3 warnings at the very top:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
How can I get my phone back to stock? I need this IMMEDIATLY if possible!!
Also make it as simple as possible, I'm new to roms and roots and flashing.
BabyPenguin said:
So I tried to flash a rom and hit some problems, now when I try to restart my phone it gets stuck on the "verizon 4g lte" screen and wont load past there. When I open bootloader there are 3 warnings at the very top:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
How can I get my phone back to stock? I need this IMMEDIATLY if possible!!
Also make it as simple as possible, I'm new to roms and roots and flashing.
Click to expand...
Click to collapse
You need to unlock the boot loader again. Flash a recovery img again.
Sent from my Rezound using xda app-developers app
tburns said:
You need to unlock the boot loader again. Flash a recovery img again.
Sent from my Rezound using xda app-developers app
Click to expand...
Click to collapse
What is a recovery img?
BabyPenguin said:
What is a recovery img?
Click to expand...
Click to collapse
as it was stated, you need to unlock your bootloader again. A recovery image is a image that we use to flash and wipe roms and the phone. Amon RA, TWRP and CW are the ones we can use for our phone. I personally use TWRP and Amon RA depending on my mood. You can find them here
http://forum.xda-developers.com/showthread.php?t=1425091
Towards the bottom of the list you will see recovery. You will need to flash one of those in order to flash a custom rom.
Also make sure to read the tutorials towards the bottom. before you start messing with your phone you should be familiar with everything. If you do something wrong and brick your phone, its hard to recover from if at all and you would have an expensive paper weight
clmowers said:
as it was stated, you need to unlock your bootloader again. A recovery image is a image that we use to flash and wipe roms and the phone. Amon RA, TWRP and CW are the ones we can use for our phone. I personally use TWRP and Amon RA depending on my mood. You can find them here
http://forum.xda-developers.com/showthread.php?t=1425091
Towards the bottom of the list you will see recovery. You will need to flash one of those in order to flash a custom rom.
Also make sure to read the tutorials towards the bottom. before you start messing with your phone you should be familiar with everything. If you do something wrong and brick your phone, its hard to recover from if at all and you would have an expensive paper weight
Click to expand...
Click to collapse
Alright, so I downloaded both the files here: http://forum.xda-developers.com/showthread.php?t=1339679
Two problems. First, I have no way of accessing my sd card now because it wont let me through my computer
Second, I don't know how to use these files and after reading the thread it still didn't help.
EDIT: After unlocking the only two notices on my hboot is
TAMPERED
and
UNLOCKED
EDIT2: I found my SD card adapter.
BabyPenguin said:
Alright, so I downloaded both the files here: http://forum.xda-developers.com/showthread.php?t=1339679
Two problems. First, I have no way of accessing my sd card now because it wont let me through my computer
Second, I don't know how to use these files and after reading the thread it still didn't help.
EDIT: After unlocking the only two notices on my hboot is
TAMPERED
and
UNLOCKED
EDIT2: I found my SD card adapter.
Click to expand...
Click to collapse
1. you need to download fastboot if you have not already. You can find that in the android sdk
2.) once fastboot is downloaded boot your phone into bootloader and select the fastboot option and plug your phone into your computer
3.) place the recovery image in the same directory as fastboot and use the command prompt (windows key +r then type cmd and hit enter)
4.) change directory to where fastboot is and run this command
fastboot flash recovery recovery.img
where recovery.img is the name of the recovery file that you downloaded
clmowers said:
1. you need to download fastboot if you have not already. You can find that in the android sdk
2.) once fastboot is downloaded boot your phone into bootloader and select the fastboot option and plug your phone into your computer
3.) place the recovery image in the same directory as fastboot and use the command prompt (windows key +r then type cmd and hit enter)
4.) change directory to where fastboot is and run this command
fastboot flash recovery recovery.img
where recovery.img is the name of the recovery file that you downloaded
Click to expand...
Click to collapse
Done, now what? Thanks for the help by the way!
BabyPenguin said:
Done, now what? Thanks for the help by the way!
Click to expand...
Click to collapse
yeah no problem.
If you go back into the bootloader and select recovery, this will bring you into the Amon Ra.
Download a rom from the forums, I personally like Neo's Roms, Infection 2.8.1 is a good choice. But download any rom and put it on your SD card.
1.) select USB-MS toggle and then select on of the options
2.) copy downloaded rom to mounted sdcard
3.) once copied, hit the power button to unmount and then return to the main menu
4.)select wipe from the main menu and then do each one of these 3 times
Wipe All data/factory reset
Wipe /data
Wipe /cache
Wipe /Dalvik-cache
Wipe /system
then go back to main menu and then select Fash zip menu and select where you placed your rom and then flash...once its flash go back to main menu and select Developers menu and selet reboot bootloader
open the rom using a zip program and pull the boot.img from the rom and place it in your fastboot directory
once you are in the bootloader it should go to fastboot usb automatically and then run these commands
fastboot flash boot boot.img
fastboot reboot
it should reboot and load your rom
clmowers said:
yeah no problem.
If you go back into the bootloader and select recovery, this will bring you into the Amon Ra.
Download a rom from the forums, I personally like Neo's Roms, Infection 2.8.1 is a good choice. But download any rom and put it on your SD card.
1.) select USB-MS toggle and then select on of the options
2.) copy downloaded rom to mounted sdcard
3.) once copied, hit the power button to unmount and then return to the main menu
4.)select wipe from the main menu and then do each one of these 3 times
Wipe All data/factory reset
Wipe /data
Wipe /cache
Wipe /Dalvik-cache
Wipe /system
then go back to main menu and then select Fash zip menu and select where you placed your rom and then flash...once its flash go back to main menu and select Developers menu and selet reboot bootloader
open the rom using a zip program and pull the boot.img from the rom and place it in your fastboot directory
once you are in the bootloader it should go to fastboot usb automatically and then run these commands
fastboot flash boot boot.img
fastboot reboot
it should reboot and load your rom
Click to expand...
Click to collapse
I have no idea why this isn't working
http://gyazo.com/2627f9963c95e7dc9a03cb118f139aac.png
I did your steps in order, but my phone has been stuck on rebooting... for over 15 minutes as you can see from the CMD. On my phone I just see the booting logo spinning.
I used this rom because I want jellybean: http://forum.xda-developers.com/showthread.php?t=2113140
Any ideas?
Also, what do I do with the MD5? I didn't use it.
BabyPenguin said:
I have no idea why this isn't working
http://gyazo.com/2627f9963c95e7dc9a03cb118f139aac.png
I did your steps in order, but my phone has been stuck on rebooting... for over 15 minutes as you can see from the CMD. On my phone I just see the booting logo spinning.
I used this rom because I want jellybean: http://forum.xda-developers.com/showthread.php?t=2113140
Any ideas?
Click to expand...
Click to collapse
the reboot step isnt 100% needed, its more for ease of use...just pull the battery and power on
Also did you flash the boot.img file?
---------- Post added at 07:22 AM ---------- Previous post was at 07:18 AM ----------
BabyPenguin said:
I have no idea why this isn't working
http://gyazo.com/2627f9963c95e7dc9a03cb118f139aac.png
I did your steps in order, but my phone has been stuck on rebooting... for over 15 minutes as you can see from the CMD. On my phone I just see the booting logo spinning.
I used this rom because I want jellybean: http://forum.xda-developers.com/showthread.php?t=2113140
Any ideas?
Also, what do I do with the MD5? I didn't use it.
Click to expand...
Click to collapse
Dont worry to much about the MD5,I havent used one if forever. Its basically just a security check to make sure that the file you downloaded didnt get corrupt. But with modern technology and internet, its less likely to mess up while downloading. Still possible, but not likely
clmowers said:
the reboot step isnt 100% needed, its more for ease of use...just pull the battery and power on
Also did you flash the boot.img file?
Click to expand...
Click to collapse
It's still just sitting on the boot screen.
If you didn't see my edit, there is an md5 file I can download, but I didn't use it because I don't know what to do with it.
BabyPenguin said:
It's still just sitting on the boot screen.
If you didn't see my edit, there is an md5 file I can download, but I didn't use it because I don't know what to do with it.
Click to expand...
Click to collapse
Just sent you a PM buds
maybe you can help me out quick im stuck on the lte logo also my bootloader is unlocked but when i open it to try and fix my problem its says i need an update. so i select update, it finishes, and makes me reboot which gets me stuck again.
i cant pick anything in the bootloader menu until i select yes or no for this update but both options require me to reboot after choosing then im back to stuck.
xcapeartist said:
maybe you can help me out quick im stuck on the lte logo also my bootloader is unlocked but when i open it to try and fix my problem its says i need an update. so i select update, it finishes, and makes me reboot which gets me stuck again.
i cant pick anything in the bootloader menu until i select yes or no for this update but both options require me to reboot after choosing then im back to stuck.
Click to expand...
Click to collapse
It sounds like you have a ph98img file on your sdcard. Remove the sdcard and Mount it in a PC and remove it. Then remount in the phone. Should allow to get into recovery and fastboot then
Sent from my ANDROFLY REZOUND using xda app-developers app
clmowers said:
It sounds like you have a ph98img file on your sdcard. Remove the sdcard and Mount it in a PC and remove it. Then remount in the phone. Should allow to get into recovery and fastboot then
Sent from my ANDROFLY REZOUND using xda app-developers app
Click to expand...
Click to collapse
thanks for the help, before i got your message i got around the issue in a different way just trying a few things. I figured out the phone would boot into recovery with no sd card in it but i couldnt flash the rom again without it installed so i put the sd in partially and then held the battery against the contacts with out inserting it completely then booted into recovery, push the sd in the rest of the way and i was golden for there.
but i happy that someone knew wat it was on the sd card that was giving me the problem ive got that deleted now thanks for the help
xcapeartist said:
thanks for the help, before i got your message i got around the issue in a different way just trying a few things. I figured out the phone would boot into recovery with no sd card in it but i couldnt flash the rom again without it installed so i put the sd in partially and then held the battery against the contacts with out inserting it completely then booted into recovery, push the sd in the rest of the way and i was golden for there.
but i happy that someone knew wat it was on the sd card that was giving me the problem ive got that deleted now thanks for the help
Click to expand...
Click to collapse
That works too, probably not the best thing for the phone, but it works, glad i could point you in the right direction
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Strikerz87 said:
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Click to expand...
Click to collapse
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Strikerz87 said:
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Click to expand...
Click to collapse
also to note....you dont have to install linux to get s-off....if you follow my guide you can do it straight from a live disk rather than installing it....so it wont erase or mess up your windows partition at all
Solved!
Thank you, Mjones, I finally got it! I knew it was much easier than I was making it out to be. I was missing the kernel! Yeah, a crucial part in the process, I know
I first ran CWM and flashed the ROM over and ran the .zip through recovery (which I couldn't understand at first as I could never find it in the directory) but the installer would only go 50% and would fail... makes sense why now lol
I later flashed TWRP and backed up again after recovering from the fail. I flashed over the kernel and voila! So simple... Had to slap myself.
Thanks again! Case solved.
REV3NT3CH, that is sweet!! I have been hoping there is a way to gain s-off with Windows. I have 7 at work and 8.1 (which I can't get anything to work on) at home. I actually have to focus on work today haha so I'll look into the method and try it out tomorrow if I can. Thanks for all of the help.
mjones73 said:
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Click to expand...
Click to collapse
Thank You So much, Mine case also Resolved. I was too frustated sice last 3 days cause my phone was in dead mode. At the end, fastboot flash boot boot.img Worked. ThankYOu
mjones73 said:
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Click to expand...
Click to collapse
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
ecols33 said:
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
Click to expand...
Click to collapse
Sorry, don't know anything about that phone.
ecols33 said:
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
Click to expand...
Click to collapse
Did you try this first? (Right from Moto's site)
Perform a factory reset using external keys
1. Power off the phone, press and hold volume down button, press power button
2. Screen will come up with "Fastboot", press Vol down key to cycle through choices until you get "Android Recovery", then press Vol up key
3. Wait for the "triangle ! / Android" screen then go on to step 4
4. Press both Vol up and Vol down key simultaneously. A menu will come up
5. Tap on Vol down key until "wipe data/factory reset" is highlighted, and tap Power key. Another Confirmation screen will come. Tap on Vol down key until coming to Yes and tap Power key
6. After userdata is cleared, the "reboot system now" option will be highlighted by Default. Tap Power key
7. Phone will reboot to initial setup screen.
PLEASE HELP! I have a Huawei P8 and I tried to update to android 6.0 (GRA-L09xxxxxxxxxxxB317 or something) Went to install it and now im stuck in bootloop (a very annoying one, I can rarely get into eRecovery and eRecovery is not able to fix my problem: "Getting package info failed") so I went into fastboot&rescue mode and I did the flash thing via my PC (that Fastboot flash boot boot.img etc.) but I get this error saying: "FAILED (remote: Command not allowed)" for any image im trying to flash. My fastboot/bootloader or whatever it's called is locked my android is unrooted and stock android. I don't know how to unlock it I can't find anything anywhere.. HELP ME
not working
hariom.gupta11 said:
Thank You So much, Mine case also Resolved. I was too frustated sice last 3 days cause my phone was in dead mode. At the end, fastboot flash boot boot.img Worked. ThankYOu
Click to expand...
Click to collapse
not working on my 4c. write successful but when reboot is completed it goes to previous state.
"the user data partition can no longer be used"
zb602kl_x00tdb
L0RDZ3RO said:
PLEASE HELP! I have a Huawei P8 and I tried to update to android 6.0 (GRA-L09xxxxxxxxxxxB317 or something) Went to install it and now im stuck in bootloop (a very annoying one, I can rarely get into eRecovery and eRecovery is not able to fix my problem: "Getting package info failed") so I went into fastboot&rescue mode and I did the flash thing via my PC (that Fastboot flash boot boot.img etc.) but I get this error saying: "FAILED (remote: Command not allowed)" for any image im trying to flash. My fastboot/bootloader or whatever it's called is locked my android is unrooted and stock android. I don't know how to unlock it I can't find anything anywhere.. HELP ME
Click to expand...
Click to collapse
I have same problem on asus zenfone max pro m1 I bought it online said used and now working
can't boot into recovery.
can't boot into system.
Only EDL Mode and Fastboot Mode, but fastboot is Locked whic I cant unlock because I cannot boot into system to toggle USB Debugging and allow OEM unlocking
Qualcomm is harder to flash than MTK that can use SP FlashTool.
on this I use QFIL but keeps "sahara error". I tried searching and try moving firmware file to bin but no Luck. I'm currently trying different version of QFIL Tool.
If it FAILS my only HOPE is to use MUT-QCfire which will Require a "SmartCardReader" Which is a bit pricey and I don't even know if it will work on my device.