Hello,
So, I have gone cross-eyed trying to sort out how to Flash PAC-rom to my SGP 5.0.
I've manged to get Clockworkmod working on it and I am running Clockworkmod 5.x.x.x (seeing as there is no official support for the G70). When I try installing the latest PAC-rom nightly I get a "signature verification failed". So, I did some more digging and found that I should try installing CM9 first and then try installing PAC-rom. I did that and I still get the same verification error.
So... I am lost. Any guidance from the community would be greatly appreciated, also... I am very green so please use small words and basically treat me like an idiot.
Thanks,
TF
Here is a pic of the error I am getting.
I've tried Superoneclick to root my device, that is were this error came from. Then I tried Framaroot, I get the same error when using Clockworkmod.
Thanks,
TF
TirrexFalcon said:
Here is a pic of the error I am getting.
I've tried Superoneclick to root my device, that is were this error came from. Then I tried Framaroot, I get the same error when using Clockworkmod.
Thanks,
TF
Click to expand...
Click to collapse
I'm not 100% on this but I think the main point of having CWM is that it doesn't do "signature verification". That way you can flash stuff that not officially "signed".
Here is the procedure for installing ROMS if your on Gingerbread.
Download an Odin flashable kernel, either Entropy's for US or Rumirand's for INT.
Flash it
If you are going to flash jellybean make sure you wipe system along with the normal wipes.
Flash your ROM in CWM.
Now what!?
So... I downloaded Entropy's (see Link below) .tar kernel and used Odin to flash it.
http://forum.xda-developers.com/showthread.php?t=1445840
After that finished I was able to Flash the PAC-Rom (pac_venturi_nightly-20131007.zip), followed by the Gapps Core (9-19_Gapps_Core_4.3_signed.zip) and lastly the Kernel (cm-10.2-USA-Kernel-REV2.zip).
Unfortunately, something went pear-shaped because I don't have the Play Store app so I can't install Clockworkmod (at least the way I know how anyway) so I can't try to reinstall the GApps core to get the Play store. I suspect that I am doing something horribly wrong and have managed to make this harder then it should be. Please help.
Thanks,
TF
TirrexFalcon said:
So... I downloaded Entropy's (see Link below) .tar kernel and used Odin to flash it.
http://forum.xda-developers.com/showthread.php?t=1445840
After that finished I was able to Flash the PAC-Rom (pac_venturi_nightly-20131007.zip), followed by the Gapps Core (9-19_Gapps_Core_4.3_signed.zip) and lastly the Kernel (cm-10.2-USA-Kernel-REV2.zip).
Unfortunately, something went pear-shaped because I don't have the Play Store app so I can't install Clockworkmod (at least the way I know how anyway) so I can't try to reinstall the GApps core to get the Play store. I suspect that I am doing something horribly wrong and have managed to make this harder then it should be. Please help.
Thanks,
TF
Click to expand...
Click to collapse
Rom Manager and ClockworkMod are 2 different things. Entrophy's kernel has ClockworkMod in it. Rom Manager does not work for the galaxy player 5.0, afaik. If you don't have the Play Store then there is something wrong with Gapps. Please read the PAC dev's thread for instructions on flashing.
Meticulus said:
Rom Manager and ClockworkMod are 2 different things. Entrophy's kernel has ClockworkMod in it. Rom Manager does not work for the galaxy player 5.0, afaik. If you don't have the Play Store then there is something wrong with Gapps. Please read the PAC dev's thread for instructions on flashing.
Click to expand...
Click to collapse
Well, to the best of my knowledge... Rom Manager was what I installed from the play store when I searched for Clockworkmod. Unfortunately neither survived the Flashing of Pac-rom so I can't attempt a reinstall of the GApps zip like I did the last time. I am still digging through the Dev forum so see if anything about how to reinstalling Gapps, but so far no luck. I suspect I'll need to find the ROM Manager apk and install it manually so that I can get this to work again.
Thanks,
Matt
TirrexFalcon said:
Well, to the best of my knowledge... Rom Manager was what I installed from the play store when I searched for Clockworkmod. Unfortunately neither survived the Flashing of Pac-rom so I can't attempt a reinstall of the GApps zip like I did the last time. I am still digging through the Dev forum so see if anything about how to reinstalling Gapps, but so far no luck. I suspect I'll need to find the ROM Manager apk and install it manually so that I can get this to work again.
Thanks,
Matt
Click to expand...
Click to collapse
DO NOT use ROM manager. It is not compatible with the Galaxy Players and you could end up bricking your device. If you are currently running PAC, you can get into clockworkmod using the reboot -> recovery option. From here you can flash gapps.
iurnait said:
DO NOT use ROM manager. It is not compatible with the Galaxy Players and you could end up bricking your device. If you are currently running PAC, you can get into clockworkmod using the reboot -> recovery option. From here you can flash gapps.
Click to expand...
Click to collapse
Whoops... well.... ummmm.... I did install ROM Manager from an APK and it says that its Recovery Setup is ClockworkMod 5.x.x.x. It seemed to work just fine and I was able to re-flash the GApps zip and get the Play Store back. Just lucky I guess?
Somethings to mention
I am currently running the *Build-1_20131006-090046 of PAC-Rom.
The OTA Rom Updates says that the "Server Is Borked or Tyler Broke Something".
I've tried putting an SD card in the expansion slot but it never comes up. I am going to boot into Linux today and try wiping the card and see if the SGP 5 will accept it and format it for use. Right now all it does is crash out when I try to view the statistics...the error given is "Unfortunately, Settings has stopped. Blame Tyler.".
And sometimes when I come out of an app the desktops are all blank, no icons or clock anywhere. I have to either launch another app of go to the drawer for things to come back.
Sorry if I am being a pain, I truly wish to learn and be helpful... I am just really green at the moment.
Thanks,
TF
Meticulus said:
Here is the procedure for installing ROMS if your on Gingerbread.
3. If you are going to flash jellybean make sure you wipe system along with the normal wipes
Click to expand...
Click to collapse
EDIT: Some say that CM9 must be installed before jellybean. I remember their being an issue where the gp5's system partition was not big enough and some accomidation had to be made....
iurnait said:
DO NOT use ROM manager. It is not compatible with the Galaxy Players and you could end up bricking your device. If you are currently running PAC, you can get into clockworkmod using the reboot -> recovery option. From here you can flash gapps.
Click to expand...
Click to collapse
:laugh:
I think I figured something out. I did install ROM Manager, but somehow I had also installed ClockworkMod. So, when I rebooted into recovery I was actually booting into ClockworkMod thus "doing it right" but going about it all wrong.
So I have since managed to flash my SGP 5.0 back to FacSpec so I am ready to try again... now that I am a little smarter... I hope.
Thanks,
TF
Related
Hey all,
I'm very new to Cyanogen, so sorry if this is a very n00b question.
The ROM Manager doesn't appear to work. It keeps telling me I'm not running ClockWorkMod recovery, and cannot connect to the web to download. I purchased the premium version thinking it would solve this (as well as to support the dev), but no luck. Is it just an issue with the nightlies not capable of handling ROM manager yet, or is it a setting of some sort that I'm neglecting? It's not a huge deal, but it looks like such a nice, simple way to stay up-to-date with the nightly builds as opposed to updating through CWM, wiping, etc.
I saw a post mentioning to go into developer tools and enable root access. The closest I found was in settings and I allowed apps and ADB root access, but this didn't help.
Any suggestions would be greatly appreciated, thanks!
I'm a bit confused, Why do you require ROM manager? The CWM that is built in with the ICS Kang releases should be doing everything that is required, then again, your reply would matter.
I think I am having the same issue. When I try to Flash ClockworkMod Touch in Rom Manager it keeps telling me I need to first install ClockworkMod Recovery even though I have Recovery 5.5.0.4 currently installed. It did the same thing when I had Recovery 4.0.0.4 installed.
I even tried to "Flash ClockworkMod Recovery" (First option in ROM Manager) and it does nothing.
Any ideas?
BEcause the same menu is in the CWM recovery lol
I'm following one of the threads that updates the kang build every 3 days, and as opposed to having to boot through CWM, wipe, install, then re-install apps and replace widgets, I thought I could update through ROM Manager instead.
It sounds like Sn0warmy and I are having similar issues.
From what I've heard the ROM Manager doesn't really work for the tab yet. If you want to update without replacing all your apps you can just flash the zip file in CWM without doing a wipe. If it causes problems then you could do a wipe & reflash afterwards.
Dolfan058 said:
I'm following one of the threads that updates the kang build every 3 days, and as opposed to having to boot through CWM, wipe, install, then re-install apps and replace widgets, I thought I could update through ROM Manager instead.
It sounds like Sn0warmy and I are having similar issues.
Click to expand...
Click to collapse
ROM manager works but it's wonky on the ICS kangs. It doesn't do anything that you can't already do in recovery, so there's no real advantage anyways. Oh, and don't use ROM manager to install a new recovery, and CWR touch doesn't work for the GT10.
^You saved me the trouble of insisting Why thank you good sir.
Thanks for the replies. I'll keep updating through CWM.
Coffeebeans, obviously I'm following your thread (thanks for the good work!) and I tried flashing over once but I got a ton of process media FCs so I figured wiping was the best way to go and have done so ever since. Probably should invest in titanium backup at this point so I don't have to reinstall from market everytime I wipe.
Thanks again for the help y'all.
It worked once with 4/17 build of CM9. After that, it has never worked again. It boots into recovery and pretends its flashing, but stops half a second later and restarts.
Something odd happened today when I tried to update. It rebooted and phone locked up and screen went black. I took out the battery and put it back in then held up and power to go into CWM. All of a sudden Rom Manager took over and flashed the rom as well as the additional zips successfully and rebooted. Everything works.
CWM tries to flash from /emmc. Rom Manager tries to flash from /sdcard and fails. It may be due to the swapped mount points on CM9. in CWM they are still swapped, even if you check the use internal storage box and everything shows up properly in CM9.
First of all, I want to thank everyone working on the CM7, CM9, CM10, SGT7, TWRP, CWM projects for the Nook Tablet. I've really been enjoying trying different ROMs on my Nook Tablet.
I started with CM7, and it ran pretty well. I also tried the CM9 (NX-Fire?) port, and I liked it as well.
I have been using the SGT7+CM10+Cherry Picks and it has been fine up to the 27/9 release. I cannot run anything higher than this on my NT.
I have tried CWM (up to 6.0.1.2) and TWRP (up to 2.2.2.0) to flash the newer ROMS, but the ROMS will not boot. The screen blanks, and after a time, it goes back to the boot screen.
I also can't seem to use the CWM 6.0.1.5 or TWRP 2.3.1.1 from the SGT7+CM10 thread.
I know I have the 16GB Nook Tablet. I have repartitioned the userspace, as mentioned in other threads. I can't help but feel like I'm missing a step somewhere.
Presently, my NT is running TWRP 2.2.20 and SGT7+CM10+Cherry Picks 27/9. Any one have any hints? A thread on the boards I have missed? Any help would be appreciated.
Again, thanks for all the hard work!!
Hi,
TWRP 2.2.2 has a flashing bug that causes updating recovery with current script to fail.
You must manually update to newer version and after that recovery update packages will function as descripted
Moved. Questions belong in the Q&A section.
Thanks
AvRS
demetris_I said:
Hi,
TWRP 2.2.2 has a flashing bug that causes updating recovery with current script to fail.
You must manually update to newer version and after that recovery update packages will function as descripted
Click to expand...
Click to collapse
Thanks! I'll try that this weekend. I knew I was missing something.
demetris_I said:
Hi,
TWRP 2.2.2 has a flashing bug that causes updating recovery with current script to fail.
You must manually update to newer version and after that recovery update packages will function as descripted
Click to expand...
Click to collapse
Sorry, but how does one manually update a recovery? I've tried flashing the newer TWRP from CWM as well (from an older version of CWM), and while the flash doesn't fail, it won't let me boot into TWRP, and the new CWM crashes before I can do anything. I've also tried flashing the recovery from fastboot, but I get a "bad boot magic" error when I try to boot.
Just flashed couple of days ago: pretty nice ROM
Besides annoying "SD card unmounting" problem I found that B&N Nook app does not work, it just keeps restarting, some error message shows up but goes away so quickly I can't read it. I wiped before I installed the ROM and reinstalling the app didn't help.
Please post a link to cwm 6 please, i need to install cm10 without it freezing and crashing
Sent from my Nook Tablet using xda app-developers app
jnorrisman said:
Please post a link to cwm 6 please, i need to install cm10 without it freezing and crashing
Sent from my Nook Tablet using xda app-developers app
Click to expand...
Click to collapse
There is a search function on here...
Sent from my NOOK Tablet running CM10
jnorrisman said:
Please post a link to cwm 6 please, i need to install cm10 without it freezing and crashing
Sent from my Nook Tablet using xda app-developers app
Click to expand...
Click to collapse
The OP in the developers section has links to both CWM and TWRP for your use. Remember, SEARCH is your FRIEND!
play store/goomanager closing
First let me say this rom is awesome! I had no idea my nook could run this smoothly. The only problem I seem to have is that on the newest build(10/25) both playstore and goo manager will open then close. I have tried clearing the app cache, re flashing rom and gapps, full wipes then reflash. I also tried reflashing the newest gapps without success. The 10/12 build works with both play store and goo manager. I am using the 10/12 build now so no worries if it can't be fixed. Again thanks for the time and effort on an awesome rom:good:
edit: I am using the latest twrp for my recovery (also awesome). the tablet is the 16gb version
Same problem as OP, latest SGT7 not loading
I am having the exact same problem as Byron and Spurious. I've really enjoyed this series of ROMs up until the last couple, which give the same symptoms as described in the OP - the ROMs will appear to load up to a certain point, then the device reboots. For me, the the device will load up to a seemingly random point -- sometimes it will reboot itself during the boot animation, and once it got all the way to the point where it starts updating the applications. But it never actually finishes booting up before it reboots itself.
In addition, the latest CWM and TWRP do not work for me. TWRP does not come up at all, and sometimes CWM will come up and I can move around the menus for a few seconds, then it hangs. It happens whether they were flashed via fastboot or SD, I've tried every combination. I can fastboot back to TWRP 2221 or CWM 6013 and they work fine.
I've been keeping my NT (16G) updated with the latest builds since early ICS and everything has worked as described up until now. I follow all instructions to the letter as regards to wiping, etc. so I don't think I'm doing anything wrong.
Is anybody else having the same issue with these latest ROMs? Byron, Spurious - did you get yours sorted? Could it be a hardware issue?
jarvz said:
I am having the exact same problem as Byron and Spurious. I've really enjoyed this series of ROMs up until the last couple, which give the same symptoms as described in the OP - the ROMs will appear to load up to a certain point, then the device reboots. For me, the the device will load up to a seemingly random point -- sometimes it will reboot itself during the boot animation, and once it got all the way to the point where it starts updating the applications. But it never actually finishes booting up before it reboots itself.
In addition, the latest CWM and TWRP do not work for me. TWRP does not come up at all, and sometimes CWM will come up and I can move around the menus for a few seconds, then it hangs. It happens whether they were flashed via fastboot or SD, I've tried every combination. I can fastboot back to TWRP 2221 or CWM 6013 and they work fine.
I've been keeping my NT (16G) updated with the latest builds since early ICS and everything has worked as described up until now. I follow all instructions to the letter as regards to wiping, etc. so I don't think I'm doing anything wrong.
Is anybody else having the same issue with these latest ROMs? Byron, Spurious - did you get yours sorted? Could it be a hardware issue?
Click to expand...
Click to collapse
Sort of. I figured out what I was doing wrong flashing the recovery from fastboot (you apparently have to extract the .img file from the zip) but was still having the exact same issues with CWM and TWRP as you. I've managed to get a newer version of CWM installed without it hanging by using the 5 touch enabled one from here. Using this I still have the same issues with the meghd00t rom going into a bootloop though.
I noticed OP said he has repartitioned his Nook, and I have as well. I wonder if this could be causing problems, have you done this as well, jarvz? Does anyone else have any input about if repartitioning could effect this?
spurious_access said:
Sort of. I figured out what I was doing wrong flashing the recovery from fastboot (you apparently have to extract the .img file from the zip) but was still having the exact same issues with CWM and TWRP as you. I've managed to get a newer version of CWM installed without it hanging by using the 5 touch enabled one from here. Using this I still have the same issues with the meghd00t rom going into a bootloop though.
I noticed OP said he has repartitioned his Nook, and I have as well. I wonder if this could be causing problems, have you done this as well, jarvz? Does anyone else have any input about if repartitioning could effect this?
Click to expand...
Click to collapse
Yes I have repartitioned mine as well, so that must be it. I was hesitant to go to the 5-touch because it was indicated in the thread that there was no way back after you do the firmware update, and so far there is only one rom that worked with the new firmware, so I didn't want to take a chance.
At least I'm pretty sure I'm not doing anything wrong, lol.
jarvz said:
I was hesitant to go to the 5-touch because it was indicated in the thread that there was no way back after you do the firmware update, and so far there is only one rom that worked with the new firmware, so I didn't want to take a chance.
At least I'm pretty sure I'm not doing anything wrong, lol.
Click to expand...
Click to collapse
Yeah, I don't have the new touch firmware installed either. CWM worked fine, though TWRP didn't seem to work properly (maybe it needs the new touch firmware?).
Do you know if there is any mention of re-partitioning causing an issue? I looked in the rom dev thread but didn't notice anything. I guess one of us who are seeing this issue could post there to see if anyone knows what could be causing this.
I finally got it to work. My PC is running Ubuntu, so YMMV.
Here is what I did:
1. Used "gparted" to create 2GB FAT32 partition that is bootable.
2. Used the instructions in the this thread thread to create a bootable SD disk that boots into CWM 6.0.1.2.
3. CWM 6.0.1.5 just doesn't seem to work on my Nook Tablet. So, I downloaded CWM 6.0.1.3 from here
4. I downloaded the latest ROM here
5. Downloaded the latest gapps: here
6. Copied the CWM, ROM, and gapps to the SD disk.
7. Inserted the SD and booted the Nook Tablet.
8. On first boot, it boots to CWM 6.0.1.2, so I flashed the CWM 6.0.1.3, and rebooted.
9. This time it boots to Cyanoboot, so I entered the boot menu and selected EMMC Recovery.
10. From CWM 6.0.1.3, I formatted /storage, and did a factory wipe. (I didn't format /storage the first time, and the wireless would not come up.)
11. Installed ROM from SD card.
12. Installed gapps from SD card.
13. Rebooted, this time letting cyanoboot boot from EMMC.
14. Profit!
I haven't tried 6.0.1.4 to see if that would work.
Here's the deal:
I rooted my phone a long time ago, and have been using CM since ICS. Mostly nightlies.
A few weeks ago I decided installing a Carbon nightly (4.3), and everything went smooth as usual.
Then new nightly came, so I decided flashing it. (Dirty flash, but it's that way from what I read in the Carbon thread)
The thing is, my phone boots up correctly, but I can't get into recovery mode. Whenever I try booting recovery mode, the logo appears, then the screen flashes gray. I have tried both the advanced reboot menu, the button combo, and ROM Man...jk
I think something might be wrong with the recovery included in the kernel. If that's the case, would it be OK to flash just a new kernel or do I have to reflash the whole thing?
I have already seen some guides on flashing kernels with mobile ODIN, but they're either ancient or for another model. Also, I don't know if that's the right thing to do under this situation.
I'd appreciate if someone pointed me in the right direction. I don't wanna frak up my phone.
You can install a kernel to see if that will solve the issue, but as far as I can see, the Carbon devs do not provide a stand alone kernel for their rom. You could use AJK or one of the other kernels though. Or you could just reinstall the rom to see if it would clear up the problem.
Or, you could extract the zImage from the full rom and use Mobile Odin.
I didnt want to create a new thread for this and get yelled at.. so I am asking the question here:
I had to do the ODIN method and returned my phone from ShoStock 3 to Stock Gingerbread, because for some reason my phone was getting stuck at the "samsung galaxy s2" boot screen.
So I am back on Stock Gingerbreak Rom and trying to install ClockWork Mod Recovery, so that I can restore the backup of ShoStock that I had created.
I am doing the Mobile Odin Lite method and I downloaded the i777 kernel. When I try to install it, I boot in the Android System Recovery (3e) and get the following errors:
Installing package...
Finding Package...
Verifying Update Package...
E: failed to verify whole-file signature
E: signature verification failed.
Before I get yelled at, I searched google and came up with the solution -- all of which say that the issue can be easily fixed by toggling the setting in ClockWork Mod Recovery Mode, but I have to install it first, and whenever I try to install it, I get the above error.
Can someone help please?
jjack0310 said:
I didnt want to create a new thread for this and get yelled at.. so I am asking the question here:
I had to do the ODIN method and returned my phone from ShoStock 3 to Stock Gingerbread, because for some reason my phone was getting stuck at the "samsung galaxy s2" boot screen.
So I am back on Stock Gingerbreak Rom and trying to install ClockWork Mod Recovery, so that I can restore the backup of ShoStock that I had created.
I am doing the Mobile Odin Lite method and I downloaded the i777 kernel. When I try to install it, I boot in the Android System Recovery (3e) and get the following errors:
Installing package...
Finding Package...
Verifying Update Package...
E: failed to verify whole-file signature
E: signature verification failed.
Before I get yelled at, I searched google and came up with the solution -- all of which say that the issue can be easily fixed by toggling the setting in ClockWork Mod Recovery Mode, but I have to install it first, and whenever I try to install it, I get the above error.
Can someone help please?
Click to expand...
Click to collapse
3e recovery is the stock recovery. It means you have not installed a custom kernel yet. Please look at the links in my signature and use the guide information there, which will help you understand what you need to do to install mobile odin lite and then install a custom kernel.
Also, remember that you will need to have the correct version of ClockworkMod Recovery to restore your backup. If the backup and the version of CWM recovery are not compatible, it will not restore.
If you have questions, ask them here, but be aware, I only come on line usually two or three times a day to check the forums.
creepyncrawly said:
3e recovery is the stock recovery. It means you have not installed a custom kernel yet. Please look at the links in my signature and use the guide information there, which will help you understand what you need to do to install mobile odin lite and then install a custom kernel.
Also, remember that you will need to have the correct version of ClockworkMod Recovery to restore your backup. If the backup and the version of CWM recovery are not compatible, it will not restore.
If you have questions, ask them here, but be aware, I only come on line usually two or three times a day to check the forums.
Click to expand...
Click to collapse
I followed Step 3a on this post: http://forum.xda-developers.com/showthread.php?p=18576627#post18576627
Unfortunately, for some reason, ODIN Lite was not recognizing DD_03042012.zip file. So I went with Siyah and downloaded the TAR file used ODIN to get the clockwork mod. It worked.
Now the problem is I cant restore my backup. I know the same backup has worked before, not it is giving me an error "Error while restoring /system". wth!
I dont remember what version of Clockwork Mod I had. I know it was an older version, becuase it didnt have touch.
How do I get a previous version of CWM?
But my problem isn't even remotely similar to this guy!
I'm trying to ask if there's some way to flash a new kernel/rom without using recovery, taking advantage of the fact that my phone boots fine but I can't boot recovery. That's the reason why I mentioned ODIN.
Also, go make your own thread. My question didn't even get answered
Actually,
Creepyncrawly, thanks for your help.
I downloaded ShoStock 3 and flashed it to get the previous version of CWM, and then was able to do a restore.
Sigh.. no harm done.
You can have your thread back... good luck!!
Mighty_Rearranger said:
But my problem isn't even remotely similar to this guy!
I'm trying to ask if there's some way to flash a new kernel/rom without using recovery, taking advantage of the fact that my phone boots fine but I can't boot recovery. That's the reason why I mentioned ODIN.
Also, go make your own thread. My question didn't even get answered
Click to expand...
Click to collapse
Yes, as stated by creepyncrawly, u can use mobile odin or regular odin to flash a kernel.
But i would suggest doing a MD5 check on the Rom u downloaded, because the Rom u flashed may be that of a corrupted download. If MD5 doesn't match then redownload, check MD5 and if good, reflash the Rom.
.....or maybe the nightly is messed up.
Sent from my SAMSUNG-SGH-I747 using xda premium
Mighty_Rearranger said:
Here's the deal:
I rooted my phone a long time ago, and have been using CM since ICS. Mostly nightlies.
A few weeks ago I decided installing a Carbon nightly (4.3), and everything went smooth as usual.
Then new nightly came, so I decided flashing it. (Dirty flash, but it's that way from what I read in the Carbon thread)
The thing is, my phone boots up correctly, but I can't get into recovery mode. Whenever I try booting recovery mode, the logo appears, then the screen flashes gray. I have tried both the advanced reboot menu, the button combo, and ROM Man...jk
I think something might be wrong with the recovery included in the kernel. If that's the case, would it be OK to flash just a new kernel or do I have to reflash the whole thing?
I have already seen some guides on flashing kernels with mobile ODIN, but they're either ancient or for another model. Also, I don't know if that's the right thing to do under this situation.
I'd appreciate if someone pointed me in the right direction. I don't wanna frak up my phone.
Click to expand...
Click to collapse
Mighty_Rearranger said:
But my problem isn't even remotely similar to this guy!
I'm trying to ask if there's some way to flash a new kernel/rom without using recovery, taking advantage of the fact that my phone boots fine but I can't boot recovery. That's the reason why I mentioned ODIN.
Also, go make your own thread. My question didn't even get answered
Click to expand...
Click to collapse
I can see why you could be upset that someone hijacked your thread.
I only see one question in your original post, which I believe I answered. You also requested assistance which I thought I provided.
Let me be a little more specific for you. Yes, you can flash just a kernel without re-flashing the system. However, you will need either an Odin flashable tar of the kernel, or you will need to install Mobile Odin and then you can flash a kernel directly from a zImage file.
However, I think 4-2ndtwin has the right of it. It was probably a bad flash, even though the phone booted normally. You should consider re-flashing the entire rom.
If you are not clear about anything, please ask questions.
Never mind.
I concluded it wasn't worth it just because I was lazy backing up stuff.
I used this: http://forum.xda-developers.com/showthread.php?t=1525821, then flashed a clean ROM.
Thanks for the help, you guys are awesome.
New to this - I really apologize if this has been covered before but I've been searching all evening and not coming up with a definitive answer.
What's the easiest way to remove a custom recovery (like twrp) and go back to stock? Still on the stock rom, just have custom recovery. I manually deleted a nandroid backup using a file manager from my sd card yesterday, and now when booting into recovery it sits on the twrp screen for easily 10-15 minutes. I can't fathom why that would have an effect on the start up time but that's all I can think of that changed. I've tried re-installing twrp via goomanager - no change.
Is there a way to do so without using usb? I'm curious because the first S4 I had, the usb port went bad after only a month and I was in a panic that I wouldn't be able to get it back to stock (until I finally got it to work long enough to flash it with odin). Really don't want to risk that happening again.
Looking to run some roms once I think I understand at least half of what I'm doing, but trying to be cautious. I'd like to keep twrp but I want to make sure it's working right by loading a clean install of it.
Thanks in advance.
A lot of users are experiencing the lag with TWRP version installed by Goo Manager - (TWRP 2.6.0).
The link below has a flashable zip to version 2.5.0.2, this version seems to be stable and doesn't lag at the TWRP screen for most people including myself.
I would try flashing this and I think it will solve your problem.
http://forum.xda-developers.com/showpost.php?p=45006486&postcount=289
gadget! said:
A lot of users are experiencing the lag with TWRP version installed by Goo Manager - (TWRP 2.6.0).
The link below has a flashable zip to version 2.5.0.2, this version seems to be stable and doesn't lag at the TWRP screen for most people including myself.
I would try flashing this and I think it will solve your problem.
http://forum.xda-developers.com/showpost.php?p=45006486&postcount=289
Click to expand...
Click to collapse
Thank you. I'm a little stumped on what to do with the zip now that I have it though and all my searching for "loading recovery with goo manager" just shows the method to load the newer version. Or if you're supposed to load it via pc, what do you use? Odin doesn't like any of those file types.
Sorry if this is a dumb question. Probably just not searching for the right thing.
bretbretterson said:
Thank you. I'm a little stumped on what to do with the zip now that I have it though and all my searching for "loading recovery with goo manager" just shows the method to load the newer version. Or if you're supposed to load it via pc, what do you use? Odin doesn't like any of those file types.
Sorry if this is a dumb question. Probably just not searching for the right thing.
Click to expand...
Click to collapse
You flash it via recovery. Put in your sdcard/internal boot to recovery amd use the install zip option. Navigate to where it is and flash away.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk. now Free
bretbretterson said:
Thank you. I'm a little stumped on what to do with the zip now that I have it though and all my searching for "loading recovery with goo manager" just shows the method to load the newer version. Or if you're supposed to load it via pc, what do you use? Odin doesn't like any of those file types.
Sorry if this is a dumb question. Probably just not searching for the right thing.
Click to expand...
Click to collapse
Yes, it is a flashable zip, just flash it in the recovery you have now.
I found this post based on the OP's original question, "how to remove TWRP recovery".
I have been flashing rooted ROMs for a while now via ODIN, but am just now starting to foray into the realm of custom recoveries. Before I install TWRP though, I wanted to know how to remove it just in case something ever goes wrong. That is, I've been avoiding the use of a custom recovery so far because if something ever happened to my device, I could just flash the stock ROM, and having already used Triangle Away, Samsung will never be the wiser and would service my device, but with a custom recovery installed, they would be able to see I'm not running totally stock.
So, is there a way to completely return my device to 100% stock after installing TWRP? And if so, how would I go about doing that?
My device is a Samsung Galaxy Note 10.1 GT-N8013, currently running a root injected stock ROM, 4.1.2
EDIT: I just noticed that this is in the S4 forum, which my N8013 obviously is not, but the answer to my question should be the same regardless, yes?
margentieri said:
I found this post based on the OP's original question, "how to remove TWRP recovery".
I have been flashing rooted ROMs for a while now via ODIN, but am just now starting to foray into the realm of custom recoveries. Before I install TWRP though, I wanted to know how to remove it just in case something ever goes wrong. That is, I've been avoiding the use of a custom recovery so far because if something ever happened to my device, I could just flash the stock ROM, and having already used Triangle Away, Samsung will never be the wiser and would service my device, but with a custom recovery installed, they would be able to see I'm not running totally stock.
So, is there a way to completely return my device to 100% stock after installing TWRP? And if so, how would I go about doing that?
My device is a Samsung Galaxy Note 10.1 GT-N8013, currently running a root injected stock ROM, 4.1.2
EDIT: I just noticed that this is in the S4 forum, which my N8013 obviously is not, but the answer to my question should be the same regardless, yes?
Click to expand...
Click to collapse
Answer would be device specific
Sent from my cm_tenderloin using xda app-developers app
Thanks Gadget, Hex. TWRP 2.5.0.2 works great. But just for future reference, is the only way to revert to the stock recovery by flashing a stock device image via odin over usb? So if the USB port were to fail entirely, I would be SoL - correct?
My friend and I both have Fascinates. I got mine first, and just rooted the Gingerbread that came with it. I use it for medical purposes, and really needed something stable and reliable.
When my friend got hers, we decided to go for a more recent ROM, and chose GeeWiz 4.4.2 (Jellybean). It was real easy to install and didn't require anything special. It worked great for a little while, but as she added apps to it, it got real laggy and hard-crashed a fair amount.
Yesterday, all hell broke loose with it. Suddenly, every Google app was crashing, including the Play Store. I researched the issue and found many other people with similar problems on various phones. I tried literally 16 different fixes, none of which worked. So I had to hard reset it.
Since it's a blank canvas, and her experience with GeeWiz wasn't all that great, I figure it's a good time to try something else.
What do YOU recommend?
Here's her priorities:
1. Must be super stable.
2. Everything must work. Speakerphone, bluetooth, camera, video, microSD, you name it.
3. Not laggy.
4. Good battery life.
She really likes the Jellybean notifications, so she would prefer Jellybean or later.
I'm very interested in what the community recommends. :highfive:
the newest cm10.1 nightly was rock solid for me. helly bean 4.2.2 was good too. don't go beyond 4.2 if you want good stability, i don't think some basic things work in the cm11 builds yet (GPS and MMS are flaky)
oh also don't feel bad for running stock GB. i'm actually running it right now (rooted, lean kernel, and i gutted out the majority of samsung things)
---------- Post added at 11:04 PM ---------- Previous post was at 11:00 PM ----------
also, for future reference, any thread you post of similar connotation to this will probably get locked by a moderator and he'll say "oh try roms out for yourself blah blah blah"
so if that happens, don't say i jinxed it. also, i've had my fassy for around 6 months and i've tried literally everything under the sun for it.
I agree with sceptic on these ROM selections
rockpaperlizard said:
Yesterday, all hell broke loose with it. Suddenly, every Google app was crashing, including the Play Store. I researched the issue and found many other people with similar problems on various phones. I tried literally 16 different fixes, none of which worked. So I had to hard reset it.
Click to expand...
Click to collapse
I thought Geewiz was only made for the Fascinate? I have been trying the Geewiz rom, and so far the only time it became laggy was when I set the cpu Govenor to a power saving option. Otherwise it has actually been much faster booting up than the kitkat roms.
Sent from my GT-N5110 using xda premium
Okay, trying to get Hellybean working... but am stuck!
Thank you to everyone providing a reply so far. Please keep the suggestions coming. :highfive:
I am trying to install the recommended Hellybean 4.2, and am stuck.
The phone was stock Gingerbread, and then I installed the GeeWiz 4.4 ROM on it. Had some lagging and crashing, so now I'm trying to get Hellybean 4.2 on it, per recommendations of others.
So I downloaded the latest Hellybean 4.2 from the hellybean website. I then booted into recovery, and selected Update from Zip and and tried to install the Hellybean zip. I get a Status 7 error. Some sites said to try it 3 times. I tried it 5 times. No dice.
I can't find a Hellybean 4.2 Fascinate thread on XDA, so details are sparse. Am I blind?
Am I correct in understanding that Hellybean 4.2 includes the devil kernel? Or do I need to ODIN a different kernel first?
I installed ROM Manager to get the latest CWM Recovery, but it says the Fascinate is an "unknown device". There is no CWM Recovery installation file for the Fascinate listed on the Clockworkmod website. UGH! :crying:
Can anyone help? I can follow step by step instructions real well. :good:
Progress Update
I noticed the link in hhp_221's signature, and followed it. I installed his devil kernel for Jellybean 4.2.2. Works a treat. :good:
Then I tried to install the Hellybean 4.2 zip file in the resultant CWM Recovery, and now I get a Status 0 error. Tried it 5 times. Same thing each time.
Help!
rockpaperlizard said:
I noticed the link in hhp_221's signature, and followed it. I installed his devil kernel for Jellybean 4.2.2. Works a treat. :good:
Then I tried to install the Hellybean 4.2 zip file in the resultant CWM Recovery, and now I get a Status 0 error. Tried it 5 times. Same thing each time.
Help!
Click to expand...
Click to collapse
okay here's some instructions (assuming the phone is on stock. if it isn't just go into odin and reflash it again because you're probably bricked)
1. let it boot up after odining EH03 (might want to throw cm10.1, helly, and google apps on the sd card at this point)
2. after it boots, flash GBBootloaders.tar and cwm 4 fixed for cm7. those files can be found here: http://forum.xda-developers.com/showthread.php?t=1238070
3. go into recovery by pressing and holding volume up, down, and power until the samsung logo flashes and reapppears
4. wipe data and cache
5. flash the newest cm10.1 (gapps too if you want to stay on cm, if you want helly don't bother flashing gapps)
6. reboot
7. if you're flashing helly, reboot into recovery from cm and flash helly from CWM. and gapps. wipe data too just to be safe.
if any of my guide didn't help, just follow the thread i linked in step 2. it's a good comprehensive guide.
also never flash anything with ROM Manager, it's useless for this phone because the version of CWM on ROM Manager is really old. i've bricked my phone when trying it.
Getting closer!
skepticmisfit said:
okay here's some instructions (assuming the phone is on stock. if it isn't just go into odin and reflash it again because you're probably bricked)
1. let it boot up after odining EH03 (might want to throw cm10.1, helly, and google apps on the sd card at this point)
2. after it boots, flash GBBootloaders.tar and cwm 4 fixed for cm7. those files can be found here: http://forum.xda-developers.com/showthread.php?t=1238070
3. go into recovery by pressing and holding volume up, down, and power until the samsung logo flashes and reapppears
4. wipe data and cache
5. flash the newest cm10.1 (gapps too if you want to stay on cm, if you want helly don't bother flashing gapps)
6. reboot
7. if you're flashing helly, reboot into recovery from cm and flash helly from CWM. and gapps. wipe data too just to be safe.
Click to expand...
Click to collapse
Thank you for all the tips. Using your tips, I successfully got CM 10.1 onto her phone. But I read her the description of HellyBean, and she would prefer that (of course :cyclops.
So once CM 10.1 is on, I booted into it, and then immediately turned it off. I then booted into CWM recovery, and tried to install the Hellybean ROM. I get the Status 7 error each time. You mentioned wiping data after installing helly, but I think you meant before (let me know if I'm mistaken).
I researched Status 7 errors, and some people say they are because the ROM is expecting a different existing version to be installed over. I took a look at the build.prop file in Hellybean, and it references the Gingerbread 2.3.5 EI20 ROM, whereas all I could find was the stock Gingerbread 2.3.5 EH03 ROM. I tried editing the build.prop file to reflect EH03, but I an aborted error when trying to install that.
The radio and all other items on the phone should be stock. Not sure if that helps or hurts in getting Hellybean installed.
Anyways, any and all help in getting from CM 10.1 to Hellybean 4.2.2 would be most appreciated. Or I can put stock Gingerbread 2.3.5 EH03 back on and start from there. :good:
rockpaperlizard said:
Thank you for all the tips. Using your tips, I successfully got CM 10.1 onto her phone. But I read her the description of HellyBean, and she would prefer that (of course :cyclops.
So once CM 10.1 is on, I booted into it, and then immediately turned it off. I then booted into CWM recovery, and tried to install the Hellybean ROM. I get the Status 7 error each time. You mentioned wiping data after installing helly, but I think you meant before (let me know if I'm mistaken).
I researched Status 7 errors, and some people say they are because the ROM is expecting a different existing version to be installed over. I took a look at the build.prop file in Hellybean, and it references the Gingerbread 2.3.5 EI20 ROM, whereas all I could find was the stock Gingerbread 2.3.5 EH03 ROM. I tried editing the build.prop file to reflect EH03, but I an aborted error when trying to install that.
The radio and all other items on the phone should be stock. Not sure if that helps or hurts in getting Hellybean installed.
Anyways, any and all help in getting from CM 10.1 to Hellybean 4.2.2 would be most appreciated. Or I can put stock Gingerbread 2.3.5 EH03 back on and start from there. :good:
Click to expand...
Click to collapse
wipe data before installing helly. also i've never bothered with build.prop in Hellybean. it only references to EI20 for Voodoo Sound drivers. EI20 is the stock build for.. i believe the US Cellular Mezmerize (aka not the Verizon Fascinate). so don't screw with it
yes stock radio is good. EH03 is a good radio but if you want you can flash EC09, based off of a leak of GB. some people have good luck with it, i used to but i like EH03.
so.. i'm not sure if you can boot the phone into helly bean. it sounds like you were getting a lot of "status 7" errors, which i didn't ever get while trying to use helly. this may or may not be caused by the sd card. try a different card if possible. if you're bricked at this point just start over from EH03.
also be sure you're using the 2013-7-23 build of helly, that's the last one based off of 4.2.2, the rest are broken 4.3 builds.
Good advice!
skepticmisfit said:
also be sure you're using the 2013-7-23 build of helly, that's the last one based off of 4.2.2, the rest are broken 4.3 builds.
Click to expand...
Click to collapse
Thanks for the heads up on the helly build! I got one from the Hellybean website, and it's labeled 20131024. I tried and tried to find the 2013-7-23 but no luck , could you guide me to a source for it? Thanks!
rockpaperlizard said:
Hey, it's the girlfriend here. BF is out, so I was trying to get the right files gathered. Thanks for the heads up on the helly build! I got one from the Hellybean website, and it's labeled 20131024. I tried and tried to find the 2013-7-23 but no luck , could you guide me to a source for it? Thanks!
Click to expand...
Click to collapse
here you go: http://andromirror.com/file/1386
good luck!
Sooooo close...
Thank you for the helly link!
Followed instructions, and successfully got it to helly!:good:
But... been trying to flash the gapps, and no go. It says it's successfully installed, but then nothing happens. Also noticed it can't mount the cache. And noticed that the zip says it's signed but if signature verification is enabled, cwm says the signature is not valid.
Any thoughts/ideas/solutions? Thanks!
rockpaperlizard said:
Thank you for the helly link!
Followed instructions, and successfully got it to helly!:good:
But... been trying to flash the gapps, and no go. It says it's successfully installed, but then nothing happens. Also noticed it can't mount the cache. And noticed that the zip says it's signed but if signature verification is enabled, cwm says the signature is not valid.
Any thoughts/ideas/solutions? Thanks!
Click to expand...
Click to collapse
cache...
give us what the recovery version number is.
Is it the red touch recovery (that is what is included with hellybean)
gapps...
bad download maybe, it does happen...
get and verify the md5 yourself with an app
for windows
or an android one
like this one
are you using this gapps version? http://goo.im/gapps/gapps-jb-20130812-signed.zip
its what you need to start with,, and then after you sign in to your account,, it will check to see what needs to be updated.
.
I tried the cm10 mentioned here. It does seem very nice. It appears to have more features than Geewiz also, along with a lot more ringtones.
Sent from my GT-N5110 using xda premium
Information
hhp_211 said:
cache...
give us what the recovery version number is.
Is it the red touch recovery (that is what is included with hellybean)
.
Click to expand...
Click to collapse
Thank you for the avenues to explore. The recovery that comes up is CWM Recovery v4.0.1.0. Does that mean helly didn't really install successfully? When it boots, it does give the Devil kernel graphic, which I understand is part of helly?
hhp_211 said:
gapps...
bad download maybe, it does happen...
get and verify the md5 yourself with an app
are you using this gapps version? http://goo.im/gapps/gapps-jb-20130812-signed.zip
.
Click to expand...
Click to collapse
I looked at the gapps. It is the gapps-jb-20130812-signed.zip and the md5 checks out.
It's the blue CWM, forgot to mention that...
rockpaperlizard said:
Hi, GF here again. I'm new to all this, thank you for the avenues to explore. The recovery that comes up is CWM Recovery v4.0.1.0. Does that mean helly didn't really install successfully? When it boots, it does give the Devil kernel graphic, which I understand is part of helly?
I looked at the gapps. It is the gapps-jb-20130812-signed.zip and the md5 checks out.
Click to expand...
Click to collapse
whoa you're not supposed to have blue recovery after flashing a 4.x ROM (or MTD as we call it).
go to step 4 in this guide: http://forum.xda-developers.com/showthread.php?t=1238070
you're going to have to reflash EH03 in Odin before doing anything because your recovery is borked.
Got it!!
Finally got helly onto a phone! Ended up starting all over, and then just flashing to helly since had the right file and hadn't tried going directly (skipping CM). And it worked! But the 3-finger salute got us back into blue CWM. So I started all over again, and once helly was on, I thought I'd do a reboot just to make things happier, which is when we noticed the 'reboot to recovery' and remembered that we had read somewhere that you sometimes have to use that instead of the 3-finger. So we did and everything has been golden since then. I love, love this ROM! :laugh:
Big thanks to you guys for helping us through the process! We couldn't have done it without you!!
rockpaperlizard said:
GF here. We finally got helly onto the my phone! We ended up starting all over, and then just flashing to helly since we had the right file and hadn't tried going directly (skipping CM). And it worked! But the 3-finger salute got us back into blue CWM. So I started all over again, and once helly was on, I thought I'd do a reboot just to make things happier, which is when we noticed the 'reboot to recovery' and remembered that we had read somewhere that you sometimes have to use that instead of the 3-finger. So we did and everything has been golden since then. I love, love this ROM! :laugh:
Big thanks to you guys for helping us through the process! We couldn't have done it without you!!
Click to expand...
Click to collapse
that's weird that 3-finger into recovery is broken for you.. it wasn't for me. but whatever, as long as it works