hey, I installed a custom ROM with twp. after the installation I figured out that the rom don't work properly(I tried any rom possible but each one had some issues ) so I tried to get back to stock and couldn't do it.
I tried putting an update file into a "dload" folder on my SD and then going to stock recovery (I flashed it manually through adb) and tried to flash it but it failed every time.
does anybody knows what should I do to get back to stock?
You can't flash custom ROMs one over another, usually each one must be flashed only from the appropriate stock ROM(s) - because their ZIP files overwrite various system partitions and in different combinations.
Also, you can't install every stck ROM by DLOAD, and neither from any unknwn state/mess (good luck, after all the phone wasn't bricked).
You should know from which stock ROM you originally started and you want now to go back (no info above?!).
If iit was one of the stock ROMs listed in the following post, you may flash the corresponding HWOTA.zip and do a Factory reset as described:
https://forum.xda-developers.com/showpost.php?p=74913874&postcount=3
Related
With all of the really good roms now a days...that is..
1) Rooting...doing a back up of the stock rom..and then using that backup to return to stock without having to flash through Odin?
I'm guessing here...but..wouldn't you have to have disable any lag fix..going back to rfs..disable any voodoo..changing any oc/uc settings to stock..prior to doing this ?
2) Pulling a copy of the entire EFS folder from stock to your PC before doing any flashing new roms and then prior to un-rooting dropping it back in with root explorer...Won't this do the same thing without having to use a terminal or hex editor to have the original imei # and product code #? If #1 is a complete copy..would #2 be even needed ?
Just looking for a easy way to do this on a brand new phone
Thanks
Mac
Mac11700 said:
With all of the really good roms now a days...that is..
1) Rooting...doing a back up of the stock rom..and then using that backup to return to stock without having to flash through Odin?
I'm guessing here...but..wouldn't you have to have disable any lag fix..going back to rfs..disable any voodoo..changing any oc/uc settings to stock..prior to doing this ?
2) Pulling a copy of the entire EFS folder from stock to your PC before doing any flashing new roms and then prior to un-rooting dropping it back in with root explorer...Won't this do the same thing without having to use a terminal or hex editor to have the original imei # and product code #? If #1 is a complete copy..would #2 be even needed ?
Just looking for a easy way to do this on a brand new phone
Thanks
Mac
Click to expand...
Click to collapse
1) You should basically be doing this everytime you flash a new rom. I've flashed my cappy probly 50 times and everytime except once I went back to stock first. 0 issues -- the 1 time I didn't have a pc at hand and had to disable the lagfix then flash rom. But. going back to stock with Odin3 1 click is easy as long as you can get into download mode. Make sure you can get into dload mode before even attempting to flash a rom.
You only have to disable lagfix if you are not going back to stock prior to flashing a new rom (don't ever flash a rom over another rom without first disabling the lagfix or going back to stock).
2) I never backup my sdcard when flashing rom or master clear (I'm lazy I guess and don't want to wait for the files to transfer). I also keep update.zip as the clockwork recovery update.zip file. So after going back to stock, all I have to do is go into stock recovery and reinstall packages to install clockwork recovery, then I can flash the new rom and any add ons.
mod777 said:
1) You should basically be doing this everytime you flash a new rom. I've flashed my cappy probly 50 times and everytime except once I went back to stock first. 0 issues -- the 1 time I didn't have a pc at hand and had to disable the lagfix then flash rom. But. going back to stock with Odin3 1 click is easy as long as you can get into download mode. Make sure you can get into dload mode before even attempting to flash a rom.
You only have to disable lagfix if you are not going back to stock prior to flashing a new rom (don't ever flash a rom over another rom without first disabling the lagfix or going back to stock).
2) I never backup my sdcard when flashing rom or master clear (I'm lazy I guess and don't want to wait for the files to transfer). I also keep update.zip as the clockwork recovery update.zip file. So after going back to stock, all I have to do is go into stock recovery and reinstall packages to install clockwork recovery, then I can flash the new rom and any add ons.
Click to expand...
Click to collapse
I guess I am wording this wrong...I know how to flash..and I know how to odin back...but I was curious if I could eliminate doing some of that by just using the back up of the stock rom that is rooted..I don't think that can be done with out flashing stock via Odin first (because of the kernels if not using a Captivate kernel )...but if you are using one... I haven't read anything about...cause I really don't know..
I am trying to see if all the EFS files are replaced with the correct #s without having to do and terminal work or use a hex editor..once the back up from Rom manager is put back on and used..Just trying to make a real easy check list about it..
Mac
mod777 said:
(don't ever flash a rom over another rom without first disabling the lagfix or going back to stock).
Click to expand...
Click to collapse
I guess I got lucky cuz one day I was too lazy and away from the PC, but I have a couple of ROMs on my SD so I just flashed Assonance on top of Perception and worked fine.. that is the only time I did that, I always go back to stock with one click ODIN before flashing a new rom
dq13 said:
I guess I got lucky cuz one day I was too lazy and away from the PC, but I have a couple of ROMs on my SD so I just flashed Assonance on top of Perception and worked fine.. that is the only time I did that, I always go back to stock with one click ODIN before flashing a new rom
Click to expand...
Click to collapse
the lagfixes may not have been installed...i think you have to manually install them with the roms you mentioned
Trying to install the Cynogen ICS ROM, and when installing the .zip, it loads the Samsung flash screen with Cynogen, then get the green guy and loads of text for about half a second, then it just reboots. Over and over for about 10 mins. WHat went wrong? What should I do?
It happend the same to me.
I just removed the battery and put it back, entered in CWM and reinstalled the ROM.
Good luck!
I somehow got into a recovery mode, but with the assumption it would all go wrong again, tried to install the .zip Darky rom instead, went through the process and said it worked but then it just went back to the Cynogen loop problem!? I just tried a Restore instead, but I haven't rebooted yet, should I wipe everything again, and try the ICM .zip again?
Yep, just go with the whipe. I hope you did a backup.
OK turns out the Restore failed, so now trying to reinstall ICS .zip again. fingers crossed!
yep backed it up, not that its seems to have helped.
Well now it's stuck in the Galaxy S bootscreen...
that really sucks....did you deactivated the lagfix before running the rom?
If the problem persists you have to run a basic ROM using ODIN.
Yes deactivated the lagfixI can't get into recovery or anything now, except download mode.
Download mode is all you need to run a ROM with Odin.
I recommend Amestris, it is a good ROM, good battery life but the thread in not complete, there are some files missing...for now.
I've put some older ROM on I had, then tried to install ICS again but now when I use Clockwork, and select the file it goes to recovery but I can't select any zip files, just reboot back to this awful old ROM!
I had same issue when I installed ics, what I did that worked was pull battery and go back into cwm, reflashed ics zip and it fully installed that time. Had same experience when flashing cm7 before.
Not getting anywhere with this. I get an option to install zip from sdcard which is where the update is (an where the darky update also is which worked), but there is an option to update from internal SD, which is not where the file is. Is it in the wrong place?
I think you would be best to use Odin 1.3 to flash DarkyROM Ficeto JVT base rom.
are you sure those files are still on your sd card?
The reason you need to pull the battery and reflash the ICS rom a few times is because Samsung ROM (most) have a different partition layout to CM7 based roms (which the ICS port is one).
GL.
Hi guys, having some serious issues with my Tab. It's the Telstra GT-P7320T.
So I had it rooted and flashed with the glitkis kernel all working fine still on the standard Telstra version of honeycomb. Then when their update for ICS finally came out (after nearly 6 months of knocking it back) I went to update it in the normal manner, not thinking it would have a hissy fit with the root and the custom kernel.
So after it downloaded it did its pre install bit, it rebooted, but then loaded into CWM recovery, and thats where its stayed. I've tried factory resets, clearing and formatting all the caches (davlik, system etc) i've used adb to push a few different roms and kernels etc to the device but nothing ive tried has worked. I flashed arlics ics rom, but it still just boots into recovery. Ive tried flashing the stock kernel and stock recovery but when i try to install zip from sd them they fail "install aborted (bad)"
Anyone got any ideas on what process and files I should try? Ive searched up and down the forum trying different methods for fixing soft brick and returning to stock but to no avail.
Cheers
ragvaror said:
Hi guys, having some serious issues with my Tab. It's the Telstra GT-P7320T.
So I had it rooted and flashed with the glitkis kernel all working fine still on the standard Telstra version of honeycomb. Then when their update for ICS finally came out (after nearly 6 months of knocking it back) I went to update it in the normal manner, not thinking it would have a hissy fit with the root and the custom kernel.
So after it downloaded it did its pre install bit, it rebooted, but then loaded into CWM recovery, and thats where its stayed. I've tried factory resets, clearing and formatting all the caches (davlik, system etc) i've used adb to push a few different roms and kernels etc to the device but nothing ive tried has worked. I flashed arlics ics rom, but it still just boots into recovery. Ive tried flashing the stock kernel and stock recovery but when i try to install zip from sd them they fail "install aborted (bad)"
Anyone got any ideas on what process and files I should try? Ive searched up and down the forum trying different methods for fixing soft brick and returning to stock but to no avail.
Cheers
Click to expand...
Click to collapse
hey mate,
i was just caught out by this last night. all you need to do is re-flash on a stock rom with ether oden of heimdall and youre good to go. im sure there is a oden flashable rom on these forums
take it sleazy!
Cheers mate,
Ive been trying to reflash a stock rom by pushing it to the sd card and installing it, but when i go to install it from recovery it tells me the rom file is bad and aborts, like its corrupt or something, so maybe i need to find some different downloads to try. Thanks, there's hope still at least, lol. I'll find the odin file and try doing it that way.
ragvaror said:
Cheers mate,
Ive been trying to reflash a stock rom by pushing it to the sd card and installing it, but when i go to install it from recovery it tells me the rom file is bad and aborts, like its corrupt or something, so maybe i need to find some different downloads to try. Thanks, there's hope still at least, lol. I'll find the odin file and try doing it that way.
Click to expand...
Click to collapse
yeah, i think its becaute the cwm recovery doesnt know what to do with the update.
you need to have the stock recovery installed. dont take my word for it though.
just look up a tutorial for flashing a rom via oden. its really easy, just make sure the image you are flashing is of .tar.md5 extension.
You can get the stock rom at sammobile.com. down load the zip file then extract the .tar.md5 file out of it using 7-zip.
God promised men that he'd put beautiful women in all corners of the world. Then he laughed and laughed and made the world round
FIXED!! - Cheers Everyone!
OK, so I downloaded the stock telstra rom off the forum here, its at the top of page 3 at present, flashed that with Oden, which fixed the soft brick and allowed me to boot again. I then flashed the stock recovery, rebooted, got into the system and downloaded the ICS update again. Once it rebooted, with the stock recovery it was able to install and successfully boot into ICS!! I was more stoked than I've ever been before, let me tell you, lol.
how ?
ragvaror said:
FIXED!! - Cheers Everyone!
OK, so I downloaded the stock telstra rom off the forum here, its at the top of page 3 at present, flashed that with Oden, which fixed the soft brick and allowed me to boot again. I then flashed the stock recovery, rebooted, got into the system and downloaded the ICS update again. Once it rebooted, with the stock recovery it was able to install and successfully boot into ICS!! I was more stoked than I've ever been before, let me tell you, lol.
Click to expand...
Click to collapse
i currently have the same problem as you did, how did you flash with odin if you're stuck in recovery mode ?
please help, I'm racking my brain trying to figure this out.
after trying CM on my desire C and being unhappy with the battery performance, i wanted to return to a sense rom. i did a full wipe (factory reset/cache/dalvik) , flashed the rom for revolution sense 5, and pushed the boot.img files to the phone with fastboot. i know the phone might take awhile on first boot, but i thought after 10 minutes something was wrong.
now every rom fails to boot, even if i use the stock rom and kernel, it stick at the white htc logo screen. i've tried several roms, and moved to cwm 6.0.3. the only thing i haven't tried is going back to stock recovery. i'd like to avoid that.
any suggestions?
joe
edit: i did manage to successfully reinstall CM10. not sure why none of the sense based roms will work. i assume the stock rom is also sense based.??
It's because if you install CM mod, you also installed file named boot.img which is kernel file. Unfortunately Stock rom doesn't work with modified Kernel (and I tell it from my experience), so if you want to go back to stock ROM you need to download stock Kernel file too.
So here are some tips to revert back to stock:
1) Boot in Fastboot
2) Install stock boot.img via Desire_C_All-In-One_Kit_v2.0
3) Boot into Recovery
4) Wipe all data
5) Wipe cache
6) Install stock rom
Your phone should be back with stock ROM and Kernel
I recently started flashing custom roms. The most common trouble that comes is how to get back to stock rom. Anyone please give a detailed procedure how to get back to stock rom from flashing stock recovery to flashing stock rom...
Thank you
arindam28 said:
I recently started flashing custom roms. The most common trouble that comes is how to get back to stock rom. Anyone please give a detailed procedure how to get back to stock rom from flashing stock recovery to flashing stock rom...
Thank you
Click to expand...
Click to collapse
1.Download the stock rom from letv forum
2.If you r on Codeworkx TWRP, install Chinese TWRP by ycjeson
3.Then install the stock zip file (19s). First time you may get error, flash again the same file.
4.It asks whether to install stock rom, give yes.
5.Now your phone will be with stock rom and recovery. with bootloader locked.
If this helped ..hit thanks
Stock Recovery given by rishab rao :
https://drive.google.com/file/d/0B8T-FsY2G8InSW9lNzZiNGlOem8/view?usp=sharing
Stock Rom :
https://devs-lab.com/download-letv-official-stock-rom.html#Le_2_Qualcomm_Stock_ROM
rename the downloaded stock rom to update.zip and then place it in the root directory of internal storage
flash stock recovery and click the update option
you'll get an error but try again
That's it!
Better take a twrp back up soon after you flash the stock rom just in case.