I Installed CM 10.1 on my phone with the zip file placed on the sd card. Before I did this, I updated my root to the current verizon firmware using a zip file and installed it using clockworkmod. I don't want CM 10.1 on my phone anymore, I just want to go back to the touchwiz interface. Please help me! I obviously can't flash the firmware using odin because It was a zip file I downloaded right to my phone. I haven't backed it up using CWM I know that was not smart but what's done is done. Do I just need to delete the zip file of CM 10.1? How do I go about restoring the touchwiz. I already tried to reinstall the zip file that the verizon updated firmware used. It didn't work.
Thanks in advance!
Just find the stock ROM and flash via Odin or download one of the many touchwiz based roms (Axis, Hyperdive, Synergy etc) and install the same way you installed CM
Related
HI , i am using galaxy mini ICS CM9 Beta3, can i use odin instant install back my gingerbread 2.3.6 ? .....my beta3 rom is not working the USB storage,but i test boot my phone to downloading mode and open ODIN,it is connect to my phone. i am confused,someone can help me
if you want to go back to your previous rom, you should have backed it up using clockworkmod.
if you didn't, I suggest you install it (if you have root, you can install the rom manager application to do that for you)
Regarding Odin, you can use it to restore to your previous version, if you have the rom on your computer. As usual, you will loose all your user data.
In Galaxy Mini, to use that program is to have a hard brick, so don't install that. Rom manager is not compatible with our device.
I think if you make a nandroid and flash the rom through CWM after the wipes, you won't have any problem, but it will be better if someone gives more opinions, just in case.
Sent from my GT-S5570 using XDA
boot loop on galaI've been trying to load custom ROxy mini (not lack of /data format)
I actually have ROM Manager on my Mini, though I haven't flashed CWM through it, granted (and I won't after your advice, thanks).
I installed my clockworkmod on my phone , how to back my previous ROM ? How should i do??
To be clear, you CANNOT go back to your existing rom through clockworkmod if you didn't back it up first.
Since you didn't, your only chance now is to flash the original firmware. If you don't have the firmware file on your computer, you're going to have to obtain it somehow. I recommend your mobile operator, and google if that fails.
a tutorial to install a 2.3.6 ROM
http://forum.xda-developers.com/showthread.php?t=1255305
I rooted & installed CWM via the one-click method. It installs Rogue XM Recovery 1.3.0.
http://forum.xda-developers.com/showthread.php?t=1689193
I backed everything up in CWM so that when & if I flashed back everything would be backed up. So I flashed Jelly Bean
[ROM][JB][4.1.1] AOSP build #4 http://forum.xda-developers.com/showthread.php?t=1779133
I played around with & didn't see what the big deal was with Jelly Bean was. Also was irritated that there was no file explore built into the ROM. I really like the one on Asus ICS ROM. Anyway I go back into recovery to install the stock Asus ICS ROM (US_epaduser9_2_1_27UpdateLauncher.zip). It tries but aborts
Finding update package...
Opening update package ...
Installing update...
Installation aborted.
What am i missing or doing wrong?
Well for starters the only reason the stock ICS roms have a file explorer is because its an Asus proprietary app, every custom ICS, or JB rom will require you to download one. Secondly are you trying to re-flash the stock rom or restore your back up? Id recommend you try using TWRP
JoinTheRealms said:
Well for starters the only reason the stock ICS roms have a file explorer is because its an Asus proprietary app, every custom ICS, or JB rom will require you to download one. Secondly are you trying to re-flash the stock rom or restore your back up? Id recommend you try using TWRP
Click to expand...
Click to collapse
Just trying to re-flash the stock ROM.
jadesse said:
Just trying to re-flash the stock ROM.
Click to expand...
Click to collapse
I think i seen this before you are trying to flash an update to a rom not that actual rom......check the file size. I haven't had any issue converting Jb back to ICS. you have to flash a fresh install of the version you backed up then you can flash the back up you made. The mounting from ICS to JB is different and you cannot go backwards without flahsing a clean rom first.
itj1228 said:
I think i seen this before you are trying to flash an update to a rom not that actual rom......check the file size. I haven't had any issue converting Jb back to ICS. you have to flash a fresh install of the version you backed up then you can flash the back up you made. The mounting from ICS to JB is different and you cannot go backwards without flahsing a clean rom first.
Click to expand...
Click to collapse
I downloaded the newest firmware straight from the Asus website. That is what I am trying to flash but it fails to. If I should be doing something else then please tell me.
Did you unzip the download and flash the zip that is inside? For some reason Asus packages a zip within a zip. You need the one on the inside to flash.
Woodrube said:
Did you unzip the download and flash the zip that is inside? For some reason Asus packages a zip within a zip. You need the one on the inside to flash.
Click to expand...
Click to collapse
I feel like such a moron because that was the issue. I found the .24 firmware that I had extracted to a folder with the need zip file in side. I was able to flash t e.24 with out an issue. I knew my issue was something stupid but I could put my finger on it right away.
You might want to go back to the ASUS site and download the newer firmware(.27) and do the same thing(install the zip inside the zip) That's the newest Official ASUS Firmware.
http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+TF101&p=20&s=16
sfot said:
You might want to go back to the ASUS site and download the newer firmware(.27) and do the same thing(install the zip inside the zip) That's the newest Official ASUS Firmware.
http://support.asus.com/Download.aspx?SLanguage=en&m=Eee+Pad+Transformer+TF101&p=20&s=16
Click to expand...
Click to collapse
I already had it.
There's a lot of disparate information on how to do this so wanted to share what worked for me.
Heimdall was way better than Odin in recognizing and flashing ROM's. You need to watch a tutorial on youtube on how to use Heimdall manually in case you can't find a ROM in the right format (compressed as "tar.gz").
I used a rooted Gingerbread 2.3.6 ROM, which was packaged for Odin. Had to decompress the files and set them up manually in Heimdall for flashing.
Once Infuse 4G was running with root I downloaded/installed ROM Manager from Google Play and transfered the Carbon KitKat ROM 4.4.4 (2014-07-06) and GAPPS 4.4.2 (2014-06-06) ".zip" files to the root folder via USB cable from PC (phone connected as USB Mass Storage).
In ROM Manager you can select the ROM you want to install when the phone reboots. At some point I was able to also install GAPPS before finally booting to Carbon KitKat.
kikato said:
There's a lot of disparate information on how to do this so wanted to share what worked for me.
Heimdall was way better than Odin in recognizing and flashing ROM's. You need to watch a tutorial on youtube on how to use Heimdall manually in case you can't find a ROM in the right format (compressed as "tar.gz").
I used a rooted Gingerbread 2.3.6 ROM, which was packaged for Odin. Had to decompress the files and set them up manually in Heimdall for flashing.
Once Infuse 4G was running with root I downloaded/installed ROM Manager from Google Play and transfered the Carbon 4.4.4 KitKat ROM and GAPPS 4.2 ".zip" files to the root folder via USB cable from PC (phone connected as USB Mass Storage).
In ROM Manager you can select the ROM you want to install when the phone reboots. At some point I was able to also install GAPPS before finally booting to Carbon KitKat.
Click to expand...
Click to collapse
so how were you able to flash carbon and the gapps? why did you use 4.2 gapps with a 4.4.4 rom????
Used ROM Manager from Google Play to install latest versions of KitKat (2014-07-06) and GAPPS (2014-06-06) from Carbon website. ROM Manager can also install Clockworkmod Recovery.
Files for download at the website have no version numbers, but the phone showed upgrades for 4 of the Google applications.
kikato said:
Used ROM Manager from Google Play to install latest versions of KitKat (2014-07-06) and GAPPS (2014-06-06) from Carbon website. ROM Manager can also install Clockworkmod Recovery.
Files for download at the website have no version numbers, but the phone showed upgrades for 4 of the Google applications.
Click to expand...
Click to collapse
okay so you used rom manager to install CWM recovery.....and you selected to flash carbon via rom manager which then took you to the recovery then somehow you were able to flash the gapps.........but how was it able to directly flash on GB CWM version did you have to flash carbon rom twice in order to get the updated CWM version then flash carbon again to get the rom then flash the gapps then wipe cache and dalvik cache?
also you made a "root folder" in your sdcard?
PS. did you use heimdall one click or the more complicated version?
I can't say if the Carbon ROM was flashed twice, but it seems the phone rebooted more than once during the whole process (from rooted Gingerbread 2.3.6 to KitKat 4.4.4).
ROM Manager only requires to save ROM .zip file(s) in your phone SD card, read somewhere to use root folder or topmost location in SD card (not a folder named "root"), but you can use Recovery to select the location of the .zip file to install.
ROM Manager boots into Recovery to install .zip files, whether is Carbon ROM or GAPPS.
After the Carbon ROM was installed (and maybe a reboot), before booting into KitKat, I was in CWM Recovery and used the menu to install GAPPS.
Recovery has a "wipe data/factory reset" menu option.
Used Heimdall 1.4.0 to manually flash a rooted Gingerbread 2.3.6 ROM that was packaged for Odin, but there are other ways to root the phone.
It can take a while for KitKat to install so give it some time.
I thought you had to go to ICS before KitKat. Can you really go straight from GB to KK?
Also when I downloaded "Rom Manager" and tried to install CWM it did not list the Infuse as being supported for installing the CWM Recovery saying I had to find and install one manually.
SirAndroid said:
I thought you had to go to ICS before KitKat. Can you really go straight from GB to KK?
Click to expand...
Click to collapse
Apparently can be done as long as you disable lagfix.
SirAndroid said:
Also when I downloaded "Rom Manager" and tried to install CWM it did not list the Infuse as being supported for installing the CWM Recovery saying I had to find and install one manually.
Click to expand...
Click to collapse
CWM for the i9000 is supposed to be a valid substitute. I don't use the AT&T version of the Infuse (mine is Rogers), so it didn't work for me at first - still had to flash with ODIN.
Interestingly, as I remember after flashing with ODIN and rebooting into recovery, it was Blue CWM, not Red (which Red is what you usually get by flashing only the ODIN/Heimdall images).
I didn't have to install any other version before flashing KitKat, only had to root the phone. I rooted by flashing a "rooted" GB 2.3.6 ROM, but there are other ways to root the phone.
When I tried to install CWM Recovery with ROM Manager I got an error so I went ahead and flashed with whatever recovery the phone had.
Is possible the rooted GB 2.3.6 ROM had CWM Recovery already, or ROM Manager was able to install CWM Recovery after all (phone rebooted more than once, I kept trying until it worked ).
Read you must use "Samsung I9300 Galaxy S III" in ROM Manager since they have similar partitions.
ROM Manager no longer has the i9300 Galaxy S III option, but you only need to create a Recovery shortcut in Apex launcher and flash from a Carbon ROM .zip file (KK v4.4.4 nightly for Infuse 4G, dirty flashing with no wipes).
The Carbon ROM includes a Carbon Delta, which doesn't update nightlies (it always says "system is up to date").
Have not seen other KitKat kernels or TWRP touch for the Infuse 4G, currently using CWM Recovery 6.0.5.0.
hey, i am new to android. Just got an old Samsung galaxy sl gt-i9003. it has never been rooted. i tried rooting it using odin and the cf root file by LoLaTiOn for DDMF1 firmware. Did everything correctly and when it came to install zip from sd card, it gave an error after i selected the zip file. the error says- can't open E:/(name_of_the_ROM).zip (bad). I thought the problem might be with the zip file. but i tried a lot of ROMs like CM11 and Nameless but still the same error. please help me. i can't figure out what is the problem. how can i install the ROM properly without any error?.
CF-ROOT file i used by LoLaTiOn: http://forum.xda-developers.com/showpost.php?p=43016372&postcount=30
My phone details:
k_mahajan said:
hey, i am new to android. Just got an old Samsung galaxy sl gt-i9003. it has never been rooted. i tried rooting it using odin and the cf root file by LoLaTiOn for DDMF1 firmware. Did everything correctly and when it came to install zip from sd card, it gave an error after i selected the zip file. the error says- can't open E:/(name_of_the_ROM).zip (bad). I thought the problem might be with the zip file. but i tried a lot of ROMs like CM11 and Nameless but still the same error. please help me. i can't figure out what is the problem. how can i install the ROM properly without any error?.
CF-ROOT file i used by LoLaTiOn: http://forum.xda-developers.com/showpost.php?p=43016372&postcount=30
My phone details:
Click to expand...
Click to collapse
Greetings;
1st: you should do some research (either Google or XDA Forum)....
2nd: Try not to duplicate threads.
Now to your problem:
You must use a specific CF-Root for your ROM and Device. Otherwise it wont work (in most cases).
If you're under a Custom Rom, search for the specific CF-ROOT for that ROM.
Also note that most custom Roms are already Rooted. Did you check this before?
Either ways. I see you're using GingerBread Rom...
If you wish to go "Perfect", Just go for FULL DDLF2 ROM.
Search for the specific CF-ROOT and Deodex +.zip file, and Kernel.
The Deodex zip file will help you remove some bloatware. (Just flash CF-Root 1st Before Flashing Deodex Zip file).
After that you can also flash bagaria Kernel (Also search for the specific file for your device).
Hope this helps.
Please press Thanks Buttons if this helped you, as this will keep me motivated to continue helping people.
I hope this question is not redundant,but I want to know if I should consider my tablet as an 8013 which it was,or as an 8000 with the gnabo rom v6,when I go to certain websites its identified as gt-8000, others see it as gt-8013, I installed initially with cwm recovery and rom was installed only, Cwm would not install KK kernal or su zip or anything else so I uninstalled Cwm and installed Twrp with 8013 zip, I then finished flashing rest of rom package then wifi fix later, all is ok except what I can see of sd card= all files were empty except the downloaded file folder, When I use flashify it doesnt show boot image and when I touch recovery it asks if I want to d/l TWRP when I already have TWRP and working? 1. Should I use twrp for 8013 or8000 2.Should I be concerned about all files being empty? Also when going to KK4.43, are you limited as to access to sd card? Thanks to any and all for any help offered. By the way,I do really like the rom,very nice!!! JW
I'm wondering this myself.
If the leaked firmware is flashed does it permanently change the device? And secondly if I flash from Hyperdrive 4.1.2 to Gnabo V6 is it possible to restore the Hyperdrive rom?
Thanks for any help