[HELP] Attempted installing paranoid, resulted in always booting to CWM instead. - Galaxy S II Q&A, Help & Troubleshooting

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

Related

[Q] HELP: I cannot get vibrant to boot into CWM

I have successfully been able to root and install everything on my Mytouch4G just fine, however, when I tried to install my wife's Vibrant, I am stuck. Here is what I have done:
1) I rooted successfully using superoneclickv1.9.1
2) I installed ROM Manager and also downloaded the Auxora ROM to get ready to install
3) When I flash CWM recovery, it says current and latest recover is 2.5.1.2 (concern here that my mytouch says 3.0.2.4 - do different phones install differently with CWM?). When I look at all CWM recoveries I also notice there is two seemingly more current versions available 2.5.1.3 and 2.5.1.4. I have left it at .2 but wondering why all the versions.
4) When I reboot into recovery, I always get the stock recovery and have not been able to get CWM recovery so I am unable to flash my Auxora ROM. I ran update packages numerous times, and get a signature verification error. I have tried a recovery 3e patch that does not work either. I also gave a try at downloading and SDK, but received temp root errors (phone is already rooted).
After reading many posts, I cannot seem to get a direct answer on what I should do to get CWM to actually boot properly, so I can flash a ROM. Someone said to flash the stock JDK rom, but if I can't boot into recovery, how can I flash anything.
Any help would be greatly appreciated.
You need to get a program for your pc called odin to get back to stock. you can find that and instructions on how to use it if you search for the daily updated vibrant bible its GREAT
http://forum.xda-developers.com/showthread.php?t=849028
going to stock eclair heres a a great guide
So going back to stock eclair will then allow me to install CWM recovery then load roms?
Every once n a while I haft do the install packages thing twice before it gives me clockwork green
. Hope this helps.. o n btw u should look at some of the other roms in the bible before u try auxora
yes u should go back to stock eclair for every rom, in my opinion. Then after that do the 3 button combo and install packages and u will have to do it twice and then the green screen will kick in and ready to rock a new rom.
i hope this helps
What is your current firmware?
I see you posted over in the "NOOB GUIDE" thread, you should really try to root using the method posted there and not any one click root apps.
This should be the root method everyone uses:http://forum.xda-developers.com/showthread.php?t=723479
After root your phone recovery should be blue. Choose "reinstall packages" gives you green recovery(this may need to be repeated multiple times to work possibly including flashing CwMRecovery with ROM manager. I recently did it 5 times b4 i got green recovery)Once you access green recovery chose "apply sdcard:update.zip" go into advanced and choose "reboot recovery" This should give you red recovery. Do a nandroid backup and flash away. Good luck!
Another option you could do is to download SGS kernel flasher from the market and flash a voodoo injected kernel with that app. Then when you boot into recovery you will have red voodoo recovery and you can flash away.
Odin to stock the best way to flash a new rom
Sent from my SGH-T959 using XDA Premium App
jman531 said:
So going back to stock eclair will then allow me to install CWM recovery then load roms?
Click to expand...
Click to collapse
The stock 2.2 that Samsung distributed with their Kies tool has a recovery that checks signatures. Everything earlier does not check signatures. So either use something earlier to get CWM running, or use a ROM that doesn't have the stock 2.2 recovery in the first place, or mod your recovery using the method described in http://forum.xda-developers.com/showthread.php?t=833423
Using Odin to go back to stock Eclair between your flashes of modded roms has the benefit of taking care of this, and also can clear up left over bits and pieces that may interfere with the proper function of your new ROM.
ok, i followed the instructions and am back to eclair, however, whenever I install packages, it just reboots the phone, not even back into stock recovery. I use the 3 key method and get into recovery, run install packages, and the phone just boots back up...its like it isn't running the update.zip file...
UPD: When i load rom manager and try to reboot into recovery, it says the application superuser permissions has stopped unexpectedly and keeps force closing now....titanium backup wont run now either, my root permissions seem whacked after going back to eclair?
UPD2: I followed instructions to unroot and reroot here: http://forum.xda-developers.com/showthread.php?t=739300
It removed superuser, then added it back again, but I still get the unexpected error and it appears my root is not in place. I am back to eclair, and now need a certain way to get my root fixed, so I can try and flash CWM recovery. Without root working, it is not letting me. My wife hates me now for doing this to her phone, so those of you that are married, I would appreciate your assistance to get back on her good side...before Mother's day...please? =)
Ok, thanks for all the help, however, I am really back where I started. I can only get stock recovery, and for the life of me, cannot get CW recovery to load. I used ODIN to go back to eclair on the vibrant, have a good root on the phone now, and no matter how many times i reinstall packages i cannot get clockworkmod recovery to load, ever. Any more thoughts out there?
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
starkiller86 said:
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
Click to expand...
Click to collapse
thanks...It is rooted, but not sure about busybox...the stock recovery is 2e now since I went back to eclair, so not sure i should follow that link as it talks about modifying 3e and making it backwards compatable. I did use that process before I went back to eclair, and it didn't work for me. I have uninstalled rom manager, and reinstalled...and it is different in that it shows a flashed recovery 2.5.1.2, and never asks me for my phone type anymore...it used to ask me and i had to select vibrant....is the recovery supposed to be 2.5.1.2? when I show all recoveries it lists .1, .2, .3, .4 so wondering if I should use .3 or .4...why does it stay at .2?
starkiller86 said:
I had this trouble a few months back. Things to check before going into recovery:
You gotta have root access.
Make sure you have debugging on
Install busybox FIRST
Try uninstalling Rom manager and reinstalling the latest version.
apply the recovery for vibrant and let it boot into recovery.
When it boots into recovery Don't try to install packages yet. Just reboot.
Look here for the files:
http://forum.xda-developers.com/showthread.php?t=833423&highlight=3e+recovery
When it boots up push the update.zip to the sd card on the phone, not the external card.
Run the script and it should reboot back into recovery.
You should now be able to install packages.
This way has always worked for me.
Click to expand...
Click to collapse
OK>>> I GOT IT... Thanks to everyone who helped...Here is what was needed:
1) Install ODIN, install back to eclair
2) uninstall ROM Manager, reinstall
3) I needed to select the 2.5.1.2 recovery from the list again (this was important as it somehow knew of the previous load, but files were missing, or something was just wrong.) It finally loaded properly, and asked for phone type again, so selected vibrant
4) I rebooted into recovery, and instead of install packages, i rebooted once, as starkiller suggested
5) After reboot, went back into recovery from rom manager, and this time installed updates, and it showed that it replaced the recovery with CWM.
6) It rebooted into stock recovery however, so I once again selected install updates, and it went right into CWM recovery, and now I am flashing happy!!!
Thanks again everyone...this was soooooo different than my mytouch4g!
If you have the Kies update of Froyo, the 3e mod will sometimes not work. I've gotten to CWM though , but its best to downgrade then flash a ROM from there.
I just wanted to bump this thread because it really helped me.
I've messed around with numerous android phones, and I've never had thie issues I've had with this phone getting into recovery to flash ROMs
Thank you!

