I would say my convert to GPe is perfect. I have found some issues. First, when i drop the audio folder to the root of the "sdcard" it goes like this: root_of_SD/audio/ringtones and root_of_SD/audio/alarms root_of_SD/audio/notifications and i used it this way on stock nexus devices, CM 10.1 nexus and non nexus devices and a completely stock HTC one and it worked after reboot, the tones were available for selection. It doesnt work on this GPe. Second is if i have confirmed root, using android terminal emulator and doing an su to root and accepting the super user screen to always accept, i type "reboot" and it says not allowed or something to that affect, i installed a root app i have used before called reboot control, gave it always allow root, hit reboot or shutdown and it never does anything. Am i crazy?
bump. Anyone?
Someone throw me a bone. Does this happen to anyone else?
Sent from my HTC One using Tapatalk 4 Beta
jasunto said:
Someone throw me a bone. Does this happen to anyone else?
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
I have been running the conversion for weeks and and I have not experienced any of this.
I may have to titanium my apps and run the RUU again. This is killing me. Also USB otg is fine. But with paragon app for ntfs it does not work.
Sent from my HTC One using Tapatalk 4 Beta
Fixed permissions via recovery. Still nothing. Checked permissions on reboot in system bin and they are sqq. Tries busy box smart install vs normal. No luck. Busybox reboot no worky either.
Sent from my HTC One using Tapatalk 4 Beta
Reflashed RUU same issues.
Sent from my HTC One using Tapatalk 4 Beta
Related
First connect to WiFi and make sure you can access the web.
Next put the N4 into airplane mode.
Then go to Settings > Apps > All > Google Services Framework > Clear data
Take the N4 out of airplane mode and let it connect to WiFi.
After a few minutes, you will be prompted to install the OTA update.
If you are not prompted within 10 minutes, open the dialer and force a "checkin" by typing: *#*#2432546#*#*
After "checkin succeded" message, you should be prompted to install the update.
Enjoy!
Doesn't work for me.
Sent from my Nexus 4 using Tapatalk 2
You have to be standing in the bathroom for it to work.
No. But for real. Updates are pushed out in waves. If your device is not on the current wave you will not get the update. That's it.
Don't want to wait. Do it manually.
albundy2010 said:
You have to be standing in the bathroom for it to work.
No. But for real. Updates are pushed out in waves. If your device is not on the current wave you will not get the update. That's it.
Don't want to wait. Do it manually.
Click to expand...
Click to collapse
http://www.androidpolice.com/2012/11/27/manual-download-android-4-2-1-update-jop40d-for-the-nexus-4/
This is the easy way reboot to cwm and flash done
Sent from my Nexus 4 using xda premium
bline007 said:
This is the easy way reboot to cwm and flash done
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
"Easy" is a relative term. Not everyone here, especially in the "General" forum is comfortable yet with flashing alternative recoveries or using abd, etc. This is meant for the novice and/or purist who does not want to alter the phone in order to receive and apply the update. This method does in fact work. Quite often the device is ready to receive the update, but the built in automatic & manual checkin fails to trigger the process. Clearing the GSF data forces the device to initiate it almost immediately, as opposed to waiting an undetermined amount of time for the device to resolve the issue on its own.
My advice to the audience who this is intended for: If this did not work for you now, try it again in a few hours or tomorrow, I assure you it will be much faster than waiting for it to happen naturally. In fact, to prove my point further, go ahead and try the manual checkin (under settings > about phone > system updates) first, each time, before you try this. You'll eventually see what I mean. FYI - Every Nexus device has behaved this way.
How come I can't get the update to install either in CWM or from OTA?? If I do OTA the phone reboots into CWM and I get an "assert failed" and installation aborted.... And if I manually go into CWM and "update from SD card" option I get the same issue!
Sent from my Nexus 4 using xda premium
Girn said:
How come I can't get the update to install either in CWM or from OTA?? If I do OTA the phone reboots into CWM and I get an "assert failed" and installation aborted.... And if I manually go into CWM and "update from SD card" option I get the same issue!
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
If you changed your build.prop it will fail. U need to have stock build.prop.
I see your point skillllz
Sent from my Nexus 4 using xda premium
I have a stock build prop.. All I've done is Root and cwm
Sent from my Nexus 4 using xda premium
Girn said:
I have a stock build prop.. All I've done is Root and cwm
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Try wiping cache and dalvik then flash. It worked first time for me. Some custom Roms change build prop. I'm on stock rom
Sent from my Nexus 4 using xda premium
Thanks! Worked perfectly (on 1st try) to get 4.2.0 on my Galaxy Nexus finally.
Still doesn't work and I did a factory reset just now.. Get assert failed something about genie widget.odex then all these numbers and the file name then installation failed status 7
Sent from my Nexus 4 using xda premium
Worked here. Thanks.
Sent from my Nexus 4 using xda app-developers app
Girn said:
Still doesn't work and I did a factory reset just now.. Get assert failed something about genie widget.odex then all these numbers and the file name then installation failed status 7
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
That means you removed genie widget.odex . put the file back or any other that you deleted and it will go through. I deleted currents, books, earth, genie, videos and a few more and it failed on the update and its because you have to have the same build prop or same apps back
Sent from my Nexus 4
worked a charm for me! thanks
Don't work for me
Worked. Thanks.
Sent from my Nexus 4 using xda app-developers app
You only need to clear data of google services framework, then check for updates. Rinse and repeat until it works - usually 1-5 times.
All those other steps aren't necessary.
bline007 said:
If you changed your build.prop it will fail. U need to have stock build.prop.
Click to expand...
Click to collapse
For those who have altered build.prop, any way to fix beside completely going back to the original Google ROM img?
Worked for me thanks.
As I have CWM, CWM asked if I want to flash untrusted update - I said yes. After isntall, I rebooted back to Recovery (as it said something about restoring stock recovery while installing update). CWM was still there. I told CWM to reboot and it said 'you may have lost root'. I selected yes to fix root and it rebooted. all seems fine now.
Worked nicely!! Thanks
In the course of switching the recovery to TWRP, I came across this error when I selected Fastboot while in HBoot. It doesn't seem to impact anything, but nonetheless I'm wondering if I should be concerned.
What exactly is PH39img.zip and why is Fastboot scanning for it?
Sent from my Nexus 10 using Tapatalk HD
Its the name of the update package that comes from HTC...
Hboot automatically runs it...
It searches for it when you boot to hboot...
No worries
Sent from my Vivid 4G using Tapatalk 2
Cool. Thanks. So did unlocking the phone delete it? Cause I know I didn't.
Sent from my Nexus 10 using Tapatalk HD
No... there wasn't one on there...
Those zip files are part of the upgrading android process
Sent from my Vivid 4G using Tapatalk 2
Just looking to see if anyone else got this issue.
Tried live usb, live cd, and hdd install of ubuntu 32 bit 12.04.
Tried different roms and made sure fastboot was off, debugging check on and no lock code.
It will reboot to bootloader but the ADB part fails.
Any ideas?
Sent from my HTC ONE using xda premium
I had the same problem and this worked for me, might not for you. My problem is caused by easy tether client installed on my laptop so when I plug in my phone I have to do this
1. Turn off development settings
2. Turn it back on
3. Check the use debugging box
4. Run adb from command prompt
My laptop runs windows 7 BTW
Sent from my HTCONE using Tapatalk 4 Beta
Also just so you know you have to run ADB as root or else you'll get a device not connected message
Sent from my HTC One running ViperROM v1.1.0
FrozenRiff said:
I had the same problem and this worked for me, might not for you. My problem is caused by easy tether client installed on my laptop so when I plug in my phone I have to do this
1. Turn off development settings
2. Turn it back on
3. Check the use debugging box
4. Run adb from command prompt
My laptop runs windows 7 BTW
Sent from my HTCONE using Tapatalk 4 Beta
Click to expand...
Click to collapse
Tried that. Still didn't work.
benmatlock said:
Also just so you know you have to run ADB as root or else you'll get a device not connected message
Sent from my HTC One running ViperROM v1.1.0
Click to expand...
Click to collapse
I did the sudo before the command and put in my password.
Sent from my HTCONE using xda premium
You should try the other method that's not moonshine. Forgot what bits called but that's what I used and it worked flawlessly
Sent from my HTCONE using Tapatalk 4 Beta
FrozenRiff said:
You should try the other method that's not moonshine. Forgot what bits called but that's what I used and it worked flawlessly
Sent from my HTCONE using Tapatalk 4 Beta
Click to expand...
Click to collapse
YEPPERS, this one worked in about 3 min.. just easy as can be
http://forum.xda-developers.com/showthread.php?t=2314703
Doesnt it break hot reboot?
Sent from my HTCONE using xda premium
eyeisdasteve said:
Doesnt it break hot reboot?
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
I don't know what hot reboot is but if it's something with adb reboot then probably yes
Sent from my HTCONE using Tapatalk 4 Beta
eyeisdasteve said:
Doesnt it break hot reboot?
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
With the other method it does break hot reboot, I don't use it so it doesn't matter to me, also the method can be done right from terminal emulator, just follow the same command but instead of typing just revone you need to type revone.bin
Sent from my HTCONE using xda premium
josh030181 said:
With the other method it does break hot reboot, I don't use it so it doesn't matter to me, also the method can be done right from terminal emulator, just follow the same command but instead of typing just revone you need to type revone.bin
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
I sometimes like hot reboot. But I can wait the extra seconds for the whole phone to boot.
Sent from my HTCONE using xda premium
So, came to the conclusion that my laptop does not like ubuntu for some reason. It will not recognize my device in ubuntu but is fine in windows.
I'm gonna try a live cd on my buddies laptop.
If I get it to recognize my phone, I'm gonna moonshine over revone. :thumbup:
Sent from my HTCONE using xda premium
eyeisdasteve said:
So, came to the conclusion that my laptop does not like ubuntu for some reason. It will not recognize my device in ubuntu but is fine in windows.
I'm gonna try a live cd on my buddies laptop.
If I get it to recognize my phone, I'm gonna moonshine over revone. :thumbup:
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
You can always do revone first then moonshine afterwards, OMJ confirmed that works
Sent from my HTCONE using Tapatalk 4 Beta
FrozenRiff said:
You can always do revone first then moonshine afterwards, OMJ confirmed that works
Sent from my HTCONE using Tapatalk 4 Beta
Click to expand...
Click to collapse
Did the revone. Now just gonna do moonshine on my buddy's laptop.
I'll see what happens.
Sent from my HTCONE using xda premium
eyeisdasteve said:
Did the revone. Now just gonna do moonshine on my buddy's laptop.
I'll see what happens.
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
My initial problem with device and moonshine was resolved by flashing stock rooted Rom, then everything worked fine. Completed and restored from backup. Think the issue with phone being seen and flashing was noted on the site somewhere that stock kernel was recommended or required.
Sent from Taptalk on HTC One on some awesome custom Rom!
avwheeler said:
My initial problem with device and moonshine was resolved by flashing stock rooted Rom, then everything worked fine. Completed and restored from backup. Think the issue with phone being seen and flashing was noted on the site somewhere that stock kernel was recommended or required.
Sent from Taptalk on HTC One on some awesome custom Rom!
Click to expand...
Click to collapse
I tried 3 different roms and even stock.
Nothing was working for me. But in ubuntu if I ran 'lsusb' my device doesn't even pop up. It won't recognize that it's there.
Sent from my HTCONE using xda premium
eyeisdasteve said:
I tried 3 different roms and even stock.
Nothing was working for me. But in ubuntu if I ran 'lsusb' my device doesn't even pop up. It won't recognize that it's there.
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
I used the newest live cd 13 I think, the more stable and without all media crop version had bad wife drivers for me. I downloaded file, copied over only adb and fastboot to folder, though they would not see device, also don't think needed, then continued. Made sure debugging was turned on, also updated to latest. 35 supersu (don't think this had anything to do with it) only other difference would be computer hardware. It pissed me off for a while until I loaded vipers stock deodexed.
Good luck :sly:
Sent from Taptalk on HTC One on some awesome custom Rom!
I was getting the same ADP error. I talked to support on IRC, they said viper 1.1.0 is not supported for moonshine. Suggested doing RUU to go back to stock. In which case you would have to nandroid your rom, backup contents to computer. Relock phone, RUU, unlock phone again, moonshine, flash recovery, restore nandroid. I might wait till next release of viper rom to s-off.
Sim-X said:
I was getting the same ADP error. I talked to support on IRC, they said viper 1.1.0 is not supported for moonshine. Suggested doing RUU to go back to stock. In which case you would have to nandroid your rom, backup contents to computer. Relock phone, RUU, unlock phone again, moonshine, flash recovery, restore nandroid. I might wait till next release of viper rom to s-off.
Click to expand...
Click to collapse
I DID MINE WITH MACKS ROM, IF YOU HAVE A STOCK ROM NANDROID JUST RESTORE IT AND TRY AGAIN.watch your downloads on moonshine so you get the right firmware version for your rom, they were reversed fuses was notified, he might have changed it by now but check for sure anyway.
Aldo101t said:
I DID MINE WITH MACKS ROM, IF YOU HAVE A STOCK ROM NANDROID JUST RESTORE IT AND TRY AGAIN.watch your downloads on moonshine so you get the right firmware version for your rom, they were reversed fuses was notified, he might have changed it by now but check for sure anyway.
Click to expand...
Click to collapse
yea I did notice that that I did download the right one but again not working on VIPER at least for me. I got tired of messing with it, gonna do it a different time.
Sim-X said:
yea I did notice that that I did download the right one but again not working on VIPER at least for me. I got tired of messing with it, gonna do it a different time.
Click to expand...
Click to collapse
don't know if this makes a difference or not. did you plug your phone in before or after you had ubuntu booted.i would try after it's booted up.
So I think I'm in trouble.
I guess I must have downloaded the 9/6 nightly RIGHT before they fixed the boot animation bug, so it won't boot, I don't have any other nightly zips on my phone, my computer won't recognize my device so I can't put another one on it. I've been looking up solutions and I'm seeing this stuff about ADB transfers but it says you have to enable USB de-bugging and I don't think I did before and I can't do it now. I'm a noob, but I can follow directions (lol), anybody got another way to file transfer? Or just maybe get my computer to recognize my phone?
Thanks in advance...I'm probably going to stop tinkering if/once this is back to normal.
Restore your backup
Sent from my GT-N5110 using Tapatalk 4
Can you enter the recovery mode ?
sent from my m7spr using tapatalk 4
I got it y'all...thanks anyway
9/7 is the same haha
Sent from my One using XDA Premium HD app
I've used Titanium to uninstall a ton of the Sprint crap. But as soon as I reboot it redownloads everything.... How do we get around this?
thenags said:
I've used Titanium to uninstall a ton of the Sprint crap. But as soon as I reboot it redownloads everything.... How do we get around this?
Click to expand...
Click to collapse
Educated guess because it happens to me too, I would uncheck restore apps in the backup settings. Believe that the system thinks that the apps need to be reinstalled because they were backed up prior to you removing them.
If you still have SprintID installed you can go in there and delete the Sprint pack it removes most of the Sprint bloat
Sent from my 831C using Tapatalk
thenags said:
I've used Titanium to uninstall a ton of the Sprint crap. But as soon as I reboot it redownloads everything.... How do we get around this?
Click to expand...
Click to collapse
I did the same thing first night I got the phone. I would uninstall tons of crap apps and they all come back. The stock rom is secured and has system write protection enabled. The easiest way around this is to first s-off which you should anyway if your going to root. Next flash a custom rom or if you wanna stick with stock (I actually am staying stock for now to give the custom roms time to mature) then flash Captain Throw backs version over at themikmik. It's comes rooted out of the box and if you s-off you won't have any issues getting rid of bloat apps. Mine is squeaky clean. I couldn't believe how much crap they loaded it with. No issues with them coming back. If you stay s-on you need to flash a kernel patch which I did before s-off was available but I wouldn't recommend doing that.
Sent from my HTC One M8 using XDA Premium 4 mobile app
I am s-off and rooted. I used titanium to remove everything that's coming back. Captain has a ROM out?
Sent from my 831C using Tapatalk
Found it. Downloading now
Sent from my 831C using Tapatalk
Damn. That didn't do it. Did a 100% clean install. Used Titanium to remove a ton of apps. Rebooted and they all reinstalled. Can't wait for someone to get GPE on this thing
Sent from my 831C using Tapatalk
thenags said:
Damn. That didn't do it. Did a 100% clean install. Used Titanium to remove a ton of apps. Rebooted and they all reinstalled. Can't wait for someone to get GPE on this thing
Sent from my 831C using Tapatalk
Click to expand...
Click to collapse
Did you apply the latest firmware before flashing? Here is the version I am using
http://themikmik.com/showthread.php?16276-SPRINT-ROM-M8WHL-Stock-Rooted-Base-1-54-651-8
Firmware
http://themikmik.com/showthread.php...WHL-Firmware-Collection-LATEST-1-54-651-8-OTA
I applied my firmware via OTA update but it shouldn't matter. Something is up because it should work just fine.
Sent from my HTC One M8 using XDA Premium 4 mobile app
I did. Took the phone out of the box. Did every update available. Rooted. Then realized I couldn't uninstall the stuff. Then flashed Captains. Then tried again. And no I'm here lol
Sent from my 831C using Tapatalk