Hi all.
Hope everyone is having a good day!
Lets start: in simple words, it appears I've got two CWM installed. Know it sounds crazy but this is how it looks.
I run Villain 2.4.2 with nynmphetamine 2.1.3 kernel and "some" CWMs
Previously I had also Villain but on CFRoot kernel that preloads a custom CWM
What I've done:
I tried to install CM7 "easy" way so installed ROM manager and when it asked me if I wanted to flash CWM with the newest one I pressed "yes" and stupidly overwrote it. Then downloaded CM7 and when ROM manager attempted to boot into CWM android logo with an expression mark appeared and the phone hung. I rebooted into recovery and it showed me I run CWM 4.0.0.2 (i think that's the custom from CFroot) but the ROM manager says I've got 4.0.1.5.
When I tried to install CM7 via 4.0.0.2 the installation itself went fine but the phone stucked on Samsung logo during post-instalation booting.
Could you give me an advice on how to sort this out? I mean to get properly set up kernel and CWM after some serious messing up
I'd be grateful for any help.
Cheers.
chalger
I dont know if its possible to have 2 CWMs (maybe app version is different), but this happens with CM7. You should wipe dalvik, factory reset, flash cm7 and boot. Phone will get stuck, shut down long pressing power, reboot in cwm and reflash (no wipe needed). CM7 should boot now.
I have been at this for 3 days any help would be great.
Anything installed runs until shutdown and then is gone after reboot - like it is restoring itself every time to CM7.
Can't run ADB becuase install of TGPS_Launcher.apk causes screen flicker cannot select anything to install on nook.
Goo manager -rebbot recovery - downloaded various roms- boots to CM7
Installed CWM - gone on reboot - boots to CM7
Tried reflashing variations of CM - istallation goes too quickly but says complete - but CM7 is back on reboot.
Tried AdamOutlers method looked to run fine - performed as expected - rebooted to CM7
Tried RayWaldo repart got green check mark - took sd out and it boots to CM7.
Tried to revert to stock BN - via SD and direct download - no dice.
Someone said reflash partitions 5, 6, 7 any suggestions on how to do that without adb. I'm not good with Linux but am willing to try if there are some instructions somewhere.
Getting desperate here...
I have the same problem since April. Still no solution. http://forum.xda-developers.com/showthread.php?t=1879942
Nevertheless, you can run Android from sdcard
niksnotes said:
I have been at this for 3 days any help would be great.
Anything installed runs until shutdown and then is gone after reboot - like it is restoring itself every time to CM7.
Can't run ADB becuase install of TGPS_Launcher.apk causes screen flicker cannot select anything to install on nook.
Goo manager -rebbot recovery - downloaded various roms- boots to CM7
Installed CWM - gone on reboot - boots to CM7
Tried reflashing variations of CM - istallation goes too quickly but says complete - but CM7 is back on reboot.
Tried AdamOutlers method looked to run fine - performed as expected - rebooted to CM7
Tried RayWaldo repart got green check mark - took sd out and it boots to CM7.
Tried to revert to stock BN - via SD and direct download - no dice.
Someone said reflash partitions 5, 6, 7 any suggestions on how to do that without adb. I'm not good with Linux but am willing to try if there are some instructions somewhere.
Getting desperate here...
Click to expand...
Click to collapse
You need to provide more details before anyone can help with suggestion: i.e., which version of CM7 do you have and which version of CWM (release no.? emmc or sd based?) you used to flash new CM, etc.
Hello dear community
This is my very first thread I am making on this website, so please pardon me if I am on the wrong page of this website.
Anyways, I'm more or less desperate. I saw a youtube tutorial on how to install Android 4.4 Kit Kat on a Samsung Galaxy Note N7000 and I heard I'd need root AND a custom recovery.
Because I'm a total newbie to this kind of stuff, I tried the very first thing I saw that had something to do with custom recovery, because I already had my phone rooted. So, I looked up a tutorial on youtube on how to install CWM custom recovery and ended up with installing it successfully, but now my phone is stuck in a bootloop. As I already mentioned, I am a newbie and therefore I am very desperate at the moment, you know.
The only thing I can do is go to Recovery Mode, but if I try to turn the phone on it gets stuck in a bootloop (It actually doesn't loop at all, it just freezes at the moment when the Samsung Galaxy Note logo appears and doesnt do anything after that.).
I think my problem is that I actually threw a new Kernel on my phone, because the video title says "How to install Kernel with CWM [...]"
I would be very very very very very grateful if anyone was kind enough to help me get out of this!
I really need help!
Thanks!
PS.
If this helps you help me:
This happened when I had Android 4.1.2 installed.
There's going to be 2 ways to get out of this:
1) Reinstall the stock firmware via Odin.
2) Install a custom rom via recovery.
Personally, I'd go with number 2 because a) you wanted to update anyway and b) if you have the right recovery and rom, it'll be easier as you can just put the files you need on an external SD card and install via the custom recovery. Now, not all recoveries are able to flash any file. Many times you need specific ones to install the newer android versions. So, if you are wanting to install something 4.4 based, then using a recovery that was made, say, last year, probably will not work well if at all.
Another thing to try first, is to wipe the cache and dalvik cache in recovery since you said you tried to install a kernel. It is always recommended to wipe these when installing (assuming you did pick a compatible kernel with what you were trying to install).
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:
Hello, i will try to be thorough.
BUT, i am a noob and didnt write down everything i did.
Have a I717 at&t note 1. with the 4.1.2 update originally OTA installed by keis.
I recently rooted it using Saferoot. it went well and i didnt see any problems. i flashed a custom rom and didnt like it so using clockworkmod recovery i went back to the 4.1.2. I then tried pac lollipop >pac_quicyatt_lp.beta-1.unofficial_20150327< i liked this rom but needed to flash Gapps.
This is where the trouble started. i didnt/dont know the proper procedure to flash the Gapps on top of or into the rom.
I first tried >gapps-5.0.x-20150404-minimal-edition-signed.zip< and it looked like it loaded correctly. but nothing appeared in the phone. the pac rom was still working well.
I then did more research and tried >gapps-lp-20150222-signed.zip< , again it looked like it loaded well but nothing showed up "in" the phone.
right here is where things got screwy. i had been using clorkworkmod for recovery and rebooting. and i think somewhere in developer settings i clicked something about how rebooting is handled.
because after trying to install the Gapps it went into Cyanogen recovery... and loops.
no matter what i do it goes back to cyanogen recovery.
I never knowingly installed cyanogen and dont know why it all of a sudden is going into cyanogen recovery over and over.
a list of things that may have bearing:
1. i tried reinstalling the pac rom. it loads and completes but it still just goes to recovery.
2. tried different ways of clearing cache and data wipes.
3. computer, kies, and odin 3.09 do not recognize phone.
4. have proper drivers on computer. phone was previously recognized by kies and cpu (4.1.2).
5. currently the only way to get anything into phone is by pulling sd card and reinstalling with info on it then using cyanogen recovery.
6. i have searched for about 11 hours and tried a bunch of things. but just restarts in cyanogen recovery
7. i was scared to fully try things i found that wernt specifically for the i717.
8. i could not find an original gingerbread rom. they all seemed fishy (needed downloaders. or ended in .zip.rar)
9. had backed up with clockworkmod and with titanium recovery (while in 4.1.2).
I dont know if i can reach the clockworkmod save through cyanogen recovery.... if so it seems like a great option.
10. at the bottom of the screen while loading rom is.... ---->>> E: cannot load volume /misc
11. only pac rom will successfully re-flash (even though it still just goes back to cyanogen). any other flash and it crashes halfway through.... i then restart and it just loops back to cyanogen recovery.
I searched here and tried the five recommended posts.
I could not try a lot of the "fixes" because the phone isnt recognized by cpu or odin (computer does beep when connected but doesnt show up anywhere).
Can you help me get back my phone please?
Randall
added
This is the only site i am asking for help on. I am willing to reply quickly and put in the time!
Thank you very much for reading this far.
Randall