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 .
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
I am currently on 4.1.2 10-20121209-UNOFFICAL-acclaim ROM
I want to move to CM 11.
My current recovery is CWM - Recovery v6.0.1.9
ON all CM 11 page , it says to update my recovery to new one through fastboot.
I am not sure how to do this on nook tablet. Can anyone help me ?
Also does repartitioning of 16Gb needs to done with each rom install or once done , it stays the same through out ?
naveen_reloaded said:
I am currently on 4.1.2 10-20121209-UNOFFICAL-acclaim ROM
I want to move to CM 11.
My current recovery is CWM - Recovery v6.0.1.9
ON all CM 11 page , it says to update my recovery to new one through fastboot.
I am not sure how to do this on nook tablet. Can anyone help me ?
Also does repartitioning of 16Gb needs to done with each rom install or once done , it stays the same through out ?
Click to expand...
Click to collapse
Hi, repartitioning doesnt need to be done with a new rom install.
IF THIS IS A CLEAN INSTALL
you dont HAVE to install it through flashing a new recovery using fastboot
you just need a working newer CWM , or a working TWRP that you can boot
if you can boot to an older Clockwordmod recovery in any form, you can flash a newer version of CWM to the internal by using a zip file , this user has a couple of the newest ones hosted here:
newbtrigger69 said:
https://www.mediafire.com/folder/3j4kxa3bwkrs1/CLOCKWORKMODS <--------------------------------------------- my compilation of a few important CWM versions in case u dont like twrp (like me).
Click to expand...
Click to collapse
after you flash the new recovery, remove the SDcard, power completely down,
press and hold the "N" NOOK button, and hold the power button for just a second or 2 after you see the tablet boot, and you should be prompted for the new recovery that you just flashed.
---
the newer recoveries have an option on the boot menu to start fastboot. So, if you really wanted to follow the instructions to the letter, get or make a working sd card of a newer CWM recovery, boot to it, then as long as your adb/utilities folder on your PC has fastboot in it, you can fastboot the recovery-0.2.img as is in the cm11 thread.
I found I never had to use fastboot before this cm11 install , so I didnt even have the fastboot on my pc side and had to hunt it down.
my first several installs of CM11 were done using an older boot sdcard that had TWRP recovery on it and it works fine.
----
it will probably be a lot easier it you have a working tablet, to have the copied the zips for cm11 and the gapps you want to install to the tablets
internal memory first, before flashing the new recovery internally
---------- (I completely forgot this other possibility, I'm always just doing clean installs)
IF YOU WANT CM to automatically upgrade though the CM updater process on a running CM10
then , yes you need the newer recovery, and it probably is best if it is the recovery-0.2.img the developer posted in the CM11 thread.
I've never tried it so I dont know how well it migrates your "stuff" from CM10 to CM11
theres a lot of changes to the way storage is mounted in CM11 , and the CM updating process is an important thing they are trying to make as seamless as possible.
If theres stuff on the tablet you really need, I'd save it first before doing any kind of major upgrade like this.
Thanks. I might do a clean install itself. I dont have much stuff.
Actually i am moving to CM 11 in hope that it would be faster. Currently i cant rad the PDF on thios tablet. The scrolling is very stuttery.. gives me headache. If that too doesnt solve that issue , i might simply sell this one and get some nexus tablet.
I just need a tablet to read my study books.
naveen_reloaded said:
Thanks. I might do a clean install itself. I dont have much stuff.
Actually i am moving to CM 11 in hope that it would be faster. Currently i cant rad the PDF on thios tablet. The scrolling is very stuttery.. gives me headache. If that too doesnt solve that issue , i might simply sell this one and get some nexus tablet.
I just need a tablet to read my study books.
Click to expand...
Click to collapse
the latest nightlies of CM11 on a 16GB tablet (has 1GB RAM) are fantastic. best thing ever, especially if you replace the kernel with one that user:demetris has supplied.
I havent run the CM11 on an 8GB (512MB RAM) tablet yet, but it really is a good package.
Its kinda like when Windows 7 came out, its what should have been released instead of XP or Windows 98, its really, really good.
Just tell me .. is flashing recovery via fastboot is same for all devices or for nook tablet its different. Also i need a SD card to do this ?
Can you help me how to flash recovery via fastboot for our nook tablet ?
naveen_reloaded said:
Just tell me .. is flashing recovery via fastboot is same for all devices or for nook tablet its different. Also i need a SD card to do this ?
Can you help me how to flash recovery via fastboot for our nook tablet ?
Click to expand...
Click to collapse
hmmm...
Ive seen fastboot on other devices, Kindle Fires, which I think have a motherboard thats a close match to the NOOK tablet.
on the Kindle, you can force fastboot by using a special cable.
if you need fastboot on the NOOK, the recovery program that you execute at boot has to have the option to start fastboot.
you can boot a recovery that has that option from an internal recovery (CWM newer versions have it, I dont remember about older versions)
or you can boot from an SD card you make that boots a CWM recovery
in any scenario, for fastboot to work, you need a working ADB setup and the fastboot program on your PC
------
you can completely install CM11 without replacing the internal recovery partition of your NOOK which is what that fastboot instruction is trying to get you to do.
the special internal recovery, as I understand it, is only for compatability with the automated CM updating process.
you can boot from an SD card that has CWM 6.0.4.x , or TWRP , and as long as the CM 11 nightly is on the SDcard too, or in the NOOK internal memory, you can flash it.
I am more confused
can you take me step by step or link me to a relevant thread ?
I am sorry if i am taking your time ..
naveen_reloaded said:
I am more confused
can you take me step by step or link me to a relevant thread ?
I am sorry if i am taking your time ..
Click to expand...
Click to collapse
--------- assuming you want to update your NOOK's INTERNAL software, and not run CM11 from an SDcard
I apologize had wrong file linked first post
this zip file should be flashable through your current CWM (6MB)
http://www.mediafire.com/download/0f5fjkjvxp1hga0/flashable_CWM_6.0.4.5(2).zip
http://forum.xda-developers.com/showpost.php?p=48855275&postcount=2
it should update your internal recovery to cwm 6.0.4.5
then you should be able to flash the CM11 nightly and gapps without error
--------------------------
a different (I think slightly more dangerous) way to load the newer recovey to your internal was posted here:
http://forum.xda-developers.com/showpost.php?p=48317620&postcount=15
get the newest recovery image file -
File: http://goo.im/devs/chrmhoffmann/cm-11.0/acclaim/recovery-0.2.img
md5sum: e2a87c433171b3d97d852d27aea1ff49
-------
You can install it from a terminal emulator, if you want to.
1. Download the cwm-recovery.img file referenced in the first post of the thread.
2. Copy this file to the internal memory of your Nook Tablet. Rename this file to cwm.img.
3. On your Nook Tablet, launch Android Terminal Emulator (ATE).
4. In ATE, type in 'su' [ENTER]. Grant it access when prompted.
5. In ATE, type in 'cd /emmc' [ENTER]. This will change your file system current directory to /emmc, which corresponds to the internal storage drive.
6. In ATE, type in 'ls' [ENTER]. This will list the contents of the /emmc directory. You should see the cwm.img file you copied over and renamed earlier (step 2).
7. In ATE, type in 'dd if=/emmc/cwm.img of=/dev/block/mmcblk0p3' [ENTER]. This will write the contents of the cwm.img file to partition 3 of device mmcblk0 (internal memory).
You should now be able to reboot and use cwm. CAREFUL, as you could brick your device if you get step 7 wrong.
nvm
@mikeataol
It worked perfectly. Just flashed it and it udpated to lastest CWM.
Installed CM 11 and got GApps and installed them too. Now downloading some PDF apps to see if they work smoothly and no stuttering is there.
In CM 11 , there is no option for "reboot to recovery" , why so ? I had to use cnyaboot option to enter into recovery.
naveen_reloaded said:
@mikeataol
It worked perfectly. Just flashed it and it udpated to lastest CWM.
Installed CM 11 and got GApps and installed them too. Now downloading some PDF apps to see if they work smoothly and no stuttering is there.
In CM 11 , there is no option for "reboot to recovery" , why so ? I had to use cnyaboot option to enter into recovery.
Click to expand...
Click to collapse
Great!
re: reboot recovery
you have to unlock developer options first by going into
Settings/ About Tablet / Build Number
and tapping the "build number" field 7 times.
then you see a new settings group "developer options",
and in there is advanced reboot and other things.
---------- Post added at 04:24 AM ---------- Previous post was at 04:21 AM ----------
are you on an 8GB / 512 MB ram, or a 16GB 1GB RAM Nook tablet?
Lol , just found that reboot to recovery , came here to say i found , you already replied.
Installing bexus kernel.
Thanks a lot for your help.
One thing though. The scroll stuttering issue is there . Its as if the screen refresh rate or frames per second is not upto the mark , scrolling is very stuttering.
Is there any way to increase or solve this issue ? Please
this is killing the whole tablet and the purpose i want to use this tablet .. ie to read books.
I use 16Gb/1GB tablet
ok ran into issue
After flashing gapps and installing kernel , i am stuck with andoid.phone stopped working error as soon as the tablet boots.
What is the gapps to be used for CM 11 on tablet and is bexus interfering with the gapps ?
how to enable multi touch ?
Also i think there is a serious problem with the screen/display. There is considerable lag and its not smooth scrolling. Its very stuttery...
naveen_reloaded said:
how to enable multi touch ?
Also i think there is a serious problem with the screen/display. There is considerable lag and its not smooth scrolling. Its very stuttery...
Click to expand...
Click to collapse
I would not enable the multi touch, thats just asking for even more trouble.
I think you should consider a total re wipe , and start over
on a 16GB Nook Tablet, the nightly just by itself should run fine
i just downloaded and opened a 71mb pdf file with no issues whatsoever
opens in Adobe reader just fine, scrolling and zooming and searching is perfectly acceptable, nothing I would describe as a stutter
----
if you HAD enabled the multi touch while you were on CM10, I'd consider reflashing the stock LCD firmware before you put CM11 back on it
yeah flashed thrice and i have witheld flashing bexus kernel for time being.
Stutter in the way , the refresh rate is not upto the mark
To best see this issue , dont swipe a text/pdf fast , do it slowly then you will see the jerkiness and also a lag between your swiping and actual screen change.
LCD firmware ? where to get it ?
naveen_reloaded said:
yeah flashed thrice and i have witheld flashing bexus kernel for time being.
Stutter in the way , the refresh rate is not upto the mark
To best see this issue , dont swipe a text/pdf fast , do it slowly then you will see the jerkiness and also a lag between your swiping and actual screen change.
LCD firmware ? where to get it ?
Click to expand...
Click to collapse
to me, seeing a white page while adobe pdf loads the next buffer of pages several pagesahead is normal
I dont see anything abnormal while swiping slowly
re: LCD firmware
if you were on CM10, and fashed the 10 point LCD firmware, then I think you would need to rebuild the unit back to CM10, and reflash the stock LCD firmware.
I dont know how to explain , but look carefully when scrolling (slowly) , you will see tests stuttering as its been scrolled .
I am on CM 11 , do you want me to go to CM 10 ? and flash that firmware?
https://play.google.com/store/apps/details?id=com.aatt.fpsm&hl=en
Used this app and saw that fps varies and it varies like from 7 - 50 during reading pdf.
On slow scrolling of pdf , it only shows 11 or so fps , which is why i think shows the stuttering effect
Used the same app on my GS3 to see the difference and it holds its FPS at 60+ and not dropping below 50.
I think if i can make this tablet to render everything at 30+ fps i might not feel this stuttering effect.
Which PDF reader are you using?
I don't have any stuttering issue on the Mantano Reader.
Hi all,
After spending many hours trawling the internet, and especially this forum I still am having problems getting ANY custom rom I've tried booting on this phone
I know it's old, but it's just a phone I had lying around and want to use it as a small tablet for my 6yo daughter.
I can flash any "stock" rom I've found with odin, but when flashing using an install from an SD card through CWM, it just hangs on the Samsung bootscreen.
CWM installs as the default recovery console, so something is going on the phone, but it won't boot to android.
Oh I'm also using a 5830I rom, but my research has shown this is basically the same phone?
I've used CM7 and tried lots of other custom roms with the same outcome - please can anyone help!?
My daughter is dying to use her new games machine, but the stock rom is sooooo laggy and slow it's no good at all!
Thanks in advance.
@macsbig, "About device" information from settings of your device please < home+power button for screenshots > or kindly state the full details here.
Your original CSC/PDA/MODEM parts of your device <Dial *#1234# >
Your Region /Country/ carrier you are staying please.
Thanks for the reply ehsanotaku!
PDA : S5830iXXLA4
PHONE : S5830iXXLA2
CSC : S5830iOXXLA2
I'm in the uk. This is not the original rom (that got stuck in a bootlock) and the only way to get the 'phone working again was to flash with a stock rom from the internet.
The original rom was from "Three".
During my various attempts at flashing a rom I have ticked the "re-partition" box and tried both "cooperve_0623.pit" and totoro_0623.pit
I've flashed my P5110 tablet, and a Galaxy S1 for my son with no problems - odd!
@macsbig, How come you are ended up with outdated ( 2012 ) s5830i in the first place ? Any particular problems with your s5839i original firmware ( do you know your original CSC/PDA/MODEM parts ) ? Are you absolutely sure this is not re-branded version ( "About Device" info of the original phone would be nice to see though ) Did you take any Nandroid back up of all of the original partitions of your s5839i through temporary CWM zip file ( files will be stored inside your Clockworkmod directory inside the root of the SD card )
Do you still have access to Recovery stock e3 console and Download mode ?
Another important subject in need of clarification are ".pit" files ( partition table info ) and Re-partition option. Playing around with wrong .pit file such as totoro and incorrect usage of Re-partition will lead into hard bricking of your device .
Since you already did modify partition table couple of time partially without success , I would suggest the following process :
1. Download one of the newest non wipe xxx.tar.md5 s5830i firmware from here < It is free, but registration is required > Probably 2013 xxMD1 is the right one for our experiment.
2. Make your wipe flash able zip package through splitfus2 tutorial provided here, my comment @ post 9 or simply you may use European/Russian pre-made package from here , your choice though ( I would advise the first method , but the latter also will work ) .
3.Get the following files:
3.1 - Odin3.v3.07.Cooperve.exe from either places would be fine : 1 , or any sticky post in general/development section will do ( correct cooperVe .pit file will be resided inside the package )
3.2- Get the Temp-CWM 5.0.2.6 or 5.0.2.8 zip file from here or here < put the zip file inside the root of your SD card for flashing later >
3.3- Boot loader <DefaultCalDataWithBoot_S5830iXXLB1_REV00.tar.rar from post#27 , my attachment .
3.4 - SLIM_CM7.2_Cooperve #4 Rom < put it inside the root of SD card >
3.5- This kernel is also goes into Root of SD card for later usage .
3.6- EXT4 Formatter Tool , into the root of SD card again.
4- Now , if you don't have proper drivers installed inside your Windows PC , you can get then form here .
Ok, assuming you have at least access to Download mode , provided the combo keys work (pressing Vol(+) + Vol(-) + Power Keys) Go there according to manual :
-Power off your Phone.
-Get into "Download mode" by pressing Vol(+) + Vol(-) + Power Keys.
-press volume up
-Open Odin3.v3.07.Cooperve.exe
-Connect your phone to PC via USB cable.
-Make sure that your phone is detected in "ID:COM" area.
- Put your wipe PDA/CSC/MODEM/ boot loader/pit files into their proper places , Re-partition is ticked , Factory reset and reboot selected by default >> push the START !
- DO NOT disconnected nor disturb the flashing Nand process , until the process being terminated . Now you must be out of boot loop .
For completing our partition conversion and also put some cm7.2 custom Rom into the test at the same time , do the following :
- Boot into stock e3 recovery >> wipe data and flash your Temp CWM
- CWM > wipe data > wipe cache > wipe Dalvik cache
- Flash the EXT4 Formatter tool, so whole system will be converted to EXT4. (Stock filesystem is RFS).
- Flash kernel_CM7_v4.0_cooperVe .
- When the Kernel is installed, go to the advanced menu --> "reboot recovery" (this will reboot the device, thus you will be directed into your new CWM built-in, which is implanted inside Kernel ).
- Wipe data, cache and Dalvik
- Go to "mounts and storage", and make sure /system partition is mounted (will show -unmounted ; it is like ON/OFF switch)
- Main menu > "Install zip from SD Card" > choose "zip from SD card" and install the ROM, you have already got inside your SD <SLIM_CM7.2_Cooperve #4>
- Reboot
waiting for some good news ............
It's a long story, but here goes!
I had a couple of old phones we no longer use hanging around the house, so I thought it would be good to let my (young) children use them as simple games playing deivices. It doesn't matter too much if the phone is dropped and damaged etc, as I probrably wont use them for anything else as we have new phones.
Within a couple of days - and I'm not sure what happened, my daughters phone was stuck in a boot loop (samsung and "Three" logos repeatedly). Having no experiance of "unbricking" phones I immediately reached for google, and set out on my quest to sort out her phone for her (as we had lots, and lots of tears over her new toy!). The phone has no sim card in and is on wifi for installs etc.
After searching I found a rom that would load on and make the phone good again, this one: S5839iXXLK2_S5839iH3GLC2_S5839iNELK1_HOME.tar.md5
This worked ok, but was very laggy, and irritated me imensely as I was sorting games etc for her, so I decided to to instal a custom rom. After 3 roms refused to load (just stuck on the "Samaung GALAXY Ace GT-S5839i boot screen) I decided to try flashing it to 5380i firmware and Pit file - as nearly all custom roms for the ace seem to be for the 5830i variant - I wondered if this would sort my problem!
It didn't! But now it has become a challenge, and a chance to learn something of Android and how it works - as I said in my last post I have successfully flashed an I9000 with carbon and my P5110 with CM11, I learnt how to do this by what I've learnt from reaserching about this phone, so it has been a worthwhile excercise!
But back to the point. No I don't have any back-ups of the original phone, I neither had the knowlege, or know how of having or needing to do this - it's only now I'm finding my phones/tablets so facinanting!!
Yes I am now back to the stock (e3) recovery, which I can get into.
Many thanks for your help so far - I will try your ideas and repeort back!
@macsbig, Yes do that please and after resolving your initial problems , here is a confirmed list of the games compatible with your GPU/CPU of your child's legacy device . Also you can use chainfire 3d only under stock firmware/rooted phone for the games required plugin(s) and app being activate for proper almost lag free experience . You may read theses links as well for some insight : 1 , 2 .
The ext4 formatter link doesnt work my friend
macsbig said:
The ext4 formatter link doesnt work my friend
Click to expand...
Click to collapse
Just cross-linking it ( wasn't my links to begin though ^:^ )
Attached the flash able zip file to the post body .
I will try you solution(s) later. Working late today! But wow this seems quite complicated! ! Hehe.
Sent from my GT-I9300 using XDA Free mobile app
macsbig said:
I will try you solution(s) later. Working late today! But wow this seems quite complicated! ! Hehe.
Click to expand...
Click to collapse
Well , researching a new area of knowledge ( in this case customization/rooting/bricking/moding and many more technical things inside XDA) can be a bit overwhelming.I do agree with you that the sheer wealth of material means that it can be overwhelming, but more you read and spend time @ XDA, more you will get the hang of the material presented here .
Nevertheless we are here to share/help all of the possible/working solution mate. Just ask anything you can not understand very well . I will try to depict even more detailed walk-through guidelines.
Regards
Right, I now have a custom rom on the 5839i!
I didn't have too much time last night, so what I did was flashed the phone with Odin, using the bootloader and pit file you specified. I then rebooted into the stock revovery, wiped the Data, Cache and Delvic partitions, then booted into CMW 5.0.2.6 and flashed the EXT4 Formatter tool. I then installed the kernel you specified
After that I rebooted into the CMW recovery from the new kernel and followed your instructions - and Voila! It booted into the slim rom you linked me too
Just to test it wasn't a fluke, I then installed CM9, and that went on fine too - with just the normal steps.
I now have to decide after your other advice, whether I go for a stock rom, and try and get rid of the lag, use chainfire 3D etc or go for a custom mod!
Is there a similar app for modded roms's like chainfire 3D to help game perfomance on this limited hardware? I'd really prefer to use a modded rom and build up from there, but as I stated earlier in the post, this will be used only for games and listening to music from youtube, so i'll maybe have to research some more to find out what would work the best.
Many, many thanks for your help, I've learnt alot during this project!!
Oh as a bit of an aside, got a bit worried when downloading some of the links, some of the "download managers" were causing my anti-virus and anti-malware software to give me warnings!
Thanks again
@macsbig, Glad everything worked out for you mate . To address your concerns I must say that I did not come across any working solution for accelerating your GPU with reduction [email protected] custom Roms unfortunately ( only works on stock fw/rooted device) .
For CM9 beta Rom available @ development sub forum , this is an unstable Rom with some serious problems , because of ICS bugs an other things( Read this troubleshooting session and links provided there ).
For malware's concerns they are mostly false positives . Even virus total wold miss lead you in many cases, due to nature of advertising agent implanted inside some of the app inside system directory of custom Roms . You can simply replace the app in question with another one free of adverts. However they are harmless mostly. Please read this discussion (post #472-475) (post#291-298) between me and moderators team for more information about advertisement policies. Basically we have a very good control over materials presented here , thanks to mod teams .
Hope I did help you with your quest
My apologies, when I said that I was getting anti-virus/malware warnings, that was aimed at when I was trying to download the files on "mediafire(?)" and such like. They want you to install a stupid downloader etc., which then installs some crap on your pc.
Had it when downloading splitfus2 if I recall correctly (it was late 12am!).
That's why in the end I decided to use a pre - split (is that what you mean by wiped?) rom in the end.
I'm gonna have a play with the 'phone again later when I finish work.
Years ago, I installed CyanogenMod onto an old Samsung phone with no trouble. A few weeks back, I was given a Barnes & Noble Nook Tablet 16 GB. The UI is pretty limited and I don't want a B&N account, so I thought I'd unleash the beast and install the full Android OS on it.
I read through various HOWTOs including "Install CM for acclaim" from the CyanogenMod Wiki.
I have formatted an 8 GB SD-card with a single FAT32 partition which has been flagged as bootable.
I downloaded and extracted CWM-based-Recovery v5.5.0.4 to the SD-card.
The device booted to recovery mode OK.
I first tried to install "cm-13.0-20160629-NIGHTLY-acclaim".
It failed with the well known OTA update / Status 7 error.
Reading up on this, the main advice is to try an earlier version, maybe even the last stable release.
I then tried "cm-10.2.1-acclaim" which is from all the way back in 2014.
It failed with just "E: Error in /sdcard/cm-10.2.1-acclaim Status 0.
A web search didn't return anything useful.
Next up, I tried the next release CM11: "cm-11-20140210-SNAPSHOT-M3-acclaim".
I got the same failure as with CM10.
Finally I tired the last snapshot before the latest nightly releases: "cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NI-acclaim"
This time it is back to the Status 7 failure.
Considering all the successful HOWTOs I have read and the procedure is basically the same in each one and I have tried searching these forums.
I can only assume I am missing something really basic.
I checked on whether I need to root the device, as I had to with the old Samsung phone, but it seems the B&N Nook Tablet has root access by default.
So, can someone please help?
Thanks!
alloydog said:
Years ago, I installed CyanogenMod onto an old Samsung phone with no trouble. A few weeks back, I was given a Barnes & Noble Nook Tablet 16 GB. The UI is pretty limited and I don't want a B&N account, so I thought I'd unleash the beast and install the full Android OS on it.
I read through various HOWTOs including "Install CM for acclaim" from the CyanogenMod Wiki.
I have formatted an 8 GB SD-card with a single FAT32 partition which has been flagged as bootable.
I downloaded and extracted CWM-based-Recovery v5.5.0.4 to the SD-card.
The device booted to recovery mode OK.
I first tried to install "cm-13.0-20160629-NIGHTLY-acclaim".
It failed with the well known OTA update / Status 7 error.
Reading up on this, the main advice is to try an earlier version, maybe even the last stable release.
I then tried "cm-10.2.1-acclaim" which is from all the way back in 2014.
It failed with just "E: Error in /sdcard/cm-10.2.1-acclaim Status 0.
A web search didn't return anything useful.
Next up, I tried the next release CM11: "cm-11-20140210-SNAPSHOT-M3-acclaim".
I got the same failure as with CM10.
Finally I tired the last snapshot before the latest nightly releases: "cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NI-acclaim"
This time it is back to the Status 7 failure.
Considering all the successful HOWTOs I have read and the procedure is basically the same in each one and I have tried searching these forums.
I can only assume I am missing something really basic.
I checked on whether I need to root the device, as I had to with the old Samsung phone, but it seems the B&N Nook Tablet has root access by default.
So, can someone please help?
Thanks!
Click to expand...
Click to collapse
The CWM version you are trying to use is too old, I think, even for CM 10.2
Thanks, I thought it might be something like that, but one tutorial said it didn't matter. I have been trying to find a newer version of ClockworkMod, but can only find image (img) files that don't seem to work: I used the gnome-disk-utility 3.10.0, UDisks 2.1.3 to write the image (recovery.img extracted from flashable_CWM_6.0.4.8_chrmhoffmann.zip), but it just makes an empty SD-card - that is, when I check the card with GParted, there are no usable partitions.
I have just found "cm-13.0-20160629-NIGHTLY-acclaim-recovery.img" but I cannot find any clear instructions what to do with it next.
Do I just write the image to the SD-card with the image writer? Because then I get a warning that the target disk is over7 GB bigger than the image and end up with an empty SD-card.
alloydog said:
Thanks, I thought it might be something like that, but one tutorial said it didn't matter. I have been trying to find a newer version of ClockworkMod, but can only find image (img) files that don't seem to work: I used the gnome-disk-utility 3.10.0, UDisks 2.1.3 to write the image (recovery.img extracted from flashable_CWM_6.0.4.8_chrmhoffmann.zip), but it just makes an empty SD-card - that is, when I check the card with GParted, there are no usable partitions.
I have just found "cm-13.0-20160629-NIGHTLY-acclaim-recovery.img" but I cannot find any clear instructions what to do with it next.
Do I just write the image to the SD-card with the image writer? Because then I get a warning that the target disk is over7 GB bigger than the image and end up with an empty SD-card.
Click to expand...
Click to collapse
I can't speak to the CM 13 since I haven't gone there (yet). I followed the excellent instructions by @digixmax for CM 10.2 and (more recently) CM 12.1. In some cases there is no working CWM version and you have to use a version of TWRP. Late in the second thread there are a variety of file combinations people found that worked for them. But the instructions--if followed exactly--work, or at least they did for me.
TWRP worked perfectly for me. However I had to flash CM10.2 before I could go higher, otherwise trying to flash CM13 made TWRP reboot outright with no warnings while on stock. I'm sure since it was on Android 2.3 it needed to have the newer partition table to install to.
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)