Database Develop

[GUIDE] How To Receive OTAs Again If You Are On A Leak ***Proven Working Method***

If followed correctly, this a bulletproof method (reposted from our work at Rootzwiki) of returning any image to a true 5.5.886 stock and then applying the OTA update.
Commands/Screenshots
Moto-Fastboot Commands
Root Commands
Boot Mod Commands
***All the files you must have in one folder - Full Package from below***
Necessary Resources
Motorola Drivers v5.4.0 (32-bit) or Motorola Drivers v5.4.0 (64-bit)
5.5.886 Radios (radio.zip)
Full Package of All Other Files You Will Need: Link 1 or Link 2
Optional Resources
5.5.886 Boot Mod
5.5.886 FXZ Restore File
Motorola Fastboot
Root and Forever Root Files
ADB-Fastboot Files
5.5.893 OTA Update
RSDLite v5.6
Fastboot Mode
Make sure the phone is off
Hold down the Volume Down + Volume Up buttons and press the Power button
When the choices appears, press Volume Down twice, till "AP Fastboot" is selected
Press Volume Up to select
Recovery Mode
Make sure the phone is off
Hold down the Volume Down + Volume Up buttons and press the Power button
When the choices appears, press Volume Down once, till "Recovery" is selected
Press Volume Up to select
When the icon with the android and exclamation appear press both Volume Up and Volume Down at the same time to enter the recovery
Step-by-step Process
Download the 3 files under "Necessary Resources"
Install the appropriate Motorola drivers for your operating system
Place the radio.zip file on the root of your SD card (not internal storage)
Unpack the full package of files to one folder on your computer
Turn off your phone completely
Start into Fastboot Mode (listed above)
Connect your phone to your PC with the USB cable and let it install the drivers for your device
After the drivers are done installing, open a command prompt in the folder where you unzipped the full package to
Using the Moto-Fastboot Commands screenshot from above follow each one step by step until you are done
When you have finished, disconnect your USB cable and press the Power button once to turn it off
Start into Recovery Mode (listed above)
Highlight "wipe cache partition" and press the Power button to select it
When it has completed, pull the battery out of your phone and then put it back in
Start into Recovery Mode again
Highlight "apply update from sdcard" and press the Power button to select it
Highlight the "radio.zip" file on your SD card and press the Power button to select it
When it has completed, highlight "reboot system now" and press the Power button to select it
When the device reboots into the OS waited 1 minute for it to load everything in the background
Follow the prompt but don't sign into anything, just get to the homescreen
When at the homescreen, connect your USB cable and then from the pull down menu select "USB connection", then select "Charge Only" and hit OK
Go into Settings -> Applications and enable Unknown Sources and hit OK
Go into Development and enable USB Debugging and hit OK
Back out to Settings -> Battery & data manager -> Battery mode and select Performance mode
Power off your phone and then power it back on normally
Open a command prompt in the folder where you unzipped the full package to
Using the Root Commands screenshot from above follow each one step by step until you are done
Power off your phone and then power it back on normally
Open a command prompt in the folder where you unzipped the full package to
Using the Boot Mod Commands screenshot from above follow each one step by step until you are done
***When a Superuser prompt appears on your phone after the last command, quickly select Allow and make sure you do NOT reboot your phone***
When it has finished, connect your phone to your 3G/4G or a WiFi connection
Go into Settings -> About phone and select System updates
When the prompt comes up, press Setup
Place a check in "I agree to the Motorola Terms of Service" and then press Next
When the update prompt comes up, press Download
Wait for the update to download
When the update prompt comes up, press Install Now
Let update reboot to recovery and install itself
***Your phone may appear as if it is completely off for a little while but leave it be it will turn itself on and continue***
Let the update finish and then it will reboot back into your system
Congratulations! You now have the official 5.5.893 update installed and are back on the official OTA path and forever rooted
Credit to all developers of the zergRush exploit, to realbbb (from Rootswiki) for discovering the Boot Mod, and anyone else who participated in making this all possible.

I have edited the instructions to make things easier. I have included the entire package of all the files you will need under "Necessary Resources".

The official fully detailed guide is now up. Please feel free to comment if you have any questions, concerns, or need help.

The steps can be made even simpler actually.
The radio flash is unnecessary and all that is required is moto-fastboot of the system.img, grfs.img and preinstall.img and then boot, root and DD the .886 boot.img and then the 5.5.893 will succeed.
You can keep data and avoid all those extra steps too!

Hey guys I got a little problem, unfortunatly you guys have generated so much traffic on my Dropbox account that they suspended it for 3 days. I'm going to ask if any of you guys have the full package file to please upload somewhere for a few days and post a link here until my account has been unfrozen. In the mean time you guys can use the optional files to recreate that package listed in the 4th screenshot. I greatly apologize for this inconvinience.

cellzealot said:
The steps can be made even simpler actually.
The radio flash is unnecessary and all that is required is moto-fastboot of the system.img, grfs.img and preinstall.img and then boot, root and DD the .886 boot.img and then the 5.5.893 will succeed.
You can keep data and avoid all those extra steps too!
Click to expand...
Click to collapse
Noob question ... what does "DD" mean?
I'm going to let the process (OP or the one quoted) shake out over the next few days before I even consider going forward. I definitely would love to maintain data.

GertBFrobe said:
Noob question ... what does "DD" mean?
I'm going to let the process (OP or the one quoted) shake out over the next few days before I even consider going forward. I definitely would love to maintain data.
Click to expand...
Click to collapse
dd=raw image
i think or at least it does to me being in computer forensics
---------- Post added at 05:06 PM ---------- Previous post was at 05:04 PM ----------
someone please share a working link for those files.

As soon as your account becomes unfrozen I'll download the "full files package" and try to upload to Megaupload or something like it to have them permanently downloadable.
The steps can be made even simpler actually.
The radio flash is unnecessary and all that is required is moto-fastboot of the system.img, grfs.img and preinstall.img and then boot, root and DD the .886 boot.img and then the 5.5.893 will succeed.
You can keep data and avoid all those extra steps too!
Click to expand...
Click to collapse
Also, I too would like to keep my data and would like to do the simpler way. please clarify what DD means in the above post?

Ok, since nobody can download the full package from the OP, I won't feel so badly about hijacking his thread with different information.
This method is overly complicated and includes many redundant and unnecessary steps. A lot more info about this procedure has been developed since the OP made this guide and the process has been accomplished in several different ways at this point, including RSD lite using modified .xml files and a limited set of images.
dd is a command in Linux to make a direct digital copy of a file or partition, a raw image as stated above. One of the required steps which is part of the streamlined process, is to use a .bat file created by a user to dd the .886 boot.img to the phone after having flashed the system.img, preinstall.img and grfs.img from the FXZ and then rooting it again. This is the part that actually fixes the boot.img so that the update.zip will pass it's assert check for mtd/boot and flash the 5.5.893 update successfully.
This is despite the fact that manually copying the boot.img like this will fail to boot because it is not a signed image. The image is in fact an exact copy so the update.zip accepts it and patches it as per the updater-script.
That is the crux of the fix. All the rest is not needed. The radio does not need to be reverted because the update.zip does not assert the radio version at all.
All of the other pieces being flashed and reflashed is redundant and wiping data is not required at all and makes the rerooting and running the boot mod that much quicker and easier because you are already setup and have USB debugging checked etc. To say nothing of saving the time to resetup the device after a wipe.
I will also add that P3Droid has created a scripted method with all files included and options for loading 5.5.893 and then 5.9.901 if desired. This includes flashing the 3 images with moto=fastboot, the rooting and dd of the boot.img and then reboots into recovery where the only user input needed is to select the update.zip and run it and reboot.
This method will be released on MDW very soon.
I don't want to steal the thunder from the OP, as he was involved in the process much earlier than was I. I came in after success had been established and P3Droid and I saw the extraneous steps and both completed this simpler method with the reduced steps successfully last night.
We take no credit for the development of the method, which involved a large number of people contributing over several days of hashing out the details.
We just took the fat out and made sure it worked as we understood it should.

