Related
What are most people using and does it matter that much?? What are the differences?? Cwm or twrp? I'm on twrp because I used qbkings root method and that's what his tutorial had used. I've also seen people say they r using cwm, if I wanted to use that instead, is it OK to use rom manager to flash the recovery? And is rom manager fully functional for the gnexus? I'm sure I could probably test most of this and figure it out with my backup if something goes wrong but sure would b a lot nicer I didn't have to do all that, and maybe this will help someone else too.
Sent from my Galaxy Nexus using Tapatalk 2
i use cwm touch on my gnex, have not tried twrp. i flashed it using fastboot. you can also just try/use it (or other recoveries) without flashing using "fastboot boot [image]". if you flash it be sure to rename/delete recovery-from-boot.p in system as it will otherwise overwrite your custom recovery again once you reboot.
stesmo said:
i use cwm touch on my gnex, have not tried twrp. i flashed it using fastboot. you can also just try/use it (or other recoveries) without flashing using "fastboot boot [image]". if you flash it be sure to rename/delete recovery-from-boot.p in system as it will otherwise overwrite your custom recovery again once you reboot.
Click to expand...
Click to collapse
Where can I find fastboot image for cwm or would it just b easier to rom manager?
Do u know of any differences in the 2, when u say "other recoveries" what else is available for the gnexus??? I've only seen the 2.
Sent from my Galaxy Nexus using Tapatalk 2
justen7723 said:
Where can I find fastboot image for cwm or would it just b easier to rom manager?
Do u know of any differences in the 2, when u say "other recoveries" what else is available for the gnexus??? I've only seen the 2.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
images can be found here: http://clockworkmod.com/rommanager
i have not tried the rom manager, i guess its a little bit easier if you dont want to use the command line.
since i have not tried twrp i cannot say exactly what the differences are. but i would guess both can do about the same things as the job for a recovery is quite well defined.
at least 4 for gnex : stock, cwm, cmw touch and twrp. don't really know if there are others...
Well, in my experience TWRP offers many benefits over CWR e.g. being able to be themed, having scripts, 'flashier' GUI, built-in file explorer but in the end I still swapped back to Touch CWR as it's simple, and it has everything that a recovery should do (flash, wipe, mount etc.). TWRP also has a few small bugs here and there but it's great if you want more options and features. Also that animation of booting into recovery bugs the hell out of me, along with the 'Swipe to continue' thing and touch response isn't that good in file lists (like when you have to choose what you want to flash).
It's all up to personal preference so that easiest way is to just flash both and try it yourself.
Twrp is awesome much quicker than cwm my only complaint right now is I can't find any themes for twrp 2.1.2
Sent from my Galaxy Nexus using xda premium
I have tried updating my rom through Rom manager and I keep getting an error. it says unknown volume path and cant mount backup path. Any assistance would be appreciated.
Posted in the wrong section this should be in Q&A. But I would advice not to use ROM manager and use another form of recovery like CWM.
Sorry about wrong section. What is CWM and where can I get it?
Pm me primedef lest they lock this thread
Sent from my Galaxy Nexus using xda app-developers app
primedef said:
Sorry about wrong section. What is CWM and where can I get it?
Click to expand...
Click to collapse
CWM is clockwork mod recovery.
Custom recovery used to flash ROMs.
Although I don't remember if there's different versions of it for each Nexus.
If this doesn't get automatically moved to Q&A, repost it there.
Agreed, and worst comes to worst, ROM Manager installs a version (possibly outdated) of cwm automatically, so you can always use that. Personally, I'd suggest flashing cwm 6.0.x and using that to manually flash everything from now on. Doing so (and understanding what you're doing) will vastly improve your Android experience, and knowledge, and may help you get out of a tight spot in the future, if something goes wrong with your phone. A little knowledge can go a looong way in the flash game.
Galaxy Nexus - Slim Bean 1.0
GooManager and TWRP is a superior replacement for koush's stuff. Just go with that and you'll never look back. They integrate well together and it actually works just like cwm and rom manager used to when it was 1st released a couple of years ago. Can't recommend it enough. I haven't used a properly working cwm/RM since the moto OG. But if you insist on cwm then I would find a version that has been been modified to function properly. Seems someone released a working touch version but I don't know if it integrates with the RM app.
Sent from my Galaxy Nexus using xda premium
primedef said:
I have tried updating my rom through Rom manager and I keep getting an error. it says unknown volume path and cant mount backup path. Any assistance would be appreciated.
Click to expand...
Click to collapse
Most likely failed if you don't have custom recovery installed as stated above
. Can't install custom ROM without custom recovery.
Travisdroidx2 said:
Posted in the wrong section this should be in Q&A. But I would advice not to use ROM manager and use another form of recovery like CWM.
Click to expand...
Click to collapse
Good call
primedef said:
Sorry about wrong section. What is CWM and where can I get it?
Click to expand...
Click to collapse
You can get it via ROM manager, choose install custom recovery. or you can flash it via fastboot.
jjhiza said:
Agreed, and worst comes to worst, ROM Manager installs a version (possibly outdated) of cwm automatically, so you can always use that. Personally, I'd suggest flashing cwm 6.0.x and using that to manually flash everything from now on. Doing so (and understanding what you're doing) will vastly improve your Android experience, and knowledge, and may help you get out of a tight spot in the future, if something goes wrong with your phone. A little knowledge can go a looong way in the flash game.
Galaxy Nexus - Slim Bean 1.0
Click to expand...
Click to collapse
I don't think it installs "automatically". It WILL choose the correct one for your device but you need to actually choose to install it. (sorry not trying to say you are wrong, just wanted to clarify for the guy
But like someone else said, you might want to download app called goo manager beta. Then open app, press menu, choose install openrecovery script. Say yes. Let it finish installing. Then reboot into recovery via the option in the app. That will give you TWRP2.2.0 as your custom recovery, i used to use cwmr for the longest time, one day i tried TWRP(and goo manager app) and i haven't looked back.
Just one MAJOR tip for you:
After installing a custom recovery, the VERY FIRST THING YOU SHOULD DO IS MAKE A NANDROID BACKUP.(choose option "backup" and let it do its thing) you won't regret making a backup. 75% of time before i flash/install something new or different i make a backup, this way if i don't like what i changed i can just restore and be back where i was. Plus, if anything ever goes wrong it's nice to have a couple nandroid backup files to choose from to recover your device to working condition.
ashclepdia said:
Most likely failed if you don't have custom recovery installed as stated above
. Can't install custom ROM without custom recovery.
Good call
You can get it via ROM manager, choose install custom recovery. or you can flash it via fastboot.
I don't think it installs "automatically". It WILL choose the correct one for your device but you need to actually choose to install it. (sorry not trying to say you are wrong, just wanted to clarify for the guy
But like someone else said, you might want to download app called goo manager beta. Then open app, press menu, choose install openrecovery script. Say yes. Let it finish installing. Then reboot into recovery via the option in the app. That will give you TWRP2.2.0 as your custom recovery, i used to use cwmr for the longest time, one day i tried TWRP(and goo manager app) and i haven't looked back.
Just one MAJOR tip for you:
After installing a custom recovery, the VERY FIRST THING YOU SHOULD DO IS MAKE A NANDROID BACKUP.(choose option "backup" and let it do its thing) you won't regret making a backup. 75% of time before i flash/install something new or different i make a backup, this way if i don't like what i changed i can just restore and be back where i was. Plus, if anything ever goes wrong it's nice to have a couple nandroid backup files to choose from to recover your device to working condition.
Click to expand...
Click to collapse
You're right...my explanation was a bit too simplified, I think. I meant that the process of installing cwm is automated when you choose to install it, versus having to manually flash it to the device. And you're 100% correct about immediately making a Nandroid after installing a recovery...having a stock, rooted system is always a prudent fallback. As for Too Manager; I actually just downloaded it the other day, because it gives me quick access to new Gapps whenever I need them, and it's a quicker solution than going to the site. I haven't used it for anything else at all, so I'm unaware of it's full capabilities... I would assume that anything that's hosted on Goo, is relatively easy to find via the app. Unfortunately, most of the JB ROMs I've flashed aren't hosted there. Yet and still, it's a very useful tool, even if you only use it to stay current with Gapp packages.
Galaxy Nexus - Slim Bean 1.0
jjhiza said:
You're right...my explanation was a bit too simplified, I think. I meant that the process of installing cwm is automated when you choose to install it, versus having to manually flash it to the device. And you're 100% correct about immediately making a Nandroid after installing a recovery...having a stock, rooted system is always a prudent fallback. As for Too Manager; I actually just downloaded it the other day, because it gives me quick access to new Gapps whenever I need them, and it's a quicker solution than going to the site. I haven't used it for anything else at all, so I'm unaware of it's full capabilities... I would assume that anything that's hosted on Goo, is relatively easy to find via the app. Unfortunately, most of the JB ROMs I've flashed aren't hosted there. Yet and still, it's a very useful tool, even if you only use it to stay current with Gapp packages.
Galaxy Nexus - Slim Bean 1.0
Click to expand...
Click to collapse
I fell in love with goo manager and TWRP as soon as i installed them, they are great. Was even able to find the beta versions of twrp2.2 on there. Tons of things are available on goo.you can usually find IMOSEYON lean kernel RC's on there as well. I even donated to not have to wait the 10seconds before download and help them get done new server equipment, hopefully they can get to their goal and we can get very speedy downloads.
(again sorry, i wasn't trying to step on ya toes or make ya look bad, i hate that i always want to clarify things further lol, makes me feel like a douche sometimes.)
Since this has not been closed or moved yet I just wanted to add that goo.im is great! I love that app for my getting downloads and gapps. I do have to say I tried twrp and it was faster but I never got the hang of it. Seemed you could only flash what was in your download folder? Or else I would have to move the file over to download folder to get it to flash. I guess on the dinc2 I got spoiled with touch ext4 recovery. It was a great recovery. I did notice the speed of twrp but decided to go back to my touch cwm since I already was familiar with the controls. Was probably user error on twrp since I see so many people love it on his forum.
ashclepdia said:
I fell in love with goo manager and TWRP as soon as i installed them, they are great. Was even able to find the beta versions of twrp2.2 on there. Tons of things are available on goo.you can usually find IMOSEYON lean kernel RC's on there as well. I even donated to not have to wait the 10seconds before download and help them get done new server equipment, hopefully they can get to their goal and we can get very speedy downloads.
(again sorry, i wasn't trying to step on ya toes or make ya look bad, i hate that i always want to clarify things further lol, makes me feel like a douche sometimes.)
Click to expand...
Click to collapse
No harm, no foul man. We all need correcting once in a while. I rarely get mad at anything in forums, other than people flaming devs or not following rules the devs have outlined (like asking a CM team member for an ETA, lol). You've actually me a reason to delve into the Goo app a bit deeper, to see what's there.
Galaxy Nexus - Slim Bean 1.0
I am trying to flash the SuperNexus 3.0 ROM to my D710 E4GT
http://forum.xda-developers.com/showthread.php?t=2208729
I downloaded the file and tried to open it in the PDA tab of ODIN like I normally would when flashing a device.
There isn't a TAR or MD5 file to open inside of the ZIP file.
I know that I'm missing something and I've searched around but I haven't found anything that points me in the correct direction.
Could somebody point me to what I am missing? Is there a tutorial for installing ROMS from a ZIP that I missed?
Thanks!
-Mike
You're probably the only person I know that doesn't flash using zips lol. Just boot up recovery and install zip. Pretty simple to navigate. This will explain it better http://forum.xda-developers.com/showthread.php?t=1761666
Sent from my SPH-D710 using Tapatalk 4
FuMMoD said:
You're probably the only person I know that doesn't flash using zips lol. Just boot up recovery and install zip. Pretty simple to navigate. This will explain it better http://forum.xda-developers.com/showthread.php?t=1761666
Sent from my SPH-D710 using Tapatalk 4
Click to expand...
Click to collapse
Thanks for the reply I'll check the page out that you posted.
I am a total noob. I've crept the forums and used Odin to flash a lot.
I guess, I'm surprised by the .zip comment. Not because I know anything about anything (By now this should be obvious) but because when you look at a tutorial on flashing your phone, it always points at using odin.
It's one thing to root your phone with Odin and another to flash a custom Rom. All the custom roms are zip files and in the original post of the threads they tell you exactly the best way to flash the Rom.
Sent from my SPH-D710 using Tapatalk 4
FuMMoD said:
It's one thing to root your phone with Odin and another to flash a custom Rom. All the custom roms are zip files and in the original post of the threads they tell you exactly the best way to flash the Rom.
Sent from my SPH-D710 using Tapatalk 4
Click to expand...
Click to collapse
OK. That makes sense. I'm reading that now in the thread you handed to me.
Thanks again!
I knew the info existed, I needed some help getting to it and wrapping my head around it.
It's refreshing to ask an honest question because I'm over-whelmed and not get flamed out.
Yeah the instructions in that thread are not noob friendly. I hope the sticky can help you out. Use the el26 or el29 kernel packed with clockwork mod available in the kernel repo. You can find it in the Android development forum at the top. Use that kernel and recovery combo to safely flash any rom. Also going to jb you need to do an Odin rooted restore of a stock jb Rom in order to partition everything correctly. You'll be able to find this in Android development too. Sorry I can't provide much links im on my phone at work so it'll take me a bit to link.
Sent from my SPH-D710 using Tapatalk 4
FuMMoD said:
Yeah the instructions in that thread are not noob friendly. I hope the sticky can help you out. Use the el26 or el29 kernel packed with clockwork mod available in the kernel repo. You can find it in the Android development forum at the top. Use that kernel and recovery combo to safely flash any rom. Also going to jb you need to do an Odin rooted restore of a stock jb Rom in order to partition everything correctly. You'll be able to find this in Android development too. Sorry I can't provide much links im on my phone at work so it'll take me a bit to link.
Sent from my SPH-D710 using Tapatalk 4
Click to expand...
Click to collapse
So I went to the Kernel Download Page and all of the links to el26 with CWM were dead.
I dug around some more and found this:
w w w. rwilco12.com/Files/Devices/Samsung%20Galaxy%20S2%20%28Sprint%29%20%28SPH-D710%29/Tutorials/SPHD710-Root. p h p
[Can't post URL, new user]
I went with Chris41g's EL26 Stock CWM5 Repack
It looked like what I needed to root with recovery so that I could install the SuperNexus ROM.
Now, my phone has been stuck at the Samsung Galaxy S II screen with the yellow triangle for a half an hour.
Did I miss something else?
HighSeraphim said:
So I went to the Kernel Download Page and all of the links to el26 with CWM were dead.
I dug around some more and found this:
w w w. rwilco12.com/Files/Devices/Samsung%20Galaxy%20S2%20%28Sprint%29%20%28SPH-D710%29/Tutorials/SPHD710-Root. p h p
[Can't post URL, new user]
I went with Chris41g's EL26 Stock CWM5 Repack
It looked like what I needed to root with recovery so that I could install the SuperNexus ROM.
Now, my phone has been stuck at the Samsung Galaxy S II screen with the yellow triangle for a half an hour.
Did I miss something else?
Click to expand...
Click to collapse
Pull your battery, put it back in, hold the vol up and power until it loads up in recovery. Clean cache, then clean Dalvic cache(in Advanced Menu), Find the zip you want on your sd card install zip. It should boot into your new rom. The CWM repack you used is not the one I would have, but it probably is just the repack kernal and cant boot your phone.
byrdcfmma said:
Pull your battery, put it back in, hold the vol up and power until it loads up in recovery. Clean cache, then clean Dalvic cache(in Advanced Menu), Find the zip you want on your sd card install zip. It should boot into your new rom. The CWM repack you used is not the one I would have, but it probably is just the repack kernal and cant boot your phone.
Click to expand...
Click to collapse
Sweet! I'm figuring some things out now!
I actually had GB on the device. I got it from the factory yesterday. Apparently it had a higher OS on it. So I had to go put a GB kernel on it.
I couldn't find the one with CWM but this one has AGAT
HighSeraphim said:
Sweet! I'm figuring some things out now!
I actually had GB on the device. I got it from the factory yesterday. Apparently it had a higher OS on it. So I had to go put a GB kernel on it.
I couldn't find the one with CWM but this one has AGAT
Click to expand...
Click to collapse
once you get the phone set up, get Mobile Odin and keep this .tar files on your sd card. If I Mobile Odin back to this .tar then I can get a clean install on any new rom. this is the name of the file you are looking for, we have been requested not to provide direct links
StockCWM-EL26.tar.md5
If you phone boot loops again have thie zip as well. Pull batt, then press vol up and power to get to CWM recovery then clean and flash
EL26_StockCWM.zip
As you will see when you get more experienced, there is more than one way to skin the cat. This is what I do and it works every time.
byrdcfmma said:
once you get the phone set up, get Mobile Odin and keep this .tar files on your sd card. If I Mobile Odin back to this .tar then I can get a clean install on any new rom. this is the name of the file you are looking for, we have been requested not to provide direct links
StockCWM-EL26.tar.md5
If you phone boot loops again have thie zip as well. Pull batt, then press vol up and power to get to CWM recovery then clean and flash
EL26_StockCWM.zip
As you will see when you get more experienced, there is more than one way to skin the cat. This is what I do and it works every time.
Click to expand...
Click to collapse
That's great! Thank you!
I picked up the Stock EL26 loads.
To make sure I understand when you say that you can get a clean install on any new rom, you mean that you can install StockCWM-EL26 first and then throw the ROM on and it works right?
Also as a note, I have gotten the SuperNexus ROM running on my machine. I don't have 3G data yet. I'm still working on it. I installed the latest ICS modem and changed the xml file that was suggested. I then updated the permissions on the file to what the other files in the directory had and rebooted. Still nothing... I'm not sure if this is your wheel-house and you've already helped me tremendously! I'm digging around trying to find answers.
(I can't post on the SuperNexus dev forum yet. I'm going to look for a support forum or something to post on.)
HighSeraphim said:
That's great! Thank you!
I picked up the Stock EL26 loads.
To make sure I understand when you say that you can get a clean install on any new rom, you mean that you can install StockCWM-EL26 first and then throw the ROM on and it works right?
Also as a note, I have gotten the SuperNexus ROM running on my machine. I don't have 3G data yet. I'm still working on it. I installed the latest ICS modem and changed the xml file that was suggested. I then updated the permissions on the file to what the other files in the directory had and rebooted. Still nothing... I'm not sure if this is your wheel-house and you've already helped me tremendously! I'm digging around trying to find answers.
(I can't post on the SuperNexus dev forum yet. I'm going to look for a support forum or something to post on.)
Click to expand...
Click to collapse
First - Yes, when I want to change roms, I use mobile odin to flash the .tar EL26 CWM kernal. Pull Batt if needed and then Vol up and power to get to CWM. Then I follow the ROM developer's instructions. reboot and almost always get a good clean install.
Second - I use my phone all day for work so I dont mess with the AOSP Roms much. I like them a lot, but I cant have data/connection issues interfere with my lively-hood so I mostly stay on the TW side of things. Cant help you there, sorry...
HighSeraphim said:
That's great! Thank you!
I picked up the Stock EL26 loads.
To make sure I understand when you say that you can get a clean install on any new rom, you mean that you can install StockCWM-EL26 first and then throw the ROM on and it works right?
Also as a note, I have gotten the SuperNexus ROM running on my machine. I don't have 3G data yet. I'm still working on it. I installed the latest ICS modem and changed the xml file that was suggested. I then updated the permissions on the file to what the other files in the directory had and rebooted. Still nothing... I'm not sure if this is your wheel-house and you've already helped me tremendously! I'm digging around trying to find answers.
(I can't post on the SuperNexus dev forum yet. I'm going to look for a support forum or something to post on.)
Click to expand...
Click to collapse
In this step for SN, what rom did you get the xml from? "NAVIGATE TO system/etc and look for apns-conf.XML and delete it. Then grab one from another ROM that has working data then paste it into the same directory and fix permissions and reboot".
That might be the issue. You need to make sure that a) you have an ICS modem(FL24) is the latest, and make sure you're not flashing it through mobile Odin, it won't take, and b) you have a working apn-conf.xml file from a rom with working data. Dastin15's Wild For The Night is also 4.2.2, and last I checked, had working data. Might give that a go. Good luck!
Sent from my SPH-D710BST using xda premium
I just want to make one thing clear, I have just finished downgrading my Galaxy Nexus to 4.2.2 from 4.3 so my phone is clean, there is nothing on it that I want, it has the Stock Google 4.2.2 yakju image, I used WugFresh's toolkit to downgrade. My phone is rooted and it's bootloader is unlocked, all done using the toolkit. I also installed twrp recovery using the GooManager app.
So how do I install Cyanogenmod (Latest Stable version) on my phone.
eyad_996 said:
I just want to make one thing clear, I have just finished downgrading my Galaxy Nexus to 4.2.2 from 4.3 so my phone is clean, there is nothing on it that I want, it has the Stock Google 4.2.2 yakju image, I used WugFresh's toolkit to downgrade. My phone is rooted and it's bootloader is unlocked, all done using the toolkit. I also installed twrp recovery using the GooManager app.
So how do I install Cyanogenmod (Latest Stable version) on my phone.
Click to expand...
Click to collapse
head here you will find latest build here
http://download.cyanogenmod.com/?device=maguro&type=stable
just flash in recovery
cheers :good:
A little more detail on the "just flash in recovery" part.
eyad_996 said:
A little more detail on the "just flash in recovery" part.
Click to expand...
Click to collapse
download zip file in memory
reboot into recovery
select wipe cache data factory reset
select advance option and wipe dalvik cache
select flash zip from sd card/internal memory
flash it!!!
Someone on YouTube Flash two zip files, one is cyanogenmod, and the other is a Google Apps/play store file, he was flashing on a GS3, do I need this file?
eyad_996 said:
Someone on YouTube Flash two zip files, one is cyanogenmod, and the other is a Google Apps/play store file, he was flashing on a GS3, do I need this file?
Click to expand...
Click to collapse
If you want the Google Apps, then yes you have to flash them as they aren't included with most custom ROMs.
E2A, make sure you grab the proper ones for whatever build/ROM you are flashing.
Damnit, can't you read up, it's all over the damned stickies...
If you don't even know how to flash a zip, you shouldn't even be flashing anything....
Beamed from my Grouper
Relax, I'm done by the way.
And yes I don't know anything about flashing zips, I'm learning, I'm sure that you at some point of your life didn't know anything about flashing too, you weren't born with the full knowledge of Flashing.
BTW, that's why this site is for, learning.
So use the learning resources that are available here for you. Read everything before you try anything. THEN, if you still have a question, ask. It's not fair to waste people's time re-answering questions that have been answered time and time again. Your laziness won't get you far in this community. And no, the primary purpose of this site is for development not holding people's hands.
Hi, hope my exact issue wasn't discussed after page 10 of the help & troubleshoot forum, anyway my rooted, unlocked cwm recovery stock 4.2 yakju (if I remember well) Samsung GNEX started to behave strangely slower then usual less then a week ago, then a couple of days later I woke up after night battery recharge to the boot up animation which never gave way to the operating system starting up.
After the first moment of despair I tried reading something here and with the use of adb I was able to first see the device and, after backing up via recovery, to pull the files from the phone (backup included). Problem is the 0 folder is very light for all the data and apps that I had, and inside the DCIM folder there's nothing, no trace of the 1k+ picture I shot in the past couple years, only an igc file which should have been in another folder. But strangely enough the backup weights almost 6GB which is consistent with what was inside prior to the crash.
Before attempting the backup I fiddled with recovery and tried to wipe cache, dalvik and fixing permissions, with no apparent results.
So now I'm undecided whether to take the phone to a samsung job centre which will surely wipe all data and possibly find out I have a corrupt memory or partition table, which renders many files and folders unavailable to be adb pulled or to wipe data/restore factory by myself hopying, fingers crossed, that the backup actually saved all my files and that could be restored without hassle. I actually had hoped that, like for the desktop environment, there was the possibility to awake my phone with a linux live or whatever to check if all files were present and downloadable before actually restoring the phone.
Thanks for your interest and help.
https://drive.google.com/file/d/0B8Pbk0TslYN6cm1wWWZydVM2V0k/edit?usp=sharing
Have you tried dirty flashing your rom?
Sent from my Galaxy Nexus using XDA Free mobile app
This is probably what I was thinking to do in the last sentence, I just have no idea how this could be done. Are there any videos explaining a dirty flash for gnex out there? Thanks for your help
Sent from my ASUS Transformer Pad TF300T using XDA Free mobile app
berniefranz said:
This is probably what I was thinking to do in the last sentence, I just have no idea how this could be done. Are there any videos explaining a dirty flash for gnex out there? Thanks for your help
Sent from my ASUS Transformer Pad TF300T using XDA Free mobile app
Click to expand...
Click to collapse
Its really easy. Just wipe cache and dalvik cache and then flash your rom (the same rom that is on the phone) again. Reboot.
Sent from my Galaxy Nexus using XDA Free mobile app
As far as I remember there is no identifiable rom files inside my GNEX memory, or wait, it seems I do already have a 6c7ff815e7762f651ad6f8c74e5cb281093f1e0b.signed-yakju-JWR66V-from-JDQ39.6c7ff815 zip in my download folder. So I need to clean cache and dalvik then install from zip. Do you know if this system wipes everything and I need to restore everything applying my hopefully working backup, or if it keeps all the files?
I'll try it tomorrow with fingers crossed.
Thanks again
mrgnex said:
Its really easy. Just wipe cache and dalvik cache and then flash your rom (the same rom that is on the phone) again. Reboot.
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
berniefranz said:
As far as I remember there is no identifiable rom files inside my GNEX memory, or wait, it seems I do already have a 6c7ff815e7762f651ad6f8c74e5cb281093f1e0b.signed-yakju-JWR66V-from-JDQ39.6c7ff815 zip in my download folder. So I need to clean cache and dalvik then install from zip. Do you know if this system wipes everything and I need to restore everything applying my hopefully working backup, or if it keeps all the files?
I'll try it tomorrow with fingers crossed.
Thanks again
Click to expand...
Click to collapse
Dirty flashing wont wipe any data. Only cache (which is only helpful with some speed). Cache will rebuild. If thats your rom. Dirty flash it. If it isnt. Adb push the right rom.
Sent from my Galaxy Nexus using XDA Free mobile app
Then I don't think the mentioned file is the my rom but a rom update I wanted to push myself but never did. Now, I'm definitely sure it was already JB, but which flavour? 4.2 JOP40C, 4.2.1 JOP40D or 4.2.2 JDQ39? I guess it should have been the last one, if I intended to update from JDQ to JWR (according to the file name), and I'm quite sure it was Jakju but just can't remember for sure. Is there a way via recovery or adb to check which was my rom? Or should I just close my eyes and download and flash JDQ39?
Again, thanks
mrgnex said:
Dirty flashing wont wipe any data. Only cache (which is only helpful with some speed). Cache will rebuild. If thats your rom. Dirty flash it. If it isnt. Adb push the right rom.
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
berniefranz said:
Then I don't think the mentioned file is the my rom but a rom update I wanted to push myself but never did. Now, I'm definitely sure it was already JB, but which flavour? 4.2 JOP40C, 4.2.1 JOP40D or 4.2.2 JDQ39? I guess it should have been the last one, if I intended to update from JDQ to JWR (according to the file name), and I'm quite sure it was Jakju but just can't remember for sure. Is there a way via recovery or adb to check which was my rom? Or should I just close my eyes and download and flash JDQ39?
Again, thanks
Click to expand...
Click to collapse
I know that TWRP default names a nandroid as the ROM build name/number and date. Don't know what cwm does for that as its been ages since I used it. You could install twrp and see what that tells you as the name of backup maybe to try and grab current ROM info.
Or using the file manager in recovery(twrp has one dunno about cwm) and see if you can look at the build.prop in /system which will have all relevant ROM information. If you can use adb in recovery try pulling /system/build.prop and looking at it. Right near top will be ROM build and info
Thanks, CWM doesn't have a file manager, but adb did actually pull the build prop id=JOP40D, so I'll go back to download the correct ROM and try to flash it..
ashclepdia said:
I know that TWRP default names a nandroid as the ROM build name/number and date. Don't know what cwm does for that as its been ages since I used it. You could install twrp and see what that tells you as the name of backup maybe to try and grab current ROM info.
Or using the file manager in recovery(twrp has one dunno about cwm) and see if you can look at the build.prop in /system which will have all relevant ROM information. If you can use adb in recovery try pulling /system/build.prop and looking at it. Right near top will be ROM build and info
Click to expand...
Click to collapse
small update, I managed to download the correct rom and I tried to adb push the .tar to the device (twice and attempting a third to /sdcard/ /sdcard/clockworkmod/ and now /sdcard/0/Download/) but still haven't been able to spot the uploaded file to choose for dirty flash. adb shows the file as uploaded , but again no sign of it with CWM Recovery. should I try to install TWRP recovery? with the nexus toolkit there is a function to flash a rom, but it says it will wipe the device first, so it's really not the option I was looking for. Another strange behaviour of CWM Recovery, or maybe my phone, inside mounts and storage menu, mount sdcard seems to be not working as it never changes to unmount after you click it. I think my memory went berserk and that's the reason why the phone rebooted and never woke up again. Maybe I'll take to the nearest job center to ascertain the damage...
thanks for all your help
berniefranz said:
Thanks, CWM doesn't have a file manager, but adb did actually pull the build prop id=JOP40D, so I'll go back to download the correct ROM and try to flash it..
Click to expand...
Click to collapse
installed TWRP and was able to see to rom.tar uploaded via adb in the download folder, but wasn't able to use to flash as probably both recovery wants .zip and not .tar, so I'll now untar and zip the stock rom and upload it again...
small steps...
had a md5 check fail during flash, so still no good news. I was surfing a bit when noticed that developers.google.com doesn't have a factory image for 4.2.1 jop40d but only for 4.1.2 jzo54k. Does this mean I should flash 4.1.2 and then update, or try directly for the 4.2.1 which I can't find (a working one)?
went back to CWM but installation failed as well as TWRP, so I guess my last option is to take it to a samsung job center to check whether I have a corrupted memory or else... ANyway thanks everybody for your support..
berniefranz said:
had a md5 check fail during flash, so still no good news. I was surfing a bit when noticed that developers.google.com doesn't have a factory image for 4.2.1 jop40d but only for 4.1.2 jzo54k. Does this mean I should flash 4.1.2 and then update, or try directly for the 4.2.1 which I can't find (a working one)?
Click to expand...
Click to collapse
Had to take it to the job center where, it was downgraded to 4.0.4 (have still to check which flavour) fixed something and Wiped everything. When I side about he post mortem backup and the intention to try a restore from there I was give an are you kidding look, it could crash again... sigh.
Anyway thanks everyone that spent some time to try and explain a noob how to try to solve this issue.. Now I've got a new galaxy nexus, so after a little grievance I'll start reading on how to flash a nice rom...
berniefranz said:
went back to CWM but installation failed as well as TWRP, so I guess my last option is to take it to a samsung job center to check whether I have a corrupted memory or else... ANyway thanks everybody for your support..
Click to expand...
Click to collapse