I have an HTC One S, rooted and unlocked. I downloaded CM10, attempted to update to it, yes without wiping(my fail) and sent the phone into a bootloop. In my attempts to fix I lost the ability mount the SDCard.
I did this to fix the SDCard and it worked - http://forum.xda-developers.com/showthread.php?t=1630459&page=12
I have tried to do the RUU update to bring it back to stock but it failed with error 171, USB Connectivity lost so I abandoned that idea. I did play with drivers, HTC Sync, reinstalls and registry cleanups all to no avail. This is the process I wanted to follow but no luck.....http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html
When updating with CM10 it installed VERY quick, like 20ish seconds. This seemed very fast so I thought maybe a different ROM would work and I went with Dark Jelly http://forum.xda-developers.com/showthread.php?t=1848100
No matter what I do I am stuck in the bootloop. Looking for any guidance available of things to try. I have searched all over and tried the solutions that make sense but to no avail.
Fixed
So I did this: http://forum.xda-developers.com/showpost.php?p=33857020&postcount=2181
delete that file and it booted right up. Have not looked at the Dark Jelly rom to see fi it has that file too but that may have been the issue with the other ROM as well.
Summary - CM10 contains that file that needs to be deleted before upgrading if you have hboot of low versions...I know, not very descriptive but its all in my posts above.
nvm, you got it.
Related
Hi all,
I decided to install the InsertCoin 4.4.0 Custom ROM, apparently I needed to update my firmware with a link provided. While in the Revolutionary Bootloader I instantly got a message asking wether I wanted to update (I assumed that was the firmware). The update apparently went OK and I got a message 'Press <POWER> to reboot.
However, when pressing the Power button the device reboots, but after the Quietly Brilliant screen the device constantly reboots again, resulting in a loop. When going in to the Revolutionary Bootloader I get the same update message.
So, updates seem to go okay, but I can't get my device started again. Hopefully this is fixable, but unfortunately I'm still not that familiar with software like this.
Thanks in advance!
I am having the same issue after updating firmware..help guys!
By removing the SD Card, Booting into Recovery I can get in the recovery menu. Then by putting the SD card back in and mounting it I can restore the device using the backup I created just before I updated. But that apparently doesn't solve the problem, it still crashes after the Quietly Brilliant screen.
download new 4.4.0 and flash
Apparently I need to install the firmware update first. I'm not sure if installing 4.4.0 is a smart idea now that it seems the firmware update failed.
Ok i found the fix..just remove the firmware file from the SD card by deleting and install the new ROM thru recovery...but first do a super wipe..and then install the new ICS rom..that will fix everything. Given you didnt restore ur device..do this after updating the firmware..
Thanks. I managed to fix it and have installed IC 4.4.0. Didn't install the firmware update though, but it seems to work fine. Apart from the fact that all data on my SD card is not recognized. But that's not really related to this topic anymore.
Breznikov said:
Thanks. I managed to fix it and have installed IC 4.4.0. Didn't install the firmware update though, but it seems to work fine. Apart from the fact that all data on my SD card is not recognized. But that's not really related to this topic anymore.
Click to expand...
Click to collapse
Download the 3.24 firmware, place it on the root of your SD card, boot into bootloader and update. After update has finished, press power to reboot, do a battery pull, put the SD card into your computer and delete the PMG15 zip, put the SD card back in your phone, boot into bootloader, select recovery, flash ROM, enjoy.
Sent from my HTC Sensation 4G using XDA App
Thanks, but I don't have a PMG15 file on the SD card after installing the Firmware. I ran Super Wipe, rebooted in Bootloader, let the installer install the PG58IMG file (after checking the MD5 sums). Basically did exactly as you said, but I can't find a PMG15 zipfile to delete.
I don't even care anymore if I manage to get IC 4.4.0 installed (also tried, ARHD 6.1.0, doesn't work either), I just want my phone to work again.
EDIT: Regarding the firmware, I'm not sure what CID I have, I haven't installed SuperCID yet, and I can't install it now because I can't boot up the device, which is necessary to get SuperCID.
Breznikov said:
Thanks, but I don't have a PMG15 file on the SD card after installing the Firmware. I ran Super Wipe, rebooted in Bootloader, let the installer install the PG58IMG file (after checking the MD5 sums). Basically did exactly as you said, but I can't find a PMG15 zipfile to delete.
I don't even care anymore if I manage to get IC 4.4.0 installed (also tried, ARHD 6.1.0, doesn't work either), I just want my phone to work again.
Click to expand...
Click to collapse
It's not PMG15, its PG58IMG....sorry I couldn't remember the exact name....but you should get what I'm saying right?
Sent from my HTC Sensation 4G using XDA App
Ah, yes. Well I did figure that out earlier, because if I keep the file it simply keeps updating in Bootloader. But it still doesn't get past the HTC splash screen when I try to start it up after installing a custom ROM. InsertCoin 4.4.0 shuts down right after 'Quietly Brilliant', ARHD 6.1.0 keeps rebooting at the plain HTC screen.
Thanks for the help so far, still giving me headaches though
EDIT: ARHD 6.1.0 now manages to get past the Quietly Brilliant screen and reboots as soon as the Beats logo flies in. It's progress, but it's still constantly crashing.
Hi All,
I'm probably one of the few here who is still using HoneyComb instead of ICS on my Xoom. I've been on 3.2.4 for some time now, and started getting the 3.2.6 update notification which I blew off until the other day when I said screw it, I'll update and go through the trouble of re-rooting, etc.
However, I attempted to use Solarnz's universal root method which I've used numerous times before and never had an issue with until now. So after pushing the recovery.img via Fastboot, everything appears to have been completed just fine, except when I reboot into recovery I get the damn android with an error.
I've tried pushing a few versions of recovery and each time it seems to work just fine, but again on reboot, I can't get into recovery like it never got pushed or somehow has been erased. I can even revert back to 3.2.2 and update to 3.2.4 and root and re-install clockwork no problem. But I keep getting that damn update notification every 5 mins, and I'm sick of it, hence why I bothered to update in the first place.
I know most people have by-passed this altogether by jumping to ICS, but I've had too many issues with the beta ICS versions out there (WIFI handoffs and disconnects mostly) and need to reliable daily driver vice ICS goodness (fortunately I have a GNex for that).
Anyway, since I hadn't seen much on this, I decided to post and see if its just me, or if this really is an issue?
I can probably go old skool and use the manual root method of pushing the SU files via ADB, but something isn't right here, and I wanted to get some feedback.
Thanks
DANOinSD said:
Hi All,
I'm probably one of the few here who is still using HoneyComb instead of ICS on my Xoom. I've been on 3.2.4 for some time now, and started getting the 3.2.6 update notification which I blew off until the other day when I said screw it, I'll update and go through the trouble of re-rooting, etc.
However, I attempted to use Solarnz's universal root method which I've used numerous times before and never had an issue with until now. So after pushing the recovery.img via Fastboot, everything appears to have been completed just fine, except when I reboot into recovery I get the damn android with an error.
I've tried pushing a few versions of recovery and each time it seems to work just fine, but again on reboot, I can't get into recovery like it never got pushed or somehow has been erased. I can even revert back to 3.2.2 and update to 3.2.4 and root and re-install clockwork no problem. But I keep getting that damn update notification every 5 mins, and I'm sick of it, hence why I bothered to update in the first place.
I know most people have by-passed this altogether by jumping to ICS, but I've had too many issues with the beta ICS versions out there (WIFI handoffs and disconnects mostly) and need to reliable daily driver vice ICS goodness (fortunately I have a GNex for that).
Anyway, since I hadn't seen much on this, I decided to post and see if its just me, or if this really is an issue?
I can probably go old skool and use the manual root method of pushing the SU files via ADB, but something isn't right here, and I wanted to get some feedback.
Thanks
Click to expand...
Click to collapse
Depending on what ROM your flashing if your trying to do the update from OTA then you have to have a 100% no bloatware removed rom, my suggestion is to download the one @ motodev and then flash 3.1 and update all the way to ICS (if wanted) otherwise I believe that when you get the (!) in recovery you can press once pwr+up fast (don't hold) and it will display the recovery window with the error message that's preventing you from upgrading.
after flashing the recovery, did you reboot into android and then into recovery? if yes, don't!
you have to reboot into recovery right after flashing the recovery.
Hi All,
Thanks for the feedback, I finally got recovery pushed and booted, along with root on 3.2.6.
As llama points out you must reboot into recovery upon rebooting from fastboot. I don’t believe this was a requirement previously. But once I did that, all was fine.
I’ve done this a thousand times before and even in my old notes I couldn’t find any reference to booting into recovery immediately after pushing the recovery.img. Is this something new with this update or has it always been this way? Call me crazy, but I can’t ever recall scrambling to catch the reboot and get into recovery before re-launching Android. I always rebooted in Android and made sure it actually loaded to ensure something didn’t get hosed, then I would reboot into recovery and flash the root zip.
DANOinSD said:
Is this something new with this update or has it always been this way?
Click to expand...
Click to collapse
as far as I know, this is a 'feature' introduced with every ota-update. To my knowledge: get a xoom from a store and flash recovery right away-> everything is good; have the xoom install an ota-update and flash recovery afterwards -> do it this way
Alright, so here goes. I've searched the thread for the issue I'm having, but have come up empty handed. I'm not Droid noob, especially not when it comes to flashing roms. But, here are the details I have.
I had been following dragonzkiller's development on his ICS rom. I hadn't really put forth any effort looking lately until yesterday, and saw that he had the wifi and camera fixed, which were really my two biggest issues, so when I saw that, I was excited. I began working on getting it all running. I've had the x2 for about 5 months or so, and usually, the first thing I do, as soon as I get a new phone, is root it. Back in April, I rooted with GingerBreak. Worked good, no issues there. Back in June, apparently I still received the OTA update taking it to 2.3.5-418, which I found out last night had kinda broken my root. So, I went back to find a way to re-root. I did that, with a desktop .exe that went in, and was supposed to flash BSR to my phone also. After I ran that, all my root permissions started asking for options again, so I was relieved. Now, for the issues I'm having.
I downloaded an app in the play store called Online Nandroid Backup. For some reason, and I think this may be a dev issue with the app, it won't run a backup, and tells me that it wasn't able to be granted superuser permissions, even though it is prompting and I'm allowing. Issue number two is this. I've tried 3 different ways to get this working. I used ROM Toolbox Lite, selected the rom I wanted to flash, and wipe data and cache, no delvik. I've selected to run a backup of my current rom. When it boots into recovery, I only have 4 options. Reboot your phone, something about installing the rom from sdcard, wipe data, and wipe cache. I'm not given the backup option on the recovery. Furthermore, when I kinda just decided that since I hadn't had any trouble flashing a rom to any of my other phones I've had, I would just try to flash the rom, it gives me a prompt about 25% through the rom package saying E: signature could not be verified, or something to that extent.
Even though it has said not to use Rom Manager, I did download that and try that, and got pretty much the same outcome of no rom, just a bit different scenario going through. Rom Manager won't reboot into recovery, and when I select to do a backup, it reboots the phone straight up. I also used the manual entrance into recovery, volume up, but it tells me something about starting RSD protocol, and sticks at that forever.
My real questions are this... I've always ever used CWM. All of my previous phones have been supported by Rom Manager nicely, so when it came to downloading and flashing a rom on them, no problems at all. I have never used BSR, to my knowledge, so I'm not sure if the recovery screen I'm seeing is the actual BSR recovery, or if it's some other recovery. If it's not BSR, do I just flash it like I would a rom, then re-run into that? And does the signature issue that I'm running into mean that I have to wait for a signed version of the rom in order to work it? Is there any way to fix this issue, or am I basically SOL right this moment? Any information on how I can fix all of this would be greatly appreciated. Thank you.
I doubt anyone has had a problem like this before, I think I'm in a real pickle (forum is censored), so brace yourself:
Phone: Optimus L7 P705
Firmware(that's what's called, right?): V20 (official update for jellybean)
I installed CM 10 today, and it was great, but I decided to uninstall it after 5 minutes of ''fun'' since some major features were missing like the ability to make calls (no signal) and the ability to listen to music with headphones (they won't work). Now I tried to look for fixes for it, but nothing worked, so I decided to get rid of it
Now this is where it gets REALLY INTERESTING: I have tried to flash ROMS with the KDZ updater, it gave me an error with 3 different KDZ files, I have also tried installing another ROM from the recovery mode, but it just gives me an ''install aborted'' error right after I start the install. I have made sure that all my settings were right and tried several times, I tried re-installing CM but nothing seems to work....
My phone is now as useless and basic as an iPhone....(Well okay, not THAT bad) but I need a solution urgently, so your help would be very appreciated.
Edit: RESOLVED, if you found this topic and want to know how I solved the issue, check the last post.
Sewrizer said:
Flash v10k(i think this would work) with the kdz thing. It should have everything working. Make a backup of the v10k then full wipe data cache and dalvik. At this point go into recovery mode and install zip from sd card: cm10 and gapps for jelly bean.
A friend of mine did this and worked
Sent from Area 51 using my HTC Sensation XE, hit thanks if I helped
Click to expand...
Click to collapse
Thank you for the reply, but as I had already explained, the KDZ Update Tool does not work for me, I have tried 3 different KDZ files including the v10k
Edit: Issue fixed, I downloaded the v10 baseband zip file and installed it with clockworkmod.
(this belongs elsewhere but 10 posts...)
I have a rooted S4 and just installed Dandvh's Google Play Edition v.20150919 (http://forum.xda-developers.com/showthread.php?t=2539361) rom. I used TWRP to install, wiping everything but internal storage, then flashed the rom. Installed fine, no errors. Took the usual bit of extra time to boot the first time then up and running clean and stable. The issue is that the OTA Updater app doesn't work, severely limiting my ROM options. It didn't install as part of the rom install, though I'm not sure if it's normal to just get it off the play store. I get an error message about not being compatible with the ROM and can't access it (error message screen cap below). Just in case, I wiped the phone and flashed again just to be sure, same result. The OTA Updater is important as this is where you can change kernals, audioFX stuff, toggle advanced power menus, and quite a bit more. When I used this ROM during the first part of the year OTA Updater worked just fine but I switched off in July to try another ROM so maybe something with the ROM has changed? I tried searching for any comments in the thread to indicate either that something changed with OTA Updater or if anyone else had a similar problem, found nothing. Would appreciate if anyone might know why OTA Updater isn't working or how I might correct it. Thanks.
Edit #1: I haven't changed the model number to SGH-M919 (as seen in the screen cap) in build.prop yet as if I can't get this ROM to work right I'll need to flash something else.
Edit #2: I noted in the patch notes that the ROM was updated for OTA Updater 2.4.2 and I was running 2.5.3 so I uninstalled it and installed 2.4.2. No luck there either.
Version and Build Screenshot
https://imgur.com/SQ6ie5i
Error message
https://imgur.com/TfWN7p2