Related
So I got this Tablet a few days ago and wanted to get root. It came with the 3.2 update already installed so I read around and saw I needed to downgrade the os, root, flash recovery, then flash a rom via recovery.
I plan to install this rom:
http://forum.xda-developers.com/showthread.php?t=1290318
It is basically stock acer 3.2 with root. Which is all I really want.
I followed method 2 here:
http://forum.xda-developers.com/showthread.php?t=1276227
After booting and installing the unstable version to be able to get root, then I did the adb push for cwm and itsmagic. Wasn't sure what to do after this so I rebooted. (I tried downloading the acer recovery installer but my market would not let me type anything in with all the force closes)
So after reboot I am unable to get adb to show it as a listed device and everytime I try to copy the rom over I need I get an error "Cannot copy *filename* The device has either stopped responding or has been disconnected"
In frustration I figured I didn't get cwm installed properly so I downloaded the apk from the web and installed it via dropbox. It let me apply it and actually boot into recovery.
I powered off and tried getting back in but my pc still fails to see the device listed in adb or save files to it via the basic windows file explorer.
I'm currently letting the update install itself (I flashed back the original recovery via acer recovery installer) don't know if this will fix it.
If anyone can help, it would be much appreciated.
Update:
It upgraded me to 3.1 but I still can't save anything to my tab (atleast the fc's are gone). It doesn't list anything on my tab just shows 0 files. Not sure how to get this fixed.
Update:
I did a factory reset. Now it detects it and I'm able to save the rom to it. I did the root, and flashed cwm thru acer recovery installer. (avoiding adb entirely). However when I'm in there now it says "E:Can’t mount /sdcard". Read some folks are throwing it on a usb drive and flashing it that way.(BTW I put the rom zip on the root file directory, not on the external SD). Will update if it works or not.
*RESOLVED*
Got it working. It installed off the USB thumb drive just fine. Was able to install the 3.2 root Rom mentioned earlier. Everything is working as it should. Able to read and write to and from the device now. Showing superuser in my apps. Now to start removing the crap Acer put on there
This is just in case anyone runs into the same problem. Took a few hrs but its working nice
Basically I suggest this if you wish to just install the the 3.2 stock rom via cwm
1.) Since the unstable flash doesn't clear your data, download and install everything you will need first. ex: Acer Recovery Installer, Iconia Root. Put the rom on the root drive and/or a thumb drive.
2) Flash the downgrade.
3) Run the Iconia Root tool.
4) Run the Acer recovery installer (since you'll have root now) and reboot to recovery
5) Flash the rom. If it doesn't detect it try it on a usb thumb drive. Done
I always put my ROMS on an external microSD. That is the only thing I use my SD card for, and as far as I can tell is always the recommended place to store your ROMS for updating. In the root of the microSD card.
Glad to hear you got it working though.
Hey guys, I am having some issues flashing roms through CWM as well as rerooting.
A bit of backround info
Device: GT-P7510
Started with latest OTA stock rom. I was wanting to use titanium backup to uninstall some bloatware.
Rooted successfully following the wifi only version forum post on how to root.
Did what i wanted, but now i wanted more.
Decided to try to get Jellybean on my device. Loaded into CWM - flashed - successful.
Now i ran into the issue of no flash support - needed for school work i do on my tablet. Tried to follow guide on installing flash.. did not work, tried the titanium backup method as well with no prevail.
Decided to flash back to ICS. I chose the CM9 ROM.
Loaded into CWM - wiped data / cache/ dalvik / Installed rom from SD card - flashed successfully
I noticed that my home button was not working. so after another data wipe etc. and re flash of the rom it did.
I then could not get googleplay to function just kept getting server error no matter what i tried. I tried installing apk from the web. did not work. and tried loading gapps.zip through odin. Installed other google apps that did work, just not google play..
So i was like holy hell. what to do now. Tried installing another ICS ROM ( the one that mimics jellybean)... It fails instantly after unloading package or something of that nature. I tried about 3 different roms and get the same issue.
So i then followed the guide to unroot - it required flashing the stock ROM through CWM . I tried this but got a status 7 error. Not really sure what that was so i found another guide.
The alternative guide had me load the original ROM for the device via odin. Worked great!!! I thought i was in clear sailing. Updated to the OTA ICS ROM. And then went to follow the root guide again. It acted as if it was rooted, but upon reboot option in CWM it says root access might have been lost.. do you want to fix. I tried both no and yes. Reguardless i do not gain root.
I tried flashing other roms through CWM - they all fail instantly ( not with any specific error messages ) just says aborted.
Any idea on what i may be doing wrong?
What version of cwm u using ?
5.5.0.4 works best for our tabs coz he has not got some verification for unsigned zips something like that .
Hmm i think the problem is when u updated ota it took your root away so i would suggest flashing cf-root again via odin
Just guessing though really strange, perhaps back up data on sd card and format it too i know its a pain but could help aswell
;/
Sent from my GT-P7500 using xda app-developers app
I was on 6. something. So that may be my issue.
I did try an older version v4.0.0.4 which was included in the guide i used but that did not seem to work either. I will download that version and see what happens.
As far as flashing cf-root. I am going to do a forum search but the method i used used the file Samsung_galaxy_tab_10.1_root.zip through CWM.
it is always risk to Odin back to stock and update OTA I have bricked 2 android devices by doing this .......once you install custom roms it is always better not to install official update ..... ur device is not rooted properly just go to unrooted stock rom if possible and later get root.zip then try rooting ur tab using it .......and this might help ...... forum.xda-developers.com/showthread.php?t=1474971..........
CHEERS
HIT THANKS BUTTON IF I HAVE HELPED
Rooting Kindle Fire HDX 7 32gb 3rd Gen Fire OS 13.3.2.1
Airplane Mode ON WIFI Off
Kindle Fire ADB Composite Drivers must be installed to working PC
In KFHDX Settings
Set Enable ADB - ON
Set Apps from unknown sources - ON
Faznx's KF-HDX Toolkit v0.95
https://www.androidfilehost.com/?fid=95832962473395302
KFHDX ToolKit v0.95.zip
MD5: 3C1D7DB855E54A39BF2FD59BE6ABA9DC
SHA-256: 614A0D077BEC8B85F6D6B377D2D18EB719AB9ED15B08B41CD5 8968BEED653C0C
Rooted KFHDX using Towelroot in above toolkit. - No Issues
Then applied:
1> SuperSU v2.14 installer in Faznx's KF-HDX Toolkit v0.95 - No Issues
2> Over the air update blocker and re-enabler for all current rootable versions in Faznx's KF-HDX Toolkit v0.95 - No Issues
Airplane Mode ON WIFI Off
Use adb to install ES File Explorer
http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
ADB install (installs application) -- adb install c:\com.estrongs.android.pop.apk - No Issues
Checked in ES File Manager to make sure I had root.
Next rename the /system/etc/security/otacerts.zip file - one issue - resolved
Even though I ran the disable OTA updates, I am concerned that some post I have read said their system was update even though they renamed.
I think now it's possible they get around us by running an MD5 hash on files in that folder and compare to the hash they store for that version.
The better idea may be to move that file out of that folder. I did just that.
Here are the directions to rename:
see the contents of that folder with adb shell ls -Ral /system/etc/security
Example:
C:\Users\davcam\AppData\Local\Android\sdk\platform-tools>adb shell ls -Ral /system/etc/security
/system/etc/security:
drwxr-xr-x root root 2014-02-07 04:23 cacerts
-rw-r--r-- root root 1337 2014-02-07 04:23 otacerts.zip
Before you can rename this file you must set the \ and \system file systems to r/w - then you can rename or mv the file.
When completed, change \ and \system file systems back to ro
Next : Safestrap
https://goo.im/devs/Hashcode/thor/safestrap/
I tried Safestrap-Thor-3.72.apk and it did not seem to work. I unistalled recovery and Safestrap-Thor-3.72.apk.
I was able to successfully install Safestrap-Thor-3.75-os3.2.4-B02.apk, install recovery, boot into recovery, backup up stock, create a new rom slot,
change to that Rom slot and restore stock backup into that slot.
Now on startup i get the Safestrap screen.
One thing I noticed was that the stock values for the rom slots are a little small, so keep that in mind.
Thanks to everyone on XDA Forums, especial to EncryptedCurse for the terse, meaningful tips., Faznx's KF-HDX Toolkit v0.95, Geohot's Towelroot,
hashcode0f's Safestrap, OTA disable, and Supersu.
Current Status:
Using a copy of stock on a somewhat larger partition, no otacerts.zip file
Next steps:
0> Thank and donate to the developers I mentioned above.
1> Airplane mode OFF, wifi ON , register with Amz
1.1> Get GAPPS installed on this copy of stock I'm booting into
2>to see if possible to load a CM11 image into one or my bran new slots.
Question: If Amazon were able to push an update to me, would I just be able to recover to my stock image and move on?
Thanks for the help and education!
reggie9 said:
Next steps:
0> Thank and donate to the developers I mentioned above.
1> Airplane mode OFF, wifi ON , register with Amz
1.1> Get GAPPS installed on this copy of stock I'm booting into
2>to see if possible to load a CM11 image into one or my bran new slots.
Question: If Amazon were able to push an update to me, would I just be able to recover to my stock image and move on?
Thanks for the help and education!
Click to expand...
Click to collapse
Dont try to install CM11 with Safestrap!! It wont work, and you will brick your device! You have to install TWRP 2.8.4.0 and only then you can install CM11 safely.
If your device get FW 4.X.X, you lost root and ability to install custom roms through custom recovery (Safestrap, TWRP 2.8.4.0) - and only way to get the root again is rollback from 4.x.x to 3.2.7-8 (by amazon tech support), and then you can use only Safestrap, so no CM11 or Nexus 2.0.4 ROMs for FW 3.2.7-8!
Edit: Looks like jeryll already said it.
jeryll said:
Dont try to install CM11 with Safestrap!! It wont work, and you will brick your device! You have to install TWRP 2.8.4.0 and only then you can install CM11 safely.
If your device get FW 4.X.X, you lost root and ability to install custom roms through custom recovery (Safestrap, TWRP 2.8.4.0) - and only way to get the root again is rollback from 4.x.x to 3.2.7-8 (by amazon tech support), and then you can use only Safestrap, so no CM11 or Nexus 2.0.4 ROMs for FW 3.2.7-8!
Click to expand...
Click to collapse
Thanks! I appreciate the heads up. Any idea where I can locate TWRP 2.8.4.0 for this device?
Sorry - Found it here: http://forum.xda-developers.com/kindle-fire-hdx/development/recovery-twrp-2-8-1-0-thor-t2986004
Reggie9
jeryll said:
Dont try to install CM11 with Safestrap!! It wont work, and you will brick your device! You have to install TWRP 2.8.4.0 and only then you can install CM11 safely.
If your device get FW 4.X.X, you lost root and ability to install custom roms through custom recovery (Safestrap, TWRP 2.8.4.0) - and only way to get the root again is rollback from 4.x.x to 3.2.7-8 (by amazon tech support), and then you can use only Safestrap, so no CM11 or Nexus 2.0.4 ROMs for FW 3.2.7-8!
Click to expand...
Click to collapse
Everything has seemed pretty clear up to now, but I am trying to understand what I should do next? I have Safestrap 3.72 beta installed and I'm running off of a backup of stock running in ROM-Slot 1.
Do I need to wipe rom slot one, remove recovery and uninstall Safestrap? Then install TWRP? Can I take a backup of my current ROM Slot one and use it in TWRP. I am looking for a good install post or video for installing TWRP 2.8.4.0 on KFHDX. It appears that TWRP does not use the concept of ROM slots but actually wipes the main system (that has been backed up to the builtin recovery area?) Then installs an image on the main system? I understand basically what Safestrap is doing, but not TWRP.
reggie9 said:
Everything has seemed pretty clear up to now, but I am trying to understand what I should do next? I have Safestrap 3.72 beta installed and I'm running off of a backup of stock running in ROM-Slot 1.
Do I need to wipe rom slot one, remove recovery and uninstall Safestrap? Then install TWRP? Can I take a backup of my current ROM Slot one and use it in TWRP. I am looking for a good install post or video for installing TWRP 2.8.4.0 on KFHDX. It appears that TWRP does not use the concept of ROM slots but actually wipes the main system (that has been backed up to the builtin recovery area?) Then installs an image on the main system? I understand basically what Safestrap is doing, but not TWRP.
Click to expand...
Click to collapse
You are on compatible firmware so dont complicate things so much If you want to understand how Safestrap or TWRP itself work - google is your friend, you will certainly find plenty of information about how things works: here is little introduction about differencies between them, not all of course...
And here is little something from ggow about how to install twrp and remove safestrap, you can later find safestrap slot image files in data/media/safestrap - and after you have functional TWRP 2.8.4.0, you can delete safestrap folder safely and free some space taken by these image files
Normal way is how TWRP 2.8.4.0 works (IMHO) - only one big playground managed by mighty TWRP recovery always accessible by shortcut when you made mistake and need to repair something...
Safestrap uses multiple slots for (un)modified stock roms simply because is too dangerous to play with stock rom on systems with locked bootloader, so you can play with slot rom instead of stock where small mistake leads to different types of bricks - some repairable, some not
And yes you can make a backup of your current ROM and use it later with TWRP, but here comes catch, Safestrap only backups system and data partition, not boot (contains kernel), so I recommend after you install your preferred CM11 or Nexus 2.0.4, restore only DATA part of your backup
jeryll said:
You are on compatible firmware so dont complicate things so much If you want to understand how Safestrap or TWRP itself work - google is your friend, you will certainly find plenty of information about how things works: here is little introduction about differencies between them, not all of course...
And here is little something from ggow about how to install twrp and remove safestrap, you can later find safestrap slot image files in data/media/safestrap - and after you have functional TWRP 2.8.4.0, you can delete safestrap folder safely and free some space taken by these image files
Normal way is how TWRP 2.8.4.0 works (IMHO) - only one big playground managed by mighty TWRP recovery always accessible by shortcut when you made mistake and need to repair something...
Safestrap uses multiple slots for (un)modified stock roms simply because is too dangerous to play with stock rom on systems with locked bootloader, so you can play with slot rom instead of stock where small mistake leads to different types of bricks - some repairable, some not
And yes you can make a backup of your current ROM and use it later with TWRP, but here comes catch, Safestrap only backups system and data partition, not boot (contains kernel), so I recommend after you install your preferred CM11 or Nexus 2.0.4, restore only DATA part of your backup
Click to expand...
Click to collapse
jeryll - Thanks for the the thoughtful response - will study this. - reggie9
hey guys i found custom ROM for d858hk version which is here
http://bbs.gfan.com/android-7892224-1-1.html
can be translated through Google but we need someone to explain to us in details.
I might able to help, I can read Chinese
let me know if you want any explanations.
it's based on lollipop 20d
- v1.0 LED not working, and this v2.0 fixed the problem
- rooted, superSU v2.46
- once you flashed the ROM, no need to flash the ROOT again
- busybox is in the system and no app not there
- works on D857 858 and 858HK
- it's a LIGHT version, there are functions that are deleted, like weather widget for example
- including deleted app inside the ROM, and could recover yourself
- app can write data to external SD card
- split view works for 3rd party app
- smart cover function removed, user can download the "deleted app" and put back into the system to get it working
deleted apps
http://pan.baidu.com/s/1mg86X6o
HOW TO FLASH
FOR D858HK
1. ROOT
2. install TWRP 2.8.1.0
3 Reboot to TWRP 2.8.1.0 and upgrade it to 2.8.5.1
4. Flash ROM using this newest TWRP
D857 and D858
1. ROOT
2. download build.prop.zip, extract, using ES explorer to replace the one in "system" folder
3 flash D858HK 's TOT (http://bbs.gfan.com/android-7502599-1-1.html)
4.install TWRP 2.8.1.0
5. Reboot to TWRP 2.8.1.0 and upgrade it to 2.8.5.1
6. Flash ROM using this newest TWRP
Do "double wipe" after flashing the ROM, otherwise might have FC messages
Thanks alot i think this will help ...will try it now
but can we install twrp when in lollipop as i am now on lollipop
any ideas?
maybe these
http://bbs.gfan.com/android-7677473-1-1.html
one click Recovery installation
need to be rooted
1. extract files to computer
2 connect phone
3 turn on usb debugging
4. run Recovery.bat
---------------------------------------
old temp way, didn't say if it works on L or only KK
http://bbs.gfan.com/android-7727191-1-1.html
So...can any of you fluent Chinese speakers/readers help with the actual downloading of the ROM? It seems the rom is available at http://pan.baidu.com/s/1mg86X6o, but I get a little overloaded and can't figure out how to download from there. It seems to want me to log in, but I can't figure out if there's a non-login download ability lurking somewhere?
Do you have some screenshoots ?
Two things. First, I had the wrong link before. Correct one is: http://pan.baidu.com/s/1sjoKe4l. Second, I realized the reason is that the zip file is over 1GB and they force you to a "download butler". So the login thing is related to copying that file into your (QQ, for example) account and then you could download the file from there.
If anyone with a D858HK is interested, I was able to install this custom rom on my phone without any problems. I followed steps elsewhere to root (the one click version) and install TWRP. The rom is basically a slim version of the standard lollipop rom. If you end up deciding to install this, be aware that the Google Contact Sync app is not included within the rom and you'll need to also download the "deleted apps" zip file mentioned in the same post (link in OP). In the "deleted apps" zip, you'll want to grab the Gooogle Contact Sync apk and install that ... otherwise you can't get your contacts copied to the new rom. There were a bunch of other apks, but this one the only one so far that seemed like it shouldn't have been removed from the rom.
FYI, here are the version details of the rom:
Android version: 5.0.1
Baseband version: MPSS.DI.3.0.c6.2-00011-M8974AAAAANAZM-1
Kernel version: 3.4.0
Build number: (some chinese)1121561(more chinese)
Software version: D858HK20d-HKG-XX
So in total its not worth installing it? But anyway, thanks for your report!
silencer1979 said:
So in total its not worth installing it? But anyway, thanks for your report!
Click to expand...
Click to collapse
I guess that depends on how easy it is to remove LG's bloatware and whether or not you need all/any of it. I personally didn't care for it anyway. But yeah, other than that, nothing special about the rom.
There were a bunch of other apks, but this one the only one so far that seemed like it shouldn't have been removed from the rom.
i believe there's a thread somewhere in this forum (http://bbs.gfan.com/forum-1508-type-10913.html) regarding d858 MIUI, could someone confirm? Thanks
Edit
twrp flashh from MM
has anyone successfully flashed TWRP from an MM rom i tried it and i got bricked and i cant seem to find one for MM only for LP
Lg g3 d858hk
Hey, did you install? There is a problem or not? All programs worked fluently?
xdax1 said:
let me know if you want any explanations.
it's based on lollipop 20d
- v1.0 LED not working, and this v2.0 fixed the problem
- rooted, superSU v2.46
- once you flashed the ROM, no need to flash the ROOT again
- busybox is in the system and no app not there
- works on D857 858 and 858HK
- it's a LIGHT version, there are functions that are deleted, like weather widget for example
- including deleted app inside the ROM, and could recover yourself
- app can write data to external SD card
- split view works for 3rd party app
- smart cover function removed, user can download the "deleted app" and put back into the system to get it working
deleted apps
http://pan.baidu.com/s/1mg86X6o
HOW TO FLASH
FOR D858HK
1. ROOT
2. install TWRP 2.8.1.0
3 Reboot to TWRP 2.8.1.0 and upgrade it to 2.8.5.1
4. Flash ROM using this newest TWRP
D857 and D858
1. ROOT
2. download build.prop.zip, extract, using ES explorer to replace the one in "system" folder
3 flash D858HK 's TOT (http://bbs.gfan.com/android-7502599-1-1.html)
4.install TWRP 2.8.1.0
5. Reboot to TWRP 2.8.1.0 and upgrade it to 2.8.5.1
6. Flash ROM using this newest TWRP
Do "double wipe" after flashing the ROM, otherwise might have FC messages
Click to expand...
Click to collapse
My LG-D858HK phone hard bricked:
What happened/how I hard bricked the phone. I'd already rooted the phone with Marshmallow and then tried to flash phone TWRP by (mistakenly) using https://play.google.com/store/apps/details?id=b007.autorecd858hk when it hard bricked the phone. Now, the phone screen is black/blank and blue/red LED light flashing.
In addition, my PC doesn't recognise phone when plugged into USB port/s. Pop-up on PC screen says; “The last USB device you connected to this computer malfunctioned and windows do not recognize it.” And in Device Manager, I see a ‘yellow triangle’ next to LGE Platform Android Composite USB Device Driver.
I tried different methods to go into download mode and I’m not sure if any worked. Because, obviously, I can’t see anything on the phone screen to carry out procedures to fix phone in download mode. Moreover, I’m not even sure if the phone goes into download mode apart from a sound made from PC and the pop-up straight after.
PC always recognised phone when plugged into USB port/s before it was hard bricked.
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