Need help getting RUU Stock back on phone.

Need help getting RUU Stock back on phone. - HTC One X+

(SOLVED)i downloaded the RUU from HTC Dev Site and i have no clue on ow to install it.

this is the guide it came with any ideas?
--Please follow below command to download the official android toolchain: (arm-eabi-4.6)
git clone https://android.googlesource.com/platform/prebuilt
NOTE: the tool ¡¥git¡¦ will need to be installed first; for example, on Ubuntu, the installation command would be: apt-get install git
--Modify the .bashrc to add the toolchain path, like bellowing example:
PATH=/usr/local/share/toolchain-eabi-4.6/bin:$PATH
--Start
$make ARCH=arm CROSS_COMPILE=$TOP/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin/arm-eabi- ap37_android_defconfig
$make ARCH=arm CROSS_COMPILE=$TOP/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin/arm-eabi- -j12
$TOP is an absolute path to android JB code base
--Clean
$make clean
--Files path
> arch/arm/boot/zImage
> Please remember to update kernel modules also by the following commands before full function testing
adb remount
adb push ./drivers/scsi/scsi_wait_scan.ko system/lib/modules/
adb push ./drivers/net/wireless/bcmdhd_4334/bcmdhd.ko system/lib/modules/
adb push ./drivers/net/usb/raw_ip_net.ko system/lib/modules/
adb push ./drivers/usb/class/cdc-acm.ko system/lib/modules/
adb push ./drivers/usb/serial/baseband_usb_chr.ko system/lib/modules/
adb push ./crypto/tcrypt.ko system/lib/modules/
adb push ./arch/arm/mach-tegra/baseband-xmm-power2.ko system/lib/modules/
adb shell "chmod 0644 system/lib/modules/"
adb reboot

omg someone please help me i just want my phone back to the way it was when it was brand new, i tried getting the RUU but its in a TAR file and theres hundreds of files i don't understand why this is so complicated never have i been so confused on an android device..

Do you know how to use ADB command window?

Lucky Thirteen said:
Do you know how to use ADB command window?
Click to expand...
Click to collapse
Yes i do, i have Rooted a HTC Desire Z, HTC Desire C, Nexus 7, and Samsung Galaxy S3, i have never had such a problem like this ever been sitting on my pc for 2 days trying to figure out whats wrong.

I can help you if you tell me what is your problem.
Is your phone unlocked, rooted and custom recovery installed? Which recovery? I already now that you have an ENRC2B International version.

Lucky Thirteen said:
I can help you if you tell me what is your problem.
Is your phone unlocked, rooted and custom recovery installed? Which recovery? I already now that you have an ENRC2B International version.
Click to expand...
Click to collapse
thank you! it is unlocked, S-on, the whole phone has been wiped now, it all started yesterday morning when i wanted to stop the lag while playing games so i flashed the elite kernel big mistake as i had stock rom.. didn't know it would cause all this problems... so then i side loaded ARHD and it installed and everything but the phone says there is still no OS.. i forgot to flash the ARHD boot.img first being that i'm s-on, so i don't know if that screwed things up? any way i want to go back to Stock Rom im with Telus Android 4.1.1. i went to HTC Dev Site and got this only RUU for it
evitare-jb-3.1.10-262c6aa.tar but it's in the TAR format so i downloaded 7-zip to view the files and theres hundreds of files im so confused.

Are you telling me that your phone is a TELUS version?
In Bootloader under ***Unlocked***
Is it written EVITARE_UL?

Lucky Thirteen said:
Are you telling me that your phone is a TELUS version?
In Bootloader under ***Unlocked***
Is it written EVITARE_UL?
Click to expand...
Click to collapse
Yes..

Alright!
This is where you have made all wrong. AHRD is only available for the International version. On your phone you can only install any custom ROM tagged AT&T/TELUS.
Which Recovery you have? TWRP?
To fix your issue tell me which ROM you want and I will write you a guide on how to get out of this situation.
There is a Venom full tweaked and customized.
Elegancia Stock and full y modded.
Blackout Mongoose a good mix of stock and customization with an optimized kernel.