So I think that I will do this. Lets says I get to 5.893, install safestrap, and on my non safe 'strap' ie, my daily driver, I restore a nandroid backup of the ROM I am running now (eclipsev 2.0, 5.7.893), Will this work? And theoretically I will have the same system I do now, but with 5.5.893/new radio/kernal/on the update path... That all sound about right and doable?
Sent from my DROID BIONIC using xda premium

You cant use safestrap with this because it modifies the preinstall partition.
It won't matter anyway because you have to be completely stock with just root and the steps require will do all of that and remove Safestrap anyway when you flash the stock images. The update.zips are run from stock recovery and the only reason root is required is to dd the boot.img because that operation needs root in adb shell.
So, whatever ROM your are on is immaterial and this will revert you to 5.5.886 and then forwards to 5.5.893 and 5.9.901 as a last option, all the while keeping root by 4everoot.
If you do go to .901 then you have to do extra steps to have any custom ROMs work with the new radio. I am sure the ROM devs will progress rapidly with these new requirements as they have already, but I will not comment nor advise regarding any custom ROMS because I don't use them myself.

cellzealot,
Thank you for all the time you have contributed to participating in the work of this method. I appreciate your continued effort in order to slim down and automate the steps I have listed. I do encourage anyone interested to feel free to use this method instead of mine. However for those who are more interested to take the manual route and prefer to be in full control of what's going on with your device (maybe learn a few things along the way too), I will be keeping this method up and hopefully my Dropbox account will be unfrozen in a few days so the full package can be downloaded again. In the mean while, if anyone still has this file please PM me a link when you can upload it elsewhere and I will have it updated.
Thanks again,
Open1Your1Eyes0
EDIT: FYI, for all those you who want to keep their data just skip the last command in the Moto-Fastboot commands screenshot. The command is "moto-fastboot -w". Skipping this will leave your data intact. However, note that because everyone's data is different, I cannot guarantee this will work for everyone so please note that it is no longer considered "bulletproof" in this case although most likely should work.

cellzealot said:
You cant use safestrap with this because it modifies the preinstall partition.
It won't matter anyway because you have to be completely stock with just root and the steps require will do all of that and remove Safestrap anyway when you flash the stock images. The update.zips are run from stock recovery and the only reason root is required is to dd the boot.img because that operation needs root in adb shell.
So, whatever ROM your are on is immaterial and this will revert you to 5.5.886 and then forwards to 5.5.893 and 5.9.901 as a last option, all the while keeping root by 4everoot.
If you do go to .901 then you have to do extra steps to have any custom ROMs work with the new radio. I am sure the ROM devs will progress rapidly with these new requirements as they have already, but I will not comment nor advise regarding any custom ROMS because I don't use them myself.
Click to expand...
Click to collapse
So are you saying you can't do this to get back on the path and then install safestrap? Maybe i am not understanding something somewhere but i would think you could do this then use safestrap to install a custom rom then when a new update comes from verizon just switch back over to update then if you want go back to your safestrap just go back over. can someone explain this?

Let me clarify your clarification on clarifying what it is I want clarified.
I understand safe strap, as with everything else goes kaputski when doing this as our phone will go back to a stock system. I don't want to try to do this IN safestrap, rather:
1.make a nandroid of current eclipse ROM.
2.use this method to get back to the ota path and a stock phone (5.5.893)
2.5 make nandroid of stock system
3.Install safestrap
4. Restore eclipse nandroid/backup
5.install super cool ics alpha 42 on safe system
6. Rejoice with a cookie, knowing that now I have the radio/kernel back to upgrade path
7. New update comes out, restore nandroid of stock system.. On UN safe system
8. Accept ota
9.rinse
10. Lather
11.repeat
12. Enjoy another one of those cookies
Does this sound feasible? Or not so much.
Thank you Happy Festivus
Sent from my DROID BIONIC using xda premium

ticrandall said:
Let me clarify your clarification on clarifying what it is I want clarified.
I understand safe strap, as with everything else goes kaputski when doing this as our phone will go back to a stock system. I don't want to try to do this IN safestrap, rather:
1.make a nandroid of current eclipse ROM.
2.use this method to get back to the ota path and a stock phone (5.5.893)
2.5 make nandroid of stock system
3.Install safestrap
4. Restore eclipse nandroid/backup
5.install super cool ics alpha 42 on safe system
6. Rejoice with a cookie, knowing that now I have the radio/kernel back to upgrade path
7. New update comes out, restore nandroid of stock system.. On UN safe system
8. Accept ota
9.rinse
10. Lather
11.repeat
12. Enjoy another one of those cookies
Does this sound feasible? Or not so much.
Thank you Happy Festivus
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
Wonderfully explained! Thank you

cellzealot said:
Ok, since nobody can download the full package from the OP, I won't feel so badly about hijacking his thread with different information.
This method is overly complicated and includes many redundant and unnecessary steps. A lot more info about this procedure has been developed since the OP made this guide and the process has been accomplished in several different ways at this point, including RSD lite using modified .xml files and a limited set of images.
dd is a command in Linux to make a direct digital copy of a file or partition, a raw image as stated above. One of the required steps which is part of the streamlined process, is to use a .bat file created by a user to dd the .886 boot.img to the phone after having flashed the system.img, preinstall.img and grfs.img from the FXZ and then rooting it again. This is the part that actually fixes the boot.img so that the update.zip will pass it's assert check for mtd/boot and flash the 5.5.893 update successfully.
This is despite the fact that manually copying the boot.img like this will fail to boot because it is not a signed image. The image is in fact an exact copy so the update.zip accepts it and patches it as per the updater-script.
That is the crux of the fix. All the rest is not needed. The radio does not need to be reverted because the update.zip does not assert the radio version at all.
All of the other pieces being flashed and reflashed is redundant and wiping data is not required at all and makes the rerooting and running the boot mod that much quicker and easier because you are already setup and have USB debugging checked etc. To say nothing of saving the time to resetup the device after a wipe.
I will also add that P3Droid has created a scripted method with all files included and options for loading 5.5.893 and then 5.9.901 if desired. This includes flashing the 3 images with moto=fastboot, the rooting and dd of the boot.img and then reboots into recovery where the only user input needed is to select the update.zip and run it and reboot.
This method will be released on MDW very soon.
I don't want to steal the thunder from the OP, as he was involved in the process much earlier than was I. I came in after success had been established and P3Droid and I saw the extraneous steps and both completed this simpler method with the reduced steps successfully last night.
We take no credit for the development of the method, which involved a large number of people contributing over several days of hashing out the details.
We just took the fat out and made sure it worked as we understood it should.
Click to expand...
Click to collapse
And this is exactly as it should be.
I was one of the first to try the method out, and my set of steps was a lot simpler, as I had not hacked my webtop, and neither had I removed any apps from the system area either. All I did the was revert to stock rooted 43v3r r00ted system with r3l34s3d r00t, revert radio, dd kernel, then flash ota.
Now that you guys have stepped in and cut the fat out, I think a lot of people are going to be much happier with the whole process, happier and more comfortable, which is a major factor with this sort of thing.
Thanks again, cz, p3 and anyone else refining the process, and especially thanks to 0 open for detailing the steps in the beginning, and a huge thanks to real BBB for providing me with the files to dd the kernel when I started doing all this.
This is why I love my bionic and Android in general - you guys rock!
Sent from my DROID BIONIC using Tapatalk

This makes me happy to see this. I was worried about getting back on the upgrade path. Thank you to all those involved in this!

Hey guys,
So I'm finally home and now had a chance to access my files. I'm choosing to forget about Dropbox because I cannot wait for them any longer since I've been getting a lot of PM's requesting this file. I have edited the OP and all file links are updated and working. The full package has been moved to MegaUpload instead. Anyone who was waiting before the method is now fully working and ready for use. As always please feel free to comment if you need any help or have any questions. Thank you for your patience and once again I apologize for the delay.
Thank you,
Open1Your1Eyes0

If this doesnt work for anyone or the instructions seem to insane, p3's new OTA fixer program works like a charm.

