Database Develop

[Resolved] Need help Unbricking and Installing CM7.1

This seems to be the only place I can post.
Basically the title.
Here is some info to avoid some easy questions:
Rooted D3 (obviously)
5.6.890 (I think those were the numbers, I am sure it wasn't 5.7 something)
Using the Droid 3 bootstrapper. NOT safestrap, though in Hashcode's post, he said he updated it to be compatible with boostrap.
Flashed Steel Droid v3 about 2 weeks ago, week later flashed to the Bionic Blue theme.
Ran the "Safe bloat removal script (50+ apps) [UPDATED 9/1/2011]" script.
Ran the script to get my bloat back.
No problems until....
Tried to flash to CM7.1 Alpha using Droid 3 Bootstrapper
Bootloop.
tl;dr: How do I correctly install CM7.1?

you may just need to boot into andriod recovery and clear cache. i dont use bootstrap anymore, but its essentially the same. boot into recovery, format /system (under mounts and storage) then install CM7, factory reset (wipe data/cache) then boot her up. Safestrap is the way to go though

So I tried again, wiping my cache and /system, this time I ended up with a soft brick (Only thing appearing is the Motorola Dual Core screen). Clockwork Recovery doesn't appear on startup anymore.
How do I:
a) Unbrick and
b) Correctly install CM7.1?
Thanks to anyone who responds in advance.
EDIT: I should have read more closely, the order I performed the actions was:
1. Install CM7.1
2. Install Gapps
3. Format cache
4. Format /system.
5. Factory reset

slayer621 said:
So I tried again, wiping my cache and /system, this time I ended up with a soft brick (Only thing appearing is the Motorola Dual Core screen). Clockwork Recovery doesn't appear on startup anymore.
How do I:
a) Unbrick and
b) Correctly install CM7.1?
Thanks to anyone who responds in advance.
EDIT: I should have read more closely, the order I performed the actions was:
1. Install CM7.1
2. Install Gapps
3. Format cache
4. Format /system.
5. Factory reset
Click to expand...
Click to collapse
Ya formatting /system after flashing removes the cm7 rom. Try
Format /system
Install cm7/gapps
Wipe data/cache
xt860, android 2.3.5, Monster rom

Endoroid said:
Ya formatting /system after flashing removes the cm7 rom. Try
Format /system
Install cm7/gapps
Wipe data/cache
xt860, android 2.3.5, Monster rom
Click to expand...
Click to collapse
Thanks for that. Any idea on how to unsoftbrick though?
Also, the link in this thread http://forum.xda-developers.com/showthread.php?t=1255198
is dead.

if you formated /system after installing the rom, then you need to SBF. start the phone with m+pwr, use vol down to reach AP Fastboot, then use vol up to select. download RSD 5.5 and the sbf file. check out the RSD thread in the dev section. and you are on verizon, correct?
edit: dang i see what youre referring to. the 5.6.890 download isnt working. i have it, but i dont know i dont have an account to upload to. And on my 5meg pipe itll still take a few min lol
2ndedit: i cant upload. sorry i dont have a professional account and its 455MB.. check this out it works http://rootzwiki.com/topic/4370-sbf-droid-3-fastboot-files-55959-and-56890/

MrJudylicious said:
if you formated /system after installing the rom, then you need to SBF. start the phone with m+pwr, use vol down to reach AP Fastboot, then use vol up to select. download RSD 5.5 and the sbf file. check out the RSD thread in the dev section. and you are on verizon, correct?
edit: dang i see what youre referring to. the 5.6.890 download isnt working. i have it, but i dont know i dont have an account to upload to. And on my 5meg pipe itll still take a few min lol
Click to expand...
Click to collapse
hxxp://rootzwiki.com/topic/4370-sbf-droid-3-fastboot-files-55959-and-56890/
(replace xx with tt)
I'm following this guide, figured I'd just re root and install cwm again and restore my back up. Will that work?

lol yes youve got it. follow the instructions. also, do not freak out if after you SBF it still does not boot up. Even after the SBF (RSD will show rebooting) and you could bootloop on the animation. if that happens, boot into recovery using M+pwr, select android recovery, when you get the android with the !, use vol up and down and you'll get another menu, and clear cache. then you'll be ok
and also, dont use cwm, use hashcodes safestrap. read up on safestrap, and then you can flash without worrying about bricking