Lucky Thirteen said:
Alright!
This is where you have made all wrong. AHRD is only available for the International version. On your phone you can only install any custom ROM tagged AT&T/TELUS.
Which Recovery you have? TWRP?
To fix your issue tell me which ROM you want and I will write you a guide on how to get out of this situation.
There is a Venom full tweaked and customized.
Elegancia Stock and full y modded.
Blackout Mongoose a good mix of stock and customization with an optimized kernel.
Click to expand...
Click to collapse
really omg.. i thought at&t was america only and int. was for canada... i hear everyone is on this venom or viper rom, i just want something fast, with sense and wont lag games with the T3 chip, what
would you recommend?

You wanna try Venom ROM? No problem!
Give me 15 minutes to write you a guide to install this on your phone. For now download this Venom ROM HERE. Once done sideload this ROM to your phone.

Lucky Thirteen said:
You wanna try Venom ROM? No problem!
Give me 15 minutes to write you a guide to install this on your phone. For now download this Venom ROM HERE. Once done sideload this ROM to your phone.
Click to expand...
Click to collapse
cool thank you so much! im going crazy without my phone. gonna have lots of fun when i get my OUYA..

Lets do this!
Download the required boot.img for this ROM HERE
Move this file in your platform-tools folder
Press and hold the Shift key and right click on a empty space of that platform-tools folder and select Open Command Window Here
Reboot in bootlader and in the command window with your phone in FASTBOOT USB mode
Type>fastboot flash boot Venom_boot.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 Wipe menu, then select Factory reset (swipe), select System (swipe)
Go back to the Install menu and select it.
Locate sideload.zip and select it.
Swipe to confirm.
Probably Aroma installer will start, simply follow the on-screen instructions and complete the installation.
Confirm the Rebooting option.
Give your phone ~5-10 minutes to complete the installation.
Lets start with this, if something is not clear, don't hesitate to ask, I will stay online.

Lucky Thirteen said:
Lets do this!
Download the required boot.img for this ROM HERE
Move this file in your platform-tools folder
Press and hold the Shift key and right click on a empty space of that platform-tools folder and select Open Command Window Here
Reboot in bootlader and in the command window with your phone in FASTBOOT USB mode
Type>fastboot flash boot Venom_boot.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 Wipe menu, then select Factory reset (swipe), select System (swipe)
Go back to the Install menu and select it.
Locate sideload.zip and select it.
Swipe to confirm.
Probably Aroma installer will start, simply follow the on-screen instructions and complete the installation.
Confirm the Rebooting option.
Give your phone ~5-10 minutes to complete the installation.
Lets start with this, if something is not clear, don't hesitate to ask, I will stay online.
Click to expand...
Click to collapse
Finally! I can't thank you enough! after the fast boot flash image i pretty much knew how to do the rest i appreciate it! and now i know when it says AT&T its also ment for Telus Canada and Not Int.

Is your phone alive now?
If all is good now for you, can you edit the title of your thread and this tag to it : [SOLVED]Need help getting RUU Stock back on phone

Related

[Help] Installing VenomXL+ on AT&T HTC One X+

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)?

[Tutorial] Root, Unlock, Recovery and flashing a Custom ROM

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

[Q] problem with recovery and boot

hi guys
i've unlocked my HTC ONE X + international!
but now i can't go further the HTC logo
i tried fastboot, flashing boot and recovering recover.img. but nothing go right.

