Need some help here. Basically im on the tweaked bootstrap( the one where it says bootstrap recovery and reboot recovery when the apk is clicked on) and im currently running the monster rom. Ive been recently interested in installing safestrap but i have no idea how to switch over. Ive been reading alot of different forums and people have been struggling trying to switch and i heard theres data confliction and it can be difficult. Soo im gonna throw some questions at you guys and it might be alot but its good info that i would like to know so... thanks in advance!!
1) Do i have to start from scratch. Meaning wipe data as my first step?
2) is it as simple as deleting the bootstrap and installing safestrap?
3) Can i flash a new rom with safestrap (lets say cm7 for example) over the monster rom even tho monster was installed using the tweaked bootstrap?
4) using safestrap, how does it actually work? Meaning do i still install a new rom the same or similliar way as the tweaked bootstap? ( ex: cwm recovery.. install from sd.. etc.)
5) and the 5th question is. Im sure im missing some important info so.. What am i missing that would be helpful to me?
THANK YOU GUYS
Sent from my droid 3 using Tapatalk
you can just install safestrap but when you flash a rom now it will be flashed to your pre install partition leaving your original system (in this case with monster rom intact, though hash meant for you to keep the blur original system) intact. if you are leaving monster rom though i recommend just backing up with titanium backup and sbf ing back to stock then doing everything from safetsrap from now on
jellydroid13's answer is right on point.
However, I can answer your questions in more detail:
1. Installing Safestrap won't affect your primary system, as jellydroid13 says. It's meant to add a "2nd- system" where you're protected against bad flashes, etc. So there's no worry about /data for the 1st step.
2. Yes. Remove Koush's Bootstrap and Install Safestrap. Then open the app and use the "Install Recovery" button. The next time you reboot, you'll should see a splashscreen right after the Red "M" Logo. While that's being displayed you can enter Safestrap recovery by hitting the [ menu ] button.
3. No. Currently, there is no way for you to affect your MonsterROM /system from Safestrap. Be it flashing or otherwise. Now you can do a bunch of stuff with the data for your MonsterROM installation, via backup / restore, etc. But that's a bit more advanced.
4. Safestrap is basically a modified version of Clockwork Recovery. It has mostly the same menus for making backups, flashing ROMs, etc. If you're familiar with Koush's Clockwork Recovery, then you'll immediately know where everything is in Safestrap. For reference, Safestrap recovery is currently using CWRecovery 5.0.2.7 sources as it's base.
The biggest difference is that anywhere you see "/system" it's talking about a 2nd-system on your phone. SO, when you flash a ROM, you're flashing it to this 2nd area which you can now choose to boot from.
Added to the normal Clockwork Recovery menus is a Safestrap Menu, where you can set which system you want to boot from. When you "toggle" between the systems, Safestrap will stash your current data/cache files and save them and try to load any previously stashed data/cache for the system you're going to.
If you want your data from a previous ROM (or the Non-safe system) you'll need to advanced restore it from a backup file (data partition only). In many cases, data can cause a hung boot. If it does, then battery pull, go back into Safestrap recovery and wipe data/cache. You'll have to use a titanium backup instead once the OS is loaded.
5. Know that the /system backups you make in Safestrap are NOT compatible with Koush's Bootstrap(or the tweaked version of it). Safestrap expects to be loaded from the /preinstall partition. When you try and restore a Safe System to the main /system.. you will get a hung boot at the Red "M" Logo.
Don't do it... Bad.
Just so I understand.....
Hashcode, can you tell me if the following is true?
The actual phone has only one "real" /data partition.
Each time you toggle between systems (which is done via toggleing safe mode on and off), safestrap tars up the contents of /data and copies the tar file to sd/emmc, then DELETES the contents to free up the only real /data partition. Then optionally restores the /data from the previously deactivated system from a previously created tar file.
Right now my phone is running CM4D3 from an activated safesystem. Can I assume the contents of my original /system partition still contains the stock blur rom, and my original stock /data has been DELETED (after having been tarred up and moved to SD/EMMC by the toggle process)?
Questions:
Is the /restore partition a real actual disk partition or is it a subdirectory somewhere?
If something goes terribly wrong, is there a working SBF method that works no matter what has happened?
Following your directions, I do a "wipe data/factory reset". During this process, safestrap says it's formatting sdcard-ext. This obviously scared the **** out of me. Turns out my external sdcard was NOT formatted. What actually happened?
Now that I have a orig system and cm4d3 system in my tars, do I need to wipe data/cache and format system each time I toggle? (Does the unzipping of the saved system info do a format or wipe first)?
Since I did a backup BEFORE activating safe system, this backup does contain my stock /system and stock /data correct? I was using safestrap 1.04.
When you release a new version of cm4d3, do I need to wipe data before installing if I'm running a previous version of cm4d3?
When I installed safestrap, did you resize any of my physical partitions?
So far, I love SafeStrap and CM4D3. What was bugging me about stock (openvpn and tether) is working great! Thanks for all your hard work. For me, the only thing I see so far are the known audio-volume and camera issues. Also, it seems youtube and cam360 both try to scale and position video into a small box rather than go fullscreen (or be where they should be). MoboPlayer in hardware decode mode gets it wrong too, but in software decode mode, works fine.
Hello ryanmcdonald,
These are very insightful questions. I'm probably going to put them up on my FAQ.
Answers:
- Yes, the phone (and Safestrap) currently manage the 1 /data partition. (It's 2Gig in size, I couldn't find a 2nd area to store Safestrap's data in)
- Yes, it's doing a /data swap between toggles from the original system to 2nd-system.
- Your original system still contains the stock blur ROM. And your original /data has been moved to the .tar in {internal storage}/safestra/orig (and deleted from the /data partition)
- The restore files are stored in a subdirectory on your internal storage: safestrap/orig and safestrap/safe
- YES, we have a full fastboot for 5.6.890 (It's somewhere around here in the forums)
- The message is "formatting sd-ext" but yeah it looks scary when you first see it. The sd-ext area is where apps go when you place them on the SD card.
- You do not need to wipe data/cache between toggles now, as long as you want the same ROM and apps when you go back to that system.
- YES, you did exactly what you should have done: make a full backup prior to entering Safe Mode which means you have a fall back of your entire stock system for Safestrap to restore from should anything unforseen happen.
- You will not need to wipe data for new versions of CM4D3 (unless I say so in the release notes, but I can't think of a reason offhand.)
- No, I didn't resize any partitions. SIDE NOTE: I was considering in the future placing the 2nd-system and a new 2nd-data partition on the external storage area -- which would require resizing the vfat partition to be smaller by about 2GIG. But, I'll talk about that if I move towards that direction. I need to confirm that running from the SD card is a stable option through testing.
And thanks!
I had the Droid3Bootstrapper installed on my Droid3 with stock ROM. I uninstalled it and installed Safestrap apk.
I am getting the safestrap spalsh screen on boot up BUT when I hit the menu button I get a blank screen...I have to remove the battery to get it to reboot. Then it reboots to Blur with no problems...
I tried doing an factory reset within blur and still getting the same hang up after pushing the menu button on boot up...
Any suggestions on where I go from here?
Thank you!
johnniekombat said:
I had the Droid3Bootstrapper installed on my Droid3 with stock ROM. I uninstalled it and installed Safestrap apk.
I am getting the safestrap spalsh screen on boot up BUT when I hit the menu button I get a blank screen...I have to remove the battery to get it to reboot. Then it reboots to Blur with no problems...
I tried doing an factory reset within blur and still getting the same hang up after pushing the menu button on boot up...
Any suggestions on where I go from here?
Thank you!
Click to expand...
Click to collapse
I had the same problem but hashcode never answered after asking multiple times . After 3rd time reinstalling safestrap and reinstall recovery my phone bootlooped on droid 3 screen and had to debrick with .890 SBF.
When I tried safestrap then it worked fine. I think there is a bug when removing the old boostrap.
DoubleYouPee said:
I had the same problem but hashcode never answered after asking multiple times . After 3rd time reinstalling safestrap and reinstall recovery my phone bootlooped on droid 3 screen and had to debrick with .890 SBF.
When I tried safestrap then it worked fine. I think there is a bug when removing the old boostrap.
Click to expand...
Click to collapse
I remember he said he had 3 people who had issues like you are describing. i believe uninstalling his bootstrap and then installing safestrap should do it. i thought part of the safestrap install was to remove the other hijacks. when in doubt, SBF, root with 1 click, safestrap and go go go
edit: i recently moved from tweaked bootstrap to safestrap and it worked find for me and its in his instructions per the thread in dev. DoubleYouPee I see where you actually quoted Hashcode saying that but i cant find where he said he knew of a couple people who had problems but i know he said he was looking into it. that couldve been a prior release too, not sure.
johnniekombat said:
I had the Droid3Bootstrapper installed on my Droid3 with stock ROM. I uninstalled it and installed Safestrap apk.
I am getting the safestrap spalsh screen on boot up BUT when I hit the menu button I get a blank screen...I have to remove the battery to get it to reboot. Then it reboots to Blur with no problems...
I tried doing an factory reset within blur and still getting the same hang up after pushing the menu button on boot up...
Any suggestions on where I go from here?
Thank you!
Click to expand...
Click to collapse
Which version of the Droid3Bootstrap were you running? I had made an original one back in Sept. (before Koush picked up support). And that hijack was slightly different than Koush's. It may be that there's an issue with Safestrap cleaning up the hijack files for that original version.. but I'd like to see what you were running.
Well, in my case i was using your updated version of koush bootstrap. I succesfully used it to create 2 nandroids.
Then uninstalled, installed safestrap 1,04, installed recovery, reboot, touch menu, black screen. Retried a couple of times..on the 3rd time it bootlooped.
It works fine now though after SBF.
Hello Hashcode,
I was wondering if the deodexing rom found on the rootzwiki is compatible with safestrap, I had tried it last night but got nothing but a black lit up screen anf had to battery pull after several minutes
RandomTaskMan said:
Hello Hashcode,
I was wondering if the deodexing rom found on the rootzwiki is compatible with safestrap, I had tried it last night but got nothing but a black lit up screen anf had to battery pull after several minutes
Click to expand...
Click to collapse
I'm not sure but that ROM might still have the /system/etc/rootfs files in it which causes Safestrap to bomb out during boots.
You can try deleting that folder from the ROM. Then format your /system and re-flashing. Let me know if that fixes it.
---------- Post added at 04:30 PM ---------- Previous post was at 04:25 PM ----------
DoubleYouPee said:
Well, in my case i was using your updated version of koush bootstrap. I succesfully used it to create 2 nandroids.
Then uninstalled, installed safestrap 1,04, installed recovery, reboot, touch menu, black screen. Retried a couple of times..on the 3rd time it bootlooped.
It works fine now though after SBF.
Click to expand...
Click to collapse
There may be some case I'm missing for the cleanup of the old bootstrap code, and I'm nearly certain you ended up with 2 bootstraps installed. I'll have to take a look and see if I did anything different in my tweaked version vs. his which is available in the Market. Sorry about that.
I'd also like to apologize for missing your posting on the other thread asking for help. At the time I was checking 4 different forums for Safestrap issues, and working on a new release of CM7 for the D3.
Unfortunately, I totally passed over your posting some how and it got lost in the mix.
Hashcode said:
I'd also like to apologize for missing your posting on the other thread asking for help. At the time I was checking 4 different forums for Safestrap issues, and working on a new release of CM7 for the D3.
Unfortunately, I totally passed over your posting some how and it got lost in the mix.
Click to expand...
Click to collapse
Ah I see, well no problem then I also think it didn't properly remove the older boostrap. But I'm sure I followed the right steps. Anyway the debrick was very easy with the 5min debrick and it works great now. Used it with maverom.
Goodluck with safestrap and CM7 etc!
Worked like a charm! Thank you sir!
WORKS like a charm. Thank you for your hard work. Your dedication to the development of these products is greatly appreciated.
Bootloop in safe system of Droid 3 XT862
I have a bootloop problem. (Thanks to Safestrap, it's recoverable ) I activate the "safe system". Format /system. Wipe data (and cache, sd-ext, .android-secure). I also tried anally retentive extra wipes; didn't help. I installed CM4D3-nightly-20111116-1445.zip with gapps-gb-20110828-signed.zip; also tried motoblur-5.7.894.zip with the same result. I tried an extra wipe at this point; didn't help. Reboot (also tried power cycling and a battery pull; didn't help). Motorola logo for 8 secs, Safestrap boot menu for 10 secs, gray screen (lamp on but all pixels black) for 22 secs; at this point the boot animation should start, but the screen goes black (lamp off) for 5 secs and the Motorola logo reappears, starting from the beginning. I've removed and re-installed safestrap-1.06, didn't help. Here are some versions, from About Phone in the unsafe (stock) system:
Model Number: DROID3
System Version: 5.5.959.XT862.Verizon.en.US
Baseband Version: N_03.18.16P
Safestrap version: 1.06In another thread Hashcode asked for this info: ls -l /system/bin/log*
lrwxrwxrwx root shell 2011-06-13 00:10 log -> toolbox
-rwxr-xr-x root shell 13952 2011-06-12 23:57 logcat
-rwxr-xr-x root shell 6975 2011-12-12 10:49 logwrapper (By: Hashcode)
-rwxr-xr-x root root 9760 2011-12-09 21:59 logwrapper.bin
cat /proc/cmdline #list breaks inserted for readability
console=/dev/null rw [email protected] vram=4M omapgpu.vram=0:4M
init=/init ip=off brdrev=P2A omap3_die_id androidboot.bootloader=0x0000
mmcparts=mmcblk17(pds),p15(boot),p16(recovery),p17(cdrom),p18(misc),
p19(cid),p20(kpanic),p21(system),p22(cache),p23(preinstall),
p24(userdata),p25(emstorage)
(busybox) df
Filesystem Size Used Free Blksize
/dev 219M 76K 219M 4096
/mnt/asec 219M 0K 219M 4096
/mnt/obb 219M 0K 219M 4096
/system 320M 312M 8M 1024
/data 1G 472M 1G 4096
/cache 535M 16M 518M 4096
/data/tmp 2M 12K 1M 4096
/pds 3M 1M 2M 1024
/preinstall 464M 181M 283M 1024
/mnt/sdcard-ext 966M 460M 505M 4096
/mnt/sdcard-ext 966M 460M 505M 4096 (listed twice)
/mnt/sdcard 11G 1G 9G 8192
/mnt/secure/asec 11G 1G 9G 8192
/mnt/sdcard/.android_secure: Cross-device link
/mnt/sdcard 11G 1G 9G 8192 (listed twice)
Does anyone have a suggestion what I could try next, or what detail I might have omitted? Normally I would install safestrap-1.07 but I'll wait for responses before trying.
jimcarter said:
I have a bootloop problem. (Thanks to Safestrap, it's recoverable ) I activate the "safe system". Format /system. Wipe data (and cache, sd-ext, .android-secure). I also tried anally retentive extra wipes; didn't help. I installed CM4D3-nightly-20111116-1445.zip with gapps-gb-20110828-signed.zip; also tried motoblur-5.7.894.zip with the same result. I tried an extra wipe at this point; didn't help. Reboot (also tried power cycling and a battery pull; didn't help). Motorola logo for 8 secs, Safestrap boot menu for 10 secs, gray screen (lamp on but all pixels black) for 22 secs; at this point the boot animation should start, but the screen goes black (lamp off) for 5 secs and the Motorola logo reappears, starting from the beginning. I've removed and re-installed safestrap-1.06, didn't help. Here are some versions, from About Phone in the unsafe (stock) system:
Model Number: DROID3
System Version: 5.5.959.XT862.Verizon.en.US
Baseband Version: N_03.18.16P
Safestrap version: 1.06In another thread Hashcode asked for this info: ls -l /system/bin/log*
lrwxrwxrwx root shell 2011-06-13 00:10 log -> toolbox
-rwxr-xr-x root shell 13952 2011-06-12 23:57 logcat
-rwxr-xr-x root shell 6975 2011-12-12 10:49 logwrapper (By: Hashcode)
-rwxr-xr-x root root 9760 2011-12-09 21:59 logwrapper.bin
cat /proc/cmdline #list breaks inserted for readability
console=/dev/null rw [email protected] vram=4M omapgpu.vram=0:4M
init=/init ip=off brdrev=P2A omap3_die_id androidboot.bootloader=0x0000
mmcparts=mmcblk17(pds),p15(boot),p16(recovery),p17(cdrom),p18(misc),
p19(cid),p20(kpanic),p21(system),p22(cache),p23(preinstall),
p24(userdata),p25(emstorage)
(busybox) df
Filesystem Size Used Free Blksize
/dev 219M 76K 219M 4096
/mnt/asec 219M 0K 219M 4096
/mnt/obb 219M 0K 219M 4096
/system 320M 312M 8M 1024
/data 1G 472M 1G 4096
/cache 535M 16M 518M 4096
/data/tmp 2M 12K 1M 4096
/pds 3M 1M 2M 1024
/preinstall 464M 181M 283M 1024
/mnt/sdcard-ext 966M 460M 505M 4096
/mnt/sdcard-ext 966M 460M 505M 4096 (listed twice)
/mnt/sdcard 11G 1G 9G 8192
/mnt/secure/asec 11G 1G 9G 8192
/mnt/sdcard/.android_secure: Cross-device link
/mnt/sdcard 11G 1G 9G 8192 (listed twice)
Does anyone have a suggestion what I could try next, or what detail I might have omitted? Normally I would install safestrap-1.07 but I'll wait for responses before trying.
Click to expand...
Click to collapse
Looks like you never got the OTA for 5.6.890 install that first then try again.
I second the OTA install. In almost all cases, the ROMs are built from the 5.6.890 files (including kernel modules).
With 5.6.890 CM4D3 boots
Thanks, Hashcode and eww245! I de-installed Safestrap Recovery, uninstalled Safestrap entirely, (didn't remove Superuser, Busybox or setUID "su"), updated to system 5.6.890 and reinstalled everything. Now CyanogenMod CM4D3-nightly-20111116-1445.zip installs and boots successfully.
I have an initial report on items that I tested. Almost everything is working, except I have an unusual carrier issue which I haven't dealt with yet, and the cellular connection isn't going to happen until that's resolved one way or the other. Here's the URL: (sorry, I'm new on this site so am not allowed to put links in posts, mail to [email protected] and I'll send it). The only real failure is well known to you: the camera app in the distro doesn't show camera content. But surprisingly, the Barcode Scanner app can use the rear camera to read barcodes. This suggests that the underlying driver or interface library is not whacked; the camera app may be doing something that the others avoid.
Anyway, thank you Hashcode for putting together this system image.
safestrap 3.71
I rooted my AT&T I337 4.2.2 mf3 s4 and installed safestrap It said installed and when I press install recovery it comes up with installation complete but when I reboot the phone it just reboots the phone it does not go into a safe strap menu. I am using 3.71 ver.
One quick note I have been reading and learning a lot from this site and would like to thank all the Devs for thier work. Thanks for any help you can give.
:good:
Related
Hi Everyone,
Sorry for this long-winded post. I've spent hours reading posts here, AndroidCentral and AndroidTablets.net forums, but have not found answers that work for me.
I hope someone can sort out the mess I've created on my rooted 1.1 Nook. Everything worked for 4-5 weeks after I rooted with Decad3nce method until...
A few days ago I decided to try 1.1G kernel. Read many threads about issues with Root Manager/ CWM; 3.0.0.5/3.0.0.6/SD CWM/EMMC CWM/Nook/Nook (old). When I booted into CWM, the version was 3.0.0.5. If I tried flashing CWM through Rom Manager, it said it 'flashed' 3.0.0.6 (tried both "Nook" and "Nook(old)"), but it never changed version of CWM I booted into. I also tried nemiths' "[RECOVERY] Official CWM 3.0.0.6 Update [BROKEN] (new fix soon!)" method to flash 3.0.0.6, but "adb shell busybox" always gave a 'can't get root' type error, so I gave up on that. I ended up using my current CWM to flash 1.1G kernel, and it worked very well. So I ignored the the CWM issues.
Then, I decided to try rookie1's dual-boot method so I could try out Honeycomb. I could never get 'prep_dualboot' zip to flash. It always gave an 'error in zip (status 0)'. His thread showed a few others getting same error, but none of the fixes given worked for me. I re-flashed that zip and ran the 'un-dualboot' zip many times with same result. I then found a "EMMC_CWM_3.0.0.6" zip and flashed that with my CWM. That actually gave me 3.0.0.6 CWM, but flashing dualboot still didn't work. I also again un-dualbooted, wipe cache partition, wipe dalvik cache, fix permissions with same result. So I gave up on that for now.
Then this morning, I found Market updates and downloads don't work anymore. It says 'about to download', then shows the arrows in status bar and nothing else happens. Saw threads regarding this issue and tried clearing Market cache and wiping whatever I could in CWM. Nothing I've found has helped so far.
As a side note in Rom Manager, "Recovery" section now shows 3.0.0.5 (before it wanted to flash 3.0.0.6). Tried flashing 3.0.0.5 there, but it doesn't seem to do anything (same as when it tried to flash 3.0.0.6). I can't understand the logic in Rom Manager. I also have Fascinate phone and RM has issues on that phone also.
I do have CWM backups and Titanium backups of all my stuff, so at worst I can do those. Looking for possibly easier way to get back to 'normal' so Market works and I can download the 'dual boot' zip and be happy again.
Some additional questions I have:
1) I saw in Decad3nce post that he left out 'root' for busybox in an early release, so that may be why mine won't work. I know I had used busybox before, but that may have been on earlier rooted 1.0.1. Is there a way to fix my current busybox without re-rooting?
2) What is the correct CWM I should use for 1.1 and will let me flash dual-boot zip? Also, where can I download it from and how can I replace the one I have?
3) I have saved my SD card to my computer many times and then re-formated it on the Nook. Is there some partition on it that format isn't cleaning that may contain some CWM image(s) causing at least some of my headaches?
Thanks in advance to anyone that can help with these issues. I may have tried a few other 'fixes' that I've since forgotten in the 5 hours last night trying to setup dual boot and quick hour this morning before work trying to sort out Market. Sorry (in advance) if you suggest something and I then say I tried it already. Possibly, just doing all the fixes I've tried previously in the correct sequence is what I need.
I seem to back to where I was before 'bad' versions of CWM skewered Market on me.
1) busybox: found that I just had to 'chmod 755' on my /system/xbin/busybox.
2) Saw that nemith posted a 3.0.0.9 version of CWM. Flashed that using his manual method. Didn't flash his kernel. Rebooted.
3) Tried clearing Market cache and didn't help. Wiped partition cache in CWM (or possibly Dalvik cache, not sure now...was going to do both but rebooted by mistake). After reboot, Market is working again.
Not sure if any of these affected Market, but I also unchecked/checked "Allow Non-Market Apps" and Unchecked/Checked "USB Debugging" and Unchecked "Auto Mount" in Settings.
Can't post in Dev area, so hope some there having same issue as me Market see this.
Now, gonna try the dual-boot again.
Alas, still getting (status 0) error flashing dual boot prep zip. Project for another night.
Sent from my LogicPD Zoom2 using XDA App
I'm getting that same error trying to flash the dual boot prep zip on my rooted Nook. Very frustrating.
jhoward88 said:
I'm getting that same error trying to flash the dual boot prep zip on my rooted Nook. Very frustrating.
Click to expand...
Click to collapse
From error logs it appears the sizes used in re-partitions may be the problem. Over weekend I'm going to try to find values that work. Could be the size differences reflect how NC was originally configured or how many re-roots/updates it has gone through and affect whether the prep works or not. Errors do occur on the 'remove dual boot' ZIP also.
vinal said:
From error logs it appears the sizes used in re-partitions may be the problem. Over weekend I'm going to try to find values that work. Could be the size differences reflect how NC was originally configured or how many re-roots/updates it has gone through and affect whether the prep works or not. Errors do occur on the 'remove dual boot' ZIP also.
Click to expand...
Click to collapse
No luck getting this to work
vinal said:
No luck getting this to work
Click to expand...
Click to collapse
Got a suggestion from Rookie1 to reformat my media partition. Prep now succeeded!
newfs_msdos -F 32 -L media /dev/block/mmcblk0p8
SAFESTRAP v3.05 (2nd-System Bootstrap / Recovery)
PRIOR TO UPGRADING TO V3.x FROM V2.x MOVE THE /sdcard/safestrap FOLDER FROM YOUR /sdcard TO THE /sdcard-ext. THIS OPENS UP VALUABLE INTERNAL EMMC SPACE WHERE ROM SLOTS ARE CREATED. AND KEEPS YOUR V2 BACKUPS SAFE IN CASE YOU WANT TO REVERT TO V2 AND USE THEM TO RESTORE.
** INSERT STANDARD DISCLAIMER: I'm not responsible for any damage you do to your phone using my tools. Always have a fastboot available for disaster recovery. **
Download the "Droid3Safestrap-3.05.apk" Installer Here for "DROID 3"
FOLLOW THESE INSTRUCTIONS: How to Safestrap
[ DOUBLE-CHECK you have the DROID3 VERSION ]
CHANGES:
[10/17] (3.05) Fixed SD card / emmc sharing in recovery (UMS)
[10/17] (3.05) Fixed recovery installation/removal from ROM-slots
[10/14] Updated to v3.04 BETA.
[10/14] Recovery is now based off TWRP 2.2.2.1 (fully featured touch-based recovery)
[10/14] Can create up to 4 Virtual ROM-slots to flash ROMs to and when "Active" ALL TWRP functions affect that ROM-slot (For example: Flashing .zips, Backup and Restore)
[10/14] Nearly instant swapping from ROM to ROM
[10/14] User selectable data partition sizes during ROM slot creation: 1GB, 2GB or 3GB
[10/14] ROM slots are saved on the internal emmc space so that preinstall and webtop partitions are no longer used and shouldn't break OTAs.
[10/14] Charging in recovery
[10/14] Supports "Reboot Recovery" from Android OS
Entry to recovery via Splashscreen on boot-up. The screen stays up for around 8-10 seconds and if you hit the menu button, it takes you to Safestrap Recovery.
SPECIAL THANKS TO:
The entire TWRP team who has built an AMAZING recovery system.
The testers which have helped in past and present versions of Safestrap, knowing that it could mean they brick their devices.
As always, let me know what you think!
A quick note about why I made a MotoBlur 5.6.890 ROM .zip for Safestrap:
1. This is the stock version of our Phone's software. If you want to swap back and forth between CM7 and the standard software, but NOT turn off "Safe System" then you need a stock ROM to use. This is it.
2. Devs can use this ROM as a sort of base for making their skinned ROMs without fear of bootlooping into an SBF. Feel free to tweak and hack away.. nothing you can do to the ROM will force you to fastboot restore. At worst you're looking at a battery pull -> bp-tools -> recovery -> restore.
3. I know some people are checking dev servers for future Moto updates. In theory I will pull the /system images from those updates and put out updated MotoBlur ROMs in the future as a way of test driving upcoming Moto patches w/o fear of leaving yourself stranded on an upgrade path that won't be supported.
So, im just curious, if I wanted to...
I could run say steel droid, then install safestrap, flash cm7,
And by turning safestrap off/on, I could technequally go back and forth
between 2 custom roms? Or do I have to keep the /system partition clean?
Sent from my DROID3 using Tapatalk
Actually the idea for Safestrap is to keep the main system clean.
I'm working with ChevyCam to get a Safestrap version of SteelDroid. Then you can use Safestrap exactly like regular recovery where you would swap from ROM to rom via backup and restore. The advantage being your method of recovery entry and ROM booting is always protected.
Great news !!!
Safestrap works on the XT883 rom too at least w/o the ota update, I'm going to test it on the updated system.
Thanks so much for clarifying, and thanks a million times over for all the great work you've selflessly done for the Droid3 community. I look forward to future CM7 updates.
hey hashcode, just a clarification, we can use safestrap like koush's bootstrap, but we just must turn safe system off right? cause your post makes it seem as if we cant do this
Right now, zips applied with Safestrap are applied to the 2nd-system only. In theory I could make some adjustments to allow for applying zips to the original system as well.. and while I understand the idea of "dual booting" a phone seems fantastic, it's really just an unrecoverable bootloop waiting to happen.
I'd rather that Droid 3 users turn on "Safe System" and never turn it off again (or need to). If all of our ROMs were installable via Safestrap I really feel that we would see alot less "I've bootlooped" postings on the boards.
For the recovery portion of Safestrap: it does NOT backup the original system. Only the 2nd-system, data and cache partitions. (Remember the idea is that you basically root your original system, toss on Safestrap and then enter recovery and toss a .zip onto your 2nd system)
I'm considering changing this in the next version of Safestrap so that backups from Safestrap can be used for full system recovery.
Another question with which to bother you...
When you have the option to do a backup, will you have the ability to choose the destination where the backup is stored as well as the location from where the backup can be restored (either internal or external storage)?
Thank you for your time.
Excellent work, I think this is a fabulous idea and should be the de facto standard for these locked devices. Were you still thinking about using a 2nd data/cache partition as well?
I think it would be pretty sweet if you could loopback mount file system images stored on internal storage for the system/data/cache partitions to implement a proper and safe multiboot system. I don't know how much of a performance hit this would take though.
Anyway, the one suggestion I would make about backing up the original system is to not do it as part of the regular backup/restore. Since system should rarely change, it'd be a waste of time and storage space to back it up every time. Could you either make it a separate option, or perhaps only back it up if the partition's checksum changed?
Besides, if you hose your system and need to restore it, you're probably not going to be using this recovery anyway.
The Solutor said:
Great news !!!
Safestrap works on the XT883 rom too at least w/o the ota update, I'm going to test it on the updated system.
Click to expand...
Click to collapse
I can confirm it works on the updated system too, btw for some odd reasons I'm unable to do a nandroid backup.
I''m investigating what's going on...
So in order to switch to another ROM (from CM7), that is not Safestrap compatible, I just need to toggle safe mode in recovery?
Sent from my DROID3 using XDA App
Yes. But beware of bootloops caused by not wiping your data between ROM switches.
To prevent that from happening you currently need to maintain copies of your data via backup/restore.. This will get addressed in the next version of Safestrap.
I have a version of Steel Droid that is supposed to be safestrap compatible. Im uploading it now. Will test it really quick, to be sure, and if its all good, will post a link!
The Solutor said:
I can confirm it works on the updated system too, btw for some odd reasons I'm unable to do a nandroid backup.
I''m investigating what's going on...
Click to expand...
Click to collapse
Ok I spoke too soon, backup and restore doesn't works on XT883
The backup folder is created correctly on the SDcard, the backup process starts normally with the /system partitons and then the process fails telling that there was an error while backing up the system partition.
Hashcode do you have any idea ?
The only differences in the partitioning between the two systems are the mount options
this is the 862
/dev/block/system on /system type ext3 (ro,noatime,nodiratime,barrier=1,data=ordered)
and this the 883
/dev/block/system on /system type ext3 (rw,relatime,barrier=1,data=ordered)
Do we install the MOTOBLUR Rom via safestrap or can we install it via bootstrap if coming from another Rom?
Sent from my DROID3 using XDA App
I guess it's safe to assume that this is not OK for international Droid3's like the XT860 / ME863?
Just a few short hours later I'm feeling adventurous, but the backup step indicates the MD5 generation failed. Any ideas?
Sent from my DROID3 using XDA App
LaZiODROID said:
I guess it's safe to assume that this is not OK for international Droid3's like the XT860 / ME863?
Click to expand...
Click to collapse
There would probably be radio issues.
Joe.cotto said:
Do we install the MOTOBLUR Rom via safestrap or can we install it via bootstrap if coming from another Rom?
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
This MotoBlur ROM is specifically for Safestrap to run as 2nd-system.
T-Mobile/Samsung have rebranded the Exhibit II 4G, giving us a new kernel, a bump to Android v2.3.6 and performance improvements (they claim) in the process. The phone we all love is now the Samsung Galaxy Exhibit 4G.
This stock ROM (UVLG3) is NOT vulnerable to USSD Dialer Attacks!
Rooting
Currently, zergrush will not root this phone's Android 2.3.6. Three known methods:
Root Stock 2.3.6 w/o a new kernel or ROM
root-stock.zip
Mirror
This zip will install Superuser, su and busybox, leaving you rooted, but otherwise no changes to your phone. ClockworkMod must be installed to flash this. So:
1. Flash ClockworkMod
2. Boot into ClockworkMod and flash root-stock.zip.
Rooted Community ROM (forkable)
t679.uvlg3.odex.01.zip
Mirror
(also see custom ROMs)
Linked above is Samsung's newest release for the Galaxy Exhibit, a stock rooted UVLG3 Gingerbread ROM. Busybox is also included. You must flash it via clockworkmod. Clockworkmod can be flashed with Samsung's stock recovery.
Custom rooted kernel
t679-root-v1.8.zip
Mirror
Kernel sources
The kernel is based on Samsung's kernel source. This kernel is rooted; if you flash it via stock recovery or cwm your ROM will be rooted with Superuser.apk, Busybox and the Galaxy Exhibit cwm-recovery installed. This kernel works with all Samsung Gingerbread releases.
Rooted ROM Installation
CWM Keys:
Home key = enter
Back key = back
VolUp/Dwn = highlight choice
1. Back up your data. The installation will format your data partition. I suggest Titanium Backup, available in the Market.
2. Download & copy the current t679.uv???.deodex.0x.zip to your internal sd card (if you already have a cwm installed you may use your removable card).
3. Install Galaxy Exhibit Custom Recovery . If you're already rooted, you may install from the command line, otherwise you may install from Samsung's Recovery. Samsung's recovery only sees the internal SD, so copy the cwm zip there if you just have stock recovery. Stock recovery sometimes takes more than one try to start.
Easy way to start recovery
* Make sure the cwm zip is on your internal (non-removable) sd.
* Pull the battery from your phone.
* Connect phone to your pc via usb.
* Press & hold Volume-up
* Insert battery
Your phone will boot into recovery. Press the capacitive menu button (left bottom button) when you see the open white box and droid. Choose 'apply update from sdcard' and select the cwm zip file.
4. Start Custom Recovery (cwm): Press & hold Vol-Up, then press & hold Power. Shortly after the plain white Samsung logo appears, release both buttons. Recovery should start after the Galaxy Exhibit logo.
5. Select ROMwipe. This step is required!
6. Highlight install zip from sdcard, then press Home.
7. Highlight 'choose zip from sdcard/external sdcard, depending where you placed the download in step 2.
8. Highlight the rooted rom zip file, then press Home.
After you confirm your choice, installation should take less than three minutes.
Anything you download and install is at your own risk. No guarantees or warranties are given or implied. Your first post-installation boot may be several minutes long.
Rooted Kernel Installation
CWM Keys:
Home key = enter
Back key = back
VolUp/Dwn = highlight choice
1. Back up your data. I suggest Titanium Backup, available in the Market.
2. Download & copy t679-root-v1.8.zip to your internal sd card (if you already have a cwm installed you may use your removable card).
It's recommended to install Clockwork Mod, but you can also flash the kernel from Samsung's stock recovery. Samsung's recovery only sees the internal sd, so copy files there if you don't have cwm.
Stock recovery sometimes takes more than one try to start.
Easy way to start recovery
* Make sure the cwm zip is on your internal (non-removable) sd.
* Pull the battery from your phone.
* Connect phone to your pc via usb.
* Press & hold volume-up
* Insert battery
Your phone will boot into recovery. Press the capacitive menu button (left bottom button) when you see the open white box and droid. Choose 'apply update from sdcard' and select the cwm zip file.
4. Start Custom Recovery (cwm): Press & hold Vol-Up, then press & hold Power. Shortly after the plain white Samsung logo appears, release both buttons. Recovery should start after the Galaxy Exhibit logo.
5. Highlight install zip from sdcard, then press Home.
6. Highlight 'choose zip from sdcard/external sdcard, depending where you placed the download in step 2.
7. Highlight the kernel zip file, then press Home.
After you confirm your choice, installation should take less than a minute.
Anything you download and install is at your own risk. No guarantees or warranties are given or implied.
Please DO NOT PM me with support questions! They will be ignored! Post them in this thread!
Links and useful info
Galaxy Exhibit XDA Wiki
Galaxy Exhibit IRC channel
Galaxy Exhibit Themes
Custom ROMs
All ROMs listed require cwm for installation.
Peach Sunrise
RebelROM
XquiziT
CyanogenMod 9 Beta
Galaxy ExHibition
CM10 Port
AOKP (WIP)
CM7 (WIP)
CM9 Pure Nexus
Stalled, partially working
AOKP
KEMIUI
Help! I keep getting FCs!
Custom kernel for Rebel Rom
This is custom kernel 1.8 packaged specifically for RebelRom, tested on
version 3.0.8. This package includes kernel & modules only.
rrkernel.zip
Mirror 2
Stock 2.3.6 via Odin
uvlg3.odin.zip
Mirror
Adb for Windows
winadb.zip unzip and copy to your c:\Windows directory
Mirror
Flash2Stock
Flash2Stock (flash via cwm) will install stock UVLG3 and Samsung's stock recovery, un-rooting
your phone, removing ClockworkMod and returning your phone to factory condition.
uvlg3.flash2stock.zip
Mirror
SwapSD
SwapSD This simple app allows you to swap internal "usb storage" (aka /sdcard) and your removable sdcard (aka external_sd) so your larger "external sd" is mounted as "/mnt/sdcard/" and the smaller sd internal memory is mounted as "/mnt/sdcard/external_sd". This is done by changing a file called vold.fstab in your phone's /etc folder. The original device vold.fstab file is backed up to /etc/vold.fstab.backup when this app first runs. Your data on /mnt/sdcard and /mnt/sdcard/external_sd is not touched in any way whatsoever.
Dropbear (flash via cwm)
is a software package that provides a Secure Shell-compatible (ssh) server and client. It is designed as a replacement for standard OpenSSH for environments with low memory and processor resources, such as embedded systems. This archive also includes the scp and rsync utilities.
dropbear.zip
Mirror
Bloatware
These apps are safe to delete. You may also freeze them using Titanium backup.
AnalogClock.apk
Browser.apk (Only if you use an alternative browser)
Dlna.apk
DownloadProviderUI.apk
DualClock.apk
DualClock.apk
IQ-tmobile-release-signed-zipaligned-v1.1....
JobManager.apk
KiesAir.apk
MobileBackup-unsigned_v3.3.02.apk
MyFiles.apk(Only if you have an alternative File Browser i.e. Astro File Manager)
SamsungWidget_Program...
Swype.apk
TetheringManager2.apk(Only if you don't use T-Mo's tethering service)
TouchWizCalendar.apk
TouchWizCalculator.apk
TwCalendarAppWidget.apk
VideoPlayer.apk(Only if you have an alternative video player)
VoiceRecorder.apk
WiFi-Calling.apk(If you don't use it)
ZinioSettingsProvider.v2.03.3331.TMobile....
sihome-signed-tmo-android-8.apk
talkback.apk
tmobile_m4m_3_0_15.signed...
vvm-signed.apk
Partition Table
/dev/block/mmcblk0p1 secboot2 partition map
/dev/block/mmcblk0p2 dbl.mbn (boot loader)
/dev/block/mmcblk0p3 osbl.mbn (boot loader)
/dev/block/mmcblk0p4 MBR extended partition table
/dev/block/mmcblk0p5 EMMCBOOT.MBN (boot loader, has odin download mode)
/dev/block/mmcblk0p6 amss.mbn
/dev/block/mmcblk0p7 emmcparam.bin
/dev/block/mmcblk0p8 boot.img (linux kernel)
/dev/block/mmcblk0p9 adsp.mbn (baseband)
/dev/block/mmcblk0p10 rmt
/dev/block/mmcblk0p11 rmt
/dev/block/mmcblk0p12 persist.ext4
/dev/block/mmcblk0p13 recovery.img (linux kernel+initrd for recovery mode)
/dev/block/mmcblk0p14 param
/dev/block/mmcblk0p15 system.ext4
/dev/block/mmcblk0p16 cache.ext4
/dev/block/mmcblk0p17 data.ext4
/dev/block/mmcblk0p18 preload.ext4
/dev/block/mmcblk0p19
/dev/block/mmcblk0p20 all 0's
/dev/block/mmcblk0p21 all 0's
/dev/block/mmcblk0p22 all 0's
/dev/block/mmcblk0p23 all 0's
/dev/block/mmcblk0p24 all 0's
/dev/block/mmcblk0p25 all 0's
/dev/block/mmcblk0p26 all 0's
/dev/block/mmcblk0p27 efs (encrypted fs)
/dev/block/mmcblk0p28 /mnt/sdcard
Credits:VanillaTbone,s0unds,KemikalElite, jocala, Wildchild, bpear96, camcory, Intercepter and others. If your name belongs here or you have info that needs to be added please speak up!
Zergrush
Rooting the original Exhibit II via zergrush: Please read DooMLoRD's Easy Rooting Thread
Please note that this method does not work with Android 2.3.6 on the Galaxy Exhibit.
ClockworkMod
Galaxy Exhibit cwm-based recovery v6.0.1.2
6.0.1.2 has new features, including better support for both external and internal SD cards, faster backups and restores with a new backup format that de-duplicates data in between backups. Exclusive features for Galaxy Exhibit include:
wipe menu with rom wipe
All system wipes under one menu: rom (system/cache/data),cache,dalvik,cache/dalvik,data.
Stack zip files for installation:
Flash cm9 & gapps, etc. Select as many zip files for installation as you choose. Flash them all with one command.
Install system images:
Drop any recognized system image into a folder on your phone and recovery can flash it. You can even drop the entire contents of an odin tar/md5 file in a folder and cwm recovery will flash it all automatically.
All images must conform to Odin naming standards:
adsp.mbn
amss.mbn
boot.img
cache.img.ext4
preload.img.ext4
recovery.img
system.img.ext4
Click to expand...
Click to collapse
This is regular interface, not touch.
cwm.6012.t679.zip
Mirror
To initially install Galaxy Exhibit Custom Recovery you need to:
1. Copy cwm.galaxy.exhibit.zip to your internal SD storage.
2. Boot into stock recovery:
Starting recovery: Press & hold Vol-Up, then press & hold Power. Shortly after the plain white Samsung logo appears, release both buttons.
Or a different method some find easier:
* Pull the battery from your phone.
* Connect phone to your pc via usb.
* Press & hold Volume-up
* Insert battery
Recovery should start after the Galaxy Exhibit/T-Mobile logo.
3. Press the capacitive menu button (left bottom button) when you see the open white box and droid. Choose 'apply update from sdcard' and select the cwm.galaxy.exhibit.zip file.
If you already have cwm installed, to update follow the steps above, booting into your current cwm instead of stock recovery.
Should you need to install ClockworkMod via Odin:
cwm.6012.tar
Mirror
We have needed a new thread for our phone, thanks for making this!
kingdavidd said:
We have needed a new thread for our phone, thanks for making this!
Click to expand...
Click to collapse
You're welcome. Just fyi, I'm no longer going to post in the old dev thread or discussion thread. I also plan to make good use of the <reserved> posts above for Galaxy Exhibit links and information.
I'm committed to this phone for the long haul, so thanks for joining me here. I hope this thread will be used for any general discussion of our Galaxy Exhibits (concerning development as well). I also hope folks will evangelize and point people here rather than carry on in the older abandoned OP threads.
Nice job jocala! Thanks.
Sent from my Calculator with Android.
So the rom is stock exhibit after the update... Other than being rooted and the custom recovery, correct? Much rather flash that then go back to stock then update. Thank you for that.
Sent from my SGH-T679 using xda premium
jocala said:
You're welcome. Just fyi, I'm no longer going to post in the old dev thread or discussion thread. I also plan to make good use of the <reserved> posts above for Galaxy Exhibit links.
I'm committed to this phone for the long haul, so thanks for joining me here. I hope this thread will be used for any discussion of our Galaxy Exhibits.
Click to expand...
Click to collapse
Yea all the old threads OP's abandoned them and the original post had all old info, I am glad you're dedicated to this phone!
SurgeRush said:
So the rom is stock exhibit after the update... Other than being rooted and the custom recovery, correct?
Click to expand...
Click to collapse
Yep, that's it. Purely stock except for root, busybox & recovery.
Cant wait to see what roms come out of this
Sent from my SGH-T679 using XDA
The rebranding works out nicely, if for no other reason than providing a point of demarcation.
Many props to Jocala who is awesome, as we all know. It can't be said too often but we'll try not to overdo it. :thumbup:
Sent via frazzled carrier pigeon -->
Ditto here man. We'd all be screwed & tattooed without his know-how. BTW worth mentioning I had to refreeze all the bloatware again after the update. Noticed how the phone lagged and then checked Titanium Backup. Sure enough all the crap was back. Also re-check settings in programs like Juice Defender and Rom Toolbox. I had to re-enter some of them again as well.
Has anyone managed to update successfully while already being rooted? (Specifically by Zerg Rush method)
I've yet to received the OTA notification and still holding off If i should update using the software. Stock ROM but just rooted. Holding off on "flashing" anything as I've never done it before.
ArtfulDodger said:
Ditto here man. We'd all be screwed & tattooed without his know-how.
Click to expand...
Click to collapse
That's not true at all, but thanks for saying it. Anyone handy with *nix can do what I do, and 95% (or more) of the techniques I use were pioneered by others here on xda.
Hey so i was just looking, and had a few questions, the rom you say is stock and odexed, are all the official roms odexed? Also just curious is the extra file in ur rooted rom, that are not in stock, extra like tweaks or part of odex or are they needed? some are just text and xml so im sure prolly wouldnt hurt, but not exatly the same as stock. Also depending on the answers to the above would you mind looking at the rom i made or maybe releaseing one that has no extras just root and busybox so stock kernel and recovery?
edit: also just noticed theres an extra folder(not in stock) T9DB just wondering what they are for or what they do, looks to be like something for the keyboard?
edit2: i think i answered one of my questions stock is odexed., other questions still wondering about though. It also looks like you might have taken a different approach to rooting the rom, maybe you could look at mine see if its just complete fail or not lol and or maybe pming me, to avoid clutter, on how you did urs.
ive made sooo many edits lol but just wanted to add too, thanx for all the work you have done for us.
cars1189 said:
Hey so i was just looking, and had a few questions, the rom you say is stock and odexed, are all the official roms odexed? Also just curious is the extra file in ur rooted rom, that are not in stock, extra like tweaks or part of odex or are they needed? some are just text and xml so im sure prolly wouldnt hurt, but not exatly the same as stock. Also depending on the answers to the above would you mind looking at the rom i made or maybe releaseing one that has no extras just root and busybox so stock kernel and recovery?
edit: also just noticed theres an extra folder T9DB just wondering what they are for or what they do, looks to be like something for the keyboard?
edit2: i think i answered one of my questions stock is odexed., other questions still wondering about though.
Click to expand...
Click to collapse
The phones I use have always come odexed. I know of no other root methods. I don't have time to beta your rom, but feel free to post a link. I'm sure you'll have volunteers
cool, and no problem, and basically all i did was use the dsixd kitchen and added root(from in the kitchen menu), does that not really root it? does that just change the file permissions? cause when i did that it added the su binary so i assumed it did, but doesn't look like thats what you did, urs has a mkroot folder that im gonna guess is used by the update-script to add the su binary and such.
cars1189 said:
urs has a mkroot folder that im gonna guess is used by the update-script to add the su binary and such.
Click to expand...
Click to collapse
You are correct
Flashed the ROM, all went smooth, but I can't install anything from the Market. Every time I try I get "ERROR "Blah" Could not be downloaded due to an error." Any ideas? Did a full romwipe and dalvik before flashing. The markets not even updating to Play store either.
Hi all,
I have kind of a strange problem with my girlfriends Galaxy Mini S5570.
It was bought with Android 2.2.1 installed, later on I flashed a 2.3.4 Stock ROM with Odin.
What I try to achieve now is using a CustomROM and so far I've tried to flash CM7.2 and emanoN 6, both without luck. Here comes what I did and what happens for both ROMs:
using Odin 4.42 and without SIM or SD installed, I flashed a Stock 2.3.6 (XWKTN) (PASS)
also with Odin I flashed CWM 4 (PASS)
in order to flash the CustomROM of my choice I wiped everything on the Galaxy (data/cache/DalvikCache)
SD card has a 256MB ext4 partition that is mounted later as /sd-ext
using zip installation I flashed CM7.2 stable or later emanoN 6, flashing went fine
at time of reboot it always gets stuck
Everytime I try to boot one of the CustomROMs it shows the initial Model information, then the boot animation that ends with the shiny SAMSUNG text, then screens turns black but backlight still on and every couple of minutes the phone vibrates very short.
The phone can be accessed by adb and responds fine there but screen is always black with dimmed backlight. All relevant volumes are mounted. data partition has some 10,000kB on it which varies up and down by some kB.
Code:
# df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 143016 32 142984 0% /dev
tmpfs 143016 0 143016 0% /mnt/asec
tmpfs 143016 0 143016 0% /mnt/obb
/dev/stl14 25436 4200 21236 17% /cache
/dev/stl13 182672 10668 172004 6% /data
/dev/stl12 211400 166728 44672 79% /system
/dev/block/mmcblk0p2 245692 4236 241456 2% /sd-ext
/dev/block/vold/179:1
1678340 98384 1579956 6% /mnt/sdcard
/dev/block/vold/179:1
1678340 98384 1579956 6% /mnt/secure/asec
Code:
# ls /system
ls /system
T9DB bin etc lib misc xbin
TEAM build.prop fonts lost+found usr
app cameradata framework media wifi
# ls /data
ls /data
aeqcoe.txt dalvik-cache lost+found system
anr data misc system_ordered
app data_ordered property tombstones
app-private dontpanic radio zipalign.db
backup gps sd_ordered zipalign.log
cache local secure
cache_ordered log soundbooster.txt
# ls /sd-ext
ls /sd-ext
lost+found
# ls /mnt/sdcard
ls /mnt/sdcard
Android LOST.DIR
DCIM emanoNROM-v6-signed.zip
When trying emanoN 6 after CM7.2 failed, of course I went through the full procedure again, starting with Stock ROM via Odin. Also I tried using CWM 5 which I zip-installed from within CWM 4. Both ROMs hav the exact same behavior and I have no idea what causes it.
I can always access CWM or Download mode, nothing looks bricked to me. When I flash a Stock ROM again, no matter which, it just boots and runs fine.
Now it's my hope that anybody has seen this before and can point me to where the problem is.
Thanks and very best regards,
Peter
Did u root your your device
Sent from my GT-S5570 using Tapatalk 2
Did u do a full wipe ?
Sent from my GT-S5570 using Tapatalk 2
Hi Messi10,
at which point is rooting required when installing a pre-rooted ROM like CM7.2 or emanoN? Did I miss something here? I didn't apply any separate root solutions in the process.
Hi R.A.G.E,
yes I did. I always wiped data/cache/Dalvik Cache and once even Battery Stats. All content in data that I've posted in my initial post came from first boot of the CustomROM, in this case it was emanoN.
Thanks, Peter
PeBo75 said:
Hi Messi10,
at which point is rooting required when installing a pre-rooted ROM like CM7.2 or emanoN? Did I miss something here? I didn't apply any separate root solutions in the process.
Hi R.A.G.E,
yes I did. I always wiped data/cache/Dalvik Cache and once even Battery Stats. All content in data that I've posted in my initial post came from first boot of the CustomROM, in this case it was emanoN.
Thanks, Peter
Click to expand...
Click to collapse
For me i rooted my device first then i installed CMW i don't have any problem when flash roms
Sent from my GT-S5570 using Tapatalk 2
I always use 2.3.4 as my base and everything is always fine.
Do u have the sim inserted when u boot the phone after flashing a rom?
roofrider said:
I always use 2.3.4 as my base and everything is always fine.
Do u have the sim inserted when u boot the phone after flashing a rom?
Click to expand...
Click to collapse
Hi roofrider,
I used XWKTN and also XWKTH, both are 2.3.6. I did because that is told to be the base ROM for the emanoN. In his TUT parasmi says any 2.3.x would do as base but I tried XWKTH many times as well which is the one he mentions in his changelog.
When booting after flash I tried both, with and without SIM inserted. Makes no difference.
Is there anything I can check via adb to see where the phone gets stuck?
Where can I find the OS log files? Would like to have a look at them.
This it what it shows in dmesg every now and then:
Code:
<3>[ 1547.963619] kgsl kgsl: |kgsl_yamato_waittimestamp| Device hang detected wh
ile waiting for timestamp: 6, last submitted(rb->timestamp): 7, wptr: 87
ya, just do
adb logcat > log.txt
Then later terminate it with ctrl+c
wipe is also needed after flash, so wipe two times before installing and after ibstalling
dheeraj (dhlalit11) said:
wipe is also needed after flash, so wipe two times before installing and after ibstalling
Click to expand...
Click to collapse
not mandatory (i mostly don't do), but if things don't work, sure why not.
roofrider said:
ya, just do
adb logcat > log.txt
Then later terminate it with ctrl+c
Click to expand...
Click to collapse
Thanks, I did that now during a full boot until the first time it vibrated after a couple of minutes.
Condition: no SIM, SD with Ext4fs and VFAT, data/cache/dalvik cache wiped -> first boot of emanoN v6
As soon as the phone booted up I fired adb logcat, even before adb was ready. First response was "- waiting for device -", then it captured as per attachment.
Actually ur phone boots just fine, i see this a lot
Code:
W/SharedBufferStack( 2782): waitForCondition(LockCondition) timed out (identity=1, status=0). CPU may be pegged. trying again.
but then this is just a warning..
So ur display is actually just freezing...
Pulling out the battery and rebooting again gives the same result?
Also the bootanimation does not end with a samsung logo..at least not for CM7.
Also it vibrating once just after the bootanimation(or end stage of bootanimation) is normal.
roofrider said:
Actually ur phone boots just fine, i see this a lot
Code:
W/SharedBufferStack( 2782): waitForCondition(LockCondition) timed out (identity=1, status=0). CPU may be pegged. trying again.
So ur display is actually just freezing...
Pulling out the battery and rebooting again gives the same result?
Also the bootanimation does not end with a samsung logo..at least not for CM7.
Click to expand...
Click to collapse
Pulling battery is the only way to get out of it. At next reboot the same happens again.
This log was from emanoN v6. It checks if there is a custom bootanimation on SD card, if not it shows the Samsung default. You can see this in early stages of booting in the log.
Anyway, I have not confirmed the details via log file but the behavior was exactly the same when CM7.2 was flashed.
The vibration is not at this early stage but after having it some minutes on the table... untouched. In the log a whole lot of things happens again then. Could this be caused by a partly restart of something? Also it vibrates not once but endless times if I just leave it in this state. (Sorry, I still have the 5 minutes time barrier for editing/posting)
Now what could cause this message which appears a thousand times?
@dheeraj: I have wiped so many times: before, after and also before + after flashing. I'm sure it's nothing that can be solved with another wipe.
I'm exactly not sure..but googling this error helps a little...try searching maybe u'll find something.
--sry.
try running logcat longer and check..that should tell a little more.
possible reasons:
-try booting without SD card, it could be cos of a2sd (just a blind guess).
-maybe a certain app that is included is the culprit (again just a guess).
--OT--
U've been a member since 2010 and this is the 1st time ur posting!
I have severe problems when reflashing my Galaxy Tab GT-P1000 (via recovery) to CM 10.1 nightly. Before that, I ran 9.1.0-p1 for quite a while.
What I do:
Reboot to recovery (CWM-based Recovery v6.0.1.2)
wipe data/factory reset
wipe cache partition
install zip from sdcard, e.g. cm-10.1-20130504-EXPERIMENTAL-p1-cdesai.zip
It tells me: "This ROM uses an incompatible partition layout. Your /data will be wiped upon installation. Run this update.zip again to confirm install" and "assert failed: run_program("/tmp/updater.sh") == 0".
I re-run the zip as told.
It reboots to a seemingly updated CWM-based Recovery v6.0.3.2
And now, all kinds of errors occur. First time I tried, flashing seemingly went through (despite showing some ot the CWM error messages mentioned below). After rebooting, I ended up with a weird looking CM10 bootup animation (didn't fit to screen) animating forever with no further (visible) progress. I waited for more than 10 minutes and tried re-booting several times, but it hung there forever. I couldn't connect via adb.
After some tries, the error has changed. Now it won't come to starting CM10 at all, but CWM ends up in a loop saying "Root access is missing. Root device?". If I choose "Yes", it reboots to end up in the same question over and over again.
I tried a lot of nightlies, all showing a varying selection of the errors described above and none leading to a somehow booting CM10.1. I tried some of the official nightlies from get.cm (e.g. cm-10.1-20130515-NIGHTLY-p1.zip), cm-10.1-20130504-EXPERIMENTAL-p1-cdesai.zip from goo.im/devs/cdesai/cm as well as the OpenPDroid taste announced by alroger (cm-10.1-20130514-UNOFFICIAL-p1.zip).
They all seem to use the same new CWM, which gives me collection of error messages, all seemingly connected to partitioning:
Usually, I see a varying number of erros in /cache/recovery, e.g. that it can't mount and/or open /cache/recovery/command, as well as .../log, .../last_log and .../last_install and that it can't open the same files.
Sometimes, I see "E:unknown volume for path []. E: Can't mount"
Sometimes, when trying to wipe, I get informed that make_extf4fs failed on mmcblk0p3
Normally, I'd say that I'm either making a fundamental error in the process or my hardware is somehow badly broken. BUT what puzzles me is that I can go back to CM 9.1 at any time and flash it as often as I want - it always works and CM9 is starting up correctly.
So, I more suspect that my partitioning is somehow setup in a way that CWM v6.0.3.2 or the setup scripts from update.zip can't handle cleanly.
Any suggestions / ideas? Please let me know if there are any logs which could help in narrowing things down! I should be able to operate a Linux shell, so don't hesitate to suggest things I could try manually. (I can certainly access "adb shell" in the recovery - but please note that I didn't manage to connect with adb during the CM10 boot hang, so I can't provide logcat from that state, sorry...)
HTML:
[media=youtube]JmvCpR45LKA[/media]
:thumbup::thumbup:
And restock..
I recommend overcome method..
Search for it..or wait for priyana come here and post "click at my signature"
Then press the thanks button..
When you on stock..
Install the overcome kernal..
Flash cm10..3x
First..to get cwm..
Second..to change partition layout..
Third..to install cm10..
Then flash the gapss..
Reboot..
-----------------------------------
(҂`☐´)︻╦̵̵̿╤── .:System:.
-----------------------------------
No interest in solving the problem in CM10?
mike_disturbed said:
And restock..
I recommend overcome method..
Search for it..or wait for priyana come here and post "click at my signature"
Then press the thanks button..
Click to expand...
Click to collapse
Wow, first of all thx for the rapid answer! And thank you for the hint, I can certainly try that.
However, my initial intention was not only to have the problem solved for my tablet but I tried hard to do a qualified bugreport so that the situation can be correctly handled in the cm10.1 nightlies. I at least assume that an update from a clean CM 9.1 to CM10.1 should be a supported update path, no? As said, I returned to a clean CM 9.1 several times and re-tried the update from there.
So I assumed that the CM10 developers would be interested in my feedback and analyzing the error. Unfortunately, however, I'm not allowed to post that to the right thread yet, so I chose the Q&A channel.
If you don't think the developers are interested in the bug report, just let me know and I'll happily try your suggestion. Otherwise, I'd refrain from it now to not disturb the test case yet...
yoda_la said:
Wow, first of all thx for the rapid answer! And thank you for the hint, I can certainly try that.
However, my initial intention was not only to have the problem solved for my tablet but I tried hard to do a qualified bugreport so that the situation can be correctly handled in the cm10.1 nightlies. I at least assume that an update from a clean CM 9.1 to CM10.1 should be a supported update path, no? As said, I returned to a clean CM 9.1 several times and re-tried the update from there.
So I assumed that the CM10 developers would be interested in my feedback and analyzing the error. Unfortunately, however, I'm not allowed to post that to the right thread yet, so I chose the Q&A channel.
If you don't think the developers are interested in the bug report, just let me know and I'll happily try your suggestion. Otherwise, I'd refrain from it now to not disturb the test case yet...
Click to expand...
Click to collapse
I'm not really sure about this..but cm9, cm9.1 and cm10 , cm10.1..
They have different partition layout..and the rom zip..can change partition layout from gb to cm layout..something about mtd layout or something..lol
I'm not quite sure myself since i still using gb base rom..
Just help in general and q&a..then you can post at dev section..that's the rule..and it apply to everyone..even the dev..
Yeah the dev would definitely interested with that..but..i think that cm10 is been here long enough..and someone would likely brings that up already..but if you still think that it worth a shot..try pm'ing the dev..may take a while for the reply..but I'm sure the dev would love to get some helping hand..or just complete the 10 post..you have done 2 post here already..8 more to go..
-----------------------------------
(҂`☐´)︻╦̵̵̿╤── .:System:.
-----------------------------------
Only cm Rom from last year April onwards use new partition scheme.
If yours was old one, better restock.
Like mike said, check my signature.
Sent from my GT-N7100 using xda app-developers app
mike_disturbed said:
:
:
Flash cm10..3x
First..to get cwm..
Second..to change partition layout..
Third..to install cm10..
Then flash the gapss..
Reboot..
:
:
Click to expand...
Click to collapse
What can I say... that is totally f****** but damn it... it flamin' well works! I can't even guess how you came up with that sequence but THANK YOU! This has been driving me nuts.
Stil no luck...
Ok, tried all that several times, but it still doesn't work. "Restocking" is great as it brought back my /efs partition which has somehow been damaged during my first update tries, so thank you again!
However, my tab still won't boot with CM10, even after "restocking" successfully two times and trying different CM10 nightlies (the current cm-10.1-20130604-NIGHTLY-p1.zip as well as cm-10.1-20130504-EXPERIMENTAL-p1-cdesai.zip as I found specific success reports for that one on the forum). I also tried flashing CM10 3 times in a row as you told.
I always end up with a boot hang and the weird distorted boot animation shown forever. In recovery, I still see errors when accessing the
/cache partition. I've no idea whether this is the root cause of my boot hangs or if this is expected behaviour in CM10 nightlies, but when I try to wipe cache, I get:
Code:
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p3
I also checked with "adb shell" in /proc/partitions and found that there's simply no mmcblk0p3 found by the kernel:
Code:
-> reboot to recovery
$ adb shell
~ # cat /proc/partitions
major minor #blocks name
31 0 7680 mtdblock0
31 1 7680 mtdblock1
31 2 443904 mtdblock2
31 3 22528 mtdblock3
31 4 12800 mtdblock4
31 5 11264 mtdblock5
179 0 15552512 mmcblk0
179 1 13586400 mmcblk0p1
179 2 1966080 mmcblk0p2
179 16 1024 mmcblk0boot1
179 8 1024 mmcblk0boot0
179 24 15339520 mmcblk1
179 25 15335424 mmcblk1p1
dmesg show no suspicious entries during mmc detection, it looks like mmcblk0 simply only has two partitions. So can someone tell whether I should have a mmcblk0p3 partition or if my fstab is somehow broken? Any idea how to narrow this down further?
yoda_la said:
Ok, tried all that several times, but it still doesn't work. "Restocking" is great as it brought back my /efs partition which has somehow been damaged during my first update tries, so thank you again!
Click to expand...
Click to collapse
How are you restocking? I used the Overcome method and files, going back to GB Stock Safe V5. Then I put the Overcome kernel 4.0.0 on, finally doing the CM10.1 x 3 and GApps.