Related
I read on flip board that cm 10.1 is official for our phone and I I want to flash it and I did but the after I flash it and flash the boot.IMG it get stuck on the HTC logo and I see that the soft key button turn on and have vibration when I touch them can anyone help .
Sent from my HTC One S using xda premium
Do you have an S4 or S3 phone
Did you check md5 for good/bad download
Did you wipe all including System 2x in recovery
Which recovery are you using
I have s4 and I didn't check the md5 cause all 4.2 ROMs have the same problem for me,i have twrp
Sent from my HTC One S using xda premium
which version twrp. some of the later 2.3's had issues
otherwise if you are wiping all and fastbooting boot, not sure
fastboot boot after rom and fastboot erase cache before booting onto rom
rugmankc said:
which version twrp. some of the later 2.3's had issues
otherwise if you are wiping all and fastbooting boot, not sure
fastboot boot after rom and fastboot erase cache before booting onto rom
Click to expand...
Click to collapse
I have v 2.3.3.0 for twrp I'll update it and try what you said and report back here if it works
Sent from my HTC One S using xda premium
i had 2.3.3.0 and it was not one of the bad ones
Still doesn't work and I tried force md5 sum check on twrp and it failed could that be the problem
Sent from my HTC One S using xda premium
brandontamas said:
Still doesn't work and I tried force md5 sum check on twrp and it failed could that be the problem
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I'd reccomend clockworkmod over twrp, had more bootloops with twrp in the past.
Also, good alternative rom is dark jelly cm10.1 with android 4.2.1 stable and reliable, using it a pretty long time.
Easy install via an automatic installer program called aroma installer, no need to flash boot.img here
http://forum.xda-developers.com/showthread.php?t=2051865
Sent from my One S using xda app-developers app
yes, ck your md5's. i use es explorer and it is easy
as john said you can try another rom, but still ck md5 and wipe system as part of your wipes
if you flash a rom with aroma, don't wipe in recovery and aroma. only one. i prefer recovery
as for cwm or twrp. everyone has their favorite. it is my understanding though cwm hasn't kept pace on updates with later version roms afaik
hope you get it--
My brother just got himself a skyrocket he's on the newest radio w/custom recovery installed but can't seem to flash anything but cm 10.1 with an old 4.2 GApps package.
Kinda frustrating because I haven't seen anyone else having this issue in any other thread. I did to his all I did to mine and I'm running Wantowan2's DU. Just says installation failed and we can't even flash other recovery from within recovery. Where should we go from here
Sent from my SGH-I727 using xda app-developers app
Odin back to stock and start over. Something got messed up in your recovery
Make sure you've got the proper recovery for 4.3 as well.
Sent from my SGH-I727
Well we did Odin back to stock and Odin flashed twrp 2.6.3 and tried to flash the new cwm touch 6043 and it just failed. Not sure why. I repeated process with my phone and it worked but I feel like he did some stuff he's not telling me.
And the only things that do flash remain to be the cm 10.1.3 and GApps from 2012
Sent from my SGH-I727 using xda app-developers app
K
Boot_Derran said:
Well we did Odin back to stock and Odin flashed twrp 2.6.3 and tried to flash the new cwm touch 6043 and it just failed. Not sure why. I repeated process with my phone and it worked but I feel like he did some stuff he's not telling me.
And the only things that do flash remain to be the cm 10.1.3 and GApps from 2012
Sent from my SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
The gapps isn't right for 4.3, cm 10.1. Flash the 8-13-2013 gapps
Edit, you can find it on the OP of this http://forum.xda-developers.com/showthread.php?p=46685423
My understanding is that cm 10.1.3 is android version 4.2.2 and the gapps he used worked. No force closes or anything but one thing he mentioned is that his first flashing of the ROM did not include a full wipe. He did not format system. And even after a full wipe in twrp 2.6.1; data, cache, android secure, dalvik, and system still nothing. Still shows dead android and failed install
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Boot_Derran said:
My understanding is that cm 10.1.3 is android version 4.2.2 and the gapps he used worked. No force closes or anything but one thing he mentioned is that his first flashing of the ROM did not include a full wipe. He did not format system. And even after a full wipe in twrp 2.6.1; data, cache, android secure, dalvik, and system still nothing. Still shows dead android and failed install
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
What is the exact error message that TWRP is giving?
Gotta wait for my bro to get off work but will post as soon as I can get his phone and give it another go
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Hi – I have a stubborn issue with my Blaze 4G not working on CM roms, I would appreciate any help you guys can provide. Below are the details:
I recently bought a T-Mobile Samsung Galaxy S Blaze 4G, and did the following:
- Rooted it using the following guide (it now has ICS)
- SIM Unlocked it using the following guide (now it works on other networks)
- Updated to CWM 6.0.3.8, since JB roms needs it
- Flashed the T769-UVLH5 modem, since CM support it
And now when I flash CM 10 stable or 10.2 nightly it gets stuck in booting and displaying the CM logo animation screen, after few minutes it reboots and does it all over again.
I remember when I upgraded to CM JB on my SGS3 I needed to flash a JB stock rom on it to get the new boot loaders for JB, but I saw no mention of this on this forum. What else am I missing?
Thanks.
TINGEA said:
Hi – I have a stubborn issue with my Blaze 4G not working on CM roms, I would appreciate any help you guys can provide. Below are the details:
I recently bought a T-Mobile Samsung Galaxy S Blaze 4G, and did the following:
-Rooted it using the following guide (it now has ICS)
-SIM Unlocked it using the following guide (now it works on other networks)
-Updated to CWM 6.0.3.8, since JB roms needs it
-Flashed the T769-UVLH5 modem, since CM support it
And now when I flash CM 10 stable or 10.2 nightly it gets stuck in booting and displaying the CM logo animation screen, after few minutes it reboots and does it all over again.
I remember when I upgraded to CM JB on my SGS3 I needed to flash a JB stock rom on it to get the new boot loaders for JB, but I saw no mention of this on this forum. What else am I missing?
Thanks.
Click to expand...
Click to collapse
You wiped data/cache/system? Reinstall it. Anyways use the new 6.0.4.4 recovery.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
You wiped data/cache/system? Reinstall it. Anyways use the new 6.0.4.4 recovery.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom. I have to admit that I forgot to do the wipes. but even after doing the wipes (data/system/ factory rest/ cach/devalk) and reinstalling the CM nightly, I still have the same issue.
as for recovery, I updated to the latest version using the rom manager, and according to the official site clockworkmod[dot]com[slash]rommanager (can't post links) I have the latest version for Blaze. how do you get the 6.0.4.4 on blaze?
I still feel it's a ICS vs JB bootloaders issue, but not sure how to proceed next.
Thanks!
TINGEA said:
Thanks Somcom. I have to admit that I forgot to do the wipes. but even after doing the wipes (data/system/ factory rest/ cach/devalk) and reinstalling the CM nightly, I still have the same issue.
as for recovery, I updated to the latest version using the rom manager, and according to the official site clockworkmod[dot]com[slash]rommanager (can't post links) I have the latest version for Blaze. how do you get the 6.0.4.4 on blaze?
I still feel it's a ICS vs JB bootloaders issue, but not sure how to proceed next.
Thanks!
Click to expand...
Click to collapse
No boot loaders man. This is before Samsung's complications.
Recovery is here.
http://d-h.st/AFu
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Thanks Somcom3X, but still didn't work. When installing the CM room in recovery 6.0.4.4 I get a bunch of getprop assert failures. This used to work on the previous version (6.0.3.8). Now the Rom won't install.
Also, I'm curious what did you mean by this is before Samsung's complications?
Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
Thanks Somcom3X, but still didn't work. When installing the CM room in recovery 6.0.4.4 I get a bunch of getprop assert failures. This used to work on the previous version (6.0.3.8). Now the Rom won't install.
Also, I'm curious what did you mean by this is before Samsung's complications?
Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
After 2011 samsung began installing software and counters to try and prevent people from rooting and installing custom firmwares.
knox is an example of this.
These devices don't have any of that complicated security.
You handy with odin? Your recovery is not right. Just to be clear, what is your model number?
If it is T 7 6 9, your good to go to odin. I'd recommend going back to stock, and then install a recovery and you should be good to go.
Somcom3X said:
After 2011 samsung began installing software and counters to try and prevent people from rooting and installing custom firmwares.
knox is an example of this.
These devices don't have any of that complicated security.
You handy with odin? Your recovery is not right. Just to be clear, what is your model number?
If it is T 7 6 9, your good to go to odin. I'd recommend going back to stock, and then install a recovery and you should be good to go.
Click to expand...
Click to collapse
Thanks again, I use the guide here to convert the image into a tar.md5 to flash using odin, but after flashing successfully I still have the same issue when installing the CM zip file in recovery, and yes it is the T-mobile Samsung Galaxy S Blaze 4G T769.
any other possible causes?
BTW - when I was flashing via Odin my upload phone screen was showing that I have a custom rom and the counter was 1.... do I need to fix that?
TINGEA said:
Thanks again, I use the guide here to convert the image into a tar.md5 to flash using odin, but after flashing successfully I still have the same issue when installing the CM zip file in recovery, and yes it is the T-mobile Samsung Galaxy S Blaze 4G T769.
any other possible causes?
Click to expand...
Click to collapse
SOLUTION:
The reason your stock recovery system keeps getting overwritten at Android startup is because of a script that is being run.* All you need to do is either rename this script or simply delete it.
Please keep in mind that if you restore your stock ROM, this script will be restored with it so you will have to rename or delete it again.* Do the following:*
1.
Make sure your device is powered on and running normally,
2.
Make sure you have rooted your device and that you have all of the necessary permissions in order to manipulate system files.*
3.
In the root file system go to \system\etc
4.
Find the file named install-recovery.sh and either rename it or, as I did, delete it.*
That’s all there is to it.*
Please keep in mind that you will need to flash your custom system recovery one more time after modifying the script file.* After that, reboot away and you will always be able to get back into your new system recovery.
Good Luck and Happy Tweaking.
Click to expand...
Click to collapse
Try that.
Found it here http://mark.candleshoreblog.com/201...-factory-stock-roms-at-android-system-reboot/
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
Try that.
Found it here http://mark.candleshoreblog.com/201...-factory-stock-roms-at-android-system-reboot/
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom3X - but I'm not sure this is needed for my case. I read the original blog post and my recovery does not get overwritten. I actually rebooted multiple times into CWM recovery and each time it is the same 6.0.4.4.
I also went into the /system/etc folder and there is no install_recovery.sh file.
to clarify, here is where I'm stuck now:
- when I use CWM 6.0.3.8 CM install completes successfully, but then CM will not boot, and will keep on cycling on the boot logo screen.
- when I use CWM 6.0.4.4 I can't start to install CM as it complained that my phone is not t769.
in all cases I'm using CM 10.2 nightly for T769.
Thanks for the help.
You should delete assert lines at the top of the zip's updater-script and it will let you flash it.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
I removed the assert lines from the updater script, and it was able to complete the install process afterwards, however when I booted the new CM 10.0 system it got stuck on the cyanogenmod boot logo. I made sure I do a system/data rest, cleared cash, and cleared devalk.
I do not think it's an issue with my recovery as I'm getting the same result as I did with the official 6.0.3.8.
Something else is going on.
Any ideas?
Thanks.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
I removed the assert lines from the updater script, and it was able to complete the install process afterwards, however when I booted the new CM 10.0 system it got stuck on the cyanogenmod boot logo. I made sure I do a system/data rest, cleared cash, and cleared devalk.
I do not think it's an issue with my recovery as I'm getting the same result as I did with the official 6.0.3.8.
Something else is going on.
Any ideas?
Thanks.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Tar back to stock GB. Upgrade to ICS. Then root and install cwm. Flash away
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
You should delete assert lines at the top of the zip's updater-script and it will let you flash it.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom3X - but this is more trouble than what I wanted to put in - I'll stick with the rooted stock ROM I have. I was hoping the process was a little more straight forward, similar to my SGS3.
thanks for all your help thus far!
Somcom3X said:
Tar back to stock GB. Upgrade to ICS. Then root and install cwm. Flash away
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Ok, my rooted ICS stock is acting up (random shutdowns and such), so I need to give this another try and get this phone to CM.
I tared back to stock GB, skipped the upgrade to ICS (was not able to upgrade via the ROM software update option), flashed CWMR (5.0.4.x) via Odin, upgraded to CWMR 6.0.4.5, installed CM 11 nightly, and then wiped data/factory rest and Dalvik .... and ....
it is still stuck on the boot screen....
I seriously would appreciate a silver bullet right now!
TINGEA said:
Ok, my rooted ICS stock is acting up (random shutdowns and such), so I need to give this another try and get this phone to CM.
I tared back to stock GB, skipped the upgrade to ICS (was not able to upgrade via the ROM software update option), flashed CWMR (5.0.4.x) via Odin, upgraded to CWMR 6.0.4.5, installed CM 11 nightly, and then wiped data/factory rest and Dalvik .... and ....
it is still stuck on the boot screen....
I seriously would appreciate a silver bullet right now!
Click to expand...
Click to collapse
Hmm. Go back to stock ics, flash a 10.2 recovery, then flash whatever you desire.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
What is a10.2 recovery? Is it a certain version of CWMR? And do I need to flash it via Odin? Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
What is a10.2 recovery? Is it a certain version of CWMR? And do I need to flash it via Odin? Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
It would be cwm 6.0.2.7
You can flash the img through a zip or by terminal on the phone.
Odin needs a tar'd recovery img
Sorry been very busy.
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2577265
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Thanks Somcom3X - I looked all over this forum and the internet, and could not find a link for a 6.0.2.7 CWM for Blaze - I found it for other phones but not Blaze. can you please point me to a link if you happen to know of one. the official site does not have an archived list of previous versions.
as for the provided link, I did follow it through, and downloaded the recovery Tar (it was CWM 5.5.04) but that yielded the same results after installing CM 10 and 10.2 - stuck at boot screen logo. I'm reasonably confident now that it is not a recovery issue, as I flashed half a dozen different versions and none worked with CM 10, 10.2, or 11.... it has to be something else!
Thanks.
TINGEA said:
Thanks Somcom3X - I looked all over this forum and the internet, and could not find a link for a 6.0.2.7 CWM for Blaze - I found it for other phones but not Blaze. can you please point me to a link if you happen to know of one. the official site does not have an archived list of previous versions.
as for the provided link, I did follow it through, and downloaded the recovery Tar (it was CWM 5.5.04) but that yielded the same results after installing CM 10 and 10.2 - stuck at boot screen logo. I'm reasonably confident now that it is not a recovery issue, as I flashed half a dozen different versions and none worked with CM 10, 10.2, or 11.... it has to be something else!
Thanks.
Click to expand...
Click to collapse
I'm very sorry for the delay. Been very very busy.
https://www.dropbox.com/s/awp1zy4u3x34a2v/CWM-cm-10.2-Recovery-t769.zip
That is my personal 10.2 recovery. Works fine for me.
The author is me, but I was too lazy to change the lines.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
So I installed the lateat CM12 nightly, wasn't really impressed yet and went to go restore my backup and once it's done restoring, it get stuck at the bootscreen animation. Just keeps going and going abs going. I used the latest cwm touch recovery as CM12 is not compatible with MultiROM. I would just flash the factory img back but my computer decided to it doesn't ever want to recognize adb avid fastboot on Linux.
Anyone know where I can find a flashable zip for the factory 5.0.1 ROM? Any help would be appreciated!
Try googling Nexus 5 factory image...
Here's a flashable 5.0 : http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523
Niflheimer said:
Here's a flashable 5.0 : http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523
Click to expand...
Click to collapse
Now I'm assuming I'd have to unroot it and flash stock recovery and lock the bootloader to get it to update to 5.0.1?
No, it's flashable in your custom recovery. It's 5.0 though
Sent from my Nexus 5 using XDA Free mobile app
Yeap , ota needs stock recovery. Also , switch to twrp since cwm isn't playing nice with L.
jd1639 said:
No, it's flashable in your custom recovery. It's 5.0 though
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I was talking about the 5.0.1 update but thanks.
Niflheimer said:
Yeap , ota needs stock recovery. Also , switch to twrp since cwm isn't playing nice with L.
Click to expand...
Click to collapse
I'm on the stock ROM you linked too, stock recovery, and unrooted but, when I get the update for 5.0.1 and try and install it, I get an error. Do I need to relock my boatloader?
asd87 said:
I'm on the stock ROM you linked too, stock recovery, and unrooted but, when I get the update for 5.0.1 and try and install it, I get an error. Do I need to relock my boatloader?
Click to expand...
Click to collapse
You're on a custom Rom. The ota isn't going to work. And you don't need to relock your bootloader. If you can afford to wipe your data download the 5.0.1 factory image. Extract it and use the flash-all.bat
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You're on a custom Rom. The ota isn't going to work. And you don't need to relock your bootloader. If you can afford to wipe your data download the 5.0.1 factory image. Extract it and use the flash-all.bat
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
My computer is Linux, and adb and fastboot for whatever reason unknown to me, won't install. That's why I asked for a zip file of the factory image. Thanks for the help though.
asd87 said:
My computer is Linux, and adb and fastboot for whatever reason unknown to me, won't install. That's why I asked for a zip file of the factory image. Thanks for the help though.
Click to expand...
Click to collapse
Well, unfortunately, there isn't a 5.0.1 flashable rom available right now. If you can't get fastboot to work on your Linux machine you're kind of sol as you need to be 100% stock to get the ota to work. That means stock recovery in your case. Google recovery zip collection xda. There's a custom recovery flashable stock recovery there.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Well, unfortunately, there isn't a 5.0.1 flashable rom available right now. If you can't get fastboot to work on your Linux machine you're kind of sol as you need to be 100% stock to get the ota to work. That means stock recovery in your case. Google recovery zip collection xda. There's a custom recovery flashable stock recovery there.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I have the stock 5.0 recovery that I installed through Flashify. I'll barrow a windows computer or something lol
asd87 said:
I have the stock 5.0 recovery that I installed through Flashify. I'll barrow a windows computer or something lol
Click to expand...
Click to collapse
I'd work on getting adb/fastboot working on your Linux machine. You're going to need it in the long run.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I'd work on getting adb/fastboot working on your Linux machine. You're going to need it in the long run.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I've spent hours trying to get it work one night. I'll do some note searching for more advice and again thanks.
jd1639 said:
I'd work on getting adb/fastboot working on your Linux machine. You're going to need it in the long run.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Did some more digging, got it install, and flashed the factory img for 5.0.1 and twrp recovery then superSU through twrp.
Mods please lock the thread thanks.
Get wugfreshes Toolbox. It has access to all factory images. Some people are not fans of "one click solutions" but this has never let me down.
There's a flushable zip on here also. Put it in a search in the app and you should come across it. It IS the full version.
Did you ever find out why the CWM restore led to getting stuck on boot animation??
Just ran into this last night. Tried restoring 2 different CWM backups and both got stuck on boot animation.
I eventually got a new ROM flashed. Going to try TWRP recovery I suppose.
I know I never had this problem with 4.4, this was the first time I have restored a LP ROM..
one7dchevy said:
Did you ever find out why the CWM restore led to getting stuck on boot animation??
Just ran into this last night. Tried restoring 2 different CWM backups and both got stuck on boot animation.
I eventually got a new ROM flashed. Going to try TWRP recovery I suppose.
I know I never had this problem with 4.4, this was the first time I have restored a LP ROM..
Click to expand...
Click to collapse
My guess would be; cwm hasn't been optimized for Lollipop. Cyanogen has just recently started working on 5.0 and they probably haven't touched the recovery too much. But that's just my guess.
asd87 said:
My guess would be; cwm hasn't been optimized for Lollipop. Cyanogen has just recently started working on 5.0 and they probably haven't touched the recovery too much. But that's just my guess.
Click to expand...
Click to collapse
Yea figured something like that.
Got TWRP installed, will try to update after my next nandroid restore so that any old CWM users will know..
Wifi was working fine with CM12.1. I wonder why its not working in CM12.0 Since 12.1 had crash issues, I flashed it back to 12.0 for which wifi doesnt turn ON.
I cannot flash stock ROM/firmware anyway. Can anyone help? Thank You.
sivakrishnan said:
Wifi was working fine with CM12.1. I wonder why its not working in CM12.0 Since 12.1 had crash issues, I flashed it back to 12.0 for which wifi doesnt turn ON.
I cannot flash stock ROM/firmware anyway. Can anyone help? Thank You.
Click to expand...
Click to collapse
Explain the exact way of flashing please
Sent from my mint using XDA Free mobile app
sivakrishnan said:
Wifi was working fine with CM12.1. I wonder why its not working in CM12.0 Since 12.1 had crash issues, I flashed it back to 12.0 for which wifi doesnt turn ON.
I cannot flash stock ROM/firmware anyway. Can anyone help? Thank You.
Click to expand...
Click to collapse
Did you come from the latest firmware??
SdtBarbarossa said:
Explain the exact way of flashing please
Sent from my mint using XDA Free mobile app
Click to expand...
Click to collapse
I was using CM12.1 and due to crashes i decided to install CM12, and for easiness i flashed twrp recovery to FOTAKernal using TWRP Manager app.
But TWRP failed to install any rom, so i flashed stock firm (not latest) using flash tool.
Then using in fast boot mode, flashed Philz Recovery by command "fastboot flash boot <boot.img>"
got Philz Recovery and using that recovery installed CM 12.0
is this clear?
Did I had to install latest firmware before flashing CM12.0 to get wi-fi turned on?!!!
sivakrishnan said:
I was using CM12.1 and due to crashes i decided to install CM12, and for easiness i flashed twrp recovery to FOTAKernal using TWRP Manager app.
But TWRP failed to install any rom, so i flashed stock firm (not latest) using flash tool.
Then using in fast boot mode, flashed Philz Recovery by command "fastboot flash boot <boot.img>"
got Philz Recovery and using that recovery installed CM 12.0
is this clear?
Did I had to install latest firmware before flashing CM12.0 to get wi-fi turned on?!!!
Click to expand...
Click to collapse
Yes it must be latest stockrom!
Sent from my mint using XDA Free mobile app
SdtBarbarossa said:
Yes it must be latest stockrom!
Sent from my mint using XDA Free mobile app
Click to expand...
Click to collapse
thank you so much, i have clicked thanks,
well will you please tell me why we should use latest stock firmware, since we are wiping all data, change kernel etc using recovery?
just out of curiosity
I would like to know whether i can use its FOTAKernel for TWRP Recovery??
Once I failed to flash rom using twrp recovery..
sivakrishnan said:
thank you so much, i have clicked thanks,
well will you please tell me why we should use latest stock firmware, since we are wiping all data, change kernel etc using recovery?
just out of curiosity
I would like to know whether i can use its FOTAKernel for TWRP Recovery??
Once I failed to flash rom using twrp recovery..
Click to expand...
Click to collapse
1. because of some "invisible" partitions that must be up-to-date... Most important is "modemst" partition... You never touch them while flashing!
2.use the app by Corphish to get my TWRP .... Twrpmanager is ****ty
Sent from my mint using XDA Free mobile app
SdtBarbarossa said:
1. because of some "invisible" partitions that must be up-to-date... Most important is "modemst" partition... You never touch them while flashing!
2.use the app by Corphish to get my TWRP .... Twrpmanager is ****ty
Sent from my mint using XDA Free mobile app
Click to expand...
Click to collapse
flash the recovery zip through recovery after flashing the image file via flashtool!
if we flash using flash tool, it will lose after flashing another CM rom right? i need to get it for ever that's why I'm asking about flashing in to fotakernel.
thanks