I am currently running CM10.1 on my Fascinate on Verizon and it works well, when I try and flash any of the 4.2 and even the new 4.3 Slim ROM I get a status 7 error and says try again to confirm so I flash it a second time then it just boot loops and I have to odin back to stock. My question is the boot loop from the status 7 error or from it just being the wrong ROM. I have tried to format /system before installing without luck as well.
When coming up from odin are you using the the GB bootloader?
Other problem could just be from certain sd cards don't work well on fascinate.
Odin from Powerwashed EC09
When I start I use (Powerwashed EC09 with modem) then (CWM4) then I flash (eh03_tsm_res2.2). From there I will try to flash slim rom and I get the status 7 message but if I try and flash CM9,CM10, or CM10.1 they work. I have a 32 GB Class 10 SD card.
Chainsaw32608 said:
When I start I use (Powerwashed EC09 with modem) then (CWM4) then I flash (eh03_tsm_res2.2). From there I will try to flash slim rom and I get the status 7 message but if I try and flash CM9,CM10, or CM10.1 they work. I have a 32 GB Class 10 SD card.
Click to expand...
Click to collapse
you also missed installing the GBbootloader.tar file
you should do that right after you odin the
cwm4_fixed_for_cm7-ODIN.tar
you can install to 4.2.x this way::
Power off and pull battery,
remove micro sdhc card
put into d/l mode, install battery
odin:: :: PDA Slot :: CI500_VZW_EH03_GB_CM.tar.md5 ::
and in the :: PIT Slot :: Atlas_v2.2.pit ,,, and appropriately check box [[ Re-Partition ]]
when finished
reboot (important)
~~check out all of Verizon goodness ~~
oh sorry,,,
Power off and pull battery
put into d/l mode, install battery
odin:: :: PDA Slot :: cwm4_fixed_for_cm7-ODIN.tar
when finished, click reset in odin
pull battery and usb to power down the fassy and close out of odin
put into d/l mode, install battery
odin:: :: BOOTLOADER Slot :: GBbootloaders.tar ,,, and appropriately check box [[ Phone Bootloader Update ]]
when finished, click reset in odin
pull battery and usb to power down the fassy and close out of odin
Reinstall micro sdhc card
Use three finger ,, [[[ Hold -- Volume buttons UP / Down & Power ]] into CWM blue recovery 4 [ie: cwm4_fixed_for_cm7]
((you have to use this recovery at this point in the process,,, it lets file system properly update from a bml ROM to an mtd ROM)))
and, Choose the Wipe Data/Factory reset, and also wipe dalvik cache [1 time for each is fine]
then while still in recovery,,, flash your 4.2.x ROM of choice,,,
most likely it will auto reboot into any newer recovery 6.0.x.x, or new TWRP 2.x.x Recovery,,, never go back to the [cwm4_fixed_for_cm7] recovery,, ,, unless you have ODIN'ed back to stock,,, ,,, this is normal,,, and you will need to select install zip from sd [again]::
and choose to install/flash your 4.2.x ROM of choice AGAIN,
if it auto reboots you back into this same recovery again [meening: any newer recovery]
...[[[ the recovery style and version is determined by the ROM you are installing, some have standard CWM Recovery, some have Hellybean Touch Recovery,,, some have TWRP Recovery, and some have a blue Touch Recovery version ]]]...
,,, still that is fine/normal ,,,,,,, simply install/flash your 4.2.x ROM of choice AGAIN,
if it auto reboots and tries to load the ROM,, if not manually choose to Reboot Rom,,, and ,,, Wait ,,, patiently,,, ,,, maybe as much as 8-10 minutes for it to boot all the way up.
you may ultimately have to flash 1 more time,, some ROMs seem do be more finicky than others.
After that you really should be almost good to go.
On the 1st boot of your new 4.2.x ROM give the filesystem about 5-10 minutes to scan through everything before making any changes to any of your ringtones or notifications
after that reboots into recovery,,,Wipe cache,,, and Install a gapps zip of choice::: [ either whats recommended by the ROM dev/maintainer,,, or an official gapps of the appropriate date that matches your ROM ]
reboot
Enjoy your jellybean goodness ~ Yummy!
.
.
If all else fails please refer back to ::
Section:4 How to flash any ICS 4.0.x & 4.x.x JellyBean based rom
in the ::
[GUIDE] Installing a Rom/CWM recovery/Root or going back to Stock
posted by and updated by :: droidstyle
.
.
Still Status 7
I did everything up to the CWM4 blue screen wiped data and dalvik then tried to install Slim 4.2 build 6,7 &8 and got the status 7 error on all three builds. I have seen some people saying to by-pass this you can edit the updater in the ROM file. Do you think this has something to do with the version of my phone because CM9 & 10, PAC, and Hellybean work fine, Liquid Smooth and Slim do not.
What is weird the latest 4.3 slim not from their website but from the XDA dev post works Slim-fascinatemtd-4.3.build.1.2-UNOFFICIAL-20130927-1827.zip posted by BDogg718. No other versions will work. And I can not use this ROM because MMS does not work.
Related
I have had CM7 for about a month now and the troubles are becoming too much. My sd card isint read at all anymore and i cannot use the camera or gallery anymore. I have tried multiple fixes/sd cards and no cigar. Just yesterday many of my apps started force closing and many functions of the phone are now unusable. I tried wiping cache/dalvik and reflashing the rom but still have the same problem. I think it is time to upgrade to the most stable version of cm9 out. Can anyone advise me on the best/safest way to upgrade from cm7 to cm9? I have heard flashing over it can work perfectly and sometimes it doesnt.
Any advice in the right direction would be appreciated. Thanks in advance!
hurley2481 said:
I have had CM7 for about a month now and the troubles are becoming too much. My sd card isint read at all anymore and i cannot use the camera or gallery anymore. I have tried multiple fixes/sd cards and no cigar. Just yesterday many of my apps started force closing and many functions of the phone are now unusable. I tried wiping cache/dalvik and reflashing the rom but still have the same problem. I think it is time to upgrade to the most stable version of cm9 out. Can anyone advise me on the best/safest way to upgrade from cm7 to cm9? I have heard flashing over it can work perfectly and sometimes it doesnt.
Any advice in the right direction would be appreciated. Thanks in advance!
Click to expand...
Click to collapse
cm7 has work arounds for all of those issues...and you may have the same troubles on cm9 since they are both mtd based. take sometime and research, this has all been covered 100+ times.
Teamhacksung ICS instructions
These instructions will walk you through installing Teamhacksung CM9 build 10 on the Fascinate.
1. Download: ICS build 1 to your SD card (www.mediafire.com/?67782p054lp6o22), ICS build 10 to your SD card (http://goo.im/roms/sbrissen/fascinate/cm_fascinatemtd-ota-eng.BUILD10.zip), Stock Gingerbread ROM (minus.com/m3yQWm9wg/), cwm4 fixed for CM7 (http://api.viglink.com/api/click?fo...d=1311907538&jsonp=vglnk_jsonp_13379472165344), Odin v1.83 (mediafire.com/?429fcpdtpckkcea), gapps (http://goo.im/gapps/gapps-ics-20120429-signed.zip), and Atlas 2.2 pitfile (mediafire.com/?r2mi80911vgjjjz).
2. Put your phone into download mode and open Odin.
3. Check repartition in Odin.
4. Click PIT and select the Atlas pit file. Click PDA and select the stock ROM.
Click start. (it will take 5 minutes)
5. Boot the phone up, then shut it down.
6. Put it into download mode and open Odin again.
7. Select the cwm4_fixed_for_cm7.tar file you downloaded with the PDA button.
Click start.
6. Three-finger into recovery.
7. Clear data, cache, and Dalvik cache.
9. Click Install ZIP from SD card, then Chooze ZIP from SD card. Navigate to teamhacksung_fascinatemtd-ota-eng.BUILD1.zip, then confirm install.
10. Let it boot up. Select Reboot, then Recovery from the power menu.
11. You should be in CWM-Based Recovery v5. Install cm_fascinatemtd-ota-eng.BUILD10.zip. Then install gapps-ics-20120429-signed.zip. Select Reboot System Now.
12. Congrats! You should be on Teamhacksung ICS Build 10!
NOTE: NEVER three-finger into recovery with this ROM. ALWAYS use the power menu.
TROUBLESHOOTING:
Q: Help! CWM_fixed_for_cm7 gives me errors!/isn't working correctly!
A: Install CWM_ALL.tar (http://www.mediafire.com/?6x5utoca59et7o9) first, then install cwm4_fixed_for_cm7-BWM.zip (http://forum.xda-developers.com/attachment.php?attachmentid=1082600&d=1337909700) from CWm.
Q: T.H.S. Build 1 installs fine, but when I try to install build 10, it bootloops/won't install!
A: Start over, but install Build 5 before Build 10.
Q: The above answer is no good! It still gives me guff when installing Build 5!
A: Start over, but try installing the builds in sequential order.
I tried following this:
http://forum.xda-developers.com/showthread.php?t=1580070
"INSTRUCTIONS" part:
* RECOVERY: FACTORY RESET IF YOU WERE USING ANOTHER ROM!
* RECOVERY: Install Rom: Download
* RECOVERY: Install Gapps, ALWAYS-EVEN FOR UPDATES: Download (find the latest one that carries the "jb" tag)
* RECOVERY: Wipe Cache Partition
* RECOVERY: Wipe Dalvik Cache
* Reboot and enjoy
Click to expand...
Click to collapse
did all the above, never forgot any of the 3 wipes/resets that were necessary.
used this rom file:
http://goo.im/devs/paranoidandroid/roms/i9100g
(latest one)
for my Galaxy Samsung S II GT-i9100g.
I had CWM and also had a rooted android 2.3.
first boot it showed me the normal samsung boot screen, for 45 minutes....
so I restarted and the phone gave me the same behaviour..
so I removed the battery to turn off the phone, and attempted to reinstall the whole thing, going through this process again from scratch
not forgetting any of the wipes etc...
now every time I boot it, it leads me to CWM instead of the normal boot screen and the expected paranoid rom eventually...
I followed this path because CM 10 failed me because upgrading from 2.3 to 4.x requires going through something that is called "stock" or as I think it actually is - google's /manufacturer's original firmware/rom production line thingy
and after that it needs me to re-enable root on that stock rom all over again. And only then I may attempt to install CM10...
so I picked paranoid instead, because in it's instructions is showed me no such constraint. heck it can't give me that constraint because there is no "stock" of android 3.x for smartphones
but then this issue happened... so I need your help.
I found similar search results but couldn't figure out their solutions or how whatever triggered that same problem (which isn't mentioned in those threads) is related to what I did to my phone... (so that I will not repeat the same mistake)
your help is much appreciated as I need it so so much!
Huh?
Just flash a stock ROM, get back on your feet and go CM or paranoid.
Sent from the little guy
gastonw said:
Huh?
Just flash a stock ROM, get back on your feet and go CM or paranoid.
Sent from the little guy
Click to expand...
Click to collapse
by "flash"ing you mean the option "install from a zip file" in CWM in recovery mod?
if I have some rom, the only way for me to install another would always be by going through that middle step of also installing a 'stock' rom as well?
there is no way around it?
installing a 'stock' rom, wouldn't it make me loose my root I have on the phone and force me to root it all over again before I can continue install anything at all?
thats the reason I wanted to try out the paranoid way of doing this instead of the CM10, because I have no interest in rooting my already rooted phone and I hoped that paranoid does not need me to go to stock first....
Couple of things:
Stock: why, when in trouble, we suggest stock?
Stock is the original state of the phone.
Samsung write it for our device to work flawless, so, by flashing stock we can check if our device is fully functional.
Imagine you flash a custom ROM and you lose IMEI, you go "wtf?" right?
In order to check if your EFS folder is f&#cked up, you flash stock and check if your IMEI is still there.
We can always use stock to take a long breath "phew, we're fine" after a f*&k up.
You can flash stock via CWM (zip file), Odin (tar file, md5) and mobile Odin (tar, zip and md5).
CWM: custom recovery, you can get it by flashing a custom kernel or by flashing it via stock Recovery (generally comes with BusyBox and SuperUser app, which gives you Root).
Odin: Just download any version and follow directions.
Mobile Odin: Well, this is a hell of an app, you need Root to run it.
It does all that Odin does, plus it roots your ROM (only stock ROMs) while it's flashing it, all by itself. Costs 5 bucks, but it's damned worthwhile.
Wanna know the best scenario?
You get M.O Pro, you get a nandroid back up online app, you get CWM zip files (sitting on your SD).
With that line up, you can flash whatecer the hell you want and you will ALWAYS have root.
Sent from the little guy
some questions
ONE QUICK IMPORTANT QUESTION BEFORE THE REST:
If I use mobile odin, will I be able to use it to install stock rom and also root it at the same time?
SECOND IMPORTANT QUESTION:
you said I could flash whatever I want and still have root, but my problem was not 'not having root', it was not having the flash process complete successfully... how do I attack that?
THIRD IMPORTANT... info... :
My "BUILD" version is "GINGERBREAD.XXKL5", isn't that a 'stock' one?
If you don't have a lot of time,
then the rest of this post is not as important as the 2 questions above...
gastonw said:
Couple of things:
Stock: why, when in trouble, we suggest stock?
Stock is the original state of the phone.
Samsung write it for our device to work flawless, so, by flashing stock we can check if our device is fully functional.
Imagine you flash a custom ROM and you lose IMEI, you go "wtf?" right?
In order to check if your EFS folder is f&#cked up, you flash stock and check if your IMEI is still there.
We can always use stock to take a long breath "phew, we're fine" after a f*&k up.
You can flash stock via CWM (zip file), Odin (tar file, md5) and mobile Odin (tar, zip and md5).
CWM: custom recovery, you can get it by flashing a custom kernel or by flashing it via stock Recovery (generally comes with BusyBox and SuperUser app, which gives you Root).
Odin: Just download any version and follow directions.
Mobile Odin: Well, this is a hell of an app, you need Root to run it.
It does all that Odin does, plus it roots your ROM (only stock ROMs) while it's flashing it, all by itself. Costs 5 bucks, but it's damned worthwhile.
Wanna know the best scenario?
You get M.O Pro, you get a nandroid back up online app, you get CWM zip files (sitting on your SD).
With that line up, you can flash whatecer the hell you want and you will ALWAYS have root.
Sent from the little guy
Click to expand...
Click to collapse
the saddest part is that I couldn't figure out most of what you just said
what is 'nandroid'? 'flashing'? do you mean like dd in linux? copying to the entire flash storage device?
'IMEI'? huh..? O_O
at the moment I was able to 'get back on my feet', I restored everything back to normal with manual copying of important parts of the CWM corrupted backup from this week, and old stuff for a CWM backup made few months ago.
now that I am at a 'normal' state.. I want to install paranoid or CM10 on my GT-I9100g.
which one of those 2 does not force me going through installing stock?
I have this fear of installing stock that it will take away my root and that I will have to use adb from command line to re-enable root afterwards, which I have bad experience with.
I need to know a few things before I attempt to install stock via CWM,
will installing stock disable my root? will installing stock disable my ability to load recovery boot menu CWM?
is 'root' an attribute or state that belongs to the running rom itself after boot has been completed and to that only?
or does it also belong to the state the device is at while in the recovery boot menu CWM ?
I tried messing around with ADB in the past to see if I could root devices via that way but it wasn't very successful so thats why I'm afraid of having to attempt it again.
bumpitybump
even though a year later, I would still love some replies
resurrecting my motivation to do this once again.
copy paste from my other post;
before flashing, you will need these;
-stock rom (get it from Sammobile, sign in and select your country and phone model)
-blazing kernel for recovery (search in XDA)
-custom rom (CM, PA, Supernexus...your choice)
-backup your data
-GApps (get the latest one)
-you must know what are you doing and dont flame/blame other member if something wrong
how to flash;
-make sure you are on latest stock rom (mine is JellyBean 4.1.2), if not like the OP, flash the latest stock rom using Odin;
*reboot your phone in Download Mode
*open Odin and in PDA option select your stock rom and then Start
*if done it will display Done and disconnect your phone, it will boot up
*if bootloop, reboot into Recovery Mode, and then wipe data and cache, and then reboot normally
-after updating your phone to latest stock rom, copy your custom rom, GApps, and Blazing kernel into external SD card, then reboot into Recovery Mode
-choose "apply update from external storage" and choose Blazing kernel, wait for it to finish update
-reboot normally, and then reboot back to Recovery Mode. this time you will notice that your recovery is different from the previous one
-select install zip > choose from external storage/sdcard 1 > and then choose your custom rom. then wait for it to finish update
-repeat the above step to install GApps, and after that reboot normally
-if bootloop, reboot back to Recovery Mode and then wipe data, cache and dalvik and then reboot
-done, now you are running on custom rom
Click to expand...
Click to collapse
and about the root, i believe that almost all custom rom rooted
hi all motorola fans
today i want to learn you how can install 5 custom rom side your stock FW
1st : you need be on stock JB 4.1.2
2nd you need to download SafeStrap from there : http://goo.im/devs/Hashcode/spyder/Safestrap-JB41-3.07.apk
install SafeStrap as normal app than open it and touch on install recovery and wait to complete
than download any custom rom and put zip file in phone memory
reboot your phone
wow you see new screen touch on menu key and go to recovery
in recovery 1st you need to make new partion for any custom rom you want to install so touch on boot options and go to rom-slot-1 and put data partion size on 1GB and create rom slot, wait to complete
go you 1st page and this time touch on install
find your zip file and let to install
do it for other 3 custom rom
for boot :
go to boot options touch on rom-slot-1 (any partion you install your rom) and touch on active
than go back and touch on reboot
WARNING : you can install only rom with same base "base mean jb ics" and version is not matter "4.1.2 and 4.2.2 have same base"
Well, this is basic knowledge for each user, so it's good to share it. But you could extend it with some important details, like:
+SS AOSP Roms have restrictions to Rom slots (e.g. CM10.1 must be on Slot 1, etc)
+Handling of backups, selective backups, restoring, moving systems, etc
+Usage of TWRP File Explorer
+Ability of ADB
+Unbrick solution (given by the tools and options given by SS)
Only to mention some of them Why not making this a real SS tutorial?
Do you know if there is a way to fix the problem while flashing to stock slot:
E:Unable to unmount /system
I cannot flash anything to stock slot.
Olao99 said:
Do you know if there is a way to fix the problem while flashing to stock slot:
E:Unable to unmount /system
I cannot flash anything to stock slot.
Click to expand...
Click to collapse
Safestrap won't flash on stock. You need to use bmm.
Sent from my OG RAZR
DiRtY UnIcOrNs, JBX kernel, Viper4android Fx
s27moto said:
hi all motorola fans
today i want to learn you how can install 5 custom rom side your stock FW
1st : you need be on stock JB 4.1.2
2nd you need to download SafeStrap from there : http://goo.im/devs/Hashcode/spyder/Safestrap-JB41-3.07.apk
install SafeStrap as normal app than open it and touch on install recovery and wait to complete
than download any custom rom and put zip file in phone memory
reboot your phone
wow you see new screen touch on menu key and go to recovery
in recovery 1st you need to make new partion for any custom rom you want to install so touch on boot options and go to rom-slot-1 and put data partion size on 1GB and create rom slot, wait to complete
go you 1st page and this time touch on install
find your zip file and let to install
do it for other 3 custom rom
for boot :
go to boot options touch on rom-slot-1 (any partion you install your rom) and touch on active
than go back and touch on reboot
WARNING : you can install only rom with same base "base mean jb ics" and version is not matter "4.1.2 and 4.2.2 have same base"
Click to expand...
Click to collapse
a little help for other
mokee to slot 1
carbon to slot 1
buttered to slot 1
avatar to slot 1
art v3.1 to slot 1
paranoid to slot 1
miui v4 to all
pacman v5 to slot 2
dirty to slot 2
jelly 4.33 to slot3
cyanogen 10.1 to slot 3
https://www.youtube.com/watch?v=iT_Foay4dUs&feature=youtube_gdata_player
Sent from my HTC Butterfly using Tapatalk 4 Beta
I'm going from stock to 11
I follow the steps in this guide
I'm trying to install CM10.1 before installing CM11. From what i've read this is ideal
The problem occurs when I go to install cm 10.1
-push EH03 via odin
-reboot
-push cwm4 fixed for 7 via odin
-push GB Bootloaders
-3 button into recovery
-wipe (recover-factory reset / wipe dalvik cache)
*** I get an E: unkown volume for path [/sd-ext] when clearing dalvik cache. I don't know if this is normal***
-install zip -> CM-10.1-xxxxx.zip
This is where i get stuck
load screen starts then reads "bml/mtd..."
reboots into cwm v6.0.2.2
immediately flashes META-INF... with error droid background (cant read the error flashes to fast)
repeats this error 3-5 times then loads into cwm 6.0.2.2
If i try to reinstall zip from there it just blinks then goes back to cwm home.
I cant do anything from this point and I have to reload EH03
Any ideas or help would be appreciated.
Have you verified the MD5 of your CM10.1 download. Could just be a bad download.
Read this thread and see if it helps.
http://forum.xda-developers.com/showthread.php?t=2551041
tsdsbrk said:
Read this thread and see if it helps.
http://forum.xda-developers.com/showthread.php?t=2551041
Click to expand...
Click to collapse
yes I've referenced that thread and posts in the original guide as well.
I've tried many different install methods and guides and I either get a status 7 error or install immediately resets the recovery and fails to load.
I've spent all day and a good portion of last week on this and its super frustrating
reloaded all the downloads from the guide this morning to make sure I didn't end up with a bad file same result.
I did get a cm7 rom working this weekend and one ICS(CM9?) rom working but when I would try to move on from there im ending up in this position.
just tried to flash hellybean 4.2.2 and im getting status 7 error.
saw a post that said to install zip again after first 7 error and still the same result, cant get past status 7 error.
I did a few other searches for status 7 fixes and im not coming up with anything definative.
I had a similar problem a while back that was due to the SD card. Let me see if I can find the thread...
http://forum.xda-developers.com/showthread.php?t=2407858
Try flashing this rom after the EH03 stock rom and before the 4.2.2 rom
http://d-h.st/ih2m13vt442z/sc3_milestone2_full.zip
SupraLance said:
I had a similar problem a while back that was due to the SD card. Let me see if I can find the thread...
http://forum.xda-developers.com/showthread.php?t=2407858
Click to expand...
Click to collapse
sounds exactly like my problem, I did just buy a sandisk class 10 last friday after an old class 4 became currupt.
I'll try it with a diffrent sd card and see where that gets me.
Hey Guys,
I'm having a bit of an issue. Currently I was running STOCK Android 4.3 JB, have been for a while, it started to get a bit slow & I was wanting to fresh install, but also try out a 5.0 lollipop ROM. I've rooted my phone in the past and installed custom ROMs before without a problem (Revolution Remix + Cyanogenmod 11), however, I decided to try Liquidsmooth 5.0 lollipop. i followed this video,
https://www.youtube.com/watch?v=QquFDFEEKlI
http://forum.xda-developers.com/galaxy-s3/development/rom-liquidsmooth-lollipop-4-0-b1-t2980477
I downloaded both files and copied them onto my MicroSD card.
I backed up my data (contacts, images, files etc..)
Booted into "Recovery Mode", wiping Cache & factory Reset
When to install from SD, located file and it started reading/installing (sorry can't remember exactly what it did), but during process it failed. I went back into Android (had to setup again), Went and made sure Developer Mode and USB Debugging was on, still didn't work.
Went to make sure CWM was installed/update, which it said it was (possibly from previous custom installs?), tried updating, failed. It said
Went and installed 'SuperSU' from Play store, but got this error.
Decided to try re-install STOCk 4.3 JB, I
made sure USB Debugging was on
loaded Odin 3.07 (or was it 3.09) and loaded 4.3 Firmware under PDA (left everything else as is)
Started and let it do its thing. It finished/PASSED and phone restarted.
i went back into the phone, installed ROM manager & SuperSU again to give it another shot... but same problem again, getting the error above.
I'm not sure what's happened and I'm not sure what "solutions" to search for... anyone have any suggestions?
At this stage I'm thinking of just going back to STOCK 4.3, then maybe try again (either with Liquidsmooth lollipop, or, Slimkat 4.4)
Thanks guys, any help would be super appreciated,
Regards,
~ Dave
Le Widget said:
Hey Guys,
I'm having a bit of an issue. Currently I was running STOCK Android 4.3 JB, have been for a while, it started to get a bit slow & I was wanting to fresh install, but also try out a 5.0 lollipop ROM. I've rooted my phone in the past and installed custom ROMs before without a problem (Revolution Remix + Cyanogenmod 11), however, I decided to try Liquidsmooth 5.0 lollipop. i followed this video,
https://www.youtube.com/watch?v=QquFDFEEKlI
http://forum.xda-developers.com/galaxy-s3/development/rom-liquidsmooth-lollipop-4-0-b1-t2980477
I downloaded both files and copied them onto my MicroSD card.
I backed up my data (contacts, images, files etc..)
Booted into "Recovery Mode", wiping Cache & factory Reset
When to install from SD, located file and it started reading/installing (sorry can't remember exactly what it did), but during process it failed. I went back into Android (had to setup again), Went and made sure Developer Mode and USB Debugging was on, still didn't work.
Went to make sure CWM was installed/update, which it said it was (possibly from previous custom installs?), tried updating, failed. It said
Went and installed 'SuperSU' from Play store, but got this error.
Decided to try re-install STOCk 4.3 JB, I
made sure USB Debugging was on
loaded Odin 3.07 (or was it 3.09) and loaded 4.3 Firmware under PDA (left everything else as is)
Started and let it do its thing. It finished/PASSED and phone restarted.
i went back into the phone, installed ROM manager & SuperSU again to give it another shot... but same problem again, getting the error above.
I'm not sure what's happened and I'm not sure what "solutions" to search for... anyone have any suggestions?
At this stage I'm thinking of just going back to STOCK 4.3, then maybe try again (either with Liquidsmooth lollipop, or, Slimkat 4.4)
Thanks guys, any help would be super appreciated,
Regards,
~ Dave
Click to expand...
Click to collapse
First of all and most important don't use rom manager! it causes more problems than anything else.The best way to install custom roms is to use Cwm,PhilZ or Twrp to install anything!
Flash superSU zip in recovery from here >> http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 << SuperSU forum here >> http://forum.xda-developers.com/showthread.php?t=1538053 << Technically you should not need to flash SuperSU because nearly all custom roms come with root built in so you could flash a custom recovery then wipe and flash your rom (but I can see you have been having problems doing that)
What you should do is
(1) Flash a custom recovery with Odin (Recommend PhilZ)
(2) Reboot to custom recovery
(3) Wipe phone
(4) Install custom rom (which is already rooted) from Ext SD card
(5) Reboot (If you get bootloop factory reset/ wipe cache
Also to note PhilZ recovery (which I think is better as more options and is based on Cwm) as a option to fix root in settings.
tallman43 said:
First of all and most important don't use rom manager! it causes more problems than anything else.The best way to install custom roms is to use Cwm,PhilZ or Twrp to install anything!
Flash superSU zip in recovery from here >> http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 << SuperSU forum here >> http://forum.xda-developers.com/showthread.php?t=1538053 << Technically you should not need to flash SuperSU because nearly all custom roms come with root built in so you could flash a custom recovery then wipe and flash your rom (but I can see you have been having problems doing that)
What you should do is
(1) Flash a custom recovery with Odin (Recommend PhilZ)
(2) Reboot to custom recovery
(3) Wipe phone
(4) Install custom rom (which is already rooted) from Ext SD card
(5) Reboot (If you get bootloop factory reset/ wipe cache
Also to note PhilZ recovery (which I think is better as more options and is based on Cwm) as a option to fix root in settings.
Click to expand...
Click to collapse
hi tallman, much appreciated for the reply
For some reason I couldnt get Philz Custom Recovery to work with odin, kept getting an error :/ . So I ended up trying TWRP, which worked, I booted into it then installed Liquidsmooth + gapps, all installed ok, but all up it was the same process you mentioned, which I greatly appreciate.
So running Liquidsmooth 5 now with TWRP recovery, though will likely give Philz recovery a shot down the track
Le Widget said:
hi tallman, much appreciated for the reply
For some reason I couldnt get Philz Custom Recovery to work with odin, kept getting an error :/ . So I ended up trying TWRP, which worked, I booted into it then installed Liquidsmooth + gapps, all installed ok, but all up it was the same process you mentioned, which I greatly appreciate.
So running Liquidsmooth 5 now with TWRP recovery, though will likely give Philz recovery a shot down the track
Click to expand...
Click to collapse
Good to hear it's working Yes it's worth persevering with PhilZ it's a good recovery although Twrp is not bad either:good: