Stock Jelly Bean Factory Images with Root, Custom Recovery, Unlocked Bootloader and No Data Wipe
{
"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"
}
Description: This is a guide that will help you flash a 99% stock factory image for the official Jelly Bean leaks for Verizon Galaxy S III overwriting every partition on the device to stock. The ONLY major change I have made is for your convenience it keeps all your data/apps/settings and internal storage partition in tact. In addition to that I have also provided a small mod in the image that allows the following options below as optional flashes.
Flashing ClockworkMod or TWRP Recovery
Adding SuperSU (Rooting your ROM)
Unlocking your Bootloader
Minor Warning: Please note that if you had any special mods that you had to manually flash before or move on the system partition (like Google Wallet, AOSP 4.2 apps like camera and gallery, etc...) they will be lost as you are overwriting your system partition to factory stock. Please make sure to do the needful with your mods before following this guide (for example resetting the Google Wallet app).
Frequently Asked Questions
I have just received the Jelly Bean OTA and all I'm looking to do is root it. What do I do?
I have created a new thread for such a method. Please refer here: Link
Does this method trip the flash counter?
Yes and no. The only time your flash counter gets tripped is when you flash a custom kernel or recovery. Since the factory image in Step 1 contains the original kernel and recovery partitions, your flash counter should not be tripped. However, after flashing the custom recovery in Step 2, that will indeed increase the counter (no way to escape that since you are flashing a custom recovery).
Solution? Download the TriangleAway app from this thread or from the Play Store after you have completed Step 3 and reset the counter. That easy!
I get an "MD5 hash value is invalid" error when I load the ODIN file. What do I do?
This usually happens whenever your downloaded file is corrupt and has not transferred properly to your computer and your best bet is to try to redownload the file and try once again.
However, there are certain cases where you download the file multiple times and still get the error. In that case there is a small workaround. Firstly, you should see an MD5 that I have posted for each ODIN file in the downloads below. Download this MD5 Checker application to your computer and verify that the MD5 value I have listed for the accompanying download matches the file you have download. If it does not, redownload the file again until you get a match (not safe to flash it in ODIN until you do). However, if the MD5 does match and you still get the same error, all you have to do is rename the file and remove ".md5" from the end of the filename and it will flash. But take note, ONLY do that if the MD5 matches the one I have listed. Otherwise you are running the risk of flashing a corrupt image in ODIN and you can hard brick your device in some cases.
Do I need to flash kernel, radio, or RPM separately?
Not necessary at all. What makes my guide different from your everyday ROM is that these are complete factory images. What that means is that the image file contains every single updated partition for that build that you would need to bring your entire device to the latest build. Normally most ROMs that you flash in recovery only include System and sometimes Kernel partitions.
However, these ODIN images includes every single partition that exists on your device (kernel, radio, RPM, system, aboot, and over 15+ other hidden partitions you normally don't see or have access to). So upon flashing these images you do not have to flash any other partition as these will all automatically be upgraded after completing all three steps in my guide.
I'm coming from a completely stock device. Will this guide work for me too?
Absolutely! This guide was exactly intended with stock devices in mind. Flash with no worries and at the end of all three steps you will be on the latest Jelly Bean build, rooted, and with an unlocked bootloader.
I can't find Blocking Mode that was added to Jelly Bean on every other Galaxy S III. Where is it?
For some unknown reason Verizon decided to leave us out in the cold with Blocking Mode just as they didn't have the All-Share Cast option in ICS. They have done the same thing with the Galaxy Note II and recently a small workaround has been found to activate this feature. Please check this thread for details.
After flashing this image I no longer see the lockscreen notification bubbles for missed calls and text messages that I had in ICS. Where did they go?
For one reason or another Samsung and Verizon intended to remove the lockscreen missed notifications with the Jelly Bean upgrade so what you are seeing is normal. There is a small workaround to get them back but then you will have a small bug if you do that. For the workaround, if you use Root Explorer to look in "/system/csc" you should see a file named "customer.xml". Rename it to "customer.xml.bak" and this is brings back the lockscreen notification bubbles. However, upon doing that you will notice that this message will now never go away. The helper text for that specific notification will never go away because that notification is not supposed to exist in Jelly Bean so it doesn't know how to clear it properly after you've completed the action. The only thing you can do is by the disabling the "Help" app in your Application manager ("All" tab), which will stop showing all helper text. The workaround is reversible so the choice is up to you.
If I have <your build or ROM version here>, can I flash this image to get back to stock?
Absolutely. That is exactly what these factory images are intended for. They will reset your device to a complete build as official from Samsung and Verizon. Go right ahead.
Click to expand...
Click to collapse
Main Downloads
Samsung Official USB Drivers - Link
ODIN v3.07 - Link
SuperSU (Root) - Link
Verizon Galaxy S III Unlocked Bootloader - Links (1, 2)
SuperSU + Unlocked Bootloader - Link
Click to expand...
Click to collapse
VRBMB1 Image Downloads
Stock VRBMB1 Factory Image with No Data Wipe - Link
MD5: b4507fd5bfdf59dbeedf51ff1a6afc7c
VRBLK3 Bootchain with ClockworkMod Touch Recovery 6.0.3.1 - Link
MD5: 99f65a8ce3f93fa46ddad2e02fc0e9f9
VRBLK3 Bootchain with TWRP Recovery 2.5.0.0 - Link
MD5: 7245c10c1daa94b95d633f58547e77c1
Click to expand...
Click to collapse
Step-by-Step Procedure
Step 1 - Flashing the Factory Image
Download and Install USB drivers (Main Download #1)
Download and extract ODIN v3.07 (Main Download #2)
Download the Stock Factory Image with No Data Wipe (Image Download #1)
Boot phone into ODIN mode (See here for how-to)
Flash the flash the factory image using ODIN v3.07 (See here for guide on flashing)
After reboot you should now be on Jelly Bean with all your apps, data, and storage contents in tact
Step 2 - Installing a Custom Recovery
If you would like ClockworkMod Touch Recovery (Image Download #2)
If you would like TWRP Recovery (Image Download #3)
Boot phone into ODIN mode (See here for how-to)
Flash the flash the recovery image using ODIN v3.07 (See here for guide on flashing)
After reboot you should now be able to boot into you recovery of choice using the button combos (See here for how-to)
Along with that the original bootchain for the factory image will be restored as well
Step 3 - Rooting Your ROM and Unlocking Your Bootloader
If you would like Root Only (Main Download #3 to your SD Card)
If you would like Unlocked Bootloader Only (Main Download #4 to your SD Card)
If you would like Both Root and Unlocked Bootloader Main (Download #5 to your SD Card) ***RECOMMENDED***
Boot phone into Recovery mode (See here for how-to)
Flash the download you chose from above using your custom recovery
After reboot your ROM will now be fully rooted and your bootloader fully unlocked to allowing additional flashing of custom kernels/recoveries
Click to expand...
Click to collapse
Credits
Credit goes to "source requested to remain anonymous" for providing the original VRBMB1 leak (via PM)
Credit goes to "source requested to remain anonymous" for providing the original VRBMA2 leak (via PM)
Credit goes to "source requested to remain anonymous" for providing the original VRBLK3 leak (via PM)
Credit goes to "source requested to remain anonymous" for providing the original VRBLK1 leak (via PM)
Credit goes to "source requested to remain anonymous" for providing the original VRBLJ1 leak (via PM)
Credit goes to scrosler for providing the extracted VRBLI5 tarball (Original Link)
Credit goes to jucytec for providing the original VRBLI5 leak (Original Post)
Credit goes to cnlson for providing ftp filehosting (via PM)
Credit goes to scrosler for providing ftp filehosting (via PM)
Credit goes to AdamOutler and African-Canadian Sock Monkey for providing the Verizon Galaxy S III Unlocked Bootloader (Original Post)
Credit goes to invisiblek for providing the VRALEC Bootchain allowing custom recovery flashing (Original Link)
Credit goes to Chainfire for creating SuperSU (Original Post)
Credit goes to Koush for creating ClockworkMod Recovery (Original Link)
Credit goes to Dees_Troy for creating TWRP Recovery (Original Post)
Credit goes to alexcolodner for merging SuperSU/Unlocked Bootloader into one file and providing filehosting (via PM)
First, thanks!
Sent from my SCH-I535 using xda app-developers app
Very nice, will have to give this a try.
I guess going back to the HE ROM would still work if you do a CWM Backup first?
One reason why I was reluctant to try I5 was having to reinstall all my apps and settings.
Does this also include the I5 radio baseband, or does that still have to be flashed separate? Some have reported the HE baseband is working better than the I5 one. Either way, it's easy to flash those zip.
Thank You
Just flashed it, and missing is any Camera or Gallery app, either the Samsung one or the (new) Android 4.2 one.
FAUguy said:
Just flashed it, and missing is any Camera or Gallery app, either the Samsung one or the (new) Android 4.2 one.
Click to expand...
Click to collapse
Please note that mods you have applied to the system partition will have to be reinstalled after flashing the image. Since Camera and Galley are both mods that affect the system partition and you manually flashed onto it, you will lose them normally. Wallet is another example as well so make sure to reset your Wallet app before flashing this image. But you should still see the original Camera and Gallery apps show up that are part of the stock firmware. Please double check that they are not hidden in your launcher or disabled (see the bottom of your Application Manager for disabled apps) from a previous mods perhaps you disabled them before flashing the 4.2 apps. I can personally confirm after multiple testing that Camera and Gallery are both included in this firmware.
I know this is going to be a stupid question... but is the stock (untouched) image not able to be rooted/unlocked? Only reason I ask is because I like having a factory image to flash that does wipe data so it acts as a "start fresh" approach. Thanks for this guide and the joined root/unlock. That's good stuff.
indyssee said:
I know this is going to be a stupid question... but is the stock (untouched) image not able to be rooted/unlocked? Only reason I ask is because I like having a factory image to flash that does wipe data so it acts as a "start fresh" approach. Thanks for this guide and the joined root/unlock. That's good stuff.
Click to expand...
Click to collapse
If you'd like to do a data wipe all you have to do after the image flashes is go into Settings > Back up and reset > Factory data reset. This does the same exact process. I highly don't recommend using the Original Untouched image or it is a much more complicated process to restore root and custom recovery after that. Hence this is why I created this modified image and this guide. The only reason I am linking to that image is for reference purposes only to any developers who want to explore and compare.
Thank you have been waiting for this.
Sent from my SCH-I535 using xda premium
Excellent write up. Thank you very much for your contribution.
open1your1eyes0 said:
Please note that mods you have applied to the system partition will have to be reinstalled after flashing the image. Since Camera and Galley are both mods that affect the system partition and you manually flashed onto it, you will lose them normally. Wallet is another example as well so make sure to reset your Wallet app before flashing this image. But you should still see the original Camera and Gallery apps show up that are part of the stock firmware. Please double check that they are not hidden in your launcher or disabled (see the bottom of your Application Manager for disabled apps) from a previous mods perhaps you disabled them before flashing the 4.2 apps. I can personally confirm after multiple testing that Camera and Gallery are both included in this firmware.
Click to expand...
Click to collapse
When using the HE ROM, I only had the included Samsung Camera and Gallery app, I did not install the separate Android 4.2 app. So when I used ODIN to flash this I5 ROM, I noticed that the Camera and Gallery are not listed in the app drawer. I went into Settings/Applications, and they are still listed, but doesn't have an option to open them. Also went into Titanium Backup, to restore them from a backup of apps I did a few weeks ago. Even after restoring them, they still were not listed and could not be opened. I'm not sure why these two apps were having a problem, but after trying it for a day, I used CWM and restored my HE backup. Now the camera and gallery apps work again, as they should, but now I get a Visual Voicemail error each time the phone turns on. So I had to force stop that app from loading.
FAUguy said:
When using the HE ROM, I only had the included Samsung Camera and Gallery app, I did not install the separate Android 4.2 app. So when I used ODIN to flash this I5 ROM, I noticed that the Camera and Gallery are not listed in the app drawer. I went into Settings/Applications, and they are still listed, but doesn't have an option to open them. Also went into Titanium Backup, to restore them from a backup of apps I did a few weeks ago. Even after restoring them, they still were not listed and could not be opened. I'm not sure why these two apps were having a problem, but after trying it for a day, I used CWM and restored my HE backup. Now the camera and gallery apps work again, as they should, but now I get a Visual Voicemail error each time the phone turns on. So I had to force stop that app from loading.
Click to expand...
Click to collapse
Darn, it seems like your all mixed up over there now. My recommendation ONLY in your case is start fresh using the below process:
Backup your internal SD Card contents to your computer
Save your HE backup in safe place on the computer as well
Flash the Original Untouched Data Wipe image ***REMEMBER THIS WILL WIPE EVERYTHING***
Ensure that everything is working fine upon reboot, setup your phone and make sure all apps are working (Camera, Gallery, etc...)
After that follow my guide from the start to the finish (flashing the No Data Wipe image first!)
Confirm you are rooted, unlocked bootloader, have custom recovery and everything is working
Use "Advanced Restore" in to restore only your "data" partition from your HE backup
If everything is good you can now restore your internal SD Card contents back to your device. Let me know what happens in each step.
I see some of my dropbox links are starting to be suspended due to the heavy traffic. I'd like ask if anyone would like to make some mirrors (especially the No Data Wipe image) please kindly PM me and I will add them to the OP.
open1your1eyes0 said:
Darn, it seems like your all mixed up over there now. My recommendation ONLY in your case is start fresh using the below process:
Backup your internal SD Card contents to your computer
Save your HE backup in safe place on the computer as well
Flash the Original Untouched Data Wipe image ***REMEMBER THIS WILL WIPE EVERYTHING***
Ensure that everything is working fine upon reboot, setup your phone and make sure all apps are working (Camera, Gallery, etc...)
After that follow my guide from the start to the finish (flashing the No Data Wipe image first!)
Confirm you are rooted, unlocked bootloader, have custom recovery and everything is working
Use "Advanced Restore" in to restore only your "data" partition from your HE backup
If everything is good you can now restore your internal SD Card contents back to your device. Let me know what happens in each step.
Click to expand...
Click to collapse
I ended up using CWM and restoring one of the first HE backups that I did a few weeks ago, then tried the I5 (no wipe) install method again.
This time around, it did work, and the Samsung Camera and Gallery apps are there and working, as are all my apps.
The only thing I had to do extra was install the TW JB Google Wallet and 4.2 Keyboard after.
FAUguy said:
I ended up using CWM and restoring one of the first HE backups that I did a few weeks ago, then tried the I5 (no wipe) install method again.
This time around, it did work, and the Samsung Camera and Gallery apps are there and working, as are all my apps.
The only thing I had to do extra was install the TW JB Google Wallet and 4.2 Keyboard after.
Click to expand...
Click to collapse
Excellent! Glad to hear you're up and running. :good: I had a feeling it was something in your latest data partition that was messing with it.
open1your1eyes0 said:
Excellent! Glad to hear you're up and running. :good: I had a feeling it was something in your latest data partition that was messing with it.
Click to expand...
Click to collapse
The only difference between the two HE backups is that there is a few weeks between them, which some app updates were installed through Google Play, the Google Wallet hack, and the Android 4.2 keyboard. So something in there had to cause the Samsung Camera/Gallery app not to work with the I5 (no wipe) ROM. But going to the older HE backup (which is before all those apps were updated) and without Wallet and Keyboard 4.2, then installing I5, the camera/gallery works.
By the way, I remember seeing last week a post (somewhere in here) that was just the I5 Kernel zip.
I did a search, but can't find it.
I want to try the KT747 Kernel, but would like the I5 Kernel to have as a flash backup.
Found the link, but looks like your DropBox is getting slammed
http://forum.xda-developers.com/showthread.php?p=33625822&highlight=kernel#post33625822
FAUguy said:
The only difference between the two HE backups is that there is a few weeks between them, which some app updates were installed through Google Play, the Google Wallet hack, and the Android 4.2 keyboard. So something in there had to cause the Samsung Camera/Gallery app not to work with the I5 (no wipe) ROM. But going to the older HE backup (which is before all those apps were updated) and without Wallet and Keyboard 4.2, then installing I5, the camera/gallery works.
By the way, I remember seeing last week a post (somewhere in here) that was just the I5 Kernel zip.
I did a search, but can't find it.
I want to try the KT747 Kernel, but would like the I5 Kernel to have as a flash backup.
Found the link, but looks like your DropBox is getting slammed
http://forum.xda-developers.com/showthread.php?p=33625822&highlight=kernel#post33625822
Click to expand...
Click to collapse
Attached it for you. Extract the tarball from the zip and flash in ODIN.
open1your1eyes0 said:
Attached it for you. Extract the tarball from the zip and flash in ODIN.
Click to expand...
Click to collapse
Thanks.
I've also been reading about an RPM file in some other threads, but Inc's link is dead. Is that something that should be installed?
FAUguy said:
Thanks.
I've also been reading about an RPM file in some other threads, but Inc's link is dead. Is that something that should be installed?
Click to expand...
Click to collapse
It's included in the image since it's the complete factory package.
EDIT: However also attaching the tarball zip in case you want to mess around with it. Flash in ODIN as well.
By the way, I haven't seen anyone mention it yet but this image finally unlocks the promised "Global Roaming" capabilities that Verizon promised via OTA. You can now use AT&T/T-Mobile/Other GSM carrier microSIM cards and run on their network. AKA: phone is now technically unlocked.
Related
This thread is dedicated to hacking and development of the Sharp SH7218u. This is an Android phone with a somewhat unique clamshell form-factor.
Before proceeding, please note that all of the usual warnings apply. The software and techniques described here have the potential to break your device and make it unusable. By using the software and following these techniques you run the risk of bricking your phone. I take no responsibility if this happens - proceed at your own risk.
First, some credits for the work of others:
Z4root:
Developed by xda member RyanZA.
http://forum.xda-developers.com/showthread.php?t=833953
SH7218u Clockworkmod Recovery:
Clockworkmod original developer is Koushik Dutta:
www.clockworkmod.com
Dialer2:
Original developer of now open source dialer is dnaq Productions:
http://dnaq.tumblr.com/
Initial hacking and development work:
Gigi Tse is credited for early and ongoing work for the SH7218u:
http://gigitse.com/
http://www.msharp.cn/forum/t390991/page1/
Now on the instructions....
-------------------
Rooting Your Phone, Installing Clockworkmod Recovery, and Installing Google Apps
Gather the Required Files:
1. Go to the z4root xda thread, login in and download z4root.1.3.0.apk:
http://forum.xda-developers.com/showthread.php?t=833953
2. Download SH7218u_recovery.apk:
(attached below)
3. Download the Clockworkmod recovery flashable Google Apps file from the following site:
http://goo-inside.me/gapps
In the table, you want to select the HDPI, CyanogenMod 6 version. The file that you download should be
called 'gapps-hdpi-20101114-signed.zip'
4. Place these three files on your micro-SD card and insert the card into your phone.
Root Your Phone
1. Boot up your phone and skip the system setup wizard. Go to the app drawer and run 'Settings'.
2. Select 'Applications', and enable 'Unknown sources'.
3. Select 'Development', and enable 'USB debugging'.
4. Exit back out to your home screen launcher, then go to the app drawer and run 'ES File Explorer'.
5. The file explorer should show you the contents of your sd card. Tap on the file 'z4root.1.3.0.apk'.
6. Confirm installation of z4root, and when this is complete select 'Open' to run the app.
7. From within z4root, press the 'Permanent Root' button.
8. Wait until this process is complete, and the phone will reboot by itself. It can take 30 seconds or so for this to happen, so be patient. You are now rooted.
Flash Clockworkmod Recovery Image
You must be rooted for this to work. Do this after you have successfully completed the rooting process above. Also please note that this is not the CWM recovery image developed by Gigi Tse. Her image contains CWM version 3.0.2.4. This is my recovery image and contains CWM version 5.0.2.8.
1. Open the app drawer and run 'ES File Explorer'.
2. Tap on the file 'SH7218u_recovery.apk'.
3. Confirm installation and run the application by selecting 'Open' once installation is complete.
4. On startup, the application will request Superuser privleges - press 'Accept' to allow this.
5. Press the 'Flash Clockworkmod Recovery' button.
6. Wait a few seconds until you see the confirmation message 'Recovery Flash Complete'.
7. Exit out of the application. You now have Clockworkmod as your recovery. You can uninstall the SH7218u_recovery app if you wish as you have no further use of it.
Note for users of Link2SD: This version of Clockworkmod recovery will perform backup and restore operations on the secondary SD card partition used by Link2SD. However, that partition must be formatted in the ext3 filesystem for this to work. Formatting the partition in any other filesystem (e.g. ext2, fat32, ext4, etc.), will result in failure to mount and backup the partition. An SD card can be prepared for use with Link2SD from within this version of Clockworkmod recovery by using the 'Partition SD Card' feature within the 'Advanced' menu.
Install Google Apps
1. Boot into Clockworkmod Recovery. This is done by powering down your phone, then turning it back on by pressing and holding down the number 3 and 6 buttons together, then pressing and releasing the power button. Continue to hold the number 3 and 6 buttons until you see the Clockworkmod screen.
2. Select 'install zip from sdcard' from the menu.
3. Select 'choose zip from sdcard' from the next menu.
4. The next menu will be the contents of your sdcard. Select the Google Apps file - 'gapps-hdpi-20101114-signed.zip'.
5. Confirm the installation and wait until it is complete.
6. Press the back button once to get back to the main screen and select 'reboot system now'. You now have Google Apps installed.
When you reboot the device, you will be taken through the Google account setup. Please note that in order for contacts applications to work with Google synchronization, you will need to install a modified contact editor. The stock firmware on this phone is not intended to sync with the Google servers as it was intended for Chinese users. The modified contact editor fixes this issue. It is free and available from the Market. Look for 'Contact Editor Free' by a developer named 'dmfs'.
Deleted
Deleted
Thank you! Very good job!
No ideas how to get the phone to answer a call when you open?
TabletGuru said:
Thank you! Very good job!
No ideas how to get the phone to answer a call when you open?
Click to expand...
Click to collapse
Hey someone read my thread!!
Sorry, no posts on this thread yet and it has been up for a while. I think most people who have this phone stick to Howard forums or other such sites that cater to the phone type and its region of origin.
As for your question, no...but I have tried. That would require a modification of the phone app or a change to the OS itself as the phone app is the active app when the phone is ringing and the device is opened. If I had the source code for the stock phone app, this would be a fairly easy thing to do. Unfortunately, I have been unable to find the source for the stock device firmware anywhere. I tried compiling a generic Froyo phone app from the Google source, but of course this did not work. This is a somewhat special app that needs to interface with several parts of the device's hardware, so a generic version just doesn't work. Unless Sharp releases the full source code for the stock firmware, I don't think this is going to be possible....at least not from someone with my somewhat limited development abilities.
Sent from my MB855 using xda premium
Google Play
Hey xdajunkman, amazing work you are doing here.
Have you considered adding Google Play to the mix? I was able to get the latest version working just fine on my SH7218u.
How hard would it be to hack the light notifications area of the phone, to make some of the notifications last for 1-2 seconds longer?
I should also add that my phone is giving some really flaky GPS information. It is putting me somewhere in the ocean near China unless I use wifi only. Do you have any experience with this?
EDIT: I don't know why, but the dialer is not working for me with regard to the long-press of the delete key and silent (#) key. No idea why...
EDIT2: It is because I had another keyboard installed; which must do something funky... switching back to a default keyboard and then trying seemed to work!
Thanks for your guide! Do you have got new version Rom? 2.3 or 2.3.5?
johnny8384 said:
Thanks for your guide! Do you have got new version Rom? 2.3 or 2.3.5?
Click to expand...
Click to collapse
Not likely to come. This would mean building something like CM7 for a new device from scratch. This kind of task takes dozens of man-hours for an expert developer, and that assumes that they have access to the original source for the release build. We do not have the original source, and there is no such developer working on this device. We will be stuck with Froyo.
Thank you so much for taking the time to write a guide xdajunkman!
I received my SH7218u today and did everything. The instructions were clear and the whole process took no more than 30 minutes.
Surprisingly, my SH7218u accepts 64 microsd card (after you format it).
Is it ok to have 2 partitions?
One is a ext2, and the other I just created using clockwork mod ext3...
I'm wanting to use that custom rom..
EDIT: clockwork mod Repartitioned my ext2 to ext3 now ಠ_ಠ
and all my apps are "installed"
Going to make a backup rom now.. and then Install xdajunkman's custom rom >__<
EDIT: Ok succesfully installed the Custom rom It looks great I might say awesome work xdajunkman
Ok the question is now.. how to I get back all my previous apps and stuff?
I followed the guide and made a backup already
My 7218u stuck at Sharp logo when boot because i've uninstalled a system apps ( don't remember exactly) what i've to do now? plz help me
P/S: My english sucks, sorry for that
delpan said:
My 7218u stuck at Sharp logo when boot because i've uninstalled a system apps ( don't remember exactly) what i've to do now? plz help me
P/S: My english sucks, sorry for that
Click to expand...
Click to collapse
Boot into clockwork mod by pressing 3and 6 and the power on button, (assuming you have that installed)
Reinstall the rom.. http://forum.xda-developers.com/showthread.php?p=22106340#post22106340
sirjoe1 said:
EDIT: Ok succesfully installed the Custom rom It looks great I might say awesome work xdajunkman
Ok the question is now.. how to I get back all my previous apps and stuff?
I followed the guide and made a backup already
Click to expand...
Click to collapse
It is usually just easier if you wait until you have the new ROM installed before you try and install your apps. There is no reliable way from within CWM to restore your installed apps.
However, because the new ROM is just a modified version of the stock ROM, it should be possible to flash the new ROM without wiping the existing user data and keeping your installed apps. Restore your backup that has all of your apps installed. Then, flash the modified ROM but skip the step in the instructions that tells you to wipe existing user data. Instead of wiping the user data, do the following:
1. In the 'mounts and storage' menu of CWM recovery, select to format both '/system' and '/cache'
2. In the 'advanced' menu of CWM, select 'Wipe Dalvik cache'
Now proceed with installing the ROM as per the instructions. This should result in the modified ROM being installed, but all of your installed apps should be protected.
If this does not work, then you will just have to re-installed the modified ROM according to the instructions (including wiping the existing user data), then re-install all of your apps. For future reference, a great app called Titanium Backup will allow you to backup your apps and restore them after changing the ROM.
sirjoe1 said:
-->My 7218u stuck at Sharp logo when boot because i've uninstalled a system apps
-->( don't remember exactly) what i've to do now? plz help me
Boot into clockwork mod by pressing 3and 6 and the power on button, (assuming you have that installed)
Reinstall the rom.. http://forum.xda-developers.com/showthread.php?p=22106340#post22106340
Click to expand...
Click to collapse
Agree with sirjoe1. Hopefully you flashed CWM as your recovery before you did this. However, if not then booting into recovery mode as described above should trigger a factory reset from the stock recovery partition. I have not attempted this myself with the stock recovery, but usually what this will do is simply return your device to it's stock state. You can then start over using the instructions in the OP....but without deleting critical system apps this time.
Hello again, I've a question, has anyone successfully Overclocked the cpu frequency on this phone using setcpu or similar apps?
Overclocking not possible without either a custom kernel or a kernel module of some sort. As the source for the stock kernel was never released, such a thing would be a HUGE undertaking. Very unlikely to ever happen.
xdajunkman said:
Overclocking not possible without either a custom kernel or a kernel module of some sort. As the source for the stock kernel was never released, such a thing would be a HUGE undertaking. Very unlikely to ever happen.
Click to expand...
Click to collapse
Oh darn, that's such a downer..
These sh7218u threads are so dead nowadays :/
I might have messed up my phone -_- (again)
I went into the /data/sdext2/dalvik-cache and deleted everything and now a few apps have gone missing, and some won't work, they just give me a force close error >___<
I also lost my go launcher ex settings..
and to make things worse.... my internal memory went to 0% free... deleted a few things to clear up 8mb..
Any Ideas how to fix this ? @[email protected]
[Can you guys play 480p videos?
I can't.. 360p runs fine though..]
I am hoping to get this device this week.
Thanks for your tutorial, and I will let you know if it runs out just fine
Post development questions/logcats etc here. Post "my data doesn't work" (after reading the OP) in the Q&A thread. The mods don't like the developers thread being filled with these user questions, and it's contrary to the goal of this board.
Read this post from our very helpful moderator if you still have any questions. I'll keep both OPs updated. I try to install every nightly and read all of the 10.1 threads. If anything is missing please PM me.
Q&A thread: http://forum.xda-developers.com/showthread.php?t=2071252
10.1.3 has been released.
As for all recent releases, please make sure you are on the MF1 modem
{
"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"
}
Cyanogen Mod 10.1.0 Release is now available:
http://get.cm/?device=d2vzw
Huge thanks to the CM devs! Pop on over to http://www.cyanogenmod.org/ and make a donation (mouse over "Community" at the top right then select "Donate to us") if you'd like to help support the CM project!
Anyone looking for mastamoon's build with his tweaks, reverts, and cherrypicks - it was moved to Android Development. Here is the link! http://forum.xda-developers.com/showthread.php?t=2094251
Rooting, flashing, installing roms, following any instructions below, will void your phone's warranty and there is a chance (however small) that you'll screw up and permanently break your phone. Anything you do to your phone in violation of the warranty, insurance, or anything else is at your own risk!
CyanogenMod June 24th, 2013
http://www.cyanogenmod.org/blog/cyanogenmod-10-1-0-release
CyanogenMod 10.1.0 Release
Tonight we are ending the Release Candidate phase and pushing CM 10.1.0 to general release.
The files will be landing on our servers as they complete the build process. The list of devices will be in line with the devices that have received release candidates to-date. At this time, we do not plan on incorporating devices that did not receive a RC into this release. Also absent from this release are Tegra 2 powered devices and many of the Exynos based Samsung devices. We will provide a status report for these devices later this week.
Next on deck
With the 10.1.0 code finalized, we will return to our M-release cycle and work towards adding additional functionality and features; including the new Privacy Guard feature, which was merged into the nightlies today.
There are many new and exciting things planned for the remainder of the year, just wait and see what we will do next!
-The CyanogenMod Team
Click to expand...
Click to collapse
-+-+-+-+-+-+-+-+ OFFICIAL DOWNLOAD LINK -+-+-+-+-+-+-+-+
http://get.cm/?device=d2vzw
-+-+-+-+-+-+-+-+ NIGHTLY CHANGE LOG -+-+-+-+-+-+-+-+
App from invisiblek: https://play.google.com/store/apps/details?id=com.invisiblek.cm.nightlies
Or: http://10.1.cmxlog.com/?device=d2vzw
-+-+-+-+-+-+-+-+ GUIDE ON HOW TO ROOT AND FLASH -+-+-+-+-+-+-+-+
http://forum.xda-developers.com/showthread.php?t=2046439
-+-+-+-+-+-+-+-+ HOW TO BACKUP AND RESTORE YOUR IMEI -+-+-+-+-+-+-+-+
http://forum.xda-developers.com/showthread.php?t=1852255&highlight=nvbackup
-+-+-+-+-+-+-+-+ OFFICIAL GOOGLE+ -+-+-+-+-+-+-+-+
https://plus.google.com/+CyanogenMod/posts
-+-+-+-+-+-+-+-+ OFFICIAL GOOGLE+ COMMUNITY -+-+-+-+-+-+-+-+
https://plus.google.com/communities/107373456059326217974
-+-+-+-+-+-+-+-+ KNOWN / REPORTED ISSUES -+-+-+-+-+-+-+-+
On the 10.1.3 RC: (updated 7/18)
1: Only use the MF1 AIO file available here.
2: If you cycle bluetooth off and on it may get stuck. You need to reboot to resolve the issue.
3: Verizon FIOS app crashes
4: BT headsets don't work with the Skype app
5: If you set up a phone number to include pauses (like your voicemail PIN) the keypad wont register any other touches during that call.
Many other problems are fixed by simply re-flashing the same rom file over itself.
Please PM repeatable issues from the release to me. Post a logcat in the developer thread or a JIRA ticket if you expect it to get fixed.
-+-+-+-+-+-+-+-+ SPECIAL NOTES -+-+-+-+-+-+-+-+
1. To enable Developer Options: Menu > Settings > About Phone. Tap build number 7 times to unlock Developer Options
2. Photosphere: This feature is not offered on non-nexus devices
3. There are a lot of questions about how CM10.1 moves your files to sdcard/0/ folder. This is to support multi-users. If you flash back and forth between a non-4.2 ROM and CM10.1 (which is 4.2) you'll end up with sdcard/0/0/..etc since the upgrade to 10.1 moves your folders into a new /0/. You can safely move your files out of /0/ back to your sdcard if you're on CM10, or back to the first /0 folder if you're on CM10.1.
4. Don't update from CM10 to CM10.1 using the built-in cmupdater. Update in recovery for the first flash from CM10 to 10.1. Once on 10.1 you can use cmupdater.
-+-+-+-+-+-+-+-+ INSTALLATION NOTES -+-+-+-+-+-+-+-+
CM can be flashed using CWM or TWRP. Only use the latest TWRP or CWM!
When you install CM10.1 your data will be moved to a new folder /0/ (this is to support multi-users).
Make sure you have the latest CWM or TWRP installed so that your recovery isn't confused by the new location of your backups. Official TWRP d2vzw or Latest CWM (scroll down to Samsung Galaxy S3 (Verizon))
GAPPS is not included in any CM download. You must flash a gapps zip if coming from another rom or when starting with a clean install. You do not need to flash gapps when 'dirty flashing' over a previous CM install. Download gapps here.
According to Cyanogen it is possible to flash CM10.1 over top of an existing CM10 installation. It is generally recommended to do a clean install if you run into any issues.
Always make a backup before you try a dirty flash or upgrade to CM10.1.
-+-+-+-+-+-+-+-+ HOW TO INSTALL OVER CM10 -+-+-+-+-+-+-+-+
Consider backing up your IMEI if you haven't already (link)
If you use a lockscreen pattern disable it
Flash the latest CWM or Official TWRP d2vzw
Download a CM10.1 rom (nightly or unofficial) to your sd card
Download the latest gapps from goo to your sd card
Reboot into recovery
Make a backup
Wipe cache and dalvik (if you want)
Install CM10.1 zip
Install gapps
Reboot
After your phone boots go into Menu > Settings > Apps. Under "All" find "Clock", open it, and click "Clear Data"
-+-+-+-+-+-+-+-+ HOW TO INSTALL FROM ANY ROM OTHER THAN CM -+-+-+-+-+-+-+-+
Consider backing up your IMEI if you haven't already (link)
Flash the latest CWM or Official TWRP d2vzw
Download a CM10.1 rom (nightly or unofficial) to your sd card
Download the latest gapps from goo to your sd card
Use an app like Titanium Backup or Mybackup Pro to backup your apps (if you want)
Use an app like SMS Backup+ to backup your text messages and call log (if you want)
Reboot into recovery
Make a backup
Wipe cache and dalvik (if you want)
Wipe Data/Factory Reset/System
Install CM10.1 zip
Install gapps
Reboot
Reinstall Titanium Backup/Mybackup Pro/SMS Backup+ and restore the stuff you have to have, but its better to reinstall things from the market if possible (keep in mind your backups will be located in sdcard/0/) (if you want)
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
I am not a developer, I have no direct association with the CM project, I am just a community member. I will do my best to maintain this thread. Please PM me with any OP suggestions!
I Fixing Data
If you flashed a CM10.1 nightly and are stuck at roaming/activating or don't have data, try any of the following (in order of simplicity):
(1) Go into Mobile Settings - Mobile Networks. Change CDMA mode to RUIM, go into airplane mode, come out, it should login to 4g in a minute. You can wait for activating to time out then skip or not install gapps until after setting the correct mobile network setting.
Click to expand...
Click to collapse
(2) Power down. Take out the sim card and reboot. In mobile network settings set roaming to auto and the subscription to RUIM/SIM, turn off the phone, pop the sim card back in, boot up.
Click to expand...
Click to collapse
If none of those work this will work for sure:
Deevious88 said:
Hallelujah! My phone has voice AND data back! (thanks to the posters above)
How to get voice AND data back:
1.) Odin the root66.tar file from http://forum.xda-developers.com/showthread.php?t=1762204 (the torrent version downloads MUCH faster)
2.) Open the dialer and enter *2767*3855#
3.) DONE! Voice and data should be fixed (it fixed it for me at least, and I had tried EVERYTHING else)
From there just Odin back to Jellybean following http://forum.xda-developers.com/showthread.php?t=1974114 and you're golden...
Click to expand...
Click to collapse
That's how to get back to working condition without fail... Might want to post similar instructions in the OP as dirty flashing did nothing for quite a few of us.
Click to expand...
Click to collapse
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Fixing GPS
invisiblek said:
GPS - it HAS been working for 98% of builds, however if you cannot get GPS to connect, possibly due to dirty flashing, the following has worked every build for me: Settings - Apps - downloaded - GPS Status - clear cache, clear data, force stop. Then open gps status back up, let it sit with gps on for a moment and see if it starts searching for signal again....if this still doesn't work (sometimes) - settings - apps - all - google services framework - clear data. This has worked 100% of the time but I try to avoid it because if you do this, you need to go open back up the play store and see if it still connects. If not, recovery - clear cache, clear dalvik usually takes care of that.
Clean install of builds has given me 100% functional gps every time.
Click to expand...
Click to collapse
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Unofficial CM10.1
(I know several people have posted these, I looked quickly and only found mastamoon's which is also what I am running, I'll happily post more here if I find them).
mastamoon http://forum.xda-developers.com/showthread.php?t=2094251
Click to expand...
Click to collapse
invisiblek https://twitter.com/invisiblek_cm
Click to expand...
Click to collapse
aerovan http://rootzwiki.com/topic/37216-uno...zw-2012-12-18/
Click to expand...
Click to collapse
Unless somebody says otherwise, the official 10.1 nightlies wont have data until 2 commits are merged.
Add SamsungCDMAQualcommSIMRILL
http://review.cyanogenmod.org/#/c/28246/
Enable SamsungCDMAQualcommSIMRILL
http://review.cyanogenmod.org/#/c/28247/
Continue to use the unofficial builds that can be found on other forums if you want your CM10.1 fix.
Thanks for this thread. About time.
Sweet
Via my Google Galaxy S3 running sweet sweet Jelly Bean
Noticed these don't have data yet. Later in the week I may merge those commits and upload a kang
Via my Google Galaxy S3 running sweet sweet Jelly Bean
Strange they would leave out the commits for data, but I will flash as soon as there is a build with them
after flashing 10.1, how did you guys find your previous backup?
I can't seem to find it because now 10.1 is trying to use my external sd to save everything, and i cannot locate my previous back up anywhere.
kimsj756 said:
after flashing 10.1, how did you guys find your previous backup?
I can't seem to find it because now 10.1 is trying to use my external sd to save everything, and i cannot locate my previous back up anywhere.
Click to expand...
Click to collapse
For some reason it nested your old internal SD card. Check inside a folder labeled as "0" then CMUpdater if that is what you downloaded it through.
On another note. Is anyone planning on making a build with the data commits yet today? Or are they slated to be included in the next nightly? The disclusion of the data severely through me off this morning.
This might sound stupid however, would it be possible to get a list of additional features that are added with 10.1 the only thing i know that is different is the quick settings menu. other than that, i am not certain what is new with this version.
littleneutrino said:
This might sound stupid however, would it be possible to get a list of additional features that are added with 10.1 the only thing i know that is different is the quick settings menu. other than that, i am not certain what is new with this version.
Click to expand...
Click to collapse
Here is the clock fix.
The single application known not to work is the Clock: Our changes to 4.1's clock to add the Stopwatch and Timer in CM10 aren't compatible with Google's own implementation of those features in 4.2 (which we're using in cm10.1); If your clock starts crashing after upgrading to 10.1, simply go into the Settings -> Apps menu, choose Clock from the All tab, and hit "Clear data".
littleneutrino said:
This might sound stupid however, would it be possible to get a list of additional features that are added with 10.1 the only thing i know that is different is the quick settings menu. other than that, i am not certain what is new with this version.
Click to expand...
Click to collapse
The thing I'm interested in from 4.2 (I'm assuming it will make it over to cm10.1) is always on VPN
Sent from my SCH-I535 using Tapatalk 2
A few important notes from cyanogen:
# Do not use the CyanogenMod Updater to go from 10.0 to 10.1. While you will have a functional rom, due to the 1st bullet point, you will be left without your proprietary applications and their data. We highly suggest performing the initial install manually via recovery (flashing CM and your addons). Once you are on 10.1, you can use the CM Updater as per normal.
# Finally, we always advise that you create a backup before any update. Do note, however, that due to Android 4.2 changes to support multi-user mode, your backups will automatically be transferred to /sdcard/0/[backup folder]. Remember this when attempting to restore 10.0.
On the nexus 7 boards I heard TWRP has been updated to see this. Not sure if that is true or not, not sure if that holds true for CWM, or for any recovery on the d2vzw.
However you can use a file explorer app to move them back to the root of the sd card.
Restola said:
A few important notes from cyanogen:
# Do not use the CyanogenMod Updater to go from 10.0 to 10.1. While you will have a functional rom, due to the 1st bullet point, you will be left without your proprietary applications and their data. We highly suggest performing the initial install manually via recovery (flashing CM and your addons). Once you are on 10.1, you can use the CM Updater as per normal.
# Finally, we always advise that you create a backup before any update. Do note, however, that due to Android 4.2 changes to support multi-user mode, your backups will automatically be transferred to /sdcard/0/[backup folder]. Remember this when attempting to restore 10.0.
On the nexus 7 boards I heard TWRP has been updated to see this. Not sure if that is true or not, not sure if that holds true for CWM, or for any recovery on the d2vzw.
However you can use a file explorer app to move them back to the root of the sd card.
Click to expand...
Click to collapse
TWRP has been updated to 2.3.2 (may show up as 2.3.2.3 on your phone) and doesn't have the problem of borking your folders. I've downloaded it (don't remember where, just google it) and it works fine.
also, i'm on 12.18, and do have data, have sent back and forth MMS, downloaded and everything seems find, EXCEPT:
camera works, first time it froze and said couldn't find camera, but rebooted, wiped cache and dalvik and fixed permissions and seems to "work" however, picture quality seems borked a little.
other than that all seems to be working fine.
Clockwork was updated yesterday.
Restola said:
A few important notes from cyanogen:
# Do not use the CyanogenMod Updater to go from 10.0 to 10.1. While you will have a functional rom, due to the 1st bullet point, you will be left without your proprietary applications and their data. We highly suggest performing the initial install manually via recovery (flashing CM and your addons). Once you are on 10.1, you can use the CM Updater as per normal.
# Finally, we always advise that you create a backup before any update. Do note, however, that due to Android 4.2 changes to support multi-user mode, your backups will automatically be transferred to /sdcard/0/[backup folder]. Remember this when attempting to restore 10.0.
On the nexus 7 boards I heard TWRP has been updated to see this. Not sure if that is true or not, not sure if that holds true for CWM, or for any recovery on the d2vzw.
However you can use a file explorer app to move them back to the root of the sd card.
Click to expand...
Click to collapse
goldsmitht said:
TWRP has been updated to 2.3.2 (may show up as 2.3.2.3 on your phone) and doesn't have the problem of borking your folders. I've downloaded it (don't remember where, just google it) and it works fine.
also, i'm on 12.18, and do have data, have sent back and forth MMS, downloaded and everything seems find, EXCEPT:
camera works, first time it froze and said couldn't find camera, but rebooted, wiped cache and dalvik and fixed permissions and seems to "work" however, picture quality seems borked a little.
other than that all seems to be working fine.
Click to expand...
Click to collapse
What method did you use to UG to 10.1 to allow you to have data working?
goldsmitht said:
TWRP has been updated to 2.3.2 (may show up as 2.3.2.3 on your phone) and doesn't have the problem of borking your folders. I've downloaded it (don't remember where, just google it) and it works fine.
also, i'm on 12.18, and do have data, have sent back and forth MMS, downloaded and everything seems find, EXCEPT:
camera works, first time it froze and said couldn't find camera, but rebooted, wiped cache and dalvik and fixed permissions and seems to "work" however, picture quality seems borked a little.
other than that all seems to be working fine.
Click to expand...
Click to collapse
According to the TWRP site the vzw gs3 is still on 2.3.1.0. If you have a link to the new one spread the love
peaceofpi said:
What method did you use to UG to 10.1 to allow you to have data working?
Click to expand...
Click to collapse
+1
pyrostic said:
+1
Click to expand...
Click to collapse
I have factory reset the phone - couldn't back anything up - so there goes a lot of music and pictures and most important my backups but oh well - rebuilt the phone - installing 10.1 over stock - let's see what happens.
Note to self - always move your backups to BOTH the SD card AND your computer. Live and learn
peaceofpi said:
I have factory reset the phone - couldn't back anything up - so there goes a lot of music and pictures and most important my backups but oh well - rebuilt the phone - installing 10.1 over stock - let's see what happens.
Note to self - always move your backups to BOTH the SD card AND your computer. Live and learn
Click to expand...
Click to collapse
Data still won't work FYI.
Update 09/10/13. This thread is being updated to reflect many new developments with the HD/HD+. Alternate ROMs are now plentiful and B&N has added Google Play Store and gapps to stock. And now the biggest change for stock is verygreen has broken the file protection scheme that B&N implemented that had made it very difficult to modify stock. The complicated methods developers had to implement to root and modify stock are now gone. So I am modifying this thread to reflect that. It still will be focused on stock and the use of CWM to modify it, but will have a few other mods to other ROMs as well.
What verygreen has developed is a new boot.img file that removes the file protection that prevented users from modifying /system. After that modified boot.img is flashed to internal memory, those /system files can be modified without danger of the device resetting. Also, one added benefit is that with the new boot.img installed on your device, any B&N update will fail. So that means once you have installed the boot.img it will stay there until the user flashes a complete new rom themselves.
The only way users can modify the /system files is to be rooted or to use zip files flashed by CWM. This thread provides zips to root using his boot.img and other zips to make other mods, like enabling Unknown Sources so apps can be sideloaded without using Play Store or the B&N Store.
Verygreen has published his boot.img zips that remove the file protection here. If you use his latest versions of recovery to flash his zip, they will ask if you want to root. It does root and it works very well. But that version of root does not include busybox or superuser which some users like.
I have updated my Universal Root zip to rev3 to include his boot.img and adds superuser and busybox. Just flash that zip with either his or my recovery and you will have root. And with this version of root, there is no danger of being reset by B&N. If you used my earlier versions of Universal Root, I recommend you use my Disable Root zip before flashing this new version.
I also have full rooted 2.1.1 stock zips in item 6 below.
WARNINGs. The CWM recovery in this thread is used to install the zips below to internal memory which are mainly to modify stock. But it can also be used to install a Cyanogenmod (CM) ROM on internal memory as described in the Dummies Guide to installing CM to internal memory here, as well as to modify CM once installed.
Be sure to use CWM to nandroid backup your existing ROM before you try to install anything here. That way if something goes wrong and your system messes up, you can boot to the CWM SD and restore your ROM exactly the way it was before you did anything.
Some of the newer HDplus devices are very difficult to get to boot to an SD. They should eventually boot but many users, including me, have had difficulty. Look at this thread (in particular, look at this post within that thread).
Click to expand...
Click to collapse
If you have questions or comments on this post, reply to this thread. If you are a new user and cannot post here, post on my HD/HD+ tips thread here. Please do not send me private messages or emails. By posting in the forums others get a chance to help you and if I answer your question in the forum, others can see my response and it may help them too.
1. Clockworkmod (CWM) Recovery - READ THIS SECTION FIRST, IT HAS EVERYTHING YOU NEED TO GET STARTED!
CWM recovery is a tool that you can use to install modifications to your stock that you ordinarily could not do without already being rooted. And it has lots of other features like making an exact backup of your stock so you can restore it later if you want. And you should do that before you ever start installing anything else. But the feature that is most useful here is the ability to install (flash) the zips I have here on this thread.
A summary of the below section for those looking for steps is as follows:
a. Make the CWM SD.
b. Copy the installation zips to the CWM SD.
c. Insert the CWM SD to the device and boot to it.
d. Use the CWM commands to backup your device and install the zips.
e. Remove the CWM SD and boot to your modified device.
a. Make the CWM SD.
Before you can install the modifications here you must make a bootable CWM SD. To make one, you will need a spare SD that you are willing to dedicate to use as a permanent CWM card, a card reader for your PC, and burning software.
EDIT (5/22/13) - There is a new procedure brought to my attention by another user (thanks fanoush) which lets you make the CWM SD without burning the image. It seems the OMAP4 devices are a little more liberal on the booting requirements than previous OMAP devices. This makes it easier to install on any size SD. Follow this new procedure as the old procedure sometimes is difficult to acheive:
New procedure:
Format (fat32) any size card with SDFormatter (free on web).
Use partitioning software (Mini-Tool Partition Wizard or EaseUS Partition Manager, both free) to set the first (and only) partition as "active". Don't repartition, just set active. I have read that some versions of Windows will let you set the first partition active without having to use partitioning software, but I only use XP and it does not have that feature.
Unarchive the appropriate set of BOOTFILES for your device (HD or HD+) from my .rar file attached below and copy them to the SD. There should be five files. Make sure you copy the MLO file first before you copy the other four. DO NOT INSERT THE SD INTO YOUR NOOK UNTIL TOLD TO DO SO IN SECTION 1c BELOW!
Move on to item b below to copy the installation zips.
Click to expand...
Click to collapse
Old procedure: Click on Show Contents.
To make a CWM card you must use a process where software copies (burns) an image file to an SD. I recommend using Win32DiskImager. Download and extract the image file for your device (HD or HD+) attached below and burn that to your SD. For detailed instructions, click on the Show Content button.
Attached at the bottom of this post you can get the CWM image zips that I have modified to work on stock. I have versions for HDplus and for the HD. You must use the version for your device, they are not interchangeable. And you must use the CWM image zips from this thread if you want them to work on stock. Download the appropriate 4GB CWM image zip for your device and extract it. You will end up with an approximate 3.7GB .img file. Burn that image to your 4GB or larger SD using Win32diskimager in Windows or use the dd command in Linux or OSX (Mac).
To use Win32DiskImager, find it on the web (here, it's free) and install it on your Windows PC. Open it (be sure to run it as administrator) and select the drive (device) that has your card reader with your SD inserted. Then in the image file box put the location where you have the extracted img file. Then when everything is set right, click on the write button. A warning will pop up asking if you want to proceed. When you have verified that you are going to write to the correct device, click on Yes. (One user overwrote their external USB hard drive by not verifying first). With this 4GB image it will take a while. If you get an error message about access denied it means you are looking at the drive with Windows Explorer. Close Windows Explorer and try again. In fact, it is a good idea to close all unnecessary windows when burning, even your browser.
When burning is complete, temporarily remove the card and re-insert again so the PC recognizes the new image.
If you do not have a 4GB or larger SD, you can use my small version of the image, also attached below. It only requires 120MB of space on the SD. And it has all the same features as it's bigger 4GB brother, it is just smaller. But there is not room to put backups on the card. If you use a small card, see item 11 below for workarounds on making backups.
You can use partitioning software, like Mini-Tool Partition Wizard or EaseUS Partition Manager (both free), to can expand the partition to the full size of the SD you burned it to. But I recommend you not use a really large SD to put CWM on. Certainly no larger that 8GB. It is a waste of a big card to use it for stock CWM.
To burn using Linux or Mac, you are on your own. A user, (jfever311) just added some Linux instructions here. And recently cdaters just added some Mac instructions here.
b. Copy the installation zips to the CWM SD.
With the card still in the PC, copy to the SD card those zips (keep them as zips) that you want to install to the Nook. I recommend the Enable Unknown Sources zip, and, if you want root, the Universal Root zip as discussed in the sections below.
c. Insert the CWM SD to the device and boot to it
Remove the card from the PC and insert into your POWERED OFF Nook and power back on. CWM should appear. If it does not and boots to stock instead, power off and try again. You can tell when it is going to boot to CWM when the 'cyanoboot' logo shows. If it still does not boot after several retries, first make sure you have the right version of the image/files to match your device (HD or HD+). Some of the newer HD+ devices a very resistant to booting to SD. My new device boots to SD maybe once in ten tries. I think it is hardware related. HD's seem to boot to SD very reliably.
d. Use the CWM commands to backup your device and install the zips.
Once CWM appears, use the volume up/down keys to move the cursor and highlight "backup and restore". Then use the n key to activate it. The power key is the back button. Pick backup and it will take several minutes to backup your system. That way if something messes up you can later restore that backup. Keep the backups for future needs, don't delete them.
Then use the power key to move back to the main screen and select "install zip from SD". Pick the zip you want from the list of zips that you put on the SD earlier and select install. Do them one at a time in any order you want. You do not have to do any wiping.
e. Remove the CWM SD and boot to your modified device.
After you finish, remove the CWM card and tell CWM to reboot. Sometimes you get a message saying that it is set to flash a new recovery and do you want to fix that? It makes no difference what answer you choose, so I just say no. It should boot to stock with your changes installed.
Most of the below zips can be flashed (installed) on any version of stock HD-HDplus ROM as long as you have booted the Nook into stock at least once and registered. All of the zips below can be installed and work without the Universal Root if you don't want to be rooted. Just copy any additional zips to the SD while it is inserted in the PC, remove from the PC, insert into the Nook again and boot to the CWM and install per the previous paragraph.
There is an alternative to downloading on your PC and copying the zip to the SD card for flashing. You can download the zip on your device and store it on internal media memory. Then, when you boot to CWM to flash it, select "install zip from SD/choose zip from internal memory" and install from there.
One additional thing. Since the device is very sensitive to the apps you install later (the device will try to reset itself if you install an app that writes to /system), it is probably a good idea to back up with CWM periodically so that if you do have to restore, you won't have to repeat a lot of the changes you made since the last backup.
If you do get into the 8 failed boot process because something got inadvertently added to /system, you can recover from the reset by turning off the device before the 8th reboot and inserting your CWM card. The next boot will boot to CWM and you can restore your last back up to get back to where you were.
Be sure to keep your CWM SD for future use.
EDIT (9/18/13) I don't like or use TWRP recovery but many users have asked for a bootable SD that uses it. So I extracted the files from verygreen's internal TWRP and made bootable SD versions for each device and added them to the list of attachments below. I have both the BOOTFILES version (which I recommend using) and a burnable 4GB image version. The image version is compressed to 7z format to make it small enough to attach to this post.
You are on your own for how to use TWRP, don't ask me, I don't use it.
2. Universal Root for Stock (rev3 - 09/10/13 )and Disable Root (rev2 - 2/3/2013)
Adding Root to stock is an important step in making your device better. It gives you access to files and locations that you are ordinarily not allowed to see or modify. Many further mods to your device depend on being rooted.
This zip will detect which device you have and will root your stock no matter what version of the software (even 2.1.1). The zip is very small and is attached to this post. I added a couple of small apps to help users. Zeam is an alternate launcher to help you see sideloaded apps and AnyCut lets you put a stock Home shortcut on the zeam screen. If you do not want these apps, just go to settings and uninstall them.
This version of root also changes how the boot sequence looks. It briefly shows the original Nook logo, followed by the Cyanoboot logo, followed by the normal stock boot up sequence. After the first boot when the stock home screen comes up, press the n key and a dialog box pops up asking which launcher you want to use. Click default and select zeam. To put a stock home shortcut on zeam, long press the zeam screen, choose shortcut, choose AnyCut, choose activity and scroll to home and select it Then press OK. There will now be a shortcut installed to get back to the stock home screen. An alternative way to switch back and forth between stock home and zeam is described by natefish here.
I also added another zip to disable root if you already rooted your device. It is only to be used if you rooted using rev2 or older of the Universal Root. It will leave all the other things installed by the zips below, just root will be gone. And you can always add root later again if you want by flashing the Universal Root zip. It will not work on rev3. If you want to remove the rev3 root, just go to item 6 below and flash one of my plain stock ROMs. It will take everything back to plain stock including removing the Cyanoboot loader and the root files (and CWM or TWRP if you installed them to internal memory). This is handy if you need to return it to B&N under warranty. But it will leave the Unknown Sources setting enabled if you had flashed that zip.
If you prefer not to be rooted, all of the other below zips can be installed and work without having root.
If you have a previous version of root and get updated by B&N despite setting OTA to manual per item 7 below, just flash this root zip again and your root should be back. Breaking root will not effect your installed apps unless those apps specifically required root. One of the side benefits of the rev3 root is it causes any B&N update to fail, so the root sticks.
3. Enabling Unknown Sources - (rev0 - 09/08/2013) (formerly the Extras zip)
I have a new stand alone Enable Unknown Sources zip and attached it below. It replaces the former Extras zip that is now obsolete. This zip changes a hidden setting in stock to allow apps to be installed from other sources besides the Nook Store or Play Store. You will need to have booted and set up stock before flashing this zip. But you do not need to be rooted.
And I now have a version of the old Extras zip (which included enabling Unknown Sources) for 'Stock installed on SD' by verygreen. Get it here (WARNING! This version of the extras zip is only for users running stock installed on an SD, NOT for users running original stock installed on internal memory. Do not install it on stock on internal, it will do nothing.)
4. Swapping "sdcard" and "ext_sdcard"
Many users have complained that on the HD/HD+, like many phones, the internal media is named "sdcard" so that apps can store their files there. Some users would like them stored on their external SD. This mod will swap "sdcard" and "ext_sdcard" so that apps will store their files on the external SD. The external SD will show as "sdcard" and the internal media will show as "ext_sdcard". And it shows swapped using MTP also. It can be a little confusing since we cannot control the names, but they are swapped. If you don't have an external SD in the slot, both sdcard and ext_sdcard will display the internal media.
I have two zips attached below, one to install the swap feature and one to remove the feature. Just flash the one you want and on the next boot it will become effective. These are for stock only.
I also now have a version for the official CM10.1/CM10.2 on emmc for the HD+ and HD.
WARNINGs This swap is kind of a kludge, so some things are troublesome. For these swap zips to work, your SD must be formatted to fat32. And the settings, storage option in CM does not provide accurate information. In fact, it may hang your device if you try to view it. If it hangs, just reboot. Also another issue is you cannot install apk files from the new sdcard. You must move the apk to internal media memory before installing.
5. New CWM (v6036) for internal memory (emmc) and Restoring stock recovery to emmc (HD/HD+)
Now that verygreen has made available his native CM10.1 ROM and has matching native CWM and TWRP recoveries that can be put on internal memory (emmc), I have made three more zips. The first two are my versions of a repackaged verygreen CWM (v6036) for internal memory for HD (here or here) and HD+ (here or here) that work on both stock and internally installed CM. If you are already on the newer CWM for CM11 (v6045 or newer) that cannot flash older zips and you want to go back so you can, I have modified this zip (rev2) to be flashable with the newer CWM. That way you can go back to v6036 to be able to flash older zips.
The third is a zip to return the stock recovery to internal memory should users want to return their devices to pure stock. A nandroid restore of an earlier stock backup will restore everything except the stock recovery. So if you have installed verygreen's or my recovery to emmc and you want to go back to pure stock, flash my HD+ zip here or here and my HD zip here or here. Both are also attached below.
6. Plain Stock HD/HDplus 2.1.0/2.1.1/2.2.0/2.2.1, Full 2.1.1 Stock with Root (latest 03/05/15)
Warning! All of the zips in this section must be flashed with CWM v6036 or earlier. v6045 or later will cause the installation to abort with assert errors.
I have plain unrooted factory 2.1.0, 2.1.1 and 2.2.0 zips for each device. They will take you back to stock with no root (and with file protection) so you can let B&N update you to the latest ROM version if you want. They also restore the recovery to stock in case you had previously installed CWM or TWRP to internal memory. The plain stock 2.1.0 for HD is here or here, and the HD+ here or here. Plain stock 2.1.1 for HD here or here and HD+ here or here. The plain stock 2.2.0 for HD is here or here and the plain stock 2.2.0 for HD+ is here or here. The plain stock 2.2.1 for HD is here or here and the plain stock 2.2.1 for the HD+ is here and here. If you are flashing these so you can return a device to B&N, be sure to also factory reset/wipe data with recovery (CWM or TWRP). Also an added warning if you are using TWRP and flashing these plain stock zips. After flashing and telling it to reboot, it detects that the plain stock is not rooted and asks if you want to install SuperSU. Tell it to not install as that will cause the plain stock to reset itself.
I also have full stock 2.1.1 rooted ROM zips. They can be flashed with the CWM above and have the verygreen boot.img that removes the /system file protection. They also are rooted and have superuser and busybox. Get the HD version of the rooted stock here or here and the HD+ version here or here. They can be flashed over whatever version you have. You can do it without any wiping so your installed apps and settings will remain intact. This version does not include Enable Unknown Sources, but if you had previously flashed the new Enable Unknown Sources zip, that is a setting and should stick and not need flashing again. The ROM zips will replace your entire /system so any other zips you flashed here like Extras or swaps will be gone. After flashing this ROM, you will need to reflash any mods you want from this thread (except the new Enable Unknown Sources if you had flashed it earlier).
These zips are quite large (over 400MB) so expect long downloads.
7. New OTA (Over the Air) update block
Another user (thanks greenya!) has come up with a new method to block OTA updates from B&N that seems to work. I have tested it with AdAway. I tried to manually update my 2.0.5 system in settings. It says there is an update available but does nothing when I push download. I removed the block and hit download and it began downloading immediately. So it does block them.
If you are rooted, you can do this yourself with AdAway. I have a description in my HD/HD+ Tips thread linked in my signature, here. See item 4.
Another possible block would be to put CWM or TWRP on internal memory per item 5 above. I don't think updates will install without stock recovery installed. They usually fail with CWM or TWRP.
Edit: I just did some testing and if the new boot.img has been installed, the B&N updates fail and abort. See my post here.
8. The Importance of doing Backups
Some users have not made backups because they have installed CWM to a relatively small SD. You need to have backups with these devices because they can and will reset themselves, especially if rooted.
Save your CWM card and the backups because you WILL need them again. I recommend you make a backup of the device before any modifications and another when you think you have it the way you want it. Keep both backups because you may someday need to get back to pure stock so you can update. Some of my mods interfere with updates.
Also, being rooted adds the danger of being reset by some app that modifies /system. So, if you are rooted and you want to install a new app that requires root, make a backup of your device just before installing the app in case it causes a reset.
To restore, go to the backup and restore menu and select restore. That will restore the whole device if you are recovering from a system reset. Or can go to the advanced restore menu to just restore /system if you caught the reset before it completed. There are other times you might want to just restore /data, like just after a clean device update.
9. Modifications to verygreen's New SD Scheme
With bokbokan's help, I modified bokbokan's Cyanoboot to work on verygreen's New SD so the menu works. It is now easy to boot back and forth between stock and CM10.1 with verygreen's New SD Scheme. Just flash the NookHDplus-verygreen-New-SD-add-bokbokan-Cyanoboot zip attached below.
The second zip allows stock to see his emulated media SD partition as ext_sdcard in stock. Just flash the NookHDplus-verygreen-New-SD-fix-stock-to-use-New-SD-Media zip attached below.
Both zips can only be flashed with verygreen's New SD CWM (early 7.1).
10. Recovery Bootloops - (Device boots only to CWM or TWRP recovery)
Occasionally the /rom partition (p5) will get corrupted. That partition contains vital information necessary to operate your device. When that happens it tries to boot to stock recovery so that it can repair itself. But since many users have replaced stock recovery with CWM or TWRP, it boots to one of them and does nothing. Rebooting again does the same thing. So you end up in a recovery bootloop. And restoring your original stock backup does not help since it does not restore the stock recovery nor repair the /rom partition.
To fix it you need to restore the stock recovery by either flashing one of my stock recovery zips attached below or flash a whole plain stock zip from item 6. Then when it reboots, it can repair itself.
Obsolete zips have been moved to the next post.
Current attachments:
XDA:DevDB Information
[CWM/ROOT/UNKNOWN SOURCES] HD/HDplus Stock Root/other Mods - via CWM flashable zips, ROM for the Barnes & Noble Nook HD, HD
Contributors
leapinlar
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2014-10-11
Last Updated 2015-03-05
Change Log
Change Log
03/05/15 - added plain stock 2.2.1 zips for both devices to item 6
12/23/13 - added plain stock 2.2.0 zips for both devices to item 6
11/12/13 - added item 10 Recovery Bootloops
09/22/13 - updated internal CWM to v6036
09/15/13 - added bootable SD versions of TWRP recovery for emmc for each device
09/10/13 - reworked entire post for new Universal Root rev3 and full rooted 2.1.1 stock ROMs.
09/08/13 - Created stand alone enable Unknown Sources for stock and added reference to verygreen's new boot file zip
09/04/13 - updated Swap SD for CM10.1/CM10.2 on emmc to rev6 to fix assert error on HD
08/22/13 - updated Swap SD to apply to the official HD/HD+ CM10.1/CM10.2 on emmc
07/29/13 - fixed broken HD/HD+ CM10.1 emmc swap SD zip (rev4 now works properly on HD)
07/21/13 - added HD version of Restore Stock Recovery zip to item 5
06/29/13 - added link to Extras for stock on SD, item 3
06/16/13 - fixed another typo in SD Swap zip to rev2
06/16/13 - revised SD Swap zip for verygreen's emmc CM10.1 to rev1 to fix an issue where the userinit.d folder was not created.
06/15/13 - added SD Swap zip for verygreen's emmc CM10.1
06/06/13 - added two zips to help with verygreen's New SD scheme (item 9)
05/24/13 - added zip to install my custom CWM (v6028) to internal memory to item 5
05/24/13 - rearranged and renumbered sections to move obsolete items to bottom and added warning about newer HDplus booting from SD
05/22/13 - added alternate procedure for making bootable CWM SDs
05/16/13 - removed item 5, Voice Search and added new item 5, Restore Stock Recovery
05/15/13 - updated HD+ CWM images to rev4, which adds recovery partition backup (v6028)
05/06/13 - modified Extras zip to remove old OTA block (which no longer worked) and add GPS permissions to improve Play Store compatiblity
05/03/13 - added full plain unrooted ROM version 2.1.0 for both devices to section 9 (now 6) and edited other sections accordingly
03/29/13 - added Section 11 (now 8), The Importance of doing Backups, and updated OTA to rev2
03/25/13 - added rev1 of location services to add gps permissions to allow more apps to show as compatible in Play Store
03/17/13 - even further editing to make it look less intimidating
03/04/13 - general editing of text to improve readability
02/24/13 - minor change to new OTA block (rev1)
02/23/13 - added new OTA block method and zips
02/18/13 - added revised HD+ stock CWM compatible with new HD+ Hybrid CM SD
02/04/13 - added modified Update to 2.06 zips for all ROM versions. Numbered sections and put dates on revisions and files
02/03/13 - revised CWM images - HD+ with larger fonts and HD made compatible with the new HD Hybrid CM SD.
02/02/13 - added rev2 of Universal Root, Disable Root, Extras and Gapps + Extras
01/31/13 - added white-on-white repair for version 2.0.6 and plain stock 2.0.0 zips so your system can update to the latest stock version
01/12/13 - added rev1 of Gapps + Extras to correct minor issues and to add zeam and AnyCut for those not wanting to root
01/10/13 - added Location Services
01/06/13 - added SDSwap
01/05/13 - added HD versions of 2.0.0 rooted ROM and white-on-white repair zips
01/04/13 - restored HD+ 2.0.0 rooted ROM link
01/03/13 - added warnings about Voice Search and about the danger of being rooted on these devices, added disable root zip and rev1 of Universal Root
01/02/13 - added small CWM image files and instructions
01/01/13 - added tip about doing periodic backups, interrupting 8 failed boot reset, added Voice Search and updated the HD CWM image to rev2
12/31/12 - re-arranged post and reworked instructions
12/30/12 - temporarily disabled HD+ 2.0.0 rooted ROM link
12/27/12 - added HD CWM and re-labeled zips that work on HD
12/25/12 - added Universal Root and other zips.
12/23/12 - original post for HD+ CWM and HD+ 2.0.0 rooted stock ROM
Obsolete Zips
If you want to see these items, click on Show Content below
a. Gapps/Play Store + Extras (rev2 - 2/3/2013) - No longer necessary for version 2.1.0.
This zip adds Play Store and a few other extras. This is the zip that most will want to install since it gives you a lot of flexibility to install new apps. And if you install it without the Universal Root there is no danger of getting reset.
You can download my NookHD-HDplus-Gapps+Extras-for-stock-rev2.zip here. Rev1 included a few minor fixes and added zeam and AnyCut. Rev 2 adds Terminal Emulator, Root Browser and Userinit. It is approximately 24MB. It can be flashed as long as you have booted and set up (registered) the Nook first. After you install the zip, remove the SD and reboot. You will see "Updating Apps" during boot. That is the system setting up the gapps. Then you should see Play Store in the zeam launcher and you can open it and register with Google. Warning! This version of the gapps zip is for stock only. Do not try to install this version to CM10 on SD.
If you did not install the Universal Root and set up zeam as described in the Universal Root section, you need to do it now.
Many users complain that Play Store lists many common apps as incompatible with your device. Just because Play Store says it is incompatible does not mean it will not run on your device. It just means Play Store will not let you install it. The solution is to find and install the app from somewhere else like the Amazon Store, the 1Mobile Store or from another device. I have found most apps that Play Store says is incompatible actually do work.
b. White-on-White repair for HD/HDplus (latest - 1/31/2013) - No longer necessary for version 2.1.0.
This mod changes some text colors so that most third party apps no longer display white text on a white background. The choice of the text colors was a compromise since the same text colors are used on white backgrounds and grey backgrounds. If too dark they will not show on grey and if too light they will not show on white. Thanks to someone0 for help in selecting the colors and making this mod.
Some people do not like the effect of this mod, so be sure you have made a backup of your system as I recommended earlier before you install this mod so you can easily revert back to stock colors.
Also be sure to install the correct version for your device and software version. If you install the wrong version for your device, it will either not install or get stuck at 99% when it boots. If it does not install or gets stuck, just install the correct version or restore your backup.
You can get the version for HDplus 2.0.0 here and HDplus 2.0.2/2.0.4/2.0.5 here. And the version for HD 2.0.0 here and HD 2.0.2/2.0.4/2.0.5 here. I just added versions for 2.0.6 for both devices. HDplus here and HD here. Since this mod interferes with future updates, I have included two zips to take them back to the 2.0.6 stock settings so that it can update without failing. Get the rev1 of revert to stock settings for HDplus here and HD here.
Leapinlar, shouldn't this thread be in the Nook Hd+ forum?
Yes, I will see if I can get it moved. Thank you for catching that.
Thx so much. I will try it.
Moved.
Wow, thank you very much for this. Flashable CWM? Another road to custom ROMs. Thank you.
Once I get my new setup, I'll see if I can get back on Android development. I've only worked on the Samsung Galaxy 5/Europa for Android development before.
Sorry for the bother, please may I ask; after installing the ROM, will it keep the 8-bootup-failure-reset intact? I know it sounds like a stupid question, haha but I'm curious; since it is overwriting the default ROM. Thank you.
TYVM, I was told I was going to get on HD+ for Christmas and wanted to use it stock for ebooks (I have a BN account and a dieing nook 3G with bought books I want to keep) but the new 2.0.5 update would leave me to choose no tablet stuff (until CM10/cyanoboot gets up) or no BN access.
Does this have the White on White Text fix in or will I need to do that myself?
I don't think he did.
The Old One said:
TYVM, I was told I was going to get on HD+ for Christmas and wanted to use it stock for ebooks (I have a BN account and a dieing nook 3G with bought books I want to keep) but the new 2.0.5 update would leave me to choose no tablet stuff (until CM10/cyanoboot gets up) or no BN access.
Does this have the White on White Text fix in or will I need to do that myself?
Click to expand...
Click to collapse
I'm working on it. Soon. Ok, see OP for links, one for 2.0.0 and one for 2.0.2/2.0.4.
Sent from my HD+ rooted stock using Tapatalk
I believe there is a fault with my dad's HD+, would it be possible to get any version of the stock ROM back? Sorry for the bother.
The pre-rooted ROM (modified 2.0.0 in this thread) loads up sideways, and freezes at 99% upon second boot.
Just checking, you will have the ability to use your B&N account with this, right? You aren't skipping OOBE and becoming "test", right?
dbh369 said:
Just checking, you will have the ability to use your B&N account with this, right? You aren't skipping OOBE and becoming "test", right?
Click to expand...
Click to collapse
That's exactly what I'm thinking. I can't seem to register, that could be my device fault though. I'm going to test with version 2.0.5, and see if I can register. I'll edit with the result.
EDIT: I can't seem to register with version 2.0.5 either, must be a tablet fault. I'll have to get it replaced. So, I'm assuming you can register the modified ROM in this htread, since leapinlar did state it can be activated right?
dbh369 said:
Just checking, you will have the ability to use your B&N account with this, right? You aren't skipping OOBE and becoming "test", right?
Click to expand...
Click to collapse
Right, go ahead and register. It is just like when it came out of the box, except it is rooted. But you can skip it if you want.
Sent from my HD+ rooted stock using Tapatalk
HiddenG said:
I believe there is a fault with my dad's HD+, would it be possible to get any version of the stock ROM back? Sorry for the bother.
The pre-rooted ROM (modified 2.0.0 in this thread) loads up sideways, and freezes at 99% upon second boot.
Click to expand...
Click to collapse
How did you flash it? And what files did you use? Did you wipe /data first? It will freeze at 99% if you flashed the wrong white-on-white file.
Sent from my HD+ rooted stock using Tapatalk
leapinlar said:
How did you flash it? And what files did you use? Did you wipe /data first? It will freeze at 99% if you flashed the wrong white-on-white file.
Sent from my HD+ rooted stock using Tapatalk
Click to expand...
Click to collapse
Thank you for your response.
I'm using CWM on a SanDisk 4GB Class 4 SD Card, I went into "Mounts and storage" > format /data > Yes. Then, "install zip from SD" and selected "NookHD+factory-2.0.0-rooted.zip". After that I waited, rebooted the device, took the SD card out before reboot, and it all worked fine. I'm currently having problems with registration, probably a device fault, therefore I rebooted to solve the issue, then the loading loaded sideways (i.e. landscape mode) even when the tablet is held straight. It also gets stuck/freezes at 99%. I have not installed GAPPS yet, or even downloaded/installed the white-on-white file yet. This problem only occurs on a second reboot, and if you reboot it again after the second time, the same problem occurs.
To get out of the problem, I flashed the ROM again. Now I'm back to stock ROM after 8 failed boots.
Thank you for your response once again. I hope I'm the only one with this problem, and no one else, haha.
HiddenG said:
Thank you for your response.
I'm using CWM on a SanDisk 4GB Class 4 SD Card, I went into "Mounts and storage" > format /data > Yes. Then, "install zip from SD" and selected "NookHD+factory-2.0.0-rooted.zip". After that I waited, rebooted the device, took the SD card out before reboot, and it all worked fine. I'm currently having problems with registration, probably a device fault, therefore I rebooted to solve the issue, then the loading loaded sideways (i.e. landscape mode) even when the tablet is held straight. It also gets stuck/freezes at 99%. I have not installed GAPPS yet, or even downloaded/installed the white-on-white file yet. This problem only occurs on a second reboot, and if you reboot it again after the second time, the same problem occurs.
To get out of the problem, I flashed the ROM again. Now I'm back to stock ROM after 8 failed boots.
Thank you for your response once again. I hope I'm the only one with this problem, and no one else, haha.
Click to expand...
Click to collapse
When you rebooted again after interupting registration, you probably messed up /data again. You probably should have wiped it again and reflashed. You could have a problem with registration if you have a corrupt /rom partition. Stock will automatically repair that if it can. But one of the things I did to help prevent automatic updates was to interfer with that process. Were you able to register once you did the 8 failed boot reset?
Sent from my HD+ rooted stock using Tapatalk
I'm an experienced flasher of many Android devices and I have followed all of the instructions in this thread.
I have:
-- in CWM wiped /data /system
-- then also did the 8 time failed boot to restore stock
... and this ROM will *not* register. After typing in a valid user name and password, registration fails with a "contact customer support".
Ideas guys?
scoopman said:
I'm an experienced flasher of many Android devices and I have followed all of the instructions in this thread.
I have:
-- in CWM wiped /data /system
-- then also did the 8 time failed boot to restore stock
... and this ROM will *not* register. After typing in a valid user name and password, registration fails with a "contact customer support".
Ideas guys?
Click to expand...
Click to collapse
Was that a brand new registration or just reusing the same screenname/ password you used before? I had not problem resigning in with the same credentials as before. I wonder if there was something in my factory zip that identified that rom for my device? I will follow up that with my second device.
EDIT: I was able to flash and B&N register my second device which is on a completely different account. And I could see nothing in my zip that identified anything other than saying it was a US device. It did take what I considered a long time to respond to putting in my credentials. It churned for a while, but eventually responded.
Sent from my HD+ rooted stock using Tapatalk
leapinlar said:
Was that a brand new registration or just reusing the same screenname/ password you used before? I had not problem resigning in with the same credentials as before. I wonder if there was something in my factory zip that identified that rom for my device? I will follow up that with my second device.
Sent from my HD+ rooted stock using Tapatalk
Click to expand...
Click to collapse
Interesting you ask as I've now tried both using an account that was on 2.05 as well as formatting stuff again, reflashing, then trying a new account.
BOTH fail with the same message.
I'm hypothesizing that there could be something on their server that's identifying your ROM as something that should be rejected...
FAQ & Troubleshooting
Samsung Galaxy Ace Plus
====================================================================================================
If you have any queries or doubts regarding Ace Plus Post Here I will Help You.
This Thread will provide you all the information in case you face any problem.
Ask Your questions here without any worries beacuse :
"The More You Ask, More You get to Learn"
====================================================================================================
WARNING : EVERYTHING ONLY FOR GINGERBREAD
====================================================================================================
>>Things You Need To Know Before Flashing Any Rom
Before Flashing Any Rom Be Sure That You Are Fully Prepared:
See that the Ace Plus is Rooted. If not then Go Here
Also Install CWM Recovery.
Make Sure That the Rom is Compatible with Phone Model.
If You Brick Device Then Developers Will not be Responsible.
Make Sure that You are Flashing Rom on your Own Risk.
====================================================================================================
>>Revert back to Gingerbread Rom after Flashing CM10
If you Love your Ace Plus
If you want to Revert back to Gingerbread Rom after Flashing CM10 the follow this Precaution. If you don't do this you will Lose your dear Ace Plus(Super Shiny Hard Brick):
Open the Gingerbread Rom with 7-zip.
Check whether the rom is Lite Package(Contains only some System Folders with required files)
or Full Package (Includes all the System Files & Folders present in Stock Rom)
Don't flash Lite Package Rom Directly. First Flash a Full Package Rom and then Flash Lite Package Rom.
Check whether it has boot.img inside it.
If not then place boot.img from a GB Rom which has boot.img
Now Flash Any Gingerbread Rom you Want.
Enjoy.
====================================================================================================
>>Preventing MD5 Sums Mismatch Error while Restoring Backup
MD5 Sums mismatch error occurs usually when the backup is corrupted.
To prevent his just follow the precaution given below:
Take a Nandroid Backup
After backup is completed go to backup&restore>advance restore (to save time)
Select the backup you just created
Select advance restore cache
Now if everything goes right then the backup was successful.
====================================================================================================
>>Root Access Lost Suddenly
It may happen very rarely that root access is lost. To get back root access just follow these steps:
Download SuperSu and copy to SD card
Boot into CWM
Flash SuperSU
Reboot.
====================================================================================================
>>Location & Security Force Close
If you delete Samsungservice.apk from /system/app then you will get FC in Location & Security.
Download Samsungservice.apk and copy it to /system/app/here
====================================================================================================
>>Adding BusyBox & Init.d Support to Any Rom
If your Stock Rom or any Custom Rom doesnot have Busyox or Init.d Support the follow this:
Download Busybox.zip
Copy it to SD card
Boot into CWM
Now flash the Zip
====================================================================================================
>>White/Black Screen Fade Issue When Installing Rom
If you are getting White screen fade issue try this.
Method 1(Easy):
Requirements:
CWM backup of your working Gingerbread Stock Rom.
Any working Gingerbread Based Custom Rom
Procedure:
Flash Custom Rom
Don't reboot.
Goto backup & restore > advance restore
Restore only boot image of Working Stock Gingerbread Rom
Now Reboot.
Method 2(Advanced):
Requirements:
7-zip for windows.
Galaxy ace plus GT-S7500 only.
Stock Rom of your region or country.
Do not use winrar it will corrupt zip
Procedure:
Download Rom, Your stock rom, and 7-zip.
Get boot.img from your Stock Rom.
Open Inspiration Rom with 7-zip.
Replace the boot.img inside Inspiration Rom with Boot.img of Stock rom.
After it is replaced copy Inspiration rom to your sd card.
Boot CWM, Wipe data, cache, dalvik cache.
Install zip from sd card.
====================================================================================================
>>Precautions To Be Taken For Triangle Away & Reset Binary Counter
Please Follow This Guide For Triange Away:
Requirements:
Read Original Post Carefully Before Going Further
Chainfire's Super SU.(Download)
Triangle Away App.(Download From Here)
Patience.
Procedure:
Make Nandroid Backup.
Flash Chainfire SuperSU in CWM
Install Triangle Away App.
Now Select Reset Flash Counter.
After Reboot The Phone will be temporarily unrooted for 5-7 mins So be patient.
Credits to Chainfire
Don't Forget to Hit Thanks in Original Post
====================================================================================================
>>Installed Apps Are Not Displayed in Google Play Store
If You Are Not Able to See Your Installed Apps on Play Store Follow this.
Go to Settings>Manage Apps.
Go to All Apps.
Find & Select Play Store.
Clear Cache & Clear Data.
If Installed Apps are not Displayed then Reboot Phone
Now You Can See Installed Apps.
If it doesn't work for first time then try again 3-5 times. It will definitely work.
====================================================================================================
>>Enable Android Device Manager for Security (Recommended)
This is the latest feature that Google has added to Google Play Service and most of the users are not aware about it.
Everytime you install a new rom, login, and carry on your work but you forget to Enable this feature.
It is highly recommended for users to keep it enabled.
What it does?
Using this feature you can Remotely wipe your device, ring your device. This feature can erase your important information such as contacts, messages and other information in case your device gets Stolen.
How do I enable it?
Go to Settings > Location & Security
Scroll Down and Select Device Administrators
There you will See that Android Device Manager is Unchecked.
Now tap on Check Android Device Manager
Now Select Activate (See Image)
{
"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"
}
Thats it you have now enabled it.
================================================== ==================================================
>>Battery Bug & Overheating
If you find Battery Bug with your device don't use any app from Play Store to fix it because it will make it even more dangerous.
Follow this Safety Battery Calibration Process :
Charge your phone till 100% and Unplug Charger.
If after charging the percentage falls immediately to 98,97,96.....% then plug charger again.
This time don't unplug your phone after it reaches 100%.
Switch OFF your phone keeping the Charger ON.
Don't Unplug Charger after the phone Switches OFF.
Let the Phone Show 100% Charged then Unplug Charger.
Take out the battery and leave your phone as it is for at least 30 Minutes.
Now plug the battery IN again and restart phone.
Now wou will see that the battery is 99% Charged.
Don't Charge your phone after this.
Charge your phone only when you reach to low battery level after all the above is done.
Now the Battery is Caliberated.
Same applies to Overheating
====================================================================================================
>>Some Useful Advices
Advice 1(USB Debugging):
After installing any rom please go to settings and enable USB Debugging. There are some root apps which require it to be enabled.
If you do not enable it then you will have it face Force Close in that Root apps.
Advice 2(CM10>GB):
If you are using CM10 and want to revert back to gingerbread rom then do not do it directly. Open the gingerbread rom and check whether it has boot.img inside it or not.
Follow the procedure given above Reverting back to ginger bread rom.
Advice 3(Maintenance):
Wipe Cache and Dalvik cache from time to time for removing junk from your phone. Also perform it after installing any Mod.
This will also help you to keep your phone Healthy and also fix some Force Close Issues.
Advice 4(Triangle Away):
Use Triangle Away & Binary Counter Reset At your own risk. Developer will not be responsible for any Damages caused to your device.
Advice 5(Nandroid):
Always Make a Nandroid Backup in CWM before doing anything like Flashing Rom, Flashing Mods, Playing With System Files,
Flashing Kernels etc. In case something goes wrong.
Advice 6(Be Prepared):
Always keep a CWM backup of your Rooted Stock Rom before flashing any Custom Rom.
Store your backup in some safe place. So that when JB update comes you can restore it before flashing Official Jelly Bean
====================================================================================================
+1
reserved for more
reserved
404 error on my signature
some advice from me too
if you are flashoic
then flash stock rom while you are changing majorily
gb>jb or jb<gb
this will prevent some errors
Woo Thats Cool
This should be a sticky in general forum... ask a mod to move it and sticky it...
Re: [IMP]FAQ's All ROMS, MODS
lokeshsaini94 said:
This should be a sticky in general forum... ask a mod to move it and sticky it...
Click to expand...
Click to collapse
No its to be here sticky as everyone will post here q&a and definitely will read it
sent from my arc s, ace +,sgy,st9,mmx a116 or from laptop
amanmehta007 said:
No its to be here sticky as everyone will post here q&a and definitely will read it
sent from my arc s, ace +,sgy,st9,mmx a116 or from laptop
Click to expand...
Click to collapse
Yes, the thread is at right place.
My question is, I have S7500T.
To flash custom ROMS I have been replacing the boot.img with my phones original and it works no problem..
I've tried flashing cyanogen mod but only get blank screen, I'm assuming the only way to get it working on the S7500T is if official update ever comes out and I once again use stock boot.img, or is there another way?
spaedi said:
My question is, I have S7500T.
To flash custom ROMS I have been replacing the boot.img with my phones original and it works no problem..
I've tried flashing cyanogen mod but only get blank screen, I'm assuming the only way to get it working on the S7500T is if official update ever comes out and I once again use stock boot.img, or is there another way?
Click to expand...
Click to collapse
Please don't try Gingerbread boot.img in CM10. You will SUPER HARD BRICK your device. You will have to wait for Official Release and no other method is there for making it work. And CM10 requires CM10 kernel only.
Re: [IMP]FAQ's All ROMS, MODS
One question is, why isn't it possible to simply restore a nandroid GB backup over CM10? Why is it that only a zip should be flashed? Both nandroid backup and flashable zip have the GB kernel after all..
I tried to do that, but only got an error. Thankfully I had an inspiration ROM zip and I flashed it over CM10.
because its a change in android version and as i said
its better to flash stock rom again(once in 5 times) to prevent bricks or anyother issues blah blah...
mon_iker said:
One question is, why isn't it possible to simply restore a nandroid GB backup over CM10? Why is it that only a zip should be flashed? Both nandroid backup and flashable zip have the GB kernel after all..
I tried to do that, but only got an error. Thankfully I had an inspiration ROM zip and I flashed it over CM10.
Click to expand...
Click to collapse
We can restore Nandroid Backup of GB over CM10. I have done it more than 30 times.
I think you should use CWM Recovery 5.5.0.4 by MB-14 because it is best at least for me.
hello friend I know you're good at custom rom.
t but today I have a question, I have the samsung galaxy ace s7500 plus I have the samsung galaxy ace plus s7500L ends in L if I install a custom rom I have no risk??? since only changes the kerne.
Shisuy said:
hello friend I know you're good at custom rom.
t but today I have a question, I have the samsung galaxy ace s7500 plus I have the samsung galaxy ace plus s7500L ends in L if I install a custom rom I have no risk??? since only changes the kerne.
Click to expand...
Click to collapse
You Can Flash the Gingerbread Rom on S7500L Model because the Hardware is Same. You Just need to restore boot.img of your working stock rom after flashing custom rom. Don't know whether it will work because I don't Have L model
Re: [IMP]FAQ's All ROMS, MODS
thanks to thewhisp for a great rom
and especially for 411mb ram... all the features are great...
i want to update my ace plus to thewhisp's CM so... if i update to his rom...
1) all my data will be lost ?
2)if yes what can be done ?
3)will all my apps. + data will be lost ?
i backed up my current rom and my apps. with titanium backup but titanium backup also back's up the system apps. also...
so what should be done ???
please help... i am a newbie...
sent from my GT-S7500 using xda app-developers app
zacg.rishabh said:
thanks to thewhisp for a great rom
and especially for 411mb ram... all the features are great...
i want to update my ace plus to thewhisp's CM so... if i update to his rom...
1) all my data will be lost ?
2)if yes what can be done ?
3)will all my apps. + data will be lost ?
i backed up my current rom and my apps. with titanium backup but titanium backup also back's up the system apps. also...
so what should be done ???
please help... i am a newbie...
sent from my GT-S7500 using xda app-developers app
Click to expand...
Click to collapse
Nandroid backup first. then :
1. Yes, You will lose all data.
2. It would be better if you could do online backup of contacts & messages so that you can restore it in CM10.
3. Backup only your User apps with data and cache using Titanium Backup. Don't backup system apps
Mod problem...
I applied the tabley UI mod...
But after that when i flash my previous backup of cm10
It showed md5 sum mismatch...
Why so...
Now i cant flash my GB back up... what can be done if i want to install my GB back up please help
device - GT S7500
rom - CM10 (thewhisp)
mods - a few...
zacg.rishabh said:
I applied the tabley UI mod...
But after that when i flash my previous backup of cm10
It showed md5 sum mismatch...
Why so...
Now i cant flash my GB back up... what can be done if i want to install my GB back up please help
device - GT S7500
rom - CM10 (thewhisp)
mods - a few...
Click to expand...
Click to collapse
I don't know why that happened.
Try flashing any GB Rom and then try Restoring Backup.
If it doesn't work then flash Stock Rom & CWM again and then try restoring backup.
:good::good::good::good:
Is resetting the binary counter important.. ?? It causes any problems if not reset??
And.. is there any limit to flashing custom firmwares??
Suyash1996 said:
Is resetting the binary counter important.. ?? It causes any problems if not reset??
And.. is there any limit to flashing custom firmwares??
Click to expand...
Click to collapse
As per me it is important. It will not cause any problem.
Yes, there is limit for flashing custom firmwares. If you exceed the binary counter you may hard brick your device. Resetting Binary counter will solve this problem.
Updated: 03/24/2015
Hi all,
I did this mostly for practice but I thought it might be helpful so I went ahead and posted.
Stock LG D850 20f ROM
[*]Rooted/SuperSu
[*]Most bloat removed
[*]Oversharpening fix
[*]Flashable zip
[*]init.d support*
[*]CarrierIQ Remover*
*Init.d support is implemented in ROM only, not the kernel. CarrierIQ is removed automatically after first boot via an init script. Say thanks to @skeevydude for his help in getting this done. I shouldn't say "help", he pretty much did it!
Installation
Flash the Lollipop modem - see @autoprime 's thread here for modem zip
Flash the ROM zip
Wipe cache and dalvik (and in some cases data) if coming from a different ROM
Download
v3* - https://www.androidfilehost.com/?fid=95916177934548695
[QRCODE]https://www.androidfilehost.com/?fid=95916177934548695[/QRCODE]
*No change at all to the ROM itself since v2, I just realized that I've been forgetting to zero out the free space on the image file before uploading, which saves about 600 MB when zipped. New flashable zip is about 1.1 GB instead of 1.7 GB.
Older versions:
v1 - https://www.androidfilehost.com/?fid=95916177934543883
Apps Removed
/system/app:
Google Books
Google Chrome
Google Cloud Print
Google Drive
Facebook
Hangouts
Google Newsstand
Google Play Games
Google Play Music
Google Play Movies and TV
Google Plus
Twitter
/system/priv-app:
ATT Address Book
ATT Caller Name ID
ATT DriveMode
ATT Games
ATT Locker
ATT Lookout
ATT Mobile Locate
ATT Remote Support
ATT Smart Wifi
ATT Mobile TV
ISIS Wallet
ATT Visual Voicemail
MLT (LG tracker)
/system/vendor/app:
Amazon Kindle
ATT Family Map
ATT Home
ATT Keeper
ATT MHS Launcher
ATT Navigator
Uber
DeviceHelp
myATT
YP Mobile
ATT Apps
In case you want some of the ATT apps back, I have uploaded a zip here with those apps. This is NOT a flashable zip. You have a couple of options:
1. You may be able to install these as a normal (user) app by just pulling out the apk and installing the usual way.
2. If that doesn't work as expected, copy the app folder from the zip into the appropriate system folder as listed in the "Apps Removed" section.
Download: ATT Apps
Xposed Info
cmulk said:
Xposed has a couple of bad side effects at this point, so before doing anything you need to use Titanium or something similar to Freeze (this basically what the "helper" does):
LGSmartCover
Weather
Weather Theme
WeatherPlatform
Then you can install xposed as in the thread here: http://forum.xda-developers.com/showthread.php?t=3034811
However, there is still one more bug to keep in mind: Xposed will crash the Tethering and Networks menu. There is no fix for that yet, but as a workaround you can download some apps from the play store (like Mobile Network Settings), to shortcut around the menu that force closes.
Click to expand...
Click to collapse
Credits
@autoprime - Flashable zips, bump'd boot.img, and very clear instructions in his thread here
@timmytim - uploading the lollipop stock images (although I know a lot of others were working on that too)
@Skin1980 - Oversharpening fix
@skeevydude - init.d support and carrierIQ remover
CarrierIQ Removal
CarrierIQ has now been removed!
The removal is done via an init script that runs at boot to disable the IQ service before removing the files in order to prevent a force close. However, if you have to wipe data/factory reset without re-flashing the ROM, you will get a force close on the first boot. The good news is that I've tested this scenario and it should fix itself if you just wait about 20 seconds. In other words, the mentioned script does it's thing to stop the service to fix the force close and you are good to go after that.
Old info below:
cmulk said:
On the 20f lollipop rom (either mine or stock, there's no difference) either freezing LADDM or removing the libraries and LADDM as you mention will cause a force close unless you disable the "IQService" first, which is built into the framework-res.apk. I have repeated it multiple times and it has been discussed quite a bit in the Lounge and other threads. Disabling the service is easy for users to do with the "DisableService" app, and then you can remove LADDM and the libraries as mentioned. The difficulty is that disabling a service is a user setting, so, for example, if I reflash my ROM without the IQ files onto a phone with clean /data, I will again get the force close and an unusable ROM.
Click to expand...
Click to collapse
Manual Steps
In the meantime, here is how users can manually disable CarrierIQ. I take no credit for this method, it is posted in several places by several people, I'm just putting it here for convenience:
YOU MUST DO THIS IN ORDER (or at least the first few steps)
1. Download the "DisableService" app from the play store
2. In the DisableService app, go to System -> Android System and disable the "IQService" service
3. Use a root explorer to delete the folder /system/app/LADDM
4. Use a root explorer to delete /system/lib/libiq_client.so and /system/lib/libiq_service.so
5. (Optional) Uninstall DisableService
Remember, disabling the service is a user setting, so if you need to wipe /data for some reason, you will need to re-flash the ROM (which has the CarrierIQ files included) or else you will get a constant force close when your phone boots.
I'll give it a try, thanks
Flashing now. Will report.
I will be watching this ROM. Thanks for posting.
Exactly what does " if coming from a different ROM" mean? I'm on 4.4.2 10f Wulf (stock - rooted) ROM
JeffDC said:
I will be watching this ROM. Thanks for posting.
Exactly what does " if coming from a different ROM" mean? I'm on 4.4.2 10f Wulf (stock - rooted) ROM
Click to expand...
Click to collapse
Just clean flash to save yourself a hassle
2SHAYNEZ
Thanks for your work. I wish I had some skill in this realm. It'd be nice to pick and choose which apps you wanted removed. I prefer the stock ATT Visual Voicemail app over the one in the Play Store as its more reliable. I also use some of the Google Apps that are removed here as well. But great job in getting something debloated out there.
Sent from my LG-D850 using Tapatalk
Flashing lollipop Issues
Thanks for your work.... When flashing the 2 lollipop roms, 9 out of 10 times I get just a screen with icons, no wallpaper, no notification pull down no buttons at the bottom. I flash the modem the rom then SU and clear cache. I have only got the other ROM to flash successfully once. The same is going on with this ROM, is this happening to anyone else. I flashed it 5 times with the same results, would anyone know why this is happening, seems others dont have this issue. Thank you again for bringing us a debloated Lollipop rom.
shayneflashindaily said:
Just clean flash to save yourself a hassle
2SHAYNEZ
Click to expand...
Click to collapse
Here is what I understand for a clean flash:
"1. Boot into Recovery
2. Make a Nandroid backup
3. Wipe data/factory reset
4. Wipe cache partition
5. Wipe Dalvik Cache
6. Flash ROM
7. DO NOT REBOOT – STAY IN RECOVERY
8. Select backup and restore
9. Select advanced restore
10. Select the Nandroid backup you made above
11. Select Restore data
12. Select Yes – Restore data
13. WAIT!
14. REBOOT"
What I do not understand is step 8, which selects the backup made in step two... and then flashing the backup over the (new) ROM flash in step 6. Wouldn't that overwrite the new ROM you just flashed?
JeffDC said:
Here is what I understand for a clean flash:
"1. Boot into Recovery
2. Make a Nandroid backup
3. Wipe data/factory reset
4. Wipe cache partition
5. Wipe Dalvik Cache
6. Flash ROM
7. DO NOT REBOOT – STAY IN RECOVERY
8. Select backup and restore
9. Select advanced restore
10. Select the Nandroid backup you made above
11. Select Restore data
12. Select Yes – Restore data
13. WAIT!
14. REBOOT"
What I do not understand is step 8, which selects the backup made in step two... and then flashing the backup over the (new) ROM flash in step 6. Wouldn't that overwrite the new ROM you just flashed?
Click to expand...
Click to collapse
I always do a clean flash.. dont need to back up and restore and still get bad results.
louvass said:
I always do a clean flash.. dont need to back up and restore and still get bad results.
Click to expand...
Click to collapse
That's not encouraging.
louvass said:
Thanks for your work.... When flashing the 2 lollipop roms, 9 out of 10 times I get just a screen with icons, no wallpaper, no notification pull down no buttons at the bottom. I flash the modem the rom then SU and clear cache. I have only got the other ROM to flash successfully once. The same is going on with this ROM, is this happening to anyone else. I flashed it 5 times with the same results, would anyone know why this is happening, seems others dont have this issue. Thank you again for bringing us a debloated Lollipop rom.
Click to expand...
Click to collapse
I have not seen that issue, but in case you are not clearing data you may need to try clearing dalvik cache.
Also, (and this is just a shot in the dark) you could try formatting system before doing anything else just in case something strange is left behind there.
JeffDC said:
That's not encouraging.
Click to expand...
Click to collapse
You can try dirty flashing first without losing any of your data.
1. Back up your current Boot and System
2. Back up your current modem (if you're coming from the Kitkat modem), or just download a flashable KK modem already posted on XDA
3. Flash the modem and ROM in this post
4. Wipe cache and dalvik
5. See if it works
If it's not working, then you will need to restore your boot, system, and modem to go back to your original kitkat setup without losing data.
Otherwise, you'll have to backup with Titanium and do a clean flash (wipe data) as already mentioned. Using Titanium makes clean flashing not so bad
I do clear Wipe cache and dalvik I wipe everything and it boots back into a desktop and thats it no notification, the same thing happened with the first lollipop.. but after 10 flashes it finally took... so I thought Id try your de-bloated and the same thing is happening again, not sure why this is. I can jump back to kk after flashing the modem without issues. Thank you again for your work.
Pdj7969 said:
Thanks for your work. I wish I had some skill in this realm. It'd be nice to pick and choose which apps you wanted removed. I prefer the stock ATT Visual Voicemail app over the one in the Play Store as its more reliable. I also use some of the Google Apps that are removed here as well. But great job in getting something debloated out there.
Click to expand...
Click to collapse
I agree that I use most or all of these Google apps as well. However, they update so often anyway that I prefer to just have them as user apps (otherwise you end up with 2 copies - the old static version in the system apps folder, and the updated version in the user apps folder).
As for the visual voicemail, I have posted the ATT apps in a zip in the OP. Visual voicemail is in the VVM_ATT folder.
Thanks!
cmulk,
Would you please clarify post 5 and 9 questions?
JeffDC said:
cmulk,
Would you please clarify post 5 and 9 questions?
Click to expand...
Click to collapse
Sure thing! That's actually what I meant to do in post 13. I am not sure if you can flash over 10f without wiping data, but you could give it a try without losing anything (except time) if you look at post 13.
You should clear cache and dalvik mostly any time you are flashing, unless you are just flashing over another stock 20f ROM.
louvass said:
I do clear Wipe cache and dalvik I wipe everything and it boots back into a desktop and thats it no notification, the same thing happened with the first lollipop.. but after 10 flashes it finally took... so I thought Id try your de-bloated and the same thing is happening again, not sure why this is. I can jump back to kk after flashing the modem without issues. Thank you again for your work.
Click to expand...
Click to collapse
Have you tried formatting /system before doing anything else? I'm not sure that will make any difference, but just for process of elimination at least
cmulk said:
Have you tried formatting /system before doing anything else? I'm not sure that will make any difference, but just for process of elimination at least
Click to expand...
Click to collapse
Thanks I do clear everything but my external mem.
Ever since flashing this I'm getting "no sd card" messages every time I try to download anything ( I don't have an external sd card) but it's never been a problem before. I've restored a backup of my stock Tim and the problem followed me after full wipes.