yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] neonafk:
Lenovo A10 70f finally rooted and cwm lollipop 5.0.1

Hi my first post but I'm sure u will all enjoy, finally got this tablet rooted on lollipop 5.0.1, using following method.

1. Download and install SPflashtools.

2. Download and install MT6575 USB vcom drivers,

3. Download a zip called carlivtouchrecovery.zip

4. Download UPDATE-SuperSU-v2.46.zip.

Right now to start.

First off set device into USB debug, from about device, press build 10 times to access features.

Now with device turned ON connect to PC using cable make sure all drivers installed OK.

No disconnect again, and load up SPflashtools, choose scatter file from within carlivtouchrecovery. And make sure only recovery option has a tick. Now click download.

Now connect device again whilst switched OFF, and now custom recovery is installed.

Disconnect device, turn on device holding power and vol+ check recovery installed.

Now to ROOT, insert the UPDATE-SuperSU-v2.46.zip onto sdcard1, load into recovery mode using power and vol+ again, choose recovery, then from here choose update from sdcard1, choose the UPDATE-SuperSU.zip and install. Restart and 100% rooted and with custom recovery, unfortunately I cannot add links but easy to Google search to find, please like if helps, thanx

I did. that is what i was quoting earlier...

No disconnect again, and load up SPflashtools, choose scatter file from within carlivtouchrecovery. And make sure only recovery option has a tick. Now click download. I can't get it to download, the progress bar doesn't go anywhere. Am i doing something wrong? The tablet connects fine, drivers, it appears and I can transfer files on my PC
[Android Q&A, Help & Troubleshooting] Sparkrite:
That's all very well but have you installed the SP drivers??? (attached)

These MUST be installed for SP Tools to "see" the tablet and are different from the USB drivers

you seem to be referring to.
[Android Q&A, Help & Troubleshooting] neonafk:
Hey,

How do i install these? opening the Android_winusb file and right click install or active install, not getting anywhere. Should i see something pop up?

i Right click on the device in "Portable Devices" "Lenovo Tab 2 A10-70F" and try to update the drivers to the SP TOol and Windows is saying you have the most up to date drivers. and Closes the box?
[Android Q&A, Help & Troubleshooting] Sparkrite:
You are still trying to update the USB drivers, FORGET about them!!

Ok, turn off the tablet,

Open "device manager" on PC,

Now connect the tablet via usb and keep an eye on the device manager,

Be ready to move quickly, you should see an unrecognised device detected, as far as I can

remember it appears as something like "Mediatek Preloader" or something like that,

Before it disappears click on it and update/load the drivers by pointing it to where you have

the drivers saved on drive.

And Voila !!

It took me a couple of attempts but it only has to be done once.
[Android Q&A, Help & Troubleshooting] neonafk:
So i followed this process, and now i have this picture appearing in my control pannel --> Device Manager

Update Driver Software -- MediaTek DA USB VComm Port (COM8),

I tried to load the SP Drivers, but no luck. it keeps saying i have the most up to date drivers?

Uninstllaed the MTK625 driver from my comptuer, and i keep unplugging and plugging back in, still no luck i saw the pre-loader pop up once and disappear in 1 second!

\nm i think it loaded!! FINALLY!!! I can load the SU Zip now hold on

---------- Post added at 06:58 PM ---------- Previous post was at 06:48 PM ----------

I think it works! Can i buy you guys a beer? lol.

Now that its installed , i opened the SuperSU app and need to install binary, anything else? What method should i go about for doing this, normal or TWRP/WRM

I went to root checker, and still no luck, says my device is not rooted?
[Android Q&A, Help & Troubleshooting] Sparkrite:
Try normal first and if that then use TWRP/CWM method.

Good to hear you eventually have it working now.
[Android Q&A, Help & Troubleshooting] neonafk:
F

Tried, normal, no luck, reset tablet,

tried TWRP/CWM, reset tablet, no luck. What gives?

For the TWRP/CWM Install, it says if the device does not reboot into recovery, do it manually.