MrJudylicious said:
lol yes youve got it. follow the instructions. also, do not freak out if after you SBF it still does not boot up. Even after the SBF (RSD will show rebooting) and you could bootloop on the animation. if that happens, boot into recovery using M+pwr, select android recovery, when you get the android with the !, use vol up and down and you'll get another menu, and clear cache. then you'll be ok
and also, dont use cwm, use hashcodes safestrap. read up on safestrap, and then you can flash without worrying about bricking
Click to expand...
Click to collapse
Alright thanks man, after I get back up and running I'll be sure to switch to safestrap. Thanks for all the help.

glad i could help. ive been there lol

[Q] safestrap question...

I apologize if this has been covered already, but the search feature finds more noise than signal and I just don't see it.
I have safestrap on my xt860 with cm9 on the safe side of things, and I have a messed up and broken "stock" on the unsafe side. I'm pretty happy with cm9 in general, however there are still some known limitations, so I'm thinking of putting something else on the non safe side. Obviously I'd rather not break cm9 in the process.
Is doing this as simple as switching back to non safe and flashing the zip for what I want to try? Or is it more complicated than that?

You got to put back bootstrap. I think though that safe mode backs up to your internal storage so you should be good.
Sent from my XT862 using XDA

I believe that, when you have switched into non-safe mode, safestrap will not allow you to select the "install zip from sdcard" menu option. I am running safestrap 1.08d tweaked and just tried to do it. It says ".zip install is only available while safe System is enabled."

