Related
Hi
I have bricked my nexus s when I loaded a ROM that I downloaded.
I have used several different ROMs and had no problems.
I asume this ROM was dodgey.. Anyway I get no screen at all, the menu control at the botom of the screen lights up but that is it.
I can get to it using fastboot but it won't load any ROMS. There is no action on the Nexus screen itself.
Is there a guide using fastboot to recover this also what file/files will I need to download?
Thanks in advance any help would be much appreciated.....
If you are here looking for help you need to give us more information.
What model Nexus S do you have?
What rom did you flash?
What have you done sense flashing the rom?
My guess is you flashed a rom that isn't for your model phone. So you either have SAMOLED or SLCD. I'm guessing the rom you installed was for the screen type you don't have.
So let us have some more details so we can help.
Sent from my Nexus S 4G using xda premium
Sounds like a call for the mighty Odin...
Sent from my Nexus S 4G using xda premium
And u can't get into recovery using the button method?
Sent from my Nexus S using XDA App
If you can get fastboot to work, you can flash all partitions including system. Don't worry, this is an easy fix.
Hi Again guys
Firstly thanks a lot for the replys I really appreciate it.
Its a 3g the model no: is GT-19023.
Its SAMOLED that much I know.
I cannot get into recovery I can get fastboot to recognise the phone but nothing on the screen.
I have downloaded a stock rom and extracted the boot, recovery & system.img files.
I have followed the instructions below and all seems to work till I get to the system. it fails with the following message. The other steps seem to work OK.
"FAILED (remote write failed)"
I have also tried this with several other ROMs I know work on wifes Nexus s and still no luck. Some allow the system to be flashed but the phone still won't boot.
1. fastboot flash boot boot.img
2. fastboot flash recovery recovery.img
3. fastboot flash system system.img
4. fastboot erase cache
5. fastboot erase userdata
Any help would be great
I also downloaded ODIN but cant get it to work; It does not recognise that it is connected to the USB, but fastboot does!. (Is there a step by step guide to using it?)
Sorry for sounding like noob, but I have read everything and looked up these forums and tried a lot before asking for help.
GL
If your phone is a Gt-i9023 it is SLCD!!!!! Not SAMOLED.
Again what rom did you flash? Post a link to it. I still think you flashed a rom for SAMOLED when you have SLCD.
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
If your phone is a Gt-i9023 it is SLCD!!!!! Not SAMOLED.
Again what rom did you flash? Post a link to it. I still think you flashed a rom for SAMOLED when you have SLCD.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
BTW, so 9020 ROMs are incompatible with 9023? I am aware of differences between those devices, but when I looked in "Development" section, there is no info, about compatibility with 9020a/t/9023
http://forum.xda-developers.com/showthread.php?t=955719
pretty sure that is the link to the ROM.
I tried to restore using another stock ROM (I backed it up from another Nexus that was only rooted and stock)... Yes it was exactly the same phone model etc.
The problem is now the error is saying ===FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)===
I tried that (the unlock command) and the prompt just types three dots (...) and then hangs there. I have tried removing the battery etc and the same issue.
I am happy to erase the phone to nothing and load another image.
It seems that maybe this phone is cooked....
I hope not ==shattered==
k_myk said:
BTW, so 9020 ROMs are incompatible with 9023? I am aware of differences between those devices, but when I looked in "Development" section, there is no info, about compatibility with 9020a/t/9023
Click to expand...
Click to collapse
ROMs are compatible between those variants! But, if you're flashing some stock ROM bundles you can flash wrong one. Because bundles contain rom, kernels and radios for specific device with specific drivers. In that case you can flash wrong driver for your display, or even something worse...
Follow what it says, unlock your bootloader first.
Sent from my GT-P1000 using xda premium
glockman63 said:
http://forum.xda-developers.com/showthread.php?t=955719
pretty sure that is the link to the ROM.
I tried to restore using another stock ROM (I backed it up from another Nexus that was only rooted and stock)... Yes it was exactly the same phone model etc.
The problem is now the error is saying ===FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)===
I tried that (the unlock command) and the prompt just types three dots (...) and then hangs there. I have tried removing the battery etc and the same issue.
I am happy to erase the phone to nothing and load another image.
It seems that maybe this phone is cooked....
I hope not ==shattered==
Click to expand...
Click to collapse
Your link still does not tell us which rom you flashed....
You can't flash a rooted rom through fastboot without unlocking the bootloader first. Sounds like you need to restore a factory rom with Odin.
Sent from my Nexus S 4G using xda premium
Hi all
I got this sorted out and am really happy to have my phone going again.
For those interested or in the same predicament I was in please read on as this is how I managed to make this phone go again.
Please rmemeber this phone was really bricked no screen at all jus the menu light like in the picture in my first post.
As I stated I could get fast boot to see the phone. And also Odin. (Still no screen at all)
I had another phone the same with the original rom on board.
I rooted this phone and installed ClockworkMod recovery ad used this to backup the standard ROM.
I then rebooted this phone an copied these files from the backup into my fastboot directory (boot.img, recovery.img, system.img)
I then connected my dead phone up to my PC and ran the following commands.
1. fastboot flash boot boot.img
2. fastboot flash recovery recovery.img
3. fastboot flash system system.img
4. fastboot erase cache
5. fastboot erase userdata
I then removed the battery and to my astonisment the phone booted normally into the standard ROM.
WOW I was over the moon I have since installed my MIUI Rom and using my phone happily...
Thanks everyone for your input..
Rem3Dy said:
Your link still does not tell us which rom you flashed....
You can't flash a rooted rom through fastboot without unlocking the bootloader first. Sounds like you need to restore a factory rom with Odin.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I've got a phone in the same state I am trying to revive for a guy. With the bootloader locked download mode gives you a locked bootloader screen. Odin sends the flash images to the phone, the phone verifies them but then refuses to flash them (presumably due to the bootloader being locked). The bootloader won't unlock so there is no way to flash a rom to fix the phone.
glockman63 said:
Hi all
I got this sorted out and am really happy to have my phone going again.
For those interested or in the same predicament I was in please read on as this is how I managed to make this phone go again.
Please rmemeber this phone was really bricked no screen at all jus the menu light like in the picture in my first post.
As I stated I could get fast boot to see the phone. And also Odin. (Still no screen at all)
I had another phone the same with the original rom on board.
I rooted this phone and installed ClockworkMod recovery ad used this to backup the standard ROM.
I then rebooted this phone an copied these files from the backup into my fastboot directory (boot.img, recovery.img, system.img)
I then connected my dead phone up to my PC and ran the following commands.
1. fastboot flash boot boot.img
2. fastboot flash recovery recovery.img
3. fastboot flash system system.img
4. fastboot erase cache
5. fastboot erase userdata
I then removed the battery and to my astonisment the phone booted normally into the standard ROM.
WOW I was over the moon I have since installed my MIUI Rom and using my phone happily...
Thanks everyone for your input..
Click to expand...
Click to collapse
So it wasn't bricked...... glad you got it working.
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
So it wasn't bricked...... glad you got it working.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Your lucky your bootloader was already unlocked. Once a phone gets borked like that unlocking the bootloader is impossible and Odin refuses to flash.
jboxer said:
Your lucky your bootloader was already unlocked. Once a phone gets borked like that unlocking the bootloader is impossible and Odin refuses to flash.
Click to expand...
Click to collapse
Dude.... stop spreading incorrect information. The bootloader state does not affect Odin. Please understand this!
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
Dude.... stop spreading incorrect information. The bootloader state does not affect Odin. Please understand this!
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Yes it does! Or at least on the phone I am trying to repair it has. On the phone I am trying to repair when you go into download mode you get a screen that says to unlock the bootloader. Odin connects and sends the file but then the phone refuses to flash it. If that is not the bootloader being locked affecting Odin then I don't know what is. I have flashed with Odin hundreds of times with Galaxy S phones so I know what I am doing. I have never seen Odin send a file, have the phone say it is verified and then refuse to flash it, but that is what is happening with this Nexus S with an unlockable bootloader. The files are the correct files and Odin is the correct version. If you are so smart, then you tell me what to do to get Odin to accept the flash and you will be my hero.
I have attached a shot of the phone in "download mode." Notice it is a warning about the bootloader being locked, not the normal screen with the Android bot and a shovel. Odin sees the phone (connected to computer as Samsung device) but once the phone verifies the file nothing else happens. The file is never flashed. Notice in the photo there is no YES and NO selections to unlock the bootloader like you get when you issue the "fastboot oem unlock" command. In Fastboot when that command is issued you get the normal unlock the bootloader screen but when you select YES and press Power nothing else happens. It just hangs no matter how long you leave it. A battery pull is the only thing you can do and when you turn the phone back on the bootloader is still locked.
If you are getting g stuck there you may have a hardware issue. I still think you need to try flashing through fastboot.
Sent from my Nexus S 4G using xda premium
Rem3Dy said:
If you are getting g stuck there you may have a hardware issue. I still think you need to try flashing through fastboot.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Cannot flash in fastboot. Sends over image then says fail due to bootloader being locked. If you have a signed update.zip with android-info and android-product files that can be flaahed in fastboot mode let me know where it can be downloaded from.
Sent from my LG-P999 using Tapatalk
Alright its my first issue that I have needed to post about so here we go.
Basically I decided to encrypt my doom before I brought it with to spring break and now that I'm home I want to un encrypt it. I tried the way through settings and it just boots into recovery and will not format the /data option. Next I tried to factory reset through rom manager and through CWM (I'm rooted running codename android) it wont let me mount the SD card to do anything so I'm wondering how can I get it to factory reset? Thanks
Sent from my Incredible 2 using XDA
diablodow said:
Alright its my first issue that I have needed to post about so here we go.
Basically I decided to encrypt my doom before I brought it with to spring break and now that I'm home I want to un encrypt it. I tried the way through settings and it just boots into recovery and will not format the /data option. Next I tried to factory reset through rom manager and through CWM (I'm rooted running codename android) it wont let me mount the SD card to do anything so I'm wondering how can I get it to factory reset? Thanks
Sent from my Incredible 2 using XDA
Click to expand...
Click to collapse
I've had this problem too. Not 100% positive this is the BEST way to do it, but it certainly works: download the proper build files you need, then, using fastboot, use these commands:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
Hope that helps. Let me know if I can clarify.
Ok I can update with what happens I'm on a roadtrip now. It managed to format /system so now its stuck at the boot screen but still lets me go into recovery and fastboot so I feel its not hopeless.
Sent from my Incredible 2 using XDA
So you don't have any access to a laptop or anything you could use to use fastboot? In my experience, you cannot do a wipe from recovery when you've encrypted the device. I have only been able to get back to factory with the method described above.
I don't mean to discourage you, I'm not completely positive you can't do something in recovery that might be able to get you back to stock, hopefully someone else can chime in if that's the case.
Got it fixed once I got to a machine that had ADB and could do some fastboot command. Moral of the story is don't encrypt your tablet then format random stuff. Please close.
Sent from my Incredible 2 using XDA
Problem solved please delete
Sent from my Incredible 2 using XDA
johnpwu said:
I've had this problem too. Not 100% positive this is the BEST way to do it, but it certainly works: download the proper build files you need, then, using fastboot, use these commands:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
Hope that helps. Let me know if I can clarify.
Click to expand...
Click to collapse
I just had this same issue with my Galaxy Nexus (GSM) and now I'm back to factory!
Thanks so much!!!
johnpwu said:
I've had this problem too. Not 100% positive this is the BEST way to do it, but it certainly works: download the proper build files you need, then, using fastboot, use these commands:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
Hope that helps. Let me know if I can clarify.
Click to expand...
Click to collapse
Trully sorry man for my ignorance here but...
I'm a complete n00b and i wanted to know, like, what do i need to do with that exactly, I also have my phone encrypted
could you tell me, I'm kind of a beginner so please don't be harsh lol
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
Good day everyone.
I relocked and installed stock RUU (4.0.3) on my Evita since I had that failing zip install though TWRP. It worked fine but when I tried to manually install the latest RUU (Android 4.1) it failed. Now I decided to unlock it again and start to flash custom ROMs, problem started.
1.) After flashing boot, recovery and custom rom (tried it with CM 10.1 and JellyBam), it would go only up to the boot image (HTC) and stay on there forever. Cleared everything that I could clear on the recovery and cleared fastboot cache.
What I did, relocked it again and tried running the stock RUU (through the computer) and shows error and won't complete.
2.) Now, phone no longer recognizes the Unlock_code.bin from HTC dev. I tried manually flashing it in fastboot and as well as using the All-in-one-tool for Evita, it would somehow show that it went through on both but looking at my phone, it stays: Relocked. Tried it with at least three unlock bin files to no avail.
3.) Other than that, turning the phone off and back on would go straight to bootloader. When I select Recovery, it would go back straight to fastboot mode. Tried to flash recoveries again, and would get this:
E:\Mobile Devices\sd-fix\Nocturnal_SD_FIX_EVITA\Nocturnal_SD_FIX_EVITA>fastboot
flash recovery openrecovery-twrp-2.5.0.0-evita.img
sending 'recovery' (7992 KB)... OKAY [ 2.140s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.871s
E:\Mobile Devices\sd-fix\Nocturnal_SD_FIX_EVITA\Nocturnal_SD_FIX_EVITA>fastboot
flash recovery openrecovery-twrp-2.2.0-evita.img
sending 'recovery' (7460 KB)... OKAY [ 1.692s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.370s
Now I'm stuck with a phone with no OS. Please help. I appreciate your time.
Here's my phone info.
AT&T HTC One X
S-ON
HBOOT - 2.14.0000
Getting a new code only requires fast boot. So just get a new unlock code.....
*edit*
Sorry I misread. This happened to me. Just simulate a battery pull by pressing and holding power and try again. Keep doing that over and over. Eventually, it will work.
Took me about 10-15 tries once.
Sent from my One X using xda app-developers app
Also try to lock the phone even if it tells you it is already locked.
fastboot oem lock
Do that prior to attempting the unlock after full power cycle. Sometimes that gets the device back on track, dont worry too much this issue is not exactly new and after a bit of dicking around the phone will unlock again.
Thanks for your responses!
Yeah, it did. After a number times requesting for unlock bins and re locking, finally it was unlocked.
Now I now have problem #1 from OP. It actually goes to HTC boot screen, stays there for a couple of seconds then reboot. It's been doing that in a loop. Flashed three different ROMs and three different versions of TWRP and phone still does the same thing.
Found my mainver to be 3.18 which I suspect have been changed when I attempted to run the 4.1 RUU (this was before I tried to unlock the bootloader). Downloaded the said RUU from two different sites just to be sure. None of those have worked.
So I found a thread here in XDA saying that this could be the reason why I couldn't boot any of these ROMs.
Any thoughts/help would be greatly appreciated.
Must not have read very much before trying to root if you don't know fastboot flash boot boot.Img
Sent from my One X using xda app-developers app
You're s-on so you need to flash the boot.img manually on hboot 2.14.
Retrieve the boot.img from the ROM zip and place it in your working directory on your pc.
Copy ROM to phone (if you haven't already done that).
Do a full wipe in recovery, then flash the ROM.
Reboot to the bootloader, connect phone to pc, make sure it says fastboot usb on your phone screen.
Open a command prompt in your working directory and issue the following command:
fastboot flash boot boot.img
Reboot the phone.
Enjoy.
Sent from my Evita
Typically bootloops are solved by
flashing recovery cwm or twrp.
wipe cache, data and system.
Manual install the boot.ing from rom you are installing.
Fastboot flash boot boot.img
Install your rom in recovery.
Hopefully all will work then
Sent from my HTC One XL using xda app-developers app
exad said:
Must not have read very much before trying to root if you don't know fastboot flash boot boot.Img
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
timmaaa said:
You're s-on so you need to flash the boot.img manually on hboot 2.14.
Retrieve the boot.img from the ROM zip and place it in your working directory on your pc.
Copy ROM to phone (if you haven't already done that).
Do a full wipe in recovery, then flash the ROM.
Reboot to the bootloader, connect phone to pc, make sure it says fastboot usb on your phone screen.
Open a command prompt in your working directory and issue the following command:
fastboot flash boot boot.img
Reboot the phone.
Enjoy.
Sent from my Evita
Click to expand...
Click to collapse
twistedddx said:
Typically bootloops are solved by
flashing recovery cwm or twrp.
wipe cache, data and system.
Manual install the boot.ing from rom you are installing.
Fastboot flash boot boot.img
Install your rom in recovery.
Hopefully all will work then
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
It's actually my fourth device. Did flash boot.img all the time. That's why it's kind of frustrating.
Any thoughts about damaged eMMC? Just hypothetical.
I don't know if it was a brick but I had an issue before where this HOXL didn't boot up after flashing a wrong kernel. Didn't even light up when plugged to power and had to re-flash the eMMC block using that WIP method. It went back to life.
Might need to try that again. Would that be possible? Still have to download live ubuntu, though. The one I used before got corrupted.
What I did so far:
-relock
-unlock
-erased fastboot cache
-flashed boot.img ( from the custom ROMs that I've tried )
-flashed twrp ( 3 versions )
-wiped every wipe option i could see
I already have tested at least 6 ROMs on this device with no issue with TWRP.
I had ViperXL installed before this happened. I wiped everything out and tried to flash the ATT Android 4.1 RUU and everything got screwed.
edit: i typed the capcha on the title box. lol
You're still s-on right?
Sent from my One X using xda app-developers app
exad said:
You're still s-on right?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Yup!
Is there a way to s-off while you're on fastboot? Facepalm method requires it on booted android. So far can't see other procedures done through fastboot.
EjWilkes0121 said:
Yup!
Is there a way to s-off while you're on fastboot? Facepalm method requires it on booted android. So far can't see other procedures done through fastboot.
Click to expand...
Click to collapse
Get twrp running 2.3.3.1 and flash any sense Rom then s-off
Sent from my HTC One XL using xda premium
I'm going to try again once I get home from work.
Thanks for all your responses guys.
Done it all.
Relocked, intalled RUU - fail.
Unlocked, wiped everything, installed ROM, erased fastboot cache, flashed boot.img, erased fastboot cache - bootloop.
Tried using CWM and same thig happes - bootloops after flashing rom and boot.img
However, I just noticed something.
Whenever I get to flash a zip through recovery, process seems to just complete in no time. I have flashed multiple ROMs and one could really see progress shown on progress bar on both recovery flashing( CM10.1, JellyBam ) and through Aroma installer( CleanROM, ViperXL ).
When this problem started, entire process would initiate, pauses for few seconds then it completes. Can't see the progress bar move across.
I might be going out of topic here but I'm desperate in having this fixed.
Your thoughts and ideas means a lot.
Are there any roms you can boot?? How are you downloading the files? On a pc? Did the md5 match. Maybe the usb wire has a defect and screws the file upon transfer. Your have a really strange issue. I'll flash out of boredom and never had that happen, Even with roms that do nothing more than boot.
And your running twrp 2.3.3.1???
Sent from my HTC One XL using xda premium
I think the recovery is most likely at fault here.
Make sure it's twrp 2.3.3.1: http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.1-evita.img
Use a USB 2.0 port just to be safe.
check md5 omg so important!
Code:
fastboot erase recovery
fastboot flash recovery openrecovery-twrp-2.3.3.1-evita.img
fastboot erase cache
fastboot reboot bootloader
Select recovery
Check the md5 of the sense rom you downloaded
Extract boot.img from rom.
Transfer the rom zip to the phone.
wipe cache, dalvik, system and factory reset in recovery
install sense rom
reboot to bootloader
Code:
fastboot flash boot boot.img
fastboot reboot
Do all that and then tell me what happens.
Back to life!
A huge thanks to you guys! Big time! :victory:
It could be the recovery that screwed it up. Been trying TWRP 2.5 and TWRP 2.2 most of the time. I gave TWRP 2.6 a shot and that made a successful install. I flash ViperXL 3.2.7 + ElementalX 6.7 and phone's back to life!
One thing i noticed. After I S-Off'ed, phone's kind of jerky using normal use. One noticeable thing is the lock screen that doesn't respond after waking, takes 1-2 sec to respond when swiping the lock ring. Big prob for me, battery stuck at 77% even when charged or used heavily. Random reboots also happen. Maybe have to read the entire FacePalm S-Off thread this week. LoL. For now, back to S-On, phone works perfect.
Again, thanks so much for your help guys! Won't be missing any Thank button that you got. :laugh:
I found current sense roms work better with latest firmware so s-off ruu to 3.18 and then see how things run.
Sent from my HTC One X using xda app-developers app
First time post and it's been a hell of a day. I need to figure out how to either sideload the factory ROM, load a 3rd party ROM, or actually factory reset my phone to stock.
I unlocked my bootloader and installed TWRP and SuperSU earlier in the day. I then wanted to try to load Cyanogen11, but there were issues with the load, it constantly failed. I made a backup before I did this, but when I attempted to load the backup, nothing happened, it would just continually boot to recovery.
I attempted a few other things, clearing caches, doing wipes, powering the phone off for 5~ minutes, etc. etc.
Nothing is working, I can't load any ROM now and phone is either stuck at a bootcycle or the HTC Splash screen (Aside from being able to load bootloader/CWP)
jdolbeer said:
First time post and it's been a hell of a day. I need to figure out how to either sideload the factory ROM, load a 3rd party ROM, or actually factory reset my phone to stock.
I unlocked my bootloader and installed TWRP and SuperSU earlier in the day. I then wanted to try to load Cyanogen11, but there were issues with the load, it constantly failed. I made a backup before I did this, but when I attempted to load the backup, nothing happened, it would just continually boot to recovery.
I attempted a few other things, clearing caches, doing wipes, powering the phone off for 5~ minutes, etc. etc.
Nothing is working, I can't load any ROM now and phone is either stuck at a bootcycle or the HTC Splash screen (Aside from being able to load bootloader/CWP)
Click to expand...
Click to collapse
Are you still having issues? If so, PM me and I'll help you out.....
Got everything sorted with the great help of Nelvin. I had previously gone to the twrp support IRC and after answering a few questions, they just stopped talking... Glad there are people out there still willing to help! He spent a good hour or so with me making sure everything was working.
Hey you two!
Did you solve your problem via PM, then maybe send me the log of it please.
I dont know exactly if we have the same problem, but i'll try to explain mine:
I wanted to put a ROM on my mini, because it is branded.
I unlocked the bootloader on the htc one mini and then put the twrp recovery on it. It seems to work.
Next i wanted to put super su on it, but I'm already stuck in a bootcircle, so i cant put any files onto the phone. I tried to move files with Qick ADB Pusher, but always when I try to send the file from PC(win7) to one mini it says "Opeartion Failed! Exit Code 1". I tried this when i was in Bootloader. When I am in Recovery ADB doesnt even recognize the phone via USB.
If there is more explanation needed, please feel free to ask.
Thank you for your help in advance!
Greetins,
just2lose.
just2lose said:
Hey you two!
Did you solve your problem via PM, then maybe send me the log of it please.
I dont know exactly if we have the same problem, but i'll try to explain mine:
I wanted to put a ROM on my mini, because it is branded.
I unlocked the bootloader on the htc one mini and then put the twrp recovery on it. It seems to work.
Next i wanted to put super su on it, but I'm already stuck in a bootcircle, so i cant put any files onto the phone. I tried to move files with Qick ADB Pusher, but always when I try to send the file from PC(win7) to one mini it says "Opeartion Failed! Exit Code 1". I tried this when i was in Bootloader. When I am in Recovery ADB doesnt even recognize the phone via USB.
If there is more explanation needed, please feel free to ask.
Thank you for your help in advance!
Greetins,
just2lose.
Click to expand...
Click to collapse
Hi, can you let me know: Which ROM you want to flash, if you have attempted to s-off, and that you can boot to recovery?
Also, i'd advise against using utilities like the "pusher", please download this http://d-h.st/qmi and create a directory called c:\adb\ - move your ROM and SuperSU zip files here and extract the adb_windows.zip file to the directory.....
I did not attempt s-off, just normal htc dev bootloader.
First i wanted to flash Magio R4, but then i was thinking about Stock Rom Sense 5.5, which tr1gg3r84 uploaded.
i created folder and moved rom there. i also extracted the adb_windows zip there. what to do next? (i just wanna ask, because im a little scared of totaly breaking the phone now)
Thanks for now!
just2lose said:
I did not attempt s-off, just normal htc dev bootloader.
First i wanted to flash Magio R4, but then i was thinking about Stock Rom Sense 5.5, which tr1gg3r84 uploaded.
i created folder and moved rom there. i also extracted the adb_windows zip there. what to do next? (i just wanna ask, because im a little scared of totaly breaking the phone now)
Thanks for now!
Click to expand...
Click to collapse
Boot to recovery, then
adb push therom.zip /sdcard/
adb push UPDATE-SuperSU.zip /sdcard/
Remember to extract the boot.img from the ROM zip file, and after flashing the ROM and SuperSU, boot to bootloader and FASTBOOT menu then:
fastboot flash boot boot.img
you mean to push with the quick ADB Pusher? but in this programm (on PC) it doesnt find the phone whilie it is is recovery boot.
just2lose said:
you mean to push with the quick ADB Pusher? but in this programm (on PC) it doesnt find the phone whilie it is is recovery boot.
Click to expand...
Click to collapse
No, use the adb binary from the download link I posted......
If your phone isn't found, check the windows device manager and verify that you have ADB Android device listed..... if not, download adb drivers for windows and install - then plug your phone back in.....
You are using TWRP 2.6.0.0 recovery image from here right? http://forum.xda-developers.com/showthread.php?t=2418938
the adb.exe just pops up the cmd console, showing a lot of commands for half a second and then its gone again.
the android device is listed on device manager.
no, i did not use this one(twrp). i used some explanation how to do it from another forum and another file.
should i use this one now? how exactly to do that? theres no explanation :/
Open a command prompt in Windows and cd to c:\adb
Then when your phone is in recovery, type the adb commands I posted earlier.....
Sent from my HTC One mini using XDA Premium 4 mobile app
terdingb all
cmd says that the command is wrong or misstyped
(im in c:/adb typing: adb push rom.zip /sdcard/)
Is your ROM zip file called rom.zip? Can you post a screenshot?
Sent from my HTC One mini using XDA Premium 4 mobile app
ok got it.
now the rom and the supersu.zip are on the phone.
i cleared cache and dalvik and flashed both files(Stock Sense 5.5 4.3 Rooted Odex/Deodex;UPDATE-SuperSU-v1.86; both zip files) and , after that i went into fastboot and tried (fastboot folder) "fastboot flash boot boot.img" but cmd only says "waiting for device"
just2lose said:
ok got it.
now the rom and the supersu.zip are on the phone.
i cleared cache and dalvik and flashed both files(Stock Sense 5.5 4.3 Rooted Odex/Deodex;UPDATE-SuperSU-v1.86; both zip files) and , after that i went into fastboot and tried (fastboot folder) "fastboot flash boot boot.img" but cmd only says "waiting for device"
Click to expand...
Click to collapse
Check device manager on your pc, most likely the adb driver device isn't listed - if not, reboot your pc and try again.... This has happened to me several times......
ok now it worked. writing boot and so on .. finished. total time: 2.717.
i shut it down and started the phone again.
now it almost made the starting sound. after 5 boot cycles it played the whole starting sound and also showed the second screen with the "o1ne" and "beatsaudio" on the bottom.
but thats it. boot cycling in a different way now .
seems like it just doesnt want to work.
i'm so sorry that I am bothering you for so long now..
another idea?
thanks again!
edit: im gonna go through everything again with magio rom r5...
ok got it now. thanks a lot dude!
i deleted the rom files now from the phone but still there is 9gb used on the phone. this is way to much, isnt it?
is there a safe method to clean the whole phone .. something like c:format ?
thanks ³
No problem dood.....
Download an app called diskusage from the store - start it and choose storage card.... Post a screenshot please!
Sent via a weather balloon towed by a flock of seagulls. That's how this messaging stuff works, right?
after the phone went out of battery, it was in a boot cycle again after loading and rebooting.
flashed super su.zip again, but it didnt help. stupid me didnt do a backup yet. so do i have to install the rom again and do all the configs from scretch?
What's your hboot status? Locked/unlocked, s-on/s-off etc
Also, did you do, or install anything before your phone powered off?
Sent from my HTC One mini using XDA Premium 4 mobile app