Hi everyone!
This is my first post, hope there is a solution.
I have Samsung Galaxy A3 [A300FU].
I wanted to get rid of branded firmware, so I've found stock ROM here: mrcrab.net/stockrom/sm-a300fu.html and flash it with Odin and it was ok.
Then I wanted root, so I've followed this guide: trueandroid.com/root-samsung-galaxy-a3-sm-a300f-easy-guide and now, whenever I restart the phone, it boots to the screen with yellow text: set warranty bit : recovery (file_1.jpg). Then it goes to the screen with opened green robot (file_2.jpg) and after I choose: reboot system now, it loads to OS normally.
How to fix it?
Ok guys, I don't know what happened, but I've managed to save the day
What I did was connecting my phone to KIES and select Firmware Update and Initialization from the Tools menu. It wipes all the data so be prepare for that. This helped to get rid of the yellow text on the screen while booting, but the phone still kept booting to the recovery mode.
Then I've installed TriangleAway from this thread: forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114 but it didn't seems to work (and, by the way, it doesn't support my phone). I've also installed SuperSU from Play Store, and also didn't work, so I've uninstalled both and reboot the phone. And guess what - it booted normally, straight to the OS.
Magic.
Sooo, the solution I've provided above wasn't what I needed, because I insist to have my device rooted. That's why I started once again.
I've installed stock ROM, rooted it and the result was the same (yellow text and booting through recovery mode).
I've customized the build with 360 Security (there's many apps out there which allow uninstalling system software and bloatware). Then I've installed Team Win Recovery Project through Odin meant for Samsung Alpha (teamw.in/project/twrp2) and that was it. No more yellow text or booting to the recovery mode. Shiny clean rooted A3.
locovibe said:
Sooo, the solution I've provided above wasn't what I needed, because I insist to have my device rooted. That's why I started once again.
I've installed stock ROM, rooted it and the result was the same (yellow text and booting through recovery mode).
I've customized the build with 360 Security (there's many apps out there which allow uninstalling system software and bloatware). Then I've installed Team Win Recovery Project through Odin meant for Samsung Alpha (teamw.in/project/twrp2) and that was it. No more yellow text or booting to the recovery mode. Shiny clean rooted A3.
Click to expand...
Click to collapse
Hello, I recently bought a A3 as well and im quite dissapointed to see there are no custom roms or forums dedicated to the A Series (A3, A5, A7). Ive been itching to root and install a custom rom seeing the stovk is starting to slow down a A LOT! Could you help me out by guiding me through the bloatware removal as i dont want to uninstall something i shouldn't
Sent from my SM-A300FU using XDA Free mobile app
locovibe said:
Sooo, the solution I've provided above wasn't what I needed, because I insist to have my device rooted. That's why I started once again.
I've installed stock ROM, rooted it and the result was the same (yellow text and booting through recovery mode).
I've customized the build with 360 Security (there's many apps out there which allow uninstalling system software and bloatware). Then I've installed Team Win Recovery Project through Odin meant for Samsung Alpha (teamw.in/project/twrp2) and that was it. No more yellow text or booting to the recovery mode. Shiny clean rooted A3.
Click to expand...
Click to collapse
You flashed a custom recovery meant for Galaxy Alpha on Galaxy A3? Doesn't doing that bricks the device? I'm having the same problem too.
Sent from my SM-A300F using XDA Free mobile app
Ok, here are the steps:
Download the newest formware from sammobile and install it through Odin.
Turn off the phone and boot into recovery, wipe cache and run factory reset. I don't know if it's meaningful, but I did it and that's it.
Set up the device and turn on USB Debugging in Developer options. To make those options appear you have to open Settings, then About Phone and keep tapping on Build Number.
Download root files for your model from here: autoroot.chainfire.eu, run Odin, install it and turn on the phone.
I assume you'll get those messages like I did "Set warranty bit : recovery" and the phone will keep booting into recovery mode and from there you can boot into OS. But it's unconvenient, so I've download the TWRP files to get rid of it. At first I used files for Alpha but last time I've install recovery meant for S4 Qualcomm and it worked as well (here: twrp.me/devices/samsunggalaxys4internationalqualcomm.html).
It didn't brick my phone. It keeps going. I don't know much about devices so I didn't hesitate I just wanted root for Macrodroid
Oh and I have SD Maid to freeze unwanted apps, like preinstalled ones and those I don't use, like android e-mail app (I prefer Gmail), stock calendar S Planner (I have Sunrise, it syncs with iCal), KNOX, live wallpapers, some widgets, Fliboard, S Voice, Google Movies Music Games Newsstand Books Hangouts, Google+, Hancom Office.
* Download Odin 3.09 from here: odindownload.com (second link)
Is TWRP 2.80 Working?
locovibe said:
Ok, here are the steps:
Download the newest formware from sammobile and install it through Odin.
Turn off the phone and boot into recovery, wipe cache and run factory reset. I don't know if it's meaningful, but I did it and that's it.
Set up the device and turn on USB Debugging in Developer options. To make those options appear you have to open Settings, then About Phone and keep tapping on Build Number.
Download root files for your model from here: autoroot.chainfire.eu, run Odin, install it and turn on the phone.
I assume you'll get those messages like I did "Set warranty bit : recovery" and the phone will keep booting into recovery mode and from there you can boot into OS. But it's unconvenient, so I've download the TWRP files to get rid of it. At first I used files for Alpha but last time I've install recovery meant for S4 Qualcomm and it worked as well (here: twrp.me/devices/samsunggalaxys4internationalqualcomm.html).
It didn't brick my phone. It keeps going. I don't know much about devices so I didn't hesitate I just wanted root for Macrodroid
Oh and I have SD Maid to freeze unwanted apps, like preinstalled ones and those I don't use, like android e-mail app (I prefer Gmail), stock calendar S Planner (I have Sunrise, it syncs with iCal), KNOX, live wallpapers, some widgets, Fliboard, S Voice, Google Movies Music Games Newsstand Books Hangouts, Google+, Hancom Office.
* Download Odin 3.09 from here: odindownload.com (second link)
Click to expand...
Click to collapse
I like what you did!. Is the TWRP 2.80 or twrp2 for Samsung Alpha working in Samsung A3? I mean to say that if you go to recovery by pressing Vol Up _Power _ Home Butttons, does TWRP Recovery appears? Or the stock recovery appears and you solve only the recovery and yellow problem?
If the TWRP Recovery Appears then you can install custom roms, backup your system and data. This will be a great job done by you and many owners of Samsung A3 will be thankful to you. Please Reply because I want to test it on my mobile
Etnad07 said:
I like what you did!. Is the TWRP 2.80 or twrp2 for Samsung Alpha working in Samsung A3? I mean to say that if you go to recovery by pressing Vol Up _Power _ Home Butttons, does TWRP Recovery appears? Or the stock recovery appears and you solve only the recovery and yellow problem?
If the TWRP Recovery Appears then you can install custom roms, backup your system and data. This will be a great job done by you and many owners of Samsung A3 will be thankful to you. Please Reply because I want to test it on my mobile
Click to expand...
Click to collapse
Well, it seems it only solved yellow text and can't boot into recovery at all. It can't be that way! So!
I've installed unbranded software once again and was waiting to update to Lollipop via Kies. But it took so long that I couldn't resist to root, but I did it differently this time. I've found KingRoot app which works like a charm. Just download the apk [mmgr.myapp.com/myapp/Kingroot/webapp_kingroot/image/KingRoot-4.1.0.249-release-nolog-201505211812_105001.apk] from [kingroot.net/down#root], run it and voila! No hassle, no Odin. After rooting there will come up two apps: Kinguser and some app in Asian. I've uninstalled the second one - it cleans memory and stuff. Stock recovery stays untouched and booting is normal.
Hi Everyone!
I Hope There Is a Solution....
I have galaxy a500g running with stock lollipop and I need to install a custom rom so I flashed TWRP_2.8_SM-A500-LL.img and booted into recovery once it booted into recovery it struck at set warranty bit:recovery and struck at recovery loop....is there a way to install a working custom recovery for galaxy a500g
Thanks in advance
Related
hi all.
I'm really struggling here and dont know what to do.
Ive been rooted and have been running EchoeRom 4.4.2 with an Alucard kernel thats been brilliant.
Last week i seemed to have lost a load of apps - which in hindsight were some that i had moved to SD card. I couldnt update the apps, reinstall or reinstall via titanium.
Long story short I used mybackup after reflashing the ROM but started getting some f/c
A factory reset didnt help so I decided to unroot and flash stock 4.3 NG8 firmware then re-root through ODIN. This is something I/ve done before - but now it wont work.
Ive tried CF Autoroot but the Superuser app says missing Binary.
If I try to get to recovery it just reboots again after 2 seconds to normal startup. I have tried just flashing CWM and TWRP recoveries both with auto reboot checked then un-checked with a battery pull about 20 times.
On 2 or 3 occasions I've had the CF red splash screen for rooting, but that seems to finish with a 'restoring stock recovery' message and i'm back to square one after it reboots.
Ive tried a different superuser app but it couldnt update the binary.
I even attempted a different rooting method with Towelroot but after accessing the APK it starts phone not supported.
Im really stumped now and have no root and no access to any recovery. If i could get to recovery Id be ok.
I dont know if ive destroyed root forever - when updating on ODIN I usually get a PASS message so i suspect something bootloader related may be overwriting the installed recovery ?
Any clues folks !!
1. Reflash android 4.4.2 GN8 firmware through ODIN
2. Download this FILE and copy it to your phone (in SDCard better)
3. Go to DOWNLOAD MODE and Flash TWRP (for example) through ODIN.
4. Remember the combination for go TWRP is a lil difficult and sometimes your phone will reboot normally. This happend to me too:
- Power off your device completely.
- Press and hold Volume Up, Home and Power buttons simultaneously.
- Release the buttons when the phone’s screen flickers or the TWRP Recovery logo blue appears.
- That is it, after you release buttons, you will be taken to the main Recovery Mode menu..
5. Install the file of the step 2 with TWRP.
6. Done
sorry for delay in responding.
I was about to follow your advice, when at random when using the phone it flashed up a message..
something along the lines of 'unauthorised activity detected - reboot phone'
I did this only to go straight into Philz recovery and since then have been able to load a backup, reflash a new rom and all seems ok.
Very strange !
Thanks for the help though.
Robin
Hello guys.
I have successfully ported TWRP 3.0.0-0 for our Smart Prime 6.
It's 100% working !!
There are NO BUGS !! :good:
DOWNLOAD
NEW LINK: DOWNLOAD
________________________________________
How to install
Via app:
1) Download TWRP 3.0.0-0 from the link above and place it on internal storage of your phone.
2) Download Flashify app from Google Play Store.
3) Open Flashify app.
4) Grant root permissions.
5) Click "Recovery image" and then click "Choose a file"
6) Navigate to the folder where you placed TWRP 3.0.0-0 and choose the .IMG file.
7) Press "Yup!" button and wait.
8) After a while the phone will require reboot. So click "reboot" button.
9) Phone will reboot and automatically boot into TWRP, so you can press reboot to system.
10) Enjoy!
Special thanks to Oneb1t for modded .fstab file! :highfive:
edit: you can use Flashfire app too instead of Flashify, but it's not recommended, because the latest version of the Flashfire app is not flashing properly.
Brilliant! Thank you so much! Do you know any custom ROM what is better than the factory ROM?
There is no custom ROM for this phone yet.
But I'm trying to make LITE ROM.
Adreno306™ said:
There is no custom ROM for this phone yet.
But I'm trying to make LITE ROM.
Click to expand...
Click to collapse
Do you think it's easier/possible to adapt a ROM from a similar device like say, the Alcatel
Pop 2 (5) Premium ? I don't know if there's any ROM for that phone tho, but since it's branded as Alcatel you might get more support from the community here than by using Vodafone's name.
Hello, Demonlord6.
I have tried to make a stock flashable ROM via dumping the system folder and the boot.img file, but without success.
It does not boot properly.. when I tried to flash it without dalvik/system wipe everything was as before.
When I tried to wipe /system and dalvik first and then flash the ROM, it causes bootloop.
So now I'm trying to fix this issue..
I don't know where the problem is.
So when this issue will be solved I will try to build a ROM from Alcatel phones with same specs.
Adreno306™ said:
Hello, Demonlord6.
I have tried to make a stock flashable ROM via dumping the system folder and the boot.img file, but without success.
It does not boot properly.. when I tried to flash it without dalvik/system wipe everything was as before.
When I tried to wipe /system and dalvik first and then flash the ROM, it causes bootloop.
So now I'm trying to fix this issue..
I don't know where the problem is.
So when this issue will be solved I will try to build a ROM from Alcatel phones with same specs.
Click to expand...
Click to collapse
Hey, Andreno306
I don't know much about Rom's in that level of expertise I'm afraid :/ but I did some digging and came across this simple tutorial on XDA:
http://forum.xda-developers.com/showthread.php?t=2387941
I imagine it does not work for every single device out there, at least not with modifying stuff after, but it might be a good starting point I think, in fact I would try to actually make one myself had I a working PC currently at home. But even if I did I had no way of testing it because this is currently my daily driver phone.
Just wanted to say that I'm also very interested in getting a slim ROM for this device. I can't offer any expertise I'm afraid! Just wanted to show that there are people interested in your project.
:highfive:
Stock Kernel
Thanks, it works great.
This is little off-topic but does anyone has the stock kernel, i flashed NeoKernel but it is not that good and i forgot to make a backup do can anyone please link me to the stock kernel?
vojta_horanek said:
Thanks, it works great.
This is little off-topic but does anyone has the stock kernel, i flashed NeoKernel but it is not that good and i forgot to make a backup do can anyone please link me to the stock kernel?
Click to expand...
Click to collapse
I have one
https://mega.nz/#!tMJD3B4T!f6m2ELYCVupqGCcN2aGbkrNzEqijLu7au-7usEfeVL0
But I recommend to restore it with the flashify app, because that's how the backup was made.
If, for some reason, you don't/can't restore it, then you can always try Sugar on the PC which basically restores everything to factory settings (recovery, kernel, etc, it all gets reset)
Demonlord6 said:
I have one
But I recommend to restore it with the flashify app, because that's how the backup was made.
If, for some reason, you don't/can't restore it, then you can always try Sugar on the PC which basically restores everything to factory settings (recovery, kernel, etc, it all gets reset)
Click to expand...
Click to collapse
Restored and my phone keeps turning off after boot(once i saw the turn off screen, other times it just vibrates at boot screen), isnt it the wrong file? (flashed wia flashify)
I was able to restore the boot from TWRP (lucky i made a backup this time)
vojta_horanek said:
Restored and my phone keeps turning off after boot(once i saw the turn off screen, other times it just vibrates at boot screen), isnt it the wrong file? (flashed wia flashify)
I was able to restore the boot from TWRP (lucky i made a backup this time)
Click to expand...
Click to collapse
Sorry there about the bootloop but glad u could restore it from TWRP, maybe it was because we have different ROM versions ?
Demonlord6 said:
Sorry there about the bootloop but glad u could restore it from TWRP, maybe it was because we have different ROM versions ?
Click to expand...
Click to collapse
I got this one: http://www.needrom.com/download/vodafone-smart-prime-6-vf-895n-debloatedclean-stock/#
vojta_horanek said:
I got this one: http://www.needrom.com/download/vodafone-smart-prime-6-vf-895n-debloatedclean-stock/#
Click to expand...
Click to collapse
Yeap, that's not the same version as my ROM, mine is not 130FNN etc. Maybe that's why it didn't work
Enviado do meu GT-S5280 através de Tapatalk
Sorry for the stupid question but... does it works on Smart Prime 7 too?
Has anyone installed that linked ROM? It seems to be what we are looking for... a slim debloated rom.
I presume we need to be rooted, install this TWRP, then flash that ROM?
It mentions unlocking the bootloader, I dont think I've seen any info anywhere about unlocking the bootloader.
Can anyone give a quick lowdown on all the steps required to install that ROM please?
Hi everyone, I discovered that Elephone Trunk and Smart Prime 6 have (almost) identical specs: https://www.devicespecifications.com...ison/c584481c6
So it would be great to "port" (or build ?) the official Nougat-OmniROM for Trunk to VF-895N: http://dl.omnirom.org/trunk/
Last but not least, here's official Vodafone Smart Prime 6 sources: Vodafone_Smart_prime_6_20150413.tar.xz
TWRP for vodafone smart max 4 990N (coolpad 8890u).
I tried this recovery image for vodafone smart max 4 990N (coolpad 8890u).
The phone is in a bootloop state. I think i have usb debugging enabled already.
So, in fastboot mode i can see the device in my pc in adb fastboot cmd.
Im trying to ''fastboot boot recovery.img" but it stops in ''booting..''.
Dont know whats the problem but for sure i can not find a specific twrp image for this device.
If i enter fastboot oem device-info it says ''(bootloader) Device unlocked: true''.
Any ideas ?
hi i was wondering if you could share how you did this or if you can make one for the Vodafone smart n9 (VFD720) it would help a lot of people out looking for this
Needed to root a Vodafone Smart Prime 6 (VF 895N) (got it from a friend because it became unresponsive from all the updated google play stuff ) to get linux-deploy running. Just wanted to leave a big thank you here for Adreno306 for his TRWP 3.0.0-0. it did the job very well!
Only the procedure to get it installed differed quite a bit for me, since Flashify is no longer available.
I wanted to preserve boot and just flash trwp to recover, what worked quite well.
The first thing I did was to boot the phone manually in recovery mode (Power+Vol up) and reset it to factory settings from there. It takes a little while. Then follow the setup, go to phone settings, enable developer mode and set usb debugging. If "unlock oem" is not available there, reboot into recovery again, set unlock there and reboot into bootloader.
The prerequisites are adb and fastboot, both must work. Means adb devices and fastboot devices must show the phone. What can make problems under win10 as it sometimes does not detect the phone in bootloader mode. An actual google usb driver is needed, as provided by google.
For me adb worked well, but when rebooted into bootloader with adb reboot bootloader, fastboot didnt detect the phone. With the phone still connected, the windows device manager showed an unknown device with and exclamation mark (!). Right click, install driver, select driver manually, select driver from device list, mark all devices (first entry) and click "disk", then point to the usb driver director and select "ADB fastboot driver". ( A more comprehensive description is available here )
Once adb and fastboot detect the device, it is time to prepare it. Boot to system (normal operation) first. Make sure that the TRWP 3.0.0-0.img is renamed to trwp.img and then
adb reboot bootloader
fastboot devices
fastboot oem unlock
fastboot boot trwp.img
Now the phone should show the trwp menu, set it up to root the phone and install SuperSU. Reboot into bootloader and
fastboot flash recovery trwp.img
fastboot reboot
Verify with adb reboot recovery, you should see trwp now. Reboot to system.
Now finally go into the app selector, start SuperSU, and root the phone. SuperSu uses trwp recovery mode to install its image and root is done.
Again, big thanks for providing the TRWP image!
Adreno306™ said:
Hello guys.
I have successfully ported TWRP 3.0.0-0 for our Smart Prime 6.
It's 100% working !!
There are NO BUGS !! :good:
DOWNLOAD
NEW LINK: DOWNLOAD
________________________________________
How to install
Via app:
1) Download TWRP 3.0.0-0 from the link above and place it on internal storage of your phone.
2) Download Flashify app from Google Play Store.
3) Open Flashify app.
4) Grant root permissions.
5) Click "Recovery image" and then click "Choose a file"
6) Navigate to the folder where you placed TWRP 3.0.0-0 and choose the .IMG file.
7) Press "Yup!" button and wait.
8) After a while the phone will require reboot. So click "reboot" button.
9) Phone will reboot and automatically boot into TWRP, so you can press reboot to system.
10) Enjoy!
Special thanks to Oneb1t for modded .fstab file! :highfive:
edit: you can use Flashfire app too instead of Flashify, but it's not recommended, because the latest version of the Flashfire app is not flashing properly.
Click to expand...
Click to collapse
Hi, I would like to try your tutorial but I can't root this phone (which is an important step in the tutorial), is there any way someone could help me??
Thanks
I wanted to install Xposed on my Samsung Galaxy Note 4 SM-910C Version 6.0.1
So through a lot of "googling" i found a way to root my phone with Chainfire through Odin Flashing, which worked (Root Checker confirmed it so i guess it worked)
After a few more google searches i managed to flash TWRP Recovery through Odin which also worked.
Here's where i went a bit off instructions: After TWRP i went on to attempt installing Xposed Firmware on to my phone. I downloaded An Xposed APK from the instruction website i was reading but it also required i download another Xposed file which i went on to install through TWRP recovery. This particular File i donwloaded from another source since the one on the instruction site's mirror was broken, it was Armv7 and it matched what my phone's hardware required.
After installing this Xposed file on TWRP i went on to reboot my phone but before this TWRP told me that root access wasn't installed and prompted me to install SuperSU, this really confused me since Root checker said that i already had Super User turned On. I don't know why but i actually agreed to it and installed it AGAIN.
My phone rebooted until the animated Samsung Logo came on and it never moved past that for about an hour.
Right now all i can do is pull my battery out and boot recovery, i tried factory resetting my phone and wiping everything. now what happens is TWRP keeps on prompting me to install SuperSU and now it doesn't even reach the animated Samsung logo it always gets stuck on the [Samsung GALAXY Note 4].
I'm sorry if i posted this text wall but i thought these details might help, can anyone help me?
Edit: Sorry for the title don't know how to change it, fyi i wanted to change that to "Messed up trying to install Xposed Framework"
SpoonOjiisan said:
I wanted to install Xposed on my Samsung Galaxy Note 4 SM-910C Version 6.0.1
So through a lot of "googling" i found a way to root my phone with Chainfire through Odin Flashing, which worked (Root Checker confirmed it so i guess it worked)
After a few more google searches i managed to flash TWRP Recovery through Odin which also worked.
Here's where i went a bit off instructions: After TWRP i went on to attempt installing Xposed Firmware on to my phone. I downloaded An Xposed APK from the instruction website i was reading but it also required i download another Xposed file which i went on to install through TWRP recovery. This particular File i donwloaded from another source since the one on the instruction site's mirror was broken, it was Armv7 and it matched what my phone's hardware required.
After installing this Xposed file on TWRP i went on to reboot my phone but before this TWRP told me that root access wasn't installed and prompted me to install SuperSU, this really confused me since Root checker said that i already had Super User turned On. I don't know why but i actually agreed to it and installed it AGAIN.
My phone rebooted until the animated Samsung Logo came on and it never moved past that for about an hour.
Right now all i can do is pull my battery out and boot recovery, i tried factory resetting my phone and wiping everything. now what happens is TWRP keeps on prompting me to install SuperSU and now it doesn't even reach the animated Samsung logo it always gets stuck on the [Samsung GALAXY Note 4].
I'm sorry if i posted this text wall but i thought these details might help, can anyone help me?
Edit: Sorry for the title don't know how to change it, fyi i wanted to change that to "Messed up trying to install Xposed Framework"
Click to expand...
Click to collapse
Since you have twrp, find supersu.zip and save into sdcard. Flash supersu.zip to gain root access. And for xposed. Make sure it is arm-sdk23.
Sent from my SM-G925F
Rosli59564 said:
Since you have twrp, find supersu.zip and save into sdcard. Flash supersu.zip to gain root access. And for xposed. Make sure it is arm-sdk23.
Sent from my SM-G925F
Click to expand...
Click to collapse
Did a quick google search do these work?
download.chainfire.eu/696/supersu/
androidsage.com/2016/04/06/how-to-install-xposed-framework-on-marshmallow-update-with-xposed-v81/
and btw how exactly do i save this into my sd card, i can't get past the product logo.
also thanks a lot for replying man
edit: oh wait if you mean put the zips into an external sd card imma try that now. thx
Hi,
You have to use custom built version of xposed if you use stock or any touchwiz-based-rom(other versions cause bootloops). Just google 'xposed custom build by wanam'. Hope that helps.
Just wanted to clear some stuff up, if i am able to flash supersu.zip and a custom built xposed framework, will my phone stop getting stuck on the product logo?
Because being unable to use my phone normally is my top priority right now. The root and getting xpose3d installed is secondary. I really can't get through the product logo, i hope someone can shed some light on this.
but still, i really appreciate your replies.
SpoonOjiisan said:
Just wanted to clear some stuff up, if i am able to flash supersu.zip and a custom built xposed framework, will my phone stop getting stuck on the product logo?
Because being unable to use my phone normally is my top priority right now. The root and getting xpose3d installed is secondary. I really can't get through the product logo, i hope someone can shed some light on this.
but still, i really appreciate your replies.
Click to expand...
Click to collapse
I strongly believe you flashed wrong xposed zip. There is no arm7 zip by wanam. Hence find arm-sdk23. I think the last 1 is v81.
Supersu is just to give you root access. I won't causing phone to stuck at boot logo. Or do you mean splash screen showing 'samsung galaxy note 4'?
Sent from my SM-G925F
I honestly don't know if that will solve the problem, but you can try it. If it doesn't work, try flashing a rom via recovery or stock rom via odin. Since your data is already gone, I would suggest you wiping your phone completely and flashing a custom rom(I have a SM-N910C as well and I use erobot). Before doing anything, do a full backup in recovery, just in case.
Edit: If you wiped everything in recovery, including /system, that is probably the reason why your phone is stuck. Flash a rom and yo should be good.
Yeah that one exactly, splash screen showing note 4.
so based on what you guys said i should first flash a ROM so it works normally and then i can attempt for Supersu and Xposed arm-sdk23? was watching this random video you think i might have somehow wiped my touchwiz OS? was fiddling around in the Recovery trying to solve it you think i might have done that?
Since you have the same phone and you are using erobot i might go for that same ROM just to be on the safe side, i don't want to try something random.
So first try flashing custom ROM >> SuperSU >> Xposed
That's what i'm going for (i might need confirmation haha kinda scared now, i think i almost bricked my phone)
I believe your phone has to be rooted before you can install a custom rom. I can't tell if your is, but I would do the following:
Make a full backup in twrp>flash supersu again just to make sure the phone has root access>flash a custom rom.zip from your SD card>boot the custom rom, if everything works, flash xposed CUSTOM BUILD(!) and install the xposed installer.apk
I am not a pro, so wait for someone to confirm what I have written. I suggest you to use erobot as your custom rom because of the user-friendly aroma installer. Erobot is prerooted if you choose custom kernel in aroma installer, so keep in mind not to choose stock kernel.
Hope it helped
SuperSU >> Erobot >> Xposed
Ok got it, its currently 23:36 here in the Philippines guess i'm going to sleep, i'm doin that stuff tomorrow confirmation or not.
I can't really afford to throw this phone and it was a gift. So you guys have no idea how much i appreciate your help. /downslash/ Rosli thanks a bunch guys. goodnight
Hi there.. dont worry about the su not install button.. its common as i've aslo rooted my phone through chainfire an it does show me too. Click on do not install..an yeah you have flashed wrong xposed that bricked your phone.. did you backed up your phone before flashing xposed framework? If so try to restore..if not try to get in downloading mod an flash the official framework through odin.. try visiting sammobile.com there tou will get the official framework.. before flashing read ann the instruction or take a look to video tutorial on youtube about how to unbrick phone.. this might help you all the best
Hello dear Community!
It is depressing that my first appearance here is to ask for help, but I am going crazy.
So, I tried to Root my phone via Odin + CF Autoroot klte and it seemed to have been a success.
The root checker also said, that my device was rooted so I went on and installed TWRP to be able to install Lineage OS.
After getting Lineage to work I got a few error messages suddenly popping up, telling me that either "Music had stopped" or other android operation were closed because they didn't work properly.
I tried to install Gapps, it seemed to have worked but I was only able to open and enter the store once, afterwards the store never managed to load and then the app closed itself after starting it.
So I checked again with Root Checker, but this time it gave me an error message, too. It said, that my device was not rooted properly.
I guess this is were I made it worse by deciding to just root the phone again. Obviously, it didn't work either.
Afterwards I thought that maybe installing The Original Android OS and then unrooting the phone would be the best solution to be able to start anew.
First I tried to flah Lineage again and that made it impossible for me to boot the phone. The farthest I got was the setup page, were it tells you Hello and were you can choose a Language, but clicking the arrow key didn't do anything at all.
The recovery mode was also not the TWRP one anymore, but the original Android one and that was a huge problem for me.
Then I tried to flash the 6.1 OS for the S5 (I made sure it was the correct version), but now it is stuck at the "Samsung" screen while it boots.
It never boots though.
I don't know what to do anymore.
Please, I beg you, could anyone help me out?
Don't flash the latest Lineage OS ROM
Hello AsylumAlice u shouldn't have flashed the latest Lineage OS ROM because now u will need a new motherboard for your S5 since the ROM corrupts the MMC chip now u will need to get a new MMC chip or a new Motherboard sorry that your s5 is now hard bricked but when u get it fixed flash the DreamUX S8 Rom it works flawless on my S5 SM-G900i
Yours Sincely
Matty Bourke
mattybourke1994 said:
Hello AsylumAlice u shouldn't have flashed the latest Lineage OS ROM because now u will need a new motherboard for your S5 since the ROM corrupts the MMC chip now u will need to get a new MMC chip or a new Motherboard sorry that your s5 is now hard bricked but when u get it fixed flash the DreamUX S8 Rom it works flawless on my S5 SM-G900i
Yours Sincely
Matty Bourke
Click to expand...
Click to collapse
What are the grounds for your claims?
You needn't root via CF-autoroot if your end goal was to flash lineage. CF autoroot was intended to root stock roms with ease and less effort.
Flash The LATEST, official TWRP via odin then do a FULL WIPE. Wipe system, data, cache and dalvik cache.
From here on, you have two options:
1.) Sideload the LineageOS rom via ADB
2.) Transfer it to the phone's storage via MTP and flash it from TWRP.
As for how to accomplish this, the forum search bar and Google has your back. You need only choose one procedure.
If you need the Play Store, flash gapps AFTER flashing LINEAGE AND BEFORE REBOOTING.
Since you were under the idea that utilizing CF-autoroot was a necessity, I suggest that you re-read this post thoroughly before actually putting it into practice.
Kinloch said:
What are the grounds for your claims?
You needn't root via CF-autoroot if your end goal was to flash lineage. CF autoroot was intended to root stock roms with ease and less effort.
Flash The LATEST, official TWRP via odin then do a FULL WIPE. Wipe system, data, cache and dalvik cache.
From here on, you have two options:
1.) Sideload the LineageOS rom via ADB
2.) Transfer it to the phone's storage via MTP and flash it from TWRP.
As for how to accomplish this, the forum search bar and Google has your back. You need only choose one procedure.
If you need the Play Store, flash gapps AFTER flashing LINEAGE AND BEFORE REBOOTING.
Since you were under the idea that utilizing CF-autoroot was a necessity, I suggest that you re-read this post thoroughly before actually putting it into practice.
Click to expand...
Click to collapse
Thank you so much for your fast reply!
-> I flashed the newest Version for klte via Odin, but I can't get into the boot mode.
I only am able to enter the download mode. What can I do now?
Flash TWRP via odin again, untick the Auto-Reset option of Odin first. Then try booting to recovery via long holding the power, home and volume up button simultaneously without releasing any of the buttons until you successfully see the TWRP splash screen.
If that still doesn't work, reboot to recovery via adb from download mode. You need the adb and the usb drivers for your device.
If that still doesn't work, you might have flashed an incompatible version of TWRP.
Kinloch said:
Flash TWRP via odin again, untick the Auto-Reset option of Odin first. Then try booting to recovery via long holding the power, home and volume up button simultaneously without releasing any of the buttons until you successfully see the TWRP splash screen.
If that still doesn't work, reboot to recovery via adb from download mode. You need the adb and the usb drivers for your device.
If that still doesn't work, you might have flashed an incompatible version of TWRP.
Click to expand...
Click to collapse
Thank you so much, it worked perfectly!
I can now start my phone and use it normally.
But the Root Checker still says:
"Sorry! Root access is not properly installed on this device.
Device: SM-G900M
Android version: 7.1.2"
What should I do from now on?
Thank you so much for your help (agaiN).
And as for why I used the auto-root, well I just followed a guide that I found, it only had positive reviews so I assumed it was a correct tutorial.
AsylumAlice said:
Thank you so much, it worked perfectly!
I can now start my phone and use it normally.
But the Root Checker still says:
"Sorry! Root access is not properly installed on this device.
Device: SM-G900M
Android version: 7.1.2"
What should I do from now on?
Thank you so much for your help (agaiN).
And as for why I used the auto-root, well I just followed a guide that I found, it only had positive reviews so I assumed it was a correct tutorial.
Click to expand...
Click to collapse
just flash supersu in twrp
AronFerr said:
just flash supersu in twrp
Click to expand...
Click to collapse
I thought about doing that, but wasn't sure how exactly to proceed and what Version to install.
I downloaded SuperSU v.2.82 and put it on my internal storage.
Just install over TWRP the same way that I Installed Lineage and Gapps I suppose?
I guess if it doesn't work out, I just follow the steps from above again and retry?
Thank you so much. I feel like in idiot in this situation.
AsylumAlice said:
I thought about doing that, but wasn't sure how exactly to proceed and what Version to install.
I downloaded SuperSU v.2.82 and put it on my internal storage.
Just install over TWRP the same way that I Installed Lineage and Gapps I suppose?
I guess if it doesn't work out, I just follow the steps from above again and retry?
Thank you so much. I feel like in idiot in this situation.
Click to expand...
Click to collapse
yes just flash it but no wipes
My device is a J530F (J5 2017).
Im using custom roms for years, but now im deparated with a situation that I don’t understand.
I decided to back to my StockRom (J530FXXS7CTG2_J530FBTU7CTG1_BTU) via Oddin because the CustomRom im using doesn’t have GooglePlayServices (crDroidAndroid-10.0-20210418-j5y17lte-v6.17 flashed with OrangeFox Recovery). PS: This CustomRom is 64Bits, do u think that changed or damaged something in my device?
So, for the 1st time I haved some troubles during the flash stockrom but with few tryes I solved.
When Im back to my StockRom, im surprised to see that my CTS Profile is false and GooglePlay non-certified device. (I think is not normal)…
I rooted the device with magisk for solve this problem and in fact, I solved the Cts Profile but Google Play keeps say that non-certified device. (I searched for Netflix on google play and appear to me so its fine…)
My next step was Reboot in Recovery to flash custom rom. I turn off and turn on with Power, Volume+ and HomeButton. Recovery don’t appear and hes reboot to system mod… So I opened magisk and click Reboot to Recovery but hes turn off and reboot in system mod again… (wtf? -.-‘).
So I have to flashed the TWRP throw Oddin (again) to reboot to recovery. In TWRP I Wiped (Dalvik/Art Cache; System; Data; Internet Storage; Cache) and swipe. Next step was flash new CustomRom (PROMETHEUS_V3_G610X_ARM64 based on A730FXXU6CSJ2)… After flash, when phone rebooted hes show SAMSUNG GALAXY J5 LOGO and then Black Screen (No Samsung Logo) and do not do nothing. (I waited 45min… was the Binary that cause the error??... Was because is 64bits rom? IDK)…
So I repeat all process, go into Download Mode, flashed StockRom, rooted again and flash another CustomRom (PrometheusOneUI V2.0 based on A600FNXXU3BSC5 by Ananjaser1211 @xda-developers That im sure that works on my device because I used during like 1 year). After flash and reboot, the device turn on with Samsung Galaxy J5 and black screen again.
So in conclusion, I cant install custom roms now and don’t know why… somebody can help me?? I don’t tried the same process with OrangeFox twrp because don’t feel that make different but whos know…
Sorry for the long text and bad English, but I did my best for sure…