I was running the new Jellybean ROM just fine but decided to revert back to the AOKP ICS ROM. I did a backup of my JB rom in CWM and then did a restore of the backup from the AOKP ROM. But I forget to do a factory wipe. The ROM booted up fine the first time and then after a reboot it was just endlessly running the boot animation.
I could only boot into download mode so I tried to use PC Odin to flash a ROM I had but the program gets stuck at factoryfs.img. Please can anyone offer assitance?!
If you're to that point, flash back to stock first before you do anything else using creepyncrawlys guide in the dev section.
BROKKANIC said:
If you're to that point, flash back to stock first before you do anything else using creepyncrawlys guide in the dev section.
Click to expand...
Click to collapse
Sadly... I have tried this and it still gets stuck.
Using the downloads here: http://forum.xda-developers.com/showpost.php?p=18859438&postcount=199
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Have you tried this:?
http://forum.xda-developers.com/showthread.php?t=1286432
benjamingdelacruz said:
Have you tried this:?
http://forum.xda-developers.com/showthread.php?t=1286432
Click to expand...
Click to collapse
I have. This is what I did first. It gets to about 30% and gets stuck.
AngelsNecropolis said:
I was running the new Jellybean ROM just fine but decided to revert back to the AOKP ICS ROM. I did a backup of my JB rom in CWM and then did a restore of the backup from the AOKP ROM. But I forget to do a factory wipe. The ROM booted up fine the first time and then after a reboot it was just endlessly running the boot animation.
I could only boot into download mode so I tried to use PC Odin to flash a ROM I had but the program gets stuck at factoryfs.img. Please can anyone offer assitance?!
Click to expand...
Click to collapse
You don't have to do a wipe when restoring a nandroid backup on our phones, since it overwrites the entire data partition anyway. I'm wondering if ClockworkMod versions could be at the root of this. You didn't say which JB you were using, and I am not up on AOKP, but did the JB rom have CWM 6.0.1.1? and AOKP have the 5.x version? I think these are supposed to be backward compatible, but I'm wondering if restoring a 5.x backup with the 6.0.1.1 version could be at fault here. Just clutching at straws for a reason.
As far as recovering, go to the Download Repository, and first try flashing the complete firmware package with bootloaders. If that doesn't work, then try flashing the critical parts individually, i.e. secondary bootloader and param.lfs. If that doesn't work, there is a pit file there also, so you can flash the stock package with repartition. I assume you understand the risks.
I was using the SuperNexus JB rom. They did have different cwm versions but not sure which they were. Luckily I found an md5 file that would load 100% using pc Odin. Any tar file I tried to use first wouldn't load. Then I was successfully able to use the gingerbread stock with root tar listed in the unbrick section and then install a kernel with cwm to do the restore again. So I'm back to the AOKP. Only took 5 hours to fix this time. Ugh.
Sent from my SGH-I777 using Tapatalk 2
AngelsNecropolis said:
I was using the SuperNexus JB rom. They did have different cwm versions but not sure which they were. Luckily I found an md5 file that would load 100% using pc Odin. Any tar file I tried to use first wouldn't Loa. Then I was successfully able to use the gingerbread stock with root tar listed in the unbrick section and then install a kernel with cwm to do the restore again. So I'm back to the AOKP. Only took 5 hours to fix this time. Ugh.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Mind posting that file? It might come in handy.
The file is 618mb. I'll try to find the site where I downloaded it from.
Sent from my Galaxy S II running AOKP Jellybean
AngelsNecropolis said:
The file is 618mb. I'll try to find the site where I downloaded it from.
Sent from my Galaxy S II running AOKP Jellybean
Click to expand...
Click to collapse
I found the file on this site: http://www.droidreader.com/2012/05/how-to-un-brick-or-fix-soft-bricked.html
It's the Recovery Package for ICS that I used: http://hotfile.com/dl/146748985/809318f/I9100XXLPH.zip.html
The zip contains an md5 file which PC Odin was successfully able to load entirely. I suppose the md5 fixed something that was screwed up which prevented the tar files from completely loading.
Then I was able to successfully flash the kernel + rooted UCKH7 system package found here. Next I flashed a gingerbread Siyah kernal found here in order to gain access to CWM and restore my previous backup.
AngelsNecropolis said:
I found the file on this site: http://www.droidreader.com/2012/05/how-to-un-brick-or-fix-soft-bricked.html
It's the Recovery Package for ICS that I used: http://hotfile.com/dl/146748985/809318f/I9100XXLPH.zip.html
The zip contains an md5 file which PC Odin was successfully able to load entirely.
Click to expand...
Click to collapse
thats all i9100 stuff. Please dont confuse the masses posting that crap here.
MotoMudder77 said:
thats all i9100 stuff. Please dont confuse the masses posting that crap here.
Click to expand...
Click to collapse
Well that crap helped unsoft brick my phone. I only had to use the md5 file in order to get the correct TAR files to work.
AngelsNecropolis said:
I found the file on this site: http://www.droidreader.com/2012/05/how-to-un-brick-or-fix-soft-bricked.html
It's the Recovery Package for ICS that I used: http://hotfile.com/dl/146748985/809318f/I9100XXLPH.zip.html
The zip contains an md5 file which PC Odin was successfully able to load entirely. I suppose the md5 fixed something that was screwed up which prevented the tar files from completely loading.
Click to expand...
Click to collapse
Which .tar.md5 file did you use? And which proceedures in the tutorial did you follow?
Then I was able to successfully flash the kernel + rooted UCKH7 system package found here. Next I flashed a gingerbread Siyah kernal found here in order to gain access to CWM and restore my previous backup.
Click to expand...
Click to collapse
I'm surprised you were able to enter download mode to complete this step, since the I9100 package you used previously contained bootloaders. The secondary bootloader for the I9100 would change the button configuration for entering download mode and recovery mode.
creepyncrawly said:
Which .tar.md5 file did you use? And which proceedures in the tutorial did you follow?
I'm surprised you were able to enter download mode to complete this step, since the I9100 package you used previously contained bootloaders. The secondary bootloader for the I9100 would change the button configuration for entering download mode and recovery mode.
Click to expand...
Click to collapse
I tried using files:
I777UCKH7 OCD With Root.exe
UCKH7_stock_root.tar
uckk6_stock_rooted.tar
ATTGalaxyS2Unroot_SGH-i777.tar
I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5
None of the tar files would complete. The md5 was located in the zip that I downloaded from the previously mentioned site. The file did load a ROM whose hard button configuration didn't match my phone model. Only the menu and home buttons worked and home was actually back. But I didn't have to do anything in the ROM. Download mode was still VOL Down + Power button.
After loading the md5 file I was able to use the exe but when the ROM loaded I wasn't able to get past the setup wizard. I would click on the android in the middle and either it wouldn't respond or different processes kept force closing. I remember one was a google framework process and there were like 2 others that popped up.
Everytime one of the other files failed I had to redo the md5 because the tars would get stuck again. So after several attempts I finally was able to use the UCKH7_stock_root.tar file to move forward with restoring my soft bricked phone.
Maybe someone can list the md5 file of the UCKH7_stock_root.tar incase PC Odin gets stuck like this for someone else? Though I'm no expert so I can't be sure if the tar vs md5 was what fixed the issue. I just know that file helped even if it wasn't the right one for my phone and, to my knowledge, caused no other issues once I used the correct tar files. I'm happily running the new AOKP JB ROM with no issues thus far.
Related
A lot of people have been asking for it. Here it is: All the samsung galaxy player/s wifi 4.0 full recovery if your player is bricked. It includes Stock (and rooted) roms and kernels WITH bootloaders (Intl Only). These can be useful if for exemple you are from a rom which use a different partition (eg Klin's Klassic R5 or CM9/CM10.) Instructions will be in the 2ND POST!!!
Definition: (screenshots are here if you don't know the differences)
INTL = THEY HAVE A HARDWARE (PHYSICAL) HOME BUTTON (except for korea because they have an antenna)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
US = THEY HAVE A CAPACITIVE HOME BUTTON
THESE FILES CONTAINS BOOTLOADERS AND CAN BE HARMFUL FOR YOUR DEVICE. IF YOU DON'T KNOW WHAT YOU ARE DOING ASK FOR HELP OR DON'T CONTINUE.
G1ZKC5
Full Recovery for YP-G1CW 2.2.1 (INTL) Hong Kong (It includes English UK and US, Chinese, Korean.) It should work with all the INTL version.
Link: G1ZKC5 Download
Heimdall Firmware Package Download
G1XXKPQ
Full Recovery for YP-G1CW 2.3.6 (INTL) France (It includes English UK and US. However if you want another locale for your language for exemple French CA, download morelocale 2 from market.) It should work with every INTL version
(This rom is rooted)
Link: G1XXKPQ Download
Heimdall Firmware Package Download
G1UEKI8
Full Recovery for YP-G1CWY/XAA 2.3.5 (US) United States (I don't think I need to say the languages) It should work with every US versions of the 4.0.(TRY THIS AT YOUR OWN RISK. NOTE THAT PEOPLE WITH HARD BRICK DEVICES CAN'T POSSIBILY RECOVER FROM THIS.)
Link: G1UEKI8 Restore Pack Download
Heimdall Firmware Package Download
Odin Flashable Download
Misc
Blank Efs Image needed for EFS Re-partition:
Efs Image Download
Dummy Efs for those who have lost it
Dummy Efs Download
Pit Files
Here's the .pit files They are needed for the re-partition (If you have some texts appearing, right-click the link to download):
Intl Pit: Intl Pit Download
US Pit: US Pit Download
Korean Pit: Korean Pit Download
Instructions (how to flash)
Before asking questions and sending multiples PM on how to flash READ THIS CLOSELY
Download mode:
If you want to enter download mode (which is needed for odin) youtube is your friend
1. You will need to flash with ODIN (If your using Heimdall you know what you have to do, if not follow the ODIN instructions.)
Odin Download: Odin v1.85 Download
1.1: If you need the .pit file download it from here (download the .pit according to your device)
http://forum.xda-developers.com/showthread.php?t=1389873
1.2: If your device is bricked but you can still access to download mode go to 1.3 if not, download the AdamOutler's Resurrector with the instructions: http://forum.xda-developers.com/showthread.php?t=1369799
Flashing Time
1.3: If your device is bricked and you can go to download mode:
1.3.1: Download one of the roms (according to your device)
1.3.2: Open odin, take the .pit file and put the rom .tar.md5 in the PDA SECTION
1.3.3: Before flashing, ensure re-partition is checked.
1.3.4: Flash, when the flash is finished your device should reboot.
1.3.5: When you device reboots, you will be in recovery with red errors which are saying mostly of the time: Can't mount... To erase these errors, WIPE DATA.
1.3.6 Reboot and enjoy your restored device!
Instructions for US Only (Does work with Intl too.)
Note: the odin flashable tar is here so you can use the odin method too.
1. Download heimdall from here: http://www.glassechidna.com.au/products/heimdall/
2. If you have Linux you can go to step 5. If you have windows follow step 3-4
3. This is a first time installation only. Extract heimdall, go to your drivers folders and run zadig.exe Install anything samsung related. (do this when in home menu and in download mode. If you're not in home menu install them while in download mode.)
4. If you recieve errors concerning the drivers install them anyway. (THIS IS NORMAL.)
5. Open heimdall-frontend.exe or in terminal heimdall-frontend.
6. Go at the flash tab and chose the .pit according to your device.
7.1. After add the following partitions in the following order (with their files forget boot.bin and sbl.bin Thanks to klin1344 for this remark.):
PARAM: param.lfs
CACHE: cache.rfs
DBDATA: dbdata.rfs
FACTORYFS: factoryfs.rfs
KERNEL: zImage
7.2. In the case of Intl devices it would be:
IBL+PBL: boot.bin
SBL: sbl.bin
PARAM: param.lfs
CACHE: cache.rfs
DBDATA: dbdata.rfs
FACTORYFS: factoryfs.rfs
KERNEL: zImage.
8. When that is done double-check (just to be sure you're not obligated) ensure that re-partition is CHECKED!
9. Flash!
10. You should errors concerning can't mount cache (or something like that) Just wipe data is necessary.
11. You should have a like new device.
Instructions for Heimdall Package
If you're using an heimdall flashing package, all you need to do is to choose your .tar.gz file and check re-partition in the flash section, and flash.
Special instructions for people coming from MTD based roms
I've seen people complaining about their efs not mounting in stock recovery after flashing CM9/CM10 so it can issue some problems like don't have a lockscreen or device turns off directly instead of getting a prompt. To resolve this ensure that you have your efs backup made when you flashed CM9 based on Nebula (Nebula and LinICS). (It is MANDATORY. EFS contains unique information about your device and if you deleted or you lost it I CAN'T HELP YOU.) This is how I managed to recover my efs back ( I did have like 3 backups of my efs so It wasn't a problem.)
1. Use my recovery method.
2. In heimdall in the efs section take the blank_efs.img file that I will include in first page. I will insert it in the restore. (For intl users You must use heimdall for this. To do so, remove the .md5 extension and extract the .tar from your recovery package)
3. Re-partition and flash.
4. Wipe data.
5. After wiping data go to download mode, then flash a kernel with CWM (I used terra silent)
6. Ensure that you have a file named efs.tar in /sdcard (if you don't have it, well i'm sorry for you )
7. Be sure to have an adb shell ready and execute these commands.
Code:
cd /efs
tar -x -f /sdcard/efs.tar
7. Reboot and your device has EFS restored and the bugs should be fixed.
Note: You can use EFS Professional from lyriquidperfection to restore your efs.tar: http://forum.xda-developers.com/showthread.php?t=1308546 (Thanks to markymark567 for the heads up.)
Note 2: If you had backup your efs as efs.rfs before, just flash it using odin or heimdall.
Alternative way of restoring efs.tar
You can use a file manager to restore it (credits to goldflame09 for this)
MAKE SURE YOU ARE ON GINGERBREAD AND RUNNING CWM AND NOT THE STOCK KERNEL WHEN DOING THIS!!!
1. Extract the files inside the efs backup into a folder on your sdcard SEPERATE from anything else.
2. Move all of these files into your /efs folder.
3. Reboot into CWM.
4. Choose factory reset/data wipe.
5. Format system.
6. Under mounts and storage.
7. Reboot into download mode.
8. Flash the STOCK factoryfs.rfs onto your device.
9. Reboot and all should be fixed.
Click to expand...
Click to collapse
Dummy EFS
I decided to make a dummy efs to all those that have lost their efs and don't have their backups anymore. You can find it in the misc section in the downloads at the first post.
There's 3 files to modify: serial.info, buyer_code.dat and /imei/bt.txt. It's specified in each file that you need to modify them according to your values but I'm saying it here so EVERYONE CAN SEE IT. When you've modified them according to your values, you can save them and copying your tar into the device. (It's recommended to use notepad++ if you're with windows). It should work with Intl and US devices.
Thanks to:
Samfirmware for the G1ZKC5
Choucas06 for the G1XXKPQ
Kwipper for his initial rom dump (G1UEKI8)
Klin1344 for making G1UEKI8
AdamOutler for making the Unbrickable Resurrector.
SGP4isokay for his tests.
Tdmcode for his blank efs image to re-partition EFS.
Saleenman95 for the hosting.
Goldflame09 for the US Heimdall restore package, Odin flashable tar and his dummy efs package.
If you have questions you can PM me (don't abuse) or you can ask your questions in the thread.
Also if you want to thank me, use the thanks button!
i have a problem. just flashed this and now my touchscreen doesnt work at all. gonna pull the battery. let you know what happense
---------- Post added at 09:08 PM ---------- Previous post was at 09:06 PM ----------
minimeofctown said:
i have a problem. just flashed this and now my touchscreen doesnt work at all. gonna pull the battery. let you know what happense
Click to expand...
Click to collapse
after battery pull touchscreen still doesnt work. it boots up fine. im just stuck at the screen where you pick a language. bottom three buttons dont work either
minimeofctown said:
i have a problem. just flashed this and now my touchscreen doesnt work at all. gonna pull the battery. let you know what happense
---------- Post added at 09:08 PM ---------- Previous post was at 09:06 PM ----------
after battery pull touchscreen still doesnt work. it boots up fine. im just stuck at the screen where you pick a language. bottom three buttons dont work either
Click to expand...
Click to collapse
Did you try to flash without re-partition?
zaclimon said:
Did you try to flash without re-partition?
Click to expand...
Click to collapse
flashed without repartion at first and it gave me a fail. so i flashed with repartition after
minimeofctown said:
flashed without repartion at first and it gave me a fail. so i flashed with repartition after
Click to expand...
Click to collapse
In this case I would need some files from a US galaxy player. The files I used were from the INTL one (Except the factoryfs.rfs and zImage. I tought this would work)
I will remake The US Rom.
zaclimon said:
In this case I would need some files from a US galaxy player. The files I used were from the INTL one (Except the factoryfs.rfs and zImage. I tought this would work)
I will remake The US Rom.
Click to expand...
Click to collapse
I'll pull the files directly from my device and make the rom again. Link will be available soon..
Edit: btw zaclimon, its G1UEKI8, you might want to change that in your post
Edit2: Link available here: -not available-
I took all the files needed for the recovery ROM directly from my player, so it *should* work, though I haven't tested it yet.
I can't get into download mode. Adb won connect either. I tried unbrickable but that didnt seem to work. Do I need a full Linux system? I have Ubuntu dual booted on my laptop
No, a Ubuntu dualboot should work.
The problem on your side, that you can't use any physical button.
So we need something like an app to boot into Download Mode.
I was looking for some fixes, but the problem: Your Keys don't work.
So i'm hoping, that it can be changed within Android. As of now i haven't found anything.
Maybe a USB jig?
Sent using Tapatalk
Hmm... Do you have a tutorial?
klin1344 said:
Maybe a USB jig?
Sent using Tapatalk
Click to expand...
Click to collapse
id like to try it. just that i dont know how to. and i dont have a solder. and it seems risky
Yes, but what is more risky: Having a unusable system or having a chance to change this ?
You could buy one from ebay for cheap.
Sent using Tapatalk
klin1344 said:
You could buy one from ebay for cheap.
Sent using Tapatalk
Click to expand...
Click to collapse
Link?
Sent from my MB855 using XDA
minimeofctown said:
Link?
Sent from my MB855 using XDA
Click to expand...
Click to collapse
Here: http://www.ebay.com/sch/i.html?_fro....l1313&_nkw=usb+jig&_sacat=See-All-Categories
This one is made and sold from the US and not International sellers, (I'm assuming you live in the US) so you should receive it quicker if you buy this one: http://www.ebay.com/itm/Micro-USB-J...ccessories&hash=item3370fe16a4#ht_1155wt_1139
Here is a video if you want to make your own: http://www.youtube.com/watch?v=lojU5bvGz3c
klin1344 said:
Here: http://www.ebay.com/sch/i.html?_fro....l1313&_nkw=usb+jig&_sacat=See-All-Categories
This one is made and sold from the US and not International sellers, (I'm assuming you live in the US) so you should receive it quicker if you buy this one: http://www.ebay.com/itm/Micro-USB-J...ccessories&hash=item3370fe16a4#ht_1155wt_1139
Here is a video if you want to make your own: http://www.youtube.com/watch?v=lojU5bvGz3c
Click to expand...
Click to collapse
Do you have 1 that can ship in canada?
This one has free International shipping, so you can just choose Canada when you checkout. But they ship from Hong Kong and has to go through customs so it could take a while...
klin1344 said:
This one has free International shipping, so you can just choose Canada when you checkout. But they ship from Honk Kong and has to go through customs so it could take a while...
Click to expand...
Click to collapse
Just bought it, the shipping time isn't a problem. Thanks!
Isn't this the wrong person buying it?
Gesendet von meinem YP-G1 mit Tapatalk
These are my phone specs
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am running Stock ROM with root and CWM recovery and Kernel of ICS 4.0.3. I want to flash a different kernel(just the kernel), but backup my old(official one) in case I need to flash it back.
So, how do I backup my original kernel, in a easily re-flashable format and how do I recognize unsupported/supported kernels for my stock rom?
Also, is it true it's much harder to flash kernels(perhaps the original) on a stock rom, than a modded one?
You can try flashing Siyah Kernel either the CWM or Odin ones.
You don't have to backup your stock kernel as it can be easily download in XDA
example from Intratech Thread...
Siyah Kernel:
http://www.gokhanmoral.com/
Stock kernel from Intratech:
http://forum.xda-developers.com/showthread.php?t=1075278
Good Luck & Happy Flashing.
Right, I downloaded the official kernel, just to have it backed up, but it's in a zImage format, not in a zip. How would I go about flashing it back via CWM recovery?
dikidera said:
Right, I downloaded the official kernel, just to have it backed up, but it's in a zImage format, not in a zip. How would I go about flashing it back via CWM recovery?
Click to expand...
Click to collapse
For zipped tar format try here:
http://forum.xda-developers.com/showthread.php?t=1640812
---------- Post added at 10:05 PM ---------- Previous post was at 09:53 PM ----------
dikidera said:
How would I go about flashing it back via CWM recovery?
Click to expand...
Click to collapse
From CWM Manager, select Flash Kernel, and select the zImage you previously put on your SD-card. The kernel will flash and the device will reboot.
I dont have any Flash kernel option in cwm recovery. And the link to the tar is for Odin, not for CWM
dikidera said:
I dont have any Flash kernel option in cwm recovery. And the link to the tar is for Odin, not for CWM
Click to expand...
Click to collapse
Not CWM recovery. He said to use the CWM Manager app in your app drawer. It should be there if you flashed a CF-root kernel.
I have not flashed any kernel yet since i cant be sure if I can flash the original back. Does siyah provide this cf-root?
dikidera said:
I have not flashed any kernel yet since i cant be sure if I can flash the original back. Does siyah provide this cf-root?
Click to expand...
Click to collapse
Siyah and CF-Root are two different kernels.
Both have forms of CWM Recovery packaged with them, but they will be slightly different.
I think you need to read some more.
Hi,
you said you rooted your phone ???
I am running Stock ROM with root and CWM recovery and Kernel of ICS 4.0.3.
Click to expand...
Click to collapse
i dont think you can backup the stock kernel just go there:
http://forum.xda-developers.com/showthread.php?t=1640812
are all zip - so u can flash via CWM
Kernel != ROM.
I might be rooted but I did it straight from the phone.
I just want to flash a different kernel just for the fun but with the ability to flash the original back, get it?
The link that was given to me has kernels in tar format or whole roms
if you got stock your NOT rooted..
link works fine for me with *.zip files which can be easily flashed in cwm recover (vol up + power + home)
roms come WITH a kernel
just click the link above - dll your xwlp7 stock kernel and try CF Root (for beginners)
get it?
But I don't want the rom, just the kernel. And just as an fyi, I used the root method which doesn't require flash with Odin. Yes I have the Superuser app.
My 3g is so slow that by the time i download any rom it will be 2022. Kernel is smaller thus dlfaster download(sort of)
Um ok which method is this? (this one? http://forum.xda-developers.com/showthread.php?t=1679778 ? i9100G?) i think i already read this but didnt try - i used to flash via odin at the beginning now i go for CWM Recovery to flash ;-) i only root per Kernel..
Link posted before still work fine - those are also (or only) Kernels
so i still dont get your Problem
Just go for any (supported) Kernel and flash - if you+re not happy go back and flash stock kernel (dll before..)
Cwm recovery requires zip files whig have boot.img inside them just like the siyah kernel, but the original kernel is just a zImage file produced when the Linux kernel is compiled and I don't think its fit for flashing
CWM Recovery is like Download Mod - you can get there via "the 3 Buttons."
I think you talking bout CWM - the Touch Version of it?
You need the zip file Kernel - could you give me the link to your stock kernel which is in (you say) zImage?
This is the one I downloaded http://skywanker.net/download/download.aspx?link=GT-9100/Kernels/Kernel_I9100XWLP7.7z
I'm sitting in the same boat and sorry to Jack your Thread, But do you know when you flash a Kernel, does it need to be rooted before hand or not? "Auto-Root" is on the Specifications so a little confused :fingers-crossed:
dikidera said:
These are my phone specs
I am running Stock ROM with root and CWM recovery and Kernel of ICS 4.0.3. I want to flash a different kernel(just the kernel), but backup my old(official one) in case I need to flash it back.
So, how do I backup my original kernel, in a easily re-flashable format and how do I recognize unsupported/supported kernels for my stock rom?
Also, is it true it's much harder to flash kernels(perhaps the original) on a stock rom, than a modded one?
Click to expand...
Click to collapse
According to this, you still have your stock kernel, right?
So it also sounds like you just want to dump your current kernel as a backup. In that case, just download HC-kTool from the Play Store. It will allow you to dump your current kernel. It also allows you to backup your EFS, which is useful.
---------- Post added at 03:55 PM ---------- Previous post was at 03:54 PM ----------
Jordan2012 said:
I'm sitting in the same boat and sorry to Jack your Thread, But do you know when you flash a Kernel, does it need to be rooted before hand or not? "Auto-Root" is on the Specifications so a little confused :fingers-crossed:
Click to expand...
Click to collapse
No, you do not need to be rooted before flashing a kernel, and in fact, some kernels, when you flash them, will root your phone for you.
That's good to hear, Also my is Phone is under Contract With Three (3) will everything be alright for example minutes I don't wanna end up unable to use my SIM? :')
Jordan2012 said:
That's good to hear, Also my is Phone is under Contract With Three (3) will everything be alright for example minutes I don't wanna end up unable to use my SIM? :')
Click to expand...
Click to collapse
Just be sure you use firmwares/kernels meant for your device.
For example, if you have an i9100, do NOT use a firmware or kernel for an i9100G, or any other device.
Hello Gentlemen,
Last time I managed to root my device Samsun galaxy S III (GT-I9300) via CF-Root 6.4 and it was successfully rooted,
This was the last time it has been rooted, afterwards, I upgraded and flashed a Jelly Bean 4.1.1 via Odin and found out that Root has GONE !!!
That's okay, but the most amazing problem is, the device does never get rooted no matter how many times I try to root it via the same method mentioned above (CF-Root 6.4),
I though afterwards that this is because CF-Root needs to be updated or something, so I reverted back to ICS 4.0.4 by flashing a stock md5 ROM over.
I tried the CF-Root 6.4 and found out it does not work anymore, please help me gentlemen as I spent the last night trial & error, never succeeded.
I am doing all of this just because I want to flash the HD 14 Android Revolution ROM made by Mike here:
http://forum.xda-developers.com/showthread.php?t=1797334
I hope there was an md5 or tar file (Odin flashable) so that it could be much easier to flash for people who are stuck with this situation.
can you post the exact file name you are trying to use to root
slaphead20 said:
can you post the exact file name you are trying to use to root
Click to expand...
Click to collapse
It is Chainfire CF-Root 6.4 (Latest one)
you many find it here
http://forum.xda-developers.com/showthread.php?t=1695238
Thank you
cfroot is Odin flashable... extract the .tar from the zip you downloaded.
Sent from my GT-I9300 using Tapatalk 2
beaver2233 said:
cfroot is Odin flashable... extract the .tar from the zip you downloaded.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I did extract it and end up with tar file, I flashed it, I know the procedure very well, the point is, the device is not welling to get rooted what so ever.
Engineering Support said:
I did extract it and end up with tar file, I flashed it, I know the procedure very well, the point is, the device is not welling to get rooted what so ever.
Click to expand...
Click to collapse
Can you see the su app? If not try installing it
similar problem
Hi, Im having a similar problem, I was rooted, upgraded to 4.1.1 through kies and it was rooted no more. I rooted it again and no problem. I tried a custom rom and it had an issue with wifi so I went back to stock. Now Ive loaded the stock back on and after wiping/factory reset and clear cache it still says Im running a custom binary, system status is custom also, so trying to root it again so I can reset the flash counter and load my backup but it keeps getting stuck on set up connection on odin and eventually fails.
Ive been at this all afternooon with out much luck, can anyone provide me with some guidance on this?
Hi
I have the same problem
slaphead20 said:
Can you see the su app? If not try installing it
Click to expand...
Click to collapse
I can't see anything like SU or CWM or anything else, besides, I use root checker and it tells me that I am not rooted yet.
Any idea why this is happening?
Also I noticed that upgrading to Jelly Bean changes the SDCard name to Sdcard0
After flashing CF-Root with Odin, your phone should restart in custom recovery to install SuperSU and CWM app
If it's not, try that:
-Flash CF-Root with "auto-reboot" disabled in Odin
-once flash is done, unplug your phone from the computer
-restart in recovery with VolUp+Power+Home
It should trigger the apps installation process
Mopral said:
After flashing CF-Root with Odin, your phone should restart in custom recovery to install SuperSU and CWM app
If it's not, try that:
-Flash CF-Root with "auto-reboot" disabled in Odin
-once flash is done, unplug your phone from the computer
-restart in recovery with VolUp+Power+Home
It should trigger the apps installation process
Click to expand...
Click to collapse
I am happy to read this different answer. I will try your recommendations today,
and if it does succeed, I'm gonna fly to the moon
:good:
have you tried flashing a custom kernel which autoroots?
Sent from my GT-I9300 using Tapatalk 2
Must be having a brain dead day today! Totally forgot about the rebooting recovery to trigger installation....my bad! That will fix it
Finally
Mopral said:
After flashing CF-Root with Odin, your phone should restart in custom recovery to install SuperSU and CWM app
If it's not, try that:
-Flash CF-Root with "auto-reboot" disabled in Odin
-once flash is done, unplug your phone from the computer
-restart in recovery with VolUp+Power+Home
It should trigger the apps installation process
Click to expand...
Click to collapse
I finally got it to flash the .tar file in odin, in odin I unpluged the phone after hitting start ( it was just in SetUpConnection doing nothing ) and when I plugged in straight away it started doing its thing. However it didnt go through and load the SU etc. So I did it over again using the above method and it worked:good:. So thanks to you Mopral!!:laugh:
Engineering Support said:
I am happy to read this different answer. I will try your recommendations today,
and if it does succeed, I'm gonna fly to the moon
:good:
Click to expand...
Click to collapse
You Shiny Star,
You did it, you saved my days and nights
many thanks man
many thanks
Mopral said:
After flashing CF-Root with Odin, your phone should restart in custom recovery to install SuperSU and CWM app
If it's not, try that:
-Flash CF-Root with "auto-reboot" disabled in Odin
-once flash is done, unplug your phone from the computer
-restart in recovery with VolUp+Power+Home
It should trigger the apps installation process
Click to expand...
Click to collapse
You Shiny Star,
You did it, you saved my days and nights
many thanks man
many thanks
By following the above simple steps, I got what I want and resolved this puzzle which really pissed me off for 3 nights already,
Many thanks XDA
Does not work for me
My stats
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No-Wipe Factory Image for Verizon Galaxy S4
(Restore from any soft-brick without wiping data)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Description: This is a guide (based similar to my previous guide for the Verizon Galaxy S III) that will help you flash a 99.9% stock factory image for the Verizon Galaxy S4 overwriting every partition on the device back to stock. The ONLY major change I have made is for your convenience I have modified the factory image to keep all your data/apps/settings and internal storage partition intact. This method should help you restore from any soft-brick that you may encounter without having to wipe your data.
Minor Warning: Please note that if you had any special mods that you had to manually flash before or move on the system partition (like Google Wallet, AOSP 4.2 apps like camera and gallery, etc...) they will be lost as you are overwriting your system partition to factory stock. Please make sure to do the needful with your mods before following this guide (for example resetting the Google Wallet app).
Step 1 - Preparation
Download and Install Samsung Official USB Drivers - Link
Download and extract ODIN v3.07 - Link
Download and extract the correct Factory Image below (modified with No-Wipe):
For VRUAMDK Build (Look for this) - Link
For VRUAME7 Build (Look for this) - Link
For VRUDMI1 Build (Look for this) - Link
Click to expand...
Click to collapse
Step 2 - Flashing Factory Image
Boot phone into ODIN mode (See here for how-to)
Flash the Factory Image using ODIN v3.07 ***in PDA section only*** (See here for guide on flashing)
You should now be able to boot back to Android and all your data should be intact exactly as it was
Click to expand...
Click to collapse
Step 3 - Restoring Root (Optional)
Just follow one of the below guides again after you are back up and running:
For VRUAMDK Build (Look for this) - Link
For VRUAME7 Build (Look for this) - Link
For VRUDMI1 Build (Look for this) - Link
Click to expand...
Click to collapse
Step 4 - Restoring Custom Recovery (VRUAMDK Build only!)
Make sure you are rooted first
For official TWRP Recovery follow the steps in this thread (or download from Goomanager): Link Here
For official ClockworkMod Recovery just download ROM Manager app and install from there
For CWM-based Recovery follow the steps in this thread: Link Here
For OUDHS Gesture Touch CWM-based Recovery follow the steps in this thread: Link Here
Click to expand...
Click to collapse
Credits
Credit goes to sextape for providing the original VRUAMDK Stock Firmware (Original Source)
Credit goes to mrRobinson for assisting to modify cache file (via PM)
Credit goes to alexcolodner for providing filehosting (via PM)
Wonderful! Thank you
Thanks for this. On point as usual
Sent from my SCH-I545 using xda premium
This is GREAT!!! Thank you.
Sent from my SCH-I545 using Tapatalk 2
@open1your1eyes.... can this be posted on droid-hive?
sporty377 said:
@open1your1eyes.... can this be posted on droid-hive?
Click to expand...
Click to collapse
Certainly, just make sure to give the proper credits as I have in my post.
open1your1eyes0 said:
Certainly, just make sure to give the proper credits as I have in my post.
Click to expand...
Click to collapse
yes sir thanks
This is very good,this post deserve another sticky.
is this good for restoring to factory for insurance purposes? My s4 has a defect and I have to take it back in to get a replacement :-/
Elvis_Marmaduke said:
is this good for restoring to factory for insurance purposes? My s4 has a defect and I have to take it back in to get a replacement :-/
Click to expand...
Click to collapse
Absolutely, just with this one make sure to do your own data wipe afterwords since this one doesn't wipe it automatically.
It didn't put me on stock recovery so i was still getting that unlocked bootloader thingie, but I found a stock recovery and it worked like a charm, thanks a lot
Elvis_Marmaduke said:
It didn't put me on stock recovery so i was still getting that unlocked bootloader thingie, but I found a stock recovery and it worked like a charm, thanks a lot
Click to expand...
Click to collapse
Ahh I knew I forgot something. Simple fix, I'll get the new one up either tonight or tomorrow. For now you can probably consider it a good thing you don't have to reflash recovery if you're trying to keep data. :good:
open1your1eyes0 said:
No-Wipe Factory Image for Verizon Galaxy S4
(Restore from any soft-brick without wiping data)
Description: This is a guide (based similar to my previous guide for the Verizon Galaxy S III) that will help you flash a 99.9% stock factory image for the Verizon Galaxy S4 overwriting every partition on the device back to stock. The ONLY major change I have made is for your convenience I have modified the factory image to keep all your data/apps/settings and internal storage partition intact. This method should help you restore from any soft-brick that you may encounter without having to wipe your data.
Minor Warning: Please note that if you had any special mods that you had to manually flash before or move on the system partition (like Google Wallet, AOSP 4.2 apps like camera and gallery, etc...) they will be lost as you are overwriting your system partition to factory stock. Please make sure to do the needful with your mods before following this guide (for example resetting the Google Wallet app).
Step 1 - Preparation
Step 2 - Flashing VRUAMDK Factory Image
Step 3 - Restoring Root (Optional)
Step 3 - Restoring Custom Recovery (Optional)
Credits
Credit goes to sextape for providing the original VRUAMDK Stock Firmware (Original Source)
Credit goes to mrRobinson for assisting to modify cache file (via PM)
Credit goes to alexcolodner for providing filehosting (via PM)
Click to expand...
Click to collapse
after the step 3 do i have to do this
Step 4 - Restoring VRUAMDK Stock Kernel
Quote:
Boot phone into ODIN mode (See here for how-to)
Flash the VRUAMDK Stock Kernel using ODIN v3.07 ***in PDA section only*** (See here for guide on flashing)
Boot back to Android and verifying everything is still working and kernel has flashed successfully
After your phone boots back to Android, you should now be fully rooted and on the fully original stock firmware as the device came
android-incredible said:
after the step 3 do i have to do this
Step 4 - Restoring VRUAMDK Stock Kernel
Quote:
Boot phone into ODIN mode (See here for how-to)
Flash the VRUAMDK Stock Kernel using ODIN v3.07 ***in PDA section only*** (See here for guide on flashing)
Boot back to Android and verifying everything is still working and kernel has flashed successfully
After your phone boots back to Android, you should now be fully rooted and on the fully original stock firmware as the device came
Click to expand...
Click to collapse
Please kindly do not quote the entire post. Also I believe you're referring to my root thread in which case yes you should, but please keep posts related in that thread instead.
I have uploaded and updated OP link with new No-Wipe image that includes stock recovery now as well.
Hello will this method work wit the s4 att phone... Plz say it will work I got myself in a jam...thanks
please help! im getting a compressed folder is invalid or corruted when trying to extract the file. i have tried to re download and get the same thing.
edit: the factory extract tool sucks. thanks 7zip
I was talking about no wipe factory image.and i was confuse with this process,because after the step 3 l wasnt sure if i have to go to the step 4.
azz72 said:
Hello will this method work wit the s4 att phone... Plz say it will work I got myself in a jam...thanks
Click to expand...
Click to collapse
May want to check with the dev who posted the AT&T firmware to make one. This is Verizon only!
android-incredible said:
I was talking about no wipe factory image.and i was confuse with this process,because after the step 3 l wasnt sure if i have to go to the step 4.
Click to expand...
Click to collapse
Steps 3 and 4 in this thread are optional only if you're trying to restore root and custom recovery again and you had it before or just want it for the first time. If you don't know, may want to read up on it in the thread. Probably don't need it for now.
I dont have to do it now,my problem was with a custom rom,after install the custom rom the phone reboot with the padlock,i was trying to get rid of the pad lock reinstallig the goomanager and no luck,what i did was restore my nandrood backup and the padlock gone.
I'm terribly sorry is this is the wrong place to post this, but I'm new to the whole 'forums' in general thing.
A while ago, a friend came to me and said his android was growing buggy, so I told him how to factory reset it and such. Then I rooted it for him to clear it of any stock apps he didn't want. Now I've currently got the device next to me, and I've tried installing a custom rom onto it for him, to help make his device a bit faster and less buggy. I tried installing PAC-ROM ( http://forum.xda-developers.com/showthread.php?t=2235446 ), but I got the same error in CWM that I got when I tried to flash my HTC Glacier, which was remedied by updating to the latest CWM. I tried updating CWM from its current 5.0.2.7 to something 6.0+, but the 5.0 version sticks, which might be due to the fact that I used ODIN to flash the CWM according to a different XDA forum, which I cannot locate right now. Now, after attempting to flash PAC-ROM, and getting said errors, I seem to be unable to remount anything from CWM (/system, /data, etc), so the device cannot boot.
Is the device bricked for good, or is there something that can help me? I'm not totally inexperienced with flashing/customizing android, but I'm not great at it either.
Thanks for the help in advanced.
uhhh, what exactly did you flash to upgrade CWM? Did you use something for another device? Because you arent supposed to do that.
I would reboot into download mode, and then flash the stock firmware. Then you can flash a either RJ's kernel (for INTL) or Entropy's kernel (US) depending on what device you have. To flash PAC, you have to first flash a cm9 rom, reboot into recovery, and then flash PAC
iurnait said:
uhhh, what exactly did you flash to upgrade CWM? Did you use something for another device? Because you arent supposed to do that.
I would reboot into download mode, and then flash the stock firmware. Then you can flash a either RJ's kernel (for INTL) or Entropy's kernel (US) depending on what device you have. To flash PAC, you have to first flash a cm9 rom, reboot into recovery, and then flash PAC
Click to expand...
Click to collapse
I've reflashed stock through ODIN, and this showed up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Do a wipe data and see if your errors are resolved
iurnait said:
Do a wipe data and see if your errors are resolved
Click to expand...
Click to collapse
I did, it gave me the 'error can't mount /system, /data, etcetc' thing, and then rebooted, and now it's stuck in CWM.
you probably need to find the pit file and flash that via odin. just keep holding the power and volume down keys until you are in recovery. then put the pit file in odin along with the stock firmware and flash.
Pits:
http://forum.xda-developers.com/showthread.php?t=1389873
iurnait said:
you probably need to find the pit file and flash that via odin. just keep holding the power and volume down keys until you are in recovery. then put the pit file in odin along with the stock firmware and flash.
Pits:
http://forum.xda-developers.com/showthread.php?t=1389873
Click to expand...
Click to collapse
Found the stock here http://forum.xda-developers.com/showthread.php?t=2192488 , but I get errors when trying to flash everything.
TacoSeeker said:
Found the stock here http://forum.xda-developers.com/showthread.php?t=2192488 , but I get errors when trying to flash everything.
Click to expand...
Click to collapse
After trying a few more times, I end up with the same screen as I posted before, the android recovery screen.
try downloading and extracting this: http://forum.xda-developers.com/attachment.php?attachmentid=812772&d=1323614740
this contains odin version 1.81, which has always worked for me.
TacoSeeker said:
Found the stock here http://forum.xda-developers.com/showthread.php?t=2192488 , but I get errors when trying to flash everything.
Click to expand...
Click to collapse
That PIT file is invalid. It has never worked and never will. If you need the pit file then get it from Adam Outler's post that has all the PIT files for the all players 5.0.
I didn't know what I was doing when I made it. I just dumped the partition that has the pit file on it and that is what that is. NO ONE SHOULD EVER USE ueki8.pit FROM YP-G70_UEKI8_MIN !!!
Try using Heimdall.
TheKryptonite said:
Try using Heimdall.
Click to expand...
Click to collapse
Heimdall says it can't connect to the devices, libusb error -12
iurnait said:
try downloading and extracting this: http://forum.xda-developers.com/attachment.php?attachmentid=812772&d=1323614740
this contains odin version 1.81, which has always worked for me.
Click to expand...
Click to collapse
Even after flashing using that, it still returns me to either the download screen, or the recovery screen.
Now the devices is stuck in a state where it won't exit download mode.
TacoSeeker said:
Heimdall says it can't connect to the devices, libusb error -12
Click to expand...
Click to collapse
Are you drivers installed? Did you install the drivers on Zadig?
TheKryptonite said:
Are you drivers installed? Did you install the drivers on Zadig?
Click to expand...
Click to collapse
Yes, I always stay updated on drivers on my PC.
TacoSeeker said:
Yes, I always stay updated on drivers on my PC.
Click to expand...
Click to collapse
Try uninstalling the Samsung drivers and Kies. Try to find the Samsung device and replacing/installing all drivers.
TheKryptonite said:
Try uninstalling the Samsung drivers and Kies. Try to find the Samsung device and replacing/installing all drivers.
Click to expand...
Click to collapse
Same result as before.
Try the instructions here. http://forum.xda-developers.com/showthread.php?p=44192192
Meticulus said:
Try the instructions here. http://forum.xda-developers.com/showthread.php?p=44192192
Click to expand...
Click to collapse
After all that, I still get the screen showed in my previous comment,