TheMuffStuff said:
If this doesnt work for anyone or the instructions seem to insane, p3's new OTA fixer program works like a charm.
Click to expand...
Click to collapse
Where can this be found? I haven't been able to locate a link for it.
Edit: Appears to be here: http://www.droidforums.net/forum/dr...ates-your-modified-motorola-droid-bionic.html

[ROM] STOCK - FULL ICS IMM76D.LP10 for Verizon i815 LTE Tab (only!) *UPDATE 10/16*

UPDATE: My hosting I had for XDA related work expired, so I re-uploaded everything here: http://www.mods4cars.com/pub/xda
Hi everyone. As pretty much everyone of us who got suckered into buying this excellent (hardware) tab from Verizon knows, their update strategy has been very slow and on top of that, glitchy. Finally, 4 months after the other editions of this tab, we're getting ICS... BUT the update is an incremental OTA update that fails on 99% of the tabs, because it expects a version FD01b instead of the FD01 most of us have. The update seems to have gone through for only 2 or 3 lucky users who must somehow have had FD01b on their tab when they got it.
So after one of the best collaboration efforts on the "Tab 7.7 General" forums, I am happy to present to you
The CWM flashable "full stock" ROM for the SCH-i815 - ICS IMM76D.LP10
First up, let me stress again that this is a HACK and that this is RISKY and that if something goes wrong you MAY end up with a BRICK that will require complicated revival ceremonies! Unfortunately I *have* to say here, that whatever you do here, you do AT YOUR OWN risk, I can not be held liable for anything!
Prerequisites:
Verizon SCH-i815 LTE Tablet (ONLY this version!) with Honeycomb (everyone should have FD01 at this point)
Windows PC with Samsung USB drivers installed, meaning when you connect the tab, you should be able to copy files to it.
A micro-SD Card 2GB or bigger, preferable BLANK, FAT32 formatted.
Step 1: Prepare the SD card
Connect the SD card to your PC and copy the ROM files to it.
ROM Choices:
Original Cloned ROM (First version with direct partition image copy, requires >1GB space on SD card which has caused issues for some)
http://electron73.org/XDA/i815/electron_ICS-LP10_i815.zip
Update 10/12:
NEW ROM with full ext4 optimizations. System, Cache and Data (only in wipe version) will be cleared, formatted and "fsck -Dfy" checked!
DO NOT WIPE ANYTHING IN CWM!!! Just choose the ROM file appropriately.
Non-Wipe Version (This one leaves existing data partition alone, only checks it for errors)
http://electron73.org/XDA/i815/electron_ICS-LP10_i815_nowipe.zip
Wipe Version (THIS ONE WILL FORMAT DATA PARTITION, ALL USER DATA WILL BE LOST!)
http://electron73.org/XDA/i815/electron_ICS-LP10_i815_wipe.zip
Step 2: Download the Odin CWM Recovery pack and get ready to flash
Odin Pack: http://electron73.org/XDA/i815/electron_i815_odin_pack.zip
This ZIP contains everything you need now and later during this process. Extract it in any folder you like (Desktop/Odin or C:\Odin).
Run Odin3 v1.85.exe
Step 3: Bring the tab into Odin mode
Hold down the power and volume down buttons on your tab continuously until you see the big warning. Press volume UP to enter flash (odin) mode. Connect USB. In Odin the leftmost ID:COM field should now be yellow. Click the PDA button and select the cwm-6.0.1.1-i815.tar file. Leave everything else as-is. Click start to flash and when it says rebooting immediately grab the tab and hold down power and volume UP until you see the blue CWM screen! If you don't do this and let the tab boot, then it will automatically kill CWM (yes, bastards!), so don't let it boot the regular ROM!
Step 4: Flash the ICS ROM
Insert the card into the tablet, then in CWM go to install zip from sdcard, then choose zip from external sdcard. Select the electron_ICS-LP10_i815_v2.zip.
It will flash the kernel, the radio (LTE modem), the factory fs (/system) and preload partitions. The whole flash will take about 5 min. Especially on the last two steps be patient, it takes a while to extract 800mb and then flash the full filesystem image. Turning off power here (or running out of battery juice!) will make the rom unbootable and will require a full re-do. IMPORTANT: This requires the use of an external SD card! Using internal storage will not work!
WARNING: DO NOT wipe or factory reset in CWM! You can simply install ICS over an existing Honeycomb setup! Choose the correct ROM version: One erases everything and the other one preserves user data. Since this was originally an OTA, it knows how to convert your saved data. So all your emails, save games etc. will still be there! We had too many reports of problems when wiping/factory resetting with CWM. So for now the best advice for anyone looking into installing the ROM is DO NOT WIPE!
UPDATED PROCEDURE as of 10/16 - NO NEED to flash the old 3e recovery any more! Much easier and quicker baseband update below...
Step 5: Download and flash the baseband modem.bin with ODIN
Download the baseband update: http://electron73.org/XDA/i815/electron_ICS-LP10_i815_modem.zip
Bring the tab back into ODIN mode the same as before. Extract the modem.bin file from the modem.zip and drop it in the PHONE section (not PDA!) in ODIN this time. Click start and let it flash and reboot. Done. Under settings/about device you should now have Baseband Version i815.04 V.LP10 / I815LP10
B]Step 6: Optional: Keep CWM or go all stock[/B]
If you would rather like to be full stock than keeping CWM as the recovery program, then bring the tab back into ODIN mode one last time (pwr + vol down) and Connect USB, then flash LP10_recovery.
The ROM is pre-rooted. SuperSU is pre-installed as part of the ROM.
Trouble?
If the tab for some reason gets stuck in a boot loop with the Verizon animation playing over and over, don't fret! Give it AT LEAST 10 full minutes to start with and if it still doesn't show the home screen after that, hold down power and vol up until you're in CWM and wipe data/factory reset (yes, that will completely kill all user data and the tab will be "like new").
Trickier: If you see any warnings in CWM or 3e stock recovery, that there was an error mounting /data, then you lost the data partition and need to do extensive hacking before the tab will ever boot again. We fixed exactly this problem beginning on the very bottom of the page here http://forum.xda-developers.com/showthread.php?t=1927392&page=16 so don't panic! This repair surgery thanks to the excellent guide by Androguide.fr here: http://forum.xda-developers.com/showthread.php?t=1862294
Thanks
Thanks to everyone involved in making this happen! Especially asenduk for dumping the image backups from his tab, rayjr13 for bringing this whole thing to my attention and sending me the first OTA bin file.
Every use of the thanks button is greatly appreciated

Hi, thank you so much for these instructions and all the help. I was wondering does that 6.0.1.1 protect you from the brick bug and I saw that you hosted the V2 file in the original thread but here you have the regular file hosted. Is the V2 better?

johnny13oi said:
Hi, thank you so much for these instructions and all the help. I was wondering does that 6.0.1.1 protect you from the brick bug and I saw that you hosted the V2 file in the original thread but here you have the regular file hosted. Is the V2 better?
Click to expand...
Click to collapse
What is this brick bug people speak of? Bricking during a flash or bricking when you're sleeping at night and doing nothing to the tab?
Thanks again for this Rom electronic73! Hopefully some devs will take this as a base and run with it!
Sent from my SCH-I815 using xda premium

johnny13oi said:
Hi, thank you so much for these instructions and all the help. I was wondering does that 6.0.1.1 protect you from the brick bug and I saw that you hosted the V2 file in the original thread but here you have the regular file hosted. Is the V2 better?
Click to expand...
Click to collapse
Yes the 6.0.1.1 (as far as I know!) is safe. No need to wipe anyway. The v2 included more files that turned out to be not necessary. The files posted here along with the updated, safer method of flashing, should be the best and quickest way to get to full stock ICS.
The v2 was mainly an attempt to bring user ice's tab back to life after his data partition got killed.

Newbie question of the day - where is the IMEI stored on the 7.7? If it's in /system, won't this result in *everyone* flashing this image ending up with the same IMEI (which causes a whole set of problems of its own)?
Rodney

