Related
For these steps to work, ensure that your Milestone currently contains an unprotected recovery image (eg. Brazilian 2.0.1 SPF or the vulnerable recovery SPF for 2.1 Milestones).
Also ensure that you have installed the Android SDK so that you can access your phone with ADB.
These instructions are mostly based on user poseiden's guide at alldroid.org, before the site went down and was cleaned up.
How to make a Nandroid backup
Download the ADBRecovery files from here.
Unzip the archive onto the base of your SD card, so that you have a /recovery folder and an update.zip (NOTE: if you had an earlier update.zip, it will be overwritten with the ADBRecovery update.zip, so back up or rename the original update.zip.)
Reboot your phone into recovery menu:
Turn off phone
Press Camera button, then press Power. Hold them both till you see recovery screen.
Press Volume Up and Camera button at the same time till you see the recovery menu.
Run the update.zip.
Connect via ADB and execute:
If you want everything backed up:
Code:
nandroid-mobile.sh --backup
If you don't want your installed apps + data backed up:
Code:
nandroid-mobile.sh --backup --nodata --nocache --nomisc
How to do a Nandroid restore
Ensure the Nandroid backup content is found under your phone's /sdcard/nandroid/console=ttyS2,115200n8 folder.
Ensure the /recovery folder and ADBRecovery update.zip is at the base of your SD card.
Reboot your phone into recovery menu:
Turn off phone
Press Camera button, then press Power. Hold them both till you see recovery screen.
Press Volume Up and Camera button at the same time till you see the recovery menu.
Run the update.zip.
Connect via ADB and execute:
Code:
nandroid-mobile.sh --restore
Type the name of the backup you want to restore.
Telus 2.0.1 unrooted backup
Here's a clean Telus Milestone 2.0.1 Nandroid backup. I found this one on the web, and then I removed the "su" and "Superuser.apk" files so that it's no longer rooted. Sorry, the original source is uncredited as I forgot where I got it from.
As far as I know, there is no shipped SPF of the 2.0.1 Telus firmware, so this is your only option to go back to stock.
http://www.multiupload.com/TA8V2QPJEO
I used this to restore back to stock Telus Milestone ROM so that I could return the device. The only thing different from the original purchased state was the recovery SPF, but that would be really hard to tell or to find out (just a version number difference).
There's a step missing from the backup process. You need to 'flash' the update.zip from the recovery menu before you can connect over adb.
slightly said:
There's a step missing from the backup process. You need to 'flash' the update.zip from the recovery menu before you can connect over adb.
Click to expand...
Click to collapse
Oops! Fixed now. Thanks!
no need for a computer to do this anymore custome recovery does all that from the phone now .
DAGr8 said:
no need for a computer to do this anymore custome recovery does all that from the phone now .
Click to expand...
Click to collapse
Wicked, thanks for letting us know. Do you have instructions or a link to one?
EDIT: You mean this?
http://www.motorolafans.com/forums/...m-update-recovery-package-updated-v1-12d.html
I see it also does root!
dsixda said:
Here's a clean Telus Milestone 2.0.1 Nandroid backup. I found this one on the web, and then I removed the "su" and "Superuser.apk" files so that it's no longer rooted. Sorry, the original source is uncredited as I forgot where I got it from.
As far as I know, there is no shipped SPF of the 2.0.1 Telus firmware, so this is your only option to go back to stock.
http://www.multiupload.com/TA8V2QPJEO
I used this to restore back to stock Telus Milestone ROM so that I could return the device. The only thing different from the original purchased state was the recovery SPF, but that would be really hard to tell or to find out (just a version number difference).
Click to expand...
Click to collapse
You just saved my Milestone. Thank you x10!
(using xperia x10)
I've made a lot of modifications to my stock rom, and would like to share it.... so is system.img a valid way to share my *own* rom or mod ? (valid as in technically feasible? means ppl can d/l it n flash using recovery n use it?)
my main concerns are... will it boot on someone else's device? (i tried it myself... total wipe + clean stock instal, followed by flashing only my backed up system.img, *didn't flash data.img, only system* it took an eternity to boot first time but it ran)
second concern... system.img doesn't have any personal data right? logs, msgs etc are in data partition i guess??
Sent from my X10i using XDA App
Sent from my X10i using XDA App
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
DUAL BOOT for LG O2X v2
{
"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"
}
This is a guide to get Real Dual boot on O2X, please be careful because this may brick your phone if you don´t know what you are doing. The method is based on a method i found on a Chinese forum but i moded it to have more space on system and data partition and fixed some bugs i found on it.
V2 Changelog:
Increased System partition size, now we have around 370 MB for each ROM, so we don´t need to reduce the size of the ROMs
No need to download ROM for nvflash by Homero, instead i made a NVFlash Partition resizer with a smaller size ( 14 MB)
Better fix for Internal SD corruption
Included Touch CWM Recovery ( important for Internal SD)
Reduced several steps in this guide to make the process shorter and easier
To update to V2 from V1, make a nand backup and backup your internalSD, then do the resizing process and use the new DUAL-ROM... process.
What is this usefull for?
Devs: you can have one ROM configured and ready for use in one partition and a second partition to test your ROMs without touching your daily ROM, so you won´t need to wipe or backup any thing.
Users: you can have a stable ROM, lets say a stock ROM with everything working and configured and you can have a second partition to test ROMs ( for example a new miui v4 or a CM10 beta..) so you won´t need to do backups and wipes.
How Dual boot works?
There are three important file:
Dual-Enabler.zip: this file enables Dual boot by splitting system partition into two.
Dual-ROM-1-to-XX.zip: this file have to be flashed after flashing ROM 1, after flashing it and boot the phone, you will find an app called system changer, by launching this app and selecting change, the phone will reboot and start the ROM 2.
Dual-ROM-2-to-XX.zip: this file have to be flashed after flashing ROM 2, after flashing it and boot the phone, you will find an app called system changer, by launching this app and selecting change, the phone will reboot and start the ROM 1.
Note: It may look long and complex but when you understand the process it is very easy.
Installation
Video tutorial that shows how to install and how it works, please first read the steps below to understand the process
The video is made by Ajsh big thanks to him
Click here if you are not able to watch the video
--> Resizing partitions:
First we need to resize the system partition to have enough space for any ROM and more space in data partition ( only can have 2GB on data due to CWM limitation, so we have 2GB for two ROMs , data partition won´t be split, that is to say both roms will save their data in the same partition ). This will reduce your internal SD available space.
Before continue, it is recommended to have an external SD just in case( the size does not mind).ATTENTION: The resize operation will format all memory, including the Internal SD, so backup your Internal SD. The external SD is not affected.
Download the NVFlash_Partition-resizer.zip - 14.23 MB and extract it with winrar or similar, it includes the APX driver (folder driver).
Download Dual boot O2x - v2.zip - 5.31 MB and unzip it to any folder
Power off and remove the battery of your phone.
While holding volume up and down, connect the USB cable to the device - screen will stay black but Windows will add a new 'APX' device, go to Control panel on your PC->System-> Devices manager you will see a device with yellow exclamation, right click->update driver->search in this system then browse to ..\NVFlash_Partition-resizer\Drivers which is the folder you extracted in step 1, now click next and it will install the device Nvidia boot.....
Now go the the folder NVFlash_Partition-resizer and click on flash.bat and wait until it finish the process.
Now unplug the USB cable, put the battery back.
Power on the phone and by pressing power button + vol down you will enter the recovery
Go to mounts and storage -> mount USB storage, your PC will ask you to format the InternalSD, so select yes.
Let the phone on this state and continue reading....
--> Preparing the ROMs: We need the two roms you want to use, lets call them ROM1 and ROM2 in this guide.
Open the ROM1 with winrar o similar and drag the boot.img from the zip to a folder and rename it to boot1.img , then open Dual-ROM-2-to-XX.zip and add the boot1.img to \system\boot, overwrite the existing one.
Open the ROM2 with winrar o similar and drag the boot.img from the zip to a folder and rename it to boot2.img , then open Dual-ROM-1-to-XX.zip and add the boot2.img to \system\boot, overwrite the existing one.
Now return to your phone which is on recovery mode, go to mount and storage and select mount usb storage.
Now copy ROM1, ROM2, Dual-Enabler.zip, Dual-ROM-1-to-XX.zip, and Dual-ROM-2-to-XX.zip to your SD
Flash Dual-Enabler.zip, the phone will reboot, so when you see black screen, quickly press and hold Power button + vol down to enter recovery again, if the phone doesn't go to recovery, remove the battery, plug it again and enter recovery.
Make a full wipe to avoid boot-loops.
Now flash ROM1 and without rebooting flash Dual-ROM-1-to-XX.zip and reboot.
When the phone completely boots, you will find an app called SystemChanger, launch it and click Switching, i will asks you for root rights, click yes, the phone will reboot so quickly press and hold Power button + vol down to enter recovery, if the phone doesn't go to recovery, remove the battery, plug it again and enter recovery.
Now flash ROM2 and without rebooting flash Dual-ROM-2-to-XX.zip and reboot.
And that is all, if you want to switch to ROM1, as before, run SystemChanger and click Switching.
Note: Only if the internal SD is not available or still corrupt when you finish the process, you can fix it by doing the following: flash any stock Gb ROM and when it completely booted, you will have the option to format the InternalSD.
Tips and advices:
What ROMs can i use?
You can use any combination of ROMs for dual booting ( CM roms, MIUI roms, non wipe stock ROMs...), the only ROMs you should not use are Auto-wipe ROMs because they will delete your data partition and with it ROM1 and ROM2 save files, of course if you are an advanced user, you can open the wipe rom and modify the updater-script to remove the auto wipe lines.What about ROMs size?The system folder of any ROM should not be bigger than 370MB extracted, so if it is bigger you should reduce it by deleting apps you do no use from system/app.I want to change ROM1 or ROM2 with a new ROM, what sould i do?
Lets suppose you want to change ROM2. Open the new ROM with winrar o similar and drag the boot.img from the zip to a folder and rename it to boot2.img , then open Dual-ROM-1-to-XX.zip and add the boot2.img to \system\boot, overwrite the existing one. Then transfer the new ROM and Dual-ROM-1-to-XX.zip to your SD.
Then you have to be on the ROM you don´t want to change, for example if i want to change ROM2, then i have to be in ROM1. The reason of doing this is because we need to delete some files on data partition used by ROM2 because those files may wont be compatible with your new ROM, of course you won´t need to do this if ROM2 and the new ROM are compatible and do not need a wipe to flash new rom.
While we are on ROM1, we need an explorer with root rights like root explorer or solid explorer.then we go to /data/ and delete these folders: dalvik-cache-2, app-2, data-2, lgdrm-2, misc-2 and system-2 , basically are the folder with a -2 (or -1 if you are changing ROM1) in the name. This is equivalent to a full wipe because we delete all folder where ROM2 saves its data. Alternative Only for advanced users: There is a easier way, you can be on ROM2, enter recovery (mount DATA) and with a PC software like Android commander you can delete those folders or via ADB shell.
Now we run Systemchanger and click Switching, the phone will reboot so quickly press and hold Power button + vol down to enter recovery and flash the new ROM and without rebooting flash Dual-ROM-2-to-XX.zip and reboot, if the phone doesn't go to recovery, remove the battery, plug it again and enter recovery.
When the phone boots it is recommended to switch to ROM1 and flash Dual-ROM-1-to-XX.zip to have the kernel of the new ROM so when we switch again to ROM2(the new ROM), it will boot correctly.
I want to update ROM1 or ROM2, what should i do?
You have to be on the ROM you want to update
Enter Recovery
Flash the ROM update and flash Dual-ROM-1-to-XX.zip if you are updating ROM1 or flash Dual-ROM-2-to-XX.zip if you are updating ROM2.
What about backups?
If you do a nand backup, it will backup the system partition of the ROM you are in( ROM1 or ROM2) and all data partion with the data of both ROMs, so if you restore that backup, you will be able to boot correctly the ROM you were on when you made the backup, to boot the other ROM, you have to run Systemchanger and swithc to the other ROM, but quicly enter to recovery and flash again the other rom and its Dual-ROM-x-to-XX.zip.
huy_gm said:
Can i use this without losing my current running rom?.
Click to expand...
Click to collapse
Easy, first make a nand backup of your current ROM, then follow my guide to get dual boot, when finished, just restore that nand backup while on ROM1 for example. of course make sure your system partion size is smaller than 370MB.
Whats the way to rollback to one ROM system and original partition sizes?
Flashing a nvflash rom or any stock rom via smartflasher will do the trick .
Some notes:
As i said before, both roms share the 2GB of space, so you should use that space smartly, for example do no install a lot of apps on the test ROM, instead use is your main rom to install all the apps you need, for big apps, move them to SD.
As i said, you have to take the kernel (boot.img) from ROMx to put it in Dual-Rom-xxx, this is true if you are going to use the default kernel that comes with ROMx, if you flashed another kernel independent from ROMx, you should take the boot.img from that kernel and put it on Dual-Rom-xxx. if there is no boot.img on kernel.zip installer, you can use terminal emulator from play store or adb shell to extract a boot.img from the rom with the independent kernel already installed by this code:
su
dd if=/dev/block/mmcblk0p5 of=/sdcard/boot.img
Click to expand...
Click to collapse
Example: If the kernel is in boot.img format, simply put it on dual-rom as i say on 1st post, if not, then first install cm7 +kernel+gapps and when it boots use terminal emulator to extract boot.img from your phone.
For better ROM changing: i have several Dual-ROM-x-to-XX.zip, for example: Dual-ROM-1-to-CM7.zip, Dual-ROM-2-to-CM9.zip Dual-ROM-1-to-stock.zip.... so that way i change ROMs easily. Of course this is valid if you always use ROM default kernels, if not, you should put the right bootX.img into the right Dual-ROM-x-to-XX.zip
Thanks to:
The creator of the scripts and System changer ChinaGB.
Homero for its nvflash ROM.
Modaco for Nvflash method
Owain for the partition resize guide
Ajsh for the great video tutorial
If you like my work, please hit the Thanks button.
Wow, sounds amazing, thanks for this. I will try it later and report back !
One thing:
8. Now flash ROM2 and without rebooting flash Dual-ROM-1-to-XX.zip and reboot.
Click to expand...
Click to collapse
Am I wrong or should it be Dual-ROM-2-to-XX.zip ?
d1dd1 said:
Wow, sounds amazing, thanks for this. I will try it later and report back !
One thing:
Am I wrong or should it be Dual-ROM-2-to-XX.zip ?
Click to expand...
Click to collapse
yes, corrected it.
Wow,been waiting for such options D ,greatly appreciated
Just curious,have you seen multiboot tread on motorola defy? Its made so you can install several roms on sd card.....if not you should check it out,new challenge
SuperSkill said:
Wow,been waiting for such options D ,greatly appreciated
Just curious,have you seen multiboot tread on motorola defy? Its made so you can install several roms on sd card.....if not you should check it out,new challenge
Click to expand...
Click to collapse
yes i saw it, but i don´t like that method because the phone get very slow and laggy due to sdcard speed, my method is better because it uses the nand memory on both roms. Also i think we do not need more than two roms really.
The bad thing is it uses system changer not some boot loader screen menu, so if one OS gets corrupt, you'll be stuck?
Ferrum Master said:
The bad thing is it uses system changer not some boot loader screen menu, so if one OS gets corrupt, you'll be stuck?
Click to expand...
Click to collapse
no, if one OS gets corrupt, enter to recovery and flash it again or flash other ROM, and to delete the corrupted OS data files, you can use Android commander pc program to delete them or you can also use aroma file manager which is a file explorer that can be started from recovery.
bihariel said:
no, if one OS gets corrupt, enter to recovery and flash it again or flash other ROM, and to delete the corrupted OS data files, you can use Android commander pc program to delete them or you can also use aroma file manager which is a file explorer that can be started from recovery.
Click to expand...
Click to collapse
By meaning stuck... I meant the fact you'll have to do some recovery stuff in order to boot at least one OS and fast, as it always needed.
But for playing around OK, I got the Idea... not as smooth as in my N9 but still nice
Please redownload this file Dual boot O2x.zip again, the other one has a bug.
I waited very long for Dual Boot and now I can have ICS and CM7 on my Device.
thanks mate
It sounds like Christmas, Eastern and Birthday in my ears *___*
If that works, it will be on the same level as a 100% working ICS/JB ROM !!
What doesn't work? If there isn't problem it's fantastic! Thank you
Inviato dal mio Optimus 2X con Tapatalk 2
Thanks so much for this. I wonder if i can use this without losing my current running rom?
Is there a way to modify nandroid backup for it to be compatiple with new boot method?
huy_gm said:
Can i use this without losing my current runningrom? What if we modify nand backup for it to compatiple with new boot method.
Click to expand...
Click to collapse
esay, first make a nand backup of your current ROM, then follow my guide to get dual boot, when finished, just restore that nand backup while on ROM1 for example. of course make sure your system partion size is smaller than 310MB.
i have a problem.
After replace the cfg file and run the batch the phone is stuck in the epgrade software screen.
If i pull the battery and press the power + volume down button the phone doesn't boot.
If i don't replce the cfg file everything is fine and the phone boots normally.
I've redownloaded the zip and the problem persist.
Cice96 said:
i have a problem.
After replace the cfg file and run the batch the phone is stuck in the epgrade software screen.
If i pull the battery and press the power + volume down button the phone doesn't boot.
If i don't replce the cfg file everything is fine and the phone boots normally.
I've redownloaded the zip and the problem persist.
Click to expand...
Click to collapse
that is strange, i repeated the process again and it boots. just unplug the cable, put back the battery and power on + vol down.
anyone else has the same problem?
Cice96 said:
i have a problem.
After replace the cfg file and run the batch the phone is stuck in the epgrade software screen.
If i pull the battery and press the power + volume down button the phone doesn't boot.
If i don't replce the cfg file everything is fine and the phone boots normally.
I've redownloaded the zip and the problem persist.
Click to expand...
Click to collapse
i detected the problem.sorry i reupload again.
I also detected it. just edit the cfg file.
Cice96 said:
I also detected it. just edit the cfg file.
Click to expand...
Click to collapse
ok, smart boy, heheh
Now it works
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?
After seeing another user on here (hopefully soft) brick their Maven 3 from trying to root using ZPST and the rooting guide here, as well as myself, I want to warn anyone else to not attempt to use any other tool other than the QFIL application from the Qualcomm QPST (the v2.7.480 should be good) software package.
QFIL can backup and flash any partition on the device, negating the need to use any other tool, including ZPST. I am not sure if it is enabled by default, but on the (new) Maven 3 board I have, the devinfo partition did already have the necessary bits for the bootloader to be unlocked (guide for that can be found here). I was able to successfully backup the boot partition (boot.img), put it on my device from my computer, then build a modified Magisk boot.img from the Magisk Manager app. With that, I flashed it as a boot.img partition and it works fine. I can write a full tutorial if there is interest.
But the most important information you should take from this thread is to backup all of your partitions before doing anything to the phone using QFIL. Once you do this, I don't think you can hard-brick your phone, as, if necessary, you can short two solder joints by the SD card slot (message me if you need a picture) to automatically put your device in a functional EDL mode in order to flash your original partition(s) back to the device.
do you have backup files for the phone, I can get into edl mode only. My backup file will not restore the phone
xecutionkrk said:
do you have backup files for the phone, I can get into edl mode only. My backup file will not restore the phone
Click to expand...
Click to collapse
What partitions do you need? boot? I know there seems to be different bootloader versions and stuff
000Nick said:
After seeing another user on here (hopefully soft) brick their Maven 3 from trying to root using ZPST and the rooting guide here, as well as myself, I want to warn anyone else to not attempt to use any other tool other than the QFIL application from the Qualcomm QPST (the v2.7.480 should be good) software package.
QFIL can backup and flash any partition on the device, negating the need to use any other tool, including ZPST. I am not sure if it is enabled by default, but on the (new) Maven 3 board I have, the devinfo partition did already have the necessary bits for the bootloader to be unlocked (guide for that can be found here). I was able to successfully backup the boot partition (boot.img), put it on my device from my computer, then build a modified Magisk boot.img from the Magisk Manager app. With that, I flashed it as a boot.img partition and it works fine. I can write a full tutorial if there is interest.
But the most important information you should take from this thread is to backup all of your partitions before doing anything to the phone using QFIL. Once you do this, I don't think you can hard-brick your phone, as, if necessary, you can short two solder joints by the SD card slot (message me if you need a picture) to automatically put your device in a functional EDL mode in order to flash your original partition(s) back to the device.
Click to expand...
Click to collapse
can you please writ a tutorial on how you did it and also which 2 points to solder in case its needed?