First off, I tried to add the 3e recovery by replacing the Recovery file in /system/bin.
I couldn't find a recovery file in there..which I found to be pretty odd.. but I placed the 3e recovery file in there anyway.
I rebooted into recovery and it brought me to the blue recovery menu and it doesn't have the "Install updates" option.
Help!
DLXII said:
First off, I tried to add the 3e recovery by replacing the Recovery file in /system/bin.
I couldn't find a recovery file in there..which I found to be pretty odd.. but I placed the 3e recovery file in there anyway.
I rebooted into recovery and it brought me to the blue recovery menu and it doesn't have the "Install updates" option.
Help!
Click to expand...
Click to collapse
Did you remember to change the permissions for the recovery file?
What was done to your phone prior to your attempt to install 3e? And try selecting "reinstall packages" (first option in blue CWM) to boot into green CWM...what are you trying to do exactly? B/c I don't recall an install updates option in CWM.
oops - I meant to say it didn't have the "reinstall packages" option in the menu. Hm.. I think I should use Root Explorer. Currently I'm using Super Manager but it has no option to change permissions, that I could find.
DLXII said:
oops - I meant to say it didn't have the "reinstall packages" option in the menu. Hm.. I think I should use Root Explorer. Currently I'm using Super Manager but it has no option to change permissions, that I could find.
Click to expand...
Click to collapse
Than that must be your problem, the permissions have to be set, Root Explorer is WELL worth the money. Once you get it the permissions should all be good just uncheck the group/write box, then try booting into recovery and reinstalling packs
Hm.. so I bought Root Explorer, changed the permissions but it's still doing the same thing. Am I doing something wrong?
Btw I found a recovery file, but it's not in /bin. It has a different date on it, and it says rwxr-xr-x on it.
DLXII said:
Hm.. so I bought Root Explorer, changed the permissions but it's still doing the same thing. Am I doing something wrong?
Btw I found a recovery file, but it's not in /bin. It has a different date on it, and it says rwxr-xr-x on it.
Click to expand...
Click to collapse
I think those permissions are what the original recovery is set to (and what the 3e recovery needs to be set to) what size is the file? If that is the original, rename it to something like recovery.orig
It is 404.77K in size. Should I move this to bin?
DLXII said:
It is 404.77K in size. Should I move this to bin?
Click to expand...
Click to collapse
No, I'm pretty sure that's the original cuz the 3e recovery file I extracted from the zip when I did 3e is 306.64k and right outta the zip the 3e recovery permissions should be --xrwxr-x which you need to change to match the original.
So here's what I would do, rename the file in question to recovery.orig.
Next I would start over, find the 3e recovery zip and extract it.
Go to extracted and find the recovery file(306.64k, --xrwxr-x) from that zip and copy it.
Scroll up to the parent folder (..) press till it goes away basically.
Find System/Bin and scroll down to a recovery file if any is in there. (you can either delete it or rename)
Make sure you hit the mount button at the top.
Hit paste, and change the permissions of that recovery file to the correct format and see if that works for you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Permissions should look like this, disregard the "radiooptions."
Sent from my B.A. Infuse 4G
I followed everything you did, but I still bumped into this. Maybe the 3e recovery file I downloaded could be corrupted?
Ok, it's not applying the 3e it looks like, one more thing, you said the original recovery was not in system/bin(didn't catch that on your last post),you should probably put the recovery.orig file in the system/bin location with the new 3e recovery file, not sure if it will help. It's just weird that reinstall packages is not showing up.
I went ahead and did that, but for some reason the original recovery (renamed recovery.orig) isn't renamed, like as if it never saved any changes that I did.
Anyways, I renamed it and added it to system/bin along with the 3e recovery file and set the permissions correctly. Both have the same permissions, actually.
I booted into clockwork and it's still the same screen.
Ya they should have the same permissions, well damn, I've troubleshot every way I knew how...
Here is a LINK for an ODIN back to stock that will put you back to stock but give you root and modded 3e, since apparently your phone is being uber difficult. Just follow the instructions including the samsung kies drivers (download Kies here)
This is what I use whenever I have problems and it works for me every time
Thank you a lot for your patience and your help! I really appreciate it. I'll try the link out. Hopefully it'll work on a rogers phone..
DLXII said:
Thank you a lot for your patience and your help! I really appreciate it. I'll try the link out. Hopefully it'll work on a rogers phone..
Click to expand...
Click to collapse
No problem, I've been in your shoes, trust me, and I wasn't aware you were on a rogers infuse, so you rooted using THIS method? I'm not sure if 3e is the same for ATT and Rogers, but I know rooting is different along with many other things. The link I gave you might not work on rogers infuses, I wouldn't want you to brick your phone.
Yea i used that method. Hm.. I guess I'll just lay low with rooting until I find a solution. Thanks!
Well it's late here, but maybe tomorrow someone with more Rogers Infuse expertise will chime in, sorry, I know the ATT infuse pretty well just not Rogers
If I run across anything useful, I'll post it here
THIS link should solve your issues, specifically for Rogers.
Related
Phone: Froyo 2.2 with root and S-OFF
I am trying to theme the clock widget with no luck. All I am trying to do is replace the flip digits, AM, PM, and background with identical sized graphics. I have tried replacing them with WinZip and 7Zip. I am signing them with the test signature which works with every other type of apk file.
I mount the system partition and push the new version with adb and when I restart all I get is a blank widget. It also shows up in the widgets list as something like 01db as the name.
So, I suspect the signing is the problem. Could be some signature check within the widget causing it to fail.
Any thoughts?
If anyone has this widget working with a black background and silver digits I would be just as happy.
I'm afraid I can't be much help at the moment, since I'm away from my computer, but here is a mod from the hero forums that I used to use on my eris. It'll be mdpi instead of hdpi, but taking a look at its files might help you out.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://forum.xda-developers.com/showpost.php?p=6270955
EDIT: You might also try making a metamorph or update.zip to apply the new widget. Sometimes that works better than an adb install.
mixedlemon said:
EDIT: You might also try making a metamorph or update.zip to apply the new widget. Sometimes that works better than an adb install.
Click to expand...
Click to collapse
Thanks. I will give the update.zip approach a shot.
Have you tried pushing the modified apk file without signing it first?
Oddity said:
Have you tried pushing the modified apk file without signing it first?
Click to expand...
Click to collapse
Actually no I haven't. Worth a shot Thanks
Well, that was weird... Pushing it unsigned worked. I never thought to try that since any add on apk's I have done needed to be signed.
Thank you
So, to summarize:
Code:
1) Open apk with 7zip and leave it open
2) Extract res folder to desktop
3) Modify graphics or whatever (I only did graphics)
4) Drag the res folder over the zip window and drop
5) Exit 7zip
6) Go into recovery mode and mount /system
7) Connect phone to pc
8) Open cmd and cd to your sdk folder where you put the apk
9) Push to original folder (in this case adb push HtcClockWidget.apk /system/app) on phone in recovery mode
Happiness
Awesome, glad you got it to work. The way I usually do it is to push any apk unsigned first, and if I have problems try it again but sign first.
Oddity said:
Awesome, glad you got it to work. The way I usually do it is to push any apk unsigned first, and if I have problems try it again but sign first.
Click to expand...
Click to collapse
I guess I just got hung up on signing since I have never had luck with unsigned. However, this was my first attempt at a built in apk.
Thanks again
Just incase anyone likes the silver on black numbers for their clock like I do I decided to post my mods to HtcClockWidget.apk
This is based on the stock 2.2 widget but may work on 2.1 ROM's
Requires being rooted so just use adb to push it to /system/app folder
Back up your original just incase you want to go back
NilsP said:
Just incase anyone likes the silver on black numbers for their clock like I do I decided to post my mods to HtcClockWidget.apk
This is based on the stock 2.2 widget but may work on 2.1 ROM's
Requires being rooted so just use adb to push it to /system/app folder
Back up your original just incase you want to go back
Click to expand...
Click to collapse
looks awesome thxs
tried pushing. but it doesnt seem to be going to the /systems/apps folder using the (adb push HtcClockWidget.apk /system/app)
RLKirk said:
tried pushing. but it doesnt seem to be going to the /systems/apps folder using the (adb push HtcClockWidget.apk /system/app)
Click to expand...
Click to collapse
Have you tried to push it in recovery mode with system mounted.
NilsP said:
Have you tried to push it in recovery mode with system mounted.
Click to expand...
Click to collapse
yeah i went to recovery checked to make sure it seen my device mounted system and pushed it done the size and time thing in dos as if it pushed the apk but then when i went and looked in the folder it was not there and i cant push the original clock back either lol... idk what it is
RLKirk said:
yeah i went to recovery checked to make sure it seen my device mounted system and pushed it done the size and time thing in dos as if it pushed the apk but then when i went and looked in the folder it was not there and i cant push the original clock back either lol... idk what it is
Click to expand...
Click to collapse
Not sure how to help. I just boot into hboot start, recovery mode, go to mount and mount system then open the cmd prompt and do the adb push HtcClockWidget.apk /system/app and all goes well. Have done it multiple times with changes
I am assuming you have the USB drivers installed and not HTC Sync.
When I ran SRS 2.5.2 it had the MOD for the silver clock widget, I now have 3.1 RC3 but when I try your method, "adb push HtcClockWidget.apk /system/app" it uninstalls the stock one but does not install the new one. I have to flash a Nandroid backup to restore it. What am I doing wrong? I really liked the one from 2.5.2 and want it again.
Update.zip
Sent from my ADR6300 using Tapatalk
Yeah, tried that. No good. I uninstalled the original and still no good. Now I have to reflash again. Any other ideas?
i pushed the file from post number 9 into system app and it shows up as being in system/app in root explorer but i no longer have it in my widgets list. i even tried pushing the old one back and i still have no clock in my widget list. what do i do?
jasonb1985 said:
i pushed the file from post number 9 into system app and it shows up as being in system/app in root explorer but i no longer have it in my widgets list. i even tried pushing the old one back and i still have no clock in my widget list. what do i do?
Click to expand...
Click to collapse
I can understand it not working if you are on other than a stock 2.2 ROM since it is from the stock. What I don't understand is why pushing you original backup back isn't working.
Can you reinstall it from your Nand backup?
NilsP said:
I can understand it not working if you are on other than a stock 2.2 ROM since it is from the stock. What I don't understand is why pushing you original backup back isn't working.
Can you reinstall it from your Nand backup?
Click to expand...
Click to collapse
i did a nandroid restore, back to where i was before. its just weird that its not working.
Hi all,
I have successfully flashed ROMS for my Gtab for over a month now. Tonight, though I have a problem. I decided to to NVFlash back to stock (which I have done successfully several times), so APX mode works. However, THIS time, the Gtab does what I believe is that Bootloop thing. I have read threads about it, but I don't quite understand what I do to fix it.
So I get into APX mode - then what? Again - Again, I have tried NVFlash and this time it will not boot into stock - It just loops from the Viewsonic screen to the G Tablet screen over and over again.
I appreciate being rescued from my disaster.
Thanks!
Mark
mlinder1958,
I am understanding you have nvflashed and are having boot loops.
If so, you can usually re-partition with ClockWorkMod and that normally will
fix it.
http://forum.xda-developers.com/showthread.php?t=844088
When you get CWM installed, reboot into recovery (CWM) with power/volume+. Go to the
advanced menu and partition. Take a few minutes--don't panic. The Fix Permissions.
Then Wipe Dalvic Cache. The go back to the Main Menu and Wipe Cache and then
Wipe/Reset Factory Data. The reboot and hopefully you will come up running right.
If not, the re-do the nvflash back to stock.
Hope this helps.
Rev
Hi Rev,
Thanks for replying.
Here is the problem. When I enter APX mode, I hear the PC (Windows 7) make its little beep sound and the gtab screen goes blank, but there is no dos prompt window opening in windows unless I run the gtablet .bat file. This is where I am confused. Since i am getting into apx mode, how do i move put recoery and update.zip back onto the gtablet since no indication (drive letter) of the gtablet appears?
Again, I can run NVFlash and the dos prompt appears, showing the progress and the gtablet black screen displays the nvflash info at the top.
I know I need to get CWM back on there. I just don't know how to do it from APX mode withou a drive letter appearing.
Thanks again.
Mark
mlinder1958,
I gave you the CWM link so you could download the correct CWM file.
Now we need someone to come along who can tell you how to use nvflash
to load CWM into your tablet. I have never used that procedure as I have
used my microSD card in /SDCARD2 whenever I have needed it.
I will see if I can find the procedure, but you need to be looking too. If you
can flash CWM on the tablet, then you can follow my repair process.
Rev
To fash CWM recovery with nvflash, you follow the same procedure as flashing back to stock but replace part9.img in the stock image with the .img file extracted from the cwm zip download rnamed to part9.img.
So I rename update.zip to part9.img?
mlinder1958 said:
So I rename update.zip to part9.img?
Click to expand...
Click to collapse
Unzip and extract the recovery.img - then rename THAT to part9.img (and backup the old file first, of course).
roebeet,
Oh man, what an honor!
Anyway, when I extract the zip it gives me the recovery folder and the update.zip file, which I am famliar with. Howewver, I see no recovery.img file. Or did I find/unzip the wrong file?
sorry for the long drawn out call for HELP
Mark
confirmed. I am confused. I cannot find any file called recovery.img after I unzip the CWM 08 zip file.
any help is appreciated.
Mark
The recovery.img is inside the update.zip... keep extracting ;-)
The recovery.img is inside the update.zip. It's a "file inside a zip inside a zip". I used to do this early on, but later started using rar files to make it less confusing.
No worries on the thread - you made me blush.
Roebeet and Rev,
I AM DE-BRICKED!
Thank you so much for your help.
Maybe a oughtta tone down my flashing for awhile : )
You guys ROCK!
Mark
Glad to hear! Many thanks to Rev for all the good advise!
Everyone,
Let's just all celebrate.
When I read a post from someone with a major or hard problem and sense the sadness,
it really makes me sad too.
It is so great to help someone and see that sadness become joy!! Anybody that
wouldn't like that has to be a rock head!!
Mark, now just ENJOY!!
Rev
Thank you everyone who responded to this thread. This also fixed my problem of a bricked/looping system.
when i tried to go back to power + vol + a triangle with "!" shows up. any remedy?
ramerco said:
To fash CWM recovery with nvflash, you follow the same procedure as flashing back to stock but replace part9.img in the stock image with the .img file extracted from the cwm zip download rnamed to part9.img.
Click to expand...
Click to collapse
Do you rename it part9.img or 09_SOS.img?
It seems as if there is no 'part9.img' and just the latter
Edit*Ah part9 is the one in the normal NVFlash and I am trying out nvflash_gtablet_46 to fix my issues
edit2* didn't work for me, a shame
I'm in the same boat as Citi is. Still a no go for me. I have even tried what was described in this thread to no avail:
http://forum.xda-developers.com/showthread.php?t=974422
Here is one thing that I am seeing that I also didn't see mentioned.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The "Can't Mount" error has been consistant for a while. Also something else I forgot was that when connected through USB to the PC, I can't see the device in My Computer. It is there and does allow an NVFlash though.
My gTablet is in the same boat after reflashing it after using VeganTab v7.0. I'm going to try the recovery.img rename this afternoon to get it out of the bootloop.
Hi all
Whipped this up for a friend. Thought we'd be nice and share
These packages will work on any current sw version for the Charge.
Please find below kernel and recovery packages hacked for the following:
permanent adb root
installs Superuser and su binary automatically on boot
includes Voodoo ext4 lagfix - CREDIT TO SUPERCURIO! http://project-voodoo.org/lagfix
lowmemorykiller tweaks
sdcard readahead cache speed tweak
If you are using Odin to flash, simply flash the below package. If you are using Heimdall, remove the zImage file from the below package and flash it.
After flashing the first time, you will hear a voice from the phone telling you what is occurring. The conversion to ext4 will take a few minutes. BE PATIENT. Once it boots, Superuser should be installed, and your phone's filesystem will be converted from rfs to ext4. To disable Voodoo lagfix and convert back to rfs, simply create a file on your sdcard inside the Voodoo folder, named "disable-lagfix". Then reboot your phone and listen for the voices again. This will also take a few minutes.
Please familiarize yourself with using Odin or Heimdall and have backup images on-hand if you are going to use this kernel. If you screw up, you will need them
I DO NOT have a Charge, these files have been tested by other users. As always I assume absolutely NO liability for anything that happens if you use this kernel. Phone blows up? It's on you to fix it
If you find this software helpful please click the "Thanks" or the "Donate" button. Either is fine by me. If you would like to investigate the changes that were made, please feel free to find them here, and here.
Enjoy.
EDIT
Uploaded 2nd version
EDIT
Uploaded 3rd version
changed the install scripts around
should copy files more efficiently
fix file ownership and permissions
UNTESTED!
EDIT
Uploaded 4th version
Confirmed root from independent user!
rewrote install process to preserve file path and permissions
will look into the bootanimation graphics issue
http://dl.dropbox.com/u/14764513/VoodooChargeKernel4.tar.md5
EDIT
Uploaded additional recovery file
Flashes custom version of ClockworkMod recovery 3.x
Recovery includes Voodoo specific options for enabling/disabling Voodoo lagfix
Flash with Odin or Heimdall just like the kernel files
HAS BEEN LIGHTLY TESTED! USE CAUTION AND HAVE A BACKUP!
if you do not have root:
* check adb shell and see if you get a '#' prompt. If so, you *have* root on adb, and you may install whatever you want in /system
* check to see if Superuser app is installed
* check to see if /system/xbin/su exists on your phone.
If you have problems, please post the results of those checks. Thanks.
LLGW. Headed to bed now but first thing in the morning, I wondering what I'm doing
Thanks jt!!!! Can't wait to flash this once my charge comes in the mail.
Sent from my SCH-I500 using XDA App
Ok, somebody use this to system dump ED2.
And, uh, is there matching Voodoo clockwork?
s44 said:
Ok, somebody use this to system dump ED2.
Click to expand...
Click to collapse
please
And, uh, is there matching Voodoo clockwork?
Click to expand...
Click to collapse
probably not
What verison of odin should I use? I just flashed this and it failed.
using odin3 v1.3 and failed too..
phone wont boot, had to reflash ed1
The kernel flash was successful, and the filesystem conversion took about 8 minutes to run. However, I was not rooted when the phone booted back up. Here is what I did, let me know if I missed a step:
Start on rooted ED1
Accept ED2 OTA
Lose Root
Flash new kernel using ODIN
After ~10 minutes, phone boots successfully, but I do not have root.
asenduk said:
using odin3 v1.3 and failed too..
phone wont boot, had to reflash ed1
Click to expand...
Click to collapse
Keep trying. I finally got it to flash with 1.30. Seems to be booting. On boot it did not change the file system, it just booted normally.
Edit:I just put in my spare battery and it is now converting the file system. The other battery was probably too low.
Where's my wifi? Anyone else facing an error when attempting to start wifi?
Yeah it looks like it killed wifi. I also am not rooted.
So if I flash back to rooted ED1 will it wipe my data?
azhockey said:
So if I flash back to rooted ED1 will it wipe my data?
Click to expand...
Click to collapse
I just reversed the filesystem changes and then flashed back to ED1. My data appears to be intact.
moondrius said:
Keep trying. I finally got it to flash with 1.30. Seems to be booting. On boot it did not change the file system, it just booted normally.
Edit:I just put in my spare battery and it is now converting the file system. The other battery was probably too low.
Click to expand...
Click to collapse
had to rename the file to .tar.md5 now its working..
asenduk said:
had to rename the file to .tar.md5 now its working..
Click to expand...
Click to collapse
I was able to flash with it just named .tar, using ODIN 1.85. Did you retain your root access after the renamed flash?
Updated OP with a new version. Anyone who has flashed the original version, please check adb shell and see if you get a '#' prompt. If you do, then you're technically rooted
NotATreoFan said:
I was able to flash with it just named .tar, using ODIN 1.85. Did you retain your root access after the renamed flash?
Click to expand...
Click to collapse
Superuser was installed but root was lost... Trying the updated version... On a positive note Quadrant is great! 1400-1550 avg
EDIT: wifi fixed with v2 but still no root.. will try from scratch and report back
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Everything has worked for me. Thank you.
Sent from my ADR6400L using XDA Premium App
yes im obviously a newb for asking this question but i have odin and have downloaded the kernal tar file. how am i supposed to flash it onto the phone now? Ive found how to put the phone into download mode i just dont know what im supposed to do with odin
devanmc said:
yes im obviously a newb for asking this question but i have odin and have downloaded the kernal tar file. how am i supposed to flash it onto the phone now? Ive found how to put the phone into download mode i just dont know what im supposed to do with odin
Click to expand...
Click to collapse
Click PDA and select the file then just hit start
Please help. Try to install Tiamat on my Xoom. I am wrote zip-file with ROM on sd-card. After that reboot in recovery mode. Was done wipe data and factory rest.
After that choose "Apply update from USB drive" and get error: E:failed to mount /sdcard (No such file or directory). What is problem?
Please refer to this thread.
Mutantz said:
Please help. Try to install Tiamat on my Xoom. I am wrote zip-file with ROM on sd-card. After that reboot in recovery mode. Was done wipe data and factory rest.
After that choose "Apply update from USB drive" and get error: E:failed to mount /sdcard (No such file or directory). What is problem?
Click to expand...
Click to collapse
Do you have ClockworkMod. Recovery solarnz version R4c installed? What sdcard are you flashing the zip file from? You chose the wrong option from the recovery menu...you need to choose "install zip file from sdcard" or something like that. Then "choose zip file" navigate to it and choose it,
If you are trying to flash the zip file from your 'internal' sdcard, it won't work. You need a physical micro sdcard, inserted in your Xoom.
HuckFinn said:
Please refer to this thread.
Click to expand...
Click to collapse
How I can instal CWM from zip file, if I can't select zip-file in recovery mode? Error the same as in first message.
Problem solved. Thank you for help!
But now have other problem. After flashing Tiamat-Xoom-Rom-2.2.1.Moray.zip device is not boot. I only see animated screen with water waves. Screen blinkink time from time. What this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Same Issue with Blue Phokus!Tiamat Screen
Let me give you some specifics on exactly what I tried to do, maybe I made an obvious mistake that lead to this problem.
First I am am on a stock kernel Xoom that has had CWM Recovery flashed and a new boot.img flashed so that I could root it. I did that a few weeks ago so that I could start taking advantage of some of the superuser applications I wanted to use. It did not take me long to realize that I still seemed to be locked down a bit as far as overclocking and the like. So I decided to start considering custom roms/kernels. I decided to go with the Tiamat-Xoom-Rom-2.2.2.Moray.zip. I opened up CWM Rom Manager and go to install ROM from SD Card, and go to my downloads folder and choose the zip. From there CWM takes over on backing up / installing the new ROM. However, it will never get past that blue splash screen. I was able to reboot into recovery and load a backup I took right before trying to load the ROM. However, any help getting the ROM to work would be appreciated.
Caldaga said:
Let me give you some specifics on exactly what I tried to do, maybe I made an obvious mistake that lead to this problem.
First I am am on a stock kernel Xoom that has had CWM Recovery flashed and a new boot.img flashed so that I could root it. I did that a few weeks ago so that I could start taking advantage of some of the superuser applications I wanted to use. It did not take me long to realize that I still seemed to be locked down a bit as far as overclocking and the like. So I decided to start considering custom roms/kernels. I decided to go with the Tiamat-Xoom-Rom-2.2.2.Moray.zip. I opened up CWM Rom Manager and go to install ROM from SD Card, and go to my downloads folder and choose the zip. From there CWM takes over on backing up / installing the new ROM. However, it will never get past that blue splash screen. I was able to reboot into recovery and load a backup I took right before trying to load the ROM. However, any help getting the ROM to work would be appreciated.
Click to expand...
Click to collapse
You will need to go into recovery menu, choose: wipe data/factory reset, then reboot. If you change roms, in this case from stock to Tiamat Moray, you will need to wipe/factory reset. Otherwise, bootloops.
Thanks and a couple questions
i had read that I had to do a factory reset /restore before doing this and thought that might be the problem. I appreciate the quick response a couple questions I have.
Will this reset also reset my boot.I mg and recovery? Do I have to catch the boot sequence back into recovery before it reboot after the reset to avoid issues or let it boot fully? I do appreciate the help.
Caldaga said:
i had read that I had to do a factory reset /restore before doing this and thought that might be the problem. I appreciate the quick response a couple questions I have.
Will this reset also reset my boot.I mg and recovery? Do I have to catch the boot sequence back into recovery before it reboot after the reset to avoid issues or let it boot fully? I do appreciate the help.
Click to expand...
Click to collapse
No a "wipe data/factory reset" will only wipe/reset your data to the basic level of the most recent rom you flashed. You need to do this to clear out anything from earlier versions that might conflict with the new rom.
Hey, I'm a total noob but I have been diggin around. Rooted my first phone after bricking it a few times before installing this, which finally unbricked my phone leaving it rooted: http://forum.xda-developers.com/showthread.php?t=1193927
but my problem now is, when I try to install modded 3e recovery by replacing the old recovery file(http://forum.xda-developers.com/showthread.php?t=1091465) in /system/bin I find it that there is nothing there, instead the recovery file shows up in the root folder... which is pretty messed up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have tried replacing the recovery file in the root folder and placing it into the /system/bin folder, nothing seems to work... It could have to do with the cracked version of Root Explorer I have... but that seems unlikely as the recovery file is simply not where it's spposed to be. And as expected, it still checks signature rendering me unable to install CMW (http://forum.xda-developers.com/showthread.php?t=1107881)
I have resorted to other methods such as the one described by this user:
JOJO_SSC said:
1. Flash to stock Rogers UXKG3 Gingerbread packages (rooted) with odin packet.
http://forum.xda-developers.com/showthread.php?t=1193927
2. Install SGS kernel flasher from market or apk file.
http://forum.xda-developers.com/showthread.php?t=877444
3. Download kernel Infusion-GB.1.0 put in SDcard.
http://forum.xda-developers.com/showthread.php?t=1212485
4. Open SGS kernel flasher choose kernel...zip and flash kernel, waiting for restart
5. Now, your phone will have ClockWork Mod (CWM) for install custom rom.
6. Choose custom rom and follow method.
Enjoy.
Sorry, i m not good in english.
Click to expand...
Click to collapse
But my phone gets stuck at the samsung screen and starts speaking in a robotic voice saying something about not enough room in system partition...
I have also tried to flash this ROM: http://forum.xda-developers.com/showthread.php?t=1092021
which comes with the modded 3e recovery... same issue, except I was able to get into the recovery mode once, and it was indeed CMW, but after factoy resetting and clearing the cache it still gets stuck at samsung screen and a robotic voice comes on saying the same thing.
If anyone has any idea or could point me in the right direction, it would be much apprecieated.
Thanks
The easiest thing to do is put your phone in download mode while connected to Odin and flash the community kernel from the superthread....this will give you red cwm ....the voice you are hearing is voodoo lagfix activating...wipe data, cache,and dalvik cache....format system and data...fix permissions and then flash your desired rom....
Sent from my SAMSUNG-SGH-I997 using xda premium
every time I do it my phone seems to brick.
...EDIT: nvm fixed it, forgot to disable lagfix
Nice. Glad i found this. you disable lagfix by putting the Voodoo file on ur internal sd right? the one with disable-lagfix? or should these b deleted ? ugghhh
jafrow said:
Nice. Glad i found this. you disable lagfix by putting the Voodoo file on ur internal sd right? the one with disable-lagfix? or should these b deleted ? ugghhh
Click to expand...
Click to collapse
I can't remember offhand but if you Google disable voodoo lagfix or search in the QA thread, you should get some hits. It wasn't hard from what i remembered...empty folder or somthing like that...also can be disabled in cwm...there's a voodoo lag disable.
Important to keep straight rfs files system from voodoo. You'll boot loop...i found that out the hard way.
Disable lag fix before flashing community kernel. Or be bootlooped.
Sent from my SAMSUNG-SGH-I997 using xda premium
Ive done this ,also disabled lagfix. still no recovery file in system/bin ....
EDIT: sorry by "this" i meant
Originally Posted by JOJO_SSC
1. Flash to stock Rogers UXKG3 Gingerbread packages (rooted) with odin packet.
http://forum.xda-developers.com/show....php?t=1193927
2. Install SGS kernel flasher from market or apk file.
http://forum.xda-developers.com/showthread.php?t=877444
3. Download kernel Infusion-GB.1.0 put in SDcard.
http://forum.xda-developers.com/show....php?t=1212485
4. Open SGS kernel flasher choose kernel...zip and flash kernel, waiting for restart
5. Now, your phone will have ClockWork Mod (CWM) for install custom rom.
6. Choose custom rom and follow method.
Enjoy.
Sorry, i m not good in english.
Click to expand...
Click to collapse
Then I also tried deleting the Voodoo file, reboot... still no recovery in system/bin... its on my root as first posted by jakjak
sorry people don't seem to read the title. don't use community kernel that's froyo. use the kernel in the Rogers root thread, infusion gb a2, hellrsiser, or entropy dd. if you have already rooted then sgs kernel flasher creates less confusion because you don't have to worry about what form the package is in. it can flash .tar.md5, .zip and other package types with or without internal folders.
since its having trouble with the lagfix create /sdcard/Voodoo/disable-lagfix
the V in Voodoo is capital and all others are lower case. disable-lagfix can be either a text file name or an empty folder. it just look for the path, not anything in it.
then you will have red cwm and be free to flash whatever.