Related
I have CWM 5.0.2.7. I want to upgrade from 2.3.6 Gingerbread to Android 4(PACMAN ROM preferred). I tried at least 50 - 75 times flashing >5 different ROMS, almost once bricked my phone... I found stable Gingerbread 2.3.6 and I am using it right now. I really want to upgrade to version 4, because I develop apps in Buzztouch and they will now support Android devices with Honeycomb or later. My question now is: how can I really upgrade to Android 4, because every ROM I flash is stuck at the first boot. Any help?
There is absolutely zero possibility of bricking your phone in flashing custom ROMs unless you do it in a wrong way (flashing other phone's ROM ). Same thing goes for bootloop. Wipe data,cache, dalvik cache and even format /system before flashing and also do wipes after flash. This way u can view a new dimension to the android world
swat4samp said:
There is absolutely zero possibility of bricking your phone in flashing custom ROMs unless you do it in a wrong way (flashing other phone's ROM ). Same thing goes for bootloop. Wipe data,cache, dalvik cache and even format /system before flashing and also do wipes after flash. This way u can view a new dimension to the android world
Click to expand...
Click to collapse
I already knew everything you said, even more, but thanks for idea of formatting /system. Maybe that is the main problem. Thank you so much!
UPDATE! Nothing is working. I think I will give up on ROMing.
Lol which baseband are u on? Try to flash latest stock rom ie DXKT7 and then flash a custom rom.
swat4samp said:
Lol which baseband are u on? Try to flash latest stock rom ie DXKT7 and then flash a custom rom.
Click to expand...
Click to collapse
I cannot find any with DXKT7 baseband. I am on XWKTI.
I got the same problem. Flashing from stock 2.3.6 XWKTI to any other cm 10.1 rom is not working. Clearing caches etc. does not help.
Any solution to this?
The latest rom I tried is cm-10.1-20130907-NIGHTLY-beni.zip. No luck so far.
What is wrong here?
Solved. I used the wrong CWM. beni_cwm-5_ext4_v2.tar does the trick.
Junnix said:
Solved. I used the wrong CWM. beni_cwm-5_ext4_v2.tar does the trick.
Click to expand...
Click to collapse
How did you solve the problem?
AleksaSavic said:
How did you solve the problem?
Click to expand...
Click to collapse
Did u ever successfully used ny custom rom b4.. or is this ur 1st chance...??
AleksaSavic said:
How did you solve the problem?
Click to expand...
Click to collapse
The CWM you use might be a one which is not working. At least I used a CWM 5.0.2.7. But it was rfs which is not compatible with the S5670.
So install CWM beni_cwm-5_ext4_v2.tar and you will be able to install any custom rom without problem.
Junnix said:
The CWM you use might be a one which is not working. At least I used a CWM 5.0.2.7. But it was rfs which is not compatible with the S5670.
So install CWM beni_cwm-5_ext4_v2.tar and you will be able to install any custom rom without problem.
Click to expand...
Click to collapse
It is this:
http://forum.xda-developers.com/showthread.php?t=1339640
BRO F U WANT TO UPDATE TO 4.+ THEN FOLLOW THESE STEPS
BOOT TO RECOVERY
WIPE DATA
WIPE CACHE
ADVANCE>>WIPE DALVIK CACHE
MOUNTS AND STORAGE>>FORMAT SYSTEM
INSTALL THE ROM U WANT
WIPE DATA
WIPE CACHE
REBOOT
WAIT FOR 5-10 MINS AS IT TAKS TIME FOR FIRST BOOT
STILL NOT HAPPENING
THEN UR DOWNLOADED FILE MUST BE CORRUPTED SO DOWNLOAD THE FILE AGAIN
Galaxy_Rohit said:
Did u ever successfully used ny custom rom b4.. or is this ur 1st chance...??
Click to expand...
Click to collapse
Flashed custom ROMs at least 75 times. I am not a newbie.
Junnix said:
The CWM you use might be a one which is not working. At least I used a CWM 5.0.2.7. But it was rfs which is not compatible with the S5670.
So install CWM beni_cwm-5_ext4_v2.tar and you will be able to install any custom rom without problem.
Click to expand...
Click to collapse
I already have CWM 5.0.2.7. Can I install it again via Odin or not?
ZmisiS said:
It is this:
http://forum.xda-developers.com/showthread.php?t=1339640
Click to expand...
Click to collapse
I flashed that already(I think).
vinayaksuresh said:
BRO F U WANT TO UPDATE TO 4.+ THEN FOLLOW THESE STEPS
BOOT TO RECOVERY
WIPE DATA
WIPE CACHE
ADVANCE>>WIPE DALVIK CACHE
MOUNTS AND STORAGE>>FORMAT SYSTEM
INSTALL THE ROM U WANT
WIPE DATA
WIPE CACHE
REBOOT
WAIT FOR 5-10 MINS AS IT TAKS TIME FOR FIRST BOOT
STILL NOT HAPPENING
THEN UR DOWNLOADED FILE MUST BE CORRUPTED SO DOWNLOAD THE FILE AGAIN
Click to expand...
Click to collapse
/system - ext4
/data - rfs
/cache - rfs
/db-data - unknown
I am using this apk:
CF-Root-ext4-v1.3-Addon.apk from Chainfire, but it is not made for my phone.
It has options for converting ext4 to rfs and rfs to ext4, but I am scared to do that. How can I manually convert from rfs to ext4? And, will my system even boot after doing that?
Possible solution...
Hi,
I have successfully flashed cm-10.1-20130914-NIGHTLY-beni.zip using ClockWorkMod 6.0.2.7. I initially had problems getting cm 10.1 to boot, it would just stop at the cyanogenmod logo. I got this ROM to work by first flashing ╰☆╮ [ROM][CM7.2] JellyBread v5.0 | SURPRISE! UPLOAD COMPLETE! ╰☆╮. then flashing the nightly.
Good luck:fingers-crossed:.
Regards,
jemail
I wouldn't recommend installing ICS on a Galaxy Fit. The phone doesn't really stand that much of the ROM itself.. I use a rom that'll look exactly alike it, that's basically it. But I tried Lenio vQuattro. it seemed pretty nice If you really need to then try this rom. And it wouldn't be such a bad idea tp update CWM, or try another Recovery.
AleksaSavic said:
/system - ext4
/data - rfs
/cache - rfs
/db-data - unknown
I am using this apk:
CF-Root-ext4-v1.3-Addon.apk from Chainfire, but it is not made for my phone.
It has options for converting ext4 to rfs and rfs to ext4, but I am scared to do that. How can I manually convert from rfs to ext4? And, will my system even boot after doing that?
Click to expand...
Click to collapse
Good question.
I really got no answere to that question. But as far as I know there are CMW for rfs and for ext4/ext3 filesystems.
If you use the wrong CMW than the phone will hang in a boot loop after flashing. That's what I had.
So I suggest you should try different CMW. For rfs and ext4. Better to flash them with Odin. I used Odin_Multi_Downloader_v4.42.exe.
As CWM try: http://forum.xda-developers.com/showpost.php?p=24719114&postcount=1387 or this CWM http://androidlegend.com/dl/beni_cwm-5_ext4_v2.tar
One of these should work for you.
Hello guys, I have a XT1033 converted to GPe in stock 5.1. What can I do to get CM12.1?
Flash stockrom 5.0.2 and after that twrp. Flash cm12.0 and dirty flash cm12.1 . hope this is correct.
klaymaniaf said:
Flash stockrom 5.0.2 and after that twrp. Flash cm12.0 and dirty flash cm12.1 . hope this is correct.
Click to expand...
Click to collapse
After I flash the stock rom, it wont go past the boot logo.
In twrp it will say the flash was successful, but if i reboot into stock it wont go past the boot logo which is still the google logo from the 5.1 GPe. If I go to flash CM over that, I get an error.
wipe dalvik cache/cache
Never mind, i got it to work. I had to flash the correct gpt.bin file, because the partitions are different on stock motorola than to the gpe. After that a full wipe and i could go back to stock and onto cm12.1.
http://forum.xda-developers.com/showpost.php?p=57444986&postcount=1
this is the file that worked for me You will have to do a full wipe and reboot to recovery to be able to mount any of the file systems again tho.
r97smith said:
Never mind, i got it to work. I had to flash the correct gpt.bin file, because the partitions are different on stock motorola than to the gpe. After that a full wipe and i could go back to stock and onto cm12.1.
http://forum.xda-developers.com/showpost.php?p=57444986&postcount=1
this is the file that worked for me You will have to do a full wipe and reboot to recovery to be able to mount any of the file systems again tho.
Click to expand...
Click to collapse
Mate can u step by step explain what you did and downloaded? I am on converted GPE and want to install cm12.1 - funny thing is I didnt get anything online for getting gpe to cm12.1 other than your post Your help is appreciated. Also does your sms work on cm12.1?
Vivek
vivekdeshmukh said:
Mate can u step by step explain what you did and downloaded? I am on converted GPE and want to install cm12.1 - funny thing is I didnt get anything online for getting gpe to cm12.1 other than your post Your help is appreciated. Also does your sms work on cm12.1?
Vivek
Click to expand...
Click to collapse
From GPE, I wiped everything in twrp recovery. Flashed the gpt.bin file I had linked to there, and then rebooted to recovery again.
Then I decided to go back to stock 5.0.2, flashed that, then cm12 and then cm12.1. But thats just how I did it anyway.
I had to flash the gpt.bin file to re-partition the system storage, because its different to the stock and cyanogenmod. I flashed stock 5.0.2 just to be sure there wasnt going to be anymore problems when flashing cyanogenmod. Then I flashed cm12 to see everything booted right, and cm12.1 with the 5.1 gapps.
Yes, everything works excellent on cm12.1
r97smith said:
From GPE, I wiped everything in twrp recovery. Flashed the gpt.bin file I had linked to there, and then rebooted to recovery again.
Then I decided to go back to stock 5.0.2, flashed that, then cm12 and then cm12.1. But thats just how I did it anyway.
I had to flash the gpt.bin file to re-partition the system storage, because its different to the stock and cyanogenmod. I flashed stock 5.0.2 just to be sure there wasnt going to be anymore problems when flashing cyanogenmod. Then I flashed cm12 to see everything booted right, and cm12.1 with the 5.1 gapps.
Yes, everything works excellent on cm12.1
Click to expand...
Click to collapse
Thanks mate, it sounds bit of a task for a noob like me, but hell i will give that a try
---------- Post added at 05:16 PM ---------- Previous post was at 05:09 PM ----------
r97smith said:
stock 5.0.2, flashed that, then cm12 and then cm12.1.
Click to expand...
Click to collapse
Our of curiosity, why do we have to go from 5.02 to cm12 to cm12.1? cant we go directly from 5.02 to cm12.1?
vivekdeshmukh said:
Thanks mate, it sounds bit of a task for a noob like me, but hell i will give that a try
---------- Post added at 05:16 PM ---------- Previous post was at 05:09 PM ----------
Our of curiosity, why do we have to go from 5.02 to cm12 to cm12.1? cant we go directly from 5.02 to cm12.1?
Click to expand...
Click to collapse
For flashing cm 12.1 if you are currently using gpe 5.1 converted, you dont need to do all that **** like flashing stock 5.0.2 then cm 12 and then cm12.1
You just need to do this
In twrp recovery go to wipe and change data partition file system to f2fs
Then wipe every thing in recovery and flash cm12.1
sjandroiddeveloper said:
You just need to do this
In twrp recovery go to wipe and change data partition file system to f2fs
Then wipe every thing in recovery and flash cm12.1
Click to expand...
Click to collapse
1st step - wipe and change Data partition to f2fs ONLY or should i change the partition to f2fs for all (data, cache, system, usb)?
2nd step - wipe everything meaning dalvik, data, cache, system BUT NOT internal storage and USB - correct?
vivekdeshmukh said:
1st step - wipe and change Data partition to f2fs ONLY or should i change the partition to f2fs for all (data, cache, system, usb)?
2nd step - wipe everything meaning dalvik, data, cache, system BUT NOT internal storage and USB - correct?
Click to expand...
Click to collapse
You have to change file system to f2fs of data partition only ,don't change other, if you do there is no doubt your device will not boot but it may cause several other problems
And after changing file system of data partition you need to wipe dalvik,cache,system and data
No need to wipe internal storage (data/media)
And where does USB come in this ???
Sent from falcon
PRESS THANKS IF HELPED
sjandroiddeveloper said:
And where does USB come in this ???
Click to expand...
Click to collapse
USB OTG is an option that comes under recovery in twrp - advanced wipe. Thanks trying it right now!
vivekdeshmukh said:
USB OTG is an option that comes under recovery in twrp - advanced wipe. Thanks trying it right now!
Click to expand...
Click to collapse
I know what is USB OTG and where it comes
What I meant was why did you even think of wiping USB
sjandroiddeveloper said:
You have to change file system to f2fs of data partition only ,don't change other, if you do there is no doubt your device will not boot but it may cause several other problems And after changing file system of data partition you need to wipe dalvik,cache,system and data No need to wipe internal storage (data/media)
And where does USB come in this ???
Sent from falcon
PRESS THANKS IF HELPED
Click to expand...
Click to collapse
Tried it yesterday night >> BOOM! OS gone! Dont know what happened, did the f2fs no problem but after dalvik, cache, system and data wipe the OS and all files just disappeared - dont know if it was corrupt data partition or me being too sleepy (5.00am) and could have deleted Internal storage. But the point is I ended up with no OS and then tried ADB pushing my cm files to phone, well only to realize that ADB was not recognizing the device inspite of uninstall/install drivers ... slept at 6.00 in morning. Today, finally, copied the cm files by mounting the phone and copying from PC, just to realize after flashing that the cm12.1 still has the same issues of not able to send sms.
But anyways thanks to you I did learn something new and the opportunity to be in a soft brick situation and come out of it
Btw do u hv a converted gpe and tried the cm12.1 simply by changing the partition? EVerything works very smooth for me but just that the SMS doesnt work - which i cant live without.
vivekdeshmukh said:
Tried it yesterday night >> BOOM! OS gone! Dont know what happened, did the f2fs no problem but after dalvik, cache, system and data wipe the OS and all files just disappeared - dont know if it was corrupt data partition or me being too sleepy (5.00am) and could have deleted Internal storage. But the point is I ended up with no OS and then tried ADB pushing my cm files to phone, well only to realize that ADB was not recognizing the device inspite of uninstall/install drivers ... slept at 6.00 in morning. Today, finally, copied the cm files by mounting the phone and copying from PC, just to realize after flashing that the cm12.1 still has the same issues of not able to send sms.
But anyways thanks to you I did learn something new and the opportunity to be in a soft brick situation and come out of it
Btw do u hv a converted gpe and tried the cm12.1 simply by changing the partition? EVerything works very smooth for me but just that the SMS doesnt work - which i cant live without.
Click to expand...
Click to collapse
No I never converted to gpe
But the method I told you was absolutely correct
And your OS was deletes because you wiped system partition which was necessary to install cm 12.1 so that was obvious and no need to worry.
And for your information you don't need adb if you are using twrp because it supports mtp
And the sms bug was there but it was solved long ago but I don't know why its not working for you
May be try different kernels
And bro PRESS THANKS instead of saying
can you plz help with the sms bug..
sjandroiddeveloper said:
No I never converted to gpe
But the method I told you was absolutely correct
And your OS was deletes because you wiped system partition which was necessary to install cm 12.1 so that was obvious and no need to worry.
And for your information you don't need adb if you are using twrp because it supports mtp
And the sms bug was there but it was solved long ago but I don't know why its not working for you
May be try different kernels
And bro PRESS THANKS instead of saying
Click to expand...
Click to collapse
can you plz help with the sms bug..
I ran into a bit of a problem recently. My phone suddenly froze, and didn't want to wake. This happens occasionally, so I did what I always do: hard reboot the phone. Hard rebooting resulted in a bootloop, I got stuck in the bootanimation. So at this point, I figured wiping the phone and reflashing would do the trick. Guess what? It didn't. I thought this was a bit odd, so I started to (clean) reflash earlier builds of TugaPower, but nothing seemed to help; every build resulted in a bootloop, except for TugaPower N5. So I decided to just run N5, new N8 build was released though, so I tried flashing that build, still stuck in bootloop.
At this point I lost all hope in TugaPower and decided to flash the official CM14.1 build; no dice, resulted in a bootloop. At this point I tried resetting everything, wiping my complete phone, but nothing helped. Then I tried flashing kwoktopus/updateing AOSP build, which did boot fine! I really want to run CM14.1/TugaPower though, but my phone just refuses to boot on both. Any ideas?
It is worth noting that I've tried almost everything (in TWRP) recovery at this point. From formatting system all the way to running adb to fix the persist partition. Nothing seemed to help. CM14.1 builds don't boot, but AOSP boots fine. WHAT IS WRONG WITH ME? MY PHONE?
Useful info about the phone:
I'm not running multirom;
I am using latest TWRP recovery;
I wasn't deliberately using F2FS or EXT4 memory, partition, whatever (I didn't know what they both did)
TugaPower N5 build ran fine, after that build everything bootlooped
CM13 boots, CM14.1 bootloops
Kwoktopus/updateing AOSP 7.1 build boots fine
Try checking if your /cache partition is formatted to f2fs, it sometimes automatically does that
f41lbl0g said:
Try checking if your /cache partition is formatted to f2fs, it sometimes automatically does that
Click to expand...
Click to collapse
It wasn't, it was in EXT4 format...
Which gapps?
giaur said:
Which gapps?
Click to expand...
Click to collapse
Open Gapps Pico, 7.1 of course. But I quit flashing it after a while, figured I'd keep that out of the equation when I was triangulating the source of what caused the bootloop. It definitely isn't because of Gapps.
Maybe you need to flash a different firmware?
Thepromodder said:
Maybe you need to flash a different firmware?
Click to expand...
Click to collapse
How would I need to do that? I (re)flashed the latest firmware for the TugaPower rom, but I figured that flashing a (new) firmware for the CM14.1 builds wasn't necessary.
Managed to fix it using this link: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
I don't know what causes this to happen, but now you guys know how to fix it.
Whenever I try to return to stock EMUI 5.0.1 from Lineage OS 14.1 with my TWRP backup, it just stays at the boot screen that says "Honor" and doesn't continue past that point. I was wondering why this happens and what I can do to fix this since I want to return back to stock without doing the painful dload method. I currently have TWRP 3.1.1-0 OpenKirin Edition, the same version I used to make the backup too.
Which LineageOS ROM do you have, OpenKirin's or HassanMirza01's..?
RedSkull23 said:
Which LineageOS ROM do you have, OpenKirin's or HassanMirza01's..?
Click to expand...
Click to collapse
I have the one by HassanMirza01
SenyorMauricio said:
I have the one by HassanMirza01
Click to expand...
Click to collapse
Did you already formatted data partition back to ext4 before trying to restore the backup? Hassan's roms are f2fs based, so you won't be able to restore an ext4 based rom over f2fs
RedSkull23 said:
Which LineageOS ROM do you have, OpenKirin's or HassanMirza01's..?
Click to expand...
Click to collapse
RedSkull23 said:
Did you already formatted data partition back to ext4 before trying to restore the backup? Hassan's roms are f2fs based, so you won't be able to restore an ext4 based rom over f2fs
Click to expand...
Click to collapse
Should I do that before restoring the backup? I've done it after restoring the backup, and it doesn't do anything but mess up TWRP's permissions.
RedSkull23 said:
Did you already formatted data partition back to ext4 before trying to restore the backup? Hassan's roms are f2fs based, so you won't be able to restore an ext4 based rom over f2fs
Click to expand...
Click to collapse
It booted up whenever I changed it back to ext4, but it comes up with a screen saying "Unencryption Unsuccessful" whenever I boot up. I click on reset phone, and it brings back to TWRP. This even happens if I reset the phone via TWRP. I'm not sure if this process would work if I restored the stock recovery, but I'm not sure if I want to find out.
SenyorMauricio said:
It booted up whenever I changed it back to ext4, but it comes up with a screen saying "Unencryption Unsuccessful" whenever I boot up. I click on reset phone, and it brings back to TWRP. This even happens if I reset the phone via TWRP. I'm not sure if this process would work if I restored the stock recovery, but I'm not sure if I want to find out.
Click to expand...
Click to collapse
Whenever I formatted data through the stock e-Recovery (the stock portion of the recovery that stays even with TWRP), it booted up perfectly fine! Thanks for all your help!
SenyorMauricio said:
Whenever I formatted data through the stock e-Recovery (the stock portion of the recovery that stays even with TWRP), it booted up perfectly fine! Thanks for all your help!
Click to expand...
Click to collapse
Nice one dude
I'm currently running OOS 9.5.13 with arter97's kernel. I converted the data partition to f2fs and it have been very stable for me. Can anyone tell me if the stock OOS kernel still supports f2fs? I suspect it does since I was temporarily running the stock kernel after the 9.5.13 OTA, and didn't get any errors from apps trying to access data on the phone.
Not interested in formatting my data partition, and if it does not support it, I will just wait for an updated kernel before going to 10.
NotATreoFan said:
I'm currently running OOS 9.5.13 with arter97's kernel. I converted the data partition to f2fs and it have been very stable for me. Can anyone tell me if the stock OOS kernel still supports f2fs? I suspect it does since I was temporarily running the stock kernel after the 9.5.13 OTA, and didn't get any errors from apps trying to access data on the phone.
Not interested in formatting my data partition, and if it does not support it, I will just wait for an updated kernel before going to 10.
Click to expand...
Click to collapse
It's working fine. I'm on f2fs Android 10 stock kernel. Waiting for arter kernel as well.
keaheng said:
It's working fine. I'm on f2fs Android 10 stock kernel. Waiting for arter kernel as well.
Click to expand...
Click to collapse
Thanks! That's what I was hoping for.
keaheng said:
It's working fine. I'm on f2fs Android 10 stock kernel. Waiting for arter kernel as well.
Click to expand...
Click to collapse
How????? IS there any guide to convert to f2fs? I tried and tried and it never works no matter what guide I've used.
I have TWRP, convert data partition to f2fs, all from a fresh wipe. I installed oos and it never boots; always into recovery. FOR YEARS. EVEN ON MY OP5T. The guide is clearly not working for me and never has.
JhinCuatro said:
How????? IS there any guide to convert to f2fs? I tried and tried and it never works no matter what guide I've used.
I have TWRP, convert data partition to f2fs, all from a fresh wipe. I installed oos and it never boots; always into recovery. FOR YEARS. EVEN ON MY OP5T. The guide is clearly not working for me and never has.
Click to expand...
Click to collapse
Did you install OOS after converting to f2fs? You cannot convert without a clean install after.
NotATreoFan said:
Did you install OOS after converting to f2fs? You cannot convert without a clean install after.
Click to expand...
Click to collapse
Tried that (via twrp i guess?). Only reboots to recovery. Already wasted hours, and I assumed the guide was supposed to pretty much actually say what to do, which it clearly doesn't if another oos installation was needed after (which i already did anyway..)
Guess f2fs will only be worth considering in the next few years; not worth all the problems just for a marginal increase in performance on an alreasy fast phone.
Format Data, reboot to TWRP, convert to f2fs, install OOS OTA, reboot. If you wind up in stock recovery, do a factory reset from there, and then it will boot.
Sent from my GM1915 using Tapatalk