Related
First off, I'm very sorry as I know by now you are mostly sick of noobs but I tried to figure out what I'm doing wrong on my own and am just stuck.
So here it goes:
I rooted my DROID 2.2.1 with superone click. Did everything I've read to do and tried to install bugless beast ROM. Tried to boot into recovery but I got the triangle exclamation point screen on reboot. Tried to install the ROM via ROM manager and the same thing happened. I was then able to get to clockwork recovery through ROM manager somehow and installed the ROM. At this point, I got the startup screen for bugless beast and it just looped. I restored back to Froyo and cannot get back to recovery boot because that $#%% screen with the triangle exclamation is killing me.
What should I do now? Or am I just too noob at this and should go back to the Matrix lifestyle of "ignorance is bliss" by unrooting?
Thanks again.
Matt
prepare to kick yourself in the head ^^
- the "triangle exclamation" pictures is EXACTLY the point where you can enter Recovery.
here´s how: press "volumeUP" and the "camera" button at the same time.
then navigate through the recovery (if you have a custom recovery installed, you´ll need to choose "apply update.zip" to load the custom/open recovery on the first screen) using your D-Pad.
Thank you for the button combo to get where I need to go. Now does anyone know why when I load a ROM, the start up screen just loops forever? I have tried loading cyanogen6 and bugless beast now both with the same issue.
nevermind...I'm stupid. Sorry. Needed to wipe data. But how do I get all my data back? If I restore data through nandroid then I just get boot loops again.
I haven't used rom manager before.
So i would recommend you to use open recovery to do flashing or rooting.
Have u flash a vulnerable recovery sbf ??
If yes, you can go to recovery mode and select "apply update".
Then the open recovery is applied.
By using OR, you can root phone and apply any updates you want.
Sent from my A853 using XDA App
matty1098 said:
nevermind...I'm stupid. Sorry. Needed to wipe data. But how do I get all my data back? If I restore data through nandroid then I just get boot loops again.
Click to expand...
Click to collapse
Boot loops??
Do u mean your phone keep rebooting??
Sent from my A853 using XDA App
Ok, so after using clockwork rom manager on my nook color and seeing how convenient it was, I thought, "hey maybe this would be good on my milestone." WRONG. I flashed the clockwork recovery (they even had an option for milestone) and when I rebooted into recovery from the software (either in rom manager or the reboot power option) it just rebooted straight into android. When I held the power and camera keys, it just took me to bootloader.
Under rom manager, there was also an option to flash the RA recovery, but that didn't seem to help (exact same behavior as clockwork recovery).
I'm currently running the CM7 mod and prior to this fiasco, I was using RA 1.7 (pretty sure). edit: RA 1.7 was my girlfriend's HTCmagic, I just remembered that I would have had some version of openrecovery on this phone.
So, I guess my question is, what are my next steps here? I'd really like to stop flying without a recovery. My only shred of an idea was to flash a stock image from rsdlite and set my milestone all the way back to stock and then reroot and re everything, but if someone has a better idea, I'd be very open to that as my plan seems like a big hassle.
A) not really the place for this post but anywa
B) you should beable to just flash the Vulnerable recovery http://android.doshaska.net/rootable then you can install a recovery from this forum thats for our phone!
Apologies, I didn't mean to step on any toes. Could a mod please recategorize this thread.
I will check out that link and report back if I need further assistance. Although, if that's a surefire way to fix my problem, I should be fine. Thank you for your fast (and succinctly informative) reply.
Tyfighter said:
Apologies, I didn't mean to step on any toes. Could a mod please recategorize this thread.
I will check out that link and report back if I need further assistance. Although, if that's a surefire way to fix my problem, I should be fine. Thank you for your fast (and succinctly informative) reply.
Click to expand...
Click to collapse
Quite alright if you have any more problems feel free to just PM me
Check this thread:
http://forum.xda-developers.com/showthread.php?t=1139120
Well, the good news is, that I flashed the vulnerable recovery and I'm able to boot into recovery. The bad news is, it only lasts for a few seconds. I see the standard recovery icon and then a bar fills up and then my phone reboots into android. From what you said, I take it that there's another step in here where I take another file from the forums and then install that as well. Is that just through RSD lite then?
Tyfighter said:
Well, the good news is, that I flashed the vulnerable recovery and I'm able to boot into recovery. The bad news is, it only lasts for a few seconds. I see the standard recovery icon and then a bar fills up and then my phone reboots into android. From what you said, I take it that there's another step in here where I take another file from the forums and then install that as well. Is that just through RSD lite then?
Click to expand...
Click to collapse
Ok so you need to take an open recovery for example http://forum.xda-developers.com/showthread.php?t=1091787 and extract it to the root of your sdcard so you have a update.zip file and openrecovery folder.
Then boot into recovery and press the volume up and camera button and a menu should come up.
Then select the 'flash update.zip' and this should 'boot' you into the custom recovery, sadly because of the looked bootloader we must do this everytime we wish to boot into recovery
Okay, I have that file, or one similar, from when I originally had started using custom roms (and updated/changed them etc.).
The problem is that before, when I'd go into recovery, it would have the icon of the phone out of the box with the exclamation mark or whatever, and it would stay there indefinitely.
Now, it only stays for a few seconds before rebooting into android. A little bar appears, fills up, then reboot. Doing the volume up + camera combo only serves to expedite this process (i.e. reboots as soon as I press it).
zacthespack said:
Ok so you need to take an open recovery for example http://forum.xda-developers.com/showthread.php?t=1091787 and extract it to the root of your sdcard so you have a update.zip file and openrecovery folder.
Then boot into recovery and press the volume up and camera button and a menu should come up.
Then select the 'flash update.zip' and this should 'boot' you into the custom recovery, sadly because of the looked bootloader we must do this everytime we wish to boot into recovery
Click to expand...
Click to collapse
what your doing (power + camera) is meant to put you into the bootloader mode... to get into recovery, hold 'x' on the physical keyboard and then hold the power button. This will get you into recovery. Hope this helps.
~D
are you sure that you did in fact flash the vulnerable bootloader, and not a newer, non-vulnerable one? sounds like that.. exploit fails, system reboots. also, if you are running an original rom right now, it does check the bootloader every reboot and flashes the non-vulnerable one!
Tyfighter said:
Okay, I have that file, or one similar, from when I originally had started using custom roms (and updated/changed them etc.).
The problem is that before, when I'd go into recovery, it would have the icon of the phone out of the box with the exclamation mark or whatever, and it would stay there indefinitely.
Now, it only stays for a few seconds before rebooting into android. A little bar appears, fills up, then reboot. Doing the volume up + camera combo only serves to expedite this process (i.e. reboots as soon as I press it).
Click to expand...
Click to collapse
I'm a bit confused with how you're getting into Recovery mode, but the way to enter recovery is to hold Power + X, then Camera + Vol Up when you see the Motorola Logo.
I'm getting into recovery the same way I always have Power+camera then volumeup+camera. Power+DpadUp is how I've been getting into bootloader. Power+X actually yields nothing, just a regular boot.
Unless the file hosted on the site that was linked earlier in the thread is a newer, nonvulnerable recovery then, yes, I'm sure I flashed vulnerable recovery. I'm going to attempt to flash again. Just to see if maybe that's the issue.
I'm pretty sure I'm seeing it at least attempt to enter recovery, which is a step up from before (before being that it just went to bootloader). Because I'm seeing the image that displays in the recovery menu, but then it brings up a progress bar (which I never saw before) and when that fills up (in about 2.5 seconds), that's it. Reboot.
Thanks everyone, for all the help though.
EDIT: Despite RSD lite saying that the process as a success, the reflash did nothing.
Tyfighter said:
I'm getting into recovery the same way I always have Power+camera then volumeup+camera. Power+DpadUp is how I've been getting into bootloader. Power+X actually yields nothing, just a regular boot.
Unless the file hosted on the site that was linked earlier in the thread is a newer, nonvulnerable recovery then, yes, I'm sure I flashed vulnerable recovery. I'm going to attempt to flash again. Just to see if maybe that's the issue.
I'm pretty sure I'm seeing it at least attempt to enter recovery, which is a step up from before (before being that it just went to bootloader). Because I'm seeing the image that displays in the recovery menu, but then it brings up a progress bar (which I never saw before) and when that fills up (in about 2.5 seconds), that's it. Reboot.
Thanks everyone, for all the help though.
Click to expand...
Click to collapse
Where did you get the VR sbf? android.doshaska.net/rootable ?
Yep, that's the one.
EDIT: Finally got up the guts to load the official Telus sbf into RSD lite and pull the trigger. It seems like this is probably beyond salvage now. Once again, many thanks to everyone, and if all goes well, I hope to only be in the ranks of the unrooted/unmodded for a few minutes.
EDIT the second: Okay, so flash to stock went perfectly. Everything works, including recovery, but not openrecovery. I can get to the menu to flash the .zip, but it fails the esignature check. Which I'm assuming points to Vulnerable recovery not flashing correctly or perhaps my file is corrupt, or maybe something more exotic and exciting. I flashed SHOLS_U2_03.11.0 if that's relevant.
For those interested, everything is up and functional again.
I had to first flash back to stock, then flash the vulnerable recovery located at http://modmymobile.com/forums/downloads.php?do=file&id=28089 , then the standard, boot to recovery, blah blah blah, install a new rom.
Let this be a lesson to the rest of you; Clockwork Rom Manager does not, I repeat, does NOT seem to work on our milestones. Which is a real shame...
I realize this is a double post, but I'm just so darned jubilant to be able to update my rom again.
A couple days ago I decided to load the new Safestrap Hashcode linked to. Everything went very well, and I have been running Maverick 4.5 in slot 2 as my daily driver. I was able to get back into Safestrap using the menu button. I also loaded Gummybear ICS into Slot 3, but went back to Maverick.
Yesterday I was going to go back into Safestrap and switch to the Gummybear/slot 3 rom to check it out.
I can't get back into Safestrap at all. I am stuck in the Maverick 4.5 rom.
One thing I did notice and do not understand: When I use Titanium Backup or the Reboot Widget to "Reboot into Recovery", I get a Yellow Triangle with an Exclamation Mark and the Android guy.
mhelm23 said:
One thing I did notice and do not understand: When I use Titanium Backup or the Reboot Widget to "Reboot into Recovery", I get a Yellow Triangle with an Exclamation Mark and the Android guy.
Click to expand...
Click to collapse
That's the stock Droid 3 recovery. Using a reboot recovery will lead to that, and will not allow Safestrap's bootloader to intercept the boot and activate Safestrap recovery.
I haven't tried running Safestrap 3.05 myself, since it's still not official, but I do know that you cannot reboot recovery as you describe to to get into Safestrap for any version of Safestrap.
mhelm23 said:
A couple days ago I decided to load the new Safestrap Hashcode linked to. Everything went very well, and I have been running Maverick 4.5 in slot 2 as my daily driver. I was able to get back into Safestrap using the menu button. I also loaded Gummybear ICS into Slot 3, but went back to Maverick.
Yesterday I was going to go back into Safestrap and switch to the Gummybear/slot 3 rom to check it out.
I can't get back into Safestrap at all. I am stuck in the Maverick 4.5 rom.
One thing I did notice and do not understand: When I use Titanium Backup or the Reboot Widget to "Reboot into Recovery", I get a Yellow Triangle with an Exclamation Mark and the Android guy.
Click to expand...
Click to collapse
thats the stock recovery
now. do you still get the boot menu splash page where it asks you to input the menu key or continue?
if so hit the menu many times or hit on the screen the hit menu for recovery image section, as it shoulod also work.
maybe my next question is silly or already tried, but have you tried to try it with the charger disconnected?
some times when my droid 3 is connected, the touch screen gets un responsive o registers more than input
hope this helps
I now have the same problem. I see the splash screen and it vibrates and reacts when I press the menu button, however it does not boot into safestrap v3.05.
From the JB topic it seems more people have this problem!
DoubleYouPee said:
I now have the same problem. I see the splash screen and it vibrates and reacts when I press the menu button, however it does not boot into safestrap v3.05.
From the JB topic it seems more people have this problem!
Click to expand...
Click to collapse
For those with trouble entering recovery with SS 3.05
The EASIEST and most DEPENDABLE way I've found to boot into the new SS 3.05 is;
Shutdown the phone
Slide open keyboard
Hold M and press the power button to boot the phone (still holding M, release when it boots the next step)
Immediately a menu pops up
Press Volume DOWN to highlight "BP Tools" (tap several times, be quick, if you wait too long, it'll automatically select what is highlighted)
Press Volume UP to select it.
Phone will reboot showing the M logo, then proceed into SS Recovery.
Skreelink said:
For those with trouble entering recovery with SS 3.05
The EASIEST and most DEPENDABLE way I've found to boot into the new SS 3.05 is;
Shutdown the phone
Slide open keyboard
Hold M and press the power button to boot the phone (still holding M, release when it boots the next step)
Immediately a menu pops up
Press Volume DOWN to highlight "BP Tools" (tap several times, be quick, if you wait too long, it'll automatically select what is highlighted)
Press Volume UP to select it.
Phone will reboot showing the M logo, then proceed into SS Recovery.
Click to expand...
Click to collapse
This did not work for me. It just hangs on the Motorola splash screen after choosing BP Tools. Just tried a few moments ago.
Also I haven't had my phone plugged in or charging.
Sent from my DROID3 using xda premium
mhelm23 said:
This did not work for me. It just hangs on the Motorola splash screen after choosing BP Tools. Just tried a few moments ago.
Also I haven't had my phone plugged in or charging.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
Strange, I have tried it several times... worked each time... maybe try reinstalling safestrap 3.05? Back up what you can of course, stock should not be touched.
Skreelink said:
Strange, I have tried it several times... worked each time... maybe try reinstalling safestrap 3.05? Back up what you can of course, stock should not be touched.
Click to expand...
Click to collapse
Yea - I tried that too. I am really at a loss.
Sent from my DROID3 using xda premium
I am sittin in the same spot. Can't boot into recovery...
Sent from my DROID3 using xda app-developers app
Skreelink said:
For those with trouble entering recovery with SS 3.05
The EASIEST and most DEPENDABLE way I've found to boot into the new SS 3.05 is;
Shutdown the phone
Slide open keyboard
Hold M and press the power button to boot the phone (still holding M, release when it boots the next step)
Immediately a menu pops up
Press Volume DOWN to highlight "BP Tools" (tap several times, be quick, if you wait too long, it'll automatically select what is highlighted)
Press Volume UP to select it.
Phone will reboot showing the M logo, then proceed into SS Recovery.
Click to expand...
Click to collapse
Had this problem today after creating a rom slot and flashing a new rom, this worked for me however I had to try it a few times. Once I got into recovery I wiped the rom and rom slot and ss3 is working properly now. Not sure if this was a rom issue or ss3.
Sent from my DROID3 using XDA
i had the same problem. and a bootloop top...
i have complete install my droid everything is lost...
another question. my "new" droid has the build 860 and withe safetrap i installed 2 other system.
can i update the stock to 906 without loosing safetrap and the 2 new systems?
dabayer said:
i had the same problem. and a bootloop top...
i have complete install my droid everything is lost...
another question. my "new" droid has the build 860 and withe safetrap i installed 2 other system.
can i update the stock to 906 without loosing safetrap and the 2 new systems?
Click to expand...
Click to collapse
When you run the OTA update to 906, it will remove the Safestrap bootstrap and will unroot as well. However, you can reroot with Motofail, then run the Safestrap app again to install recovery, and you slots *should* still be there. Perhaps making a backup of each slot before running the OTA would be smart.
doogald said:
When you run the OTA update to 906, it will remove the Safestrap bootstrap and will unroot as well. However, you can reroot with Motofail, then run the Safestrap app again to install recovery, and you slots *should* still be there. Perhaps making a backup of each slot before running the OTA would be smart.
Click to expand...
Click to collapse
i dont like the word "should"
ok i try to save the files in safetrap and try an OTA. yesterday the ota didn't run but i think i have to wait longer thar it starts the installation than the 10 minutes...
The slots are all stored on the internal storage (the mount point /sdcard) on the phone, so as long as you don't format internal storage, they should stay there.
I should note that I have never tried installing the OTA with safestrap 3.05 installed - I did it with 1.08. Actually, you may want to activate the stock slot, go into the safestrap app and uninstall recovery, and then try running the OTA. It's possible that the OTA will balk with a custom recovery installed - I don't remember, and, like I said, I never tried with Safestrap 3.05 installed.
You can also download the OTA, copy it to an external SD card, and manually run the update from stock recovery. See this thread: http://forum.xda-developers.com/showthread.php?t=1643521
[edit] Sorry - that link is for an update from 890 to 906. I forgot that you were not on 890. Sorry about that...
I had almost the same problem with my phone, the diference is that mine got stuck on non safe system (Stock ROM). Initializing the phone with th Android Recovery (Turning on with the key "m" pressed down) and choosing BP Tools doesn't worked.
- Phone: Milestone 3 XT860 (Brazilian Droid 3)
- Carrier: Vivo
- Current ROM: Stock 2.3.5 - 5.2.440
when I did it go into bootloader but it could not go into download mode, i know how to restore back to stock rom unroot. i rooted it using towelroot then flashed wrong recovery but recovery worked, it was on 6.0.0.0 something. When I try to go into fastboot and it say "loading" top of screen and tap volume up to continue, nothing moving foward into download mode.
Please Help.
Pull battery? Enter recovery (or flash new recovery.img in fastboot). If this doesn't help, try kdz.
bravho said:
Pull battery? Enter recovery (or flash new recovery.img in fastboot). If this doesn't help, try kdz.
Click to expand...
Click to collapse
I will try it when I get home, already did battery pull, that did not do it. So I was thinking doing lg tool to update firmware then downgrade later.
Where do I can find this recovery IMG? Custom recovery or stock recovery?
Thanks for replying.
Custom : see thread from cm11, @Quarx, twrp or cwm. @shoxxy has latest twrp
Sent from my LG-D405n using XDA Free mobile app
LeonKnight12 said:
when I did it go into bootloader but it could not go into download mode, i know how to restore back to stock rom unroot. i rooted it using towelroot then flashed wrong recovery but recovery worked, it was on 6.0.0.0 something. When I try to go into fastboot and it say "loading" top of screen and tap volume up to continue, nothing moving foward into download mode.
Please Help.
Click to expand...
Click to collapse
When making this kind of post, ALWAYS include the device model you are speaking of. There are 4 different models of the LG L90. From your location, I'll guess that you have the LG-D415 model.
From what I'm reading, you are NOT in fastboot mode but Software Update Mode. You MUST zero out the LAF partition in order to enable fastboot on the device. Also, fastboot and download modes are one in the same.
And what exactly are you trying to do? If your recovery is your issue, you can go here and scroll down to post #4 and download a flashable version of TWRP which can be flashed with the recovery you already have. Once flashed, find an option in your current recovery to "Reboot Recovery". It's probably in the "Advanced" menu. This will unload the current recovery from memory and load and execute the new recovery.
You also may want to have a look at the Frequently Asked Questions - LG Optimus L90 thread.
Well I messed up big time, no os installed, But device stills works were able to see download mode with numbers beside left screen not on second screen with bars.
Able to go in Twrp but it keep saying failed when i flash stock rom (remounting problem?).
Device I battery pull and put battery in and able to see LG logo then it went into CWM recovery itself then I selected Recovery reboot from CWM leaded me to TWRP recovery.
Tried to flash using lgtool2014 but flashing stock rom bars hasn't moved kept saying replug usb and retry.
Good News! I got it to work again!
Searching many website homework endless hours and I got my phone to work again. I was not panic I had nexus 6 with me, so I had a experience previous devices rooting.
Anyway, I went through to unlock bootloader and then I reboot the phone into TWRP recovery and flashed stock.zip sucessfully, unmounting was failed. Clicked reboot phone and LG logo appears stayed for like few sec then starting seeing tmobile boot up and everything seem well. gonna root again to see if i get any of this to work.
Hi guys, I need help please!
I am using Samsung Note 3 SM-N9005 ARMv7 Lollipop 5.0. Rooted it with Kingoroot. "installed" TWRP through Flashify.
I downloaded Xposed Framework xposed-v86-sdk21-arm.zip onto my phone and installed it through TWRP in Flashify. Everything seemed fine, got the message install successful, I selected "reboot" instead of "clear cache/dalvik". Phone went into reboot...Samsung Note 3...Samsung logo...and stuck there. I understand that it takes some time for first boot, and I waited, but almost an hour and its still showing the same screen. So I tried to power off the phone, but it restarted again and stuck in the same logo screen. I tried to go into recovery mode hoping to get TWRP to do a reset or something, but no TWRP! Was only given option of "volume up - continue(to odin mode)" and "volume down - cancel(restart phone)". No option for factory reset either. So i booted odin, and tried to flash openrecovery-twrp-2.6.3.7-hlte.img.tar, got the messaged passed, phone rebooted and again stuck in Samsung logo. Tried recovery mode and still no TWRP! Please help!!:crying: :crying: :crying:
p.s. phone won't power off, only way to do it is to remove the battery.
Samsung phones stock ROMs need an special version of Xposed framework. Geez, it is on the official thread:
Known issues:
- Bootloops on Samsung stock ROMs. That's due to Samsung's changes to ART. There are unofficial builds that work around this by deodexing and adjusting the ROM.
Click to expand...
Click to collapse
Archy12 said:
Hi guys, I need help please!
I am using Samsung Note 3 SM-N9005 ARMv7. Rooted it with Kingoroot. "installed" TWRP through Flashify.
I downloaded Xposed Framework xposed-v86-sdk21-arm.zip onto my phone and installed it through TWRP in Flashify. Everything seemed fine, got the message install successful, I selected "reboot" instead of "clear cache/dalvik". Phone went into reboot...Samsung Note 3...Samsung logo...and stuck there. I understand that it takes some time for first boot, and I waited, but almost an hour and its still showing the same screen. So I tried to power off the phone, but it restarted again and stuck in the same logo screen. I tried to go into recovery mode hoping to get TWRP to do a reset or something, but no TWRP! Was only given option of "volume up - continue(to odin mode)" and "volume down - cancel(restart phone)". No option for factory reset either. So i booted odin, and tried to flash openrecovery-twrp-2.6.3.7-hlte.img.tar, got the messaged passed, phone rebooted and again stuck in Samsung logo. Tried recovery mode and still no TWRP! Please help!!:crying: :crying: :crying:
p.s. phone won't power off, only way to do it is to remove the battery.
Click to expand...
Click to collapse
When you flash TWRP, you have to have reset unchecked in Odin, when the flash finishes you pull the battery and then boot into recovery via button combo. If you don't do that TWRP doesn't stick. From there flash the Xposed uninstaller so you can boot properly.
Sent from my SCH-R220
io_gh0st said:
Samsung phones stock ROMs need an special version of Xposed framework. Geez, it is on the official thread:
Click to expand...
Click to collapse
Thank you for you reply. Yes, I understand that, which was why I have been trying to find the correct version. Did a few searches using my phone type and version and found a list of sdk21.zips...so i selected the latest version..
mattzeller said:
When you flash TWRP, you have to have reset unchecked in Odin, when the flash finishes you pull the battery and then boot into recovery via button combo. If you don't do that TWRP doesn't stick. From there flash the Xposed uninstaller so you can boot properly.
Sent from my SCH-R220
Click to expand...
Click to collapse
Thank you for your reply, I'll try that now.
mattzeller said:
When you flash TWRP, you have to have reset unchecked in Odin, when the flash finishes you pull the battery and then boot into recovery via button combo. If you don't do that TWRP doesn't stick. From there flash the Xposed uninstaller so you can boot properly.
Sent from my SCH-R220
Click to expand...
Click to collapse
I tried it, unchecked "reboot", flashed TWRP, power off. When I tried button combo, I can't boot into recovery. It either keep giving me the restarting loop (power on, samsung note 3..then power off, and on again..) or if i let go of the power button at note 3, it goes to the samsung logo and stuck there.
update: I kept trying, and finally got a little different response. I pressed volume up + home + power buttons, and got 3 small lines of colorful words...
Recovery booting
Recovery is not seandroid enforcing
Set warranty bit : recovery
and then the phone turns off and start again
Tried different combinations, so far only the volume up sequence showed something a little different.
Archy12 said:
I tried it, unchecked "reboot", flashed TWRP, power off. When I tried button combo, I can't boot into recovery. It either keep giving me the restarting loop (power on, samsung note 3..then power off, and on again..) or if i let go of the power button at note 3, it goes to the samsung logo and stuck there.
update: I kept trying, and finally got a little different response. I pressed volume up + home + power buttons, and got 3 small lines of colorful words...
Recovery booting
Recovery is not seandroid enforcing
Set warranty bit : recovery
and then the phone turns off and start again
Tried different combinations, so far only the volume up sequence showed something a little different.
Click to expand...
Click to collapse
If you your phone does not boot into TWRP right after you flash it it will not stick and you need to flash it again. To get into recovery is power+home+volume up
Sent from my SCH-R220
mattzeller said:
If you your phone does not boot into TWRP right after you flash it it will not stick and you need to flash it again. To get into recovery is power+home+volume up
Sent from my SCH-R220
Click to expand...
Click to collapse
Could it be the TWRP versions doesn't work on my phone?
I tried openrecovery-twrp-2.6.3.7-hlte.img.tar and also twrp-2.8.7.0-hlte-4.4.img.tar both getting the same results "recovery is not seandroid enforcing" when I pressed vol up + home + power
Archy12 said:
Could it be the TWRP versions doesn't work on my phone?
I tried openrecovery-twrp-2.6.3.7-hlte.img.tar and also twrp-2.8.7.0-hlte-4.4.img.tar both getting the same results "recovery is not seandroid enforcing" when I pressed vol up + home + power
Click to expand...
Click to collapse
That is ok, you get that when you have modified system/recovery. Means your are not fully stock. If you had full stock unrooted unmodified system and recovery that goes away, nothing to worry about. If you are still having problems follow these step exactly:
1) Pull battery out of phone then put it back in
2) boot to download mode (power+home+volume down)
3) open Odin on computer (run as admin)
4) plug phone into computer
5) Uncheck a. Reboot and f. Reset time in Odin
6) flash TWRP (TWRP.img file goes in AP)
7) after successful flash unplug phone and pull battery
8) put battery back in and boot directly to recovery (power+home+volume up)
If you let it boot normally without going into TWRP first, it does not stick
Sent from my SCH-R220
mattzeller said:
That is ok, you get that when you have modified system/recovery. Means your are not fully stock. If you had full stock unrooted unmodified system and recovery that goes away, nothing to worry about. If you are still having problems follow these step exactly:
1) Pull battery out of phone then put it back in
2) boot to download mode (power+home+volume down)
3) open Odin on computer (run as admin)
4) plug phone into computer
5) Uncheck a. Reboot and f. Reset time in Odin
6) flash TWRP (TWRP.img file goes in AP)
7) after successful flash unplug phone and pull battery
8) put battery back in and boot directly to recovery (power+home+volume up)
If you let it boot normally without going into TWRP first, it does not stick
Sent from my SCH-R220
Click to expand...
Click to collapse
Thank you very much!!! I am finally able to boot into TWRP and did a restore, now my phone is back on!! Strange though, I was doing exactly those steps earlier but not successful. Anyways, Thank you very much!! <3
Oh, since I'm here, can you give me advise on which version xposed framework I should get? (Although I don't think my phone is touchwiz, is there a way to find out/confirm? I'm a noob as you can see)
Archy12 said:
Thank you very much!!! I finally able to boot into TWRP and did a restore, now my phone is back on!! Strange though, I was doing exactly those steps earlier but not successful. Anyways, Thank you very much!! <3
Oh, since I'm here, can you give me advise on which version framework I should get? (Although I don't think my phone is touchwiz, is there a way to find out? I'm a noob as you can see)
Click to expand...
Click to collapse
Ok, now that TWRP is on there things should be easier. You are on Stock ROM, it is TouchWiz. You will need to flash a custom ROM that is deodexed. If you like the stock look, feel, and options look in the threads for your device for a stock deodexed ROM. Or you can flash CM. Depending on what version of Android you decide to run will dictate which version of Xposed you install.
Sent from my SCH-R220
I am getting a note3 and wanted to install xposed on it. the phone is running 4.3. with that version there is no need for flashing correct? simply download apk and install?
mattzeller said:
Ok, now that TWRP is on there things should be easier. You are on Stock ROM, it is TouchWiz. You will need to flash a custom ROM that is deodexed. If you like the stock look, feel, and options look in the threads for your device for a stock deodexed ROM. Or you can flash CM. Depending on what version of Android you decide to run will dictate which version of Xposed you install.
Sent from my SCH-R220
Click to expand...
Click to collapse
I am quite used to the look and functionity of the current version I am using...which is lollipop 5.0. My phone is Samsung Note 3 SM-N9005 ARMv7 international Qualcomm. I'll need to flash custom ROM and then get a "matching" xposed framework,correct? Could you please direct me as to how to get xposed framework to work please?
Archy12 said:
I am quite used to the look and functionity of the current version I am using...which is lollipop 5.0. My phone is Samsung Note 3 SM-N9005 ARMv7 international Qualcomm. I'll need to flash custom ROM and then get a "matching" xposed framework,correct? Could you please direct me as to how to get xposed framework to work please?
Click to expand...
Click to collapse
Just go to the threads for your device and flash a TouchWiz based deodexed ROM
Sent from my SCH-R220
---------- Post added at 07:41 AM ---------- Previous post was at 07:38 AM ----------
trulosdoulos said:
I am getting a note3 and wanted to install xposed on it. the phone is running 4.3. with that version there is no need for flashing correct? simply download apk and install?
Click to expand...
Click to collapse
Correct, you would need this one:
http://dl-xda.xposed.info/modules/de.robv.android.xposed.installer_v33_36570c.apk
Sent from my SCH-R220
There is now an Xposed framework package supporting Stock (odexed) TouchWiz ROMS: http://forum.xda-developers.com/showpost.php?p=65373013&postcount=3960