Hi guys,
I have a weird problem. I want to disable the HTC start-up sound, but if I try with adb, it says HTC_Sense5_Boot.mp3 is a read-only file system.
So I tried with fx xplorer. I checked "Mount Read-Write" and tried to rename or even delete the file. But every time when I uncheck "Mount Read-Write" the file just pops back like it was before.
Does anyone know what's the problem here? With my old Phone it worked like a charm!
I think you need an unsecured kernel.
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
Hedied4me said:
I think you need an unsecured kernel.
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
Click to expand...
Click to collapse
How do I get one? And why do I need that? My Htc One SV didn't need it. Is this some extra protection from HTC?
Well first you need root. Then the kernel you need depends on whether your on kitkat or jellybean and zara_cl or zara_ul.
http://forum.xda-developers.com/showthread.php?p=54392909
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
Oké thanks, I do have root and I'm still on JB (4.2.2). So I downloaded the file but I don't know what to do with it. Do I have to put it on my sd and start up recovery, or do I have to put it in my pc where I have fastboot stored?
EDIT: I already found it, just not sure if I have to rename the file to boot.img?
Its not necessary but if u want to
So, I flashed the kernel but it still won't work! How frustrating is this!! Does it by any change have anything to do with the fact that I also can't get S-OFF? Maybe there is something blocking the whole process?
Just tried firewater to S-OFF, but now I got the message: ERROR: kernel contains HTC
anti-firewater patch! ***** Try again with a different kernel *****. Is there a way to check if I have the unsecured kernel I flashed?
Use rumrunner to get s-off http://forum.xda-developers.com/showthread.php?t=2827793
I already tried that for a couple of times but then I get the message: FATAL: Download updated package at www.rumrunner.us
Press ENTER to exit
EDIT: It looks like the kernel can't install. I just tried it again, but nothing changes.....
Delete that mp3 startup sound with TWRP's file manager.
For S-off look through that linked thread. The gist seems to be try a different network and disable firewall/antivirus/try linux
mrplowdan said:
Delete that mp3 startup sound with TWRP's file manager.
For S-off look through that linked thread. The gist seems to be try a different network and disable firewall/antivirus/try linux
Click to expand...
Click to collapse
According to the twrp website there is no twrp for zara_ul.
I don't know linux unfortunately...
Smellie2 said:
According to the twrp website there is no twrp for zara_ul.
I don't know linux unfortunately...
Click to expand...
Click to collapse
Yes there is for zara-ul http://forum.xda-developers.com/showthread.php?t=2804520
Child's Play said:
Yes there is for zara-ul http://forum.xda-developers.com/showthread.php?t=2804520
Click to expand...
Click to collapse
But I'm not on KK, I have 4.2.2
Smellie2 said:
But I'm not on KK, I have 4.2.2
Click to expand...
Click to collapse
the one on twrp's website is for 4.2.2, the cl version will work on ul
mrplowdan said:
Delete that mp3 startup sound with TWRP's file manager.
For S-off look through that linked thread. The gist seems to be try a different network and disable firewall/antivirus/try linux
Click to expand...
Click to collapse
A bit late to react due to the holidays, but I've managed to get the boot-up sound off. Now further with Linux :silly:
I'm not sure if I can write about the further problems here, since I got rid of my initial problem, but I can't get S-OFF. I tried with Linux but got the same FATAL error as I did with windows. So, I suspected my HTC not be able to flash the unsecure kernel. I googled and found out about using HTC Dumlock. I followed instructions and opened the app. My device didn't automatically boot into recovery, so I rebooted my phone. It just rebooted! It didn't go into recovery as it should have. So I went into recovery manually and clicked "Restore Original Boot". Then I tried to flash the kernel through adb again, but all I get is "waiting for device". (I did check adb devices first and it found my phone). So, I now can't use the fastboot command anymore, and I can't find a bootable zip for the unsecure JB zara ul kernel. Does anybody have any idea why my phone is giving me such a hard time? It's like there is an option is blocked or something which won't let me do the things that everybody else can. Is it possible the unlocking of my bootloadere didn't go completely or something?
You have flash the kernel from fastboot mode, if adb devices returns anything your not in fastboot mode.
Regarding s-off, make sure to try different cables and if it's still not working try another computer.
To test if your kernel is insecure once your phone is booted normally, adb shell should give you a prompt ending with a #, if it's a $ it's not insecure
mrplowdan said:
You have flash the kernel from fastboot mode, if adb devices returns anything your not in fastboot mode.
Regarding s-off, make sure to try different cables and if it's still not working try another computer.
To test if your kernel is insecure once your phone is booted normally, adb shell should give you a prompt ending with a #, if it's a $ it's not insecure
Click to expand...
Click to collapse
I now have the # when I type in adb shell, but I don't understand why in software - kernel in the phone it's still named the same as before flashing.
What S-OFF is regarding, I tried everything! Different cables, different computers, Windows, Linux, rumrunner, firewater.... it's just not working!! Drives me crazy.
Smellie2 said:
I now have the # when I type in adb shell, but I don't understand why in software - kernel in the phone it's still named the same as before flashing.
What S-OFF is regarding, I tried everything! Different cables, different computers, Windows, Linux, rumrunner, firewater.... it's just not working!! Drives me crazy.
Click to expand...
Click to collapse
If u keep getting an error msg saying "fatal: download updated package", its a server-side issue. U need to tell beaups in irc that u've tried everything. He can fix the issue so that u can run rumrunner again. This is not the 1st time. It has happened over and over again
I FINALLY, FINALLY have S-OFF!! I replaced the insecure kernel I had first with the one from this thread:
http://forum.xda-developers.com/des...x-roms-mods-recoveries-backups-tools-t2804427
and then tried again. And what-do-you-know! It worked!!!
Related
Backstory: I tried flashing android revolution for the amaze once, and it didn't work (error 1) left it alone for a bit after recovering it, went back to bulletproof and flashed faux .009 kernel, then decided to try again...
Well I'll try to make this brief, sorry if I'm posting in the wrong subforum but here goes, I tried going from bulletproof 2.5.0 to Android Revolution HD and didn't flash the superwipe .zip (lazy me). The install failed with the same error 1, only this time I can't boot back into recovery. Booting to bootloader works but when I tried going into recovery I see it pop up for maybe a fraction of a second before the phone reboots.
I've tried reflashing clockwork mod but no dice
any sort of tips you folks can give me to steer me in the right direction?
Pulsewave said:
Backstory: I tried flashing android revolution for the amaze once, and it didn't work (error 1) left it alone for a bit after recovering it, went back to bulletproof and flashed faux .009 kernel, then decided to try again...
Well I'll try to make this brief, sorry if I'm posting in the wrong subforum but here goes, I tried going from bulletproof 2.5.0 to Android Revolution HD and didn't flash the superwipe .zip (lazy me). The install failed with the same error 1, only this time I can't boot back into recovery. Booting to bootloader works but when I tried going into recovery I see it pop up for maybe a fraction of a second before the phone reboots.
I've tried reflashing clockwork mod but no dice
any sort of tips you folks can give me to steer me in the right direction?
Click to expand...
Click to collapse
Not sure about the Amaze tbh, but if I had a failed flash on either of my HTC phones, I just re RUU'd.
D'oh! I forgot about that! Had to do that for my buddy's thunderbolt a few times. Lemme give that a shot and I'll report back
Edit: Worked
Edit:double post
im also having this problem, my phone keeps freezing at the startup screen when the htc logo pops up. i dont know much about this kind of stuff so i would really appreciated if anyone could guide me to what to do
the way that my phone froze like that was that i tried to flash a kernel for the Energy rom, i did installed the rom itself
http://forum.xda-developers.com/showthread.php?t=1362759 this is the rom that i wanted to use
and i flashed the kernel that was provided in the 4th post, i downloaded that file, extracted and ran the .bat file and thats how it happened
i would appreciate if anyone could help me with this
Bricked Htc Amaze 4g
I have a bricked HTC Amaze 4g. I had beastmod v2.20 on when i decided i wanted quick sense. After i finished it just froze on the htc startup logo. I played with it and got it into a bootloop. When i try to flash a ruu the blue bar loads up and comes back to the bootloader screen. I can get into recovery but it wont let me flash anything.Thanks to whoever replies I really appreciate it.
lmfaoomg said:
im also having this problem, my phone keeps freezing at the startup screen when the htc logo pops up. i dont know much about this kind of stuff so i would really appreciated if anyone could guide me to what to do
the way that my phone froze like that was that i tried to flash a kernel for the Energy rom, i did installed the rom itself
http://forum.xda-developers.com/showthread.php?t=1362759 this is the rom that i wanted to use
and i flashed the kernel that was provided in the 4th post, i downloaded that file, extracted and ran the .bat file and thats how it happened
i would appreciate if anyone could help me with this
Click to expand...
Click to collapse
You need to superwipe the phone and flash the ROM. After the ROM flashes, you have to flash the kernel twice.
samiaziz said:
I have a bricked HTC Amaze 4g. I had beastmod v2.20 on when i decided i wanted quick sense. After i finished it just froze on the htc startup logo. I played with it and got it into a bootloop. When i try to flash a ruu the blue bar loads up and comes back to the bootloader screen. I really appreciate it.
Click to expand...
Click to collapse
Same with you. You need to superwipe the phone and flash the ROM. After the ROM flashes, you have to flash the kernel twice.
Superwiping the phone removes all the data from the old ROM so you can install a fresh clean ROM.
If you want to install the RUU, you have to relock the bootloader first and then you can reflash the original RUU
Edit: i was misinformed
Sent from my NRGized Amaze...
via xda premium
aj_2423 said:
I dont believe u have to relock
Sent from my NRGized Amaze...
via xda premium
Click to expand...
Click to collapse
To flash an official RUU, you must relock it. I've done so plenty of times lol
Sent From My HTC Amaze 4G via Someone's Room
If the phone wont go into recovery, you have to use ADB and wipe the cache partition for it to go into recovery again. This is apparently a bug with some of recoveries posted by other devs in the development forum. You need to use fastboot.exe to wipe the cache via adb
And if... If the superwipe doesn't work due to recovery version you have try to boot in to your Bootloader run one of hasoon's tool and choose different recovery.. it did happen to me the bootloop before due to the fact the old roms like mike's rom. he doesn't update his script to support the newer recoveries and it doesn't support X's recovery, it will give you an error installation.. just try different recoveries and for sure your problem will be solved..
just make sure boot in your bootloader/H-boot then run hasoon's tool and have enough battery just to make sure...
hasoon2000 said:
To flash an official RUU, you must relock it. I've done so plenty of times lol
Sent From My HTC Amaze 4G via Someone's Room
Click to expand...
Click to collapse
Thanks for the good info Sir but i my HTC Amaze is bootloader locked and S-ON but i cannot find a RUU for T-mobile to unbrick it. Will a Ruu such as this one work?
RUU_Ruby_Videotron_CA_1.46.1530.1_R2_Radio_1.09.550L.17DC_30.68.550L.09_release_227343_signed.exe
My HTC Amaze scans all the versions of the PH85IMG i place on the sd card but goes back to the menu when its down
any advice that could help i will appreciate!
There's a thread in the dev section that has about a dozen RUUs. I don't see how one can miss it.
Thanks for your reply but i was a little unsure and did not want to make my phone any worst than it already is.
Can you explain 1 thing thing for me please - RUU always you to flash the phone via the computer? where as PH85img.zip allows you to flash the phone via sdcard? I hope i am correct here.
but i want to know how can i flash the phone when its connected via HBoot usb cause my pc recognizes it as "Android Composite ADB Interface"
Currently this is what is on my lcd
LOCKED
RUBY PVT SHIP S-ON RL
HBOOT-1.93.0002
EMMC BOOT
MAR 15 2012
i have tried several PH85img.zip files but the phone just scans them and goes back to the menu.
Some help will be appreciated extremely.
---------- Post added at 03:40 PM ---------- Previous post was at 03:33 PM ----------
I forgot to mention it connects to the pc but when i run command adb devices this is what i get
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\rquinlan.GOSL_DOM>adb devices
List of devices attached
C:\Documents and Settings\rquinlan.GOSL_DOM>
The latest ruu would be your best option, do not put the .zip part of the name since its already there, also a ruu may be an exe or zip file, since it is a complete stock file to restore the device, what would your carrier be to be exact? Just not up to reading through everything in this thread to see if you mentioned that piece of info, if its tmobile then the very first file in the stock ruu/ota thread would be the file you need.
Sent from my iPad using Tapatalk HD
thanks for your advice i managed to reboot the phone into recovery but heres whats strange to me the phone is in recovery with HTC on the screen thats it, the pc has recognized it as "MY HTC" in the device manager however, when i run the command adb devices this is what i get "SH218vp00163 offline". i ran the RUU file but i get error 170 usb connection.
so i am a bit lost as device manager can see the phone but the RUU file cannot and i am plugging the phone into the rear of the pc.
any ideas
Linkzz said:
thanks for your advice i managed to reboot the phone into recovery but heres whats strange to me the phone is in recovery with HTC on the screen thats it, the pc has recognized it as "MY HTC" in the device manager however, when i run the command adb devices this is what i get "SH218vp00163 offline". i ran the RUU file but i get error 170 usb connection.
so i am a bit lost as device manager can see the phone but the RUU file cannot and i am plugging the phone into the rear of the pc.
any ideas
Click to expand...
Click to collapse
Why are you using recovery exactly?
RUU's are to be flash via hboot, which is the very first screen you see when you go into the device's bootloader, in the case of exe files, you'll need to flash it via fastboot mode, which happens to be, correct me if I'm wrong, the very first or second option on the hboot menu.
yes you are correct cause i just tried it with an RUU from another carrier. i found out that the phone had 2.14.531 software installed. but the RUU i was using was 1.46 and so i got a signature error 132. now i need to find a way to remove the 2.14.531 software and replace it with a lower version. can you help me here
Linkzz said:
yes you are correct cause i just tried it with an RUU from another carrier. i found out that the phone had 2.14.531 software installed. but the RUU i was using was 1.46 and so i got a signature error 132. now i need to find a way to remove the 2.14.531 software and replace it with a lower version. can you help me here
Click to expand...
Click to collapse
What carrier are you on?
t-mobile
this is the RUU i tried and made a connection but the PH85img.zip are not working no matter how i try
RUU_Ruby_Videotron_CA_1.46.1530.1_R2_Radio_1.09.55 0L.17DC_30.68.550L.09_release_227343_signed.exe
Hello,
I was recently given a bootlooping Evo 4G Lte. I have been trying to figure out how to get this thing out of a bootloop and havent been able to do it. I, unfortunately, have no history on what happened to this device. Currently, it bootloops on the "Mean Bean" loading screen but will go no further. I can get into the bootloader, which says it is Unlocked, S-On, but I am unable to boot it into a recovery, it just returns back to bootloader. I have tried fastbooting twrp, but it fails (remote: image update error), and I have tried fastbooting the Mean Bean kernel thinking maybe thats all it needs, but that failed as well. Anybody have an insight? Much appreciated! Thanks.
Mike
I would run the 3.17 RUU. Hit the top link in my sig and look at the last post in the thread. You can run it from the bootloader. You'll need to re-root afterwards but it should get your phone back in working condition.
Sent from my HTC EVO 4G LTE
FinZ28 said:
I would run the 3.17 RUU. Hit the top link in my sig and look at the last post in the thread. You can run it from the bootloader. You'll need to re-root afterwards but it should get your phone back in working condition.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Thanks for the quick reply. I downloaded the RUU and ran it. However it sits and says "Waiting for bootloader" then errors out with "USB connection issue". The usb is working. The reason I never ran the RUU in teh first place was because i thought i read that you cant RUU with and unlocked bootloader. Is that not true? or is that my problem?
Mike
Not 100% sure but I will check with someone who used this tool recently and see if they were still unlocked at the time. Were you connected via Fastboot USB? Sounds more like a driver issue.
Sent from my HTC EVO 4G LTE
FinZ28 said:
Shouldn't matter. I know of a couple of users who were having phone issues and had unlocked bootloaders when they ran this tool. Were you connected via Fastboot USB? Sounds more like a driver issue.
Click to expand...
Click to collapse
Yeah I was connected and it said fastboot USB. It said rebooting to bootloader and rebooted, still said fastboot USB. Then it sat at a screen that said "waiting for bootloader" and after a while error ed out.
You can try relocking. You just need to run the command "fastboot oem relock" from a command line while connected via fastboot USB mode.
Sent from my HTC EVO 4G LTE
FinZ28 said:
You can try relocking. You just need to run the command "fastboot oem relock" from a command line while connected via fastboot USB mode.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
I have since tried relocking to see if that was it, and it did the same thing.
Mike
Hopefully @YoFayce can shed some light on the matter since he recently used this on his phone.
Sent from my HTC EVO 4G LTE
FinZ28 said:
Hopefully @YoFayce can shed some light on the matter since he recently used this on his phone.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
crazymike1234 said:
I have since tried relocking to see if that was it, and it did the same thing.
Mike
Click to expand...
Click to collapse
you can use the stock RUU and you can leave the bootloader unlocked as it will not affect anything.. it will fix your looping problem (Amongst others) as in gps not working ect.. once your done you will need to fastboot over your TWRP and from there mod as normal Good Luck! and ill be watching if you need any help!
YoFayce said:
you can use the stock RUU and you can leave the bootloader unlocked as it will not affect anything.. it will fix your looping problem (Amongst others) as in gps not working ect.. once your done you will need to fastboot over your TWRP and from there mod as normal Good Luck! and ill be watching if you need any help!
Click to expand...
Click to collapse
Problem is the ruu keeps error in out. I am beginning to think it may still be a driver problem. Someday I will get this done!
Mike
crazymike1234 said:
Problem is the ruu keeps error in out. I am beginning to think it may still be a driver problem. Someday I will get this done!
Mike
Click to expand...
Click to collapse
When in doubt update your android SDK remove the htc drivers reboot install drivers reboot and you should be good to go! Check the integrity of your USB cable and if possible use a rear USB port (More Power) Painful process yes but well worth it.. HTC drivers act strange till you reboot OOOh and make sure your using the proper HTC drivers for windows 32 bit or 64 bit!
YoFayce said:
When in doubt update your android SDK remove the htc drivers reboot install drivers reboot and you should be good to go! Check the integrity of your USB cable and if possible use a rear USB port (More Power) Painful process yes but well worth it.. HTC drivers act strange till you reboot OOOh and make sure your using the proper HTC drivers for windows 32 bit or 64 bit!
Click to expand...
Click to collapse
The drivers seem to be ok, but I am still not able to get any further. The RUU finds my phone, then reboots again to bootloader, but it just sits there saying "Waiting for bootloader" until it errors out due to "USB Connection error". I have tried a few different cables, and different USB ports. Not sure what the problem is but it just wont go any further. I re-unlocked my bootloader with htcdev. I have tried fastbooting a recovery to the phone but it errors out. I just cant get anything to work so I can boot anything. I really just want to get something working...anything! Any other ideas? Thanks.
Mike
use an sd card put a recovery image on the root of the sd boot into bootloader apply the recovery you should then have a recovery if you did it right, go into twrp mount device add a rom flash in recovery viola.
Sinistertensai said:
use an sd card put a recovery image on the root of the sd boot into bootloader apply the recovery you should then have a recovery if you did it right, go into twrp mount device add a rom flash in recovery viola.
Click to expand...
Click to collapse
Sinister,
Thanks for the reply. I put TWRP on the sdcard (named PJ75IMG, right?) and tried to apply that when I rebooted to recovery last night and it failed. It tries to load it but gives a few errors quick (No Image) Did I do it wrong?
Mike
crazymike1234 said:
Sinister,
Thanks for the reply. I put TWRP on the sdcard (named PJ75IMG, right?) and tried to apply that when I rebooted to recovery last night and it failed. It tries to load it but gives a few errors quick (No Image) Did I do it wrong?
Mike
Click to expand...
Click to collapse
make sure the file is just the PJ75IMG no additional text and it should be .zip If I recall correctly. make sure its on the root of the sdcard not internal but sd or external and it should be at the top level e.g. sdcard/ make sure its not in any other folders after you do that hold power and vol down get to hboot screen itll scan and then just follow the instructions.
Sinistertensai said:
make sure the file is just the PJ75IMG no additional text and it should be .zip If I recall correctly. make sure its on the root of the sdcard not internal but sd or external and it should be at the top level e.g. sdcard/ make sure its not in any other folders after you do that hold power and vol down get to hboot screen itll scan and then just follow the instructions.
Click to expand...
Click to collapse
Thats exactly what I did. It is the only thing on the sdcard. It says no gift file, Loading, no image for 4 different things. Then returns to the bootloader.
Mike
crazymike1234 said:
Thats exactly what I did. It is the only thing on the sdcard. It says no gift file, Loading, no image for 4 different things. Then returns to the bootloader.
Mike
Click to expand...
Click to collapse
zip files probably corrupt then. download another do the same process make sure you've got a good file use md5 checks
Sinistertensai said:
zip files probably corrupt then. download another do the same process make sure you've got a good file use md5 checks
Click to expand...
Click to collapse
Hmmm, Ill try download again. I got it from the main TWRP site.
crazymike1234 said:
Hmmm, Ill try download again. I got it from the main TWRP site.
Click to expand...
Click to collapse
careful on the vol down press you might be holding it too long and its canceling the update.
Sinistertensai said:
careful on the vol down press you might be holding it too long and its canceling the update.
Click to expand...
Click to collapse
Well, which recovery file should I be using? When I use the main TWRP ones (ie openrecovery-twrp-2.6.0.0-jewel.img) it gives me the errors like I said above. I now see they have a few labeled like this PJ75IMG-twrp-2.3.1.0-jewel.zip. When I use these, it tries to continue but says "Main Version Is Older. FAILED"
so after i managed to root my verizon one max, i downloaded market helper which spoofs your device so you can trick the play store into thinking you have a different device. I spoofed my device as a nexus 10 and it said i needed to reboot to save the changes. When it rebooted it just stays at htc screen and then the screen goes dark... I tried to go to twrp recovery but it wouldnt boot into recovery. i relocked my bootloader and when i type adb devices in command prompt, it says my device isnt connected when its in fastboot usb mode. and i tried flashing the ruu for verizon one max but it failed somehow...any one know what to do?
To check for devices in fastboot type fastboot devices. Adb devices is for when ur phone is booted.
Likely the market spoofer changed your build.prop which borked it on restart.
What error when flashing verizon ruu?
Jiggity Janx said:
To check for devices in fastboot type fastboot devices. Adb devices is for when ur phone is booted.
Likely the market spoofer changed your build.prop which borked it on restart.
What error when flashing verizon ruu?
Click to expand...
Click to collapse
Thank you for replying!
thanks for the information and when i typed in fastboot flash zip 0P3PIMG.zip, everything seemed fine until it said FAILED. i cant remember. i dont have access to my phone right now otherwise i would retry but i cant.
do you have an idea how to fix this?
Really juat need to know how far it got before it failed. Was it the encrypted or decrypted ruu? Encrypted requires s on to flash. Make sure the OP3 img file is on the true external sd and not the internal sd. Those kinds of things...
herzig.grant said:
Thank you for replying!
thanks for the information and when i typed in fastboot flash zip 0P3PIMG.zip, everything seemed fine until it said FAILED. i cant remember. i dont have access to my phone right now otherwise i would retry but i cant.
do you have an idea how to fix this?
Click to expand...
Click to collapse
i meant fix my build.prop not the flashing problem
herzig.grant said:
i meant fix my build.prop not the flashing problem
Click to expand...
Click to collapse
but im s-off so does it matter?
i think it was encrypted...
let my try again with a decrypted
thanks again
If your tried to flash an ruu and it even got started you likely need to make that work. Im not sure the exact order of what the ruu does but it may have failed on something simple and important that cannot be fixed now just by you working on the build.prop. It 'may' be fixable piece by piece but I wouldnt recommend it.
Flashing the ruu correctly will take you to stock and fix anything that you did.
Jiggity Janx said:
If your tried to flash an ruu and it even got started you likely need to make that work. Im not sure the exact order of what the ruu does but it may have failed on something simple and important that cannot be fixed now just by you working on the build.prop. It 'may' be fixable piece by piece but I wouldnt recommend it.
Flashing the ruu correctly will take you to stock and fix anything that you did.
Click to expand...
Click to collapse
Thank you and i want to know have you ever flashed a ruu through cmd? if so, can you tell me what to type?
Im not testing your experience or anything, i just think a second opinion always helps
OMG it worked....
Thank you sooooo much for your time.
Turns out I needed to do the decrypted Thu
herzig.grant said:
OMG it worked....
Thank you sooooo much for your time.
Turns out I needed to do the decrypted Thu
Click to expand...
Click to collapse
Shouldn't require encrypted. The only require is if you are s-on you must you encrypted ruu that matches or exceeds you current software version.
S-off will flash either encrypted or decrypted.
Sent from my Nexus 7 using Tapatalk
My HTC One M8 from AT&T got stuck in a boot loop after I unlocked it, put a custom recovery on it, and then tried to put a custom ROM on it.
I tried to put InsertCoin on there and it got stuck in a boot loop for some reason.
I got the SDK kit and tried doing a adb push my NANDroid I did originally (before trying the ROM) and so I have my NANDroid backup.
I just can't push anything to my SDCard because it keeps saying "adb shell ls /mnt/sdcard/" no such file or directory exists
same thing with "adb shell ls /sdcard/" no such file or directory exists.
I have my NANDroid backup (before the soft brick) and, a new ROM (Viper One M8 2.3.0)
so how do I "adb push" a file onto a filesystem that I have no access to?
Thanks!
**EDIT**
adb push viperOne.zip /sdcard says "protocol failure"
It's as if I have no rights to push anything.
When I try to "install from .zip" it says "unable to mount SDCard"
Hope this helps
adb push viperOne.zip /sdcard/. is what it should be @command. make sure rom zip is in same location as adb/fastboot files
Wonders_Never_Cease said:
adb push viperOne.zip /sdcard/. is what it should be @command. make sure rom zip is in same location as adb/fastboot files
Click to expand...
Click to collapse
They are in the same location as the adb/fastboot.
Still same errors.
Are you booted into recovery when running that command?If so and still getting that error... Gonna have to attempt running an ruu then see if it clears it up, try to flash back stock recovery, boot into bootloader connect to computer and run the ruu. s-on or s-off?
It is S-ON
Also I have a nandroid backup. But because I can't adb push anything, I can't even run the nandroid backup to restore.
It won't mount my SD card.
I have to do an RUU? How do I do that?
ok so did you try to flash the kernel [email protected] s-on device? since rom has been flashed... pull the kernel from the rom zip you flashed and copy it to adb/fastboot location,boot into bootloader,connect via fastboot, then run fastboot flash boot boot.img
I didn't do a kernel. It was just default.
That seems too complicated.
I somehow fixed my issue but getting CyanogenMod and flashing that using sideload. For the first time ever sideload worked.
However when I got the Google play services, it kept crashing when I opened it, any reason why? I have the CM nightly 20140830
Thanks!
Cant help you on that,better to ask in the devs thread for that software your running. Good luck.
technocrat7 said:
I didn't do a kernel. It was just default.
That seems too complicated.
I somehow fixed my issue but getting CyanogenMod and flashing that using sideload. For the first time ever sideload worked.
However when I got the Google play services, it kept crashing when I opened it, any reason why? I have the CM nightly 20140830
Thanks!
Click to expand...
Click to collapse
What recovery? If TWRP, try CWM as SD mount issue (while sideload works) is a problem I've seen here several times before on TWRP.
Help help help soft brick no os no baseband
Wonders_Never_Cease said:
adb push viperOne.zip /sdcard/. is what it should be @command. make sure rom zip is in same location as adb/fastboot files
Click to expand...
Click to collapse
I have a sprint htc one M7 I just got my replacement phone today and i rooted it and got every thing restored on it then there was a problem with the speakers on the phone it would play music but only on the right side .....(i forgot to mention i installed renovate rom after i rooted it) so i figured if i installed another kernal it would fix it so i installed kangaroo kernal for SPRINT HTC ONE android version 4.4.2 which was the right kernal for my phone ..so i thought... so when i installed it ..it took a while for it to turn on and i knew something was wrong when it turned on the home screen wouldn't load and it was showing i had no service when i was in a area i clearly new i had service in so i tried to run a RUU and i keep getting a USB error when it tries to send the ruu . I know the cable works and when i ran fastboot getvar all there is no baseband and no os .........HELP SUPER URGENT URGENT MY parents are going to kill me cause i just got my replacment.... my hboot is 1.57 PLEASE HELP QUICK.:crying::crying::crying::crying::crying::crying:
Jac15myers said:
I have a sprint htc one M7
Click to expand...
Click to collapse
This forum is for the M8, not the M7. Not only that, but the AT&T version, not Sprint.
You should post to your device specific forum section. As the devices are completely different hardware, advice given here may not work for your M7 and may even damage it.
HTC One M8 (AT&T) Soft-Brick Bootloop
Hey everyone, I'm new to XDA and am a bit of a noob at flashing so take it easy on me
Here's my problem: As implied by the title, my AT&T One M8 is stuck in a bootloop at the white HTC screen and won't boot me into my rom. Something to note is that there's a little open gray lock icon at the bottom of the white screen. After a moment the screen just takes me to Philz recovery. Also, the phone was previously rooted and is currently S-On (no firewater support for AT&T yet), with my custom recovery (Philz). Unfortunately, I did not make a backup of my phone (I know, bad move) but at this point I just want the thing to work properly!
What happened: With a stock GPE Rom by Graffixnyc, I installed Google's stock recovery in hopes of recieveing the 4.4.4 OTA; the rom I had was 4.4.2. A day later I get the 4.4.4 OTA, accept and install it, and then that's what started the bootloop. I haven't gotten back into the OS since. In addition, my computer does not recognize my device when it's connected, although fastboot and adb commands do work.
What I've tried: Flashing through both TWRP and Philz, trying two different GPE roms. Neither worked, even through adb sideloading I get the same error. To transfer files from my computer to phone I've been using a micro SDcard with an SD adapter. I've also tried doing a factory wipe through Philz and even flashed a 'fix permissions' emulator.
I'd imagine that I need a One M8 factory image just for a fresh clean start, but apparantly HTC only has one for the unlocked developer edition. Would I be able to use this version of the factory image/obtain one for the AT&T model or is there a different route I need to go?
Thanks in advance for the help; this seems like a great community to be involved in!!
Blaise56 said:
Here's my problem: As implied by the title, my AT&T One M8 is stuck in a bootloop at the white HTC screen and won't boot me into my rom. Something to note is that there's a little open gray lock icon at the bottom of the white screen. After a moment the screen just takes me to Philz recovery. Also, the phone was previously rooted and is currently S-On (no firewater support for AT&T yet), with my custom recovery (Philz). Unfortunately, I did not make a backup of my phone (I know, bad move) but at this point I just want the thing to work properly!
What happened: With a stock GPE Rom by Graffixnyc, I installed Google's stock recovery in hopes of recieveing the 4.4.4 OTA; the rom I had was 4.4.2. A day later I get the 4.4.4 OTA, accept and install it, and then that's what started the bootloop. I haven't gotten back into the OS since. In addition, my computer does not recognize my device when it's connected, although fastboot and adb commands do work.
What I've tried: Flashing through both TWRP and Philz, trying two different GPE roms. Neither worked, even through adb sideloading I get the same error. To transfer files from my computer to phone I've been using a micro SDcard with an SD adapter. I've also tried doing a factory wipe through Philz and even flashed a 'fix permissions' emulator.
I'd imagine that I need a One M8 factory image just for a fresh clean start, but apparantly HTC only has one for the unlocked developer edition. Would I be able to use this version of the factory image/obtain one for the AT&T model or is there a different route I need to go?
Click to expand...
Click to collapse
Did you do the full conversion, of just flashed the GPE ROM?
If you didn't do the full conversion, GPE uses a different partition layout, bootloader, and different CID (and MID?) than Sense, so any one or all of those can be your issue.
What happens if you try to boot into bootloader and select recovery?
Blaise56 said:
I'd imagine that I need a One M8 factory image just for a fresh clean start, but apparantly HTC only has one for the unlocked developer edition.
Click to expand...
Click to collapse
Not sure why you think that. RUUs are available here:
http://www.htc.com/us/support/htc-one-m8-att/news/
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Proper CID and relocked bootloader required to run RUU with S-on. And hboot number of the RUU must be equal or greater than what you have installed.
redpoint73 said:
Did you do the full conversion, of just flashed the GPE ROM?
If you didn't do the full conversion, GPE uses a different partition layout, bootloader, and different CID (and MID?) than Sense, so any one or all of those can be your issue.
What happens if you try to boot into bootloader and select recovery?
Not sure why you think that. RUUs are available here:
http://www.htc.com/us/support/htc-one-m8-att/news/
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
Proper CID and relocked bootloader required to run RUU with S-on. And hboot number of the RUU must be equal or greater than what you have installed.
Click to expand...
Click to collapse
Thanks man!
I have the almost same problem yesterday when i unlocking the bootloader, flash TWRP recovery after flashing a recovery i want to root device in TWRP i install update SuperSU and i restart phone my M8 is stoped in HTC logo & cannot further i need solution quickly because i need phone i don't have spare for replacing my M8 please help
Fifa91 said:
I have the almost same problem yesterday when i unlocking the bootloader, flash TWRP recovery after flashing a recovery i want to root device in TWRP i install update SuperSU and i restart phone my M8 is stoped in HTC logo & cannot further i need solution quickly because i need phone i don't have spare for replacing my M8 please help
Click to expand...
Click to collapse
Not enough info, please do fastboot getvar all, and post the output (delete IMEI and serial number before posting).
You probably used an obsolete version TWRP, and obsolete SuperSU. But I need to see the getvar data, plus what TWRP version and what SuperSU version, to know for sure or advise any more.
Hello fellow Android users,
I am here to ask for your help.
Just to be clear, my phone is an HTC Desire 601 locked with FIDO, use to have Android 4.4.2, Zara_UL, Unlocked bootloader, S-ON and no OS installed.
My HTC Desire 601 has had a rough week.
Everything went well for unlocking the bootloader, rooting, installing new recovery.
Then I wanted to go S-OFF, but Firewater told me the current kernel was blocking the exploit.
So I decided to flash KofilaKernel for my device and try again. The install went well,
only problem was I wiped my cache and system and now, NO MORE OS INSTALLED and still S-ON.
Couldn't use Firewater anymore...
So I tried installing custom ROM and also tried going back to stock, miserably failing.
A. I tried flashing InsertCoin custom ROM wich failed because of S-ON (forgive noobishness)
B. I tried using "fastboot boot" command that made possible flashing custom ROM with S-ON.
I was counting on this one, but had problems too : Most recoveries wouldn't boot (ClockWorkMod several versions, TWRP several versions) except one TWRP recovery wich booted, but the touch screen WAS NOT ACTIVATED. Tried using side buttons with no luck, and power button just locked the screen. I have heard that Google has changed the fastboot boot for newer android versions and that you had to add something to the command like :
"fastboot -c "lge.kcal=0|0|0|x" boot recovery.img"
This example is for Nexus 4 I think, but I don't know the one for Desire 601... I tried it and it wouldn't boot.
C. I have tried "fastboot flash system system.img" with stock image. Had an error saying not enough memory available.
I wiped everything with TWRP and with CLCKWRKMOD : System, cache, dalvik cache, etc... tried again to flash system with no luck.
D. I have tried the Telus RUU.exe file. Told me I had the wrong RUU for my phone and to find the right one, wich doesn't exist for Android 4.4.2 as far as I know.
E. I have tried flashing several versions of 4EXT recovery to get SmartFlash, but it is not compatible with HTC Desire 601.
There I am.
Please help a brother with unusable new phone LOL.
Thanks a bunch for any help.
black-venomz
black-venomz said:
Hello fellow Android users,
I am here to ask for your help.
Just to be clear, my phone is an HTC Desire 601 locked with FIDO, use to have Android 4.4.2, Zara_UL, Unlocked bootloader, S-ON and no OS installed.
My HTC Desire 601 has had a rough week.
Everything went well for unlocking the bootloader, rooting, installing new recovery.
Then I wanted to go S-OFF, but Firewater told me the current kernel was blocking the exploit.
So I decided to flash KofilaKernel for my device and try again. The install went well,
only problem was I wiped my cache and system and now, NO MORE OS INSTALLED and still S-ON.
Couldn't use Firewater anymore...
So I tried installing custom ROM and also tried going back to stock, miserably failing.
A. I tried flashing InsertCoin custom ROM wich failed because of S-ON (forgive noobishness)
B. I tried using "fastboot boot" command that made possible flashing custom ROM with S-ON.
I was counting on this one, but had problems too : Most recoveries wouldn't boot (ClockWorkMod several versions, TWRP several versions) except one TWRP recovery wich booted, but the touch screen WAS NOT ACTIVATED. Tried using side buttons with no luck, and power button just locked the screen. I have heard that Google has changed the fastboot boot for newer android versions and that you had to add something to the command like :
"fastboot -c "lge.kcal=0|0|0|x" boot recovery.img"
This example is for Nexus 4 I think, but I don't know the one for Desire 601... I tried it and it wouldn't boot.
C. I have tried "fastboot flash system system.img" with stock image. Had an error saying not enough memory available.
I wiped everything with TWRP and with CLCKWRKMOD : System, cache, dalvik cache, etc... tried again to flash system with no luck.
D. I have tried the Telus RUU.exe file. Told me I had the wrong RUU for my phone and to find the right one, wich doesn't exist for Android 4.4.2 as far as I know.
E. I have read about 4EXT recovery and SmartFlash, but the only way to get 4EXT recovery seems to be through app and I don't have any OS so it's impossible.
There I am.
Please help a brother with unusable new phone LOL.
Thanks a bunch for any help.
black-venomz
Click to expand...
Click to collapse
I'd just reinstall a rom based off of your current firmware and then you need to copy the boot.img out of it and flash in bootloader. The command you'll want to use is:
fastboot flash boot boot.img
Be cautious trying to run KK roms on JB firmware as you'll have issues with the radio and touch, bare minimum. Only ways to update firmware are via being S-Off and doing a firmware update of just the essentials or find a KK RUU for your phone, if it is available.
es0tericcha0s said:
I'd just reinstall a rom based off of your current firmware and then you need to copy the boot.img out of it and flash in bootloader. The command you'll want to use is:
fastboot flash boot boot.img
Be cautious trying to run KK roms on JB firmware as you'll have issues with the radio and touch, bare minimum. Only ways to update firmware are via being S-Off and doing a firmware update of just the essentials or find a KK RUU for your phone, if it is available.
Click to expand...
Click to collapse
So a ROM based on my current firware wouldn't need S-OFF to be installed ? Can I install stock ROM via recovery even if S-ON ?
Do you know where I could find such thing ?
Many thanks.
black-venomz
black-venomz said:
So a ROM based on my current firware wouldn't need S-OFF to be installed ? Can I install stock ROM via recovery even if S-ON ?
Do you know where I could find such thing ?
Many thanks.
black-venomz
Click to expand...
Click to collapse
Correct, you can install a rom while S-On, as long as you install the boot.img separately. You can install a rom based off of stock, but you won't be able to do the official RUU type rom from it unless there is an RUU zip for your phone (some HTCs have this, but most are just via an exe of a PC) but that would actually go through the bootloader instead of recovery.
es0tericcha0s said:
Correct, you can install a rom while S-On, as long as you install the boot.img separately. You can install a rom based off of stock, but you won't be able to do the official RUU type rom from it unless there is an RUU zip for your phone (some HTCs have this, but most are just via an exe of a PC) but that would actually go through the bootloader instead of recovery.
Click to expand...
Click to collapse
Ok great !
So I have access to a stock ROM apparently. I can't post links yet, but if you look up on Google "htcdesire 601 stock rom" you will find a google docs page with the stock ROM for desire 601 4.4.2.
Would you be king enough to walk me through the steps to achieve this ? There are many .img files in this folder and I am far from an expert.
Thanks again.
black-venomzz
I did :
1. Copy whole .zip file on sd card found when searched "htc desire 601 stock rom" on google in google docs pasge (can't post link yet).
2. Install .zip with TWRP.
- Failed (still bootloop) -
The tried :
1. fastboot flash boot boot.img (boot.img was found in the .zip file)
2. Copy whole .zip file on sd card
3. Install .zip with TWRP
- Failed (still bootloop) -
I'm probably missing something here...
You might not have the correct zip for your variant of 610. They make a few and could depend on the carrier as well. Should also factory reset in TWRP.
es0tericcha0s said:
You might not have the correct zip for your variant of 610. They make a few and could depend on the carrier as well. Should also factory reset in TWRP.
Click to expand...
Click to collapse
Still need help guys ! I believe I have the right one.
Could you check it out ? It looks legit.
**drive**.google.**com/folderview?id=0B6WBFlAKqe30ZG1wOGk2T0xwTkE&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
(I still can't post links on threads because I'm new...)
I tried Installing ROM from zip in TWRP (successful) and then fastboot flash boot boot.img but still didn't work !
My phone is still bricked.
Any help would be appreciated.
black-venomz said:
Still need help guys ! I believe I have the right one.
Could you check it out ? It looks legit.
**drive**.google.**com/folderview?id=0B6WBFlAKqe30ZG1wOGk2T0xwTkE&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
(I still can't post links on threads because I'm new...)
I tried Installing ROM from zip in TWRP (successful) and then fastboot flash boot boot.img but still didn't work !
My phone is still bricked.
Any help would be appreciated.
Click to expand...
Click to collapse
Couldn't find that page, even after taking out the asteriks. But you'll need to boot to the bootloader and run this command:
fastboot getvar all
to find out your exact model/region/carrier/etc.
es0tericcha0s said:
Couldn't find that page, even after taking out the asteriks. But you'll need to boot to the bootloader and run this command:
fastboot getvar all
to find out your exact model/region/carrier/etc.
Click to expand...
Click to collapse
I ran the command. See attachment. I don't know how to compare it to ROM.
Here is the link again :
**https**://**drive.**google.**com/folderview?id=0B6WBFlAKqe30eUh3WXB4eURwRjQ&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
If it still fails (wich truly shouldn't) I access it by searching "htc desire 601 stock ROM" on Google and it's the first one, the page is called "Firmware"
Thank you for your help !
Edit : I know why the link fails. It seems xda adds a space somewhere in the link. Need to remove it for the link to work.
black-venomz said:
I ran the command. See attachment. I don't know how to compare it to ROM.
Here is the link again :
**https**://**drive.**google.**com/folderview?id=0B6WBFlAKqe30eUh3WXB4eURwRjQ&&tid=0B6WBFlAKqe30TjRLa2Qxa0toYlU
If it still fails (wich truly shouldn't) I access it by searching "htc desire 601 stock ROM" on Google and it's the first one, the page is called "Firmware"
Thank you for your help !
Edit : I know why the link fails. It seems xda adds a space somewhere in the link. Need to remove it for the link to work.
Click to expand...
Click to collapse
I'll look around for it later, but real quick, you probably want to take down the picture since it has your IMEI and Serial Number of the phone listed, for safety's sake.
es0tericcha0s said:
I'll look around for it later, but real quick, you probably want to take down the picture since it has your IMEI and Serial Number of the phone listed, for safety's sake.
Click to expand...
Click to collapse
Ok I'll wait ! Thanks for the tip. If you need it for the info, I'll post it again without IMEI/Serial.
black-venomz said:
Ok I'll wait ! Thanks for the tip. If you need it for the info, I'll post it again without IMEI/Serial.
Click to expand...
Click to collapse
Ok, I think we might be on the right track now...
According to the read out from getvar, you were on 4.2.2. It's also listed as a Rogers phone (I'm assuming there's a direct connection between Fido and Rogers, though being an American, I'm not 100% up to date with Canadian carriers...) so I found the RUU for 4.2.2 (system 1.10.631.8 which you can see in the getvar list) http://www.htcdev.com/devcenter/downloads/P510 (it won't let me do a direct link for some reason) and pick the Rogers one for 1.10.631.8
This should get you back up and running.
Make sure to relock the bootloader before you run it or it'll fail. You can re-unlock afterwards. Should be able to do "fastboot oem lock" then when ready to unlock again then "fastboot oem unlock" should work since you've already used the bootloader key.
es0tericcha0s said:
Ok, I think we might be on the right track now...
According to the read out from getvar, you were on 4.2.2. It's also listed as a Rogers phone (I'm assuming there's a direct connection between Fido and Rogers, though being an American, I'm not 100% up to date with Canadian carriers...) so I found the RUU for 4.2.2 (system 1.10.631.8 which you can see in the getvar list) http://www.htcdev.com/devcenter/downloads/P510 (it won't let me do a direct link for some reason) and pick the Rogers one for 1.10.631.8
This should get you back up and running.
Make sure to relock the bootloader before you run it or it'll fail. You can re-unlock afterwards. Should be able to do "fastboot oem lock" then when ready to unlock again then "fastboot oem unlock" should work since you've already used the bootloader key.
Click to expand...
Click to collapse
Your a life saver thanks !
I'll make sure to relock.
The only thing is I have no clue how to use this RUU. It's not like a ".exe" that you execute.
The .zip file contains a .tar.gz file, wich contains another .tar file, wich contains binaries I believe.
The readme.txt file talks about using Linux commands but I'm far from an expert.
I'll do a little research on my own since you helped me a lot already, but if you have any tips feel free to share !
Thanks again,
black-venomz
BTW for information purposes,
Fido is indeed a subsidiary brand of Rogers.
black-venomz said:
BTW for information purposes,
Fido is indeed a subsidiary brand of Rogers.
Click to expand...
Click to collapse
Ah shoot, I didn't realize it at the time, but that's like the source code, as in, if you wanted to compile a rom for your phone. That actually isn't what we need. :/ I'll have to keep looking...
es0tericcha0s said:
Ah shoot, I didn't realize it at the time, but that's like the source code, as in, if you wanted to compile a rom for your phone. That actually isn't what we need. :/ I'll have to keep looking...
Click to expand...
Click to collapse
****e. How do people build RUU.exe in the first place ? Can't we build one with these binary files ?
Edit : Did some reading and found out only vendors can make RUU's.
Tried this, found on another thread.
"The RUU is your normal, executable program and does everything for you. The ZIP is an RUU but you have to set the phone up to flash it by using fastboot commands. the process is:
1. Connect phone in fastboot mode
2. Run the command 'fastboot oem rebootRUU'
3. Once the phone is at the HTC screen, you run the command 'fastboot flash zip name_of_zip.zip'
4. It will flash the first part and then give an error and you run the same command as above a second time straight away
5. Once the second flash sequence has finished, you the type 'fastboot reboot' and it will reboot the phone and finish the installation"
It failed, but I didn't relock bootloader yet. Will try that now.
Edit : Also failed with relocked bootloader.
Fastboot error message was :
"(bootloader) signature checking
FAILED (remote : 12 signature verify fail)"
black-venomz said:
Tried this, found on another thread.
"The RUU is your normal, executable program and does everything for you. The ZIP is an RUU but you have to set the phone up to flash it by using fastboot commands. the process is:
1. Connect phone in fastboot mode
2. Run the command 'fastboot oem rebootRUU'
3. Once the phone is at the HTC screen, you run the command 'fastboot flash zip name_of_zip.zip'
4. It will flash the first part and then give an error and you run the same command as above a second time straight away
5. Once the second flash sequence has finished, you the type 'fastboot reboot' and it will reboot the phone and finish the installation"
It failed, but I didn't relock bootloader yet. Will try that now.
Edit : Also failed with relocked bootloader.
Fastboot error message was :
"(bootloader) signature checking
FAILED (remote : 12 signature verify fail)"
Click to expand...
Click to collapse
You can flash RUUs like that, but that zip does not house the files you would need. RUUs have to be signed with HTC's special key or it won't work. That's why it was only a 99MB file...
---------- Post added at 12:16 AM ---------- Previous post was at 12:00 AM ----------
http://forum.xda-developers.com/desire-601/help/rogers-ruu-available-t2836217
https://drive.google.com/folderview...RFdlTWc&tid=0BzrP5DWIlpplWkNROHh6Y3o4UHc#list
es0tericcha0s said:
You can flash RUUs like that, but that zip does not house the files you would need. RUUs have to be signed with HTC's special key or it won't work. That's why it was only a 99MB file...
Click to expand...
Click to collapse
Thanks for looking around. Unfortunately the RUU failed (see picture).
I think my phone was updated with Android 4.4.2 when I bought it (recently) so it might be what's causing the error.
I wanted to try with a Telus RUU for 4.4.2 but it's not there..........
I'm starting to lose hope here.