Related
i was rooting my htc one x that when well when i tried to flash a rom to it i somehow deleted everything stock os everything i can still get to the bootloader and root screen please some one help me get my phone back and working again??????
What hboot do u have 1.14?
---------- Post added at 12:30 AM ---------- Previous post was at 12:30 AM ----------
And don't worry your phone isn't close to being bricked :victory:
If you want to return to stock unrooted just lock the bootloader via fastboot and install the ruu for your device.
boot into bootloader, run "fastboot oem lock", then run the ruu afterwards
I'm sure someone can provide you your devices ruu download, just be patient.. or if you want a rom installed I'm pretty sure you have to install the boot.IMG first then rom after that after clearing caches.
what is a ruu and can someone give me a step by step process im using the bootloader from onexroot.com i have hboot 1.14 yes
im using team win recovery project v2.3.1.0
The reason your phone didn't boot up all the way was because 1 you flashed wrong Rom or 2 you dint flash the boot IMG separately because your on hboot 1.14
---------- Post added at 02:22 AM ---------- Previous post was at 02:21 AM ----------
Do. you know how to flash the boot IMG through fastboot?
omario8484 said:
The reason your phone didn't boot up all the way was because 1 you flashed wrong Rom or 2 you dint flash the boot IMG separately because your on hboot 1.14
---------- Post added at 02:22 AM ---------- Previous post was at 02:21 AM ----------
Do. you know how to flash the boot IMG through fastboot?
Click to expand...
Click to collapse
no i do not i just downloaded the ruu file
C:\Users\NJHCphotography2012>fastboot erase cache
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
this is a message i am currently getting so i think this is hindering me from recovery any solutions?
If u want to run the ruu go into fastboot from there in command prompt type fastboot OEM lock
Locks your bootloader than go into bl mode and run the ruu... But al you have to do is flash the boot IMG from the Rom and your device will be functional and running that Rom you should read a bit.more
omario8484 said:
If u want to run the ruu go into fastboot from there in command prompt type fastboot OEM lock
Locks your bootloader than go into bl mode and run the ruu... But al you have to do is flash the boot IMG from the Rom and your device will be functional and running that Rom you should read a bit.more
Click to expand...
Click to collapse
C:\Users\NJHCphotography2012>fastboot OEM lock
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
im still getting this message in the command prompt when i try to do it
randyarenz said:
im still getting this message in the command prompt when i try to do it
Click to expand...
Click to collapse
Whoa, there, slow down, hoss.
It's obvious from this thread that you're in way over your head. You should not even be rooting before you even know what a RUU or bootloader is, or how to run fastboot correctly.
First, make sure you have the HTC drivers installed on your computer.
Second, you have to run the command in command prompt from the same directory that you put fastboot.exe.
When you relock and run the RUU, you will be stock, locked, and unrooted. Stay there until you've done a lot more reading and understand what it is you're doing to your phone.
Also, stay away from onexroot.com, which is mainly for the international version. Stuff from there may brick your phone.
iElvis said:
Whoa, there, slow down, hoss.
First, make sure you have the HTC drivers installed on your computer.
Second, you have to run the command in command prompt from the same directory that you put fastboot.exe.
Click to expand...
Click to collapse
Should've said that too thanks for putting that out there
I have a feeling he doesn't even have the sdk installed..... If you do OP open the folder where your android sdk platform-tools folder and hold shift on your keyboard right click on your mouse and chose open command prompt here it will open the cmd window where you need to type your commands like the others told you.... GL and please make sure you read and understand everything before doing ANYTHING
Sent from my Nexus 7 using xda app-developers app
Try this tread may be easier for you to lock bootloader.
Just make sure you read carefully
http://forum.xda-developers.com/showthread.php?t=1952426
Make your way to Onex general and find gunnymans quick and dirty adb and fastboot thread. Download adb. extract. RIGHT CLICK ON THE ADB FOLDER and choose "open command prompt here"
Nowwww you can type fastboot oem lock
That will lock bootloader. Now run the ruu, but you have to have HTC sync or it won't work :/
Good luck and have patience
Sent from my One X using Tapatalk 2
Thanks for all the advice my manager helped me out I had everything right except for a working rom
InflatedTitan said:
Make your way to Onex general and find gunnymans quick and dirty adb and fastboot thread. Download adb. extract. RIGHT CLICK ON THE ADB FOLDER and choose "open command prompt here"
Click to expand...
Click to collapse
As an addendum, you will have to hold down the shift key and then right click for the "open command prompt here" option to appear in the context menu.
Ok new help
I've been trying to install new roms I have backups I'm not worried about losing the stuff but when ever I flash the rom it says mdk5 file not found then proceeds and confuses me to boot up but it just stays on the rom screen and doesn't do anything I know that's because the mdk5 file is needed to run it I'm using viperxl and I also have a clean Rom that works and thoughts? Or aybe missing a step or not getting the right download for the rom? Thanks in advance.
randyarenz said:
I've been trying to install new roms I have backups I'm not worried about losing the stuff but when ever I flash the rom it says mdk5 file not found then proceeds and confuses me to boot up but it just stays on the rom screen and doesn't do anything I know that's because the mdk5 file is needed to run it I'm using viperxl and I also have a clean Rom that works and thoughts? Or aybe missing a step or not getting the right download for the rom? Thanks in advance.
Click to expand...
Click to collapse
I'm also using twrp recovery if that helps
i do this in winxp might work on any windows os.
make a file named "install adb fastboot.bat"
add these lines to it then save and run, if you are in vista/7/8 run as admin.
@echo off
cls
copy adb.exe %systemroot%\system32\
copy AdbWinApi.dll %systemroot%\system32\
copy AdbWinUsbApi.dll %systemroot%\system32\
copy fastboot.exe %systemroot%\system32\
pause
exit
make sure those 4 files are in the same folder when you run the .bat file
this will allow you to use adb/fastboot from anywhere you open the command prompt
I did the HTC One X All in one root and I then downloaded Jellybam and put it on the root of my storage. I booted into recovery and wiped the cache. Thats where I think I went wrong by only wiping the cache. Now I just need to figure out how I can get back into the bootloader as I'm stuck in a boot loop. Any help would be appreciated.
Luminate7s said:
I did the HTC One X All in one root and I then downloaded Jellybam and put it on the root of my storage. I booted into recovery and wiped the cache. Thats where I think I went wrong by only wiping the cache. Now I just need to figure out how I can get back into the bootloader as I'm stuck in a boot loop. Any help would be appreciated.
Click to expand...
Click to collapse
Power off the phone, hold the power button and the phone will shut down... Press the volume- and power, boot in bootloader and select recovery, boot in recovery and wipe dalvik, cache and factory reset... Reflash jellybam... If your hboot is 1.14 and your phone is s-on you need to manually flash the boot.img, extract de zip of jellybam find the boot.img, put on your fastboot directory and use the command fastboot flash boot boot.img
atileto said:
Power off the phone, hold the power button and the phone will shut down... Press the volume- and power, boot in bootloader and select recovery, boot in recovery and wipe dalvik, cache and factory reset... Reflash jellybam... If your hboot is 1.14 and your phone is s-on you need to manually flash the boot.img, extract de zip of jellybam find the boot.img, put on your fastboot directory and use the command fastboot flash boot boot.img
Click to expand...
Click to collapse
My phone doesn'tt show up on my computer but I can still put it into bootloader and such through it so how can I extract the zip. And yes my device is s-on and it's h-boot 1.140002 or something like that.
What hboot r u on?
a box of kittens said:
What hboot r u on?
Click to expand...
Click to collapse
1.140002
So you're going to need to do a number of steps
Download the Rom you had wanted to flash on your comp
Extract the boot.img from the zip by opening the zip
Get your phone into fastboot mode(I'll post a tutorial on how to flash the boot.img in a sec)
After you have flashed the boot.img go into recovery and do a factory reset and flash the Rom again
Luminate7s said:
1.140002
Click to expand...
Click to collapse
Dowload the Rom in your computer or boot in recovery and mount the phone to the pc and transfer Rom.zip to the pc and extract it and find the boot.img
Hhttp://forum.xda-developers.com/show....php?t=1671237
Flashing boot img through fastboot...
download the file in the link which above which will include adb and fastboot....put that on your computer somewhere you can find it.. now take the boot image out of the Rom zip and place it in that folder... Boot your phone into bootloader scroll down and select fastboot and now open a command prompt with in the fastbootbadb folder on your comp and type to command without the quotes "fastboot flash boot boot.img"...now go wipe in recovery and install the Rom it doesn't matter if you keep the boot img in the Rom zip or not
a box of kittens said:
So you're going to need to do a number of steps
Download the Rom you had wanted to flash on your comp
Extract the boot.img from the zip by opening the zip
Get your phone into fastboot mode(I'll post a tutorial on how to flash the boot.img in a sec)
After you have flashed the boot.img go into recovery and do a factory reset and flash the Rom again
Click to expand...
Click to collapse
My phone won't show up on my computer under devices with removable storage so how can i get the boot.img out of the zip and put it on my phone? Also under my bootloader it says ***Tampered** so idk if that's bad or not.
Did you not read? ....download it on your computer.....
a box of kittens said:
Did you not read? ....download it on your computer.....
Click to expand...
Click to collapse
It is on my computer
Ok so follow the directions I gave you. Look at my other post
a box of kittens said:
Hhttp://forum.xda-developers.com/show....php?t=1671237
Flashing boot img through fastboot...
download the file in the link which above which will include adb and fastboot....put that on your computer somewhere you can find it.. now take the boot image out of the Rom zip and place it in that folder... Boot your phone into bootloader scroll down and select fastboot and now open a command prompt with in the fastbootbadb folder on your comp and type to command without the quotes "fastboot flash boot boot.img"...now go wipe in recovery and install the Rom it doesn't matter if you keep the boot img in the Rom zip or not
Click to expand...
Click to collapse
Theres a million links in that thread how do i find right file with adb
Luminate7s said:
Theres a million links in that thread how do i find right file with adb
Click to expand...
Click to collapse
Oops sorry I'll give you the right dl
---------- Post added at 06:27 AM ---------- Previous post was at 06:26 AM ----------
http://forum.xda-developers.com/attachment.php?attachmentid=1179735&d=1344782533
a box of kittens said:
Oops sorry I'll give you the right dl
---------- Post added at 06:27 AM ---------- Previous post was at 06:26 AM ----------
http://forum.xda-developers.com/attachment.php?attachmentid=1179735&d=1344782533
Click to expand...
Click to collapse
how do i open cmd within the fastboot folder
Basic computer knowledge... I'll let you Google that... I've done my share here I hope your phone gets better and your thanks button gets fixed
a box of kittens said:
Basic computer knowledge... I'll let you Google that... I've done my share here I hope your phone gets better and your thanks button gets fixed
Click to expand...
Click to collapse
I added the adb folder to my system variables and when i typed the code in its says ''error could not load 'boot.img' ''
So just place the adb folder somewhere on your desktop...put the boot.img inside of there.. make sure your phone is in fastboot...make sure you open the command prompt within the directory usually shift key+ right click and you'll see a option to open one... Than type the command I told you too
a box of kittens said:
So just place the adb folder somewhere on your desktop...put the boot.img inside of there.. make sure your phone is in fastboot...make sure you open the command prompt within the directory usually shift key+ right click and you'll see a option to open one... Than type the command I told you too
Click to expand...
Click to collapse
Ok I flashed the boot.img so now do i just go to recovery and flash the rom?
EDIT: Wiped dalvik and cache, did a fr and phones booting up thanks I really appreciate it.
Luminate7s said:
Ok I flashed the boot.img so now do i just go to recovery and flash the rom?
Click to expand...
Click to collapse
Do a factory reset in recovery(tip never do a factory reset from bootloader) than flash the Rom than you should be good to go
Hi, if anyone can help me solve this, I will be eternally grateful.
So I was following the CyanogenMod guide for installing the ROM on my HTC One S, but I foolishly flashed the ROM as a .zip, instead of the boot.img.
I can access the bootloader screen, and also the TeamWin recovery screen, but I cannot seem to use flashboot.
It always comes up as <waiting on device>.
I am lost, because I obviously used flashboot to flash the recovery and the ROM across to my phone, and all the files are still in the same folder.
Basically, I cannot start my phone, other than into the recovery screen or the bootloader screen. I cannot seem to flash anything across either.
If anyone can solve this issue from this poor explanation I will be more than impressed.
Many thanks.
trentarmy said:
Hi, if anyone can help me solve this, I will be eternally grateful.
So I was following the CyanogenMod guide for installing the ROM on my HTC One S, but I foolishly flashed the ROM as a .zip, instead of the boot.img.
I can access the bootloader screen, and also the TeamWin recovery screen, but I cannot seem to use flashboot.
It always comes up as <waiting on device>.
I am lost, because I obviously used flashboot to flash the recovery and the ROM across to my phone, and all the files are still in the same folder.
Basically, I cannot start my phone, other than into the recovery screen or the bootloader screen. I cannot seem to flash anything across either.
If anyone can solve this issue from this poor explanation I will be more than impressed.
Many thanks.
Click to expand...
Click to collapse
It is waiting for device because the phone isn't in bootloader (fastboot USB) connected to pc...most likely.
So with phone in bootloader and it reads fastboot USB
from your fastboot folder press shift and right click to open command window.
fastboot flash boot boot.img
(this assumes you have put the boot.img in the fastboot folder)
Then go to recovery
install rom.zip
wipe the caches
If you don't have the rom.zip on your phone then mount usb storage in twrp and move the rom.zip from your pc to your phone.
Hopefully your Hboot is 2.15 or you will just bootloop.
tivofool said:
It is waiting for device because the phone isn't in bootloader (fastboot USB) connected to pc...most likely.
So with phone in bootloader and it reads fastboot USB
from your fastboot folder press shift and right click to open command window.
fastboot flash boot boot.img
(this assumes you have put the boot.img in the fastboot folder)
Then go to recovery
install rom.zip
wipe the caches
If you don't have the rom.zip on your phone then mount usb storage in twrp and move the rom.zip from your pc to your phone.
Hopefully your Hboot is 2.15 or you will just bootloop.
Click to expand...
Click to collapse
So can I clarify that I need to flash both the boot.img file and the rom.zip separately. Then install the rom.zip, not the boot.img?
Because I install the rom.zip last time without the boot.img being flash, and thats when it messed up.
Basically, am I installing the .zip or the .img?
Thanks a million.
trentarmy said:
So can I clarify that I need to flash both the boot.img file and the rom.zip separately. Then install the rom.zip, not the boot.img?
Because I install the rom.zip last time without the boot.img being flash, and thats when it messed up.
Basically, am I installing the .zip or the .img?
Thanks a million.
Click to expand...
Click to collapse
.img , you need to extract boot.img from ROM zip and than just "fastboot flash boot boot.img" ,no quotes in command -that is for boot.img and you do flash ROM as a zip
luxandroid said:
.img , you need to extract boot.img from ROM zip and than just "fastboot flash boot boot.img" ,no quotes in command -that is for boot.img and you do flash ROM as a zip
Click to expand...
Click to collapse
Thanks!
Next issue. I have flashed the boot.img to the phone, now I need to get the rom.zip onto the phone.
Everytime I click mount on TWRP, my computer tells me that I must format the disk before I can use it.
I can't seem to use adb, I always get "no device found".
Any ideas?
adb push ROM.zip /sdcard ,ROM needs to be in fastboot folder, are U s-off or s- on ,did U flash ROM zip before soft brick, can U see files from TWRP when U go to install from sd...some info that is important,if all fails think you'll have to run RUU to fix memory partitions
Sent from my HTC One S using XDA Premium 4 mobile app
luxandroid said:
adb push ROM.zip /sdcard ,ROM needs to be in fastboot folder, are U s-off or s- on ,did U flash ROM zip before soft brick, can U see files from TWRP when U go to install from sd...some info that is important,if all fails think you'll have to run RUU to fix memory partitions
Sent from my HTC One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Everything is in the same folder. adb push function still won't work.
I am s-on.
I did flash the rom.zip before the soft-brick, but when it bricked, I wiped the memory and cache, reset to factory settings. So there is currently no files on the phone.
U wiped all this in bootloader ?
Sent from my HTC One S using XDA Premium 4 mobile app
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
Anyway best thing is to flash RUU and do all over again...
Sent from my HTC One S using XDA Premium 4 mobile app
luxandroid said:
U wiped all this in bootloader ?
Sent from my HTC One S using XDA Premium 4 mobile app
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
Anyway best thing is to flash RUU and do all over again...
Sent from my HTC One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I wiped it all via the TWRP recovery.
Any chance you could walk me through RUU? Or at least point me in the right direction.
It does sound like it would be easiest just to start all over again. What's the best way to do this?
Thank you for your help.
trentarmy said:
I wiped it all via the TWRP recovery.
Any chance you could walk me through RUU? Or at least point me in the right direction.
It does sound like it would be easiest just to start all over again. What's the best way to do this?
Thank you for your help.
Click to expand...
Click to collapse
what happened when you tried to push the rom.zip via adb?
ThudButt said:
what happened when you tried to push the rom.zip via adb?
Click to expand...
Click to collapse
I just get "error: device not found"
Any ideas?
If not, could someone please run me through just wiping everything and starting again?
Cheers
luxandroid said:
U wiped all this in bootloader ?
Sent from my HTC One S using XDA Premium 4 mobile app
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
Anyway best thing is to flash RUU and do all over again...
Sent from my HTC One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not sure if this makes a difference, but when connected to my PC, my phone is called "My HTC".
I remember reading somewhere that it should be called an Android ADB Device or something similar?
Okay I was flashing a ROM for the S4 version and the phone began rebooting in the middle of the flash. I realize my error so lets not focus on that Im just trying to fix the boot loop issue. Im trying to use fastboot to fix it but when the phone is connected to my windows 7 PC it makes the connected sound but the device cannot be found by fastboot and it is not shown in the sidebar tree. I cannot get into recovery the TRWP splash screen is displayed for 10 seconds then it goes to the HTC developers use only screen. Please help. Are there any options to repair the damage?
sideshow03 said:
Okay I was flashing a ROM for the S4 version and the phone began rebooting in the middle of the flash. I realize my error so lets not focus on that Im just trying to fix the boot loop issue. Im trying to use fastboot to fix it but when the phone is connected to my windows 7 PC it makes the connected sound but the device cannot be found by fastboot and it is not shown in the sidebar tree. I cannot get into recovery the TRWP splash screen is displayed for 10 seconds then it goes to the HTC developers use only screen. Please help. Are there any options to repair the damage?
Click to expand...
Click to collapse
Okay so can someone confirm then that I am out of luck on this one:?
sideshow03 said:
Okay so can someone confirm then that I am out of luck on this one:?
Click to expand...
Click to collapse
What is device manager showing when your phone is connected to pc while in bootloader (fastboot USB)
for example here is mine:
tivofool said:
What is device manager showing when your phone is connected to pc while in bootloader (fastboot USB)
for example here is mine:
Click to expand...
Click to collapse
It looks the same as yours. But Im not able to connect to the pc to transfer the ROM over. What do I need to do please and thank you?
sideshow03 said:
It looks the same as yours. But Im not able to connect to the pc to transfer the ROM over. What do I need to do please and thank you?
Click to expand...
Click to collapse
well don't give up then, it isn't bricked.
I'm guessing the way you worded it, you have a villeC2 (S3) version and you flashed (S4) ROM? So just make sure you have the S3 version of TWRP flashed and flash a boot.img and rom. wipe caches and you should be fine.
Never mind that if your phone is S4 and I misinterpreted that.
With phone in Bootloader, (fastboot USB) try and check fastboot devices again. Opening your folder with fastboot in it and shift right click, pick open command window.
fastboot devices
(should show a serial #)
flash recovery again, since it was bootlooping. That will probably allow it to be stable again so you can mount USB storage.
If you are in bootloader (fastboot USB) and command window on pc is ran from the correct folder but it still shows device cannot be found then reinstall fastboot drivers. That should fix it for you.
tivofool said:
well don't give up then, it isn't bricked.
I'm guessing the way you worded it, you have a villeC2 (S3) version and you flashed (S4) ROM? So just make sure you have the S3 version of TWRP flashed and flash a boot.img and rom. wipe caches and you should be fine.
Never mind that if your phone is S4 and I misinterpreted that.
With phone in Bootloader, (fastboot USB) try and check fastboot devices again. Opening your folder with fastboot in it and shift right click, pick open command window.
fastboot devices
(should show a serial #)
flash recovery again, since it was bootlooping. That will probably allow it to be stable again so you can mount USB storage.
If you are in bootloader (fastboot USB) and command window on pc is ran from the correct folder but it still shows device cannot be found then reinstall fastboot drivers. That should fix it for you.
Click to expand...
Click to collapse
Im on the S4 variant my error was not flashing the boot.img separately
Im needing to run the cmd as admin so Im opening it up from the start button and changing the directory to the folder fastboot is in. I did get a serial # HT251W408295 fastboot. as shown
Just to confirm my next step is to flash recovery so my command line should be C:\Android fastboot flash recovery twrp2.1.6-ville.img
Correct?
Im using an older twrp cause I read that the newest one is not the best for HTC one S devices.
Thanks
sideshow03 said:
Im on the S4 variant my error was not flashing the boot.img separately
Im needing to run the cmd as admin so Im opening it up from the start button and changing the directory to the folder fastboot is in. I did get a serial # HT251W408295 fastboot. as shown
Just to confirm my next step is to flash recovery so my command line should be C:\Android fastboot flash recovery twrp2.1.6-ville.img
Correct?
Im using an older twrp cause I read that the newest one is not the best for HTC one S devices.
Thanks
Click to expand...
Click to collapse
That would work, BUT:
I see Maximus HD in that pic. For Maximus and any other ROM that uses 2.16 HBoot you can only use the recovery provided in the Maximus original post. It has been modified to work with the new partitions.
If you have moved back to or are still on HBoot 2.15 older firmware, then yes go ahead and flash like you are.
---------- Post added at 07:07 PM ---------- Previous post was at 07:04 PM ----------
oh, and usb storage (mount sd card) will not be available on this new recovery.
Easy way to move a ROM onto the phone while in this recovery is adb push
put ROM.zip in the adb folder and type in command window:
adb push filename.zip /sdcard
tivofool said:
That would work, BUT:
I see Maximus HD in that pic. For Maximus and any other ROM that uses 2.16 HBoot you can only use the recovery provided in the Maximus original post. It has been modified to work with the new partitions.
If you have moved back to or are still on HBoot 2.15 older firmware, then yes go ahead and flash like you are.
---------- Post added at 07:07 PM ---------- Previous post was at 07:04 PM ----------
oh, and usb storage (mount sd card) will not be available on this new recovery.
Easy way to move a ROM onto the phone while in this recovery is adb push
put ROM.zip in the adb folder and type in command window:
adb push filename.zip /sdcard
Click to expand...
Click to collapse
Ok I have both packages now but when I try to flash twrp is shows FAILED (remote: image error! (BootMagic check fail)).
I have verified the md5 with HASHCALC.
Im lost but feel like Im getting somewhere
sideshow03 said:
Ok I have both packages now but when I try to flash twrp is shows FAILED (remote: image error! (BootMagic check fail)).
I have verified the md5 with HASHCALC.
Im lost but feel like Im getting somewhere
Click to expand...
Click to collapse
Is your bootloader locked? Can't install recoveries with locked bootloader.
tivofool said:
Is your bootloader locked? Can't install recoveries with locked bootloader.
Click to expand...
Click to collapse
No I am Unlocked S-off CID 11111111
sideshow03 said:
No I am Unlocked S-off CID 11111111
Click to expand...
Click to collapse
Sorry, you need to extract that zip on your pc and put the recovery.img in your folder. Or I guess just extract it in that same folder you are using.
then depending on the name of the recovery.img flash that. But I think that extracts to recovery.img
so
fastboot flash recovery recovery.img
tivofool said:
Sorry, you need to extract that zip on your pc and put the recovery.img in your folder. Or I guess just extract it in that same folder you are using.
then depending on the name of the recovery.img flash that. But I think that extracts to recovery.img
so
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Ok Ive completed that and the phone went into recovery, i can see the ROM when I click on the install tab. But when I trying to install the ROM i get E: Unable to open zip file Error flashing zip
sideshow03 said:
Ok Ive completed that and the phone went into recovery, i can see the ROM when I click on the install tab. But when I trying to install the ROM i get E: Unable to open zip file Error flashing zip
Click to expand...
Click to collapse
One of the possibilities with that error is a bad download. You may have to redownload the ROM.
Another is if you change the name of the rom, just in case you did that.
Solved
tivofool said:
One of the possibilities with that error is a bad download. You may have to redownload the ROM.
Another is if you change the name of the rom, just in case you did that.
Click to expand...
Click to collapse
Yes it was a bad download. Thanks for all of your help I really appreciate your time to help me get back up and running. :victory:
Q&A for **TWRP** custom recovery for IDOL3 6045
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for **TWRP** custom recovery for IDOL3 6045. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
stuck on twrp bootloop
stuck on twrp boot loop. any suggestions? i followed instructions as posted, but when rebooted into twrp and tried to reboot system, i keep going back to twrp. thanks
Heyy
I have the same problem,, although i did a backup and then a deleted everything cause it was looping,,, how do i fix everything to the original condition,, i won't be doing this again,, my model is an i version.. Although mine is not booting into twrp ,, just the original..
Restoring my backup does not work
I tryed everything,, i know not to do this anymore I think it's broke forever.
If you can get into twrp it can most likely be fixed.
Download the system image and try to install it. May need to put it on sdcard or USB otg.
This is all Alcatel's fault for not releasing anything when we kindly asked...
Where is the system image?
neilownz said:
If you can get into twrp it can most likely be fixed.
Download the system image and try to install it. May need to put it on sdcard or USB otg.
This is all Alcatel's fault for not releasing anything when we kindly asked...
Click to expand...
Click to collapse
---------- Post added at 12:30 AM ---------- Previous post was at 12:20 AM ----------
im in tears (
I believe there's a link in the thread about ota updates after rooting.
http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
Yeah that what i was following and made a backup.. and now my crap is all screwed
I updated another backup from someone but it doesn't notice it,, same model and everything... sighhh
---------- Post added at 02:43 AM ---------- Previous post was at 01:43 AM ----------
TrevBlu19 said:
Yeah that what i was following and made a backup.. and now my crap is all screwed
I updated another backup from someone but it doesn't notice it,, same model and everything... sighhh
Click to expand...
Click to collapse
Trying to make the other guys restore show up.... with my other phone and swapping.. trying to change timestamps...
TrevBlu19 said:
Yeah that what i was following and made a backup.. and now my crap is all screwed
I updated another backup from someone but it doesn't notice it,, same model and everything... sighhh
---------- Post added at 02:43 AM ---------- Previous post was at 01:43 AM ----------
Trying to make the other guys restore show up.... with my other phone and swapping.. trying to change timestamps...
Click to expand...
Click to collapse
Tell us which backup you used and exactly what the path is to where you put it on the phone. Is it in TWRP/BACKUPS? If so, give us the rest of the path. If TWRP's Restore menu is not showing the backup you put on the phone, it's probably (assuming it's there and in the right place) because the folder name that starts with "4" isn't the right one or because it's in the wrong place. If you haven't already done this, from TWRP, make a system image backup. You probably won't use it, but it'll create the directory in which you can put the backup from XDA. It'll have a name that your installation of TWRP can recognize. Then, you can put that unrecognized backup there and it should be seen.
I can't even get into TWRP mode now it reboots too fast now..
maigre said:
Tell us which backup you used and exactly what the path is to where you put it on the phone. Is it in TWRP/BACKUPS? If so, give us the rest of the path. If TWRP's Restore menu is not showing the backup you put on the phone, it's probably (assuming it's there and in the right place) because the folder name that starts with "4" isn't the right one or because it's in the wrong place. If you haven't already done this, from TWRP, make a system image backup. You probably won't use it, but it'll create the directory in which you can put the backup from XDA. It'll have a name that your installation of TWRP can recognize. Then, you can put that unrecognized backup there and it should be seen.
Click to expand...
Click to collapse
You mean it's looping every few seconds? What happens, exactly? Do you get the black logo screen briefly, then it all goes black and comes back again?
Maybe it's worth copying a command like
Code:
adb reboot-bootloader
or, maybe better,
Code:
fastboot reboot bootloader
so that you have it in your clipboard. Then, keep entering them into the command line. You're bound to time it right at some point, at least if it can possibly be done in the state your device is in. You might have to do:
Code:
fastboot -i 0x1bbb reboot-bootloader
If you can get into the bootloader, you should be able to get booted into TWRP from there. Keep in mind that when you do get booted into the bootloader, it won't look like anything distinct. It's just that same black logo screen you see every time you boot up (or loop, probably).
I soft-bricked my 6045i after editing the build.prop and didn't have a backup like a fool. I cannot get the phone to boot at all, stuck on the Alcatel Onetouch boot logo and can't go any further. I have tried to create an update.zip to be able to flash the build.prop thru stock recovery but so far no luck. Each time it would give me an error saying invalid footer, I tried editing the updater-script to match the device but still the error remains and I cannot sideload the update.zip.
Would it be possible for someone to upload a signed update.zip for the 6045i model with only the build.prop for use with adb sideload in stock recovery?
datkevjames said:
I soft-bricked my 6045i after editing the build.prop and didn't have a backup like a fool. I cannot get the phone to boot at all, stuck on the Alcatel Onetouch boot logo and can't go any further. I have tried to create an update.zip to be able to flash the build.prop thru stock recovery but so far no luck. Each time it would give me an error saying invalid footer, I tried editing the updater-script to match the device but still the error remains and I cannot sideload the update.zip.
Would it be possible for someone to upload a signed update.zip for the 6045i model with only the build.prop for use with adb sideload in stock recovery?
Click to expand...
Click to collapse
Flash a stock system rom image from here: http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745/
Important points: A corrupted build.prop should still mean you have adb access to your phone even though it won't finish booting...you can do an "adb reboot bootloader" then fastboot boot twrp and flash one of the stock recoveries.
How do I know this so well? I soft bricked mine for a day by editing the build.prop before TWRP was available.
---------- Post added at 07:42 PM ---------- Previous post was at 07:41 PM ----------
maigre said:
You mean it's looping every few seconds? What happens, exactly? Do you get the black logo screen briefly, then it all goes black and comes back again?
Maybe it's worth copying a command like
Code:
adb reboot-bootloader
or, maybe better,
Code:
fastboot reboot bootloader
so that you have it in your clipboard. Then, keep entering them into the command line. You're bound to time it right at some point, at least if it can possibly be done in the state your device is in. You might have to do:
Code:
fastboot -i 0x1bbb reboot-bootloader
If you can get into the bootloader, you should be able to get booted into TWRP from there. Keep in mind that when you do get booted into the bootloader, it won't look like anything distinct. It's just that same black logo screen you see every time you boot up (or loop, probably).
Click to expand...
Click to collapse
If you can execute fastboot commands, your already in bootloader.
famewolf said:
Flash a stock system rom image from here: http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745/
Important points: A corrupted build.prop should still mean you have adb access to your phone even though it won't finish booting...you can do an "adb reboot bootloader" then fastboot boot twrp and flash one of the stock recoveries.
How do I know this so well? I soft bricked mine for a day by editing the build.prop before TWRP was available.
---------- Post added at 07:42 PM ---------- Previous post was at 07:41 PM ----------
If you can execute fastboot commands, your already in bootloader.
Click to expand...
Click to collapse
Believe me I've already tried. For whatever reason I cannot boot to fastboot, no matter what I try. I go into stock recovery and choose update from adb, when this happens adb gets enabled supposedly. Well when I try doing 'adb reboot-bootloader' it gives me: error: closed, no matter what I do. I've even added the 0x1bbb and same thing. When I try doing fastboot commands it just gives me <waiting for device> and nothing happens.
I either need to flash an update.zip with build.prop or somehow flash an entire image uploaded to the other thread which I'm well aware of.
PS: I've tried all different sorts of adb/fastboot executables as well as multiple adb drivers (Samsung, Motorola, Google etc) even the Alcatel ones provided with their Mobile Upgrade Q app which install more of the phone than any other drivers, I've noticed.
PPS: A handful of times I was able to get a tiny bit further in stock recovery adb sideload mode, of course it was an error: 'you must use adb 1.0.32 to be able to sideload' blah blah and I made sure I was using that version.
PPPS: Is there a 3rd party app I can use to flash the image like odin or rsd lite? I cannot for the life of me get to fastboot to flash the image. Adb devices detects the phone but beyond this I can't do squat.
PPPPS: Phone is rooted and bootloader unlocked. USB debugging enabled iirc although this may be the reason for all the 'error: closed' issues.
Please someone upload a signed flashable zip with build.prop in it for 6045i (USA) model. I love this phone more than my Moto X 2014 (XT1097), that's saying something considering the Moto has more power and smoothness to it.
twrp bootloop
im able to boot into bootloader and also able to get into twrp, but cant fully reboot. i have 6045i and if anybody has any solution to this, i would greatly appreciate it.
datkevjames said:
Believe me I've already tried. For whatever reason I cannot boot to fastboot, no matter what I try. I go into stock recovery and choose update from adb, when this happens adb gets enabled supposedly. Well when I try doing 'adb reboot-bootloader' it gives me: error: closed, no matter what I do. I've even added the 0x1bbb and same thing. When I try doing fastboot commands it just gives me <waiting for device> and nothing happens.
I either need to flash an update.zip with build.prop or somehow flash an entire image uploaded to the other thread which I'm well aware of.
PS: I've tried all different sorts of adb/fastboot executables as well as multiple adb drivers (Samsung, Motorola, Google etc) even the Alcatel ones provided with their Mobile Upgrade Q app which install more of the phone than any other drivers, I've noticed.
PPS: A handful of times I was able to get a tiny bit further in stock recovery adb sideload mode, of course it was an error: 'you must use adb 1.0.32 to be able to sideload' blah blah and I made sure I was using that version.
PPPS: Is there a 3rd party app I can use to flash the image like odin or rsd lite? I cannot for the life of me get to fastboot to flash the image. Adb devices detects the phone but beyond this I can't do squat.
PPPPS: Phone is rooted and bootloader unlocked. USB debugging enabled iirc although this may be the reason for all the 'error: closed' issues.
Please someone upload a signed flashable zip with build.prop in it for 6045i (USA) model. I love this phone more than my Moto X 2014 (XT1097), that's saying something considering the Moto has more power and smoothness to it.
Click to expand...
Click to collapse
There are no install-script and install-binary example files to use to build a signed update.zip because there are no rom's available....maybe someone could build something using the spanish rom just posted but I don't read spanish and they seem to have built it for a 6045Y which isn't gonna help 6045i or 6045K users. If you were running twrp it wouldn't be an issue as twrp allows adb access....stock recovery doesn't..it also doesn't support rebooting to bootloader....if your bootup was "freezing" as a normal build.prop issue would then you should STILL be able to do an "adb reboot bootloader" or an "adb shell" and look around.
datkevjames said:
Believe me I've already tried. For whatever reason I cannot boot to fastboot, no matter what I try. I go into stock recovery and choose update from adb, when this happens adb gets enabled supposedly. Well when I try doing 'adb reboot-bootloader' it gives me: error: closed, no matter what I do. I've even added the 0x1bbb and same thing. When I try doing fastboot commands it just gives me <waiting for device> and nothing happens.
.
Click to expand...
Click to collapse
Try this:
-turn off your phone
-run command line in direcotry where is fastboot and adb.exe
-connect phone to the pc and turn the phone on
-when the phone is booting you will hear a sound that new device is detected from your pc
-in this point type "adb reboo bootloader"
-the phone should reboot to initial screen and stays there
-now you are in bootloader mode and you can flash twrp recovery
-in twrp recovery you can run file manager and copy and delete files, so you can replace the bad build.prop with your backup (you surely have)
---------- Post added at 10:58 AM ---------- Previous post was at 10:50 AM ----------
faresbreech said:
im able to boot into bootloader and also able to get into twrp, but cant fully reboot. i have 6045i and if anybody has any solution to this, i would greatly appreciate it.
Click to expand...
Click to collapse
if you have a problem then:
1- you have to tell what did you do before it happen.
anyway if you can go to TWRP, you can download system Image backup from @famewolf thread HERE, copy it to your sd card and then proceed with restore menu from TWRP. And just check the "system" .
First I rooted phone, then verified through root checker that I was truly rooted. After that I proceeded to flash twrp. Once twrp was flashed, I went to recovery to make a full backup. There I first chose read only and then backed up, but realized that I was limited on performing different actions so I reflashed twrp and this time I chose for twrp to fully work and again preformed another backup. It was when I rebooted system after the second backup when I started looping back to twrp.
I was wondering if maybe there is a terminal command I can execute through twrp to fix this like the LG G2 has. I had a problem like this before on my G2 but after executing the terminal command it would get fixed. Thanks
Sent from my Z987 using XDA Free mobile app
DallasCZ said:
Try this:
-turn off your phone
-run command line in direcotry where is fastboot and adb.exe
-connect phone to the pc and turn the phone on
-when the phone is booting you will hear a sound that new device is detected from your pc
-in this point type "adb reboo bootloader"
-the phone should reboot to initial screen and stays there
-now you are in bootloader mode and you can flash twrp recovery
-in twrp recovery you can run file manager and copy and delete files, so you can replace the bad build.prop with your backup (you surely have)
Click to expand...
Click to collapse
I tried spamming 'adb reboot-bootloader' as fast as possible, but apparently I didn't authorize my computer. ADB gives me this: error: device unauthorized. Please check the confirmation dialog on your device. ffs. Now what? I do appreciate all help. I am savvy enough to try to solve this on my own but any helpful advice would be awesome.