Related
hey all.finally got my chacha back after 2months of it being repaired to no avail and now it's working fine yeyy. but i got a couple questions,anyone else has "car mode"? cause since i got it back and this pops up weirdly.and it just says press to exit car mode. and another thing i noticed was that i got new message notifications (the envelope is green,not white as it was)
now to my main question, i got my phone rooted and a custom recovery.can i update the phone without going back to stock recovery?cause i tried that and it fails.
thank you
RockyAJ said:
hey all.finally got my chacha back after 2months of it being repaired to no avail and now it's working fine yeyy. but i got a couple questions,anyone else has "car mode"? cause since i got it back and this pops up weirdly.and it just says press to exit car mode. and another thing i noticed was that i got new message notifications (the envelope is green,not white as it was)
now to my main question, i got my phone rooted and a custom recovery.can i update the phone without going back to stock recovery?cause i tried that and it fails.
thank you
Click to expand...
Click to collapse
What software version are you on?
jporch316 said:
What software version are you on?
Click to expand...
Click to collapse
2.3.5
software version:1.57.415.3 arabic rom
no one?
RockyAJ said:
can i update the phone without going back to stock recovery?cause i tried that and it fails.
thank you
Click to expand...
Click to collapse
I had also tried to update and it fails,too. I think we need to restore the stock first.
samyangel said:
I had also tried to update and it fails,too. I think we need to restore the stock first.
Click to expand...
Click to collapse
i tried that but still didn't work..that's why am asking if there's some other way...
RockyAJ said:
i tried that but still didn't work..that's why am asking if there's some other way...
Click to expand...
Click to collapse
Well if your OTA is working you can try what I did before I sent my phone to the repair. Download an older RUU (or the same if there is a newer one available), extract from it Rom.zip and from that zip extract system.img, boot.img and recovery.img. Flash those three via fastboot and when your phone boots you will have a stock rom on it. Then just use OTA to update your phone to the latest version.
didije said:
Well if your OTA is working you can try what I did before I sent my phone to the repair. Download an older RUU (or the same if there is a newer one available), extract from it Rom.zip and from that zip extract system.img, boot.img and recovery.img. Flash those three via fastboot and when your phone boots you will have a stock rom on it. Then just use OTA to update your phone to the latest version.
Click to expand...
Click to collapse
Do I need to relock the phone before flash three files above?
samyangel said:
Do I need to relock the phone before flash three files above?
Click to expand...
Click to collapse
No need to do that.
didije said:
No need to do that.
Click to expand...
Click to collapse
Thanks
I have been holding off from updating to 30O since it came out because of battery issues, however now that 33R is rolling out im trying to install 30O in preparation but am unable to do so. Whenever I hit the "Download Update" button through settings nothing happens, I have tried restarts and cache wipes with no luck. Everything on the phone is still stock.
Any suggestions?
Do you have the update via recovery button checked in dev settings? Also you don't need to download 30O, just go straight to 33R.
teh roxxorz said:
Do you have the update via recovery button checked in dev settings? Also you don't need to download 30O, just go straight to 33R.
Click to expand...
Click to collapse
I am trying to update via ota not a custom recovery does that make a difference?
teh roxxorz said:
Also you don't need to download 30O, just go straight to 33R.
Click to expand...
Click to collapse
I don't think that's possible; the OTAs are incremental.
Joe-Pk said:
I am trying to update via ota not a custom recovery does that make a difference?
Click to expand...
Click to collapse
Well yes; if you uncheck the update via recovery you can't ota, and you have to have stock recovery installed as well.
teh roxxorz said:
Well yes; if you uncheck the update via recovery you can't ota, and you have to have stock recovery installed as well.
Click to expand...
Click to collapse
This is also not true. The "Update CM recovery" option in developer options just keeps updates from overwriting your custom recovery back to the stock recovery. You can update via OTA with a custom recovery; I did it with TWRP.
dr3amsINdigital said:
This is also not true. The "Update CM recovery" option in developer options just keeps updates from overwriting your custom recovery back to the stock recovery. You can update via OTA with a custom recovery; I did it with TWRP.
Click to expand...
Click to collapse
Well yea. Sorry if my wording was a bit convoluted; but I just see it being a waste of time to overwrite the custom recovery. But also from my experience OTA just goes with stock recovery, so thank you for your input.
Joe-Pk said:
I have been holding off from updating to 30O since it came out because of battery issues, however now that 33R is rolling out im trying to install 30O in preparation but am unable to do so. Whenever I hit the "Download Update" button through settings nothing happens, I have tried restarts and cache wipes with no luck. Everything on the phone is still stock.
Any suggestions?
Click to expand...
Click to collapse
You can download the OTA updates from somewhere like Android Police and flash them manually.
teh roxxorz said:
Do you have the update via recovery button checked in dev settings? Also you don't need to download 30O, just go straight to 33R.
Click to expand...
Click to collapse
This is irrelevant.
Joe-Pk said:
I am trying to update via ota not a custom recovery does that make a difference?
Click to expand...
Click to collapse
It makes zero difference.
dr3amsINdigital said:
I don't think that's possible; the OTAs are incremental.
Click to expand...
Click to collapse
It is possible by using the fastboot images from the cyngn site.
teh roxxorz said:
Well yes; if you uncheck the update via recovery you can't ota, and you have to have stock recovery installed as well.
Click to expand...
Click to collapse
Not true.
dr3amsINdigital said:
This is also not true. The "Update CM recovery" option in developer options just keeps updates from overwriting your custom recovery back to the stock recovery. You can update via OTA with a custom recovery; I did it with TWRP.
Click to expand...
Click to collapse
Exactly.
teh roxxorz said:
Well yea. Sorry if my wording was a bit convoluted; but I just see it being a waste of time to overwrite the custom recovery. But also from my experience OTA just goes with stock recovery, so thank you for your input.
Click to expand...
Click to collapse
An OTA can be flashed by stock recovery or TWRP on this device.
Transmitted via Bacon
I'm just trying to install it through the settings options. I don't want to use any custom recovery. I want to keep everything stock like it is now.
Joe-Pk said:
I'm just trying to install it through the settings options. I don't want to use any custom recovery. I want to keep everything stock like it is now.
Click to expand...
Click to collapse
You can manually flash updates while stock.
Joe-Pk said:
I'm just trying to install it through the settings options. I don't want to use any custom recovery. I want to keep everything stock like it is now.
Click to expand...
Click to collapse
dr3amsINdigital said:
You can manually flash updates while stock.
Click to expand...
Click to collapse
Yes you can. Rename file to update.zip and flash through stock recovery. Please make sure you give out accurate information if you're going to answer questions.
Transmitted via Bacon
timmaaa said:
Yes you can. Rename file to update.zip and flash through stock recovery. Please make sure you give out accurate information if you're going to answer questions.
Transmitted via Bacon
Click to expand...
Click to collapse
I'm not sure if you read my post wrong or not, but I said you can manually flash updates while stock. If you did read it correctly and are just complaining that I didn't give a detailed answer with instructions, I wasn't exactly sure of the process, so I left that to someone else. Some helpful information is better than none.
dr3amsINdigital said:
I'm not sure if you read my post wrong or not, but I said you can manually flash updates while stock. If you did read it correctly and are just complaining that I didn't give a detailed answer with instructions, I wasn't exactly sure of the process, so I left that to someone else. Some helpful information is better than none.
Click to expand...
Click to collapse
My sincerest apologies! I completely misread your post.
Transmitted via Bacon
I ended up just flashing manually using files from android police and stock recovery, however the download update button still didnt work even when i was trying to go to 33R. If I get some time ill get around to factory resetting and trying again because as far as i can tell there is no reason for it not to work.
You could always sideload a OTA if you have the zipfile.
Code:
adb reboot recovery
in recovery choose "ADB Sideload"
Code:
adb sideload update.zip
I've been in the samsung family for so long that I didn't realize how different flashing can be. I broke my phone so I bought a Moto G. Rooted it right away with only a little trouble. I installed a Lollipop ROM afterward and couldn't get my phone to boot. Guess who forgot to do a backup of the stock ROM? Yay me... but anyway, I found a stock file and went through all the steps in the screenshot. Each time, I got the okay to move on and I assumed I had the stock file flashed. Upon rebooting, I stay at the "warning, bootloader is unlocked" and phone doesn't go any further. I'm not booting up at all and custom recovery is gone now.
Can anyone help? I'm at my wit's end.
Thanks in advance.
http://forum.xda-developers.com/showthread.php?t=2542219
Follow this step by step. I did it twice. If your phone boots, it is more than likely recoverable. Once you get everything sorted out and are ready to flash a custom ROM, I recommend Carbon ROM (personal preference).
The lollipop ones are still shaky. I would try em out but they truly aren't daily drivers yet
---------- Post added at 11:19 AM ---------- Previous post was at 11:01 AM ----------
Another thought. You have your bootloader unlocked. You can flash the TWRP image through fastboot. Then you can flash the "flashable zip" stock firmware
BBobby said:
http://forum.xda-developers.com/showthread.php?t=2542219
Follow this step by step. I did it twice. If your phone boots, it is more than likely recoverable. Once you get everything sorted out and are ready to flash a custom ROM, I recommend Carbon ROM (personal preference).
The lollipop ones are still shaky. I would try em out but they truly aren't daily drivers yet
---------- Post added at 11:19 AM ---------- Previous post was at 11:01 AM ----------
Another thought. You have your bootloader unlocked. You can flash the TWRP image through fastboot. Then you can flash the "flashable zip" stock firmware
Click to expand...
Click to collapse
That's actually the instructions I used to try to flash back to stock. But when it reboots, it never gets past the warning about bootloader. I can get the TWRP recovery back but from there is there another way to flash the "flashable zip"? With Samsung I could always use ODIN but I don't think it works with Moto G. I can't get the zip to internal storage to flash it.
Thanks for the reply by the way I'm going to try it one more time I think....
http://forum.xda-developers.com/showthread.php?t=2854688
Flashable stock zips. I don't have a PC to do a full reset. But with TWRP and the flashable stock zip I have had absolutely no problem.
If all else fails I would give it a shot
I have the xt 1032 cricket/aio. I am using stock "us retail" and it works just fine. If you have radio issues etc there is also a repository of flashable radio images
BBobby said:
http://forum.xda-developers.com/showthread.php?t=2854688
Flashable stock zips. I don't have a PC to do a full reset. But with TWRP and the flashable stock zip I have had absolutely no problem.
If all else fails I would give it a shot
I have the xt 1032 cricket/aio. I am using stock "us retail" and it works just fine. If you have radio issues etc there is also a repository of flashable radio images
Click to expand...
Click to collapse
I hate sounding dumb... but how will I flash the zip if I can't get it on my phone?
Get back TWRP custom recovery by booting your phone into bootloader and flash via fastboot. You can get the .IMG file for the falcon from their website latest version is 2.8.5.0
http://teamw.in/project/twrp2/233
Then simply install the corresponding stock flashable zip
BBobby said:
Get back TWRP custom recovery by booting your phone into bootloader and flash via fastboot. You can get the .IMG file for the falcon from their website latest version is 2.8.5.0
http://teamw.in/project/twrp2/233
Then simply install the corresponding stock flashable zip
Click to expand...
Click to collapse
Thank you for all your help. I'll give that a shot.
BBobby said:
Get back TWRP custom recovery by booting your phone into bootloader and flash via fastboot. You can get the .IMG file for the falcon from their website latest version is 2.8.5.0
http://teamw.in/project/twrp2/233
Then simply install the corresponding stock flashable zip
Click to expand...
Click to collapse
Quick question. When I go into recovery to flash the zip, do I go to 'advanced' and then ' terminal command'? and go from there? I feel like a noob and I've flashed dozens of roms...
To flash a zip, choose the install option, find the name of the zip, select it, swipe to install it.
audit13 said:
To flash a zip, choose the install option, find the name of the zip, select it, swipe to install it.
Click to expand...
Click to collapse
The problem is that I didn't make a backup. When I tried flashing back to stock using fastboot everything was wiped. I don't even have the original custom ROM that started the whole mess. The stock file flashed but phone won't boot. I never get passed the boot loader warning screen. I did everything to the tee (following the directions that BBobby posted above. Actually did it twice. Isn't there an ODIN type deal for this phone. Brand new and I've broke it dangit.
Oh and I can't get into the phone to enable us debugging.
There is rsd lite but it may not help. Odin doesn't help if you can't enter download mode too. Usb debugging isn't require to flash a rom or install recovery.
It sounds like your phone is not booting because of the bootloade or the data partition is messed up.
I can get into bootloader and I have TWRP installed and can boot into it. I'm starting to think it's a lost cause. Thanks though y'all.
stacalicious said:
I can get into bootloader and I have TWRP installed and can boot into it. I'm starting to think it's a lost cause. Thanks though y'all.
Click to expand...
Click to collapse
I also got similar problem as yours. I have xt1033 dual sim phone and i had flashed lollipop 5.0.2 soak version. When official update was released for xt1033 i got back to kitkat 4.4.4 to download ota. But when i flashed kitkat through fastboot it got stuck on unlocked bootloader screen. Only solution i got still is converting to gpe. Only Gpe firmware boots. Im still finding solution for bootloop
You can get into TWRP? What happens when you use it to flash a custom ROM?
BBobby said:
http://forum.xda-developers.com/showthread.php?t=2542219
Follow this step by step. I did it twice. If your phone boots, it is more than likely recoverable. Once you get everything sorted out and are ready to flash a custom ROM, I recommend Carbon ROM (personal preference).
The lollipop ones are still shaky. I would try em out but they truly aren't daily drivers yet
---------- Post added at 11:19 AM ---------- Previous post was at 11:01 AM ----------
Another thought. You have your bootloader unlocked. You can flash the TWRP image through fastboot. Then you can flash the "flashable zip" stock firmware
Click to expand...
Click to collapse
audit13 said:
You can get into TWRP? What happens when you use it to flash a custom ROM?
Click to expand...
Click to collapse
I originally flashed a custom ROM but it never would get past the loading screen. I went through all the steps to flash back to stock and now all my data is gone. The ROM I had in my download folder is gone as is all my other info. So I get into TWRP but there's nothing in my phone I can flash.
audit13 said:
You can get into TWRP? What happens when you use it to flash a custom ROM?
Click to expand...
Click to collapse
I've flashed dozens, probably hundreds of ROMs in the past and never ran into such an issue. Custom ROM seemed to take, but got stuck. So I used fastboot and followed the directions to the tee in this link http://forum.xda-developers.com/showthread.php?t=2542219
When the ROM is finished flashing (stock that is) it never gets past the bootloader warning screen. If I could just get a zip onto the phone, I could flash through TWRP but I have no idea how to or if it's even possible.
Cwm have a option "sdcard mount" via usb. I dont remember the specific option but you can mount your device and connect it to a computer.
esd316 said:
Cwm have a option "sdcard mount" via usb. I dont remember the specific option but you can mount your device and connect it to a computer.
Click to expand...
Click to collapse
So I got into cwm. I can't mount usb storage, but I have an option to use adb sideload? Can I flash stock from there?
http://teamw.in/project/twrp2/233
Instructions on how to flash via fastboot are there in the same download page
---------- Post added at 02:47 AM ---------- Previous post was at 02:43 AM ----------
stacalicious said:
Quick question. When I go into recovery to flash the zip, do I go to 'advanced' and then ' terminal command'? and go from there? I feel like a noob and I've flashed dozens of roms...
Click to expand...
Click to collapse
The moto g just needs to do a wipe. Advanced wipe is not necessary. Then install the zip from the folder. By the way you can flash from USB otg (USB storage device such as a flash drive)
I fixed it!!!
stacalicious said:
I originally flashed a custom ROM but it never would get past the loading screen. I went through all the steps to flash back to stock and now all my data is gone. The ROM I had in my download folder is gone as is all my other info. So I get into TWRP but there's nothing in my phone I can flash.
Click to expand...
Click to collapse
esd316 said:
Cwm have a option "sdcard mount" via usb. I dont remember the specific option but you can mount your device and connect it to a computer.
Click to expand...
Click to collapse
I'd hug your neck right now if I could get to you!!! I flashed cwm, went to adb sideload and installed a stock rom. My phone is back up and money isn't going to be pissed into the wind because I made a mistake. Thanks to everyone for your help.
HI all, I have CM12 installed on my rooted phone and this morning when I switched it on, I got a message saying:
"WARNING: Update Cyanogen recovery is disabled. This may cause issues with updating your device. Please enable Update Cyanogen recovery in developer options"
Now, that option is off because I have my custom recovery TWRP installed on the phone, I'd like to keep that and I don't want to reinstall it after the update, so I believe I should ignore the message, but what I wanted to check with you guys is whether ignoring it will in fact cause any issues as this is the first time ever I've seen this message (this update by the way I think is the first one after installing CM12).
Any idea?
thanks
Disregard the message.
Thanks Heisenberg,
I did that but when the phone restarts trying to install the update, it goes straight into recovery mode (TWRP) and from there I don't think I can install the update, as none of the options seem to allow me to do so, see screenshot http://s23.postimg.org/6d6s7wyq3/IMG_20150625_135453.jpg
All right, I downloaded the zip from here http://cyanogen-ota-bacon.somee.com/ and tried to flash it from TWRP, but I get an error, screenshot here http://s28.postimg.org/zb06wtcpp/OTA_error.jpg, any idea why?
Same here, got an error in TWRP logs that prevented the update to install.
I'd like to avoid reflashing stock recovery only to install the update...
Heres the log: http://s29.postimg.org/njqqqlfc7/Screenshot_2015_06_25_08_49_42.png
Seems something related to outdated "build fingerprint" my device has currently 12.0-YNG1TAS17L
I guess the alternative would be to do it thru Cyanogen Recovery, but let's see what more knowledgeable members have to say as, like you, I don't want to have to reinstall TWRP and SU just for the sake of the update
Looks like you cant use the official update with TWRP. Either flash it via cyanogen recovery then flash back TWRP, or use a differnt zip for update not the official
Thanks for clarifying that davebugyi, then so be it, I'll do it thru cyanogen recovery and then reflash TWRP and probably SU as well
thanks
davebugyi said:
Looks like you cant use the official update with TWRP. Either flash it via cyanogen recovery then flash back TWRP, or use a differnt zip for update not the official
Click to expand...
Click to collapse
Ah, sorry forgot to ask, is there an unofficial update? If so where do I get it from?
davebugyi said:
Looks like you cant use the official update with TWRP. Either flash it via cyanogen recovery then flash back TWRP, or use a differnt zip for update not the official
Click to expand...
Click to collapse
duratto said:
Ah, sorry forgot to ask, is there an unofficial update? If so where do I get it from?
Click to expand...
Click to collapse
For example here: http://forum.xda-developers.com/showthread.php?t=2810365
thanks! Ah OK I see so that's the whole ROM there as opposed to just an update
davebugyi said:
For example here: http://forum.xda-developers.com/showthread.php?t=2810365
Click to expand...
Click to collapse
Do you mean flashing only this update found at the end of the first post?
YNG1TAS2I3 Radio, etc - Mirror - Same as YNG1TAS0YL
md5 - 6d5db5af6c92b814b9a0ebd18341dd8e
Click to expand...
Click to collapse
Is it safe to flash only that zip from TWRP over the stock Cyanogen OS?
Yes, but if I'm not mistaken, judging from the file size, that's the whole ROM
tsnake said:
Do you mean flashing only this update found at the end of the first post?
Is it safe to flash only that zip from TWRP over the stock Cyanogen OS?
Click to expand...
Click to collapse
The file I quoted is not a whole ROM, it's 31 MB.
AH OK, sorry I thught you referred to the 500mb file
Apparently even by enabling cyanogen recovery, I still can't get the updated installed as the phone keeps rebooting in the TWRP recovery, which is very odd.
I'm having the same issue. Anyone?
Got the same problem. Any idea?
duratto said:
Apparently even by enabling cyanogen recovery, I still can't get the updated installed as the phone keeps rebooting in the TWRP recovery, which is very odd.
Click to expand...
Click to collapse
Bump for a fix?
Juergen1337 said:
Got the same problem. Any idea?
Click to expand...
Click to collapse
The solution seems to be installing the new ROM provided. Related problem here http://forum.xda-developers.com/oneplus-one/help/twrp-cm-android-version-mismatch-t3147658
Hey there fellow U11 Users,
I just received the update concerning 60fps HD-Video etc. I use TWRP so the update can't be installed by itself. So I have two questions:
A
Where do I find the update file. I looked around a lot but couldn't locate it.
B
Once found, can I just flash it with TWRP?
Thanks in advance!
Dito13 said:
Hey there fellow U11 Users,
I just received the update concerning 60fps HD-Video etc. I use TWRP so the update can't be installed by itself. So I have two questions:
A
Where do I find the update file. I looked around a lot but couldn't locate it.
B
Once found, can I just flash it with TWRP?
Thanks in advance!
Click to expand...
Click to collapse
See here: https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048/page63
Alright, thanks! :good: That only leaves the first question unanswered.
Dito13 said:
Alright, thanks! :good: That only leaves the first question unanswered.
Click to expand...
Click to collapse
/data/data/com.htc.updater/files
btw...twrp can install the update but you need to flash the firmware.zip inside the ota manually
Thank you kindly!
OMJ said:
/data/data/com.htc.updater/files
btw...twrp can install the update but you need to flash the firmware.zip inside the ota manually
Click to expand...
Click to collapse
Just to be clear: I only flash the firmware.zip manually via TWRP or do I need to flash the whole ota?
Sorry for the question. I mostly handled Nexus devices...
Dito13 said:
Just to be clear: I only flash the firmware.zip manually via TWRP or do I need to flash the whole ota?
Sorry for the question. I mostly handled Nexus devices...
Click to expand...
Click to collapse
twrp will install the ota zip but it wont install the firmware.zip inside, you have to extract & manually install from download mode
grrr.... I tried following your suggestions, but recieved error 7 in TWRP. Can you help me in the right direction?
Dito13 said:
grrr.... I tried following your suggestions, but recieved error 7 in TWRP. Can you help me in the right direction?
Click to expand...
Click to collapse
list your steps your using to install the ota via twrp....personally, I let the system initiate the install (booted into OS) as if I was 100% stock, once twrp loads, it automatically installs except for the firmware.zip
more details here...
OK, I am a Noob to the HTC world. I am used to easy flashing/rooting/etc. on Nexus devices.
TWRP doesn't do anything after accepting the ota. When I try to install the OTA via TWRP I receive Error 7. I worked my way through a lot of guides here on XDA concerning manual OTA installing. One thing I tried was flashing back to stock recovery which I found in the firmware.zip of the OTA in bootloader mode. That failed also ("FAILED (remote: not allowed on PRODUCTION device).
Edit: The device has obviously an unlocked bootloader, s-on, rooted via magisk and is a DGLU device, software number 1.16.400.5
Are you on an Untouched System Image? Completely stock ROM? While it is great we can flash the OTA in TWRP, the system stills needs to be stock, and of course will still have to fastboot firmware.
schmeggy929 said:
Are you on an Untouched System Image? Completely stock ROM? While it is great we can flash the OTA in TWRP, the system stills needs to be stock, and of course will still have to fastboot firmware.
Click to expand...
Click to collapse
Yes, everything is stock.
I managed to flash the stock recovery now. I didn't remember to use the download mode /sorry. Then Then I checked for the ota again, downloaded it and tried to apply but I landed in the stock recovery with the red exclamation mark and then nothing happened.
Dito13 said:
Yes, everything is stock.
I managed to flash the stock recovery now. I didn't remember to use the download mode /sorry. Then Then I checked for the ota again, downloaded it and tried to apply but I landed in the stock recovery with the red exclamation mark and then nothing happened.
Click to expand...
Click to collapse
re-flash twrp and try it again.
schmeggy929 said:
re-flash twrp and try it again.
Click to expand...
Click to collapse
Same result unfortunately. TWRP hands out Error 7 and "system partition has unexpected contents" or something like that although I didn't do any tinkering with the stock rom. I flashed Magisk and did a backup before and that was all.
Dito13 said:
Same result unfortunately. TWRP hands out Error 7 and "system partition has unexpected contents" or something like that although I didn't do any tinkering with the stock rom. I flashed Magisk and did a backup before and that was all.
Click to expand...
Click to collapse
Only thing I would say is start fresh. Backup all the data for your apps first. Flash the RUU, Take the OTA and reinstall all your apps.
schmeggy929 said:
Only thing I would say is start fresh. Backup all the data for your apps first. Flash the RUU, Take the OTA and reinstall all your apps.
Click to expand...
Click to collapse
Thanks again - seems to have worked. It will be interesting to see which problems occur with the Android Oreo update which was announced till the end of the year by HTC