Some questions:
Which rom did you try to flash?
What method did you use to flash it? (e.g. Hasoon's all in one tool/through recovery/sideload)
Did you make sure to flash your kernel (boot.omg) separately?
Did you perform a full wipe before flashing?
Can you enter the bootloader by holding volume-down while powering the phone on?
Can you use adb or fastboot to interact with the phone? e.g.
Code:
$ adb reboot bootloader
or
$ fastboot devices
Sent from my cellular telephone using xda premium

o_O said:
Some questions:
Which rom did you try to flash?
What method did you use to flash it? (e.g. Hasoon's all in one tool/through recovery/sideload)
Did you make sure to flash your kernel (boot.omg) separately?
Did you perform a full wipe before flashing?
Can you enter the bootloader by holding volume-down while powering the phone on?
Can you use adb or fastboot to interact with the phone? e.g.
Code:
$ adb reboot bootloader
or
$ fastboot devices
Sent from my cellular telephone using xda premium
Click to expand...
Click to collapse
after i unlocked the phone i've used fastboot to fastboot recovery.img
and that's all i did .
now i have low battery

Boot into bootloader by holding volume-down and restarting the phone (if you don't know how to do that, hold the power button until the capacitive lights flash).
Then, try flashing a recovery image. You can get twrp from the thread in the One X+ Original Android Development forum. I think you already have the platform tools (adb and fastboot).
The command to flash a recovery is:
Code:
$ fastboot flash recovery recovery.img
This is assuming your recovery filename is "recovery.img" and that it's in the same directory as your command prompt when you run the command.
Sent from my cellular telephone using xda premium

o_O said:
Boot into bootloader by holding volume-down and restarting the phone (if you don't know how to do that, hold the power button until the capacitive lights flash).
Then, try flashing a recovery image. You can get twrp from the thread in the One X+ Original Android Development forum. I think you already have the platform tools (adb and fastboot).
The command to flash a recovery is:
Code:
$ fastboot flash recovery recovery.img
This is assuming your recovery filename is "recovery.img" and that it's in the same directory as your command prompt when you run the command.
Sent from my cellular telephone using xda premium
Click to expand...
Click to collapse
thanks bro )))
but now it says there is no any zip file
is there any methods to "put custom rom inside" the phone???

tyomaus said:
thanks bro )))
but now it says there is no any zip file
is there any methods to "put custom rom inside" the phone???
Click to expand...
Click to collapse
If you've gotten the recovery installed, then you can sideload the rom onto the phone. I can give you instructions to do that with TWRP as your recovery. With your phone connected to your computer, enter the recovery from the bootloader. Choose the "Advanced" button, and then "ADB Sideload" and then swipe to start the sideload process.from your command line on your computer, you can now start the sideload process:
Code:
$ adb sideload name-of-rom-zip-file.zip
Obviously you would need to put the actual name of your rom's zip file and make sure your zip is in the correct directory to be picked up by the command. You should see the rom begin to upload to your phone, and when it's done, it will automatically flash.
I've found that sometimes sideload can take a little while to detect the phone but usually it detects it immediately. If it's taking a while, try running the following command and then do the sideload again; it might help:
Code:
$ adb kill-server
$ adb sideload name-of-rom-zip-file.zip
Don't forget that because we haven't gotten S-OFF for our device yet, we need to flash the kernel separately. Just open the rom zip file, and extract "boot.img". Then you need to enter the bootloader and flash that to your phone with this command:
Code:
$ fastboot flash boot boot.img
Hopefully that helps to sort your phone out.

thanks for help! )))
, MAN u r the best!!!! thanks a lot ! ))))

No problem! Glad to help.

