Related
My MT4GS is boot looping. I can get into the bootloader, but can't get into recovery and flashing a stock image doesn't do anything. I've unlocked the phone and achieved S-OFF using the j-bear wire trick. I've ran the phone for a few weeks after getting the s-off, so I don't think it's that. When I flash a stock image from the bootloader, the software/radio versions don't change and it still boot loops. I also have a faint red light in the notification and trackpad. I'm out of ideas. Anyone have any suggestions?
well first thing id attempt is to grab an image of a recovery and try and flash it through fastboot, image HERE
fastboot command
Code:
fastboot flash recovery recovery.img
if you need any further instruction on how to use fastboot you can get some info HERE
or if this dosent work or have more questions feel free to ask
its not a brick if you can get into hboot, you may have a tough time getting your phone working again but usually its doable.
good luck!
Thanks for the quick reply. I did a recovery flash through fastboot (CWM 5.0.2.7), but still couldn't get to recovery. I was able to update hboot to the jb_hboot. That allowed me to perform some more fastboot commands, such as: erase boot, recovery, system, userdata. I then tried to flashed a signed stock image, but still got stuck at boot loop and couldn't get into recovery. I might try TWRP recovery to see if it changes anything.
what all does it say on your bootloader screen now?
It says:
= Juopunut Bear =
DOUBLESHOT PVT SHIP S-OFF RL
HBOOT-1.45.1313
RADIO-11.16.3504.20_2
eMMC-boot
Nov 21 2011, 20:20:47
Well it let you write to the emmc so that's a good sign. Did it give you an error in fastboot? Or did it say completed in .9 sec or something like that?
What happens when you choose recovery from the bootloader screen? Also have you tried adb reboot-recovery?
Sent from my Desire Z using Tapatalk 2
when you say you cant get to recovery what's basically happening when you boot to recovery? Red triangle on screen? reboot loop? black screen? or what else.
demkantor said:
Well it let you write to the emmc so that's a good sign. Did it give you an error in fastboot? Or did it say completed in .9 sec or something like that?
What happens when you choose recovery from the bootloader screen? Also have you tried adb reboot-recovery?
Sent from my Desire Z using Tapatalk 2
Click to expand...
Click to collapse
Riyal said:
when you say you cant get to recovery what's basically happening when you boot to recovery? Red triangle on screen? reboot loop? black screen? or what else.
Click to expand...
Click to collapse
I didn't get a fastboot error when I wrote to boot, it said completed and a time. When I choose recovery, I get a boot loop. I can't connect via adb. I don't think I have the right drivers setup for adb because when I type "adb remount" it says no device found.
Drivers taken from weekendsr2shorts mirror thread
it is strange that you can get fastboot working but not adb, but maybe more digging needs to be done to solve that. but it could just be from hboot screen there is no access to adb... come to think of it that sounds normal
try erasing recovery partition and flashing again, maybe there is some corruption there that stuck around even after the last flash
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot-bootloader
see if any of that works
Erasing and flashing recovery still resulted in a boot loop. How can I find out if there is a corruption in flash?
Not too sure a great way of telling, maybe try reformatting recovery? On a side note what exactly were the stock image you were trying to flash? I believe there is an issue when flashing certain stock setups after the radio s-off, being the way bootloader varifies the radio, recovery, Rom, etc. Sometimes things can go awry when doing this. I don't have a ds yet (still waiting on stupid parts from China) so I haven't done a whole lot of research on this phone. Maybe someone will chime in who knows more specifically what to be looking for
Sent from my Desire Z using xda premium
I tried to flash both "PG59IMG_Doubleshot_TMOUS_1.55.531.3_Radio_11.59.3504.00_11.16.3504.20_2_release_227956_signed" and "PG59IMG_Doubleshot_TMOUS_1.63.531.2_Radio_11.59.3504.00_11.16.3504.20_2_release_245247_signed". You think I should try a custom ROM instead? Is there one available to flash through the bootloader or fastboot? I tried to flash the signed stock image zips with fastboot, but it complained about not finding expected signature. Sorry to hear about your DS. Hope you get your parts soon.
rumi409 said:
Erasing and flashing recovery still resulted in a boot loop. How can I find out if there is a corruption in flash?
Click to expand...
Click to collapse
Here's a copy of my "platform-tools" files. They've always been flawless for me. You can also take the PG59IMG file and rename it to JUST PG59IMG.zip, put it in the root directory of your SD card and reboot and see if your bootloader will load it for you.
**you'll need to get a recovery operational before you can move on to custom ROMs. Edit: UNLESS you want to use Update.zip (See demkantor's post below.....)
This IS assuming that the main files you're running thru ADB have no corruption issues though.
Well you can flash roms through fastboot,
fastboot update.zip
Just change the name of the Rom to what's needed
Maybe try to format as many partitions as you can through fastboot first?
Sent from my Desire Z using xda premium
WeekendsR2Short said:
Here's a copy of my "platform-tools" files. They've always been flawless for me. You can also take the PG59IMG file and rename it to JUST PG59IMG.zip, put it in the root directory of your SD card and reboot and see if your bootloader will load it for you.
**you'll need to get a recovery operational before you can move on to custom ROMs. Edit: UNLESS you want to use Update.zip (See demkantor's post below.....)
This IS assuming that the main files you're running thru ADB have no corruption issues though.
Click to expand...
Click to collapse
I flashed this recovery image via the bootloader and fastboot. Still no luck. Is erase and format the same thing? I've erased boot, recovery and system. I checked that they were erased by doing a Image CRC, which resulted in a 0 value. Then flashed the signed DS ROMs. It still resulted in the same, boot loop.
erasing will wipe out whats in the partition, formatting will get rid of the partition and replace it with a new one. so think of it as a super eraser sorta
fastboot format recovery
but you can also see if any of this helps but im not too sure it would
fastboot format system
fastboot fromat boot
fastboot format userdata
fastboot format cache
also you can do a fastboot oem format, never done this but my understanding is it will reformat most partitions for you, and something is nagging me about this one and i just cant remember, ill do some googleing and get back on that, although im not sure if any of this will help too much in your situation
demkantor said:
erasing will wipe out whats in the partition, formatting will get rid of the partition and replace it with a new one. so think of it as a super eraser sorta
fastboot format recovery
but you can also see if any of this helps but im not too sure it would
fastboot format system
fastboot fromat boot
fastboot format userdata
fastboot format cache
also you can do a fastboot oem format, never done this but my understanding is it will reformat most partitions for you, and something is nagging me about this one and i just cant remember, ill do some googleing and get back on that, although im not sure if any of this will help too much in your situation
Click to expand...
Click to collapse
I can't seem to get any of the format commands to work. It just displays the fastboot commands and options, as if I typed something it can't understand.
Have you tried a different SD card?
mattlowry said:
Have you tried a different SD card?
Click to expand...
Click to collapse
I'm not using a micro sd card. Have been flashing through the computer.
rumi409 said:
I'm not using a micro sd card. Have been flashing through the computer.
Click to expand...
Click to collapse
have you tried placing the pg file on your sd card and let the bootloder load it itself?
Hi Everyone,
So i followed all the steps to temp root 2.20 including successfully installing TWRP (Team Win Recovery Project). I then downloaded the CM10 rom and extracted the boot.img as per posts and rebooted into the bootloader and flashed the boot.img from CM10 via Fastboot. However after doing then rebooting to Recovery mode in order to flash the ROM, i get stuck in the red text where it gives you a warning about it being in development mode or something.
I am able to successfully boot into the bootloader via Power+down volume. Additionally I am able to boot into the TWRP recovery just fine, however I am lost and have no clue how to restore my phone to either the CM10 ROM or most importantly at least to stock working condition.
When i got to mount the SDCARD via twrp normally i would get a pop up on my screen and allow me to access my SD card, now i get a pop up just telling me that i need to format my SD card first. I'm afraid some how my SD card got wiped or something.
Can someone please walk me through the steps on how to restore my phone. Please if possible i would appreciate using LAME terms as i do not have any experience as you can tell i screwed up :/ Can you please listed step by step instructions including commands for Fastboot/adb etc etc if needed. Thank you very much for your help and support.
I've typed and retyped a response to help. I'm so tired and my brain is mush. (More so than normal) if you can't find any resolution by morning? Pm me and I'll try and help. Something about pluggin the USB in The back of your pc something something....... snore
Sent from my One X using xda premium
subarudroid said:
I've typed and retyped a response to help. I'm so tired and my brain is mush. (More so than normal) if you can't find any resolution by morning? Pm me and I'll try and help. Something about pluggin the USB in The back of your pc something something....... snore
Sent from my One X using xda premium
Click to expand...
Click to collapse
I know you tried to help, but it appears now I have bricked the phone. Hopefully i can fix it as i still have access to Bootloader and TWRP recovery. I'll PM you in the morning, thank you.
dont factory reset in bootloader. only factory reset in twrp. sometimes evita has a hard time getting into recovery from bootloader. just keep trying to get into recovery from bootloader. also even if your phone doesn't boot all the way adb sometimes still works. so try "adb reboot recovery" while its trying to boot.
if you did corrupt your sdcard try this method to get it fixed without having to run ruu.
[How to] Fix corrupt/unmountable internal storage on the HTC One X/XL
when you get your sdcard fixed remember to wipe everything and then copy cm10 and gapps to your sdcard and flash. since boot.img is already flashed you shouldn't need to do it again.
you did flash boot.img as "fastboot flash boot boot.img"? i made the mistake of flashing boot.img to recovery instead of boot. i was freaking out. just to make sure flash recovery again "fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img"
DvineLord said:
dont factory reset in bootloader. only factory reset in twrp. sometimes evita has a hard time getting into recovery from bootloader. just keep trying to get into recovery from bootloader. also even if your phone doesn't boot all the way adb sometimes still works. so try "adb reboot recovery" while its trying to boot.
if you did corrupt your sdcard try this method to get it fixed without having to run ruu.
[How to] Fix corrupt/unmountable internal storage on the HTC One X/XL
when you get your sdcard fixed remember to wipe everything and then copy cm10 and gapps to your sdcard and flash. since boot.img is already flashed you shouldn't need to do it again.
you did flash boot.img as "fastboot flash boot boot.img"? i made the mistake of flashing boot.img to recovery instead of boot. i was freaking out. just to make sure flash recovery again "fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img"
Click to expand...
Click to collapse
Yes i did fastboot flash boot boot.img from within the Bootlader. FYI that boot.img was from inside the CM10 zip file. I belive my SD card is corrupt i will check out that link. FYI I am able to get into Recovery mode form the Boatloader if i chooser recovery. However since the SD card seems messed up i can't access it currently. Also I tried to use the method to install the CM10.zip file using TWRP recovery. That recovery has a GUI and you can click on the INSTALL button and choose the zip file you want to install, however it errors out.
What is the proper way to flash a rom when i am in the TWRP recovery? Can you provide me with the commands/steps? Thanks for all your support guys.
movadoevo8 said:
Yes i did fastboot flash boot boot.img from within the Bootlader. FYI that boot.img was from inside the CM10 zip file. I belive my SD card is corrupt i will check out that link. FYI I am able to get into Recovery mode form the Boatloader if i chooser recovery. However since the SD card seems messed up i can't access it currently. Also I tried to use the method to install the CM10.zip file using TWRP recovery. That recovery has a GUI and you can click on the INSTALL button and choose the zip file you want to install, however it errors out.
What is the proper way to flash a rom when i am in the TWRP recovery? Can you provide me with the commands/steps? Thanks for all your support guys.
Click to expand...
Click to collapse
install/install from zip/browse to your zip/slide to flash (they really should patent that)
now most of us, to do a clean flash, we'd go into the "wipe" menu in TWRP before flashing , factory reset, wipe cache, wipe dalvik cache, wipe system. then we flash our rom.
hope that cleared it up!
Sent from my One X using xda premium
You won't be able to flash anything until you fixed your sdcard using the method in that link.
Ptesmoke where have you been? DvineLord is the only one been helping here. The Q&A thread is a mess. where is edditsync chongo, rohan and the other superhero's. I feel like Hawkeye trying to shoot sh#@ down with a bow and arrow. Waiting for ironman, hulk, Thor and the other avengers to get real sh#@ done. I'm tired going to sleep now.
Sent from my One X using xda premium
ptesmoke said:
install/install from zip/browse to your zip/slide to flash (they really should patent that)
now most of us, to do a clean flash, we'd go into the "wipe" menu in TWRP before flashing , factory reset, wipe cache, wipe dalvik cache, wipe system. then we flash our rom.
hope that cleared it up!
Sent from my One X using xda premium
Click to expand...
Click to collapse
I tried to fixed corrupted SD card as per video. however after flashing the recovery.img via fastboot when it wants me to do a factory reset instead of doing the factory reset it just goes back to the HTC brilliant screen with the red warning text and sits there. If i go to twpr recovery and click on install i can't access me zip currently due to sd card issues.
Is there a way to format via PC since it lets me as long as I am in twpr and just put stock files/folders onto the SD card? Or is it possible to install the 2.20 ruu again? I re-downloaded it form HTC's site while I am in twrp however I cannot install it won't detect my phone. Thanks for your help.
"fastboot oem lock" then run ruu. ruu gets run in fastboot.
after the ruu, reunlock bootloader and flash twrp, copy cm10 and gapps to your sdcard, flash boot.img in fastboot, wipe everything except for external storage in twrp, flash cm10 and gapps in twrp, then reboot.
If you can get into twrp and go to mount, mount usb storage and connect your phone windows should prompt you to format the SD card.
Once that's done you can drag and drop the rom you want to flash then boot into fastboot and flash the boot.img.
If you want to run the ruu you need to relock the bootloader first.
To do that you must go into fastboot usb and then type fastboot oem lock.
Sent from my HTC One XL using xda premium
DvineLord said:
"fastboot oem lock" then run ruu. ruu gets run in fastboot.
after the ruu, reunlock bootloader and flash twrp, copy cm10 and gapps to your sdcard, flash boot.img in fastboot, wipe everything except for external storage in twrp, flash cm10 and gapps in twrp, then reboot.
Click to expand...
Click to collapse
I'm sorry i'm not too tech savy. Can you clarify how to Fastboot OEM lock. Assuming i just need to be in fastboot mode and run a command in command prompt?
Also once that is done how can i run RUU via fastboot? Right now i have HTC RUU for 2.20 from august that i downloaded from their site and not sure how i can have it detect my phone. If you could clarify and explain those steps in Lame terms i would greatly appreciate it, thanks in advance.
movadoevo8 said:
I'm sorry i'm not too tech savy. Can you clarify how to Fastboot OEM lock. Assuming i just need to be in fastboot mode and run a command in command prompt?
Also once that is done how can i run RUU via fastboot? Right now i have HTC RUU for 2.20 from august that i downloaded from their site and not sure how i can have it detect my phone. If you could clarify and explain those steps in Lame terms i would greatly appreciate it, thanks in advance.
Click to expand...
Click to collapse
That's the command you do and the ruu is an exe file so get into fastnoot on your phone from bl and run the ruu after you've locked the bootloader
Thank you both will try that now.
Hey guys thanks for all your help and your support it worked. I had the wrong CM10 file instead of Evita i had the other one :/ That was the issue all along ugh... but all resolved could of not have done it without your support. Thanks!! I can now finally go to bed.. been at it since 10pm, now 3:11am
Maybe you can help me . I'm having the same problem. The problem is, everytime I try to use any fastboot commands, it'll say "waiting for device". I'm stressing out.
marcur12 said:
Maybe you can help me . I'm having the same problem. The problem is, everytime I try to use any fastboot commands, it'll say "waiting for device". I'm stressing out.
Click to expand...
Click to collapse
Make sure you have the right drivers installed, download the latest htc sync from htc's website.
Install HTC sync connect phone and let the drivers install, then make sure you close htc sync from the system tray and try again.
Like DvineLord said below make sure you're in the bootloader then select Fastboot once selected it should say in red writing Fastboot USB.
fastboot only works in bootloader btw
Hit the thanks button for the people helping you fix your boo boos.
If you can type it, click it for them, least you can do in return.
WR
Sent from my HTC One X
Sent from my HTC One XL using Tapatalk 2
Today I flashed the last CleanRom 5.1 then I flashed kernel BeastMode evita 4.4 and the phone has bricked in the screen of HTC. So I did a big mistake, in the bootlloader i am pretty sure I have wiped the phone, now I have no ROM in the phone, and the TWRP will not let me select mount sd card. I have thinking in push the ROM in ADB but sincerely I have no idea how to do that. Actually I´m in the bootloader screen and connected the phone, appearing "Fastboot USB". Could someone kindly tell me what are the orders in the Command Prompt to connect the phone to my pc and push the rom?
The phone was with CM10 ROM, rooted and TWRP provided by a friend who is not available to help me.
BTW sorry for my regular english, I´m from Argentina.
juanfranrod said:
Today I flashed the last CleanRom 5.1 then I flashed kernel BeastMode evita 4.4 and the phone has bricked in the screen of HTC. So I did a big mistake, in the bootlloader i am pretty sure I have wiped the phone, now I have no ROM in the phone, and the TWRP will not let me select mount sd card. I have thinking in push the ROM in ADB but sincerely I have no idea how to do that. Actually I´m in the bootloader screen and connected the phone, appearing "Fastboot USB". Could someone kindly tell me what are the orders in the Command Prompt to connect the phone to my pc and push the rom?
The phone was with CM10 ROM, rooted and TWRP provided by a friend who is not available to help me.
BTW sorry for my regular english, I´m from Argentina.
Click to expand...
Click to collapse
My First advice, relock bootloader and run ruu...If your on the newer hboot don't you have to flash boot.img as well before flashing the rom? Did you wipe cashe and dalvik when you flashed? Did you see if rom first worked before flashing kernel?
WhatTheAndroid? said:
My First advice, relock bootloader and run ruu...If your on the newer hboot don't you have to flash boot.img as well before flashing the rom? Did you wipe cashe and dalvik when you flashed? Did you see if rom first worked before flashing kernel?
Click to expand...
Click to collapse
I have flashed boot.img in the aroma installer of cleanrom. Then I wipe cache and dalvik after flash rom. But I made the mistake of not checking if it worked the ROM before installing the new kernel.. I installed after the rom.
Could you explain me how to relock bootloader and run ruu?
Appreciate your help
juanfranrod said:
I have flashed boot.img in the aroma installer of cleanrom. Then I wipe cache and dalvik after flash rom. But I made the mistake of not checking if it worked the ROM before installing the new kernel.. I installed after the rom.
Could you explain me how to relock bootloader and run ruu?
Appreciate your help
Click to expand...
Click to collapse
I'm sure someone will provide a ruu download based on your phone. Fastboot oem lock command in fastboot to lock bootloader. I would wait though to see if there is still a way to flash Rom and mount your phones sd card.by the way did you create a recovery in twrp of stock rooted version?
You dont need to RUU. I don't know why everyone runs to that.
Open TWRP, mount usb storage.
If you're on windows, it should prompt you to format your sd card. Format it to fat32.
Copy whatever rom you want onto the card.
Install in TWRP.
Dance
He wiped his phone from bootloader... Therefore corrupting his SD card. He could adb push the rom to his card though
Sent from my One X using xda app-developers app
WhatTheAndroid? said:
I'm sure someone will provide a ruu download based on your phone. Fastboot oem lock command in fastboot to lock bootloader. I would wait though to see if there is still a way to flash Rom and mount your phones sd card.by the way did you create a recovery in twrp of stock rooted version?
Click to expand...
Click to collapse
Myrder said:
He wiped his phone from bootloader... Therefore corrupting his SD card. He could adb push the rom to his card though
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Hi, I still cannot solving my problem :/ I locked the phone with the command "fastboot oem lock" in fastboot. Then I downloaded a RUU called htc_one_x_RUU_2.20.502.7_att_us_08022012.exe and I´ve executed the file in fastboot but appears during the installation process an error message that the phone is not connected with the USB cable, when obviously connected.
I have no idea what to do, I tried to check the connections, right now I'm trying to download another RUU apparently compatible, my CID is 11111111 and my HBOOT is 1.09.0000. Can you think of anything else I can do?
juanfranrod said:
Can you think of anything else I can do?
Click to expand...
Click to collapse
Did you reformat your SD card?
iElvis said:
Did you reformat your SD card?
Click to expand...
Click to collapse
Yes, I did it. I will try with another RUU (1.85) and see what happens.. for now I accept suggestions. Thanks
Your hboot is 1.09 which means you need the 1.85 firmware
area51avenger said:
Your hboot is 1.09 which means you need the 1.85 firmware
Click to expand...
Click to collapse
Newer RUU version should still work, but avoiding the 1.14 hboot is a good idea. So I too would recommend getting the 1.85 RUU: http://forum.xda-developers.com/showthread.php?t=1670238
OP should make sure he has the latest HTC drivers installed on the PC, or try re-installing them. Also try a different USB port. I've seen more than a few times on here, where it was simple as the drivers or the USB port.
redpoint73 said:
Newer RUU version should still work, but avoiding the 1.14 hboot is a good idea. So I too would recommend getting the 1.85 RUU: http://forum.xda-developers.com/showthread.php?t=1670238
OP should make sure he has the latest HTC drivers installed on the PC, or try re-installing them. Also try a different USB port. I've seen more than a few times on here, where it was simple as the drivers or the USB port.
Click to expand...
Click to collapse
damn.. now adb devices doesn't show my phone, there is no way to connect the phone to the pc, sooner if I did, I find it very strange
maybe for this reason the install of the RUU 1.85 has failed
This is my screen, and in fastboot, the pc doesnt recognize the phone with the command "adb devices"
please help, im freaking out!
juanfranrod said:
This is my screen, and in fastboot, the pc doesnt recognize the phone with the command "adb devices"
please help, im freaking out!
Click to expand...
Click to collapse
Don't freak out, if your phone can be turned on it can be fixed.are you sure you have done everything they have said? Or have you tried unlocking again wiping and flashing a Rom? Does the computer make those 2 beeps when you plug your phone in?
juanfranrod said:
This is my screen, and in fastboot, the pc doesnt recognize the phone with the command "adb devices"
please help, im freaking out!
Click to expand...
Click to collapse
You can't use adb in fast boot
Use
Fastboot devices
Sent from my HTC One X-
WhatTheAndroid? said:
Don't freak out, if your phone can be turned on it can be fixed.are you sure you have done everything they have said? Or have you tried unlocking again wiping and flashing a Rom? Does the computer make those 2 beeps when you plug your phone in?
Click to expand...
Click to collapse
Ok I unlocked the phone again, and wiped the phone. I tried typing in commands "fastboot flash zip Cleanrom5.zip" and gave me FAILED.. and yes, the computer make the beep (1) when I connect the phone, as a usb sound.
iElvis said:
Did you reformat your SD card?
Click to expand...
Click to collapse
hey iElvis, had not understood exactly where reformatting the SD card, as I did through the recovery and failed, will be the problem?
I have relocked the phone again, and I have tried to run the RUU in fastboot, but the last step in the installation appear an Error 170: Usb Connection Error... sigh
almost a complete day for nothing
juanfranrod said:
I have relocked the phone again, and I have tried to run the RUU in fastboot, but the last step in the installation appear an Error 170: Usb Connection Error... sigh
almost a complete day for nothing
Click to expand...
Click to collapse
This happened to me and I was able to do
fastboot flash recovery recovery.img (using original recovery)
Then reboot into bootloader then fastboot
fastboot boot TWRP.img
Then, once you're in TWRP, you can just flash a rom
Hope it helps! I'm still kinda nooby w/ htc as I was with motorola forever! I got my phone 1 month ago so... yeah
Try it! I was hopeless but I just kept trying!
Good luck!
---------- Post added at 05:48 AM ---------- Previous post was at 05:42 AM ----------
juanfranrod said:
This is my screen, and in fastboot, the pc doesnt recognize the phone with the command "adb devices"
please help, im freaking out!
Click to expand...
Click to collapse
Also, that just means your battery is low.
Just charge the phone while in bootloader overnight.
You should then be able to detect USB
juanfranrod said:
hey iElvis, had not understood exactly where reformatting the SD card, as I did through the recovery and failed, will be the problem?
Click to expand...
Click to collapse
You connect the phone to the PC, select "Mount USB" in TWRP. Then on your PC format the phone's SD card.
HELP TO ALL THE COMMUNITY ASAP!!!
here is the deal, i had the HTC One S Rooted fine, it was working but i tried now to install a custom rom, baked black beans, but now i've downloaded the rom, set it in my HTC, accessed CMW, wiped data, installed from sd, rebooted, went to bootloader, run boot.img on cmd on computer, restarted and now i am getting the HTC Bootloader that states that "This build is for development purporses etc. etc.." now here is the deal guys... i was able to get to bootloader then to recovery, i check the sd files in clockwork recovery and nothing!! all i want now is just stock and try again.. guys.. help???
URGENT!!
therion0 said:
HELP TO ALL THE COMMUNITY ASAP!!!
here is the deal, i had the HTC One S Rooted fine, it was working but i tried now to install a custom rom, baked black beans, but now i've downloaded the rom, set it in my HTC, accessed CMW, wiped data, installed from sd, rebooted, went to bootloader, run boot.img on cmd on computer, restarted and now i am getting the HTC Bootloader that states that "This build is for development purporses etc. etc.." now here is the deal guys... i was able to get to bootloader then to recovery, i check the sd files in clockwork recovery and nothing!! all i want now is just stock and try again.. guys.. help???
URGENT!!
Click to expand...
Click to collapse
CWM cant mount SD you need TWRP for that and a RUU put you back to stock but the bootloader needs relocking. So did you even try booting the rom because the red writing is fine.
you didn't mention it, but you should wipe system and caches as well as data
Not hard brick. you can chose the correct Ruu file and flash it to your phone.... solved your case.
Darknites said:
CWM cant mount SD you need TWRP for that
Click to expand...
Click to collapse
CWM can not mount our sdcard onto your computer over USB.
But it absolutely can mount the sdcard partition onto the root filesystem.
Unless you have the 'unmountable sdcard' problem, for which there is a sticky in Q&A.
My feeling is that the OP didnt mount the sdcard partition. In that case it is normal to see the mount point as an empty folder.
Once it's mounted, you can adb push rom zips to it.
touch of jobo said:
CWM can not mount our sdcard onto your computer over USB.
But it absolutely can mount the sdcard partition onto the root filesystem.
Unless you have the 'unmountable sdcard' problem, for which there is a sticky in Q&A.
My feeling is that the OP didnt mount the sdcard partition. In that case it is normal to see the mount point as an empty folder.
Once it's mounted, you can adb push rom zips to it.
Click to expand...
Click to collapse
Oh right seems a lot work lol, I think I stick to TWRP.
Darknites said:
Oh right seems a lot work lol, I think I stick to TWRP.
Click to expand...
Click to collapse
+1, 2 & 3!
Really don't understand why anyone still uses CWM, I think its just habit with some people.
shadowch31 said:
+1, 2 & 3!
Really don't understand why anyone still uses CWM, I think its just habit with some people.
Click to expand...
Click to collapse
Habit and guides.
I thought I saw a post that mentioned cwm has not kept up to date--not sure
But, I was a slow convert too and very happy with twrp 2.2.2.0
rugmankc said:
I thought I saw a post that mentioned cwm has not kept up to date--not sure
But, I was a slow convert too and very happy with twrp 2.2.2.0
Click to expand...
Click to collapse
I not seen updates but then I not looked and I didn't move over in till it got the usb mount.
when i run the CMD Command prompt adb reboot bootloader I get error: device not found, i was able to flash the boot.img and i got the 2 OKs but i get that error now... what now?
Also, when i go to recovery mode, i don't see any files to install the .zip file of the rom i want to install
therion0 said:
Also, when i go to recovery mode, i don't see any files to install the .zip file of the rom i want to install
Click to expand...
Click to collapse
You lost SD then and best off running a RUU to recover it.
ok i'm lost.. how do i run an RUU to recover it?
therion0 said:
ok i'm lost.. how do i run an RUU to recover it?
Click to expand...
Click to collapse
Download the right RUU for your carrier and location by looking at http://forum.xda-developers.com/showthread.php?t=1543588 and you can get free download at http://www.4shared.com/folder/jKN2qjTl/HTC_Ville_RUU_Collection.html
Then plug in your phone and follow the instructions when you run the RUU .exe file.
AKToronto
but everytime i try to run it, it says it fails because the phone it is not connected to the computer but it is...
did you ever try to boot into the rom after you flashed it and boot image as in just tapping on reboot system
can you plug phone into pc and get indicator at top of screen that says you are connected. then pull down notification bar and select to mount drive
if so, does it show you your sdcard in the windows screen
you do have an S4 device and assume you are hboot .13 or higher
if you can get into os and see sdcard, you can get twrp and flash image gui and flash rom and boot image with it
i am sure you tried these things, just hard to know when reading posts
also, i don't know if you are running your commands correctly based on how i undestand your posts. you can't run adb commands from fastboot, which is what you were in to fastboot boot image. you would want to type fastboot reboot-bootloader
if you are very familiar with adb/fastboot--sorry. if not need to get up to speed on them
if i misread or misunderstood any of this, sorry for butting in--
rugmankc said:
did you ever try to boot into the rom after you flashed it and boot image as in just tapping on reboot system
can you plug phone into pc and get indicator at top of screen that says you are connected. then pull down notification bar and select to mount drive
if so, does it show you your sdcard in the windows screen
you do have an S4 device and assume you are hboot .13 or higher
if you can get into os and see sdcard, you can get twrp and flash image gui and flash rom and boot image with it
i am sure you tried these things, just hard to know when reading posts
also, i don't know if you are running your commands correctly based on how i undestand your posts. you can't run adb commands from fastboot, which is what you were in to fastboot boot image. you would want to type fastboot reboot-bootloader
if you are very familiar with adb/fastboot--sorry. if not need to get up to speed on them
if i misread or misunderstood any of this, sorry for butting in--
Click to expand...
Click to collapse
Ya he messed it up so needs RUU. He has PM me just waiting on a reply.
UPDATE 11/30/20: I AM STILL PROVIDING FAST 1 ON 1 SUPPORT VIA DISCORD https://discord.gg/RNJXXPp
READ WHOLE THING!
So I was stuck in a TWRP bootloop with the corruption orange triangle. This happened after I got the encryption unsuccessful please factory reset and I wiped my cache it put me here. So I accidentally wiped /system which meant I had no OS. So what I did was download: http://www.mediafire.com/file/pcuslla00j22zqw/h918-v20d.7z
Along with the noverity here: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Now, after flashing the boot and system images in TWRP, flash no verity. Try booting up, this should take you back to recovery. Now, reboot into bootloader, and type:
fastboot oem lock
This does give you a red triangle now. If you get this you are doing the correct thing! Now pull out the battery so it is completely off. Now put it back in
THIS IS VERY IMPORTANT:
http://www.hardreset.info/devices/lg/lg-v20/
FOLLOW METHOD 1 AND DO IT TWICE! TWICE I SAID!
It won't give you a success message so after you do this pull the battery out and put it back in
hold down the volume down button, and plug in a USB as you are holding it down. This should take you to back into fastboot mode.
fastboot oem unlock
Now type:
fastboot reboot
And it SHOULD still give you the orange triangle, but then it should go past that and boot into the operating system.
If you end up in TWRP, mount /system and go to the file manager to see if there are any files in /system. If not, then you need to reflash the system.img.
Please let me know if this worked. I actually went to tmobile and they ordered me a replacement but then I fixed it when i got back by doing this. I figured this out myself. So please give me credit if you post this somewhere. Thanks!
UPDATE: If you are stuck in TWRP after the OTA follow the these steps:
1. Wipe everything in twrp. (internal storage, data, cache, davilk etc.)
2. Flash a custom rom from xda. (I used Overdirve. No promises if it works on anything else: https://forum.xda-developers.com/v20/development/rom-maximum-ovrdrive-lg-v20-v2-0-t3518475
3. Now, reboot into bootloader, and type:
fastboot oem lock
This does give you a red triangle now. If you get this you are doing the correct thing! Now pull out the battery so it is completely off. Now put it back in
THIS IS VERY IMPORTANT:
http://www.hardreset.info/devices/lg/lg-v20/
FOLLOW METHOD 1 AND DO IT TWICE! TWICE I SAID!
It won't give you a success message so after you do this pull the battery out and put it back in
hold down the volume down button, and plug in a USB as you are holding it down. This should take you to back into fastboot mode.
fastboot oem unlock
Now type:
fastboot reboot
And it SHOULD still give you the orange triangle, but then it should go past that and boot into the operating system.
If you are still having issues, join this discord I made and leave a message. I will response faster there: https://discord.gg/RNJXXPp
If I helped, please feel free to donate paypal.me/ScottM911
ScottFlysPlanes said:
So I was stuck in a TWRP bootloop with the corruption orange triangle. This happened after I got the encryption unsuccessful please factory reset and I wiped my cache it put me here. So I accidentally wiped /system which meant I had no OS. So what I did was download: https://build.nethunter.com/misc/h918/h918-v20d.7z
Along with the noverity here: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Now, after flashing the boot and system images in TWRP, flash no verity. Try booting up, this should take you back to recovery. Now, reboot into bootloader, and type:
fastboot oem lock
This does give you a red triangle now. If you get this you are doing the correct thing! Now pull out the battery so it is completely off. Put the battery back in, and hold down the volume down button, and plug in a USB as you are holding it down. This should take you to back into fastboot mode. Type
fastboot oem unlock
Now type:
fastboot reboot
And it SHOULD still give you the orange triangle, but then it should go past that and boot into the operating system.
If you end up in TWRP, mount /system and go to the file manager to see if there are any files in /system. If not, then you need to reflash the system.img.
Please let me know if this worked. I actually went to tmobile and they ordered me a replacement but then I fixed it when i got back by doing this. I figured this out myself. So please give me credit if you post this somewhere. Thanks!
If I helped, please feel free to donate http://bit.ly/2gilo51
Click to expand...
Click to collapse
How did you get the system.img onto your device to flash? I keep getting a file size limit error whenever i try to copy it over...
Murphy71984 said:
How did you get the system.img onto your device to flash? I keep getting a file size limit error whenever i try to copy it over...
Click to expand...
Click to collapse
Use a flash drive and get a USB to USB c adapter. I had one from my note 7. You can also use adb push
ScottFlysPlanes said:
Use a flash drive and get a USB to USB c adapter. I had one from my note 7. You can also use adb push
Click to expand...
Click to collapse
I'm still getting a bootloop to the Recovery....ugh I just don't get it. I followed everything to a T.....I thought that as long as I could get to TWRP I could flash the Stock Odex/DeOdex zip found in another thread and everything would be fine...when it gets to the LG screen it sorta does an 'old TV flash' and goes into recovery...what am I missing?
Murphy71984 said:
I'm still getting a bootloop to the Recovery....ugh I just don't get it. I followed everything to a T.....I thought that as long as I could get to TWRP I could flash the Stock Odex/DeOdex zip found in another thread and everything would be fine...when it gets to the LG screen it sorta does an 'old TV flash' and goes into recovery...what am I missing?
Click to expand...
Click to collapse
Try wiping everything including /system. Also make sure after you flashed the images, see if there are files in /system using the twrp file manager.
ScottFlysPlanes said:
So I was stuck in a TWRP bootloop with the corruption orange triangle. This happened after I got the encryption unsuccessful please factory reset and I wiped my cache it put me here. So I accidentally wiped /system which meant I had no OS. So what I did was download: https://build.nethunter.com/misc/h918/h918-v20d.7z
Along with the noverity here: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Now, after flashing the boot and system images in TWRP, flash no verity. Try booting up, this should take you back to recovery. Now, reboot into bootloader, and type:
fastboot oem lock
This does give you a red triangle now. If you get this you are doing the correct thing! Now pull out the battery so it is completely off. Put the battery back in, and hold down the volume down button, and plug in a USB as you are holding it down. This should take you to back into fastboot mode. Type
fastboot oem unlock
Now type:
fastboot reboot
And it SHOULD still give you the orange triangle, but then it should go past that and boot into the operating system.
If you end up in TWRP, mount /system and go to the file manager to see if there are any files in /system. If not, then you need to reflash the system.img.
Please let me know if this worked. I actually went to tmobile and they ordered me a replacement but then I fixed it when i got back by doing this. I figured this out myself. So please give me credit if you post this somewhere. Thanks!
If I helped, please feel free to donate http://bit.ly/2gilo51
Click to expand...
Click to collapse
@ScottFlysPlanes
Hi, I did the same thing you mentioned with yours and accidentally deleted /system. I felt a little relieved when I saw your post. But unfortunately your method is not working for me. I tried every step as per your directions. My phone boots back into TWRP (after doing 'fastboot oem unlock") and I checked /system folder which has alot of files in it... I have a question, during the initial steps, after flashing boot.img and then system.img and before rebooting, TWRP say "No OS available"! ....Your steps did not mention this. Is it supposed to say that?
I would really appreciate your help. I am freaking out here.
Thanks!!!
bighit101 said:
@ScottFlysPlanes
Hi, I did the same thing you mentioned with yours and accidentally deleted /system. I felt a little relieved when I saw your post. But unfortunately your method is not working for me. I tried every step as per your directions. My phone boots back into TWRP (after doing 'fastboot oem unlock") and I checked /system folder which has alot of files in it... I have a question, during the initial steps, after flashing boot.img and then system.img and before rebooting, TWRP say "No OS available"! ....Your steps did not mention this. Is it supposed to say that?
I would really appreciate your help. I am freaking out here.
Thanks!!!
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/showthread.php?p=69685809
Sent by using the battery of my LG V20
Murphy71984 said:
Try this: http://forum.xda-developers.com/showthread.php?p=69685809
Sent by using the battery of my LG V20
Click to expand...
Click to collapse
@Murphy71984
Thanks for the reply. Unfortunately the same thing happens, it just boots back into TWRP ... What am I doing wrong? I couldnt have messed up that bad by deleting /system...or did I???? I see other people having success with the method you linked me to, but not me.
Any other tips that might work?
Thanks once again!
bighit101 said:
@Murphy71984
Thanks for the reply. Unfortunately the same thing happens, it just boots back into TWRP ... What am I doing wrong? I couldnt have messed up that bad by deleting /system...or did I???? I see other people having success with the method you linked me to, but not me.
Any other tips that might work?
Thanks once again!
Click to expand...
Click to collapse
When you go into /system the first time when it should be clear... are you seeing a lost&found folder? That needs to be deleted.
Sent by using the battery of my LG V20
Murphy71984 said:
When you go into /system the first time when it should be clear... are you seeing a lost&found folder? That needs to be deleted.
Sent by using the battery of my LG V20
Click to expand...
Click to collapse
I tried to delete it, but it says Done and right after in red it says "rm -r f "/system" process ended with ERROR: 1"
???
@bighit101
Are you mounting /system beforehand?
Sent by using the battery of my LG V20
Murphy71984 said:
@bighit101
Are you mounting /system beforehand?
Sent by using the battery of my LG V20
Click to expand...
Click to collapse
Yes The system, cache and dalvik have check marks on them....
bighit101 said:
Yes The system, cache and dalvik have check marks on them....
Click to expand...
Click to collapse
Hmmm.... I don't know then! That process helped me. Just double check you are doing everything correctly and in order especially....Wipe > Format Data (type 'yes')....the Fix Contents bit...etc.... Just go through step by step.
Sent by using the battery of my LG V20
Ok, when you wipe /system and everything. Reboot. Then flash, boot.img, THEN. System.img. After that reboot, it should still take you into twrp. Wipe cache dalvik. Then reboot. Then from twrp reboot to fastboot mode and lock the bootloader. Reboot again. If you see the red triangle, and it should keep looping. Then pull out the battery and put it back in to completely turn it off. Now follow this guide http://www.hardreset.info/devices/lg/lg-v20/ for hard reset. It should just reboot after you press the reset and boot into the red triangle. Now boot back into fastboot, (hold down volume and plug in cable) and type fastboot oem unlock. Now reboot. Tell me if that works for you?
Help!!! I'm stuck on TWRP. tried different roms and no luck. I'm unable to move the system.img to the SD or phone storage. I don't have a flash drive and ADB push is failing
well i been having the boot problem as you go now but now i went from orange triangle to red. I think i have a brick for sure now if anybody knows a fix please let me know.
jrdejavux said:
well i been having the boot problem as you go now but now i went from orange triangle to red. I think i have a brick for sure now if anybody knows a fix please let me know.
Click to expand...
Click to collapse
You need to re-unlock your bootloader. Sounds like you relocked it.
Sent by using the battery of my LG V20
Murphy71984 said:
You need to re-unlock your bootloader. Sounds like you relocked it.
Sent by using the battery of my LG V20
Click to expand...
Click to collapse
i tried but it wont go into fastboot
lourock21 said:
Help!!! I'm stuck on TWRP. tried different roms and no luck. I'm unable to move the system.img to the SD or phone storage. I don't have a flash drive and ADB push is failing
Click to expand...
Click to collapse
When doing adb push did you make sure you press "Open command window here?" In the folder of where the file you are trying to push is located.
Yeah, it starts to push then fails at around 30%