[Q] Installing new ROMS in the phones - Android Q&A, Help & Troubleshooting

Installing new ROMS should be as simple as
1.copying installer file say install.zip in the external SD card
2.break boot sequence by the press of some key combinations to invoke installer
3.mount external hard drive
4.bring up a explorer to choose the install file
5.install.
6.reboot.
All backups to be taken before to the external SD
which could be restored after rebooting in the new OS.
Why it is not simple like this?
Google has to do some work on this one ASAP.
xdadevelopers has to do something on this one first.

N Rajeaswar said:
Installing new ROMS should be as simple as
1.copying installer file say install.zip in the external SD card
2.break boot sequence by the press of some key combinations to invoke installer
3.mount external hard drive
4.bring up a explorer to choose the install file
5.install.
6.reboot.
All backups to be taken before to the external SD
which could be restored after rebooting in the new OS.
Why it is not simple like this?
Google has to do some work on this one ASAP.
xdadevelopers has to do something on this one first.
Click to expand...
Click to collapse
Really?
Google isn't responsible for all these things. It just releases source codes and developers develop it for their respected phones.
Common steps for flashing custom ROM are;
1.Unlock Bootloader (if locked)
2.Flash custom recovery
3.Backup stock ROM
4.Wipe system+data
5.Install ROM.zip
6.Install GApps
7.Wipe cache+dalvic cache
8.Reboot
If you followed every step, you'll just need near about 30Mins and Your new ROM will be installed successfully.
For some phones, their manufacturer don't allow them to flash custom ROM.
As flashing custom ROMs is experimental and one can mess up its phone, manufacturer do not provided warranty for such messed up phone. As noobs can do it easily.
So, the main reason is 'manufacturer' who takes care of their consumers for not messing up their phone and do not provide flexibility for flashing custom ROMs
Hope found this helpful
Regards,
hitman-xda

Related

[Q] HElp HElp HElp!!!

Hey plz tell me in detail how do i install custom rom (most stable with excellent performance) in my lg p500!!!
plz answer in detail including how do i wipe sd card and all
THnx in advandee
Have you rooted your phone?
Well I'll assume that you have an P500 with v2.2.2, Stock Rom Untouched.
Firstly you would want to root the phone. http://forum.xda-developers.com/showthread.php?t=1044765
Download Gingerbreak
- Make sure USB debugging is enabled(Can be enabled through settings)
- Make sure you have an SD card (formatted and) inserted
- Place the app onto the root of your SD card
- Open the APK, press the root button
- Wait a few minutes. If there are no problems, the device will reboot (note that the reboot itself can take like 10 minutes due to cache wipe)
Congratulations the phone is rooted.
danialrocker said:
Have you rooted your phone?
Well I'll assume that you have an P500 with v2.2.2, Stock Rom Untouched.
Firstly you would want to root the phone. http://forum.xda-developers.com/showthread.php?t=1044765
Download Gingerbreak
- Make sure USB debugging is enabled(Can be enabled through settings)
- Make sure you have an SD card (formatted and) inserted
- Place the app onto the root of your SD card
- Open the APK, press the root button
- Wait a few minutes. If there are no problems, the device will reboot (note that the reboot itself can take like 10 minutes due to cache wipe)
Congratulations the phone is rooted.
Click to expand...
Click to collapse
ya i have rooted!!!
i have 2.2.1 and recovery of
Build : RA-thunderg-1.2.0-GNM
how do i install cm7 and wipe and other things
thnx in advance
danialrocker said:
Have you rooted your phone?
Well I'll assume that you have an P500 with v2.2.2, Stock Rom Untouched.
Firstly you would want to root the phone. http://forum.xda-developers.com/showthread.php?t=1044765
Download Gingerbreak
- Make sure USB debugging is enabled(Can be enabled through settings)
- Make sure you have an SD card (formatted and) inserted
- Place the app onto the root of your SD card
- Open the APK, press the root button
- Wait a few minutes. If there are no problems, the device will reboot (note that the reboot itself can take like 10 minutes due to cache wipe)
Congratulations the phone is rooted.
Click to expand...
Click to collapse
ya i have rooted!!!
i have 2.2.1 and recovery of
Build : RA-thunderg-1.2.0-GNM
how do i install cm7 and wipe and other things
thnx in advance
After rooting your phone, you must have 1) Recovery Installer
2) Terminal Emulator (Free from market)
3) The Custom Rom
I recommend FranciscoFranco's Rom as it contains excellent tweaks without hassle of flashing many files which may cause your phone to brick.
Recovery Installer, You can get it from: http://dl.dropbox.com/u/11987571/quick/recovery_installer.rar
when you have everything, lets start
1. extract contents of "recovey_installer.rar" to the root(meaning the base) of your SDcard.(it contains 3 files, so you should also see 3 new files on your SD card).
2. open terminal emulator, enter these lines(press enter after each line):
Code:
su
sh /sdcard/rf.sh
just wait and this should reboot you directly to recovery.
3. now in recovery(remember: "vol + and - button" is "up and down" "menu button is ok/select" and "back button" is back)
Congratulations, Your Recovery Installer is installed.
Now, You can get FranciscoFranco's Rom which is called Devoid from
here: http://forum.xda-developers.com/showthread.php?t=1049518
Download franco.devoid and the kernel.
Go to recovery boot
1.Select Wipe and Wipe everything and that includes data+factory settings, cache, system, .android-secure and sd-ext partition (if you had it already)
2. Select ext partition and choose either ext2/3/4 : 512mb,swap:0
3.Toggle usb connection and place devoid.franco and the kernel zip files onto your sd card.
4.Select flash and flash devoid.franco first then flash the kernel.You do not need to toggle signature verify as it should have signatured. If you are a ***** then carry on and toggle signature verify.
5.Reboot.
Enjoy
You can thank me by pressing the thank button
virusshah1997 said:
ya i have rooted!!!
i have 2.2.1 and recovery of
Build : RA-thunderg-1.2.0-GNM
how do i install cm7 and wipe and other things
thnx in advance
Click to expand...
Click to collapse
There's an option where it says "wipe" when you are in your recovery boot you should enter that category and wipe what the developer says.
Also there should be a guide of how to flash cm7 onto your phone in the thread itself
There shouldn't be any problem .
Do you mean you do not know how to enter recovery boot menu?
If so, open your terminal emulator and type
su
reboot recovery
It will reboot your phone to recovery boot.
Then wipe what the developer asks you to wipe,
make the partition on your sd card wether its ext2/3/4
Then flash it.
danialrocker said:
After rooting your phone, you must have 1) Recovery Installer
2) Terminal Emulator (Free from market)
3) The Custom Rom
I recommend FranciscoFranco's Rom as it contains excellent tweaks without hassle of flashing many files which may cause your phone to brick.
Recovery Installer, You can get it from: http://dl.dropbox.com/u/11987571/quick/recovery_installer.rar
when you have everything, lets start
........
Click to expand...
Click to collapse
Sorry i had cut down your post a little bit, as i was quoting it
Thanks from my side
As you made it very easy for us to understand on how to flash with custom roms
danialrocker said:
After rooting your phone, you must have 1) Recovery Installer
2) Terminal Emulator (Free from market)
3) The Custom Rom
I recommend FranciscoFranco's Rom as it contains excellent tweaks without hassle of flashing many files which may cause your phone to brick.
Recovery Installer, You can get it from: http://dl.dropbox.com/u/11987571/quick/recovery_installer.rar
when you have everything, lets start
1. extract contents of "recovey_installer.rar" to the root(meaning the base) of your SDcard.(it contains 3 files, so you should also see 3 new files on your SD card).
2. open terminal emulator, enter these lines(press enter after each line):
Code:
su
sh /sdcard/rf.sh
just wait and this should reboot you directly to recovery.
3. now in recovery(remember: "vol + and - button" is "up and down" "menu button is ok/select" and "back button" is back)
Congratulations, Your Recovery Installer is installed.
Now, You can get FranciscoFranco's Rom which is called Devoid from
here: http://forum.xda-developers.com/showthread.php?t=1049518
Download franco.devoid and the kernel.
Go to recovery boot
1.Select Wipe and Wipe everything and that includes data+factory settings, cache, system, .android-secure and sd-ext partition (if you had it already)
2. Select ext partition and choose either ext2/3/4 : 512mb,swap:0
3.Toggle usb connection and place devoid.franco and the kernel zip files onto your sd card.
4.Select flash and flash devoid.franco first then flash the kernel.You do not need to toggle signature verify as it should have signatured. If you are a ***** then carry on and toggle signature verify.
5.Reboot.
Enjoy
You can thank me by pressing the thank button
Click to expand...
Click to collapse
When ever i type
su
sh /sdcard/rf.sh
It say not found
iamrajeev said:
When ever i type
su
sh /sdcard/rf.sh
It say not found
Click to expand...
Click to collapse
HeY!
Have u copied files on root of ur sd card?
(on sdcard not in any folder)
Extaract it and den copy it
it in root..i coped there & than extracted
iamrajeev said:
it in root..i coped there & than extracted
Click to expand...
Click to collapse
add me in fb.... i will teach u
id de add kar leta
virusshah1997 said:
add me in fb.... i will teach u
Click to expand...
Click to collapse
good virusshah good to see u helping enjoy