Thank you so much, and I do plan on doing a wipe to clear out my Tab to bring it to a clean slate. Just didn't want it to be a broken state lol.

rhester72 said:
Newbie question of the day - where is the IMEI stored on the 7.7? If it's in /system, won't this result in *everyone* flashing this image ending up with the same IMEI (which causes a whole set of problems of its own)?
Rodney
Click to expand...
Click to collapse
IMEI and such is stored in the mmcblk0p1 partition which (along with 2 and 3 which are the bootloader) we don't touch. So no, we only flash the factory fs, lte modem and kernel. CDMA modem.bin via the new method.

electron73 said:
Hi everyone. As pretty much everyone of us who got suckered into buying this excellent (hardware) tab from Verizon knows, their update strategy has been very slow and on top of that, glitchy. Finally, 4 months after the other editions of this tab, we're getting ICS... BUT the update is an incremental OTA update that fails on 99% of the tabs, because it expects a version FD01b instead of the FD01 most of us have. The update seems to have gone through for only 2 or 3 lucky users who must somehow have had FD01b on their tab when they got it.
So after one of the best collaboration efforts on the "Tab 7.7 General" forums, I am happy to present to you
The CWM flashable "full stock" ROM for the SCH-i815 - ICS IMM76D.LP10
First up, let me stress again that this is a HACK and that this is RISKY and that if something goes wrong you MAY end up with a BRICK that will require complicated revival ceremonies! Unfortunately I *have* to say here, that whatever you do here, you do AT YOUR OWN risk, I can not be held liable for anything!
Prerequisites:
Verizon SCH-i815 LTE Tablet (ONLY this version!) with Honeycomb (everyone should have FD01 at this point)
Windows PC with Samsung USB drivers installed, meaning when you connect the tab, you should be able to copy files to it.
A micro-SD Card 2GB or bigger, preferable BLANK, FAT32 formatted.
Step 1: Prepare the SD card
Connect the SD card to your PC and copy the ROM files to it.
ICS ROM: http://electron73.org/XDA/i815/electron_ICS-LP10_i815.zip
Modem Upgrade: http://electron73.org/XDA/i815/electron_ICS-LP10_i815_modem.zip
Make sure you have MORE than 1GB of free space left on the SD card when done.
Step 2: Download the Odin CWM Recovery pack and get ready to flash
Odin Pack: http://electron73.org/XDA/i815/electron_i815_odin_pack.zip
This ZIP contains everything you need now and later during this process. Extract it in any folder you like (Desktop/Odin or C:\Odin).
Run Odin3 v1.85.exe
Step 3: Bring the tab into Odin mode
Hold down the power and volume down buttons on your tab continuously until you see the big warning. Press volume UP to enter flash (odin) mode. Connect USB. In Odin the leftmost ID:COM field should now be yellow. Click the PDA button and select the cwm-6.0.1.1-i815.tar file. Leave everything else as-is. Click start to flash and when it says rebooting immediately grab the tab and hold down power and volume UP until you see the blue CWM screen! If you don't do this and let the tab boot, then it will automatically kill CWM (yes, bastards!), so don't let it boot the regular ROM!
Step 4: Flash the ICS ROM
Insert the card into the tablet, then in CWM go to install zip from sdcard, then choose zip from external sdcard. Select the electron_ICS-LP10_i815_v2.zip.
It will flash the kernel, the radio (LTE modem), the factory fs (/system) and preload partitions. The whole flash will take about 5 min. Especially on the last two steps be patient, it takes a while to extract 800mb and then flash the full filesystem image. Turning off power here (or running out of battery juice!) will make the rom unbootable and will require a full re-do. IMPORTANT: This requires the use of an external SD card! Using internal storage will not work!
BTW there is NO NEED to wipe! You can simply install ICS over an existing Honeycomb setup! Since this was originally an OTA, it knows how to convert your saved data. So all your emails, save games etc. will still be there!
Step 5: Flash the old Honeycomb recovery in order to do the modem upgrade
Since CWM does not understand the proprietary command used to flash the "firmware" which is the base modem file, we need to use STOCK recovery for this. The downside is that, of course, the new recovery is now locked down and won't accept unsigned files. So we need to flash the OLD Honeycomb FD01 recovery and feed it the modem update!
When the CWM flash above is finished and tells you to reboot, simple press and hold power and vol down again to get back into ODIN mode. Connect the USB again and this time use Odin the same way as above, but to flash the FD10_recovery.tar. This time uncheck the "reboot" tick mark.
Step 6: Flash the modem upgrade with the old stock 3e recovery
When Odin is done above, hold down pwr and vol up until you see the old school recovery pop up saying *manual mode*. Select flash update zip from sdcard and select the electron_ICS-LP10_i815_modem.zip this time. It will go on for a while in total bling flight. No output apart from rotating gears! This one is tricky. Just wait until it either ends saying that it is done or a yellow exclamation point shows up in the middle of the screen. The flash is done.
Step 7: Choose between Stock and CWM
Now bring the tab back into ODIN mode one last time (pwr + vol down) and Connect USB, then flash either CWM or LP10_recovery if you rather like to be full stock. If you chose CWM then be aware that the ROM will try to overwrite that immediately on first boot!! In order to avoid that, flash it with "reboot" box unticked and manually reset into CWM mode (pwr + vol up) and inside CWM select reboot system. It will then give you a big warning that the ROM has a CWM killer and offers you to disable that, so CWM will stay in place (good for Nandroids etd).
Step 8: Boot the ICS ROM and enjoy!
Once you see ICS, go to the play store and install SuperSU. The rom is pre-rooted and just needs the SuperSU app for full root access control.
Trouble?
If the tab for some reason gets stuck in a boot loop with the Verizon animation playing over and over, don't fret! Give it AT LEAST 10 full minutes to start with and if it still doesn't show the home screen after that, hold down power and vol up until you're in CWM and wipe data/factory reset (yes, that will completely kill all user data and the tab will be "like new").
Trickier: If you see any warnings in CWM or 3e stock recovery, that there was an error mounting /data, then you lost the data partition and need to do extensive hacking before the tab will ever boot again. We fixed exactly this problem beginning on the very bottom of the page here http://forum.xda-developers.com/showthread.php?t=1927392&page=16 so don't panic! This repair surgery thanks to the excellent guide by Androguide.fr here: http://forum.xda-developers.com/showthread.php?t=1862294
Thanks
Thanks to everyone involved in making this happen! Especially asenduk for dumping the image backups from his tab, rayjr13 for bringing this whole thing to my attention and sending me the first OTA bin file.
Every use of the thanks button is greatly appreciated
Click to expand...
Click to collapse
Hey Electron, thanks again for your outstanding work as well as all involved to make this happen. Since I installed your V2 this morning, I can skip the ICS ROM installation and go straight to step 5 right? Or is it better to start over from scratch?
Sent from my Nexus 7 using xda premium

bathanr said:
Hey Electron, thanks again for your outstanding work as well as all involved to make this happen. Since I installed your V2 this morning, I can skip the ICS ROM installation and go straight to step 5 right? Or is it better to start over from scratch?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Same here, what steps do I take to flash the updated modem

Awesome!

ice0901 said:
Same here, what steps do I take to flash the updated modem
Click to expand...
Click to collapse
from step 5 on forward. no need to reflash the whole rom if you already have ICS running.
Just odin the old recovery on, flash the modem update zip, then odin the new recovery or CWM back.

boot loop
Not sure whats up. Ive had your rom on all day. No problems. When i went to install the modem update, i entered odin and installed stock recovery, and boom, went into a verizon logo boot loop. i continued any way with the modem install, then put cwm back on, then wiped and data factory reset. waited 10 minutes during bootloop. Gave up, totally reflashed entire V2 Rom, again, stuck on a bootloop...so nwiped and data factory reset again,,,,still a bootloop....
bummer...does it just run until battery dies?

