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?
Related
So i have been trying to fix my phone now for about.... 5 days or so.
I know that its the internal partitions because nothing I MEAN NOTHING has fixed it.
Flashed everything to stock flashed every recovery IMG and everything else under the sun. The problem is that the phone is stuck in a reboot loop. I ran an RUU into the phone by use of good old cmd. Had to access it through fastboot menu.
I have no ADB!! I am stuck in Hboot and Fastboot menu. I cant get into anything else and i cant fix anything else. I have to fix the partitions first, This is an advance problem so i really need some professional help here.
IE how the F*ck do i fix this >_<
TestTodeath said:
So i have been trying to fix my phone now for about.... 5 days or so.
I know that its the internal partitions because nothing I MEAN NOTHING has fixed it.
Flashed everything to stock flashed every recovery IMG and everything else under the sun. The problem is that the phone is stuck in a reboot loop. I ran an RUU into the phone by use of good old cmd. Had to access it through fastboot menu.
I have no ADB!! I am stuck in Hboot and Fastboot menu. I cant get into anything else and i cant fix anything else. I have to fix the partitions first, This is an advance problem so i really need some professional help here.
IE how the F*ck do i fix this >_<
Click to expand...
Click to collapse
Did you try to mess with the partition addresses?
You can always do 2 things:
- do a fastboot boot recovery.img
try to mount the partitions from there; see if they mount at all
or list your mtd partitions (The DI is on MTD right?)
- do a fastboot boot boot.img
and post a logcat to pastebin
Remote not allowed
Did you try to mess with the partition addresses?
You can always do 2 things:
- do a fastboot boot recovery.img
try to mount the partitions from there; see if they mount at all
or list your mtd partitions (The DI is on MTD right?)
- do a fastboot boot boot.img
and post a logcat to pastebin
Click to expand...
Click to collapse
Well im running all stock so every time i try to run a fastboot command it returns as Remote not allowed. Heh Im pretty sure im NOT running a perfected SPL.
Any way to fix the remote not allowed?
Ps im not to smart lol clarify DI=what? MTD=what? logcat to pastebin? what? sorry Im not to to firmiluar with every term
PPs google chrome's spell check sucks -_-
Ok so i need to enable fastboot from the phone. there is an ENG HBOOT that runs .77 but i got a black screen which im guessing means i have an SLCD. SO how do i enable it :/
Good news and bad news. I got to run fastboot commands to the phone but i flashed the recovery partition with stock and CWM 3.0.0.5 and 3.0.0.8
No good :/
Seems like i have to erase every partition and format everything. the ram space; i mean everything. i have to treat this like the company sent me a blank phone and i have to put everything on it. Any help?
I'm was using CM9 nightly and it froze, I removed the battery and tried to boot but it hangs at Google screen.
I can access bootloader and recovery but, in CWM touch recovery, I can't mount or format system, sdcard, or data but can wipe and mount/unmount cache.
And I can't mount USB in recovery
I can access through fastboot, so what would I need to go about doing to get this thing back up and running?
I don't want to try to many things and screw it up worse or something. It seems to me like the partitions got screwed up or something, but that's just a wild guess. Can anyone help me fix this or point me in the right direction?
jivetrky said:
I'm was using CM9 nightly and it froze, I removed the battery and tried to boot but it hangs at Google screen.
I can access bootloader and recovery but, in CWM touch recovery, I can't mount or format system, sdcard, or data but can wipe and mount/unmount cache.
And I can't mount USB in recovery
I can access through fastboot, so what would I need to go about doing to get this thing back up and running?
I don't want to try to many things and screw it up worse or something. It seems to me like the partitions got screwed up or something, but that's just a wild guess. Can anyone help me fix this or point me in the right direction?
Click to expand...
Click to collapse
sounds like the sd(storage) is gone bad or going bad.
simms22 said:
sounds like the sd(storage) is gone bad or going bad.
Click to expand...
Click to collapse
Any way I could test that theory, through ADB or something?
jivetrky said:
Any way I could test that theory, through ADB or something?
Click to expand...
Click to collapse
maybe a logcat while trying to access the storage? but really, if it isnt accessible, thats all the info you should need.
Wow... internal memory already gone bad? Have you tried fastboot flash the factory images for ns4g?
Sent from my Nexus S 4G using XDA
rasengan82 said:
Wow... internal memory already gone bad? Have you tried fastboot flash the factory images for ns4g?
Sent from my Nexus S 4G using XDA
Click to expand...
Click to collapse
the internal storage going bad is actually a very common problem.
I guess locking bootloader and claiming warranty is the way to go.
Sent from my Nexus S 4G using XDA
rasengan82 said:
I guess locking bootloader and claiming warranty is the way to go.
Sent from my Nexus S 4G using XDA
Click to expand...
Click to collapse
How might I go about doing that?
jivetrky said:
How might I go about doing that?
Click to expand...
Click to collapse
fastboot oem lock
with fastboot while in the bootloader. provided that fastboot sees your device(fastboot devices).
Just a warning... if you oem lock you won't be able to oem unlock again IF you internal memory is indeed corrupted.
Sent from my Nexus S 4G using XDA
rasengan82 said:
Just a warning... if you oem lock you won't be able to oem unlock again IF you internal memory is indeed corrupted.
Sent from my Nexus S 4G using XDA
Click to expand...
Click to collapse
very true. but if youre doing it to send back to samsung for a warranty repair, does it matter?
I don't know the inner workings of Android or this device specifically, but isn't there just a single bit of flash on the phone which is divided/partitioned into SD, system, etc. Is it possible that the partitions have just been corrupted or something like that? I was playing around just seeing what the phone could do and Odin3 will recognize it, but I didn't want to play around and screw anything up even more than it is.
Is it possible to use Odin to try and attempt a fix? I see there is a re-partition option, I was wondering if that could be worth a try?
Well, I guess I've given up and I'll just hope for Samsung to replace/fix it.
Google-foo has not shown me anything as far as trying to repartition just in case it was corrupted or something; couldn't find any images out there with PITs. I'm able to write the bootloaders and recovery so I just used the one-click-stock provided boot and recovery images and flashed them with fastboot then locked it.
Doesn't boot and recovery go on the same flash that is theoretically bad which is stopping SD, system, & data from being mounted?
Just for the sake, what happens now if you do fastboot oem unlock?
Do you get an error? If you don't get an error, unlock it and then download this:
https://dl.google.com/dl/android/aosp/sojus-imm76d-factory-10660f4c.tgz
Unzip everything and put it on a folder (you will find several img files). Now start the phone again in fastboot mode.
fastboot flash bootloader bootloader-crespo4g-d720sprke1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo4g-d720sprlc1.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
rasengan82 said:
Just for the sake, what happens now if you do fastboot oem unlock?
Do you get an error? If you don't get an error, unlock it and then download this:
https://dl.google.com/dl/android/aosp/sojus-imm76d-factory-10660f4c.tgz
Unzip everything and put it on a folder (you will find several img files). Now start the phone again in fastboot mode.
fastboot flash bootloader bootloader-crespo4g-d720sprke1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo4g-d720sprlc1.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
I can't unlock it now, as the bootloader pops up a screen that says to unlock it you have to wipe/factory reset. But it hangs on that probably because it can't see system/data.
I did try flashing it with fastboot though, before I locked it, and I could flash boot, recovery, and radio but it will just hang forever on flashing system. It never gives an error. I let it sit there for over an hour and it never did anything.
So I guess now that it's locked there really is nothing I can do.
Ok, I think Samsung warranty is the only thing left.
Forgot to update, sent to Samsung and they replaced the PBA, so the flash was apparently bad. Thanks for the advice, everyone!
Was only about a week turn around, just took me a while to actually get the RMA started.
They even send a UPS label to ship it to them then took a week turnaround, overall it was good service.
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
was flashing a rom, then a kernel.. it stopped, so i rebooted. things were fine.
tried to factory reset, flash rom.. damn thing froze again. so i rebooted.
now it bootloops. i have since fastboot flashed the boot.img from the rom, and fastboot flashed the twrp.img recovery.
can get to bootloader, can get to fastboot usb, but cannot get to recovery or back to a running phone.. bootloops
please help
can i RUU or something?
wdkingery said:
was flashing a rom, then a kernel.. it stopped, so i rebooted. things were fine.
tried to factory reset, flash rom.. damn thing froze again. so i rebooted.
now it bootloops. i have since fastboot flashed the boot.img from the rom, and fastboot flashed the twrp.img recovery.
can get to bootloader, can get to fastboot usb, but cannot get to recovery or back to a running phone.. bootloops
please help
Click to expand...
Click to collapse
So I have noticed with my phone (hboot 1.14) I have to DISCONNECT it from my computer while in bootloader to be able to boot into recovery. So I do the following:
With phone in bootloader fastboot mode:
1) fastboot reboot-bootloader
2) While the screen is black, DISCONNECT the cable
3) In bootloader, use vol keys navigate to Recovery
4) Hopefully profit
Give it a try
wdkingery said:
was flashing a rom, then a kernel.. it stopped, so i rebooted. things were fine.
tried to factory reset, flash rom.. damn thing froze again. so i rebooted.
now it bootloops. i have since fastboot flashed the boot.img from the rom, and fastboot flashed the twrp.img recovery.
can get to bootloader, can get to fastboot usb, but cannot get to recovery or back to a running phone.. bootloops
please help
Click to expand...
Click to collapse
Can you relock the bootloader? If can then download the official RUU(here is 2.20 firmware http://www.htc.com/us/support/htc-one-x-att/software-updates) and that'll probably save your phone.
oh, you can use the all in one toolkit(http://forum.xda-developers.com/showthread.php?t=1952426) to relock your bootloader if you can.. good luck
TheEmpyre said:
So I have noticed with my phone (hboot 1.14) I have to DISCONNECT it from my computer while in bootloader to be able to boot into recovery. So I do the following:
With phone in bootloader fastboot mode:
1) fastboot reboot-bootloader
2) While the screen is black, DISCONNECT the cable
3) In bootloader, use vol keys navigate to Recovery
4) Hopefully profit
Give it a try
Click to expand...
Click to collapse
GOD ALMIGHTY what in the gayness.
thanks dude. was the problem.
now i have a probably bigger problem; unable to mount SD card.. i think i have read that means a bad thing. tried to mount SD card: windows wants to format it. **** me
wdkingery said:
GOD ALMIGHTY what in the gayness.
thanks dude. was the problem.
now i have a probably bigger problem; unable to mount SD card.. i think i have read that means a bad thing
Click to expand...
Click to collapse
You probably corrupted it at some point in this process. You need to mount with your pc and reformat. It happens.
iElvis said:
You probably corrupted it at some point in this process. You need to mount with your pc and reformat. It happens.
Click to expand...
Click to collapse
you are saying if i allow windows to format it, i won't have a brick, but instead will be able to fix my problem?
wdkingery said:
you are saying if i allow windows to format it, i won't have a brick, but instead will be able to fix my problem?
Click to expand...
Click to collapse
Sweet! Glad I could help, it took me a while to figure it out too, my palms were all sweaty thinking I derped my phone. And about the un-mountable SD card:
I had the same problem with my Nexus 10 when I was unlocking the bootloader, and all I had to do was actually do a format via Recovery (TWRP). Then I was able to boot into the ROM -- although I wasn't able to mount the Nexus 10 SD card still....so thats still a mystery. But I was able to get into the installed ROM
TheEmpyre said:
Sweet! Glad I could help, it took me a while to figure it out too, my palms were all sweaty thinking I derped my phone. And about the un-mountable SD card:
I had the same problem with my Nexus 10 when I was unlocking the bootloader, and all I had to do was actually do a format via Recovery (TWRP). Then I was able to boot into the ROM -- although I wasn't able to mount the Nexus 10 SD card still....so thats still a mystery. But I was able to get into the installed ROM
Click to expand...
Click to collapse
i tried that, and it failed.
i almost had windows format it, but i don't know which format type (FAT 32?)
and i'm still not clear if it will brick if i do
NEW EDIT: it doesn't brick, use default format type.
looks like i'm out of the weeds, thanks for all the quick replies.
wdkingery said:
i tried that, and it failed.
i almost had windows format it, but i don't know which format type (FAT 32?)
and i'm still not clear if it will brick if i do
NEW EDIT: it doesn't brick, use default format type.
looks like i'm out of the weeds, thanks for all the quick replies.
Click to expand...
Click to collapse
Does your TWRP not have a "Format Data" Option in the Wipe Menu?
Edit: Just read your most recent edit, happy flashing hope everything works out. Oh and add [Solved] to your title if you don't mind
it does, but even that didn't work..
Hey there!
I'm pretty new to the Android platform. I've been on iOS for many years.
I already flashed a custom firmware on a Moto G, which worked fine. (SlimKat)
I thought about doing the same thing with my HTC One X.
GSM version (Model: PJ83100)
Current device state:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.01.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
Nov 26 2012, 18:37:14:-1
Unlike the Moto G Bootloader, I'm unable to erase any partition but the cache. Example:
./fastboot erase system
erasing 'system'...
FAILED (remote: not allowed)
I am not able to boot into the OS or the recovery partition anymore, so they have probably been wiped. When I reboot the device, it's either a boot loop or it simply shuts down.
I already tried to flash CWM and TWRP. Each of those were successful, at least according to the terminal... Unfortunately, same thing happens when the phone reboots (unable to access recovery).
I also tried to flash SlimKat with the "./fastboot flash zip file_name.zip" command, even if it isn't supposed to work (I believe). It wasn't successful.
In despair, I flashed the boot image from the ROM but still without result.
I did all of those in the FastBoot window and on the RUU mode (./fastboot oem rebootRUU).
Both stuck at the same points.
If anyone knows how to fix this, it would be really appreciated.
All the posts related to the issue did not help me in any ways.
Thank you!
You need to work out why your recovery flashes aren't working, you need a custom recovery to install custom ROMs on this device, flashing them through fastboot will not work. Can you explain in detail and step by step the method you use to flash the recovery please?
Sent via Bacon
timmaaa said:
You need to work out why your recovery flashes aren't working, you need a custom recovery to install custom ROMs on this device, flashing them through fastboot will not work. Can you explain in detail and step by step the method you use to flash the recovery please?
Sent via Bacon
Click to expand...
Click to collapse
I'm doing the same thing that should be done.
./fastboot erase cache
./fastboot flash recovery openrecovery-twrp-2.7.1.0-evita.img
./fastboot reboot-bootloader
Select BOOTLOADER
Select RECOVERY
Device shows HTC logo for one-two secs
Shuts down
Did you check the md5 of the downloaded recovery? It might be corrupt.
Sent via Bacon
timmaaa said:
Did you check the md5 of the downloaded recovery? It might be corrupt.
Sent via Bacon
Click to expand...
Click to collapse
I redownloaded the file from the internet so it can't be corrupted twice.
I believe that I also tried with CWM with same results.
None of those even want to boot.
And now since yesterday, I'm not even able to boot my phone.
I contacted HTC and their hard reset procedure did nothing.
Well...
jeanchoquette56 said:
I redownloaded the file from the internet so it can't be corrupted twice.
I believe that I also tried with CWM with same results.
None of those even want to boot.
And now since yesterday, I'm not even able to boot my phone.
I contacted HTC and their hard reset procedure did nothing.
Well...
Click to expand...
Click to collapse
It can be corrupted twice, it can be corrupted a thousand times in a row, that's why you need to check the md5 like I suggested. Did you do that??
Forget what HTC have to say, any advice they would give is irrelevant for a modified device. In fact, if you've performed a factory reset from the bootloader you've also just corrupted your sd card.
Sent via Bacon
timmaaa said:
It can be corrupted twice, it can be corrupted a thousand times in a row, that's why you need to check the md5 like I suggested. Did you do that??
Forget what HTC have to say, any advice they would give is irrelevant for a modified device. In fact, if you've performed a factory reset from the bootloader you've also just corrupted your sd card.
Sent via Bacon
Click to expand...
Click to collapse
I'm not sure how to verify the md5. You want me to verifiy the file on the computer or after is has been transfered to the phone?
Like I said, I'm not able to do a factory reset from the bootloader as all "format erase --partiton--" return in errors.
These commands helped me to corrrectly install Slimkat on my Moto G, but how can you do the same when it's not possible to wipe the phone in any ways? From the recovery partition, that would be possible. I'm able to flash the recovery, but not to access it. As this said, I'm really stuck.
The One X does not have a SD card btw. At least, there look to be no slot for it.
Thank you!
Especially timmaaa
jeanchoquette56 said:
I'm not sure how to verify the md5. You want me to verifiy the file on the computer or after is has been transfered to the phone?
Like I said, I'm not able to do a factory reset from the bootloader as all "format erase --partiton--" return in errors.
These commands helped me to corrrectly install Slimkat on my Moto G, but how can you do the same when it's not possible to wipe the phone in any ways? From the recovery partition, that would be possible. I'm able to flash the recovery, but not to access it. As this said, I'm really stuck.
The One X does not have a SD card btw. At least, there look to be no slot for it.
Thank you!
Especially timmaaa
Click to expand...
Click to collapse
Ok, you don't know how to verify the md5, but you can overcome that problem by using Google to search how to do it.
So you've attempted a factory reset from the bootloader, it gave you errors, and it has corrupted your sd card.
I'm aware that this device doesn't have an sd card slot, it has internal memory (or a virtual sd card), which is commonly referred to as the sd card.
Sent via Bacon