I think I am in the right place?
I am jumping from apple to the dark side and I would like to know if you can root without touching the boot loader on z2 tablet and is unlocking the boot loader for use of roms and kernels I have moved from the iPhone to note 3 and now it’s time for the iPad to go i like the of the Note 10.1 2014 but the Xperia z2 tablet looks even better I have read that you should back up the ta partition to keep drm keys to restore for warranty use on the Xperia z and just wanted to now it was the same for the z2 tablet? any help would help thanks for looking.
john09121 said:
I think I am in the right place?
I am jumping from apple to the dark side and I would like to know if you can root without touching the boot loader on z2 tablet and is unlocking the boot loader for use of roms and kernels I have moved from the iPhone to note 3 and now it’s time for the iPad to go i like the of the Note 10.1 2014 but the Xperia z2 tablet looks even better I have read that you should back up the ta partition to keep drm keys to restore for warranty use on the Xperia z and just wanted to now it was the same for the z2 tablet? any help would help thanks for looking.
Click to expand...
Click to collapse
I also use Apple devices, and i would call iOS "the dark side" as one never knows what is going on there, and why so many restricitions XD
Aside from that, you can root the Z2 tablet perfectly without unlocking the bootloader, and you will always be able to do it. If Sony ever releases a new firmware with rooting exploit patched, then you will always be able to downgrade, root, and update with a pre-rooted firmware. All without touching your bootloader. Downgrading to any firmware is allowed here.
Anyway it is a good idea to backup the TA partition of your device if you ever decide to go the bootloader unlocking way, so you can restore your device to 100% factory state later.
Have fun.
Both Google and Apple are dark sides... we don't live in a world of light and dark; sadly we live in a world of grey... dark grey...
Here is what you need.http://forum.xda-developers.com/showthread.php?p=53448680
I would also recommend this thread out afterwords. http://forum.xda-developers.com/showthread.php?t=2785598
Related
i recently broke my last phone, so i had it replaced and this one is running 2.3.6, i tried using that black white screen (cmd?) with the options ex: 1. unlock root etc.
2. CWM install/root etc etc. x. debugging etc
but no luck ._. is there some guide somewhere?
when i reach the rsd lite portion of the first section, my phone just boots up into the os and rsd lite gets cancelled, any ideas? ( i chose 2.3.4)when i first got it, i could do everything fine, but i couldnt boot after installing 3 different roms.
but when i install clean software it works just as it should
and when i press apply fix for "failure to boot" etc. it unlocks fine, but i cant install roms without it freezing at the dual core screen
Sounds like you got a replacement that motorola locked down the bootloader on. Everything will go as planned but you wont get unlocked. Been happening more and more to people getting replacement phones. Until a different way of unlocking is found (other the sbf flashing or fastboot flashing the unlock files) youre stuck with stock, but you can root. Bad luck.
pre4speed said:
Sounds like you got a replacement that motorola locked down the bootloader on. Everything will go as planned but you wont get unlocked. Been happening more and more to people getting replacement phones. Until a different way of unlocking is found (other the sbf flashing or fastboot flashing the unlock files) youre stuck with stock, but you can root. Bad luck.
Click to expand...
Click to collapse
how do i fastboot flash the unlock files? and since this phone is older, would anyone even try unlocking the newer models?
and im VERY disapointed in these new models, mabye its just mine, but on mine, the screen is litterally popping out, and theres a faint white square that borders the actual lcd, and the on/off/fingerprint scanner barely has any click so its hard sometime to know if u pressed it or not .... damn you moto, im not buying another one of your phones after this one, HELLO GS3 :d
wasssabi5 said:
how do i fastboot flash the unlock files? and since this phone is older, would anyone even try unlocking the newer models?
and im VERY disapointed in these new models, mabye its just mine, but on mine, the screen is litterally popping out, and theres a faint white square that borders the actual lcd, and the on/off/fingerprint scanner barely has any click so its hard sometime to know if u pressed it or not .... damn you moto, im not buying another one of your phones after this one, HELLO GS3 :d
Click to expand...
Click to collapse
If youre already seeing those type problems, you might want to notify warranty department again. Sounds like a dud replacement. As for the fastboot thing, check out the stockier noob guide first then search for those files. I dont have them anymore or I'd pass em to you.
Sticky, not stockier
I can help you using the same process I went through with my phone, but I have to warn you I won't be responsible for anything that happens to your phone. If interested PM me
sent u a pm but u didnt answer
Hey every1
Well been using android phones for a few years now but finally decided to treat myself to a tablet and aimed high with the tablet z So far very happy with my new tablet. But with all android devices the root and recovery bug has struck, problem is compared to my phones its another manufacturer with different ways of rooting and different system menus etc so im a little lost :/
So heres my questions
* "Doomlord easy root" seems to be the one stop shop for rooting but I was wondering how do you unroot? Do I just use seus to factory reset and that resets root?
*I currently use a 32GB wifi (SGP312 GB/B) model 10.1.c.0.370 firmware , but is there a central hub like sammobile for firmware downloads? Or is a copy of my current firmware required to have in case of emergency or will SEUS correct most problems???
* I also see CWM available for the tablet z but my understanding is to get CWM u have to unlock bootloader but this loses the bravia engine, is this correct? or what else do I lose?
* Does the tablet Z have any button combinations for stock recovery etc and if so what is the currently know button combinations and what service menus do they access?
thanks for any answers you guys can help me with, as its my 1st tablet and a new brand that ive not used before I just don't wanna jump before ive got my facts together
I'm new to rooting myself and I don't know how you might unroot the device, but with my SO-03E .269 rooted I installed SuperSU and the 'disable Superuser' appears to function properly as a temporary unroot. Maybe that'll help you?
I think the Fastboot key combo is power and volume-up.
http://forum.xda-developers.com/showthread.php?t=2287881
very informative for beginners. after you read that ask again here in your thread if there still are any questions
K found the button combo info but still looking for the rest, the link was helpful but really only got me the basic info I already knew about its the particular answers im looking for.
Hey guys, please forgive me for any bad etiquette or lack of information (any information I can provide is available upon request if I leave anything out). I am new to forums in general and especially to XDA, which seems like a good place to get help.
I recently purchased a Sony Xperia Z2 Tablet from Craigslist under the assumption it was a fully unlocked tablet not associated to a carrier. Turns out it was a Verizon Z2 tablet. I dislike Verizon with a firey passion and without getting into too many details, I'm fairly certain they won't help me because a) this tablet wasn't purchased through them as a customer and b) Verizon and I have bad history (unauthorized account modification, shady charges, etc.)
So I thought I'd do my best to make the tablet mine since the asshole who sold it to me has ceased all contact and I don't know how to get a hold of him anymore. No receipt and a data-less tablet.
Anyway, I successfully rooted the tablet and began installing apps that I installed for my G4 when I rooted it (SuperSU, Adaway, Greenify, etc.)
Things were going well but I realised I wanted anything that had to do with Verizon removed from the tablet so I was going to flash Cyanogenmod onto it with a guide I found online. Now rooting and installing custom recoveries was familiar territory and I did these flawlessly. It had TWRP and I made a backup of the system -no Nandroid, sadly-and I began the flashing process. The process said it completed without issue and I went to reboot my device. Enter my current situation:
The device, when I attempted to turn it on, all it did was vibrate constantly until I let go of the power button. Attempting to enter recovery mode (green LED, power + vol down) it showed me, instead of TWRP, a very basic recovery mode with basic options. "Continue booting up", "enter safe mode", "system recovery", and "power down". I tried entering safe mode and it just shut back down, I tried doing a system recovery and it shut down. The only time I ever see the "SONY" logo is if I'm entering this mode. I can enter what I assume is "fastboot mode" (power + vol up and plugging the device into a PC). Nothing on the screen but the LED is blue. I am trying to find guides to restore it if I can and it all looks promising but the only things I know how to really do are root and install custom recovery. I know there are PC tools I can use to send commands to it while it's in fastboot, or send commands in general I just don't know where to begin.
Does anyone know how to fix this? I know it was from Verizon, which sucks, and I know the problem most likely occurred with the attempted flashing of Cyanogenmod. I think I read somewhere I might have done something regarding mismatching kernal numbers. I couldn't find a way to unlock the bootloader so I assume that had something to do with it too.
If someone could give me a guide to restore it to at least its stock ROM where I can begin rooting and installing a custom recovery again, that would be great. Even better would be just flashing a ROM on there that doesn't need Verizon or being able to take it to a stage where it's unlocked and the only evidence it was ever with a carrier is the Verizon logo on the back. I'd really hate to think I wasted money on this and now I'm at a dead end because of a mistake I made. This was supposed to be a gift for my mom on her birthday which is coming up soon. So if anyone knows anything, or has a guide where we can at least get the thing bootable again and I'll just try and deal with a rooted locked device, that would be great.
Thanks for considerations,
Marmalade_Shaws
I have spent time on that screen too.
2 things
1. .. If you installed dual recovery, there is an up, down sequence to select the recovery.
2. Find a downgrade guide, use flashtool to flash. Ft back to stock.
Also you need to know what hardware you are running..511, 561.. And use the proper version.
There are some options with the flashtool and prf maker that can remove branding and vendor stuff. I have not tried those options.
Ez-go said:
I have spent time on that screen too.
2 things
1. .. If you installed dual recovery, there is an up, down sequence to select the recovery.
2. Find a downgrade guide, use flashtool to flash. Ft back to stock.
Also you need to know what hardware you are running..511, 561.. And use the proper version.
There are some options with the flashtool and prf maker that can remove branding and vendor stuff. I have not tried those options.
Click to expand...
Click to collapse
Sorry if this is late... But where can I find the stock? I've searched everywhere and I would need to do it from a flash tool on my PC? I could use all the help I can get.
I just had a very similar experience to the OP, seemingly identical in every way, and am curious if anyone has a solution.
ADB won't function at all, and the bootloader has blocked any sort of flashing via fastboot. Can't boot into TWRP, it goes into a very minimal "recovery," which I imagine is the stock tool, and the Factory Restore option there does absolutely nothing. Flashtool would work great if ADB / Flashmode was at all functional (device blinks and vibrates in a fashion typical of something bricked, and no connection is picked up).
Verizon Z2 Tablets are 561s.
This thing dead or is there some way to push back onto it?
Please, I hope somebody doesn't start berating me for not reading XDA posts about my Verizon Galaxy Note II more thoroughly. I have read many over recent years and been saved by quite a few during the hacking of my SCH-I605. Furthermore, I've been working in software development and network administration for decades now, so please don't somebody suggest I not mess with rooting my phone, custom recoveries, et cetera. I am here asking questions to make sure I don't hard brick my phone. Not asking resulted, about two months ago, in almost succeeding at Kobol's very interesting "short the tiny resistor" mode of getting out of a boot loop. I have a fully functioning phone now running rooted Kitkat and it's a sturdy platform, runs really great after I melted most of the bloatware and froze the rest (in case I ever need it), but I'd still like to move on to Lollipop and there is only one means for doing so which I know of (CyanogenMod), which I think may be problematic unless I am able to reflash an earlier ROM with unlocked bootloader.
The basic question I need verified is multi-part but basically boils down to this:
1. Is it or is it not true that if one is at baseband version I605VRUFND7, the bootloader is locked and one cannot install a custom recovery? (I think I read that in a few places anyhow.)
2. Is it or is it not possible to flash back to I605VRALJB from rooted I605VRUFND7?
3. Is flashing back to I605VRALJB, then installing TRWP or CWM, then using custom recovery to flash the latest CM12.x the best and only way to get from rooted Kitkat to rooted Lollipop?
4. I know there are some functional improvements in Lollipop but are they really that significant? I like the whole "material" thing which comes with Lollipop, but not at the price of loss of functionality.
Anyhow, here's my little sob story, which has a happy ending -- perhaps some of these details will elucidate my situation and lead to better answers:
I got tired of waiting around for Lollipop and had been unrooted by Kitkat for almost a year when I rooted again back in July 2015. I had wanted to go with the latest CyanogenMod Lollipop version, but ran into problems first using Heimdall (which refused to properly connect and write) and then trying Odin (against best advice post-root) to install a custom recovery (preferred TWRP but would go with CWM). Always led to that "unauthorized software" boot screen, which then necessitated reinstalling stock Kitkat and rerooting (I found the Ghettoroot .BAT file worked okay.) All was well, I was too busy to think about Lollipop but I woke up one morning about a month after I rooted Kitkat to find my Note II was stuck on red Verizon book splash-screen. Found a great article and YouTube showing all the keypress sequences which might exit a Note II from been stuck in boot -- but unfortunately not until after my further finagling just left me with a dead no-display-at-all device. I undertook Kobol's method, which requires partially reassembling the Note II's electronics outside its case and attempt to reboot with a very tiny screwdriver shorting a minute resistor on the motherboard right adjacent to the CPU -- I did in fact see the screen flash on briefly -- but I held my little screwdriver down too hard, accidentally gouged out the tiny resistor, and ended up buying a refurbished motherboard which very likely may have been scavenged from a stolen phone before going on sale on eBay. New motherboard worked great, I erased the original owner's info and data and proceeded to reinstall and root Kitkat. (Motherboard was already at I605VRUFND7) when I received it.
Anyhow, I also tried to install a custom recovery after I had new motherboard and rooted Kitkat. Using the TWRP Manager app put me back on the "unauthorized software" boot failure screen from Verizon, but I was able to Odin back Kitkat easily enough without losing my apps and configuration data. I believe I tried to use ROM Manager and Flashify as well -- but didn't find those apps very cooperative (though I didn't bother to upgrade to "pro" level on any of these in cast that matters). Unless I am mistaken, all these apps just place a zipped update file in the root of my internal SD card and then just hand it over to the Note II's stock recovery. I figured I just needed to stop and regroup later. That was a few weeks now.
Honestly, after the ordeal of having to replace a broken motherboard, and also -- after having looked at Verizon, Sprint and AT&T and the new Galaxy devices with no removable back and cracking the phone open necessary to replace the battery or upgrade the hidden microSD card and not liking that one would have to pay $600 over two years for a smartphone even further crippled at the cell carriers' requests -- it's even more important to me to be careful not to damage my Note II. (In fact, my Note II had turned out to be irreparable, I might even have even bought a refurbished unlocked Note 2 or 3 or 4 -- Samsung has made a real error on their latest generation of phones with their sealed backs and no user-accessible microSD reader.)
Yet, perhaps naively, I really do want to move on to Lollipop and even Marshmallow when CyanogenMod makes that available. So I really would appreciate it if you guys can verify whether what I intend to do (downgrading to pre-Kitkat in order to install custom recovery and then CM12.x) is workable? Or if there's a better solution? Or if I should just be content to have Kitkat rooted with all the fat cut off?
Many thanks. Hope my digression was not too long. Please don't anybody yell at me. XDA Developer's web forum is so full of very useful write-ups but unfortunately also some incorrect information and a lot of just plain useless posts -- it's really difficult sometimes to tell posts by guys who are actually experts from post by well-meaning folks with a lot of ideas but not so much expertise specific to SCH-I605 and VRUFND7. And I really need to get this right. (Granted that nobody on the forum can be held culpable should on mess up my phone based on their advice.)
Thanks once again!
I did a quick search of the forums and even contacted Sony because someone told me they could help and I believed them.
Anyway I parted ways with Verizon after a disagreement but got to keep my Xperia Ztab 2 I bought from them. I rooted and debloated it but when I attempted to install a custom ROM and realized I'd picked the wrong one it was too late and the tablet soft bricked.
This is my first time dealing with a failed root and soft-bricked device. I've dealt with root and flashing and installing recoveries but this is my first experience with a soft brick.
I was wondering if anyone could point me toward a resolution. The device can only be interacted with through the hardware buttons and there is no user interface. When it turns on it vibrates incessantly and there's an LED light. I was told it was recoverable but I don't know how to do it. I know I need a compatible stock or rooted ROM but I don't know which steps to take.
Can someone help me find the proper ROM and give me a list of steps I should take (or reference me to one)?
Thanks guys.
Basically I just want to get the stock back so I can begin the rooting process again. Does it have to be Verizon at this point or with it the way it is can the international ROM work?
If anyone has ideas or could help I'd appreciate it.
Use flashtool to flash an ftf file to it. Use xperifrm to download the files to create one. Just Google for guides for both of those pieces of software. Hold down the volume down button and when the guide tells you to connect it you plug it in with the button still held down.
Sent from my SGP512 using Tapatalk