rspong said:
Not sure whats up. Ive had your rom on all day. No problems. When i went to install the modem update, i entered odin and installed stock recovery, and boom, went into a verizon logo boot loop. i continued any way with the modem install, then put cwm back on, then wiped and data factory reset. waited 10 minutes during bootloop. Gave up, totally reflashed entire V2 Rom, again, stuck on a bootloop...so nwiped and data factory reset again,,,,still a bootloop....
bummer...does it just run until battery dies?
Click to expand...
Click to collapse
Weird. OK did the v2 flash go all the way through? Did it finish at some point and say "please reboot" ? Or did it get stuck half way though?
Can you in CWM mount your internal storage? Did you get any errors when you did the full wipe/factory reset? anything saying "error mounting /data" maybe ?

electron73, did you create the .pit file in the cwm zip? It does not seem to match my i815 (which may be my problem, that mine is wrong)

I noticed the latest stock rom is like 550mb opposed to the one you uploaded this morning which was 990mb.. Is there a difference?

almus said:
electron73, did you create the .pit file in the cwm zip? It does not seem to match my i815 (which may be my problem, that mine is wrong)
Click to expand...
Click to collapse
No I didn't create it but it is guaranteed the right one for i815. I know because I messed up my partition table last night and had to use that pit to repartition Lucky I found that. What you would do in order to re-do your pit is open odin, put the CWM in the PDA section as usual and then click PIT and select that pit. That should activate a checkbox "repartition device". Leave that on for this one run and click start.
As a result it should partition, then flash the CWM and you should immediately be able to enter CWM. With CWM running connect USB
and use adb shell to get onto your tab.
IN the root prompt enter parted /dev/block/mmcblk0
and in the parted prompt enter print. If you see the result as in the attached pic (note: no file system in the DATAFS line) then you need to fix that the same way ice got it fixed last night. I think the link to the thread is in the OP

bathanr said:
I noticed the latest stock rom is like 550mb opposed to the one you uploaded this morning which was 990mb.. Is there a difference?
Click to expand...
Click to collapse
Yes the difference is that the preload partition (550mb decompressed) is not included any longer. Not needed. It was never altered in the first place. It only contains a game and useless verizon demonstration videos. I found out later that it had been untouched since Honeycomb FA02c

Yes. V2 went through with no problems.in CWM I can mount efs,cache,system but not data. Then in cwm... OK..wiping data then I get a error mounting data. Skipping format
Sent from my DROID RAZR using xda premium

chefdave12118 said:
What is this brick bug people speak of? Bricking during a flash or bricking when you're sleeping at night and doing nothing to the tab?
Thanks again for this Rom electronic73! Hopefully some devs will take this as a base and run with it!
Sent from my SCH-I815 using xda premium
Click to expand...
Click to collapse
The flash controller in our tablets is buggy. See here http://forum.xda-developers.com/showthread.php?t=1862294

electron73 said:
Yes the difference is that the preload partition (550mb decompressed) is not included any longer. Not needed. It was never altered in the first place. It only contains a game and useless verizon demonstration videos. I found out later that it had been untouched since Honeycomb FA02c
Click to expand...
Click to collapse
Thanks again man.. You have put forth an awesome effort in this work.. Sent you a little something as an appreciation:good:
---------- Post added at 09:43 PM ---------- Previous post was at 08:46 PM ----------
bathanr said:
Thanks again man.. You have put forth an awesome effort in this work.. Sent you a little something as an appreciation:good:
Click to expand...
Click to collapse
I ran into the splash screen just hanging and followed the data retore steps. I keep getting this error when trying to print the print command from the parted prompt.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Flatlinz>f:
F:\>cd 7.7
F:\7.7>cd adb
F:\7.7\adb>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # ls
ls
boot init sys
cache init.rc system
charger lpm.rc tmp
data preload ueventd.goldfish.rc
default.prop proc ueventd.rc
dev recovery ueventd.smdk4210.rc
efs res vendor
etc sbin
external_sd sdcard
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Error: Can't have the end before the start!
(parted)
Any ideas?

How to Install 4.2 images, keep root and all data

