So I have used MultiRom for a while. It was cool to mess with, but in practice it wasn't something I used often. I used the uninstall option to delete it from my device.
But I have noticed, that my battery charging icon is different from the default. I think this is still the MultiRom boot.IMG.
Also sometimes the led splashes green, also a feature of MultiRom to know when it is listening for a keystroke.
Can I somehow see what boot IMG this is, and should I change it to the original OPO one?
Thanks,
-JustRamon
Sent from my A0001 using Tapatalk
JustRamon said:
So I have used MultiRom for a while. It was cool to mess with, but in practice it wasn't something I used often. I used the uninstall option to delete it from my device.
But I have noticed, that my battery charging icon is different from the default. I think this is still the MultiRom boot.IMG.
Also sometimes the led splashes green, also a feature of MultiRom to know when it is listening for a keystroke.
Can I somehow see what boot IMG this is, and should I change it to the original OPO one?
Thanks,
-JustRamon
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Your battery icon has nothing to do with the kernel, so that isn't it. You probably didn't wipe properly (system, data, cache, dalvik cache) when you flashed last or there are some remnants of Multirom left over. Your best option is to first use TWRP to wipe your data partition, and then to flash the stock images with fastboot. Once you've done this just flash whatever ROM you want (wipe properly first).
Heisenberg said:
Your battery icon has nothing to do with the kernel, so that isn't it. You probably didn't wipe properly (system, data, cache, dalvik cache) when you flashed last or there are some remnants of Multirom left over. Your best option is to first use TWRP to wipe your data partition, and then to flash the stock images with fastboot. Once you've done this just flash whatever ROM you want (wipe properly first).
Click to expand...
Click to collapse
I meant the charging animation outside the rom. Normally its a big battery with red/green filling, but for me its just a small white battery now.
But for the rest I could test out to flash the factory images. But, first I have to get my adb/fastboot drivers working again *sigh*
Sent from my A0001 using Tapatalk
JustRamon said:
I meant the charging animation outside the rom. Normally its a big battery with red/green filling, but for me its just a small white battery now.
But for the rest I could test out to flash the factory images. But, first I have to get my adb/fastboot drivers working again *sigh*
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Ok, probably should have specified that in the OP. Flashing the stock images is your best bet, so get those drivers sorted out (or use a Linux machine, no drivers required) and you should be able to fix it.
Heisenberg said:
Ok, probably should have specified that in the OP. Flashing the stock images is your best bet, so get those drivers sorted out (or use a Linux machine, no drivers required) and you should be able to fix it.
Click to expand...
Click to collapse
That's a good idea. My Elementary dualboot can help me
I knew it was handy to have that...
Sent from my A0001 using Tapatalk
Heisenberg said:
Ok, probably should have specified that in the OP. Flashing the stock images is your best bet, so get those drivers sorted out (or use a Linux machine, no drivers required) and you should be able to fix it.
Click to expand...
Click to collapse
Can I just search for a OnePlus One boot.img and flash it? I thought it changed during upgrade to lollipop, and I would like to keep my rom if possible
If not so, did someone provide a oneplus one lollipop boot.img, and will it just work with my (allready flashed ofcourse) CyanogenMod nightlies?
JustRamon said:
Can I just search for a OnePlus One boot.img and flash it? I thought it changed during upgrade to lollipop, and I would like to keep my rom if possible
If not so, did someone provide a oneplus one lollipop boot.img, and will it just work with my (allready flashed ofcourse) CyanogenMod nightlies?
Click to expand...
Click to collapse
You need to flash tire appropriate boot.img, you can just extract it from the ROM zip.
Heisenberg said:
You need to flash tire appropriate boot.img, you can just extract it from the ROM zip.
Click to expand...
Click to collapse
Which ROM zip? The Cyanogen 12S one? And can I use flashify to make things easier?
Sent from my A0001 using Tapatalk
JustRamon said:
Which ROM zip? The Cyanogen 12S one? And can I use flashify to make things easier?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Aren't you on a nightly? You need to flash the appropriate boot.img for the ROM you're currently on.
Heisenberg said:
Aren't you on a nightly? You need to flash the appropriate boot.img for the ROM you're currently on.
Click to expand...
Click to collapse
Is it included in those zips? Why is it in there and isn't it automatically flashed when installing it?
Sent from my A0001 using Tapatalk
JustRamon said:
Is it included in those zips? Why is it in there and isn't it automatically flashed when installing it?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Yes, it is included in those zips, and it is flashed automatically when you flash the ROM. The boot.img is the kernel, without flashing the kernel the phone wouldn't even boot. This is why I've been telling you that I don't think it's the boot.img that's causing your problem, and why I suggested you flash the stock images with fastboot. I say these things for a reason.
Heisenberg said:
Yes, it is included in those zips, and it is flashed automatically when you flash the ROM. The boot.img is the kernel, without flashing the kernel the phone wouldn't even boot. This is why I've been telling you that I don't think it's the boot.img that's causing your problem, and why I suggested you flash the stock images with fastboot. I say these things for a reason.
Click to expand...
Click to collapse
What controls the outside-rom charging animation then? Or did TWRP or the Nightlies change it?
Edit: After some searching I found out it's part of the bootloader. Something I've never messed with!
Sent from my A0001 using Tapatalk
Related
First of all, I heard that Google had an API error in 4.1.2 that causes the mobile data or internet data to consume twice as fast. Which means you use 2x more data compared to normal. Is this true? and has it been fixed in CM10?
Secondly, if I am going to flash a new ROM, do I have to flash the ROM first then flash the boot.img separately? Or just flash everything together in the recovery? When should I flash the boot.img separately? I am kinda new to this new phones I so don't know about much these things.
Sent from my One X using xda premium
You only need to flash boot.img separately if you are on hboot 1.14 or higher. Otherwise, it will just flash in TWRP automatically when you flash the ROM.
Don't know about your other questions.
That's "tons" of questions??? That's just 2!
CalamitySir said:
First of all, I heard that Google had an API error in 4.1.2 that causes the mobile data or internet data to consume twice as fast. Which means you use 2x more data compared to normal. Is this true? and has it been fixed in CM10?
Secondly, if I am going to flash a new ROM, do I have to flash the ROM first then flash the boot.img separately? Or just flash everything together in the recovery? When should I flash the boot.img separately? I am kinda new to this new phones I so don't know about much these things.
Sent from my One X using xda premium
Click to expand...
Click to collapse
Where did you hear that? Seems like bs because your carrier measures the amount of data on their servers
If you have hboot 1.14 then you have to flash the boot.IMG separately after you flash the ROM
Otherwise you flash everything in recovery all at once
Sent from my One X using Tapatalk 2
superchilpil said:
Where did you hear that? Seems like bs because your carrier measures the amount of data on their servers
If you have hboot 1.14 then you have to flash the boot.IMG separately after you flash the ROM
Otherwise you flash everything in recovery all at once
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Then how do I downgrade the hboot?
Another question is that when I tried to flash 4.1.1 ROMs when coming from 4.1.2 Roms, it stuck in the boot logo.
Sent from my One X using xda premium
You'll pretty much have to flash boot.IMG seperate every time... Or it will boot loop.
Sent from my One X using Tapatalk 2
InflatedTitan said:
You'll pretty much have to flash boot.IMG seperate every time... Or it will boot loop.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
ok now the question is, do i flash the boot.img first then flash the rom or flsah the rom first then the boot.img??!! The latter method was reccomendded by devs in the HOX section and the former one was used in ours?
I tried ROM then kernel on my cousins phone... Bootlooped.. Started fresh, flashed kernel then ROM and works perfectly every time
Sent from my One X using Tapatalk 2
Another question is the ss below, the total amount of data doesn't add up correctly....is this a bug or was it already predetermined like this?
Sent from my One X using xda premium
CalamitySir said:
Then how do I downgrade the hboot?
Click to expand...
Click to collapse
Tool here (but requires a Linux machine): http://forum.xda-developers.com/showthread.php?t=1982442
The total amount of data doesn't add up. Is this a bug in CM10?
Sent from my One X using xda premium
I'm still not seeing the "tons" of questions.
iElvis said:
I'm still not seeing the "tons" of questions.
Click to expand...
Click to collapse
maybe u cna help me answer the question regarding the data in page one, i have 2 screenshots for that.
Another question is how do i flash the b6 kernel for cm10? flash like normal in twrp or flash the boot.img? i am messed up!
CalamitySir said:
maybe u cna help me answer the question regarding the data in page one, i have 2 screenshots for that.
Another question is how do i flash the b6 kernel for cm10? flash like normal in twrp or flash the boot.img? i am messed up!
Click to expand...
Click to collapse
I have heard only that there may be a bug in CM that makes your data usage appear to be worse. That's all I know.
I have never used CM so I can't help with the kernel. If you're on 1.14 you have to flash it separately in fastboot.
iElvis said:
I have heard only that there may be a bug in CM that makes your data usage appear to be worse. That's all I know.
I have never used CM so I can't help with the kernel. If you're on 1.14 you have to flash it separately in fastboot.
Click to expand...
Click to collapse
ok. does fastboot makes me unable to downgrade the android version, i tried to flash 4.1.1 from 4.1.2, i did it separately and it didnt work, stuck at bootloop... any idea?
Well you have to flash the boot.img from the 4.1.1 rom. Maybe try flashing the older gapps http://goo.im/gapps/gapps-jb-20120726-signed.zip I would also wipe cache, dalvik and system. Use flashimagegui for kernel flashing so you dont need to use fastboot and a pc http://forum.xda-developers.com/showthread.php?t=1963896
Here's what I do and I have flashed every ROM in this section without a single boot loop.
Flash boot IMG in fast boot
Reboot to recovery
Wipe dalvik and cache
Wipe system
Factory reset
Flash rom and gapps or just ROM (sense)
Reboot system
Do I do steps I don't need? Perhaps. But the results are hard to argue
Sent from my One X using xda app-developers app
smolck said:
Here's what I do and I have flashed every ROM in this section without a single boot loop.
Flash boot IMG in fast boot
Reboot to recovery
Wipe dalvik and cache
Wipe system
Factory reset
Flash rom and gapps or just ROM (sense)
Reboot system
Do I do steps I don't need? Perhaps. But the results are hard to argue
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
do i have to follow this sequence to wipe everytime?
Usually if its same rom u dont need to factory reset[wipe data] but ive been wiping system alot each time though.
Hello guys,
I've been looking around for CM11 for my HTC One X+.
Now I've found the original CM11 on their website for HOX+, but there is one little question I got about this.
http://download.cyanogenmod.org/?device=enrc2b
That's the link where I've found it by the way.
There is no boot.img download, how safe is it to just install the ROM? In my opinion it isn't.
So let me know what you guys think.
Sent from my HOX+
NiZii. said:
Hello guys,
I've been looking around for CM11 for my HTC One X+.
Now I've found the original CM11 on their website for HOX+, but there is one little question I got about this.
http://download.cyanogenmod.org/?device=enrc2b
That's the link where I've found it by the way.
There is no boot.img download, how safe is it to just install the ROM? In my opinion it isn't.
So let me know what you guys think.
Sent from my HOX+
Click to expand...
Click to collapse
Its on the official website, and It should work. Make a backup though.
The boot.img download isn't there because the boot.img is probably inside the .zip.
So open the zip and you'll have your boot.img.
Sent from my Nexus 5 using Tapatalk
krishneelg3 said:
Its on the official website, and It should work. Make a backup though.
The boot.img download isn't there because the boot.img is probably inside the .zip.
So open the zip and you'll have your boot.img.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah, already found it.
Thanks though.
One small question, if I'm going to put the .zip file on my SD card I can just leave the boot.img in the .zip right?
Sent from my HOX+
NiZii. said:
Yeah, already found it.
Thanks though.
One small question, if I'm going to put the .zip file on my SD card I can just leave the boot.img in the .zip right?
Sent from my HOX+
Click to expand...
Click to collapse
Well is your device s-off or s-on?
Sent from my Nexus 5 using Tapatalk
krishneelg3 said:
Well is your device s-off or s-on?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
S-On, after hours of searching how to put S-Off I gave that up. Since I can't find it for my HTC One X+.
Sent from my HOX+
NiZii. said:
S-On, after hours of searching how to put S-Off I gave that up. Since I can't find it for my HTC One X+.
Sent from my HOX+
Click to expand...
Click to collapse
Oh okay, you will need to flash the boot.img alone then as flashing the ROM zip won't just work. So boot into bootloader, and flash the new boot.img you had extracted from the .zip
Once yo uhave flashed the .img boot into recovery mode and perform a gull wipe, including cache. Once done simply flash the zip and reboot.
First reboot takes a bit so be patient. I also recommend you getting a band backup in case.
Sent from my Nexus 5 using Tapatalk
krishneelg3 said:
Oh okay, you will need to flash the boot.img alone then as flashing the ROM zip won't just work. So boot into bootloader, and flash the new boot.img you had extracted from the .zip
Once yo uhave flashed the .img boot into recovery mode and perform a gull wipe, including cache. Once done simply flash the zip and reboot.
First reboot takes a bit so be patient. I also recommend you getting a band backup in case.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ye I know it takes a lot of time since I've been flashing a ROM once before, but I can just leave the file in the .zip when flashing it in recovery?
Sent from my HOX+
NiZii. said:
Ye I know it takes a lot of time since I've been flashing a ROM once before, but I can just leave the file in the .zip when flashing it in recovery?
Sent from my HOX+
Click to expand...
Click to collapse
Yeah I suppose you can. Nothing will happen.
Sent from my Nexus 5 using Tapatalk
krishneelg3 said:
Yeah I suppose you can. Nothing will happen.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Okay thanks.
Sent from my HOX+
NiZii. said:
Okay thanks.
Sent from my HOX+
Click to expand...
Click to collapse
No worries.
All the best.
Sent from my Nexus 5 using Tapatalk
If you're coming from a Sense ROM you can't just flash the zip without flashing the boot.img. It wouldn't even boot. And sometimes it boots but without mobile signal or WiFi signal.
So just place the zip on your sdcard, take the boot.img out of the zip on your computer.. Then boot into bootloader and connect it to the computer using USB then type
"fastboot flash boot boot.img"
Then "fastboot erase cache"
(you must have fastboot installed and configured on your computer)
Then boot into recovery and flash the zip file and gapps. Oh don't forget a wipe is mandatory if you're coming from sense ROM. But if you're coming from an AOSP ROM it's recommended but you can go without wiping. I flashed cyanogen over paranoid android without wiping data and had no issues at all. But I wiped the system partition.
And you cannot S-OFF an HTC One X+.. If it's S-ON then it stays that way. Only a few amount of people have S-OFF on their HOX+.
Oh and I don't think TWRP recovery is compatible with CM11 on HOX+.. So I recommend you flash philz recovery. Flash it by using the fastboot command "fastboot flash recovery recovery.img"
(recovery.img should be replaced with the name of the recovery you downloaded)
It doesn't take a lot of time. I change ROMs almost every week.
Please press the thanks button if I helped!
Sent from my One X+ using XDA Premium 4 mobile app
backb0ne5p1d0r said:
If you're coming from a Sense ROM you can't just flash the zip without flashing the boot.img. It wouldn't even boot. And sometimes it boots but without mobile signal or WiFi signal.
So just place the zip on your sdcard, take the boot.img out of the zip on your computer.. Then boot into bootloader and connect it to the computer using USB then type
"fastboot flash boot boot.img"
Then "fastboot erase cache"
(you must have fastboot installed and configured on your computer)
Then boot into recovery and flash the zip file and gapps. Oh don't forget a wipe is mandatory if you're coming from sense ROM. But if you're coming from an AOSP ROM it's recommended but you can go without wiping. I flashed cyanogen over paranoid android without wiping data and had no issues at all. But I wiped the system partition.
And you cannot S-OFF an HTC One X+.. If it's S-ON then it stays that way. Only a few amount of people have S-OFF on their HOX+.
Oh and I don't think TWRP recovery is compatible with CM11 on HOX+.. So I recommend you flash philz recovery. Flash it by using the fastboot command "fastboot flash recovery recovery.img"
(recovery.img should be replaced with the name of the recovery you downloaded)
It doesn't take a lot of time. I change ROMs almost every week.
Please press the thanks button if I helped!
Sent from my One X+ using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey i have htc one m7_ul and when ever i tried to flash cyanogenmod i ended up with so error like some binary problem do you know the fix for it???
Aisfkhan said:
Hey i have htc one m7_ul and when ever i tried to flash cyanogenmod i ended up with so error like some binary problem do you know the fix for it???
Click to expand...
Click to collapse
Whats the error exactly ? and where did you get the error ?
backb0ne5p1d0r said:
Whats the error exactly ? and where did you get the error ?
Click to expand...
Click to collapse
Its in twrp 2.6.3.3 and about some extracting binary failed error but now solved i flashed the boot.img file from cm11.zip file then flashed from philz recovery and everything goes fine
Basically, my userdata partition keeps getting corrupted every couple of flashes. I have to factory flash to get everything working again. It just started happening recently(A few hours ago). What is going on? Thanks!
While flashing the stock images make sure you have also Erased cache partition and formatted it using stock recovery.. I was exactly in the same spot as you were few weeks ago and a cache partition format solved it completely!
Koopa777 said:
Basically, my userdata partition keeps getting corrupted every couple of flashes. I have to factory flash to get everything working again. It just started happening recently(A few hours ago). What is going on? Thanks!
Click to expand...
Click to collapse
I had the same problem as you. I used this guide and now it works great. Just follow the steps. Good luck.
prabs99 said:
I had the same problem as you. I used this guide and now it works great. Just follow the steps. Good luck.
Click to expand...
Click to collapse
I can actually confirm that it is an issue with ParanoidAndroid. It always corrupts the data partition following boot. I repeated it with continued success.
Sent from my Nexus 5 using Tapatalk
Koopa777 said:
I can actually confirm that it is an issue with ParanoidAndroid. It always corrupts the data partition following boot. I repeated it with continued success.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You're the only one saying such things. If there was a problem with the ROM we would have heard it from others and the team would see the same issues.
The ROM ships with stock Google kernel. The ROM doesn't do anything in itself that could corrupt your userdata
Sent from my Nexus 5
Pirateghost said:
You're the only one saying such things. If there was a problem with the ROM we would have heard it from others and the team would see the same issues.
The ROM ships with stock Google kernel. The ROM doesn't do anything in itself that could corrupt your userdata
Sent from my Nexus 5
Click to expand...
Click to collapse
I've come to the conclusion, after 4(!) factory images, that the ROM DEFINITELY corrupts the recovery. I have a 100% success(failure?) rate when flashing PA. Clean md5, after first boot the ROM functions properly, but recovery fails to mount the userdata partition, every time. Flash a new recovery, or adb shell and attempt to repair don't work. I understand that it doesn't make sense, but it's obviously something that's happening with the ROM. After 4 factory images, the only other factors are the recovery(PhilZ, TWRP, AND CWM all fail) being borked from the start, or the ROM. It's obviously not the recovery(all 3 have clean md5s, are transferred with adb push, and function perfectly otherwise).....
Again, in the ROM I can r/w to the /data, so the partition is fine, but the ROM borks the recovery.
But there is nothing in the ROM that would cause that. Are you restoring anything from previous versions? Are you installing an app that does this?
Sent from my Nexus 5
Pirateghost said:
But there is nothing in the ROM that would cause that. Are you restoring anything from previous versions? Are you installing an app that does this?
Sent from my Nexus 5
Click to expand...
Click to collapse
No and no. I don't even install Gapps. The ROM alone still triggers it. I just boot into system then boot to recovery.
Sent from my Nexus 5 using Tapatalk
Koopa777 said:
No and no. I don't even install Gapps. The ROM alone still triggers it. I just boot into system then boot to recovery.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
This sounds like you have a hardware issue. Did it do this on stock image with custom recovery?
Sent from my Nexus 5
Pirateghost said:
This sounds like you have a hardware issue. Did it do this on stock image with custom recovery?
Sent from my Nexus 5
Click to expand...
Click to collapse
No. I can flash different ROMs, kernels, etc. Just not PA. The only thing of note was that my stock backup bootlooped when restoring with TWRP, but other than that no.
Sent from my Nexus 5 using Tapatalk
Nevermind, I just flashed liquidsmooth+Elementalx with PhilZ and it happened again. So what exactly is going on?
Are you not able to repair the corrupted partition as explained in the linked thread?
Sent from my Nexus 5
Pirateghost said:
Are you not able to repair the corrupted partition as explained in the linked thread?
Sent from my Nexus 5
Click to expand...
Click to collapse
Nope. Adb shell in Philz says repair failed. I found this
http://forum.xda-developers.com/google-nexus-5/help/unable-to-mount-data-issue-t2723993
http://forum.xda-developers.com/google-nexus-5/help/recovery-mount-data-t2639945
But neither helps. Recovery still can not mount /data.
I would RMA it.
Sent from my Nexus 5
I would try LG Flashtool it worked for me.
maxal said:
I would try LG Flashtool it worked for me.
Click to expand...
Click to collapse
Seriously? I have the LGFT installed(G2 owner) too. Hm......So basically get the tot and dll, and flash? COM41 and all that jazz?
Koopa777 said:
Seriously? I have the LGFT installed(G2 owner) too. Hm......So basically get the tot and dll, and flash? COM41 and all that jazz?
Click to expand...
Click to collapse
Yup, here is the link http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
I just called Google. RMA is inbound. It just kind of sucks, this phone was solid. No light bleed, no dead pixels, etc. Except for a loose power button.
Anyway I think it is definately a hardware issue, as my phone has been getting crazy hot lately. I know it's supposed to get hot, but this phone was scorching...Might have fried something.
I have flashed ROMs a few times before on a couple different devices, but I have a couple questions.
1. When I try to flash a OnePlus One CM11 Nightly through TWRP, it always says "Failed". Is there some simple thing that I am forgetting to do?
2. Will it erase anything that is currently on my phone by flashing a nightly? (I don't care if I have to re-root, but I don't want it to erase anything)
Thanks!
ecrab1 said:
I have flashed ROMs a few times before on a couple different devices, but I have a couple questions.
1. When I try to flash a OnePlus One CM11 Nightly through TWRP, it always says "Failed". Is there some simple thing that I am forgetting to do?
2. Will it erase anything that is currently on my phone by flashing a nightly? (I don't care if I have to re-root, but I don't want it to erase anything)
Thanks!
Click to expand...
Click to collapse
It won't erase anything from your virtual sd card. Of course you should wipe system/data/cache/dalvik cache when installing a ROM. Did you check the md5 of the ROM zip after downloading it? What's the full filename of the ROM zip?
Transmitted via Bacon
timmaaa said:
It won't erase anything from your virtual sd card. Of course you should wipe system/data/cache/dalvik cache when installing a ROM. Did you check the md5 of the ROM zip after downloading it? What's the full filename of the ROM zip?
Transmitted via Bacon
Click to expand...
Click to collapse
Have you unlocked the bootloader?
Yup!
Sent from my A0001 using XDA Free mobile app
How to see if i have a locked bootloader?
Okay, thanks. And what is the point of wiping the system/data if it is essentially the same ROM?
Sent from my A0001 using XDA Free mobile app
Enea307 said:
How to see if i have a locked bootloader?
Click to expand...
Click to collapse
Code:
fastboot oem device-info
But wouldn't you be aware if you unlocked it?
ecrab1 said:
Okay, thanks. And what is the point of wiping the system/data if it is essentially the same ROM?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Because it isn't the same ROM. CM11S and CM11 are similar but not identical.
Transmitted via Bacon
ecrab1 said:
I have flashed ROMs a few times before on a couple different devices, but I have a couple questions.
1. When I try to flash a OnePlus One CM11 Nightly through TWRP, it always says "Failed". Is there some simple thing that I am forgetting to do?
2. Will it erase anything that is currently on my phone by flashing a nightly? (I don't care if I have to re-root, but I don't want it to erase anything)
Thanks!
Click to expand...
Click to collapse
If you don't wipe your device it will fail on installing the zip. I am using TWRP and it failed no matter what unless I wiped first. You do not have to wipe you "sdcard" but you will lose your apps. I tried doing a data restore through TWRP and no matter what it would just hang on boot after. I ended up doing a backup through titanium backup and then restored after and it brought pretty much everything over including game data.
There might be a way around this in CWM, but I can say with some confidence there is not using TWRP. It's kind of a bad idea not to do a wipe before flashing a different rom anyways.
inaudible101 said:
If you don't wipe your device it will fail on installing the zip. I am using TWRP and it failed no matter what unless I wiped first. You do not have to wipe you "sdcard" but you will lose your apps. I tried doing a data restore through TWRP and no matter what it would just hang on boot after. I ended up doing a backup through titanium backup and then restored after and it brought pretty much everything over including game data.
There might be a way around this in CWM, but I can say with some confidence there is not using TWRP. It's kind of a bad idea not to do a wipe before flashing a different rom anyways.
Click to expand...
Click to collapse
Well, I may try with Titanium later. Thank you!!
timmaaa said:
Code:
fastboot oem device-info
But wouldn't you be aware if you unlocked it?
Because it isn't the same ROM. CM11S and CM11 are similar but not identical.
Transmitted via Bacon
Click to expand...
Click to collapse
He may not know if he was successful in unlocking it.
And that makes sense about them being different. I just wish there was a way around it. They are more similar than the next OTA probably.
I wish I could just do a NANDROID backup and try it, but oh well.
I am running stock, latest stage fright update with stock recovery and s-off. I would like to try the GPE rom, what are the steps I need to flash this rom? I have read the thread but still need a little guidance. Any help would be appreciated. Thanks
Sent from my Nexus 6 using Tapatalk
luvtorev01 said:
I am running stock, latest stage fright update with stock recovery and s-off. I would like to try the GPE rom, what are the steps I need to flash this rom? I have read the thread but still need a little guidance. Any help would be appreciated. Thanks
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/ver...ment/rom-vzw-stock-gpe-5-1-lmy47o-h9-t3212413
Just as the instructions state:
Install: TWRP custom recovery is recommended
1. Reboot to TWRP custom recovery
2. Wipe/Factory reset if coming from another ROM
3. Flash ROM
4. Reboot
5. Enjoy, First boot will take 5 to 10 minutes
You may want to flash a sense ROM first and get a lock on GPS, some people have had an issue with GPS on GPE ROM, however I didn't have this issue, but I did come from a Sense ROM.
You are already on Sense ROM, so just do a lock on GPS, make sure it works, then go ahead, flash custom recovery TWRP, download the ROM of choice, reboot to recovery, wipe, flash ROM.
andybones said:
http://forum.xda-developers.com/ver...ment/rom-vzw-stock-gpe-5-1-lmy47o-h9-t3212413
Just as the instructions state:
Install: TWRP custom recovery is recommended
1. Reboot to TWRP custom recovery
2. Wipe/Factory reset if coming from another ROM
3. Flash ROM
4. Reboot
5. Enjoy, First boot will take 5 to 10 minutes
You may want to flash a sense ROM first and get a lock on GPS, some people have had an issue with GPS on GPE ROM, however I didn't have this issue, but I did come from a Sense ROM.
You are already on Sense ROM, so just do a lock on GPS, make sure it works, then go ahead, flash custom recovery TWRP, download the ROM of choice, reboot to recovery, wipe, flash ROM.
Click to expand...
Click to collapse
Thank you. So just to make sure I am on sense stock and from here just install twrp and wipe and flash rom? Do I need to worry about installing a different firmware?
Sent from my Nexus 6 using Tapatalk
luvtorev01 said:
Thank you. So just to make sure I am on sense stock and from here just install twrp and wipe and flash rom? Do I need to worry about installing a different firmware?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Nope just make sure to be on latest Verizon firmware.
andybones said:
Nope just make sure to be on latest Verizon firmware.
Click to expand...
Click to collapse
I just have s-off but not rooted, can you send me to right direction for that? Thanks again
Sent from my HTC6525LVW using Tapatalk
luvtorev01 said:
I just have s-off but not rooted, can you send me to right direction for that? Thanks again
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
The ROM comes rooted.
andybones said:
The ROM comes rooted.
Click to expand...
Click to collapse
I get it, but how can I install twrp recovery if I'm not rooted?
Sent from my HTC6525LVW using Tapatalk
luvtorev01 said:
I get it, but how can I install twrp recovery if I'm not rooted?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
You don't need root to install custom recovery.. Just S-OFF.
have you looked at the TWRP thread?
You need to know how to use adb and fastboot
Reboot to fastboot
Put custom twrp.img in adb folder
Run cmd:
Fastboot flash recovery nameoffile.img
A little research goes along way..
Google and searching is your friend.
andybones said:
You don't need root to install custom recovery.. Just S-OFF.
have you looked at the TWRP thread?
You need to know how to use adb and fastboot
Reboot to fastboot
Put custom twrp.img in adb folder
Run cmd:
Fastboot flash recovery nameoffile.img
A little research goes along way..
Google and searching is your friend.
Click to expand...
Click to collapse
Thanks for this and you are right Google is a friend but you seem on point with everything so I figure I would ask you. Thank you for your time.
Sent from my HTC6525LVW using Tapatalk
luvtorev01 said:
Thanks for this and you are right Google is a friend but you seem on point with everything so I figure I would ask you. Thank you for your time.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
More than welcome. If need anymore help let me know. :good: