Warning this is engboot, meaning its not made to be used on day to day basis you may run into some issues. Hopefully we can fix them as we go!
Also do not update supersu through playstore untill we are for sure that it wont mess anything up
Notice from @Chainfire:
Quote:
Originally Posted by Chainfire
I'm just going to leave this here...
SuperSU-v2.74-2-S7QC.zip
You will need:
- Engineering boot images
- Patched version of Odin3 (only AT&T models ?)
- Extract files, and run root.bat with adb on the path
This version of SuperSU is not officially supported. I recommend against updating the APK from the Play Store, or otherwise updating the binaries, unless someone knowledgable has tried before you and confirmed it worked.
If it breaks, you get to keep all the pieces.
First of all thanks to @Chainfire for helping achieve su
I take no responsibility for anything that happens to your device, same goes for everyone that helped.
1. Download Modified Odin and Engineering Kernel
Odin:
MOD EDIT: DOWNLOAD LINK REMOVED
This is special Odin to bypass SHA-256 made by Princecosmy
Second file you will need is
Kernel:
G935A (Edge) MOD EDIT: DOWNLOAD LINK REMOVED
G930A (S7) MOD EDIT: DOWNLOAD LINK REMOVED
This is the engboot
2. Flash the kernel to your phone
a. Boot into download mode (Power, Volume Down, and Home button)
b. Put the Kernel file into AP on Odin
c. Flash, and boot phone
3. Download SuperSU made for our phone, and extract into C:\adb\super
(You're going to need to create the "super" folder)
SuperSU: https://download.chainfire.eu/968/Su....74-2-S7QC.zip
4 Open a command prompt in C:\adb
(Shift right-click in the folder, click "Open command window here")
then navigate to the super folder: type "cd super" into the command prompt
5 Enable USB debugging on your phone, and enter the following command into the command prompt
a. "Root.bat"
(This is what the command prompt will display when finished:
{
"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"
}
6. The program should run, reboot your phone, and you have root!
For the bounty id prefer if you just donate to [email protected] PayPal
Makes more of a lasting impact then what i could do with any of it.
Again thank you to everyone who helped!
We made it fam!
If you are successful after rooting and can give better instructions please let me know!
Do you have access to the FW for the 935A or know where we can find it?
Sent from my VK815 using XDA-Developers mobile app
Done, works in G930A, although the performance is bit slower than usual :/
Does anyone know why?
Enviado desde mi SAMSUNG-SM-G930A mediante Tapatalk
Anyone have the google acount lock that sends a code thru txt msg? Cant get my s7 edge to automatically pick up the code as it should so i cant setup my device. If any ideas please help
Carlos Terán said:
Done, works in G930A, although the performance is bit slower than usual :/
Does anyone know why?
Enviado desde mi SAMSUNG-SM-G930A mediante Tapatalk
Click to expand...
Click to collapse
Usually clearing the cache and letting it rebuild helps. However, like everything else, try it at your own risk. The boot method just came out so there is going to have to be a lot of trial and error before things smooth out. Generally, first adapters (such as yourself) are often the ones that have to try things before anyone knows if it works or not. Best case scenario is that it helps, worst case scenario is saying bye bye to your phone. Then again, anytime you do anything to your phone there is always risk. Good luck and let us know if you try anything that seems to help (or hurt).
icon
okay, not really a noob, but not really an expert, I have been doing this kind of things since the LG ally. but I am baffled, ever since root I cannot for the life of me get this little cyclone icon or the vo)) lte icon to Go Away. I don't have an option for HD voice in any setting, nor do I have a setting for rcs service. I have been scowling through threads for about 3 hrs, so I have looked for an answer, pretty much my last resort here. any help would be great!!!
odin is getting stuck at setupconnection. I'm on the latest ATT update, could that be the problem? Trying this on the S7 Edge/935A
Need link for working xposed framework for flash fire g935p
Sent from my SM-G935P using XDA-Developers mobile app
---------- Post added at 03:48 AM ---------- Previous post was at 03:48 AM ----------
Also have problem with constant reboot and heating issue with sim car inserted. Busy box works when placed in different directory, and no font changer.
Sent from my SM-G935P using XDA-Developers mobile app
" You have root access but you need to install the app superuser ", can i download that app from my phone
Chocolatetai said:
" You have root access but you need to install the app superuser ", can i download that app from my phone
Click to expand...
Click to collapse
You need to add flash it.
Sent from my SM-G935P using XDA-Developers mobile app
---------- Post added at 04:09 AM ---------- Previous post was at 04:09 AM ----------
Adb
Sent from my SM-G935P using XDA-Developers mobile app
I followed the instructions and got Odin to flash but once my phone reboots it gets stuck at the at&t logo. I can turn it off via vol down+power but once it boots back up it stops at the logo again. Any idea on what to do to either get it back to normal or moving forward?
Cryosx said:
odin is getting stuck at setupconnection. I'm on the latest ATT update, could that be the problem? Trying this on the S7 Edge/935A
Click to expand...
Click to collapse
Make sure you are in download mode
Sent from my SAMSUNG-SM-G935A using Tapatalk
---------- Post added at 10:13 PM ---------- Previous post was at 10:12 PM ----------
kangfat said:
I followed the instructions and got Odin to flash but once my phone reboots it gets stuck at the at&t logo. I can turn it off via vol down+power but once it boots back up it stops at the logo again. Any idea on what to do to either get it back to normal or moving forward?
Click to expand...
Click to collapse
Wipe phone. Guessing you had packages disabled before.
Sent from my SAMSUNG-SM-G935A using Tapatalk
how do I post the picture of my screenshot??
Has anyone tried this method on a Verizon model?
It looks like it works on Sprint, so I'm curious. If not, I can try it tomorrow night when I get home from traveling.
br3w3r said:
Make sure you are in download mode
Sent from my SAMSUNG-SM-G935A using Tapatalk
---------- Post added at 10:13 PM ---------- Previous post was at 10:12 PM ----------
Wipe phone. Guessing you had packages disabled before.
Sent from my SAMSUNG-SM-G935A using Tapatalk
Click to expand...
Click to collapse
Interesting problem here. Restarted the phone for a reason unrelated to the root, and it's stuck at the AT&T logo. Won't boot no matter what. Wiping/Factory restore doesn't fix it either. It'll wipe and reset but never gets to the setup, just stays at the logo. Any ideas?
Symphony0fLife said:
Interesting problem here. Restarted the phone for a reason unrelated to the root, and it's stuck at the AT&T logo. Won't boot no matter what. Wiping/Factory restore doesn't fix it either. It'll wipe and reset but never gets to the setup, just stays at the logo. Any ideas?
Click to expand...
Click to collapse
Reflash the .tar file should fix it and you won't lose anything
Sent from my SAMSUNG-SM-G935A using Tapatalk
I did a wipe cache partition and ready I was solved, now is the normal
For those who were to slow your phone after rooting
Enviado desde mi SAMSUNG-SM-G930A mediante Tapatalk
Tested and working on my SM-G930P
Thank you!
br3w3r said:
Reflash the .tar file should fix it and you won't lose anything
Sent from my SAMSUNG-SM-G935A using Tapatalk
Click to expand...
Click to collapse
No luck. Reflashed the .tar according to the instructions here, still just stays at the AT&T logo.
Symphony0fLife said:
No luck. Reflashed the .tar according to the instructions here, still just stays at the AT&T logo.
Click to expand...
Click to collapse
Do you have the files for a recovery or can you Skype me?
Sent from my SAMSUNG-SM-G935A using Tapatalk
Related
Shabbypenguin and the OUDHS
presents to you
OUDHS Touch CWM-based Recovery 1.0.3.6
for your Samsung Galaxy Note 3
Read this whole post before doing anything
Enjoy
Do not restore a backup until this whole Selinux thing is figured out, its not a bug in this recovery its purely security on all the note 3's
ODIN tar - OUDHS CWM-based Recovery 1.0.3.6
Odin 3.04
Directions:
1) Download the above files
2) Extract Odin3-3.04.zip and copy the tar that you downloaded into the folder
3) Run Odin as an administrator
4) Power your device off
5) Enter download mode
6a) Connect your phone to your computer
6b) Wait for drivers to finish installing if they need to be
7) You should see Odin find your device by marking a blue square in the ID COM box
8) Click on PDA and choose the recovery tar you downloaded
9) Disable auto-reboot
10) When it says finished you need to pull the battery out
11) You need to unplug it and enter recovery
-------------------------------------------------------------------------------------------------------------------------------------------------
Congrats you now have CWM now if you wish to root youll need to follow these instructions
-------------------------------------------------------------------------------------------------------------------------------------------------
SuperSU
Directions:
1) Download the above file
2) Connect your phone and copy them to your phone
3) Once they are copied power down your device
4) Hold volume up and power to enter recovery
5) Navigate recovery by using the volume keys and power to select
6) Choose install zip from sdcard, then pick internal or external (where you copied it to)
7) Scroll down to the Superuser.zip and select it to install
8) IF IT ASKS TO FIX ROOT CHOOSE NO
-------------------------------------------------------------------------------------------------------------------------------------------------
Congrats you are rooted! this procedure will work on any firmware update you guys get
-------------------------------------------------------------------------------------------------------------------------------------------------
Source for hltespr
Credits:
Members of the Official Unloved Devices Hit Squad (OUDHS) for being the best we can for those whom need us
@JoshBeach for testing.
@utkanos & @garwynn for teh crash course on DTB
{
"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"
}
Swipe action/power button not working...
The swipe action nor the power button allow you to select an option. Did you, by chance, post a "Test" version of this??
in teh Op i list the bugs
and version 2 apparently fixed both. fully working now
shabbypenguin said:
in teh Op i list the bugs
and version 2 apparently fixed both. fully working now
Click to expand...
Click to collapse
Ahhh, I see it. Guess we'll have to wait for an update unless there's another way around it I've never heard of (LOL)
christianrance said:
Ahhh, I see it. Guess we'll have to wait for an update unless there's another way around it I've never heard of (LOL)
Click to expand...
Click to collapse
its almsot fully working, recompiling final version
shabbypenguin said:
its almsot fully working, recompiling final version
Click to expand...
Click to collapse
so you're saying we have full root access and functional cwm?? if so, i love you and you sir have a 6-pack of your choice of drink coming as soon as i get home.
pyr0path said:
so you're saying we have full root access and functional cwm?? if so, i love you and you sir have a 6-pack of your choice of drink coming as soon as i get home.
Click to expand...
Click to collapse
indeed, the version currently in OP should work fully now. using supersu 1.65 should net you root. just gutta wait for teh awesome devs to make yall some roms now. there are some things still left needed to be fixed for 4.3/note3 stuff.
dont restore any backups until this selinux stuff is fixed/figured out, luckily its a note 3 issue so all the note 3 people will be working on it .
this is a 4.3 thing but dont have my recovery fix root/remove scripts. you need them for root, when i get some time ill trash that stuff and compile a better version but for now just click no
shabbypenguin said:
indeed, the version currently in OP should work fully now. using supersu 1.65 should net you root. just gutta wait for teh awesome devs to make yall some roms now. there are some things still left needed to be fixed for 4.3/note3 stuff.
dont restore any backups until this selinux stuff is fixed/figured out, luckily its a note 3 issue so all the note 3 people will be working on it .
this is a 4.3 thing but dont have my recovery fix root/remove scripts. you need them for root, when i get some time ill trash that stuff and compile a better version but for now just click no
Click to expand...
Click to collapse
Thank you for your work on this - I am amazed that you rooted the 3 so quickly!
When you say don't restore any backups, are you talking about Nandroids or TiBU files?
Sent from my SPH-L900 using XDA Premium 4 mobile app
PuppyPowered said:
Thank you for your work on this - I am amazed that you rooted the 3 so quickly!
When you say don't restore any backups, are you talking about Nandroids or TiBU files?
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
nandroids, currently there is an issue where selinux flag isnt being set properly when restoring data and then causes bootloops. titanium backup should be good
just to be clear, i didnt root the note 3, you guys had an unlocked bootloader it means rooting was as simple as flashing recovery. i included rooting steps in my OP to help people out.
Great Work Shabby!
Thanks for allowing me to assist you in getting it up and running!
Now we are just waiting on jellybomb 1.0
Sent from my SPH-L900 using Xparent BlueTapatalk 2
Oh crap. Now I'm ma have to listen to Shabby's whining again...
jre1981 said:
Oh crap. Now I'm ma have to listen to Shabby's whining again...
Click to expand...
Click to collapse
nah, wanted to get this out so people could use it. whenever twrp and cwm come out im closing up shop here.
shabbypenguin said:
nah, wanted to get this out so people could use it. whenever twrp and cwm come out im closing up shop here.
Click to expand...
Click to collapse
Weak, stay and hang out a while
I was able to get the recovery to install and also the supersu. Once I rebooted it offered to repair root which I selected no per instructions but when I login to the stock room now after installing recovery and SU I receive an error that SuperSU has stopped and it never opens or allows me to open rooted applications.
---------- Post added at 04:14 AM ---------- Previous post was at 03:59 AM ----------
EJerVJerO said:
I was able to get the recovery to install and also the supersu. Once I rebooted it offered to repair root which I selected no per instructions but when I login to the stock room now after installing recovery and SU I receive an error that SuperSU has stopped and it never opens or allows me to open rooted applications.
Click to expand...
Click to collapse
I also receive a prevention message with a grey shield possibly selinux?
EJerVJerO said:
I was able to get the recovery to install and also the supersu. Once I rebooted it offered to repair root which I selected no per instructions but when I login to the stock room now after installing recovery and SU I receive an error that SuperSU has stopped and it never opens or allows me to open rooted applications.
---------- Post added at 04:14 AM ---------- Previous post was at 03:59 AM ----------
I also receive a prevention message with a grey shield possibly selinux?
Click to expand...
Click to collapse
Just re-run the CF-Auto Root instructions to the T and you should be back in business. I had the same issues and just used CF auto Root and it resolved my issues and I have root with no seen issues so far. Just got the device literally 1hr ago and just finishing up on it. Also if you installed a recovery you will have to ODIN back to OUDHS to get that back. I am holding off until I see some Jellybomb
tandxcstar1 said:
Just re-run the CF-Auto Root instructions to the T and you should be back in business. I had the same issues and just used CF auto Root and it resolved my issues and I have root with no seen issues so far. Just got the device literally 1hr ago and just finishing up on it. Also if you installed a recovery you will have to ODIN back to OUDHS to get that back. I am holding off until I see some Jellybomb
Click to expand...
Click to collapse
I am now in business
---------- Post added at 06:35 AM ---------- Previous post was at 06:04 AM ----------
EJerVJerO said:
I am now in business
Click to expand...
Click to collapse
Anyone know if we can now install busybox successfully without issues with this root?
EJerVJerO said:
I am now in business
---------- Post added at 06:35 AM ---------- Previous post was at 06:04 AM ----------
Anyone know if we can now install busybox successfully without issues with this root?
Click to expand...
Click to collapse
Yes you can, at least I just did without error.
go use TWRP, its a far better recovery
http://forum.xda-developers.com/showthread.php?t=2471564
I have the lastet update for my sprint note 3 and I have rooted once and tripped Knox but now I am not rooted. Can I just use the root method in the general forum? I'm kind of a noon when it comes to rooting.
{
"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"
}
delphox said:
I have the lastet update for my sprint note 3 and I have rooted once and tripped Knox but now I am not rooted. Can I just use the root method in the general forum? I'm kind of a noon when it comes to rooting.View attachment 2702476
Click to expand...
Click to collapse
Unfortunately, NC5 has built-in tools to prevent rooting. Any rooting process done with ODIN or bootloader is disabled on startup (thus, the Android is upgrading grey window). Until someone finds a workaround, I don't think there is a way yet. Which stinks, since I'm stuck in the same boat you are.
TheoRidGEinal said:
Unfortunately, NC5 has built-in tools to prevent rooting. Any rooting process done with ODIN or bootloader is disabled on startup (thus, the Android is upgrading grey window). Until someone finds a workaround, I don't think there is a way yet. Which stinks, since I'm stuck in the same boat you are.
Click to expand...
Click to collapse
What exactly do you mean NC5 has built in tools to prevent rooting? I and tons of other people are all rooted.
Sent from my SM-N900P using Tapatalk
---------- Post added at 06:49 PM ---------- Previous post was at 06:47 PM ----------
delphox said:
I have the lastet update for my sprint note 3 and I have rooted once and tripped Knox but now I am not rooted. Can I just use the root method in the general forum? I'm kind of a noon when it comes to rooting.View attachment 2702476
Click to expand...
Click to collapse
Just use chainfires cfautoroot for the 9005, use Odin 3.09, then Odin twrp 2.7.01, flash superuser and you're good to go.
Sent from my SM-N900P using Tapatalk
---------- Post added at 06:51 PM ---------- Previous post was at 06:49 PM ----------
And use superuser 1.94, it's the latest version..
Sent from my SM-N900P using Tapatalk
tonyevo52 said:
What exactly do you mean NC5 has built in tools to prevent rooting?
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
I booted up my fresh install of NC5
I reboot to upload mode and install TWRP
I let the phone boot normally
I reboot to recovery
I let TWRP install root when rebooting
During bootup, "Andriod is upgrading" gray box pops up, but it doesn't do the usual "Upgrading app x of y" message
I got to the app drawer, open SuperSU
I get the error "There is no SU binary installed"
Same thing happens when I use ODIN Auto Root.
the only explanation I can think of is that the ROM checks for root on bootup, and if it exists, removes Superuser access.
TheoRidGEinal said:
I booted up my fresh install of NC5
I reboot to upload mode and install TWRP
I let the phone boot normally
I reboot to recovery
I let TWRP install root when rebooting
During bootup, "Andriod is upgrading" gray box pops up, but it doesn't do the usual "Upgrading app x of y" message
I got to the app drawer, open SuperSU
I get the error "There is no SU binary installed"
Same thing happens when I use ODIN Auto Root.
the only explanation I can think of is that the ROM checks for root on bootup, and if it exists, removes Superuser access.
Click to expand...
Click to collapse
Did you use CFautoroot first for the 9005? And using Odin 3.09 seems to play best with our phones, you may have just had a bad experience with your attempt, you can always try rjwilcos one click method or micmars nc5 tar and go back to complete stock and try the process again.
Sent from my SM-N900P using Tapatalk
delphox said:
I have the lastet update for my sprint note 3 and I have rooted once and tripped Knox but now I am not rooted. Can I just use the root method in the general forum? I'm kind of a noon when it comes to rooting.View attachment 2702476
Click to expand...
Click to collapse
I'm on NC5 and it took me a while to rot and get twrp to install on my n3. Here is what I did.
I used Odin 3.09
completely turn off phone
go into download mode
flash CFroot n900p to root
Let it go thru a full boot, then turned it off
Go into download mode
flash twrp 2.7.0.0. or 2.7.0.1
that did it for me.
tonyevo52 said:
Did you use CFautoroot first for the 9005? And using Odin 3.09 seems to play best with our phones, you may have just had a bad experience with your attempt, you can always try rjwilcos one click method or micmars nc5 tar and go back to complete stock and try the process again.
Sent from my SM-N900P using Tapatalk
Click to expand...
Click to collapse
I am going to guess that part of my issue was bad flash and part wrong AutoRoot version. I had been using 9005, but the n900p from the below post worked better.
rosystreasures said:
I'm on NC5 and it took me a while to rot and get twrp to install on my n3. Here is what I did.
I used Odin 3.09
completely turn off phone
go into download mode
flash CFroot n900p to root
Let it go thru a full boot, then turned it off
Go into download mode
flash twrp 2.7.0.0. or 2.7.0.1
that did it for me.
Click to expand...
Click to collapse
This also was the working process for me. Honestly, it was the same order I was doing things, but for some reason being patient on the reboots helped. It probably also helped prevent issues with the flashing. Long story short, both these posts helped, and the process listed by rosystreasures is what I would suggest.
[ intro ]
So I recently got the ZU GPe and have been trying few things... and I messed it up bad so things were not even booting properly
I was trying to get it back to factory settings but couldnt find any direct way and no one XDA had any good info to go by...
finally i was able to get a procedure to restore to original Google Play Edition firmware! so here is a step-by-step procedure (with pictures) to restore your phone to original firmware!
[ requirement ]
a PC with USB cable
latest FULL OTA ZIP (I used this one from this thread)
adb drivers installed
[ how-to ]
[ 1 ] Get into Graphical Bootloader
to enter graphical bootloader you can either use the command:
Code:
adb reboot bootloader
OR
power down device connect the USB cable to phone before connecting the other end of cable to PC keep the VOLUME UP button pressed
this will trigger Bootloader mode:
{
"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"
}
[ 2 ] Get into Stock Recovery
while in the Graphical Bootloader use the VOLUME keys to navigate to "Recovery Mode"
now press the POWER button to select it, device will now "reboot" and trigger stock recovery entry
[ 3 ] Reveal Stock Recovery menu
at first you will see:
to combination to "reveal" the Recovery menu is:
POWER button + VOLUME DOWN (first press POWER button and then TAP the VOLUME DOWN key ONCE)
you will now see this:
[ 4 ] Flashing FULL OTA ZIP
in the recovery menu use VOLUME keys to navigate and select using POWER button
now navigate to "apply update from ADB"
select it!
this will enable "adb sideload" mode in recovery on phone
now on you PC (hope that you have downloaded the FULL OTA and kept it easily accessible) enter the following command to send the FULL OTA ZIP via sideload:
Code:
adb sideload [B]PATH-OF-FULL-OTA-ZIP-INCLUDING-ZIP-FILENAME.zip[/B]
e.g.: if u have saved the KOT49H full ota to c:\ then enter:
Code:
adb sideload c:\830f5fda644bfc55f82a4e01fb5fadae4b64fad6.update_1278-8069_R3C_KOT49H.S2.2052_Final_signed.zip
this should start the transfer process to phone and flashing will start once file is fully transferred
after flashing is complete I recommend doing a Factory Reset! THIS WILL WIPE THE INTERNAL SDCARD AND ALL DATA WILL BE LOST! select "wipe data/factory reset"
now select "reboot system now" and device will reboot! thats it!
you will now be on original Google Play Edition firmware!
hope this helps!
regards,
DooMLoRD
Thank you for this. I had gotten to the first picture in step 3 accidentally while trying to guess my way through button combo to unlock bootloader in flashtool. Glad to know there is a way to enter stock recovery if needed. My investment is already paying dividends!
@DooMLoRD I installed Minimal ADB and Fastboot and connected phone and can't figure why it doesn't show up when I type adb devices.
Edit...got it needed to go to device manager and pick drivers.
Would this overwrite the Advanced Stock Kernel with Dual Recovery? I'm looking to get my phone 100% back to stock.
richie138 said:
Would this overwrite the Advanced Stock Kernel with Dual Recovery? I'm looking to get my phone 100% back to stock.
Click to expand...
Click to collapse
Yes!
This will get the device back to complete 100% stock!
Sent from my C6902 using XDA Free mobile app
DooMLoRD said:
Yes!
This will get the device back to complete 100% stock!
Sent from my C6902 using XDA Free mobile app
Click to expand...
Click to collapse
Pretty certain my bootloader remained unlocked after using this process.
DooMLoRD said:
Yes!
This will get the device back to complete 100% stock!
Sent from my C6902 using XDA Free mobile app
Click to expand...
Click to collapse
What about the bootloader unlock status?
adfurgerson said:
Pretty certain my bootloader remained unlocked after using this process.
Click to expand...
Click to collapse
richie138 said:
What about the bootloader unlock status?
Click to expand...
Click to collapse
that we cannot change...
i havent tried an oem relock.... hold on, will test it out now
@adfurgerson thanks for your edit, i had to do the same
richie138 said:
@adfurgerson thanks for your edit, i had to do the same
Click to expand...
Click to collapse
About the drivers? They were the ones from flashtool folder but had to reinstall them for adb to work. I assumed they were there from unlocking bootloader and flashing kernel.
adfurgerson said:
About the drivers? They were the ones from flashtool folder but had to reinstall them for adb to work. I assumed they were there from unlocking bootloader and flashing kernel.
Click to expand...
Click to collapse
I was able to pick Android and then Sony and see the Sony ADB driver. I had installed drivers in the past but it wasn't recognizing my phone right now and your post reminded me :good:
---------- Post added at 04:49 PM ---------- Previous post was at 04:42 PM ----------
DooMLoRD said:
that we cannot change...
i havent tried an oem relock.... hold on, will test it out now
Click to expand...
Click to collapse
If anyone figures out how to re-lock the bootloader they'd be the man
richie138 said:
I was able to pick Android and then Sony and see the Sony ADB driver. I had installed drivers in the past but it wasn't recognizing my phone right now and your post reminded me :good:
---------- Post added at 04:49 PM ---------- Previous post was at 04:42 PM ----------
If anyone figures out how to re-lock the bootloader they'd be the man
Click to expand...
Click to collapse
I would think OEM relock should work?
I would make a backup of the unlocked TA so that you could restore that and have the data wipe that you get with OEM unlock.
blueether said:
I would think OEM relock should work?
I would make a backup of the unlocked TA so that you could restore that and have the data wipe that you get with OEM unlock.
Click to expand...
Click to collapse
dont flash TA from another device!
So I went back to stock GPE and updated to 4.4.3. How would I re root my phone again. Thank you.
Sent from my C6806_GPe using XDA Premium 4 mobile app
EvoYas said:
So I went back to stock GPE and updated to 4.4.3. How would I re root my phone again. Thank you.
Sent from my C6806_GPe using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Same process as for 4.4.2 except you would use advanced stock kernel v.2 this time.
Can't seem to find V.2, is that DoomKernal or a different one?
Sent from my C6806_GPe using XDA Premium 4 mobile app
EvoYas said:
Can't seem to find V.2, is that DoomKernal or a different one?
Sent from my C6806_GPe using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Link http://doomlord.xperia-files.com/do...lLUFkdlN0a0tlcm5lbC1LVFU4NEwuUzEuMzA1Ni12MDI=
From this thread http://forum.xda-developers.com/showthread.php?t=2579005
Thank you, rooted successfully again
Sent from my C6806_GPe using XDA Premium 4 mobile app
My GPE already on 4.4.3 before stuck on Google boot up screen. Already tried the above method for 4.4.2 but encountered an error of "Can't install this package (Tue Dec 10 14:17:53 CET 2013) over newer build (Mon May 12 11:10:10 CEST 2014)". Any ideas how to restore this phone?
acbc2k said:
My GPE already on 4.4.3 before stuck on Google boot up screen. Already tried the above method for 4.4.2 but encountered an error of "Can't install this package (Tue Dec 10 14:17:53 CET 2013) over newer build (Mon May 12 11:10:10 CEST 2014)". Any ideas how to restore this phone?
Click to expand...
Click to collapse
You don't have any backups from 4.4.2? I wonder if you were to flash a custom ROM then try this method would it work? @DooMLoRD do you know?
Another question I have is can a backup be restored to a different device and if so would it put me at risk?
Example... Restore my phone to completely stock 4.4.2 then skip signing into Google accounts and create a backup to share with people needing to restore back from 4.4.3 update.
Hi
I got my MX4 Ubuntu Edition a few days ago , and noticed that there is folder named ( Android )
{
"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"
}
what does it mean? can we have dual boot?
I also have the international version if MX4 , can I install ubuntu?
Sent from my MI 4W using Tapatalk
dual boot would be great
Flashing Ubuntu devices to Android or the other way round is possible but not easy. You have to repartition your device to fit the other OS'es needs. If you want, you can find some information on the internet regarding that.
The Android files are still there because Ubuntu relies on some Android code for harware drivers. That makes it easy for harware vendors to get started.
Sent from my awesome Ubuntu Touch device using the Forum Browser app
nikwen said:
Flashing Ubuntu devices to Android or the other way round is possible but not easy. You have to repartition your device to fit the other OS'es needs. If you want, you can find some information on the internet regarding that.
The Android files are still there because Ubuntu relies on some Android code for harware drivers. That makes it easy for harware vendors to get started.
Sent from my awesome Ubuntu Touch device using the Forum Browser app
Click to expand...
Click to collapse
Hey!
I just want to confirm that I was able to flash Flyme OS 4.0.4A into my MX4 Ubuntu edition instead of Flyme 4.1.1A, and most importantly that I got an OTA upgrade to 4.2.8.2A
So now, I am running Flyme OS 4.2.8.2A Android 4.4.2 on my MX4 Ubuntu Edition.
Mamdou7 said:
Hey!
I just want to confirm that I was able to flash Flyme OS 4.0.4A into my MX4 Ubuntu edition instead of Flyme 4.1.1A, and most importantly that I got an OTA upgrade to 4.2.8.2A
So now, I am running Flyme OS 4.2.8.2A Android 4.4.2 on my MX4 Ubuntu Edition.
Click to expand...
Click to collapse
could you please give me the procedure to flash Flyme OS?
Sent from my MI 4W using Tapatalk
Ibramj12 said:
could you please give me the procedure to flash Flyme OS?
Sent from my MI 4W using Tapatalk
Click to expand...
Click to collapse
I'm in too, otherwise the post about successful flashing is just about nothing, we need a proof!
Ibramj12 said:
could you please give me the procedure to flash Flyme OS?
Sent from my MI 4W using Tapatalk
Click to expand...
Click to collapse
Hi
I've followed the instructions in this link lists.launchpad.net/ubuntu-phone/msg13848.html , but got the Flyme 4.0.4A instead from this link meizufans.eu/forum/topic/751/flyme-os-4-0-4-stable
---------- Post added at 12:24 PM ---------- Previous post was at 12:19 PM ----------
botema said:
I'm in too, otherwise the post about successful flashing is just about nothing, we need a proof!
Click to expand...
Click to collapse
lol
Okay will do that once I arrive home. I will go through the whole procedure again starting from 4.0.4A to upgrade to 4.2.8.2A with some screenshots as a proof
Mamdou7 said:
Hi
I've followed the instructions in this link lists.launchpad.net/ubuntu-phone/msg13848.html , but got the Flyme 4.0.4A instead from this link meizufans.eu/forum/topic/751/flyme-os-4-0-4-stable
---------- Post added at 12:24 PM ---------- Previous post was at 12:19 PM ----------
lol
Okay will do that once I arrive home. I will go through the whole procedure again starting from 4.0.4A to upgrade to 4.2.8.2A with some screenshots as a proof
Click to expand...
Click to collapse
Let's rock! First thing, maybe I'm to stupid - how to get to the fastboot mode? I'm pressing simultaneously Vol-down and Power button, however it switches on and boots in normal mode
botema said:
Let's rock! First thing, maybe I'm to stupid - how to get to the fastboot mode? I'm pressing simultaneously Vol-down and Power button, however it switches on and boots in normal mode
Click to expand...
Click to collapse
lol no, you are not! because I had the same issue before, but actually it's not an issue. It just take longer to get into it rather than the recovery mode.
just make sure it's totally off, then Vol-Down+Power button for longer time then you will get the black screen of fastboot
Mamdou7 said:
lol no, you are not! because I had the same issue before, but actually it's not an issue. It just take longer to get into it rather than the recovery mode.
just make sure it's totally off, then Vol-Down+Power button for longer time then you will get the black screen of fastboot
Click to expand...
Click to collapse
Ok. Step 1 is done: Fastboot mode -> 'fastboot flash recovery recovery.img' -> Recovery Mode. In recovery I see Flyme screen with 2 options: install update(it asks for update.zip in root) or clear data. My question is how to transfer update.zip, while ADB is not seeing my phone?
Can I just use "fastboot update update.zip" from my command line while my phone is attached and staying in fastboot mode??
botema said:
Ok. Step 1 is done: Fastboot mode -> 'fastboot flash recovery recovery.img' -> Recovery Mode. In recovery I see Flyme screen with 2 options: install update(it asks for update.zip in root) or clear data. My question is how to transfer update.zip, while ADB is not seeing my phone?
Can I just use "fastboot update update.zip" from my command line while my phone is attached and staying in fastboot mode??
Click to expand...
Click to collapse
It's very simple. In Windows, just open Computer and you will see the recovery partition showing up, copy and paste it over there and make sure it has the name "update.zip" otherwise it won't detect it. Finally, hit upgrade and wait until it finish.
Mamdou7 said:
It's very simple. In Windows, just open Computer and you will see the recovery partition showing up, copy and paste it over there and make sure it has the name "update.zip" otherwise it won't detect it. Finally, hit upgrade and wait until it finish.
Click to expand...
Click to collapse
I'm under Ubuntu Desktop Seems to be a problem with finding recovery partition to mount. Will try under Windows. Thanks!
---------- Post added at 04:03 PM ---------- Previous post was at 03:52 PM ----------
botema said:
I'm under Ubuntu Desktop Seems to be a problem with finding recovery partition to mount. Will try under Windows. Thanks!
Click to expand...
Click to collapse
I did it! It works! 4.0.4A is running on my MX M461. Now the next step is update to 4.2.8.2
botema said:
I'm under Ubuntu Desktop Seems to be a problem with finding recovery partition to mount. Will try under Windows. Thanks!
---------- Post added at 04:03 PM ---------- Previous post was at 03:52 PM ----------
I did it! It works! 4.0.4A is running on my MX M461. Now the next step is update to 4.2.8.2
Click to expand...
Click to collapse
Excellent! :good:
Good luck with 4.2.8.2A
Mamdou7 said:
Excellent! :good:
Good luck with 4.2.8.2A
Click to expand...
Click to collapse
Did you update as before, same procedure through the recovery mode?
botema said:
Did you update as before, same procedure through the recovery mode?
Click to expand...
Click to collapse
No, I've updated it through the "Upgrade" app within the Android. It will download the 4.2.8.2A OTA file with 415.29MB on the root folder of the device as update.zip, then it will ask to reboot to upgrade.
Mamdou7 said:
No, I've updated it through the "Upgrade" app within the Android. It will download the 4.2.8.2A OTA file with 415.29MB on the root folder of the device as update.zip, then it will ask to reboot to upgrade.
Click to expand...
Click to collapse
Mamdou7 thank you for your answers, there is no need to make a screen shots, while the installation is very simple, just sometimes you have to switch you brain . I figured out to enable dev mode in Flyme and forced recovery boot from ADB, while pressing Vol-up and Power was not helpful. I'm going to try international package, because I'm little bit confused with partially localized interface in Chinese version.
botema said:
Mamdou7 thank you for your answers, there is no need to make a screen shots, while the installation is very simple, just sometimes you have to switch you brain . I figured out to enable dev mode in Flyme and forced recovery boot from ADB, while pressing Vol-up and Power was not helpful. I'm going to try international package, because I'm little bit confused with partially localized interface in Chinese version.
Click to expand...
Click to collapse
Most welcome Botema, I'm so glad that it worked with as well.
Thank you, you saved me great time, although I already went through the same procedure again with the screenshots and I am so confident now with this approach as a success one.
Can't wait to get the latest upgrade to Lollypop version
http://forum.xda-developers.com/meizu-mx/general/meizu-mx4-ubuntu-touch-rom-leaked-t3173934 Look this
Flyme OS 4.5 (based on Lollipop 5.0.1 though, not 5.1 like the M2 Note) is now available for our beloved MX4 !
Here is the international update.zip :
https://mega.co.nz/#!NctWQYyT!G8EaGUsYfvho2VJm69I1kOT0vGalJbdnxqQpKHagjrU
anatole78 said:
Flyme OS 4.5 (based on Lollipop 5.0.1 though, not 5.1 like the M2 Note) is now available for our beloved MX4 !
Here is the international update.zip :
https://mega.co.nz/#!NctWQYyT!G8EaGUsYfvho2VJm69I1kOT0vGalJbdnxqQpKHagjrU
Click to expand...
Click to collapse
Official?
So, i had my phone off for awhile, and on my bed, i was using my sim to try to network unlock an old tablet. tablet wont unlock, so i go to put the SIM back in and reboot the phone, after 5 min i notice i am stuck in a bootloop. so ive tried using ADB to boot into recovery, and i cant....and ive tried getting into recovery via hardware....no possible way???? so basically i have a phone, that when put into fastboot, wont connect to ADB, and that means wont boot into recovery....totally stuck in a loop, been half an hour now. can anyone help me??? ive tried using a mac to use ADB (no drivers) but still no success. PLEASEE. ADB wont connect (and I had the same issue right after root. ADB worked one time, the one time i needed to flash TWRP, and then flash Debranded, Debloated, Deodexed H901-10c ROM for T-Mobile LG V10 (LG-H901) - Clean & Stable by @siraltus, which it is an amazing ROM, and i dont think this had anything to do with this. but please i really need to get my only phone working. if this is in the wrong section please wait till i get an answer to flag it...
All you have to do is make sure the phone is off with the battery in, then hold the volume down button and insert the micro usb cable to your computer, it'll boot up fastboot.
ohmygaa said:
All you have to do is make sure the phone is off with the battery in, then hold the volume down button and insert the micro usb cable to your computer, it'll boot up fastboot.
Click to expand...
Click to collapse
yeah...but ADB doesnt work, i still have no way of getting into recovery...i did the fastboot method
Have you tried erasing your partitions and flashing stock again?
EDIT: using fastboot erase system / fastboot flash system system.img / etc
ohmygaa said:
Have you tried erasing your partitions and flashing stock again?
EDIT: using fastboot erase system / fastboot flash system system.img / etc
Click to expand...
Click to collapse
ADB DOES NOT CONNECT, nothing i do with the shell gets sent to the phone
Have you tried bootng into recovery?
Sent from my Nexus 6 using Tapatalk
---------- Post added at 11:59 PM ---------- Previous post was at 11:56 PM ----------
From power off. Press and hold both power and volume down... When you see the LG logo release and repress the power button, DON'T RELEASE THE VOLUME DOWN KEY. It should bring up a factory reset many select yes... Then yes again...
Sent from my Nexus 6 using Tapatalk
@SPHM900 any luck
Sent from my LG-H901 using Tapatalk
Will try factory reboot after I get home
got into recovery, thank you very very much
Good deal...
Sent from my LG-H901 using Tapatalk
@ZDeuce2
Great job bud.....[emoji106]
@SPHM900
glad you got it working Sir....
Note: MOD please move this to Q&A section. Solved
{
"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"
}
So, the power vol down actually brings you into recovery instead of a factory reboot. Didn't know that. After I got into recovery, I did a back up. a system wipe did nothing. So I reflashed the v10 stock non root and reflashed the @siraltus ROM over top. then restored data. Its like it never happened. Thanks again guys!!! Issue resolved
SPHM900 said:
So, the power vol down actually brings you into recovery instead of a factory reboot. Didn't know that. After I got into recovery, I did a back up. a system wipe did nothing. So I reflashed the v10 stock non root and reflashed the @siraltus ROM over top. then restored data. Its like it never happened. Thanks again guys!!! Issue resolved
Click to expand...
Click to collapse
Power+Vol Down always takes you into recovery. On stock recovery, it automatically triggers a factory reset, but with TWRP, it just boots it.
Glad to hear you got your problem resolved. Nice work guys.
@KennyG123, @svetius could we get this thread moved to the proper forum?
Sent from my LG-H901 using XDA Free mobile app
Apache0c said:
Glad to hear you got your problem resolved. Nice work guys.
@KennyG123, @svetius could we get this thread moved to the proper forum?
Sent from my LG-H901 using XDA Free mobile app
Click to expand...
Click to collapse
Done
KennyG123 said:
Done
Click to expand...
Click to collapse
Well there's a familiar face I haven't seen in awhile! How goes it man! Here I was thinking I'd have to have a rage fit to see you again!!!
markbencze said:
Well there's a familiar face I haven't seen in awhile! How goes it man! Here I was thinking I'd have to have a rage fit to see you again!!!
Click to expand...
Click to collapse
I still show up when paged. Promotion at work means less free time for XDA during the day though.