[SOLVED] Every ROM I flash soft bricks device

Any ideas why this could happen?
What I do everytime:
Flash XXLPB with ODIN 1.85, root with CF-Root v5.2 CWM, reboot, all fine.
Then I flash for ex. Carbon ROM Nighlty, GAPPS, reboot and it's stuck at triangle screen. Can't go to recovery, only download mode works.
I also tried "old" Carbon 1.8, and even other ROMS that worked like a charm some time ago.
All started when I tried yesterday to flash 4.3 Carbon nightly over 4.2.2 (1.8) Carbon w/o wiping...
Please help as for now I'm stuck with my 3310 xD
Back to stock via Odin/download mode (you don't really have another option), make sure you do a wipe/factory reset, try flashing the rom again.
I tried 4-5 times, and always the same is coming out! Is there any minimum requirement for flashing let's say 4.2.2? Shouldn't matter, right?
It shouldn't matter but we see cases on here all the time where for whatever reason, Odin flashes don't take on the first/second.....eighth (as an example), and for whatever reason, the ninth flash works. In other words, you need to persevere. Try different stock roms for your carrier (different Android versions, not just the recent ones - but don't use 4.0.4 in case you forget when you re-root your phone & do a wipe which will brick your phone). And keep trying. There's no easy fix for these situations unfortunately (search for Hopper8's 'Odin won't flash' thread, there's stuff in that thread you can try).
Actually the ODIN flash of the stock rom always works. But then I flash a rom through CWM and it bricks...
Is there a way to flash those roms with ODIN?
No. Almost all custom roms are CWM flashable.
OK...What I suggest you do is this...
*Clean install of stock with wipe/factory reset.
*Root your phone by flashing a custom kernel like PhilZ or Siyah (or Dorimanx).
*Do not flash a separate CWM or any other mod after you've rooted the phone.
*Read the first page of the thread devoted to the rom you want to flash very carefully. Flash the rom with CWM/follow the instructions to the letter (do not use Rom Manager or the CWM app from your homescreen; boot the phone into recovery & flash that way).
If you're seeing specific errors in CWM having done those steps (And do them again now even if you've done them previously), you need to tell us exactly what's going wrong in CWM. We're not mindreaders.
Edit - Your phone isn't bricked. Bricked phones don't boot. At all.
Thanks for the detailed answer.
Actually that's what I'm doing every time!
I'm trying to install 4.3 nightly build of carbon
I tried also stable build which was working well before...
There are no specific instructions, but I think it's pretty much standard:
1. Wipe Data/Factory Reset
2. Flash zip
3. Flash GAPPS
4. Wipe Dalvik Cache
5. Reboot
Thanks!
EDIT: After flashing the custom rom the phone doesn't boot, it gets stuck at kernel panic upload mode. Once I managed to get into CWM but there I couldn't perform any action, it was freezed.
Hi Again,
it looks like everything worked fine. Maybe I had a strange version, or the CWM was to old (5).
Now I could flash what I wanted and it's not stuck at boot anymore!
Thanks for the help!
Perseverance is a beautiful thing.

[Q] Made mistake while flashing a custom ROM. Need help!

Warning: I'm a total n00b. I'm afraid I permanently wrecked my phone and I want to know if I can get it back to normal again.
Here is a step by step of what I think happened:
I tried flashing CyanogenMod 10.1 by using the ClockWork ROM Manager. I went to the Download ROM section of ROM Manager and found Cyanogen 10.1. It gave me the prompt "Backup existing ROM" and "Wipe Data and Cache," and I selected both. My phone started downloading the ROM. After it finished downloading the recovery menu popped up and I pressed Reboot System Now which I think was my first mistake.
It rebooted into Samsung's TouchWiz, not CyanogenMod, and asked me to sign into my Google account, which I did. I knew I had made a mistake so I went back to the ClockWork Recovery menu to start over. I made a backup of my ROM (which at this point was not even useful due to my first attempt), wiped the data/Factory Reset, wiped the cache, and wiped the Dalvik Cache. Then I tried to install the CyanogenMod ROM by going to "choose zip from sd card," however I couldn't find any ROM saved! I then tried to restore from a safe point, but no files could be found to restore from. At this point I panicked and hit "reboot system now" not knowing what it would do.
It rebooted into TouchWiz again, except this time with zero of my contacts, apps, anything. And it kept freezing every couple of seconds. I tried booting into the stock recovery image but instead of the menu it asked me if I was sure I wanted to download a custom OS. First I said no and it just froze again. Then I said yes and it started downloading something. My phone currently has the green android in the middle, and up top it says Odin Mode/Custom Binary Download: No/Current Binary: Samsung Official. It hasn't changed in about 20 minutes.
At this point I just want to get out of the jam I created and hopefully get some files back, especially the photos I have saved. Can anyone help me?
ps sorry for the long post
Well the good news is that as long as your phone is booting all the way into ANY OS, you're doing okay. Here at XDA, the ROM MANAGER method is frowned upon. From this point, your best (safest) bet is a clean slate, and I think that the best way for you to get there is to ODIN to stock touchwiz jellybean 4.1.2 (UCMD8) -then start the root - ROM process over again.
Odin 1.85 or 3.07 will both work
the UCMD8 firmware can be found in creepyncrawly's download repository
---------- Post added at 07:35 AM ---------- Previous post was at 07:23 AM ----------
gschmutz said:
...I tried booting into the stock recovery image but instead of the menu it asked me if I was sure I wanted to download a custom OS. First I said no and it just froze again. Then I said yes and it started downloading something. My phone currently has the green android in the middle, and up top it says Odin Mode/Custom Binary Download: No/Current Binary: Samsung Official. It hasn't changed in about 20 minutes...
Click to expand...
Click to collapse
What you describe here indicates that you booted into download mode, not recovery. Although it seems as though the phone is actively downloading something, it's just entered a ready-to-receive mode until you actively tell ODIN to send data (from a PC).
the keypress to get into download mode or recovery:
download mode: usb cable PLUGGED IN; vol- & vol+ & power --> until the prompt appears, then release and follow the instructions on screen
recovery: usb cable UNPLUGGED; vol- & vol+ & power --> until bootlogo appears, then release, and the phone should continue to boot into recovery.
---------- Post added at 07:43 AM ---------- Previous post was at 07:35 AM ----------
Once you're comfotably back to stock, this is the easiest way to get from stock to custom recovery on the i777:
Framaroot <-- tool to establish root-access to the device
Mobile Odin Lite <-- tool that uses root-access to install...
Custom Kernel <-- a custom kernel (there are many available) installed primarily to provide cwm recovery, but are also commonly used to:
-install a different ROM
-provide additional functionality to the existing ROM
-backup your ROM install
-install a different kernel
-flash cleanup scripts
-and many many other things
The ROMs are usually packaged with their own kernels, so the kernel used above only remains in place until another ROM is flashed, which will overwrite the existing recovery with one specifically designed for the ROM flashed.
This guide will walk you through the steps, but read through the thread carefully to be sure that you understand everything before leaping.
-happy flashing
Great thank you so much! I will try to flash Jelly Bean when I get home from work. You lifted a weight from my chest.
Here's another update before I go any further. Late last night my phone stopped its bootloader cycle and seemed to be stably running TouchWiz on 4.1.2, and it is still rooted. It has been running stable all day. Do you think I still need to flash stock TouchWiz using ODIN before trying anything with my phone?
gschmutz said:
...running TouchWiz on 4.1.2, and it is still rooted. It has been running stable all day. Do you think I still need to flash stock TouchWiz using ODIN before trying anything with my phone?
Click to expand...
Click to collapse
probably not, I'm glad to hear that things have stabilised.
From here, my strongest recommendation is that whenever you flash firmware, do some house-cleaning:
-either run a rom-wipe script before-hand
OR (at least)
-factory reset
-format /system

I9300 Internationl ROM/Root Issues...

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:

No OS installed! Are you sure you wish to reboot?

Hi all
How exciting it is to see that so many people are so involved in improving or fixing their mobile devices.
I got some sort of a virus on my Samsung Galaxy S3 so decided to try to wipe it clean and load a more up-to-date version of Android on it. It had 4.3.?. On a Windows 7 PC, I downloaded the Skipsoft Unified Android Toolkit (version 1.4.5). I think now I didn't need to but probably succeeded in rooting my S3 with Kingo ROOT.
Next, using the toolkit and Odin, I think I succeeded in flashing the recovery-twrp-2.7.1.0-i9300.tar custom recovery.
My phone would only boot up with the stock Android.
I took me a while before I learnt about entering the recovery mode by holding the volume up, home and power-on buttons simulateously.
In the recovery mode, I used Wipe, Advanced, ticked all of the boxes and wiped everything on the phone.
Then, using the toolkit and Odin again, I flashed the same recovery-twrp-2.7.1.0-i9300.tar custom recovery I'd flashed before.
I still can't boot my phone. If I choose Reboot from twrp (v2.7.1.0) and then either System or Recovery, I just get, "No OS installed! Are you sure you wish to reboot?"
I can still enter either download or recovery modes but the latter is something of a hit and miss affair.
Using File Manager in the twrp I can see lots of files and directories so guess I managed to flash something.
Also, using Terminal Command I see that my prompt is a "#"so think I'm still rooted.
I know something about Unix and programming mainframe computers but am not an expert with mobile devices. I'd be so grateful if someone could please advise me as to what to do?
Mike
You wiped system partition ;-;
If you want stock rom you need to flash the stock rom by odin.
I recommend you to install a custom rom like Temasek or CM13, it's real easy just flash the zip.
Haha yes^ this guy is right
You might have to flash stock rom if you somehow wiped efs, most of the time custom roms doesn't include efs with them
Turga said:
You wiped system partition ;-;
If you want stock rom you need to flash the stock rom by odin.
I recommend you to install a custom rom like Temasek or CM13, it's real easy just flash the zip.
Click to expand...
Click to collapse
Thanks for your response, Turga and snkmv, below. I didn't know what efs was so looked it up on the net and found this worrying but expert explanation from ryanrazer and Rukbat in androidcentral ( http://forums.androidcentral.com/as...erstanding-cwm-backups-efs-partition-etc.html )
In twrp's recovery mode on my phone and using File Manager, I see that the directory /efs is empty (all files are shown in File Manager, right, including invisible files?)
I'd prefer to try to flash a custom ROM which includes efs rather than the stock ROM. Do Temasek or CM13 include efs or does another, reliable custom ROM?
Thanks again folks
Mike

Categories

Resources