Related
Alright so i installed my first ROM on my evo last night. seems like it worked fine everything still works and the ROM is awesome.
http://forum.xda-developers.com/showthread.php?t=1012918
One questions i did have is, if i want to install another one how would i go about that?
Do i just install it like i did the first or do i need to remove the current one and install the new one?
Im sure this is posted somewhere but i wasent able to find the answer im looking for.
Thanks for any input
The tried-and-true and overall preferred method, as I've observed, of XDA forum members is to do the following when changing to a new ROM, or for the first time:
Place the ROM in the root of your SD card.
Boot into Recovery by holding vol+down and Power (most custom ROMs will let you reboot into Recovery specifically instead of having to turn off the phone and back on).
Make a nandroid backup.
Wipe data/factory reset.
Wipe cache.
Go into Advanced, wipe Dalvik cache.
"Go Back."
Install zip from SD card.
Choose applicable .zip.
Wait for installation.
Reboot.
Enjoy.
Furthermore, if going to an AOSP ROM, be sure to flash GApps right after you flash your ROM.
As far as kernels go, some people say to do it after you flash your ROM, some day to reboot and then go back into Recovery and do it, some say either way.
Load the new rom zip on your sd card from your pc. Boot to Recovery, make a nandroid backup of your current rom. Then factory reset the phone in Recovery and wipe data, cache and dalvik cache. Wiping them each 2-3x for optimal results.
Then flash the zip for your new rom. Reboot and there it is. If your gonna change kernels or task bars etc, I recommend booting between each zip flashed. Just seems I have less problems this way.
Also get a sms backup app if they are important to you. I use sms backup+. It's free and works great, backs up msgs to gmail. Then u can restore with the app when the new rom is loaded.
Sent from my Warm Z EVO
totalanonymity said:
The tried-and-true and overall preferred method, as I've observed, of XDA forum members is to do the following when changing to a new ROM, or for the first time:
Place the ROM in the root of your SD card.
Boot into Recovery by holding vol+down and Power (most custom ROMs will let you reboot into Recovery specifically instead of having to turn off the phone and back on).
Make a nandroid backup.
Wipe data/factory reset.
Wipe cache.
Go into Advanced, wipe Dalvik cache.
"Go Back."
Install zip from SD card.
Choose applicable .zip.
Wait for installation.
Reboot.
Enjoy.
Click to expand...
Click to collapse
Awesome thank you very much. Sounds pretty much just like how you install one.
Thanks again
yes do that ^^ nandroid and you can leave the rom on your card if you have enough space and in case you want to reinstall it clean again.
one more question
im thinking about installing another rom and it has multiple downloads some are themes and some widgets and the main ROM. Do I install them 1 at a time or can i do them one after another.
Honestly, preference, with those, I think. As stated before, some people's phones are fine with flashing tons of things at once and some people's phones like to take it nice and slow and have a reboot in between.
Also, make sure the themes you are installing are in flashable zips. There are some out there that aren't and require manually placing them in the SD card or using adb.
http://forum.xda-developers.com/showthread.php?t=841311
this is the one i was thinking about
dahlinc said:
http://forum.xda-developers.com/showthread.php?t=841311
this is the one i was thinking about
Click to expand...
Click to collapse
ROMs are flashed in recovery just the same as any other ROM.
All add-ons in his first post are flashable via Recovery, as well.
Get into a habit of wiping cache and Dalvik cache before every flash of anything. (Data/factory when flashing between ROMs, though.)
Also, a nandroid backup before you flash anything would be wise. I stopped doing them as often because they take up quite a bit of memory when you start flashing things left and right! But, it is wise to do so before flashing anything. If anything goes wrong flashing a particular item, you can always restore a backup and start again from a very recent point (i.e. not losing much of what you did) from when there were no issues.
I personally also copy my files to my computer for safekeeping, should something occur with the SD card.
Thats all i need know thank you again!!!!
This is my first phone that doesn't have an external SD card and I'm not 100% sure how to properly perform a full wipe it
I know this is a noob question, but I just don't want to brick my phone.
What I Used to Do
Back in the day with my SGS Captivate or SGS2 I just put all my files on my external SD card, then via Android (Astro File Manager) I deleted every folder from the internal SD card, booted into CWM, performed a wipe/factory default, cleared cache, formatted system partition and then installed custom ROM and everything worked fine.
What I Need
I want to be sure that I don't brick it so I'm hoping that someone can give me a step-by-step walk-through of how to install CM 10.1 (or any other ROM i guess) on my phone after completely wiping it of anything on it.
What I've Tried
I used the Galaxy Nexus Toolkit to unlock, root and install CWM but unfortunately when I then installed CM 10.1 via CWM, some leftover files remained from the stock ROM.
Basically, my phone is ridiculously slow/lagging and I'm getting sick of it.
I've tried installing a custom kernel (Franco Kernel), I've set the CPU governor on Performance (1200MHz always) uninstalling any un-needed apps... but my phone is still un-usable.
Sometimes when I install the latest nightly of CM 10.1 I do an update and other times I tried doing a full install where I wipe the Dalvik; neither way helps I still get the ridiculous lag.
The definition of a full wipe:
-wipe data / factory reset
-wipe cache
-wipe dalvik cache
-(optional) format system
Then flash the rom/gapps/kernel.
Maybe you have a "bricked" phone. It has something to do with the emmc chip. How much free storage do you have?
Check it by downloading the app in the screenshot.
If you havent a bricked emmc version, then I suggest returning to stock again, and then root again. ( most clean process , as it restores all the partitions to the stock state.)
Hopefully this helps my friend!
PS: you posted in the wrong forum, don't do it in the future
Sent from my Nexus Prime
That's not related to development, read the rules next time.
Try the full wipe zip from Android Revolution HD Rom.
Use the pinned guide for fast boot. Use fast boot format/erase commands for all partitions, and for good measure flash to stock with fast boot also. This is the most surefire way and it hasn't failed me yet.
thegtfusion said:
The definition of a full wipe:
-wipe data / factory reset
-wipe cache
-wipe dalvik cache
-(optional) format system
Then flash the rom/gapps/kernel.
Maybe you have a "bricked" phone. It has something to do with the emmc chip. How much free storage do you have?
Check it by downloading the app in the screenshot.
If you havent a bricked emmc version, then I suggest returning to stock again, and then root again. ( most clean process , as it restores all the partitions to the stock state.)
Hopefully this helps my friend!
PS: you posted in the wrong forum, don't do it in the future
Sent from my Nexus Prime
Click to expand...
Click to collapse
Thanks for the info, I'll be more careful in the future where I post.
I have the 16GB model and 4GB free right now.
I installed the eMMC Brickbug Check app and it says that my chip is ok (sane).
My phone is definately rooted, so I'm not sure why this app says that root is required for the memory test (clicking it just launches wiki page on rooting).
https://www.dropbox.com/s/gzuzhn22n0f354w/Screenshot_2013-01-28-11-07-40.png
If you're on 4.2.1 you won't see any CWM backups so get ES File Explorer, give it root access and then go to /data/media/clockworkmod and see what's about. Or boot into CWM and delete some old backups
As for a full wipe, I use this before flashing a new ROM:
http://www.mediafire.com/download.php?lxpw84fwtm5cj6w
EddyOS said:
If you're on 4.2.1 you won't see any CWM backups so get ES File Explorer, give it root access and then go to /data/media/clockworkmod and see what's about. Or boot into CWM and delete some old backups
Click to expand...
Click to collapse
It totally forgot about the CWM backups
I'll delete those ASAP
There wasn't a lot in the backups folder but there is about 3.82 GB in the blobs folder in the clockworkmod folder; are those ok to delete?
Flash the newest version of CWM (6.0.2.3) as it doesn't use blobs any more. Delete all old backups and take a new one if you want. Also, check when I added to my last post
EddyOS said:
Flash the newest version of CWM (6.0.2.3) as it doesn't use blobs any more. Delete all old backups and take a new one if you want. Also, check when I added to my last post
Click to expand...
Click to collapse
Thanks a lot, I'll give that a shot tonight.
I'll update CWM to the latest, then run your super wipe zip followed by the latest CM 10.1.
Thanks a lot for the super wipe zip too.
After wiping and flashing go ahead and run fix permission too.
EddyOS said:
Flash the newest version of CWM (6.0.2.3) as it doesn't use blobs any more. Delete all old backups and take a new one if you want. Also, check when I added to my last post
Click to expand...
Click to collapse
WiredPirate said:
After wiping and flashing go ahead and run fix permission too.
Click to expand...
Click to collapse
Thanks guys, my phone is usable again
You guys are awesome.
What I Did
- installed the latest CWM using fastboot
- booted into recovery
- used adb to sideload your super wipe script, then the latest CM 10.1 nightly and then the latest gapps
- fixed permissions via CWM
- restarted my phone to get a very responsive phone again
With my last 2 phones I was spoiled having external SD cards so that i never had to sideload or use fastboot (I let Odin do that part).
Hi everyone!
My Galaxy Nexus has become slow over the last year, I think due to several factors and trash that's been accumulating onto its memory.
I would therefore like to bring it TOTALLY back to where it was when I switched it on for the first time, consequently deleting all data on it.
I have to mention that the phone originally had ICS 4.0.4 and was updated to JB 4.2.2.
I have tried to read a bit about the topic and found out there are many options; but as those solutions also involved the flash of a new ROM, thing of which I'm not intrested, I preferred asking here for further explanations or solutions on what is best to do.
I was wondering how effective the "Factory data reset" that the phone offers under the "Backup & reset" menu of "Settings" is. In particular: does it delete all the data (Cache, personal, as well as apps) or does it leave something behind?
Also, I've read things about CWM, which seems to be the most apt tool for wiping. (I haven't installed it, and do not plan onto; I've only run it temporarily).
If someone could explain me what the following (and particularly the last 3 [such as Dalvik?]) do exactly, I would be very grateful.
Wipe Data/factory reset
Wipe Cache
Wipe Dalvik-Cache
Wipe Battery Stats
Format /system
Also, when I format, will I get the version of Android I had originally (ICS) or the lastest I updated to (JB)? In the latter case... Did the phone store (hence occupying memory) all the versions that were downloaded in between?
Should you have better ideas on how to achive what I need, please let me know.
Thank you!
Anybody willing to help?!
what carrier do u have for your galaxy nexus?
OP,
1) factory reset in the menu in android will wipe everything off the phone, but will not return the phone to the original rom of when you got it.
2)
if you have stock recovery
Wipe Data/factory reset - wipes all data/apps from the phone (including stuff on /sdcard/ )
if you have a custom recovery
Wipe Data/factory reset - wipes apps and app data off phone, leaves /sdcard alone
Wipe Cache - wipes cache
Wipe Dalvik-Cache - wipes davlik cache
Wipe Battery Stats - deletes the battery stats file
Format /system - formats the /system directory ( you will not have a OS after this )
3) the phone will not go back to a previous version of android unless you flash it. end of story.
i decided to go back to 4.1.2 after using 4.2.2 after a few months, and many disappointments later. i ended up downloading factory images for 4.1.2 and the old radios. and then used my older verstion of the Galaxy Nexus ToolKit to flash everything back. it was painless and fast. But I have stayed on AOKP, so i'm unsure how else you will be able to go back fully "stock."
Get a stock rom ,flash .
sent by reversed alien technology....
jaymazz13 said:
what carrier do u have for your galaxy nexus?
Click to expand...
Click to collapse
It's a no brand GSM Nexus, though the carrier is TIM (Italy).
Zepius said:
OP,
1) factory reset in the menu in android will wipe everything off the phone, but will not return the phone to the original rom of when you got it.
2)
if you have stock recovery
Wipe Data/factory reset - wipes all data/apps from the phone (including stuff on /sdcard/ )
if you have a custom recovery
Wipe Data/factory reset - wipes apps and app data off phone, leaves /sdcard alone
Wipe Cache - wipes cache
Wipe Dalvik-Cache - wipes davlik cache
Wipe Battery Stats - deletes the battery stats file
Format /system - formats the /system directory ( you will not have a OS after this )
3) the phone will not go back to a previous version of android unless you flash it. end of story.
Click to expand...
Click to collapse
I do have a stock recovery, but I could temporarily run CWM through mskip's tool: there should be no problem I believe.
Also, if I run "Format /system", and therefore have no OS, how am I supposed to act later? Get the stock ROM from Google and flash it through mskip's tool (in this case, could I do it through the Stock Recovery or I imperatively need CSW?)? Or there is another partition with a backup that I could use?
Further, do you think that formatting the /system folder is pivotal for a complete clean or it just adds the hassle of reflashing?
Just for curiosity:
How will deleting the battery stats affect my phone/battery life, if it will?
What exactly is Dalvik-chache?
Thank you all!
UlixesTNT said:
It's a no brand GSM Nexus, though the carrier is TIM (Italy).
I do have a stock recovery, but I could temporarily run CWM through mskip's tool: there should be no problem I believe.
Also, if I run "Format /system", and therefore have no OS, how am I supposed to act later? Get the stock ROM from Google and flash it through mskip's tool (in this case, could I do it through the Stock Recovery or I imperatively need CSW?)? Or there is another partition with a backup that I could use?
Further, do you think that formatting the /system folder is pivotal for a complete clean or it just adds the hassle of reflashing?
Just for curiosity:
How will deleting the battery stats affect my phone/battery life, if it will?
What exactly is Dalvik-chache?
Thank you all!
Click to expand...
Click to collapse
It wipes your stats from your previous ROM ,so when you flash another ROM you get a completely different stats ,so you might get good battery or not depends on ROM/kernel
Sent from my Galaxy Nexus using xda app-developers app
Wiping battery stats will accomplish nothing useful.
https://plus.google.com/app/basic/stream/z13dgb0rksywh3muq222fzkqnwfgdbgrk04
Its a myth.
About dalvik... Just Google search.
Sent from my Nexus
UlixesTNT said:
It's a no brand GSM Nexus, though the carrier is TIM (Italy).
I do have a stock recovery, but I could temporarily run CWM through mskip's tool: there should be no problem I believe.
Also, if I run "Format /system", and therefore have no OS, how am I supposed to act later? Get the stock ROM from Google and flash it through mskip's tool (in this case, could I do it through the Stock Recovery or I imperatively need CSW?)? Or there is another partition with a backup that I could use?
Further, do you think that formatting the /system folder is pivotal for a complete clean or it just adds the hassle of reflashing?
Just for curiosity:
How will deleting the battery stats affect my phone/battery life, if it will?
What exactly is Dalvik-chache?
Thank you all!
Click to expand...
Click to collapse
1) if you wipe /system, you need to flash the system.img again.
2) you dont need cwm or a toolkit to flash the system.img from google
3) whenever system.img is flashed, it wipes what was there anyways.
4) deleting battery stats does nothing other than remove the log file (which is the battery stats file)
5) use google for dalvik. its all over the place there
6) STOP USING A TOOLKIT. - http://forum.xda-developers.com/showthread.php?t=1626895
Hello:
So I rooted my phone today and I downloaded the app, "ROM Manager," and downloaded a ROM from it, which I read that I'm not supposed to do, afterwards. Now, whenever I turn my phone on, it only shows the Cyanogenmod boot animation. I read in another thread that I should clear the cache, which I did, but it did not help. Should I try and flash it to the stock? Please help! I am inexperienced with this and I don't know what to do. Thanks in advance!
dallinrigby said:
Hello:
So I rooted my phone today and I downloaded the app, "ROM Manager," and downloaded a ROM from it, which I read that I'm not supposed to do, afterwards. Now, whenever I turn my phone on, it only shows the Cyanogenmod boot animation. I read in another thread that I should clear the cache, which I did, but it did not help. Should I try and flash it to the stock? Please help! I am inexperienced with this and I don't know what to do. Thanks in advance!
Click to expand...
Click to collapse
Alright. First off: what OS were you running before you went to cyanogenmod? was it 4.0.4? 4.1.x? 4.2.x? or 4.3.x?
Second, give us more information about the phone.
Third, you might have to go into recovery mode, wipe your phone (theres two options in the main menu, and one in the advanced called wipe dalvik). Then youll have to reinstall Cyanogenmod.
ChinDaChin said:
Alright. First off: what OS were you running before you went to cyanogenmod? was it 4.0.4? 4.1.x? 4.2.x? or 4.3.x?
Second, give us more information about the phone.
Third, you might have to go into recovery mode, wipe your phone (theres two options in the main menu, and one in the advanced called wipe dalvik). Then youll have to reinstall Cyanogenmod.
Click to expand...
Click to collapse
Your phone will get stuck if you did not clear the dalvik as well as the cache. I would recommend first clearing cache again and also dalvik before rebooting back into the operating system or doing something else which may not be necessary.
shortydoggg said:
Your phone will get stuck if you did not clear the dalvik as well as the cache. I would recommend first clearing cache again and also dalvik before rebooting back into the operating system or doing something else which may not be necessary.
Click to expand...
Click to collapse
I have already tried to clear the cache and the dalvik and then did a reboot but it didn't change anything.
shortydoggg said:
Your phone will get stuck if you did not clear the dalvik as well as the cache. I would recommend first clearing cache again and also dalvik before rebooting back into the operating system or doing something else which may not be necessary.
Click to expand...
Click to collapse
ChinDaChin said:
Alright. First off: what OS were you running before you went to cyanogenmod? was it 4.0.4? 4.1.x? 4.2.x? or 4.3.x?
Second, give us more information about the phone.
Third, you might have to go into recovery mode, wipe your phone (theres two options in the main menu, and one in the advanced called wipe dalvik). Then youll have to reinstall Cyanogenmod.
Click to expand...
Click to collapse
I was running the stock jellybean before I installed cryogenmod...my phone is a galaxy s3 it47 (AT&T) network unlocked phone. Also, at the bottom in recovery mode it says
ClockworkMod Recovery v6. 0. 4. 5
I'm not sure whether or not this is important but it is the only thing that I can think of to tell you about my phone.
I don't care whether we keep my data, I just want it to be able to turn on! Can I just restore it using Odin somehow? I tried the wipe user memory option in recovery mode and that didn't help...
Personally, I hate both ROM manager and clockworkmod.
It sounds like you just need to wipe data (or factory reset), cache and dalvik, and then reboot. If that doesn't work, then you might have flashed a version of cyanogenmod that may not be compatible with your bootloader, and may have to manually try another ROM.
shortydoggg said:
Personally, I hate both ROM manager and clockworkmod.
It sounds like you just need to wipe data (or factory reset), cache and dalvik, and then reboot. If that doesn't work, then you might have flashed a version of cyanogenmod that may not be compatible with your bootloader, and may have to manually try another ROM.
Click to expand...
Click to collapse
I tried to do a factory reset, it didn't help as far as I know. How do i manually try another rom?
dallinrigby said:
I tried to do a factory reset, it didn't help as far as I know. How do i manually try another rom?
Click to expand...
Click to collapse
Can you tell us what version of touchwiz you were running before you tried rooting it? It's important if it's past 4.3.x, or before 4.3.x. Do the following if you were running 4.3.x before you rooted.
Go to http://download.cyanogenmod.org/?device=d2att&type=
Choose the one named: cm-10.2.0-d2att.zip
Download it and save it to your SD Card.
Go here and download 10.2: http://wiki.cyanogenmod.org/w/Google_Apps and put it on your SD card with the above .zip.
Once thats done, power off your phone. Go into recovery mode (volume up + home + power).
Wipe Data/Factory Reset
Wipe Cache partition
Advanced -> wipe Dalvik Cache
Go back, and choose Install Zip
Choose zip from /storage/sdcard (find your cm10.2 zip, run it. then run the gapps)
After you "installed" both zips, go back to the main menu and reboot system now
This will be a clean install of 10.2.
FYI: Clockworkmod Recovery is v6.0.4.5, so you have the most up to date.
ChinDaChin said:
Can you tell us what version of touchwiz you were running before you tried rooting it? It's important if it's past 4.3.x, or before 4.3.x. Do the following if you were running 4.3.x before you rooted.
Choose the one named: cm-10.2.0-d2att.zip
Download it and save it to your SD Card.
Once thats done, power off your phone. Go into recovery mode (volume up + home + power).
Wipe Data/Factory Reset
Wipe Cache partition
Advanced -> wipe Dalvik Cache
Go back, and choose Install Zip
Choose zip from /storage/sdcard (find your cm10.2 zip, run it. then run the gapps)
After you "installed" both zips, go back to the main menu and reboot system now
This will be a clean install of 10.2.
FYI: Clockworkmod Recovery is v6.0.4.5, so you have the most up to date.
Click to expand...
Click to collapse
I don't know what version I had. Is there a way for me to tell? I just had whatever I bought it with, I never downloaded anything else.
It says on that second link to download Torrent or via It Vends, is this the right place, and if so what do I pick?
Thanks by the way, also is there a way I could do this with Odin?
dallinrigby said:
I don't know what version I had. Is there a way for me to tell? I just had whatever I bought it with, I never downloaded anything else.
Click to expand...
Click to collapse
I used Goo.im. It's a funky looking website, but it's legitimate. I didn't do this with Odin, I used Cyanogenmod Installer :silly:
If you follow what I posted before, it will update everything, and you will run cyanogenmod 10.2. (What I'm running on my s3). HOWEVER, it will update your phone to 4.3. This means you cannot downgrade it, or it will be bricked. By downgrade, I mean you will not be able to run anything before 4.3. (So you can ONLY install roms that are 4.3, or jellybean).
I'm pretty sure you already updated everything since its stuck in the boot loop.
Any chance you did a nandroid backup(before you did the root)? If not, you've got nothing to lose and might as well go through with CM 10.2 (in my honest opinion).
ChinDaChin said:
I used Goo.im. It's a funky looking website, but it's legitimate. I didn't do this with Odin, I used Cyanogenmod Installer :silly:
If you follow what I posted before, it will update everything, and you will run cyanogenmod 10.2. (What I'm running on my s3). HOWEVER, it will update your phone to 4.3. This means you cannot downgrade it, or it will be bricked. By downgrade, I mean you will not be able to run anything before 4.3. (So you can ONLY install roms that are 4.3, or jellybean).
I'm pretty sure you already updated everything since its stuck in the boot loop.
Any chance you did a nandroid backup(before you did the root)? If not, you've got nothing to lose and might as well go through with CM 10.2 (in my honest opinion).
Click to expand...
Click to collapse
Okay, so now it says Android system recovery <3e> at the top and at the bottom is this:
#MANUAL MODE#
--Applied Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC
Then when I pushed install from sdcard it said E:failed to verify whole file signature
Do i need to unzip it?
dallinrigby said:
Okay, so now it says Android system recovery <3e> at the top and at the bottom is this:
#MANUAL MODE#
--Applied Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC
Then when I pushed install from sdcard it said E:failed to verify whole file signature
Click to expand...
Click to collapse
Don't lose hope, but every site/page I check, it says the error is with you flashing through Rom Manager. It's okay though, there has to be a solution.
I'm going to continue looking for the solution. If you could try and remember what version of the OS you were running before you tried to root, it would help out SO MUCH!
LOL., I forgot to hit post on this.
And no, don't unzip it. The phone can read it fine.
Anyway, after some quick reading, a few people are saying its either your rom that is corrupted, or you don't have the proper recovery. It can't be the rom, because the rom was downloaded from the source. So chances are its your recovery. I'm not sure if you can download the CWM recovery, and flash it from recovery. (if that makes sense?)
ChinDaChin said:
Don't lose hope, but every site/page I check, it says the error is with you flashing through Rom Manager. It's okay though, there has to be a solution.
I'm going to continue looking for the solution. If you could try and remember what version of the OS you were running before you tried to root, it would help out SO MUCH!
LOL., I forgot to hit post on this.
And no, don't unzip it. The phone can read it fine.
Anyway, after some quick reading, a few people are saying its either your rom that is corrupted, or you don't have the proper recovery. It can't be the rom, because the rom was downloaded from the source. So chances are its your recovery. I'm not sure if you can download the CWM recovery, and flash it from recovery. (if that makes sense?)
Click to expand...
Click to collapse
I don't really understand this stuff very much, and also I am pretty sure my android version before was 4.1.2, that's jelly bean right? is that what you meant?
If it's CWM that is the problem, you can download TWRP and flash it via Odin if you can get into download mode. Then, you can use TWRP to flash a custom ROM.
audit13 said:
If it's CWM that is the problem, you can download TWRP and flash it via Odin if you can get into download mode. Then, you can use TWRP to flash a custom ROM.
Click to expand...
Click to collapse
Where do i get TWRP? It doesn't say that I have Clockwork anymore, since I factory reset it
dallinrigby said:
I don't really understand this stuff very much, and also I am pretty sure my android version before was 4.1.2, that's jelly bean right? is that what you meant?
Click to expand...
Click to collapse
Sorry.
I'm kind of conflicted on what's going on with your phone. It is partially a problem with going through Rom Manager to flash cyanogenmod.
audit13 said:
If it's CWM that is the problem, you can download TWRP and flash it via Odin if you can get into download mode. Then, you can use TWRP to flash a custom ROM.
Click to expand...
Click to collapse
I guess you can try TWRP. I haven't used TWRP so I can't comment on it. I'll try finding an explanatory video that is simple to follow. (Don't throw out Cm10.2, or the gapps. You will need those to get Cyanogenmod on your phone!)
Hey I have a problem here.I have a dev edition Note 4. I have been running EMSpoilt's first ROM ([Rom][N910VOYU1ANI1][4.4.4] Stock Root Deodex/Knox-Free Updated 11/24/2014) for about 2 weeks now. It was running great smooth as butter until now. I tried flashing his new [Rom][N910VVRU1ANJ5][4.4.4] Stock Root Odex/Knox-Free) but my phone wouldn't boot up, it wouldn't get past the first Samsung screen just keeps restarting. I made sure to follow step by step instructions. Wiped everything but my SD card. Tried it 2 more times and nothing. Tried to wipe cache and all that. Nothing helped. So I decided to restore back to my backed up ROM. Once restored it started to act weird. My finger print scanner doesn't work and I can't download anything another than apps from app store...the phone is very glitchy and almost unusable.. almost like it has a virus. It did get pretty hot when I was flashing the ROM I hope I didn't fry anything. I tried and tried to reset things but no luck. I don't have a backup of stock Dev ROM unfortunately...is there a way to reset back to stock(out of the box state)? I still have root and TWRP recovery works fine.
Anyone help please?
Sent from my SM-N910V using XDA Free mobile app
Sent from my SM-N910V using XDA Free mobile app
shpotik said:
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
If you want to get the NJ5 ROM up and running without issues I would suggest flashing the NJ5 stock restore tar file in Odin, then flash TWRP recovery in Odin. Once that is done boot into TWRP and flash SU, then flash the ROM. I was having the same issue yesterday and this fixed things for me.
+1 on what airmaxx23 has recommended. Caution: Make damn sure you ODIN the stock restore file intended for the DE, not the retail. If you just want to get back to a fully functional DE without the ROM then ODIN the stock restore file, ODIN TWRP and flash SUPERSU in recovery. You don't have to flash the ROM.
jpcalhoun said:
+1 on what airmaxx23 has recommended. Caution: Make damn sure you ODIN the stock restore file intended for the DE, not the retail. If you just want to get back to a fully functional DE without the ROM then ODIN the stock restore file, ODIN TWRP and flash SUPERSU in recovery. You don't have to flash the ROM.
Click to expand...
Click to collapse
Can you point me into direction of stock restore file? Thanks
Sent from my SM-N910V using XDA Free mobile app
shpotik said:
Can you point me into direction of stock restore file? Thanks
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
I linked all the files you need for the DE in my original response.
shpotik said:
Can you point me into direction of stock restore file? Thanks
Sent from my SM-N910V using XDA Free mobile app
Click to expand...
Click to collapse
Here you go: http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937. Make sure you go to post #2 and select the stock restore file for the DE.
I am having problems with mine, too
After getting into trouble yesterday with a phone that stuck in Verizon logo screen, I was able to restore from backup.
Then I started noticing weird things that I believe were working a day ago.
I cannot download any email attachments, cannot create folders on sdcard, cannot install xposed or even install Fora offline dictionary files I downloaded from PlayStore. I never flashed custom ROMs on my DE, just flashed TWRP and then rooted it. I am still running original SW N910VOYU1ANI1. Screenshots and photos are saved just fine (burst shots on sdcard and regular photos on extsdcard).
Any Ideas? I've tried to restore from pre-root backup, then restored my image that has root and some applications but cannot move from there.
inseek said:
After getting into trouble yesterday with a phone that stuck in Verizon logo screen, I was able to restore from backup.
Then I started noticing weird things that I believe were working a day ago.
I cannot download any email attachments, cannot create folders on sdcard, cannot install xposed or even install Fora offline dictionary files I downloaded from PlayStore. I never flashed custom ROMs on my DE, just flashed TWRP and then rooted it. I am still running original SW N910VOYU1ANI1. Screenshots and photos are saved just fine (burst shots on sdcard and regular photos on extsdcard).
Any Ideas? I've tried to restore from pre-root backup, then restored my image that has root and some applications but cannot move from there.
Click to expand...
Click to collapse
Here is what I would do if I were you:
1. Go into TWRP Recovery and do a complete wipe (system, data, cache, delvik). Do not select recovery.
2. While in TWRP do a factory reset
3. In TWRP, RESTORE the backup you mentioned.
4. While in TWRP clear cache and delvik again
5. Power off the phone and remove the battery
6. Replace the battery and boot
7. If the phone boots normally then power off the phone, boot into recovery and flash SuperSU (Do not try to restore any "image", just flash SuperSU.zip)
8. Reboot the phone
jpcalhoun said:
Here is what I would do if I were you:
1. Go into TWRP Recovery and do a complete wipe (system, data, cache, delvik). Do not select recovery.
2. While in TWRP do a factory reset
3. In TWRP, RESTORE the backup you mentioned.
4. While in TWRP clear cache and delvik again
5. Power off the phone and remove the battery
6. Replace the battery and boot
7. If the phone boots normally then power off the phone, boot into recovery and flash SuperSU (Do not try to restore any "image", just flash SuperSU.zip)
8. Reboot the phone
Click to expand...
Click to collapse
Although I did it already almost the same way multiple times since yesterday, I'll try it again.
How do I do #2 in your list from TWRP?
Thanks.
inseek said:
Although I did it already almost the same way multiple times since yesterday, I'll try it again.
How do I do #2 in your list from TWRP?
Thanks.
Click to expand...
Click to collapse
Go to "Wipe" then "Format Data" then type "yes" and hit "go". This will completely remove all data. Under "Advanced Wipe" check "dalvik", "system", "data", and "cache" and wipe those as well.
If that doesn't work you're going to have to start fresh.
inseek said:
Although I did it already almost the same way multiple times since yesterday, I'll try it again.
How do I do #2 in your list from TWRP?
Thanks.
Click to expand...
Click to collapse
When you're in TWRP and select Wipe, there will appear a "swipe bar" that when swiped will perform a Factory Reset. It is the first screen you see when you select Wipe on the home screen. Do the Factory Reset and then clear cache, delvik, system and data. You can do the Factory Reset before clearing cache etc or after clearing cache etc. It really doesn't make a difference in what order you do the Factory Reset, just do it.
If this process doesn't get you back to normal then another option is to flash the stock restore file for NJ5 availble in the Android Development Section. But, lets do the process I've outlined first.
jpcalhoun said:
Here is what I would do if I were you:
1. Go into TWRP Recovery and do a complete wipe (system, data, cache, delvik). Do not select recovery.
2. While in TWRP do a factory reset
3. In TWRP, RESTORE the backup you mentioned.
4. While in TWRP clear cache and delvik again
5. Power off the phone and remove the battery
6. Replace the battery and boot
7. If the phone boots normally then power off the phone, boot into recovery and flash SuperSU (Do not try to restore any "image", just flash SuperSU.zip)
8. Reboot the phone
Click to expand...
Click to collapse
I did everything up to the #7, then powered the phone. I am getting all bunch of errors like "com.sec.phone has stopped" and other I don't remember. It shouldn't be this way, right?
Then I powered the phone off and on again, this time I got the setup wizard without error messages and flashed SU and then installed Xposed. So far, so good. Will install couple apps to see how it goes.
Thanks, jpcalhoun!
airmaxx23 said:
If you want to get the NJ5 ROM up and running without issues I would suggest flashing the NJ5 stock restore tar file in Odin, then flash TWRP recovery in Odin. Once that is done boot into TWRP and flash SU, then flash the ROM. I was having the same issue yesterday and this fixed things for me.
Click to expand...
Click to collapse
do i have to extract the file with 7zip ?
inseek said:
I did everything up to the #7, then powered the phone. I am getting all bunch of errors like "com.sec.phone has stopped" and other I don't remember. It shouldn't be this way, right?
Then I powered the phone off and on again, this time I got the setup wizard without error messages and flashed SU and then installed Xposed. So far, so good. Will install couple apps to see how it goes.
Thanks, jpcalhoun!
Click to expand...
Click to collapse
Glad you got it working. I'd have to see the error messages to try, I emphasize try, to determine what might be causing them. Often after flashing or using ODIN to install software you'll get an error message until the system has been rebooted. You should probably power off you phone, again, pull the battery, replace the battery and reboot to see if you continue to get error messages. You shouldn't be getting error messages during boot unless you have installed something that has turned a service off or has altered a service that the system is asking for (that's not technically well stated, but I think you get the point). Exposed Framework is great and enables users to customize many things in Android. But, not all the modules work the same on every device, and in fact some modules will not work at all on the Note 4. If you're trying to run a module that does not work as advertised then you should uninstall that module or not select that particular customization. A misbehaving module can cause problems that manifest themselves in funny ways.
shpotik said:
do i have to extract the file with 7zip ?
Click to expand...
Click to collapse
Yes, extract it with 7zip.