I shut it down and tried to restart using Power + Volume UP.

What do I do once the tablet starts up in recovery?
[Android Q&A, Help & Troubleshooting] Sparkrite:
I think you are going about this all wrong.

AFAIK there is know TWRP/CWM working for this tablet on Ver5.01

Have you actually installed Carlivtouchrecovery.zip for Lollipop

(I have linked to this in a previous post)

using your now working SPtools?

It is from within that recovery that you flash the SuperSU-v2.46.zip, (without unzipping)

Also see "The spillers" step by step guide.....................

"load up SPflashtools, choose scatter file from within carlivtouchrecovery. And make sure only recovery option has a tick. Now click download.

Now connect device again whilst switched OFF, and now custom recovery is installed.

Disconnect device, turn on device holding power and vol+ check recovery installed.

Now to ROOT, insert the UPDATE-SuperSU-v2.46.zip onto sdcard1, load into recovery mode using power and vol+ again, choose recovery, then from here choose update from sdcard1, choose the UPDATE-SuperSU.zip and install. Restart and 100% rooted and with custom recovery"
[Android Q&A, Help & Troubleshooting] neonafk:
Yes when i get to recovery mode, it pops up carlivtouchrecovery for me to access and then i load the zip file from my storage card.

Installation was successful of the Superuser.2.46.zip

I just downloaded the Superuser.binary.3.1.1 zip and loaded it through recovery. still the same problem somehow.

