Related
So far I've had no luck using custom ROMs as it just stays on the htc boot screen and does not work. I can confirm that 'MiUi' does work on my phone - however it is buggy and I don't like it.
I want cyanogenod or either android revolution HD but none of these work.
I thinkit has something to do with the HBOOT being 1.16.000, and the ROM version i'm after is 2.34.981.1 (virgin or optus branded) - am with virgin though in Australia.
I have a custom bootloader/recovery whatever you call it, I wipe the cache, dalvik cache and factory wipe, before installing all ROM's. I can't update to stock ROM either because there is none for hboot 1.16.000
So right now my phone is pretty much a paper weight until I can get it working again.
I prefer custom ROM's if there is any that work, if not I atleast want the stock ROM to work for now so I can use my phone. If someone can help me through the process to get it working it would be greatly appreciated. Thanks.
jakeyo said:
So far I've had no luck using custom ROMs as it just stays on the htc boot screen and does not work. I can confirm that 'MiUi' does work on my phone - however it is buggy and I don't like it.
I want cyanogenod or either android revolution HD but none of these work.
I thinkit has something to do with the HBOOT being 1.16.000, and the ROM version i'm after is 2.34.981.1 (virgin or optus branded) - am with virgin though in Australia.
I have a custom bootloader/recovery whatever you call it, I wipe the cache, dalvik cache and factory wipe, before installing all ROM's. I can't update to stock ROM either because there is none for hboot 1.16.000
So right now my phone is pretty much a paper weight until I can get it working again.
I prefer custom ROM's if there is any that work, if not I atleast want the stock ROM to work for now so I can use my phone. If someone can help me through the process to get it working it would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Hyun is looking for you at revolutionary irc channel.
Sent from my HTC Incredible S using Tapatalk
I know.. I have spoken to him.
jakeyo said:
I know.. I have spoken to him.
Click to expand...
Click to collapse
Any luck? still unable to flash anything?
jakeyo said:
So far I've had no luck using custom ROMs as it just stays on the htc boot screen and does not work. I can confirm that 'MiUi' does work on my phone - however it is buggy and I don't like it.
I want cyanogenod or either android revolution HD but none of these work.
I thinkit has something to do with the HBOOT being 1.16.000, and the ROM version i'm after is 2.34.981.1 (virgin or optus branded) - am with virgin though in Australia.
I have a custom bootloader/recovery whatever you call it, I wipe the cache, dalvik cache and factory wipe, before installing all ROM's. I can't update to stock ROM either because there is none for hboot 1.16.000
So right now my phone is pretty much a paper weight until I can get it working again.
I prefer custom ROM's if there is any that work, if not I atleast want the stock ROM to work for now so I can use my phone. If someone can help me through the process to get it working it would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
If you go to the development section of the HTC Incredible 2 forum, attn1 has a script tool that uses the latest Revolutionary/Unreovked exploit to downgrade the ROMand HBOOT to a version that is supported by Revolutionary.
If you look at the script, it is pretty simple. You would just need to use an older Virgin Mobile RUU.zip instead of the Inc2 version. It looks like the 2.12.981.2 would be the one to try.
Hang on a second, how did you S-off the Hboot 1.16?
I thought you need S-off to be able to flash a custom Rom...
How did you install Miui?
Am I missing something here?
Doesnt matter if you need S-ON or S-OFF, as long as you get permissions to access root files.
Someone installed a custom bootloader so I can install custom ROM's, and it just works.... apparently the radios are locked though.
So, another day gone by and my phone is still not working. I can use MiUi, but I ran out of data on my 3g sim and wifi doesnt work, so now I have no internet on it.
katu2006 said:
Hang on a second, how did you S-off the Hboot 1.16?
I thought you need S-off to be able to flash a custom Rom...
How did you install Miui?
Am I missing something here?
Click to expand...
Click to collapse
I'm pretty sure no soff will cause the issues he is experiencing, though he doesn't seem to be listening
no, you're all just noobs.
It was the boot.img, we swapped it with the MiUi then put back the original one, now it boots up on cyanogenmod7.1 and works completely fine.
Can access root files, can take screenshots, everything is normal.
and I have s-on.
jakeyo said:
no, you're all just noobs.
It was the boot.img, we swapped it with the MiUi then put back the original one, now it boots up on cyanogenmod7.1 and works completely fine.
Can access root files, can take screenshots, everything is normal.
and I have s-on.
Click to expand...
Click to collapse
Yes im a noob that has been using android since 2009..
You seem like a supreme douche.
Weren't you the one who was crying about wanting to go back to his iphone lol
jakeyo said:
no, you're all just noobs.
It was the boot.img, we swapped it with the MiUi then put back the original one, now it boots up on cyanogenmod7.1 and works completely fine.
Can access root files, can take screenshots, everything is normal.
and I have s-on.
Click to expand...
Click to collapse
You're calling us noobs, but you don't even know what was done on your phone...
What's the following sentence supposed to say?
"It was the boot.img, we swapped it with the MiUi then put back the original one"
To get a custom Rom, you actually have to INSTALL it...To get the custom Rom installed, you need CWM recovery. But if you have HBoot 1.16.000, you can't have a custom recovery yet.
In less your "friend" did a downgrade of the HBoot to 1.13.000, it's unlikely that you have CWM recovery on your phone. Even so, to my knowledge HBoot 1.16.000 does a version check and won't let you downgrade it.
So, the question remains, how did you get CWM recovery on your phone?
katu2006 said:
You're calling us noobs, but you don't even know what was done on your phone...
What's the following sentence supposed to say?
"It was the boot.img, we swapped it with the MiUi then put back the original one"
To get a custom Rom, you actually have to INSTALL it...To get the custom Rom installed, you need CWM recovery. But if you have HBoot 1.16.000, you can't have a custom recovery yet.
In less your "friend" did a downgrade of the HBoot to 1.13.000, it's unlikely that you have CWM recovery on your phone. Even so, to my knowledge HBoot 1.16.000 does a version check and won't let you downgrade it.
So, the question remains, how did you get CWM recovery on your phone?
Click to expand...
Click to collapse
This thread is awesome
no, if I hold down power down and power button I see S-ON and HBOOT 1.16.0000
He typed in commands to give it root permissions, not sure exactly as he remote controlled my computer and typed it in. Then yes, he flashes CWM onto the phone then I installed revolutionary.
Firstly, I went onto the HTC dev site (created an account) and followed the steps to unlock the bootloader. In the end, it was successful, and once it's finished it will wipe the phone (AND WILL STILL SAY s-on)
So then the bootloader is now unlocked, and he did various commands in fastboot. My guess is that he installed CWM from there and it just worked.
at first, cyanogenmod would not boot, so he copied the (boot.img that is working) from MiUi and repled it with cyanogenmod's. The phone booted up and worked. Then he put it back how it was and it now works. Strange, but something must've given it a kick.
I'll repeat myself.
HBOOT 1.16.0000
S-ON
Cyanogenmod &.1 (stable)
Full root access
Need I say more to prove it?
As far as I know, I just cannot flash radios, which actually require the S-OFF....
sorry if I come across as rude, just a long day..
Talk to aftab565 he has the same hboot as you and has arhd running. Sounds like your phone was temp rooted and flashed and I would advise against letting people you don't know take remote access of your pc.
Hopefully it works for him I couldn't help.
Just replied to his thread.
And I know I was aware. I had full control though (could press a certain key to disconnect the connection - and only gave a temporary password) He was only typing in CMD things to do with the phone that I've heard of before
(ADB shell, fastboot recovery etc) and in the end worked well. He said my job is done and disconnect himself, so good guy
Didn't take my eyes off the screen either.
jakeyo said:
Just replied to his thread.
And I know I was aware. I had full control though (could press a certain key to disconnect the connection - and only gave a temporary password) He was only typing in CMD things to do with the phone that I've heard of before
(ADB shell, fastboot recovery etc) and in the end worked well. He said my job is done and disconnect himself, so good guy
Click to expand...
Click to collapse
You gotta give props to these guys for donating their time. Every day there's more talk about h-boot 1.16.0000 so I figure if devs want to keep devin there'll be a rev released eventually.
I really appreciate the amount of work hes done, in total I recon he's spent about 6 hours trying to help me getting it to work.
Never left me by myself, he always helped me through every step and was always there if I needed help. I've now got CM7 thanks to him. If he didn't fix it, I would have a useless phone because I couldn't even put on the stock ROM because of my HBOOT im guessing (I did an OTA update to get 1.16.0000 therefore too new to download)
I think SOME of the custom roms do have support for 1.16.0000 and what you only need is the boot file from them to boot up your non-booting ROM then you're all good.
ok, just to put some closure and sanity on this thread.
Firstly I'm probably bettery know as hyuh on #revolutionary, and it was me who was connected to his PC.
I use teamviewer to connect to people remotely, this allows anyone who doesn't like the look of *anything* I do to diconnect me...The user in front of the PC has full control of my session and I remind them to close teamviewer after we're done.
Secondly to those who think you need to be S-OFF to install a custom ROM or custom recovery, this is simply not true in the case of the 1.16 hboot. If you follow the HTC unlock procedure then you will have sufficient access to the phone to do this, it is not S-OFF just an unlock. Your phone will be in state "S-ON unlocked" This allows certain partitions on the emmc to be written to, and this sufficient for custom ROMs.
Really all that is requird is:
Code:
fastboot flash recovery <recovery.img>
then follow the normal flashing procedures.
In jakeyo's case CM7 would not boot, but MIUI would. When I say it would not boot I do not mean a boot loop here, I mean no boot period. At this point I had expected to need to rebuild a boot image for CM7 for him suspecting that HTC had done something different in the new hboot with paritions or the boot image offset.
The reason for flashing the MIUI boot image on top of CM7 was simple, to get to adb in the boot image. However seeing nothing particularly strange in the boot sequence ( other than the mismatch and resulting bootloop) I decided to reflash the CM7 boot image through fastboot.
The phone booted fully this time without issues.
It appears that the boot image simply did not flash properly from recovery the first time but I don't have a vivo to troubleshoot further.
A couple of things:
1. Don't take the OTA for 1.16 hboot if you haven't already done so.
There is currently no unofficial unlock/S-OFF
There is no RUU to fix the phone if you screw up.
There is nothing in the OTA you can't get in other ways.
2. If you're on 1.16 and want custom ROMs and aren't worried about warranty, go ahead and do unlock from HTC, but bear in mind:
There is no RUU, so you can't go back to stock
You can't flash radios
You can't superCID or similar ( but not needed since there is no RUU )
2a. You don't need any existing root method to exist, there is no exploit involved in any of this, this will work irrespective of the current status of a root expoit existing or not.
2b. The phone does not have to be listed by HTC as being supproted. Any phone with a suitable hboot can be unlocked.
if this:
Code:
fastboot oem get_identifier_token
returns an identifier code then the phone can be ulocked.
globatron said:
ok, just to put some closure and sanity on this thread.
Firstly I'm probably bettery know as hyuh on #revolutionary, and it was me who was connected to his PC.
I use teamviewer to connect to people remotely, this allows anyone who doesn't like the look of *anything* I do to diconnect me...The user in front of the PC has full control of my session and I remind them to close teamviewer after we're done.
Secondly to those who think you need to be S-OFF to install a custom ROM or custom recovery, this is simply not true in the case of the 1.16 hboot. If you follow the HTC unlock procedure then you will have sufficient access to the phone to do this, it is not S-OFF just an unlock. Your phone will be in state "S-ON unlocked" This allows certain partitions on the emmc to be written to, and this sufficient for custom ROMs.
Really all that is requird is:
Code:
fastboot flash recovery <recovery.img>
then follow the normal flashing procedures.
In jakeyo's case CM7 would not boot, but MIUI would. When I say it would not boot I do not mean a boot loop here, I mean no boot period. At this point I had expected to need to rebuild a boot image for CM7 for him suspecting that HTC had done something different in the new hboot with paritions or the boot image offset.
The reason for flashing the MIUI boot image on top of CM7 was simple, to get to adb in the boot image. However seeing nothing particularly strange in the boot sequence ( other than the mismatch and resulting bootloop) I decided to reflash the CM7 boot image through fastboot.
The phone booted fully this time without issues.
It appears that the boot image simply did not flash properly from recovery the first time but I don't have a vivo to troubleshoot further.
A couple of things:
1. Don't take the OTA for 1.16 hboot if you haven't already done so.
There is currently no unofficial unlock/S-OFF
There is no RUU to fix the phone if you screw up.
There is nothing in the OTA you can't get in other ways.
2. If you're on 1.16 and want custom ROMs and aren't worried about warranty, go ahead and do unlock from HTC, but bear in mind:
There is no RUU, so you can't go back to stock
You can't flash radios
You can't superCID or similar ( but not needed since there is no RUU )
Click to expand...
Click to collapse
Get a mod to make a hboot sticky there will be floods of this crap further down the road.
OK, so I got a HTC One yesterday. Checking the development status here I decided not to bother with stock a single day and went straight ahead to prepare it for custom ROMs. While I was at it I decided to go for S-OFF as well so i would be able to flash radios in the future.
I think something went wrong, the status is: phone boots into (stock) system allright, but it will not establish a WiFi connection at all (it worked prior to S-OFFing), when I move the slider from disable to enable it says "Turning on..." and is grayed out but it is stuck there for infinity. Switching Bluetooth on and off works, but due to this glitch I fear that somehow my radio partition got corrupted (if I recall that is usually where S-OFF flags etc are stored).
Here is exactly how I proceeded: I got the revone command line tool and moonshine tool in the newest versions.
First I used revone according to the steps outlined on XDA, which worked and displayed an S-OFF in the bootloader header. To my understanding this only gave me S-OFF, so then I proceded with moonshine to install unsecure bootloader, superuser.apk and su. This tool also ran through as described without a glitch and rebooted me into the bootloader showing the custom moonshine S-OFF header. I then used the One-in-all-tool to install a custom recovery (TWRP in this case). This also worked great.
Then I was getting ready to put on a custom ROM and tried to hook the device to my PC via USB as a mass storage to copy over the custom ROMs I downloaded. At first boot HTC Tell jumped up and claimed it "fixed something because it noticed it was not as expected". I fgured this was to be expected, with the device S-OFFed and stock ROM still on it but gave it no 2nd thought. I checked and S-OFF stuck even through this.
Copying the ROMs as planned would not work, I can browse the /mnt/sdcard contents and also read files from there, but no matter how and when I try to write anything it fails with an error (device is disconnected or not ready). I then tried to sideload a filemanager with SMB client feature so I could transfer the ROMs through my local WiFi but then I noticed the glitch with the WiFi which could not be resolved even with reboots and clearing cache/dalvik cache throuch recovery.
What is my best bet now? Try to rollback the moonshine S-OFF and reinstall the original bootloader which was backed up? Just install a custom ROMs and assume all is good and it will straighten itself out? Flash the original RUU stock ROM, therefore prolly going back to stock and re-doing the entire S-OFF process? Any ideas on how to further diagnose what (if anything) is wrong? Is it all possible to roll back to a completely stock base by flashing the RUU through TWRP?
You didn't need to use Moonshine, you could've just flashed CWM/TWRP and flashed the SuperSU package to get root access. As you're S-OFF I would flash an RUU to get back to a stock state (you'll keep S-OFF) and then try to re-root using the normal methods.
What software build are you on at the moment?
Thank you for your quick reply.
FYI, I am on PN07IMG_M7_UL_JB_50_HTC_Europe_1.29.401.13_Radio_4A.14.3250.13_10.33.1150.01_release_316789_signed. That was ther software / radio version installed when it came out of the box.
However, as per advice from the guys in moonshine IRC channel I have re-flashed the boot.backup-img moonshine created when it ran and the problem with WiFi seems to be gone. I will play around a bit more, but it could be the issue is resolved (although I fail to understand eactly why).
Sounds like the custom HBOOT could be the issue
Yes, I have just now understood how HBOOT and the bootloader / boot.img are two separate things.
I think my reasoning for using both tools was kind of: "well, instructions for moonshine say it needs a HTCDEV unlocked device to run, and then will install su / superuser.apk in one swoop, yet revone will S-OFF / unlock my phone without hopping through the HTCDEV hoops, so hell, I will just use revone to S-OFF / unlock and then moonshine to S-OFF again and get su / superuser.apk conveniently..." The facepalm in this might be obvious to the hardcore / experienced coders / developers here but it made sense for my layman brain (at least at that late time of night...).
The question at hand is resolved though, the device behaves just fine as of now.
Out of curiosity, what would happen if I went and flashed the entirety of the stock RUU (including all partitions like recovery, ramdisk, radio, hboot, etc) through TWRP? Would that work at all? And would it, as I presume, return the device to completely bone-stock-out-of-the-box or would there still be traces modifications?
Walter_White said:
Out of curiosity, what would happen if I went and flashed the entirety of the stock RUU (including all partitions like recovery, ramdisk, radio, hboot, etc) through TWRP? Would that work at all? And would it, as I presume, return the device to completely bone-stock-out-of-the-box or would there still be traces modifications?
Click to expand...
Click to collapse
Not all of that stuff can be flashed in recovery. Some partitions like hboot have to be flashed in rebootRUU mode. You can return to stock that way, but running a RUU is simpler and usually safer (provided you have the right RUU).
Hello everyone, I need some help if possible.
Basically I had a HTC One on stock 4.1.2. I unlocked the bootloader, installed ClockWorkMod and rooted the phone successfully. I've had a notification for a OTA update to 4.2.2 recently so I read that I would have to go back to stock recovery and relock the bootloader and remove root access. Somewhere along the line Ive must have totally messed up. I can start the phone and it loads up but Iv'e not got no WIFI ( hangs on turning on), SD card isnt recognised by the phone and after checking the firmware I'm still on 4.2.1. I ran the Hboot menu and it said ***Relocked*** and ***Tampered***. I tried running recovery and it had a red triangle. So I retraced my steps and unlocked the bootloader and installed CWM again.
Am I right in thinking the best thing to do would be to flash the firmware using CWM which requires root access?
Few things that may help:
Ive checked the Hboot menu and it says the phone is ***Tampered*** and ***Unlocked***
S-ON after running getvar in CMD prompt. (Does this mean phone isnt rooted any more?)
I can still get into CMW recovery but I'm not sure how I could install SuperUser if the SD is corrupt?
Ideally I'd like to get on 4.2.2 with root access but I dont know the best way to go about it. Im not too bothered about losing data, I would just like the phone back in working order. Any help would be greatly appreciated!
http://forum.xda-developers.com/showthread.php?t=2224752
That's Sense 4.2.2 stock with the link to the rooting tools. Well, everything you need is on the the post
Sent from my HTC One using xda app-developers app
Hello,
I seem to have gotten myself into a bind, and looking ahead to the 4.4 KitKat release, I am not sure how to get myself out of it. I've already done a lot of research and troubleshooting on my own, but can't seem to resolve the problem.
I purchased an HTC One Google Play edition, and decided to root to apply a quick fix with utilizing the Nexus 5 launcher. To that end, I unlocked my bootloader and rooted. I had a Windows 7 partition on my Mac at the time, but it was giving me trouble. Since the root, I became dissatisfied with the performance of the phone, and attempted to restore to factory.
I flashed stock recovery again, and relocked the bootloader. Now the bootloader shows as "relocked" and "tampered." However, in between root and unroot attempts, I upgraded my partition to Windows 8.1. Suddenly, when in fastboot, my HTC One shows up as "USB Device not Recognized," meaning I cannot issue any commands using ADB. If I don't get "waiting for device" I get "device offline," and my device is still rooted.
Whenever I uninstall Super SU, it's right back upon reboot.
I currently have S-ON. I am unable to get S-OFF because my computer doesn't recognize the phone when in fastboot. I tried updating and downloading different HTC Drivers to no avail.
I want to attempt to get my device back to its exact status when I bought the phone. Meaning, I want to have my bootloader as locked, keep S-ON (although I don't mind having S-OFF temporarily), and flash the stock RUU/Recovery. Upon Google Search, this seems easy, but there is not much out there for the GPE. A lot of the guides I have found are for Sense versions. My phone is not a GPE conversion. It is an actual GPE phone purchased on the Play Store.
Phone is functional, but I am concerned when 4.4 comes out, the update will fail or brick.
Sorry if this thread is long. I wanted to be as detailed as possible when asking for help. Thanks again to anyone on XDA who can assist.
mikhailov1 said:
Hello,
I seem to have gotten myself into a bind, and looking ahead to the 4.4 KitKat release, I am not sure how to get myself out of it. I've already done a lot of research and troubleshooting on my own, but can't seem to resolve the problem.
I purchased an HTC One Google Play edition, and decided to root to apply a quick fix with utilizing the Nexus 5 launcher. To that end, I unlocked my bootloader and rooted. I had a Windows 7 partition on my Mac at the time, but it was giving me trouble. Since the root, I became dissatisfied with the performance of the phone, and attempted to restore to factory.
I flashed stock recovery again, and relocked the bootloader. Now the bootloader shows as "relocked" and "tampered." However, in between root and unroot attempts, I upgraded my partition to Windows 8.1. Suddenly, when in fastboot, my HTC One shows up as "USB Device not Recognized," meaning I cannot issue any commands using ADB. If I don't get "waiting for device" I get "device offline," and my device is still rooted.
Whenever I uninstall Super SU, it's right back upon reboot.
I currently have S-ON. I am unable to get S-OFF because my computer doesn't recognize the phone when in fastboot. I tried updating and downloading different HTC Drivers to no avail.
I want to attempt to get my device back to its exact status when I bought the phone. Meaning, I want to have my bootloader as locked, keep S-ON (although I don't mind having S-OFF temporarily), and flash the stock RUU/Recovery. Upon Google Search, this seems easy, but there is not much out there for the GPE. A lot of the guides I have found are for Sense versions. My phone is not a GPE conversion. It is an actual GPE phone purchased on the Play Store.
Phone is functional, but I am concerned when 4.4 comes out, the update will fail or brick.
Sorry if this thread is long. I wanted to be as detailed as possible when asking for help. Thanks again to anyone on XDA who can assist.
Click to expand...
Click to collapse
try this http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers
it worked for some users
Thanks. Will try when I get home. I was able to use my Win 7 computer at work to unlock the boot loader again, but I cannot get S Off. I ran rumrunner and it looked like it was working, but then said FATAL: download update. Is there no rumrunner for GPE?
Sent from my HTC One using Tapatalk
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
mikhailov1 said:
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
You got stock rom and stock recovery ryt... lock the bootloader and check for update
Prash8429 said:
You got stock rom and stock recovery ryt... lock the bootloader and check for update
Click to expand...
Click to collapse
Yeah I have stock rom and I removed TWRP and flashed stock recovery. Because I did two factory restores from bootloader, I'm assuming the stock recovery is working properly, but I'm a noob at this stuff so I could be wrong.
Going to relock the bootloader, remove SuperSU, and attempt the update when it hits. Hopefully it will work.
Thanks for your help! Since I'm a new member, how do I add to your thanks meter? Want to make sure you're properly....thanked.
mikhailov1 said:
Yeah I have stock rom and I removed TWRP and flashed stock recovery. Because I did two factory restores from bootloader, I'm assuming the stock recovery is working properly, but I'm a noob at this stuff so I could be wrong.
Going to relock the bootloader, remove SuperSU, and attempt the update when it hits. Hopefully it will work.
Thanks for your help! Since I'm a new member, how do I add to your thanks meter? Want to make sure you're properly....thanked.
Click to expand...
Click to collapse
you can still get OTA with a rooted phone, as long as you have stock recovery and flashed stock ruu.... tip if your having trouble with flashing ruu change the zip file name to something simple like ruu.zip worked for me.:good:
mikhailov1 said:
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Can you tell me if your bootloader was 1.54 or 1.55? I have been unable to get Windows 8.1 to recognize the 1.54 bootloader. It always says "device not recognized" If yours was 1.54.0000 I will try this fix. Thanks.
I am 1.54.
Sent from my Nexus 5 using Tapatalk
Thanks for this, helped me out alot
Sent from my HTC One using XDA Premium 4 mobile app
I have a Republic Wireless Moto x (XT1049) with an unlocked bootloader, and knowing how rare it is (literally 0 support on any thread/site/country), I'm still going to ask a few questions, maybe start a band of RWers with unlocked Moto Xs that will only survive by sticking together/cuddling for warmth.
Before anyone starts to disbelieve me, I do have an xt1049 (not confusing it) with an unlocked bootloader (not confusing it with simply being rooted). I achieved this by purchasing a $25 license for SunShine by the jcase crew, and it worked wonderfully for whoever is out there, looking to unlock you xt1049. Why did I want to fork out 25 bucks for this? I started to hate the grind with towelpieroot+xposed every time I turned my device on, plus things like Viper4Android (among others) don't work well with temp roots, plus no write protection off, which has its purposes.
So on to my questions, (1) are there any custom ROMs designed for XT1049? (Probably no, so before you tell me no, (1a) are there any that work with my model?)
(2) If no one knows 1 or 1a, theoretically, what would happen if I flashed a ROM, say, CM 11/12, onto my phone? Please, to avoid a clutter of responses that consist of "idk probs no," have some level of confidence before answering.
For the theorists, Republic has a bunch of republic things going on in the background for the plural wifis to work correctly, how would these services (wifi calling/stuff) be affected, but also how would more universal things (moto x line specifically, but universal across carriers)? I don't know a whole lot about carriers because I have a serious phobia of letter combinations like CDMA and LTE, but to help understanding the "universal things" I mentioned, looking at the CM11 download page, one ZIP file can be used to flash the XT1053, XT1056, XT1058, XT1060, XT1055, you get the point. OK you got me, to refine it down,(3) I'm just trying to get a complete understanding of what would happen without trying it. I might/probably/would try it some other day, I have a load of college on my plate so if I have to undo anything (another question: (4) would I be able to revert to republic stuff if I have the correct zip, or what would have to go wrong so that I wouldn't be able to get to my bootloader/recovery?) I don't pay my phone bill, and my pops would be pissed if he read this so that's why I might not want to test it, but if there is a way to return I will be ballsy anyway.
(5) A question that I've had for a while but I never needed it answered, bootloaders remain unlocked after an update, right? My old phone (RIP HTC design 4g ) lost support at 4.2 and I never updated it the entire time it was rooted/unlocked. My moto on the other hand has 4.4.4 coming out soon and yeah I don't know the answer to it. I think it's implied it stays unlocked, but no one ever says it directly...
Well, thanks if you made it this far! And I would link whatever I could but I am a new user to this site and I'm restricted, you can just look up Sunshine jcase if interested.
Hi, this is my first time posting on xda, so I apologize ahead of time if I don't do it correctly. I'm also very interested in what can be done with a Republic Wireless Moto X (2013) in order to update to 4.4.4 and still be able to use TowelPieRoot and Xposed. I also looked at the SunShine unlocker but have not tried it yet. I'm currently on 4.4.2 and I just go the update notification today for 4.4.4 (much later than my wife's phone, which does not have TowelPieRoot or Xposed). Just wondering if you had any success with updating and still remaining unlocked and able to use TowelPieRoot and Xposed. Thanks for any feedback!
Unlocked boot loader...
Today I unlocked the boot loader on my Republic Wireless XT1049, since they were trying to force me to upgrade to android 4.4.4 from 4.4.2, and I realized that running Sunshine on 4.4.2 would be my last opportunity for unlocking the boot loader, before upgrading. I haven't yet rooted or updated to 4.4.4. Have either of you upgraded to 4.4.4 android with an uplocked boot loader, and re-rooted? Is there anything different about root in 4.4.4 vs 4.4.2, if you have an unlocked boot loader? Would the "Rooting Unlocked Bootloader" instructions in this guide work in android 4.4.2 and/or 4.4.4? Or, would Sunshine SUInstaller make that unnecessary? (Hopefully SUInstaller would work in 4.4.4...)
I'm on 4.4.2 with an unlocked bootloader from when the china man was giving out unlock codes. Having my code guarantees that I can unlock my bootloader even after locking it again for an update. I'm not sure how Sunshine works but be careful before taking the 4.4.4. update and do lots of research before doing anything to your device.
To answer some questions:
CM11 and CM12 will flash fine. The problem you'll have is a loss of phone functionality. With Republic, their app is baked into their custom ROM. But you can use it like a tablet and get a feel for what lollipop will look like on our phone. Make sure you have a nandroid backup or you'll lose everything. CM11 requires a wipe before it will install and CM12 requires you have CM11 (at least it did the last I checked) so you'll want to make sure you have a backup so you can get your working RW ROM back. Otherwise you'll have to flash the Stock RW ROM and start from scratch.
I've done lots of digging and have been able to get the Republic app working on CM11 and CM12 but the functionality is still missing. My tweaks allow texts on CM11 but it's from the "hidden number" not the RW number and the formatting is messed up upon receiving a message. Calls don't work at all on either ROM.
I posted a thread in General with my instructions to get the app working. I'm hoping someone with more ROM knowledge than myself can take a look at the RW Stock ROM and see what else needs to be moved into a CM ROM to give us functionality. I tried moving everything over and skipping duplicates and now I've seriously messed my phone up and will likely have to relock, unlock, flash TWRP and hope I can restore from my TWRP backup.
I've only tried CM11 and CM12, I have no idea how another ROM will affect our phone. Chances are you'll end up in an endless boot after flashing. You could brick the phone though, or end up in a situation like I'm currently in.
bstevens23 said:
I'm on 4.4.2 with an unlocked bootloader from when the china man was giving out unlock codes. Having my code guarantees that I can unlock my bootloader even after locking it again for an update. I'm not sure how Sunshine works but be careful before taking the 4.4.4. update and do lots of research before doing anything to your device.
Click to expand...
Click to collapse
Thanks for the warning about upgrading. I still haven't decided to allow my phone to upgrade to 4.4.4 android, but the most immediate issue I face with not upgrading is that my phone automatically downloaded the update, and now it is incessantly prompting me to install it. I have found any way to stop the annoying prompting. I would rather wait before updating, because there are always details you don't know about such upgrades, and I have no pressing need for the upgrade, except that ultimately I would like to be able to root my phone, also allow for writing to the system partition, so that recording calls would be possible.
You raise a good point in mentioning your capability to lock and unlock the boot loader. As far as I know Sunshine only unlocks the boot loader. I haven't seen that it provides any code or other means for re-locking it. It is also my understanding that technically there are 3 possible locking states of the boot loader. The factory state not only being locked but also indicating that it was never unlocked. It's my understanding that once a boot loader is unlocked, it can be re-locked, but never restored to the factory locked state that indicates it was never unlocked. That said, I don't know whether it matters if the boot loader is unlocked when running the Republic Wireless upgrade. In other threads I had read claims that once a boot loader is unlocked, that it should remain unlocked after OS upgrades, and as such, in a state that would allow for rooting. But, I am far from an expert on that.
bstevens23 said:
To answer some questions:
CM11 and CM12 will flash fine. The problem you'll have is a loss of phone functionality. With Republic, their app is baked into their custom ROM. But you can use it like a tablet and get a feel for what lollipop will look like on our phone. Make sure you have a nandroid backup or you'll lose everything. CM11 requires a wipe before it will install and CM12 requires you have CM11 (at least it did the last I checked) so you'll want to make sure you have a backup so you can get your working RW ROM back. Otherwise you'll have to flash the Stock RW ROM and start from scratch.
I've done lots of digging and have been able to get the Republic app working on CM11 and CM12 but the functionality is still missing. My tweaks allow texts on CM11 but it's from the "hidden number" not the RW number and the formatting is messed up upon receiving a message. Calls don't work at all on either ROM.
I posted a thread in General with my instructions to get the app working. I'm hoping someone with more ROM knowledge than myself can take a look at the RW Stock ROM and see what else needs to be moved into a CM ROM to give us functionality. I tried moving everything over and skipping duplicates and now I've seriously messed my phone up and will likely have to relock, unlock, flash TWRP and hope I can restore from my TWRP backup.
I've only tried CM11 and CM12, I have no idea how another ROM will affect our phone. Chances are you'll end up in an endless boot after flashing. You could brick the phone though, or end up in a situation like I'm currently in.
Click to expand...
Click to collapse
I hope there will be others who are willing to collaborate in your endeavors to reverse engineer the ROM that you are working on. Are you pursuing that because nobody has been able to root a Republic Wireless XT1049 on android 4.4.2 with a ROM? It seems that the original poster found some way to root 4.4.2 with his unlocked boot loader. I would be interest to know how he did that.
gxdaspark said:
Thanks for the warning about upgrading. I still haven't decided to allow my phone to upgrade to 4.4.4 android, but the most immediate issue I face with not upgrading is that my phone automatically downloaded the update, and now it is incessantly prompting me to install it. I have found any way to stop the annoying prompting. I would rather wait before updating, because there are always details you don't know about such upgrades, and I have no pressing need for the upgrade, except that ultimately I would like to be able to root my phone, also allow for writing to the system partition, so that recording calls would be possible.
You raise a good point in mentioning your capability to lock and unlock the boot loader. As far as I know Sunshine only unlocks the boot loader. I haven't seen that it provides any code or other means for re-locking it. It is also my understanding that technically there are 3 possible locking states of the boot loader. The factory state not only being locked but also indicating that it was never unlocked. It's my understanding that once a boot loader is unlocked, it can be re-locked, but never restored to the factory locked state that indicates it was never unlocked. That said, I don't know whether it matters if the boot loader is unlocked when running the Republic Wireless upgrade. In other threads I had read claims that once a boot loader is unlocked, that it should remain unlocked after OS upgrades, and as such, in a state that would allow for rooting. But, I am far from an expert on that.
Click to expand...
Click to collapse
I have yet to update to 4.4.4 because I've heard of people having problems with Messenger after the update. I'm waiting to see how my wife's phone functions on it before I make the leap and get the stock recovery back to take the OTA. Until then, I get the obnoxious update warning constantly as well. I could probably freeze the app with Titanium, we'll see if it bothers me enough in the next few days. I'm not sure if the bootloader will need to change for the update as I've only ever had 4.4.2 since I was bootloader unlocked. I know flashing the stock recovery is needed and I feel like that may require a relocked bootloader. As far as I know, from a software/OTA side at least, relocked and locked are equal. Republic/Moto would care about relocked but I don't think the system throws any flags for taking stock software updates because of it.
I hope there will be others who are willing to collaborate in your endeavors to reverse engineer the ROM that you are working on. Are you pursuing that because nobody has been able to root a Republic Wireless XT1049 on android 4.4.2 with a ROM? It seems that the original poster found some way to root 4.4.2 with his unlocked boot loader. I would be interest to know how he did that.
Click to expand...
Click to collapse
I'm pursuing this because I want CM12 to test out Lollipop since I have no idea when Republic is going to push it out to us. I haven't heard of Sprint getting soak tests yet and we're typically 2-3 months behind Sprint. Waiting until May when Google I/O takes place will be difficult for me, especially if they break their current trend and announce the next version of Android.
My goal is much more ambitious than just CM12 though. I got the Republic app to recognize CM11 as native, meaning if someone can figure out which radio portions I'm missing and get the phone functioning as if it were the Republic ROM, we would not be restricted to just the stock ROM/software anymore. I've been an Android user for a few years now and I've always had the ability to flash whatever I wanted if it was available for my device. Since joining RW, I'm extremely restricted. I have 1 ROM option, which is only helpful because it allows Xposed. But I no longer have the ability to test the newest version of Android whenever I please, or to give a custom ROM a spin if I feel like it. If we can figure out what makes the RW ROM function properly, that wouldn't be a restriction anymore. That's my goal.
Unfortunately, I have no idea what I'm doing. The best I can do is compare files and try pulling random things. I'm hoping someone with more ROM knowledge will be able to take a look at the RW ROM and see which pieces I'm missing. I feel like CM12 is going to be a bit more complicated though, and might not be possible at this time. We'll see though. I know something is getting screwed up with the MEID because the Republic app doesn't recognize an MEID at all. How to go about fixing that? Beyond me.
step-by-step, 4.4.4 root
I think the steps would be: first Sunshine, then 4.4.4 OTA, then root, then Xposed. Is that correct? After I unlock with Sunshine, will my phone still prompt me to update to 4.4.4? Or do I need to need to download 4.4.4 and then flash it? After Sunshine, do I FIRST need to flash 4.4.2 custom recovery? If so, where can I get that? I should probably get a copy of that anyway, even if I don't need it now.
It seems pretty easy overall, but I think I need to refer to a step-by-step guide to make sure I do all of this correctly. If I start the guide below, can you please be so kind as to make corrections for me? Add, remove, or change steps? Thanks!!! Here it goes, this is my best guess at the steps I need to take:
1. Go to theroot.ninja and complete the unlock process.
2. Download and install Android SDK on PC (installer_r24.1.2-windows.exe).
3. Download and install Motorola Device Manager on PC.
4. Get mfastboot.exe and place it in the same directory as fastboot (fastboot is in the \sdk\platform-tools subdirectory of the Android SDK).
***Do I just drag this .exe to the said folder on my PC?***
5. Get the TWRP for Moto X 4.4 custom recovery for kit kat and place it in the same directory as fastboot.
6. Enable USB debugging and download SuperSU
7. Double check to make sure USB debugging has been enabled. Put your unlocked Moto X into bootloader mode by pressing the Volume Down button and then the Power button. Hold for about 3 seconds and release and you should be in bootloader mode. Connect your Moto X to your PC via a USB cable.
8. Open a command prompt on your PC and change directory to the folder where mfastboot.exe is.
9. At the command prompt type: mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img to flash the custom recovery to your Moto X.
***Is this the version of TWRP I need to root 4.4.2? What about 4.4.4? Or do I just flash the 4.4.4 OTA on top of 4.4.2?***
10. After the custom recovery has been flashed to your Moto X, at the command prompt type: fastboot reboot-bootloader to reboot into the bootloader.
11. Unplug your device from your PC. Then get into recovery mode by pressing the Volume Down button to highlight recovery mode and pressing the Volume Up button to select the recovery mode.
12. You should now have booted into the Team Win Recovery Project custom recovery. Click on Install to install SuperSu. Scroll down to find the sdcard and select it. Then scroll down to download and select it. Select the SuperSU zip file and swipe to install.
*** I also saw this:
"For new users who have only unlocked their bootloaders, flashed TWRP and rooted, then only make use of apps like RootExplorer, QuickBoot(reboot), Adfree, Wifi Tether for Root, etc.. that do NOT modify /System, the easiest way to take the OTA is to...
download the SBF/FXZ for your carrier and the Software Version currently on your phone. Do NOT use a lower Software Version, or the SBF/FXZ for another carrier or you will risk bricking your phone!!!
unzip it.
boot the phone into fastbootAP/bootloader mode
use mfastboot to flash the recovery.img to your phone - mfastboot flash recovery recovery.img
immediately reboot into fastbootAP/bootloader - mfastboot reboot-bootloader
select recovery.
once you've entered stock recovery, you can reboot back into normal system.
take the OTA when it gets to your phone.
you will likely remain rooted, and its optional to flash your custom recovery back on there via mFastboot
However, if you are running Xposed, did a wifi tethering hack, edited build.prop, DELETED bloat from your phone, your phone will fail the OTA Update's validation checks and it will fail. In that case, you can boot back into fasbootAP/Bootloader mode, use mfastboot to flash system.img (mfastboot flash system.img ) from the SBF/FXZ you already downloaded and unzipped. then reboot ( mfastboot reboot ), and try the OTA again. You will need to re-root by flashing custom recovery (like twrp), and re-install SuperSU."
***Is there any way to break down the whole thing into simpler steps???*** THANKS!!!
PackerDroid said:
I think the steps would be: first Sunshine, then 4.4.4 OTA, then root, then Xposed. Is that correct? After I unlock with Sunshine, will my phone still prompt me to update to 4.4.4? Or do I need to need to download 4.4.4 and then flash it? After Sunshine, do I FIRST need to flash 4.4.2 custom recovery? If so, where can I get that? I should probably get a copy of that anyway, even if I don't need it now.
It seems pretty easy overall, but I think I need to refer to a step-by-step guide to make sure I do all of this correctly. If I start the guide below, can you please be so kind as to make corrections for me? Add, remove, or change steps? Thanks!!! Here it goes, this is my best guess at the steps I need to take:
1. Go to theroot.ninja and complete the unlock process.
2. Download and install Android SDK on PC (installer_r24.1.2-windows.exe).
3. Download and install Motorola Device Manager on PC.
4. Get mfastboot.exe and place it in the same directory as fastboot (fastboot is in the \sdk\platform-tools subdirectory of the Android SDK).
***Do I just drag this .exe to the said folder on my PC?***
5. Get the TWRP for Moto X 4.4 custom recovery for kit kat and place it in the same directory as fastboot.
6. Enable USB debugging and download SuperSU
7. Double check to make sure USB debugging has been enabled. Put your unlocked Moto X into bootloader mode by pressing the Volume Down button and then the Power button. Hold for about 3 seconds and release and you should be in bootloader mode. Connect your Moto X to your PC via a USB cable.
8. Open a command prompt on your PC and change directory to the folder where mfastboot.exe is.
9. At the command prompt type: mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img to flash the custom recovery to your Moto X.
***Is this the version of TWRP I need to root 4.4.2? What about 4.4.4? Or do I just flash the 4.4.4 OTA on top of 4.4.2?***
10. After the custom recovery has been flashed to your Moto X, at the command prompt type: fastboot reboot-bootloader to reboot into the bootloader.
11. Unplug your device from your PC. Then get into recovery mode by pressing the Volume Down button to highlight recovery mode and pressing the Volume Up button to select the recovery mode.
12. You should now have booted into the Team Win Recovery Project custom recovery. Click on Install to install SuperSu. Scroll down to find the sdcard and select it. Then scroll down to download and select it. Select the SuperSU zip file and swipe to install.
*** I also saw this:
"For new users who have only unlocked their bootloaders, flashed TWRP and rooted, then only make use of apps like RootExplorer, QuickBoot(reboot), Adfree, Wifi Tether for Root, etc.. that do NOT modify /System, the easiest way to take the OTA is to...
download the SBF/FXZ for your carrier and the Software Version currently on your phone. Do NOT use a lower Software Version, or the SBF/FXZ for another carrier or you will risk bricking your phone!!!
unzip it.
boot the phone into fastbootAP/bootloader mode
use mfastboot to flash the recovery.img to your phone - mfastboot flash recovery recovery.img
immediately reboot into fastbootAP/bootloader - mfastboot reboot-bootloader
select recovery.
once you've entered stock recovery, you can reboot back into normal system.
take the OTA when it gets to your phone.
you will likely remain rooted, and its optional to flash your custom recovery back on there via mFastboot
However, if you are running Xposed, did a wifi tethering hack, edited build.prop, DELETED bloat from your phone, your phone will fail the OTA Update's validation checks and it will fail. In that case, you can boot back into fasbootAP/Bootloader mode, use mfastboot to flash system.img (mfastboot flash system.img ) from the SBF/FXZ you already downloaded and unzipped. then reboot ( mfastboot reboot ), and try the OTA again. You will need to re-root by flashing custom recovery (like twrp), and re-install SuperSU."
***Is there any way to break down the whole thing into simpler steps???*** THANKS!!!
Click to expand...
Click to collapse
Were you able to break this down into simpler steps? Did the steps work for you?