hello,
I try to root my tablet with a downgrad by flashtool with the newest Version, but there is no way. After the reboot I have always the same actual version 5.1.1
There is a error during the flash process:
14/059/2016 09:59:42 - ERROR -
14/059/2016 09:59:42 - ERROR - Error dumping TA. Aborted
Is this the problem?
Thanks
Spot.Zwei said:
hello,
I try to root my tablet with a downgrad by flashtool with the newest Version, but there is no way. After the reboot I have always the same actual version 5.1.1
There is a error during the flash process:
14/059/2016 09:59:42 - ERROR -
14/059/2016 09:59:42 - ERROR - Error dumping TA. Aborted
Is this the problem?
Thanks
Click to expand...
Click to collapse
Are you saying your downgrade is not working? I'm not getting any luck from the forums myself and I see some folks posting in other threads with weeks pass since last post.
I botched a previous install with an incorrect WiFi firmware, so I ended up flashing a 5.1.1 worldwide-wifi TW for my sgp512 just to get it up and running and it's running great.
Now I'm researching how to root and it does appear you will have to be at least 5.0.2 (it may be that a 4.4.2 is preferred) in order for the root tools to work. Once rooted, you could then install a recovery (or dual recovery??) and then flash ROMs or flashable firmwares.
But I believe having 5.1.1 is not helpful for rooting the Z2 tablet at this time. Still researching and will post if I learn something different.
If you want to root without unlocking the bootloader, you have to be on Android 4.4. So if you are on LP, you have to downgrade to KK.
After installing the dual recovery, you can then upgrade to Lollipop.
Or do it the hard way and unlock your bootloader, Sony provides the description and tools needed on their page. Then you are free to do what you want (e.g. rooting by simply flashing SuperSU via a recovery). But note that you lose the DRM keys and the automatic Sony updates.
Hope this helps. Further information can be obtained by searching the forums
thanks a lot.
the problem is still present.
I try to flash a old KK-Firmware, but there is the error message anyway.
I try to unlock my bootloader with the sony-tool (with a special number), but I got no answer from Sony.
KingRoot 4.6 has been released, she can root 5.1 well and some 6.0 devices
I found this one on other thread about king root
http://forum.xda-developers.com/devdb/project/dl/?id=17287
For some try and fail in using http://mobilego.wondershare.com/
finally
I use kingroot.apk install in my Tablet Z2 SGP512 and root successed.
http://forum.xda-developers.com/devdb/project/dl/?id=17287
It worked perfect. On my SGP521
This worked for me on SGP561 on 5.1.1
Related
hi, i have a problem with my tablet, i tryed the tool ALLinOne and first i rooted my device and it was fine.
after that i installed rescue-backdoor and the tablet installed the 3.2.1 android again. and i lost the root.
but the problem is, i can't root my tablet anymore now. i get the message:
your kernel version ... has been locked down
Hi,
If you have kernel build #10, then you can't root.
The problem is that once you have root and applied rescue-door, then you should NOT update, otherwise you loose all your changes.
The main problem is that seems that the new update you downloaded brings build 10... so you can forget root for a time.
Regards
maybe it is possible to install a other OS via the recovery mode?
Not without root ... sorry for this bad news ...
Now you only can wait for ICS update.
May be there is a little chance to change the unfortunately situation.
Hey guys need alittle help getting my head around rooting my spg611.
Which process would you recomend?
Will any of these methods work?
1. Downgrade to 5.0.2 with flash tool
2. Root with kingroot
3. Install dualrecovery
4. Flash a prerooted 5.1.1
Or
1. Downgrade to 4.4.4
2. Root with gieroot
3. Install dualrecovery
4. Flash prerooted 5.1.1
Root
Hi,
I used the desktop version of this on my SGP612.
Works fine.
ziggiesden said:
Hi,
I used the desktop version of this on my SGP612.
Works fine.
Click to expand...
Click to collapse
Sorry, the desktop version of what?
Kingroot
Kingroot - It somehow did not paste in the link? That is kingroot.org if you google it.
Weird, they don't let you post outside links initially.
One other thing - every modded pre-rooted rom seems to have one or more issues - I'm keeping an eye on it all but Kingroot lets me do what I want so I'll keep it for the moment...
Kingroot & NTFS
I was trying to get NTFS working with this and I choose initially to go down the Paragon & Total Commander route.
Alas, it did not seem to work so I blamed it on Kingroot. I used XZDualRecovery to utilise TWRP to flash SuperSu to replace Kingroot.
Same issue as an NTFS formatted SD Card was not recognised. I'm wanting it in the hope that I can download torrents that have file sizes > 4GB.
I'm looking to see if I can get it to work utilising a Kernal mod now. Although Paragon just updated via playstore so I guess a better try it again first!
Anyone get it to work on their SGP612 or equivalent?
Did you get kingroot to work with lollipop 5.1.1?
as far as I got, it could only root 5.0.2 and then updated like a dummy to 5.1.1 and now I am stuck.
I tried this 1. Downgrade to 4.4.4
2. Root with gieroot
3. Install dualrecovery
4. Flash prerooted 5.1.1
but i can't downgrade. i boot loop after flashing old firmware and the exploit D6603 system.
Is it possible to downgrade to 5.0.2 instead of 4.4.4
Well the first post kind of answers that, lol
Downgrade to 5.0.2
1. Downgrade to 5.0.2 with flash tool
2. Root with kingroot
3. Install dualrecovery
4. Flash a prerooted 5.1.1
Or
1. Downgrade to 4.4.4
2. Root with gieroot
3. Install dualrecovery
4. Flash prerooted 5.1.1
5.1.1
Olivierica said:
Did you get kingroot to work with lollipop 5.1.1?
as far as I got, it could only root 5.0.2 and then updated like a dummy to 5.1.1 and now I am stuck.
I tried this 1. Downgrade to 4.4.4
2. Root with gieroot
3. Install dualrecovery
4. Flash prerooted 5.1.1
but i can't downgrade. i boot loop after flashing old firmware and the exploit D6603 system.
Is it possible to downgrade to 5.0.2 instead of 4.4.4
Click to expand...
Click to collapse
I flashed a Custom Rom that did not involve unlocking the bootloader (pre rooted with recovery) to solve the upgrade issue although my sdcard permissions need fixed with sdfix.zip - will do that next. Although I noticed a clean sgp11 ftf that looks good. I have my DRM keys backed up so I might have a wee go at that as it involves an unlock. I went a bit mad with the backups - used Titanium to back up it all, then used TWRP to do the same and also did three drm key backups. I'm mad about protecting my data - I backup to three HD's, a RAID5 array on one system and a RAID 6 array too! Mine is the 32GB SGP612.
My research indicated these write issues were a Kit Kat problem but it seems not. I will try to a couple of fixes out there, if not I'll go back a bit and try again. Android is a bit of a bugger with all these different flavours? I suppose it makes life interesting!
Edit: Fixed write issues with SDFix_R7 as it solved the permissions problem.
Or just use KINGROOT
Kingroot
I utilised Kingroot for quite a while. Although it did work ok 90% of the time it seemed that it was not a complete root solution. The prerooted firmware with SuperSu is the way you will eventually go.
I have just recently flashed to 5.11 with SuperSu, TWRP and then SDFix (see above) and am having no issues with anything. Stuck a 128GB SD Card form Sandisk into my SGP612 as my old Sony 32GB failed after 10 months. It is good for downloading torrents onto with ttorrent.
Overall I'm really impressed with the SGP612 and the mods you guys are doing - keep up the good work!
I think it won best tablet award of 2014 in one of the mags?
Hello Everyone,
I'm a first time poster but have been reading this site for weeks trying to find the answer to my questions. I've acquired a good bit of info but still wanted to clarify some things before I take the plunge.
I'm currently using a Verizon GS4 (I-545) running rooted stock MK2 jellybean. I rooted ~2 years ago to get rid of the bloatware and just never bothered upgrading/keeping up with the firmware updates. There are some new apps that won't work on my phone, but are working on my wife's stock GS4 on OF1. I'd like to upgrade my firmware (and keep root) so that I don't have to keep stealing her phone.
I've come across several threads discussing upgrading from one baseband to the next - none quite match my scenario. Most threads talk about how to upgrade and keep root but now that I'm late to the party, it seems like root methods have been discovered for all stock firmware versions (even OF1 by flashing OC1 kernel, rooting, and flashing back to OF1 kernel). So with this in mind, can I just skip all the complicated stuff and just use Odin to flash OF1 and then follow Edgardo_Uchicha's OF1 root method?
If I can use Odin to flash OF1, will the file I load in the "AP" slot also includes the proper modules, bootloaders, etc. to upgrade everything to OF1? Will it do a factory reset/wipe or will I keep all my data like an OTA? As for getting the Odin file, it looks like I should just use the Samsung site to get it directly?
If I can use the Odin method, are there any drawbacks? If I don't like lollipop I realize I'm stuck and can't go back, but is there anyway to upgrade and be able to go back (downgrade)?
Thanks again for your help!
Mike
Hello Mike,
You can flash OF1 and root via the method others and I posted, some people wrote that other rooting software/apps are starting to work on lollipop builds, I haven't tested yet(since my device have a custom rom and it's rooted) but soon I will and will update the thread. Btw, my suggestion to you is flashing this specific odin package:
[Odin][TAR] I545VRUGOF1 neutered (No BL)
I was on kitkat bootloader, flashed this OF1 build and went back to kitkat without problems
Good luck!
Edgardo_Uchiha said:
Hello Mike,
You can flash OF1 and root via the method others and I posted, some people wrote that other rooting software/apps are starting to work on lollipop builds, I haven't tested yet(since my device have a custom rom and it's rooted) but soon I will and will update the thread. Btw, my suggestion to you is flashing this specific odin package:
[Odin][TAR] I545VRUGOF1 neutered (No BL)
I was on kitkat bootloader, flashed this OF1 build and went back to kitkat without problems
Good luck!
Click to expand...
Click to collapse
So I followed the thread you linked and it looked like my phone upgraded OK. However, even at lock screen I get the message "Unfortunately, the process com.android.phone has stopped". It reappears as soon as I dismiss it...basically making my phone useless. I was able to navigate to the Settings page though and it says I'm on 5.0.1 but under baseband it says "Unknown" rather than OF1. It does show OF1 under the build number though. I'm guessing it didn't like the MK2 bootloader?
Any ideas how to fix? Help!!
mike2914 said:
So I followed the thread you linked and it looked like my phone upgraded OK. However, even at lock screen I get the message "Unfortunately, the process com.android.phone has stopped". It reappears as soon as I dismiss it...basically making my phone useless. I was able to navigate to the Settings page though and it says I'm on 5.0.1 but under baseband it says "Unknown" rather than OF1. It does show OF1 under the build number though. I'm guessing it didn't like the MK2 bootloader?
Any ideas how to fix? Help!!
Click to expand...
Click to collapse
Try wiping via recovery, if I'm not wrong this package does not wipe your phone so maybe there are some leftovers that are messing up the new system
You are correct, the OF1 Odin file you recommended did not wipe my data/apps. You were also correct in that doing a factory reset/wipe fixed the issue. I had some apps that were previously "frozen/disabled" while I had root so I have a feeling that didn't help things when it got updated.
Is there any way to confirm that I still have the MK2 bootloader?
mike2914 said:
You are correct, the OF1 Odin file you recommended did not wipe my data/apps. You were also correct in that doing a factory reset/wipe fixed the issue. I had some apps that were previously "frozen/disabled" while I had root so I have a feeling that didn't help things when it got updated.
Is there any way to confirm that I still have the MK2 bootloader?
Click to expand...
Click to collapse
Download and install terminal emulator, the run these commands:
1. su
2. getprop ro.bootloader
Awesome! I was able to confirm I'm still using the MK2 bootloader. Thanks for all your help!
I have my SGP612 (Wi-Fi only model 32gb version) and I had prerooted 6.0.1 but lack of access to custom recovery. Then I tried installing the custom recovery with the latest XZDualrecovery software and that ruined my tablet to go into bootloop. So the next solution was to try out in reverting back to Kitkat (or whatever software available I could grab here on XDA).
I also tried the Xperia Companion app to repair software, but that pushed it to upgrade to the latest Marshmallow version with no root or anything! Even now I reverted back to 23.4.A.0.546 (pretty sure this is Lollipop), I have all these service errors and it would go back to force restarting itself.
What to do?
GigaSPX said:
I have my SGP612 (Wi-Fi only model 32gb version) and I had prerooted 6.0.1 but lack of access to custom recovery. Then I tried installing the custom recovery with the latest XZDualrecovery software and that ruined my tablet to go into bootloop. So the next solution was to try out in reverting back to Kitkat (or whatever software available I could grab here on XDA).
I also tried the Xperia Companion app to repair software, but that pushed it to upgrade to the latest Marshmallow version with no root or anything! Even now I reverted back to 23.4.A.0.546 (pretty sure this is Lollipop), I have all these service errors and it would go back to force restarting itself.
What to do?
Click to expand...
Click to collapse
You try FLASHTOOL?? And you go everywhere kitkat,lolipop ... with no root.
I do it from 6.01 to 4.4 now (until google fix the usb storage issue).
tito1231 said:
You try FLASHTOOL?? And you go everywhere kitkat,lolipop ... with no root.
I do it from 6.01 to 4.4 now (until google fix the usb storage issue).
Click to expand...
Click to collapse
Although I didn't explicitly said it on my first post, that's how I'm trying to go back to older software. I will successfully flash, but i will have lots of processes crashing and errors, which then it will do a forced restart and repeat. Processes crashing such as com.Android.phone and etc.
gigaspx said:
although i didn't explicitly said it on my first post, that's how i'm trying to go back to older software. I will successfully flash, but i will have lots of processes crashing and errors, which then it will do a forced restart and repeat. Processes crashing such as com.android.phone and etc.
Click to expand...
Click to collapse
not the right firmware FOR YOUR TAB ??
tito1231 said:
not the right firmware FOR YOUR TAB ??
Click to expand...
Click to collapse
From @Spectre51 in the FTF collection thread:
US Retail - SGP612
23.4.A.0.546
1291-4653_R4C
Shall I attempt to bootloader unlock instead to be able to revert back to Kitkat, kingroot to install XZDualrecovery, then flash prerooted Marshmallow correctly?
Bump
When you used the flashtool, did you check the possibility to wipe data and the other two options? Can't say what they are at the moment, but you need a clean install.
Sent from my 401SO using XDA Free mobile app
the problem you are describing is happening if you dont check wipe data - always wipe data when downgrading or you get crashing processes
Hi guys,
first of all I want to salut everybody here as I am completely new to the Android world and that's indeed the best resource online. Thanks for that.
Now my big problem. As from the title, I downgrade my Fire HD 6 (4th gen) to 4.5.3 with adb sideload to root it with kingroot and everything went fine. I have then installed TWRP and everything went fine. I have then used TWRP to go back to 5.3.1 and I lost root and recovery. I managed to gain my root privileges back but as for the recovery not a chance. I tried to install TWRP again with dd from adb shell (as I can su) but once again nothing. Checking with fastback getval all, I do have a locked bootload:
Is this the reason why TWRP doesn't run anymore?
If yes, how can I unlock it back?
Is this what's meant with boot loader loop?
Thank you all in advance!
Edit 1:
maybe cuber.py may help but I can't find this file.
Edit 2:
ok found the tools here https://forum.xda-developers.com/kindle-fire-hdx/development/tools-create-unlock-img-fix-boot-img-t3050689
Edit 3:
I tried with cuber.py but the tool can't sign the img because it's not ANDROID. That's what it says. Now I am really stuck. Help please!
LM
I was in the exact same situation, so maybe I can offer some insight. I also have an HD 6 running 5.3.1 that I have downgraded to get root then upgraded a few times. Let me say that I am still learning too, and am by no means an expert but I can try to help.
As far as losing root, i'm not sure as that never happened to me. Did you flash the most up-to date SuperSu with TWRP or did you just answer yes when TWRP prompted you if you wanted root privileges? Flashing a SuperSu through TWRP will give you the SuperSu icon on your home screen once you upgrade back to 5.3.1, whereas just letting TWRP grant root access won't. You will still have root, but without the icon there's no direct control over it (at least not that I could find) so it's still there, just hidden.
My TWRP also replaced by the stock recovery upon updating back to 5.3.1. As far as I know, this is unavoidable. I believe it's as you suspect and is due to the 5.3.1 bootloader being locked. This would also explain why the process for rooting 5.3.1 is so involved as opposed to just using something like Kingroot. I also don't think there's anyone still doing active development on the HD 6 / HD 7.
If you really want to have both root and TWRP, you could try downgrading to an older OS that still has the feel of 5.3.1. I'm not sure about any other versions, but 5.1.1 is rootable via Kingroot (which should mean that it has an unlocked bootloader) and has the same exact UI as 5.3.1. So if you're feeling adventurous try downgrading to 4.5.3, installing TWRP, and upgrading to 5.1.1 instead of 5.3.1 (just be sure to block automatic updates!) and see if TWRP is still active. If so, root with Kingroot and you're good. If you still don't have TWRP, at least you're no worse off than you were.
If you do try this, please post your results here. I might try this myself. I am currently running stock. As I said, I went through the process a few times. For some reason SuperSu was causing erratic behavior in some of my apps and when I tried to switch my SU app to kingroot I lost root completely. I really didn't care about root enough to repeat the whole process again, but if I could keep TWRP it might be worth it. Anyway, good luck.
P.S. You may need to try rooting with Kingroot several times for it to work. I know for a fact that it can root 5.1.1 since I've done it on my own HD 6 when I was running 5.1.1. I'm not sure why it fails, but keep trying and eventually it will get root access. You may have to try 6 or 7 times but eventually it will work.
I went back and re-read this thread more carefully:https://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 and it turns out that TWRP doesn't play well with any 5.X.X bootloaders. Oh well, I was kind of hoping my idea would work. It turns out that you can use TWRP on your current rooted 5.3.1, but only on a temporary basis. Refer to the above thread post #2 for instructions. Basically, you put the correct 5.3.1 bootloader on your device then run AutoTWRP which will flash 4.5.3 bootloaders and TWRP for you. Reboot into recovery and you have your TWRP. You can then do whatever you want. The downside is that since you are running a 4.5.3 bootloader you can't get back into your OS, only TWRP. And once you flash your 5.3.1 bootloader to get back into your OS, TWRP no longer works. I know it's a pain in the arse having to connect to a PC and run a batch file every time you need to use TWRP, but at least it's a sort of workaround.