Related
Hey guys, im trying to flash my htc one xl to viperXL. I've gotten TWRP on it and I made a backup and installed ViperXL but it keeps going to a boot loop.I managed to get it into recovery and it showed that my SDCard was wiped. I couldnt restore it, any help? I will provide more detail if asked. I just want to restore it to stock
Please someone help me ;( I just want to get back to stock.
Did you factory reset in bootloader?
Sent from my Evita
SD has been corrupted. Possibly because you did a factory reset in bootloader (known bug) as mentioned in the previous reply.
Plug the device into a Windows PC, go to device manager and format the SD. Then mount the SD in TWRP and move a ROM to the device, and flash.
timmaaa said:
Did you factory reset in bootloader?
Sent from my Evita
Click to expand...
Click to collapse
redpoint73 said:
SD has been corrupted. Possibly because you did a factory reset in bootloader (known bug) as mentioned in the previous reply.
Plug the device into a Windows PC, go to device manager and format the SD. Then mount the SD in TWRP and move a ROM to the device, and flash.
Click to expand...
Click to collapse
Holy ****! thank you!!!!!! I searched everywhere for a fix. You guys are lifesavers I thought It was bricked for good!!!!!
Zehmistah said:
Holy ****! thank you!!!!!! I searched everywhere for a fix. You guys are lifesavers I thought It was bricked for good!!!!!
Click to expand...
Click to collapse
Also don't forget if you are S-ON that you should flash the boot.img manually after you flash a new ROM. I use TN_WIN_Boot_Installer to ease this task.
drubin333 said:
Also don't forget if you are S-ON that you should flash the boot.img manually after you flash a new ROM. I use TN_WIN_Boot_Installer to ease this task.
Click to expand...
Click to collapse
What's hard about "fastboot flash boot boot.img" to begin with.... Using tools only adds risk
Or flashimagegui
I have an AT&T HTC One x. Its ***Tampered*** ***Unlocked*** HBOOT 1 .09. 0000 S-ON
I had been running an older version of TWRP, and decided I was going to clear my phone and do a fresh start. I know, I know, I should have made a backup, but I felt pretty confident in what I was doing, and was in too much of a hurry to rationalize this.
I wiped both the OS and previous version of TWRP in order to update to the new ones. While in fastboot I flashed CLEANrom and the new version of TWRP, and my administrative command prompt confirmed that they were installed successfully. Even cleared the cache afterwards. Now is the difficult part. I've researched, and researched, and cannot find a solution for this problem. I keep having a Boot Loop.... I'm stumped guys... I need some sort of help, be it technical, or something to drink lol
Previous ROM was CM 10, with TWRP and PA GAPPS :good:
Check the Evita FAQ thread in my signature, your answer probably lies within.
Sent from my Evita
timmaaa said:
Check the Evita FAQ thread in my signature, your answer probably lies within.
Sent from my Evita
Click to expand...
Click to collapse
I don't see anything in your FAQ that I haven't already tried unfortunately.....
Exactly which version of TWRP is currently installed? Did you flash the boot.img via fastboot?
Sent from my Evita
timmaaa said:
Exactly which version of TWRP is currently installed? Did you flash the boot.img via fastboot?
Sent from my Evita
Click to expand...
Click to collapse
It's the newest version of TWRP that is out, and yes, I flashed it via Fastboot, and it says successful on both the recovery install and ROM install.
Have you tried flashing another ROM? I asked for the exact recovery version for a reason, please provide that information.
Sent from my Evita
---------- Post added at 03:48 PM ---------- Previous post was at 03:43 PM ----------
Also it isn't completely clear to me that you're flashing the boot.img from the ROM zip via fastboot after flashing the ROM in TWRP. Are you extracting the boot.img from the ROM zip and doing that or not?
Sent from my Evita
1332858898
timmaaa said:
Have you tried flashing another ROM? I asked for the exact recovery version for a reason, please provide that information.
Sent from my Evita
Click to expand...
Click to collapse
TWRP 2.7. And yes, I have flashed about 4 Roms all succeeded according to fastboot and still getting the boot sequence.:good:
Yes I have extracted the boot.img
timmaaa said:
Have you tried flashing another ROM? I asked for the exact recovery version for a reason, please provide that information.
Sent from my Evita
---------- Post added at 03:48 PM ---------- Previous post was at 03:43 PM ----------
Also it isn't completely clear to me that you're flashing the boot.img from the ROM zip via fastboot after flashing the ROM in TWRP. Are you extracting the boot.img from the ROM zip and doing that or not?
Sent from my Evita
Click to expand...
Click to collapse
yes the boot.img file was extracted. I get a confirmation that it was successful when I flash it on fastboot
Exactly which ROMs have you tried to flash?
Sent from my Evita
timmaaa said:
Exactly which ROMs have you tried to flash?
Sent from my Evita
Click to expand...
Click to collapse
CM 10.2, CM 11, CLEANrom 7.0. all via fastboot with confirmations.
outcold32 said:
CM 10.2, CM 11, CLEANrom 7.0. all via fastboot with confirmations.
Click to expand...
Click to collapse
Why are you flashing roms via fastboot? -_- You're making your life difficult. Wipe everything in TWRP then flash in TWRP. ALso, you should really s-off and update your firmware/hboot. via RUU. You will likely encounter issues running a newer software on an such an old firmware.
exad said:
Why are you flashing roms via fastboot? -_- You're making your life difficult. Wipe everything in TWRP then flash in TWRP. ALso, you should really s-off and update your firmware/hboot. via RUU. You will likely encounter issues running a newer software on an such an old firmware.
Click to expand...
Click to collapse
If you would have read the thread, you would have noticed, that I am in bootloop, therefor I cannot access the recovery. And I have to have access to the ROM on my phone in order to flash anything via TWRP so this is moot. My question isn't how to flash roms, it's why am I getting a loop when I am successful on a clean partition and clean flash of both the recovery and ROM? And to me, fastboot is way easier than TWRP. I guess I could get a UART and try to debug the sequence myself, but I have more important things to do than that. I was posting to see if anyone had any similar problems. And this phone is an original model and I haven't really bothered with the security off, since I only wanted to get rid of sense in the first place. It was unlocked well before any commercial unlocker was available for the evita(Literally no stable CM10 at all at the time), so it's a little finicky in the first place. I ran the RUU after I re-locked the bootloader, and I'm at least out of the loop. I'm just going get to a more stable version so that this process will be more streamline when I re do my unlock and stuff.
So I guess the only solution at this point I have for any problem like this is to use the proper RUU. I tried a couple of times with no success, and it seemed the charm was to re lock the bootloader ( Fastboot oem lock) in order to properly and successfully get the RUU to work.:good:
Wth are you even on about? Of course you can access recovery in a bootloop. How are you getting to fastboot without accessing the bootloader? from the bootloader you can access recovery. If recovery isn't loading SCREW flashing a rom, reflash your recovery, 2.7 TWRP preferably. and then boot to recovery, mount your USB, copy the rom and flash it. Recovery is more important than having a ROM.
I know what I am talking about, do you know what you're talking about?
FFS I am trying to help you, there's no reason for you to be an ass. You're having issues BECAUSE you're flashing your rom via fastboot. You cannot flash a rom via fastboot.
exad said:
Wth are you even on about? Of course you can access recovery in a bootloop. How are you getting to fastboot without accessing the bootloader? from the bootloader you can access recovery. If recovery isn't loading SCREW flashing a rom, reflash your recovery, 2.7 TWRP preferably. and then boot to recovery, mount your USB, copy the rom and flash it. Recovery is more important than having a ROM.
I know what I am talking about, do you know what you're talking about?
FFS I am trying to help you, there's no reason for you to be an ass. You're having issues BECAUSE you're flashing your rom via fastboot. You cannot flash a rom via fastboot.
Click to expand...
Click to collapse
You didn't read the thread. I'm not being an ass. The information is already there.I can not access the recovery at all. That's why I am in in this situation. And again, if you had read the whole thread, or the even the original post, you would know that I cannot access the recovery. The only reason I'm being as detailed as I am is so I don't have to repeat myself, as well as for other people who may encounter this problem. And Yes I know what I am talking about. If I didn't I probably wouldn't have gotten to this point, right?
Okie dokie. No point in arguing. You're right. I'm wrong. Glad it's all working now.
Sent from my One XL using xda app-developers app
outcold32 said:
You didn't read the thread. I'm not being an ass. The information is already there.I can not access the recovery at all. That's why I am in in this situation. And again, if you had read the whole thread, or the even the original post, you would know that I cannot access the recovery. The only reason I'm being as detailed as I am is so I don't have to repeat myself, as well as for other people who may encounter this problem. And Yes I know what I am talking about. If I didn't I probably wouldn't have gotten to this point, right?
Click to expand...
Click to collapse
Exad is right in saying that the reason you're having problems is because you're attempting to flash ROMs with fastboot. That isn't how it's done. The correct way is to flash your ROM with recovery. You're barking up the wrong tree, not only that but you're arguing with experienced people who are only attempting to help get you out of the mess that you've gotten yourself into. You came here for advice, but there's no point in asking for advice if you're just going to argue and dismiss what you're being told to do.
You said you can't access your ROM so you can't flash anything, that makes absolutely no sense, which leads me to believe you don't really know what you're doing. Get out of the mindset that you need to use fastboot, it's wrong. You're dealing with people who have extensive and intimate knowledge of this device, trust us, we know what we're talking about.
Exactly why can't you access recovery? If you can issue fastboot commands that means you can access your bootloader, if you can access your bootloader that means you can use your volume keys to scroll through the options and the power button to select recovery. What happens when you do that? Exactly which recovery have you flashed to your device? I need to the full filename of the recovery that you've flashed.
Sent from my Evita
outcold32 said:
And this phone is an original model and I haven't really bothered with the security off, since I only wanted to get rid of sense in the first place. It was unlocked well before any commercial unlocker was available for the evita(Literally no stable CM10 at all at the time), so it's a little finicky in the first place.
Click to expand...
Click to collapse
S-on is a downright dangerous place to be, if the phone is also SuperCID (which is very likely, since its the AT&T variant). exad is right in recommending s-ff, as he is about a good many things.
sorry if this doesn't quite belong here but I was curious to go back just to stock kernel, not completely stock itself. Could anyone link me to a good step by step for me to do this? Do i use adbfastboot the boot.img only? Im just a a little confused..
Sorry I am still new and learning. Thanks for any help!
Download the relevant kernel to your device from here.
Reboot to recovery
Install the zip you just downloaded
This stuff tends to be a lot simpler than you'd expect, tbh.
dallas220 said:
sorry if this doesn't quite belong here but I was curious to go back just to stock kernel, not completely stock itself. Could anyone link me to a good step by step for me to do this? Do i use adbfastboot the boot.img only? Im just a a little confused..
Sorry I am still new and learning. Thanks for any help!
Click to expand...
Click to collapse
Download the factory images from Google : https://developers.google.com/android/nexus/images#hammerheadkot49h
Extract the boot.img and flash it via fastboot.. (fastboot flash boot boot.img)
Make sure your on stock rom before you flash it..
Sent from my Nexus 5 using Tapatalk
dallas220 said:
sorry if this doesn't quite belong here but I was curious to go back just to stock kernel, not completely stock itself. Could anyone link me to a good step by step for me to do this? Do i use adbfastboot the boot.img only? Im just a a little confused..
Sorry I am still new and learning. Thanks for any help!
Click to expand...
Click to collapse
Fastboot, you flash with fastboot and yes the kernel image is boot.img. You should probably also reflash your ROM (system.img if you're on the stock ROM) as many custom kernels also modify the system partition.
BirchBarlow said:
Fastboot, you flash with fastboot and yes the kernel image is boot.img. You should probably also reflash your ROM (system.img if you're on the stock ROM) as many custom kernels also modify the system partition.
Click to expand...
Click to collapse
Thanks for all the replies guys!
I am indeed on stock rom. To flash the system.img is pretty much the same as the boot.img yes?
dallas220 said:
Thanks for all the replies guys!
I am indeed on stock rom. To flash the system.img is pretty much the same as the boot.img yes?
Click to expand...
Click to collapse
Hi,
Same way: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701.
Hammer_Of_The_Gods said:
Hi,
Same way: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701.
Click to expand...
Click to collapse
Thank you brother
And just to add to my noobness.. Returning to stock kernel and or rom doesn't wipe any files on the phone correct? Ie picture data etc....?
dallas220 said:
Thank you brother
And just to add to my noobness.. Returning to stock kernel and or rom doesn't wipe any files on the phone correct? Ie picture data etc....?
Click to expand...
Click to collapse
As long as you don't flash the userdata.img, you are fine!
If you are using the flashall script then remove the -w flag and you're good to go!
Sent from my Nexus 5 using Tapatalk
vin4yak said:
As long as you don't flash the userdata.img, you are fine!
If you are using the flashall script then remove the -w flag and you're good to go!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I plan on flashing sys and boot!
And so sorry but what do you mean the flashall srcipt?
Would that be basically flashing everything to stock?
Sorry for such dumb questions
dallas220 said:
I plan on flashing sys and boot!
And so sorry but what do you mean the flashall srcipt?
Would that be basically flashing everything to stock?
Click to expand...
Click to collapse
So no worries since you don't flash all (you use the "Method2" from the link I posted above), about the "flash-all.sh" file, when you open the factory image file, you have this script, more info here about the "-w" to delete: http://forum.xda-developers.com/showpost.php?p=51949577&postcount=4.
Hammer_Of_The_Gods said:
So no worries since you don't flash all (you use the "Method2" from the link I posted above), about the "flash-all.sh" file, when you open the factory image file, you have this script, more info here about the "-w" to delete: http://forum.xda-developers.com/showpost.php?p=51949577&postcount=4.
Click to expand...
Click to collapse
thanks for you help my brother. Just another question.. If I have a nandroidbackup on the computer that I made before I installed my custom kernel, could you somehow use that to get back to the stock kernel? Is that something...or I am just asking the most ridiculous questions?
It seems the more I read, the less I am confident with adb, flashing, backups etc.... :S
dallas220 said:
thanks for you help my brother. Just another question.. If I have a nandroidbackup on the computer that I made before I installed my custom kernel, could you somehow use that to get back to the stock kernel? Is that something...or I am just asking the most ridiculous questions?
It seems the more I read, the less I am confident with adb, flashing, backups etc.... :S
Click to expand...
Click to collapse
If want the stock kernel download the factory images from google and flash the boot.img via fastboot. That's the easiest way.
If you still want to use nandroid backup then copy the nandroid backup to the correct location... Head over to Philz Touch recovery and use the custom restore option by which you can select only the "boot" and "system" partition. But I haven't tried doing it so can't say whether it will work or not. However, technically it should work. I have no idea how to do this using TWRP though as I haven't used it much.
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a custom recovery and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt custom recovery, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Thanks
SORRY JUST REALISED THIS SHOULD BE IN Q&A
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a bootloader and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt bootloader, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Than
Click to expand...
Click to collapse
hi, you're asking in the general section. which is wrong.
Just flash custom recovery again via fastboot and SuperSu via custom recovery http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a bootloader and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt bootloader, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Than
Click to expand...
Click to collapse
the exclamation point is the stock recovery. once you take in an ota, it removes both root and your custom recovery. to get your custom recovery back so that you can flash a bootloader(and the supersu root binaries). you can flash a custom recovery while youre in your bootloader via fastboot on your desktop.
GUGUITOMTG4 said:
hi, you're asking in the general section. which is wrong.
Just flash custom recovery again via fastboot and SuperSu via custom recovery http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Click to expand...
Click to collapse
Yeah just realised that. Sorry its my first post
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a custom recovery and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt custom recovery, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Thanks
SORRY JUST REALISED THIS SHOULD BE IN Q&A
Click to expand...
Click to collapse
why don't you try twrp maybe you can flash twrp then remove the file then go back to cwm
Sent from my Nexus 5 using Tapatalk
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a custom recovery and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt custom recovery, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Thanks
SORRY JUST REALISED THIS SHOULD BE IN Q&A
Click to expand...
Click to collapse
just read this again..when you are flash a custom recovery, and it still goes to the exclamation point, it means that you arent flashing the custom recovery right. its.. fastboot flash recovery recoveryname.img
GUGUITOMTG4 said:
hi, you're asking in the general section. which is wrong.
Just flash custom recovery again via fastboot and SuperSu via custom recovery http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Click to expand...
Click to collapse
Thats what I was trying to explain. I tried flashing custom recovery as per instructions but nothing happens. From what I am reading this is because of the reboot-from-recovery.p file which needs to be deleted BUT I cannot do this without root!
luppas said:
Thats what I was trying to explain. I tried flashing custom recovery as per instructions but nothing happens. From what I am reading this is because of the reboot-from-recovery.p file which needs to be deleted BUT I cannot do this without root!
Click to expand...
Click to collapse
na, you dont need to delete that to flash a custom recovery(i never have, in my 6 years with android, and all my devices). is fastboot seeing your device? kkdo you see fastboot going through the process of flashing a recovery? if you are typing it right, and fastboot sees your device, you would have flashed a custom recovery. when you connect to fastboot, type.. fastboot devices. if it sees your device, its id number will be shown.
simms22 said:
just read this again..when you are flash a custom recovery, and it still goes to the exclamation point, it means that you arent flashing the custom recovery right. its.. fastboot flash recovery recoveryname.img
Click to expand...
Click to collapse
C:\Users\user\Downloads\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
I have it right mate. But nothing seems to be happening. Maybe drivers issue? When I do adb version I get the version so I assumed that means its working
luppas said:
C:\Users\user\Downloads\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
I have it right mate. But nothing seems to be happening. Maybe drivers issue? When I do adb version I get the version so I assumed that means its working
Click to expand...
Click to collapse
adb version and fastboot devices is different. adb is not fastboot and you can not use adb as fastboot. fastboot is fastboot.
simms22 said:
na, you dont need to delete that to flash a custom recovery(i never have, in my 6 years with android, and all my devices). is fastboot seeing your device? kkdo you see fastboot going through the process of flashing a recovery? if you are typing it right, and fastboot sees your device, you would have flashed a custom recovery. when you connect to fastboot, type.. fastboot devices. if it sees your device, its id number will be shown.
Click to expand...
Click to collapse
Yeah you were right. Driver issue. fastboot devices showed nothing. Reinstalled drivers and looks to be good now.
Thanks guys sorry for the post in wrong area
luppas said:
Yeah you were right. Driver issue. fastboot devices showed nothing. Reinstalled drivers and looks to be good now.
Thanks guys sorry for the post in wrong area
Click to expand...
Click to collapse
glad you got it
Hi! My question is lame, i know.. But here it goes anyway, i couldn't find a simple and direct answer..
Is less than a week that i have this phone, and i've been reading a lot of guides of how to rollback to cm11s.. the thing is i've flashed the latest CM12S signed zip ota through CM Recovery, everything is fine as i'm testing it right now..
My question is: if i want to go back to CM11S (in the case that i don't like CM12S or have some bugs), can i just wipe data / factory reset and cache in CM Recovery, and then flash the cm11s signed zip?
I haven't rooted or unlocked bootloader, is it relatively easy from what i read around here.. but i wondered if i had to go through all those steps (unlock bootloader, custom recovery, and then flash) or just doing the steps mentioned before will work just fine..
Is it better to fastboot flash or through custom recovery is fine also?
Thanks in advance!
PD: I'm also asking what do you think about some other 5.1.1 Lollipop ROM, custom kernel, etc.. I'm kind of a flashaholic and i would be able to install the custom recovery if would be really worth it
PD2: sorry for the bad english, i'm from argentina
cesarp3791 said:
Hi! My question is lame, i know.. But here it goes anyway, i couldn't find a simple and direct answer..
Is less than a week that i have this phone, and i've been reading a lot of guides of how to rollback to cm11s.. the thing is i've flashed the latest CM12S signed zip ota through CM Recovery, everything is fine as i'm testing it right now..
My question is: if i want to go back to CM11S (in the case that i don't like CM12S or have some bugs), can i just wipe data / factory reset and cache in CM Recovery, and then flash the cm11s signed zip?
I haven't rooted or unlocked bootloader, is it relatively easy from what i read around here.. but i wondered if i had to go through all those steps (unlock bootloader, custom recovery, and then flash) or just doing the steps mentioned before will work just fine..
Is it better to fastboot flash or through custom recovery is fine also?
Thanks in advance!
PD: I'm also asking what do you think about some other 5.1.1 Lollipop ROM, custom kernel, etc.. I'm kind of a flashaholic and i would be able to install the custom recovery if would be really worth it
PD2: sorry for the bad english, i'm from argentina
Click to expand...
Click to collapse
Just unlock your bootloader now, the longer you leave it the more difficult it'll be to backup your internal storage beforehand. You should really have it unlocked anyway as insurance against anything going wrong with your phone. Once you have unlocked it you can flash TWRP recovery, then the correct procedure to go back to CM11S would be to perform a full wipe (system, data, cache, dalvik cache) and then just flash the zip. As far as custom ROMs for this device go, there are many excellent options to choose from that offer extra customisation that you won't find on the stock ROM.
Don't we have to flash the firmware prior to flashing back to CM11s to prevent a hardbrick? I'm looking into doing this as well, so I'm just asking for my own clarity.
uansari1 said:
Don't we have to flash the firmware prior to flashing back to CM11s to prevent a hardbrick? I'm looking into doing this as well, so I'm just asking for my own clarity.
Click to expand...
Click to collapse
The firmware is contained in the official zip.
Heisenberg said:
The firmware is contained in the official zip.
Click to expand...
Click to collapse
Thanks! Stupid question, but can you please link me to the official zip? I already have TWRP installed, so it would be nice to revert sooner than later.
uansari1 said:
Thanks! Stupid question, but can you please link me to the official zip? I already have TWRP installed, so it would be nice to revert sooner than later.
Click to expand...
Click to collapse
You'll find them all here:
http://forum.xda-developers.com/showthread.php?t=2906746
Thanks!
Thank you both, i believe that this week i'll have some time and unlock the bootloader and flashing the TWRP recovery right away.. Then i'll see which ROM suits my use (i'm looking to battery friendly and high screen on time, will see the forums accordingly) and start the journey on this beautiful and well supported device
Also, thanks for the clarification of the modems.. Will be looking after that and make sure not to miss that step if required :good:
cesarp3791 said:
Thank you both, i believe that this week i'll have some time and unlock the bootloader and flashing the TWRP recovery right away.. Then i'll see which ROM suits my use (i'm looking to battery friendly and high screen on time, will see the forums accordingly) and start the journey on this beautiful and well supported device
Also, thanks for the clarification of the modems.. Will be looking after that and make sure not to miss that step if required :good:
Click to expand...
Click to collapse
Once you've flashed the ROM, please do share your results. I am still unsure if reverting from a Lollipop ROM to CM11S will cause issues with the radio and/or a softbrick of the device, as I've read that this "can" happen.
uansari1 said:
Once you've flashed the ROM, please do share your results. I am still unsure if reverting from a Lollipop ROM to CM11S will cause issues with the radio and/or a softbrick of the device, as I've read that this "can" happen.
Click to expand...
Click to collapse
Reverting from Lollipop to KitKat won't brick your device, whoever said that is wrong, and would have caused a brick because they didn't know what they were doing. You do need to make sure you flash a KitKat modem though, otherwise you'll have issues with the prox sensor.
Heisenberg said:
Reverting from Lollipop to KitKat won't brick your device, whoever said that is wrong, and would have caused a brick because they didn't know what they were doing. You do need to make sure you flash a KitKat modem though, otherwise you'll have issues with the prox sensor.
Click to expand...
Click to collapse
Thanks Timaaa...last question, I'm downloading the latest modem from this thread http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-xnph05q-t3027033.
Is this the correct flashable modem file to use, or do you recommend another for XNPH05Q?
uansari1 said:
Thanks Timaaa...last question, I'm downloading the latest modem from this thread http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-xnph05q-t3027033.
Is this the correct flashable modem file to use, or do you recommend another for XNPH05Q?
Click to expand...
Click to collapse
That modem should be fine.