Related
I install the clockworkmod for set up the GTAB rom...
but now i want to return to the stock recovery...so how to uninstall clockworkmod?
thanks!
savage,
You install CWM to replace the stock recovery. Therefore, you have to re-install the
stock recovery. If you were using a stock rom like say 3588, you would just reinstall
the rom again and let it overwrite CWM.
But since I don't know what rom you are using, you need to check the source of
your rom, make sure it contains the stock recovery -- and then inquire of the issuer
of the rom whether or not you should re-install or do some other special procedure.
Rev
thanks！ Now i am using the VEGAn-Tab Build rom~
so what should i do next?
sorry for the confusion~
GTAB ROM is not granular enough - you running stock or a modded ROM? If so, which ROM?
I can reply for TNT Lite 4.3.0+ or gADAM 1.3.0+ - there's a script setup to go back to standard recovery. If you are running either of these, please see my first posts on those ROMs for instructions on what to do. Again, this is only if you are running TNT Lite or gADAM.
You can also attempt to flash standard recovery using a build 3588 standard recovery firmware image in PART3 here: http://forum.xda-developers.com/showthread.php?t=1005080
savage,
EDIT: roebeet answered you first so I'll just stand by and see what y'all do.
Good luck!
Rev
thanks！ Now i am using the VEGAn-Tab Build rom 5.1.1~
so what should i do next?
sorry for the confusion~
problem with installing CWM
I got my gtablet yesterday and tried to install CWM v.8 using external micro SD card. It looked like it was half way done because it could not reboot by itself and stuck at a screen asking for reboot. So I selected reboot but it did not reboot. I had to force it to close. When I pressed volume+ and power, it had this message on the upper left coner: Recover key detected, booting recovery kernel image and 3 birds in the middle of the screen. It stuck there forever without doing anything. I only installed Z4root and nothing else. How can I remove the half-done CWM and redo it again. If I can do it again, what should I look out to avoid the same error?
yu203964 said:
I got my gtablet yesterday and tried to install CWM v.8 using external micro SD card. It looked like it was half way done because it could not reboot by itself and stuck at a screen asking for reboot. So I selected reboot but it did not reboot. I had to force it to close. When I pressed volume+ and power, it had this message on the upper left coner: Recover key detected, booting recovery kernel image and 3 birds in the middle of the screen. It stuck there forever without doing anything. I only installed Z4root and nothing else. How can I remove the half-done CWM and redo it again. If I can do it again, what should I look out to avoid the same error?
Click to expand...
Click to collapse
If you got your tablet yesterday, then it probqbly had firmware 1.2.4349 on it, which is a 1.2 bootloader firmware. You tried installing a CWM made for a 1.1 bootloader. how much research did you do prior to modding? Seeing as you installed Z4root, I'd imagine that you didn't do much, as it's not needed at all to root your G-tab.
go to http://viewsonic-gtablet-for-dummies.webs.com/ and start reading at "START HERE" to get an idea of what your dealing with, and what you can and can't do...look through the entire site!
to get out of where you are now, and back to a workable base, follow the "CODE RED" instructions here: http://viewsonic-gtablet-for-dummies.webs.com/
Lastly...don't do anything else silly until you've read and understand all of the instructions on Goodintentions site...it's a GREAT resource and should be a pre-requisite for all new G-Tab owners.
Tuesday night I loaded CM7, and then the Market wouldn't update my apps so I decided I would restore BAMF 1.5. After doing so, the Market just gave me "Fails" trying to update, and I could not access recovery, as I was going to do a complete wipe and reflash. Most of Wednesday, an extremely helpful & knowledgable member, Mattgyver83, tried diligently to help me rectify the situation, but to no avail. We tried to Fastboot, tried flash_image, tried fix permissions...shoot, I practically wore out adb..anyway, I ended up reverting back to stock and unrooted. I used jcase's method to revert back to stock, and that was painless, and successful. I decided last night to try rooting again, thinking a fresh root would solve my issue of not being able to access recovery. Root was successful, but I still cannot access recovery, through rom manager, or through bootloader. When I attempt it my Tbolt goes to white HTC screen, and stays there. All functions of my phone now work, and all aspects of root work, except I cannot flash anything. Rom manager shows I have clockwork recovery, but I just can't get to it.
Sorry for the long ramble. If anyone has had this issue, or if anyone knows a fix, I would appreciate it. Otherwise, I wait for Gingerbread.
Thanks
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
travishamockery said:
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
Click to expand...
Click to collapse
Tried that, but thanks. Still just goes to white HTC screen, and stays there until I do battery pull.
jr4000watts said:
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
Click to expand...
Click to collapse
I can get to bootloader, just not able to get into recovery.
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
monolithic said:
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
Click to expand...
Click to collapse
Thanks, but that didn't work. I think something in my os got lost when I restored BAMF from CM7.
Yea I spent a good few hours yesterday trying to help Orio out and we attempted a ton of things to try and fix the recovery issue, this post should offer a bit more insight to the methods used, this is running off memory;
adb reboot recovery failed
Reinstall latest Rom Manager apk and Flash CWM
flash latest rom manager via fastboot (CWM only)
(fastboot flash recovery /sdcard/recovery-clockwork-3.0.2.5.img)
**did not do fastboot erase recovery first**
"return to stock safely and properly" XDAthread by jcase
return to stock image [RUU], reroot, try again
try to boot into recovery via hboot
manually installed fix_permissions.sh script and busybox on rooted stock, ran.. didnt fix
tried to see if flash_image method would work, didn't
All of the above have failed and we basically tried almost all combinations. Not once would this phone get back into recovery, even after flashing the appropriate RUUs which include either stock android or CWM recovery. The only thing we have not currently attempted which might be the last thing left is to do is manually install the nandroid.sh script and do an advanced restore of the recovery image only from a nandroid backup on SD. I would rather not go down this method as it could have an undesired result, I have done it to restore a G1 back in the day but not 100% if its gonna work on a tbolt. Thankfully his phone boots, and we can get into hboot, but yea.. pretend recovery just doesnt exist at all...
Curious if anyone has any knowledge above what we have already tried.
monolithic said:
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Click to expand...
Click to collapse
I recall the same thing and its a good thought however that was mostly a generic error due to a CWM update and CM6 (I think) but either way flashing an RUU should override this shortcoming and im pretty sure that issue was worked out in CWM as well.
Not to be rude, but I don't think this question belongs in the development section.
Orio56 said:
I can get to bootloader, just not able to get into recovery.
Click to expand...
Click to collapse
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
hogowner said:
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
Click to expand...
Click to collapse
Thanks, but no, I deleted that after loading it. I actually reverted back to stock/unrooted last night and rerooted and the problem still remains. It's quite strange.
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
shelooga said:
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
Click to expand...
Click to collapse
That is what I was going to suggest. In ROM Manager at the very bottom try and flash an older version.
Sent from my ADR6400L using XDA Premium App
SUCCESS !!!
I fixed it !
Apparently, when I loaded up cm7, files showed up about the same time on my sdcard in clockworkmod download file. I deleted those files, and reflashed clockworkmod in rom manager, (which this time took like 3 - 4 minutes), and rebooted into recovery and it worked...did it again, just in case it was a fluke and it worked.
All is well now...the planets are realigned !!!
Thanks everyone for your ideas and especially thanks to mattgyver83 who helped me for something like 4 hours yesterday. Exceptional kindness !!
mods...you can close this thread.
GREAT NEWS!!!! CONGRATULATIONS!!
THANKS FOR REPORTING BACK!
This may help out other members with the same problem!!
now go ahead and start playing with your T-BOLT again!
That's a very odd solution. My first two things to try would have been:
1) fastboot:
fastboot erase recovery
fastboot flash recovery C:\some\local\path\recovery.img
You can't, well, probably shouldn't, flash a recovery from the /sdcard. When in fastboot mode I don't think the sdcard is even mounted. Either way, I think fastboot needs the img file on the local file system.
2) Create a PG05IMG.zip file with the recovery.img file in it, and flash that through HBOOT. Although this should have been done in some form or fashion when you downgraded or re-rooted, so YMMV.
This is what happens when you have too much info with waaaay too little experience.
Bought an unlocked Vibrant from Amazon a year ago after the original tmobile one got stolen. It had issues like freezing up, tons of apps running all of time, etc. I finally tried installing froyo and it made the phone SO MUCH BETTER! Everything ran 1000% faster. I should have stopped there. But, it was pretty addictive I started reading about the new ice cream roms and somewhere, before I even got into it, I messed up the internal sd card. I have been working on this for a week, reading, downloading, flashing, etc. I feel like I have tried everything and have gone around in circles.
I can get into download mode with no problem. The furthest I have gotten after that was getting the "pass" in Odin. The phone does the boot up, then stay on the Galaxy S screen. Now, my computer won't recognize the phone (which has already happened) but now I am soooo confused and frustrated about where to go next. I have used AIO toolbox, Eugene's no brick, installing new drivers, new usb cord, etc.
Sorry so long. Thanks again.
bump...hope someone can help.
Could you give a clearer explanation/timeline of what you did? How did you mess internal sd?
Did you Odin stock jfd?
Sent from my GT-I9000 using XDA App
nolamom said:
bump...hope someone can help.
Click to expand...
Click to collapse
Is Clockworkmod recovery installed? If not, google: Samsung_Vibrant:_Full_Update_Guide and go to the Cyanogenmod wiki entry. Read through the "Installing Clockworkmod recovery" section.
In addition, from Addictivetips, to start recovery mode using the hardware buttons:
"Using hardware button combination on most Android devices:
On most Android devices including ones by HTC, you can enter recovery by powering your device off and then powering it back on while keeping either the ‘Volume Down’ or the ‘Volume-Up’ button pressed, depending on the device. This will enter the bootloader from where you can select the ‘RECOVERY’ option by navigating to it with the Volume key and entering it with the ‘Power’ key.
Sorry, but I'm not allowed to post links yet.
On most Samsung devices specifically Samsung Galaxy S series devices, you must keep both the ‘Volume-Up’ and ‘Home’ keys pressed while powering on the device, to directly enter recovery."
Thanks so much for the help. Ascallop: I tried to run Heimdall suite 1.3.1. The first time the drivers installed but I could not get passed the "run as administrator" on the next step. I have Windows XP professional even though I am on a home computer. It is automatically checked off to do so. When I tried again later that day, my computer again only recognized the vibrant as an unknown device. I just followed your link to Cyanogenmod's wiki and downloaded the older version and the same thing happened with the unknown device. I can't get passed that. Trailblazerz11, I think when I got to clockwork mod recovery, I hit repartition (if I am explaining that right). I was able to get into download mode and use Odin to get to the bootloader loop. I can't get into recovery. I was getting the message about the internal sd error. Now, I am stuck with the unknown device issue. I have tried a couple of different versions of Odin, the AIO toolbox, different usb ports, a new samsung cord, etc. Thanks again for helping this noob.
update: Used heimdall frontloader and installed cmenard overstock. Now I am stuck at the overstock screen. I am searching through different posts to find out more. But if you have any advice or can point me in the right direction, I'd appreciate it. Thanks again.
Have you tried repartition on odin?
sent from the xda app on my android smartphone.
Do you have an external SD card installed? If so, then remove it during the entire recovery process. I had lots of trouble recovering and flashing new kernels/roms while it was installed. Probably should have mentioned this earlier... sry.
No. It was already taken out. I am having trouble still with the vibrant not being recognized. I used the zadig, it recognized the samsung, did the next step, frozen at overstock screen. Now, after unplugging cable, Vibrant pops up as unknown device. Can't do zadig again.
I'm travelling until Friday, when I get back to my home PC, I'll odin my Vibrant back to stock Eclair and will list the steps that I took some months ago to install CWM/CM7. I once was at the same point as you are now, I just can't remember the steps verbatim regarding the recovery process. One question though: have you updated your phone via Kies at any point? If so, was the last update to Froyo?
BTW, I'm currently running (quite happily) ICS Passion V12 on my T-Mobile Vibrant.
The Vibrant is a pretty hard device to truly brick. Don't worry too much, yet.
Thanks so much ascallop! I think I tried Kies when froyo was offered as an update through Samsung. But, it wouldn't work. I thought it was because my phone came unlocked so I came here and was able to update to froyo and I loved it. I haven't used Kies since. The ICS Passion looks awesome. I think the ease of using froyo made me ridiculously overconfident. As of right now, I have gotten the drivers to download in Heimdall and used the frontend to flash the kernel. I'm not sure what to do next because it seems that if I reboot to get into download or unplug the usb, the computer won't recognize the phone again. I'm sure I'll be happily running ICS when you get back on Friday. Kidding, kidding.
nolamom said:
Thanks so much ascallop! I think I tried Kies when froyo was offered as an update through Samsung. But, it wouldn't work. I thought it was because my phone came unlocked so I came here and was able to update to froyo and I loved it. I haven't used Kies since. The ICS Passion looks awesome. I think the ease of using froyo made me ridiculously overconfident. As of right now, I have gotten the drivers to download in Heimdall and used the frontend to flash the kernel. I'm not sure what to do next because it seems that if I reboot to get into download or unplug the usb, the computer won't recognize the phone again. I'm sure I'll be happily running ICS when you get back on Friday. Kidding, kidding.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
Let's get your phone back to Stock first. I just did this to my own Vibrant
I am officially back to stock!!! Thanks so, so much. After all of the reading and researching, you actually jumpstarted my recovery! Thanks again!!!
You're welcome
BTW, I flashed ICS V12r1 with Nelson's new kernel today. I love it. GPS works great for me, although others have reported problems. Same old deep sleep issue for them.
I wonder if flashing back to stock first is the key to fixing the prob. Don't really know though...
After the stock flash, the steps I took were:
copied kernel and rom to the internal sd card
One-click rooted the phone
odin (1.3) the Overstock kernel just to get cwm installed (instructions on the cm7 wiki)
reboot to cwm
wipe data/factory reset
wipe cache/dalvik
flash rom
reboot, let settle
reboot to cwm
flash kernel (I used: ICS_Passion_sunset_with_nova)
reboot, let settle
---------- Post added at 05:29 PM ---------- Previous post was at 05:24 PM ----------
One more thing: I flashed the Gingerbread bootloader as well. After you do this the key combo for cwm is: Vol-up + power. Let go when you see the boot splash.
Sounds sweet! Although I'm back to stock, I can't root because I can't access the internal drive. A message comes up about E: no such file, etc. I can see the phone storage memory amount and the phone holds data. I don't have an external card in right now. So, here I go again....
You shouldn't need an external card to root. Try One click root:
http://forum.xda-developers.com/showthread.php?t=1125414
nolamom said:
Sounds sweet! Although I'm back to stock, I can't root because I can't access the internal drive. A message comes up about E: no such file, etc. I can see the phone storage memory amount and the phone holds data. I don't have an external card in right now. So, here I go again....
Click to expand...
Click to collapse
When I've seen that E: error, it has been because of a mismatch between the CWM version and the filesystem layout on the device. CWM for CM7 doesn't work for ICS, for example. At least not for me.
---------- Post added at 10:24 AM ---------- Previous post was at 10:22 AM ----------
cashmundy said:
When I've seen that E: error, it has been because of a mismatch between the CWM version and the filesystem layout on the device. CWM for CM7 doesn't work for ICS, for example. At least not for me.
Click to expand...
Click to collapse
And of course the stock recovery won't work with anything else. Different partitioning, different filesystems.
Okay. I was able to root with the one click root app. Now, I need to figure out what to do next. Ascallop, I was reading about your latest updates. I have to go through it a few times so that I can understand it all. I had froyo before and it blew away stock. I can't imagine what ICS is like Thanks again for all of the help. I HATE being back to stock.
The only reason I'm not running ICS is that I'm waiting for CyanogenMod permissions management to appear in anyone ICS rom. I'm really tempted to try Passion. ICS is markedly better than the best GB in various ways. Just remember to take a nandroid backup before upgrading, and that if something doesn't work and you need to downgrade, you will have to get the downgrade done successfully before you can nandroid-restore. Good luck!
Thanks Cashmundy. I saw the video for the root and install ice cream sandwich by Eddie West (I think that is his name.) He is a dj also. It looks like everything I would need so I may go with that.
Before doing my flash, I did my research, and it seemed that in order to update from CM7 to CM10, I had to flash a different version of CWM. So I booted into recovery, flashed the version 6.xxx CWM, and then rebooted (I assumed that in order to flash CM10, I had to be in a CM10-compliant recovery). After getting back to my regular desktop, I rebooted into recovery as normal... only it didn't go into recovery. Instead, it paused for a moment like it would go into recovery, then booted to my normal desktop.
I've tried about a billion ways to boot into recovery, to include SD based recoveries, but it either goes to a larger sized N screen, then hangs up on a black screen, or it boots me to my normal CM7. I "can" continue to operate on CM7, but until I can boot into recovery, I can neither update to CM10 nor address any problems I come across in my current build.
Suggestions?
nashdude said:
Before doing my flash, I did my research, and it seemed that in order to update from CM7 to CM10, I had to flash a different version of CWM. So I booted into recovery, flashed the version 6.xxx CWM, and then rebooted (I assumed that in order to flash CM10, I had to be in a CM10-compliant recovery). After getting back to my regular desktop, I rebooted into recovery as normal... only it didn't go into recovery. Instead, it paused for a moment like it would go into recovery, then booted to my normal desktop.
I've tried about a billion ways to boot into recovery, to include SD based recoveries, but it either goes to a larger sized N screen, then hangs up on a black screen, or it boots me to my normal CM7. I "can" continue to operate on CM7, but until I can boot into recovery, I can neither update to CM10 nor address any problems I come across in my current build.
Suggestions?
Click to expand...
Click to collapse
Have you tried holding on the power button and the "n" button as you boot? I recall running into a similar issue as yours and that was the only way I could get to recovery. If you're able to get into recovery that way I would consider maybe getting a different version fo CWM. I had trouble with the 6.0.1.5 version. You might try the 6.0.1.2 version here: http://forum.xda-developers.com/showthread.php?t=1640958&page=5
I ran into something similar when I tried installing CWM 6.x.x. I chickened out and decided to run CM10 from SD instead, and I'm so happy on the performance now that I do!
I did the "unbrick" thing with "repart.img" to get the Tablet back to "out of the box" state and sighed of relief when it worked!
Yeah, I was afraid of that. I really didn't wanna go through the process of unbricking, but I guess there's no help for it.
troy9829 said:
Have you tried holding on the power button and the "n" button as you boot? I recall running into a similar issue as yours and that was the only way I could get to recovery. If you're able to get into recovery that way I would consider maybe getting a different version fo CWM. I had trouble with the 6.0.1.5 version. You might try the 6.0.1.2 version here: http://forum.xda-developers.com/showthread.php?t=1640958&page=5
Click to expand...
Click to collapse
Power + 'n' doesn't work on my NT either, I have to turn the device off, insert the SD with CWM, then plug in the (still turned-off) NT to a wall charger and allow it to boot up that way - then (and only then) do I boot into recovery, and without touching any buttons. Hopefully that helps
Dang, whoever thought this would be such a booger of a deal?!?
Okay, first off, let me apologize for coming off like a noob, but it seems there's so much information out there that everything's kinda bleeding together, so let me tell you where I'm at.
I've unbricked and restored the NT to stock 1.4.2
I tried rooting, but the only root I can find that is flashable from SD is the 5.5 CWM which is older than the CWM 6.xxx that every CM10 version calls for. So I went ahead and did the root, so now I have a stock NT with root access. This is where I'm getting stuck...
I'm at this point...
http://forum.xda-developers.com/showthread.php?t=1640958&highlight=cwm+1+4+2
...and it apparently requires you to reboot into CWM in order to install CWM?!?
I've found the CWM 6+ files I think I need, but when I try to follow the instructions, my NT won't kick over into recovery---it keeps booting straight to the rooted 1.4.2 stock rom. I've found guides that take you from stock 1.4.3 to CM10, some that take you from 1.4.2 to root, and I even found Indirect's CM7 (without the instructions on how to get CWM on there in the first place!). I even downloaded Rom Manager and tried to boot into recovery that way, but it said there was my device wasn't supported.
I've been staring at this dang screen for three hours, trying to find a step by step, and I'm coming up empty. Maybe I'm just too frustrated at this point and need a breather.
What I need to know is how to install CWM 6+ on a NT that's either rooted or stock 1.4.2 (I still have the unbrick SD card) so that I can boot into CWM. From there, I can make my way through installing CM10. Help. Please. Am about to chew the lining out of my cheek.
I don't know if this might be helpful? http://forum.xda-developers.com/showthread.php?t=2037368
Sent from my NookColor using Tapatalk 2
Not yet. I was expecting OTA to kick in, updating my current 1.4.2 to 1.4.3, but it hasn't. Honestly starting to think my NT doesn't want to be rehacked LOL
Okay, so here's what I'm doing at the moment...
I'm at rooted stock. I moved CWM 6.0.1.2, CM10, and gapps over to internal SD.
I booted into recovery with an older version CWM SD card (SD card image with Win32 > turned off NT > insert SD > plug in USB to autoboot)
While in recovery (from SD), I flashed CWM 6.0.1.2 , CM10 (meghd00t), and gapps-jb-20121011.
I reboot...
WE HAVE JOY!
Now to check to see if the thing's gonna run right (got a whole lotta "XYZ has stopped" error messages upon boot up)
Dangit, keep getting those error messages about Gapps stopping and Google Play, and other stuff. Not allowing me to do hardly anything I need to. I can't even boot into recovery from the home page---it still loads straight to the Rom. In order to get into recovery, I need to use the SD that I made to get into recovery in the first place. Going to wipe dalvik and the other caches to see if that helps...
After wiping the caches, I boot into CM10 with no error messages. I DL'd a game from my Gmail account, and it appears to be working properly. Thanks for the suggestions and for letting me vent
I just went thru this similar ordeal too. It took me over 3 weeks to finally find a recovery & cm10 combo. What I found is that I couldn't get ANY version of twrp to act right. Indirect's flashing tool was invaluable. I finally used it to flash a cwm 6.x from Laverne's thread. It seems that not all versions of cwm 6.x are compatible with certain cm10 roms too & by chance I hit a combo that finally worked! I'm staying with what I got for a while!
Sent from my Nexus 7 using Tapatalk 2
This will help anyone who keeps having flashing issues.
More detailed instructions in my GUIDE!
http://forum.xda-developers.com/showthread.php?t=2295557
THIS IS ONE QUICK/SIMPLE ERROR FREE ROM FLASHING PROCEDURE
This should eliminate a few posts saying, stuck in download mode, stuck at logo. just vibrates and them MANY other issues that somehow, everyone seems to find.
Here is my quick rom flashing process I use ALWAYS (yes always)
THINGS YOU NEED ON extSDCARD
1. Extra kernels (2 or 3 you know works for your device)
2. Optional: 2 recoveries that can be flashed (I use CWM & TWRP)
3. Optional: apps.zip (a zip created from Titantium BU, containing Root Explorer, TU Backup, Quickpic, ES File Explorer and Terminal Emulator)
Flashing the rom: TOUCHWIZ/AOSP ROMS
1. Backup current rom (to the extsdcard)
2. Complete wipe, (I do complete, some people do not) Complete = No Issues [FACTORY RESET + CLEAR CACHE + CLEAR DALVIK CACHE + CLEAR DATA]
3. Flash the rom
4. Flash the kernel (your device kernel) (I know some roms have their own kernel) this is where your problems start.
AGAIN: FLASH YOUR KERNEL, you KNOW it works. 1 more time FLASH YOUR KERNEL. (you can experiment with other kernels after you boot)
AOSP ROMS - require you to flash gapps before you boot. [This is not required for TouchWiz roms]
5. Boot the rom.
FINISHED!!!! SUCCESS!!!
Total time to flash a rom:
7-10min
Errors - NONE
This goes for every rom in my guide.
TIPS:
This flash procedure is for Touchwiz Roms, if you are flashing AOSP roms, you must flash the gapps package associated with the rom you are flashing.
**** SGH-I337M Users: Often requires flashing a different kernel than the one included in most ATT ROMS. Any GT-i9505 kernel will work and Adam kernel and Faux kernel are both confirmed working for us Canadian users.
Note: Flash KERNEL directly after ROM then reboot device.
[Special thanks to blyndfyre for this helpful tip].
The extra recovery I flash if a rom does not like the recovery I am using.
Yes, you can flash recoveries back and forth.
Apps.zip I flash after the rom is up & running. This I use to get the rom setup (like root explorer and others needed)
I am in no way responsible for anything that may do damage to any device - Use these tips at your own risk - period!
If you found this useful in any way, please hit the THANKS button for my effort.
RESERVED
TheAxman said:
Any questions? Anyone.
Click to expand...
Click to collapse
I've been running into a lot of issues when trying to flash different ROMs. For instance, right now I'm on CleanROM 1.6 - I just tried to install PureGv2.
Steps I took:
Have Goo and ROM Manager installed after clean install of CleanROM 1.6
Flash CWM from ROM Manager
Install Recovery Script from Goo
Reboot into recover from Goo
TWRP loads
Wipe data, cache, dalvik, etc
Install PureGv2
I forget the error off the top of my head but it doesn't install
In a nutshell I'm asking what am I doing wrong? Do I need to flash another kernel?
Flash your verizon kernel. Correct. I know it is a vzn rom, but do it anyway.
TheAxman said:
Flash your verizon kernel. Correct. I know it is a vzn rom, but do it anyway.
Click to expand...
Click to collapse
Was looking through Tomsgt's Youtube channel and stumbled across a video of his that showed his "About Phone". Everything was identical to mine, so I'm still a little lost as to why I can flash certain ROMs but not others. Sac/Gru's ROM soft bricked my phone, Hyperdrive5.7 didn't install, CleanROM does. It's just funky...maybe I'll just Odin back to stock, flash the MDK and start fresh.
Could the downloads be a problem? I downloaded 2 of the ROMs from work today on a 50meg pipe and they didn't work.
Do you download the ROMs to your phone or to your computer and then move them to your SD card?
If you download to your phone, do you move them to the SD card or leave them in the download folder on the internal storage?
If you do the latter, do you use a micro SD adapter or plug the phone in and move them that way?
harrytery said:
Was looking through Tomsgt's Youtube channel and stumbled across a video of his that showed his "About Phone". Everything was identical to mine, so I'm still a little lost as to why I can flash certain ROMs but not others. Sac/Gru's ROM soft bricked my phone, Hyperdrive5.7 didn't install, CleanROM does. It's just funky...maybe I'll just Odin back to stock, flash the MDK and start fresh.
Could the downloads be a problem? I downloaded 2 of the ROMs from work today on a 50meg pipe and they didn't work.
Do you download the ROMs to your phone or to your computer and then move them to your SD card?
If you download to your phone, do you move them to the SD card or leave them in the download folder on the internal storage?
If you do the latter, do you use a micro SD adapter or plug the phone in and move them that way?
Click to expand...
Click to collapse
Download to the computer,then copy to the phones extsdcard, should be ok, make sure you do a md5 check on the files to make sure they are the correct size.
TheAxman said:
Download to the computer,then copy to the phones extsdcard, should be ok, make sure you do a md5 check on the files to make sure they are the correct size.
Click to expand...
Click to collapse
Alright sounds good. Flashing back to stock later today then re-rooting
thanks for the help
Remember always do a BACKUP before you do anything.
First off, big thanks for this thread.
Now I'm running Cleanrom 1.5. If I wanted to install a new rom can someone please explain exactly what I do to go about it? As jargon free as possible would be awesome.
Sent from my SCH-I545
I certainly scared the carp outta me the other night. I'm using the Carbon ROM and while I do like it, I miss a couple of the S4s features. I picked what looked like a good modified stock ROM and proceeded to flash it.
I'm using Goo and TWRP for the job. I checked of all 3 boxes for clearing cache, davik and factory reset.
Then I chose the file and started it.
The first result, it acted like if was doing everything but nothing changed. Phone still worked fine.
On the next try, I waited for TWERP to start and I reselected the ROM I wanted and flashed it.
When it booted up, I was very happy to see the original screens come up. Then it stopped on the one with the Verizon check mark. The blue LED slowly pulsing and nothing else for about 30 min. I removed battery to try and start over. Same thing again.
Time to goto my backup and restore my phone back to Carbon.
IT FAILED.
Now my phone is stuck in a weird looking boot up loop. After a few tries I was able to get into recovery
mode. TWRP started loading, froze and crashed! Even though I am a total noob at this, I still did not panic.
I'd restart my phone by removing the battery, going into recovery mode and then wildly press every button on my phone hoping to break the loop. It worked! I chose a different save and tried it all over again. FAIL.
ON the next I wiped every bit of old data off. Chose Factory restore crossed my fiingers....it work! My phone is fine now.
Thanks to that ordeal and this thread I think I know what I did wrong even though this never happened to me. before.
1) WIPE THE DATA
2)INSTALL A COMPATABLE KERNAL FIRST
V^^^^V
Vampyre111 said:
I certainly scared the carp outta me the other night. I'm using the Carbon ROM and while I do like it, I miss a couple of the S4s features. I picked what looked like a good modified stock ROM and proceeded to flash it.
I'm using Goo and TWRP for the job. I checked of all 3 boxes for clearing cache, davik and factory reset.
Then I chose the file and started it.
The first result, it acted like if was doing everything but nothing changed. Phone still worked fine.
On the next try, I waited for TWERP to start and I reselected the ROM I wanted and flashed it.
When it booted up, I was very happy to see the original screens come up. Then it stopped on the one with the Verizon check mark. The blue LED slowly pulsing and nothing else for about 30 min. I removed battery to try and start over. Same thing again.
Time to goto my backup and restore my phone back to Carbon.
IT FAILED.
Now my phone is stuck in a weird looking boot up loop. After a few tries I was able to get into recovery
mode. TWRP started loading, froze and crashed! Even though I am a total noob at this, I still did not panic.
I'd restart my phone by removing the battery, going into recovery mode and then wildly press every button on my phone hoping to break the loop. It worked! I chose a different save and tried it all over again. FAIL.
ON the next I wiped every bit of old data off. Chose Factory restore crossed my fiingers....it work! My phone is fine now.
Thanks to that ordeal and this thread I think I know what I did wrong even though this never happened to me. before.
1) WIPE THE DATA
2)INSTALL A COMPATABLE KERNAL FIRST
V^^^^V
Click to expand...
Click to collapse
I can not stress enough HOW IMPORTANT THE KERNEL IS!
Hmm so everyone is a now a Oriental Flash Master from the far East now huh?
What recovery is everyone using?
[updated: 07-12-2013]
Flashing Questions
So, if you just need to add something, like different Kernerl, do you have to wipe and start from scratch?
Should you.
If so, and you backup apps and data in Titanium, then what you do a full wipe, flash entire rom, and reinstall the apps and data associated therewith?
Last, I have asked this but cannot seem to get an answer.
Installed Hyperdrive 7 (also had 5.7 and 6). Rom is super smooth and fast, working like a charm. but I want Verizon Visual Voice Mail.
I tried to copy the apk file to the devices system/app directory but get permission denied message....tried to install, and get failed message....
xander45 said:
So, if you just need to add something, like different Kernerl, do you have to wipe and start from scratch?
Should you.
If so, and you backup apps and data in Titanium, then what you do a full wipe, flash entire rom, and reinstall the apps and data associated therewith?
Last, I have asked this but cannot seem to get an answer.
Installed Hyperdrive 7 (also had 5.7 and 6). Rom is super smooth and fast, working like a charm. but I want Verizon Visual Voice Mail.
I tried to copy the apk file to the devices system/app directory but get permission denied message....tried to install, and get failed message....
Click to expand...
Click to collapse
did you set the permissions for the app? That should work actually. Look at one of the apps in that directory, and set the permissions the same for the voice app. Reboot and see what happens.
Good luck.
May want to post this question also in my guide thread.
http://forum.xda-developers.com/showthread.php?t=2295557
Sorry if this is dumb, but how do I know what kernels for sure work with my device and how do I get them to my external sd card? I suppose the one that is currently on my device(how to get that to sd?), but what others?
Thanks.
Painterface said:
Sorry if this is dumb, but how do I know what kernels for sure work with my device and how do I get them to my external sd card? I suppose the one that is currently on my device(how to get that to sd?), but what others?
Thanks.
Click to expand...
Click to collapse
Please bring the question over to my thread up above. It shows also what kernels to use. We will help there.
Another noob question: so you still advise flashing a kernel even if the ROM creator says that the ROM comes with the appropriate kernel and that no extra flashing is required? I've got the Verizon Galaxy S4 variant and specifically am thinking of Dubbsy's Google Play Edition ROM.
Sent from my SCH-I545 using Tapatalk 2
theoneknownasbob said:
Another noob question: so you still advise flashing a kernel even if the ROM creator says that the ROM comes with the appropriate kernel and that no extra flashing is required? I've got the Verizon Galaxy S4 variant and specifically am thinking of Dubbsy's Google Play Edition ROM.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
You would flash the rom, and after, flash your verizon kernel, simple as that.