I don't think rick has gotten non safe flashing functional on any version.
To the op, make a backup of just safe rom, then switch to you non safe, uninstall safestrap recovery, install bootstrap, flash, uninstall bootstrap(you can't do the recovery part, but safestrap install script should clean that out), then reinstall safestrap recovery, and when you switch back to safe you can restore your backup
That's how I do it anyways
Sent from my XT860 using xda premium

Endoroid said:
To the op, make a backup of just safe rom, then switch to you non safe, uninstall safestrap recovery, install bootstrap, flash, uninstall bootstrap(you can't do the recovery part, but safestrap install script should clean that out), then reinstall safestrap recovery, and when you switch back to safe you can restore your backup
Click to expand...
Click to collapse
Not sure what happened there... I backed up my safe rom, then switched to non-safe, uninstalled safestrap, booted in to "stock" installed bootstrap, rebooted recovery, installed my new rom (cm9) and bootlooped... (I had CM9 working beautifully in my safe for ages, wanted it in my non-safe so I could play with other roms in safe)
So much for that plan...
I guess plan B is to figure out how to unbrick an XT860 (I don't think there are any Bell SBFs up, so I guess I go with one from somewhere else...)

I believe a Bell XT860 SBF is here (got it from another thread):
http://sbf.droid-developers.org/umt...M-111109-release-keys-BellMobility-CA.xml.zip

LaZiODROID said:
I believe a Bell XT860 SBF is here (got it from another thread):
http://sbf.droid-developers.org/umt...M-111109-release-keys-BellMobility-CA.xml.zip
Click to expand...
Click to collapse
Yeah, got the SBF loaded. Still have no idea why i couldn't get CM9 in to my non-safe. right now though I seem to have a bigger issue, for some reason my recovery can no longer mount my SD card (though the OS can) I've tried bootstrap, and safestrap, neither can read from my external SD... it's rather odd!

I found with safestrap 1.08f (ricks version) it wouldnt mount mine either.
I started from scratch and installed 1.08d and it works just fine.
As for flashing your non-safe .... i didnt know that was even possible.
Stick with your safe... its the .... safest. Lol
Sent from my XT860

thanks for the tip about 1.08f... maybe that's it, I'll investigate...
LaZiODROID said:
As for flashing your non-safe .... i didnt know that was even possible.
Stick with your safe... its the .... safest. Lol
Click to expand...
Click to collapse
I know sticking to safe is safer, but sometimes I don't want "safe" I want functional. seems a waste to me to have stock loaded on non-safe when I don't plan to ever, under any circumstances, use stock.
I like CM9, I'm quite happy with it as my every day rom. I'd like to put it in non-safe so that I can play with new ones in safe. unfortunately I'm not having much luck with that right now...

I'd like to do that as well (run something fun as my non-safe and try out others in my safe)... let me know if you get that going ;D

ve6rah said:
Not sure what happened there... I backed up my safe rom, then switched to non-safe, uninstalled safestrap, booted in to "stock" installed bootstrap, rebooted recovery, installed my new rom (cm9) and bootlooped... (I had CM9 working beautifully in my safe for ages, wanted it in my non-safe so I could play with other roms in safe)
So much for that plan...
I guess plan B is to figure out how to unbrick an XT860 (I don't think there are any Bell SBFs up, so I guess I go with one from somewhere else...)
Click to expand...
Click to collapse
There is indeed a sbf. Theyre called fastboot now. There's a thread for it
Sent from my XT860 using xda premium

LaZiODROID said:
I'd like to do that as well (run something fun as my non-safe and try out others in my safe)... let me know if you get that going ;D
Click to expand...
Click to collapse
well, others have reported success, but none of them seem to be using CM9 in the non-safe, so maybe it's something specific about that one rom?
I think I'll give it one more try today before giving up and going back to root/cm9 so that I don't end up without a phone for the next 2 weeks until I have time to play again!

seems to me that the trick is to find a bootstrap/recovery that is NOT safestrap, install it, install whatever you want, uninstall it, install safestrap, and go on with life as usual.
Unfortunately I can only find one non-safestrap recovery, and it doesn't seem to work too well. most are dead links now as everyone moved to safestrap.
Anyone have a link to a non-safestrap recovery I can try?

I have uploaded 2 bootstrap versions to DepositFiles. Sometimes when you root, a complete version of BusyBox isn't included, so:
1) Root
2) Install Busybox Installer from the market (it's free)
3) Run BusyBox Installer and install whatever highest version installs successfully. (I found that after using the Bell SBF, the highest version wouldnt install properly, so I just chose the next one in the list)
4) Install whatever bootstrap app, and click its button to do the recovery install.
Droid3 Bootstrap:
Link: http://depositfiles.com/files/5qcaay2e7
(This one's for the Droid3 - I believe that if you're using an XT860, the only way this will boot is if you have USB plugged in!)
Milestone3 Bootstrap
Link: http://depositfiles.com/files/o248gldkm
(For the XT860, this should just boot normally, without USB cable)

Well, the solution continues to elude me.
With Milestone3 Bootstrap I simply can't get cm9 to boot. it flashes ok, but then it just freezes on the motorola logo and won't go any further.
With Droid3 Bootstrap (and USB plugged in) I can boot in to cm9, but USB has to be plugged in EVERY time you boot up (not much of an option for an every day phone)
After getting cm9 working under Droid3 bootstrap though I decided to try to change to safeboot. Unfortunately that way it boots up to "android is upgrading... optimizing applications" followed by "starting applications" and it never gets past there.
I think part of the problem is that I have no way to uninstall the droid3 bootstrap before installing safestrap. anyone have any ideas how to do that properly?

So are you saying you had cm9 running, then installed safestrap, but after doing that, your CM9 wouldnt start up (freeze?). Do you get the safestrap splashscreen at least? I wonder if a wipe would fix up your CM9 (but is that even possible.. and would that wipe out the safestrap install... hmmmm)

LaZiODROID said:
So are you saying you had cm9 running, then installed safestrap, but after doing that, your CM9 wouldnt start up (freeze?). Do you get the safestrap splashscreen at least? I wonder if a wipe would fix up your CM9 (but is that even possible.. and would that wipe out the safestrap install... hmmmm)
Click to expand...
Click to collapse
yes CM9 worked on Droid3 Bootstrap. but not once I installed safestrap (without tweaking anything in safestrap.)
it doesn't so much "freeze" as it decides to "optimize applications" and then just can't seem to get past there. (only solution is a battery pull at that point) I do get the safestrap flashscreen, and can get in to safestrap.
After wiping cache, dalvik cache, and data (factory reset) I reboot, go through the safestrap boot screen, and get to... nothing. blank screen, refuses to boot further.
So something obviously went wrong between when I had Droid3 Bootstrap loaded, and when I installed safestrap. I'm just not sure what other option I have at that stage to make things go more smoothly. theoretically if it works under the Droid3 bootstrap, then it should work as the non-safe for safestrap, but it just doesn't, and I have no idea why.

well, still didn't figure out CM9 in the non-safe... so I've gone a different route.
I now have mavrom in the non-safe, and I'm in the process of installing steeldroid in safe...

Nice. So there was nothing special you had to do after your fresh MavROM install to get safestrap going?
Sent from my XT860

No, went smoothly.
- SBF to stock
- root
- install milestone3 bootloader
- flash mavrom
- remove miletone3 bootloader
- install safestrap
- switch to safe
- install steeldroid

[solved] need help, ICS 208 safeboot backup? fastboot?

hi last night (very late) i was trying out a miui rom i am trying to port, i used the wrong update-script and i seems as though its overwritten my unsafe partition even though i was in safe. i couldnt see the safeboot splash but could still get to it form tools in the bootloader menu, i now have the safeboot menu back but no touch buttons. i have done a restore but i only have 2 backups and this is making me think i haven't backed up when i got on the leak.
so dose any one have a backup they would let me try to see if this is the case, can i fastboot out of this (i dont really understand how fastboot works with this phone as its locked down), or is there anything else i can do to get it back working i would like to keep root if possible.

Are you still able to boot your phone when you try to boot your phone of you can then the best thing for you is that try to install fresh stock room of your phone repeat the whole process again that would be better.
If I or anyone else have helped you in any kind of way please press THANK YOU button.

what type of phone do you have.if you Samsung thing will go fast and smooth to go back to stock Rom
If I or anyone else have helped you in any kind of way please press THANK YOU button.

i have droid 4 this is the droid 4 sub forum, i can boot the safe rom, i used to be able to boot non-safe (had miui on it) but after trying a restore form backup its not booting. i am still new to safe boot i dont fully know how it works.

I think you should be able to use the process for going from one leak to another to to get back to a stock ICS leak system. Follow the instructions in the Droid 4 Utility Updated thread.
Sent from my Droid 4

been thinking that and hoping it to as i think there is root for ICS now, but you are ment to unfreeze apps and uninstall safeboot before you upgrade both of witch i cant do, there is no apps to unfreeze to as the partitions gone.
and safeboot is the only thing that is making this phone not bricked.

Unfreezing and uninstalling recovery shouldn't matter the way I understand it. Fastbooting .219 should wipe that stuff out allowing you to freshly install the ICS leak.
Sent from my Droid 4

Yea, I'd fastboot "back" to 219, which of course WILL brick you, but also allow you to flash the ICS leak, which should get you back to a working phone.
Luckily there are root methods for ICS now, so you don't need to have root on 219 to enjoy root on (ICS) 213 :laugh:

Don't worry man, I've done it a dozen times already.
Just flash the system.img and the preinstall.img .219 fastboot files and erase your data and cache partitions with moto-fastboot:
Code:
moto-fastboot erase userdata
moto-fastboot erase cache
moto-fastboot flash system system.img
moto-fastboot flash preinstall preinstall.img
moto-fastboot flash boot [boot.img for .208/.213 kernel]
(You can skip erasing your /data partition if you want but unless you really need something on there, it's usually best to just start fresh.)
You can find the moto-fastboot executables on xda here with a quick search.
Otherwise you can just do a normal fastboot flash through RSD Lite but the method above is a bit quicker since you only really need to re-flash your /system and /preinstall partitions. If you choose to use RSD Lite, then you have to delete the boot.img file in the .219 package and replace it with the .208/.213 boot.img that you can find here on xda.
Pop the corresponding leaked .208/.213 update .zip file onto your external sdcard and reboot your phone into recovery mode by pressing Vol-Up+Vol-Down+Power and choosing Recovery Menu from the screen with white text on a black background and follow the prompts to install the update from your external card and you're good to go.

thanks i will try this soon.

i have updated to 213 now and it boots in to the animated droid eye but dose nothing not even getting a logcat.
got it working just updated again then wiped catch and data then it booted thanks a lot.

Sweet, glad to hear it. Happy hacking!

[Q safestrap] Recreate a new safe system

I am using safestrap with unsafe=stock905+root and safe=KINETX rom. I want to get my safe system into ICS leak and need to get the safe system back to stock 905 to make that happen.
The first question is: Is there a easy way to get my safe system back to stock905+root? My original backup for safe system has MD5 problem so that won't work. I am imagine something like "purge the current safe system and recreate it from unsafe system".
Second question: If my only way back is RSDLite, do I need to remove/uninstall safestrap before doing that? Or, the question is rather "If I do RSDLite with safe system enabled, will that bring the safe system back to stock without affecting the unsafe system". I am not sure if RSDLite will erase the entire system including safestrap.

maxion said:
I am using safestrap with unsafe=stock905+root and safe=KINETX rom. I want to get my safe system into ICS leak and need to get the safe system back to stock 905 to make that happen.
The first question is: Is there a easy way to get my safe system back to stock905+root? My original backup for safe system has MD5 problem so that won't work. I am imagine something like "purge the current safe system and recreate it from unsafe system".
Second question: If my only way back is RSDLite, do I need to remove/uninstall safestrap before doing that? Or, the question is rather "If I do RSDLite with safe system enabled, will that bring the safe system back to stock without affecting the unsafe system". I am not sure if RSDLite will erase the entire system including safestrap.
Click to expand...
Click to collapse
i would recommend going back to unsafe to RSD Lite, but I don't think it's necessary as it will erase it all anyway.
I am not sure what you mean about trying to get your safe system back to stock+root. Why not just find a Deodexed .905 ROM and install it on your safeside after doing a wipe of KINETX or just using some other ROM on the safe side?

linuxgator said:
i would recommend going back to unsafe to RSD Lite, but I don't think it's necessary as it will erase it all anyway.
I am not sure what you mean about trying to get your safe system back to stock+root. Why not just find a Deodexed .905 ROM and install it on your safeside after doing a wipe of KINETX or just using some other ROM on the safe side?
Click to expand...
Click to collapse
Thanks!
When I say "get back to stock+root", I mean returning the safe system to the status when I enabled safe system for the first time, before I flashed KINETX.
You suggestion should get me exactly what I want. How come I didn't think of that! I guess my thought was stuck on "getting back to before KINETX".

Working CWM Recovery for LOCKED 183.46.15 + Deodex and more

This is a bootstrapped CWM recovery originally made for the LG G3. I am not the developer of this app. I've no idea why it works with our locked RAZR HDS, but it does. I've flashed a few mods perfectly with this.
Install the recovery installer apk. http://goo.gl/Vkwx9Y
Once app is installed, open it and press install recovery and grant it superuser permissions. (Yes obviously you must be rooted)
Press reboot to recovery, and wait a few seconds. Obviously, choose english for the language and flash away.
*Please don't be foolish and try to flash custom ROMs with this. Your boot loader is still locked. This is only meant for flashing mods to the stock ROM, and the state of this is experimental as it is without flashing custom roms. Be careful with this recovery. Again, it wasn't made for our phones. I would advise you to only use the factory reset/wipe options if you're bold. I imagine the G3 and RAZR HDs mount points are different. Do not hold me accountable for what you mess up.
Want a deodexed stock 183.46.15? Flash this --> http://goo.gl/DZjvCk *updated working*
Advanced power menu/battery mod (Deodexed, be sure to flash deodexing zip above first.) --> http://goo.gl/n0hyTm
Beats Audio, Xloud --> http://goo.gl/wl5rP1
^ALL of the above mods are to be flashed WITHOUT wiping data. Just dirty flash them. Also, after flashing, if you are given a prompt about fixing root access, always select NO.
Enjoy!

When i press reboot in to recovery it just restart my phone..

grengo said:
When i press reboot in to recovery it just restart my phone..
Click to expand...
Click to collapse
This is a bootstrap recovery. That means it doesn't replace the stock recovery on the phone. If it's setup and working correctly just a normal reboot should give you a prompt you boot cwm. (I haven't actually tried this but my reply is based off my experience with safestrap twrp in the past.)

thewraith420 said:
This is a bootstrap recovery. That means it doesn't replace the stock recovery on the phone. If it's setup and working correctly just a normal reboot should give you a prompt you boot cwm. (I haven't actually tried this but my reply is based off my experience with safestrap twrp in the past.)
Click to expand...
Click to collapse
You're right... It's bootstrapped. You have to press reboot to recovery from the recovery installer app... I should've clarified that.

If I use this to flash the stock, deodexed 183.46.15, I'm assuming that I'll have to use Hydrogen Peroxide XT926 to root the firmware again?

Guapo613 said:
If I use this to flash the stock, deodexed 183.46.15, I'm assuming that I'll have to use Hydrogen Peroxide XT926 to root the firmware again?
Click to expand...
Click to collapse
I'm sure it's like other custom roms and it's pre-rooted

sd_shadow said:
I'm sure it's like other custom roms and it's pre-rooted
Click to expand...
Click to collapse
Idk dude, it just says "Deodexed 183.46.15 stock"??. I might try it but I dont know if I want to go through the process of rooting again because I've had to use RSDlite before to flash the stock firmware so that Hydrogen Peroxide would work.

Guapo613 said:
Idk dude, it just says "Deodexed 183.46.15 stock"??. I might try it but I dont know if I want to go through the process of rooting again because I've had to use RSDlite before to flash the stock firmware so that Hydrogen Peroxide would work.
Click to expand...
Click to collapse
I've seen dozens of Deodexed stock roms, for a dozens of different devices. I have never seen one the was not pre-rooted, and rarely are they referred to as rooted because it's assumed that if they are installed with a custom recovery that they are pre-rooted.

Ok i've downloaded the deodex_install.zip, and looked at the updater-script (install script).
It deletes all the .odex files from /system/apps and framework and installs deodexed .apks.
Code:
rm -rf /system/app/*.odex
rm -rf /system/framework/*.odex
rm -rf /system/priv-app/*.odex
exit 0
SuperSU does not have a .odex file, and does not affect su binary which is in /system/xbin
also user data should not be affected.

Thanks for the reply and for the info.

Cool deal. Hopefully this will lead to more development for the xt907.

I've read that this should work for the RAZR M. Recovery installer reports that recovery is installed however when I try to use it as described all that happens when I select "reboot recovery" is that the phone reboots normally.
I have checked in my SU app and the recovery installer app is getting SU permission. I have read the whole thread and only one other person has reported this behavior. Am I missing something?
My system details are as follows: System Version 183.46.15 RAZR M rooted with hydrogen peroxide. Titanium Backup and Exposed framework both working correctly.

I tried this on XT926.
CWM was installed (It reboots properly if I wait some time after phone was booted up, before pushing "reboot into Recovery".).
Wipe works.
I flashed deodex and some mods.
Phone works correctly
Thanks

Why Its only restart my xt907 183.46.15 when i click boot into recovery option from recovery installer application

hrrhacker said:
Why Its only restart my xt907 183.46.15 when i click boot into recovery option from recovery installer application
Click to expand...
Click to collapse
I got an answer to this problem in another thread. You may need to factory reset your phone. It worked for me when I had the same problem.
A word of caution though. I made a Titanium backup to internal SD card for easy restore of settings and apps and it was erased by the factory reset along with the apk for this recovery.
Fortunately my full Ti-backup on external SD was OK so I just had to do a selective restore.

Paul.ryan said:
I got an answer to this problem in another thread. You may need to factory reset your phone. It worked for me when I had the same problem.
A word of caution though. I made a Titanium backup to internal SD card for easy restore of settings and apps and it was erased by the factory reset along with the apk for this recovery.
Fortunately my full Ti-backup on external SD was OK so I just had to do a selective restore.
Click to expand...
Click to collapse
I think internal storage is only wiped if you use the settings>backup & reset>factory data reset option
if you wipe in android recovery internal storage should not be wiped
but if you used encryption, storage will be unreadable.

I used the wipe option from recovery. This is the first phone I've ever had that wasn't unlocked with a custom recovery so I have never used the settings factory reset.
This is only a temporary phone till I replace the dead screen on my unlocked RAZR M.

does backup work in this cwm?

It does not work. No matter if wiped as factory or not...
I just erased my phoine and it didn't work. no command once, phone not supported (tr) in other... is not working.

Caliburno said:
It does not work. No matter if wiped as factory or not...
I just erased my phoine and it didn't work. no command once, phone not supported (tr) in other... is not working.
Click to expand...
Click to collapse
Device?
System version?
Rooted?
Superuser popup?
Sent from my XT1028 using Tapatalk