CWM Recovery Test for MediaPad

CWM 5.8.0.9 for Huawei MediaPad
WARNING !!! DON'T FORMAT AND DON'T WIPE PARTITIONS USING THESE CWM !
I don't know how much this CWM version improves over the existing one by segler11.
However these build were more aimed at compiling and testing the new kernel sources.
I have tested compiling with both arm-eabi-4.4.0 and arm-eabi-4.4.3 with success on Ubuntu 10.04.
This is experimental, however with the new kernel sources it will just be a matter of time.
I have compiled the kernel included in this CWM recovery image but I didn't recompile the complete image.
I took as base Pyramid CWM 5.8.0.9 and I replaced the files from those found on a stock C232B005 kernel.
As the default build configuration I have used the /proc/config.gz of a C232B005 running kernel.
I have tested this CWM to be able to backup these partitions (I have not tested "restore" yet, just checked the tar archives):
boot.img - 12.582.912 (match 12Mb)
recovery.img - 16.777.216 (match 16Mb)
data.ext4.tar
cache.ext4.tar
system.ext4.tar
custom.ext4.tar
as you can see my hand tweaks to "recovery" require the name of "cust" partition to be "custom" instead but I believe this is a no issue while you backup and restore with the same CWM. Suggestions welcome.
BUGS:
data & time on archives are wrong
mount USB storage does not work
adb not enabled in recovery mode
Formats and Wipes do not work don't use them
The "busybox hwclock" applet doesn't work to set the hardware clock of our device.
The "adb shell" is not active while in CWM recovery, I don't know why and this was my objective so if you have suggestion please help.
As usual flash both "recovery" and "recovery2" partitions using "fastboot" and one of the attached CWM recovery:
Code:
fastboot flash recovery recovery-5.8.0.9-HWMOD-eabi-4.4.3.img
fastboot flash recovery2 recovery-5.8.0.9-HWMOD-eabi-4.4.3.img
fastboot reboot
WARNING !!! DON'T FORMAT AND DON'T WIPE PARTITIONS USING THESE CWM !
.:HWMOD:.
.
Reserved CWM HWMOD
This version seemed to work better for me.Tnx dude!
john9 said:
This version seemed to work better for me.Tnx dude!
Click to expand...
Click to collapse
Thank you for trying it.
Remember to absolutely avoid formatting or wiping partitions.
If you need to format/wipe do it ONLY after reinstalling the original "recovery.img" in both "recovery" and "recovery2" partitions and then reset the device from:
"Settings -> Backup and reset -> Factory reset"
ATTENTION !!! You can safely do a wipe or factory reset only after reinstalling the original recovery image.
Sorry for insisting but I don't want to create problems on users devices and I know those operations will create problems.
.:HWMOD:.
Just a note: I used your 4.4.3 version to try making a nandroid backup last night. Good news and bad news.
This morning I inspected the result using the app Nandroid Browser.
Good: Your CWM does successfully backup /data/data. The other CWM that had been posted here did not do so properly.
Bad: Your CWM also backs up the entire internal SD storage contents inside the folder /data/share. It is customary *not* to include this in a nandroid backup because a) you don't want to inflate the file size unnecessarily, and b) you don't want to overwrite the internal SD on a restore.
Idea: After you fix it, and until you manage to get ADB over USB working, maybe you could add a menu option to make a separate backup archive of internal SD to external SD. This would allow a route to save the internal storage if the device becomes unbootable and requires a data wipe.
cmstlist said:
Just a note: I used your 4.4.3 version to try making a nandroid backup last night. Good news and bad news.
This morning I inspected the result using the app Nandroid Browser.
Good: Your CWM does successfully backup /data/data. The other CWM that had been posted here did not do so properly.
Bad: Your CWM also backs up the entire internal SD storage contents inside the folder /data/share. It is customary *not* to include this in a nandroid backup because a) you don't want to inflate the file size unnecessarily, and b) you don't want to overwrite the internal SD on a restore.
Idea: After you fix it, and until you manage to get ADB over USB working, maybe you could add a menu option to make a separate backup archive of internal SD to external SD. This would allow a route to save the internal storage if the device becomes unbootable and requires a data wipe.
Click to expand...
Click to collapse
Thank you for trying it. I wanted to compile/test a kernel with new sources in a CWM.
Yes, in our device the internal memory "/mnt/sdcard" is also mapped under "/data/share".
Unfortunately I don't have the skills (yet) to build a complete recovery image from scratch,
so what I did was just compiling the kernel part of the recovery image, using the new sources.
Then I simply hex tweaked the "recovery" executable of a 5.8.0.9 Pyramid CWM (HTC Sensation).
So, in conclusion, I have no control over what is copied during the backup process of those partitions.
Though I could control which partition is processed by removing them from "fstab", but there is no gain into it.
We will have to wait somebody with the specific knowledge, or maybe I will have some time to learn once I return from holidays.
.:HWMOD:.
Today i have builded bootable CWM 5.5.0.4 from sources, so now we can adjust all what we need
after_silence said:
Today i have builded bootable CWM 5.5.0.4 from sources, so now we can adjust all what we need
Click to expand...
Click to collapse
well done
HI, can anyone share buckup from working device created by CWM.?
Thanks to all.
Hi,
Is it possible to flash update zips from this CWM recovery (like Beats Audio which is in flashable zip format)?
I don't want to use it for backup-recovery.
...and how about doing wipe cache and wipe dalvik cache?
.dredd. said:
Hi,
Is it possible to flash update zips from this CWM recovery (like Beats Audio which is in flashable zip format)?
I don't want to use it for backup-recovery.
...and how about doing wipe cache and wipe dalvik cache?
Click to expand...
Click to collapse
Haven't tried installing a ".zip" archive from CWM but it should work.
Avoid "wiping" and/or "formatting" partitions, they will be messed up.
hwmod said:
Haven't tried installing a ".zip" archive from CWM but it should work.
Avoid "wiping" and/or "formatting" partitions, they will be messed up.
Click to expand...
Click to collapse
The main reason for use of CWM would be to have the possibility of flashing update zips from CWM... but I am afraid of messing up my device... to understand: no problem if I have to reflash the rom but I would not want to cause mistake which could be repaired only by service.
fastboot is always available if something goes wrong and if you flash cwm you wont be able to install official roms because cwm will overwrite stock recovery
so i was stupid and wiped data and cache - then remembered that it said not to - how do i fix this paperweight? i tried fastbooting all the usual partitions (system, boot, userdata, cache, etc) but still nothing - i can get to fastboot but i cant flash any dload updates. any suggestions are greatly appreciated.
flash stock recovery (2 files) from zipped rom via fastboot and then you should be able to flash stock rom
flashed three different stock recoveries to recovery and recovery2 - still only get the media pad logo twice (flashed androidani intl rom before bricking) cant boot to recovery - think the partition table is screwed. is there a way to create partitions from fastboot, and if so, still would be nice to know the names of the partitions to flash as referenced in tmo stock thread.
byt3b0mb said:
flashed three different stock recoveries to recovery and recovery2 - still only get the media pad logo twice (flashed androidani intl rom before bricking) cant boot to recovery - think the partition table is screwed. is there a way to create partitions from fastboot, and if so, still would be nice to know the names of the partitions to flash as referenced in tmo stock thread.
Click to expand...
Click to collapse
The time needed to reformat and rewrite all the firmware partitions (the first time) will be between 10-15 minutes.
Be patient and give enough time to the device to execute all the needed processes.
When the device finally boot it need to completely regenerate dalvik-cache (the first time).
So try again as instructed above, rewrite "BOTH" partitions named "recovery" and "recovery2", both using the same "recovery.img" file found in the latest stock Huawei firmware.
Now extract the stock Huawei firmware archive on your PC and copy the "dload" folder on an empty formatted SDCard, then insert the SDCard in the MediaPad reboot it and wait until success or failure message.
If you wiped partitions you will have to wait more time (20-30m). It may be that after waiting a while a message about "Encryption not possible" could appear, just say no to encryption and let it reset the device.
It already happened to some of us so hope you are also able to recover your tablet.
thanks i will give it a shot - while it is rewriting partitions, should it be on the huawei logo? or should i see the android / gears turning?
byt3b0mb said:
thanks i will give it a shot - while it is rewriting partitions, should it be on the huawei logo? or should i see the android / gears turning?
Click to expand...
Click to collapse
First time restoration takes time on both moments during the 1st Huawei log and even during animation.
Trying to recover a partition that was wiped takes much longer for the OS to show the error.
When I tried wiping "data" and rebooted the device I recall I went for a long walk and when I returned the device was showing the "Encryption failure / Reset" message (about half an hour later).
So I can only suggest that when you retry you wait at least that amount of time (30 min.) with charger connected, whatever happens leave it alone until it display or ask you do something. Let me know if it works when you have tried.
Download links do not work for me. Can you upload in mediafire please?

