Database Develop

[Q] SafeStrap not flashing roms correctly

So I've followed all the tutorials I could find. I've rooted, installed busybox (to make sure it really existed), installed safestrap (the official one from the blog) and can get into recovery just fine. I made sure I have the right phone version and I've never done any kind of bootstrap stuff on this phone before this.
However, when I switch to safe mode to try out some roms, it simply will not work. I've tried all three versions of Eclipse and one CM9 version, but once supposedly done flashing and told to reboot, it gets a blackscreen for a few seconds and restarts back to the dual-core pre-recovery screen. I've wiped, wiped, super wiped everything just like the various instructions tell me to, but nothing ever changes the blackscreen.
Switching it back to non-safe and rebooting works just fine, but I cannot get any custom safe-mode roms to boot up. Is there something else I should be doing that I missed?

I occasionally have issues with Safestrap when you choose to reboot, so I just power off and then power on - that always works. Initial boots do take some time, though more than a few minutes without animation is probably too much.
And, just to clarify, this is the Safestrap that I use: http://blog.hash-of-codes.com/downloads/safestrap/

But it's not that it takes time, it reboots the phone itself. It's not locking up like I've seen others say and requiring a battery pull. It just refuses to go on, instead more like a boot loop? But nothing appears to be going wrong and I can easily switch back to the base no-problem.
And yeah, that's the same one I'm using. Droid 3 v1.08 exactly from that site.
It's making me sad that I can't get this going
Edit: I went ahead and tried just powering it off, leaving it for a moment, and turning it back on. Still did the reboot thing

are you installing the rom and then wiping data?
if so try wiping data first then install rom then reboot..

ovelayer said:
are you installing the rom and then wiping data?
if so try wiping data first then install rom then reboot..
Click to expand...
Click to collapse
Yeah, tried both ways. Wipe data/factory and cache numerous times, install, nothing. Install then wipe, nothing. Wipe, install, wipe, nothing.
Is there an easy way to know for sure if it is even installing anything at all, like navigating to it using a root explorer?

