Related
For unlocked bootloaders only!
Please use the recovery now to root any firmware!
http://forum.xda-developers.com/showthread.php?t=1596285
Just flash the SuperSU cwm zip with recovery and your phone will be rooted. To download SuperSU visit this thread:
http://forum.xda-developers.com/showthread.php?t=1538053
Regards
Bin4ry said:
For unlocked bootloaders only!
Download:
http://eddy.uni-duisburg.de/bin4ry/system_xps_prerooted_63fw.img
Connect device in fastboot mode (blue LED).
Open Command prompt and type:
fastboot flash system system_xps_prerooted_63fw.img
This will give you root immediatly after reboot!
A nicer way will come soon. But this should solve first problems
Regards
Click to expand...
Click to collapse
ERRRR u beat me to it
Cholek3 said:
Guys, you're asolutely f***ing amazing. Congrats.
Do you mean Command prompt in ADB or windows?
Click to expand...
Click to collapse
In Windows command prompt. But ou need fastboot installed.
This is only fist shot. If you dont know really what im talking about, then please wait for another image with good instructions
Jozinek said:
I can confirm, that it work, many thanks.
Edit - it work, but i cant downloads anything from Market, so back to stock version without root. Will wait on new kernel
Click to expand...
Click to collapse
If you get market problems go ot Settings -> Apps -> ... -> Search for the market in the list and then delete Data of the App. After that all will work fine.
Regards
Bin4ry said:
In Windows command prompt. But ou need fastboot installed.
This is only fist shot. If you dont know really what im talking about, then please wait for another image with good instructions
Click to expand...
Click to collapse
I know roughly what you are talking about. I know command prompt, although I never used fastboot, as I only owned X10 (until I dropped it and USB port snapped ), so never had to/wanted to unlock bootloader this way. But I want to learn, that's why I am reading all this now, and I need to ask about something I am not sure of.
Just go through the unlock bootloader process and then you will know what fastboot is
After that just type my comamnd with my file in the same directory and you will be done.
Regards
If I were you I would wait till I get ICS on the phone then unlock the bootloader and root the phone.
Quick question. It just wonders me. Sony "supports" unlocking bootloader, which is more dangerous than root. Why rooting is not supported then? Is it because we could unistall third party aplications and Sony has some sort of agreements with them and are obligated by law?
Cholek3 said:
Quick question. It just wonders me. Sony "supports" unlocking bootloader, which is more dangerous than root. Why rooting is not supported then? Is it because we could unistall third party aplications and Sony has some sort of agreements with them and are obligated by law?
Click to expand...
Click to collapse
No you are getting the idea wrong
Long ago we discussed alot with SonyEricsson and together decided this is the best way of doing it.
The reason is simple:
Rooting alone does not give you access to all partitions etc. pp See X10 Forums for that. Sony is very good in hiding partitions
With a bootloader unlock we get fully workable fastboot. We are able to write all partitions and change what we want. (Root too)
Also Sony(Ericsson) is able to track who unlocks and who not AND is able to provide a check mechanism to forbid unlocking of phones which are not owned by the user (for example provider branded phones in contract, the phone is usually property of the provider).
So this is the reason. Unlocked bootloader gives us nearly full access, so no need to worry I am in this game since X10 times (like you or not ?)and we always got the phones working like we wanted.
Our work for CM9 on XPS has started now too.
Regards
Bin4ry said:
No you are getting the idea wrong
Long ago we discussed alot with SonyEricsson and together decided this is the best way of doing it.
The reason is simple:
Rooting alone does not give you access to all partitions etc. pp See X10 Forums for that. Sony is very good in hiding partitions
With a bootloader unlock we get fully workable fastboot. We are able to write all partitions and change what we want. (Root too)
Also Sony(Ericsson) is able to track who unlocks and who not AND is able to provide a check mechanism to forbid unlocking of phones which are not owned by the user (for example provider branded phones in contract, the phone is usually property of the provider).
So this is the reason. Unlocked bootloader gives us nearly full access, so no need to worry I am in this game since X10 times (like you or not ?)and we always got the phones working like we wanted.
Our work for CM9 on XPS has started now too.
Regards
Click to expand...
Click to collapse
See, I was not aware of that "agreement". Now everything seems to make sense. I am android user since I bought X10 back in August 2010. I was more or less following XDA since then as well, but this forum is worldwide community and is almost imposible to keep a track on everything. I would consider myself somewhere between rookie and advanced users. I know how to do certain things (root, how to use ADB, I was changing framwork_res.apk for my own purposes, etc.). My point also is, I am more hardware sort of guy, rather than software. That's why I am glad you guys are here with us.
Will this wipe the phone data or only the system partition ?
Cholek3 said:
My point also is, I am more hardware sort of guy, rather than software. That's why I am glad you guys are here with us.
Click to expand...
Click to collapse
Hehe no problem. I'm hardware and software guy
gbil said:
Will this wipe the phone data or only the system partition ?
Click to expand...
Click to collapse
Well no. But the first step is that you need to unlock bootloader and THIS WILL wipe your data. To flash the systempartition itself will not wipe userdata.
Cholek3 said:
Yes, I agree. But myself, I will wait for root for phones with locked bootloader as well. I assume I will be happy with phone speed, but when CM9 comes out, then I will consider unlockin bootloader.
Click to expand...
Click to collapse
Your choice, i hope too that we will get a nice exploit again soon. But i personally have to time to work on an exploit.
Regards
3Shirts said:
Screw that! There are too many useful reasons for root. My motto:
Got android? Get root!
Click to expand...
Click to collapse
True that, after I heard that you can lock back the bootloader and update it via SEUS or PCC, I'm so gonna root it and true again.
thanks sir at all
every thing is ok bootloader is unlocked now and root is ok
just i face a problem when i restored 340 (programs+games) through titanium backup pro ...... and when opening just only setting application my phone force close setting menu .......i dont know why although i still have 330 mb free in app
thanks in advanced
hasan_abeer said:
thanks sir at all
every thing is ok bootloader is unlocked now and root is ok
just i face a problem when i restored 340 (programs+games) through titanium backup pro ...... and when opening just only setting application my phone force close setting menu .......i dont know why although i still have 330 mb free in app
thanks in advanced
Click to expand...
Click to collapse
So you restored with Titanium. Since Titanium is a Root app and you don't had Root before i think you are trying to restore a backup from another phone.
If you do that you have to assure that you ONLY RESTORE APPS and NOT SETTINGS! Settings from another phone will be most likely incompatible.
So this wil be your problem!
Regards
Bin4ry said:
So you restored with Titanium. Since Titanium is a Root app and you don't had Root before i think you are trying to restore a backup from another phone.
If you do that you have to assure that you ONLY RESTORE APPS and NOT SETTINGS! Settings from another phone will be most likely incompatible.
So this wil be your problem!
Regards
Click to expand...
Click to collapse
thanks sir i do so restore app+data from samsung galaxy note ........what is the best way to restore :
could i reset my phone through setting+pivacy+factory data reset without affecting root or i must reflash this rom in order to save root
thanks again for your hard job
rgrds
hasan_abeer said:
thanks sir i do so restore app+data from samsung galaxy note ........what is the best way to restore :
could i reset my phone through setting+pivacy+factory data reset without affecting root or i must reflash this rom in order to save root
thanks again for your hard job
rgrds
Click to expand...
Click to collapse
Restore only Apps in Titanium not Data! If you factory reset the phone root is still there
Regards
does the super one click work after bootloader unlocked?
unic0de said:
does the super one click work after bootloader unlocked?
Click to expand...
Click to collapse
I don't think it will, otherwise somebody would already confirmed that I think. At the moment the only way is to flash appropriate firmware (only with unlocked bootloader).
Thread cleaned guys.
Constructive posts only, if you want to say thanks then hit the thanks button.
to whom it concern for call recorder over this rom works like a charm both sides very clear and great loud
just use callrecorder by SKVALEX(green color) from market with choosing recording calls from kernel with 2 way recording patch(root required) option
+wav format
enjoy my friends
great thanks to mr Bin4ry for rooting rom
rgrds
Quick tutorial for unlocking & relocking the bootloader of the Xperia Z2 Tablet
this is the official way to unlock bootloader
WARNING!
MAKE TA BACKUP BEFORE UNLOCKING BOOTLOADER!
if you want to backup the TA or keep ur DRM keys,first root the device and then check this out
Warning!
This procedure will wipe the /data partition of your tablet, so you will loss all ur stored data, settings. SDCARD will BE WIPED!!!
For Xperia™ devices released 2013 or later (for example Xperia™ Z and Xperia™ ZL), the SD card of your device will be formatted and you will lose all content (for example photos, music, videos) when you unlock the boot loader.
Click to expand...
Click to collapse
DRM keys WILL be lost forever
schaggo said:
I'd add what losing DRM keys means, e.g. no more Music ID/Gracenote within the Walkman app plus probably most importantly, as asked all the time and all over the place in the T/mint forums: loss of Bravia Engine.
Click to expand...
Click to collapse
older Xperia devices sometimes got issues after unlock of bootloader (BRICK after FOTA update) - you have been warned
why to unlock bootloader?
u can flash custom ROMs/Kernels
u dont need to worry if the new firmware can be rooted or not as with unlocked bootloader u can always ROOT ur device
Sony gives sneak-peaks/preview builds of latest OS which requires unlocked bootloaders, as they did with Xperia 2011/2012 line, so who knows may be Sony may give early builds of next android OS
Most of this is taken from lollylost100's his tutorial from ARC thread (all credits for that concise tutorial go to him, i have elaborated on a few things and added device specific changes)
btw i dont have this device, most of this testing was done remotely on a users phone... so thanks a lot to him for helping out!!!
[ before we begin unlocking bootloader ]
download the fastboot package
IMPORTANT: if you are using Windows 8 you will need to enable few things to allow driver installation
download the latest FlashTool Xperia Driver Pack and install fastboot drivers (common) & adb drivers for this device from the list!
make sure u have a windows PC with USB cable to connect the phone
power down ur tablet and keeping the Volume Up button pressed connect the USB cable to PC this will trigger FASTBOOT mode and windows will start driver installation, which should be automatically done
once drivers are installed just disconnect cable and power on device
[ how to unlock ] (official way)
Go to: http://unlockbootloader.sonymobile.com/ and read everything!
At the bottom click 'Start Unlocking the Bootloader'
First, you should confirm that it is possible to unlock the boot loader of your tablet by checking the service menu. On your tablet, open the dialler and enter *#*#7378423#*#* to access the service menu.
In your phone, tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
Click to expand...
Click to collapse
after u have verified that u can unlock bootloader, scroll to the bottom of the page and click "Continue"
you will get numerous prompts, read all info and if u agree click on "Accept"/"OK"/"Proceed"
finally u will get a "Create Unlock request" page, enter your IMEI (sometimes the last digit needs to be removed for this to work), name and email address
You should now receive your unique unlock key via EMAIL, SAVE THIS KEY SAFELY
Extract fastboot_with_Android_USB_file.rar and open fastboot folder
Hold SHIFT and right click on the background of the folder
Select 'Open command window here'
Connect your tablet in fastboot mode (turn phone off, hold Volume UP button and plug in USB Cable) [make sure drivers are installed as explained above)
In the cmd windows type in fastboot.exe -i 0x0fce getvar version
If a value is returned (it will return 0.5), it means the tablet is correctly connected
Type in fastboot.exe -i 0x0fce oem unlock 0xKEY and replace KEY with the key which u received earlier.
You're device should now be bootloader unlocked
If this tutorial is too much for you then itskapil wrote a step-by-step guide (and recorded a video also):
-Instructions: http://www.theandroidsoul.com/how-to-unlock-bootloader-xperia-arc-play-neo-pro/
-Video: http://www.youtube.com/watch?v=LRH3pC7MhEA
(the above videos and some steps are for Xperia 2011 devices, but most the steps are same for Xperia Z)
Relock procedure is posted here
regards,
DooMLoRD
Relocking bootloader
With the latest release of Flashtool it is now possible to relock bootloader.
Download the latest flashtool from:
http://forum.xda-developers.com/showthread.php?t=920746
Important
DO NOT USE ANY FTF TO RELOCK BOOTLOADER! THOSE OLD FTFs DO NOT WORK FOR THE 2013 DEVICES!!!
before u relock bootloader u have to be on pure stock kernel (flash only the kernel.sin using flashtool), else the device WILL NOT BOOT after relock
Steps:
now start Flashtool and click on BLU button
u will be asked to connect device in flashmode
once u connect the device u will get a prompt to "Relock"
click on it and when prompted disconnect the device
Want to UNLOCK again after relocking? read this!
Obviously since we must unlock to root, no TA backup can bedone...
Diomorgan said:
Obviously since we must unlock to root, no TA backup can bedone...
Click to expand...
Click to collapse
Asking or telling..........either way, correct. TA needs root, to get root you need to unlock lol
Mikey said:
Asking or telling..........either way, correct. TA needs root, to get root you need to unlock lol
Click to expand...
Click to collapse
I'm confused now.....
Pondy said:
I'm confused now.....
Click to expand...
Click to collapse
No TA backup can be done, the guide is the same of Z1 that can be rooted withouth unlock.
Pondy said:
I'm confused now.....
Click to expand...
Click to collapse
It is very confusing indeed. In other words it actually says, do not unlock yet. Wait for an exploid to be found and released so you can root without unlocking the bootloader. Then you can safely make an TA backup, and then safely unlock the bootloader. If you unlock now, your warranty is void.
Sent from my SGP511 using XDA Free mobile app
When a root exploit is found, unlocking the bootloader or backing up TA is not necessary anymore. (Except if one wants to install a custom ROM or custom kernel.)
Yes, but that's why we here. To install custom roms and kernels I mean..
Sent from my LT26i using XDA Free mobile app
dumbl3 said:
Yes, but that's why we here. To install custom roms and kernels I mean..
Sent from my LT26i using XDA Free mobile app
Click to expand...
Click to collapse
OK thanks for clarifying that! I figured that was the case. And yes thats why I'm here, custom rom! This thing would rock with Slimkat or something similar (if it ever gets ported).
For all those who worry about unlocking I would like to cite Doomlord from the Z2 phone CWM recovery thread:
Dont worry I have been on unlocked Bootloader on all my Xperia phones and honestly there is no functionality that I missed.
Click to expand...
Click to collapse
This!
(Yes, I know, the warranty, blah... )
dumbl3 said:
Yes, but that's why we here. To install custom roms and kernels I mean..
Sent from my LT26i using XDA Free mobile app
Click to expand...
Click to collapse
Actually I have customs on all my device, but on z1 (same for z2) never needed one, just root and exposed framework+adaway.
About unlocking, as far as I know the only "useful feature" you will disable should be the bravia engine.
Bravia Engine (or X-Reality) is not "useful", it's just oversaturating and exaggerating colors in an unnatural way. A feature for noobs, just like "Beats Audio" is a bass-booster for music-unsensible juvenile oomph-oomph listeners.
So it can easily be discarded without ever looking back.
hasenbein1966 said:
Bravia Engine (or X-Reality) is not "useful", it's just oversaturating and exaggerating colors in an unnatural way. A feature for noobs, just like "Beats Audio" is a bass-booster for music-unsensible juvenile oomph-oomph listeners.
So it can easily be discarded without ever looking back.
Click to expand...
Click to collapse
i agree on that but it voids your warranty.
Im not saying we should all wait till your warranty is over, but at least fully test your device before making a irrational decision, dead pixels, speakers, loose corners (have had 2 devices with that problem), waterproof test, etc...
LitoNi said:
i agree on that but it voids your warranty.
Im not saying we should all wait till your warranty is over, but at least fully test your device before making a irrational decision, dead pixels, speakers, loose corners (have had 2 devices with that problem), waterproof test, etc...
Click to expand...
Click to collapse
True, last thing you want is to void the warranty and find out something covered by it goes bad. I can wait. This baby is running nice so far. Dont need custom rom, but im missing that root!!
SD card write
Is anyone else having issue to write to external sdcard ?
nizammoidu said:
Is anyone else having issue to write to external sdcard ?
Click to expand...
Click to collapse
That's the new rule implemented in kit kat, not Sony's fault.
This problem can be solved if root is available
Sent from my C6603 using XDA Premium 4 mobile app
what s that rule? I have been using kitkat with omni since it released in note 2 nd hammerhead. initially it had issues with selinux, then i wrote a patch to omni source as well. but here selinux is not the bad guy I suspect something to QUCOMSEC nd drm keys. l have root, can u give me pointer to fixes. This s my first sony device so I have idea, Thank u
nizammoidu said:
what s that rule? I have been using kitkat with omni since it released in note 2 nd hammerhead. initially it had issues with selinux, then i wrote a patch to omni source as well. but here selinux is not the bad guy I suspect something to QUCOMSEC nd drm keys. l have root, can u give me pointer to fixes. This s my first sony device so I have idea, Thank u
Click to expand...
Click to collapse
custom roms probably already coded it, thats why you didnt encounter the problem. Explanation of the problem can be found here provided by the OP.
If you have root already you can try both of the following,
*please note that Ive tried the xposed module on my Xperia Z running stock kit kat not Z2.
**please note, back up your stuff before proceeding, just incase something goes wrong and wipes your files.
[XPOSED] HandleExternalStorage requires Xposed framework installed. I am currently running this module and working fine.
[Playstore] SDFix: KitKat Writable MicroSD this was suggested by kingvortex in another thread, havent tried it yet, but the reviews seem to suggest it works.
hasenbein1966 said:
Bravia Engine (or X-Reality) is not "useful", it's just oversaturating and exaggerating colors in an unnatural way. A feature for noobs, just like "Beats Audio" is a bass-booster for music-unsensible juvenile oomph-oomph listeners.
So it can easily be discarded without ever looking back.
Click to expand...
Click to collapse
Sorry - but I just have to add my own experience as a "noob".
First: I gave that X-Reality thing a deeper check; I had two Z2 tablets for simultaneously checking how HD videos look with and without that X-Reality feature.
I usually dislike all kinds of "enhancers", whether for audio or video enhancement. First things to switch off.
But I have to admit: X-Reality really works. The Z2 with the feature on produced a far more lively, absorbing experience. It's hard to tell what exactly makes the difference, it's just there. Among other videos, I used the famous Samsung "build-a-helicopter" video for comparison. Contrasts were better, details improved a bit, colors got slightly accentuated, became deeper. The slightly oversaturated color reproduction of the Z2 of course is there - but with and without X-Reality.
In short: Videos were just more fun and pleasant to the eye.
Best of all: You can switch it off; but you don't want to.
To be honest: X-Reality is THE feature preventing me from rooting the Z2 now. I don't care for DRM keys, I don't care for a true-to-life color rendition. But I care for pictures and videos looking simply better.
Quite lenghty explanation - but I guess this is an issue to consider prior to unlocking your bootloader and waving X-Reality goodbye forever.
Second: Beats Audio is a bit more than a "bass-booster for music-unsensible juvenile oomph-oomph listeners".
I seem to be a 45 years old "music-unsensible" listener. In fact, I am a former professional musician, knowing just a bit about sound.
I don't see anything wrong with utilizing software techologies to overcome some of the acoustic issues tiny smartphone or tablet loudspeakers suffer of. It's not just about creating that "oomph-oomph" redneck sound; it's about compensating the shortcomings of problematic speaker setups.
That's what devices like HTCs One clearly demonstrated.
I'd be quite happy if our Z2 had anything similar to offer. :/
So please try to be a bit more reluctant if it comes to demonizing modern features not everybody may like, but which will be gone forever if you go the hasty way.
Recently, Xperia Acro S was been removed from the Unlocking Bootloader list on the Official Sony site.
As maintaining a thread on Acro S section, some of my friends were unable to unlock their bootloader due to missing device in the list.
So, I Emailed Sony few weeks ago requesting them to re-list Acro S, and they said, they'll look at this. Now its been Re-listed.
I have even attached three screenshots for your conformation. So see it, Just check out below three links,
SS-01 || SS-02 || SS-03
For those who were waiting to unlock their phone, here's a good news for you all. Go ahead and get the unlock code from official Sony site providing them your IMEI.
1. To Get Unlock Code just click HERE!
2. Unlocking Bootloader step-by-step Guide, just click HERE!
Regards,
hitman-xda
As I said, I'll notify you after Acro S is re-listed, I'll mention you here; @bluvn || @sky202_how89 || @els_sand
Wow, Thanks for the surprise! U make my days!
sky202_how89 said:
Wow, Thanks for the surprise! U make my days!
Click to expand...
Click to collapse
That sounds good
Hey but too bad is I totally brick my phone. Almost all of the solution found by google seems no used.
Out of surprise, it happened for most of the Xperia Phones who are heavy flashing with custom ROM.
Check out the thread here: http://forum.xda-developers.com/xperia-s/help/xperia-acro-s-sim-card-service-detect-t3200650
Now my XAS is becoming a powerful MP4 Player. What a desperate. ;( ;(
sky202_how89 said:
Hey but too bad is I totally brick my phone. Almost all of the solution found by google seems no used.
Out of surprise, it happened for most of the Xperia Phones who are heavy flashing with custom ROM.
Check out the thread here: http://forum.xda-developers.com/xperia-s/help/xperia-acro-s-sim-card-service-detect-t3200650
Now my XAS is becoming a powerful MP4 Player. What a desperate. ;( ;(
Click to expand...
Click to collapse
Did you checked weather your Bootloader is unlocked? If not then check it.
Also try to repair your phone through PC companion.
Its a strange problem. Hearing it first time.
Did you followed exact procedure of the Guide that I linked?
I don't think it occurs due to heavy flashing of ROMs, because I have used every ROM available for the phone for almost 100 times. I usually change my ROM after a month.
hitman-xda said:
Did you checked weather your Bootloader is unlocked? If not then check it.
Also try to repair your phone through PC companion.
Its a strange problem. Hearing it first time.
Did you followed exact procedure of the Guide that I linked?
I don't think it occurs due to heavy flashing of ROMs, because I have used every ROM available for the phone for almost 100 times. I usually change my ROM after a month.
Click to expand...
Click to collapse
The problem occurred when the user try to flash back to stock ROM from Custom ROM.
The Bootloader is unlocked.
Now the BL appear to be like this: Bootloader Unlock Allowed = No (*#*#7378423#*#*)
Enter fastboot fail (No fastboot detected), Only Flash is allowed.
To install CWM or TWRP required fastboot, so I can't do anything besides keep trying to flash wiith different version of stock FTF.
Solution I tried but failed:
- Fix using Sony PC Companion (PCC)
- Flash any version of stock ROM, inclusive of just flashed the "Baseband" only.
- Flash Acro-HD S0-03D ROM then flash back to stock ROM.
- *#*#4636#*#* -> Phone information -> Set preferred network type (any of the option & reboot)
- Settings -> More -> Mobile Networks -> Network Mode(any option & reboot)
- Settings -> More -> Mobile Networks -> Select providers (automatic or manual), it manage to detects the service providers but registered on the network failed.
- Insert other active SIM Card
I try to locate the Antenna Board but it seems like it was attached with the mainboard. Unlike Xperia Z, the Antenna Board is seperated.
I assume this problem occurred when the partition accidentally bricked by Flashtool? I did try to flash different version of Baseband, nothing seems work.
I need someone favors. Create a Pre-rooted Stock ROM(.ftf) with Recovery Accessed (CWM or TWRP).
I found somewhere from this forum stated that tried to install back any of the Custom ROM to fix the No Signal Issue which it appeared to be my last hope. Without Recovery(Required Fastboot to install), I couldn't install any custom ROM.
sky202_how89 said:
The problem occurred when the user try to flash back to stock ROM from Custom ROM.
The Bootloader is unlocked.
Now the BL appear to be like this: Bootloader Unlock Allowed = No (*#*#7378423#*#*)
Enter fastboot fail (No fastboot detected), Only Flash is allowed.
To install CWM or TWRP required fastboot, so I can't do anything besides keep trying to flash wiith different version of stock FTF.
Solution I tried but failed:
- Fix using Sony PC Companion (PCC)
- Flash any version of stock ROM, inclusive of just flashed the "Baseband" only.
- Flash Acro-HD S0-03D ROM then flash back to stock ROM.
- *#*#4636#*#* -> Phone information -> Set preferred network type (any of the option & reboot)
- Settings -> More -> Mobile Networks -> Network Mode(any option & reboot)
- Settings -> More -> Mobile Networks -> Select providers (automatic or manual), it manage to detects the service providers but registered on the network failed.
- Insert other active SIM Card
I try to locate the Antenna Board but it seems like it was attached with the mainboard. Unlike Xperia Z, the Antenna Board is seperated.
I assume this problem occurred when the partition accidentally bricked by Flashtool? I did try to flash different version of Baseband, nothing seems work.
I need someone favors. Create a Pre-rooted Stock ROM(.ftf) with Recovery Accessed (CWM or TWRP).
I found somewhere from this forum stated that tried to install back any of the Custom ROM to fix the No Signal Issue which it appeared to be my last hope. Without Recovery(Required Fastboot to install), I couldn't install any custom ROM.
Click to expand...
Click to collapse
First of all let me clear that 'Unlocking Bootloader Allowed = No'
That means you cannot unlock it unless your coming to stock from other ROM.
Also Bootloader can be unlocked only once. So if your coming back to stock from custom, why did you tried to unlock your BL again?
Even if you flash stock ftf, you no need to unlock your BL again.
Secondly, don't try to flash other ROMs into your phone, you could mess up everything, even hard brick.
Your Fastboot mode isn't working, right? If so, then try to install fastboot drivers from flashtool driver pack. Maybe it could work.
hitman-xda said:
First of all let me clear that 'Unlocking Bootloader Allowed = No'
That means you cannot unlock it unless your coming to stock from other ROM.
Also Bootloader can be unlocked only once. So if your coming back to stock from custom, why did you tried to unlock your BL again?
Even if you flash stock ftf, you no need to unlock your BL again.
Click to expand...
Click to collapse
I did not lock my BL, it just lock back by themselves. I still remember I unlock my BL with Sony Official way in 2013. After that, I did not touch that BL again. It's just after the recent flash which I did the same way like before(Custom to stock ROM), everything mess up.
Secondly, don't try to flash other ROMs into your phone, you could mess up everything, even hard brick.
Your Fastboot mode isn't working, right? If so, then try to install fastboot drivers from flashtool driver pack. Maybe it could work.
Click to expand...
Click to collapse
I even format my pc which I thought it was my pc issue earlier. But ends up I realize it was something regarding to my BL. With BL Unlock Allowed: No, you cannot enter to your bootloader or fastboot.
This video is showing exactly my problem now:
Other thread that I discovered with same issue as I am:
http://forum.xda-developers.com/showthread.php?t=2432566
http://forum.xda-developers.com/xperia-z/help/xperia-z-signal-drops-unable-to-connect-t2183045
My very last but not recommended solution is to change the motherboard. However, looking at the posting not only me having the issue and it mostly happened when users are flashing back from Custom ROMS to Stock ROMS.
Changing motherboard is like changing another phone, your feeling towards the phone changed.
sky202_how89 said:
I did not lock my BL, it just lock back by themselves. I still remember I unlock my BL with Sony Official way in 2013. After that, I did not touch that BL again. It's just after the recent flash which I did the same way like before(Custom to stock ROM), everything mess up.
I even format my pc which I thought it was my pc issue earlier. But ends up I realize it was something regarding to my BL. With BL Unlock Allowed: No, you cannot enter to your bootloader or fastboot.
This video is showing exactly my problem now:
Other thread that I discovered with same issue as I am:
http://forum.xda-developers.com/showthread.php?t=2432566
http://forum.xda-developers.com/xperia-z/help/xperia-z-signal-drops-unable-to-connect-t2183045
My very last but not recommended solution is to change the motherboard. However, looking at the posting not only me having the issue and it mostly happened when users are flashing back from Custom ROMS to Stock ROMS.
Changing motherboard is like changing another phone, your feeling towards the phone changed.
Click to expand...
Click to collapse
After flashing stock ftf, the BL status always shows 'Bootloader Unlock Allowed = No' but it is actually unlocked. So it does not get relock after flashing stock ftf.
It seems like a serious problem.
Maybe, flashing other ROM will help you a bit. For that Obviously your phone must enter into fastboot mode (which is not happening). In this case did you use 'dd' command for installing recovery? If not then you could try it. And I think you'll be succeeded to install recovery and further you can flash ROM.zip through recovery.
You just need to copy recovery.img into your internal memory and enter some command's using adb shell.
sky202_how89 said:
I did not lock my BL, it just lock back by themselves. I still remember I unlock my BL with Sony Official way in 2013. After that, I did not touch that BL again. It's just after the recent flash which I did the same way like before(Custom to stock ROM), everything mess up.
I even format my pc which I thought it was my pc issue earlier. But ends up I realize it was something regarding to my BL. With BL Unlock Allowed: No, you cannot enter to your bootloader or fastboot.
This video is showing exactly my problem now:
Other thread that I discovered with same issue as I am:
http://forum.xda-developers.com/showthread.php?t=2432566
http://forum.xda-developers.com/xperia-z/help/xperia-z-signal-drops-unable-to-connect-t2183045
My very last but not recommended solution is to change the motherboard. However, looking at the posting not only me having the issue and it mostly happened when users are flashing back from Custom ROMS to Stock ROMS.
Changing motherboard is like changing another phone, your feeling towards the phone changed.
Click to expand...
Click to collapse
You must have used a newer version of flashtool. This is causing similar issues for many people. The only solution for now seems going to Sony service center. There is another method too, flashing the TA backup, but I don''t know if it works or not.
hitman-xda said:
After flashing stock ftf, the BL status always shows 'Bootloader Unlock Allowed = No' but it is actually unlocked. So it does not get relock after flashing stock ftf.
It seems like a serious problem.
Maybe, flashing other ROM will help you a bit. For that Obviously your phone must enter into fastboot mode (which is not happening). In this case did you use 'dd' command for installing recovery? If not then you could try it. And I think you'll be succeeded to install recovery and further you can flash ROM.zip through recovery.
You just need to copy recovery.img into your internal memory and enter some command's using adb shell.
Click to expand...
Click to collapse
I will try & let you know soonest. Kinda busy this few days.
---------- Post added at 05:35 PM ---------- Previous post was at 05:32 PM ----------
Mirhawk said:
You must have used a newer version of flashtool. This is causing similar issues for many people. The only solution for now seems going to Sony service center. There is another method too, flashing the TA backup, but I don''t know if it works or not.
Click to expand...
Click to collapse
YES, I am flashing with NEWEST VERSION of Flashtool. After that, the result turned nagative.
Do you mean TA Partition? Do you have a backup copy of it?
---------- Post added at 05:41 PM ---------- Previous post was at 05:35 PM ----------
Latest UPDATE about the issue, PLEASE TAKE NOTE BECAUSE YOU'RE ABOUT TO BRICK YOUR PHONE JUST LIKE ME. THIS IS IMPORTANT!
@hitman-xda , Please pass this message around. Btw, How to quote the name?
If everyone here in this post flashed their phones with Flashtool 0.9.19.x version, then congrats my friends, we're all become owners of bricked phones with no network signal. Flashtool 0.9.19.x versions have sript error which replaces original Ta partition leading to unlocked bootloader to become locked and loss of network signal. If you're guys haven't backuped your Ta partition prior to bootloader unlocking then that's all.
Check here http://forum.xda-developers.com/show...68&postcount=4 and here http://forum.xda-developers.com/show...postcount=2758
Click to expand...
Click to collapse
http://forum.xda-developers.com/xpe...ice-detect-t3200650/post62904161#post62904161
sky202_how89 said:
YES, I am flashing with NEWEST VERSION of Flashtool. After that, the result turned nagative.
Do you mean TA Partition? Do you have a backup copy of it?
Click to expand...
Click to collapse
Flashing with latest flashtool flashes a partition which renders modem of the phone useless. Yes, I mean the TA partition. Each phone's TA partition is unique, so if You flash mine or other person's TA partition, Your phone would not even boot.
This is toooooooooooooooooooooooooooo OVER! It means my phone is bricked forever.
It's their mistake but we have to bear it on our owns.
sky202_how89 said:
This is toooooooooooooooooooooooooooo OVER! It means my phone is bricked forever.
It's their mistake but we have to bear it on our owns.
Click to expand...
Click to collapse
Did nothing worked?
hitman-xda said:
Did nothing worked?
Click to expand...
Click to collapse
Yes, nothing worked because Flashtool just accidentally bricked our Sony in the whole world. A careless mistake destroy the phone.
In 0.9.18.X, simlock.ta is always excluded by default but a careless mistake on the version 0.9.19.(1234) (at that time), The Simlock.ta is included while flashing. Each phone TA has their own unique number. Besides changing the mianboard (the only solution right now), no ones manage to solve this issue.
I wonder how many Sony phone in the world has already been bricked by this Flashtool update.
Androxyde said:
On 0.9.18.X, even if simlock is included, it is excluded from flashing
On 0.9.19.5 I did this way :
- simlock is excluded by default with a warning when including it (unticking button)
- When simlock is included, when flashing, a YES/NO box appears asking if you are absolutely sure you want to flash this unit.
- When creating bundles, simlock can be included (no risk with 0.9.18 as it is always ignored)
So if you have a TA backup, with 0.9.19.5 you can restore the 07DA unit (then reactivating the phone). Thing you cannot do with any previous release as 07DA unit is hardcoded_excluded.
I will publish another patch that will backup any TA unit that is about to be flashed. That way there will always be a solution to come back to the previous state.
simlock, if present, is always ignored in 0.9.18 release
simlock, if present is excluded by default with the ability to include it with a warning and a user query before flashing the unit
people who had issues are ones using ftf bundles created prior to 0.9.18 with simlock included. Never had issues on 0.9.18 as it is excluded by default, I forget to keep this exclusion on 0.9.19.[1234] and added a defautl exclusion on .5 with the ability to include it anyway.
But maybe it is not the right way ... I was asking myself when I did it. I want to give the ability to restore 07DA unit if ever a backup exists
The only way to recover from locked phones is to reactivate them in a service center or to restore the 07DA unit.
Click to expand...
Click to collapse
sky202_how89 said:
Yes, nothing worked because Flashtool just accidentally bricked our Sony in the whole world. A careless mistake destroy the phone.
In 0.9.18.X, simlock.ta is always excluded by default but a careless mistake on the version 0.9.19.(1234) (at that time), The Simlock.ta is included while flashing. Each phone TA has their own unique number. Besides changing the mianboard (the only solution right now), no ones manage to solve this issue.
I wonder how many Sony phone in the world has already been bricked by this Flashtool update.
Click to expand...
Click to collapse
Well, that is disappointing
Hard to believe, that Sony really did that serious change in its software.
hitman-xda said:
Well, that is disappointing
Hard to believe, that Sony really did that serious change in its software.
Click to expand...
Click to collapse
At least you're out of trouble. I suggest you need to backup your TA Partition just in case.
Each TA is unique and cannot be transferred.
If your TA is used by 3rd party, they may face a Hard Brick & cannot be recovered anymore.
Well, this is an added Security by Sony. They are not stupid to "share" openly for free.
Now I'm realize.
sky202_how89 said:
At least you're out of trouble. I suggest you need to backup your TA Partition just in case.
Each TA is unique and cannot be transferred.
If your TA is used by 3rd party, they may face a Hard Brick & cannot be recovered anymore.
Well, this is an added Security by Sony. They are not stupid to "share" openly for free.
Now I'm realize.
Click to expand...
Click to collapse
I can't do that. Coz I have already unlocked my bootloader months ago
hitman-xda said:
I can't do that. Coz I have already unlocked my bootloader months ago
Click to expand...
Click to collapse
That's bad but still not too late. Your next Sony in future will be secured
I'm already ordered the replacement mainboard.
What kind of mainboard-Lock BL or Unlock BL, I do not know because it's not a new one.
Waiting for shipment.
How to unlock bootloader on Sony Xperia M5.
How to unlock bootloader
1.In http://developer.sonymobile.com/unlockbootloader/ choose Sony Xperia M2.
2.Submit Email
3.Submit IMEI
4.And unlock bootloader with intruction.
You get the code? Then we continue.
Download the latest version here or Flashtool http://www.flashtool.net/downloads.php
After installation, go the path C: \ Users \ username \ .flashTool \ registeredDevices here and create a folder with the code-name of your machine (you can find out if flashtool click on BLU and see where in the log are in line «Current device» for example, in line 09/045/2015 23:45:08 - INFO - Current device: C2104 - AB100C2DE3 - 1272-4136_R5B - 1269-5420_15.3.A.1.17 - WORLD-a_15.3.A.1.17 code machine will AB100C2DE3. Code which will write your name and location).
Later in this folder, create a text file and name it «ulcode» (without the quotes). Open, and in it write your unlock code, that you have on the site Sony. Save. Write code very carefully.
Now open flashtool and press the BLU. If everything is correct, in line you should write your code, pressing unlock. All should be ready to unlock.
Working on:E5633
I am not responsible for the broken device. Whatever you do, you do at your own risk
After unlocking bootloader will void the warranty
I forgot write. I get unlock code with my IMEI.
Interesting, I checked my Rooting Info as per the guide and it does say allowed.
I think giving Sony my IMEI will potentially void my warranty claims? Let me think about it.
ykphuah said:
Interesting, I checked my Rooting Info as per the guide and it does say allowed.
I think giving Sony my IMEI will potentially void my warranty claims? Let me think about it.
Click to expand...
Click to collapse
I think, in service centre check bootloader. If bootloader not unlocked, warranty is valid.
This method is working also on M5 dual, 6533
But the next step should be how to gain the root =)
---------- Post added at 03:19 PM ---------- Previous post was at 03:15 PM ----------
ykphuah said:
Interesting, I checked my Rooting Info as per the guide and it does say allowed.
I think giving Sony my IMEI will potentially void my warranty claims? Let me think about it.
Click to expand...
Click to collapse
Probably no.
You could reLock your device from flashtool simply, before visiting the service center.
vsm778 said:
This method is working also on M5 dual, 6533
But the next step should be how to gain the root =)
---------- Post added at 03:19 PM ---------- Previous post was at 03:15 PM ----------
Probably no.
You could reLock your device from flashtool simply, before visiting the service center.
Click to expand...
Click to collapse
Maybe 5633 ?
DukeMcWood said:
Maybe 5633 ?
Click to expand...
Click to collapse
yep, you're right, thanks
hello guys. when you unlock bootloader, can you than record 4k video in H.264 not H.265 and upload it to youtube?
vsm778 said:
This method is working also on M5 dual, 6533
Probably no.
You could reLock your device from flashtool simply, before visiting the service center.
Click to expand...
Click to collapse
Yes, you can relock your bootloader with Flash Tool but your DRM keys are gone forever, proprietary Sony features won't work even after relocking...
Also, it's veeeeeery unlikely, but they may check if your DRM keys still exist in Sony Service Center, in case they don't find them they'll know you've unlocked your bootloader...
How about port TWRP or CWM on Xperia M5 ? If we port recovery, we can get root.
mbc07 said:
Yes, you can relock your bootloader with Flash Tool but your DRM keys are gone forever, proprietary Sony features won't work even after relocking...
Also, it's veeeeeery unlikely, but they may check if your DRM keys still exist in Sony Service Center, in case they don't find them they'll know you've unlocked your bootloader...
Click to expand...
Click to collapse
I think there's a way to do it by backing up the TA partition. That's how Sony Xperia Z1 started. We root, unlock bootloader, backup TA and when we relock, we can actually restore the TA and DRM key
firdyRAY said:
I think there's a way to do it by backing up the TA partition. That's how Sony Xperia Z1 started. We root, unlock bootloader, backup TA and when we relock, we can actually restore the TA and DRM key
Click to expand...
Click to collapse
Err, no. To preserve your DRM keys you need a way to root without unlocking the bootloader (e.g. using an exploit), then you make a backup of your TA partition which will contain your DRM keys. If you unlocked your bootloader without a taking a TA backup first, your DRM keys are gone forever, even if you root your device afterwards and make a backup of your TA partition you won't have any keys at all because they already were wiped when you unlocked the bootloader, this applies to any Sony device.
In other words, currently there's no way of unlocking M5 bootloader and keeping your DRM keys, the hope is Xperia Z5 series or other flagship devices, they draw attention of many developers and like what happened with Z2 and Z3, for example, locked bootloader users probably gonna start a bounty or some kind of incentive for a way to root the locked variant of those flagships, eventually they'll find an exploit that probably can be ported to other devices with less development activity, like Xperia M4/M5.
It's the cat-and-mouse game, new flagships are released, devs will research possible exploits to those new flagship devices and when one is found it's very likely to work with most devices released at the same time (and that probably are unpatched too). Also, in Sony devices, if you have root in one firmware version, you'll automatically have root in any new firmware too (using tools like PRFCreator or dd Flasher)...
(as record, towelroot, developed originally for Galaxy S5, could be used in a lot of Xperia devices from that time, and the Xperia Z3 exploit was successfully ported to Xperia E3 as well and could probably be used in similar devices released around the same time like Xperia C3 and others)
Thank you! What's the chance of the M5 properly supported by custom rom, like FreeXperia and CyanogenMod?
optionalmgrr.la said:
Thank you! What's the chance of the M5 properly supported by custom rom, like FreeXperia and CyanogenMod?
Click to expand...
Click to collapse
I dont know. But, I want port flyme os from meizu devices.
camping here to get notified of root asap..
DukeMcWood said:
How to unlock bootloader on Sony Xperia M5.
How to unlock bootloader
Click to expand...
Click to collapse
Hello Duke,
On Sonymobile page for M5 it is showing that it is due to update to Android 6.0 Marshmellow which is coming soon.
So what do you think? I heard root isnt possible on Android 6.0 , and if rooted they will make it hard for the users.
Is it going to be well? or Rooting is history?
p.s - When I asked a youtube user for the bootloader for M5, he said " root method has been out for months, it would be great if you can put Google to use. no offense". Is this true? whats going on?
thank you.
Ketansa said:
Hello Duke,
On Sonymobile page for M5 it is showing that it is due to update to Android 6.0 Marshmellow which is coming soon.
So what do you think? I heard root isnt possible on Android 6.0 , and if rooted they will make it hard for the users.
Is it going to be well? or Rooting is history?
p.s - When I asked a youtube user for the bootloader for M5, he said " root method has been out for months, it would be great if you can put Google to use. no offense". Is this true? whats going on?
thank you.
Click to expand...
Click to collapse
I dont know about 6.0, because i dont have 6.0. In the near future i maybe port recovery. But i dont have original recovery.img from Xperia M5 for port.
mbc07 said:
Err, no. To preserve your DRM keys you need a way to root without unlocking the bootloader (e.g. using an exploit), then you make a backup of your TA partition which will contain your DRM keys. If you unlocked your bootloader without a taking a TA backup first, your DRM keys are gone forever, even if you root your device afterwards and make a backup of your TA partition you won't have any keys at all because they already were wiped when you unlocked the bootloader, this applies to any Sony device.
In other words, currently there's no way of unlocking M5 bootloader and keeping your DRM keys, the hope is Xperia Z5 series or other flagship devices, they draw attention of many developers and like what happened with Z2 and Z3, for example, locked bootloader users probably gonna start a bounty or some kind of incentive for a way to root the locked variant of those flagships, eventually they'll find an exploit that probably can be ported to other devices with less development activity, like Xperia M4/M5.
It's the cat-and-mouse game, new flagships are released, devs will research possible exploits to those new flagship devices and when one is found it's very likely to work with most devices released at the same time (and that probably are unpatched too). Also, in Sony devices, if you have root in one firmware version, you'll automatically have root in any new firmware too (using tools like PRFCreator or dd Flasher)...
(as record, towelroot, developed originally for Galaxy S5, could be used in a lot of Xperia devices from that time, and the Xperia Z3 exploit was successfully ported to Xperia E3 as well and could probably be used in similar devices released around the same time like Xperia C3 and others)
Click to expand...
Click to collapse
That's very lengthy but good to know. Thank you!
Ketansa said:
Hello Duke,
On Sonymobile page for M5 it is showing that it is due to update to Android 6.0 Marshmellow which is coming soon.
So what do you think? I heard root isnt possible on Android 6.0 , and if rooted they will make it hard for the users.
Is it going to be well? or Rooting is history?
p.s - When I asked a youtube user for the bootloader for M5, he said " root method has been out for months, it would be great if you can put Google to use. no offense". Is this true? whats going on?
thank you.
Click to expand...
Click to collapse
Well i personally don't trust any advice from any other source except for XDA just to be safe because we the internet have too many smart alecks who know nothing and try to act smart by being sarcastic. So i guess the safest thing to do is to check on XDA for root methods and go through the forum to see if it works for others
Ketansa said:
p.s - When I asked a youtube user for the bootloader for M5, he said " root method has been out for months, it would be great if you can put Google to use. no offense". Is this true? whats going on?
thank you.
Click to expand...
Click to collapse
I don't think he have a rooted M5. Before we get root, we must unlock the bootloader first, and this is the part that is not done yet.
firdyRAY said:
That's very lengthy but good to know. Thank you!
Well i personally don't trust any advice from any other source except for XDA just to be safe because we the internet have too many smart alecks who know nothing and try to act smart by being sarcastic. So i guess the safest thing to do is to check on XDA for root methods and go through the forum to see if it works for others
Click to expand...
Click to collapse
Hello Thank you,
Yes you are right, may be he is being Sarcastic or some kind of adware developer for corporates.
Looking in XDA forums.
This was posted in the all Note 8 forum claiming it is an engineering combo. Has anyone tried it to verify it is actually an engineer boot?
https://firmware.gem-flash.com/index.php?a=browse&b=category&id=12507
The link above requires a paid membership but a file with the same name is available from androidfilehost, can't verify the md5 though.
https://www.androidfilehost.com/?w=files&flid=213338
From what i gather from the firmware this is the us firmware for sprint, which in theory should work for verizon, however not worth bricking to find out.
---------- Post added at 02:09 PM ---------- Previous post was at 02:08 PM ----------
have you checked the sprint note 8 links??
I just ordered my vzw n8 today for tomorrow delivery. However im not smart enough nor brave enough attempt anything on it with a random rouge firmware, but you can bet I will follow this thread. Here's to wishful thinking. : )
~SG
Also being discussed here
https://forum.xda-developers.com/ga...ssion-snapdragon-note-8-models-t3670091/page4
Is it possible to use the mentioned firmware for some carrier switching flashing on note 8, just like what they did to S8 in this thread: https://forum.xda-developers.com/galaxy-s8/how-to/snap-guide-flashing-standard-fw-carrier-t3625817
I can confirm this Combination firmware is legit, or at least the one from the AFH link. You must do a factory reset after flash or the phone will not boot, likely due to encryption.
This kernel is permissive, and it does have ADB enabled by default.
bangbusdriver said:
I can confirm this Combination firmware is legit, or at least the one from the AFH link. You must do a factory reset after flash or the phone will not boot, likely due to encryption.
This kernel is permissive, and it does have ADB enabled by default.
Click to expand...
Click to collapse
When you say likely due to encryption, do you mean encryption already present on the phone or does flashing this encrypt it? I don't believe my phone is encrypted as I haven't enabled any secure unlock system. Or do you mean bootloader encryption. Unless I'm mistaken the phone isn't encrypted until after a secure unlock option is enabled.
I really don't want to go through my phone setup again when root isn't available yet. This just seems like a first step to enable flashing of a rooted firmware.
jellyhead said:
When you say likely due to encryption, do you mean encryption already present on the phone or does flashing this encrypt it? I don't believe my phone is encrypted as I haven't enabled any secure unlock system. Or do you mean bootloader encryption. Unless I'm mistaken the phone isn't encrypted until after a secure unlock option is enabled.
I really don't want to go through my phone setup again when root isn't available yet. This just seems like a first step to enable flashing of a rooted firmware.
Click to expand...
Click to collapse
Since android 6.0, encryption of /userdata is supposed to have been standard. My understanding is that the partition is encrypted at first boot. It's probably encrypted with your personal key after you set a secure lock setting.
Regardless, won't boot without factory reset. You will lose your data if you want to use this firmware, but simply flashing it doesn't format /userdata. I can't say whether or not flashing back to stock triggers automatic factory reset, but sometimes it does.
I did confirm earlier today thought that you can't only flash the kernel. Phone won't boot, regardless of factory reset. Nor will it work with abl.mbn(I assume android boot loader), and xbl ( download mode?) But, the kernel is not fully permissive anyway. /system cannot be remounted rw, and I can't manipulate the files in /dev/block either.
---------- Post added at 10:57 PM ---------- Previous post was at 10:54 PM ----------
lilila said:
Is it possible to use the mentioned firmware for some carrier switching flashing on note 8, just like what they did to S8 in this thread: https://forum.xda-developers.com/galaxy-s8/how-to/snap-guide-flashing-standard-fw-carrier-t3625817
Click to expand...
Click to collapse
I'd like to try that, but insofar I noticed in Download mode it says the carrier is ATT. I think this might be set in the /efs but I could be wrong. If so, root can help. For the record, Verizon is the same model N950U as ATT.
Greetings all,
Been a couple years since I've visited these boards, I just picked up the note a couple days back. Am I reading this correctly that we can actually flash the verizon model with the engineering firmware to a more permissive setup without brick, or am I just exceptionally out of date and reading this wrong?
The.Jericho.Initiative said:
Greetings all,
Been a couple years since I've visited these boards, I just picked up the note a couple days back. Am I reading this correctly that we can actually flash the verizon model with the engineering firmware to a more permissive setup without brick, or am I just exceptionally out of date and reading this wrong?
Click to expand...
Click to collapse
Correct, its safe to flash the engineering firmware
hmm. interesting. now I just need to understand (or make sure I understand correctly) that/what is gained by using this firmware? Is root or bootloader unlocked gained by flashing this firmware? I would think this would be a hot topic and more people to chime in. Is there another thread somewhere where people are dissecting this firmware in more detail (based on what IS known)? Sorry, im just trying to simplify the subject. : )
~SG
I have successfully used this for carrier switching...Carrier Switching Guide coming soon....
SomeGuy2008 said:
hmm. interesting. now I just need to understand (or make sure I understand correctly) that/what is gained by using this firmware? Is root or bootloader unlocked gained by flashing this firmware? I would think this would be a hot topic and more people to chime in. Is there another thread somewhere where people are dissecting this firmware in more detail (based on what IS known)? Sorry, im just trying to simplify the subject. : )
~SG
Click to expand...
Click to collapse
THIS!! ^^
If this is true then I am trading in my Note 4 asap!
Though I have that sinking feeling in my gut that it may be too good to be true. As you've said, I too really feel like this info would have spread like wildfire if this was the case. I hope I am wrong!
Edit: I read a little more into it and it's pretty much just a carrier unlock. Not bootloader... :/
SomeGuy2008 said:
hmm. interesting. now I just need to understand (or make sure I understand correctly) that/what is gained by using this firmware? Is root or bootloader unlocked gained by flashing this firmware? I would think this would be a hot topic and more people to chime in. Is there another thread somewhere where people are dissecting this firmware in more detail (based on what IS known)? Sorry, im just trying to simplify the subject. : )
~SG
Click to expand...
Click to collapse
Root is now live
https://forum.xda-developers.com/galaxy-note-8/development/root-samfail-galaxy-note8-t3685340
jellyhead said:
Root is now live
https://forum.xda-developers.com/galaxy-note-8/development/root-samfail-galaxy-note8-t3685340
Click to expand...
Click to collapse
Thanks for the info. Damit, I have everything working just right in a non rooted fashion. And to be honest I kinda like it that way. But then again I do miss the typical root advantages.
~SG
I'll be waiting to see if the 80% battery issue gets solved.
I read that part. Yuk. That sucks. Ima hold out for a bit while it bakes in the oven a little longer.
I'm stoked that it does not trip knox...