Help with the rooting/ROM process

I have some questions about this whole process.
Is one rooted nook the same as another rooted nook (before using a ROM)?
Is this a good rooting tutorial:http://www.youtube.com/watch?v=5n2D5-Q6UFg
I think I would like to follow this tutorial, option C: http://forum.xda-developers.com/showthread.php?t=2081981
The first part of C says:
1. You need a bootable CWM card. Instead of making my own I use Albert's root image from B (above) because this image includes CWM 5.x.x. I use this to flash a higher version CWM internally. I erase the zip files from the card to make room for a flashable CWM 6.x.x
That refers to this link: http://forum.xda-developers.com/showthread.php?p=21275927#post21275927
That tutorial says:
6. Reboot using CWM settings
9. Follow Video for Root Calibration with Apps
7. Sideload all you want (See folder for select games and other stuff)
What does reboot using CWM settings mean? And the video for root calibration with apps is no longer available. And as far as sideloading goes, I wouldn't know what to sideload.
Then back to the original tutorial, it says:
2. Find a flashable CWM 6.x.x I found mine through http://forum.xda-developers.com/show....php?t=1640958
I use the one named "flash_cm9-10_cwm v6...." Download and copy to your sd card.
I'm not sure what a good version is. Do they all do the same thing? Can you install any version?
As you can tell I'm pretty confused on the details of these things.
I've probably got more questions but haven't gotten that far yet.
I wrote that tutorial, but I have since changed my way of doing things.
Anyway, you are not meant to jump between the two tutorials and do the rooting with that first card. It's simply a way to get a bootable CWM 5 card without having to set up partitions or anything like that. You only use that card top boot into CWM 5.
I understand from another topic that Albert's root image may not be available at his download link, but Brian's boot that I mention in the "B" section should work as well and so would a couple of others as well.
I give a link and a name of the CWM 6 file I used back then, and it should still be good.
That "changed my my of doing things" now is I skip the CWM5 step and use the CM10 sd-card that I had been using before installing it internally. I link to that image in section "A". You can use that card as a bootable CWM 6 card. The process if using that would be something like
1. Download and burn the image to a 2GB or larger sd-card. No need to expand partitions since you won't actually use this the way it was intended.
2. When booting, hold the "n" key to get into Cyanoboot menu. Once in the menu there should be a "sd recovery" or similar choice to make.
3. You should now be in CWM 6.x.x and be able to flash your ROM and gApps.
Once your CM10 (I would suggest staying with Succulent (Iamafanof) CM10, dated 1231) CWM 6 and Cyanoboot are both included and you can boot intoi Cyanoboot without the CWM bootable card.
If you feel very lost when trying to follow different tutorials, consider running from sd-card insteda with one of Succulents ready-made images (he has bot CM10 and CM10.1 images). Ther is very little loss in performance in my experience.
SuperGCNBoy said:
I have some questions about this whole process.
...
Click to expand...
Click to collapse
You can find some helpful background info and pointers at http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 and http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1.

