Related
This is a hybrid Theme of GorillaSense-DHD-MT4G-Gloss Carbon Fiber, and GorillaSense DHD-MT4G Revolution, done by request.
{
"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"
}
IT HAS THE THEMED CAMERA.APK IN IT SO YOU WILL NOT NEED TO FLASH THE FIX I POSTED FOR FCC IN GR8'S CARBON THREAD
HEAD ON OVER TO THE to the Gorilla Development Page UNDER THEMES AND ADD ONS.
Does this theme have folding or flying animation?
Nirvana Rules said:
Does this theme have folding or flying animation?
Click to expand...
Click to collapse
flying I believe.
Thanks will give it a try.
wow the colors are amazing on this theme makes it a completely new phone
I installed this theme right after I flash the GorillaSens DHD-MT4G v2.3 ROM and it said operation abort. I used cwm 3.0.0.6
Has anybody flash this theme OK ? Please help.
Oscarkb said:
I installed this theme right after I flash the GorillaSens DHD-MT4G v2.3 ROM and it said operation abort. I used cwm 3.0.0.6
Has anybody flash this theme OK ? Please help.
Click to expand...
Click to collapse
its the recovery. the update zip isn't signed correctly for that recovery so it will stop it every time
tiger013 said:
its the recovery. the update zip isn't signed correctly for that recovery so it will stop it every time
Click to expand...
Click to collapse
Anything I can do to make it NOT stop?
Like flash recovery to 3.0.0.2, 3.0.0.5 ?
I did try with 2.5.14 but I can not get into it.
Oscarkb said:
Anything I can do to make it NOT stop?
Like flash recovery to 3.0.0.2, 3.0.0.5 ?
I did try with 2.5.14 but I can not get into it.
Click to expand...
Click to collapse
it will only work on the older 2.5.14 recovery.
tiger013 said:
it will only work on the older 2.5.14 recovery.
Click to expand...
Click to collapse
So if I flash to 2.5.14 recovery, push the theme to sd card and intsall via Linda Manager, it should work, right?
I don't see any where in this thread that mention this theme does not work with new recovery.
Oscarkb said:
So if I flash to 2.5.14 recovery, push the theme to sd card and intsall via Linda Manager, it should work, right?
I don't see any where in this thread that mention this theme does not work with new recovery.
Click to expand...
Click to collapse
you can not apply the theme through a file manager. you can us rom manager to install or through recovery. put zip on sd. then reboot into recovery, then choose zip from sd . then scroll to the theme and select it and install.
tiger013 said:
you can not apply the theme through a file manager. you can us rom manager to install or through recovery. put zip on sd. then reboot into recovery, then choose zip from sd . then scroll to the theme and select it and install.
Click to expand...
Click to collapse
OK, I use Rom Manager and fashed to 2.5.14 recover image.
Reboot into recovery mode
Press volume up + Power, install update from sd
and get this error
E: can't open /cache/recovery/command
second try by wiping the cache, got error
E:signature Verification failed
Installation aboarted.
Let me try with recovery image 3.0.0.6 to see what happen
Man, I love the theme and can not install
Reflash with recovery 3.0.0.6, reboot into recovery and install update.zip from sdcard and get this error:
Amend scripting (update-scipt) is no longer supported.
I am doomed
that was my mistake. I still have clockworkmod recovery 2.5.1.2 not 2.5.1.4 and it worked fine.
Oscarkb said:
OK, I use Rom Manager and fashed to 2.5.14 recover image.
Reboot into recovery mode
Press volume up + Power, install update from sd
and get this error
E: can't open /cache/recovery/command
second try by wiping the cache, got error
E:signature Verification failed
Installation aboarted.
Let me try with recovery image 3.0.0.6 to see what happen
Man, I love the theme and can not install
Click to expand...
Click to collapse
If you are using my Recovery zip you need to:
Choose 3.0.0.5 from "All clockworkMod recoveries" (its really 3.0.0.6)
Reboot into recovery using Rom Manager.
Choose "install zip from sd card"
Choose the zip you want to install and install it.
TrueBlue_Drew said:
If you are using my Recovery zip you need to:
Choose 3.0.0.5 from "All clockworkMod recoveries" (its really 3.0.0.6)
Reboot into recovery using Rom Manager.
Choose "install zip from sd card"
Choose the zip you want to install and install it.
Click to expand...
Click to collapse
That is exactly what i did.
I use Rom Manager and select "All clockworkMod recoveries" and choose 3.0.0.5
It said fash is good. The reboot into recovery, I even wipe cache, install zip from sd card.
I did what you just said and still get installation aborted.
I even try with toggle signature verification and toggle scipt assert.
Still NO GOOD.
The device I have is MT4G/Glacier, is it have anything to do with it?
I can install Gorilla_Carbon skin perfectly fin.
tiger013 said:
that was my mistake. I still have clockworkmod recovery 2.5.1.2 not 2.5.1.4 and it worked fine.
Click to expand...
Click to collapse
Let me try 2.5.1.2
WOOHOO!!!
I reflashed with 2.5.1.2, reboot into recovery using Rom Manager
In recovery, chose insatll zip from sd and the install went fine. No more error.
Thanks a million, I can go to sleep now
Oscarkb said:
That is exactly what i did.
I use Rom Manager and select "All clockworkMod recoveries" and choose 3.0.0.5
It said fash is good. The reboot into recovery, I even wipe cache, install zip from sd card.
I did what you just said and still get installation aborted.
I even try with toggle signature verification and toggle scipt assert.
Still NO GOOD.
The device I have is MT4G/Glacier, is it have anything to do with it?
I can install Gorilla_Carbon skin perfectly fin.
Click to expand...
Click to collapse
I HAVE NOT UPDATED THE SCRIPT. IT WILL NOT WORK ON ANY OTHER RECOVERY BUT clockworkmod recovery 2.5.1.2 not 2.5.1.4
if you are still have problems after flashing 2.5.1.2 then let me know and i will take a look at it tomorrow.
i will be updating all my themes for the newer recoveries sometime this week. ive been really tied down and just havent had a chance to get to them.
TrueBlue_Drew said:
If you are using my Recovery zip you need to:
Choose 3.0.0.5 from "All clockworkMod recoveries" (its really 3.0.0.6)
Reboot into recovery using Rom Manager.
Choose "install zip from sd card"
Choose the zip you want to install and install it.
Click to expand...
Click to collapse
thank you man for trying to help. i wasnt reading it right either at first.
tiger013 said:
I HAVE NOT UPDATED THE SCRIPT. IT WILL NOT WORK ON ANY OTHER RECOVERY BUT clockworkmod recovery 2.5.1.2 not 2.5.1.4
if you are still have problems after flashing 2.5.1.2 then let me know and i will take a look at it tomorrow.
Click to expand...
Click to collapse
Thank you very much for your kindness and all your work.
I got it working with 2.5.1.2
I already post the woohoo message just above your post.
Hello XDA
I was wondering if there possibility for me to, flash (or use an app) an kernel to my stock rom? I am rooted, but I have stock recovery.
Also to be 100% sure: There is a risk of flashing a kernel right?
TheStigx said:
Hello XDA
I was wondering if there possibility for me to, flash (or use an app) an kernel to my stock rom? I am rooted, but I have stock recovery.
Also to be 100% sure: There is a risk of flashing a kernel right?
Click to expand...
Click to collapse
You can flash kernel with CWM app or odin mobile and after you'll have custom recovery.
There is a small risk that you will softbrick the phone.
This means that you can encounter some startup problems or just plain broken phone.
But dont worry, soft bricks are almost harmless and all problems have an easy solution nowadays.
Gent.XDA said:
There is a small risk that you will softbrick the phone.
This means that you can encounter some startup problems or just plain broken phone.
But dont worry, soft bricks are almost harmless and all problems have an easy solution nowadays.
Click to expand...
Click to collapse
Yeah, I thought that too. But I have read those threads about how to recovery it from soft brick, and I think it isn't a problem.
078gregory said:
You can flash kernel with CWM app or odin mobile and after you'll have custom recovery.
Click to expand...
Click to collapse
Oh, What CWM app? You mean rom manager? That can only help me with roms
TheStigx said:
Yeah, I thought that too. But I have read those threads about how to recovery it from soft brick, and I think it isn't a problem.
Oh, What CWM app? You mean rom manager? That can only help me with roms
Click to expand...
Click to collapse
Do not use rom manager .
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
from the guide in stickies .
Clockworkmod is a 'custom recovery' made by xda member koush. Every phone had a recovery partition designed so that if the user messes up a ROM installation, they can recover their phone. CWM is a modified recovery installed into the recovery partition that allows advanced control over ROM recovery, installation and much more.
Features of CWM include:
- NANDroid Backup, This allows you to completely back up your existing ROM with all its files, data and apps
- Restore Backup, Restores a previous backup (obviously...)
- ROM installation, Allows you to install a ROM contained inside a flashable .zip file
- Wipe data/Factory reset, completely erases all of your data contacts, apps etc, leaving your phone 'as new'
Amongst others...
How to install CWM
If you have already rooted your phone using the CF-root Kernel, then you already have CWM! If not, then just install the kernel linked to above in the 'how to root your phone' section
How to make a NANDroid backup using CWMBackups are important because they allow you to restore your ROM incase flashing goes wrong, or you phone starts playing up and displaying wierd bugs.
To make a backup, you need to boot into CWM recovery (done through the 'cwm' app installed onto your phone when you flash the cf-root kernel). Then, you need to navigate down to 'backup/restore' using the volume keys, and select it using the home key. From here, just click 'backup' and you are all set! Leave your phone make the backup (its takes some time) and then just reboot when it tells you its finished. To restore your backup, do the same but instead of clicking backup, click 'restore' instead. Choose which backup you would like to restore and leave the phone to do its magic. Done.
How to install a ROM using CWMInstalling a ROM using CWM is a lot less hassle then installing via Odin. The ROM developer will specify which method of installing their ROM you can use, but it is usually done by a CWM flashable .zip.
To flash:
1. Boot into CWM as described above
2. Navigate to 'install zip from sd card'
3. Select it, and then navigate to 'install zip from sdcard' again!
4. Select the ROM you downloaded from your sd card
5. Navigate down to yes
6. Let CWM install you new ROM!
jje
TheStigx said:
Oh, What CWM app? You mean rom manager? That can only help me with roms
Click to expand...
Click to collapse
Go to Chainfires thread in Original android development section and download the cf root file that match to your current rom.
Flash it with odin, You will have custom CWM
That would be a good idea!
{
"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"
}
JJEgan said:
Do not use rom manager .
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
from the guide in stickies .
Clockworkmod is a 'custom recovery' made by xda member koush. Every phone had a recovery partition designed so that if the user messes up a ROM installation, they can recover their phone. CWM is a modified recovery installed into the recovery partition that allows advanced control over ROM recovery, installation and much more.
Features of CWM include:
- NANDroid Backup, This allows you to completely back up your existing ROM with all its files, data and apps
- Restore Backup, Restores a previous backup (obviously...)
- ROM installation, Allows you to install a ROM contained inside a flashable .zip file
- Wipe data/Factory reset, completely erases all of your data contacts, apps etc, leaving your phone 'as new'
Amongst others...
How to install CWM
If you have already rooted your phone using the CF-root Kernel, then you already have CWM! If not, then just install the kernel linked to above in the 'how to root your phone' section
How to make a NANDroid backup using CWMBackups are important because they allow you to restore your ROM incase flashing goes wrong, or you phone starts playing up and displaying wierd bugs.
To make a backup, you need to boot into CWM recovery (done through the 'cwm' app installed onto your phone when you flash the cf-root kernel). Then, you need to navigate down to 'backup/restore' using the volume keys, and select it using the home key. From here, just click 'backup' and you are all set! Leave your phone make the backup (its takes some time) and then just reboot when it tells you its finished. To restore your backup, do the same but instead of clicking backup, click 'restore' instead. Choose which backup you would like to restore and leave the phone to do its magic. Done.
How to install a ROM using CWMInstalling a ROM using CWM is a lot less hassle then installing via Odin. The ROM developer will specify which method of installing their ROM you can use, but it is usually done by a CWM flashable .zip.
To flash:
1. Boot into CWM as described above
2. Navigate to 'install zip from sd card'
3. Select it, and then navigate to 'install zip from sdcard' again!
4. Select the ROM you downloaded from your sd card
5. Navigate down to yes
6. Let CWM install you new ROM!
jje
Click to expand...
Click to collapse
kachrukamble said:
Go to Chainfires thread in Original android development section and download the cf root file that match to your current rom.
Flash it with odin, You will have custom CWM
Click to expand...
Click to collapse
But I wish to keep my stock recovery. Can't I use this recovery : http://forum.xda-developers.com/showthread.php?t=1501719
?
EDIT:
I find solution : http://forum.xda-developers.com/showpost.php?p=37897681&postcount=22
Hi,
The Recovery – ClockworkMod 5.5.0.4 is very poor... Can't Save/Restaure the ROM.
h**p://droidbasement.com/db-blog/?p=2668 (sorry, I'm a new user, I can't post links - ** = tt)
Where can I find a complete CWM ?
Thank you
Le Dam said:
Hi,
The Recovery – ClockworkMod 5.5.0.4 is very poor... Can't Save/Restaure the ROM.
h**p://droidbasement.com/db-blog/?p=2668 (sorry, I'm a new user, I can't post links - ** = tt)
Where can I find a complete CWM ?
Thank you
Click to expand...
Click to collapse
I've found in this link another Recovery and very h**p://forum.xda-developers.com/showthread.php?t=1080028 but where can I download it ?
Is it better or not of mine (5.5.0.4) ?
Thank you... I need your help
CWM 6.0.1.5
What's the issue with the 5.5.0.4? I'm still using it and don't have any problems with it?
Hi XaMaB,
Thank you for your interest
First, sorry for my bad english, I usually speak french.
I not realy have a problem with 5.5.0.4 but I do not understand why there are missing features.
Picture of my recovery tablet P7100 10.1v
{
"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"
}
My smartphone (ZTE Blade) has recovery 5.5.0.4 and I can use more fonctions (Backup/Restore, USB, ...).
Do you have more fonctions in the recovery of your Tab P7100 10.1v ?
Thank you
to be continued...
Following :
Well ! It seems that I am not under ClockworkMod but Android recovery !!! -> "Android system recovery <3e>"
I don't understand... I've flashed many times with Odin and it's each time the same.
Maybe I've use a bad file ?
@ XaMaB :
Sorry for this questions:
- Are you sure your link is good for Tab 10.1v P7100 ?
- Can you post a new link with de correct CWM 5.5.0.4 for this tablet ?
Thank you for your help.
I really appreciate
Le Dam said:
Hi XaMaB,
Thank you for your interest
First, sorry for my bad english, I usually speak french.
I not realy have a problem with 5.5.0.4 but I do not understand why there are missing features.
Picture of my recovery tablet P7100 10.1v
My smartphone (ZTE Blade) has recovery 5.5.0.4 and I can use more fonctions (Backup/Restore, USB, ...).
Do you have more fonctions in the recovery of your Tab P7100 10.1v ?
Thank you
to be continued...
Click to expand...
Click to collapse
I had this issue in the past. Try to flash it with fastboot rather than Odin. Search for the guide in the forum.
Install PdaNet Desktop so you will get the correct drivers (worked for me).
Al3cks said:
I had this issue in the past. Try to flash it with fastboot rather than Odin. Search for the guide in the forum.
Install PdaNet Desktop so you will get the correct drivers (worked for me).
Click to expand...
Click to collapse
Thank you Al3cks, but...
...Ghaaaaa ! I'm going crazy
When I make a "temp root" : fastboot boot myrecovery.img : YES !! it work
But when I make a "permanent root" (flash the rom ?) : fastboot flash recovery myrecovery.img, the command windows (Dos mode) say : OKAY sending and OKAY writing but when I reboot in Recovery mode, I'm always in Android System Recovery
Please, help ... I'm near the final solution
Le Dam said:
Thank you Al3cks, but...
...Ghaaaaa ! I'm going crazy
When I make a "temp root" : fastboot boot myrecovery.img : YES !! it work
But when I make a "permanent root" (flash the rom ?) : fastboot flash recovery myrecovery.img, the command windows (Dos mode) say : OKAY sending and OKAY writing but when I reboot in Recovery mode, I'm always in Android System Recovery
Please, help ... I'm near the final solution
Click to expand...
Click to collapse
You probably have a stock ROM. I don't know how, but I think the stock bootloader somehow restores the original recovery. I never tried CWM on the stock rom. After I flashed and booted the custom recovery I always flashed CyanogenMod right after it. If I didn't do this, I would notice I had the default <3e> recovery after an adb reboot recovery command, but didn't give this too much thought.
I once thought I bricked my tablet, I had stock ROM, tried to flash something not meant for P7100 but after 15 minutes of staying with a black empty screen on, the tablet "magically" rebooted back to a fully working rom.
Search for pershoot and ask him more details. That's just what I observed.
What I think is that it is not a good idea to mess with the stock bootloader. If you want custom recovery, flash CyanogenMod and CWM will remain permanent. Otherwise, just let it be, or, when you need advanced recovery functions, use fastboot to boot CWM 6.0.x.x from your computer, do what you have to do, and reboot normally. You will remain rooted even if you have stock recovery.
Thank you Al3cks.
Yes, you're right, I do not want brick my tablet.
But I do not understand why CWM does not install in place of that of Android. Not with with Fastboot, and not with Odin (Fastboot and Odin show a good flash!).
Why?
I really want CWM Recovery on this Tablet because it's possible.
If nobody has arrived to put the CMW, I stopped immediately but many people have this Recovery on the P7100 10.1v tablet.
Now, where still the problem... bad root ?
Is it possible to flash from internal memory (recovery.zip) ???
Please, I do not want to give up, I want this mode! :crying:
Thank you all for your help and your patience...
Le Dam said:
Thank you Al3cks.
Yes, you're right, I do not want brick my tablet.
But I do not understand why CWM does not install in place of that of Android. Not with with Fastboot, and not with Odin (Fastboot and Odin show a good flash!).
Why?
I really want CWM Recovery on this Tablet because it's possible.
If nobody has arrived to put the CMW, I stopped immediately but many people have this Recovery on the P7100 10.1v tablet.
Now, where still the problem... bad root ?
Is it possible to flash from internal memory (recovery.zip) ???
Please, I do not want to give up, I want this mode! :crying:
Thank you all for your help and your patience...
Click to expand...
Click to collapse
Hi,
when you have root, try to install ROM Manager from Play Store..
Try to install Recovery from ROM-Manager..You will have to select Galaxy tab 10.1.
Try if you can go into recovery.
Than flash Recovery.img for 10.1v .. 5.5.0.4 or latest one via fastboot
jensema said:
Hi,
when you have root, try to install ROM Manager from Play Store..
Try to install Recovery from ROM-Manager..You will have to select Galaxy tab 10.1.
Try if you can go into recovery.
Than flash Recovery.img for 10.1v .. 5.5.0.4 or latest one via fastboot
Click to expand...
Click to collapse
Hi jensema,
On another forum, a guy says Rom Manager does not recognize the tablet 10.1v.
Rom Manager knows that like the 10.1 and it may brick the tablet.
But I can't say if this guy say right...
What do you think about this ?
Stay away from ROM Manager on this tablet. And as I said, I don't think you can have CWM recovery, as long as you are on stock rom. The stock rom somehow restores the original recovery on every boot.
Sent from my GT-I9000 using Tapatalk 2
Le Dam said:
Hi jensema,
On another forum, a guy says Rom Manager does not recognize the tablet 10.1v.
Rom Manager knows that like the 10.1 and it may brick the tablet.
But I can't say if this guy say right...
What do you think about this ?
Click to expand...
Click to collapse
I can only tell you what i did today:
had kind of same problem, after flashing recovery, a reboot to recovery took me to custom recovery.
Had those problem today and already in the past.. Or when a recovery flash was succesfully, i can boot to recovery, but reboot option out of recovery took me to recovery again.
Today I flashed Stock 3.0.1 to try the latest cm10.
Again i had problems flashin recovery..
From rootet stock 3.0.1 i Installed ROM manager.
I installed recovery for 10.1 through Rom manager..
and after this i booted to recovery succesfully ..(For me it worked- try at your own risk..)
I went back to fastboot and flashed CWM 6.0.1.5. for 10.1v from pershoot site..without problems..
CWM 6.0.1.5 working.. Problems never occured again..
Al3cks said:
Stay away from ROM Manager on this tablet. And as I said, I don't think you can have CWM recovery, as long as you are on stock rom. The stock rom somehow restores the original recovery on every boot.
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
Well... I just make a big risked experience.
I installed Rom Manager (before response Al3cks) and I flashed CWM Recovery.
After reboot, the tablet stay on a black screen for a few minutes (I was scared) and it restarted on CWM Recovery! Yes ... but for a short time.
And after a normal reboot on ICS, I tried again to restart the CWM Recovery and it was gone!
I back on the recovery of Android.
Al3cks say right, after each start, the original ROM check and removes recovery not original.
Fortunately, this ROM does not relock the bootloader and not uninstalled root!
Conclusion : We can only have another recovery if the tablet is flashed with a custom ROM ?
(and sorry again for my bad english)
Le Dam said:
Well... I just make a big risked experience.
I installed Rom Manager (before response Al3cks) and I flashed CWM Recovery.
After reboot, the tablet stay on a black screen for a few minutes (I was scared) and it restarted on CWM Recovery! Yes ... but for a short time.
And after a normal reboot on ICS, I tried again to restart the CWM Recovery and it was gone!
I back on the recovery of Android.
Al3cks say right, after each start, the original ROM check and removes recovery not original.
Fortunately, this ROM does not relock the bootloader and not uninstalled root!
Conclusion : We can only have another recovery if the tablet is flashed with a custom ROM ?
(and sorry again for my bad english)
Click to expand...
Click to collapse
Then just boot the recovery.
fastboot boot revovery.img
So you can backup/restore and install custom rom as well.
Le Dam said:
Well... I just make a big risked experience.
I installed Rom Manager (before response Al3cks) and I flashed CWM Recovery.
After reboot, the tablet stay on a black screen for a few minutes (I was scared) and it restarted on CWM Recovery! Yes ... but for a short time.
And after a normal reboot on ICS, I tried again to restart the CWM Recovery and it was gone!
I back on the recovery of Android.
Al3cks say right, after each start, the original ROM check and removes recovery not original.
Fortunately, this ROM does not relock the bootloader and not uninstalled root!
Conclusion : We can only have another recovery if the tablet is flashed with a custom ROM ?
(and sorry again for my bad english)
Click to expand...
Click to collapse
From what I observed, and from what you experienced, yes. If you want CWM recovery, flash a custom ROM.
Thanks for interest
Ok, but now my tablet is under ICS official (pure, no Touchwiz, ...)
This ROM is developed from Vodafone and is an official upgrade.
Can you tell me why change ROM to unofficial ICS or JB (without front cam, ..), or another ?
Thank you
Le Dam said:
Thanks for interest
Ok, but now my tablet is under ICS official (pure, no Touchwiz, ...)
This ROM is developed from Vodafone and is an official upgrade.
Can you tell me why change ROM to unofficial ICS or JB (without front cam, ..), or another ?
Thank you
Click to expand...
Click to collapse
Why you need CWM then?
Sent from my GT-P7100 using xda app-developers app
Dryfit.linux said:
Why you need CWM then?
Sent from my GT-P7100 using xda app-developers app
Click to expand...
Click to collapse
Because I often use the Backup-Restore function in CWM
I like testing many APK and when my phone is down, I restore last image.
If I can make Backup/Restore from my tablet, I can test JB rom and if I don't like this, I restore the actually rom in 2 minutes...
Le Dam said:
Because I often use the Backup-Restore function in CWM
I like testing many APK and when my phone is down, I restore last image.
If I can make Backup/Restore from my tablet, I can test JB rom and if I don't like this, I restore the actually rom in 2 minutes...
Click to expand...
Click to collapse
I had a problem with CM10 so I went back to stock ICS and I managed to get CWM 6.0.1.2 to remain permanent. I used fastboot to flash it first (fastboot flash recovery recovery.img), then immediately after this, without rebooting the tablet, while still in fastboot, i ran "fastboot boot recovery.img" and in CWM when I hit reboot system now, it gave me a warning telling me that bootloader may restore default recovery and gave an option to fix this and I selected the option. To my surprise, at the next reboot to recovery I found CWM. I only needed it to root my tablet, I didn't want it permanent, but I don't mind. Go to pershoot's blog (droidbasement) and acces the folder for the CM9 rom. From there, download the recovery archive and extract recovery.img from it.
Sent from my GT-P7100 using Tapatalk HD
---------- Post added at 12:15 PM ---------- Previous post was at 12:11 PM ----------
Link: http://droidbasement.com/galaxy/roms/cm9/p3/
Sent from my GT-P7100 using Tapatalk HD
Most of the people on xda getting error while flashing new update on YU yureka.
so i have created this thread to solve there's problems :highfive:
you just have to follow some steps.
1.you should be on stock recovery.
if you do not have stock recovery then here is LINK
************************************************************
2. now you need big data pack you have to download whole updated stock rom which is approx 643.767 MB
here is LINK.
3. now put this in internal storege(not in any folder or ext_sd card)
4. go to recovery and apply update. and choose this zip file and flash it :good:
and now very important step. Hit thanks button :laugh:
{
"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"
}
Do i need to be on stock Cm12 ROM to do this?? I am currently running Pac Rom.
Thanks!
sunny765 said:
Do i need to be on stock Cm12 ROM to do this?? I am currently running Pac Rom.
Thanks!
Click to expand...
Click to collapse
yes bro if you want update then you should be on stock if you have backup ur stock rom then just restore it.
koi yaar ye recovery ko flashable zip mai kar k dona plss. direct cwm se stock recovery flash ho esa
Rakesh251 said:
koi yaar ye recovery ko flashable zip mai kar k dona plss. direct cwm se stock recovery flash ho esa
Click to expand...
Click to collapse
have tried flishify app?
LINK
flash using this.
i have not tried yes but search.
Why is it 643 mb the update is just 130mb
thearjunraju said:
Why is it 643 mb the update is just 130mb
Click to expand...
Click to collapse
'cos it's the "whole updated stock rom", i.e., stock rom + the latest update rolled into one convenient easy-to-use package. read the op.
i was reading stock kernel was needed
i know kernel is usually in the full build
so
1. do we need the stock kernel?
2. Will TA backup work?
3. do we need to clear cache and data?
4. Will the existing 3rd party kernel and recoveries work after the update?
As far as I know from my limited flashing experience, the custom kernel will get overwritten by those present in the ROM being flashed.
Sent from my A0001 using XDA Free mobile app
oemaritradey said:
i know kernel is usually in the full build
so
1. do we need the stock kernel?
2. Will TA backup work?
3. do we need to clear cache and data?
4. Will the existing 3rd party kernel and recoveries work after the update?
Click to expand...
Click to collapse
1. you should be on stock kernel.
2.after upgrading your mobile you should take backup again. becoz why you want to revert back to older version ?
3.no need to clear cache and data.
4. yes you can flash any kernel and recovery . i had updated it and i am on TWRP.
*************************************************************************************************************************
feeroz123 said:
As far as I know from my limited flashing experience, the custom kernel will get overwritten by those present in the ROM being flashed.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
yes you are right but still there is thread on yu forum for it and they said that you should be on stock kernel by the way you can flash it on your current kernel if you see any error then you can flash stock kernel and flash this update
ashish_zarekar said:
1. you should be on stock kernel.
2.after upgrading your mobile you should take backup again. becoz why you want to revert back to older version ?
3.no need to clear cache and data.
4. yes you can flash any kernel and recovery . i had updated it and i am on TWRP.
*************************************************************************************************************************
yes you are right but still there is thread on yu forum for it and they said that you should be on stock kernel by the way you can flash it on your current kernel if you see any error then you can flash stock kernel and flash this update
Click to expand...
Click to collapse
Please flash any custom kernel to see if it works or not :3
oemaritradey said:
Please flash any custom kernel to see if it works or not :3
Click to expand...
Click to collapse
I am on thunderzap kernel
enjoy happy flashing .
best of luck
ashish_zarekar said:
1. you should be on stock kernel.
2.after upgrading your mobile you should take backup again. becoz why you want to revert back to older version ?
3.no need to clear cache and data.
4. yes you can flash any kernel and recovery . i had updated it and i am on TWRP.
*************************************************************************************************************************
yes you are right but still there is thread on yu forum for it and they said that you should be on stock kernel by the way you can flash it on your current kernel if you see any error then you can flash stock kernel and flash this update
Click to expand...
Click to collapse
LOL i tried falshing stock kernel with flashify both time i didnt get wifi signal(MAC UNKNOWN) xD Am not switching over to new update anytime soon....
Flashed this full ROM. Successful !! :highfive:
But I lost Root access and the stock recovery.
I am trying to flash it in fastboot mode, but its stuck at this message:
target reported max download size of 268435456 bytes
sending 'recovery' (8394 KB)...
Without stock recovery, I can't flash the Root.zip file to get root access.
feeroz123 said:
Flashed this full ROM. Successful !! :highfive:
But I lost Root access and the stock recovery.
I am trying to flash it in fastboot mode, but its stuck at this message:
target reported max download size of 268435456 bytes
sending 'recovery' (8394 KB)...
Without stock recovery, I can't flash the Root.zip file to get root access.
Click to expand...
Click to collapse
yes i know when you flash this rom you will lose your root.
and why are you flashing it in fastboot mode ?
this rom is flashable in stock recovery only dont do that.
and what were you doing while you got that error message ?
ashish_zarekar said:
yes i know when you flash this rom you will lose your root.
and why are you flashing it in fastboot mode ?
this rom is flashable in stock recovery only dont do that.
and what were you doing while you got that error message ?
Click to expand...
Click to collapse
I meant, I lost the stock recovery as well. SO I was trying to flash the stock recovery image file in fastboot mode as usual. But it gives me error as I mentioned earlier. My phone is connected to PC while I try to flash the recovery image file. I suspected the drivers got erased, but thats not the case.
Only when I install stock recovery, the Root.zip file can be flashed using it ( to root the phone again). Because flashing the zip files from new Cyanogen Recovery is not at all working. Some R/W or backmap/bitmap kind of issue comes when I try to flash using the updated recovery.
feeroz123 said:
I meant, I lost the stock recovery as well. SO I was trying to flash the stock recovery image file in fastboot mode as usual. But it gives me error as I mentioned earlier. My phone is connected to PC while I try to flash the recovery image file. I suspected the drivers got erased, but thats not the case.
Only when I install stock recovery, the Root.zip file can be flashed using it ( to root the phone again). Because flashing the zip files from new Cyanogen Recovery is not at all working. Some R/W or backmap/bitmap kind of issue comes when I try to flash using the updated recovery.
Click to expand...
Click to collapse
what? you lost your stock recovery ? how is it possible ? it means you dont have any recovery ?
have not face yet.
and how did you flash root.zip file using stock recovey
stock recovery does not have option to flash. it always have update option.
you can flash root.zip file using custom recovery only.
Thankyou for this post... can you please advice to update this ota
I am in stock rom with twrp recovery + sandy kernel
what are the steps to update this ota... can you tell step by step
thank you in advance
m_rajaganesh said:
Thankyou for this post... can you please advice to update this ota
I am in stock rom with twrp recovery + sandy kernel
what are the steps to update this ota... can you tell step by step
thank you in advance
Click to expand...
Click to collapse
DO NOT SPAM.
read carefully i already told the steps in my first POST
download stock kernel and flash it.
download stock recovery and flash it.
now download whole rom from my post and flash it.
ashish_zarekar said:
what? you lost your stock recovery ? how is it possible ? it means you dont have any recovery ?
have not face yet.
and how did you flash root.zip file using stock recovey
stock recovery does not have option to flash. it always have update option.
you can flash root.zip file using custom recovery only.
Click to expand...
Click to collapse
I am sorry, I put it in wrong terms.
The CWM recovery (having basic look with text in blue that can be opted only using hardware buttons and not touch) is not shown for me now. The Cyanogen Recovery it shows me now looks new (with Apply Update option that can be opted by touch as well). THis new recovery fails whenever I try to flash any zip with it. The error being R/W error or something.
With the old recovery (CWM recovery) I could/did flash the Root.zip. After flashing this full ROM (having the patch), the old recovery is lost. It shows only the new recovery. And with it the Root.zip can not be flashed as it fails, as I mentioned earlier.
May be I will get you screenshots of the new Cyanogen recovery to explain what I mean.
Old CWM Recovery:
New Cyanogen Recovery:
Disclaimer!
I, xRaZeR_FuZioNx, or anyone else who is affiliated with this project are not responsible for any kind of damage to your device in any way.
Please use it at your own risk! Whatever you do with your phone is your own choice!
{
"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"
}
Hey guys! Here's TWRP 3 for the Samsung Galaxy Core Prime (G360T/G360T1).
Screenshots:
Installation:
Put your phone into download mode, and connect it to a computer.
Flash TWRP via ODIN.
Boot into TWRP using the key combo (Volume Up, Home, and Power).
Downloads:TWRP 3.0.0-0
Bugs:
MTP may not work correctly.
SlimPickins will not flash. Recommended to flash using TWRP 2, make a backup of the System, then upgrade to TWRP 3.
Special Thanks To:
Y300-0100 - Major contributor, helped fix issues.
Let me just steal this...
You made your own? Checking this out now!!!
Sent from my SM-G360T1 using Tapatalk
bogarty said:
You made your own? Checking this out now!!!
Sent from my SM-G360T1 using Tapatalk
Click to expand...
Click to collapse
Yes, but not without the help of @Y300-0100.
xRaZeR_FuZioNx said:
Disclaimer!
I, xRaZeR_FuZioNx, or anyone else who is affiliated with this project are not responsible for any kind of damage to your device in any way.
Please use it at your own risk! Whatever you do with your phone is your own choice!
Hey guys! Here's TWRP 3 for the Samsung Galaxy Core Prime (G360T/G360T1).
Screenshots:
Installation:
Put your phone into download mode, and connect it to a computer.
Flash TWRP via ODIN.
Boot into TWRP using the key combo (Volume Up, Home, and Power).
Downloads:TWRP 3.0.0-0
Bugs:
MTP may not work correctly.
Special Thanks To:
Y300-0100 - Major contributor, helped fix issues.
Click to expand...
Click to collapse
YASSS!! TWRP 3 is out! Now at least recovery can look nicer and much improved now.
FYI, I was able to successfully make a nandroid backup and restore said backup on TWRP 3.0.0-0. However, with 3.0.0-0 I was unable to clean install Slim Pickins Rom. When that happened I rebooted into download mode, reinstalled TWRP 2.8.7.0, which I was then able to clean install Slim Pickins with
thisisapoorusernamechoice said:
FYI, I was able to successfully make a nandroid backup and restore said backup on TWRP 3.0.0-0. However, with 3.0.0-0 I was unable to clean install Slim Pickins Rom. When that happened I rebooted into download mode, reinstalled TWRP 2.8.7.0, which I was then able to clean install Slim Pickins with
Click to expand...
Click to collapse
Thank you for letting me know. I can confirm this issue appears at the "formatting system" step. I'll look into this issue and see what may be causing it.
thisisapoorusernamechoice said:
FYI, I was able to successfully make a nandroid backup and restore said backup on TWRP 3.0.0-0. However, with 3.0.0-0 I was unable to clean install Slim Pickins Rom. When that happened I rebooted into download mode, reinstalled TWRP 2.8.7.0, which I was then able to clean install Slim Pickins with
Click to expand...
Click to collapse
Twrp 3.0 has options mount system as read only on start up. Was that option ticked?
Y300-0100 said:
Twrp 3.0 has options mount system as read only on start up. Was that option ticked?
Click to expand...
Click to collapse
I don't believe so, if you're referring to the prompt that comes up the first time you boot into TWRP, I told it to go ahead and modify /system/ or whatever. Also I was able to restore a nandroid backup (including the system partition) in TWRP 3.0.0-0 before I came across this issue. Since my memory is imperfect at best, I'll retest it again tonight once I have the free time and access to my phone (it's actually my gf's but she's sold on the whole custom ROM scene since I showed her how much CM improved my S5; now she won't stop asking if I've gotten CM to build successfully yet for this phone lol)
thisisapoorusernamechoice said:
I don't believe so, if you're conflict bing to the prompt that comes up the first time you boot into TWRP, I told it to go ahead and modify /system/ or whatever. Also I was able to restore a nandroid backup (including the system partition) in TWRP 3.0.0-0 before I came across this issue. Since my memory is imperfect at best, I'll retest it again tonight once I have the free time and access to my phone (it's actually my gf's but she's sold on the whole custom ROM scene since I showed her how much CM improved my S5; now she won't stop asking if I've gotten CM to build successfully yet for this phone lol)
Click to expand...
Click to collapse
So as I thought. Wipe system definitely working but there must be some conflict between updare binary and updater script with twrp since you restored system. First recovery wipe system and than restore it.
this conflict is common when rom is made with kitchen.
So wait for cm. It won't be to long
Y300-0100 said:
So wait for cm. It won't be to long
Click to expand...
Click to collapse
God I can't wait. I synced the repos but I can't seem to get it to build, no matter what I tinker with
thisisapoorusernamechoice said:
FYI, I was able to successfully make a nandroid backup and restore said backup on TWRP 3.0.0-0. However, with 3.0.0-0 I was unable to clean install Slim Pickins Rom. When that happened I rebooted into download mode, reinstalled TWRP 2.8.7.0, which I was then able to clean install Slim Pickins with
Click to expand...
Click to collapse
Unfortunately, that was the case for me, too. I was able to wipe but not able to install the Slim Pickins ROM. It came up with an error. So I had to go back to TWRP 2.8.7.0 and successfully install the ROM.
Thanks
I've hung out in the irc almost every day and got to see this be made and released thanks all to who contributed to it now to make cm
I flashed this via an app, and I got a recovery loop. I don't have access to a computer so I can't use odin. Any way to fix this recovery loop?
X_shinobi.apk_X said:
I flashed this via an app, and I got a recovery loop. I don't have access to a computer so I can't use odin. Any way to fix this recovery loop?
Click to expand...
Click to collapse
What app did you use? The only app I know of that flashes Odin files is "Mobile Odin" by Chainfire, but I think it's still not compatible with our device, so the only way to flash TWRP is via Odin and the only way for you to fix boot is to flash either Trapkernel or the stock firmware in Odin. The only other way I can think of is if you maybe had TWRP 2 installed before this and you're still able to boot into it and restore a previous backup.
Sent from my SM-G360T1 using Tapatalk
bogarty said:
What app did you use? The only app I know of that flashes Odin files is "Mobile Odin" by Chainfire, but I think it's still not compatible with our device, so the only way to flash TWRP is via Odin and the only way for you to fix boot is to flash either Trapkernel or the stock firmware in Odin. The only other way I can think of is if you maybe had TWRP 2 installed before this and you're still able to boot into it and restore a previous backup.
Sent from my SM-G360T1 using Tapatalk
Click to expand...
Click to collapse
I just extracted the file, then just used rom installers flash image feature. And I fix it by using twrps terminal command feature and just dd my stock recovery I keep as a backup.
X_shinobi.apk_X said:
I just extracted the file, then just used rom installers flash image feature. And I fix it by using twrps terminal command feature and just dd my stock recovery I keep as a backup.
Click to expand...
Click to collapse
OK. I think I know what the problem was. Yes you can flash the recovery.img in a flash tool app. I just verified that it does work for this recovery too by using an app called "Rashr" and successfully flashing from TWRP 2 to TWRP 3 using the extracted recovery.img for TWRP 3. When it's done though it asks if you want to reboot to recovery, which you must've done. You can not select reboot to recovery from anywhere on this device without causing a recovery loop. I'd say you could try flashing the boot.img from the Trapkernel.zip in your flash tool app too to fix boot, but since you can't use apps right now and have no way to access a backup, then you will need to find a computer to fix your device.
Sent from my SM-G360T1 using Tapatalk
bogarty said:
OK. I think I know what the problem was. Yes you can flash the recovery.img in a flash tool app. I just verified that it does work for this recovery too by using an app called "Rashr" and successfully flashing from TWRP 2 to TWRP 3 using the extracted recovery.img for TWRP 3. When it's done though it asks if you want to reboot to recovery, which you must've done. You can not select reboot to recovery from anywhere on this device without causing a recovery loop. I'd say you could try flashing the boot.img from the Trapkernel.zip in your flash tool app too to fix boot, but since you can't use apps right now and have no way to access a backup, then you will need to find a computer to fix your device.
Sent from my SM-G360T1 using Tapatalk
Click to expand...
Click to collapse
Yeah I figured it out, I planned for such a problem and made backup of the stock recovery so I could use the terminal from advanced options to flash it. Let me know when they solve this issue.
Sent from my SM-G360T1 using XDA-Developers mobile app
X_shinobi.apk_X said:
Yeah I figured it out, I planned for such a problem and made backup of the stock recovery so I could use the terminal from advanced options to flash it. Let me know when they solve this issue.
Sent from my SM-G360T1 using XDA-Developers mobile app
Click to expand...
Click to collapse
Try using flash fire by chainfire if you still need to install twrp and can't use a PC. It's the successor to mobile Odin and is compatible with way more devices including virtually every Samsung device. Flashify might work too. Obviously either app will require root
X_shinobi.apk_X said:
Yeah I figured it out, I planned for such a problem and made backup of the stock recovery so I could use the terminal from advanced options to flash it. Let me know when they solve this issue.
Sent from my SM-G360T1 using XDA-Developers mobile app
Click to expand...
Click to collapse
I think the "reboot to recovery" causing a recovery loop issue might be a system one. It's always been an issue on this device. There are quite a few versions of TWRP now for the SM-G360T1, but all if them do it. I think it even did it with the stock recovery too. Not a big deal though in my mind. Just have to remember to always reboot normal.