**Disclaimer** If you don't understand what follows, don't attempt this. I'm not responsible for you softbricking your device,
This is a quick guide for how to install the new android without losing anything. You'll need fastboot for this. Also, before doing this, be sure to download the supersu cwm update zip, and have it on your sdcard. Make sure you also already have a custom recovery installed (I did twrp, but i'm sure cwm will work just as well). I would also suggest having a backup done, through titanium backup and through recovery, just incase.
First, download the factory images for the n7 from google's website. Decompress them (if you're in windows, you'll need winrar or something similar.) After you decompress the archive, there'll be another one inside (image-nakasi-jop40c.zip), decompress this one as well. Under here, you'll see the .img files for all the partitions. For now, go up one directory. You'll also see here bootloader-grouper-4.13.img. Once you have all this, reboot into the bootloader.
Once you're in the bootloader, you can update the bootloader to the new version (this step isn't needed, but I did it anyways). Plug into your pc, and type fastboot devices. Make sure it's not blank. If it is, you have to update drivers. If you can see the device, open up a command prompt, and cd to the directory that has the bootloader-grouper file. Type the following:
fastboot flash bootloader-grouper-4.13.img
then, after it's done, type:
fastboot reboot-bootloader
Now, you'll be booted back into the bootloader, it'll say 4.13. On to the rom.
cd into the folder image-nakasi-jop40c (make sure you see the files system.img and boot.img before you continue. If you don't see them, the next steps will do nothing but erase your kernel and system parition.)
now, you see the image files. Type the following (still in the bootloader)
fastboot erase system
fastboot flash system system.img
wait until it completes, then type:
fastboot erase boot
fastboot flash boot boot.img
Once this is done, hit the volume up on the device until it shows recovery mode on the top. When it does, push the power key and you'll boot into your recovery (shouldn't be touched.) Inside here, flash the supersu cwm zip file, which'll flash the superuser binary, and supersu. Once this is done, do a factory reset (removing your data and cache.) Boot into the rom.
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
My first boot got stuck for some reason. if it happens to you, just hold the power button and hard reboot. (I did this on 2 devices, it only happened to one of them, so I figured I'd give you all warning.)
Links:
SuperSu binary: https://docs.google.com/open?id=0B7a8xHNJlpgTR0ZkR1pWZWR2VzA
Google Factory Images: https://developers.google.com/android/nexus/images

Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?

Thanks for this.. Apparently you found out too a clean 4.2 isn't rootable via typical methods.
That SuperSU package did the trick. I have to remember to keep a SuperSU binary on hand for these kinds of situations that SuperUser fails..

jefferson9 said:
Thanks for this.
I flashed the 4.2 ota in the dev section and I lost root. Can I just flash the supersu binary in cwm to regain root?
Click to expand...
Click to collapse
Yes. If you do it though cwm, you're not using any exploits, you're just inserting the superuser binary and supersu.apk into the proper places on the rom. On any nexus device, any rom, this will root it.

mstrk242 said:
Once it's booted, you'll notice your internal sd card appears to be empty (mine did, I was worried at first.) For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place.
Click to expand...
Click to collapse
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.

tehSmoogs said:
DANGER WILL ROBINSON!!
The "odd reason" is called "multiple users" - add a second user and they get a folder called 10.
Click to expand...
Click to collapse
Exactly.
If everything goes right we should have an AOSP prerooted build in about *looks at watch* 20 minutes.... Unless there is a compile error or SU error. *laff*
Back to watching the scrolling terminal window

Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!

kwhee07 said:
Just got this working on a mac...
did not update bootloader(couldnt get it to)
other than that, same commands except all fastboots are ./fastboot on a mac
the only other trick is i needed the fastboot and abd files in the jop40c folder...seems to have worked like a charm....im deff on 4.2 with su installed... and it looks like my data is still there...once google is done restoring i'll know just how sucessfull it is, but so far, seems to work!!!
Click to expand...
Click to collapse
I did this all on linux, just kind of adapted the guide for windows. I figured all the linux users would understand how to do it on their own. Glad to know it's the same for mac as well.

OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/

rootbrain said:
OK where did they put the developer options? Not in settings on my 32GB 4.2 device
Never mind. This: http://www.androidpolice.com/2012/1...hidden-in-android-4-2-heres-how-to-find-them/
Click to expand...
Click to collapse
Settings - about tablet - build number
push it a few times and it will enable dev options

You have .bat file in the package.

Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...gned-nakasi-JOP40C-from-JZO54K.094f6629.zipia
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.

Here is my method:
1. Download official 4.1.2 from http://forum.xda-developers.com/showthread.php?t=1929270 and 4.2 OTA image from http://forum.xda-developers.com/showthread.php?t=1989188
2. Boot into CWM (i have CWM touch installed)
3. Clear data and install 4.1.2, don't forget to turn on root in the installer
4. reboot check that root is fully working
5. reboot into recovery install 4.2
6. before reboot CWM will ask to disable recovery flash and protect root. Ansver yes to both questions

I'm confused, it says if you are already on a custom rom, just flash as usual.
What makes this different?

I was on stock ROM rooted with some system modifications, and this wwadd the only way I could get the update working...
Sent from my Nexus 7 using xda app-developers app

mstrk242 said:
For some odd reason, it moved the entire contents of my sdcard into a folder on it called 0. When you get back into android, simply move the folder all up one level so they're in the proper place. You now have the rom booted, rooted, with all your data. Now, you can do a titanium restore to get all your stuff back.
Click to expand...
Click to collapse
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.

Ill have to wait until a rooted rom is created, I have no comp.
Sent from my Nexus 7 using XDA Premium HD app

can I install image-nakasi-jop40c.zip directly without upgrading bootloader?

Zuk. said:
So I'm at the step listed above. I have 4.2 on my device but I can't seem to find this "0" folder. I'm browsing the /sdcard folder via adb shell. Am I looking at the wrong place? Do I have have the incorrect permissions? Or might it not be there?
Thanks.
Click to expand...
Click to collapse
Not advisable to move this folder - if it got moved to a new location by the o/s then there's probably a good reason why - maybe like 4.2 introducing multiple users
Each user appears to get their own "home" directory created in /mnt/shell/emulated/
Default user dir is "0"
Second user dir is "10"
Each contain the standard dir's from 4.1 and earlier.

Travelawyer said:
Why so complicated?
I downloaded 4.2 from here:
http://android.clients.google.com/p...signed-nakasi-JOP40C-from-JZO54K.094f6629.zip
I then just flashed it from recovery via CWM.
Done.
CWM asked me if I wanted to maintain root and of course I chose the correct answer on this, so now my N7 is running on a rooted 4.2.
Click to expand...
Click to collapse
You had two extra characters at the end of your link, but I fixed it above and it's good to go for others in the future. Just flashed it in TWRP, it didn't ask if I wanted to maintain root, hit reboot when it was complete and lost root, so it doesn't work for everyone - good news is that all my data remained intact without having to resort to advanced restoring my data from a backup....
When I tried the SuperSU binary root flash trick, I finally got root back. But don't think it's as easy to get to recovery! I had to obtain the TWRP Recovery one more time since it wiped it and put in place a recovery that did absolutely nothing but reboot the device after a few minutes, so you'll have to
Code:
fastboot flash recovery openrecovery-twrp-2.3.1.1-grouper.img
to get TWRP back.... Hope that helped everyone!

[i537] Safestrap'd 4.2.2 to Root'd 4.4.2 Guide

Here is everything you need for a flawless upgrade from a 4.2.2 to 4.4.2 on the i537 hardware.
Step 0: Download this zip file. It has everything that we will need (except Odin3. Don't want my link/thread/post pulled).
Step 1 - Update from to 4.3.
Download and unzip the Stock ML2 4.3 image. Reboot your phone into Download Mode (Hold Volume Down while booting up, then press Volume Up when prompted). Don’t worry about current root, SafeStrap, etc - as it’s all going away soon.
Step 2 - Match up the file names to the four ‘Files’ sections in the lower right corner of Odin3. The individual filenames of the .tar.md5 files will be used as an identifier. Check “update bootloader” and click ‘Start’. Once it finishes and reboots into 4.3, enable USB debugging mode on the phone.
Step 2- Reboot into Download Mode. Apply Pwnedkernel 4.3 with Odin using the PDA File section.
Step3 - Now let the phone boot up. You will need USB Debugging enabled again, and ensure that you have USB ADB access.
Step 4 - Once ready, run Saferoot to the running pwned 4.3 image (install.bat for Windows, install.sh for Linux/Mac OS). Follow the terminal instructions until completion.
Reboot. Launch SuperSU and update the binary. Disable Knox with your new root access. Ignore any issues with Modems, etc.
Step 5 - Flash original 4.3 kernel back with Odin3 using the PDA File section.
Step 6 - Place your SafeStrap apk, PwnedKitKat, and SuperSU to your SD Card.
Step 7 - Install SafeStrap (make sure to launch it for the bootloader to install correctly)
Step 8 - Reboot into SafeStrap recovery. Flash PwnedKitKat.zip, followed by SuperSU.zip. Do not reboot in between, clear cache, or any other nonsense.
Step 9 - When finished, reboot back into DOWNLOAD MODE. Now flash the stock KitKat kernel using Odin3 (using the PDA File section).
Finished!
Shout-out to: Hashcode, My-blue-snog-box, TransformixS4, & Sunderwear. Y’all have kept me sane dealing with this phone and it’s locked bootloader.

casadelbeard said:
Finished!
Shout-out to: Hashcode, My-blue-snog-box, TransformixS4, & Sunderwear. Y’all have kept me sane dealing with this phone and it’s locked bootloader.
Click to expand...
Click to collapse
Great guide!
I'm glad I helped and thanks for the shout out!
I hope I will help you in more things!
-TransformixS4

Do I have to do a factory reset? Or simply clear cache/dalvik?

casadelbeard said:
Step 1 - Update from to 4.3.
Click to expand...
Click to collapse
I hate to be a nit picker, but shouldn't this say "from 4.2 to 4.3"?
Thanks for a great post and the zip file! Makes it nice n easy for us. Can't wait to flash later!

?
Tell me how do you download your zip because after an hour of "downloading to my pc" I yet have to see any file in any of my download folders.
2nd of all I made the mega account, tried downloading through the account to my pc, then through the cloud, then through the sync & still am unable to physically see any download happening onto my pc hdd... Although I respect the owner, Kim Dotcom there is something wrong since you can't simply even download a file like it is normally available, (a standard) through your browser..
Please explain to me how do you get the 1.67gb file onto the pc because I tried everything I could think of and I am unable to & I am not a noob.
This is the first time i stumbled upon something weird like this..

when i update to Kitkat on safestrap it says "Checking MD5 File... Skipping MD5 Check: no MD5 File found." Should i be worried?

casadelbeard said:
Here is everything you need for a flawless upgrade from a 4.2.2 to 4.4.2 on the i537 hardware.
Step 0: Download this zip file. It has everything that we will need (except Odin3. Don't want my link/thread/post pulled).
Step 1 - Update from to 4.3.
Download and unzip the Stock ML2 4.3 image. Reboot your phone into Download Mode (Hold Volume Down while booting up, then press Volume Up when prompted). Don’t worry about current root, SafeStrap, etc - as it’s all going away soon.
Step 2 - Match up the file names to the four ‘Files’ sections in the lower right corner of Odin3. The individual filenames of the .tar.md5 files will be used as an identifier. Check “update bootloader” and click ‘Start’. Once it finishes and reboots into 4.3, enable USB debugging mode on the phone.
Step 2- Reboot into Download Mode. Apply Pwnedkernel 4.3 with Odin using the PDA File section.
Step3 - Now let the phone boot up. You will need USB Debugging enabled again, and ensure that you have USB ADB access.
Step 4 - Once ready, run Saferoot to the running pwned 4.3 image (install.bat for Windows, install.sh for Linux/Mac OS). Follow the terminal instructions until completion.
Reboot. Launch SuperSU and update the binary. Disable Knox with your new root access. Ignore any issues with Modems, etc.
Step 5 - Flash original 4.3 kernel back with Odin3 using the PDA File section.
Step 6 - Place your SafeStrap apk, PwnedKitKat, and SuperSU to your SD Card.
Step 7 - Install SafeStrap (make sure to launch it for the bootloader to install correctly)
Step 8 - Reboot into SafeStrap recovery. Flash PwnedKitKat.zip, followed by SuperSU.zip. Do not reboot in between, clear cache, or any other nonsense.
Step 9 - When finished, reboot back into DOWNLOAD MODE. Now flash the stock KitKat kernel using Odin3 (using the PDA File section).
Finished!
Shout-out to: Hashcode, My-blue-snog-box, TransformixS4, & Sunderwear. Y’all have kept me sane dealing with this phone and it’s locked bootloader.
Click to expand...
Click to collapse
I do not understand which 4 files to put where
Match up the file names to the four ‘Files’ ... How do you MATCH them up. I only see one file to match up called CSC
What does the AP CL and CP and how do those match up to Bootloader PDA and PHONE ??

Display issues
As soon as I installed 442 kernel display issues popped up. The screen is brighter on the left than on the right with vertical lines running throughout.
Started whole process again... issues go away until 442 kernel is reapplied.
Any suggestions?

I was able to get Eclipse TW 4.02 SS ROM to boot and it looks very nice so far.. as close to AOSP as we will get. I started with the usual 4.3 > TR> SS 3.71 > NC9 Update >KK Kernel > SS3.73 upgrade path, then downloaded the newest eclipse 4.02 SS ROM and 4.4.2 i537 modules. I went ahead and inserted the modules into the eclipse ROM just to save an additional flash step, then flashed the new rom, wiped data,dalvik and cache then rebooted to download and flashed the KK i537 kernel on top. After a few minutes I'm at the setup screen.
So far the only issue I'm battling is the default camera FC, the Google camera app doesn't seem to work either

downloading issues?
baldusiek said:
Tell me how do you download your zip because after an hour of "downloading to my pc" I yet have to see any file in any of my download folders.
2nd of all I made the mega account, tried downloading through the account to my pc, then through the cloud, then through the sync & still am unable to physically see any download happening onto my pc hdd... Although I respect the owner, Kim Dotcom there is something wrong since you can't simply even download a file like it is normally available, (a standard) through your browser..
Please explain to me how do you get the 1.67gb file onto the pc because I tried everything I could think of and I am unable to & I am not a noob.
This is the first time i stumbled upon something weird like this..
Click to expand...
Click to collapse
I have downloaded the file 3 times now (accidentally deleted it the first, then ineeded it on a laptop at a friends house. Downloaded flawlessly. Im FAARRR from a noob, but honestly, a 10 year old could do it. I did my sons active and mine. Try using a differrnt browser or something. Only took about 20 minutes total to download the whole file. I used IE every time. I dont know if thays the dame browser you used but if not, then try that. (I know this post is a little older, but for someone like me who just picked up a couple actives this week it came in mighty handy. Thanks for the tutorial. Does anyone know of any 4.4.2 touchwiz based rome that I can use now that I have safestrap (3.73) running? Or is this basically all we are going to get. Im ok with that but woild love a deodexed TW rom to use. Have trued deodexing mine several times now and while it says thay it worked and is complete, its still odexed after reboot from recovery??!?!

Decrypt OxygenOS without losing data

Hello there!
Today, after a bit of tinkering around I managed to get my OnePlus 3 in a decrypted state without losing data!
However, this is NOT a method where your data will remain on the phone, it requires you to copy a backup to your PC and then copy everything back + fix permissions. In this guide you'll completely wipe/reset your phone prior to restoring everything.
FAQ:
Q: Why do I need an undecrypted phone?
A: So far (as of today, 06.07.2016) multiboot will not work on encrypted phones. That's probably the only reason why you'll ever want to decrypt your phone.
Q: Will updating the ROM force encryption again?
A: If you're using OxygenOS (or another encryption forcing ROM), yes. However if you flash the Full ROM ZIP and immediately after that SuperSU (DO NOT USE SYSTEMLESS OR IT WILL ENCRYPT AGAIN!!!) WITHOUT REBOOTING it'll not encrypt the device again. (Thanks to @JumboMan)
Q: I've followed your guide but my phone got encrypted again!
A: You've probably used the Systemless SuperSU version which does indeed not prevent your device from being encrypted again. Use the normal version available HERE.
You'll need:
A PC (obviously)
Unlocked OnePlus 3 (will probably work on other OnePlus phones, not tested!)
TWRP Recovery (follow THIS LINK for a guide)
About 50 GB of free space on your PC (depends on how much data you have on the phone)
ADB and Fastboot drivers installed on your PC (to get those connect your OP3 to your PC, as storage choose MTP, open the emulated OnePlus CD-Drive and install those drivers)
(Optional) 15 Seconds ADB Installer
A bit of time, roughly 30 minutes to 1 hour
!!!DISCLAIMER!!!
I'M NOT RESPONSIBLE FOR ANYTHING YOU'RE ABOUT TO DO HERE, THIS GUIDE IS PURELY WRITTEN "OUT OF MY HEAD" AND I CANNOT CONFIRM ANY OF THE FOLLOWING STEPS ANYMORE!!!!
ONLY DO THIS IF YOU KNOW HOW TO RECOVER FROM A HALF-INSTALLED OR COMPLETELY WIPED SYSTEM!!!​
How To:
READ AND ACKNOWLEDGE THE DISCLAIMER ABOVE!
Done? Are you really sure? ... Okay!
If you don't need your data backed up simply start at Step 10 and ignore the restore parts after that.
Still on OxygenOS (or any other ROM) make sure you've enabled ADB in Developer Options and connected + allowed your PC at least one time, else ADB in TWRP will not work.
If you have Titanium Backup, create a backup of all your apps before starting. Just in case, you never know...
Once done boot into TWRP (see above for an installation guide)
Create a normal TWRP backup
Type in "adb devices" to check if you're allowed to use ADB inside TWRP. If it says "unauthorized" refer to Step 1 again.
Once done open up a CMD on your PC and cd to the directory you want all your backup-files to be (or navigate via Windows Explorer to the folder, hold "Shift", right-click and choose "Open command window here...")
Type in "adb pull /data/media" and wait. Depending on the size this can take a few minutes.
After that's done make sure all your files are here and ADB is not reporting any skipped files.
Checked all your files? Okay!
In TWRP choose "Reboot" and "Bootloader". This will put your phone into Fatboot mode.
Type in "fastboot devices" to check if your phone is recognized. If not go into device manager, find the Google Bootloader drivers and install those.
NOW IS YOUR LAST CHANCE TO MAKE SURE EVERYTHING'S BACKED UP AND THERE!
Next type in "fastboot format userdata" and hit enter. This will completely wipe your device.
Boot back into TWRP by using the volume rocker and the Power Button.
ADB is probably not working now (will only report "unauthorized"), MTP however still works. Copy the TWRP folder we backed up earlier onto the device again.
Once copying finished restore the backup and reboot into recovery again. You're now able to use ADB due to the adbpub.key being present again. (You could've done this earlier but it's easier that way.)
Copy the rest back onto the device with "adb push / /data/media". (I'm not really sure if this command is right, beware!)
Now type "adb shell chown -R media_rw:media_rw /data/media" to fix issues later in the ROM.
You're basically finished now! Simply reboot and wait till it boots up again. If you're getting stuck at a "Wrong PIN" or "Wrong Pattern" screen SEE THIS COMMENT I made in another thread.
Finished!
As said, I'm not sure if I forgot something here or not. However I think I got everything covered

Thank you. This was a much needed guide for all of us
Sent from my ONEPLUS A3003 using Tapatalk

Nice

Noob questions: is the decrypted OS faster? Performances of the phone are the same? What about updates (any update will crypt it again?
Thanks for any feedback!
Sent from my OnePlus3 using XDA Labs

IlD4nX said:
Noob questions: is the decrypted OS faster? Performances of the phone are the same? What about updates (any update will crypt it again?
Thanks for any feedback!
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
Performance is about the same.
I have no idea if updates will crypt it again, I think not tho? Not sure.

ota updates might encrypt it again if you're on stock. depending if there's a new kernel. the kernel I think forces encryption. so we need a modified boot img to disable forced encryptions. or use a custom kernel that disables force encryption.
If you're on a custom rom based on aosp/cm. most of them doesn't force encryption. so there's no need to worry.
Sent from the moon and back

Thanks for the guide, will this wipe my internal storage?

daavid1995 said:
Thanks for the guide, will this wipe my internal storage?
Click to expand...
Click to collapse
Yes, however the guide shows you how to get a backup of ALL your files before anything gets wiped.
Ajo, und servus aus Österreich

IlD4nX said:
Noob questions: is the decrypted OS faster? Performances of the phone are the same? What about updates (any update will crypt it again?
Thanks for any feedback!
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
Yes. updates will encrypt data again.
if you want to remain non encrypted after update then following procedure.
1. download full rom zip (not ota zip)
2.flash full update zip
3.without rebooting after flashing update just flash SuperSU zip. SuperSU will patch your boot img to remain in non encrypted state.
Proof- myself tried it on 3.2.0 update and it works without any problem

JumboMan said:
Yes. updates will encrypt data again.
if you want to remain non encrypted after update then following procedure.
1. download full rom zip (not ota zip)
2.flash full update zip
3.without rebooting after flashing update just flash SuperSU zip. SuperSU will patch your boot img to remain in non encrypted state.
Proof- myself tried it on 3.2.0 update and it works without any problem
Click to expand...
Click to collapse
Added to the OP Thanks for testing!

Thanks, i will try
Dere haha :fingers-crossed::good:
EpicLPer said:
Yes, however the guide shows you how to get a backup of ALL your files before anything gets wiped.
Ajo, und servus aus Österreich
Click to expand...
Click to collapse

maybe stupid questions, but not clear for me:
is there a negative point decrypting the phone or are there any risks?
will decrypting have an effect on the security of the phone?

odooo said:
maybe stupid questions, but not clear for me:
is there a negative point decrypting the phone or are there any risks?
will decrypting have an effect on the security of the phone?
Click to expand...
Click to collapse
As long as you're not an "international searched criminal" where the FBI tries to break into your phone then, no
I'd say it is a bit less secure but who cares, anyone who wants access to your phone somehow gets it anyways, TWRP isn't helping here either since anyone can simply boot into recovery and recover all files from there nonetheless.
Decryption risks are only when you're not good at backing up your data, else there are no risks of doing so.

@EpicLPer:
17. Copy the rest back onto the device with "adb push / /data/media". (I'm not really sure if this command is right, beware!)
Click to expand...
Click to collapse
"adb push / /data/media" doesnt work for me. Can somebody help? I restored the TWRP-Backup and only need to copy the rest on the device.
Edit: I did it in another way, copied all files manually.

Can someons dcrypt this
IzpG+nubzE2m3krvbos0lVDLANkIkiekZt209MYU12Vzny8WNOS7o4JGNoVAm41e/44IYPHmh
0Y7NnLW1JghbWJwbzL1WIpQw7nkzQoH9dEwvTiloTg5BI1u9TYRExzLGQEDUqN2hjq1G5cn
CqDmYoQnMs2bMiuajZweq9ZDC7gLruq6dse0L96gzZFoC/33lF0h1mEh7SBgW3FrcsjhRQ==
Sent from my SM-N910P using XDA-Developers mobile app

Worked, Thanks

How can I check if my device is decrypted or encrypted?

odooo said:
How can I check if my device is decrypted or encrypted?
Click to expand...
Click to collapse
Go to Settings > Device Security and check if it says encrypted or if it gives you the option to encrypt. If second, you know it's decrypted.

Can somebody do some benchmarks? I am really curious whether it makes a difference or not.
from what I've heard it makes a big difference in sequential rw speeds, which are actually pretty important on android.

Will it wipe my rom too?? Or just internal storage??
---------- Post added at 04:03 PM ---------- Previous post was at 03:31 PM ----------
EpicLPer said:
Hello there!
Today, after a bit of tinkering around I managed to get my OnePlus 3 in a decrypted state without losing data!
However, this is NOT a method where your data will remain on the phone, it requires you to copy a backup to your PC and then copy everything back + fix permissions. In this guide you'll completely wipe/reset your phone prior to restoring everything.
FAQ:
Q: Why do I need an undecrypted phone?
A: So far (as of today, 06.07.2016) multiboot will not work on encrypted phones. That's probably the only reason why you'll ever want to decrypt your phone.
Q: Will updating the ROM force encryption again?
A: If you're using OxygenOS (or another encryption forcing ROM), yes. However if you flash the Full ROM ZIP and immediately after that SuperSU WITHOUT REBOOTING it'll not encrypt the device again. (Thanks to @JumboMan)
You'll need:
A PC (obviously)
Unlocked OnePlus 3 (will probably work on other OnePlus phones, not tested!)
TWRP Recovery (follow THIS LINK for a guide)
About 50 GB of free space on your PC (depends on how much data you have on the phone)
ADB and Fastboot drivers installed on your PC (to get those connect your OP3 to your PC, as storage choose MTP, open the emulated OnePlus CD-Drive and install those drivers)
(Optional) 15 Seconds ADB Installer
A bit of time, roughly 30 minutes to 1 hour
!!!DISCLAIMER!!!
I'M NOT RESPONSIBLE FOR ANYTHING YOU'RE ABOUT TO DO HERE, THIS GUIDE IS PURELY WRITTEN "OUT OF MY HEAD" AND I CANNOT CONFIRM ANY OF THE FOLLOWING STEPS ANYMORE!!!!
ONLY DO THIS IF YOU KNOW HOW TO RECOVER FROM A HALF-INSTALLED OR COMPLETELY WIPED SYSTEM!!!
How To:
READ AND ACKNOWLEDGE THE DISCLAIMER ABOVE!
Done? Are you really sure? ... Okay!
If you don't need your data backed up simply start at Step 10 and ignore the restore parts after that.
Still on OxygenOS (or any other ROM) make sure you've enabled ADB in Developer Options and connected + allowed your PC at least one time, else ADB in TWRP will not work.
If you have Titanium Backup, create a backup of all your apps before starting. Just in case, you never know...
Once done boot into TWRP (see above for an installation guide)
Create a normal TWRP backup
Type in "adb devices" to check if you're allowed to use ADB inside TWRP. If it says "unauthorized" refer to Step 1 again.
Once done open up a CMD on your PC and cd to the directory you want all your backup-files to be (or navigate via Windows Explorer to the folder, hold "Shift", right-click and choose "Open command window here...")
Type in "adb pull /data/media" and wait. Depending on the size this can take a few minutes.
After that's done make sure all your files are here and ADB is not reporting any skipped files.
Checked all your files? Okay!
In TWRP choose "Reboot" and "Bootloader". This will put your phone into Fatboot mode.
Type in "fastboot devices" to check if your phone is recognized. If not go into device manager, find the Google Bootloader drivers and install those.
NOW IS YOUR LAST CHANCE TO MAKE SURE EVERYTHING'S BACKED UP AND THERE!
Next type in "fastboot format userdata" and hit enter. This will completely wipe your device.
Boot back into TWRP by using the volume rocker and the Power Button.
ADB is probably not working now (will only report "unauthorized"), MTP however still works. Copy the TWRP folder we backed up earlier onto the device again.
Once copying finished restore the backup and reboot into recovery again. You're now able to use ADB due to the adbpub.key being present again. (You could've done this earlier but it's easier that way.)
Copy the rest back onto the device with "adb push / /data/media". (I'm not really sure if this command is right, beware!)
Now type "adb shell chown -R media_rw:media_rw /data/media" to fix issues later in the ROM.
You're basically finished now! Simply reboot and wait till it boots up again. If you're getting stuck at a "Wrong PIN" or "Wrong Pattern" screen SEE THIS COMMENT I made in another thread.
Finished!
As said, I'm not sure if I forgot something here or not. However I think I got everything covered
Click to expand...
Click to collapse
Will it wipe my rom too?? Or just internal storage??