Hi all!
I'm new here, so please instruct me if I'm doing anything wrong.
I have a Coolpad Y82-820. It's a Chinese phone, I think.
I'm in the process of getting it rooted. ---- Was rooted before, but an update on their side (to CoolUI V24. [phone model#]. 160407) removed the root and now makes it a bit difficult to root at the moment, though I'm sure it will be done eventually. For those who have this phone, I'd suggest not to update, as this update deletes any rooting applications installed on reboot/restart.
Once rooted, I don't really mind waiting, I would like to put a Custom Rom on this phone, but not sure what options are available. I see posts about the Coolpad Note/Dazen/Shine/Rogues etc. Though nothing about this one, though spec wise it's not too far off from the others.
I'd be grateful if anyone could help with confirmations, information, on how to select a correct custom rom for this device and the steps to do. Also if there's any info on how to root this current version, even better.
Thanks!
Some details of the phone below:
Model Number
Coolpad Y82-820
CPU
Qualcomm Technologies, Inc MSM8916 Quad-core 1.2 GHz
RAM
2G
Internal memory
Total 8G
Resolution
960 * 540
Android version
4.4.4
Kernel version
3.10.28
[email protected] #1
Thu Apr 7 17:01:56 CST 2016
Build number
4.4.005.150730.Y82_820
Any help possible?
Rooting maybe? Even possibly downgrading would be an option.
Johny2k9 said:
Any help possible?
Rooting maybe? Even possibly downgrading would be an option.
Click to expand...
Click to collapse
Did you try towelroot?It's best for rooting Kitkat.https://towelroot.com/
Røbin said:
Did you try towelroot?It's best for rooting Kitkat.https://towelroot.com/
Click to expand...
Click to collapse
Gave it a shot. Failed, as well. I've tried most of the popular rooting apps. King Root, Kingo, One click, and so on as well as a few Chinese rooting apps, as well. They've all failed.
The previous version was rooted with King Root though.
Johny2k9 said:
Gave it a shot. Failed, as well. I've tried most of the popular rooting apps. King Root, Kingo, One click, and so on as well as a few Chinese rooting apps, as well. They've all failed.
The previous version was rooted with King Root though.
Click to expand...
Click to collapse
In that case you have to root your phone manually by unlocking bootloader.But as a Chinese phone don't need to unlock bootloader.But you need to have a recovery that can install flashable zip.Most of this phone have built in recovery.You can go to recovery by turning off your phone and press power+volume down button.Then see if there's any option to install zip.
Røbin said:
In that case you have to root your phone manually by unlocking bootloader.But as a Chinese phone don't need to unlock bootloader.But you need to have a recovery that can install flashable zip.Most of this phone have built in recovery.You can go to recovery by turning off your phone and press power+volume down button.Then see if there's any option to install zip.
Click to expand...
Click to collapse
There is an option there to install zip files. Though I do not know the process well of doing so. Most zips I have tried have failed. I did install GMS several days ago using the install zip method. Not certain if that was a good idea though...
If I can find a flashable zip then I wouldn't mind giving it a try. I've restored this phone countless times hoping to go back to factory firmware, but that doesn't seem to be the case. It seems to go back to the most recent updated OTA which makes it unable to root with regular apps at the moment.
Not sure what the closest phone model for this phone would be. If you have ideas I'm willing to give them a shot an report back in with any findings.
Johny2k9 said:
There is an option there to install zip files. Though I do not know the process well of doing so. Most zips I have tried have failed. I did install GMS several days ago using the install zip method. Not certain if that was a good idea though...
If I can find a flashable zip then I wouldn't mind giving it a try. I've restored this phone countless times hoping to go back to factory firmware, but that doesn't seem to be the case. It seems to go back to the most recent updated OTA which makes it unable to root with regular apps at the moment.
Not sure what the closest phone model for this phone would be. If you have ideas I'm willing to give them a shot an report back in with any findings.
Click to expand...
Click to collapse
https://download.chainfire.eu/696/supersu/ go to this link,download UPDATE-SuperSU-v2.46.zip and install it.This is the way to have root manually.
Røbin said:
https://download.chainfire.eu/696/supersu/ go to this link,download UPDATE-SuperSU-v2.46.zip and install it.This is the way to have root manually.
Click to expand...
Click to collapse
I got an error:
正在查找更新包
正在打开更新包
正在验证更新包
E : failed to verify whole-file signature
E : signature verification failed 安装失败
我会汉语一点儿，所以这个汉字我都明白了，如果你有问题我可以试一试告诉你。 My Chinese isn't too bad, so if there's something you don't understand let me know.
Letting you know the steps I did, just in case I did it wrong.
- Downloaded the UPDATE-SuperSU-v2.46.zip
- Placed it on the phone internal memory (recovery only recognizes internal)
- Powered off
- Went into recovery mode
- Then tried installing the file.
Then the mentioned error.
Should I have restored the phone to the most recent OTA, cleared cache, data, first etc?
Johny2k9 said:
I got an error:
正在查找更新包
正在打开更新包
正在验证更新包
E : failed to verify whole-file signature
E : signature verification failed 安装失败
我会汉语一点儿，所以这个汉字我都明白了，如果你有问题我可以试一试告诉你。 My Chinese isn't too bad, so if there's something you don't understand let me know.
Letting you know the steps I did, just in case I did it wrong.
- Downloaded the UPDATE-SuperSU-v2.46.zip
- Placed it on the phone internal memory (recovery only recognizes internal)
- Powered off
- Went into recovery mode
- Then tried installing the file.
Then the mentioned error.
Should I have restored the phone to the most recent OTA, cleared cache, data, first etc?
Click to expand...
Click to collapse
Ok i'll give you a last solution to root your device.
first go to this linkhttp://www.file-upload.net/download-7267586/usb_driver.rar.html and download the driver file and extract the file.Now first enable developer options in your phone to enable usb debug and connect your phone to pc.In your pc right click on Computer/My PC icon and go to manager.click device manager and you will see your connected device.Now click on your device and find install driver,go and find the extracted file to install driver.After installing driver download root genius from this linkhttps://mega.nz/#!G4US0aTA!rfkmf4GSUJ75FSpq3_OBzKw58WLlExImjzlHVti5rbM,Install it and open the app.Your device will automaticlly connect to root genius.Now the final step is to click root word,click the green box,wait for 10 minute to complete the rooting process.your phone will reboot.all done.now check your device if its rooted or not by installing root checker app via google play store.
Røbin said:
Ok i'll give you a last solution to root your device.
first go to this linkhttp://www.file-upload.net/download-7267586/usb_driver.rar.html and download the driver file and extract the file.Now first enable developer options in your phone to enable usb debug and connect your phone to pc.In your pc right click on Computer/My PC icon and go to manager.click device manager and you will see your connected device.Now click on your device and find install driver,go and find the extracted file to install driver.After installing driver download root genius from this linkhttps://mega.nz/#!G4US0aTA!rfkmf4GSUJ75FSpq3_OBzKw58WLlExImjzlHVti5rbM,Install it and open the app.Your device will automaticlly connect to root genius.Now the final step is to click root word,click the green box,wait for 10 minute to complete the rooting process.your phone will reboot.all done.now check your device if its rooted or not by installing root checker app via google play store.
Click to expand...
Click to collapse
Also failed.
I guess it's too difficult to root this new version/update. If only I could downgrade then it might be possible to root.
Johny2k9 said:
Also failed.
I guess it's too difficult to root this new version/update. If only I could downgrade then it might be possible to root.
Click to expand...
Click to collapse
There's no available firmware to downgrade. Bad luck for you.
Røbin said:
There's no available firmware to downgrade. Bad luck for you.
Click to expand...
Click to collapse
Is upgrade impossible without rooting?
Johny2k9 said:
Is upgrade impossible without rooting?
Click to expand...
Click to collapse
You can upgrade or downgrade your android version without rooting but it has to be official firmware. If you want to flash custom rom you'll need custom recovery installed and unlocked bootloader.
Røbin said:
You can upgrade or downgrade your android version without rooting but it has to be official firmware. If you want to flash custom rom you'll need custom recovery installed and unlocked bootloader.
Click to expand...
Click to collapse
I wouldn't mind upgrading. Though what would be the process to get the official firmware?
Johny2k9 said:
I wouldn't mind upgrading. Though what would be the process to get the official firmware?
Click to expand...
Click to collapse
I think you didn't get what I said.You are already using updated android version. You can't update more if your service provider don't give anymore updates.And I also searched very hard to find official firmware for your device but unluckily your phone have very less information in web.So there's no one haven't uploaded any firmware or no discussion available for your device.You can though upgrade your device using custom rom but you need to have root and custom recovery .without root you can't install custom recovery.
Røbin said:
I think you didn't get what I said.You are already using updated android version. You can't update more if your service provider don't give anymore updates.And I also searched very hard to find official firmware for your device but unluckily your phone have very less information in web.So there's no one haven't uploaded any firmware or no discussion available for your device.You can though upgrade your device using custom rom but you need to have root and custom recovery .without root you can't install custom recovery.
Click to expand...
Click to collapse
Hahh... So after combing through various Chinese sites and using my limited knowledge of Chinese, I've got a ROM (previous version before there update), got the appropriate flashing software (CoolPad Download Assistant) and have successfully flashed it after disassembling the phone to get into fastboot.
Good news:
I am Rooted... again. With KingRoot.
Bad news:
The CoolPad has there update in the background. Found where it's stored and deleted. The Phone re-downloads the update.
A restart will probably update this phone making it un-rootable again.
Edit: Deleting the update file before immediately restarting gives an error in the update on restart, so I guess that's a good thing.
For now, I will just operate for now without turning the phone off. Though I do have the necessary files if I have to flash it again.
Rooting is the first requirement you mentioned... what do I need to do next? Download what? Compatible ROM's etc?
Johny2k9 said:
Hahh... So after combing through various Chinese sites and using my limited knowledge of Chinese, I've got a ROM (previous version before there update), got the appropriate flashing software (CoolPad Download Assistant) and have successfully flashed it after disassembling the phone to get into fastboot.
Good news:
I am Rooted... again. With KingRoot.
Bad news:
The CoolPad has there update in the background. Found where it's stored and deleted. The Phone re-downloads the update.
A restart will probably update this phone making it un-rootable again.
Edit: Deleting the update file before immediately restarting gives an error in the update on restart, so I guess that's a good thing.
For now, I will just operate for now without turning the phone off. Though I do have the necessary files if I have to flash it again.
Rooting is the first requirement you mentioned... what do I need to do next? Download what? Compatible ROM's etc?
Click to expand...
Click to collapse
If you have no interest in custom rom and now you can root your device then you don't need to do anything right now.And you are saying new update automatically downloading,just in download setting select "do not auto download"or"update via wifi only"this will prevent from auto downloading update.
Røbin said:
If you have no interest in custom rom and now you can root your device then you don't need to do anything right now.And you are saying new update automatically downloading,just in download setting select "do not auto download"or"update via wifi only"this will prevent from auto downloading update.
Click to expand...
Click to collapse
I disabled the update part, thank you.
I would prefer a custom rom, what options would I have?
Johny2k9 said:
I disabled the update part, thank you.
I would prefer a custom rom, what options would I have?
Click to expand...
Click to collapse
Not sure if there's any custom rom available for your phone You can somehow install custom twrp recovery but the main problem is custom rom availability.But I would suggest you to use xposed instead installing custom ROM.You can customize and control your device using xposed installer.
Røbin said:
Not sure if there's any custom rom available for your phone You can somehow install custom twrp recovery but the main problem is custom rom availability.But I would suggest you to use xposed instead installing custom ROM.You can customize and control your device using xposed installer.
Click to expand...
Click to collapse
Installed Xposed Installer, but the Download section is empty.
I am in China currently, so a lot of things may be blocked. A VPN should fix this, I believe.
What things I should install. Xposed Installer is new to me.
Related
Hello Everyone,
I badly need help on my Huawei Honor U8860 phone. I have recently updated it from 2.3.6 to 4.03 over WIFI and the update went smoothly. So now here is what my phone have:
Kernel Version: 3.0.8-perf-00059-g3a757a2 [email protected] #1
Build Number: U8860IV100R001C00B923SP01
I have not rooted the phone at this time. It was working fine until 2 days ago when I started getting messages on the screen like:
"Unfortunately, 2D Home has stopped"
"Unfortunately, Google Play has stopped"
"Unfortunately, Contacts has stopped"
"Unfortunately, Settings has stopped"
"Unfortunately, Google Play Music has stopped"
"Unfortunately, Browser has stopped"
And so on, and so forth. It seems that all apps and processes have stopped when I try to use them so I literally can't use the phone. I went through several threads here just trying to restore my phone back to a
working state. I tried to do the following in order but without success:
1.) Factory data reset / erase everything - the phone boots to the recovery menu then it formats the /Data, /Cache and /HWUserData then it reboots. After reboot, the phone is back to where it was before the factory data reset with everything in it including downloaded apps.
2.) Manually uninstalled all downloaded apps. Removed screen lock (just to see if phone behavior changes). Then rebooted the phone but after reboot, all the apps are still installed and the screen lock is back as well.
3.) I tried to Force Update with the following official ROMs: B886, B919 and B923 but I always get the message "Update failed" during the update process.
4.) I downloaded the file "recovery-u8860-en.img" so I can replace the "recovery.img" file . Rebooted the phone w/ the pink screen and connected it to my PC but there is no USB mass storage device mounted.
5.) Finally, I tried to root the phone. I enabled USB debugging. I installed the ADB drivers then I downloaded the U8860 root tools and rootexplorer.apk. When I ran the "root-me.cmd", it tried to copy some files to the phone but it failed. The error was "read-only file system".
So it seems that the problem is because of the "read-only filesystem". I does not permit/allow any changes made to the phone. Can you help me restore my phone?
Please.. Can somebody help me on this?
Thanks, clint2rose
clint2rose said:
Please.. Can somebody help me on this?
Thanks, clint2rose
Click to expand...
Click to collapse
I still did not find any solution for my problem. I read from this thread that all ICS versions can be downgraded.
http://forum.xda-developers.com/showthread.php?t=1552038&page=232
Is there a way to downgrade from B923 to B919? I think this will solve the problem I'm facing.
clint2rose said:
I still did not find any solution for my problem. I read from this thread that all ICS versions can be downgraded.
http://forum.xda-developers.com/showthread.php?t=1552038&page=232
Is there a way to downgrade from B923 to B919? I think this will solve the problem I'm facing.
Click to expand...
Click to collapse
try to back-up some of the data form the partitions that are full on your phone and delete them, maybe afterwards the stock-rom-flashing procedure will work again.
kaefert said:
try to back-up some of the data form the partitions that are full on your phone and delete them, maybe afterwards the stock-rom-flashing procedure will work again.
Click to expand...
Click to collapse
thanks for the reply. it did not work. I even formatted the internal SD. Re-run the firmware update but it failed. when i boot the phone, all the contents of the internal SD remains intact. any other suggestion?
I can remember there was some talk of "downgrade patches" to flash before official ROMs if downgrades failed
http://forum.xda-developers.com/showpost.php?p=36819830&postcount=2312
http://forum.xda-developers.com/showpost.php?p=36117718&postcount=2228
http://forum.xda-developers.com/showpost.php?p=35376103&postcount=2104
http://forum.xda-developers.com/showpost.php?p=34105274&postcount=1865
http://forum.xda-developers.com/showthread.php?p=32996711&highlight=patch#post32996711
working download linka (just tested them) -->
https://docs.google.com/file/d/0B4MkDBK_iI-gWEoyaWpEekRXT00/edit
http://www.huaweidevice.com/cn/downloadCenter.do?method=toDownloadFile&flay=software&softid=NDE5Nzg=
kaefert said:
I can remember there was some talk of "downgrade patches" to flash before official ROMs if downgrades failed
http://forum.xda-developers.com/showpost.php?p=36819830&postcount=2312
http://forum.xda-developers.com/showpost.php?p=36117718&postcount=2228
http://forum.xda-developers.com/showpost.php?p=35376103&postcount=2104
http://forum.xda-developers.com/showpost.php?p=34105274&postcount=1865
http://forum.xda-developers.com/showthread.php?p=32996711&highlight=patch#post32996711
working download linka (just tested them) -->
https://docs.google.com/file/d/0B4MkDBK_iI-gWEoyaWpEekRXT00/edit
http://www.huaweidevice.com/cn/downloadCenter.do?method=toDownloadFile&flay=software&softid=NDE5Nzg=
Click to expand...
Click to collapse
I downloaded the files from both links. Can you tell me how to flash my current ROM? Because when I tried to use the file like a regular ROM (I created dload folder then put UPDATE.APP in the folder, then ran firmware update.. the update failed)..
clint2rose said:
I downloaded the files from both links. Can you tell me how to flash my current ROM? Because when I tried to use the file like a regular ROM (I created dload folder then put UPDATE.APP in the folder, then ran firmware update.. the update failed)..
Click to expand...
Click to collapse
what do you mean by flashing your current ROM? Just like any other stock ROM put the dload folder on the sd-card and start the update procedure either from the settings menu or via the boot-key-combination.
Yes the way you discribed is the correct one for flashing those patches, If those patches also don't work, I'm out of ideas, sorry.
kaefert said:
what do you mean by flashing your current ROM? Just like any other stock ROM put the dload folder on the sd-card and start the update procedure either from the settings menu or via the boot-key-combination.
Yes the way you discribed is the correct one for flashing those patches, If those patches also don't work, I'm out of ideas, sorry.
Click to expand...
Click to collapse
Thank you once more for your time. Most of the thread I read regarding these patches often used the phrase" you have to flash the current version of your ROM using the patch"...
And yes I created dload folder, place the UPDATE.APP and put it on the sdcard. I turned off the phone and removed the battery. Then I pressed vol+ vol- and power on/off button. The firmware update went to about 70% installing before displaying update failed.
I guess I will have to bring my phone to a repair center. My only problem is that there is no Huawei service center at my place (I reside here in Saudi Arabia). I got the phone as a free device on a broadband package and the warranty is already expired. I'm a little worried to take the phone to the small mobile repair shops as they might screw up the phone even more. Huawei is not a popular device here unlike iPhone, HTC and Samsung Galaxy.
As I understood that your device is rooted, you should get some custom ROM and try to install it.
okty2k said:
As I understood that your device is rooted, you should get some custom ROM and try to install it.
Click to expand...
Click to collapse
No, my device is not rooted. I tried to root it but I get the message "failed to copy file: Read-only file system".
clint2rose said:
No, my device is not rooted. I tried to root it but I get the message "failed to copy file: Read-only file system".
Click to expand...
Click to collapse
you don't need to be rooted, you only need to have a custom recovery deployed (which you can either do with root permissions, or by using the pink screen method, but some newer stock roms (you said your on 932 or something? last non-locked working is b919) this has been locked and the device will not boot if the kernel or the recovery image has been manipulated.
I think you will have to find some (huawei-certified!) repair-center, small do-it-all phone-shops probably won't be able to take care of this problem for you.. I'm sorry but I don't see any other solution
kaefert said:
you don't need to be rooted, you only need to have a custom recovery deployed (which you can either do with root permissions, or by using the pink screen method, but some newer stock roms (you said your on 932 or something? last non-locked working is b919) this has been locked and the device will not boot if the kernel or the recovery image has been manipulated.
I think you will have to find some (huawei-certified!) repair-center, small do-it-all phone-shops probably won't be able to take care of this problem for you.. I'm sorry but I don't see any other solution
Click to expand...
Click to collapse
Ok. I will try to find a repair-center experienced in Huawei devices. I have one last question if you don't mind. Is it possible to erase everything on the phone? As in completely erase or reformat after which there will not be an operating system on the phone. I read in some threads that this is possible w/ custom recovery but I want to know if it is also possible for phones without the custom recovery. I'm hoping there might be some tool or something..
U8860 not responding
clint2rose said:
Ok. I will try to find a repair-center experienced in Huawei devices. I have one last question if you don't mind. Is it possible to erase everything on the phone? As in completely erase or reformat after which there will not be an operating system on the phone. I read in some threads that this is possible w/ custom recovery but I want to know if it is also possible for phones without the custom recovery. I'm hoping there might be some tool or something..
Click to expand...
Click to collapse
Have you find the solution yet? I have the same problem. Somehow my phone system is "locked". I can't install or uninstall app. Some google apps keep showing not responding. Everything changes i made, keep showing up after the phone rebooted.
This was happen a few days after I upgrade to ICS B932SP01 and rooted my phone (to remove original chinese apps).
Luckily i have friend in huawei indonesia. He gave my u8860 to the technical support. But the result was no good.
They try everything, even install my phone with the original GB and always failed.
The last suggestion is change the phone machine, which is as same as buy a new phone.
I really appreciate is someone can help me here...
Thanks
Greetings, fellow Mega-Maniacs!
I am currently working with dev Geohot to get us root access for the SGH-I527 with Baseband Version I527UCUBNE7. All known root methods have been tested and proven to not work with this version of android with this baseband, due to the extremely locked down nature of Samsung Knox on this device.
I, personally, have been throwing every exploit I can think of at this device, to no avail. As of the time and date of this post, we have a donor ready to help the cause (Special thanks to caguas56). That is why I'm proposing a bounty on root access for this phone (SGH-I527 AT&T US version only, although there is a high possibility that it'll work on the Sprint,T-Mo and VZW variant).
The first developer who can successfully get ROOT on KitKat with baseband I527UCUBNE7 and demonstrate this with a successful public test will be awarded the bounty. The bounty will be split equally between devs and donors willing to team up.
I'm in for $10 at the moment, and I'll piss away more if needed down the line.
Who else is in? LETS GET THIS DONE, PEEPS!
Please, only posts regarding root access on this thread. For firmware rollbacks to 4.2.2, see azpatterson3's thread located HERE
kmt5150 said:
Greetings, fellow Mega-Maniacs!
I am currently working with dev Geohot to get us root access for the SGH-I527 with Baseband Version I527UCUBNE7. All known root methods have been tested and proven to not work with this version of android with this baseband, due to the extremely locked down nature of Samsung Knox on this device.
I, personally, have been throwing every exploit I can think of at this device, to no avail. As of the time and date of this post, we have a donor ready to help the cause (Special thanks to caguas56). That is why I'm proposing a bounty on root access for this phone (SGH-I527 AT&T US version only, although there is a high possibility that it'll work on the Sprint,T-Mo and VZW variant).
The first developer who can successfully get ROOT on KitKat with baseband I527UCUBNE7 and demonstrate this with a successful public test will be awarded the bounty. The bounty will be split equally between devs and donors willing to team up.
I'm in for $10 at the moment, and I'll piss away more if needed down the line.
Who else is in? LETS GET THIS DONE, PEEPS!
Please, only posts regarding root access on this thread. For firmware rollbacks to 4.2.2, see azpatterson3's thread located HERE
Click to expand...
Click to collapse
In for at least $20.
Put me down for 2 bucks.
I know you stated you had tried it all but I have a couple questions for you.
#1. Are you able to odin and access the latest PhilZ Recovery on your Mega? I ask because I read other sections like the Note 2's, etc on AT&T and they are able to flash recovery fine and boot into recovery fine.
#2. If you have tried this method, did you try and flash the latest SuperSU v2.00 from Chainfire through PhilZ?
================
Below is a method I suggested to some in my OTA Update thread to NE4 ( KitKat ) for Rooting all my Galaxy phones on KitKat listed and not one has failed to gain root or to disable KNOX. Note this method will trip KNOX and void your warranty. Try this at your own risk....
================
1.Flash the latest Philz recovery ( Galaxy Mega (meliusltexx) ) .
1a) Be sure when flashing a custom recovery not to allow the device to reboot into the OS right after and instead go straight to the recovery first.
( Uncheck reboot device in Odin or if you forgot to uncheck the box after a successful flash of the Custom Recovery in Odin, quickly hold down vol+, Menu & Power Button or last resort pull the battery before it has time to reboot into the OS {again this is after the phone reboots from flashing the custom recovery and passes}).
The security will over write the custom recovery with the stock recovery and you will have to flash Philz or if available TWRP again. First boot into custom recovery will make it stick on after.
2. Once flashed and booted into recovery, you'll be on the main screen.
( Optional but recommended )
2a) At this point, and it is just a suggestion to you all, make a complete backup of the phone as it sits unmodded. I couldn't really tell you how many times I have read/seen of people post that they forgot to back up their phones after they had attempted to do something to their phones and had caused them to have problems..... well many would be surprised how often this happens and I have been guilty of it due to just being impatient. This way you will have a starting point fresh, stock and even unrooted to go back to. After your done proceed to step #3.
3. Tick on Philz settings.
4. Tick on Re-root System (Super SU).
5. You will then see the log scroll at the bottom and tell you to reboot and install SuperSU through the Playstore.
6. Reboot Device and once you have booted up, install SuperSU via Playstore or if you have the APK on hand, install it.
7. Once installed it will ask you that it needs to update binaries, do so. It will also detect KNOX and ask to attempt
to disable it, go ahead and it will attempt to do so. ( I have yet for it to say unsuccessful )
8. Enjoy being rooted afterwards.
=======================================
If after step #6 it fails to update binaries or for some chance the SuperSU APK failed to install properly or failed to provide Root Access, below is a link for the newer SuperSU v2.00 that is flashable in your Custom Recovery. Flash it by rebooting back into Recovery and flashing the ZIP file that's downloadable from the middle of the main page in the link below. Once flashed continue on from step #6 above.
Thank you @Chainfire
SuperSU v2.00 <------- click here
.
.
.
.
.
DarkAngel said:
I know you stated you had tried it all but I have a couple questions for you.
#1. Are you able to odin and access the latest PhilZ Recovery on your Mega? I ask because I read other sections like the Note 2's, etc on AT&T and they are able to flash recovery fine and boot into recovery fine.
#2. If you have tried this method, did you try and flash the latest SuperSU v2.00 from Chainfire through PhilZ?
================
Below is a method I suggested to some in my OTA Update thread to NE4 ( KitKat ) for Rooting all my Galaxy phones on KitKat listed and not one has failed to gain root or to disable KNOX. Note this method will trip KNOX and void your warranty. Try this at your own risk....
================
1.Flash the latest Philz recovery ( Galaxy Mega (meliusltexx) ) .
1a) Be sure when flashing a custom recovery not to allow the device to reboot into the OS right after and instead go straight to the recovery first.
( Uncheck reboot device in Odin or if you forgot to uncheck the box after a successful flash of the Custom Recovery in Odin, quickly hold down vol+, Menu & Power Button or last resort pull the battery before it has time to reboot into the OS {again this is after the phone reboots from flashing the custom recovery and passes}).
The security will over write the custom recovery with the stock recovery and you will have to flash Philz or if available TWRP again. First boot into custom recovery will make it stick on after.
2. Once flashed and booted into recovery, you'll be on the main screen.
( Optional but recommended )
2a) At this point, and it is just a suggestion to you all, make a complete backup of the phone as it sits unmodded. I couldn't really tell you how many times I have read/seen of people post that they forgot to back up their phones after they had attempted to do something to their phones and had caused them to have problems..... well many would be surprised how often this happens and I have been guilty of it due to just being impatient. This way you will have a starting point fresh, stock and even unrooted to go back to. After your done proceed to step #3.
3. Tick on Philz settings.
4. Tick on Re-root System (Super SU).
5. You will then see the log scroll at the bottom and tell you to reboot and install SuperSU through the Playstore.
6. Reboot Device and once you have booted up, install SuperSU via Playstore or if you have the APK on hand, install it.
7. Once installed it will ask you that it needs to update binaries, do so. It will also detect KNOX and ask to attempt
to disable it, go ahead and it will attempt to do so. ( I have yet for it to say unsuccessful )
8. Enjoy being rooted afterwards.
=======================================
If after step #6 it fails to update binaries or for some chance the SuperSU APK failed to install properly or failed to provide Root Access, below is a link for the newer SuperSU v2.00 that is flashable in your Custom Recovery. Flash it by rebooting back into Recovery and flashing the ZIP file that's downloadable from the middle of the main page in the link below. Once flashed continue on from step #6 above.
Thank you @Chainfire
SuperSU v2.00 <------- click here
.
.
.
.
.
Click to expand...
Click to collapse
Bootloader is locked
So no recovery flashing
Sent from my GT-I9205 using XDA Free mobile app
Grarak said:
Bootloader is locked
So no recovery flashing
Sent from my GT-I9205 using XDA Free mobile app
Click to expand...
Click to collapse
Well technically all bootloaders are locked (except for the few that aren't) but I take it AT&T is wanting/trying to join the band wagon with Verizon and locking the bootloaders indefinitely by encrypting them on all the devices they can now.
Sorry then, my method will not work straight forward. Good luck. :good:
DarkAngel said:
I know you stated you had tried it all but I have a couple questions for you.
#1. Are you able to odin and access the latest PhilZ Recovery on your Mega? I ask because I read other sections like the Note 2's, etc on AT&T and they are able to flash recovery fine and boot into recovery fine.
#2. If you have tried this method, did you try and flash the latest SuperSU v2.00 from Chainfire through PhilZ?
================
Below is a method I suggested to some in my OTA Update thread to NE4 ( KitKat ) for Rooting all my Galaxy phones on KitKat listed and not one has failed to gain root or to disable KNOX. Note this method will trip KNOX and void your warranty. Try this at your own risk....
================
1.Flash the latest Philz recovery ( Galaxy Mega (meliusltexx) ) .
1a) Be sure when flashing a custom recovery not to allow the device to reboot into the OS right after and instead go straight to the recovery first.
( Uncheck reboot device in Odin or if you forgot to uncheck the box after a successful flash of the Custom Recovery in Odin, quickly hold down vol+, Menu & Power Button or last resort pull the battery before it has time to reboot into the OS {again this is after the phone reboots from flashing the custom recovery and passes}).
The security will over write the custom recovery with the stock recovery and you will have to flash Philz or if available TWRP again. First boot into custom recovery will make it stick on after.
2. Once flashed and booted into recovery, you'll be on the main screen.
( Optional but recommended )
2a) At this point, and it is just a suggestion to you all, make a complete backup of the phone as it sits unmodded. I couldn't really tell you how many times I have read/seen of people post that they forgot to back up their phones after they had attempted to do something to their phones and had caused them to have problems..... well many would be surprised how often this happens and I have been guilty of it due to just being impatient. This way you will have a starting point fresh, stock and even unrooted to go back to. After your done proceed to step #3.
3. Tick on Philz settings.
4. Tick on Re-root System (Super SU).
5. You will then see the log scroll at the bottom and tell you to reboot and install SuperSU through the Playstore.
6. Reboot Device and once you have booted up, install SuperSU via Playstore or if you have the APK on hand, install it.
7. Once installed it will ask you that it needs to update binaries, do so. It will also detect KNOX and ask to attempt
to disable it, go ahead and it will attempt to do so. ( I have yet for it to say unsuccessful )
8. Enjoy being rooted afterwards.
=======================================
If after step #6 it fails to update binaries or for some chance the SuperSU APK failed to install properly or failed to provide Root Access, below is a link for the newer SuperSU v2.00 that is flashable in your Custom Recovery. Flash it by rebooting back into Recovery and flashing the ZIP file that's downloadable from the middle of the main page in the link below. Once flashed continue on from step #6 above.
Thank you @Chainfire
SuperSU v2.00 <------- click here
.
.
.
.
.
Click to expand...
Click to collapse
Believe me, we have tried it all. I have tried a process similar to this and when the phone got done with all the flashing and went to boot up, I got a prompt that said 'We have detected software not approved for use by AT&T. Please take your phone to an AT&T store for assistance.' It also says Secure Check Failed: Kernel. I had to send my phone to sammy to get it fixed since I tripped a few flags. Should be back by Friday the 10th.
Possible to use this method with 4.4 kernel from mega?
http://forum.xda-developers.com/showthread.php?t=2722073
I don't know much about this but my S4 active also has a locked bootloader, and I was able to achieve root on 4.4.2 using the above method. Thought it might be possible to adapt to your cause.
jstinger9489 said:
http://forum.xda-developers.com/showthread.php?t=2722073
I don't know much about this but my S4 active also has a locked bootloader, and I was able to achieve root on 4.4.2 using the above method. Thought it might be possible to adapt to your cause.
Click to expand...
Click to collapse
Will definitely try this again when my phone gets here tomorrow and post updates...
jstinger9489 said:
http://forum.xda-developers.com/showthread.php?t=2722073
I don't know much about this but my S4 active also has a locked bootloader, and I was able to achieve root on 4.4.2 using the above method. Thought it might be possible to adapt to your cause.
Click to expand...
Click to collapse
Tried and my device still won't act right, can only get into download mode. recovery is gone and when i attempt to power on, I get a msg about Secure fail: Kernel and then a yellow triangle with a ! says 'System software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nesrest AT&T store for help."
UPDATE: A buddy of mine has a JTAG service and I'm going to send it to him for repair. UGH! I'm selling this sonofabitch. I should NOT have to go thru this much bull**** just do modify something I paid 500 bucks for without a contract.
kmt5150 said:
Tried and my device still won't act right, can only get into download mode. recovery is gone and when i attempt to power on, I get a msg about Secure fail: Kernel and then a yellow triangle with a ! says 'System software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nesrest AT&T store for help."
UPDATE: A buddy of mine has a JTAG service and I'm going to send it to him for repair. UGH! I'm selling this sonofabitch. I should NOT have to go thru this much bull**** just do modify something I paid 500 bucks for without a contract.
Click to expand...
Click to collapse
Have you tried towel root
http://towelroot.com/
BarakOsama said:
Have you tried towel root
http://towelroot.com/
Click to expand...
Click to collapse
Have YOU tried towelroot?
Or have you not read any of the many theads on the subject?
Sorry, not trying to be rude, the same thing has been said so many times
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Can anyone send me boot.img of ATT KK rom?
captemo said:
Have YOU tried towelroot?
Or have you not read any of the many theads on the subject?
Sorry, not trying to be rude, the same thing has been said so many times
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
My bad..
Alright.
To summarize for people who haven't paid attention. Phone was bricked in a last ditch effort to flash back to 4.3 because the 4.4 update made my phone run like s#it. I also have an S4 Active and the service sucks harder than it already did. The 4.4 update makes the S4 drop out constantly and the battery life blows. Samsung told me to run kies in download mode to get it back to 4.3 I did and BOOM, now phone is fu©k!ng bricked and they won't fix it, claiming it's 'rooted' because the kernel says it's version 3 when it's supposed to be at 4 for kitkat. Fu©k!ng duh, you jerks made me flash it back. I am personally never buying another samsung product again because their customer service was horsesh!t. I happen to have a sammy tv, blu ray, home theater and 2 of their former 'top end' phones, but now I'm ditching them. They can lick my scrotum for all I care anymore.
end rant, back to music.
SCH-R960
I have the US Cellular Galaxy Mega SCH-R960 also updated to 4.4.2 out of the box. I am in for some bucks if you can apply this to my version also the baseband number is R960TYUBNF1, I will send you whatever info you need from the phone. Lets get this done! Thank you!
MeatHammer311 said:
I have the US Cellular Galaxy Mega SCH-R960 also updated to 4.4.2 out of the box. I am in for some bucks if you can apply this to my version also the baseband number is R960TYUBNF1, I will send you whatever info you need from the phone. Lets get this done! Thank you!
Click to expand...
Click to collapse
Can you make a complete firmware dump and compile a .PIT file?
No root.
I do not have root so I can not do those things. If there is a way without root please point me in that direction. Thanks
MeatHammer311 said:
I do not have root so I can not do those things. If there is a way without root please point me in that direction. Thanks
Click to expand...
Click to collapse
sure you can
use heimdall
and can anyone send me the boot.img now?
I don't even think you guys want root if you're not even trying to help
Grarak said:
sure you can
use heimdall
and can anyone send me the boot.img now?
I don't even think you guys want root if you're not even trying to help
Click to expand...
Click to collapse
tell me how to get it any you will have it 1 before 5pm today est.
also here is the pit file you asked for. I used it to unbvrick my phone a few times with odin.
ita for the at&t version
Hi,
Try as I may. I cant unlock my Tablet Z LTE (SGP321) bootloader.
Im using FlashTool 0.9.18.4 and am currently on stock KK 4.4.4. firmware (SGP321_10.5.1.A.0.283_CE.ftf)
Everytime I try to ulock the bootloader it fails with FlashTool message that drivers need to installed
I've trird installing the drivers via the \FlashTool\Drivers directory.......but always get the following message "DPInst.exe doe not execute on your current operating system" - I'm running Windows 7 Ultimate 64bit
Any and all help would be greatly appreciated as I'm desperate to install CM KK 4.4.4 and get rid of the Sony stuff.
Thanks in advance
_____________________________
Sony Xperia Tablet Z LTE/WIFI SGP321
vybztymz said:
Hi,
Try as I may. I cant unlock my Tablet Z LTE (SGP321) bootloader.
Im using FlashTool 0.9.18.4 and am currently on stock KK 4.4.4. firmware (SGP321_10.5.1.A.0.283_CE.ftf)
Everytime I try to ulock the bootloader it fails with FlashTool message that drivers need to installed
I've trird installing the drivers via the \FlashTool\Drivers directory.......but always get the following message "DPInst.exe doe not execute on your current operating system" - I'm running Windows 7 Ultimate 64bit
Any and all help would be greatly appreciated as I'm desperate to install CM KK 4.4.4 and get rid of the Sony stuff.
Thanks in advance
_____________________________
Sony Xperia Tablet Z LTE/WIFI SGP321
Click to expand...
Click to collapse
don't use flashtool for unblocking BL (cause you can use instruction from Sony's site), or install drivers properly: look for dpinst.exe in your temp folder and set compability mode with WinVista in it's properties and it will install properly.
Rootk1t said:
don't use flashtool for unblocking BL (cause you can use instruction from Sony's site), or install drivers properly: look for dpinst.exe in your temp folder and set compability mode with WinVista in it's properties and it will install properly.
Click to expand...
Click to collapse
Thanks for your reply/suggestion. Unfortunately I do not have the "set compatibility" option in DPInst.exe properties. I have found 2 x dpinst.exe and 2 x dpinst64.exe files on my system.
I've tried using the Sony site instructions but
1. When i attch the tablet to my laptop in Fastboot mode (Vol up), and type "fastboot devices" at the cmd prompt, i dont get any indication that my tablet has been/is recognised (see scrrenshot 1)
2. When I run the unlock command using the unlock code obtained from Sony, command line sticks at "waiting for device" (screenshot 2)
i'm at a loss as to whats wrong \ what Im doing wrong
All / any suggestions welcomed as am desperate to install CM11/12.
Thanks in advance
Vybz
vybztymz said:
Thanks for your reply/suggestion. Unfortunately I do not have the "set compatibility" option in DPInst.exe properties. I have found 2 x dpinst.exe and 2 x dpinst64.exe files on my system.
I've tried using the Sony site instructions but
1. When i attch the tablet to my laptop in Fastboot mode (Vol up), and type "fastboot devices" at the cmd prompt, i dont get any indication that my tablet has been/is recognised (see scrrenshot 1)
2. When I run the unlock command using the unlock code obtained from Sony, command line sticks at "waiting for device" (screenshot 2)
i'm at a loss as to whats wrong \ what Im doing wrong
All / any suggestions welcomed as am desperate to install CM11/12.
Thanks in advance
Vybz
Click to expand...
Click to collapse
Check that your tablet's fastboot drivers are installed correctly in device manager on windows. I haven't done this on the tablet z (yet), but if you do not have the drivers installed on a nexus you wont see any device in the fastboot devices option.
So i would suggest you download the correct drivers (preferably from sony, but google drivers might also work), and check that the device manager dont have any unknown devices (tablet z) and if you do not try reinstalling the driver by uninstalling the current one and getting the correct one from sony or the google drivers.
marcusorwen said:
Check that your tablet's fastboot drivers are installed correctly in device manager on windows. I haven't done this on the tablet z (yet), but if you do not have the drivers installed on a nexus you wont see any device in the fastboot devices option.
So i would suggest you download the correct drivers (preferably from sony, but google drivers might also work), and check that the device manager dont have any unknown devices (tablet z) and if you do not try reinstalling the driver by uninstalling the current one and getting the correct one from sony or the google drivers.
Click to expand...
Click to collapse
Thanks - you were right, it was drivers. Finally managed (I think) to unlock bootloader.........but am now stuck in a bootloop .
Any suggestions welcomesed
Use flashtool and simply flash any stock version on top.
Alternatively, you can use some non stock ROM, but for that your first need to install the custom recovery via fastboot.
vybztymz said:
Any suggestions welcomesed
Click to expand...
Click to collapse
Have a look at this guide for installing a CM ROM
vybztymz said:
Thanks - you were right, it was drivers. Finally managed (I think) to unlock bootloader.........but am now stuck in a bootloop .
Any suggestions welcomesed
Click to expand...
Click to collapse
If your stuck in a bootloop i would suggest trying and flash recovery through flashtools and see if you can clear dalvik cache in the custom recovery.
it might help.
but otherwise do as the others say and flash a custom rom (CM preferably).
Lost Root after installing CN12 Nightly (Lollipop 5.0x)
marcusorwen said:
If your stuck in a bootloop i would suggest trying and flash recovery through flashtools and see if you can clear dalvik cache in the custom recovery.
it might help.
but otherwise do as the others say and flash a custom rom (CM preferably).
Click to expand...
Click to collapse
hanks for you help.
I have rooted and unlocked the boot loader of my SGP321 (WiFi/LTE).
But every time I install CM12 (flashed zip via TWRP), I lose Root......and as far as I can see, there's no way back from that, bar a complete re-install of stock (KK444)
Really frustrated as have wanted to flash CM and get rid of the Sonly bloatware (example: of 2gb internal memory, the stock firmware leaves only c.500mb free....thats just plain ridiculous. Compared to CM12 which leaves 1.7 GIGS free.
any suggestions.......?
vybztymz said:
hanks for you help.
I have rooted and unlocked the boot loader of my SGP321 (WiFi/LTE).
But every time I install CM12 (flashed zip via TWRP), I lose Root......and as far as I can see, there's no way back from that, bar a complete re-install of stock (KK444)
Really frustrated as have wanted to flash CM and get rid of the Sonly bloatware (example: of 2gb internal memory, the stock firmware leaves only c.500mb free....thats just plain ridiculous. Compared to CM12 which leaves 1.7 GIGS free.
any suggestions.......?
Click to expand...
Click to collapse
CM12 should have root built in, check developer options for it on your device.
If not then just flash SuperSU.zip from chainfire (i prefer chainfire's version of super user).
Chainfire's SuperSU is here: http://forum.xda-developers.com/showthread.php?t=1538053
please note that i have not tested this on a Tab Z but it should work.
marcusorwen said:
CM12 should have root built in, check developer options for it on your device.
If not then just flash SuperSU.zip from chainfire (i prefer chainfire's version of super user).
Chainfire's SuperSU is here: http://forum.xda-developers.com/showthread.php?t=1538053
please note that i have not tested this on a Tab Z but it should work.
Click to expand...
Click to collapse
Thanks for the speedy reply. Really appreciated. I've gone intp developer options.....but what am i looking for?
[EDIT] In Developer Options, and under "Root Access" it says "Disabled"
[EDIT 2] Downloaded a RootChecker and it tells me I'm not rooted
I'm totally frustrated.....have been trying to install CM12 for the last 6 hours!!!!
NUT (duallockedrecovery) has done a fantastic job developing the xzdr.........but i have to say that, in common with a lot of devs.... not very good at writing nstructions.
I'm an IT manager and often train staff in systems etc, including writing user guides. When writing guides/instructions, I ALWAYS assume that the end user KNOWS NOTHING......and so the guides/etc are very detailed. Yes, it takes a while to write them, but feedback shows its the right track to take.
Almost all the articles on flashing CM12/using Fastboot etc lack small, but important, details......!!! I'm still not really sure if i should be using TabZ-lockeddualrecovery or XZ-lockeddualrecovery..........!!!!!!
i've got as far as I have by pulling together numerous XDA posts in order to get a (full'ish) picture of what to do. Devs, pls make your instructions clearer for people who aren't devs. Rant over
My current position is that my Xperia Tablet Z is
1. On KitKat 444 (Firmware ver. 283)
2. Rooted
3. Bootloader unlocked
4. SuperSU & SuperSu Pro installed
How do i get from this position to a successful CM12 install?
I have CM12 Nightly (7th May), GApps 5.0x Minimal ready and waiting....
I'm not a stupid person, but trying to do this has made me feel like a complete idiot.....help!!!
vybztymz said:
Thanks for the speedy reply. Really appreciated. I've gone intp developer options.....but what am i looking for?
I'm totally frustrated.....have been trying to install CM12 for the last 6 hours!!!!
NUT (duallockedrecovery) has done a fantastic job developing the xzdr.........but i have to say that, in common with a lot of devs.... not very good at writing nstructions.
I'm an IT manager and often train staff in systems etc, including writing user guides. When writing guides/instructions, I ALWAYS assume that the end user KNOWS NOTHING......and so the guides/etc are very detailed. Yes, it takes a while to write them, but feedback shows its the right track to take.
Almost all the articles on flashing CM12/using Fastboot etc lack small, but important, details......!!! I'm still not really sure if i should be using TabZ-lockeddualrecovery or XZ-lockeddualrecovery..........!!!!!!
i've got as far as I have by pulling together numerous XDA posts in order to get a (full'ish) picture of what to do. Devs, pls make your instructions clearer for people who aren't devs. Rant over
My current position is that my Xperia Tablet Z is
1. On KitKat 444 (Firmware ver. 283)
2. Rooted
3. Bootloader unlocked
4. SuperSU & SuperSu Pro installed
How do i get from this position to a successful CM12 install?
I have CM12 Nightly (7th May), GApps 5.0x Minimal ready and waiting....
I'm not a stupid person, but trying to do this has made me feel like a complete idiot.....help!!!
Click to expand...
Click to collapse
Yea i know what you mean by guides not being written to include alot of details and missing out on small stuff that might be important, but anyway.
In the Developer Options there should be a box called Root Access, and it should be defaulted to Disabled ones you have installed CM12 for the first time, its just a matter of enabling this.
Im guessing you already know how to enable Developer Options, but if you dont here is how:
Go to About Device (or Phone/Tablet) and click on Build number a bunch of times (i think its 5-6 times), and the developer options should be visible in the settings.
If that dosent work you might want to try and flash the SuperSU binary through recovery, the zip to use is the one found in chainfires xda-thread here: http://forum.xda-developers.com/showthread.php?t=1538053
But here is the direct link for the zip https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Just put that on your device internal memory (or SD-Card) and flash it in your recovery of choice, it should work in CWM, TWRP and Odin (but you dont have a samsung so the last one dosent matter).
This should install the SuperSU app, and its basic su binary onto your CM12 rom.
In both cases i would recommend you install root checker (https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck) and see if root is available to you.
Also to note is that the Root Access option built into CM12 isnt that customizable and i would still recomend you install SuperSU, but if the Root Access option is working you can just download the SuperSU application from the play store and let it install SU binary and then you can disable CM12's built in root option ones you make sure the SuperSU was installed correctly.
Thanks so much for your help/patience......but i'm afraid im giving up (for now).
Will try again in a few days......so its back to rooted stock 444
By the way, why have CM decided to go with their own (as good as useless) recovery????
I forgot to say that you've helped fill in a few more gaps for me in respect of this i.e. flashing SU; changing Root Access in Dev. Options etc.
These are the things that all the articles ive read FAILED to mention.
Thanks so much
vybztymz said:
I forgot to say that you've helped fill in a few more gaps for me in respect of this i.e. flashing SU; changing Root Access in Dev. Options etc.
These are the things that all the articles ive read FAILED to mention.
Thanks so much
Click to expand...
Click to collapse
No problem, if you have any other questions just tell me and i might be able to help you
I have also been in the dark about this stuff before, and im still not used to other manufacturers style of rooting and unlocking the bootloader (sony is the next best after Nexus) since samsung and the others usually you have a harder time unlocking and rooting.
But good luck if you try it again :victory:
Hey guys! Unfortunately I bricked my new HTC Desire 626s while fiddling around with xposed for lollipop after successfully rooting the phone and installing cyanogen recovery. I think if I flash the stock rom on the phone through either adb or cyanogen recovery I can unbrick it, but I have been unsuccessful in finding this file on the internet. Would anyone care to give me a link or upload the stock firmware/rom of this phone? It would really help me out, thank you!
You have to make sure the firmware is the same version or newer than the one currently on the phone as well as which carrier or region the phone is from. Without that, can't provide the correct file to download.
es0tericcha0s said:
You have to make sure the firmware is the same version or newer than the one currently on the phone as well as which carrier or region the phone is from. Without that, can't provide the correct file to download.
Click to expand...
Click to collapse
Umm.. Okay so I guess I'll give you my phone's info? WAIT DOES THIS MEAN YOU CAN PROVIDE A DOWNLOAD!? IM SO EXCITED, UH OK HERE
- HTC Desire 626s
- Metro PCS USA
- Current firmware version : 1.06.1550.7
ANYTHING ELSE?? IF YOU CAN GIVE ME THAT DOWNLOAD LINK, MY MOM WONT KILL ME:crying::crying::crying: (she's really pissed :laugh Thank you btw!
Was just thinking about this...if you soft bricked after attempting to install Xposed, and nothing else, you should be able to get out of it by flashing the xposed uninstaller zip. If that does not work, stay tuned to this thread http://forum.xda-developers.com/desire-626/help/htc-desire-626s-root-recovery-t3169169 as there are some others at the end of the thread in a similar predicament. It does not appear that there is an official RUU yet for the Metro version, only the T-Mobile version, and they are not compatible. Just try the uninstaller zip first because that would be the easiest thing to try and should only take a couple of minutes.
es0tericcha0s said:
Was just thinking about this...if you soft bricked after attempting to install Xposed, and nothing else, you should be able to get out of it by flashing the xposed uninstaller zip. If that does not work, stay tuned to this thread http://forum.xda-developers.com/desire-626/help/htc-desire-626s-root-recovery-t3169169 as there are some others at the end of the thread in a similar predicament. It does not appear that there is an official RUU yet for the Metro version, only the T-Mobile version, and they are not compatible. Just try the uninstaller zip first because that would be the easiest thing to try and should only take a couple of minutes.
Click to expand...
Click to collapse
I tried this before my phone got ****ed and it worked:good:! If you can help me dude that'd be great. After uninstalling or changing some stuff in priv-app on my HTC Desire 626s, when I rebooted, it would just stay in a boot loop with the optimizing app message. Any ideas?
What did you uninstall? I would ask for those apps in that thread and use a flashable zip and install via TWRP. You might also try clearing caches and/or resetting the phone again. It DOES take a long time to optimize the apps after wiping stuff as well, so sometimes it is a matter of being patient.
This is why I ALWAYS recommend to freeze apps vs uninstalling. Uninstalling them does not get you any usable space back, so there is no benefit, but it can cause issues if you do need the apps, as you can see...
es0tericcha0s said:
What did you uninstall? I would ask for those apps in that thread and use a flashable zip and install via TWRP. You might also try clearing caches and/or resetting the phone again. It DOES take a long time to optimize the apps after wiping stuff as well, so sometimes it is a matter of being patient.
This is why I ALWAYS recommend to freeze apps vs uninstalling. Uninstalling them does not get you any usable space back, so there is no benefit, but it can cause issues if you do need the apps, as you can see...
Click to expand...
Click to collapse
I believe I uninstalled the dialer and its service in an attempt to replace them with the stock lollipop ones. How do you install TWRP on this phone? My mom has the same phone and its also rooted but hers actually works so I was thinking since TWRP has a nandroid backup setting, I could simply do a nandroid backup on hers and flash it on to mine to see if it will boot up. What do you think? And for the optimizing apps thing, it would finish optimizing, say starting apps, reboot and then optimize again and repeat. Thanks for the help btw, I really hope we can fix this.
You have to unlock the bootloader @ htcdev.com and use fastboot to install TWRP. And yes, that would work, as long as they are on the same software update. Know that when you unlock the bootloader, it will automatically wipe the phone, so make sure she has everything backed up to Google, the PC, etc.
es0tericcha0s said:
You have to unlock the bootloader @ htcdev.com and use fastboot to install TWRP. And yes, that would work, as long as they are on the same software update. Know that when you unlock the bootloader, it will automatically wipe the phone, so make sure she has everything backed up to Google, the PC, etc.
Click to expand...
Click to collapse
Do you have the TWRP recovery file for me to download?
I'm afraid I'm a bit confused... How did you install Xposed and the Uninstaller without a custom recovery? Upon further searching, there doesn't appear to be a version of TWRP for your phone that I could find. Just figured you already had one. You must be on Kit Kat and not Lollipop?
es0tericcha0s said:
I'm afraid I'm a bit confused... How did you install Xposed and the Uninstaller without a custom recovery? Upon further searching, there doesn't appear to be a version of TWRP for your phone that I could find. Just figured you already had one. You must be on Kit Kat and not Lollipop?
Click to expand...
Click to collapse
I installed Cyanogen recovery before flashing Xposed and the uninstaller. I thought you had the TWRP recovery img for my phone which is why I asked. I believe some developers are working on a Clockworkmod recovery for this phone which is basically the same thing as TWRP recovery, right? Anyways I guess I just have to wait until that comes out, but I was wondering if anyone who somehow got a hold of the stock rom could upload it for us to use. It would be really helpful
ClockWorkMod is the recovery that Cyanogen uses. That is able to perform nandroid backups as well.
You have to unlock the bootloader, then if you messed up your stock rom and you've updated it to something newer than what Samsung gives for a stock recoverable rom, you must first use the tmobile vers, let it fail, and then use metropcs vers.
If you messed up recovery or anything it will all go back to stock after flash.
Next just copy superuser zip file to phone, go to download mode and adb flash cyanogen recovery img. Then reboot to recovery, choose to flash update, and find the superuser. zip and flash it, voila.
https://www.mediafire.com/?8o6qtn7hlsec0zj,yqbbzb7divlcvvc
Kitkat, anyone?
Does anybody have a stock KitKat ROM for this device? I'd like to try to bypass the FRP, but am stuck on what must be either a marshmallow or lollipop ROM.
What carrier do you have?
I can send you a backup of the FRP.img for Marshmallow or for lollipop.
You can dd if= flash it to your device and you should be all good.
I am looking for any older roms for these devices too.
Seems like not too many people save the RUU and then HTC only releases the newest.
I got lollipop and marshmallow that's it.
But like i said we can fix the frp partition.
Issue is fixed
BigCountry907 said:
What carrier do you have?
I can send you a backup of the FRP.img for Marshmallow or for lollipop.
You can dd if= flash it to your device and you should be all good.
I am looking for any older roms for these devices too.
Seems like not too many people save the RUU and then HTC only releases the newest.
I got lollipop and marshmallow that's it.
But like i said we can fix the frp partition.
Click to expand...
Click to collapse
I ended up fixing it using some ADB commands as noted in the "Well, I may have found..." thread. It'll be nice to have this phone out of my life. The day I had to spend with it was two days too many.
Hello, there!
The precious thing is a cheap 7" allwinner a33 tablet. By apps its recognized as Astar y33.
It is a 16Gb Storage Tablet with 1 gb ram. I bought ist for 42€. :cyclops:
Unluckily i only can install apps on a 1 gb internal storage and the 16gb are only for media or movable apps. It should have 1gb ram but Aida64 said it has 512 installed.
I urgently need to give root to it, to make it work -and enjoyable. I allready tried out:
-Kingoroot (also via PC)
-Kingroot
-Iroot
-Towelroot
-SuperOneClick.exe
-and various desktop based one click rooters
and all failed.
I dont know what i can try next.
I have the ADB driver, but not a certain fastboot interface driver, which i could not find in the internet at all. I have a 64 system.
Many people with similar tablets could root them with Kingo root or Iroot, but it worked not for me and my tablet must be somehow different, it also did not had any bloat or malware on it.
Please, please, give me a hint what i could try next. :silly:
These are the specifications of the tablet:
*See attachements
Root method for recovery
Good afternoon!
To apply the patch-and for rooting you device, it is necessary to get into Recovery.
So try to load into recovery by this way: "Settings-> Recovery and reset-> Recovery Mode".
After rebooting, you see some menu where you should select drive(sd card) on which the pre-recorded file "Update.zip"
After finishing, restart your device use first point of menu.
Now you have a root, it is necessary to update the SuperSu by selecting "OK".
P.S.
I didn't test it but find it on some good forums. Send privet massage to me if you have some questions.
Root_patch
Good evening!
I tried it out right now.
It was flashable but the su binary wont let me update. How should i update the su binary? Do i need another flashable zip?
Unluckily the root checker says that root permission is not granted yet.
Update: I flashed a current Supersu update.zip with my stock recovery mode.
It says "installtion abortet".
I dunno. I ll have to use the tablet to cut vegetables. *joke
Wow, seems like suddenly root was granted.
Last thing was: I tried to root it with Iroot via PC.
It installed some adware on the tablet but the root checker still said no.
Then Kinguser detected some malware in the notification are. I fixed this and noticed that i also could remove system apps with Kinguser.
Then i retried apps that recommed root like rashr and to my surprise - root was granted suddenly!!!
:laugh:
Woah! Somehow im not so sure what rooted it now, because i already tried everything five times before already and it didnt work ^^
I think, it could be this:
Kingroot has shown me before, that my device is not supported. I could kinda request compatibility, which i did.
Maybe this magic happend unnoticed and suddenly it was rooted.
Oh ****.
Afterwards i flashed some recovery.img someone told me its for TWRP for the tablet.
Since then, its in a bootloop.
How to fix this? For now, i will just wait until the battery has run empty. (That fixed beeing stuck in fastboot mode before)
THANKS!!!
Nejix83 said:
Root method for recovery
Good afternoon!
To apply the patch-and for rooting you device, it is necessary to get into Recovery.
So try to load into recovery by this way: "Settings-> Recovery and reset-> Recovery Mode".
After rebooting, you see some menu where you should select drive(sd card) on which the pre-recorded file "Update.zip"
After finishing, restart your device use first point of menu.
Now you have a root, it is necessary to update the SuperSu by selecting "OK".
P.S.
I didn't test it but find it on some good forums. Send privet massage to me if you have some questions.
Root_patch
Click to expand...
Click to collapse
Hey dude, you are awesome! I could not find anywhere this file. At last my tablet is rooted. I have been looking for firmwares for these tablets everywhere and, as they are really old and chinese crap now, all mirrors I find are down. Where did you find this zip? maybe I can find a firmware there. I need to flash it from 0 because I did a mess with adb and deleted every system app
Hello everyone
do you have an update.zip SuperSU-v2.82
Best Regards
Great !
Nejix83 said:
Root method for recovery
Good afternoon!
To apply the patch-and for rooting you device, it is necessary to get into Recovery.
So try to load into recovery by this way: "Settings-> Recovery and reset-> Recovery Mode".
After rebooting, you see some menu where you should select drive(sd card) on which the pre-recorded file "Update.zip"
After finishing, restart your device use first point of menu.
Now you have a root, it is necessary to update the SuperSu by selecting "OK".
P.S.
I didn't test it but find it on some good forums. Send privet massage to me if you have some questions.
Root_patch
Click to expand...
Click to collapse
That's work fine.
My Tv Box is Q Plus Android 9.
Maybe it can help : You can use the rom of Vorkez 7 in Q Plus, because they have same hardware.
steleclanel1 said:
That's work fine.
My Tv Box is Q Plus Android 9.
Maybe it can help : You can use the rom of Vorkez 7 in Q Plus, because they have same hardware.
Click to expand...
Click to collapse
@steleclanel1
Hi, I have a Q Plus box too and have managed to root it but I need to bypass google play device check. I have edited build.prop successfully but can't find the global settings database to complete this. Are you able to help... does the Vorkez 7 rom allow for this? Thanks
thanks, it is work fine