Can we use version of twrp for the other versions of this phone? I am trying to install android revolution HD, which as sprint support in the 4.3 version, but it requires the newer TWRP (or it will once it gets updated to 4.4 for us). Someone over there said it should be fine, but I just wanted to make sure.
well, i tried it. I got:
FAILED (remote: not allowed)
is that just because it's not for our device, or is it something I did wrong and can get around
TriBeard said:
well, i tried it. I got:
FAILED (remote: not allowed)
is that just because it's not for our device, or is it something I did wrong and can get around
Click to expand...
Click to collapse
The latest TWRP for m7wls (m7spr) is 2.6.3.0.
raptoro07 said:
The latest TWRP for m7wls (m7spr) is 2.6.3.0.
Click to expand...
Click to collapse
Yeah, I get that same error when I try to flash that as well.
Im running ARHD right now and you dont need 2.6.3.3 to install it, thats only for kit kat, which isnt supported as of now for us. Just use 2.6.3.0 and flash 31.6
EmSeeMAC said:
Im running ARHD right now and you dont need 2.6.3.3 to install it, thats only for kit kat, which isnt supported as of now for us. Just use 2.6.3.0 and flash 31.6
Click to expand...
Click to collapse
I can't even get that version to install. I get that same error with either one. I have CWM installed and I just used that and it seems to be doing ok, but I still would like to figure out why TWRP won't install cause the way it handles backups seems way easier.
Any idea when....
2.6.3.3 will be available for Sprint?
JoJoLanny said:
2.6.3.3 will be available for Sprint?
Click to expand...
Click to collapse
Not available yet, but not needed either.
Ok
Twrp is kind of broken on the Sprint HTC One. Use with caution guys
Sent from my HTCONE using XDA Premium 4 mobile app
Kraizk said:
Twrp is kind of broken on the Sprint HTC One. Use with caution guys
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Twrp isn't broken. I use 2.6.3.0 everyday with no problems.
Sent from my HTCONE using Tapatalk
raptoro07 said:
Twrp isn't broken. I use 2.6.3.0 everyday with no problems.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Really because I know the 3 following issues have been confirmed by the developer:
1) When screen "sleeps" the device becomes unresponsive. back and home buttons vibrate but screen fails to wake
2) When in TWRP and a charger is connected after launching the charging percentage never updates to indicate it is plugged in (+ sign is never shown). If device is launched to recovery while plugged in + sign shows but percentage never updates.
3) USB OTG storage is not read
2 and 3 are kind of big deals. 2 means it is possible the device will not charge while off/dead and 3 limits backup abilities due to the lack of an SD card.
Kraizk said:
Really because I know the 3 following issues have been confirmed by the developer:
1) When screen "sleeps" the device becomes unresponsive. back and home buttons vibrate but screen fails to wake
2) When in TWRP and a charger is connected after launching the charging percentage never updates to indicate it is plugged in (+ sign is never shown). If device is launched to recovery while plugged in + sign shows but percentage never updates.
3) USB OTG storage is not read
2 and 3 are kind of big deals. 2 means it is possible the device will not charge while off/dead and 3 limits backup abilities due to the lack of an SD card.
Click to expand...
Click to collapse
Yes I can confirm those. I think it doesn't charge while in recovery.
Add another bug. The clock doesn't show the correct time
Sent from my HTCONE using Tapatalk
elvisypi said:
Yes I can confirm those. I think it doesn't charge while in recovery.
Add another bug. The clock doesn't show the correct time
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Ive had one person claim their battery died and they got it to charge enough to boot it just took hours and a bit of luck. Again I am not bashing this recovery, it is just cautionary advice.
Kraizk said:
Ive had one person claim their battery died and they got it to charge enough to boot it just took hours and a bit of luck. Again I am not bashing this recovery, it is just cautionary advice.
Click to expand...
Click to collapse
If somebody is interested to be a beta tester for TWRP sign here http://teamw.in/get-involved
I just did and I also sent a message requesting the update and I listed the bugs
Sent from my HTCONE using Tapatalk
---------- Post added at 11:31 PM ---------- Previous post was at 11:20 PM ----------
Is there anyone willing to start porting the 2.6.3.3 from the international One? I found a guide http://forum.xda-developers.com/showthread.php?t=1943625
Unfortunately I'm no dev and have little knowledge...
Sent from my HTCONE using Tapatalk
My suggestion: for day to day, load PhilZ because all these things are not issues in that recovery (everything works).
In that rare instance that a ROM has a (poorly conceived, imho) dependency on TWRP, flash TWRP for loading the ROM, then flash back to PhilZ to get backups on OTG, proper battery handling, proper screen handling, etc.
It's a free world, no need to keep something loaded that bugs you. Load when needed, stay safe otherwise.
The issues with ROMs with different recoveries, if any, almost always end up an error properly checking device properties in the installer script. Easy fix, just have to let the dev know what's up.
I use standard CWM and it works perfect
tdhite said:
My suggestion: for day to day, load PhilZ because all these things are not issues in that recovery (everything works).
In that rare instance that a ROM has a (poorly conceived, imho) dependency on TWRP, flash TWRP for loading the ROM, then flash back to PhilZ to get backups on OTG, proper battery handling, proper screen handling, etc.
It's a free world, no need to keep something loaded that bugs you. Load when needed, stay safe otherwise.
The issues with ROMs with different recoveries, if any, almost always end up an error properly checking device properties in the installer script. Easy fix, just have to let the dev know what's up.
Click to expand...
Click to collapse
hey, you seem to know your way around android quite well. I too am a fan of philz. I was wondering if you have tried renovate rom? I read a few posts in its thread that people with philz cannot flash rom successfully. I also could not get past aroma(aroma was unresponsive to touch). I asked in thread and although fisha21 was considerate, did not get an answer due to most using twrp. I realize I can switch to flash, wondering what you thought might cause such issues? thx
also it was renovate milestone 7
jblaze10 said:
hey, you seem to know your way around android quite well. I too am a fan of philz. I was wondering if you have tried renovate rom? I read a few posts in its thread that people with philz cannot flash rom successfully. I also could not get past aroma(aroma was unresponsive to touch). I asked in thread and although fisha21 was considerate, did not get an answer due to most using twrp. I realize I can switch to flash, wondering what you thought might cause such issues? thx
also it was renovate milestone 7
Click to expand...
Click to collapse
Never ran renovate, actually don't plan to. I'm on @hawknest's EclipticONE 4.4.2 -- excellent kitkit/sense setup based on @baadnewz InsertCoin 7.x builds.
Anyway -- the issue with touch is not PhilZ, CWM, or TWRP -- it's a known Aroma bug and frankly the developers of Renovate are the best place to work with to work around that bug (note that InsertCoin, ViperONE, and a host of other Aroma users all work fine).
With that said -- touch is not required, at least if the install script was written correctly *not* to assume touch availability. Your vol up/down should work for navigation, and power for select. Note, btw, that if you install the Aroma file manager in PhilZ, half the time the touch doesn't work, but the buttons do (again, an Aroma bug -- not PhilZ, CWM or TWRP issue if touch blows it).
Related
HTC One
Sprint
HBOOT 1.55
S [ON]
OS 3.04.651.2
Problem: Friend thought it would be cool to put Android Revolution HD on my HTC One since he did it on his and wanted to surprise me with it...
Long story short he did, and now I have a soft bricked device. I've tried pushing a stock and a custom ROM through ADB sideload and I end up with a phone that acts like it is going to work, gets to the lock screen and freezes. It has no service but that's irrelevant because I can't even get past the lock screen. I can however use my volume key to raise and lower volume.
Can anyone get me past this or am I screwed till a new RUU comes out/way to get S [OFF] after hitting 1.55?
You can try this I'm not sure if it will work but it's worth a try
http://forum.xda-developers.com/showthread.php?t=2470569
bigdaddy619 said:
You can try this I'm not sure if it will work but it's worth a try
http://forum.xda-developers.com/showthread.php?t=2470569
Click to expand...
Click to collapse
Thanks so much for the reply, I'll give it a shot. I'm desperate right now willing to try anything.
Also forgot to mention the boot animation does fine, the phone acts like it's going to work fine then it just plain freezes where it would normally give you the "sign into google account" and name your phone. So I'm not sure what's missing if anything, if anyone has solved this and is willing to help I would greatly appreciate it.
Your partitions are messed up because he flashed a GSM rom on your CDMA device
bigdaddy619 said:
Your partitions are messed up because he flashed a GSM rom on your CDMA device
Click to expand...
Click to collapse
Yeah, exactly. Is there any way I can go about fixing that? I'm checking out that guys thread, and it sounds promising... but I can't figure out how to get my drive to sync with my PC to transfer it to TWRP to install it. I'm going to try to ADB it but I doubt that will work. Starting to lose hope at the moment lol but trying to stay optimistic.
Asosaki said:
Yeah, exactly. Is there any way I can go about fixing that? I'm checking out that guys thread, and it sounds promising... but I can't figure out how to get my drive to sync with my PC to transfer it to TWRP to install it. I'm going to try to ADB it but I doubt that will work. Starting to lose hope at the moment lol but trying to stay optimistic.
Click to expand...
Click to collapse
Only way to fix the partitions is to run an RUU which we don't have.
Is your phone seen by your PC when it's plugged in and booted to the rom? I know it doesn't boot correctly but maybe you can move the file to your phone.
You could also try adb push nameoffile.zip /sdcard/ most likely won't work because of the partitions
Format with TWRP first to get partitions clean, then adb push Rom/sideload
Sent from my HTCONE using XDA Premium 4 mobile app
I'm pretty sure the radio partition get overwritten as well so I would say format sd in twrp, flash a radio in fastboot then sideload your Rom and flash it
Sent from my HTCONE using XDA Premium 4 mobile app
18th.abn said:
I'm pretty sure the radio partition get overwritten as well so I would say format sd in twrp, flash a radio in fastboot then sideload your Rom and flash it
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the replies guys, going to try that now. It feels like entire ROM would work fine and there was just "something missing" from my phone. It may very well be a radio. I know something got wiped that shouldn't have because I had to do partition reset due to... well I'm sure you know. Also had to side load TWRP. Learning experience for me, not frustrated at least I'm getting knowledge to help others with it if I can solve it on my own.
Okay so, reporting back that FIXED my no service issue, and it's bringing up updates in the notification bar, only problem is I can't use the touch interface. I don't think my phone is broken, I think it just lacks everything that makes it a smartphone.
Anyone have an idea as to what I can flash to get it back up and running? It feels like it's missing touch interface, and whatever is needed to initiate the "factory" setup screens. Shouldn't the ROM include all of that? I put Viper ROM 1 on there. Progress was made, but it's missing something lol.
The radio also stopped it from resetting and turning itself off after 30 seconds like it was doing previously. Is there a flash-able touch interface I can throw on it? Heh...
Also noticed after it was plugged in for a couple of minutes it's detected by my PC now so I don't need to side-load anymore. Not that it was hard to, just a step forward I think. Just need to figure out what's missing from the boot screen and what I need to put on it to be able to use the touch screen. Any ideas?
Asosaki said:
Okay so, reporting back that FIXED my no service issue, and it's bringing up updates in the notification bar, only problem is I can't use the touch interface. I don't think my phone is broken, I think it just lacks everything that makes it a smartphone.
Anyone have an idea as to what I can flash to get it back up and running? It feels like it's missing touch interface, and whatever is needed to initiate the "factory" setup screens. Shouldn't the ROM include all of that? I put Viper ROM 1 on there. Progress was made, but it's missing something lol.
The radio also stopped it from resetting and turning itself off after 30 seconds like it was doing previously. Is there a flash-able touch interface I can throw on it? Heh...
Also noticed after it was plugged in for a couple of minutes it's detected by my PC now so I don't need to side-load anymore. Not that it was hard to, just a step forward I think. Just need to figure out what's missing from the boot screen and what I need to put on it to be able to use the touch screen. Any ideas?
Click to expand...
Click to collapse
Looks like you just need to flash a 4.3 rom
bigdaddy619 said:
Looks like you just need to flash a 4.3 rom
Click to expand...
Click to collapse
Really? That's the only problem you think? I'mma try that out I'll give you a message as soon as I do. Thanks again.
Also, is there any way I can get a MOD or someone to un-lock my account? This 5 minute wait is for the birds lol I got hardware on the line here :angel: Need all the posts/help I can get hahaha.
bigdaddy619 said:
Looks like you just need to flash a 4.3 rom
Click to expand...
Click to collapse
You are the MAN my phone's fixed now. BoO YaH. Now I can go beat my buddy up with peace of mind knowing my phone is in good working order.
Now running Stock with goodies, guess the other custom ROMs I put on it were just lacking 4.3 stability. You rock broski.
Asosaki said:
guess the other custom ROMs I put on it were just lacking 4.3 stability.
Click to expand...
Click to collapse
New firmware had updated touch drivers. That's why your touch screen wasn't working right.
bigdaddy619 said:
You can try this I'm not sure if it will work but it's worth a try
http://forum.xda-developers.com/showthread.php?t=2470569
Click to expand...
Click to collapse
Your the man bigdaddy, good to know there is a glimmer of hope for those with 4.3 and s-on.
Sent from my HTCONE using xda app-developers app
Since you're on the newest firmware you can only flash 4.3 sprint roms..the touchscreen firmware has been updated. You can't downgrade or s-off because you're on hboot 1.55. Just sideload a 4.3 Rom and you'll be up and running fine
Sent from my HTCONE using XDA Premium 4 mobile app
ok my problem is ive tried installing a few different roms VIPERONE being the one i want. when i go to recovery and try installing any custom Roms i get the Succesful FAILED instantly. i tried bad boyz rom based on the 1.54.654.9 version but still no luck. i cannot figure out why this is happening. ive tried with TWRP 2.7.0.0 revcovery as well and same thing happens. i really want ViperONE Rom as i have used it on my previous phones and its the best. anyone having this issue or know why its happening please help. thanks
i have the HTC ONE M8 Harman kardon edition with software version 1.54.654.9 i am htc unlocked, Captains Recovery, rooted, s-off', and SuperCID on stock Rom still
i searched for an answer already but did not find anything on it so sorry if i missed something.
Try to update your recovery to 2.7.0.2
Sent From My Sprint® HTC One M8™ Rooted Unlocked S-Offed TWRP 2.7.0.2
---------- Post added at 08:27 AM ---------- Previous post was at 08:20 AM ----------
Original T said:
ok my problem is ive tried installing a few different roms VIPERONE being the one i want. when i go to recovery and try installing any custom Roms i get the Succesful FAILED instantly. i tried bad boyz rom based on the 1.54.654.9 version but still no luck. i cannot figure out why this is happening. ive tried with TWRP 2.7.0.0 revcovery as well and same thing happens. i really want ViperONE Rom as i have used it on my previous phones and its the best. anyone having this issue or know why its happening please help. thanks
i have the HTC ONE M8 Harman kardon edition with software version 1.54.654.9 i am htc unlocked, Captains Recovery, rooted, s-off', and SuperCID on stock Rom still
i searched for an answer already but did not find anything on it so sorry if i missed something.
Click to expand...
Click to collapse
Here install this and you can try multiple recoveries to see which one works for you. I think that is your problem. Just a side note...you have to use the volume and power buttons to navigate through aroma installer. Hope this helped man. Let me know
http://forum.xda-developers.com/showthread.php?t=2743927
[AROMA][SPRINT]Recovery Switcher[2014-05-07]
Sent From My Sprint® HTC One M8™ Rooted Unlocked S-Offed TWRP 2.7.0.2
Just try capt throwbacks version, you'll find it on the mikmik website or in his signature.
Sent from my 831C using XDA Premium 4 mobile app
FYI, I posted in the other thread he made about the issue and it is indeed a problem with twrp recovery, it is not fully compatible with the hk version for some reason, I "solved" my issue by using philz touch recovery
I am currently running capt. Throwbacks recovery but I will give the other recoveries a try as u suggest. I'll let ya know if I get one to work.
stark1159 said:
Try to update your recovery to 2.7.0.2
Sent From My Sprint® HTC One M8™ Rooted Unlocked S-Offed TWRP 2.7.0.2
---------- Post added at 08:27 AM ---------- Previous post was at 08:20 AM ----------
Here install this and you can try multiple recoveries to see which one works for you. I think that is your problem. Just a side note...you have to use the volume and power buttons to navigate through aroma installer. Hope this helped man. Let me know
http://forum.xda-developers.com/showthread.php?t=2743927
[AROMA][SPRINT]Recovery Switcher[2014-05-07]
Sent From My Sprint® HTC One M8™ Rooted Unlocked S-Offed TWRP 2.7.0.2
Click to expand...
Click to collapse
Sorry to thread jack if that's what I'm doing but his issue was probably fixed as he has not updated this and it's touching on an issue I have with Aroma installers....I've tried the Bad Boys, NVProject, Bad Seed (i think) and one or two other Sense ROMS and they all use Aroma installers. Even that Recovery Switcher that uses Aroma I can't get working properly. I believe in many cases the touch screen is supposed to be working but mine will not work nor do that arrow keys + power advance me down the list of options. I can SOMETIMES check the agreement boxes if I hold power and press a bunch of times on the screen while hitting the side buttons, lol. This 'technique' has gotten me almost all the way through an Aroma installation but, inevitably, I end up hitting back instead of finish or can't make anyting but the "about' to come up.
I have no problems installing AOSP and AOKP roms via Philz or the Twrp I was using its only the Sense ROMS/Aroma combo that are giving me trouble....
Currently I am S-OFF and have reverted back to the sense stock rom and taken the OTA which has me up to software version 1.54.654.13.
I am having issues with my 3G and getting stuck in 1xRTT or Roaming constantly but I think this may be a network issue as tens of thousands of acres have burnt to the ground as close as 1 mile from my house this week and Sprint said they had dispatched some technicians to examine some of their structures/tower in southern california......
The only other thing I can think of is that I had to fastboot oem writeCID 11111111 to get the RUU to work...was I supposed to change that to something else afterwards?
slimbrady said:
Sorry to thread jack if that's what I'm doing but his issue was probably fixed as he has not updated this and it's touching on an issue I have with Aroma installers....I've tried the Bad Boys, NVProject, Bad Seed (i think) and one or two other Sense ROMS and they all use Aroma installers. Even that Recovery Switcher that uses Aroma I can't get working properly. I believe in many cases the touch screen is supposed to be working but mine will not work nor do that arrow keys + power advance me down the list of options. I can SOMETIMES check the agreement boxes if I hold power and press a bunch of times on the screen while hitting the side buttons, lol. This 'technique' has gotten me almost all the way through an Aroma installation but, inevitably, I end up hitting back instead of finish or can't make anyting but the "about' to come up.
I have no problems installing AOSP and AOKP roms via Philz or the Twrp I was using its only the Sense ROMS/Aroma combo that are giving me trouble....
Currently I am S-OFF and have reverted back to the sense stock rom and taken the OTA which has me up to software version 1.54.654.13.
I am having issues with my 3G and getting stuck in 1xRTT or Roaming constantly but I think this may be a network issue as tens of thousands of acres have burnt to the ground as close as 1 mile from my house this week and Sprint said they had dispatched some technicians to examine some of their structures/tower in southern california......
The only other thing I can think of is that I had to fastboot oem writeCID 11111111 to get the RUU to work...was I supposed to change that to something else afterwards?
Click to expand...
Click to collapse
The problem is the aroma installer hasn't been updated to be compatible with spirit as of yet. Use the volume up/down to highlight things and power to select. I think it's vol down 4 times and then up once to get to next. You will get the hang of it.
Sent from my 831C using Tapatalk
ok sorry havent updated til now but i have tried all the recoveries in the zip to install multiple recoveries easily and not one of them would work to install viperone rom but i tried bady boyz with them all as well and i was able to get that installed using philz recovery but none of the others worked with it. when i try viperone with any recovery it wont even start up aroma intsaller at all just gives me failed right away in the recovery. so as of now im on bad boyz rom but i want viperone rom im not satisfied with any other. bad boyz is a good rom dont get me wrong i have just used viper since i began rooting my phones and i love it. anyways aroma works for the recovery install zip just fine (other then the touch not working) so i dont knopw if its a recovery issue or something with aroma or possibly viperone rom even i have no clue?. thanks for all ur replies and suggestions everyone ur a big help always. id love to get this solved so i can run viperone rom again as i had on my first H/K M8 that i exchanged for the current one i am using. sorry again took so long to update
Konfuzion said:
The problem is the aroma installer hasn't been updated to be compatible with spirit as of yet. Use the volume up/down to highlight things and power to select. I think it's vol down 4 times and then up once to get to next. You will get the hang of it.
Sent from my 831C using Tapatalk
Click to expand...
Click to collapse
oh as to the volume/power buttons for selecting the options in aroma. i believe that there is no exact combo to get the selection on the next button. ive had 1 or 2 pages that i only hit down once and it selected next right away and then sometimes it didnt. so it varies on the up down number of times. ive had it not work using down so many times then up once a few times so its hard to really be certain . just my finding about that issue.
Original T said:
ok sorry havent updated til now but i have tried all the recoveries in the zip to install multiple recoveries easily and not one of them would work to install viperone rom but i tried bady boyz with them all as well and i was able to get that installed using philz recovery but none of the others worked with it. when i try viperone with any recovery it wont even start up aroma intsaller at all just gives me failed right away in the recovery. so as of now im on bad boyz rom but i want viperone rom im not satisfied with any other. bad boyz is a good rom dont get me wrong i have just used viper since i began rooting my phones and i love it. anyways aroma works for the recovery install zip just fine (other then the touch not working) so i dont knopw if its a recovery issue or something with aroma or possibly viperone rom even i have no clue?. thanks for all ur replies and suggestions everyone ur a big help always. id love to get this solved so i can run viperone rom again as i had on my first H/K M8 that i exchanged for the current one i am using. sorry again took so long to update
Click to expand...
Click to collapse
Did you try formatting data, cache, and system partitions in any of the recoveries that worked? Or have you tried a RUU (if you are s-off)
metalspring said:
Did you try formatting data, cache, and system partitions in any of the recoveries that worked? Or have you tried a RUU (if you are s-off)
Click to expand...
Click to collapse
i have not tried that in all the diff recoveries actually.
i am s-off and not sure about RUUing at all with this phone. i will give them ideas a try now and report back once done. hope that works.
which RUU would u suggest i try? i am on Bad Boyz Sprint ONE M8 Harman v1.1 rom with build 1.54.654.13. if that matters any.
If u know a link to the RUU thatd be great help and save me a lill time. thanks
Original T said:
i have not tried that in all the diff recoveries actually.
i am s-off and not sure about RUUing at all with this phone. i will give them ideas a try now and report back once done. hope that works.
which RUU would u suggest i try? i am on Bad Boyz Sprint ONE M8 Harman v1.1 rom with build 1.54.654.13. if that matters any.
If u know a link to the RUU thatd be great help and save me a lill time. thanks
Click to expand...
Click to collapse
I know my issue was fixed by using philz recovery, wiping data, cache, and system and then installing a new rom. If the issue is what I think it is, then wiping all the partitions I mentioned should fix it. (I think the issue is related to some file system corruption and twrp not being able to properly handle the corruption, when other recoveries work just fine, so formatting the partition will get rid of the corrupted data)
http://forum.xda-developers.com/showthread.php?t=2729173
metalspring said:
I know my issue was fixed by using philz recovery, wiping data, cache, and system and then installing a new rom. If the issue is what I think it is, then wiping all the partitions I mentioned should fix it. (I think the issue is related to some file system corruption and twrp not being able to properly handle the corruption, when other recoveries work just fine, so formatting the partition will get rid of the corrupted data)
http://forum.xda-developers.com/showthread.php?t=2729173
Click to expand...
Click to collapse
i noticed u didnt include the boot partition to wipe.. do i only wipe the partitions u suggested or include the boot as well? sorry just dont want to mess anything up if i can avoid it. thanks again tho for quick replies.
Original T said:
i noticed u didnt include the boot partition to wipe.. do i only wipe the partitions u suggested or include the boot as well? sorry just dont want to mess anything up if i can avoid it. thanks again tho for quick replies.
Click to expand...
Click to collapse
You can wipe boot partition as well, just dont wipe anything you dont immediately recognize (I know philz touch has tons of options to wipe different partitions, and a lot of them probably would be bad to wipe lol)
metalspring said:
You can wipe boot partition as well, just dont wipe anything you dont immediately recognize (I know philz touch has tons of options to wipe different partitions, and a lot of them probably would be bad to wipe lol)
Click to expand...
Click to collapse
ok i wiped said partitions and tried installing viper from philz recovery and twrp recovery and no go same thing happening. almost got worried when i tried rebooting and got the "no OS installed, r u sure?" but i just installed bad boyz again to get going again. im gonna try RUUing cause now i get a message after my phone starts saying something bout inconsistent partitions, u must wipe data partition or phone will be unstable. so gonna just RUU and start from there. do u know by chance if it is possible to create a backup with say twrp recovery and able to restore it with any of the recoveries such as philz or does a backup need to restored using the recovery it was created with? thanks again.
Here is a shot of what I received in philz after attempting viper install. http://i1369.photobucket.com/albums...s/2014-05/IMG_20140519_010012_zpsl8wwj5mi.jpg
ok so i RUUed with the RUU u suggested and then tried installing Viperone rom and still getting the same failed status. i tried restoring my backup i made before attempting these suggestions and it seems they do not restore completely either. errrrr so frustrating! my first M8 i had no problems with root soff recovery or installing viperone... this one is just not going so well. im gonna keep at it tho until i get viperone on my phone. lol
Good news.. I was able to install ViperONEm8 rom finally after all the hassle.
i went to TWRP recovery website and downloaded the TWRP recovery 2.7.0.2 and downnloaded ViperONEm8 1.5.0 version and flashed the recovery and installed the 1.5.0 version without a problem i tried 1.6.0 first but got the failed thing again but 1.5.0 installed no problem. YAYYY!!
Thank you all for your help
So I've tried installing this half a dozen times, I did a full wipe I'm using the i9305 and installing this using both kernel options for the knox based bootloader, after it completes installation it says complete, reboot the phone and I end up stuck at the Samsung Galaxy s3 black screen and it never boots into the os.
I noticed while installing this it installs some modem not sure what one it is but I thought perhaps that was the issue, to installed went straight into download mode and flashed a optus modem i've been using for my phone rebooted but still same issue.
Would appreciate some help with this, I've tried searching the thread for similar issues no such luck.
Thanks
Demonic Wraith said:
So I've tried installing this half a dozen times, I did a full wipe I'm using the i9305 and installing this using both kernel options for the knox based bootloader, after it completes installation it says complete, reboot the phone and I end up stuck at the Samsung Galaxy s3 black screen and it never boots into the os.
I noticed while installing this it installs some modem not sure what one it is but I thought perhaps that was the issue, to installed went straight into download mode and flashed a optus modem i've been using for my phone rebooted but still same issue.
Would appreciate some help with this, I've tried searching the thread for similar issues no such luck.
Thanks
Click to expand...
Click to collapse
maybe your using a old recovery?
MaHo_66 said:
maybe your using a old recovery?
Click to expand...
Click to collapse
Thanks but it's not that, I wasn't even aware of having to use the newer one for the recovery till recently and have been using the one for the old recovery even tho I have the new one... either way, I tried installing both the new and old recovery's same results.
Demonic Wraith said:
Thanks but it's not that, I wasn't even aware of having to use the newer one for the recovery till recently and have been using the one for the old recovery even tho I have the new one... either way, I tried installing both the new and old recovery's same results.
Click to expand...
Click to collapse
i see, well your 2 posts away from being able to post in development thread, you will get better help in rom thread try a full wipe anyway and install the rom with default aroma settings, maybe the problem lies in some setting you change in aroma installer..
MaHo_66 said:
i see, well your 2 posts away from being able to post in development thread, you will get better help in rom thread try a full wipe anyway and install the rom with default aroma settings, maybe the problem lies in some setting you change in aroma installer..
Click to expand...
Click to collapse
True, that could be it, except i thought of that myself and just hit next next next to the end and hit install to see if it would help matters it didn't. Yeah I tried posting there to begin with, but even if your an advanced person you have to post here first lol fun times
I did think maybe there's a newer version of philz recovery out and mine just buggers it up some how it offers to install 6.41.6 not sure what my version is.. it crossed my mind tho but I wouldn't presume that's the most likely of causes.
Demonic Wraith said:
True, that could be it, except i thought of that myself and just hit next next next to the end and hit install to see if it would help matters it didn't. Yeah I tried posting there to begin with, but even if your an advanced person you have to post here first lol fun times
I did think maybe there's a newer version of philz recovery out and mine just buggers it up some how it offers to install 6.41.6 not sure what my version is.. it crossed my mind tho but I wouldn't presume that's the most likely of causes.
Click to expand...
Click to collapse
hmm.. well philz 6.41.6 is the latest one a.t.m and roms these days need up to date recovery so you can give it a shot if you are not on philz yet. here is the latest one http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
flash it with odin then try again, hopefully this will fix your problem
MaHo_66 said:
hmm.. well philz 6.41.6 is the latest one a.t.m and roms these days need up to date recovery so you can give it a shot if you are not on philz yet. here is the latest one http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
flash it with odin then try again, hopefully this will fix your problem
Click to expand...
Click to collapse
Yeah unfortunately that didn't work either, was worth a shot tho now I can post in the proper place.
Demonic Wraith said:
Yeah unfortunately that didn't work either, was worth a shot tho now I can post in the proper place.
Click to expand...
Click to collapse
haha yeah man
First and foremost, let me say that I messed up.
Now that that's out of the way, let me begin;
I have a VS980 (obviously) with Cyanogenmod 11 running the latest nightly (6-26 I believe, running 4.4.4), and as many know the Verizon version has had issues with any rom with rotation issues. So I decided to search around and try and find a fix for this, and the most likely fix seemed to be flashing a KK baseband. I know before that my device was 12B or whatnot.
Well, now I'm in a bootloop, and have no clue what to do next.
Ive tried restoring from a nandroid backup and straight up reflashing the ROM.
I have TWRP 2.7.0.0 installed, but my United drivers wont recognize my G2 when in recovery (even though the computer sees it as "VS980" in devices), and I just downloaded and started up the SDK, but haven't downloaded anything other than that.
What I think might work is pushing the correct baseband to the phone, but I have no idea how to do so. I know basic ADB from a past experience, but very very basic.
I need some direction as what to do is what I'm saying. Any and all help is much appreciated, thank you so much!
Chirzu said:
First and foremost, let me say that I messed up.
Now that that's out of the way, let me begin;
I have a VS980 (obviously) with Cyanogenmod 11 running the latest nightly (6-26 I believe, running 4.4.4), and as many know the Verizon version has had issues with any rom with rotation issues. So I decided to search around and try and find a fix for this, and the most likely fix seemed to be flashing a KK baseband. I know before that my device was 12B or whatnot.
Well, now I'm in a bootloop, and have no clue what to do next.
Ive tried restoring from a nandroid backup and straight up reflashing the ROM.
I have TWRP 2.7.0.0 installed, but my United drivers wont recognize my G2 when in recovery (even though the computer sees it as "VS980" in devices), and I just downloaded and started up the SDK, but haven't downloaded anything other than that.
What I think might work is pushing the correct baseband to the phone, but I have no idea how to do so. I know basic ADB from a past experience, but very very basic.
I need some direction as what to do is what I'm saying. Any and all help is much appreciated, thank you so much!
Click to expand...
Click to collapse
If you can get it in download mode, restore it back to stock using the guide in the General section..
Doesnt download mode require it to actually boot? Im bootlooping.
Sent from my SCH-I510 using XDA Free mobile app
Chirzu said:
Doesnt download mode require it to actually boot? Im bootlooping.
Sent from my SCH-I510 using XDA Free mobile app
Click to expand...
Click to collapse
You should still be able to get into recovery, it's just getting the timing right. Recovery has it's own kernel.
Try holding down power for 15 or so seconds til it restarts, immediately hit the volume down and power, let go when the LG splash screen comes up and hit them both again.
You'll get the factory hard reset screen, keep hitting power til it gets you to Recovery.
CM11 nightlies are still based on JB kernel source, so you need the 12B radio for it to boot. That's why you're bootlooping. So if you have a 12B radio on your SD, you can flash that. Then clean flash your current build of CM11. Should boot up then. If I was you I'd think about updating to 24A, and use one of the ROMs that use KK kernel source. There's a CM11 for 24A build out. Not in nightlies but pretty frequent builds.
mjones73 said:
You should still be able to get into recovery, it's just getting the timing right. Recovery has it's own kernel.
Try holding down power for 15 or so seconds til it restarts, immediately hit the volume down and power, let go when the LG splash screen comes up and hit them both again.
You'll get the factory hard reset screen, keep hitting power til it gets you to Recovery.
Click to expand...
Click to collapse
Its not Recovery that I have an issue getting into, its download mode. I have no problem getting into there, however, I have no idea about anything regarding download mode.
JRJ442 said:
CM11 nightlies are still based on JB kernel source, so you need the 12B radio for it to boot. That's why you're bootlooping. So if you have a 12B radio on your SD, you can flash that. Then clean flash your current build of CM11. Should boot up then. If I was you I'd think about updating to 24A, and use one of the ROMs that use KK kernel source. There's a CM11 for 24A build out. Not in nightlies but pretty frequent builds.
Click to expand...
Click to collapse
I dont think I do, but do you know how I can get my drivers to work or where I can pull drivers from for my laptop to recognized my phone so I can push a radio to it?
Will definitely think about KK in the future, thank you.
Sent from my SCH-I510 using XDA Free mobile app
http://forum.xda-developers.com/showthread.php?t=2448960 I got mine from this thread. I've had issues too some. Sometimes I've actually had to install them a couple times with the phone plugged into my laptop to get them to work
Thanks man, Ill definitely try that out when I get to my computer.
Sent from my SCH-I510 using XDA Free mobile app
JRJ442 said:
http://forum.xda-developers.com/showthread.php?t=2448960 I got mine from this thread. I've had issues too some. Sometimes I've actually had to install them a couple times with the phone plugged into my laptop to get them to work
Click to expand...
Click to collapse
Update: The drivers honestly didn't matter in the end I think, as I tried it with 3/4 of them successfully installing (The CDC one never installed correctly) and everything went perfectly!
Thank you so much for pointing me in the right direction.
Sent from my kickass VS980
I'm new to android.I'm quite confused about the whole custom Rom installation process.I managed to unlock bootloader and root my phone.I tried to find guides to let me install custom roms on my device.I have a vague idea about the whole process but whenever I look at a ROM release thread, half the information there is beyond me.I would be happy if someone pointed me in the right direction to a complete guide with noob friendly instructions.Also, I would prefer to stay S-On, can someone help me with the whole s-off regarding custom Rom stuff too?
Thanks.
Sent from my HTC One using XDA Free mobile app
Nanda K said:
I'm new to android.I'm quite confused about the whole custom Rom installation process.I managed to unlock bootloader and root my phone.I tried to find guides to let me install custom roms on my device.I have a vague idea about the whole process but whenever I look at a ROM release thread, half the information there is beyond me.I would be happy if someone pointed me in the right direction to a complete guide with noob friendly instructions.Also, I would prefer to stay S-On, can someone help me with the whole s-off regarding custom Rom stuff too?
Thanks.
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
You don't need s-off to flash most custom roms. Only some GPE version will require s-off.
Flash twrp 2.8.5.0
boot your phone in recovery mode
plug your phone to your pc
place your rom.zip on your phone storage
in twrp select "install"
choose your rom.zip
swipe to flash
Follow instructions from the rom installer (aroma installer)
reboot
Nanda K said:
I'm new to android.I'm quite confused about the whole custom Rom installation process.I managed to unlock bootloader and root my phone.I tried to find guides to let me install custom roms on my device.I have a vague idea about the whole process but whenever I look at a ROM release thread, half the information there is beyond me.I would be happy if someone pointed me in the right direction to a complete guide with noob friendly instructions.Also, I would prefer to stay S-On, can someone help me with the whole s-off regarding custom Rom stuff too?
Thanks.
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Ill be honest. Doing things like this are not meant to be noob friendly.
Take about a week and do lots of reading this way if something goes wrong you will know how to recover.
That's what I'm having trouble with.I cant seem to find any solid reading material for stuff like these.For example, will restoring a nandroid backup really fix problems like bootloops and other errors you may run into while flashing ROMS? Also,how do kernels and ROMs match up? are they independent of each other or do certain ROMs work only when you have a particular kernel installed? will a wrong kernel cause any issues with certain ROMs and I'm seriously scared of bricking my device since the amount you're required to know is quite vast.I used to have an iPhone until the HTC One M7 and I was pretty much an advanced user on the iOS platform.I wouldnt call myself a noob, but I cant call myself an advanced android user either.Atleast not yet.
Nanda K said:
That's what I'm having trouble with.I cant seem to find any solid reading material for stuff like these.For example, will restoring a nandroid backup really fix problems like bootloops and other errors you may run into while flashing ROMS? Also,how do kernels and ROMs match up? are they independent of each other or do certain ROMs work only when you have a particular kernel installed? will a wrong kernel cause any issues with certain ROMs and I'm seriously scared of bricking my device since the amount you're required to know is quite vast.I used to have an iPhone until the HTC One M7 and I was pretty much an advanced user on the iOS platform.I wouldnt call myself a noob, but I cant call myself an advanced android user either.Atleast not yet.
Click to expand...
Click to collapse
Wow yeah you need to do alot of reading then. Now while I mean no insult. Being an advanced user for IOS and jumping to android is like going from first grade and then jumping to the 12th.
Yes depending on the device kernels only work with matching roms. Take the m7 you mentioned. You have 4 kind of kernels. AOSP, AOSP-Caf, Sense and CM
Each has to be paired with a matching rom. IF you flash the wrong one then it can cause a bootloop. Never expect a nandroid to be a fix all. While it will fix things alot of the time it is not an end all to fixing a bad flash. Sometimes you will have to flash things with a bootloader from command line. Depending on your OS on your PC there could also be other issues. So at times you may need a linux based live disc or partition.
Nanda K said:
That's what I'm having trouble with.I cant seem to find any solid reading material for stuff like these.For example, will restoring a nandroid backup really fix problems like bootloops and other errors you may run into while flashing ROMS? Also,how do kernels and ROMs match up? are they independent of each other or do certain ROMs work only when you have a particular kernel installed? will a wrong kernel cause any issues with certain ROMs and I'm seriously scared of bricking my device since the amount you're required to know is quite vast.I used to have an iPhone until the HTC One M7 and I was pretty much an advanced user on the iOS platform.I wouldnt call myself a noob, but I cant call myself an advanced android user either.Atleast not yet.
Click to expand...
Click to collapse
Your in safe hands with this forum....theres not nuch that cannot be solved if you go wrong,however there are a multitude of good videos on you tube .
I found this guys videos very easy to follow https://www.youtube.com/channel/UCKlOmM_eB0nzTNiDFZibSSA
A little out of date now but a good image of what to do,backed up with the knowledge base on this forum its relatively easy!
Once you have a custom recovery make back ups before you do anything,I found buying an OTG cable and USB drive a good way to create lots of back ups ,so if things go wrong you have a good restore point.
Unlikely to brick your device if you keep S-on ,build up your confidence and go S-off when you can...its like xmas everyday once you know how to use the power it brings!
Okay,let me start off simple.My HTC One M7 is on complete stock now.Running Lollipop from HTC.It is an unlocked Hong Kong version.Bootloader unlocked and TWRP recovery flashed.I need a kernel which will enable motion launch gestures as on the one m8 and also functions like sweep2wake etc.Can someone link me to the appropriate kernel to flash?
I know how to flash the kernel, I have trouble choosing the right one.
Sent from my HTC One using XDA Free mobile app
Nanda K said:
Okay,let me start off simple.My HTC One M7 is on complete stock now.Running Lollipop from HTC.It is an unlocked Hong Kong version.Bootloader unlocked and TWRP recovery flashed.I need a kernel which will enable motion launch gestures as on the one m8 and also functions like sweep2wake etc.Can someone link me to the appropriate kernel to flash?
I know how to flash the kernel, I have trouble choosing the right one.
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
If you are running stock rom (sense 6) + lollipop and your phone is a M7_UL or M7_U then ElementalX 20.1 should work fine
From one noob to another haha
I really like ViperOne mods, but I haven't used Elements.
alray nailed it -- easiest ROM install.
you need to install TWRP first.
I used the HTC One Toolkit for this, you can find it on XDA. (Sorry new user, I can't post links)
I assume your phone is still unlocked. -- if not, unlock it
Have Debug mode Enabled on your phone. (Settings -> About -> Software information -> More -> Click Build number 10 times)
Settings -> Developer options -> USB Debugging -> Checked
Using HTC One Toolkit, click ADB -> Devices
this will start adb. you might wait a second or 5 for your device to be shown.
Then click the Pull down reboot menu select bootloader, then click Reboot.
-the phone should reboot into the Bootloader.
Select Fastboot, press power button.
Then in HTC One Toolkit, close the adb window and click Fastboot.
Click Devices
-Your device should show in the main HTC One Toolkit window.
Once you see that, Under Label Flash, press ... button and select the TWRP you just downloaded. Then select Partition Recovery, then Flash.
Once complete and successful, reboot the phone into Recovery from the phone's menu.
!! NOTE !! You must reboot into Recovery before starting the ROM. Or it may re-write the Recovery.
Once in Recovery, reboot the phone from within Recovery and let it start normally.
Copy your rom (in .zip format) onto your phone. I make new folder called roms or mods on my phones so I don't lose track of where things are.
Once your Rom is copied to your phone (I suggest ViperOne 8.0.0.0), use ADB again and reboot the phone into recovery.
From TWRP Touch Install
navigate to your folder where your ROM is (zip file)
Click it and install.
I wipe all settings when I install a new ROM.
Good luck!
B
_FBi said:
I used the HTC One Toolkit for this, you can find it on XDA. (Sorry new user, I can't post links)
Using HTC One Toolkit, click ADB -> Devices
Then in HTC One Toolkit
-Your device should show in the main HTC One Toolkit window.
Click to expand...
Click to collapse
And I would highly recommend not using any toolkits but instead take an extra 30 mins to learn how to use adb and fastboot properly so if something bad happens you know how to deal with it.
Most noobs are totally stuck if something is not working as expected when using a toolkit. Wen you took the time learning adb and fastboot you'll know how to deal with most issues when flashing roms/recovery/ruu/frimware/kernel/radio and more. When you did not took any time to learn adb and fastboot and using a toolkit instead, when something unexpected happen, you'll just be stuck there because your little toolkit doesn't have any "I'm screwed, what should I do?" button.
alray said:
And I would highly recommend not using any toolkits but instead take an extra 30 mins to learn how to use adb and fastboot properly so if something bad happens you know how to deal with it.
Most noobs are totally stuck if something is not working as expected when using a toolkit. Wen you took the time learning adb and fastboot you'll know how to deal with most issues when flashing roms/recovery/ruu/frimware/kernel/radio and more. When you did not took any time to learn adb and fastboot and using a toolkit instead, when something unexpected happen, you'll just be stuck there because your little toolkit doesn't have any "I'm screwed, what should I do?" button.
Click to expand...
Click to collapse
I have nothing against using using tools, so long as they're trusted.
Nor is there anything wrong doing it by hand, if not more beneficial.
All in one tools bypass a lot of the understanding.
Alray's first post was right to the point, basic, and a perfect example.
B
I do know how to use adb and command line to do all that.Intact I did not know that there was a toolkit to do this before I read that post
I do have some experience with the HTC wildfire and sensation XL.But they were considerably older devices which I used a long time ago as temporary ones.
The HTC One is my first non iOS device.
Sent from my HTC One using XDA Free mobile app