What do you think?
[Android Q&A, Help & Troubleshooting] Sparkrite:
Make sure you are using the version for lollipop and not the kikat version of the recovery.
[Android Q&A, Help & Troubleshooting] neonafk:
I downloaded the recovery and flashed it again vis SP Tools. I think this is the correct version. Not sure why im still receiving the binary needs to be updated!! :(

The version of cali recovery says "kitkat 1.0" at the bottom, although i downloaded the one supplied in post 122. flashed the SUTools.2.46. zip ands still no luck?
[Android Q&A, Help & Troubleshooting] Sparkrite:
Here is the recovery for Lollipop. (see attached file)

Don't worry about SuperSU wanting to update the binary, normal enough as its an old enough su.bin

supplied with it.

Also use this BETA SuperSU............................

https://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip

All links previously given in this thread, see my post:-

http://xdaforums.com/showpost.php?p=63398435&postcount=120
[Android Q&A, Help & Troubleshooting] neonafk:
So i tried utilizing the newer version of SU. Checked the version on my tablet, says Super SU Free 2.52...yet i still dont have root enabled?

What gives? I have the recovery for lollipop installed on my machine, i'll try anything at this point, still saying i need to update my binaries and i did check-root program and says i am not enabled for root :(
[Android Q&A, Help & Troubleshooting] Sparkrite:
Have you actually updated the binary successfully ?

Have you done a factory re-set?

Also download/install something like "rom toolbox" from the app store and see if that allows root access.
[Android Q&A, Help & Troubleshooting] neonafk:
Hi,

No, after i restart the system continually tells me to update Binary. Never was able to successfully update it via the "normal" way.

I installed Rom toolbox, and tried to change a few things. Like the boot up screen, restarted the tablet twice, and still the old boot screen seems to show? Not sure if any of this took effect.

If i open other programs, like xmodgames, that says i don't have root and doesn't work. Am I doing something wrong?

Root-Checker also says my device is not rooted

WHen i open up KingO SUper User it says,

The KIngo SUper User Binary (S) Must be updated or reinstalled

Please find KingO Root at www.kingoapp.com and install SU Binary by rooting your device again
[Android Q&A, Help & Troubleshooting] Sparkrite:
Don't know why the problem in updating the su.bin.

Go into terminal emulator in Rom toolbox, type su and hit return. Tell me exactly what is on

the next line then.
[Android Q&A, Help & Troubleshooting] neonafk:
How should i do a factory reset? From the recovery menu?

I opened Kingroot app and tried to enable/disable startup programs, that seemed to work, i restarted and it was uninstalled? Had to go find the APK and reinstall it. checked the program and it kept my preferences. HOwever the appy, Kingroot kept crashing repeatedly. although it said root was granted?

I went to the emualtor and it crashed, would not open, restarted, same situation, crashed, wouldn't open. Not sure what im doing wrong. It seems i can see the emulator like MS Dos text, but it crashes and does not let me type.

Some program Purity keeps asking for permission when i open the emulator, but nothing pops up

---------- Post added at 11:15 PM ---------- Previous post was at 11:09 PM ----------

correction, thank you so so much for working with me. Somehow It seems to have granted root!???! IDK what the hell happened, but i kept checking and allowing programs, working with the KingRoot and Romtools and finally it asks for "permission to grant root" whenever i would open a program, this never happened before?! idk but it works!! HORRAY!!!!! THANK YOU!!!
[Android Q&A, Help & Troubleshooting] Sparkrite:
Now it is obvious why SuperSU would not work, you never said you had Kingroot apk installed !!!

No wonder you couldn't update the SU.bin, you CAN NOT have two apps trying to grant root access at the same time. Pity you didn't mention Kingroot earlier, would have solved this a lot

quicker. Anyway you're rooted now, which is what we set out to do. :)

If you are happy to leave Kingroot as your root app then so be it but you can also change it to SuperSU by running scripts found earlier in this thread, or by doing a search on Google for the method.
[Android Q&A, Help & Troubleshooting] free4flight:
Have any of you seen this? Not sure it's the real deal since you have fill out an offer to get to the files, but thought it was noteworthy !?!?

It is to install Android 6.0 on this tablet.

Darn, won't let me give you the link so..... no I am not spamming, i have nothing to do with this link, just happened to find it.

www dot blu-marshmallow dot xyz/2015/11/lenovo-tab-2-a10-70-7089 dot html
[Nexus 6 Q&A, Help & Troubleshooting] revolt1:
I'm looking for any zips that could make the nav bars size stock rooted vzw n6

Does xposed work and if there is where are the apks
[Galaxy S II Themes and Apps] dacsang97:
fake iphone battery: http://www.oni.vn/kr3Wp

Battery parents: http://www.oni.vn/xLBHA

gold angel pin 2 sides: http://upnhanh.mobi/f/UFCE

battery fire circle: http://www.oni.vn/tySKt

lion battery: http://www.oni.vn/p9NEi

god pin executioner: http://www.oni.vn/FvYWD

lion battery: http://www.oni.vn/63qNr

Source: https://www.facebook.com/groups/686171674773416/
[Galaxy S II Themes and Apps] dacsang97:
Guide Scroll TextView on StatusBarExpanded

1.Decom SystemUI

2.Open SystemUI-src / res / layouts / status_bar_expanded.xml (gemini_stt3_expanded.xml / tw_stt3_expanded.xml / asus_stt3_expanded.xml ... depending machines offline) find this code

*

***

<Scrollview android: id = "@ id / scroll" ...>

****

and put this code on it:

*

****

<TextView android: click Text = "16.0dip" android: textcolor = "# ffffffff" android: gravity = "center" android: ellipsize = "marquee" android: focusable = "true" android: focusableInTouchMode = "true" android: layout_width = "fill_parent" android: layout_height = "wrap_content" android: paddingLeft = "70.0dip" android: paddingRight = "70.0dip" android: layout_marginTop = "2.0dip" android: text = "@ string / kotext_cocanh" android: singleline = "true "android: marqueeRepeatLimit =" marquee_forever "/>

*****

3. Open SystemUI-src / res / values ​​/ strings.xml add this code to the bottom

*

**

**<String name = "kotext_cocanh"> **** </ string>

*****

**Replaced by the words you want ****

*****

4.Recom SystemUI-src

**Meta-inf override and AndroidManifest from SystemUI.apk to SystemUI-src.apk

**SystemUI-src.apk rename the SystemUI.apk, put into the system, set 644, included in the app, reboot

**Note: The text in <string name = "kotext_cocanh"> ... </ string> if too short, it will not scroll horizontally, but it will lay

Source : https://www.facebook.com/groups/686171674773416/
[8525, TyTN, MDA Vario II, JasJam General] Applestar:
Well, having tried a couple of new PPC phones recently I put my Hermes (T-Mobile Vario II) out of work and started to install all my apps on a Herald (P4350 = Vodafone compact 4). Guess what? Never been happier with a PPC phone so far:

Perfect:

- Crystal clear phone speaker sound

- Longer battery life

- Much nicer, quite a bit smaller than my TyTN - and a better keyboard

Downgrades:

- WM5 (WM6 should be out in a couple of weeks)

- 200 MHz processor - but so far fast enough for all my apps...

- No UMTS - but considering I always switched off UMTS due to battery life on my TyTN..

Well, well - and I would like to have a few more posts on the Herald forums here. The device does not seem to be very popular here :(
[Verizon Samsung Galaxy S 4] Anastomosis:
I don't have high hopes that this is fixable, but my Verizon Galaxy S4 phone was bricked after taking the OC1 update.

Long story short, I flashed the stock Lollipop OC1 firmware to my phone via Odin3 (v3.10) instead of the neutered one with the NK4 bootloader, by accident... I stupidly didn't read the full file name in a hurry. So, now I have an unrooted stock OC1 lollipop firmware on my machine.

Not doing all my research and thus not knowing that the OC1 bootloader is locked, I tried to use Odin to re-flash an NC5 boot.img (the old NG6 to NC5 downgrade method). This actually flashed just fine. But, it put me in a bootloop.

So, I tried to re-flash the full stock OC1 firmware. This failed as per the Odin output below:

File analysis...

SetupConnection...

Initialization...

Get PIT for mapping...

Firmware update start...

SingleDownload.

boot.img

NAND write start!!

recovery.img

system.img.ext4

__XmitData_Write

Complete(Write) operation failed.

All threads completed. (succeed 0 / failed 1)

I get similar failing results whenever I try to flash any firmware via Odin.

So I can only access download mode. My recovery won't boot, and when I just try to boot it up normally it gave a screen saying:

Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.

So I download Kies, it recognizes there is a device there, but doesn't recognize it as a compatible device.

I use the Kies option under tools "Emergency firmware recovery," but the device doesn't pop up as one in need of recovery.

So I use the "Firmware Upgrade and Initialization" tool. I type in Galaxy S4, it downloads the firmware, starts updating... and has an unexpected error. It says to run recovery. But I already tried that, and the device isn't recognized.

However, now on boot there is a slightly newer screen, saying:

Software Update Failed

Your device didn't update successfully. Use the Verizon Software Repair Assistant on a computer to repair your device and complete the update.

(sorry I don't have a picture)

Now, I can't install the Verizon Software Upgrade/Repair Assistant because apparently you can't download it from their site, since it is supposed to install automatically when you plug your phone into your computer via USB. That obviously isn't happening with my phone in the state it's in.

On XDA here, I found someone posting this software Repair Assistant as "SUA_ar" tool. It installed on my computer, but the software doesn't even recognize my device when it is plugged in, so it won't even try to recover.

By the way, both in download mode and when I try to boot up, the top left of the screen says this:

ODIN MODE

PRODUCT NAME: SCH-I545

CURRENT BINARY: Samsung Official

SYSTEM STATUS: Custom

REACTIVATION LOCK: OFF

CSB-CONFIG-LSB: 0x30

SECURE DOWNLOAD: ENABLE

WRITE PROTECTION: Enable

eMMC BURST MODE: enabled

At this point, I don't care about root, tripping KNOX, or anything. I just want to know if there is a way I can get it working as a phone again.

I definitely deserve mockery for my stupidity, but if you can help, too, that would be great.
[Verizon Samsung Galaxy S 4] XxD34THxX:
[MENTION=3586804]KaosMaster[/MENTION] (I think)has a special little ZIP that may work. It is the full wipe, but it also contains files for re partition and whatnot. That MIGHT work.
[Verizon Samsung Galaxy S 4] KaosMaster:
You must use the following files:

https://docs.google.com/file/d/0B4RU_ZH5QUASNmxLX3JpejBXREE/edit?usp=docslist_api

If you want to revert to NK1 please use this image!

https://docs.google.com/file/d/0B4RU_ZH5QUAST1M5WkRNcy1Xek0/edit?usp=docslist_api

This is to repair to OC1:

https://docs.google.com/file/d/0B4RU_ZH5QUASaU9LcDJ3WWZfdXM/edit?usp=docslist_api

In the ODIN you just downloaded, select the CSC button, and select the extracted ALl_VZW_I545****.tar.md5

Then select these checkboxes:

Auto-Reboot

Re-Partition

F. Reset Time

NAND Erase All

Phone Bootloader Update

Phone EFS Clear

Hit START
[Verizon Samsung Galaxy S 4] Anastomosis:
Wow, thanks for the quick responses!

Unfortunately, the phone doesn't seem to want to let it do the NAND erase all for some reason! Or at least that's what I gather from this output:

Odin v.3 engine (ID:5)

File analysis...

SetupConnection...

Initialization...

Erase...

Complete(Write)operation failed.

All threads completed. (succeed 0 / failed 1).

This happened with both the NK1 and the OC1. Strange, I don't know what is limiting that Erase procedure...

In the top left corner of the phone, under all the ODIN MODE data, now it says:

START[224,1440]

ERASING USERDATA PARTITION...

And there is just a tiny bit of progress bar under the android logo.

If that matters.
[Verizon Samsung Galaxy S 4] KaosMaster:
Just uncheck the erase all for now, but I would try one more time with that setup...

It should just work

---------- Post added at 05:56 AM ---------- Previous post was at 05:55 AM ----------

And you didn't select re partition...

That is important
[Verizon Samsung Galaxy S 4] Anastomosis:
I did select re-partition, sorry I forgot to include that part in the output.

I unchecked "NAND erase all" and it had this failure after Initialization...

Set PIT file...

DO NOT TURN OFF TARGET!!

Get PIT for mapping...

Firmware update start..

SingleDownload.

aboot.mbn

NAND Write Start!!

FAIL! (Auth)

Complete(Write) operation failed.

All threads completed. (succeed 0 / failed 1)
[Verizon Samsung Galaxy S 4] KaosMaster:
You have to use the OC1 lollipop file then

Pull battery, re insert, then ODIN mode on power
[Verizon Samsung Galaxy S 4] Anastomosis:
Yes, this is actually with the OC1 file you provided, in the CSC slot. Should I try it in the AP slot with same options (except NAND erase)?
[Verizon Samsung Galaxy S 4] KaosMaster:
Oh...you can try that!! But I am worried about your hardware NOW.

If you just let it start, it gets to the emergency screen?? If yes, ODIN flash with that screen on the device.

Also they battery must be above 80% or it might not flash.
[Verizon Samsung Galaxy S 4] Anastomosis:
Oh, you mean do not flash it in Download mode? I should flash it in the screen where it says "Software Update Failed" ?
[Verizon Samsung Galaxy S 4] KaosMaster:
Yes try that

Also..I am working on a set of repair files
[Verizon Samsung Galaxy S 4] Anastomosis:
It made it farther!

I haven't tried AP slot yet. This is with OC1 file, in CSC slot, selecting NAND Erase All (and the other ones you said too)

Initialization..

Erase..

Set PIT file..

DO NOT TURN OFF TARGET!!

Get PIT for mapping..

Firmware update start..

SingleDownload.

aboot.mbn

NAND Write Start!!

sbl1.mbn

sbl2.mbn

sbl3.mbn

rpm.mbn

Complete(Write) operation failed.

etc...
[Verizon Samsung Galaxy S 4] KaosMaster:
Pull battery...go into ODIN...repeat
[Verizon Samsung Galaxy S 4] Anastomosis:
Ughh. Now Odin isn't even recognizing my phone in the emergency screen. It still recognizes it in download mode, though.

It was seeing it before in the emergency screen, obviously. Restarted Odin, restarted my phone a couple times, still nothing. Trying a couple more times.
[Verizon Samsung Galaxy S 4] KaosMaster:
Go to where you hold the buttons to download...This is ODIN. Will have the boot to flash in 5 mins
[Verizon Samsung Galaxy S 4] Anastomosis:
Good things happening! I just took it out and inserted it a couple more times after restarting Odin.

It's now flashing system.img.ext4 and hasn't failed yet. Fingers crossed...
[Verizon Samsung Galaxy S 4] KaosMaster:
Awesome!! All the checkboxes marked also??
[Verizon Samsung Galaxy S 4] Anastomosis:
Yes, even NAND Erase All.
[Verizon Samsung Galaxy S 4] KaosMaster:
That's how we ROLL!! Enjoy! Your device is like brand new! :)
[Verizon Samsung Galaxy S 4] Anastomosis:
You are very much the man, Kaos! It's back up!

I've been addicted to root for the past 4 years with various devices, but I think I'll chill out with that after this craziness. :) ... for now.
[Verizon Samsung Galaxy S 4] KaosMaster:
Haha! Yea..I am trying to find a work around to revert using ODIN....

And I completely understand
[Verizon Samsung Galaxy S 4] BlueForce64:
Hey guys, i am having the same exact issue except i am getting stuck at

modem.bin

NON-HLOS.bin

Complete(Write) operation failed.

Is there a modem file i am misisng? i did this so long ago i can't remember exactly what i did originally.
[Verizon Samsung Galaxy S 4] KaosMaster:
Download both the files I posted previously, pull battery, set odin up, replace battery, boot directly into ODIN mode.

Please select all the checkboxes I mentioned. And good luck!
[Verizon Samsung Galaxy S 4] BlueForce64:
Damn, i've tried that a few times. I'll keep trying.
[Verizon Samsung Galaxy S 4] KaosMaster:
You may need to go into recovery, and wipe data / factory reset
[Verizon Samsung Galaxy S 4] Bren123:
Are you using the official samsung usb charger and is your pc usb port usb 2.0 or higher?
[Verizon Samsung Galaxy S 4] XxD34THxX:
He has a point. I had trouble with Odin until I used the cord that came with my phone.
[Verizon Samsung Galaxy S 4] BlueForce64:
Yeah I was using the original cord. Found out my battery got a little on the low side, good thing I had a fully charged back up battery. Soon as I tried it again it went right through.

Thanks guys!
[Verizon Samsung Galaxy S 4] cwa82:
If my phone has no IMEI or Baseband or ICCID; how do I get past the activation screen on either one of these roms? I know on the older roms you just push the 4 corners below the last language followed by volume up. I couldnt get that to work on the newer roms.

I am rooted and stupidly thought I could install a custom recovery forgetting that the bootloader is locked.

I have tried flashing different modems and roms, and backing up the EFS and restoring it and formatting it and restoring it. Nothing seems to work.
[Verizon Samsung Galaxy S 4] KaosMaster:
You need to ODIN flash the stock NK1 with these checkboxes selected:

Auto Reboot

Re-partition

F. Reset Time

NAND Erase All

Phone Bootloader Update

Phone EFS Clear

It that doesn't work...Then it will need to be box reprogrammed using JTAG
[Verizon Samsung Galaxy S 4] cwa82:
is there an SD card version of JTAG for the S4 like there was for the S3?

I had an S3 that wouldn't go into download mode or display anything when charging. I had to make a special SD card and it had to be an expensive one with a higher data transfer rate number on it. For some reason, with just that SD card, no battery, and USB data cable the phone magically went into download mode and it was fixed.
[Verizon Samsung Galaxy S 4] cwa82:
just completed this and I'm stuck at the Setup Wizard
[Verizon Samsung Galaxy S 4] KaosMaster:
Just hit the SKIP, NOT NOW, LATER.

You can also..Press and hold the home key...And kill the task