Hi,
I'm using a galaxy s2 gt-i9100 as a spare phone and i thought it would be a good idea to upgrade from CM13.1 to lineage os 14...
Unfortunately that didn"t go well, the phone is not bricked BUT :
1)i can only flash recovery using odin, heimdall says flash ok but recovery never changes, same as when i tried to install the TWRP recovery from a zip file in the CWM 6.0.2.9 recovery
2) flashing from that CWM version a lineage os zip file always resulted in the progress bar to be stuck at the very begining of the process so i updated the phone with a 3GB PIT file to fix the issue.
3) now the same CWM doesn"t want to mount the SD card while it's working perfectly from within the phone or with the phone(using latest stock firmware) on my PC
4) i can"t use that CWM as recovery because i can't use adb sideload or install zip from a file anymore(i guess due to the 3GB PIT file)
So is it possible to have a TWRP recovery flashable with odin for the GT-I9100 ?
Will that TWRP recovery finally allow me to flash the lineage os zip file?
thanks,
NHJ1981 said:
Hi,
I'm using a galaxy s2 gt-i9100 as a spare phone and i thought it would be a good idea to upgrade from CM13.1 to lineage os 14...
Unfortunately that didn"t go well, the phone is not bricked BUT :
1)i can only flash recovery using odin, heimdall says flash ok but recovery never changes, same as when i tried to install the TWRP recovery from a zip file in the CWM 6.0.2.9 recovery
2) flashing from that CWM version a lineage os zip file always resulted in the progress bar to be stuck at the very begining of the process so i updated the phone with a 3GB PIT file to fix the issue.
3) now the same CWM doesn"t want to mount the SD card while it's working perfectly from within the phone or with the phone(using latest stock firmware) on my PC
4) i can"t use that CWM as recovery because i can't use adb sideload or install zip from a file anymore(i guess due to the 3GB PIT file)
So is it possible to have a TWRP recovery flashable with odin for the GT-I9100 ?
Will that TWRP recovery finally allow me to flash the lineage os zip file?
thanks,
Click to expand...
Click to collapse
First--you can't mount sdcard after repit if you didn't format it
Second--repit using 3GB PIT is useless procedure, because you only changed the data partition size, instead repit with a 1GB_3GB.pit to change system partition to 1GB.
Third--to get TWRP 3 you must be on a rom with a kernel that supports isorec recovery, so you should flash a CWM kitkat compatible recovery through Odin and reboot to recovery and flash latest CM11 to get isorec support then reboot to recovery flash TWRP 3.0.2.1 image and then reboot recovery and flash your desired nogut rom and gapps.
If you couldn't understand me, then simply follow this guide
Hello,
thanks for your reply, it was exactly what i was looking for, i wish my Google searches about that matter redirected me to that tutorial.
IT worked brilliantly exept an error regarding formating and mounting of data partition after the use of the PIT file but upon restart, the procedure : 'Go to Wipe -> Advanced wipe,
select Dalvik, Cache, System, System, Data, Internal Storage then Swipe to Wipe, go back to TWRP Home.' completed without any errors.
That old phone is now running nougat.
NHJ1981 said:
Hello,
thanks for your reply, it was exactly what i was looking for, i wish my Google searches about that matter redirected me to that tutorial.
IT worked brilliantly exept an error regarding formating and mounting of data partition after the use of the PIT file but upon restart, the procedure : 'Go to Wipe -> Advanced wipe,
select Dalvik, Cache, System, System, Data, Internal Storage then Swipe to Wipe, go back to TWRP Home.' completed without any errors.
That old phone is now running nougat.
Click to expand...
Click to collapse
Great, happy to help
Enjoy the Nogut taste
Hi,
I wanted to upgrade my i9100 so i used odin 3.04 to flash the kitkat compatible .tar file you mentioned through download mode. The flashing in odin showed no errors but my phone is dead now and doesnt turn on!
Now i can only get into download mode using the key combinations.
What did i do wrong coming from CM9.1 with cwm 6.0.1.2 on it. And how to fix this?
ANDRiMiON said:
Hi,
I wanted to upgrade my i9100 so i used odin 3.04 to flash the kitkat compatible .tar file you mentioned through download mode. The flashing in odin showed no errors but my phone is dead now and doesnt turn on!
Now i can only get into download mode using the key combinations.
What did i do wrong coming from CM9.1 with cwm 6.0.1.2 on it. And how to fix this?
Click to expand...
Click to collapse
Your phone won't boot of course, because the kernel recovery you flashed is a kitkat kernel recovery, just reflash it again with a pit with 1GB system or more and your desired data partition size, all pits are available in repartition guide by saber, after you enter into recovery, you should navigate to mount then "format sdcard" or "format internal sdcard", i don't actually remember the option, then format it and format data and system and cache and dalvik cache, then install the latest cm11 rom to get isorec support, then let it reboot, then reboot to recovery and flash TWRP 3.0.2-1 image from the TWRP 3 thread's download section, then reboot recovery and flash your desired nogut rom and gapps
Just a sec i will give you some links..
Much appreciated. I am really stuck right now.
Can i conclude that when i flash CWM 6.0.1.2 my CM9.1 will be alive and kicking?
I think i want that right now, i postpone the upgrade to the future. Not really comfy right now....
hmmm i can't find the link to CWM 6.0.1.2 for i9100. Thats what i need right now...
ANDRiMiON said:
Much appreciated. I am really stuck right now.
Can i conclude that when i flash CWM 6.0.1.2 my CM9.1 will be alive and kicking?
I think i want that right now, i postpone the upgrade to the future. Not really comfy right now....
hmmm i can't find the link to CWM 6.0.1.2 for i9100. Thats what i need right now...
Click to expand...
Click to collapse
you have to flash a kernel not just a recovery, try dirty flashing your cm9.1 again that should make it boot correctly, and will replace the current recovery with the recovery that comes with the rom
I found my cm9.1. How does dirty flashing works? Can it be done with odin?
Does this erase all my data on my device?
edit:
Do i choose pda or phone when entering cm9.1 in odin. And where to select wipe cache and dalvik cache?
CM11
1.5GB PIT Files or 1GB PIT Files by ELgmal 1GB is enough.
Kitkat compatible recovery
this is for future update
---------- Post added at 04:18 PM ---------- Previous post was at 04:16 PM ----------
ANDRiMiON said:
I found my cm9.1. How does dirty flashing works? Can it be done with odin?
Does this erase all my data on my device?
Click to expand...
Click to collapse
no just flash it in recovery and wipe cache and dalvik, if you had xposed then flash xposed after the rom and wipe dalvik and cache and reboot.
ps: next time you post, please quote my post or mention me in your post so i can reply faster to your post
no it won't delete any data
---------- Post added at 04:45 PM ---------- Previous post was at 04:18 PM ----------
andrimion said:
i found my cm9.1. How does dirty flashing works? Can it be done with odin?
Does this erase all my data on my device?
Edit:
Do i choose pda or phone when entering cm9.1 in odin. And where to select wipe cache and dalvik cache?
Click to expand...
Click to collapse
DON'T USE ODIN, the rom is zip flash it through recovery
The problem is i can't access the data partition in windows explorer so i can not place the cm 9.1 zip file on my device. I can enter the recovery mode though
ANDRiMiON said:
The problem is i can't access the data partition in windows explorer so i can not place the cm 9.1 zip file on my device. I can enter the recovery mode though
Click to expand...
Click to collapse
have you tried with an external sdcard?
you can use an adapter to connect your external sdcard to your pc and copy your rom to
That worked fine. My device is up and running.
Many thanks for your help!
ANDRiMiON said:
That worked fine. My device is up and running.
Many thanks for your help!
Click to expand...
Click to collapse
No problem, glad to help
MigoMujahid said:
First--you can't mount sdcard after repit if you didn't format it
Second--repit using 3GB PIT is useless procedure, because you only changed the data partition size, instead repit with a 1GB_3GB.pit to change system partition to 1GB.
Third--to get TWRP 3 you must be on a rom with a kernel that supports isorec recovery, so you should flash a CWM kitkat compatible recovery through Odin and reboot to recovery and flash latest CM11 to get isorec support then reboot to recovery flash TWRP 3.0.2.1 image and then reboot recovery and flash your desired nogut rom and gapps.
If you couldn't understand me, then simply follow this guide
Click to expand...
Click to collapse
thanks this really helped me, I was struggling to get lineage installed, I had CyAN12 rom before and wasnt easy to move from there
Related
Hey guys. I just updated my Legend to the newest stable CM (with dalvik wipe, using ROM manager) and it freezes upon booting. I can get to recovery mode and I have ADB.
What do I do ? Is there a way to flash a ROM using ADB ?
It's been a long time since I worked with this stuff.
I don't think you can flash from ADB.
I suggest try to download the Cyanogen 7.1.0 rom again and check the MD5 after to make sure it is intact, I downloaded directly onto my phone then used ES file manager to check the MD5 # I had to download a few times because the MD5 # was not correct.
---------- Post added at 04:24 AM ---------- Previous post was at 04:21 AM ----------
grandioso said:
Hey guys. I just updated my Legend to the newest stable CM (with dalvik wipe, using ROM manager) and it freezes upon booting. I can get to recovery mode and I have ADB.
What do I do ? Is there a way to flash a ROM using ADB ?
It's been a long time since I worked with this stuff.
Click to expand...
Click to collapse
A quick question in your method, did you ONLY wipe the Davlik cache or did you wipe the system as well? I think you will have to wipe system & davlik when flashing a different rom.
How do I find out if md5 is correct or not ?
More importantly, what do I do after I donwload it ? It's not like I can do anything with the phone now, except get to recovery mode and control the phone via ADB in recovery mode.
And I only wiped dalvik cache.
I have help out someone with a similar issue here
http://forum.xda-developers.com/showpost.php?p=18597552&postcount=2
If you want to check MD5 # on the computer goto google and search for a MD5 file checker, ok you might want to know what MD5 is? its a check sum, the correct check sum is on the same page you downloaded on the cyanogen website.
if you know adb commands then you could always "push" the rom zip file to the sdcard on the phone, then flash it using CWM you'll need to wipe system and davlik at the very least.
First try to wipe data factory reset, wipe cache and wipe dalvikcache.
Reboot and it must be OK.
If it doesn't work download again cm7 stable, and flash it again with the 3 wipe.
I did a "clear storage" from HBOOT, but it didn't work.
When I get into recovery, I get a screen with a red exclamation mark. I guess that means I don't have CWM recovery. I have the files on my SD card, but htey have been copied from my previous one.
So I guess I'll need to flash CWM again...
You must have used fake flash to flash the rom correct?
Boot it into recovery and press the vol up button and the power button together ok?
It might give you an error once but press it again and again and you'll get into android recovery ok
Then go to install update.zip and cycle down to it using vol up and down buttons and the power button to select ok
Then it should load up clock work mod and you can use the trackpad now
Select mounts and storage and select mount SD card
Then connect USB and put the newly downloaded rom on your phone and once it's completed go back and go into advance settings I think... And do wipe cache and etc... Then go on install from SD and select your rom
Hope it helped
I flashed the ROM from ROM manager. I had CWM, but I don't anymore, because I changed SD cards. I have come to the point where I only need the goddamn update.zip file, but I can't find it anywhere and I think I'll go mad if I don't find it NOW
EDIT: Ok, I found it. At least I did a backup of my previous SD card....
I can't flash CM11 on my Verizon Fascinate after using the following thread. http://forum.xda-developers.com/showthread.php?t=2521427.
I did stock rom EH03, cwm4 for CM7 and bml-i500 via odin still not able to install [ROM][4.4] Unofficial CyanogenMod 11.0. Getting following error after try to install from zip sd card. I am able to install 2-kernel_cm11__11-10-13-fascinatemtd. Please help.Thank You
e:error executing updater binary in zip '/sdcard
err0r flashing zip '/sdcard/cm-11-20131125-unoff
e:unable to mount '/system.
mohan2k2 said:
I can't flash CM11 on my Verizon Fascinate after using the following thread. http://forum.xda-developers.com/showthread.php?t=2521427.
I did stock rom EH03, cwm4 for CM7 and bml-i500 via odin still not able to install [ROM][4.4] Unofficial CyanogenMod 11.0. Getting following error after try to install from zip sd card. I am able to install 2-kernel_cm11__11-10-13-fascinatemtd. Please help.Thank You
e:error executing updater binary in zip '/sdcard
err0r flashing zip '/sdcard/cm-11-20131125-unoff
e:unable to mount '/system.
Click to expand...
Click to collapse
Cant mount system huh?
I believe you are getting this error because you are coming from stock. Update the phone to another rom like JellyBean 4.1 and then try to flash this then.
Still no go
Payton95 said:
Cant mount system huh?
I believe you are getting this error because you are coming from stock. Update the phone to another rom like JellyBean 4.1 and then try to flash this then.
Click to expand...
Click to collapse
Still no go with JB 4.1 or CM 10.1. Cant mount e:data or e:system
Flashed a GB bootloader with Odin?
jason_streak said:
Flashed a GB bootloader with Odin?
Click to expand...
Click to collapse
if he's having a problem coming from stock, then its either or. attempted a flash from Slim Bean 4.2, having same issue...
try from stock again(odin-flashed+re-partitioned), flash cwm-fixed-for-cm7(odin-flashed, do NOT RE-PARTITION!), flash the kernel in the cm11 OP(it will boot into TWRP recovery; note DO NOT FLASH A TWRP-INJECTED ROM FOR TWRP TO APPLY ONLY THE RECOVERY, IT WILL CORRUPT /SYSTEM AND /DATA PARTITIONS AS IT WAS MOUNTING THEM BEFORE THE TWRP RECOVERY INJECTION REBOOT!!, THUS HAVING ERRORS WHEN FLASHING!! TO FIX RESTORE ANY WORKING TWRP BACKUP, OR USE ODIN TO START OVER!! ), (did over-killing CAPS LOCK make it look important enough to remember) XD, anyways...
when in TWRP flash the following(as all checked with a blue "x", incase u dont use TWRP much):
-data
-cache
-dalvik-cache
-system
flash the newest version in @Unjustified Dev 's thread for (unofficial) CM11(as its the rom u are currently having troubles with, and u had a glitched version where the update-binary was not signed all the way in his rom, as if u look at the difference in the binary from it and the newer rom version, it didnt transfer all the way), then the special GAPPS in one of the comments ON A SEPARATE FLASH!, or goto paranoid-android's forum and flash the newest Modular-mini 4.4 GAPPS AGAIN!! ON A SEPARATE FLASH!,, then any mods/add-ons u want(can be on same flash as GAPPS, along with any other additional zips, with the exclusion of data restoring ones like Titanium-Backup-made "update.zip", as that will only restore the system-apps at the moment as it requires data partition to be setup, e.g. first_boot=completed_successfully, then u can goto recovery and flash it for a quicker data recovery)
the only reason why i didn't tell u to make a backup is cause when u flashed the kernel to get the TWRP, its an incompatible kernel for stock, but if u are on a rom u like, make a backup for it first, then flash to stock for a cleaned-out partition, i always suggest making regular/routine backups(about every 3-7 days, or when trying a new rom/Rooted-or-flashed-mod)+(and routinely deleting/cleaning older ones, or ones u don't use), or at least update the titanium-backup-made "update.zip" for faster data recovery(DO NOT INCLUDE SYSTEM-APPS BUILT WITH THE ROM INSIDE THE ZIP, AS SOMETIMES IT WILL OVERLAP THE ROMS ZIP AND CAUSE SOME ERRORS, SAME WITH ITS DATA!!) (opps caps-lock of remembering again, where did that come from)
note: in case u(the OP, or others who see this comment) the key-combos(or requirements) for the following partition loading(s) are:
-(ANY)recovery = Volume_DOWN+Volume_UP+Power
-Download-Mode = Plugged into USB-Cable(From AC(Wall-Adapter), DC(Car-Port)(may or may-not work, as it only did for me literally twice since ive owned the phone XD), or Computer(USB-Port( duh )))+Vol_DOWN
-System= (any other combination, as long as POWER is pushed down for ~2-5 seconds (and other partition combinations are not pressed+held after the second "samsung" popup, and/or for two consecutive "samsung" popups or more in some cases)
ADB Commands for rebooting partitions arenon-adb-shell-based, as in shell there is ALOT more ways u could do it)
-System (method1)= adb reboot
-System (method2)= adb reboot system
-Recovery (method1) = adb reboot recovery
-Recovery (method2) = adb reboot-recovery
-Download = adb reboot download
-POWER_OFF = adb reboot -p
Glad if i could be any help with this mini-thread comment now that i see the length XD but i tried to be through and user-friendly as i could think XD if u have any other things wrong or needed to know, feel free to ask on here =)
---------- Post added at 08:49 PM ---------- Previous post was at 08:45 PM ----------
Payton95 said:
Cant mount system huh?
I believe you are getting this error because you are coming from stock. Update the phone to another rom like JellyBean 4.1 and then try to flash this then.
Click to expand...
Click to collapse
im not trying to sound like a [email protected]$$, but if u look into the errors on the thing, like alot of systems it usually tends to load from top-to-bottom, and in that specific version build it was the update-binary not signed all the way in the transfer in sign-apk (notice the first error, "e:error executing updater binary in zip '/sdcard", and without the binary even if the recovery is compiled right for the phone model(e.g. with the right partition labels for system, data, cache, etc, it wont be able to know for the specfic code to use it by without the binary that is unique for each individual phone(in the update-binary file), by my observations in the systems used anyways =S, cause i manages to fix that specfic zip later after downloading the newer version, just for testing of THAT error, and replaced the update-binary and re-signed and it worked =)
jkok said:
try from stock again(odin-flashed+re-partitioned), flash cwm-fixed-for-cm7(odin-flashed, do NOT RE-PARTITION!), flash the kernel in the cm11 OP(it will boot into TWRP recovery; note DO NOT FLASH A TWRP-INJECTED ROM FOR TWRP TO APPLY ONLY THE RECOVERY, IT WILL CORRUPT /SYSTEM AND /DATA PARTITIONS AS IT WAS MOUNTING THEM BEFORE THE TWRP RECOVERY INJECTION REBOOT!!, THUS HAVING ERRORS WHEN FLASHING!! TO FIX RESTORE ANY WORKING TWRP BACKUP, OR USE ODIN TO START OVER!! ), (did over-killing CAPS LOCK make it look important enough to remember) XD, anyways...
when in TWRP flash the following(as all checked with a blue "x", incase u dont use TWRP much):
-data
-cache
-dalvik-cache
-system
thanks for this, I spent longer than I should have before asking for help.
I have no problems flashing pre 4.4 roms, I am not a developer, and I am stuck
odined back to stock
flashed just the kernel
booted into twrp and then it gets messy
if I advanced wipe cache, dalvik, system data .......it fails
I can factory reset but any wipe after that fails
I know persistence is key, but ive been at this for a while and went back to stock like four times.........any insights?
Click to expand...
Click to collapse
after it fails the 1st time, can you reboot to TWRP? if you can, wipe davlik, reflash the rom.
tsdsbrk said:
after it fails the 1st time, can you reboot to TWRP? if you can, wipe davlik, reflash the rom.
Click to expand...
Click to collapse
yes, flashing the kernel is successful, but the wipe is not going well. when I advanced wipe either all four together or starting with the sysystem (one at a time) I get red letter failed.
thought maybe it had something to do with mounting so I tried a 16 gig class 10 chip instead of the 32 gig chip. no difference.
Im not giving up but am going to rtry ri go from stock to helly, to kit kat and see if that makes a difference.
aircooledbusses said:
thanks for this, I spent longer than I should have before asking for help.
I have no problems flashing pre 4.4 roms, I am not a developer, and I am stuck
odined back to stock
flashed just the kernel
booted into twrp and then it gets messy
if I advanced wipe cache, dalvik, system data .......it fails
I can factory reset but any wipe after that fails
I know persistence is key, but ive been at this for a while and went back to stock like four times.........any insights?
Click to expand...
Click to collapse
-odin to stock (or GeeWiz odin from its thread) (dont forget to repartition)
-!!!!!!BOOT THE DEVICE ONCE!!! OR /system + Data PARTITIONS ARE NOT MADE!!!"
-(after that if odin'd from GeeWiz go in its recovery and convert partitions (labeled volumes) to efs not ext4)
-if odin'd to stock odin the cm4 fixed for cm7(no repartition), if odined from geewiz(and completed above step), goto next step from its recovery
-go in the recovery then flash the kernel (as u were in a cwm based recovery it will update to TWRP)
-When booted into TWRP do the ALL wipes (except SDCARD)
-Flash Rom ONLY IN THIS ZIP QUE!!! (NO GAPPS!)
-Flash Gapps+other .ZIP packages
-Reboot /system and watch the first boot =)
Sorry i wasnt as clear, but sometimes its faster with the GeeWiz odin since it is already 4.2.2 + comes with boot.img + bootloader from Gingerbread/ISC/JB (as its the same), it only seems to take longer from the convert partitions (rfs) step, buts its easier in the long run =)
I have a spare fassy and just successfully flashed 11.1. Heres what I did.
Odin back to stock.
Flashed sc_milestone2_full
Flashed hellybean 4.2.2
Flashed TWRP then turned my phone off
Turned phone on and booted to recovery (TWRP at this point)
Flaahed 11.1 without doing any type of wipe.
jkok said:
-odin to stock (or GeeWiz odin from its thread) (dont forget to repartition)
-!!!!!!BOOT THE DEVICE ONCE!!! OR /system + Data PARTITIONS ARE NOT MADE!!!"
-(after that if odin'd from GeeWiz go in its recovery and convert partitions (labeled volumes) to efs not ext4)
-if odin'd to stock odin the cm4 fixed for cm7(no repartition), if odined from geewiz(and completed above step), goto next step from its recovery
-go in the recovery then flash the kernel (as u were in a cwm based recovery it will update to TWRP)
-When booted into TWRP do the ALL wipes (except SDCARD)
-Flash Rom ONLY IN THIS ZIP QUE!!! (NO GAPPS!)
-Flash Gapps+other .ZIP packages
-Reboot /system and watch the first boot =)
Sorry i wasnt as clear, but sometimes its faster with the GeeWiz odin since it is already 4.2.2 + comes with boot.img + bootloader from Gingerbread/ISC/JB (as its the same), it only seems to take longer from the convert partitions (rfs) step, buts its easier in the long run =)
Click to expand...
Click to collapse
man.....I feel like a moron and I have to be doing something wrong. I can follow directions and my wife says im a good listener. but this is kicking my butt!! I appreciate the help and feel like im bothering asking for hand holding- so I really appreciate your patience.
going ge whiz route..........
after converting to rfs and flashing the kernel from cm11 it boots into TWRP and here in my problems begin.
"-When booted into TWRP do the ALL wipes (except SDCARD)"
if I factory reset all other wipes fail
if I advance wipe first either all four fail or one at a time each fail.
its embarrassing to ask how do I wipe my device, so at least I am glad this is the trouble shooting thread. lol
and thans for the sc_milestone advice, but I don't have that file otherwise I would go that route since you tried it and it works. I searched for milestone but did not find a file named the one you used.
The sc milestone he mentioned is probably the Superclean rom. http://forum.xda-developers.com/showthread.php?t=1350621
Sent from my SCH-I500 using Tapatalk
lightningdude said:
The sc milestone he mentioned is probably the Superclean rom. http://forum.xda-developers.com/showthread.php?t=1350621
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
link
http://d-h.st/ih2m13vt442z/sc3_milestone2_full.zip
tsdsbrk said:
link
http://d-h.st/ih2m13vt442z/sc3_milestone2_full.zip
Click to expand...
Click to collapse
coming from stock, ge whiz (rfs converted) or milestone I am receiving status 7, status 0 or get prop errors in recovery trying to flash anything other than the cm11 kernel
I thought it might be an error in reading sd card error so I changed it once, but it flashes the milestone from the sd card so I am not sure what is going on
did you flash a flash a jelly bean rom before flashing CM 11.1? are you trying to flash the 6 Dec 11.1? I had problems with prior versions also.
tsdsbrk said:
did you flash a flash a jelly bean rom before flashing CM 11.1?
Click to expand...
Click to collapse
yes, Android 4.2.2 runs well
it is the milestone rom flashed through recovery from the sd card.
---------- Post added at 06:19 PM ---------- Previous post was at 05:38 PM ----------
tsdsbrk said:
did you flash a flash a jelly bean rom before flashing CM 11.1? are you trying to flash the 6 Dec 11.1? I had problems with prior versions also.
Click to expand...
Click to collapse
sorry, I didn't see the second question.
yes, 12.6 is the cm 11 build
- First time flashing CM-11.0 to your Galaxy S (or coming from another ROM)?1. Download Rom , Gapps and zip from the below step to sdcard.
2.Reboot into Recovery using 3-button-combo
3.Flash 4.4 kernel zip to gain twrp http://www.androidfilehost.com/?fid=23212708291679682 flash through recovery
4.Reboot recovery and you will now be in twrp
5.Select WIPE: go to advanced (wipe data/factory reset + wipe cache + dalvik cache partition)
6.Install the ROM then install Gapps don't install them simultaneously
my problems begin in step 5
I didn't do the wipe in your step 5. I just flashed the rom.
which jelly bean rom? try helly bean below
http://andromirror.com/file/1386
tsdsbrk said:
I didn't do the wipe in your step 5. I just flashed the rom.
which jelly bean rom? try helly bean below
http://andromirror.com/file/1386
Click to expand...
Click to collapse
Ill try just about anything at this point. Ive been using the helly 20131024, but ill try that one.
this is getting real curious. I do so enjoy pushing these older phones to their limit- this will all be worth it WHEN it works I am sure.
aircooledbusses said:
yes, Android 4.2.2 runs well
it is the milestone rom flashed through recovery from the sd card.
---------- Post added at 06:19 PM ---------- Previous post was at 05:38 PM ----------
sorry, I didn't see the second question.
yes, 12.6 is the cm 11 build
- First time flashing CM-11.0 to your Galaxy S (or coming from another ROM)?1. Download Rom , Gapps and zip from the below step to sdcard.
2.Reboot into Recovery using 3-button-combo
3.Flash 4.4 kernel zip to gain twrp http://www.androidfilehost.com/?fid=23212708291679682 flash through recovery
********4.Reboot recovery and you will now be in twrp********
5.Select WIPE: go to advanced (wipe data/factory reset + wipe cache + dalvik cache partition)
6.Install the ROM then install Gapps don't install them simultaneously
my problems begin in step 5
Click to expand...
Click to collapse
i highlighted the problem in alot of stars( *** ) once u are in TWRP from kernel flash u dont reboot to recovery again, that is whats causeing your errors, i tried to word it as "when u reboot into recovery" as-in when it boots up from kernel flash
try it once moire and it might work better, as when u do that the only partition it thinks u have is the kernel (boot.img, or /boot), thus /syste/ and /data arent being read to flash
as for the status 7, it might be cause the assert (getprop) on the top of the updater-script inside the zip under
META-INF>com>google>android>updater-script
edit it in NOTEPAD++!! and then put back in (without compression to solve some read-errors that could happen sometimes, but compression does make zip work, but sometimes uncompressed works faster for personal use),
then ill attach a zip for u to extract to your desktop, its a program called SignApk (notice its used to sign android zips), u will need to do this EVERY TIME u edit a flashable zip for it to flash right, to use it just extract it all into the same folder, make sure u have java (jre6+, and maybee jdk1.6.0_**+), then drag+drop the zip onto the DragApk.bat program and it will flash it with the same name with an added _signed before the zip, if u put it where your %path% system variable is u can go on command prompt and just type "signapk (zip name u edited) (zip name u want, that has to be different then the edited zip name or u get an empty zip for both)" u can leave out the second zip name and it will just do same name with a "_signed" before the extention, hope this helps =)
tetakpatak said:
Please quote my post and copy&paste whole text into some help thread for your phone, it is better idea as we are now getting off topic here. I'll try to help you there.
Format /system is done in recovery mode under "mount and storage" then after that you can restore your nandroid if it is done with the same recovery you use now. If you're on PhilZ 6, it usually can restore also CWM 6 backups.
Click to expand...
Click to collapse
What does format system do? And please help me load sentinel rom. That's the one I was gonna do.
Okay now for the question... I was running stock 4.1.2 with siyah kernel 6.0 b5. Then I decided to install philz kernel, but ended up in bootloop. Then I tried flashing dorimanx but still in bootloop. All the while I wiped everything before flashing.
Now im stuck as I can boot into recovery via any kernel but ultimately phone is stuck.
What to do?
And can anyone give me steps to install sentinel rom from this stage?
Sent from my Nexus 4 using xda app-developers app
AndroidReborn said:
What does format system do? And please help me load sentinel rom. That's the one I was gonna do.
Okay now for the question... I was running stock 4.1.2 with siyah kernel 6.0 b5. Then I decided to install philz kernel, but ended up in bootloop. Then I tried flashing dorimanx but still in bootloop. All the while I wiped everything before flashing.
Now im stuck as I can boot into recovery via any kernel but ultimately phone is stuck.
What to do?
And can anyone give me steps to install sentinel rom from this stage?
Click to expand...
Click to collapse
Mate, sorry for waiting, I was out of home. We will get your ROM back as soon as the phone boots again.
Don't worry, it doesn't sound serious so far. We have recovery and download mode (so topic name "nothing works" isn't really correct)
Formatting /system wipes all data from the system partition (so your system will be gone then) and it is important to do before installing new ROMs (essencially important for KitKat). It can't do any harm. As you have tried to install other kernels and didn't work we should check first what did you try to flash so far and it didn't boot? Is that what you wrote all what you have tried?
Now let me know please which recovery do you have now and is it the same version like when you have created your nandroid backup? If the recovery is the same, I would indeed try to restore nandroid backup right after wiping /system. Before you wipe the system just let me know: can you use ADB? If yes, check do you have ADB connection in the recovery mode?
tetakpatak said:
Mate, sorry for waiting, I was out of home. We will get your ROM back as soon as the phone boots again.
Don't worry, it doesn't sound serious so far. We have recovery and download mode (so topic name "nothing works" isn't really correct)
Formatting /system wipes all data from the system partition (so your system will be gone then) and it is important to do before installing new ROMs (essencially important for KitKat). It can't do any harm. As you have tried to install other kernels and didn't work we should check first what did you try to flash so far and it didn't boot? Is that what you wrote all what you have tried?
Now let me know please which recovery do you have now and is it the same version like when you have created your nandroid backup? If the recovery is the same, I would indeed try to restore nandroid backup right after wiping /system. Before you wipe the system just let me know: can you use ADB? If yes, check do you have ADB connection in the recovery mode?
Click to expand...
Click to collapse
Will it wipe the internal memory? Or the rom in the phone?
I have cwm based recovery v. 6.0.1.2. Yes I used it to make the backup.
Checking for adb.. How do I do it? .
Sent from my Nexus 4 using xda app-developers app
AndroidReborn said:
Will it wipe the internal memory? Or the rom in the phone?
I have cwm based recovery v. 6.0.1.2. Yes I used it to make the backup.
Checking for adb.. How do I do it?
Click to expand...
Click to collapse
Hi! Internal memory usually shouldn't get wiped by formatting /system, as it is "storage", not part of the system. I would give a try, wipe all: data/factory reset, cache, dalvik cache (advanced) and format /system (mounts and storage). Then back to the main menu --> backup & restore --> restore from (internal or external memory where your nandroid is saved) and choose your backup. It should reboot normally then.
tetakpatak said:
Hi! Internal memory usually shouldn't get wiped by formatting /system, as it is "storage", not part of the system. I would give a try, wipe all: data/factory reset, cache, dalvik cache (advanced) and format /system (mounts and storage). Then back to the main menu --> backup & restore --> restore from (internal or external memory where your nandroid is saved) and choose your backup. It should reboot normally then.
Click to expand...
Click to collapse
Thanks for helping, but I ended up downloading the stock rom and flashing it. Everything was normal. Then I installed cm10.2 so everything's great now. Thanks!
Sent from my Nexus 4 using xda app-developers app
Cool, @AndroidReborn! Now you can install your old ROM again and restore nandroid. Keep that stock FW saved on your PC, so if your phone gets ever again soft-bricked, no problem to revive it again.
I am wondering how nobody here responsed your help prompt, we have in i9000 help threads always handfull people of experience and skills who are ready to help in need. And there are double amount of the SGS2 units sold around the world.... strange.
tetakpatak said:
Cool, @AndroidReborn! Now you can install your old ROM again and restore nandroid. Keep that stock FW saved on your PC, so if your phone gets ever again soft-bricked, no problem to revive it again.
I am wondering how nobody here responsed your help prompt, we have in i9000 help threads always handfull people of experience and skills who are ready to help in need. And there are double amount of the SGS2 units sold around the world.... strange.
Click to expand...
Click to collapse
No idea. The people seem pretty 'busy'. Thanks for helping. Just one teeny tiny last question.. How do I install cm11 or any kitkat rom over this? Cwm is 6.0.4.5 so it's compatible...
Sent from my Nexus 4 using xda app-developers app
If you want to flash kitkat, the first thing you need to do is flash a kitkat compatible CWM (v6.0.4.7). If you try to flash KK with an 'older' CWM, you'll get 'installation aborted....error status 7' or something similar........
I'm currently running @infected_s KK build, and in the OP, you will find download links for the correct CWM, ROM and GApps files.......
Sent from my Infected KitKat bar.....
keithross39 said:
If you want to flash kitkat, the first thing you need to do is flash a kitkat compatible CWM (v6.0.4.7). If you try to flash KK with an 'older' CWM, you'll get 'installation aborted....error status 7' or something similar........
I'm currently running @infected_s KK build, and in the OP, you will find download links for the correct CWM, ROM and GApps files.......
Sent from my Infected KitKat bar.....
Click to expand...
Click to collapse
6.0.4.5 is compatible? I think so ......
Sent from my Nexus 4 using xda app-developers app
I've always read....not.....
In any case, probably best not to risk it......
6.0.4.7 is DEFINITELY KK compatible.... and it'd take a couple of seconds to flash.........
Sent from my Infected KitKat bar.....
AndroidReborn said:
No idea. The people seem pretty 'busy'. Thanks for helping. Just one teeny tiny last question.. How do I install cm11 or any kitkat rom over this? Cwm is 6.0.4.5 so it's compatible...
Click to expand...
Click to collapse
Yes, mate, CWM 6.0.4.5 is capable of flashing KitKat.
It is usually always the same:
download your ROM zip and compatible Gapps
check in the phone (or PC) if the zips are corrupted through download (if they open after clicking them, they are fine)
move the zips to the folder you will flash it from (if you use PC to flash zips with ADB sideload, put them in the sdk/platform-tools folder)
make nandroid backup of your presently used ROM
wipe data/factory reset
wipe cache
wipe dalvik cache (advanced)
format /system (under mount and storage)
flash ROM.zip
flash Gapps
reboot
It is in general always good to read in the development thread of the ROM you attend to flash in the opening post which Gapps are recommended, or if there is some unusual order of flashing (sometimes, developers recommend reboot system after flashing ROM, and after that going to recovery and flash Gapps zip.
Some KitKat ROMs struggle with root access by using Superuser, so SuperSU should be flashed. If SuperSU app from Play Store gives errors by updating binary, you should uninstall SuperSU app then, find in the Chainfire's thread the compatible UPDATE-SuperSu.zip (version for your phone), flash its zip in the recovery, install SuperSU app, update binary (either "normal" or "through CWM/TWRP")
Root access not working.
Already tapped build number 7 times, enabled root in developer settings by changing none to apps & adb (nothing works)
Then somewhere in thread i saw a person saying change apps & adb to apps only (still not working)
What should I do ?
Actually I had installed cm 12.1 in my s2 but after updating to cm 13 through system updates,
Cyanogen recovery installed, which is pathetic!
Phone is not connecting to odin (WTF!)
Please help me!
Whenever I try to install latest update (i.e feb10) through system update I will download successfully but in recovery installation aborted :crying:
a) you must use TWRP recovery
b) if you are using CWM recovery, the last step before reboot is asking for fix root....then say NO
ko2005pu said:
a) you must use TWRP recovery
b) if you are using CWM recovery, the last step before reboot is asking for fix root....then say NO
Click to expand...
Click to collapse
Hi,
Thanks for your reply.The problem is that, I can't install twrp or cwm recovery over cyanogen recovery because phone is not
connecting with odin.
As I said root is not working, so I can't use rom manager or other apps to install recovery.
I do have the same problem.
Recovery is useless, choosing either "apply update/choose from sdcard0" or "apply update choose from sdcard1" shows "Install failed installation aborted", so I can't switch to TWRP or anything else.
I've tried to flash through odin (win) and heimdall (linux), it never worked.
Phone is still booting to CM13, but I can't install Goggle apps. I've tried to install the play store apk manually, it won't launch.
check your terminal emulator
type "su" without quotation mark
chironfr said:
I do have the same problem.
Recovery is useless, choosing either "apply update/choose from sdcard0" or "apply update choose from sdcard1" shows "Install failed installation aborted", so I can't switch to TWRP or anything else.
I've tried to flash through odin (win) and heimdall (linux), it never worked.
Phone is still booting to CM13, but I can't install Goggle apps. I've tried to install the play store apk manually, it won't launch.
Click to expand...
Click to collapse
Exactly the same thing happening with me exept odin. Tried to download playstore but it closes immediately. No root access. :crying:
Crazyevilbeef said:
check your terminal emulator
type "su" without quotation mark
Click to expand...
Click to collapse
Tried but its telling me "connection to ui timed out"
download this file and put to your SD
Kernel - https://www.androidfilehost.com/?fid=24407100847293134
GApps from http://opengapps.org/ downlaod these ARM-6.0-Pico
Flash the kernel first. Then flash the recovery you installed.
then wipe cache and dalvik.
power off then
flash to recovery
1.when youre in the recovery , Factory data reset, wipe cache and dalvik (ALSO WIPE THE SYSTEM PARTITION)
2.Flash the ROM you downloaded, then the GApps you downloaded.
3.wipe cache/dalvik
Reboot
---------- Post added at 12:07 PM ---------- Previous post was at 11:47 AM ----------
Crazyevilbeef said:
download this file and put to your SD
Kernel - https://www.androidfilehost.com/?fid=24407100847293134
GApps from http://opengapps.org/ downlaod these ARM-6.0-Pico
Flash the kernel first. Then flash the recovery you installed.
then wipe cache and dalvik.
power off then
flash to recovery
1.when youre in the recovery , Factory data reset, wipe cache and dalvik (ALSO WIPE THE SYSTEM PARTITION)
2.Flash the ROM you downloaded, then the GApps you downloaded.
3.wipe cache/dalvik
Reboot
Click to expand...
Click to collapse
if still doesnt work, may I see the recovery you downloaded? (the download link)
Crazyevilbeef said:
download this file and put to your SD
Kernel - https://www.androidfilehost.com/?fid=24407100847293134
GApps from http://opengapps.org/ downlaod these ARM-6.0-Pico
Flash the kernel first. Then flash the recovery you installed.
then wipe cache and dalvik.
power off then
flash to recovery
1.when youre in the recovery , Factory data reset, wipe cache and dalvik (ALSO WIPE THE SYSTEM PARTITION)
2.Flash the ROM you downloaded, then the GApps you downloaded.
3.wipe cache/dalvik
Reboot
---------- Post added at 12:07 PM ---------- Previous post was at 11:47 AM ----------
if still doesnt work, may I see the recovery you downloaded? (the download link)
Click to expand...
Click to collapse
I have cyanogen recovery which automatically downloaded during update from cm 12.1 to cm 13 nightly & I couldn't do anything in that recovery.
When I try to update cm 13 to a newer version its download and after reboot, it goes into recovery & says "Installation aborted".
@Crazyevilbeef If you know how to install this kernel & recovery through cyanogen recovery please tell me.
Same problem with google play and recovery what is wrong with cm13 ??
fur1233 said:
@Crazyevilbeef If you know how to install this kernel & recovery through cyanogen recovery please tell me.
Click to expand...
Click to collapse
did you do what I told you?
---------- Post added at 10:01 AM ---------- Previous post was at 09:53 AM ----------
Axiii said:
Same problem with google play and recovery what is wrong with cm13 ??
Click to expand...
Click to collapse
download this file and put to your SD
Kernel - https://www.androidfilehost.com/?fid=24407100847293134
GApps from http://opengapps.org/ downlaod these ARM-6.0-Pico
if you already downloaded it to your SD, then you're ready to go
Go to Cyanogenmod Recovery
-Wipe Data/ Factory Reset
-Wipe Cache partition
-Go to Apply Update, Flash the Kernel first. and then flash the TWRP recovery you downloaded from your sources
-Wipe Cache Partition
-Power Off
When the phone is off, Open it and go to recovery. It should be TWRP Recovery you are flashing
-Factory Data Reset, Wipe Cache, Dalvik
-Also wipe system partition
-Reinstall your ROM, and flash the GApps you downloaded from the link I gave you.
-Wipe Cache/Dalvik
-Reboot
your phone should be working fine now
Apply update, does not let me flash the kernel or choose the kernel from a location from my sdcard. Do I have get external sd card for this procedure?
fur1233 said:
Apply update, does not let me flash the kernel or choose the kernel from a location from my sdcard. Do I have get external sd card for this procedure?
Click to expand...
Click to collapse
yea yea.. also try to put the files on your external SD card
and flash it
Crazyevilbeef said:
yea yea.. also try to put the files on your external SD card
and flash it
Click to expand...
Click to collapse
Ok thanks
fur1233 said:
Ok thanks
Click to expand...
Click to collapse
Did it work mate?
I'm experiencing the same problem and unfortunately your solution doesn't work for me. Cyanogenmod Recovery doesn't allow me to install anything. Regardless if I select the internal or external sdcard, I receive the message: "Install failed" "Installation aborted".
Uome2 said:
I'm experiencing the same problem and unfortunately your solution doesn't work for me. Cyanogenmod Recovery doesn't allow me to install anything. Regardless if I select the internal or external sdcard, I receive the message: "Install failed" "Installation aborted".
Click to expand...
Click to collapse
You are not alone...
yes the same here. Not in internal or external sdcard. I cant install anything. It is so dissapointing!
@GaffaDuck @Uome2 @zaf_4 If you would find any solution please post there!
Crazyevilbeef said:
Did it work mate?
Click to expand...
Click to collapse
My mobile has charging problem, & my universal battery charger sparked yesterday
I will tell soon as I get my charger
what error does the cm recovery give you?
---------- Post added at 10:05 AM ---------- Previous post was at 10:03 AM ----------
what status error does the recovery give u?
Hi,
I recently unlocked my bootloader after a really long time. I then proceeded to flash twrp and then flashed superSU and rooted my phone. I took a backup of my rom and then proceeded to install RR 5.8.4. I was given a error 7. Tried this method (https://forum.xda-developers.com/showthread.php?t=2522762) but then it gave me a error 6. Would someone help me out ?
Thx.
1) flash latest global developer MIUI ROM via MiFlash to updated firmware and to reset things if they messed up (watch out if you lock your bootloader while flashing, choosing the wrong .bat file);
2) after flash TWRP via fastboot;
3) boot TWRP and "advanced wipe" ALL partitions (except MicroSD if you have a MicroSD inserted and you want to keep its data);
4) reboot to recovery and install the RR .zip file (and the gapps .zip file if you use it);
5) after you boot into RR, you can then reboot to TWRP and install Magisk .zip to get root and other nice things.
Can i factory reset my device instead of flashing developer rom as the developer rom is quite big, around 1.4gb?
shalom170401 said:
Can i factory reset my device instead of flashing developer rom as the developer rom is quite big, around 1.4gb?
Click to expand...
Click to collapse
If you've TWRP installed at the moment then try this :
Boot to TWRP
Take a nandroid backup (just incase)
Wipe > advanced wipe > swipe to confirm
Flash firmware if you're coming from marshmallow based MIUI
Flash ROM & Gapps
Reboot
If you still get errors, probably corrupted zip. Try Re-downloading the zip.
shalom170401 said:
Can i factory reset my device instead of flashing developer rom as the developer rom is quite big, around 1.4gb?
Click to expand...
Click to collapse
You can try. Remember that if you download the full MIUI ROM, you should follow this guide http://en.miui.com/a-234.html
You can also upgrade the firmware without downloading the full ROM, from here https://forum.xda-developers.com/re.../firmware-firmware-update-2017-08-04-t3651537
Will try soon and reply
Even after flashing the firmware, i get the same error 7
I have downloaded this rom (https://www.google.co.in/amp/s/foru...nt/rom-resurrectionremix-5-8-2-t3567023/amp/) and flashed twrp using this guide (http://en.miui.com/thread-536180-1-1.html)
Maybe this is a stupid question, but your phone has MediaTek chipset or Qualcomm chipset?
I'm pretty sure it is qualcomm as the cpu speed is 2.0ghz
Now, i get this error and status error 7.
What should i do?
Where you can format all partitions, you can fix them too.
It looks like your /data is using f2fs, you should fix it converting the partition in ext4 (in official TWRP it's not possible to use f2fs).
Check all partitions, not only /data, to be formatted as ext4
So, what r the steps i should follow?
And btw, is there any unofficial twrp which i could use?
Enter TWRP, choose Wipe > Advanced Wipe
Check the box for "data"
Tap "change or repair file system"
Tap "Change file system"
Tap "ext4"
Swipe the button
Repeat for other partitions
I don't know if there are unofficial TWRP that support f2fs. Probably they exists, but you should also check if the default RR kernel supports f2fs, else you have to flash a custom kernel that supports f2fs.
Just one important question. During this process, if something weird happens ( like i get my phone soft bricked) and i got a nandroid backup. Will i be able to flash it successfully using twrp?
Yes, changing file system is a pretty safe operation (except for the erasing of the data inside the partition, as a normal format).
Flashing the backup or a full fastboot image will reset things back.
But it already shows it as ext4
Oh mahn, it still doesn't resolved?
Flash official TWRP via fastboot mode, skip this step if your already on official TWRP
Boot to TWRP
Wipe
Flash cm14.1 mido firmware
Flash Rom
Flash Gapps
??
Reboot
Note that, you should try Re-downloading all the things, like Rom / Gapps
Dude, i am unable to flash the rom due to cant install this package error and status error 7 !
shalom170401 said:
Dude, i am unable to flash the rom due to cant install this package error and status error 7 !
Click to expand...
Click to collapse
Yeah man, that's what I'm saying, you should try installing cm14.1 firmware first, then Rom..
Even after flashing the firmware, i get the same errors