Hi all,
I decided to take the leap of faith and N4 convert my LGOG the other day. Everything worked and it's awesome. Big thanks to the devs for that impressive hack.
After getting bored of stock N4, I decided to flash the cm 10.1 nightly found in the LGOG Android development thread. I backed up stock N4 in sk8's CWM 6.0.2.7. Now I want to try another N4 rom like PA 2.99, but I can't find my backup of N4 stock. I can see it in sdcard/clockworkmod/backups in Root explorer, but when I go into CWM, I cant see the backup.
So I now have two questions.
1) Do I need to find my N4 backup in order to flash another N4 rom? Or can I merely factory reset and flash a N4 rom in CWM?
2) If I do need to restore N4 stock first, has anyone else had problems locating/ know where to find CWM backups?
Thanks,
Brad
You only need to factory reset and flash a new rom, just like flashing any other rom normally. What recovery are you running?
Sent from my LG-E970 using Tapatalk 2
Awesome! I'm using sk8's custom CWM 6.0.2.7 for LGOG.
bwint1 said:
Awesome! I'm using sk8's custom CWM 6.0.2.7 for LGOG.
Click to expand...
Click to collapse
Alright, you can try flashing a new rom with that but if it comes up with an error try flashing a Nexus 4 recovery (cwm or twrp) then flash the rom then re-flash sk8's CWM.
Jakeroxs said:
Alright, you can try flashing a new rom with that but if it comes up with an error try flashing a Nexus 4 recovery (cwm or twrp) then flash the rom then re-flash sk8's CWM.
Click to expand...
Click to collapse
Many rom installer scripts check device/build name before proceeding with an update. sk8's cwm uses 'geeb' while Nexus 4 is 'mako'.
If flashing a Nexus 4 rom in sk8's cwm gives you an error, unzip the rom and check '/META-INF/com/google/android/update-script'.
If it begins with:
assert(getprop("ro.product.device") == "mako" || getprop("ro.build.product") == "mako");
then remove this string and repack the zip. You should be able to install it in sk8's cwm.
So you can still take advantage of sk8's cwm to access external sd card.
dvhexer said:
Many rom installer scripts check device/build name before proceeding with an update. sk8's cwm uses 'geeb' while Nexus 4 is 'mako'.
If flashing a Nexus 4 rom in sk8's cwm gives you an error, unzip the rom and check '/META-INF/com/google/android/update-script'.
If it begins with:
assert(getprop("ro.product.device") == "mako" || getprop("ro.build.product") == "mako");
then remove this string and repack the zip. You should be able to install it in sk8's cwm.
So you can still take advantage of sk8's cwm to access external sd card.
Click to expand...
Click to collapse
If I do this, will it brick my phone? What confuses me is that my phone is recognized as LGOG running CM 10.1, but if I factory reset, does it go back to being a nexus 4?
bwint1 said:
If I do this, will it brick my phone? What confuses me is that my phone is recognized as LGOG running CM 10.1, but if I factory reset, does it go back to being a nexus 4?
Click to expand...
Click to collapse
No you won't brick your phone.
Yes, if you flash anything other then the CM10.1 linked in our forums it will be displayed as a Nexus 4. This is because Sk8 did some slight changes to make the rom work better for our phone.
Jakeroxs said:
No you won't brick your phone.
Yes, if you flash anything other then the CM10.1 linked in our forums it will be displayed as a Nexus 4. This is because Sk8 did some slight changes to make the rom work better for our phone.
Click to expand...
Click to collapse
^^^^ This
Nexus 4 roms are safe if you're N4 converted.
Just don't try to install anything other than Nexus 4 roms: like The Base, Nocturnal etc. For these you need to return to stock LGOG rom using LGNPST
Reverting to Stock LGOG
Has anyone had any success reverting back to stock with LGNPST? I seem to be unable to get the phone into download mode since making the N4 conversion. Any insight here would be greatly appreciated.
Related
I can't escape TWRP!
My setup is this:
ROM: THS build 10
Kernel: ICYGlitch v14
Recovery: TWRP (included with ICYGlitch)
Recently, I wanted to flash ParanoidAndroid. I rebooted into TWRP via the power menu, made a backup, and tried to flash. It gave the error E: signature verification failed. Later, I tried turning off signature verification, but then it gave me another error. I then tried to flash cwm4_fixed_for_cm7, but it gave me the same error. Then I tried flashing the recovery through ODIN. It said it succeeded, but it still loads TWRP as the recovery. Help! I can't escape!
P.S. I know my way around the Fascinate, I'm not a complete noob.
try flashing cm7, then back to ICS, ...if all else fails odin back to stock start over.
Maybe
That would work, but I'd rather keep the Glitch kernel and stay on THS than start over. And there must be a way to change the recovery included with Glitch?
Let us know how that turns out for you. Good luck.
Sent from my SCH-I500 using Tapatalk
MultipleMonomials said:
That would work, but I'd rather keep the Glitch kernel and stay on THS than start over. And there must be a way to change the recovery included with Glitch?
Click to expand...
Click to collapse
flash a older version of glitch that still utilizes cwm recovery. check my kernels section of the guide.
That would work except for the fact that I cannot flash anything from TWRP.
MultipleMonomials said:
That would work except for the fact that I cannot flash anything from TWRP.
Click to expand...
Click to collapse
odin cwm4 fixed for cm7, then three finger and flash away.
Wait. Doesn't three-fingering on a MTD filesystem bootloop you?
at this point just odin back to stock and start over
shelby04861 said:
Let us know how that turns out for you. Good luck.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Sent from my SCH-I500 using Tapatalk
I figured it out. I was able to flash an older version of Glitch with CWM recovery.
How did you flash an older version of glitch in cwm if you were stuck in twrp? I though you couldnt flash anything. I am confused???
Sent from my SCH-I500 using Tapatalk
Sorry. I meant TWRP. Here is the procedure that I used. I don't know if it is necessary, but it worked.
1. make a nandroid
2. restore to stock
3. ODIN cwm
4. install THS build 1
5. install THS 10 (substitute whatever ROM you're using)
6. install newest Glitch (with TWRP)
7. restore nandroid
8. install older, CWM glitch
I think this works because nandroids don't restore the recovery partition.
I was having instability with the older Glitch version, so I flashed the newer version again, and I can still flash stuff.
Okay. I got it now. I thought the whole reason you didn't want to start over was because you didn't have a backup of your current setup. That is why people were saying that you were going to have to start over.
Glad it worked out.
Sent from my SCH-I500 using Tapatalk
Hello people
I recently tried installing CyanogenMod 10 on my intl Galaxy Player 5.0.
http://forum.xda-developers.com/showthread.php?t=2077671
Some things about my phone:
I recently rooted it and i am able to enter download or recovery mode, i have the intl model and im currently running:
This ROM:http://forum.xda-developers.com/showthread.php?t=1623529
And this KERNEL:http://forum.xda-developers.com/showthread.php?t=1414565
Everytime i get an assert failed error (yes formatting does not help.....) and when installing the kernel within the thread i bricked my phone....
I was able to recover it but i dont wanna brick my phone again so any help and/or detailted instructions how to get that rom installed would be appreciated.
When i was trying to flash, thought it was with Odin. My programme crashed upon NaNDwrite....
Thanks in advance, hope someone can help me out!
Maarten0009 said:
Hello people
I recently tried installing CyanogenMod 10 on my intl Galaxy Player 5.0.
http://forum.xda-developers.com/showthread.php?t=2077671
Some things about my phone:
I recently rooted it and i am able to enter download or recovery mode, i have the intl model and im currently running:
This ROM:http://forum.xda-developers.com/showthread.php?t=1623529
And this KERNEL:http://forum.xda-developers.com/showthread.php?t=1414565
Everytime i get an assert failed error (yes formatting does not help.....) and when installing the kernel within the thread i bricked my phone....
I was able to recover it but i dont wanna brick my phone again so any help and/or detailted instructions how to get that rom installed would be appreciated.
When i was trying to flash, thought it was with Odin. My programme crashed upon NaNDwrite....
Thanks in advance, hope someone can help me out!
Click to expand...
Click to collapse
Umm, if I'm understanding correctly, you installed the ROM- CM10, that is- and/or kernel via Odin. CM10 and the Mercurius kernel are zip files (.tar, .pit and the like are for Odin, not zips...if I understood correctly).
You want to place the ROM and the GAPPS zips on your actual SD card. Make sure the SD card is working properly. Reset and go to CWM (Power+Vol up).
Then, accd to the instructions on the CM10 page:
"Installation:
Reboot to CWM
Make a Nandroid (optional, but recommended)
Format /system if you had a different GApps package installed
Install ROM
Install GAPPS if you just formatted /system
Wipe data/factory reset if you are coming from Gingerbread
Reboot
??? (wait a while...)
Profit"
I'd say make a backup before doing any of this, but I'm assuming you're beyond that point....But before going on to CM10, it might be a good idea to recover your device first and back it up. Maybe flash a GB rom via CWM or Odin before proceeding to CM10, making a backup just in case...
Ok
alljokingaside said:
Umm, if I'm understanding correctly, you installed the ROM- CM10, that is- and/or kernel via Odin. CM10 and the Mercurius kernel are zip files (.tar, .pit and the like are for Odin, not zips...if I understood correctly).
You want to place the ROM and the GAPPS zips on your actual SD card. Make sure the SD card is working properly. Reset and go to CWM (Power+Vol up).
Then, accd to the instructions on the CM10 page:
"Installation:
Reboot to CWM
Make a Nandroid (optional, but recommended)
Format /system if you had a different GApps package installed
Install ROM
Install GAPPS if you just formatted /system
Wipe data/factory reset if you are coming from Gingerbread
Reboot
??? (wait a while...)
Profit"
I'd say make a backup before doing any of this, but I'm assuming you're beyond that point....But before going on to CM10, it might be a good idea to recover your device first and back it up. Maybe flash a GB rom via CWM or Odin before proceeding to CM10, making a backup just in case...
Click to expand...
Click to collapse
Well, i did not use the .zip on odin, i flashed the alternate kernel linked.
So i googled a bit and found out i needed CWM6 for CM10, but im running CWM5. How can i update this? on the site i couldnt find the Galaxy Player supported! thnx in advance
Maarten0009 said:
Well, i did not use the .zip on odin, i flashed the alternate kernel linked.
So i googled a bit and found out i needed CWM6 for CM10, but im running CWM5. How can i update this? on the site i couldnt find the Galaxy Player supported! thnx in advance
Click to expand...
Click to collapse
Just flash CM10 kernel zip
http://forum.xda-developers.com/showthread.php?t=2109674
from CWM5 and then reboot CMW and you will have CWM6..then just install CM10 rom.
Sent from my Nexus 7 using xda app-developers app
would he have to flash the kernel first, though? I'm unfamiliar with rjs, but am assuming that rjs version of CWM would be identical to entropys version of CWM, which means that he could just flash the CM10 ROM since it has the kernel baked in.
When I upgraded from Chip -> CM10, I just flashed via CWM, upgrading both the ROM and CWM in the process.
alljokingaside said:
would he have to flash the kernel first, though? I'm unfamiliar with rjs, but am assuming that rjs version of CWM would be identical to entropys version of CWM, which means that he could just flash the CM10 ROM since it has the kernel baked in.
When I upgraded from Chip -> CM10, I just flashed via CWM, upgrading both the ROM and CWM in the process.
Click to expand...
Click to collapse
i used rj's kernel and had to go from GB to ICS to JB or else i would get an assert error
iurnait said:
i used rj's kernel and had to go from GB to ICS to JB or else i would get an assert error
Click to expand...
Click to collapse
I remember Dkonzig mentioning this, that the path to JB was through ICS, but for my US device, I just flashed directly to GB. I remember another Int'l GB user who flashed directly to JB and was fine. this is peculiar.
so two methods to choose from, I suppose.
I'm used to just rooting and then using ROM Manager to get CWM on other devices.
(Or using ODIN and a .tar)
I'm only seeing .zips for Kernels/ROMs which as far as I know are only installable by a (custom?) recovery.
Can I just use the built in recovery to flash a Kernel/ROM?
However for i777 I see everyone is saying ROM Manager leads to a lot of problems.
I've seen that for s2 the kernels come with CWM (or a custom recovery) attached to them already?
I'm just seeing old and outdated posts, and the stickies don't make it terribly clear either.
So after rooting, what would the next steps be if I wanted to install CWM?
I assume Odin/Tar method? Can someone show me the latest tar to flash?
After that I could use CWM as usual to install a ROM such as CM 10(.1) or Task650 AOKP correct?
E:
Now I'm seeing inside of the .zips there is a Zimage (for this Kernel http://forum.xda-developers.com/showthread.php?t=1592228) and that I can safely flash that file using ODIN?
Would this also (in most cases/for most Kernels) also contain CWM or some type of custom recovery?
like the stickies explain, recovery is packed with the kernel. if you are rooted already, use mobile odin to flash the zimage. otherwise, use a tar file with regular odin to flash a custom kernel....
Okay so after root, use Mobile ODIN to flash the ZImage file found in the .zip of any kernel file?
Do ALL S2 kernels come with a custom recovery?
http://forum.xda-developers.com/showthread.php?t=1592228 I believe that
4.1beta4 Change Log
■Linux 3.0.40
■CWM-Based Touch Recovery v6.0.1.1
Click to expand...
Click to collapse
Means that it comes with CWM Touch 6.0.1.1?
all custom kernels pack a recovery. its pretty much mandatory here in the i777
Pirateghost said:
all custom kernels pack a recovery. its pretty much mandatory here in the i777
Click to expand...
Click to collapse
Okay thank you, just used to i747 things so this is very new to me.
What would be the proper order to move from a ICS to JB?
Flash ICS Kernel.
Flash JB ROM via CWM.
Flash JB Kernel (If I wish to use a different one that what the ROM comes from).
And just to double check, I just flash the ZImage via Mobile Odin and I'm golden?
Once you got cwm you are good to go.
Following intructions from rom's op make it safer.
Usually factory reset + flash rom.
Sent from my SGH-I777 using xda app-developers app
YoHoJo said:
Okay thank you, just used to i747 things so this is very new to me.
What would be the proper order to move from a ICS to JB?
Flash ICS Kernel.
Flash JB ROM via CWM.
Flash JB Kernel (If I wish to use a different one that what the ROM comes from).
And just to double check, I just flash the ZImage via Mobile Odin and I'm golden?
Click to expand...
Click to collapse
All correct. Make sure to wipe before flashing roms
Sent from my GS4 running CM11 Kandy Kane
I don't know if it still bears true or not but AFAIK, if your currently running GB OS, then you need to flash GB kernel, not ICS kernel and vice versa.
votinh said:
I don't know if it still bears true or not but AFAIK, if your currently running GB OS, then you need to flash GB kernel, not ICS kernel and vice versa.
Click to expand...
Click to collapse
As far as recovery goes, it shouldn't make any difference. An ICS kernel with a GB rom will not boot, but it will still boot into recovery.
Correct. If you're just flashing a kernel to gain cwm recovery it doesn't matter as you're not booting into the OS with that kernel installed.
http://wiki.cyanogenmod.org/w/Install_CM_for_i777 this method worked perfectly for me
Do. Not. Use. Rom. Manager.
the above method seems to initially just boot cwm, i didn't try to flash the zip again in cwm to see if it sticks.
DvineLord said:
the above method seems to initially just boot cwm, i didn't try to flash the zip again in cwm to see if it sticks.
Click to expand...
Click to collapse
Yupp it states that but you can flash another kernel from cwm
I've unlocked the bootloader of my Desire X, but whenever I try to install Android revolution, it gives me a bunch of errors saying the file couldn't be opened, any rom I stick on the SD has trouble being read by Nexus recovery , I've tried 3 other SD cards. Also after I rooted the phone, I still can't give applications such as Titanium backup root privileges because it says it couldn't find the root binary?
I've got Nexus recovery installed on stock 4.2.
I've also wanted to try other recoveries, is it as simple as flashing a new one through fastboot or do I have to do something else?
I really need help, so I'd be grateful for any you can offer me
Fahim92 said:
I've unlocked the bootloader of my Desire X, but whenever I try to install Android revolution, it gives me a bunch of errors saying the file couldn't be opened, any rom I stick on the SD has trouble being read by Nexus recovery , I've tried 3 other SD cards. Also after I rooted the phone, I still can't give applications such as Titanium backup root privileges because it says it couldn't find the root binary?
I've got Nexus recovery installed on stock 4.2.
I've also wanted to try other recoveries, is it as simple as flashing a new one through fastboot or do I have to do something else?
I really need help, so I'd be grateful for any you can offer me
Click to expand...
Click to collapse
If you are on stock 4.2, you also have HBoot 1.25, so maybe you can't install these roms because your HBoot it isn't 1.24 or lower.
Try to re-flash stock recovery, then flash neXus' again.
Or maybe it can be kernel stuff, did you flash the attached boot.img?
JoseluSpark said:
If you are on stock 4.2, you also have HBoot 1.25, so maybe you can't install these roms because your HBoot it isn't 1.24 or lower.
Try to re-flash stock recovery, then flash neXus' again.
Or maybe it can be kernel stuff, did you flash the attached boot.img?
Click to expand...
Click to collapse
But the rom does say it is available for 1.25+
and do I have to flash a stock recovery? Can't I install another recovery (not stock) by using the fastboot command?
Fahim92 said:
But the rom does say it is available for 1.25+
and do I have to flash a stock recovery? Can't I install another recovery (not stock) by using the fastboot command?
Click to expand...
Click to collapse
Also, is there a recovery that's sure to work with Hboot 1.25 JB?
If so, can I just flash that recovery over my current one?
Anybody?
Fahim92 said:
Anybody?
Click to expand...
Click to collapse
If you want, PM me your skypename and i'll guide you step by step.
ShadowCodeGaming said:
If you want, PM me your skypename and i'll guide you step by step.
Click to expand...
Click to collapse
I don't have Skype
Can you just provide help for me on here? I'd really appreciate it.
Here's my situation in case I wasn't clear in OP, I installed the Nexus recovery but it wasn't able to flash the rom I wanted, so now I want to flash another recovery, and was just wondering whether I could just flash another recovery on top of the old one or if I have to do something else?
Fahim92 said:
I don't have Skype
Can you just provide help for me on here? I'd really appreciate it.
Here's my situation in case I wasn't clear in OP, I installed the Nexus recovery but it wasn't able to flash the rom I wanted, so now I want to flash another recovery, and was just wondering whether I could just flash another recovery on top of the old one or if I have to do something else?
Click to expand...
Click to collapse
Look in the 'Desire X Original Android Development' Section for a TWRP recovery for JB hboot. It's working great for me. You can flash it the same way you flashed the NexusRecovery (fastboot)
ShadowCodeGaming said:
Look in the 'Desire X Original Android Development' Section for a TWRP recovery for JB hboot. It's working great for me. You can flash it the same way you flashed the NexusRecovery (fastboot)
Click to expand...
Click to collapse
So I can just flash it over the current recovery I have? I don't need to go back to stock?
Right
Sent from my black pearl using Tapatalk 2
Fahim92 said:
So I can just flash it over the current recovery I have? I don't need to go back to stock?
Click to expand...
Click to collapse
Yeah. You can just flash it over the NexusRecovery. You never have to go back to stock.
Okay, I just flashed TWRP over my current recovery.
I've tried to flash Sense revolution and it just fails through TWRP, why is this?
Wipe the phone and try again.
Maybe It can be because of MD5 verification. Only happens on that ROM?
Enviado desde mi HTC Desire X
Fahim92 said:
Okay, I just flashed TWRP over my current recovery.
I've tried to flash Sense revolution and it just fails through TWRP, why is this?
Click to expand...
Click to collapse
Try both ics and jb twrp
Sent from my HTC Desire X using xda app-developers app
I'm having troubles when i wan't to install this ROM :
http://forum.xda-developers.com/showthread.php?t=2555350 .
I'm using the dl from the first post, i'm using fastboot flash boot boot.img (the boot.img i'm getting from the zip-file).
I do a factory reset from the bootloader, then i do a factory reset in the twrp recovery
then i flash the boot.img in the jb hboot 1.25.0002
then i flash the zip file and i reboot.
but i never get to see the boot image. just a black screen...
Can someone help me?
tcornelis said:
I'm having troubles when i wan't to install this ROM :
http://forum.xda-developers.com/showthread.php?t=2555350 .
I'm using the dl from the first post, i'm using fastboot flash boot boot.img (the boot.img i'm getting from the zip-file).
I do a factory reset from the bootloader, then i do a factory reset in the twrp recovery
then i flash the boot.img in the jb hboot 1.25.0002
then i flash the zip file and i reboot.
but i never get to see the boot image. just a black screen...
Can someone help me?
Click to expand...
Click to collapse
You're definitely using a TWRP recovery made for JB hboot? @GtrCraft, did you put the right boot.img inside the zip?
Also, you can try flashing a custom JB kernel of your choice.
@dansou901 I believe so, flashing this (http://forum.xda-developers.com/showthread.php?t=2344254) work like a charm (except for the rom that hasn't got any wifi, ...)
How can i check to be sure?
tcornelis said:
@dansou901 I believe so, flashing this (http://forum.xda-developers.com/showthread.php?t=2344254) work like a charm (except for the rom that hasn't got any wifi, ...)
How can i check to be sure?
Click to expand...
Click to collapse
For booting that ROM a CM kernel is needed. As you have installed one (if it works like you said), you need to install a JB Sense kernel (just pick one from Original Android Development section). Then reinstall SuperSense and you should be fine.
I'll give that a go and let you know
@dansou901 , i've used this boot.img (http://forum.xda-developers.com/showthread.php?t=2337389) because i've already been able to flash that rom as well.
but now i can't seem to get rid of my previous custom rom. i've done a factory reset, i wiped everything there is to wipe, i've flashed the above boot.img and supersense but it's still another custom rom on my device :s
tcornelis said:
@dansou901 , i've used this boot.img (http://forum.xda-developers.com/showthread.php?t=2337389) because i've already been able to flash that rom as well.
but now i can't seem to get rid of my previous custom rom. i've done a factory reset, i wiped everything there is to wipe, i've flashed the above boot.img and supersense but it's still another custom rom on my device :s
Click to expand...
Click to collapse
That's a CM kernel as well. I told you to use a Sense kernel. Use this one for example: http://forum.xda-developers.com/showthread.php?t=2483489
and your recovery should work again as expected. Btw, which recovery did you install? Please give the link.
this is the twrp recovery.img http: // teamw . in / project / twrp2 / 140 (yeah, can't post outside links yet)
i'll give that one a shot
tcornelis said:
this is the twrp recovery.img http: // teamw . in / project / twrp2 / 140 (yeah, can't post outside links yet)
i'll give that one a shot
Click to expand...
Click to collapse
That one's made for ICS, if I recall correctly... Don't use it. Use this one instead: http://forum.xda-developers.com/showthread.php?t=2099513 But be sure to use a JB version.
After changing my recovery, finally i was able to flash the custom rom. I used the boot.img you gave me, but is that going to affect some of the features in the rom?
And i would like to thank you allready
tcornelis said:
After changing my recovery, finally i was able to flash the custom rom. I used the boot.img you gave me, but is that going to affect some of the features in the rom?
And i would like to thank you allready
Click to expand...
Click to collapse
No, it's not. You can however choose the kernel yourself as I said... But keep in mind that it has to be a JB Sense kernel (just read the OP of the kernel thread carefully, then you'll know). For recoveries, keep this in mind.
No Title Here
The boot.img in the SuperSENSE-dx5 zip is stock, every JB Sense kernel should work though
GtrCraft said:
The boot.img in the SuperSENSE-dx5 zip is stock, every JB Sense kernel should work though
Click to expand...
Click to collapse
His problem wasn't the kernel but the wrong recovery he used, it's fixed now.
Sent from my HTC Desire X using XDA Premium 4 mobile app
dansou901 said:
His problem wasn't the kernel but the wrong recovery he used, it's fixed now.
Sent from my HTC Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Perfect :good: