Hi all,
I'd like to fully format my device Samsung P1000 (deleting all files and data) before installing a new version of Omnirom (I've actually installed Omnirom of 2014.09.30)
Which is correct procedure? Which wipe I have to do more than factory/cache/dalvik? And in which way I will install the new version of Omnirom? Will I have installed the recovery mode yet?
Thanks
Related
Hi,
I tried to install Jelly Bean Custom Rom for Galaxy S Plus GT I9001. but I got problem. The ROM is stuck on Boot Logo Looping.
Here is what I do :
1. Flash Stock
2. Install CWM
3. Boot into CWM
4. Factory Reset, Wipe Dalvik Cache, Format System
5. Install ZIP
6. Reboot
Anything I did wrong ?
I have tried 2 custom rom :
1. CM 10.1
2. Pac Man
Both of them behave the same (Stuck on Boot Logo).
Any help is appreciated.
Thanks.
yokowasis said:
Anything I did wrong ?
Click to expand...
Click to collapse
You need to follow flashing guide , look in wiki according to ROM you have chosen or My Android Solutions (link below) to get out of Boot Loops
Check this out! Links to useful Guides and " Banned " Documentaries
xsenman said:
You need to follow flashing guide , look in wiki according to ROM you have chosen or My Android Solutions (link below) to get out of Boot Loops
Check this out! Links to useful Guides and " Banned " Documentaries
Click to expand...
Click to collapse
Well actually, that is the exactly step the ROM needed to be installed as stated on the thread. Actually, that is how I install all other custom rom. Never found any other way to install the ROM. But for some reasons it keep bootlopping. Stop the bootlooping is easy. Just flash the stock ROM. But that's not what I want. I want to use the custom ROM. FYI. I tried 2 ROMS and both of them behave the same. Bootloop.
yokowasis said:
Well actually, that is the exactly step the ROM needed to be installed as stated on the thread. Actually, that is how I install all other custom rom. Never found any other way to install the ROM. But for some reasons it keep bootlopping. Stop the bootlooping is easy. Just flash the stock ROM. But that's not what I want. I want to use the custom ROM. FYI. I tried 2 ROMS and both of them behave the same. Bootloop.
Click to expand...
Click to collapse
Can you point to me which Custom ROM you are trying to install and where it tells you to format system? Also you must understand certain i9001 ROM's need specific CWM and will be mentioned on developers thread..using others would fail. So refer to i9001 Wiki, as its one of the best guide for i9001
Look at what the wiki says
CyanogenMod 10.1 (Based on Android 4.2.2 / Jelly Bean) It's developed by AriesveDevConnection Team
Thread : CyanogenMod 10.1
All major components of the i9001 work except for FM radio.
Installation:
Before you install CM10.1: Preparation (First three are optional. If you want to start fresh, these can be skipped)
Install AppBak from Market, run it and save a list of all your apps.
Install SMS Backup and Restore from Market, run it and backup your SMS history.
Install Call Logs Backup and Restore from Market, run it and backup your call log history.
Boot into CWM5 recovery. Make a full backup. You will need this backup later if you decide to go back to your previous ROM and data.
WARNING: Many apps will Force Close crash if you restore data from a previous ROM.
Use CWM 5.5.0.4 Flashable zip version | Odin version OR CWM 6.0.3.2 with safe kernel (no EMMC bug)
For Odin version of CWM 5.5.0.4, flash recovery-clockwork-5.5.0.4-ariesve.tar.md5 as One Package using the regular AriesVE.ops (Tutorial)
WARNING: Only use this recovery to flash CM10.1, otherwise, you risk bricking your phone!
CyanogenMod10.1 comes as a zip that is installed inside recovery. Download the latest build and put the zip file into the sdcard.
Wipe data / Factory Reset
Wipe cache
Advanced > Wipe dalvik cache
Install zip from sdcard (choose cm-10.1-20130607-dev_connection_team-release1-ariesve.zip)
Flash the gapps-jb-20130301-signed.zip
You must flash gapps after every upgrade to CM10 since /system is formatted, wiping your previous add-ons.
Reboot phone.
After you setup your Google account, reinstall the three apps from Market in order to restore most of your apps, call log and SMS history.
WARNING: Do not restore backup data of system apps!
If you restore a bad backup with cached settings in telephony.db in data/data/com.*.*.telephony it can break MMS.
It seems that restoring backups can also break Calendar sync.
Notes:
Upgrades from previous versions of CM10.1 are the same process as install, except you do not need to wipe anything. Contrary to popular belief, you do not need to even wipe cache and dalvik-cache when upgrading between CM10.1 versions. You only need to wipe if you are doing a major upgrade, switching to a different ROM entirely, or attempting to fix bugs caused by bad backups or corrupt app data.
Under CyanogenMod 10.1, your external SD card can be found under /storage/sdcard1
Reboot into recovery from power menu not working?
Turn off "touch sounds" option in sound settings.
No Developer options & Performance setting?
Tap Build number for 7 times in Settting > About phone
Want to see something fun? CM10.1 has an easter egg that can be activated in System Settings -> About phone. Click the "Android version 4.2.2 / CyanogenMod version" entry several times very fast. The screen will clear and show an Android JellyBean / CyanogenMod icon. Click and hold on the JellyBean / CyanogenMod icon. It will zoom in and activate a lots of flying JellyBean / CyanogenMod icon.
CyanogenMod 10.1 Custom ROMs
3.0.x Kernel
SlimBean
Tiger-JellyBean
PAC-man
ParanoidAndroid
CarbonROM
Revenge
3.4.x Kernel
LiquidSmooth
ThinkingBridge
JellyBear
Baked BlackBean
XYAOSP Xylon
RootBox
M.O.W JB
Click to expand...
Click to collapse
Check this out! Links to useful Guides and " Banned " Documentaries
yokowasis said:
Hi,
I tried to install Jelly Bean Custom Rom for Galaxy S Plus GT I9001. but I got problem. The ROM is stuck on Boot Logo Looping.
Here is what I do :
1. Flash Stock
2. Install CWM
3. Boot into CWM
4. Factory Reset, Wipe Dalvik Cache, Format System
5. Install ZIP
6. Reboot
Anything I did wrong ?
I have tried 2 custom rom :
1. CM 10.1
2. Pac Man
Both of them behave the same (Stuck on Boot Logo).
Any help is appreciated.
Thanks.
Click to expand...
Click to collapse
Hi,
after I tried flashing from stock to alternative ROM I had exactly the same. I resolved it after flashing two times (Flash - reboot into recovery - Flash again)
Hope it helps
Hello everyone;
I'm all new to this rooting and flashing thing, and I've been reading lots of tutorials and wikis, but still some questions remain:
1. I have a carrier-unlocked i9305t (It came with carrier software and the carrier logo shows up everytime I start the phone, but it is unlocked to any sim-card in my country). Should I flash the device to CyanogenMOD 11 (which is available for i9305, not i9305t), would my phone brick? Or, in other words, what are the main differences between i9305 and i9305t and can I install a custom ROM for i9305 in i9305t?
2. What's the difference between rooting and installing a custom recovery (such as TWRP)? Will installing a custom recovery give me root acces to my phone?
[edit] 2.1. So I've found that I can root my phone through a custom recovery by flashing a SuperSu (super user) file on it. Where can I find a safe SuperSu file for i9305t?
3. I've found this tutorial (can't post the link thanks to forum rules, sorry!) for installing CyanogenMOD 11 in i9305 in which there's no mention to rooting the device: the process consists of installing a custom recovery in the phone and, from there, flash the CyanogenMOD 11 ROM. Is this correct and safe?
Then again, thanks for the help and sorry for the bad english, I'm not a native speaker.
Cheers!
You can flash any i9305 tom on your phone. The t just has to do with the frequency bands your phone uses. All you need to do is flash a custom recovery. Root is included in cm 11 so you only need to flash that
Sent from my GT-I9305 using xda app-developers app
I just got a i9305T too, rooted, downloaded latest CM 11 nightly, when tried to intall zip it gave me Status 7 error, something about my device being a 'm0' and so not compartible.
I somehow wiped the stock system and can't mount USB with the TWRP... Now I'm downloading things so I can flash the stock and get back to square one.
What's going on and what can I do? Will I always have the latest CM Roms? Otherwise I'm somehow giving up this phone. Please help me.
vicastro said:
I just got a i9305T too, rooted, downloaded latest CM 11 nightly, when tried to intall zip it gave me Status 7 error, something about my device being a 'm0' and so not compartible.
I somehow wiped the stock system and can't mount USB with the TWRP... Now I'm downloading things so I can flash the stock and get back to square one.
What's going on and what can I do? Will I always have the latest CM Roms? Otherwise I'm somehow giving up this phone. Please help me.
Click to expand...
Click to collapse
I am a CM i9305T user here. For me, TWRP gives me error codes but then changing to ClockWorkMod recovery (latest version) solved error code 7. I used everything for i9305 for my i9305T phone and I have no problems. Try installing ClockWorkMod and flash CM + GApps.:laugh:
dummiexx3 said:
I am a CM i9305T user here. For me, TWRP gives me error codes but then changing to ClockWorkMod recovery (latest version) solved error code 7. I used everything for i9305 for my i9305T phone and I have no problems. Try installing ClockWorkMod and flash CM + GApps.:laugh:
Click to expand...
Click to collapse
I have an I9305T running CM11, I found I had to use the TWRP for the I9305, as the one for the I9305T (which is not yet updated to 2.7) did not allow me to flash CM. CM works fine for me, and I flashed the modem.bin that I extracted out of the latest 4.3 update from Telstra (Aus) which gives me the same LTE network speeds as I was getting on stock.
1. No you will not brick your phone... difference between 9305 and 9305T is in the frequencies that the phone uses to connect to your mobile operator...95% is the same for all..but for a few countries is not...they use different frequencies to connect the phone to the network...so samsung releases a version of the phone with T at the end.
2. A custom recovery is for installing new ROMs on the phone...installing new mods...and stuff...you have access to internal parts of the device... it has a interface with different option....combo to access it: volume up+home+power
I recommend CWM recovery.
Root access is like administrator on windows...by default you can't access system files on your phone and other stuff...for safety reasons...rooting your phone enables access to that stuff...but if you are a newbie better not to root.
2.1 Here is the package: download.chainfire.eu/supersu - but at the moment i'm writing this the site is dowm.
3. Yes...the order of installing CM11 is:
a) Back-up first in case of failure - i don't do this cause it takes a lot of time and i don't have anything important on the phone...i use cloud storage.
b) Install custom recovery and enter custom recovery
c) do a full wipe - factory reset + cache partition + dalvik cache
d) install ROM
e) install GApps.
Every ROM has it's own install instructions...just follow them.
Hi guys,
I'm new to Sony devices and rooting/flashing procedures.
I run CWM recovery 6.0.4.7 and CM11 with the included Kernel 3.4.0-g14fe8eb
As the title says: when I try to flash a cm11 rom, other than the one I'm currently on (2014-03-01), I end up in a bootloop (CM arrow doesn't stop spinning). When I try to restore a backup via recovery, I end up with a missing IMEI and thus a not working mobile radio. My procedure to fix this is: full wipe, flash the current nightly.
To me it doesn't make any sense that the IMEI is missing after a restore (when I created the backup everything was fine). What is the correct procedure to update to the next nightly?
Best regards,
bumbum
Hi guys,
complete noob mistake :angel:
I hit the wrong button in TWRP (v.2.3.3.0) and wiped the system off my i9305, now I want to install AOSB (or any ROM for that matter!)
The AOSB install fails with a Status 7 "set_metadata_recursive: some changes failed"
I've unzipped the ROM and deleted the lines at the start where it checks the device type just in case, but that hasn't fixed it.
I'm getting the same error with two different CM11 builds for the i9305 too.
I read somewhere that its a problem with TWRP, so I downloaded TWRP 2.6.3.1 Flashable, and I've been trying to flash that.
It says the install was successful, then I wipe cache & dalvic, power off, and start to recovery, but it goes into the older 2.3.3.0 recovery.
I can't use Odin because the USB port is broken...I've tried replacing it with a soldering iron without success (Don't have a reflow gun...yet)
Is there any way I can update / fix TWRP by using it to flash a new recovery over itself? Ideally I'd like the newest CWM, as that is apparently needed to flash AOSB but once i get any functional rom on it at all I was planning on installing CWM from the system and flashing AOSB then.
Any help would be greatly appreciated :good:
Bump
Can anyone shed any light on this?
Hello, I have a problem with my phone and I need some help.
I tried to install Kit Kat 4.4.4 using recovery mode (CWM), the install process ran smoothly but it had some issues so I tried to install Lollipop 5.1.1 (CyanogenMod 12.1) 20150412 stable from novafusion using TWRP (v.2.8.1.0) but apparently I made some mistakes, I used the Advanced Wipe tool and deleted (Dalvik cache, System, cache, data, internal storage) after this I can not install any moded ROM.
The phone stays on the "Samsung Galaxy s3 mini" screen.
Can somebody help?
My phone model is GT-i8190L
looks like you need to head over to http://http://www.sammobile.com/firmwares/, login & d/l original firmware for ur fone & region, then flash via odin, & start root,custom flash again.............carefully this time & be sure to make full nandroid backup before flashing so you can restore if problems occur......good luck & post again if you need more help
beerwolf-crowe said:
...
Click to expand...
Click to collapse
Friend but as I do if odin does not recognize my device?
Now install the drivers and still recognize it.