Good afternoon everyone! I present myself as I am new here, and unfortunately, I'm in trouble.
I commented, I have a Kindle Fire 6.3.1 which try to give root to install the GOOGLE PLAY (ANDROID MARKET).
The problem is that now whenever I turn it on, a screen of TWRP (Team Win Recovery Project) version 2.2.0 and I can not do anything.
To start in normal mode I have to press the power button when you are starting and choose Normal Boot. The problem is that when you start to NORMAL BOOT ANDROID starts with in the middle of the screen and says WELCOME TO KINDLE FIRE ... touch the android to begin. But does not respond. All the Martian and does nothing, no onscreen button does nothing.
Anyone can help me???
PS: sorry for my english, i use a google translate
What ROM did you install?
I didnt install any ROM.
Just Root with Kindle Fire Utility (but, the process says
"Attempt to remove root checker
mv: can't rename '/system/bin/check_rooted' : No such file or directory
Please wait...
Im do the root, then i install gapps with the TWRP with the install zip option
and when i reboot in normal mode, i have the android martian with the phrase "TOUCH THE ANDROID TO BEGIN"
Can you post a picture of it? It's been a while since I used stock, but I don't remember anything about an android.
soupmagnet said:
Can you post a picture of it? It's been a while since I used stock, but I don't remember anything about an android.
Click to expand...
Click to collapse
The problem starts when i install the google apps with the TWRP
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That's weird. Where did you get the Google Apps package you installed in TWRP?
---------- Post added at 08:22 PM ---------- Previous post was at 07:30 PM ----------
It doesn't matter. Unless you have a Gapps package made for the stock Kindle software, I doubt it will ever work. You should look into installing Google Market on the KF manually.
soupmagnet said:
That's weird. Where did you get the Google Apps package you installed in TWRP?
---------- Post added at 08:22 PM ---------- Previous post was at 07:30 PM ----------
It doesn't matter. Unless you have a Gapps package made for the stock Kindle software, I doubt it will ever work. You should look into installing Google Market on the KF manually.
Click to expand...
Click to collapse
so... you think that im not lost?? How can i install the google market manually?? and how can i do to start the kindle normally? because in that way, i cant use it
Well, that depends. You can flash a custom ROM in TWRP and be done with it, or you can revert back to stock and have considerably more work to do. The upside to that is there is a stock based custom ROM (MoDaCo) that has everything you are trying to do, already done.
process cuenall
soupmagnet said:
Well, that depends. You can flash a custom ROM in TWRP and be done with it, or you can revert back to stock and have considerably more work to do. The upside to that is there is a stock based custom ROM (MoDaCo) that has everything you are trying to do, already done.
Click to expand...
Click to collapse
there is any tutorial to install the MoDaCo?? And where can i get that?
MoDaCo (download Gr9.1, not "alt")
http://forum.xda-developers.com/showpost.php?p=21282484
KFFB Supplement (Install custom ROM section)
http://forum.xda-developers.com/showpost.php?p=25730650
hold the power button down for 20 seconds then power on when you see the white kindle blue fire press your power button to get boot menu
then select recovery from the boot menu with the power button
Download modaco
select mount in twrp transfer this rom zip to your sd card but dont place it in a folder
then select unmount
go to install make sure you can find it
then hit the home button select wipe
wipe factory reset
wipe cache
wipe dalvik
wipe system
then go home again
select install again tap on rom zip flash it let it finish
then select reboot
enjoy your lovely rooted kindle fire
this is just rooted stock with playstore if you wish to try other roms use the same method with the exception of making a backup first
Really? You're going to thank this guy ^ (no offense pooch) and not the person that's been helping you THIS WHOLE TIME?!
soupmagnet said:
Really? You're going to thank this guy ^ (no offense pooch) and not the person that's been helping you THIS WHOLE TIME?!
Click to expand...
Click to collapse
jajaja!!! sorry!!! im at work! But in 2 hours i will there in my home and try to do that you say me.
THANKS A LOT!!!!
my kindle its alive and works again!!! But im still have a problem.
Everytime when i turn on the Kindle, the tablet starts with TWRP... how can i change that? it is possible?
On startup, hold the power button until the boot options appear at the bottom.
soupmagnet said:
On startup, hold the power button until the boot options appear at the bottom.
Click to expand...
Click to collapse
yes i do that, but, i need to do that everytime?? or can i change the boot mode permanent?
Choose "reset bootmode"
soupmagnet said:
Choose "reset bootmode"
Click to expand...
Click to collapse
where i can choose that option?
When you boot your device, is the boot logo a blue and white Kindle Fire?
soupmagnet said:
When you boot your device, is the boot logo a blue and white Kindle Fire?
Click to expand...
Click to collapse
yes, and if i hold the power button, a menu appears with 3 options in that menu i need to choose the reset boot mode?
Related
Hello,
I recently tried out the latest version of "PhilZ-Touch Recovery 6.0" located in this thread: http://forum.xda-developers.com/showthread.php?t=2446393. I did this from my previously installed recovery (TWRP V2.6.3.0) and everything went and had no problems, but I decided to go back to TWRP anyway and installed the latest TWRP version for my phone (V2.6.3.1) and again everything went fine and I was back to using TWRP again. The only problem I noticed is that when I boot into TWRP recovery now, I see this blue logo on my screen before I am presented with the TWRP curtain screen that I was used to seeing before.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I did a little searching and discovered this logo is the CyanogenMod Logo and since I do not have CyanogenMod installed on my phone, I can only assume it was placed on my phone as part of the philz recovery install. My question is then, how do I get rid of this logo since I do not have CM installed and do not want it to show up when I boot into TWRP?
TIA,
Mtcell
P.S. I would have posted this in the thread above, but I am a newly registered member and was not able to post in that tread until I have accumulated 10 or most post. Instead of spamming the forum to get my post count up (and taking a change on getting my account suspended in the process), I felt it would be better to post this question here.
I have been running the PhilZ recovery since @CNexus made it available, it doesn't place that image on your phone.
What ROM are you running? TW or AOSP??
jdelano said:
I have been running the PhilZ recovery since @CNexus made it available, it doesn't place that image on your phone.
What ROM are you running? TW or AOSP??
Click to expand...
Click to collapse
I am totally stock, rooted, and have been since I got the phone back in June. This is what is confusing me. Please note, the icon only shows up when I boot into recovery. If I do a normal boot / reboot then I cannot see it.
Thanks again for any and all replies,
Mtcell
mtcellph said:
I am totally stock, rooted, and have been since I got the phone back in June. This is what is confusing me. Please note, the icon only shows up when I boot into recovery. If I do a normal boot / reboot then I cannot see it.
Thanks again for any and all replies,
Mtcell
Click to expand...
Click to collapse
Hmmm, booting into recovery from android or with the phone off?
I just updated to 6.0.5 and I went into recovery to flash that update, though it was via the power menu.
Let me try with the power off ... ah yes, there is a little blue guy there when I go to recovery that way. (its been so long since I've done that)
TWRP probably doesn't over right that part of the phone.
Maybe try normal CMW flash and then back to TWRP or do a nandroid restore from a previous backup.
Twrp added that as the logo in the last update prob was a mistake
Sent from my SPH-L710 using xda app-developers app
jdelano said:
Hmmm, booting into recovery from android or with the phone off?
I just updated to 6.0.5 and I went into recovery to flash that update, though it was via the power menu.
Let me try with the power off ... ah yes, there is a little blue guy there when I go to recovery that way. (its been so long since I've done that)
TWRP probably doesn't over right that part of the phone.
Maybe try normal CMW flash and then back to TWRP or do a nandroid restore from a previous backup.
Click to expand...
Click to collapse
Thanks for the confirmation. At least I know I did not mess something up. I mainly do all of my rebooting into recovery from within android using GooManager, but I tried it from TWRP as well and the same result happened and finally, I tried it from a cold boot using the power, home, volume up buttons and the same result each time.
As far as the logo goes, I am not really overtly concerned about it as long as it's not going to mess anything up, I will probably leave it unless I find some reason I should remove it.
Thanks again for your replies,
Mtcell
yeah nothing messed up at all, you just have a new blue pal
Your welcome; a sanity test now and again is a good thing (some - like me - need them more often)
Notorious said:
Twrp added that as the logo in the last update prob was a mistake
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Ahh, that makes sense now. As I said, I will keep it just as long as it's not going to mess with anything (which it hasn't) so no harm no foul.
Thx again,
MTCell
Hi there,
The phone is rooted.
I've proceeded with the latest update today (~12mb size), don't remember the exact version.
It said it fixes some system bugs, etc.
After the update installed the phone won't load, stucks on the changing color logo.
Cannot access the recovery mode option in the boot menu (Vol+Power), says "no command", if press and hold Vol+ and Power again the phone restarts and enter the boot logo again.
Has anyone ideas how this can be fixed?
vagifn said:
Hi there,
The phone is rooted.
I've proceeded with the latest update today (~12mb size), don't remember the exact version.
It said it fixes some system bugs, etc.
After the update installed the phone won't load, stucks on the changing color logo.
Cannot access the recovery mode option in the boot menu (Vol+Power), says "no command", if press and hold Vol+ and Power again the phone restarts and enter the boot logo again.
Has anyone ideas how this can be fixed?
Click to expand...
Click to collapse
See http://forum.xda-developers.com/elephone-p8000/help/boot-loop-ota-upgrade-t3246203.
Post #16 describes how get into recovery from the 'no command' screen, and my post #12 describes how I managed to get it flashed using the SP Flashtool.
(Note my point no,5 - all I needed to do is press 'Download' first, THEN attach the powered off phone.)
Good luck!
kevvyboy said:
See http://forum.xda-developers.com/elephone-p8000/help/boot-loop-ota-upgrade-t3246203.
Post #16 describes how get into recovery from the 'no command' screen, and my post #12 describes how I managed to get it flashed using the SP Flashtool.
(Note my point no,5 - all I needed to do is press 'Download' first, THEN attach the powered off phone.)
Good luck!
Click to expand...
Click to collapse
Thanks a lot fot pointing this out.
Managed to get the recovery options menu.
However wiping the cache didn't help.
After doing the "root integrity check" got this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
do you think this can be fixed w/o reflashing an entire rom?
Oooh. Brighter minds than mine might correct me, but I think the bootloop is only fixed with a ROM flash
kevvyboy said:
Oooh. Brighter minds than mine might correct me, but I think the bootloop is only fixed with a ROM flash
Click to expand...
Click to collapse
Sad... anyway would you please direct me to where I can download the flash tool and stock ROM? Thanks.
kevvyboy said:
Oooh. Brighter minds than mine might correct me, but I think the bootloop is only fixed with a ROM flash
Click to expand...
Click to collapse
Actually, what you need to do is format the data partition or write the empty data.img file over the data partition which in effect does the same thing. And the later one is also what happens when your download entire rom using sp flash.
pitrus- said:
Actually, what you need to do is format the data partition or write the empty data.img file over the data partition which in effect does the same thing. And the later one is also what happens when your download entire rom using sp flash.
Click to expand...
Click to collapse
I've proceeded with "wipe data/factory reset" option - no effect...or are we talking about different things?
vagifn said:
I've proceeded with "wipe data/factory reset" option - no effect...or are we talking about different things?
Click to expand...
Click to collapse
In that case you probably need to flash the system.img and maybe even the boot.img from the latest rom. Elephone really should stop sending out these broken OTAs...
pitrus- said:
In that case you probably need to flash the system.img and maybe even the boot.img from the latest rom. Elephone really should stop sending out these broken OTAs...
Click to expand...
Click to collapse
I believe the case is that my phone is rooted and this is not the Elephone team's fault...anyways thanks for trying to help me.
vagifn said:
I believe the case is that my phone is rooted and this is not the Elephone team's fault...anyways thanks for trying to help me.
Click to expand...
Click to collapse
You belive this b***** that feed you on official forum? OTA should work on any device software config.
ruonim said:
You belive this b***** that feed you on official forum? OTA should work on any device software config.
Click to expand...
Click to collapse
I didn't read official forum. However you do loose your warranty if device is rooted, thus the device manufacturer owes you nothing. OTA worked fine before I rooted my device.
Btw, I got my phone back to life by re-flashing the entire ROM, just in case.
Hello my friend
vagifn said:
Hi there,
The phone is rooted.
I've proceeded with the latest update today (~12mb size), don't remember the exact version.
It said it fixes some system bugs, etc.
After the update installed the phone won't load, stucks on the changing color logo.
Cannot access the recovery mode option in the boot menu (Vol+Power), says "no command", if press and hold Vol+ and Power again the phone restarts and enter the boot logo again.
Has anyone ideas how this can be fixed?
Click to expand...
Click to collapse
The only thing you need to do is reinstall the añl the system with spflashtool. Never and remember never you can update any android with a ota if you are a rooted user.
If you speak spanish you can search in the youtube channel AndroidMxL to ser how you can reinstall the original ROM on your android.
allianzcred said:
The only thing you need to do is reinstall the añl the system with spflashtool. Never and remember never you can update any android with a ota if you are a rooted user.
If you speak spanish you can search in the youtube channel AndroidMxL to ser how you can reinstall the original ROM on your android.
Click to expand...
Click to collapse
Already did, thanks. Will never combine Root and OTA together again
Hi All,
I managed to brick my Fire TV 2 by flashing Magisk 12 whilst under the influence.
The unit now boots to the white Amazon logo, the power light goes from white to orange and then it restarts (bootloop).
I have tried various fixes covered on the AFTV site to get back in to recovery but to no avail.
Attempted to re-root the unit which fails with the message "error: source file is larger than target file!"
During the re-root process, It does load the preloader and the power light pulses white until I remove the power lead. Is there anything I can do from here?
Details: sloane-5.2.4.0-rooted_r1 rom with TWRP recovery v3.0.0-5
Thanks.
Reflash the pre rooted rom from recovery
m1steron said:
Hi All,
I managed to brick my Fire TV 2 by flashing Magisk 12 whilst under the influence.
The unit now boots to the white Amazon logo, the power light goes from white to orange and then it restarts (bootloop).
I have tried various fixes covered on the AFTV site to get back in to recovery but to no avail.
Attempted to re-root the unit which fails with the message "error: source file is larger than target file!"
During the re-root process, It does load the preloader and the power light pulses white until I remove the power lead. Is there anything I can do from here?
Details: sloane-5.2.4.0-rooted_r1 rom with TWRP recovery v3.0.0-5
Thanks.
Click to expand...
Click to collapse
The 2nd main requisite for Magisk is a fully unlocked bootloader. And only a small % of FTV1's have this done. If you can still go into TWRP. Then just flash the same PreRooted ROM you had installed before.
Y314K said:
The 2nd main requisite for Magisk is a fully unlocked bootloader. And only a small % of FTV1's have this done. If you can still go into TWRP. Then just flash the same PreRooted ROM you had installed before.
Click to expand...
Click to collapse
Sorry but it's a Fire TV 2 and the problem is that I can't get in to the TWRP recovery. I have tried multiple methods including the remote button presses and keyboard combinations.
The device isn't recognised over a network or USB adb. Before I bricked it, both USB and ADB debugging were enabled.
Have you tried the unbrick method?.
https://forum.xda-developers.com/newreply.php?do=newreply&p=65281865
I unbricked mine this morning
CFKod said:
Have you tried the unbrick method?.
https://forum.xda-developers.com/newreply.php?do=newreply&p=65281865
I unbricked mine this morning
Click to expand...
Click to collapse
Yes I have tried this but receive the following error:
error: source file is larger than target file!
I have tried using different versions of recovery and installer.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit: Your links didn't work properly. Wasn't until I looked at it again that I saw the bit about an unbrick image. Trying it now, fingers crossed...
OK, I have tried using both unbrick methods (unbrick.img and unbrick+ramdisk.img) they completed successfully but didn't resolve the issue (white Amazon logo, pulsing orange light bootloop).
Presently I am trying to inject the prerooted rom's boot.img using the "mediatek_inject firetv2 COM4 boot.img /boot -" command. At 4% so far...
Success! It took about 5 hours to flash the boot.img. Upon restarting the device it loaded to the white Amazon logo with the glowing white power led but this time it didn't reboot (no yellow light). It seemed stuck at this point so I started pressing the keyboard recovery buttons and viola, it opened TWRP. Flashed the latest pre-rooted rom, cleared caches and rebooted. Happily, all my data and apps were unaffected.
A lesson learnt. Don't mess about with technical things when you are drunk!
Thanks for all your help.
m1steron said:
Success! It took about 5 hours to flash the boot.img. Upon restarting the device it loaded to the white Amazon logo with the glowing white power led but this time it didn't reboot (no yellow light). It seemed stuck at this point so I started pressing the keyboard recovery buttons and viola, it opened TWRP. Flashed the latest pre-rooted rom, cleared caches and rebooted. Happily, all my data and apps were unaffected.
A lesson learnt. Don't mess about with technical things when you are drunk!
Thanks for all your help.
Click to expand...
Click to collapse
Thanks have wondered about magisk as more apps check root. Obviously a no no
Sent from my SM-G955F using Tapatalk
m1steron said:
Success! It took about 5 hours to flash the boot.img. Upon restarting the device it loaded to the white Amazon logo with the glowing white power led but this time it didn't reboot (no yellow light). It seemed stuck at this point so I started pressing the keyboard recovery buttons and viola, it opened TWRP. Flashed the latest pre-rooted rom, cleared caches and rebooted. Happily, all my data and apps were unaffected.
A lesson learnt. Don't mess about with technical things when you are drunk!
Thanks for all your help.
Click to expand...
Click to collapse
Just think you did some Magisk v12 on non-Unlocked Bootloader FTV test. I am just glad you at least got your device back to a normal state. Took one for the modding scene. Thanks drunken M1steron. I know sober M1steron would not have approved.
Hello m1steron,
Thxs for sharing your experience.
Krgds
m1steron said:
Success! It took about 5 hours to flash the boot.img. Upon restarting the device it loaded to the white Amazon logo with the glowing white power led but this time it didn't reboot (no yellow light). It seemed stuck at this point so I started pressing the keyboard recovery buttons and viola, it opened TWRP. Flashed the latest pre-rooted rom, cleared caches and rebooted. Happily, all my data and apps were unaffected.
A lesson learnt. Don't mess about with technical things when you are drunk!
Thanks for all your help.
Click to expand...
Click to collapse
Trying to flash boot.img the forth time using mediatek inject command... It stucks at around 50% each time. Should i try it again and again or leave it?
Servet83 said:
Trying to flash boot.img the forth time using mediatek inject command... It stucks at around 50% each time. Should i try it again and again or leave it?
Click to expand...
Click to collapse
Did it finish? I left mine flashing for most of the day so I don't know if it paused at 50% or not.
m1steron said:
Did it finish? I left mine flashing for most of the day so I don't know if it paused at 50% or not.
Click to expand...
Click to collapse
No, it didn't finish. Yesterday it stopped at 67%. Don't know what to do alternatively...is it cause im using a windows pc?
Servet83 said:
No, it didn't finish. Yesterday it stopped at 67%. Don't know what to do alternatively...is it cause im using a windows pc?
Click to expand...
Click to collapse
I used Windows 10 on an old works laptop. Could you describe all the steps you are taking?
m1steron said:
I used Windows 10 on an old works laptop. Could you describe all the steps you are taking?
Click to expand...
Click to collapse
1. Connect to FTV using a2a usb cable
2. start handshake
3. Power on Box (handshake complete)
4. Start mediatek inject command (continue with 'y')
5. Wait writing filesystem...
Here are 2 Screenshots. One for the install_firetv2_recovery process and the other dor mediatek inject process.
Servet83 said:
1. Connect to FTV using a2a usb cable
2. start handshake
3. Power on Box (handshake complete)
4. Start mediatek inject command (continue with 'y')
5. Wait writing filesystem...
Here are 2 Screenshots. One for the install_firetv2_recovery process and the other dor mediatek inject process.
Click to expand...
Click to collapse
Thanks, are you using the extracted boot.img from the same pre-rooted rom that is installed on your device?
Also, this is where I got the information from: https://forum.xda-developers.com/fire-tv/development/firetv-2-unbrick-image-t3313349/page3
rbox should be able to help.
m1steron said:
Thanks, are you using the extracted boot.img from the same pre-rooted rom that is installed on your device?
Also, this is where I got the information from: https://forum.xda-developers.com/fire-tv/development/firetv-2-unbrick-image-t3313349/page3
rbox should be able to help.
Click to expand...
Click to collapse
Yes, i am using the same boot.img (5.2.1.1).
How did u solve the error "source file larger target file" while running the install recovery batch?
Trying to get in touch with rbox. Thank u so far!
Servet83 said:
Yes, i am using the same boot.img (5.2.1.1).
How did u solve the error "source file larger target file" while running the install recovery batch?
Trying to get in touch with rbox. Thank u so far!
Click to expand...
Click to collapse
I didn't so I tried the below:
m1steron said:
OK, I have tried using both unbrick methods (unbrick.img and unbrick+ramdisk.img) they completed successfully but didn't resolve the issue (white Amazon logo, pulsing orange light bootloop).
Presently I am trying to inject the prerooted rom's boot.img using the "mediatek_inject firetv2 COM4 boot.img /boot -" command. At 4% so far...
Click to expand...
Click to collapse
m1steron said:
I didn't so I tried the below:
Click to expand...
Click to collapse
Didn't work for me i remember that usb debugging was turned of before bricking the device and maybe thats the issue now...
What you need:
TWRP (thanks to ZVOX): htt ps://mega.nz/#!SWYwAQAb!bbLnex8yhT7tyBTdTMr2wIS-tzITjg5VMJ_p1msXenQ
DM-Verity Disabler: ht tps://mega.nz/#!6bIAACia!WtfQf6DRAJVLjxhW0Gp3J4HQv_VstpGYm_7RoVkVhsQ
copy links, and remove space in "ht tps".
Tested with A505F/DualSim (me) and A505FN (tested by muhamet).
Steps to install TWRP:
Enable oem unlock in the developer settings.
Power off phone. Hold 'vol-up' and 'vol-down' then plug your phone to PC. You will enter download mode.
Long press 'vol-up' to unlock bootloader. Phone will reboot and wipe data and remove google accounts.
When phone reboots, shut down phone, unplug from PC and wait until screen is off. Hold 'vol-up' and 'power' to enter stock recovery. Do a factory reset AND wipe cache. Then select to "reboot to bootloader" to go to download mode again.
Plug phone again, and in AP select the TWRP (3.3.1-3) provided by ZVOX. go tto options and untick/unselect auto reboot.
Click on start. When its done, hold 'vol-down' and 'power' until screen goes black then IMMEDIATELY STOP HOLDING 'vol-down' and SWITCH to 'vol-up' before Samsung logo appears, WHILE KEEPING YOUR FINGER ON 'power'. VERY IMPORTANT TO BOOT IN TWRP!! keep holding no matter what until you get TWRP screen.
Swipe to allow modifications, then press Mount > System.
Go to Advance > File Manager, then scroll to /system/system/ and scroll to "recovery-from-boot.p" and rename it to "recovery-from-boot.p.bak"
Flash Disable_Dm-Verity_ForceEncrypt zip in TWRP.
Format Data partition. Type "yes" to confirm.
you can boot to system now. TWRP is permanent. GG
Thanks bro . I will provide feedback definitely
What about A505FN? The other guides that I tried, they didn't really go well.
King-V said:
What about A505FN? The other guides that I tried, they didn't really go well.
Click to expand...
Click to collapse
This works for FN,F model.I haw FN model and use this twrp
Video from flashing process
King-V said:
What about A505FN? The other guides that I tried, they didn't really go well.
Click to expand...
Click to collapse
It works with any model. (Although I only tested with A505F/Dual Sim).
If anybody tests this and reports success, reply in thread to add your device as compatible.
Does it works with South American Models!?
---------- Post added at 02:43 AM ---------- Previous post was at 01:52 AM ----------
Stuck in here, samgung Galaxy A50 SM-A505GT - I am using a virtual machine with microsoft on my MAC.
Tried Odin: 10.6, 10.7, 10.13.1 and nothing works!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This method fully works. Thanks
alejandroteen said:
Stuck in here, samgung Galaxy A50 SM-A505GT - I am using a virtual machine with microsoft on my MAC.
Tried Odin: 10.6, 10.7, 10.13.1 and nothing works!
Click to expand...
Click to collapse
What is wrong with that picture? is it stuck at "REQ_CLOSE"? Be more specific, and we will be able to help you.
alejandroteen said:
Does it works with South American Models!?
---------- Post added at 02:43 AM ---------- Previous post was at 01:52 AM ----------
Stuck in here, samgung Galaxy A50 SM-A505GT - I am using a virtual machine with microsoft on my MAC.
Tried Odin: 10.6, 10.7, 10.13.1 and nothing works!
Click to expand...
Click to collapse
1 unlock bootloader,then you will able t flash twrp
here, please... stuck in here
https://cdn1.imggmi.com/uploads/2019/9/11/15dd8876d157a249cac474465956114b-full.png
alejandroteen said:
https://cdn1.imggmi.com/uploads/2019/9/11/15dd8876d157a249cac474465956114b-full.png
Click to expand...
Click to collapse
??
immortalized2018 said:
??
Click to expand...
Click to collapse
I am stuck in here, that is the image i want to show you guys...
Worked perfectly for me.
Any way to get root after this.
I tried with magisk flashed the zip but after booting to system it vanished any way to make it work please help.
Will this work for the a505gn/ds as well?
aerithanne said:
Will this work for the a505gn/ds as well?
Click to expand...
Click to collapse
You have options for unlocking bootloader??
what about magisk?
Now i downloading the stock AP to reset and install this TWRP to have root.
BRICKED
hello ,
i flashed the Twirp file provided .
now im stuck cant boot recovery , no fast boot , not detected using ADB .
MY stock firmware is "EGY-A505FDDU2ASH4-20190910164711" i was on and working fine with last update . model A505F/DS 128 giga wirth 4 gigs rams
now its just starting android and restart the bootloop
when i boot to recovery only get TWIP splash screen with no other options not even swipe to unlock
help is very much appreciated. thanks in advance
mohamed1144 said:
hello ,
i flashed the Twirp file provided .
now im stuck cant boot recovery , no fast boot , not detected using ADB .
MY stock firmware is "EGY-A505FDDU2ASH4-20190910164711" i was on and working fine with last update . model A505F/DS 128 giga wirth 4 gigs rams
now its just starting android and restart the bootloop
when i boot to recovery only get TWIP splash screen with no other options not even swipe to unlock
help is very much appreciated. thanks in advance
Click to expand...
Click to collapse
Put the usb cable t pc hold the power and volume down,whens screen go off, hold volume up and down same time amd tou will be on dawnload mode.Flash firmware through odin.
---------- Post added at 11:28 PM ---------- Previous post was at 10:41 PM ----------
This is standard procedure for flashing TWRP.
Gaet TWRP (without magisk) and Zvonx TWRP
And multidisabler
Folow procedure
You have procedure if you stuck at TWRP screen:
Put the usb cable t pc,power and volume down,when screen go black,volume up and down and you are on downloading mod.
---------- Post added at 11:29 PM ---------- Previous post was at 11:28 PM ----------
TWRP and multidisabler flashing procedure,this procedure is for Gaet TWRP (without magisk) and Zvox TWRP
You have and procedure for stuck at TWRP screen:
Put usb cable t pc and phone,power and volume down,release when screen go off and volume up and down button press you are on download mode
muhamet said:
Put the usb cable t pc hold the power and volume down,whens screen go off, hold volume up and down same time amd tou will be on dawnload mode.Flash firmware through odin.
---------- Post added at 11:28 PM ---------- Previous post was at 10:41 PM ----------
This is standard procedure for flashing TWRP.
Gaet TWRP (without magisk) and Zvonx TWRP
And multidisabler
Folow procedure
You have procedure if you stuck at TWRP screen:
Put the usb cable t pc,power and volume down,when screen go black,volume up and down and you are on downloading mod.
---------- Post added at 11:29 PM ---------- Previous post was at 11:28 PM ----------
TWRP and multidisabler flashing procedure,this procedure is for Gaet TWRP (without magisk) and Zvox TWRP
You have and procedure for stuck at TWRP screen:
Put usb cable t pc and phone,power and volume down,release when screen go off and volume up and down button press you are on download mode
Click to expand...
Click to collapse
Thanks !you are a life saver
it worked ! i flashed to stock again .no idea if this TWRIP edition is stable for daily usage . i wanted Twrip so i can root
mohamed1144 said:
Thanks !you are a life saver
it worked ! i flashed to stock again .no idea if this TWRIP edition is stable for daily usage . i wanted Twrip so i can root
Click to expand...
Click to collapse
https://forum.xda-developers.com/ga...ecovery-twrp-galaxy-a50-t3916199/post80244309
This one is for rooting
So i've been wanting to root this phone for a while now, and i just cant seem to flash twrp, yes its the correct file, yes its the correct command, yes im using SDK developer tools, but i just cant seem to flash it. heres the error btw
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
says its flashing but its not. ive left it on for like an hour or so. please help? anyone?
SzymcioYa said:
So i've been wanting to root this phone for a while now, and i just cant seem to flash twrp, yes its the correct file, yes its the correct command, yes im using SDK developer tools, but i just cant seem to flash it. heres the error btwView attachment 5920083
says its flashing but its not. ive left it on for like an hour or so. please help? anyone?
Click to expand...
Click to collapse
Hi, try using the
Code:
fastboot boot twrp.img
command instead
Jan Skokan said:
Hi, try using the
Code:
fastboot boot twrp.img
command instead
Click to expand...
Click to collapse
oh, i actually solved it actually. im running an amd ryzen 5 5600x and thats the issue. i fixed it using a regedit tweak, thanks tho
Jan Skokan said:
Hi, try using the
Code:
fastboot boot twrp.img
command instead
Click to expand...
Click to collapse
Also, i have a question. So i've rooted my xiaomi note 5 with magisk, and i wanted to do the same with my main phone, and now i cant unlock my phone because i dont want my data lost (the apps are the most important and i have all my other data backed up) and i came across mediatekbootloaderunlock and im just wondering is it patched or does it still work? because if it works then im definitely rooting my phone.
SzymcioYa said:
Also, i have a question. So i've rooted my xiaomi note 5 with magisk, and i wanted to do the same with my main phone, and now i cant unlock my phone because i dont want my data lost (the apps are the most important and i have all my other data backed up) and i came across mediatekbootloaderunlock and im just wondering is it patched or does it still work? because if it works then im definitely rooting my phone.
Click to expand...
Click to collapse
Hi, I'm sorry but I can't confirm or deny this because I don't own a Xioami device anymore You just have to try it 🫤
Jan Skokan said:
Hi, I'm sorry but I can't confirm or deny this because I don't own a Xioami device anymore You just have to try it 🫤
Click to expand...
Click to collapse
It actually worked, and now my phone is unlocked. So i flashed orangefox and i cant seem to boot into it. When i try the combination (power and volume+) it just vibrates and goes back to system. i tried fastboot boot but it didnt work.
SzymcioYa said:
It actually worked, and now my phone is unlocked. So i flashed orangefox and i cant seem to boot into it. When i try the combination (power and volume+) it just vibrates and goes back to system. i tried fastboot boot but it didnt work.
Click to expand...
Click to collapse
This has happened to me too. What I did was that after several attempts I managed to get into twrp and reboot the phone into fastboot via twrp. I know it sounds logical, but try to connect the phone to the computer and hold the power off button and click the volume up button several times. Try it several times, it always works. Via Orange Fox, reboot the phone into fastboot and install the stock rom when you are in fastboot mode. I hope it helps you.. good luck
Jan Skokan said:
This has happened to me too. What I did was that after several attempts I managed to get into twrp and reboot the phone into fastboot via twrp. I know it sounds logical, but try to connect the phone to the computer and hold the power off button and click the volume up button several times. Try it several times, it always works. Via Orange Fox, reboot the phone into fastboot and install the stock rom when you are in fastboot mode. I hope it helps you.. good luck
Click to expand...
Click to collapse
ill try and ill keep you updated
Jan Skokan said:
This has happened to me too. What I did was that after several attempts I managed to get into twrp and reboot the phone into fastboot via twrp. I know it sounds logical, but try to connect the phone to the computer and hold the power off button and click the volume up button several times. Try it several times, it always works. Via Orange Fox, reboot the phone into fastboot and install the stock rom when you are in fastboot mode. I hope it helps you.. good luck
Click to expand...
Click to collapse
nope, doesnt work, tried it tho