Hi
I own a 100% stock Samsung Galaxy S2 (GT-i9100).
The device is not rooted or modified and is currently running standard Samsung firmware.
Baseband I9100XXMS2
Kernel 3.0.31-1211311
Build numberJZ054K.I9100XWLSW
Android 4.1.2
Whilst I am not a power user I am tired of running out of system memory and having to move apps to the SD card. I am also tired of not being able to load certain apps due to the old Android version. I do want to connect to my car via Bluetooth (audio and internet etc).
It's time for a new operating system ... hence my visit to this web site. I have tried reading the guides but most use a lot of jargon and talk of multiple ROM options. I am a little lost and need some plain English instruction to follow since this is my first step into the ROM flashing world.
Which version should I install? Where do I download it from? What tools do I need for my PC? How do I do the flash?
Anyone out there who can help a complete novice?
Thanks in advance
Jacbjacb said:
Hi
I own a 100% stock Samsung Galaxy S2 (GT-i9100).
The device is not rooted or modified and is currently running standard Samsung firmware.
Baseband I9100XXMS2
Kernel 3.0.31-1211311
Build numberJZ054K.I9100XWLSW
Android 4.1.2
Whilst I am not a power user I am tired of running out of system memory and having to move apps to the SD card. I am also tired of not being able to load certain apps due to the old Android version. I do want to connect to my car via Bluetooth (audio and internet etc).
It's time for a new operating system ... hence my visit to this web site. I have tried reading the guides but most use a lot of jargon and talk of multiple ROM options. I am a little lost and need some plain English instruction to follow since this is my first step into the ROM flashing world.
Which version should I install? Where do I download it from? What tools do I need for my PC? How do I do the flash?
Anyone out there who can help a complete novice?
Thanks in advance
Click to expand...
Click to collapse
Mate, take it easy, i see you are a good English speaker, it should be very easy for you to understand the guides, for me it was hard and i bricked my phone multiple times, I'm not saying that I'm a geek or an android expert or something like that, but i know enough about my phone and i know what it's capable of and what it isn't, you should start easy step by step, and try following a video guide from YouTube like searching in google "i9100 root and custom recovery" and start reading some articles about it, believe me no one would just give you instructions on a silver plate, even if someone did, you will remain a noob who knows nothing about flashing and you won't be able to change your new rom or go back to stock rom..you should dig for it, there are guides that provide you with instructions and information about what you do..all you have to do is do a couple of google searches..
Anyway, all i can do to you is give you a link to this guide
Hope you understand the message
Regards Migo
Well I spent the entire afternoon and evening yesterday reading all I could about the flashing of the this Samsung Galaxy S2 GT-i9100. I then started to collect the files I think I will need:
Heimdall Suite: Inc' zadig.exe 2.0.0147, heimdall-frontend.exe 1.4.0, heimdall.exe
Lineage 14.1 Rom: cm-14.1-20161225-UNOFFICIAL-i9100.zip
Minimal_adb_fastboot_v1.4.2_setup.exe: Inc' adb.exe. cmd-here.exe, fastboot.exe etc
Odin3 v1.85.exe
open_gapps-arm-7.1-nano-20170225.zip
PIT Files: I9100_2GB-STOCK.pit (in case of problems) and I91001GB_6GB.pit
SAMSUNG USB Driver for Mobile Phones 1.5.27.0.exe
TWRP: twrp-3.0.2-1-i9100.img, recovery-the.gangster-IsoRec-TWRP-3.0.2-1-i9100.zip,
On the phone I activated USB Debugging
I installed the USB drivers and the PC can see the phone
I ran Odin and the phone is seen
I tried to install TWRP using the instructions found here: https://twrp.me/devices/samsunggalaxys2i9100.html .... It didn't work!
I copied recovery-the.gangster-IsoRec-TWRP-3.0.2-1-i9100.zip to the SD card, entered recovery mode and tried to apply the update from external storage. All seem to go well but then I got E:Error in tmp/sideload/package.zip (Status 7) ..... at the Top of the page it said Android System recovery (3e) ... I take it that is the system recovery currently installed on the phone. I found twrp-3.0.2-0-i9100.zip and tried that .... but got the same System 7 error!
So I have got nowhere really!
I know I have to repartition the drive using the PIT file
I know I have to load a custom recovery file using the TWRP
I then have to load the new ROM
But I don't know the order in which to do the operations .... TWRP first or PIT?
I don't seem to be alone in my fog ... see https://forum.xda-developers.com/ga...twrp-galaxy-s2-i9100-tried-t3539940?nocache=1
I have now realized that the various guides relate to the version of ROM they wish to install .... I am planning to use a Lineage 14.1 Rom. It seems that I can load it using TWRP or Odin.
I think the first step is to load TWRP ....... But I cant seem to be able to do that ..... Can Anyone help me install TWRP if that if the first priority?
Well I spent the entire afternoon and evening yesterday reading all I could about the flashing of the this Samsung Galaxy S2 GT-i9100. I then started to collect the files I think I will need:
Heimdall Suite: Inc' zadig.exe 2.0.0147, heimdall-frontend.exe 1.4.0, heimdall.exe
Lineage 14.1 Rom: cm-14.1-20161225-UNOFFICIAL-i9100.zip
Minimal_adb_fastboot_v1.4.2_setup.exe: Inc' adb.exe. cmd-here.exe, fastboot.exe etc
Odin3 v1.85.exe
open_gapps-arm-7.1-nano-20170225.zip
PIT Files: I9100_2GB-STOCK.pit (in case of problems) and I91001GB_6GB.pit
SAMSUNG USB Driver for Mobile Phones 1.5.27.0.exe
TWRP: twrp-3.0.2-1-i9100.img, recovery-the.gangster-IsoRec-TWRP-3.0.2-1-i9100.zip,
On the phone I activated USB Debugging
I installed the USB drivers and the PC can see the phone
I ran Odin and the phone is seen
I tried to install TWRP using the instructions found here: https://twrp.me/devices/samsunggalaxys2i9100.html .... It didn't work!
I copied recovery-the.gangster-IsoRec-TWRP-3.0.2-1-i9100.zip to the SD card, entered recovery mode and tried to apply the update from external storage. All seem to go well but then I got E:Error in tmp/sideload/package.zip (Status 7) ..... at the Top of the page it said Android System recovery (3e) ... I take it that is the system recovery currently installed on the phone. I found twrp-3.0.2-0-i9100.zip and tried that .... but got the same System 7 error!
So I have got nowhere really!
I know I have to repartition the drive using the PIT file
I know I have to load a custom recovery file - TWRP
I then have to load the new ROM
But I don't know the order in which to do the operations .... TWRP first or PIT?
I don't seem to be alone in my fog ... see https://forum.xda-developers.com/ga...twrp-galaxy-s2-i9100-tried-t3539940?nocache=1
I have now realized that the various guide relate to the version of ROM you wish to install .... I am planning to use a Lineage 14.1 Rom. It seems that I can load it using TWRP or Odin.
I think the first step is to load TWRP ....... But I cant seem to be able to do that ..... Can Anyone help?
Jacbjacb said:
I have now realized that the various guide relate to the version of ROM you wish to install .... I am planning to use a Lineage 14.1 Rom. It seems that I can load it using TWRP or Odin.
I think the first step is to load TWRP ....... But I cant seem to be able to do that ..... Can Anyone help?
Click to expand...
Click to collapse
The TWRP you are trying to install requires a kernel that supports isorec, so you must have that kernel first.
To have isorec support:
Note: -the rom and the isorec recovery and nogut rom and gapps -in short: all files- should be put in external sdcard because the internal sdcard will be wiped in the procedure.
1-you should install latest kernel-Lanchon-TRIM-IsoRec, you can easily flash it using a
Kitkat compatible recovery, flash the recovery using Odin along with a pit that has 1GB system or more,
1.5GB PIT Files by the.gangster or 1GB PIT Files by ELgmal 1GB is enough
2-after that, reboot to recovery:
• wipe data
• wipe cache
• navigate to "mount" and format system and format internal sdcard using (default)
• go back and navigate to "advanced" and wipe Dalvik cache.
• then go back and choose "install zip from sdcard1 (external sdcard)"
• and navigate to your kernel-Lanchon-TRIM-IsoRec and flash it.
• install arnab isorec recovery twrp zip by the gangster
• reboot your recovery, you will find the TWRP installed, now wipe system and data and cache and dalvik and install your nogut rom and the correct gapps.
that's it
Alternative Method
DON'T use odin to flash pit, just use it to flash the kitkat compatible recovery.
• flash Kitkat Compatible recovery with odin.
• in recovery flash kernel-Lanchon-TRIM-IsoRec and then flash twrp 3 isorec.
• and reboot recovery, then in TWRP 3 flash lanchon repit tool.
Lanchon repit tool is a simple flashable zip that can be edited to split the partition in desired way, read more about it in the official thread
This method was recommended by @TriboDoP
All credits goes to our great Developers.
MigoMujahid said:
The TWRP you are trying to install requires a kernel that supports isorec, so you must have that kernel first.
To have isorec support:
Note: -the rom and the isorec recovery and nogut rom and gapps -in short: all files- should be put in external sdcard because the internal sdcard will be wiped in the procedure-
1-you should install latest CM11, you can easily flash it using a
Kitkat compatible recovery, flash the recovery using Odin along with a pit that has 1GB system or more,
1.5GB PIT Files by the.gangster or 1GB PIT Files by ELgmal 1GB is enough
2-after that, reboot to recovery:
• wipe data
• wipe cache
• navigate to "mount" and format system and internal sdcard
• go back and navigate to "advanced" and wipe Dalvik cache.
• then go back and choose "install zip from sdcard1 (external sdcard)"
• and navigate to your cm11 rom and install the rom
• install arnab isorec recovery twrp zip by the gangster
• reboot your recovery, you will find the TWRP installed, now wipe system and data and cache and dalvik and install your nogut rom and the correct gapps.
that's it
Alternative Method
• flash Kitkat Compatible recovery with odin.
• in recovery flash cm11 with twrp 3 isorec.
• and reboot recovery, then in TWRP 3 flash lanchon repit tool.
Lanchon repit tool is a simple flashable zip that can be edited to split the partition in desired way, read more about it in the official thread
This method was recommended by @TriboDoP
All credits goes to our great Developers.
Click to expand...
Click to collapse
WOW IT WORKED! THANK YOU THANK YOU THANK YOU!
I used the following files:
SAMSUNG_USB_Driver_for_Mobile_Phones v1.5.51.0.exe
Lineage-11-20170115-UNOFFICIAL-i9100.zip … (CM11)
CWM-KitKatCompatible-i9100.tar
Odin3 v3.07
PIT Files: I91001GB_6GB.pit
Lineage 14.1 Rom: cm-14.1-20161225-UNOFFICIAL-i9100.zip
TWRP: twrp-3.0.2-1-i9100.img, recovery-the.gangster-IsoRec-TWRP-3.0.2-1-i9100.zip
open_gapps-arm-7.1-nano-20170225.zip
All went well following the upgrade of SAMSUNG USB Driver for Mobile Phones 1.5.27.0.exe to SAMSUNG_USB_Driver_for_Mobile_Phones v1.5.51.0.exe. Odin 3 v3.07 had communication problems in download mode with the earlier drivers.
I followed your instructions to the letter (printed and ticked as I progressed) and only had one issue when it came to formatting the internal sdcard ….. I didn’t know what format so I selected “default” which worked.
I used a PIT file I had rather than your files simply because I didn’t know which one of your files to choose … too many options! I didn't fully appreciate the difference between them?
What can I say but Thank You …. This must be the simplest and BEST GUIDE out there for somebody going from a stock 4.1.2 to 7.1.1
One last question ..... how do I read my SD card (external) now that I have flashed my phone with 7.1.1?
Windows can see the SD card but wont let me read the contents. I have read https://www.reddit.com/r/Android/comments/3nnkaa/cant_access_android_device_internal_storage_from/ and put the phone into MTP for the USB.
Jacbjacb said:
One last question ..... how do I read my SD card (external) now that I have flashed my phone with 7.1.1?
Windows can see the SD card but wont let me read the contents. I have read https://www.reddit.com/r/Android/comments/3nnkaa/cant_access_android_device_internal_storage_from/ and put the phone into MTP for the USB.
Click to expand...
Click to collapse
It should work, I'm using AICP 12.1 (7.1.1) build 7 Feb, and it's working when i set it to MTP, but sometimes i have to change the cable, try changing the cable or use another USB port.
I installed AICP because official LineageOS 14.1 is buggy these days.
Thanks for the tip i forgot when formatting internal sdcard using default, i edited the guide and added it to my signature so every one can easily find it.
There are good talks about other nogut roms like crDroid and xenonHD, i would try them, but it would take time and i only have one s2 and it's my daily driver, so i couldn't, but many people recommended them.
I'm happy that i was able to help you, and thank you for telling me that my guide was easy, i was afraid that it might be complicated or something
Regards Migo
---------- Post added at 10:28 PM ---------- Previous post was at 10:22 PM ----------
Jacbjacb said:
One last question ..... how do I read my SD card (external) now that I have flashed my phone with 7.1.1?
Windows can see the SD card but wont let me read the contents. I have read https://www.reddit.com/r/Android/comments/3nnkaa/cant_access_android_device_internal_storage_from/ and put the phone into MTP for the USB.
Click to expand...
Click to collapse
Oh, you meant the external sdcard, have you mount it after the first boot, you must have got some notification about it.
If you didn't, navigate to storage in settings and choose the external sdcard and you will be asked to mount it as a "portable storage" or an "internal storage", choose "portable storage".
Jacbjacb said:
One last question ..... how do I read my SD card (external) now that I have flashed my phone with 7.1.1?
Windows can see the SD card but wont let me read the contents. I have read https://www.reddit.com/r/Android/comments/3nnkaa/cant_access_android_device_internal_storage_from/ and put the phone into MTP for the USB.
Click to expand...
Click to collapse
You can use recovery to transfer between computer and phone.(in case the rom fails to do that)
Related
Hello,
I've searched many topics but still didn't work
My NT 16GB worked good till today. Today I want to flash a new ROM (CM10.1 rc5).
I though I made a mistake from here: from ROM Manager, I flashed the CWM to 6.0, but I might flash with Nook Color version :crying: and from this time, my NT is ALWAYS boot into recovery mode.
- I tried press Power and N button or 8 times fail reboots but it still boot into recovery
- I tried flash new ROM from sd card, and the status is shown Installing Update.... and then it shown Install from sd card completed!!! There was no any notification more (as usual). And after "completed" by this way, reboot and still went into recovery mode again
- I also tried flash new cwm version 6.0.x, wipe data, format system, data,.... and flash ROM again from sdcard but still didnt work.
- I also tried reset to factory default http://forum.xda-developers.com/showthread.php?t=1663836 but it still boot into CWM again and again.
- and follow many topics on google search but still no luck
please anyone can give me a hint, let me see the way to escape the recovery screen :crying::crying: thank you so much!
I want to flash a new ROM, a fresh tablet to make a gift for my dad on father's day, but it is brick :crying::crying::crying:
I think using ROM manager to flash recovery may not work with our device (I may be wrong) but we don't have an official build of CWM.
Regardless.... Do you have adb set up? If so, does it recognize your nt?
Sent with my Dinc4G
DavDoc said:
I think using ROM manager to flash recovery may not work with our device (I may be wrong) but we don't have an official build of CWM.
Regardless.... Do you have adb set up? If so, does it recognize your nt?
Sent with my Dinc4G
Click to expand...
Click to collapse
I have adb set up, but it doesn't recognize my NT , it always boot to recovery mode
Ok, no big deal yet. Lets try the following.
First you are going to need an extra SD card, one greater than 2G. Go to this thread http://forum.xda-developers.com/showpost.php?p=21895025&postcount=14 and follow the instructions. This will give you the files and show you how to make a CWM bootable SD card (ignore all the steps about rooting your device in this thread for now). Note that this will repartition your SD card, so you will not be able to use is for much else unless you re-repartition it yourself.
To tell if this is successful or not, note the version of CWM you are now booting into, I am guessing it will be 6.0.3.1 (newest version) since you tried getting this from Rom Manager. If it is booting from SD card it should show up as version 5.0.x.x (I don't remember the exact version but it is older).
If you got it to boot from SD card then lets pull an updated version of CWM from this site http://goo.im/devs/succulent/acclaim/recovery The older version of CWM may not work well with CM10.1. try CWM 6.0.2.9, make sure you download the flashable CWM zip and not the image file.
OK now you will need to put this zip file onto your SD card - there should be just enough room left for it, or you could put it onto a 2nd SD card (easier) Note: while in recovery you can take the bootable SD card out of your NT. Go ahead and flash the CWM zip. You should now have a working recovery. At this point try flashing a ROM of your choice.
Good Luck
DavDoc said:
Ok, no big deal yet. Lets try the following.
First you are going to need an extra SD card, one greater than 2G. Go to this thread http://forum.xda-developers.com/showpost.php?p=21895025&postcount=14 and follow the instructions. This will give you the files and show you how to make a CWM bootable SD card (ignore all the steps about rooting your device in this thread for now). Note that this will repartition your SD card, so you will not be able to use is for much else unless you re-repartition it yourself.
To tell if this is successful or not, note the version of CWM you are now booting into, I am guessing it will be 6.0.3.1 (newest version) since you tried getting this from Rom Manager. If it is booting from SD card it should show up as version 5.0.x.x (I don't remember the exact version but it is older).
If you got it to boot from SD card then lets pull an updated version of CWM from this site http://goo.im/devs/succulent/acclaim/recovery The older version of CWM may not work well with CM10.1. try CWM 6.0.2.9, make sure you download the flashable CWM zip and not the image file.
OK now you will need to put this zip file onto your SD card - there should be just enough room left for it, or you could put it onto a 2nd SD card (easier) Note: while in recovery you can take the bootable SD card out of your NT. Go ahead and flash the CWM zip. You should now have a working recovery. At this point try flashing a ROM of your choice.
Good Luck
Click to expand...
Click to collapse
Hello DavDic,
Thank you for your help,
I follow your link and I success to boot from SD card, and CWM version is 5.0.5, then I success install the update.zip too, unfortunately after removing the sd card and reboot, it still boot to CWM version 6.0.2.9 - this is the version that I flash from ROM Manager before my NT is bricked (I flashed wrong device when I choose Nook Color in Rom Manager)
So I try to reboot again from sdcard, cwm version 5.0.5, then flash new CM10.1 ROM, and reboot and still go to CWM 6.0.2.9
and again, I boot from sdcard, cwm version 5.0.5, flash to new cwm version 6.0.2.9, flash new ROM and still boot to CWM screen
So, I can create and boot from a Sdcard, But can not boot to OS, always go to cwm 6.0.2.9 screen (that I think the wrong file since I flash from Nook Color file ). Thank you!
h a l t said:
Hello,
I've searched many topics but still didn't work
My NT 16GB worked good till today. Today I want to flash a new ROM (CM10.1 rc5).
I though I made a mistake from here: from ROM Manager, I flashed the CWM to 6.0, but I might flash with Nook Color version :crying: and from this time, my NT is ALWAYS boot into recovery mode.
...
please anyone can give me a hint, let me see the way to escape the recovery screen :crying::crying: thank you so much!
...
Click to expand...
Click to collapse
I think your problem most likely has to do with BCB/BootCnt not getting reset properly, as described at http://forum.xda-developers.com/showpost.php?p=21381141&postcount=1.
If so, the easiest way of resetting these files is to flash Succulent's flashable_fix_bootloop.zip at his repo http://goo.im/devs/succulent/acclaim/recovery.
digixmax said:
I think your problem most likely has to do with BCB/BootCnt not getting reset properly, as described at http://forum.xda-developers.com/showpost.php?p=21381141&postcount=1.
If so, the easiest way of resetting these files is to flash Succulent's flashable_fix_bootloop.zip at his repo http://goo.im/devs/succulent/acclaim/recovery.
Click to expand...
Click to collapse
Thank you, I did but no luck still boot to recovery mode
You need to try and get an adb connection. I assume you are running Windows, if not............
But, what happens when you plug your NT into your computer. Do either of your drives (Internal/external SD) show up in my computer?
DavDoc said:
You need to try and get an adb connection. I assume you are running Windows, if not............
But, what happens when you plug your NT into your computer. Do either of your drives (Internal/external SD) show up in my computer?
Click to expand...
Click to collapse
Both drives show up in my windows computer, but I can't read, "please insert a disk" error when I double click on drive,
I am trying this thread http://forum.xda-developers.com/showthread.php?t=1470910 and hope...
h a l t said:
Both drives show up in my windows computer, but I can't read, "please insert a disk" error when I double click on drive,
I am trying this thread http://forum.xda-developers.com/showthread.php?t=1470910 and hope...
Click to expand...
Click to collapse
You should have an adb connection then. Before you jump into the total wipe attempt, try getting an adb connection. Use this first and see if it works http://forum.xda-developers.com/showpost.php?p=36650082&postcount=171
You will need the driver files for this though, let me know if you don't have them.
DavDoc said:
You should have an adb connection then. Before you jump into the total wipe attempt, try getting an adb connection. Use this first and see if it works http://forum.xda-developers.com/showpost.php?p=36650082&postcount=171
You will need the driver files for this though, let me know if you don't have them.
Click to expand...
Click to collapse
Yes I have the driver files, on device manager it shown Android Phone ADB interface, something like this, and what is the next step please...
h a l t said:
Yes I have the driver files, on device manager it shown Android Phone ADB interface, something like this, and what is the next step please...
Click to expand...
Click to collapse
You should have adb access given what you just said.
Are you familiar with command prompts and adb commands?
DavDoc said:
You should have adb access given what you just said.
Are you familiar with command prompts and adb commands?
Click to expand...
Click to collapse
yes I have adb access from Dos, but don't know which command to fix my problem. Thanks so much for your patience, still googling
h a l t said:
yes I have adb access from Dos, but don't know which command to fix my problem. Thanks so much for your patience, still googling
Click to expand...
Click to collapse
Well this is a start at least.
I think Digixmax may be on to something though.
@digixmax, I am at work and don't have an NT in front of me, do you remember which partition the recovery is in. I wanted OP to see if those two files were even there. He may have gotten rid of them completely inadvertently.
DavDoc said:
Well this is a start at least.
I think Digixmax may be on to something though.
@digixmax, I am at work and don't have an NT in front of me, do you remember which partition the recovery is in. I wanted OP to see if those two files were even there. He may have gotten rid of them completely inadvertently.
Click to expand...
Click to collapse
F5, F5, ..... I see the light at the end of the tunnel,... God, what is the adb, shell command to help me escape this trouble :angel::angel:
DavDoc said:
Well this is a start at least.
I think Digixmax may be on to something though.
@digixmax, I am at work and don't have an NT in front of me, do you remember which partition the recovery is in. I wanted OP to see if those two files were even there. He may have gotten rid of them completely inadvertently.
Click to expand...
Click to collapse
These two files are in the /bootdata partition (see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for a list of the NT partitions and their content).
But if OP's flashing Succulent's flashable_fix_bootloop.zip (which basically re-install a fresh copy of these two files) didn't fix the problem then he might have wiped out some other critical components of the system.
I follow Adam's guide, unbrick my NT, and then flash new CM10.1 ROM perfectly.
Thank you again DavDoc and digixmax for helping me so much! :good:
Glad you got it working again
Sent with my Dinc4G
Hello,
my girlfriend had a S5839i that I rooted and put a custom recovery on (CWM) and to gain some performance I flashed a kernel that was described as being compatible to this specific device, too and after flashing in CWM I got a phone stuck at boot logo. I can't get into recovery mode anymore and now I need to recover data that is not stored on external, but the internal storage. I really need to get into a mode where I can copy data from the storage.
Is there any possibility to do this or does someone even know how to unbrick the device?
Thanks a lot!
Regards,
Nash.
nashsx said:
Hello,
my girlfriend had a S5839i that I rooted and put a custom recovery on (CWM) and to gain some performance I flashed a kernel that was described as being compatible to this specific device, too and after flashing in CWM I got a phone stuck at boot logo. I can't get into recovery mode anymore and now I need to recover data that is not stored on external, but the internal storage. I really need to get into a mode where I can copy data from the storage.
Is there any possibility to do this or does someone even know how to unbrick the device?
Thanks a lot!
Regards,
Nash.
Click to expand...
Click to collapse
Humm,, Please define the version of Temp-CWM you did flash( CooperVe compatible assuming)
Define 'flashed a kernel' please, Your stock firmware already contains a stock kernel, which is quite capable of performing what we are expecting from basic kernel. ( Explains in details how did you install custom kernel or custom Roms etc etc,,)
Always do your Nandroid/EFS/Data back up prior to tinkering though.
IF the only option available to you due to soft bricking is , Downland mode >> upon flashing over Odin your /data partition will be wiped out for successful restoration of your device.
waiting for your through explanation,,,,,,
Hello,
thanks for your reply. Unfortunately I cannot specify the CWM version anymore, but I flashed a custom kernel via the CWM, it was a flashable zip file downloaded somewhere in this forum that I flashed using CWM (which I installed using ODIN, iirc). The reason I cannot say what CWM I installed is, I had a data loss on the hard drive inside my computer where I downloaded the files to. If it's really important to know what kernel it was, then I believe I could reconstruct this by searching the custom kernel section for the specific device in this section, I am sure I will know when I read the name again. While waiting for a new reply I'm gonna do this to find out what kernel I flashed via CWM.
The problem with the last resort suggested by you, ODINand download mode and this stuff, is that the data I need to restore is located in data partition if I am correct. Or maybe I'm wrong? The data is from the android text editor notepad which I found out doesn't store data in /sdcard partitions, neither internal nor external, so if I'm right, this means it's being stored in the application's data directory. Please tell me if I'm wrong with this guess.
.
Regards,
Nash.
@nashsx, I fully understand your concern in regards of sensitive data recovery from internal SD partition. However you need to be more specific with all of the tools and Roms you did use whenever you ask for accurate assistance .
Nevertheless I am going to explain all of the errors and possible symptoms you might encounter during CWM flashing to Kernel procedure .
First , You need to comprehend that for your device's ( known as CooperVe) safety we need to use compatible temporary CWM flash able zip file or CWM comes with kernel . The latter is not recommended though for many reasons I would not engage at the moment ( files could be found here or here for instance,,,OR any official sticky topic )
As for kernel Let me be clear : We do not flash custom kernel on top of stock firmware for s5830i/C/M/5839i devices under any circumstances. This is a correct order >>
Stock Firmware >Custom Rom based on stock kernel > Custom kernel
Alternative : flash Custom Rom comes with custom Kernel , and there are so many wiping and formatting process will be involved in between flashing I would not go into more details .
Basically we are obtaining an exclusive right to use Mods/Scripts/Tweaks : performance , battery ,, etc etc at boot time , by activating our init.d support with the help of custom kernels and much more stuff we can perform after flashing. ( Well established name you requested : Rafael.Baugis ; ThunderKernel ; CyanogenMod 7.2 Specific BASIC Kernel ; Hells Fusion )
Now a little educational standard internal memory partitions one- on-one :
/boot
/system
/recovery
/data
/cache
/misc
SD card partitions :
/sdcard
/sd-ext
/data or User data , is the part in question you are trying to access via recovery , which is not an option anymore sadly.
This is where your contacts, messages, settings and apps that you have installed go. Wiping this partition over Odin with the help of wipe - flash able 3 parts package made by splitfus2 app( and other options ticked : re-partition and pit & boot loader selected ) for example ;essentially performs a factory reset on your device; restoring it to the way it was when you first booted it.
We only have 2 options ( if you can call it an option at all in reality ) for recovery procedure , since you don't have access to either of stock e3 / CWM recovery consoles .
1.Normally During boot loop ADB won't work, but we can give it a try ( ADB debugging option must be ticked inside Developer settings inside your Android OS ; platform-tools is required or any GUI based app such as Droid manger will do .
2. Flashing only one part file ( xxx.tar.md5) Over Odin3.v3.07.Cooperve ; you may pick your file from here < registration is required >. Proper drivers installed inside your PC; Put the file into PDA part and do not touch anything else ( Factory reset and Re-partition not selected, Reboot option is OK though ) > click start. ( Do not remove USB cable till the process being terminated and take a complete screen shot of Odin log file entries for me.
This method does not wipe the partition in question., but there is a strong possibility you can not bypass the initial boot loop to get into the OS though.
Hi all,
to make it plain and short: I messed up.
I have a GT-S5830i which I unrooted according to the Sticky Note in the forum, installed CWM Recovery and then 'installed from ZIP' a CM9_cooperve_Beta_05.zip that I found in one of the posts in the forum. The installation went on without error message but since then the phone does not make it beyond the initial screen "Samsung Galaxy Ace GT-S5830i". I can start recovery mode and Download mode. In reovery mode I can format cache, data, sdcard, sd-ext but *not* system. Error Message: "E: format_volume: make_ext4fs failed on /dev/block/st19"
I have tried already several methods according to the forum, e.g.
1) 'install from ZIP' older Cyanogenmod
2) the tool ext4_formatter.zip
3) re-flash with ODIN with several tar-ROMs, all failed. Odin finds the phone (since I start Odin as Admin now), but after I hit 'start' it tries to establish a connection to the phone and ends after a while with 'Failed'
I'm basically lost now, don't know what else to do. Any advise is appreciated (it's my mom's phone, she is getting impatient )
Thx, cheers!
Xala
Hi @xalarsk , So you can't format your /system partition , which is required for installation of your rom ,, you need to try this method from here mate . Follow my instruction from the line @post#4 :"1. Download one of the newest ,,," to the end of the post and please do not use CM9 beta , because it is unstable and will wreak havoc with your system eventually . ( either cm7 or cm11 is the place you should go for CyanogenMod experience for cooperVe device ).
If you fail at any level please give us your logcat ( error massage ) for better support for your Odin process you mentioned .
Cygwin not working
Hi @ehsanotaku,
thank you for your quick reply, it's appreciated!
Unfortunately I couldn't get cygwin to install all necessary packets. The ZIP-test always failed. I have a Linux system running (Linux Mint 17) though, and hope that might help. In the meantime I tried to download the already split packages as described in another of your forum posts, but the website provides only exe-files instead of zip-files. Is there another location to download them?
#UPDATE: It seems there is a SplitFUS2 version for linux somewhere but couldn't find links to download. Anybody can help? I'll also PM Doky73
Cheers, Holger
xalarsk said:
Hi @ehsanotaku,
thank you for your quick reply, it's appreciated!
Unfortunately I couldn't get cygwin to install all necessary packets. The ZIP-test always failed. I have a Linux system running (Linux Mint 17) though, and hope that might help. In the meantime I tried to download the already split packages as described in another of your forum posts, but the website provides only exe-files instead of zip-files. Is there another location to download them?
#UPDATE: It seems there is a SplitFUS2 version for linux somewhere but couldn't find links to download. Anybody can help? I'll also PM Doky73
Cheers, Holger
Click to expand...
Click to collapse
Cygwin was meant for windows platform to get the native Linux environment/command line you already got there . You can create a virtual instance of the windows 7 inside virtualbox or any kind of apps you are preferring such as Vmware/Parallel etc etc to get the job done .
Splitfus2 only supports windows platform as far as i know mate,,, either vitalization as i said or the pre-made zip package ( which is clearly not .exe file ,, push the download now and get yourself a descent downland manager,, tested and zip packaged delivered ) from here is the feasible approach for your problem .
Ok, had all the files ready, just the Boot loader <DefaultCalDataWithBoot_S5830iXXLB1_REV00.tar.rar seems to be broken. I downloaded the link provided in your post #8 several times with several download managers, also uses 7-zip and several online unrar services..result always the same: The archive is broken. Is that possible? Would you mind to check yourself?
xalarsk said:
Ok, had all the files ready, just the Boot loader <DefaultCalDataWithBoot_S5830iXXLB1_REV00.tar.rar seems to be broken. I downloaded the link provided in your post #8 several times with several download managers, also uses 7-zip and several online unrar services..result always the same: The archive is broken. Is that possible? Would you mind to check yourself?
Click to expand...
Click to collapse
Another fellow had similar issue with my attachment that was corrected here @ post#27
Unbricked, SD card not recognized
Update: Phone has been unbricked, many thanks for that!
Currently I have still issues with the external SD card, which also holds the ZIP files. Phone won't recognize it, not even format it properly. Still working on that.
Cheers, Xala
xalarsk said:
Update: Phone has been unbricked, many thanks for that!
Currently I have still issues with the external SD card, which also holds the ZIP files. Phone won't recognize it, not even format it properly. Still working on that.
Cheers, Xala
Click to expand...
Click to collapse
Mostly this happened because of the bug inside CM9 beta you used . Study this topic mate i troubleshooted while ago for a sample of the symptoms external SD card would show after unstable ICS usage .
Also as an alternative to the method i instructed there , you can format/Re-partition your SD card by putting it inside card reader and using app such as free MiniTool Partition Wizard "Gparted" tool for Linux users Or "iPartiton" for Mac users etc etc ,, to get the job done . You can find several tutorials inside XDA for this matter mate.
Phone works with CM7.2, can I upgrade to CM9?
Hi again,
first of all, props to @ehsanotaku, I will hit the 'Thanks' buttons.
Now, this is a bit beyond the topic, but I'd like to ask anyway for recommendations of CM9 roms. The one I picked from a post inside this forum bricked my phone and made me start this thread, I don't want to go down this road again. So I'd be glad for any recommendation of a stable ROM that will put my phone beyond Android 4.0.
Cheers again,
Xala
So i have a similar issue. I used to have CM11 installed, but i figured thats too slow for me. Then i went back to stock rom (XXMJ2) which works fine. But now i have a problem.
Everytime i want to flash a stock based or cm7 based rom on my phone, it gets messed up. Today i wanted to flash this
http://forum.xda-developers.com/galaxy-ace/s5830i-develop/cm-7-2-kitkat-smart-r2-t3075267
i naturally downloaded clockwork mod recovery (5.0.2.6) and tried to flash it. Flashing was done pretty quickly (10 seconds or so) and when i rebooted, i obviously got stuck at sammy logo. Now booting back to the recovery (first e3 then cwm) i got bunch of error about partritions not being able to be mounted (happens the same if i want to manually mout them or format them)...
So, what to do ?
I have a suspicion, that flashing CM11 and the latest cwm recovery for it somehow messed up partritions.
hojnikb said:
So i have a similar issue. I used to have CM11 installed, but i figured thats too slow for me. Then i went back to stock rom (XXMJ2) which works fine. But now i have a problem.
Everytime i want to flash a stock based or cm7 based rom on my phone, it gets messed up. Today i wanted to flash this
http://forum.xda-developers.com/galaxy-ace/s5830i-develop/cm-7-2-kitkat-smart-r2-t3075267
i naturally downloaded clockwork mod recovery (5.0.2.6) and tried to flash it. Flashing was done pretty quickly (10 seconds or so) and when i rebooted, i obviously got stuck at sammy logo. Now booting back to the recovery (first e3 then cwm) i got bunch of error about partritions not being able to be mounted (happens the same if i want to manually mout them or format them)...
So, what to do ?
I have a suspicion, that flashing CM11 and the latest cwm recovery for it somehow messed up partritions.
Click to expand...
Click to collapse
ok not going to excruciating details of symptoms and explaining all of your errors for now just please read my advice @ post2 of this topic and follow the procedures accordingly and finished it with formatter tools and cm7 instructions you will find there ., after that you can install Kitkat Smart R2 like you are coming from another CM7 build instruction . btw some problem regarding super user privileges and play store 492-498 infamous bug was reported for this fairly new development .
[Guide] Samsung Galaxy S2 i9100 Android 7.1 Nougat/Lineage OS 14.1
[Guide/Tutorial/Howto] Samsung Galaxy S2 i9100 Any version to Android 7.1 Nougat without PC
This detailed step-by-step guide helps you transform your Samsung Galaxy S2 i-9100/i-9100P to a powerful one with Android 7.1 Nougat.
Verify your phone is i9100 or i9100P before going further : when you Power on phone, it is written Galaxy SII i9100.
The flashing of recovery is a bit tricky but none of the S2 I had were recognised by the PC. So this tutorial is PC free.
If your S2 is recognised by PC, it's easier to flash directly TWRP recovery using Odin or Heimdall https://forum.xda-developers.com/showpost.php?p=75002977&postcount=343
CHANGELOG OF TUTORIAL
v10. Updated pack with TWRP 3.3.1-0
v9. Updated to Unofficial LOS 14.1
v8. Removed Dorimanx kernel (not maintained)
v7. Added Google Play certification (use instructions with my v5 pack below)
v6. Switched to Dorimanx kernel, swteaks, enhenced tutorial thx to feedback, introduced md5 signatures, Stweaks included
v5. Overclock and optimize
v4. Simpler repit, 2 profiles for repit included
v3.5. More custom partitions, kernel for Android N 1.3
v3. Moved to Lineage OS 14.1, Skyline custom kernel, TWRP 3.1 by the.gangster
v2. Added latest repit, added walkthrough for possible errors
v1. Initial release
1 ) DOWNLOAD ---------------------
- djibe Galaxy S2 i9100 pack (53 MB) v5 : http://bit.ly/GalaxyS2djibepackv5
(contains Philz Touch recovery + kernel Lanchon IsoRec CM13 + the.gangster IsoRec TWRP 3.3.1-0 recovery + lanchon repit djibe edit standard or prefered + Su for LOS 14.1 + Samsung drivers).
- ROM Unofficial Lineage OS 14.1 for GalaxyS2 i9100 : https://androidfilehost.com/?w=files&flid=302540&sort_by=date&sort_dir=DESC
Or AOKP : https://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-aokp-rom-t3606915
- OpenGApps ARM 7.1 pico (alternatives: Pico, Micro) : https://opengapps.org/?arch=arm&api=7.1&variant=pico
- a microSD card. Copy Philz Touch recovery + kernel Lanchon IsoRec CM13 + the.gangster IsoRec TWRP 3.3.1-0 recovery + lanchon repit djibe edit standard or prefered + Su for LOS 14.1 AND THEIR RESPECTIVE md5 files from my pack on microSD card and insert it in phone.
- Charge phone to 100 %
WARNING. Read carefully the sentences starting with ###.
### It will not work if your phone is encrypted. Uncrypt it before starting this tutorial.
### This tutorial works without a PC. So it will work if (like me) you get "Unknown USB device error" message when plugging phone in Windows.
### Warranty is now void.
### Later in this tutorial, if you get error : "Failed to mount */data* (No such device)", just reformat Data partition to Ext4 (Using lanchon-repit's script or TWRP recovery).
2 ) BACKUP DATA -------------------
Install Samsung drivers (you unzipped earlier).
Then plug phone to PC in File transfer mode.
Collect all .jpg or .mp4
Use an app like Backupyourmobile to backup texts, contacts, etc.
Check that backup is located on microSD card.
Then copy the backup on your PC.
3 ) FLASH RECOVERY, KERNEL AND RE-PARTITION----------------
We gonna repartition phone to reduce an unused preload partition of 512 Mo (stored Samsung updates that no more exist).
We gonna increase system partition to 1 GB so Android 7.1 and Gapps have enough space.
We gonna increase data partition so you can have all the apps you like.
ALL YOUR DATA WILL BE LOST.
FLASH RECOVERY FROM STOCK RECOVERY ----
Shut down phone.
Power it back on in recovery mode : Use Volume+ + Home + Power buttons and release them when you see Galaxy S2 logo.
### Alternative and easier process if your S2 can be recognized by PC using Heimdall : https://forum.xda-developers.com/showpost.php?p=75002977&postcount=343
Then wait till the recovery launches.
### If you already have a custom recovery, go to the mark -!-!- below.
Using default recovery, use volume buttons to navigate and power to confirm,
install zip -> choose Philz_touch_6.48*.zip and install it.
When its done, shut down phone, restart in recovery mode. You are now in the Philz touch recovery.
### If it fails, you need to install CWM recovery using Odin software and SGS2 in Download mode.
### Use a good tutorial for Odin and SGS2 i9100 recovery flashing.
### Download CWM for Odin : https://www.androidfilehost.com/?fid=95916177934516900
### Once finished, continue operations below as if you had Philz recovery.
In Philz touch recovery (or your recovery -!-!-) : go to Wipe -> format /cache and format /system partitions.
Then back to install zip -> Flash kernel-lanchon*.zip (FLASH IT OR TWRP RECOVERY WON'T LAUNCH AND PHONE WILL BE BRICKED),
then flash recovery recovery-the.gangster-IsoRec-TWRP-3.1.0-0-i9100.zip.
Reboot phone to recovery again, it is now TWRP 3.1.0-0 Recovery !!!
Swipe to unlock filesystem.
Check never show this screen during boot again and swipe again.
In TWRP, go to Backup -> select Boot, System, Data,
Tap select Storage and select External storage,
then Swipe to Backup.
Backup is located on your microSD in the TWRP folder.
(To have latest TWRP recovery, go to Install > Select TWRP 3.1.1-0.img and swype to flash).
### Don't flash repit files if you don't have a TWRP recovery
### 2 MAIN CONFIGS TO REPARTITION :
- For standard config, just use the djibe-standard-repit*.zip included in my archive, you'll have :
1GB system, 6GB data (for apps), max internal storage (photos, temp files) and minimal preload (useless partition used for OTA offical updates).
- My PREFERED version is djibe-prefered-repit*.zip :
1GB system, 2GB Internal storage (limited size for photos and files because who takes photos with SGS2 ?), max data (about 11,5 GB for apps), minimal preload (useless partition).
### And a failproof repit one. If you get flash errors with repit files above, use this one.
- For more custom partitions, ask us in a post what partition sizes you want.
### Let the lanchon*.zip filename AS IS because the filename gives the instructions for the repit script. Lanchon is smart !
Go back to TWRP Home screen,
Plug phone to charger.
Tap go to Install, select lanchon-VERSIONYOUWANT-djibe-repit*.zip from your microSD (if file not seen, tap Select storage -> External-storage),
then Swipe to flash. There is an error, files have been copied to /tmp folder. It is normal !
Go back to Install -> Select Storage -> Internal Storage, OK.
Now tap on : (Up A Level),
scroll down and enter the "tmp" folder,
### If you use another PIT file to repartition (not mine -djibe-version), plug phone to Power source (not PC !) or you could hard brick your device.
tap on lanchon-VERSIONYOUWANT-djibe*.zip and Swipe to flash.
### never connect phone to PC during repit !!!
Let it process for 2 minutes.
4 ) Wipe partitions
INFO : F2FS is the fastest filesystem for read and write partitions on flash memories. Compared to EXT4, gain is from 15 to 280 %.
No need to format the /System partition because it is Read only and Ext4 is still faster.
Format has been done with repit. No need to manually format anymore.
Go to Wipe -> Advanced wipe,
select Dalvik, Cache, System, Data, Internal Storage then Swipe to Wipe, go back to TWRP Home.
5) INSTALL ROM, GAPPS AND ROOT
Still under TWRP Home screen -> go to Install zip and set Storage to External-Storage.
We need to install files 1 by 1.
Select lineage-14.1-*.zip and Swipe to flash,
Then select addonsu-*.zip (this is the Root) and Swipe to flash,
### You get this error : Updater process ended with signal: 4, Error installing zip file '/sdcard/Download/addonsu*.zip', don't care, root is correctly installed.
then open_gapps-arm-7.1*.zip, and Swipe to flash,
### If you are using ResurrectionRemix, don't flash any custom kernel at all !
Then wipe cache/dalvik,
then reboot system.
Wait for 15 minutes while Android starts for the first time.
6 ) ROOT ACCESS
Once in Android, open the Settings menu, select "About Phone".
Go to Settings -> About -> Hit 7 times on the build number, go back,
Go to the Developer options menu, root access -> activate ADB+apps
and Lower activate Local Terminal.
7) CALIBRATE BATTERY
In Google Play Store, download App Battery Calibration (from IMobS Ltd).
Launch the App.
Confirm root acces.
Plug tab and wait till charge hits 100%, then hit BATTERY CALIBRATION and unplug it.
8) You can use Backupyourmobile to restore data,
you can use GPS Status & Toolbox app to enhance GPS fix.
Enjoy,
djibe
THANKS --------------
Teams of : TWRP, Lineage OS, the.gangster, Lanchon, Resurrection remix, Philz, Skyline, MigoMujahid
Hi, i tried that, the repit file i isntalled was the one that has your name. The whole process went ok, except for the install. please check the image for more info.
I formated cache and data partition back to ext4 and everything went fine. Now I have ressurection remix 7.1 ROM.
hi octaviojss:
- Why did you flash my PIT, cause you got the WARNING. If you got "ERROR: 1 Fatal: file system errors in partition #11 'sdcard' (UMS) could not be fixed error" ?
- What happens if you go back to Wipe -> Advanced Wipe
And reformat every partition (F2FS for cache and data and ext4 for system and internal storage) ?
Keep in touch
Why did you have your PIT file there in first place, if it wasnt needed? I installed it because it was more recent. Anyway, as said, when i reformated the cache and data partitions back to ext4 file format i was able to install the rom smoothly and flawlessly.
Glad you did it !
For the PIT file it doesn't change much, but the original lanchon PIT moves data during partition resize, mine erases data.
Enjoy
I get an error "E: error in /tmp/sideload/package.zip" Please help me fix this
Aly Rezz said:
I get an error "E: error in /tmp/sideload/package.zip" Please help me fix this
Click to expand...
Click to collapse
Hi Aly, at which step are you ?
Did you try reflashing the PITs from the SDcard and moving back to Internal stroage main folder ?
Did you authorize TWRP to mount system partition ?
djibe89 said:
Hi Aly, at which step are you ?
Did you try reflashing the PITs from the SDcard and moving back to Internal stroage main folder ?
Did you authorize TWRP to mount system partition ?
Click to expand...
Click to collapse
I wiped my phone and flashed the Philz Touch Recovery Zip. I got this error while flashing it...
Aly Rezz said:
I wiped my phone and flashed the Philz Touch Recovery Zip. I got this error while flashing it...
Click to expand...
Click to collapse
So you've wiped everything under stock recovery ? It needs to be done later once Philz touch is working !
So, we'll try flashing recovery in Download Mode (Home + Power + Volume-), use Odin to flash Philz Touch recovery in .tar format (in AP/PDA section of Odin).
1 - Download Philz Touch recovery in .tar format :
https://mega.nz/#F!oZ1QDDbC!Ko20UNhowwIlXLVFjJsyKw (it doesn't load for me right now)
+ Odin 3.07 (my pack for i9300) : http://bit.ly/2hqiWsP
2 - From my tutorial here, execute the 3rd chapter with Odin :
https://forum.xda-developers.com/galaxy-s3/help/guide-tutorial-samsung-galaxy-s3-i9300-t3491788
(do not flash TWRP inside my i9300 Archive)
3 - Once flash of Philz touch recovery is done, reboot to recovery and continue further steps.
good to have a full tutorial
Glad it pleases you. Hope your S2 is now fully unleashed
Any constructive comment is welcome to enhence the tutorial.
djibe89 said:
So you've wiped everything under stock recovery ? It needs to be done later once Philz touch is working !
So, we'll try flashing recovery in Download Mode (Home + Power + Volume-), use Odin to flash Philz Touch recovery in .tar format (in AP/PDA section of Odin).
1 - Download Philz Touch recovery in .tar format :
https://mega.nz/#F!oZ1QDDbC!Ko20UNhowwIlXLVFjJsyKw (it doesn't load for me right now)
+ Odin 3.07 (my pack for i9300) : http://bit.ly/2hqiWsP
2 - From my tutorial here, execute the 3rd chapter with Odin :
https://forum.xda-developers.com/galaxy-s3/help/guide-tutorial-samsung-galaxy-s3-i9300-t3491788
(do not flash TWRP inside my i9300 Archive)
3 - Once flash of Philz touch recovery is done, reboot to recovery and continue further steps.
Click to expand...
Click to collapse
Still doesn't work. It's stuck at " Nand Write Start!!"
Try Odin 1.3
or this "Tried to do a rollback from official 4.4.2 to official 4.1.2 via Odin.
Since the new official bootloader doesn't allow rollback procedures, I got the missing magic string error and the NAND write fail at Odin.
The tablet bricked, not even showing Samsung Note 10.1 logo. I could only access to ODIN mode, not recovery even. *YIKES*
After a day and a half trying to recover it, I removed the SIM card, the SD card and I loaded the Samsung Stock recovery file via ODIN, then rebooted. I got as far as the Samsung logo which was an improvement compared to what I had. Then I proceeded to reload the 4.4.2 firmware (INU-N8000XXUDNE6) and rebooted the device. Went into recovery mode, restored factory defailts and, voilá!
It is working now on 4.4.2, though it is not the Spanish firmware it shoud be, at least the tablet is functional. "
Hi.
Oh boy I was happy when I found this complete package with all files in a zip. All other places the files are missing or you "can't find them".
And oh boy I was unhappy when I couldn't install the first file.
My phone is a SGS2 Modelnumber GT-I9100 bought in Sweden a few mounth after the model was released.
So I guess the instructions on this page should work for me?
I've rooted my phone with CWM-SuperSU-v0.97.zip and verified with a root checking app from the store. Otherwise it's only updated to the latest Andorid 4.1.2 from Samsung. The phone is working fine with the installed Android version.
So when I choose to install "Philz_touch_6.48*.zip" the following is printed out:
################
PhilZ Touch Recovery
Full Touch CWM Based
+
Advanced Features
Phone i9100
################
This package is for 'galaxys2.i9100.GT-I9100.GT-
I9100M.GT-I9100P,GT-I9100T,SC-02C devices; this
is a ''.
E:Error in /tmp/sideload/package.zip
(Status 7)
What am I doing wrong here? Have I missed doing something obvious? Do I need to install something more before I use your guide?
BR
Tobbe
Hello,
you are rooted.
So, in Android, what happens if you download the app ROM Manager : https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager ,
grant Root access for the app,
Flash latest ClockworkMod Recovery for i9100,
reboot to recovery, reflash Philz Touch ?
Hi.
I tried to do that you wrote. Didn't seem to work with:
GT-I9100_JB_ClockworkMod-Recovery_6.0.2.9.tar
I downloaded Odin and flashed it instead. Now I got this yellow triangle with an exclamation mark in and phone didn't boot into Android.
Got very worried but I went into recovery mode and voila ClockworkMod was running
After that I followed your instruction. Up to "Format to F2FS". I got errors so I changed back to EXT4 and continued.
Installed CM13 with no problem and got very glad so I forgot step 6-8. Will do them in a few days.
Thank you very much for this guide and zip-archive.
It's actually my daughter who will get the updated phone. She is also very happy
BR
Tobbe
PS. One more thing, is it possible to get rid of the yellow triangle with an exclamation mark in? (only appears at atart up screen) DS.
Glad you did it.
It is strange how bugs can be different for everyone !
Triangle can be removed but it seems rather dangerous for a small benefit : https://forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114
I have no courage to do it after all these tricky steps we wen't by !
See you,
Thanks djibe. I wanted to flash to CM13 from stock rom, so your guide was really helpful.
I did run into two issues, and want to share how I got around them:
1. I got the "Status 7" problem when trying to flash Philz_touch_6.48*.zip. So instead I flashed the relevant ZIP file from "forum.xda-developers.com/galaxy-s2/development-derivatives/philz-cwm6-stock-kernel-cwm6-root-exfat-t1877270" from stock recovery first. This installed a custom recovery. Then I flashed Philz_touch_6.48 from the custom recovery.
2. After formatting /cache and /data to F2FS, installing CM13 failed. So instead I kept /cache and /data as EXT4 and completed the installation according to the rest of the guide. After rebooting and completing the CM13 Android setup, I redid the installation from step 4 of your guide onwards and F2FS worked this time. I should mention though that before formatting /cache and /data to F2FS, I also repartitioned with a newer repit file from lanchon's github (and increased data to 4G), so I don't know if this had an effect as well.
Hopefully this helps others facing the same problems. I should warn though that this is my first time attempting absolutely anything like this, so please take all this with caution. Your mileage may vary!
S2andCounting said:
Thanks djibe. I wanted to flash to CM13 from stock rom, so your guide was really helpful.
I did run into two issues, and want to share how I got around them:
1. I got the "Status 7" problem when trying to flash Philz_touch_6.48*.zip. So instead I flashed the relevant ZIP file from "forum.xda-developers.com/galaxy-s2/development-derivatives/philz-cwm6-stock-kernel-cwm6-root-exfat-t1877270" from stock recovery first. This installed a custom recovery. Then I flashed Philz_touch_6.48 from the custom recovery.
2. After formatting /cache and /data to F2FS, installing CM13 failed. So instead I kept /cache and /data as EXT4 and completed the installation according to the rest of the guide. After rebooting and completing the CM13 Android setup, I redid the installation from step 4 of your guide onwards and F2FS worked this time. I should mention though that before formatting /cache and /data to F2FS, I also repartitioned with a newer repit file from lanchon's github (and increased data to 4G), so I don't know if this had an effect as well.
Hopefully this helps others facing the same problems. I should warn though that this is my first time attempting absolutely anything like this, so please take all this with caution. Your mileage may vary!
Click to expand...
Click to collapse
Thank you very much for these tips that will surely help others.
Can you send me the direct link to the Philz recovery that was successful for you ?
I'm upgrading my tutorial with your stuff, and making it simpler with a new custom repit file.
Keep in touch
Nexus 4 Repartition
No one is responsible for your actions except yourself. Everything written further may potentially brick your device, although risk is reduced to minimum.
This repartition package offers 1.5G /system; a /vendor partition and it is fully backward compatible with any ROM (including stock system.img).
Known-issues
HTML:
- If repartition pack says that device isn't correct,
than, if partition table wasn't modified before,
congrats! your device has different memory chip
that those I worked with. No worry, PM me and
I'll add support for it.
DO THE BACKUPs. Repartition will erase all your data
USB connection to PC is MANDATORY else you will not have opportunity to push ROM to your device
Installation
HTML:
# Before processing further we highly recommend you to use our TWRP which has support of EFS/Persist backup
# Or you might lose your IMEI/WIFI + BT mac addresses
# This mod is backwards compatible with any ROM so we highly recommend NOT to reverse it if repartition went well.
# You should use ONLY recovery from this thread since other don't support all benefits of this mod.
# When installing ROM just after you flashed zip and before installing GAPPs you MUST make a resize in TWRP since all roms are build for ~800M system.
# To restore stock layout use same zip and steps as for repartition.
1. Boot into recovery (You need to allow system partition modification to be able resize /system in recovery).
2. Backup your data & Move your files from flash to your PC.
3. Flash repartition pack zip.
4. Do the actions asked by repartition pack (go to Terminal in ordinary recovery and input word that pack will tell you. Everything else will be done automatically).
5. Phone will reboot into recovery.
6. Install TWRP from below (it is build with support of new partitions layout and sizes. It can be differed from official TWRP by next format 3.x.x-1 UA).
7. Format everything. (mount errors will not affect formatting!)
- In TWRP: Wipe > Format data
- Type yes
- Once this completes go to: Wipe > Advanced Wipe
- Tick all the boxes and wipe. There should be no further mount errors.
8. Install ROM which you like.
9. Enjoy better flash partition layout.
If something gone wrong - we recommend you using this guide to restore your phone back
Downloads:
Repartitioning package: GitHub
Credits:
Special thanks to
- Unlegacy-Android team;
- Sudokamikaze;
- ddaggebi for 8GB model layout;
- surfrock66 for his gide for Nexus 5;
As usual, feedback is appreciated
XDA:DevDB Information
Nexus 4 Repartition, Tool/Utility for the Google Nexus 4
Contributors
Clamor, sudokamikaze
Source Code: https://github.com/clamor95/android_device_unlegacy_recovery
Version Information
Status: Stable
Created 2018-09-19
Last Updated 2019-01-18
Common issues and F. A. Q.
Repartition pack should be safe for most devices. Common mistakes, issues and their solution will be published here.
1. You shouldn't flash any internal parts of repartition pack (*.sh files) only flash whole zip using TWRP. You may use my scripts for personal use or projects but authorship should to be kept.
2. If something isn't mounting after repartition try to format partitions that don't mount using Wipe -> Advanced Wipe in TWPR. Ideally you should format in that way all partitions in Advanced Wipe menu (see 5-th step of installation guide).
3. To be sure that repartition went well I enclose loging zip. Flash it after repartition (when device reboots into TWRP). It won't modify anything only generates a partition.log in root of internal storage and outputs your current partition layout to screen. You shoud check if your layout is same as those fragments I provide under spoiler (file systems doesn't matter). If there are any differences you have to discribe what you did and enclose partition.log to your post.
MAKO STOCK
Code:
21 159383552B 1040187391B 880803840B system
22 1040187392B 1627389951B 587202560B cache
MAKO MODIFIED
Code:
21 159383552B 1732247551B 1572864000B system
22 1732247552B 1994391551B 262144000B vendor
23 1994391552B 2099249151B 104857600B cache
4. If you have touchscreen problems use common instructions till you reach entering word. Than plug your phone to PC while you remain in recovery. Enter adb shell from cmd (if you don't know how - google) and enter word that repartition pack asked. Than your phone will reboot automatically into your old TWRP but with new partition layout.
5. Flashable resize zip for ROMs that support addon.d (automatic resize when dirty flashing updates).
actually the lower left corner of my phone screen doesnt work so can you please elaborate what kind of commands are we used to use and terminal and is there any other way to access terminal
mine q,a,z,1 these key are inaccessible in twrp as screen rotation is not supported
bgoel4132 said:
actually the lower left corner of my phone screen doesnt work so can you please elaborate what kind of commands are we used to use and terminal and is there any other way to access terminal
mine q,a,z,1 these key are inaccessible in twrp as screen rotation is not supported
Click to expand...
Click to collapse
Plug your phone to PC while you remain in recovery. Enter adb shell from cmd (if you don't know how - google) and enter word that repartition pack asked. Than your phone will reboot automatically into your old TWRP but with new partition layout.
What can I do to add support for 8GB models? Can I send you some partition tables that you can tinker with? Or sth else? Anyway, huge thanks for your dedication for this device!
ddaggebi said:
What can I do to add support for 8GB models? Can I send you some partition tables that you can tinker with? Or sth else? Anyway, huge thanks for your dedication for this device!
Click to expand...
Click to collapse
PM me, I need a partition table and I'd ask you to test if you have 8GB model.
Something went wrong and now I have only 552mb space. When I try to flash again it says it's not a Nexus 4.
Can anyone help please?
cyberon said:
Something went wrong and now I have only 552mb space. When I try to flash again it says it's not a Nexus 4.
Can anyone help please?
Click to expand...
Click to collapse
Sure. In PM.
OK so my nexus 4 can't transfer files to or from PC at all so if I do this and have the ROM downloaded it will wipe the ROM and the ROM would be gone and my phone would be a nice brick because I can't transfer any files to my PC like it charges with the PC but data transfer doesn't work so again would I be screwed?
@Nathan4923 correct. Usb connection and PC are mandatory
For those who downloaded repartition pack before this message is published, please redownload pack since previous version might have a problems with repartition. If repartition was already made, don't worry everything should be fine. Just use up-to-date pack.
can i return back to old partition if i want to? i hope someone would post a video tut for this one
@jluspo you can with same zip and same steps as for repartition. You didn't read first post carefully.
Clamor said:
@jluspo you can with save zip and same steps as for repartition. You didn't read first post carefully.
Click to expand...
Click to collapse
im using xda appits different layout on browser
I'm I doing it right? I still can't flash gapps
failed to mount Vendor, any suggestions ?
@jluspo resize /system with TWRP after ROM install before GAPPs because ROMs are designed to use ~800MB system.
@cqloveqc you had to format all partitions available in advanced wipe after repartition.
Clamor said:
@jluspo resize /system with TWRP after ROM install before GAPPs because ROMs are desined to use ~800MB system.
@cqloveqc you had to format all partitions available in advanced wipe after repartition.
Click to expand...
Click to collapse
Thanks for the help !
I've found that even with that error, i still succed the process
Hello ho can I do ,,resize /system with TWRP after ROM,,??? I can't find how to do that...
I installed your TWRP > backup > repartition zip > format all partitions > ROM
And now I'm stuck because I can't flash GAPPS...
Mato_xXx said:
Hello ho can I do ,,resize /system with TWRP after ROM,,??? I can't find how to do that...
I installed your TWRP > backup > repartition zip > format all partitions > ROM
And now I'm stuck because I can't flash GAPPS...
Click to expand...
Click to collapse
just read the OP carefully it already mentioned that you had to resize system after installing rom
you can do that by going to advanced wipe in twrp