Hello guys,
I had rooted my phone (Samsung note 3 SM-N9005) rooted, but afterall decided to go back to stock. The main problem is after flashing it becomes pretty annoying. It works like ice untill I add some apps like facebook, messenger and other. It was pretty great and not laggy before rooting, so it is strange that after flashing stock rom it becomes sluggish.
Could it be that I do something wrong to flash it?
What did I do?
I boot into TWRP recovery and wipe Data, Dalvic cache, system and cache.
Using Odin I flash the stock firmware (1 File) downloaded from samsung -updates page. In the meniu of Odin I choose only F.RESET and REBOOT.
After that I boot the stock and wipe data and factory reset once more.
I read others do have issues when writing stock ROM on top of old one. But I do wipe everything. System files take up to 5.73Gb when fresh installed.
What could be wrong? Anyone had same issues? Help needed. Thank you.
I don't think you did anything wrong. My first rom was the official 6.0 rom. When I put it in, two buttons stopped working... and so I had to jump to Lineage OS to get back an "undamaged" phone. I don't think there is any going back.
Related
I'm just wondering if my procedure for updating my ROM is correct, as I've only owned a smartphone for about a month, and have only flashed once.
Basically before I was running AOKP build 2 and Franco kernel r79 (or thereabouts) on my Nexus 4. I wanted to upgrade to AOKP build 3, so I backed stuff up, booted up in recovery, wiped my data, cleared the cache, then cleared the Dalvik cache before rebooting. Then it took me back to the initial setup screen, but I got confused when AOKP and Franco Kernel was still installed. I figured I should just open up the browser, download build 3 to the device (since everything is wiped), and then I'll flash that on top of build 2.
Am I supposed to flash back the stock ROM and kernel, or does it not matter since I will be running the same custom ROM?
Likewise, if I wanted to change my custom ROM (like install PA3 or something), then I would definitely need to flash back the stock rom and kernel before proceeding, am I right?
Smeghead_ said:
I'm just wondering if my procedure for updating my ROM is correct, as I've only owned a smartphone for about a month, and have only flashed once.
Basically before I was running AOKP build 2 and Franco kernel r79 (or thereabouts) on my Nexus 4. I wanted to upgrade to AOKP build 3, so I backed stuff up, booted up in recovery, wiped my data, cleared the cache, then cleared the Dalvik cache before rebooting. Then it took me back to the initial setup screen, but I got confused when AOKP and Franco Kernel was still installed. I figured I should just open up the browser, download build 3 to the device (since everything is wiped), and then I'll flash that on top of build 2.
Am I supposed to flash back the stock ROM and kernel, or does it not matter since I will be running the same custom ROM?
Likewise, if I wanted to change my custom ROM (like install PA3 or something), then I would definitely need to flash back the stock rom and kernel before proceeding, am I right?
Click to expand...
Click to collapse
Well since I really only have experience with a tablet and older cell phone I can only speak of my experiences with those. My tablet runs 4.2.2 and the phone 2.2. With both devices I have never had to flash them back to stock to flash an update. Usually a data and cache wipe was sufficient although I will wipe the whole system when flashing a huge update on the tablet.....like from GB to JB.
What helpful people told me when I asked the same question was...
When going to a very different (including the same ROM going to a new android version, ie 4.1 => 4.2) ROM (as in, not just doing a small update on the current one) :
Wipe both caches, wipe /system, wipe /data, and wipe internal sd card and factory reset.
Then flash what you want - ROM => Kernel (if desired) => GAPPs
Wipe caches again.
Done!
I don't know about your particular phone and those ROMs. Is AOKP 2 to 3 a big change ? If so, simply writing 3 over 2 could cause some major problems. I totally messed up and did something like that once and while it wasn't a huge deal I had to start over and do it again because it wasn't usable.
In regards to your description of what you did, you didn't wipe /system, so you didn't wipe your system and so it was still installed like you saw. You'll need to "start over" and wipe everything again. Since the N 4 doesn't have an external SD, I'm guessing you guys wipe /system and like, push the ROM to be flashed to the internal storage ? Maybe ? I have no idea - I've always had an external SD, but since it's a Nexus device I'm sure the procedure is well-covered !
My Kindle Fire tablet also does not actually have an SD card either.....the 8GB memory has been partitioned and originally I would have 5GB available out of 8 which would act as the SD card and 1.09GB for internal or "phone" memory. I have mine even more scrapped down as this one has the ability to either boot into CM7(GB) or the newest CM10.1(JB).
Say for example I went from Android 4.1.2 to 4.2.2.....that's a pretty big update......I would do a full wipe meaning doing it in this order: factory reset, wipe cache, wipe dalvik, and wipe system.
If I wanted to flash a little update of my current 4.2.2 where only some slight tweaks were applied I would just wipe cache and dalvik only. There are times when this simple flash wipe technique WON'T work and you'll probably realize it real quick. There could be any one of a million bugs that could occur and usually they are pretty noticeable. If that happens (sometimes it will, sometimes it won't) the worst case scenario is just going ahead and doing the full wipe.
I'm not knowledgeable on AOKP ROMs so I don't want to venture there. Boot loops are a whole different story and you might want to educate yourself as much as possible because they can happen. I had a couple occurances with a boot loop not too long ago as I was messing with a system font editor and it caused a boot loop. I didn't panic.....I already researched how to handle them so getting it back online was quite easy.
Hope my rambling has helped even a little bit.....
As long as you are just updating the same Rom, you can usually just flash it over (unless the Rom-maker says different).
If there are some fundamental changes in the Rom update, or you are switching to another Rom, then you should wipe it all.
To make it all a bit easier, you can use the Megawipe script:
http://forum.xda-developers.com/showthread.php?t=1832326
Along with the Aroma installer, it's just a few clicks to clean it all up, and ready for a fresh install
ive been running into a strange issue installing roms lately. I can install anything touchwiz no problem and they run great. but for some odd reason if I install any of the numerous aosp roms the just hang on first boot. ive tried almost every aosp there is and they all sit there and hang, ive even let a few sit for hours with no luck. yet touchwiz will boot fine in just a few minutes. anyone have any suggestions or ideas?
Have u done a clean wipe factory reset wipe delvk catche.. Wipe everything clean.. Some stuff from the tw roms could stay behind.. Wen ppl change from aosp rom to a tw rom they use synergy rom cuz it does a clean install .. I could be wrong about this
Just be sure to wipe data/cache. The ROM zip install erases system for u.
Sent from my SCH-I535 using Tapatalk 4
Erasing data problem
I have unrooted Verizon S3.
It was working ok until I decided to put some new ROM. I instaled Synergy S3 r420 rom. It worked OK, but did not have mobile internet. WiFi and mobile hotspot were working fine. I decided to put back my old system, not to mess around any more, and went into CWM mode.
After entering CWM I tried wipe out/factory reset but it stacked at Formatting /data
Previous formating of cache and wiping of Dalvik went OK.
Part of the message was E:unknown volume for path [sd/ext]
What di I done with my phone? Is it soft bricked or what?
I can still boot last ROM, and is functional
How can I return my phone to the state saved in my CWM backup ?
Thanks!
EDIT
I have tryed to instal a different ROM - Hyperdrive, and install went normaly. At the end asked me to reboot and I said OK. Then, upon rebooting, a Warning message appeared warning me that non Verizon softvare is detected and that I should take the phone to them.
Is there anything to do to reverse this state?
You need to use odin to restore stock
Sent from my SCH-I535 using Tapatalk 4
So I can't get 4.3 ROMs to reboot. I have tried several different Roms and always the same thing. Mainly Pac. It loads the first time fine, but when I reboot it just hangs on the Galaxy S4 screen. I have updated TWRP to 2.6 and tried wiping cache and dalvik between flashing the ROM and gaaps. And still nothing the only way I can get to do anything after that is to reformat and do a factory reset and the reflash the ROM. Any help would be greatly appreciated.
captainjibblet said:
So I can't get 4.3 ROMs to reboot. I have tried several different Roms and always the same thing. Mainly Pac. It loads the first time fine, but when I reboot it just hangs on the Galaxy S4 screen. I have updated TWRP to 2.6 and tried wiping cache and dalvik between flashing the ROM and gaaps. And still nothing the only way I can get to do anything after that is to reformat and do a factory reset and the reflash the ROM. Any help would be greatly appreciated.
Click to expand...
Click to collapse
So just in case anyone else runs into this problem, I figured it out myself. I am running the MDK build so the only thing you would change is th rooting process.
1. Reflash Stock using ODIN
2. Reroot http://forum.xda-developers.com/showthread.php?t=2381382
3. Install newest 2.6.3 TWRP
4. Back up Stock
5. Flash 4.3 ROM and 4.3 Gapps
I'm not sure if it was reflashing stock or the newest update to twrp but whichever. It worked.
Way back when, I modified my 4.1.2 tab so I could use the Switchme app. Since it hasn't had a software update since then, I need to unmodify my system, so I did a hard reset but that doesn't seem to unmodify it so I can get it updated. Do I have to flash to a stock ROM, or won't that help either? I've done a hard reset twice now and restoring my Samsung account does seem to work either. Help PLEASE!
Nope it does not.
Stoney60 said:
Way back when, I modified my 4.1.2 tab so I could use the Switchme app. Since it hasn't had a software update since then, I need to unmodify my system, so I did a hard reset but that doesn't seem to unmodify it so I can get it updated. Do I have to flash to a stock ROM, or won't that help either? I've done a hard reset twice now and restoring my Samsung account does seem to work either. Help PLEASE!
Click to expand...
Click to collapse
Factory reset only Clears out use added content apps and Personal Settings. To get back to stop you will ..
1 Download the Correct Latest Version Of Android From Sam-mobile or Samsung For your Device.
2. Download odin for your device
3. Make sure you can access your device from windows or os your using.
4. Follow instructions for getting into download mode and flashing the samsung firmware with odin from your computer.
5 . Reboot the device and Leave it be..
Never flash anything on any Device until you know how to get back.
There are many Threads with step by step details on the above. even many youtube videos..
Good Luck
Hey,
I don't think you have to flash back to a stock ROM in order to upgrade to a different ROM. I was able to upgrade my tab with 4.1.2 (I can't remember what ROM it was) right to GNABO then a few hours later to Carbon, and a few hours later to Hyperdive and I'ts running fine with no issues besides the Aroma freezing, but what else is new...
You shouldn't have to flash back to a stock ROM to flash to a modified ROM, reason being is the modified ROM Flashes over the current ROM on the device, so the original ROM will be deleted anyways. The new ROM contains the updates for you, that's the advantage of androids. I recommend trying a few OS's before you pick the one for you stick with it. If you want to go stock there is a thread somewhere in the DEV section with the stock ROM just do some searching.
Make sure when you install a ROM to ;
Backup your device and make sure to keep a copy of the backup to your pc!
Boot into CWM Recovery or TWRP
Wipe data / factory reset
Wipe cache
Wipe dalvik cache
Install ROM from SD
Good Luck
I rooted my S6 SM-G920F, after root it is starting to act weird, ANDROID OS is using like 50-80% of my CPU...
I used odin to flash twrp-3.1.1-0, later installed SuperSU-v2.82...Everything was great untill i booted up my phone, it was getting hot etc...
I havent messed around with kernel, custom roms or changed CPU frequency's. If anyone have any suggestions how to fix theese freezes and lags i would be really happy to read them. I did wipe dalvik cachce and regular cache, but it got even worse. And battery dies out really fast too....
P.s I didnt make recovery, because i have rooted several phones and nothing ever has happened. I guess this was my mistake. I remember this happened to my S3 neo but after just ignoring all that mess it just disappeared...
Try installing the Latest Firmware stock from the SamsungFirmwares site for your region and model,
Then flash TWRP and Flash Latest Magisk.
Magisk already comes with Root,
Do not forget to Clear Cache and ART / Dalvik after Flash Magisk.
killerBRs said:
Try installing the Latest Firmware stock from the SamsungFirmwares site for your region and model,
Then flash TWRP and Flash Latest Magisk.
Magisk already comes with Root,
Do not forget to Clear Cache and ART / Dalvik after Flash Magisk.
Click to expand...
Click to collapse
What if my country isnt listed there? (Latvia)
Sooo ye, i accidently wiped everything on my phone, system etc...Now downloaded a stock rom installed it with twrp, its meant to be for poland region, does it make a big difference? (i am from Latvia)
jakey9 said:
Sooo ye, i accidently wiped everything on my phone, system etc...Now downloaded a stock rom installed it with twrp, its meant to be for poland region, does it make a big difference? (i am from Latvia)
Click to expand...
Click to collapse
Not if your calls and internet are working nope. Should be ok