Are you sure that the zip files you are loading are complete downloads? Generally you would receive error messages when installing if so, but you can try unzipping on your computer to see if they have errors. I always download ROM zips on my computer and transfer over (usually using the Dropbox app, but only because I don't want to bother with attaching, choosing USB storage mode, copying the files, unmounting the drives, choosing charge only.) But, if you are downloading the zips with your phone, try doing so instead with your computer, check the files sizes, and then transfer them over to the phone.
(Also, most/all/many of the CM9 zips require flashing a Google apps zip after flashing the ROM. That shouldn't prevent the phone from starting if you skip this step, but it will prevent you from having the market. Just FYI.)
I'd also try Maverick ROM to see if it has the same problem.
I've been running the stock 906 based ROM from Q9Nap here (the one marked Safestrap system), debloated by Pete Souza's script: http://forum.xda-developers.com/showthread.php?t=1554916

doogald said:
Are you sure that the zip files you are loading are complete downloads? Generally you would receive error messages when installing if so, but you can try unzipping on your computer to see if they have errors. I always download ROM zips on my computer and transfer over (usually using the Dropbox app, but only because I don't want to bother with attaching, choosing USB storage mode, copying the files, unmounting the drives, choosing charge only.) But, if you are downloading the zips with your phone, try doing so instead with your computer, check the files sizes, and then transfer them over to the phone.
(Also, most/all/many of the CM9 zips require flashing a Google apps zip after flashing the ROM. That shouldn't prevent the phone from starting if you skip this step, but it will prevent you from having the market. Just FYI.)
I'd also try Maverick ROM to see if it has the same problem.
I've been running the stock 906 based ROM from Q9Nap here (the one marked Safestrap system), debloated by Pete Souza's script: "no linkies for me"
Click to expand...
Click to collapse
I did as you suggested and tried unzipping the files on my computer (which was where I original downloaded them). They all unzipped fine without any errors, unfortunately. The chances of 4 full files being that way were slim, but I sorta hoped...
I'll try Maverick and the Safestrap stock after I get done downloading them.
Thanks everyone for trying to help.
Edit: Alright, I tried Maverick and it showed a prettier flash log, symlinked, all that, still reset itself after passing the recovery splash. Same with the 906 stock based. This time I also tried installing from internal and external SD just to test that.
I'll ask again, is there a specific folder I can get to just for my peace of mind where I can see where it is supposed to have installed these? Or is it in a area where a normal root explorer can't get to?

shinseitom said:
I did as you suggested and tried unzipping the files on my computer (which was where I original downloaded them). They all unzipped fine without any errors, unfortunately. The chances of 4 full files being that way were slim, but I sorta hoped...
I'll try Maverick and the Safestrap stock after I get done downloading them.
Thanks everyone for trying to help.
Edit: Alright, I tried Maverick and it showed a prettier flash log, symlinked, all that, still reset itself after passing the recovery splash. Same with the 906 stock based. This time I also tried installing from internal and external SD just to test that.
I'll ask again, is there a specific folder I can get to just for my peace of mind where I can see where it is supposed to have installed these? Or is it in a area where a normal root explorer can't get to?
Click to expand...
Click to collapse
wait a sec..
you unzipped them?
the zip files are not ment to be unzipped..
download the zip to your phone
go into safestrap and choose install zip then choose the zip
oh wait...duh you were just checking to see if they worked lol
use root explorer and navigate to system folder open the build.prop and see if there is a mention of the rom your trying to install..ie..version=mavrick or eclipse

I'm not finding any references to other roms anywhere in it. I did a search by eye, then a search for "version", "cm", and "mav" and didn't come up with anything relevant. Is that bad?

There are two other things that you can try, though I am not sure that they will help:
1. From non-safe, stock, run Safestrap and uninstall recovery. Restart to see that it does not intercept before the boot screen, then go back in and reinstall recovery from safestrap. Restart the phone to see if it is working. Then restart to Safestrap and try toggling safe mode and see if your flashes work.
2. One other thing to try (not sure if this will help, but...) is to (prior to flashing a ROM) go into the Mounts menu and format /system. Maybe the old system isn't being cleared out by the ROMs you are trying to flash? Then go install the zip, do a wipe data/factory reset and see if that works.

Just wondering if there is a benefit to Safestrap or Bootstrap and why?
I went with Safestrap... Is it just a style thing or is one better?

Not trying to be a jerk, but I have been scanning this post.
Any chance you have overlooked the step of "Toggle Safe System" from the recovery menu?
At the top of the menu it should say "Safe System is: Enabled"

Droidlyen said:
Just wondering if there is a benefit to Safestrap or Bootstrap and why?
I went with Safestrap... Is it just a style thing or is one better?
Click to expand...
Click to collapse
Safestrap is supposed to allow you to install a rom onto a safe "partition" of sorts, though that's not really what's going on. Anyway, it doesn't touch your stock rom so if something fails (like my flashing attempts) you're not in trouble.
SteveHebe said:
Not trying to be a jerk, but I have been scanning this post.
Any chance you have overlooked the step of "Toggle Safe System" from the recovery menu?
At the top of the menu it should say "Safe System is: Enabled"
Click to expand...
Click to collapse
Nah, I switch it every time. I'm not quite messing up that bad
Anyway, I might have to resort to bootstrap to see if that works. If not, well, I guess I'll be stuck on stock. Nothing so far mentioned in the thread has worked for me. Kinda sucks, since I have an Infuse that loves being flashed with anything I want to put on it without problems, unlike a friend's Infuse. Maybe its phone karma.

Unfortunately the setup wizard has stopped

i installed the NAA kernal and CM9, and all going great, i did however realise that i needed to install gaaps, so i placed on card, rebooted into recovery and installed, all going good, and then after bootup where you tap the android man to continue. this is what i get 'UNFORTUNATELY THE SETUP WIZARD HAS STOPPED'..
I cannot bypass this. ive tried installing two different gapps on it, and both times this..
any help would be appreciated

russy23 said:
i installed the NAA kernal and CM9, and all going great, i did however realise that i needed to install gaaps, so i placed on card, rebooted into recovery and installed, all going good, and then after bootup where you tap the android man to continue. this is what i get 'UNFORTUNATELY THE SETUP WIZARD HAS STOPPED'..
I cannot bypass this. ive tried installing two different gapps on it, and both times this..
any help would be appreciated
Click to expand...
Click to collapse
woow
what do you mean with stop??
maybe you try it again
flash the kernel
backup
factory reset etc
Flash ROM
Flash gaaps
done!

try to clear dalvik cache from cwm -> advanced

Hello guys!
I'm new to the forum, and a total noob when it comes to android. I have a VERY similar problemToday I installed the latest version of CM. Worked fine. I installed gapps. Now when I turn on the device, it just shoes the message and I can't do anything. I wanted to try reflashing a newer version of gapps, but I can't put it on my sd card, because my computer won't detect it anymore...I can't use my phone at all, I am starting to panic :/

cassiopee5 said:
Hello guys!
I'm new to the forum, and a total noob when it comes to android. I have a VERY similar problemToday I installed the latest version of CM. Worked fine. I installed gapps. Now when I turn on the device, it just shoes the message and I can't do anything. I wanted to try reflashing a newer version of gapps, but I can't put it on my sd card, because my computer won't detect it anymore...I can't use my phone at all, I am starting to panic :/
Click to expand...
Click to collapse
Get a card reader
wanna thank xda? here

unzip the rom with winrar you leave two folders that enters the system says and go to the folder that says-app-here clears-app-setup wizard again after that compress the two files that were decompressed - metainf--system-with-winrar-do not forget to put format .zip and you have the zip file to your sd put it, install it normally..
Unfortunately the message has stopped the setup wizard should no longer appear
sorry my bad English

Wizardloop
yeah i got almost the same problem but with few key differences:
i pimped up my android with pimp my rom, the system ui stopped unexpectetly and when i factory reset my phone i got stuck in so-called
wizardloop. so now i want to re-download my stock rom but i dont know any tools that helps me.kdz is for lg only and flashtool is for xperia.
i have prestigio 4055 usb driver.
so can anyone give me some advice? It will be highly appriciated.

maybe reflash kernel and after instal rom, maybe help to you problem.

[Q] xperia z stuck at boot screen

Hello,
I own an Xperia Z C6603 and i was running the latest oficially available firmware before
i m quite new to all the stuff regarding flashing/rooting/unlocking etc
so today i decided to give it a shot.
now my phone is in a state that i cant use it any more.
Basically what i wanted to do is install this [BeanStalk-4.4015] custom rom. Now its stuck on the loadscreen forever.
I started with rooting the device following the description in one of the posts i found here (flashing the previous kernel with flashtool then rooting it and flashing the original latest kernel again) which worked out very well.
After that i unlocked the bootloader following another guide here in forums which went ok without any problems aswell.
As it seemed like it reset all my settings after unlocking the bootloader i reenabled the developer mode to set the USB debugging and security options for unofficial software aswell.
All went fine and i was preparing to install the custom rom so i put the zip file on my sd card entered the recovery mode and flashed the rom zip file.
It seemed all ok and the phone was restarting and its stuck in the boot screen ever since that. I tried to get it back in order by trying out various stuff i could find here on forums.
when i tried to reset the delvik cache initially i did not see any error messages or anything so i assumed that its done correctly also cleared the other caches which were listed. I was getting a bunch of errors but i assumed its because the folders could be empty as it seemed like the phone was completely reset after the bootloader unlock.
I could not get anywhere with the CWM recovery mode so i flashed MOEW kernel through flashtool. The meow kernel was mentioned in the post regarding the custom rom as viable and it included TWRP recovery so i wanted to give it a try.
First exactly the same happened when i tried to boot it normally... Stuck...
So after that i tried to mess around with the TWRP recovery which seemed a bit more complicated than CWM.
First that came to my eye was that i could not enable all the partitions (system was constantly disabled) i managed to enable it after hitting the fix permissions button a bunch of times also i started to get some error messages while trying to reset dalvik cache but none of this changed the main problem at all.
Also i m unable to access the SD card from my computer for some reason even if i enable USB teathering in CWM or TWRP.
any suggestions how to get the phone back to work ?

druvisk said:
Hello,
I own an Xperia Z C6603 and i was running the latest oficially available firmware before
i m quite new to all the stuff regarding flashing/rooting/unlocking etc
so today i decided to give it a shot.
now my phone is in a state that i cant use it any more.
Basically what i wanted to do is install this [BeanStalk-4.4015] custom rom. Now its stuck on the loadscreen forever.
I started with rooting the device following the description in one of the posts i found here (flashing the previous kernel with flashtool then rooting it and flashing the original latest kernel again) which worked out very well.
After that i unlocked the bootloader following another guide here in forums which went ok without any problems aswell.
As it seemed like it reset all my settings after unlocking the bootloader i reenabled the developer mode to set the USB debugging and security options for unofficial software aswell.
All went fine and i was preparing to install the custom rom so i put the zip file on my sd card entered the recovery mode and flashed the rom zip file.
It seemed all ok and the phone was restarting and its stuck in the boot screen ever since that. I tried to get it back in order by trying out various stuff i could find here on forums.
when i tried to reset the delvik cache initially i did not see any error messages or anything so i assumed that its done correctly also cleared the other caches which were listed. I was getting a bunch of errors but i assumed its because the folders could be empty as it seemed like the phone was completely reset after the bootloader unlock.
I could not get anywhere with the CWM recovery mode so i flashed MOEW kernel through flashtool. The meow kernel was mentioned in the post regarding the custom rom as viable and it included TWRP recovery so i wanted to give it a try.
First exactly the same happened when i tried to boot it normally... Stuck...
So after that i tried to mess around with the TWRP recovery which seemed a bit more complicated than CWM.
First that came to my eye was that i could not enable all the partitions (system was constantly disabled) i managed to enable it after hitting the fix permissions button a bunch of times also i started to get some error messages while trying to reset dalvik cache but none of this changed the main problem at all.
Also i m unable to access the SD card from my computer for some reason even if i enable USB teathering in CWM or TWRP.
any suggestions how to get the phone back to work ?
Click to expand...
Click to collapse
hey if you wana go back to stock rom follow this post forum.xda-developers.com/showthread.php?t=2240614
i think u have to fastboot and flash boot.img
try pacman rom which is better and bug free rom

Hi, are you still able to connect to flashtool in flashmode? If so have you tried to flash back to stock rom?
Check this thread out, it contains good stuff.... 3rd video show how to flash stock ....
http://forum.xda-developers.com/showthread.php?t=2275632
Good luck !!

Hello,
thx for your replies i m still able to access all the modes it just does not load up if i dont do anything
after i unlock the bootloader to i need to reroot the phone ?
as it seems right now to me it simply doesnt write anything when i try to flash the rom also some partitions are not available

Hello,
i managed to unbrick the phone using this tutorial http://forum.xda-developers.com/showthread.php?t=2458530
however i tried to redo all the steps following the guide to install the beanstalk rom and noticed that i m getting an error about updater package when i try to execute the installation from TWRP any ideas ?
would you suggest trying another 4.4 based rom ?

Hello again,
ok so i gave up on the beanstalk 4.4 rom and decided to try my luck with pac rom mtayabkk suggested
so now the problem is not as big as it was.
Able to get the rom to run however i m unable to import my contacts/sms/call log using titan backup
The restore seems to work but after that i m getting com.android phone has stopped error everywhere i go on my phone (the contacts/etc are actually restored in this process tho and work fine apart from the errors)
i did restore a bunch of other settings together with the contacts aswell which i found as safe to back up in a guide i found
so can you give me an advice how to properly restore this to the newest pac man rom and avoiding various errors after that ?
ps
i moved all my media to sd card so it does not concern me the only thing i cant seem to be able to move over apart from contacts/sms/call log are the APN settings which is bothering me a bit aswell as i can not receive the configuration messages from carrier but i found them on the internet and i will add them manually
trying to restore the stock backup from PC companion right now to export them again as i lost the backup in process of trying to deal with the error i was getting
would you suggest trying again with titan backup or any other tools ?

Unable to install latest Mokee build properly

Today I tried to install the latest Mokee build on my phone, but I probably messed something up, as all I was left with upon reboot was a stuck boot screen and hardware keys making the phone vibrate when pressed.
I proceeded as follows:
first of all, I wiped cache and dalvik cache from recovery (I am currently using CWM r7). I did NOT wipe data, as I didn't want to lose any app/document/photo/etc. - I suspect this might be a major cause of failure, but I hope not, since I realy really really don't want to lose anything. Since I already had true dualboot enabled, I went as far as flashing it on system2, to avoid messing with my primary partition (MIUI v5 is mounted there). The procedure apparently completed fine, without errors or hiccups, then it asked me something about fixing root access on system2 and I selected to fix it since I need root access for several apps. I then rebooted the phone on system2, and I got stuck on the boot screen: a white MI logo in the middle and 'android' written on the bottom. The only sign of reactiveness the phone showed was some weird pattern of vibrations produced by the pressing of the hardware keys (volume up, down, and power).
Luckily I was able to reboot into system1 without any issue there, but still I can't use Mokee. Do you guys have any idea what I could have done wrong?

isketch93 said:
Today I tried to install the latest Mokee build on my phone, but I probably messed something up, as all I was left with upon reboot was a stuck boot screen and hardware keys making the phone vibrate when pressed.
I proceeded as follows:
first of all, I wiped cache and dalvik cache from recovery (I am currently using CWM r7). I did NOT wipe data, as I didn't want to lose any app/document/photo/etc. - I suspect this might be a major cause of failure, but I hope not, since I realy really really don't want to lose anything. Since I already had true dualboot enabled, I went as far as flashing it on system2, to avoid messing with my primary partition (MIUI v5 is mounted there). The procedure apparently completed fine, without errors or hiccups, then it asked me something about fixing root access on system2 and I selected to fix it since I need root access for several apps. I then rebooted the phone on system2, and I got stuck on the boot screen: a white MI logo in the middle and 'android' written on the bottom. The only sign of reactiveness the phone showed was some weird pattern of vibrations produced by the pressing of the hardware keys (volume up, down, and power).
Luckily I was able to reboot into system1 without any issue there, but still I can't use Mokee. Do you guys have any idea what I could have done wrong?
Click to expand...
Click to collapse
I had 70% similar scenario ,but different error. i could boot into mokkee rom but crashed during initial setup ,below were the steps i used to fix it
Take a nandroid backup of your miui using CWM recovery and apps backup(used EasyBackup ) as well contacts and other important datas for re-installing in mokkee.
saved the mokee zip in internal memory.
went back to CWM and disabled True boot.
formatted System 1 partition.
installed Mokkee zip latest
installed banks GAPPS latest
got perfectly working Mokee ROM in MI3

bluethilak said:
Take a nandroid backup of your miui using CWM recovery and apps backup(used EasyBackup ) as well contacts and other important datas for re-installing in mokkee.
saved the mokee zip in internal memory.
went back to CWM and disabled True boot.
formatted System 1 partition.
installed Mokkee zip latest
installed banks GAPPS latest
Click to expand...
Click to collapse
This step scares me. I am very afraid of data loss, so I'm not eager to try this without in depth explanation
Also, what's the exact purpose of the nandroid backup? Safety measure in case of failure? Or restoration of stuff into the new rom?

A nandroid backup is to be used in case of failure (and as a backup... but you should have backups anyway so data loss isn't the end of the world) - an app backup is so you can reinstall the apps with settings in Mokee.

isketch93 said:
This step scares me. I am very afraid of data loss, so I'm not eager to try this without in depth explanation
Also, what's the exact purpose of the nandroid backup? Safety measure in case of failure? Or restoration of stuff into the new rom?
Click to expand...
Click to collapse
Nandroid backup is nothing but a complete backup of both Rom and Data.It will in a zip format ad gets saved in your internal memory
[Clockworkmod for CWM/TWRP for TWRP recovery]
http://www.makeuseof.com/tag/what-is-a-nandroid-backup-and-how-exactly-does-it-work/
Let me tell you How I handle my backup plans for my device because at least per week i will be changing the ROM.
1) I always save my contacts in Google contacts(So a normal sync will do)
2)I backup all app data and Message data using EasyBackup
:good::good:

I decided to give all this a go, but I encountered a problem right away: I cannot make a nandroid backup due to not having enough free space on my phone's memory.... How can I solve this problem?

bluethilak said:
...got perfectly working Mokee ROM in MI3
Click to expand...
Click to collapse
Little update here!
I managed to install and boot into Mokee (yay!) without any major issue, but I get endlessly repeating "Google Play Services has stopped working" warnings as soon as it boots up. Seraching "banks gapps" I found and flashed the ones from the euroskank website, were they wrong?
EDIT: nevermind, I was able to solve this by myself flashing latest minimal gapps

isketch93 said:
Little update here!
I managed to install and boot into Mokee (yay!) without any major issue, but I get endlessly repeating "Google Play Services has stopped working" warnings as soon as it boots up. Seraching "banks gapps" I found and flashed the ones from the euroskank website, were they wrong?
EDIT: nevermind, I was able to solve this by myself flashing latest minimal gapps
Click to expand...
Click to collapse
Dude banks gapps latest is for 5.1.0 lolipop ,mokkee is still in 5.0.x try other gapps ,PA or MInimal or get old Bank Gapps of correct lolipop version.:good:
---------- Post added at 10:06 AM ---------- Previous post was at 09:59 AM ----------
isketch93 said:
I decided to give all this a go, but I encountered a problem right away: I cannot make a nandroid backup due to not having enough free space on my phone's memory.... How can I solve this problem?
Click to expand...
Click to collapse
Clear some space at least 2gb temporarily in you Internal Memory ,Since you will be backing up your App Data,it definitely requires a lot of space .

[Solved] I think I trashed my phone... wont boot custom or stock ROM.

I recently flashed a new recovery to my phone, which went well, but when I try to flash a new ROM, it wont boot. I've tried Sensational I as well as the stock ROM, same thing happens with both. I have done all the correct steps as far as I can tell. Factory reset, flash ROM, flash Gapps, flash boot.img, reboot. It simply doesn't work. I've tried to download other ROMs but its not possible, they all are no longer on the server at the link presented. I have even reformatted /system and /data as all the available types. ext2/3/4 and fat, same results on each. I have re-flashed everything many times and I'm starting to lose hope. Nothing works at all. I don't get any error messages in TWRP besides "Kernel does not support reading SELinux context", which isn't red text so I think its a warning or info. Sorry for quick rushed post, I had written out a much longer more detailed one, but I lost it all when I tried to preview it. If anyone wants more specific information, just ask. I'll do my best to supply anyone with any information about the problem.
images
Edit: I stumbled across the solution... My phone had S-ON which didn't seem to allow me to flash boot images from recovery. Flashing the boot.img from fastboot on my PC solved the issue.