HI
I will cut the long story short - I can only boot through BP TOOLS
Was trying to get Lineage OS flashed - But couldnt
Now after th initial 'M' logo, the phone doesn't go beyond a blank screen - UPDATE - I now have dead Android with the chest open and a red exclamation on it.
i have no clue what is going on.
Can someone please help//
I did a RSD Lite and the screen never went beyond the initial 'm' logo.
EDIT: 1
Very strange behavior -
I RSD Lite the phone again
Then installed BMM (after rooting it of course)
I flashed a couple of ROMs - BUT bootloop
HOWEVER, When I flashed Paranoid Android ROM - 4.4.2 - IT WORKED!
What the hell is going on?
X0LARIUM said:
HI
I will cut the long story short - I can only boot through BP TOOLS
Was trying to get Lineage OS flashed - But couldnt
Now after th initial 'M' logo, the phone doesn't go beyond a blank screen - UPDATE - I now have dead Android with the chest open and a red exclamation on it.
i have no clue what is going on.
Can someone please help//
I did a RSD Lite and the screen never went beyond the initial 'm' logo.
EDIT: 1
Very strange behavior -
I RSD Lite the phone again
Then installed BMM (after rooting it of course)
I flashed a couple of ROMs - BUT bootloop
HOWEVER, When I flashed Paranoid Android ROM - 4.4.2 - IT WORKED!
What the hell is going on?
Click to expand...
Click to collapse
With lollipop and above you need to use safe strap 3.75. reflash with rsd then root then install safe strap. There are two versions of safetrap. One version is by stargo and the other is safe strap for unused partitions. Good luck. If you run into problems just hit me up.
OGdroidster said:
With lollipop and above you need to use safe strap 3.75. reflash with rsd then root then install safe strap. There are two versions of safetrap. One version is by stargo and the other is safe strap for unused partitions. Good luck. If you run into problems just hit me up.
Click to expand...
Click to collapse
Hi. Thanks for your reply. I cant seem to get through SafeStrap no matter what I do.
I can only do the following:
1. RSD Lite - But CANT boot normally. ONLY BP TOOLS
2. Install BMM through BP TOOLS boot
3. Install and successfully boot ONLY 1 ROM - PA for Razr (All other ROMs give me a bootloop)
What I can't do -
1. Boot Normally (without BP TOOLS)
2. flash any ROM - I tried Lineage 14.1 , MIUI, Stock Razr ROM
3. Install SafeStrap - Keep saying Safestrap is deactivated etc
Update 1:
Following the instructions here:
http://www.droidforums.net/threads/how-do-i-install-safestrap-please-help.240178/
I did exactly that and there is progress
I removed BMM the right way, and I installed Safestrap successfully
I even created a slot1
I flashed Lineage OS 14.1 on it...
However, as always, it is stuck on the Lineage OS boot screen - the small circle going on the curved line from right to left
I can never get past this for some weird reason.
Is my download corrupted?
Update 2:
IT WORKED! I am IN!
Lineage OS 14.1!
ITS AWESOME!
Glad to hear you got it working
---------- Post added at 04:26 PM ---------- Previous post was at 04:25 PM ----------
X0LARIUM said:
Hi. Thanks for your reply. I cant seem to get through SafeStrap no matter what I do.
I can only do the following:
1. RSD Lite - But CANT boot normally. ONLY BP TOOLS
2. Install BMM through BP TOOLS boot
3. Install and successfully boot ONLY 1 ROM - PA for Razr (All other ROMs give me a bootloop)
What I can't do -
1. Boot Normally (without BP TOOLS)
2. flash any ROM - I tried Lineage 14.1 , MIUI, Stock Razr ROM
3. Install SafeStrap - Keep saying Safestrap is deactivated etc
Update 1:
Following the instructions here:
http://www.droidforums.net/threads/how-do-i-install-safestrap-please-help.240178/
I did exactly that and there is progress
I removed BMM the right way, and I installed Safestrap successfully
I even created a slot1
I flashed Lineage OS 14.1 on it...
However, as always, it is stuck on the Lineage OS boot screen - the small circle going on the curved line from right to left
I can never get past this for some weird reason.
Is my download corrupted?
Update 2:
IT WORKED! I am IN!
Lineage OS 14.1!
ITS AWESOME!
Click to expand...
Click to collapse
Glad to hear you got it it working
BUT oh well..life is NEVER as straight as that..I should have realised that...
Now, I can't flash any other OS on the Stock Slot. I am stuck with PA. I tried 4 different ROMs. All flash in less than a second and say 'Successful'. When I boot into Stock, its still PA.
Is it because they are BMM compatible and not SS?
X0LARIUM said:
BUT oh well..life is NEVER as straight as that..I should have realised that...
Now, I can't flash any other OS on the Stock Slot. I am stuck with PA. I tried 4 different ROMs. All flash in less than a second and say 'Successful'. When I boot into Stock, its still PA.
Is it because they are BMM compatible and not SS?
Click to expand...
Click to collapse
Are they old ROMs made to flash with bmm?
OGdroidster said:
Are they old ROMs made to flash with bmm?
Click to expand...
Click to collapse
Oh yes...I think so!
Where do I get a Stock Razr ROM - SAFESTRAP version?
X0LARIUM said:
Oh yes...I think so!
Where do I get a Stock Razr ROM - SAFESTRAP version?
Click to expand...
Click to collapse
Just use one of the virtual slots 1, 2, or 3. I use 1.
You have lineage 13 an 14. You also have other ROMs you can use 5.1 and up. You have mokee. You Also have unofficial resurrection remix by transil. Just take a pic and use one or use them all fiddle around some and see which one you like its up to you.
Related
Hello,
Device: Razr XT910 GSM
Stock soft: Android 4.0.4
It was my first attempt to install a custom rom on my Razr.
I followed instructions from wiki.cyanogenmod.org/w/Install_CM_for_umts_spyder
I rooted razr, installed safestrap and flashed it with stable version of CyanogenMOD
And here the problem occurs: boot loop
I tried to install other versions of CM - RC5, nightly; it did not change anything - boot loop
Now I have no idea what to do.
Please help
Try doing a full wipe and clear caches !!
Please hit the thanks :thumbup: if i ever helped ya !!
jacek607 said:
Hello,
Device: Razr XT910 GSM
Stock soft: Android 4.0.4
It was my first attempt to install a custom rom on my Razr.
I followed instructions from wiki.cyanogenmod.org/w/Install_CM_for_umts_spyder
I rooted razr, installed safestrap and flashed it with stable version of CyanogenMOD
And here the problem occurs: boot loop
I tried to install other versions of CM - RC5, nightly; it did not change anything - boot loop
Now I have no idea what to do.
Please help
Click to expand...
Click to collapse
Delete and recreate your rom-slot. And try againI assume you're installing in on slot1
Sent from my XT912 using Tapatalk 2
neo.ank said:
Delete and recreate your rom-slot. And try againI assume you're installing in on slot1
Sent from my XT912 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I tried to delete and create again slot. Yes, I'm using slot1.
Here's (step by step) how I'm trying to install CM:
1. I'm rooting phone with Razrs Edge Windows
2 Innstaling Safestrap 3.11 app. When running it it has superuser access
3 Clickin in "Install recovery" -> "Recovery state: Installed"
4 Reboot phone
5 Safestrap splashscreen appears -> hitting menu button
6 I'm in safestrap menu
7 "Boot options" -> "Rom-Slot-1" -> I'm choosing 2GB of data partition size -> "Create Rom Slot"
8 I'm waiting a few minutes
9 Everything looks fine
10 Going to main menu -> "Wipe"
"Cache"
"Dalvik Cache"
"Factory reset"
11 Going to main menu -> "Install"
12 Looking for zip with rom (I tried CM stable, RC5 and latest nightly)
13 Flashing rom. Everything looks fine
14 Going to main menu -> "Wipe"
"Cache"
"Dalvik Cache"
"Factory reset"
15 Going to main menu -> "Reboot"
Then Moto logo appears, later Safestrap splashscreen, after 10 seconds CM logo
It spinning
1 minute
2min
3min
5
It still spinning
10
15
30
WTF
What am I doing wrong?
Does anybody can confirm I'm flashing CM right?
I'm trying over and over again and it's not working
You're doing it right. Thats the correct procedure. Though step 14 is unnecessary.
However there might be a chance that your downloads are corrupted. Try redownloading the files.
Sent from my XT912 using Tapatalk 2
I have the same problem. I could use any rom before. Then after restoring phone with flash IT i cant install any of cm10.1 based roms. I tried about 15 roms: different versions of cm and aokp - same result. Rom just cant boot bootloop or just black screen forever. Same result with bootmenu and with safestrap.
neo.ank said:
You're doing it right. Thats the correct procedure. Though step 14 is unnecessary.
However there might be a chance that your downloads are corrupted. Try redownloading the files.
Sent from my XT912 using Tapatalk 2
Click to expand...
Click to collapse
I tried without step 14 - it not helps
I checked md5sum of downloaded roms - it is OK.
I also tried install LiquidSmooth ROM - after Safestrap splashscreen blank screen appears and the system did not start :/
jacek607 said:
I also tried install LiquidSmooth ROM - after Safestrap splashscreen blank screen appears and the system did not start :/
Click to expand...
Click to collapse
I have excatly the same problems for CM10 and LiquidSmooth . The only rom that I can flash is the MIUI V4
Any ideas?
sanieth said:
I have excatly the same problems for CM10 and LiquidSmooth . The only rom that I can flash is the MIUI V4
Any ideas?
Click to expand...
Click to collapse
How do you install Miui? With safestrap?
Sent from my XT910 using xda app-developers app
I got into boot loop when i tried CM for the first time. Then tried another ROM, again boot loop. Then downloaded and pushed EU Jelly Bean using RSD Lite and its working great now.
Sent from my Nexus 7 using xda app-developers app
All I can infer from posts above is it appears as a kernel incompatibility issue. Looks like your kernel won't allow kexec to boot the Rom. Its consistent with all kexec based ROMs so thats the only thing that could affect.
Since there aren't many people flashing CM over ICS kernel, this might not have been reported.
Sent from my XT912 using Tapatalk 2
same here on Razr "umts_spyder" (Euro Version)
neo.ank said:
All I can infer from posts above is it appears as a kernel incompatibility issue. Looks like your kernel won't allow kexec to boot the Rom. Its consistent with all kexec based ROMs so thats the only thing that could affect.
Since there aren't many people flashing CM over ICS kernel, this might not have been reported.
Sent from my XT912 using Tapatalk 2
Click to expand...
Click to collapse
Where in the last days I switched between(ish) cm-10.1.0 cm-10.1.2 and cm-10.1-20130715-NIGHTLY-umts_spyder.zip. Wasn't too stable (perhaps Navigon problems?) so I went on trying those versions.
This night I tried to install the cm-10.1-20130717-NIGHTLY-umts_spyder.zip and since got stuck in bootloop since.
Safe Strap: Wipe / Factory reset didn't get me out of there.
Hi again,
I just found solution for my problem with boot loop:
I just removed my sd card
and CM boots correctly
Something is wrong with sd card - it is visible and working well with stock ics, but when I start CM and insert card, CM can't see this card
Sent from my XT910 using xda app-developers app
removed safestrap....
Since I like to use the memory of the external card I:
removed safestrap and back on "Stock" XT910 / 4.1.2
updated to 982.124.14.xt910.Retail.en.EU
So I got all the Memory and a working system back.
Even though I kinda "love" CM I couldn't warm up to the (still genius) memory management of safestrap.
Also I didn't get a really smooth running CM - system.
Perhaps it is Navigon related that I now and then really depend on. And no, not in every part of the country the google maps gets its info via online.
My next step is to root.... http://forum.xda-developers.com/showthread.php?t=2202695
And in a couple of months I hope to find myself with a completely cracked (bootloader without safestrap) + CM stable.
format system is work
CM 10.1 boot loop
All,
Thanks in advance for any help. My XT912 was working great on the Cyanogenmod 10.1, until it became stuck in boot loop. I've tried all the steps mentioned above, to include wiping cache, FDR and removing the SD card - all to no avail.
I've also pushed the libskia.so file via: adb push ~/path/to/libskia.so /system/lib. http://forum.xda-developers.com/showthread.php?p=38591638#post38591638 - is there a similar file for the RAZR?
I'm able to use safestrap to go back to the stock ROM but i've had the taste of CM and can't get it out of my mind now!
Phil
Safestrap Bricked my Bionic Wednesday night
I used to run CM on my OG. I have always rooted my phones, relying completely on exploits found on these forums. I lost my Bionic in the forest last week and got my replacement Tuesday. After rooting it, I became nostalgic for a ROM that is devoid of bloatware. Casting around, I found good references for CM. So, I installed Safestrap 3.11 and downloaded the latest stable version of CM and booted into Safestrap recovery. So far, so good. I then configured a ROM slot 1 and tried to install CM into it. That may have been a mistake on my part since I have no experience with Safestrap and other users' posts seemed to indicate that they could switch between OS's by switching between ROM slots. Anyway, it didn't work and I couldn't boot back into my phone. So, I tried to restore my backup into Stock. That image didn't load. Presently, I could no longer get to Safestrap recovery and just got a black screen. That was late Wednesday night or early Thursday morning (8/15/2013). I tried getting to the normal recovery application and I could boot into the menu but, when I tried to select recover, instead of allowing me to navigate to my backups (or any other recovery file), I was presented with the dead robot image. After each dead end, only a battery pull would power off the phone. After messing around for a while with the recovery tools menu, I found that the sbf flash option appeared to be functional.
So, after researching how to use it, I downloaded the latest version of RSD Lite that I could find (along with the MKT patch, whatever that does) and tried to push the Verizon published zip file for the 4.1.2 OTA. Somewhere during the process and before it started pushing images, it hit an XML error and stopped. So, then I did some more research and found that someone had created a file with a patch for the XML error. Again using RSDLite, I pushed that file to my phone. It worked and, after it flashed the image, I had what was basically a factory reset phone. So I reconfigured it an rooted it using the Ubuntu exploit again.
However, when I boot into recovery and select the recovery option, I still get the dead robot icon. I tried reinstalling and uninstalling Safestrap but I still get the same dead robot behavior. With Safestrap recovery installed, I can boot into recovery and see my original backup files but I am afraid to use any of the functionality because Safestrap borked up my phone so badly the first time and I don't want to try to recover from a bricked device state. But I would like to get the recovery program working again just in case I need it to apply a package someday.
They guys
I've been running BMM for a few months now with no problems.
I saw that Hashcode updated his SS recovery so I decided to move over there since it's updated and I prefer TWRP anyway.
I uninstalled BMM and installed SS, but I think the SS apk didn't install properly, without me noticing.
When i reboot the phone, I get the red M logo but then black screen.
*sigh* so I downloaded the firmware and I flashed sbf on RSD lite.
Still black screen.
not sure what to do now, Fastboot and stock recovery working fine, it's just system not booting.
Q&A for [RECOVERY] TWRP Recovery 2.8.1.0 - Thor
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY] TWRP Recovery 2.8.1.0 - Thor. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Tried it on 13.3.2.4 with know dice. You have to hard reset a couple of times and then safestrap comes back up. Tried a few times with zero luck so I just flashed twrp2.7.1 and all is good again. Also made me post here because I have less than 10 posts.
Kudos!
Firstly - thanks very much to all people involved in this - especially vortox - excellent work!
Secondly, I've just flashed TWRP successfully on 13.3.0.5.
The only thing which seems a bit strange is that when starting TWRP, I have to wait until the HDX's display goes into power-saving mode (i. e. goes deeply black) and switch the display on again before the starting screen of TWRP can be seen & TWRP be used (before that point, the display black for a while, but not in power-saving mode).
Is this normal?
I have made a grave error and have no recovery.
Well watching this special day unfold I mistakenly lost my original backup recovery.img and after dd now have no recovery. What can I do to get a working stock recovery.img back onto /dev/block/mmcblk0p18. When I dd twrp I apparently wasn't ready and now I have no recovery. I am running the rollback 13.3.0.9 and still have root/safestrap.
Nevermind I followed this and fixed my stock recovery.
http://forum.xda-developers.com/showthread.php?t=2782159&page=20
Certainly no expert here, but can't you just flash the TWRP recovery via Rashr or Flashify while the OS is running...? Or do you just want to have the stock recovery image? If I'm misunderstanding your question - sorry.
nocmonkee said:
Well watching this special day unfold I mistakenly lost my original backup recovery.img and after dd now have no recovery. What can I do to get a working stock recovery.img back onto /dev/block/mmcblk0p18. When I dd twrp I apparently wasn't ready and now I have no recovery. I am running the rollback 13.3.0.9 and still have root/safestrap.
Click to expand...
Click to collapse
RiseT said:
Certainly no expert here, but can't you just flash the TWRP recovery via Rashr or Flashify while the OS is running...? Or do you just want to have the stock recovery image? If I'm misunderstanding your question - sorry.
Click to expand...
Click to collapse
Sure but it never would boot into recovery or it was booting into an unexploitable recovery. I hadn't fully downgraded it yet or something went wrong so I had no usable recovery. I couldn't use amazon's tools to fix it and I could properly install twrp, so after "Amazon Recovery" worked again I was able to boot into the rollback image and use amazon's own upgrade bin. "update-kindle-13.3.1.0_user_310079820.bin". Once it went through the Amazon upgrade process. I used the KFHDX Toolkit to root it, then I adb'd into it and then su'd to root and immediately dd'd the TWRP recovery and then did reboot recovery in adb and "TADA" I had working twrp recovery and was able to install the CM 11 and gapps.
I see. Great to hear that it's working now. As you've successfully installed TWRP & CM 11 now - could you confirm the above stated behaviour regarding the black screen? Additionally to TWRP, I've just installed CM as well; interestingly, the display is showing the same behaviour with CM as with TWRP (I can only see something after the display returned from power-saving mode). With Amazon stock recovery & ROM, this isn't the case, so it shouldn't be a hardware problem.
nocmonkee said:
Sure but it never would boot recovery. I hadn't fully downgraded it yet or something went wrong so I had no recovery. After "Amazon Recovery" worked again I was about to boot into the rollback image and use amazon's own upgrade bin. "update-kindle-13.3.1.0_user_310079820.bin". Once it rebooted I used the KFHDX Toolkit to root it, then I adb'd into it and then su'd to root and immediately dd'd the TWRP recovery and then did reboot recovery in adb and "TADA" I had working twrp recovery and was able to install the CM 11 and gapps.
Click to expand...
Click to collapse
RiseT said:
I see. Great to hear that it's working now. As you've successfully installed TWRP & CM 11 now - could you confirm the above stated behaviour regarding the black screen? Additionally to TWRP, I've just installed CM as well; interestingly, the display is showing the same behaviour with CM as with TWRP (I can only see something after the display returned from power-saving mode). With Amazon stock recovery & ROM, this isn't the case, so it shouldn't be a hardware problem.
Click to expand...
Click to collapse
I am not experiencing this black screen issue. I did though start from 3.2.4 and worked my way down to 3.1.0. CM boots quickly and is super responsive. When booting it flashes the all gray "kindle fire" for about 10-20 seconds before it boots into recovery or cm. Possibly you just aren't see that screen and are seeing black instead?
Thanks for the feedback!
I think I don't see the gray "Kindle Fire" for that long - so that's a possibility. Btw, I also don't see the Cyanogenmod boot logo I'm used to on mobile phones. I guess I have to investigate this further. Wondering if the fact that I started with a rather "antique" stock firmware could have something to do with it, but I would guess that this is not possible as all that old stuff is wiped away when installing TWRP & the CM rom.
Edit: The gray "Kindle Fire" logo shows up for circa 4 seconds.
nocmonkee said:
I am not experiencing this black screen issue. I did though start from 3.2.4 and worked my way down to 3.1.0. CM boots quickly and is super responsive. When booting it flashes the all gray "kindle fire" for about 20 seconds before it boots into recovery or cm. Possibly you just aren't see that screen and are seeing black instead?
Click to expand...
Click to collapse
Thanks to everyone for their hard work bringing us TWRP for the Kindle HDX models.
vortox said:
It's not working on 3.2.4, but works atleast at 3.1.0. I didn't test other versions.
Click to expand...
Click to collapse
What's the best way to downgrade a rooted/safestrapped 13.3.2.4 stock-rom to a lower version?
well
Deathcrow said:
Thanks to everyone for their hard work bringing us TWRP for the Kindle HDX models.
What's the best way to downgrade a rooted/safestrapped 13.3.2.4 stock-rom to a lower version?
Click to expand...
Click to collapse
go back to development and start reading. To have somebody here we explain everything would just be ridiculous there is a thread or several threads on rolling back..from different versions to different versions I believe in development there is even a thread started now for exactly your question. And it was started yesterday or the day before.
jimyv said:
go back to development and start reading. To have somebody here we explain everything would just be ridiculous there is a thread or several threads on rolling back..from different versions to different versions I believe in development there is even a thread started now for exactly your question. And it was started yesterday or the day before.
Click to expand...
Click to collapse
Oh yeah, I completely missed that. Thanks for pointing it out.
if i install this twrp, what would happen to my safetrap recovery and can i even access it after and use the backups i saved using safetrap on twrp?
well
latedays101 said:
if i install this twrp, what would happen to my safetrap recovery and can i even access it after and use the backups i saved using safetrap on twrp?
Click to expand...
Click to collapse
yes you will still be able to access your safestrap. And yes your safestrap backups will be compatible with your new recovery. But keep in mind that your backups from safestrap will not contain a kernel and you will have to match one up with it..
jimyv said:
yes you will still be able to access your safestrap. And yes your safestrap backups will be compatible with your new recovery. But keep in mind that your backups from safestrap will not contain a kernel and you will have to match one up with it..
Click to expand...
Click to collapse
thanks, i just installed the twrp recovery successfully, how do i boot into safetrap again if i want to use it?
lol
latedays101 said:
thanks, i just installed the twrp recovery successfully, how do i boot into safetrap again if i want to use it?
Click to expand...
Click to collapse
it probably took you longer to ask me that question then it did for you to figure it out.
if not just simply reboot it and tap recovery on the splash screen as it boots just like always if you want access to it from your system just install the APK..personally I wouldn't mess with itother than to get into the backups from my new recovery to restore data....
jimyv said:
it probably took you longer to ask me that question then it did for you to figure it out.
if not just simply reboot it and tap recovery on the splash screen as it boots just like always if you want access to it from your system just install the APK..personally I wouldn't mess with itother than to get into the backups from my new recovery to restore data....
Click to expand...
Click to collapse
yeah i tried that but seems like its just boots into twrp not safetrap and thought something weird is happening and even if i tried installing the apk and press into recovery, it just boots into the cm rom.
well
latedays101 said:
yeah i tried that but seems like its just boots into twrp not safetrap and thought something weird is happening and even if i tried installing the apk and press into recovery, it just boots into the cm rom.
Click to expand...
Click to collapse
did you open up the app and see if the recovery is installed?. Like I said I would not mess with it personally. safestrap is a version of TRWP.. but is installed in the system and may have compatibility issues with your cm 11 etc other ROM that you may install with your new true recovery.
besides if you flash cm through your new recovery nothing you can install through safestrap at this moment would be compatible with the kernel ..besides a backup of that same rom. you would have left there. Unless you flash a renamed bin file to get compatible kernel for whatever stock backup you were trying to restore from safestrap
jimyv said:
did you open up the app and see if the recovery is installed?. Like I said I would not mess with it personally. safestrap is a version of TRWP.. but is installed in the system and may have compatibility issues with your cm 11 etc other ROM that you may install with your new true recovery.
besides if you flash cm through your new recovery nothing you can install through safestrap at this moment would be compatible with the kernel ..besides a backup of that same rom. you would have left there. Unless you flash a renamed bin file to get compatible kernel for whatever stock backup you were trying to restore from safestrap
Click to expand...
Click to collapse
Hm damn i just wanted to go back into safestrap so i can delete all my rom slots that i created that are wasted space seems like i kind of screwed right now for not backing the previous safetrap recovery i guess, unless someone share a back image of safetrap that i can flash?
well .
latedays101 said:
Hm damn i just wanted to go back into safestrap so i can delete all my rom slots that i created that are wasted space seems like i kind of screwed right now for not backing the previous safetrap recovery i guess, unless someone share a back image of safetrap that i can flash?
Click to expand...
Click to collapse
you were supposed to do that somewhere in the rolling back effort just before you do your new recovery. You were supposed to do it through a stock system and stock recovery to completely wipe the device.
you can still do it in your new recovery after you back your stuff up to your PC just go into wipe options and choose the option on the right wipe complete data.but that location of that folder is someplace I'm trying to find it for you
---------- Post added at 09:31 PM ---------- Previous post was at 09:23 PM ----------
jimyv said:
you were supposed to do that somewhere in the rolling back effort just before you do your new recovery. You were supposed to do it through a stock system and stock recovery to completely wipe the device.
you can still do it in your new recovery after you back your stuff up to your PC just go into wipe options and choose the option on the right wipe complete data.but that location of that folder is someplace I'm trying to find it for you
Click to expand...
Click to collapse
Try \mnt\shell\emulated\ then delete that folder named safestrap. That is where it is on my Apollo anyway
VERIZON SAMSUNG GALAXY NOTE 2 (T0LTE)
PLEASE READ READ READENTIRE OP
"ALL MAJOR WORK DONE BY HASHCODE SO GO GIVE HIM SOM THANKS.DO NOT POST ANY BUG OR ISSUE COUSED BY THIS RECOVERY IN ORIGINAL THREAD BY HASHCODE, POST HERE AND I WILL HELP YOU."
CURRENT PROJECT STATUS:
BETA v4.00-B01 (ND7/KK)
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 2.6.1.0 (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots (3-4 on the S3 due to partition size and internal space) for flashing ROMs. NOTE: The bigger you make the /data partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
HOW DO I INSTALL SAFESTRAP?
Requirement: Root
[NEW FOR v4.00+ KK Safestrap] Requirement: Uninstall old Safestrap application.
[NEW FOR v3.75+ KK Safestrap] Requirement: busybox. Grab "Busybox" from the Play Store and run the installer.
Once installed, open up the Safestrap application, Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
INSTALL VIDEO by DMX: https://www.youtube.com/watch?v=_RZI...e_gdata_player
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting (or the hard button underneath each option).
HOW DO I UPGRADE SAFESTRAP?
Push the APK up to your sdcard.
Boot back into the "stock" rom-slot.
Open your old Safestrap app and use the "Uninstall Recovery" button
Browse to where you pushed the APK
Click on it and install like normal
Once installed, open the APK, Grant SU access, Use the "Install Recovery" button.
KNOWN ISSUES:
- Sometimes the installation doesn't work correctly. If you don't see the splashscreen after a rebooting. Install Safestrap again. (DEBUGGING THIS AS I GET TIME)
- Busybox is now required for the Safestrap APK to work correctly
DOWNLOADS:
CONFIRM THAT YOU ARE USING A VERIZON WIRELESS SAMSUNG GALAXY NOTE 2 (T0LTE) [KITKAT:ND7]
LATEST FILE: Safestrap-T0LTE-4.00-B01.apk
androidfilehost
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
Special Thanks To
@Hashcode , DeesTroy & TeamWin for all their hard work making TWRP such a fantastic recovery. If you are considering a donation, then please have a look at the Team WIN website: http://teamw.in/project/twrp2
@urphonesux for testing
CHANGES:
4.00-B01
[2015-11-22] Synced with latest TWRP commits.
[2015-11-22] Remove read-only system.
[2015-08-13] Update TWRP recovery to 2.8.7.0 .
[2015-08-13] Materialize Safestrap apk.
Safestrap Recovery theme (Stock TWRP)
How to...
The theme zips are not flashable. First installation has to be done manually:
- Download the theme and rename it to "ui.zip".
- On SD card (if device has internal and external storage, use the internal) open TWRP folder and create a folder called "theme", without capital letters.
- Copy ui.zip to theme folder.
- Restart to recovery.
Safestrap Stock TWRP theme v4.00 B01.zip
1st!! Everything works fine. Multiple rom slots, backup/restore etc.
Thanks for this Mo!
on ND7 OTA. rooted via ghettoroot. Installed a previous version of safestrap: Safestrap-T0LTE-3.72-B02
it worked but didnt work with rom slots. I uninstalled the previous recovery and then uninstalled safestrap. Then installed this new one. Keeps not installing the safestrap recovery. Any ideas?
Tried doing a system wipe then installed clean 4.00 safestrap. no work..
Tried then system wipe and doing kingroot instead of ghettoroot. same result
albert001 said:
on ND7 OTA. rooted via ghettoroot. Installed a previous version of safestrap: Safestrap-T0LTE-3.72-B02
it worked but didnt work with rom slots. I uninstalled the previous recovery and then uninstalled safestrap. Then installed this new one. Keeps not installing the safestrap recovery. Any ideas?
Tried doing a system wipe then installed clean 4.00 safestrap. no work..
Tried then system wipe and doing kingroot instead of ghettoroot. same result
Click to expand...
Click to collapse
Does busybox installed! From the app too.
What's updated over the previous versions?
Upgrade from 3.72 on Verizon Note 2
I am using 3.72 and wonder if I should upgrade to the latest version. It must be completely removed and not updated as per OP instructions under content?
Thanks
adobrakic said:
What's updated over the previous versions?
Click to expand...
Click to collapse
TWRP is now 2.8.7.0 and its support kitkat..
NB2A said:
I am using 3.72 and wonder if I should upgrade to the latest version. It must be completely removed and not updated as per OP instructions under content?
Thanks
Click to expand...
Click to collapse
yes comlplete remove the old apk as mine has different package name
Hi,in this version works the option restore?
Piombo71 said:
Hi,in this version works the option restore?
Click to expand...
Click to collapse
As reprted by urphonesux its working as it should.
hello sir i try ur recovery mood Everything works fine and install new 5.01 rom in my i605 4.4.2 but samsung logo restart prob. in my phone rom and google apps successfully install in my phone then reboot but my phone not on. :crying::crying:
plzz help me..
djrajiv said:
hello sir i try ur recovery mood Everything works fine and install new 5.01 rom in my i605 4.4.2 but samsung logo restart prob. in my phone rom and google apps successfully install in my phone then reboot but my phone not on. :crying::crying:
plzz help me..
Click to expand...
Click to collapse
Hi,then if it is as in the previous version,this recovery can flash only TW Rom and not CM Rom,because black screen upon reboot.
djrajiv said:
hello sir i try ur recovery mood Everything works fine and install new 5.01 rom in my i605 4.4.2 but samsung logo restart prob. in my phone rom and google apps successfully install in my phone then reboot but my phone not on. :crying::crying:
plzz help me..
Click to expand...
Click to collapse
If you are locked bootloader then AOSP ROMs not for you.
The recovery wont flash any kernel and lack of kernel wont boot the ROM.
mohammad.afaneh said:
If you are locked bootloader then AOSP ROMs not for you.
The recovery wont flash any kernel and lack of kernel wont boot the ROM.
Click to expand...
Click to collapse
i try this 3 roms in my note 2 i605. 4.4.2nd7.
[ROM] [5.1.1_r18] [OFFICIAL] [Layers] XenonHD i605 - Note 2
[ROM] [6.0.1r10] [MULTI-WINDOW][VRToxin][i605] [01/08/2016]
[ROM][5.1/6.0][CM12.1/13][SABER][20160201] Unofficial Build - i605
rom and google apps successfully install but my phone black screen upon reboot..
djrajiv said:
i try this 3 roms in my note 2 i605. 4.4.2nd7.
[ROM] [5.1.1_r18] [OFFICIAL] [Layers] XenonHD i605 - Note 2
[ROM] [6.0.1r10] [MULTI-WINDOW][VRToxin][i605] [01/08/2016]
[ROM][5.1/6.0][CM12.1/13][SABER][20160201] Unofficial Build - i605
rom and google apps successfully install but my phone black screen upon reboot..
Click to expand...
Click to collapse
those ROMs are AOSP and you cant flash over locked bootloader device.
mohammad.afaneh said:
those ROMs are AOSP and you cant flash over locked bootloader device.
Click to expand...
Click to collapse
how to unlock my note 2 bootloader 4.4.2 ND7 Sir ???
djrajiv said:
how to unlock my note 2 bootloader 4.4.2 ND7 Sir ???
Click to expand...
Click to collapse
http://www.mobiletechvideos.com/samsung-galaxy-note-2-bootloader-sboot-downgrade-service/
The only way to unlock the bootloader at this point is to have this done. They will downgrade your Note 2 to 4.1.2 which can be unlocked. Sorry it is what it is.
i follow everything but when i install ss from the app, it doesnt give me an option to reboot recovery , im on 4.4.2
cubajean10 said:
i follow everything but when i install ss from the app, it doesnt give me an option to reboot recovery , im on 4.4.2
Click to expand...
Click to collapse
You installed Busybox?
1) cm-14.0-20160914-UNOFFICIAL-onyx.zip, 2) cm-14.0-20160917-UNOFFICIAL-onyx.zip
These are the 2 cm14 zips that I tried to flash multiple times (using twrp 3.0.2.0). The flash was successful everytime. But no matter how hard I try, it just won't boot. Just stays stuck on the OnePlus logo for eternity. I just recovered my phone from a soft-brick (no OS, no Recovery) and still continuously trying since days to use cm14.
Please, if anyone can then PLEASE HELP!
amritanshu.sikdar said:
1) cm-14.0-20160914-UNOFFICIAL-onyx.zip, 2) cm-14.0-20160917-UNOFFICIAL-onyx.zip
These are the 2 cm14 zips that I tried to flash multiple times (using twrp 3.0.2.0). The flash was successful everytime. But no matter how hard I try, it just won't boot. Just stays stuck on the OnePlus logo for eternity. I just recovered my phone from a soft-brick (no OS, no Recovery) and still continuously trying since days to use cm14.
Please, if anyone can then PLEASE HELP!
Click to expand...
Click to collapse
Check the bootloader compatibilty of these roms, if they r for the mm bootloader it ll not boot untill u upgrade ur bootloader, check the threads from wer u hv downloaded this...
amritanshu.sikdar said:
1) cm-14.0-20160914-UNOFFICIAL-onyx.zip, 2) cm-14.0-20160917-UNOFFICIAL-onyx.zip
These are the 2 cm14 zips that I tried to flash multiple times (using twrp 3.0.2.0). The flash was successful everytime. But no matter how hard I try, it just won't boot. Just stays stuck on the OnePlus logo for eternity. I just recovered my phone from a soft-brick (no OS, no Recovery) and still continuously trying since days to use cm14.
Please, if anyone can then PLEASE HELP!
Click to expand...
Click to collapse
Most Roms now require you too flash OOS 3.1.3 first. Like mentioned above bootloader issue.
Exodusche said:
Most Roms now require you too flash OOS 3.1.3 first. Like mentioned above bootloader issue.
Click to expand...
Click to collapse
I already flash the OOS 3, but still this problem continues.
File name: OnePlusXOxygen_14_OTA_015_all_201608181615_e03d2112e8ad4bff
Is there any other way how I can manually upgrade my bootloader? That would really help.
amritanshu.sikdar said:
I already flash the OOS 3, but still this problem continues.
File name: OnePlusXOxygen_14_OTA_015_all_201608181615_e03d2112e8ad4bff
Is there any other way how I can manually upgrade my bootloader? That would really help.
Click to expand...
Click to collapse
check out this thread http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
amritanshu.sikdar said:
I already flash the OOS 3, but still this problem continues.
File name: OnePlusXOxygen_14_OTA_015_all_201608181615_e03d2112e8ad4bff
Is there any other way how I can manually upgrade my bootloader? That would really help.
Click to expand...
Click to collapse
I use Oxygen_14_OTA_18_all but there's a couple files posted on the bootloader upgrade threads that allow you not too flash the whole firmware just the partions you need to upgrade.
i am having same issue i was on oxygenos 3.1.3 firmware when i started to flash nogut roms every nogut rom works except cm. i flashed official cynogenmod 14.1 thinking that problem must have been solved but it wont boot it just shows oneplus logo. i have waited for 30 minutes but nothing happened if something worked out for you please tell me.
Well I've looked around XDA for soultion and this is it.
CM 14 has some Kernel problems, so only what you have to do is just install new kernel as Arsenic or Black Reactor kernel
I was running the new bootloader on cm13 nightlies and couldn't get it to boot either.
Even after a full wipe and reflash with v7 gapps
Gave up in the end and went back to the last cm13 Nightly
flash arsenic kernel after flashing rom and gapps it will boot. Read the posts in ashwin's official cm 14.1 thread.
Flash Black Reactor (recommended) or Arsenic Kernel.
The zip files that you have for CM are the unofficial ones. So I guess they're from Sarthak Narang. Or at least one of them. Those ROMs require the older bootloader to function. So if you have the newer bootloader, it won't work.