[HOW-TO] Updating NT Internal EMMC to CM11 from CM10.x

[Caveat emptor: adopt/follow this guide at your own risk].
[Important Note: this process is applicable for CM11 builds that still maintains two separate partitions for /data and /media – as in CM10.x and stock ROMs (see http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more info). If/when these two partitions get merged in some future CM11 builds (as being contemplated by our NT CM developers – see http://forum.xda-developers.com/showthread.php?t=2560827&page=28) this "CM10 to CM11" update process will not be valid for those future builds with merged /data+media partition].
Below is the process that can be used to update your NT EMMC from CM10.x to CM11.
Download the following files to a location in your user content-media storage space on the NT:
the flashable_CWM_6.0.4.5_chrmhoffmann.zip file from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet which contains the CWM recovery v0.2 provided by Chris Hoffmann (in the first post of the XDA Official CM11 thread http://forum.xda-developers.com/showthread.php?t=2560827).
the zip file of CM11 ROM build of your choice from http://download.cyanogenmod.org/?device=acclaim (see http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items for considerations in choosing nightlies vs. snapshot/stable builds)
the zip file of the Gapps package corresponding to CM11 – e.g., from http://wiki.cyanogenmod.org/w/Google_Apps
Boot into your current emmc recovery
Select install zip and install flashable CWM recovery zip file (obtained in step 1(a)).
Select reboot to boot into the new emmc recovery (flashed in the preceding step).
Select Wipe data & factory reset.
Select install zip and install CM11 zip file.
Select install zip and install Gapps zip file.
Reboot into the new CM11.
Once the NT boots up, set up the wifi connectivity and your google account info. If you had previously enabled Google backup service on your CM10.x your Google Playstore apps will be auto-downloaded (but their settings will not be auto-restored).
If the NT on occasion boots or reboots into a black screen (in lieu of CM boot animation), then you have encountered one of the "random boot crashes" – more info and potential remedies, see http://forum.xda-developers.com/showpost.php?p=48941796&postcount=94 and http://forum.xda-developers.com/showthread.php?p=48301259#post48301259.
A few additional points worth noting:
Flashing CM11 requires CWM version 6.0.4.5 or later, or TWRP version 2.6.3.0 or later. To create a flashable recovery zip file for TWRP, use an archive file manager such as 7-zip to delete and replace the recovery.img inside the flashable recovery zip file (obtained in step 1(a) above) with your choice of TWRP internal recovery image file from http://techerrata.com/browse/twrp2/acclaim (e.g., openrecovery-twrp-2.6.3.1-acclaim.img). Remember to rename the downloaded TWRP .img file to recovery.img before inserting it into the recovery zip file, and also rename the resulting new recovery zip file to some other name like flashable_TWRP_2.x.y.z.zip to avoid future mix-up.
Installing CM11 ROM and Gapps will override your NT's CM10.x boot, recovery, ROM, and Apps, so make sure that you backup all this stuff using recovery backup function, for easy in reverting to CM10.x if desired. See my post at http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more "Info and Tips for Mitigating Risks in Rooting and Flashing Custom-ROM".
I would advise against using any other functions of the recovery without first carefully researching to understand what they really do.
My thanks to all the developers who collective work created the wonderful CM11 ROM for the NT as well as the tools and info I made use of to install it.
A day before i moved from CM 10 to CM 11 , with the help of mikeataol
Anyway Thanks a lot for this guide.
Few questions
* Any good custom kernel ? I tried Bexus but its giving me "android.phone" stopped responding error and wont allow me to do anything , it just keeps on coming even after pressing "OK"
* What happend to multi touch feature ? any ROM , way to enable it ?
* Is it only me or others too feel that the screen lags a lot wrt to touch input ? Its more evident during scrolling or reaading pdf. Also anyway to resolve it ? I desperately need a fix for this.
* I used gapps from here : http://wiki.cyanogenmod.org/w/Google_Apps
CM 11 20140105 , is it fine or i should use PA Gapps only ?
naveen_reloaded said:
...
* What happend to multi touch feature ? any ROM , way to enable it ?
Click to expand...
Click to collapse
Look for the Touch FW Flasher app on the App Drawer screens.
* Is it only me or others too feel that the screen lags a lot wrt to touch input ? Its more evident during scrolling or reaading pdf. Also anyway to resolve it ? I desperately need a fix for this.
Click to expand...
Click to collapse
Did you do wipe /data and /cache in the CM11 installation process?
* I used gapps from here : http://wiki.cyanogenmod.org/w/Google_Apps
CM 11 20140105 , is it fine or i should use PA Gapps only ?
Click to expand...
Click to collapse
The Gapps KK package you installed is fine, the PA package just has a few more apps (such as Maps and YouTube, etc. -- all of which you can get from the Google Playstore) and is more frequently updated (-> less likelihood/need for updates for the apps in the package immediately after first installation).
digixmax said:
Look for the Touch FW Flasher app on the App Drawer screens.
Did you do wipe /data and /cache in the CM11 installation process?
The Gapps KK package you installed is fine, the PA package just has a few more apps (such as Maps and YouTube, etc. -- all of which you can get from the Google Playstore) and is more frequently updated (-> less likelihood/need for updates for the apps in the package immediately after first installation).
Click to expand...
Click to collapse
Thanks , I heard that multitouch has bug which makes tablet slow at <50% battery , is it so ? also does that app work on cm 11?
Yes , i did wipe everything and installed CM 11 , still the screen is stuttering. very annoying. Is there a way to increase the fps ? or see if GPU drivers are working properly ?
The default Gapps are giving error when flashed with Bexus kernel
---------- Post added at 08:12 AM ---------- Previous post was at 07:32 AM ----------
https://play.google.com/store/apps/details?id=com.aatt.fpsm&hl=en
Used this app and saw that fps varies and it varies like from 7 - 50 during reading pdf.
On slow scrolling of pdf , it only shows 11 or so fps , which is why i think shows the stuttering effect
Used the same app on my GS3 to see the difference and it holds its FPS at 60+ and not dropping below 50.
I think if i can make this tablet to render everything at 30+ fps i might not feel this stuttering effect.
https://dl.dropboxusercontent.com/u/15488514/nooktablet.mp4
here is the video i tried to take regarding the screen lag.
its all real time , there is no , afaik any camera lag ( taken with sg3) , its pretty much how it looks . Also i have shown the FPS . You can see when i scroll slowly , the FPS drops to 20 or so making it jerky. if i do it fast , it reaches 50+ but not stable and not very responsive to my touch feedback either.
digixmax said:
[Caveat emptor: adopt/follow this guide at your own risk].
[Important Note: this process is applicable for CM11 builds that still maintains two separate partitions for /data and /media – as in CM10.x and stock ROMs (see http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more info). If/when these two partitions get merged in some future CM11 builds (as being contemplated by our NT CM developers – see http://forum.xda-developers.com/showthread.php?t=2560827&page=28) this "CM10 to CM11" update process will not be valid for those future builds with merged /data+media partition].
Below is the process that can be used to update your NT emmc from CM10.x to CM11.
Download the following files to a location in your user content-media storage space on the NT:
the flashable_CWM_6.0.4.5_chrmhoffmann.zip file from https://www.mediafire.com/#xjwc1a482a6ll which contains the CWM recovery v0.2 provided by Chris Hoffmann (in the first post of the XDA Official CM11 thread http://forum.xda-developers.com/showthread.php?t=2560827).
the zip file of CM11 ROM build of your choice from http://download.cyanogenmod.org/?device=acclaim (see http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items for considerations in choosing nightlies vs. snapshot/stable builds)
the zip file of the Gapps package corresponding to CM11 – e.g., pa_gapps-modular-mini-4.4.2-20140301-signed.zip from http://goo.im/devs/paranoidandroid/roms/gapps-mini
Boot into your current emmc recovery
Select install zip and install flashable CWM recovery zip file.
Reboot into the new emmc recovery (flashed in the preceding step).
Select Wipe data & factory reset.
Select install zip and install CM11 zip file.
Select install zip and install Gapps zip file.
Reboot into the new CM11.
Once the NT boots up, set up the wifi connectivity and your google account info. If you had previously used Google backup service your apps will be auto-downloaded (but their settings will not be auto-restored).
If the NT on occasion boots or reboots into a black screen (in lieu of CM boot animation), then you have encountered one of the "random boot crashes" – more info and potential remedies, see http://forum.xda-developers.com/showpost.php?p=48941796&postcount=94 and http://forum.xda-developers.com/showthread.php?p=48301259#post48301259.
A few additional points worth noting:
Flashing CM11 requires CWM version 6.0.4.5 or later, or TWRP version 2.6.3.0 or later. To create a flashable recovery zip file for TWRP, use an archive file manager such as 7-zip to delete and replace the recovery.img inside the flashable recovery zip file (obtained in step 1(a) above) with your choice of TWRP internal recovery image file from http://techerrata.com/browse/twrp2/acclaim (e.g., openrecovery-twrp-2.6.3.1-acclaim.img). Remember to rename the downloaded TWRP .img file to recovery.img before inserting it into the recovery zip file, and also rename the resulting new recovery zip file to some other name like flashable_TWRP_2.x.y.z.zip to avoid future mix-up.
Installing CM11 ROM and Gapps will override your NT's CM10.x boot, recovery, ROM, and Apps, so make sure that you backup all this stuff using recovery backup function, for easy in reverting to CM10.x if desired. See my post at http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more "Info and Tips for Mitigating Risks in Rooting and Flashing Custom-ROM".
I would advise against using any other functions of the recovery without first carefully researching to understand what they really do.
My thanks to all the developers who collective work created the wonderful CM11 ROM for the NT as well as the tools and info I made use of to install it.
Click to expand...
Click to collapse
The mediafire link does work anymore. Could you reupload the zip file?
Hannibal2050 said:
The mediafire link does work anymore.
Click to expand...
Click to collapse
Link fixed.
digixmax said:
Link fixed.
Click to expand...
Click to collapse
WHen I pressed to Install zip from sd card, the screen only show the symbol of ROM Manager (a hat), and stucked.
What should I do now?
Hannibal2050 said:
WHen I pressed to Install zip from sd card, the screen only show the symbol of ROM Manager (a hat), and stucked.
What should I do now?
Click to expand...
Click to collapse
What version of CWM do you currently have on emmc?
digixmax said:
What version of CWM do you currently have on emmc?
Click to expand...
Click to collapse
Sorry, I handled this issue.
But now if I selected the ZIP file I downloaded from the first post, CWM reported that this file is BAD, and I cannot install.
I am using CWM 5.5.0.4.
I downloaded this file several times, but the issue does not disaapear
Hannibal2050 said:
Sorry, I handled this issue.
But now if I selected the ZIP file I downloaded from the first post, CWM reported that this file is BAD, and I cannot install.
I am using CWM 5.5.0.4.
I downloaded this file several times, but the issue does not disaapear
Click to expand...
Click to collapse
You need a newer version of CWM 6.0.[1-3].x to install CM10.x.
If you have a SD card handy, try the method outlined at http://forum.xda-developers.com/showpost.php?p=51377882&postcount=163.
digixmax said:
You need a newer version of CWM 6.0.[1-3].x to install CM10.x.
If you have a SD card handy, try the method outlined at http://forum.xda-developers.com/showpost.php?p=51377882&postcount=163.
Click to expand...
Click to collapse
Hi,
I did exactly like that. I tried to update CWM to 6.0.45 and the current CWM reported that the zip file of CWM 6.0.45 is BAD
Hannibal2050 said:
Hi,
I did exactly like that. I tried to update CWM to 6.0.45 and the current CWM reported that the zip file of CWM 6.0.45 is BAD
Click to expand...
Click to collapse
For CM10.x you need 6.0.[1-3].x (e.g., 6.0.2.8).
6.0.4.5 and later versions are for CM11 only.
If you follow the SD-based CWM recovery method in the referenced post the CWM recovery you'd be using (to flash the new CWM, ROM, Gapps) is provided by the file recovery.img (downloaded and copied to the SD card) rather than your current 5.5.0.4 on emmc. Make sure that you boot the NT off the SD card as prescribed in step #3 (otherwise you will end up booting emmc cyanoboot and CWM).
FYI, i'm pretty sure TWRP 2.7 (official from GooManager/TWRP site) doesn't work. if you click on the console button (square with lines in it, top) it'll say "This kernel doesn't support configuring SELinux" or something like that. i tried wiping stuff and it would just do a soft reboot. i may go file a proper report to TeamWin but i have CWM on there now and i don't particularly feel like reflashing a broken recovery.
TL;DR don't use TWRP
Hello, I'm new and trying to learn so please don't be too harsh. In following the instructions I somehow overwrote the stock rom and now duel boot CM 10.1 and 11. Any clue as in what I have done wrong?
Thanks in advance.
phrozen_flame said:
Hello, I'm new and trying to learn so please don't be too harsh. In following the instructions I somehow overwrote the stock rom and now duel boot CM 10.1 and 11. Any clue as in what I have done wrong?
Thanks in advance.
Click to expand...
Click to collapse
This thread OP is for updating the NT Internal Emmc to CM11 (from CM10.x), i.e., CM11 would be installed internally. If you were still running stock ROM internally, it wold be replaced by CM11.
good looking out
digixmax said:
[Caveat emptor: adopt/follow this guide at your own risk].
[Important Note: this process is applicable for CM11 builds that still maintains two separate partitions for /data and /media – as in CM10.x and stock ROMs (see http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more info). If/when these two partitions get merged in some future CM11 builds (as being contemplated by our NT CM developers – see http://forum.xda-developers.com/showthread.php?t=2560827&page=28) this "CM10 to CM11" update process will not be valid for those future builds with merged /data+media partition].
Below is the process that can be used to update your NT emmc from CM10.x to CM11.
Download the following files to a location in your user content-media storage space on the NT:
the flashable_CWM_6.0.4.5_chrmhoffmann.zip file from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet which contains the CWM recovery v0.2 provided by Chris Hoffmann (in the first post of the XDA Official CM11 thread http://forum.xda-developers.com/showthread.php?t=2560827).
the zip file of CM11 ROM build of your choice from http://download.cyanogenmod.org/?device=acclaim (see http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items for considerations in choosing nightlies vs. snapshot/stable builds)
the zip file of the Gapps package corresponding to CM11 – e.g., pa_gapps-modular-mini-4.4.2-20140301-signed.zip from http://goo.im/devs/paranoidandroid/roms/gapps-mini
Boot into your current emmc recovery
Select install zip and install flashable CWM recovery zip file.
Reboot into the new emmc recovery (flashed in the preceding step).
Select Wipe data & factory reset.
Select install zip and install CM11 zip file.
Select install zip and install Gapps zip file.
Reboot into the new CM11.
Once the NT boots up, set up the wifi connectivity and your google account info. If you had previously used Google backup service your apps will be auto-downloaded (but their settings will not be auto-restored).
If the NT on occasion boots or reboots into a black screen (in lieu of CM boot animation), then you have encountered one of the "random boot crashes" – more info and potential remedies, see http://forum.xda-developers.com/showpost.php?p=48941796&postcount=94 and http://forum.xda-developers.com/showthread.php?p=48301259#post48301259.
A few additional points worth noting:
Flashing CM11 requires CWM version 6.0.4.5 or later, or TWRP version 2.6.3.0 or later. To create a flashable recovery zip file for TWRP, use an archive file manager such as 7-zip to delete and replace the recovery.img inside the flashable recovery zip file (obtained in step 1(a) above) with your choice of TWRP internal recovery image file from http://techerrata.com/browse/twrp2/acclaim (e.g., openrecovery-twrp-2.6.3.1-acclaim.img). Remember to rename the downloaded TWRP .img file to recovery.img before inserting it into the recovery zip file, and also rename the resulting new recovery zip file to some other name like flashable_TWRP_2.x.y.z.zip to avoid future mix-up.
Installing CM11 ROM and Gapps will override your NT's CM10.x boot, recovery, ROM, and Apps, so make sure that you backup all this stuff using recovery backup function, for easy in reverting to CM10.x if desired. See my post at http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more "Info and Tips for Mitigating Risks in Rooting and Flashing Custom-ROM".
I would advise against using any other functions of the recovery without first carefully researching to understand what they really do.
My thanks to all the developers who collective work created the wonderful CM11 ROM for the NT as well as the tools and info I made use of to install it.
Click to expand...
Click to collapse
Ive been trying to update for a while now and i just couldn't figure it out until i came across your thread.and as right now i am running cm 11 and its all good so far.you made my day.
Help
digixmax said:
[Caveat emptor: adopt/follow this guide at your own risk].
[Important Note: this process is applicable for CM11 builds that still maintains two separate partitions for /data and /media – as in CM10.x and stock ROMs (see http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more info). If/when these two partitions get merged in some future CM11 builds (as being contemplated by our NT CM developers – see http://forum.xda-developers.com/showthread.php?t=2560827&page=28) this "CM10 to CM11" update process will not be valid for those future builds with merged /data+media partition].
Below is the process that can be used to update your NT emmc from CM10.x to CM11.
Download the following files to a location in your user content-media storage space on the NT:
the flashable_CWM_6.0.4.5_chrmhoffmann.zip file from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet which contains the CWM recovery v0.2 provided by Chris Hoffmann (in the first post of the XDA Official CM11 thread http://forum.xda-developers.com/showthread.php?t=2560827).
the zip file of CM11 ROM build of your choice from http://download.cyanogenmod.org/?device=acclaim (see http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items for considerations in choosing nightlies vs. snapshot/stable builds)
the zip file of the Gapps package corresponding to CM11 – e.g., pa_gapps-modular-mini-4.4.2-20140301-signed.zip from http://goo.im/devs/paranoidandroid/roms/gapps-mini
Boot into your current emmc recovery
Select install zip and install flashable CWM recovery zip file.
Reboot into the new emmc recovery (flashed in the preceding step).
Select Wipe data & factory reset.
Select install zip and install CM11 zip file.
Select install zip and install Gapps zip file.
Reboot into the new CM11.
Once the NT boots up, set up the wifi connectivity and your google account info. If you had previously used Google backup service your apps will be auto-downloaded (but their settings will not be auto-restored).
If the NT on occasion boots or reboots into a black screen (in lieu of CM boot animation), then you have encountered one of the "random boot crashes" – more info and potential remedies, see http://forum.xda-developers.com/showpost.php?p=48941796&postcount=94 and http://forum.xda-developers.com/showthread.php?p=48301259#post48301259.
A few additional points worth noting:
Flashing CM11 requires CWM version 6.0.4.5 or later, or TWRP version 2.6.3.0 or later. To create a flashable recovery zip file for TWRP, use an archive file manager such as 7-zip to delete and replace the recovery.img inside the flashable recovery zip file (obtained in step 1(a) above) with your choice of TWRP internal recovery image file from http://techerrata.com/browse/twrp2/acclaim (e.g., openrecovery-twrp-2.6.3.1-acclaim.img). Remember to rename the downloaded TWRP .img file to recovery.img before inserting it into the recovery zip file, and also rename the resulting new recovery zip file to some other name like flashable_TWRP_2.x.y.z.zip to avoid future mix-up.
Installing CM11 ROM and Gapps will override your NT's CM10.x boot, recovery, ROM, and Apps, so make sure that you backup all this stuff using recovery backup function, for easy in reverting to CM10.x if desired. See my post at http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more "Info and Tips for Mitigating Risks in Rooting and Flashing Custom-ROM".
I would advise against using any other functions of the recovery without first carefully researching to understand what they really do.
My thanks to all the developers who collective work created the wonderful CM11 ROM for the NT as well as the tools and info I made use of to install it.
Click to expand...
Click to collapse
So, will pa_gapps-modular-mini-4.4.2-20140608-signed.zip work with any cm11?
11lump said:
So, will pa_gapps-modular-mini-4.4.2-20140608-signed.zip work with any cm11?
Click to expand...
Click to collapse
Yes.
Can't seem to figure this out myself. I have Twrp 2.6.3.0 and it won't let me flash CWM or CM11. Just gives the standard flashing error. Any ideas?
Sent from my XT1058 using XDA Free mobile app

Stock ROM for the SM-T380 Android 9, Bloatware free TWRP backup

Since there aren't any Custom ROM for the SM-T380 I made this TWRP back from my tablet, running on stock Pie I took all the bloatware, Knox out to add some root mods, and latest updates with Magisk root with Safetynet Passing. No other personal app added
This is a compressed TWRP backup, not a flashable ZIP!
Download it from here
1971-12-30--01-34-26_PPR1180610011T380DXU3CSL2.zip
drive.google.com
how to install TWRP
https://forum.xda-developers.com/ga.../twrp-3-2-1-1-tab-sm-t380-10-02-2018-t3747564
DOWNLOAD zip file first then EXTRACT that zip file from above Google Drive's link to your PC using 7zip
Now REBOOT your tablet into TWRP recovery
connect tablet using USB cable to your PC make sure you have Samsung drivers installed, so you can see your tablet on your PC
Now ON your Tablet create a backup within TWRP's backup tab on your SD Card storage (choose storage as a SD card)
Using your PC browse to that folder and open that SD card's TWRP backup folder.
Go to last folder where you should see some files, delete all of them then
Copy EXTRACTED files from (Google Drives) into that TWRP backups folder on your SD card TWRP/BACKUPS/xxxxxxxx/ from your PC to that SD card using your PC.
xxxxxxxx is your device serial number;
Once done copying the file
go to, restore's tab within your TWRP on your tablet
RESTORE everything showing there (all those three partitions) once done
REBOOT to system
IF you can't see those copied files on your tablet's SD card then you have not copied those files into it also you can restart your tablet back into recovery using TWRP after restarting you should see those files into your SD card using restore tab within TWRP.
Thanks
Samsung - for the device, stock firmware & open source
TeamWin - for TWRP recovery @ashyx
@Chainfire - for SuperSU
Magisk
All authors of binaries/libraries, source codes, or tutorials...
Quote:
Please, PM me if I forgot to add proper credits for your work!
Can you tell me how you rooted the SM-T380 I tried rooting it using the 2018 guide but it's not working and I tried patching the Boot.img ( from Sammobile) with magisk but when i open the magisk app it says Installed: N\A Ramdisk: Yes A\B & Sars: no.
Or can you share the stock boot animation from the T830 since I'm not a big fan of the Marvel's avengers/iron man boot animation.
i just installed this and it works great, total life saver. i was about to toss my tablet in the trash
@xfk110, out of sheer desperation I want to try this. I understand why and how it should work, and I'm downloading your backup now. But a couple of questions first if I may:
1. Will Titanium Backup work with this rooted firmware? That's most important and my biggest frustration, after trying every other way described in the T380 threads, with both Oreo and Pie, TWRP or patched boot image. Nothing has worked well enough for me.
. . . My Tab A arrived with XAR 3CTH4 which meant I could downgrade it to the last Oreo update 3BSD1, and I've been back and forth between versions trying to make something work with TiBu. I'm a diehard Titanium user. I have tried 4-5 different root methods and every effort has failed somehow, if only that TiBu would not run. (Most efforts were even worse failures though.)
2. How important is the firmware version (and CSC) on my Tab A? . . . My T380 came with XAR firmware . . . Should I match the 3CSL2 version of your backup exactly, i.e., should I flash 3CSL2 first? Or if I'm on 3CSI5, would that be close enough? (I ask because I'm getting really really tired of changing firmware on this Tab lol, and I already have 3CSI5 downloaded and unpacked.)
3. You mention "all of those files" -- for a TWRP restore I would expect to select ONE FOLDER to restore from, so I'm a little confused about what you mean by "all of those files". Wouldn't it necessary to copy all of those files to one new folder under TWRP/BACKUPS/my-serial-number? Maybe named 2022-01-18, something short and simple.
I do truly truly hope this will work for me. Thanks in advance for however much you can help me understand everything I need to do to get a solid working root.
Just wanted to thank you for providing this guide. It worked first time for me and I'm very happy with the improved speed and space.
Thank you!
zfk110 said:
Since there aren't any Custom ROM for the SM-T380 I made this TWRP back from my tablet, running on stock Pie I took all the bloatware, Knox out to add some root mods, and latest updates with Magisk root with Safetynet Passing. No other personal app added
This is a compressed TWRP backup, not a flashable ZIP!
Download it from here
1971-12-30--01-34-26_PPR1180610011T380DXU3CSL2.zip
drive.google.com
how to install TWRP
https://forum.xda-developers.com/ga.../twrp-3-2-1-1-tab-sm-t380-10-02-2018-t3747564
DOWNLOAD zip file first then EXTRACT that zip file from above Google Drive's link to your PC using 7zip
Now REBOOT your tablet into TWRP recovery
connect tablet using USB cable to your PC make sure you have Samsung drivers installed, so you can see your tablet on your PC
Now ON your Tablet create a backup within TWRP's backup tab on your SD Card storage (choose storage as a SD card)
Using your PC browse to that folder and open that SD card's TWRP backup folder.
Go to last folder where you should see some files, delete all of them then
Copy EXTRACTED files from (Google Drives) into that TWRP backups folder on your SD card TWRP/BACKUPS/xxxxxxxx/ from your PC to that SD card using your PC.
xxxxxxxx is your device serial number;
Once done copying the file
go to, restore's tab within your TWRP on your tablet
RESTORE everything showing there (all those three partitions) once done
REBOOT to system
IF you can't see those copied files on your tablet's SD card then you have not copied those files into it also you can restart your tablet back into recovery using TWRP after restarting you should see those files into your SD card using restore tab within TWRP.
Thanks
Samsung - for the device, stock firmware & open source
TeamWin - for TWRP recovery @ashyx
@Chainfire - for SuperSU
Magisk
All authors of binaries/libraries, source codes, or tutorials...
Quote:
Please, PM me if I forgot to add proper credits for your work!
Click to expand...
Click to collapse
Hello could you please make a video, the truth is that I do not understand anything.
Can this process be done using internal storage?
banistersmind said:
Can this process be done using internal storage?
Click to expand...
Click to collapse
No, unfortunately, this process can only be completed with a micro sd card and another computer with an sd card reader. the sd card must be at least 8gb to work.
Still works great as of 3rd May, 2023! Thanks mate.
@banistersmind @mehmeh.re I just did it without an SD card using internal storage. Works fine.

Categories

Resources