Related
I rooted my phone without knowing about s-off and its s-on and i installed miui and i cant boot that room it gets to the miui logo and just sits there is there anyway at all to fix this
Edit:
ok now it wont turn i connect my usb to the phone and the orange light appears i get the sounds on windows saying its connected then it disconnects and then dose this over and over again so i have no idea what is going on please please help its really annoying me
If you are still s-on you need to manualy flash the boot.img or it will just boot loop. I use Flash Image GUI but there are other ways
Sent from my Vivid 4G using xda premium
Spectrejester said:
If you are still s-on you need to manualy flash the boot.img or it will just boot loop. I use Flash Image GUI but there are other ways
Sent from my Vivid 4G using xda premium
Click to expand...
Click to collapse
could u give me more info please
new problem
re edited to top post
Your battery is dead and cwm doesn't support off-mode charging, hence the reason you get the orange light but only for a moment. You can't charge the phone while its off..and you incorrectly flashed a custom rom. If you can find a way to charge your batt out of the phone you can fix this by either flashing the proper boot.IMG for the ROM from fastboot, or by running the appropriate ruu and starting from scratch. I highly recommend doing the s-off procedure. Its not difficult, and it makes customizing the phone so much simpler.
Sent from my PAC MAN Raider using XDA Premium
i have the same problem man did it just minutes before...i have only a black screen, the display gives a vibration feedback. i see the sdcards in windows but cant open them
What can i do help please!
Edit: Ok screen is on "htc" and keeps so for minutes and hours
Any solution?
N-rG said:
i have the same problem man did it just minutes before...i have only a black screen, the display gives a vibration feedback. i see the sdcards in windows but cant open them
What can i do help please!
Edit: Ok screen is on "htc" and keeps so for minutes and hours
Any solution?
Click to expand...
Click to collapse
Boot to bootloader (pwr and vol-). Does it say locked or unlocked? Does it say s-on or s-off? Select recovery. Does it still boot to custom recovery or do you get the android with the exclamation point? If the bootloader says locked, and you get the android with the !, you need to unlock the bootloader, fastboot flash a custom recovery, boot to that custom recovery, and flash your ROM. If bootloader is s-on, you'll also need to fastboot flash a boot.img that's compatible with the ROM you're flashing (can be found in the ROM's .zip)
homeslice976 said:
Boot to bootloader (pwr and vol-). Does it say locked or unlocked? Does it say s-on or s-off? Select recovery. Does it still boot to custom recovery or do you get the android with the exclamation point? If the bootloader says locked, and you get the android with the !, you need to unlock the bootloader, fastboot flash a custom recovery, boot to that custom recovery, and flash your ROM. If bootloader is s-on, you'll also need to fastboot flash a boot.img that's compatible with the ROM you're flashing (can be found in the ROM's .zip)
Click to expand...
Click to collapse
Thank you so much for your answer
It says "unlocked"
It says "s-on"
It boots to nothing. When i start the phone there is only standing "htc" nothing more happend. No explantion Mark But i can get into the bootloader.
Or what do you mean with "it still boot to custom recovery or do you get the android with the exclamation point?"
How do I do that with the boot.img? Please i am such a noob im so sorry i dont unterstand a lot im so angry about myself that i did it, please can you exactly tell me what i should do and what i need?
I did a backup before but there is no "boot.img"
And how can i use the boot.img wenn i cant get access to the sd memory?
N-rG said:
Thank you so much for your answer
It says "unlocked"
It says "s-on"
It boots to nothing. When i start the phone there is only standing "htc" nothing more happend. No explantion Mark But i can get into the bootloader.
Or what do you mean with "it still boot to custom recovery or do you get the android with the exclamation point?"
How do I do that with the boot.img? Please i am such a noob im so sorry i dont unterstand a lot im so angry about myself that i did it, please can you exactly tell me what i should do and what i need?
I did a backup before but there is no "boot.img"
And how can i use the boot.img wenn i cant get access to the sd memory?
Click to expand...
Click to collapse
When you boot to bootloader, scroll down and select recovery. What happens?
As far as flashing the boot.img, when you downloaded the ROM's .zip, inside the .zip should have been a file called boot.img. You need to drag that to the directory where you have fastboot installed, boot to bootloader, connect your phone, select fastboot. It should now say "fastboot usb". Now in the directory where you have fastboot and boot.img (with neither selected), shift+right click, choose "Open command window here". You need to enter "fastboot flash boot boot.img" and hit enter. Then reboot
At first, thaaank you so much for your help, i feel so lost....
Ah ok i understand, you mean the "[ROM][ICEss v 0.4][Stockish ICS/SENSE 3.6" -that is what i downloaded.
When i am in the bootloader menu and activate recovery the htc symbol appears with a white backround...nothing more happen for minutes
unfortuneately there is not boot.img in this zip
I did the whole procedure with the Vivid_All-In-One_Kit_v2.2 and not fastboot.
Ok i now downloaded fastboot and put it to c:/fastboot
I do what you say and reach your point " It should now say "fastboot usb" thats right, it works. But i dont have the boot.img where can i get it?
N-rG said:
At first, thaaank you so much for your help, i feel so lost....
Ah ok i understand, you mean the "[ROM][ICEss v 0.4][Stockish ICS/SENSE 3.6" -that is what i downloaded.
When i am in the bootloader menu and activate recovery the htc symbol appears with a white backround...nothing more happen for minutes
unfortuneately there is not boot.img in this zip
I did the whole procedure with the Vivid_All-In-One_Kit_v2.2 and not fastboot.
Ok i now downloaded fastboot and put it to c:/fastboot
I do what you say and reach your point " It should now say "fastboot usb" thats right, it works. But i dont have the boot.img where can i get it?
Click to expand...
Click to collapse
There's not a boot.img in the zip you downloaded? Then you need to read the thread and see what kernel they recommend, get the boot.img, and fastboot flash it. You're getting close.
It sounds like you may have lost your custom recovery along the way too (in which case more may have broke) - you'll need to get a custom recovery .img (wcx or twrp) and fastboot flash it (fastboot flash recovery <nameofrecovery>.img). Then fastboot flash boot.img, then boot to recovery and reflash the ROM and hopefully you'll be all set.
Thanks again, im getting closer! I read the whole thread and found that "Holics_Kernel_0730_S-ON" is recommended. I downloaded and found the boot.img I put it in the fastboot folder.
But i dont understand what do you mean with "you'll need to get a custom recovery .img (wcx or twrp)"
Do you mean the recovery i created with my old working Gingerbread or a recovery form the custom rum i downloaded?
When last, where can i get such a recovery.img?
Hey man btw. you gave me so much hope at the moment, thats incredible, thank you!
Check the dev section. Everything you will need is in the stickied threads. Twrp recovery also has its own thread
bypruv oculus
Okay i'll do meanwhile there is something new. I create use fastboot, the boot.img of the new kernel and do it with the command line like you said.
The phone now boots one step more to "htc quietly brilliant" and then restarts over and over again to this screen, like a loop.
---------- Post added at 11:42 PM ---------- Previous post was at 11:25 PM ----------
ahhh i reach Android System Recovry with several menus. I didnt find any help in google what i have to do now.
Backup google propritary System, nand backup, Nand Restore, Restore google proprietary System? Or something else?
No.. at this point you should wipe cache, dalvik cache, system, an data. This can all be done In Recovery's wipe menu. Them recovery should have a flash zip menu. Flash the ROM .zip
Put the brakes on!
I saw gingerbread...
When you boot to bootloader...
There is a line labeled hboot
What's the number next to it?
If its 1.85... you good...
If its 1.83... thou shalt find an ICS ruu for your carrier.
Almost none of the ROMs you find here run on 1.83
Sent from my Vivid 4G using Tapatalk 2
Good catch!
Hey,
i bring it to run! I restored every part manuall...system, cache, data. Only restore boot didnt work. I suggest its because Rom Manager/ClockworkMod didn't created such a file (boot.img) So i downloaded a custom kernel für Gingerbread.
Vola, handy startet, Os is on. Loggin into network worked!
BUT! I cannot use Wlan/wifi or mobile networking. I suppose its because the rom right?
I mentioned that i have the same phone here from my girlfriend.
How and can i make a boot.img of her phone? Please tell my how and then i have finished everything i hope
You can't. S*on devices can't flash boot.IMG or back up boot.IMG in recovery. You have to fast boot flash the boot.IMG. this is also why wifis broken
The kernel and ramdisk and some other things are packed into boot.IMG, and are made by ROM or kernel devs. Actually now that you're booting, you can use an app called flash image GUI to flash the boot.img
Ok I expressed something wrong, sorry (im not a native speaker u might noticed long before ^^ ). So i try again like I said i did the manuell recovery of everything except the boot.img.
Thats why i loaded this kernel for Gingerbread (http://forum.xda-developers.com/showthread.php?t=1351717) and installed the boot.img with fastboot "flash boot boot.img"
Fastboot said well done. Phone startet.
I think i understand what you are writing, but i dont understand which boot.img do you mean i need. I have no boot.img from my backup before flashing with custom rom without this boot.img i cant flash the not working one of the ICS on my phone am i right?
So thats why i thought i can take the phone of my girlfriend, create a boot.img and use it for my phone. So thats the only problem, i need working boot.img and then flash with fastboot oder the app you mentioned How to get the boot.img
SOLVED - check post 35
..and I don't know how to solve it. So, I would really need and appreciate your help!
Device:
m7ul s-off, currently unlocked, running cm 10.1 nightly
The problem:
I experienced reboots and fc's on various aosp roms as pa, cm and pac. cm is running best so far, on pa i lost data connection from time to time.
I tryed everything. I flashed sense roms, I flashed stock, I did a nandroid restore of stock ruu, relocked my bootloader, flashed stock recovery and everything possible to fix my device.
If I was lucky, it booted, but it shut down after a few seconds and kept bootlooping.
I can't get it back to stock and that really worries me. I did everything as explained but nothing worked.
Now to what I did with my device:
unlocked, flashed cwm, perm root
flashed cm, but coming from the nexus4 i was looking forward for pa rom
flashed a pa dev build, which was made for m7tmo. this might be the point where my troubles started. build was a bit buggy so
flashed trickdroid 6.0.0, flashed some tweaks and had major issues as no status bar and frequent reboots
went back to cm and from then on I just flashed pa or cm roms (gave pac a try but had even more issues)
everything else is already explained (the problem).
If there is any further information I have to provide you, just tell me. I don't really know much about logcat, but I could upload a log if that would help. All I see is hundreds of errors with QC-DS-LIB, LocSvc, kickstart and others..
I spent days on trying to fix my phone. I'm also afraid of bricking it with all the **** I try... Maybe someone here can help me find a solution. Please
Do you have the appropriate radio for your ROM?
http://forum.xda-developers.com/showthread.php?t=2245615
That might be the root of all evil...
I did flash 1.29.401.12 WWE OTA - 4A.14.3250.13_10.33.1150.01L while running the stable pa rom. currently I'm on 4A.13.3221.27_10.31.1131.05L (I guess stock?)
edit: it's from RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
I am not sure but all the stuff you did it is likely that something got messed up.
Which recovery do you use? Please flash that again with
fastboot erase cache
fastboot flash recovery recovery.img (*recovery.img = the exact name of the recovery as it is in your platform-tools folder) followed by
fastboot erase cache
Use only the USB cable that came with the One, and don't use a USB 3.0 under Windows 8. Maybe try a different computer as well.
Flash a Sense ROM that is close to stock, and a matching radio based.
Before flashing a ROM.zip, wipe cache/factory reset and dalvik cache within the recovery first.
Hope you get it all sorted
hardstuffmuc said:
I am not sure but all the stuff you did it is likely that something got messed up.
Which recovery do you use? Please flash that again with
fastboot erase cache
fastboot flash recovery recovery.img (*recovery.img = the exact name of the recovery as it is in your platform-tools folder) followed by
fastboot erase cache
Use only the USB cable that came with the One, and don't use a USB 3.0 under Windows 8. Maybe try a different computer as well.
Flash a Sense ROM that is close to stock, and a matching radio based.
Before flashing a ROM.zip, wipe cache/factory reset and dalvik cache within the recovery first.
Hope you get it all sorted
Click to expand...
Click to collapse
Did exactly what you said, phone got stuck on boot (with beatsaudio) for over 10 mins (this actually happened every time i tried flashing arhd). rebooted, was able to do a first setup after 3 mins. downloaded catlog, havent had the errors mentioned above so far. running smooth for now. will post again if some crazy **** happens.
Thanks!
And again, after installing some apps I got reboots. The only difference to aosp is, that I have to do a reboot by holding the home button, hence this rom gets stuck on the bootlogo. The aosp roms rebootet after 15 secs.
Sent from my HTC One using xda app-developers app
George_Mn said:
And again, after installing some apps I got reboots. The only difference to aosp is, that I have to do a reboot by holding the home button, hence this rom gets stuck on the bootlogo. The aosp roms rebootet after 15 secs.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Download the RUU for your device. boot to fastboot and relock bootloader, then install ruu.exe from PC. That will fix you up. Nandroid restore of stock ruu is different. The ruu will replace all partitions.. U have something wrong somewhere that roms dont touch i bet. The ruu should do it. If s-off and supercid you dont even need your exact ruu. Any ruu will do.
nugzo said:
Download the RUU for your device. boot to fastboot and relock bootloader, then install ruu.exe from PC. That will fix you up. Nandroid restore of stock ruu is different. The ruu will replace all partitions.. U have something wrong somewhere that roms dont touch i bet. The ruu should do it. If s-off and supercid you dont even need your exact ruu. Any ruu will do.
Click to expand...
Click to collapse
I have actually tried that. I also think it does not depend on the rom I use. Since I can't remember wether I relocked my bootloader before trying the ruu.exe I will try again.
I was also thinking about flashing boot.img but i'm afraid of bricking.
Sent from my HTC One using xda app-developers app
George_Mn said:
I have actually tried that. I also think it does not depend on the rom I use. Since I can't remember wether I relocked my bootloader before trying the ruu.exe I will try again.
I was also thinking about flashing boot.img but i'm afraid of bricking.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Just do the ruu again, it should fix you up. Boot.img is no big deal, it gets flashed with all roms. If ruu doesnt work please let us know if it successfully installed or not. If it will be like first time you powered it on (minus the s-off, that will stay) if it installed correctly. It will install correct radio and boot.img.
Have you changed your MID? i think you should just installl the latest ruu for your CID and MID.
Also have you installed different hboot? like the modded one or the eng hboot? If so have you flashed the original back? The RUU will install the correct hboot.
Sorry top say but If completed ruu doesnt fix it, its broke. Nothing software can do.
nugzo said:
Just do the ruu again, it should fix you up. Boot.img is no big deal, it gets flashed with all roms. If ruu doesnt work please let us know if it successfully installed or not. If it will be like first time you powered it on (minus the s-off, that will stay) if it installed correctly. It will install correct radio and boot.img.
Have you changed your MID? i think you should just installl the latest ruu for your CID and MID.
Also have you installed different hboot? like the modded one or the eng hboot? If so have you flashed the original back? The RUU will install the correct hboot.
Sorry top say but If completed ruu doesnt fix it, its broke. Nothing software can do.
Click to expand...
Click to collapse
No I haven't, getvar says my cid is 102 and my mid pn0710000
I think I have installed different hboot but as you said ruu will revert...
guess thats the right one?: RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
I could also try: RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13. 3227.06_10.27.1127.01_release_308001_signed_2_4.ex e
edit: omg just checked md5sum of the ruu I used earlier... there should be a tool automatically checking every md5sum. no wonder it bootlooped..
Stuck on bootscreen after installing the ruu.exe
no fastboot usb, no custom recovery
what can i do now?
George_Mn said:
Stuck on bootscreen after installing the ruu.exe
no fastboot usb, no custom recovery
what can i do now?
Click to expand...
Click to collapse
Still stuck? What happened, did pc say it finished successfully ? Takes a few minutes after ruu. Which ruu did u use?
nugzo said:
Still stuck? What happened, did pc say it finished successfully ? Takes a few minutes after ruu. Which ruu did u use?
Click to expand...
Click to collapse
I used RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
pc said it finished successfully
turned it off to not kill the battery
waited for over 10 minutes.
currently talking to htc support usa since the german support is asleep..
i can access the bootloader, thats all
George_Mn said:
I used RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
pc said it finished successfully
turned it off to not kill the battery
waited for over 10 minutes.
currently talking to htc support usa since the german support is asleep..
i can access the bootloader, thats all
Click to expand...
Click to collapse
If you wish you can unlock again, install custom recovery and then side load a rom. I'm afraid HTC will just have you try the ruu again. Or tell you it's broke.
How long did the ruu install take? Did it restart phone a few times? If it was me, I'd unlock again and install a custom rom. If that doesn't work I don't know what else to try..tried everything. Most likely Something wrong with the hardware
nugzo said:
If you wish you can unlock again, install custom recovery and then side load a rom.
Click to expand...
Click to collapse
I don't think so, my pc does not recognize my phone because usb debugging is not enabled.. any solution?
in stock recovery it says MounT SDCARD failed, so I will try fixing that by performing a few factory resets lol
George_Mn said:
I don't think so, my pc does not recognize my phone because usb debugging is not enabled.. any solution?
in stock recovery it says MounT SDCARD failed, so I will try fixing that by performing a few factory resets lol
Click to expand...
Click to collapse
When in fastboot it doesn't matter if debugging is enabled. It must say fastboot USB . If not select fastboot and press power
What hboot do you have now? Since you r s off I don't know if boot loader needs to be unlocked. If you can get to fastboot and be seen by pc,download twrp recovery and put it in your adb folder. Then "fastboot flash recovery filename.img" then u can side load.
nugzo said:
When in fastboot it doesn't matter if debugging is enabled. It must say fastboot USB . If not select fastboot and press power
What hboot do you have now? Since you r s off I don't know if boot loader needs to be unlocked. If you can get to fastboot and be seen by pc,download twrp recovery and put it in your adb folder. Then "fastboot flash recovery filename.img" then u can side load.
Click to expand...
Click to collapse
omg i'm such a stupid person... I was checking my usb ports and unplugged the cable, plugged it to my phone and yeah guess what there was no FASTBOOT USB there was just FASTBOOT ...
Okay so I can still get a rom on it that's really good news. But, there is still the other problem..
George_Mn said:
omg i'm such a stupid person... I was checking my usb ports and unplugged the cable, plugged it to my phone and yeah guess what there was no FASTBOOT USB there was just FASTBOOT ...
Okay so I can still get a rom on it that's really good news. But, there is still the other problem..
Click to expand...
Click to collapse
What's the other problem? I can help
George_Mn said:
omg i'm such a stupid person... I was checking my usb ports and unplugged the cable, plugged it to my phone and yeah guess what there was no FASTBOOT USB there was just FASTBOOT ...
Okay so I can still get a rom on it that's really good news. But, there is still the other problem..
Click to expand...
Click to collapse
What's the other prob.. We're knocking them out.. Hang in there
---------- Post added at 08:02 PM ---------- Previous post was at 07:51 PM ----------
MacHackz said:
What's the other problem? I can help
Click to expand...
Click to collapse
Mac does he have to unlock boot loader if he's s off? To flash recovery?
MacHackz said:
What's the other problem? I can help
Click to expand...
Click to collapse
Well I've been through this (ruu>stuck on boot>unlock>flash cwm>sideload rom) twice.
The problems are still reboots from time to time and app shut downs or fcs. It happens with every rom i tryed. on sense roms its stuck on bootscreen until i reboot with power button, on aosp it just reboots within 15 secs
I'll have to admit, I did the ruu on win8 with usb 3.0
When does it reboot? Sometimes upon installing apps, accessing play store, on landscape mode, on unlocking sim. Much to often to just live with it..
just sideloaded cm10.1, it's alive..
My friend's phone is stuck in bootloop and I believe it's soft bricked.
It's a stock brand new HTC One M7.
It was updating one day and he said it might have got corrupted because it just shut down and when it booted back up it was stuck at the HTC Screen and wouldn't do anything.
Over the last week I have been trying to unbrick it.
It's LOCKED and S-ON Sprint HTC One M7.
I did a factory reset, wiped cache, dalvic cache, reboot. I tried putting in fastboot and flashing RUU on it but it kept failing because the RUU I had was a lower version of the image than the current one on the phone and I read online that I can only flash backwards if it's S-OFF.
Any help?
Thanks!
technocrat7 said:
My friend's phone is stuck in bootloop and I believe it's soft bricked.
It's a stock brand new HTC One M7.
It was updating one day and he said it might have got corrupted because it just shut down and when it booted back up it was stuck at the HTC Screen and wouldn't do anything.
Over the last week I have been trying to unbrick it.
It's LOCKED and S-ON Sprint HTC One M7.
I did a factory reset, wiped cache, dalvic cache, reboot. I tried putting in fastboot and flashing RUU on it but it kept failing because the RUU I had was a lower version of the image than the current one on the phone and I read online that I can only flash backwards if it's S-OFF.
Any help?
Thanks!
Click to expand...
Click to collapse
if the phone is new (never tampered with) and still under warranty, send it back for repair or replacement
s-off and run the ruu
unlock bootloader, flash a custom recovery and flash a rom or a nandroid backup
post in the sprint htc one forum for more detailed info
So the first step is S-OFF because I don't think k the warranty is on it.
And then custom recovery and what was the part with a custom nandroid backup? Can I run someone else's nandroid?
And if I put S-OFF on it, I can flash an older version of RUU right?
Sent from my HTC One_M8 using XDA Free mobile app
I'm pretty sure that in order to S-off you will need to be booted up first? The good news is that you can flash the full factory RUU with a s-on boot loader locked device so you may need to figure out how to do that first. Do you have an adb/fastboot environment set up? If so you are practically there. On a side note, I have seen no less than 3 m7s fail and softbrick on the first attempt at applying an ota, but it was always after S-off and a conversion to fully stock gpe (these were gsm models). I figured it was just because of the mods but who knows. Anyway, if you can locate and install a fully stock sprint RUU you should be back to where you were before the ota at which point you can proceed with whatever else you want to do.
technocrat7 said:
So the first step is S-OFF because I don't think k the warranty is on it.
And then custom recovery and what was the part with a custom nandroid backup? Can I run someone else's nandroid?
And if I put S-OFF on it, I can flash an older version of RUU right?
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
sorry for the confusion, this was not steps to follow (1-2-3-4) but either 1 or 2 or 3 or 4
if you go for option 2, yes you can flash older ruu.
for option 3, yes you can flash someone else nandroid, but it must be for your phone variant (sprint) and the ideal nandroid backup should be the same OS version.
---------- Post added at 02:34 PM ---------- Previous post was at 02:29 PM ----------
dougeedug said:
I'm pretty sure that in order to S-off you will need to be booted up first?
Click to expand...
Click to collapse
Right, you need a booted rom to s-off. (at least for the M7_UL dont know for the srpint variant)
The good news is that you can flash the full factory RUU with a s-on boot loader locked device so you may need to figure out how to do that first.
Click to expand...
Click to collapse
Not exactly, you can only flash ruu with a s-on device (and locked/relocked bootloader) if the ruu is same of higher version. In that case the OP need to find another ruu (if any available)
Yeah, I have a 4.2 image when loading RUU, therefore I'm not able to use an RUU.
So what else do I need to do?
And I do have an adb and fastboot environment set up, yes.
Should I instead just S-OFF It, put a custom bootloader on it and then flash a custom recovery?
Yes if you can achieve s-off you can put any RUU you want on it and that will rule out software issues.
Okay so I unlocked it.
However I looked online how to do S-OFF and all the articles I found said the phone has to be on an functional to enable USB debugging mode and to run the appropriate programs to make it S-OFF.
Is there any other way to do it?
Now that you are bootloader unlocked, flash a custom recovery and from there a rom. That should get you back to life so you can proceed however you wish.
I have a custom recovery.
TWRP 2.6.0.0 or something. And I loaded into it and my phone got stuck and the touch wouldn't work. It says "slide to unlock" and sliding doesn't work.
What do I do now? I can't even reboot the light keeps flashing and I even tried under a bright light and still nothing.
I'm letting the battery die to restart. When u do restart it, what do I do about the bad bootloader? Can I just put another one on there? I want Philz now after that terrible experience.
technocrat7 said:
I have a custom recovery.
TWRP 2.6.0.0 or something. .
Click to expand...
Click to collapse
This is very alarming! Be double sure you are flashing exactly what you need. The CWM you would need is 6.0.4.8 found on this page. I'm not sure what TWRP version is suitable as I don't use it. I don't dislike it. I have used it and it has worked.
Can I just do the same thing I did before to install a custom recovery?
Will it override the one I have currently?
Thanks!
technocrat7 said:
Can I just do the same thing I did before to install a custom recovery?
Will it override the one I have currently?
Thanks!
Click to expand...
Click to collapse
We will have to see what it does after you let it die. The way your phone is acting is not good. Unfortunately, we must keep in mind that it may be a hardware fault causing all of this from the start. If it will still charge offline, then you'll get a chance to see if you can power it up into the bootloader and get fastbootUSB.
technocrat7 said:
Can I just do the same thing I did before to install a custom recovery?
Will it override the one I have currently?
Thanks!
Click to expand...
Click to collapse
why are you waiting for it to die ? if you want to get out of recovery and tough isn't working, just hold down the power button and the volume down until the lights on the bottom flash 10 to 15 times, when it goes off, release the power button but continue to hold the volume down, you are now in the bootloader, or should be.
and yes, if you flash another recovery it will overwrite the one that's on there, unfortunately, most rom's require TWRP
---------- Post added at 03:28 AM ---------- Previous post was at 03:22 AM ----------
I also just noticed you have the Sprint M7, you cant use the normal recoveries or rom's, they wont work, you need to use the ones built for your phone, which is different to the normal gsm version.
I would try twrp 2.6.3.3 or this http://mdmower.cmphys.com/twrp-m7spr/ a newer custom compiled twrp so your os version dont get wiped on bootloader.
Dang, being with Sprint complicates things?
So will that one be safe to put on my phone? And that means I can't get Philz huh?
technocrat7 said:
Dang, being with Sprint complicates things?
So will that one be safe to put on my phone? And that means I can't get Philz huh?
Click to expand...
Click to collapse
No it doesn't complicate things, it's the same procedure, it's like with anything, you just have to make sure you get the right files. Your phone is cdma not gsm.
---------- Post added at 04:28 AM ---------- Previous post was at 04:17 AM ----------
http://forum.xda-developers.com/sprint-htc-one?nocache=1&z=1858146956656128
You can find all of those right files there
Okay thank you!
It is unlocked, rooted and had a custom recovery on it!
Now the last thing I need help with is, getting S-OFF because I still can't boot up the phone.
So now I just need to get S-OFF and then flash a custom ROM image on there and flash a custom image on it or something.
All I see when it boots up is the HTC screen.
technocrat7 said:
Okay thank you!
It is unlocked, rooted and had a custom recovery on it!
Now the last thing I need help with is, getting S-OFF because I still can't boot up the phone.
So now I just need to get S-OFF and then flash a custom ROM image on there and flash a custom image on it or something.
All I see when it boots up is the HTC screen.
Click to expand...
Click to collapse
You need a working Rom on it to go s-off, all s-off tools are run from an android booted phone, so download a Rom of your choice, in your case a sense Rom, make sure you get it from the link I supplied earlier for your particular phone, move it to the same folder where your adb and fastboot are on your computer, boot your phone into recovery (main screen only, no sub menus) and plug it into your computer, the type
adb push NAME_OF_ROM.zip /sdcard/
Takes a while so be patient, the command window will let you know when it's done.
Unplug your phone and in recovery select install, select your Rom from the list and follow the instructions
Seanie280672 said:
You need a working Rom on it to go s-off, all s-off tools are run from an android booted phone, so download a Rom of your choice, in your case a sense Rom, make sure you get it from the link I supplied earlier for your particular phone, move it to the same folder where your adb and fastboot are on your computer, boot your phone into recovery (main screen only, no sub menus) and plug it into your computer, the type
adb push NAME_OF_ROM.zip /sdcard/
Takes a while so be patient, the command window will let you know when it's done.
Unplug your phone and in recovery select install, select your Rom from the list and follow the instructions
Click to expand...
Click to collapse
So there's a slight problem.
"ADB Devices" doesn't show anything, it says "Devices not found"
The reason I would say is because it does not have USB Debugging enabled.
And I can't get into the phone to enable it because i'm not at that point yet.
Is there anything else I can do besides "adb push" to get the file on there?
Fastboot stuff works fine.
I went to the link you provided and found CynogenMod 11 I wanted to put on there.
After looking inside of the ZIP I downloaded there's a .img file inside called "boot.img" can I do anything with that?
Thanks!
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Burky1996 said:
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Click to expand...
Click to collapse
Try re download the zip (or try an other rom)maybe you just got an false download. i also had some trouble with my m7 back in the day.
But in your case now you are stuck with no os or bootloop, i give you as advice to follow an soft unbrick method it worked for me, or if you have an usb otg cable and usb or and usb otg thumbstick, put the rom on that usb and connect it to your phone and then try to flash it (if your using twrp you have an option to choose from wich storage you want to use)
Also a piece of advice, when flashing roms, kernels etc please have your phone charged above 50% (just in case).
Sent from my HUAWEI P7-L10 using XDA Free mobile app
---------- Post added at 09:28 PM ---------- Previous post was at 09:27 PM ----------
its the peanut said:
Try re download the zip (or try an other rom)maybe you just got an false download. i also had some trouble with my m7 back in the day.
But in your case now you are stuck with no os or bootloop, i give you as advice to follow an soft unbrick method it worked for me, or if you have an usb otg cable and usb or and usb otg thumbstick, put the rom on that usb and connect it to your phone and then try to flash it (if your using twrp you have an option to choose from wich storage you want to use)
Also a piece of advice, when flashing roms, kernels etc please have your phone charged above 50% (just in case).
Sent from my HUAWEI P7-L10 using XDA Free mobile app
Click to expand...
Click to collapse
Also make sure you downloaded the rom made for your phone model!
Sent from my HUAWEI P7-L10 using XDA Free mobile app
Burky1996 said:
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Click to expand...
Click to collapse
Can you please post the output of
Code:
fastboot getvar all
please remove your imei and serial number.
Depending on which variant of the M7 you have you probably just need a different version of recovery to install a CM rom. I think they prefer TWRP 2.7.x.x. Post the getvar and we can see what you have. then I can give you a better informed instruction. :good:
P.s also check the md5 of the rom zip you downloaded. Use this tool www.winmd5.com the correct md5 should be listed with the link you downloaded the rom from
failed to mount /dev/block/blah blah blah = needs "block:by-name" support which twrp 2.6.3.3 doesn't have
everything explained here
So update your recovery
and do what danny said above so he can confirm you have the right rom/recovery for your device.
Burky1996 said:
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Click to expand...
Click to collapse
Your getvar looks fine this rom should work fine with your device. Download this version of TWRP https://www.androidfilehost.com/?fid=23501681358561860 (2.7.1.2). dropthe file in your fastboot folder and flash it with fastboot.
Code:
fastboot flash recovery "name-of-recovery".img
fastboot erase cache
fastboot reboot-bootloader
Once thats done reflash the rom with the new version of TWRP. It should flash just fine :good:
iv managed to flash cm12.1 now, thanks guys, is there anyway i could get the HTC software back on.
Burky1996 said:
iv managed to flash cm12.1 now, thanks guys, is there anyway i could get the HTC software back on.
Click to expand...
Click to collapse
There are a number of ways to return to stock software. You can simply flash a stock rom through twrp or use a stock nandroid. look for rom that match your version main. 7.19.401.22
I think there is even an lollipop 7.19.401.22 RUU for your device but I'm not sure if it will work with s-on though because it's a zip but it certainly wouldnt hurt to try it though. You will need to relock your bootloader and flash it with fastboot.
I'll edit this post with links when I find them unless some one beats me to it
Hey Dan do you think we could skype and you could talk me through it, it would be much easier?
Burky1996 said:
Hey Dan do you think we could skype and you could talk me through it, it would be much easier?
Click to expand...
Click to collapse
Sorry I am at work so availability is scetchy. I found the ruu but it's for the older 7.19.401.2 lollipop, this won't work for you because your s-on. Downgrading firmware is only possible with s-off.
You can use this stock rom though http://forum.xda-developers.com/htc-one/development/rom-100-pure-stock-5-0-2-7-19-401-2-t3044041 just flash it with twrp. The thread recommends TWRP 2.8.5.X no need to relock the bootloader or anything silly, just flash it like any other rom :good:
You'll notice that this rom is also for the older 7.19.401.2 so you will need to install the last OTA update to bring your rom in line with your firmware. Flash this recovery with the same method as twrp. (Stock recovery required for installing the OTA) http://sourceforge.net/projects/htcone/files/Recovery/STOCK/7.19.401.2_recovery.img/download reboot then just go to Settings>About>Check for updates.
Danny201281 said:
Sorry I am at work so availability is scetchy. I found the ruu but it's for the older 7.19.401.2 lollipop, this won't work for you because your s-on. Downgrading firmware is only possible with s-off.
You can use this stock rom though http://forum.xda-developers.com/htc-one/development/rom-100-pure-stock-5-0-2-7-19-401-2-t3044041 just flash it with twrp. The thread recommends TWRP 2.8.5.X no need to relock the bootloader or anything silly, just flash it like any other rom :good:
You'll notice that this rom is also for the older 7.19.401.2 so you will need to install the last OTA update to bring your rom in line with your firmware. Flash this recovery with the same method as twrp. (Stock recovery required for installing the OTA) http://sourceforge.net/projects/htcone/files/Recovery/STOCK/7.19.401.2_recovery.img/download reboot then just go to Settings>About>Check for updates.
Click to expand...
Click to collapse
i did what you said when i applied the system update my phone turned on booted to a white screen with the green htc logo then it turned off the battery symbol came up its like its turned off. i tryed to lock the boot loader to see if it would work then but it never, when i appy the update it dosent even boot into the recovery.
i did what you said when i applied the system update my phone turned on booted to a white screen with the green htc logo then it turned off the battery symbol came up its like its turned off. i tryed to lock the boot loader to see if it would work then but it never, when i appy the update it dosent even boot into the recovery.
Burky1996 said:
i did what you said when i applied the system update my phone turned on booted to a white screen with the green htc logo then it turned off the battery symbol came up its like its turned off. i tryed to lock the boot loader to see if it would work then but it never, when i appy the update it dosent even boot into the recovery.
Click to expand...
Click to collapse
Okay try this. Download the OTA but select the option "Install Later" connect your m7 to your pc and browse your storage. In the download folder on your phone you should find the OTA in zip format. Copy it to your pc.
Now open the OTA zip on your pc. Inside you'll find another zip called "firmware.zip" extract it then open it. Inside you'll find a recovery.img. extract the recovery file and flash it with fastboot. Now reboot to android and continue to install the OTA. :fingers-crossed:
Sent from my SM-T230 using Tapatalk
im going to have to unlock the boot loader again and then do it
Burky1996 said:
im going to have to unlock the boot loader again and then do it
Click to expand...
Click to collapse
Yes you will need to unlock the bootloader to flash the recovery, Dont forget to fastboot erase cache after flashing the recovery that is cruicial. You don't need to be relocked to install the OTA though.
When you select install now, the device should reboot to the Stock Recovery. At first the screen will just be black for a short while. Then you'll see an image of a phone with a Green ring and download arrow. If you hold Volume up and press the power button you will see the Stock Recovery and its progress in installing the OTA.
I'm not sure why your device was hanging on boot after installing the OTA. Maybe a bad recovery.img. that's why I say to get the recovery from the OTA file.
its still not working so i mite just install twrp and restore to cm12.1
Burky1996 said:
im going to have to unlock the boot loader again and then do it
Click to expand...
Click to collapse
Yes you will need to unlock the bootloader to flash the recovery, Dont forget to fastboot erase cache after flashing the recovery that is cruicial. You don't need to be relocked to install the OTA though.
When you select install now, the device should reboot to the Stock Recovery. At first the screen will just be black for a short while. Then you'll see an image of a phone with a Green ring and download arrow. If you hold Volume up and press the power button you will see the Stock Recovery and its progress in installing the OTA.
I'm not sure why your device was hanging on boot after installing the OTA. Maybe a bad recovery.img. that's why I say to get the recovery from the OTA file.
Danny201281 said:
Sorry I am at work so availability is scetchy. I found the ruu but it's for the older 7.19.401.2 lollipop, this won't work for you because your s-on. Downgrading firmware is only possible with s-off.
You can use this stock rom though http://forum.xda-developers.com/htc-one/development/rom-100-pure-stock-5-0-2-7-19-401-2-t3044041 just flash it with twrp. The thread recommends TWRP 2.8.5.X no need to relock the bootloader or anything silly, just flash it like any other rom :good:
You'll notice that this rom is also for the older 7.19.401.2 so you will need to install the last OTA update to bring your rom in line with your firmware. Flash this recovery with the same method as twrp. (Stock recovery required for installing the OTA) http://sourceforge.net/projects/htcone/files/Recovery/STOCK/7.19.401.2_recovery.img/download reboot then just go to Settings>About>Check for updates.
Click to expand...
Click to collapse
could it be not working coz my hboot has changed to 1.51.
Burky1996 said:
could it be not working coz my hboot has changed to 1.51.
Click to expand...
Click to collapse
Your still stuck with this? Try starting the process over, but do not relock your bootloader at any point.
Wipe system data and cache partitions with TWRP Advanced wipe
Flash the Rom with twrp as a clean install.
Reboot and download the OTA. Choose install later, then copy the OTA to your pc. Extract the Stock Recovery and flash it with fastboot. Reboot and install the OTA.
But do not relock your boot loader. Because when you unlock the bootloader, it wipes the device including the data/preload folder. If the preload folder is not intact the OTA will fail
Sent from my M7 Running ARHD 92.x
ok, i am stuck on my boot up screen. i flashed a zip file xposed arm zip. after the reboot it will not pass the boot animation screen. now on my old Motorola phone, i would do the pwr + vol keys to boot back in to recovery. well this does no work on my X. any one have any ideas. I am rooted, unlocked, twrp was installed from play store, & i did do a back up. thanks
JWACK72 said:
ok, i am stuck on my boot up screen. i flashed a zip file xposed arm zip. after the reboot it will not pass the boot animation screen. now on my old Motorola phone, i would do the pwr + vol keys to boot back in to recovery. well this does no work on my X. any one have any ideas. I am rooted, unlocked, twrp was installed from play store, & i did do a back up. thanks
Click to expand...
Click to collapse
What device do you have, XT1095, XT1097, etc? And you are not able to boot into the bootloader using vol down + power correct?
It was a 1096, now its trash. it would go into fastboot, but could not get into twrp recovery. its done. RIP
JWACK72 said:
It was a 1096, now its trash. it would go into fastboot, but could not get into twrp recovery. its done. RIP
Click to expand...
Click to collapse
If it boots to fastboot, it's not dead. Just reflash the recovery and you're good to go.
Sent from my XT1095 using Tapatalk
Was there a resolution for this? I'm having a similar problem. I'm not sure how I got to this status, but here's what I'm dealing with:
Device: XT1095
Bootloader: Unlocked
Rooted, ROM - Resurrection Remix, TWRP
Turning on the phone reaches the RR bootsplash and proceeds to bootloop.
When holding down the power and volume down, it will enter fastboot.
When I try to open TWRP recovery, it'll show the blue TWRP screen and just sit there.
I have tried to reinstall TWRP, but that has no effect. I didn't want to manually flash another ROM or go back to stock because at least now it seems USB debugging is on and if I flashed a ROM I cant be sure I'd be able to turn it on. Do any of you pros have some ideas hove I can get back into my phone? Thanks
bibbin said:
I have tried to reinstall TWRP, but that has no effect. I didn't want to manually flash another ROM or go back to stock because at least now it seems USB debugging is on and if I flashed a ROM I cant be sure I'd be able to turn it on. Do any of you pros have some ideas hove I can get back into my phone? Thanks
Click to expand...
Click to collapse
Do you have a USB-OTG device plugged in while trying to start TWRP? If so remove it, you can mount it after TWRP starts if this helps.
Have you tried a different build of TWRP? I'm currently using the one built by invisiblek, one of the CM devs for the victara. It was built and posted on December 8th and is here: http://www.invisiblek.org/twrp/twrp_2.8.7.0-0624b8bd_victara.img
Have you tried flashing the stock recovery to see if that will start? If it does, you could use the factory reset option there and then try reinstalling TWRP. (TWRP has a settings directory in /sdcard and maybe that is corrupted.)
There have been a few people posting with this problem but I've not seen a definitive fix for it.
Thank for the quick response. No, I don't have USB-OTG inserted. It is using TWRP 2.8.7.1. No, I haven't tried installing the version you mentioned. What I did do was attempt to flash the pre-installed TWRP 2.8.1.0 via MOTO X TOOLKIT. It failed. I'm not very experienced at using ADB manually. As I mentioned, I've been reluctant to flash another ROM (custom or stock) because I don't want to get stuck with USB debugging inactive with no way to get in far enough to reactivate it.
---------- Post added at 04:32 PM ---------- Previous post was at 03:40 PM ----------
If I manage to install the invisiblek TWRP and it opens properly will I then be able to restore the backups created with TWRP 2.8.7.1?
If that's the case, I need to find a tutorial on installing TWRP manually via ADB, right? I usually install TWRP via TWRP Manager.
bibbin said:
Thank for the quick response. No, I don't have USB-OTG inserted. It is using TWRP 2.8.7.1. No, I haven't tried installing the version you mentioned. What I did do was attempt to flash the pre-installed TWRP 2.8.1.0 via MOTO X TOOLKIT. It failed. I'm not very experienced at using ADB manually. As I mentioned, I've been reluctant to flash another ROM (custom or stock) because I don't want to get stuck with USB debugging inactive with no way to get in far enough to reactivate it.
---------- Post added at 04:32 PM ---------- Previous post was at 03:40 PM ----------
If I manage to install the invisiblek TWRP and it opens properly will I then be able to restore the backups created with TWRP 2.8.7.1?
If that's the case, I need to find a tutorial on installing TWRP manually via ADB, right? I usually install TWRP via TWRP Manager.
Click to expand...
Click to collapse
That's interesting, the TWRP Manager has never worked correctly for me although it's been a long time since I've tried it.
To flash manually, you actually need fastboot which is usually installed along with adb. If you open a command window, and type in fastboot and it runs, the rest is pretty easy. If it doesn't run, this thread has the 15 second ADB/Fastboot installer, select to install it system-wide: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Download the recovery image, rename the file to twrp.img, then open a command window in the folder where you downloaded it (type cmd then Enter in the address line at the top of the folder window.)
When the command window is open and the phone is in bootloader mode and connected to the computer with the USB cable, enter the command "fastboot device" (without the quotes) If everything is working it will list the serial number of your phone.
Then enter "fastboot flash recovery twrp.img" (without the quotes) to start the flashing process, ignore the size mismatch message. It will only take a few seconds to complete.
Use the volume down key to highlight recovery, then volume up to select it. Hopefully TWRP will boot up and you'll be good to go!
Well, reinstalling TWRP didn't fix it. Thoughts? Anyone?
bibbin said:
Well, reinstalling TWRP didn't fix it. Thoughts? Anyone?
Click to expand...
Click to collapse
Reflash stock rom from fastboot.
Sent from my XT1095 using Tapatalk
UPDATE: Thanks all. Well, after fiddling around with various methods of reinstalling TWRP, I managed to get it reinstalled and all is back to normal now.