o_O said:
No problem! Glad to help.
Click to expand...
Click to collapse
hi, i have one more problem (((
i've installed custom ROM, but only AOKP is working but not properly, after installing says there is no SD card ((
others stuck in loading screen.

This is because the default location of your SD card has changed from /data/media to /data/media/0. You can fix it by simply moving the contents of /data/media to /data/media/0.
Code:
$ adb remount
$ adb shell
# mv /data/media /data/0
# mkdir /data/media
# mv /data/0 /data/media/
Make sure you copy the commands exactly, including the slashes and that should have the contents of your SD card accessible again.

o_O said:
This is because the default location of your SD card has changed from /data/media to /data/media/0. You can fix it by simply moving the contents of /data/media to /data/media/0.
Code:
$ adb remount
$ adb shell
# mv /data/media /data/0
# mkdir /data/media
# mv /data/0 /data/media/
Make sure you copy the commands exactly, including the slashes and that should have the contents of your SD card accessible again.
Click to expand...
Click to collapse
thannks MAN, but it does not work (((
i tried to install OrDroid and it flies normally, however i'd like to use CM 10 4.2.2 which stuck in loading logo
maybe there is something i do wrong?!

tyomaus said:
thannks MAN, but it does not work (((
i tried to install OrDroid and it flies normally, however i'd like to use CM 10 4.2.2 which stuck in loading logo
maybe there is something i do wrong?!
Click to expand...
Click to collapse
every rom needs the correct boot.img/kernel to work. did you flash blade kernel for CM 10.1? did you wipe/factory reset your phone in recovery before you flashed CM 10?

Exactly what reaper90 said, the first thing you should check when you get a bootloop is the kernel.
A lot of other phones don't require you to flash the kernel separately, but those phones have S-OFF available to them. Since we're stuck with S-ON (for now), the boot partition is locked and can't be written to from the phone. So you have to flash the img containing the kernel + ramdisk separately. Also note that max has done three different versions of the BLADE kernel, so you need to ensure that you're grabbing the correct one.
Check max's post here: http://forum.xda-developers.com/showpost.php?p=34962464&postcount=1
Edit: Just another couple of things:
1. Like reaper90 said, doing a full wipe really helps when switching between roms. Usually you can get away without wiping if you're installing a new version of the SAME rom, but to be on the safe side I personally wipe everything when I flash a different rom.
2. If you're certain that you've done everything correctly, and it's still not working, try clearing your cache and dalvik cache from the recovery. Occasionally that can fix minor problems.

cool
reaper90 said:
every rom needs the correct boot.img/kernel to work. did you flash blade kernel for CM 10.1? did you wipe/factory reset your phone in recovery before you flashed CM 10?
Click to expand...
Click to collapse
thank you MAN!!! it's working! :good:

yourthebest
o_O said:
Exactly what reaper90 said, the first thing you should check when you get a bootloop is the kernel.
A lot of other phones don't require you to flash the kernel separately, but those phones have S-OFF available to them. Since we're stuck with S-ON (for now), the boot partition is locked and can't be written to from the phone. So you have to flash the img containing the kernel + ramdisk separately. Also note that max has done three different versions of the BLADE kernel, so you need to ensure that you're grabbing the correct one.
Check max's post here: http://forum.xda-developers.com/showpost.php?p=34962464&postcount=1
Edit: Just another couple of things:
1. Like reaper90 said, doing a full wipe really helps when switching between roms. Usually you can get away without wiping if you're installing a new version of the SAME rom, but to be on the safe side I personally wipe everything when I flash a different rom.
2. If you're certain that you've done everything correctly, and it's still not working, try clearing your cache and dalvik cache from the recovery. Occasionally that can fix minor problems.
Click to expand...
Click to collapse
nothing to say, just HUGE THANKS!!! )))

i have more questions, one of them is - how can i rollback stock ROM for my HOX+? i've bought it in UAE!
is it possible to install original ROM, if so where can i find one for my HOX+ ?
thanks in advance !

Sure, it's possible, and you have a couple of options depending on how "stock" you want to go.
If you just want to go back to a Sense rom, you can go to the One X+ Android Development forum and download any of the international roms from there. You would need to flash Elite kernel or hXORe kernel, which can also be found in that forum, and the process for flashing the rom and kernel is exactly the same as the AOKP/CM roms you already tried.
If you specifically need to get back to STOCK, then it's a little more complicated. You need to run a RUU (Rom Update Utility) for your device, which will put the original software back on your phone, but you need to remember to re-lock your bootloader before you run it, or it will fail. You can download the correct RUU for your device here (http://androidfiles.org/ruu/?developer=ENRC2B).
I would hazard a guess that you can find the right version by matching the radio version on your phone to the radio version on the RUU, along with your geographic location. You can find your phone's radio version by going to settings > about phone > baseband version. A quick explanation behind that logic is that a normal rom-flash won't touch your phone's radio, so you're likely to still have the same radio version that your phone shipped with.
WARNING, however, messing with your radio can brick your device so please please make sure you have the right one before you flash. I'm not sure which is the correct one for your device and the only RUUs I've ever flashed were way back in the early Windows Mobile days, so hopefully someone else here can give you better direction on that point.
Finally, if I were to give my opinion, you're better off taking a rom from the Android Development forum. I'm a die-hard AOSP fan, but I've flashed and played with the roms in there and our Sense devs have done a great job with the X+. The only reason I'd go back to stock is if I had to for warranty purposes.

tyomaus said:
i have more questions, one of them is - how can i rollback stock ROM for my HOX+? i've bought it in UAE!
is it possible to install original ROM, if so where can i find one for my HOX+ ?
thanks in advance !
Click to expand...
Click to collapse
As already said, I'd recommend installing a stock like custom rom, for example Android Revolution HD, it's very close to stock. You can find stock kernel/boot.img in the thread and if you want it as close to stock as possible you can just leave out all the tweaks options in aroma installer.

reaper90 & thank u BROS! )))

Help!!! My Rezound got bricked!! :'(

Ok... This is my 4th android phone.. And I love this phone... And only had it for a week.... and just now got it bricked.... here's what happen... Today I tried to flash a sense 4.1 rom, but im so new at this, and I'm half way done, and I went in a rush because I was nervous, and I accidentally press "install and keep data" and that was my mistake. I factory reset it b4 so I tried to flash it... So I thought it wouldn't be a problem. So I waited till the phone finish flashing. And when I rebooted the phone.... Nothing happened, just stuck on the white screen.... vibrating and etc... And I tried to restore all my data in clockworkmod recovery like I never even tried flashed it.. and it kept saying "won't mount sd card" and I tried to clear my cache/dalvik-cache, and like it still wont fix the issue. I even tried to restore wat I backup b4 I tried to flash it... and It was gone!!! Even my windows 8 laptop won't even detect my resound nor my sd card(unless its on a different android). But How can I fix my Rezound?!? plzzzz How can I fix this soft bricked issue? pllzzzzzzz help!!!

Im assuming you already have adb installed
Download this file
http://www.mediafire.com/download/oa2sjlvrecx0wdn/recovery-ra-vigor-3.16-gnm.img.zip
Extract the recovery img
Put it in the adb folder
Load into fastboot
Open up the terminal
Put "cd" then hit space
Drag and drop the adb folder into the terminal window then hit enter
Now use this command to flash that recovery "fastboot flash recovery recovery.img" (without the quotation marks)
Now go into recovery Find "format data system cache ect."
Go to format all to ext3 once that is done hit return
Flash your prefered rom from the flash menu and all that
Once you are done return to the main menu and go to "developer menu"
Then reboot to bootloader
Now go into your rom that you downloaded on your pc and find the rom now open it and get the boot.img
Copy the boot.img file to your adb folder
Open up terminal again and this time use the command "fastboot flash boot boot.img" in terminal its going to say sending then writing usually takes a couple of seconds
now just go to the reboot option and your rom should work
Now remember that since you are s on you need to get the boot.img file from EVERY rom you install and flash it thru the terminal in order to get your rom working

xkjonathanxk said:
Im assuming you already have adb installed
Download this file
http://www.mediafire.com/download/oa2sjlvrecx0wdn/recovery-ra-vigor-3.16-gnm.img.zip
Extract the recovery img
Put it in the adb folder
Load into fastboot
Open up the terminal
Put "cd" then hit space
Drag and drop the adb folder into the terminal window then hit enter
Now use this command to flash that recovery "fastboot flash recovery recovery.img" (without the quotation marks)
Now go into recovery Find "format data system cache ect."
Go to format all to ext3 once that is done hit return
Flash your prefered rom from the flash menu and all that
Once you are done return to the main menu and go to "developer menu"
Then reboot to bootloader
Now go into your rom that you downloaded on your pc and find the rom now open it and get the boot.img
Copy the boot.img file to your adb folder
Open up terminal again and this time use the command "fastboot flash boot boot.img" in terminal its going to say sending then writing usually takes a couple of seconds
now just go to the reboot option and your rom should work
Now remember that since you are s on you need to get the boot.img file from EVERY rom you install and flash it thru the terminal in order to get your rom working
Click to expand...
Click to collapse
If you are S-ON, you are likely not bricked, it's almost impossible to completely brick when you are S-ON.
Why do people keep telling occasional flashers that are S-ON to do this?!?!? It is the hard way, also don't use Amon Ra, is it outdated and known to cause issues with current ROMs, use TWRP or CWM recovery!!! Also, verify your ROM is specifically for the HTC Rezound, check the Developer threads here and make sure it is stable and widely used unless you really know what you are doing.
Although xkjonathanxk is on the right track, he is making more complicated than it needs to be...
- Download the first link in the first post of this thread and place it on the root of your SD card: [Tool] - 3/24 - CleanWIPE 1.0 - Wipe 5 or 10x before ROM install! - 1heffer Edition! (CleanWIPE formats all the necessary partitions for you, and prepares the phone for a new ROM)
- Download TWRP or CWM Rececovery (one of the first two links in post 1) and extract the recovery*.img and place it in the adb folder that contains fastboot.
- Download a tested and verified ROM of choice and place it on the root of your SD card
- Now, reboot into fastboot, remove battery and hold down Power and Vol Dn, once the menu comes up select Fastboot and press power, connect phone to PC
- In ADB enter the command "fastboot devices", if it shows a device continue, if not report back please
- Now enter the command "fastboot boot recovery.img" and TWRP (or CWM) should open on the device in a few seconds (replace recovery.img with whatever the name of the xxxx.img file is from TWRP or CWM archive)
- Install the CleanWIPE zip from above
- Install ROM zip image
- Reboot and enjoy the goodness
Remember to give the ROM some time to settle down on the first boot, and that the first boot can take a long time, like a painfully wrong "WTF did I do to ruin my device!" long time, but give it a solid 10 minutes before doing anything else.

@acejavelin
acejavelin said:
If you are S-ON, you are likely not bricked, it's almost impossible to completely brick when you are S-ON.
Why do people keep telling occasional flashers that are S-ON to do this?!?!? It is the hard way, also don't use Amon Ra, is it outdated and known to cause issues with current ROMs, use TWRP or CWM recovery!!! Also, verify your ROM is specifically for the HTC Rezound, check the Developer threads here and make sure it is stable and widely used unless you really know what you are doing.
Although xkjonathanxk is on the right track, he is making more complicated than it needs to be...
- Download the first link in the first post of this thread and place it on the root of your SD card: [Tool] - 3/24 - CleanWIPE 1.0 - Wipe 5 or 10x before ROM install! - 1heffer Edition! (CleanWIPE formats all the necessary partitions for you, and prepares the phone for a new ROM)
- Download TWRP or CWM Rececovery (one of the first two links in post 1) and extract the recovery*.img and place it in the adb folder that contains fastboot.
- Download a tested and verified ROM of choice and place it on the root of your SD card
- Now, reboot into fastboot, remove battery and hold down Power and Vol Dn, once the menu comes up select Fastboot and press power, connect phone to PC
- In ADB enter the command "fastboot devices", if it shows a device continue, if not report back please
- Now enter the command "fastboot boot recovery.img" and TWRP (or CWM) should open on the device in a few seconds (replace recovery.img with whatever the name of the xxxx.img file is from TWRP or CWM archive)
- Install the CleanWIPE zip from above
- Install ROM zip image
- Reboot and enjoy the goodness
Remember to give the ROM some time to settle down on the first boot, and that the first boot can take a long time, like a painfully wrong "WTF did I do to ruin my device!" long time, but give it a solid 10 minutes before doing anything else.
Click to expand...
Click to collapse
I really appreciate your help and everything. So i thank you. But Like i said im running windows 8, it wont detect my rezound or my sd card, the only time the pc is able to detect the sd card is when im able to mount my sd card to CWM. But it really wont detect it.... help me again

Multidex24 said:
I really appreciate your help and everything. So i thank you. But Like i said im running windows 8, it wont detect my rezound or my sd card, the only time the pc is able to detect the sd card is when im able to mount my sd card to CWM. But it really wont detect it.... help me again
Click to expand...
Click to collapse
Ubuntu Live CD... Windows not required.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app

Dont know how to work ubuntu.. help again
acejavelin said:
Ubuntu Live CD... Windows not required.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
Click to expand...
Click to collapse
lol its the good thing i know how to make a dual os between win8 and ubuntu, but heres another problem, i dont even know how to work ubuntu...
i think my pc can detect the rezound. But idek how to work ubuntu, plzzzz help!!

Multidex24 said:
lol its the good thing i know how to make a dual os between win8 and ubuntu, but heres another problem, i dont even know how to work ubuntu...
i think my pc can detect the rezound. But idek how to work ubuntu, plzzzz help!!
Click to expand...
Click to collapse
For the things you need to do, its not much different than Windows. Download and install adb, copy images to same places, and the commands are pretty much the same. If you can dualboot you obviously have some knowledge of such things.
If this is all do difficult, just grab a thumb drive, put mini-adb, recovery.img, and your ROM on it and go to a buddies computer with Win7 for 20 minutes and get it done that way.
I know this seems like a huge, potentially fatal problem, but it is minor...
Another thought I had... Download TWRP, go into CWM recovery and copy the TWRP file and ROM to the sd card, and FLASH TWRP recovery ZIP with CWM recovery, reboot into recovery and you will then be on TWRP and you can use TWRP's HTC Dumlock to flash the ROM and the boot.img without a PC at all... In theory, it should work.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app

[Q] No android-info.txt & android-product.txt ~I Need Help~

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.

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.

Better Mobile App

welcome