Looking for ROMs for LG VS890/FX3 - Miscellaneous Android Development

Looking for ROMs for LG VS890/FX3 - Miscellaneous Android Development

Hi, folks,
After many, many attempts, I finally was able to root my Verizon LG Enact/VS890/FX3, using NewKingrootV4.50_C120_B220_xda_release_2015_07_22_105243.apk, which I got from this forum about a week ago... for which I heartily thank Zero Sparks. Finally able to uninstall a lot of the crapware I didn't want, and to install several root-only apps which I did want.
The thing I'm having trouble with now, is finding custom ROMs for the phone. It's running KitKat, so it's not ancient, and if I can't use anything but the stock ROM, so be it. But I'm dying to try flashing Lollipop or even Marshmallow. It has to be a very specific ROM for that phone, because of the slide-out QWERTY keyboard... the wrong firmware wouldn't function properly. And there are a lot of bogus sites out there which want you to "complete a survey" or "sign up for one of these offers", but they never give you the download, it's just an endless circle of phishing sites... with lots of malware for my system, I'm sure. I'd much rather trust you folks on here, if you have anything.

I'm in the same boat, would love to upgrade off of 4.1.2 but can't find anything to use.
Additionally, a previous owner (bought off ebay) apparently unlocked the bootloader and replaced the stock recovery with something I don't recognize. When holding down power and vol down I see this:
Rooted
*********************************************
FACTORY HARD RESET
*********************************************
Permanently Erase User Data & Reset Settings?
Press Power key to confirm, and Volume Down or Up key to cancel
So not only can't I find a ROM to use, I can't even upgrade the stock ROM due to it not passing the root check. And I can't use stock recovery since it was replaced by the above. Anyone see this before?
I wish there was better support for the VS890 around, but I can't even find the original recovery / ROM image to flash.

UsualNoise said:
I'm in the same boat, would love to upgrade off of 4.1.2 but can't find anything to use.
Additionally, a previous owner (bought off ebay) apparently unlocked the bootloader and replaced the stock recovery with something I don't recognize. When holding down power and vol down I see this:
Rooted
*********************************************
FACTORY HARD RESET
*********************************************
Permanently Erase User Data & Reset Settings?
Press Power key to confirm, and Volume Down or Up key to cancel
So not only can't I find a ROM to use, I can't even upgrade the stock ROM due to it not passing the root check. And I can't use stock recovery since it was replaced by the above. Anyone see this before?
I wish there was better support for the VS890 around, but I can't even find the original recovery / ROM image to flash.
Click to expand...
Click to collapse
In my research, I could have sworn I came across a site that had the original "stock" LG software for download, but I can't find it now. The closest I come is this LG link that will give you the firmware -- and the VS890 is on their list: http://www.mylgphones.com/latest-lg-phones-firmware-update-model-version-date
I don't know if that might restore your stock recovery, at least. But have you tried doing the "factory reset" they offer, in this recovery app? Typically, this often restores the phone to whatever it was shipped with... which in your case, is just what you want. And there might be a method out there to un-root, I've seen that option in some of the better apps, like the "LG One-Click Root" found here. Then (if you're on Verizon, anyway), you could snag the OTA upgrade to 4.4.2, like I have... and root it again with the method I found.
ADDED LATER: Look in SuperSU, you should find an option for Permanent UnRoot.

Mr2nSmith said:
But have you tried doing the "factory reset" they offer, in this recovery app? Typically, this often restores the phone to whatever it was shipped with... which in your case, is just what you want. And there might be a method out there to un-root, I've seen that option in some of the better apps, like the "LG One-Click Root" found here. Then (if you're on Verizon, anyway), you could snag the OTA upgrade to 4.4.2, like I have... and root it again with the method I found.
ADDED LATER: Look in SuperSU, you should find an option for Permanent UnRoot.
Click to expand...
Click to collapse
Thanks for responding. Unfortunately my issue isn't the rooting of the OS (which I can undo, and have), it's the fact that the bootloader was unlocked and original recovery was replaced with that custom one I listed above. And yes, I did the 'factory reset', which reset everything to the original state of 4.1.2 ... but it didn't remove the custom recovery. Because of that, I can't ever upgrade via normal means (get the 0x13 error when I try).
Same deal with SuperSU, unrooting simply removes root access in the 4.1.2 OS, doesn't affect recovery. And, since there is no CMW / TWRP custom recovery option for VS890 I can't even attempt replacing the existing recovery. I'm stuck at this point unless someone figures out 1) where the stock recovery and firmware are located, and 2) a method to safely flash it to the phone. It sucks, I like this phone but it has some severe limitations. It also won't work with my Pebble watch, which is what prompted this whole endeavor in the first place (trying to upgrade to KitKat).

UsualNoise said:
Thanks for responding. Unfortunately my issue isn't the rooting of the OS (which I can undo, and have), it's the fact that the bootloader was unlocked and original recovery was replaced with that custom one I listed above. And yes, I did the 'factory reset', which reset everything to the original state of 4.1.2 ... but it didn't remove the custom recovery. Because of that, I can't ever upgrade via normal means (get the 0x13 error when I try).
Same deal with SuperSU, unrooting simply removes root access in the 4.1.2 OS, doesn't affect recovery. And, since there is no CMW / TWRP custom recovery option for VS890 I can't even attempt replacing the existing recovery. I'm stuck at this point unless someone figures out 1) where the stock recovery and firmware are located, and 2) a method to safely flash it to the phone. It sucks, I like this phone but it has some severe limitations. It also won't work with my Pebble watch, which is what prompted this whole endeavor in the first place (trying to upgrade to KitKat).
Click to expand...
Click to collapse
Have you tried simply finding and uninstalling the custom recovery? I know you said it was unfamiliar to you, but it has to be in there somewhere, under some name. And once it's removed, the phone would revert to its stock recovery. This is a great little phone, even if you can only get it to KitKat, don't give up.

Mr2nSmith said:
Have you tried simply finding and uninstalling the custom recovery? I know you said it was unfamiliar to you, but it has to be in there somewhere, under some name. And once it's removed, the phone would revert to its stock recovery. This is a great little phone, even if you can only get it to KitKat, don't give up.
Click to expand...
Click to collapse
The bad news: I would have no idea how to 'find' the custom recovery unfortunately.
The good news: I solved my problem! Although I couldn't update the OS via normal means (network) or via PC connection, I was able to manually flash KitKat (4.4.2) myself successfully. Here's what I did:
1) I downloaded the drivers for the phone from LG's site and installed them.
2) Connected the phone, it went into 'install' mode first where a drive appeared in my computer that contained the Verizon Upgrade Assistant.
3) Ran the upgrade assistant, it found the phone and downloaded the new firmware (.cab file). The upgrade assistant would not apply the update, unfortunately. I don't know if it was because of my bootloader issue or not, but I was at a dead end. Temporarily.
4) Tried following the procedure here but it didn't work with the current LG tools available. However it did point me in the right direction for
5) I found the LGFlashTool. I followed the instructions on that site. First went into download mode (powered off, removed battery, inserted battery, held vol up and down while plugging in the USB cable - *make sure it's a good cable!!*), then in the flash tool dialog itself I entered the .cab file name, selected [ CDMA, Diag, 33000 ], left what was auto-filled in version (but deleted the .cab extension) and hit the CSE Flash button. Next dialog I tried reading phone info, but it crashed (didn't fill me with confidence). Restarted, got back to that dialog, hit START. Next dialog, selected my country and language, hit OK. Then it popped up a new LG update window that actually did the update / flash.
Shockingly, it successfully worked. I was preparing myself for a bricked phone, but it worked ... AND fixed my bluetooth connection issue with my Pebble watch.
I have no idea if this procedure would work for custom ROMs or not (and I'm not going to press my luck and try), so I can't recommend it for non-stock stuff, but at least it's a way to flash a known working ROM for the LG Enact. Hopefully this helps someone else down the road. This was the first firmware flashing endeavor I've undertaken where I didn't already know someone else did it successfully first. Thus, my trepidation.

UsualNoise said:
The bad news: I would have no idea how to 'find' the custom recovery unfortunately.
The good news: I solved my problem! Although I couldn't update the OS via normal means (network) or via PC connection, I was able to manually flash KitKat (4.4.2) myself successfully. Here's what I did:
1) I downloaded the drivers for the phone from LG's site and installed them.
2) Connected the phone, it went into 'install' mode first where a drive appeared in my computer that contained the Verizon Upgrade Assistant.
3) Ran the upgrade assistant, it found the phone and downloaded the new firmware (.cab file). The upgrade assistant would not apply the update, unfortunately. I don't know if it was because of my bootloader issue or not, but I was at a dead end. Temporarily.
4) Tried following the procedure here but it didn't work with the current LG tools available. However it did point me in the right direction for
5) I found the LGFlashTool. I followed the instructions on that site. First went into download mode (powered off, removed battery, inserted battery, held vol up and down while plugging in the USB cable - *make sure it's a good cable!!*), then in the flash tool dialog itself I entered the .cab file name, selected [ CDMA, Diag, 33000 ], left what was auto-filled in version (but deleted the .cab extension) and hit the CSE Flash button. Next dialog I tried reading phone info, but it crashed (didn't fill me with confidence). Restarted, got back to that dialog, hit START. Next dialog, selected my country and language, hit OK. Then it popped up a new LG update window that actually did the update / flash.
Shockingly, it successfully worked. I was preparing myself for a bricked phone, but it worked ... AND fixed my bluetooth connection issue with my Pebble watch.
I have no idea if this procedure would work for custom ROMs or not (and I'm not going to press my luck and try), so I can't recommend it for non-stock stuff, but at least it's a way to flash a known working ROM for the LG Enact. Hopefully this helps someone else down the road. This was the first firmware flashing endeavor I've undertaken where I didn't already know someone else did it successfully first. Thus, my trepidation.
Click to expand...
Click to collapse
Good for you! See, you don't give up, and you get a happy ending.

It's a shame no roms for ours enact, its a cute qwerty android phone...please Can someone tell me how to enter recovery mode ? I bought this phone 2 day's ago but i haven't signal i want to do a wipe cache.. .sorry for my English.. .

Androide3 said:
It's a shame no roms for ours enact, its a cute qwerty android phone...please Can someone tell me how to enter recovery mode ? I bought this phone 2 day's ago but i haven't signal i want to do a wipe cache.. .sorry for my English.. .
Click to expand...
Click to collapse
Wish I could help you, but I never could do that on mine... had to use a sideload tool to do it from my PC. BUT -- I have two suggestions for you. First, download and install the KingRoot tool, to root the phone... it's called NewKingrootV4.50_C120_B220_xda_release_2015_07_22_105243.apk, and I think there is a link earlier in this thread which you can use to find and download it. You'll have to install it manually, then run it. (Don't bother with the "Purify" portion, you don't need that for now.) Your phone will now be rooted, by the only method that ever worked for me. Next, go to the Play Store, and download an app called "Quick Reboot", from Phong IT. This is a root-only app (hence the need to root, first) which includes a "Recovery" option. Try that out, and see what happens.

Related

[Q] Rooting, Flashing, Upgrade services needed!

I've searched & found 'How to....' threads on here but TBH I'm not a techy and most of it doesn't make sense to me.
I did try to upgrade from 4.0.4 to 4.1 this week and almost succeeded until some 'signature not recognised' message appeared. So I'm going to attempt another way (if possible/allowed) and ask if there's anybody out there who'd be willing to root (whatever that means), flash (ditto) and upgrade to 4.1 for me in return for payment.
I really hope this isn't against forum rules - it's a genuine, last-ditch attempt.
I live in the West Mids but travel a big chunk of the country each week so could possibly deliver the thing.
Here's hoping for an avalanche of replies.....

Can anyone tell me why I get the 'signature not verified' message please?
I've downloaded the upgrade from an October thread on this forum.

Which xoom do you have (wifi, 3g/4g, international, family)? Are you rooted yet?

dfib1 said:
Which xoom do you have (wifi, 3g/4g, international, family)? Are you rooted yet?
Click to expand...
Click to collapse
Thanks for replying!!
It's the wi-fi model. As for 'is it rooted?' - I would say not. One, because it's hardly been used and two, because I have no idea what 'rooted' means.

junctiontwo said:
Thanks for replying!!
It's the wi-fi model. As for 'is it rooted?' - I would say not. One, because it's hardly been used and two, because I have no idea what 'rooted' means.
Click to expand...
Click to collapse
Sorry I took so long to answer.
As for being rooted if you are the only one to have own the xoom and don't know what it means then you are most likely not rooted. Root is like getting administrator rights in windows. It gives you the ability to customize your device, install custom roms and also completely screw up your device .
You should be able to go to settings-about tablet--update (or system update) and it will check for your update and ask you to start the download and install. If this does not happen then you can flash back to Honeycomb (which I can walk you through this will also wipe all your data or maybe for a fresh start) and let your device automatically update to ICS (4.04) and the JB (4.1).
I can also walk you through rooting and installing a custom JB rom like you asked for free.

dfib1 said:
Sorry I took so long to answer.
As for being rooted if you are the only one to have own the xoom and don't know what it means then you are most likely not rooted. Root is like getting administrator rights in windows. It gives you the ability to customize your device, install custom roms and also completely screw up your device .
You should be able to go to settings-about tablet--update (or system update) and it will check for your update and ask you to start the download and install. If this does not happen then you can flash back to Honeycomb (which I can walk you through this will also wipe all your data or maybe for a fresh start) and let your device automatically update to ICS (4.04) and the JB (4.1).
I can also walk you through rooting and installing a custom JB rom like you asked for free.
Click to expand...
Click to collapse
Please don't apologise - you're the only one to answer!
I've tried the system update and have been told that there are none. (In my ignorance I actually thought it would update to 4.1.2 automatically!).
Your offer to walk me through the rooting & upgrade is extremely generous and I accept without hesitation.
If it's flashed back to HC, will it default back to ICS or move to JB?
A huge 'Thanks'.
James
PS. Having tried numerous times very recently to upgrade there's no data to erase so that's not an issue....

I am going to give you the steps to unlock your xoom, install a recovery, root, install CWM Rogue Touch recovery (better than the one you used to root) and then install stock JB.
Now that we are talking root I am going to ask a moderator to moved this thread to the root section.
Here is how I rooted my xoom.
follow the directions here but instead of doing step 1 follow this for adb install http://www.support-4-you.com/main/i...ged-adb-installation&catid=40:how-tos&Itemid= it is a 1 click adb install then follow from step 2 on.
When you are done there you can install CWM Rogue Touch screen recovery
Download CWM Rogue Touch zip and put on the root of your external sd card. ( if you don't have a sd card we will do it another way just let me know)
Boot into recovery by turning your xoom off.
1. press power
2. when the moto dual core logo comes on wait 3 seconds and press volume down
3. recovery should be displayed across the top press volume up.
You can skip steps 1- 3 now that you are rooted if you download Quick Boot open it, select recovery and the grant Super user permission
4. go to install zip from sd card (just like when you rooted) and find the CWM Rogue Touch Zip and install
5. reboot your xoom
6. you now have CWM Rogue Touch installed.
To install JB on your xoom you do need an sd card for this part
DownloadJB stock for wifi xoom and copy to your sd-card
Here is the thread discussing this [JB]Stock Android 4.1.1 JRO03H, Root, via CWM Recovery (US Wi-Fi MZ604) and also there steps for installing it but I will post them for you here.
boot into recovery
select backup and let it backup your current system (a Parachute)
then select wipe factory/data ( I Can't remember excactly what it says because I use a different one)
then select install zip from sd card
locate the JB rom you copy to your sd-card and install.
reboot system (it will take some time the first time)
sign in to android with your gmail account.
You are on JB
Good luck and don't worry if something goes wrong we can get you out of 99.99% of any issues that arise.

dfib1 = I cannot thank you enough.....
The frustrating thing is I'm about to leave the house and am working away until the weekend so can't try it until then! I'll let you know the outcome.
Have a great day :good:

If you need help with his excellent guide just post here or hit with a pm
Sent from my Xoom using xda app-developers app

Ok, a quick mid-procedure question....
(I'm doing something fundamentally wrong because I can't quite finish the upgrade).
Do I install the folders onto the Xoom from the SD in a zipped or un-zipped state? I've tried both but no luck so far in completing the task.
I've rooted successfully as my PC recognizes the device. I believe I've installed CWM ok - is there a way to confirm this?
On the final 4.1 install I get the 'installation aborted' message as 'signature not verified'. One thing I may be doing wrong is installing the wrong files? On selecting the JRO03H folder I'm then given file choices and I'm clicking on what I think are the most obvious. I can post a list of the choices if it helps?
Sorry to be such a newbie pain - I realize that these questions are irritating to those 'in the know'!

did you reboot after fastbooting the recovery? the recovery says clockwork at the top. It should also be touch screen controlled
When you move the zip over leave it as a zip on you xoom and when you flash the recovery will unzip it for you.

what step are you up to?

Sorry for the late update. I've tried the whole procedure several times from the very beginning, even removing previously installed Rogue & JB software, but STILL get the same error messages as previously described. I've re-booted at the right time according to the instructions but this still makes no difference, and have checked the 'USB de-bugging' option.
I did make a couple of basic errors in the Command function to begin with but realised these & corrected them. My device serial no. appeared so I assume I rooted successfully? I'm able to change Developer settings which I couldn't before. I even installed the USB drivers independently via the Motorola website.
I have a free day today so am going to make a bucket of coffee, make myself comfortable and start again.
One quick point - I'm in the UK and assume you two helpful guys are in the US? Looking at numerous sites it seems our respective Xoom models have different procedures which is maybe why this isn't working?
Thank you again for your seemingly endless patience.......

i believe you are getting these issues because you might still be running the stock recovery.
lets just backup and start fresh.
You followed the instructions mentioned before and I assume you have adb and fastboot installed.
Connect your xoom and make sure usb debugging is on.
open up a command line and type adb reboot bootloader
I'm going to assume because of the previous steps you unlocked the bootloader if not type in the command line fastboot oem unlock
You can download the recovery from here http://bit.ly/iLRAIV
If unlocked at the bootloader type fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img Note:make sure the img file is in the same folder where your fasboot.exe is in the sdk
after it has been flashed reboot device by hold volume up and power.
Move the JB stock rom into your sd card. you can download the rom from here http://www.mediafire.com/?qhbhlbvu859bv0f
after the device restarts type adb reboot recovery
in recovery Wipe everything except the sd card. Then flash the above jb rom. In theory everything should work. If you keep getting the error get back to us because Im going to give up and guide you through the install of the Team EOS Jellybean 4.1 rom that I know works without issues. PM if you want to have my direct contact info for gtalk so we can discuss further for any issues.

OK I've just tried another 8 times to root the thing, c-a-r-e-f-u-l-l-y following the instructions step-by-step.
1. I don't have the 'from SD card' option, instead have 'from USB drive'. I have a 16Gb flash drive connected via an adaptor for the Xoom which doesn't appear to prevent anything as it reads the contents of the card just fine, unless you can tell me otherwise?
2. In Recovery I get these options:
* reboot system now
* apply update from USB drive
* wipe data/factory reset
* wipe cache partition
3. Even when trying the very first install (Rogue), I get:
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E: signature verification failed
Installation aborted
I love a challenge and always get a buzz when I manage to do something that is foreign to me i.e computers. On this occasion however I'm fast getting to the stage where I think it'd be easier to leave things at 4.0.4.
My reason for wanting the upgrade in the first place is because I'm comparing this tablet to my work-supplied Galaxy Tab 2 running 4.1.1. Realistically I don't think the two will ever be comparable and I'm probably foolish to think this could be the case. It only remains to say that I am so very grateful to both of you for taking so much time & effort in talking me though the procedures.
I consider myself pretty 'switched on' but this has me foxed!
Cheers guys - have a great weekend. Hope the snow doesn't cause you problems!

here are the outline of the steps
1. unlock your xoom
2. fastboot a recovery to install custom recovery on your xoom
3. reboot into new recovery
4. flash universal root zip to root your phone
5. reboot phone that is now rooted.
6. reboot phone into custom recovery again
7. flash jb update
I think you have missed step 1 or 2.
When you type fastboot oem unlock what does it say?

Hmmm, I MAY be one step closer?
After typing' fastboot oem unlock' the tablet has gone into 'Starting Fastboot protocol support' but appears to be stuck. Do I wait until it's done it's thing?
OR would it be a whole lot easier for all concerned if we tried your other suggestion dfib and flashed back to HC and then to JB?

What if you type adb devices? Does a bunch of numbers show up or does it say waiting for device?

Hold the front page!!!!!!!
I just watched a video on how to unlock and it's worked. You were quite correct - I had missed your point 1 above and probably point 2. I'm moving onto the next bit now....

Great let us know what happens. I will be around for a while.

[Q] Where to start the root process?

I have a GT-N8013 Galaxy Note 10.1 Wireless 16G. It has been updated to Jelly Bean and has been updated to JB through the Keis OTA and has also just recently received one or two other updates, for what reason I am not sure.
I just recently rooted my Droid Razr Maxx and so far, I am happy that I did that. Now I want to go ahead and root my Note 10.1, however I am thoroughly confused as to where to start. Through all of my Google searches and message board searches, I keep coming across what seems to be older instructions for updating to JB, which I already have, or rooting based upon apps that were in existence as far back as say August, 2012.
Well now it is the end of March, and I do not know if I should be pursuing this using Odin (which version and where is the best place from which to download it) or is there an alternative or better approach using CM 10, etc. As I typed the question, the last similar threads that popped up were from November 30, 2012 and prior.
I wanted to avoid having to ask what to many of you seems to be such a basic question, but there just doesn't seem to be anything that I see out there that has a recommended method, post OTA JB.
Any advise will be greatly appreciated.

bookbean said:
I have a GT-N8013 Galaxy Note 10.1 Wireless 16G. It has been updated to Jelly Bean and has been updated to JB through the Keis OTA and has also just recently received one or two other updates, for what reason I am not sure.
I just recently rooted my Droid Razr Maxx and so far, I am happy that I did that. Now I want to go ahead and root my Note 10.1, however I am thoroughly confused as to where to start. Through all of my Google searches and message board searches, I keep coming across what seems to be older instructions for updating to JB, which I already have, or rooting based upon apps that were in existence as far back as say August, 2012.
Well now it is the end of March, and I do not know if I should be pursuing this using Odin (which version and where is the best place from which to download it) or is there an alternative or better approach using CM 10, etc. As I typed the question, the last similar threads that popped up were from November 30, 2012 and prior.
I wanted to avoid having to ask what to many of you seems to be such a basic question, but there just doesn't seem to be anything that I see out there that has a recommended method, post OTA JB.
Any advise will be greatly appreciated.
Click to expand...
Click to collapse
Some of the rooting methods have been defeated by Samsung with the last 2 updates.
Zedomax has a root method that does work will the most current firmware updates and his version of CWM that is installed with his root method seems to be more compatible with a few of the custom ROM's out there.
You should visit these links, they are very informative.
http://forum.xda-developers.com/showthread.php?t=1831152
http://rootgalaxynote.com/galaxy-note-10-1-root/how-to-root-galaxy-note-10-1-easiest-methodcwmmethod-2/
Root Video Link
http://www.youtube.com/watch?feature=player_embedded&v=nIYiXzcW7xs
Un-Root directions
http://rootgalaxynote.com/galaxy-note-10-1-2/how-to-unrootunbrick-galaxy-note-10-1-factory-firmware/

Did not succeed with root
kkretch said:
Some of the rooting methods have been defeated by Samsung with the last 2 updates.
Zedomax has a root method that does work will the most current firmware updates and his version of CWM that is installed with his root method seems to be more compatible with a few of the custom ROM's out there.
You should visit these links, they are very informative.
http://forum.xda-developers.com/showthread.php?t=1831152
http://rootgalaxynote.com/galaxy-note-10-1-root/how-to-root-galaxy-note-10-1-easiest-methodcwmmethod-2/
Root Video Link
http://www.youtube.com/watch?feature=player_embedded&v=nIYiXzcW7xs
Un-Root directions
http://rootgalaxynote.com/galaxy-note-10-1-2/how-to-unrootunbrick-galaxy-note-10-1-factory-firmware/
Click to expand...
Click to collapse
I carefully watched the video. After the CWM-SuperSU-v0.94.zip file was transferred onto my external drive, I ran odin3 v1.85exe and got to the green pass screen. After the reboot, I held down the power and volume up buttons until I saw the screen go off. When the logo came up, I let go of the power button and I kept holding onto the power up button, but I did not get to the ClockworkMod Recovery screen. Instead, I was brought to the Android Recovery Screen. I tried clicking on the file on the external SD from that screen, but all that I got were failures.
What other options are there?
Thank you, btw, for trying to assist me.

bookbean said:
I carefully watched the video. After the CWM-SuperSU-v0.94.zip file was transferred onto my external drive, I ran odin3 v1.85exe and got to the green pass screen. After the reboot, I held down the power and volume up buttons until I saw the screen go off. When the logo came up, I let go of the power button and I kept holding onto the power up button, but I did not get to the ClockworkMod Recovery screen. Instead, I was brought to the Android Recovery Screen. I tried clicking on the file on the external SD from that screen, but all that I got were failures.
What other options are there?
Thank you, btw, for trying to assist me.
Click to expand...
Click to collapse
You did something wrong....... Did you do power and vol down at the same time first 1:40 of video after that run odin again.
It maybe better to download video in1080p to your computer so you can watch easier.

Resolved with an alternative process
kkretch said:
You did something wrong....... Did you do power and vol down at the same time first 1:40 of video after that run odin again.
It maybe better to download video in1080p to your computer so you can watch easier.
Click to expand...
Click to collapse
I used Odin, but found another root method called CF-Auto-Root-p4notewifi-p4notewifiue-gtn8013.zip. That worked like a charm. I then installed Root Checker to ensure that it worked, which it did.
So now I need to know what applications I need to install next as a follow-up.

I don't believe Auto root installs CWM. You may need to get Mobile ODIN, there's a free version on XDA or a paid version in the play store... I prefer to get the licenced version as there's more things you can do.
After installing this, you can then put the CWM file on your sd card or internal memory and flash it or just flash a custom rom...
Flashing a custom rom should put a custom recovery on too...
You might want to download and run an app called triangleaway to reset your flash counter too...

Moving right along
ultramag69 said:
I don't believe Auto root installs CWM. You may need to get Mobile ODIN, there's a free version on XDA or a paid version in the play store... I prefer to get the licenced version as there's more things you can do.
After installing this, you can then put the CWM file on your sd card or internal memory and flash it or just flash a custom rom...
Flashing a custom rom should put a custom recovery on too...
You might want to download and run an app called triangleaway to reset your flash counter too...
Click to expand...
Click to collapse
Thank you all for helping this root noobie. So I am running CWM Recovery v6.0.0.1.1 right now and doing a full backup to my external card. Seems like it should be done pretty soon. The blue widget in Andy's belly doesn't seem to move too much, if at all, however I do see that the progress bar is moving along and the file names keep changing below "backup up data...".
On top of Andy's head are three little guys with the words "High on Android" across his head. Oops, now I'm getting messages about skipping backup of apps and the fact that No sd-ext found. I don't understand that as there is most certainly an ext SD card.
Assuming that this completes OK, I will next proceed for CM10 and Triangleaway, unless there are other recommendations. Now back to the main Backup and Restore screen. Sorry for the blow by blow, but this is all new to me. Would my Titanium license provide the same benefits?

Here are a few good must haves for me.
Triangle Away
https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway&feature=search_result#?t=W251bGwsMSwxLDEsImV1LmNoYWluZmlyZS50cmlhbmdsZWF3YXkiXQ..
Carbon - App Sync and Backup
https://play.google.com/store/apps/details?id=com.koushikdutta.backup
AirDroid (better than Kies for wireless file transfer)
https://play.google.com/store/apps/details?id=com.sand.airdroid
MyScript Calculator
https://play.google.com/store/apps/details?id=com.visionobjects.calculator
.

Triangle Away
kkretch said:
Here are a few good must haves for me.
Triangle Away
https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway&feature=search_result#?t=W251bGwsMSwxLDEsImV1LmNoYWluZmlyZS50cmlhbmdsZWF3YXkiXQ..
Carbon - App Sync and Backup
https://play.google.com/store/apps/details?id=com.koushikdutta.backup
AirDroid (better than Kies for wireless file transfer)
https://play.google.com/store/apps/details?id=com.sand.airdroid
MyScript Calculator
https://play.google.com/store/apps/details?id=com.visionobjects.calculator
.
Click to expand...
Click to collapse
I went ahead and downloaded Triangle Away. When I start in download mode, I receive the warning along with the big yellow triangle. After pressing volume up to continue, it goes into Odin Mode (in Red) and shows that the Custom Binary Download: Yes (5 counts), followed by Current Binary: Custom and then System Status: Custom. To get out of that screen, I have just held down the power button to turn off the device.
When I start up the Triangle Away app, the current status (under Flash Counter) says that Status cannot be determined, need to reboot into a special bootmode - tap "Reset flash counter".
In the Overview section on Play Store, it shows this warning:
On a number of devices, TriangleAway can work, but your firmware may not be supported directly. In that case, the app will tell you it needs to reboot into a special boot mode, which will be happen if you select "Reset flash counter". The device will reboot into a special mode which will allow you to review the current status and reset the binary and flash counter values (or abort and do nothing). On some devices this will actually trigger the counter to 1 if its 0 - so if you're "just checking", do that in download mode!
!!! THIS IS A DANGEROUS OPERATION AND COULD POTENTIALLY BRICK YOUR DEVICE. PROCEED AT YOUR OWN RISK. A USB JIG IS PREFERRED IF YOU HAVE A WORKING ONE !!! ( and by brick I mean brick - only a board replacement or a JTAG unit will be able to save you, don't mess with boot(loader) stuff unless you *really* mean it! )
Note#1: using Triangle Away may unmount your SD card. Reboot or manually remount it from Android settings.
Note#2: on new devices like the SGS3/SGNote2/SGNote10.1, status can only be reset on some firmwares - they must be stock firmwares!
I am not clear on how to interpret the warning, other than it makes me a bit nervous about bricking the device. I did a quick search of USB JIG for the SGN10 and I didn't see anything come up in the first few Google pages. One placed discussed making your own JIG which involves soldering. Not my thing!
So my question is has any other GT-N8013 user performed the step of selecting the reboot into the special mode, and if so, what happens after that? More importantly, did anyone experience having their SGN10/GT-N8013 bricked from this step?
Again, sorry if this is basic to most, but it is new to me, and we all have to start somewhere.
Thanks,
'Bean

bookbean said:
I went ahead and downloaded Triangle Away. When I start in download mode, I receive the warning along with the big yellow triangle. After pressing volume up to continue, it goes into Odin Mode (in Red) and shows that the Custom Binary Download: Yes (5 counts), followed by Current Binary: Custom and then System Status: Custom. To get out of that screen, I have just held down the power button to turn off the device.
When I start up the Triangle Away app, the current status (under Flash Counter) says that Status cannot be determined, need to reboot into a special bootmode - tap "Reset flash counter".
In the Overview section on Play Store, it shows this warning:
On a number of devices, TriangleAway can work, but your firmware may not be supported directly. In that case, the app will tell you it needs to reboot into a special boot mode, which will be happen if you select "Reset flash counter". The device will reboot into a special mode which will allow you to review the current status and reset the binary and flash counter values (or abort and do nothing). On some devices this will actually trigger the counter to 1 if its 0 - so if you're "just checking", do that in download mode!
!!! THIS IS A DANGEROUS OPERATION AND COULD POTENTIALLY BRICK YOUR DEVICE. PROCEED AT YOUR OWN RISK. A USB JIG IS PREFERRED IF YOU HAVE A WORKING ONE !!! ( and by brick I mean brick - only a board replacement or a JTAG unit will be able to save you, don't mess with boot(loader) stuff unless you *really* mean it! )
Note#1: using Triangle Away may unmount your SD card. Reboot or manually remount it from Android settings.
Note#2: on new devices like the SGS3/SGNote2/SGNote10.1, status can only be reset on some firmwares - they must be stock firmwares!
I am not clear on how to interpret the warning, other than it makes me a bit nervous about bricking the device. I did a quick search of USB JIG for the SGN10 and I didn't see anything come up in the first few Google pages. One placed discussed making your own JIG which involves soldering. Not my thing!
So my question is has any other GT-N8013 user performed the step of selecting the reboot into the special mode, and if so, what happens after that? More importantly, did anyone experience having their SGN10/GT-N8013 bricked from this step?
Again, sorry if this is basic to most, but it is new to me, and we all have to start somewhere.
Thanks,
'Bean
Click to expand...
Click to collapse
I think there's no USB jig to Note 10.1. I have used TriangleAway for my I9100 few times and N8010 (same that your device but european) once and both worked fine, no bricks. After you boot in "special mode", you'll be shown your counter, and it will confirm are you sure, you can cancel it there if you want and it does nothing to your device. Just check that your download mode's counters match TriangleAway's counters.

After Special Mode
niko0o said:
I think there's no USB jig to Note 10.1. I have used TriangleAway for my I9100 few times and N8010 (same that your device but european) once and both worked fine, no bricks. After you boot in "special mode", you'll be shown your counter, and it will confirm are you sure, you can cancel it there if you want and it does nothing to your device. Just check that your download mode's counters match TriangleAway's counters.
Click to expand...
Click to collapse
Thanks for giving me the courage to give it a shot, which I have now done. The counter in the special mode matched what Odin was showing, so I went ahead with it.
Now when I start up holding down the volume down button along with the power button, I am still getting the Triangle. However this time, below the Odin Mode (written in red), it shows Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
I take it that because there is still root on the device, that the System Status will continue to show "Custom" and I will continue to have the triangle? I thought that the idea was to get everything to "look" official stock. Please let me know if I am missing anything else.
Thanks,
'Bean

I Got All Things Official By Flashing A Stock Rom Through Mobile ODIN Onto The Note At This Point BUT You Will Need To Factory Reset. You Will Also Go Back To Stock Recovery. If You Want All These Things To Display Official Status.
I Haven't Got It Back To Not Show Official While Running A Custom Rom As Current Binary Changes To Custom When You Install Cwm Or System Status Does.
Theres Also A Status In Settings> About> Status That Will Also Say Custom Too. Shouldnt Be A Problem Unless You Try To Use The Allshare Cast Hub...

ultramag69 said:
I Got All Things Official By Flashing A Stock Rom Through Mobile ODIN Onto The Note At This Point BUT You Will Need To Factory Reset. You Will Also Go Back To Stock Recovery. If You Want All These Things To Display Official Status.
I Haven't Got It Back To Not Show Official While Running A Custom Rom As Current Binary Changes To Custom When You Install Cwm Or System Status Does.
Theres Also A Status In Settings> About> Status That Will Also Say Custom Too. Shouldnt Be A Problem Unless You Try To Use The Allshare Cast Hub...
Click to expand...
Click to collapse
My understanding is that Allshare is useful only if you have other Samsung devices. So first, please advise if my understanding on that is correct. Assuming that this is the case, then I suppose that I do not need to immediately concern myself with getting all three settings to be "official", as I am in no immediate need (hopefully) to go back to full factory settings with official software since I do not own any other Samsung Android device. I am only beginning the root journey. I guess that it is good to have the bread crumbs to find my way back home at first, but I also want to be adventurous and try out some of these really interesting things which root is supposed to lead me to.
Is it fair to say then, that the counter thing shouldn't be a concern for now?

bookbean said:
My understanding is that Allshare is useful only if you have other Samsung devices. So first, please advise if my understanding on that is correct. Assuming that this is the case, then I suppose that I do not need to immediately concern myself with getting all three settings to be "official", as I am in no immediate need (hopefully) to go back to full factory settings with official software since I do not own any other Samsung Android device. I am only beginning the root journey. I guess that it is good to have the bread crumbs to find my way back home at first, but I also want to be adventurous and try out some of these really interesting things which root is supposed to lead me to.
Is it fair to say then, that the counter thing shouldn't be a concern for now?
Click to expand...
Click to collapse
To zero that last you need to flash stock firmware with Odin, but thats not necessary except if you need to return your Note to warranty or something.

bookbean said:
My understanding is that Allshare is useful only if you have other Samsung devices.
Click to expand...
Click to collapse
I own an allsharecast hub and I use it at school to lecture.I project the tablet screen to an hdmi LED TV which is not a Samsung brand.So no;you have a misunderstanding at this.And since I have a GT-N8005 device and triangle away doesn't support this device I can't use the 'reset flash counter' method:crying:

Allshare
ordeniz said:
I own an allsharecast hub and I use it at school to lecture.I project the tablet screen to an hdmi LED TV which is not a Samsung brand.So no;you have a misunderstanding at this.And since I have a GT-N8005 device and triangle away doesn't support this device I can't use the 'reset flash counter' method:crying:
Click to expand...
Click to collapse
Thank you for clarifying the allsharecast hub use and I am sorry that you cannot change your flash counter. Is it possible for the author of the program to modify it for your device? Perhaps you can contact them about it.

bookbean said:
Thank you for clarifying the allsharecast hub use and I am sorry that you cannot change your flash counter. Is it possible for the author of the program to modify it for your device? Perhaps you can contact them about it.
Click to expand...
Click to collapse
Thanks.I posted a comment on google play store,and I will contact them soon.

A: Having Problems Rooting the Note Pro 12.2 SM-P900/905? TRY THIS!

**NOTE** For the SM-P900! However steps should be the same for SM-P905 EXCLUDING THE FILE TYPES (THEY ARE DIFFERENT DO NOT ATTEMPT TO USE THE FILES FOR THE SM-P900 OR BYE BYE TO YOUR NOTE 12.2 Pro because now you have a problem that may or may not be repairable/reversible). You just have to make sure you have the coordinating files for the process!
If anyone else has issues try this and these steps to complete the Root/Custom ROM/TWRP Recovery installations successfully for a "First time go":
1. Remove Kies and Kies3 files, related files, folders, and everything that has anything to do with the primary installation of either the two programs on your PC and your devices. When/if prompted, select the checkable box and elect not save any type of files... if you want to keep them save them OFF your main PC on a flash or removable storage device.
2. REMOVE ALL SAMSUNG DRIVERS AND REPLACE WITH ONLY OFFICIAL SAMSUNG DRIVES!!! THIS IS A BIG MUST!
3. Using your USB 2.0 cable and ports Install the Custom Rom "P900XXUANB3-RecoveryImg.tar" FIRST and flash it via ODIN 3.07 under the PDA checkbox that is "fixed" (so you noobs don’t make any soft bricks if this is your first attempt at rooting), and only use the ODIN 3.07 THAT COMES W/ CHAINFIRES AUTO ROOT .zip file and then unzip the folder to open ODIN 3.07 ONLY! This is only because I have read that there have been issues installing the SU via Chain Fires Auto Root Process... the file is called (currently as of 25 JUNE 2014) "P900XXUANB3-RecoveryImg.tar" PDA select it and then start when in DOWNLOAD MODE on your device. Manually select DOWNLOAD MODE if you have to BEFORE PRESSING START! Otherwise, one is just going to sit there and not accomplish anything.
http://forum.xda-developers.com/attachment.php?attachmentid=2591013&d=1392923580
http://forum.xda-developers.com/attachment.php?attachmentid=2591159&d=1392930654
http://forum.xda-developers.com/attachment.php?attachmentid=2775098&d=1401644348
4 Reboot back into DOWNLOAD MODE. Flash in ODIN 3.07 with the PDA section and select this file next to install: "openrecovery-twrp-2.7.1.0-v1awifi.img.tar"
5. In DOWNLOAD MODE and flash the file under the PDA box TWRP (OR CURRENT RECOVERY OF YOUR CHOICE THAT IS AVAILABLE)
6. AGAIN... Restart your device into DOWNLOAD MODE via ODIN 3.07 and select PDA and then finally root this: "CF-Auto-Root-v1awifi-v1awifixx-smp900.tar.md5" Then you can backup, restore, flash anything, and be happy! YOU SHOULD FINALLY HAVE A SUCCESSFUL ROOT! Turn off and REBOOT into RECOVERY to see if TWRP stuck and then reboot to see if the SU stuck. IF everything stuck reboot back into TWRP to flash whatever rom is available MAKE SURE TO BACK UP EVERY FILE BEFORE YOU FLASH ANY NON-STOCK ROMS. If not successful rinse wash and repeat until it does!
http://download.chainfire.eu/384/CF-Root/CF-Auto-Root/CF-Auto-Root-v1awifi-v1awifixx-smp900.zip
7. That’s it you should have root and a custom rom and recovery if you followed these instructions for flashing via ODIN 3.07 and Chainfires AutoRoot files. If you still have an issue repeat until root/recovery/Rom sticks. If you have to update the Binary for the SU just go to the Google Play Store and install the app and then try it again till it works. GOOD LUCK it worked for me this way!
**IMPORTANT**
BACK UP BACK UP BACK UP BACK UP after every flash that is possible to back up. If you can, back up the NON-SU stock ROM BEFORE installing SU, after installing the recovery and/or back up.
***IF I HELPED YOU OUT THANK ME***
DISCLAIMER - all research was observed via comments on the thread according to issues people have been having during ROOTING the device I simply have compiled the data and made a check list!

Need a link to the files you mentioned.

Thanks. Very helpful.
I have a P900. Is there a way to unroot and bring a unit back to stock? My main concern is if Samsung sends out a software/firmware update, and a device is already rooted, can the update be applied?

sstea said:
Thanks. Very helpful.
I have a P900. Is there a way to unroot and bring a unit back to stock? My main concern is if Samsung sends out a software/firmware update, and a device is already rooted, can the update be applied?
Click to expand...
Click to collapse
Read THIS
But still one quiestion, why the heck you root your device if you are going to update it via Samsung's official ways. Ah and one more question.. why the heck would you want to update your device if it's rooted?
A new update from Samsung can patch all known security holes and make your device unrootable, and since you are rooted now, one would think that you don't want to loose it. Or where do I know if you rooted because it sounded nice and cool, without knowing what you did and most importantly WHY you did.

Spere said:
Read THIS
But still one quiestion, why the heck you root your device if you are going to update it via Samsung's official ways. Ah and one more question.. why the heck would you want to update your device if it's rooted?
A new update from Samsung can patch all known security holes and make your device unrootable, and since you are rooted now, one would think that you don't want to loose it. Or where do I know if you rooted because it sounded nice and cool, without knowing what you did and most importantly WHY you did.
Click to expand...
Click to collapse
Thanks. I appreciate the reply. I have rooted many devices before. I have to admit that it was more of following posted instructions and not fully understanding the details. What gives me pause is how extremely limited the support is for this tablet. I want to root my note if I can make it more responsive, get rid of bloatware, enable more apps for multi-window, titanium backup, etc. I want to make sure that if I root that I don't get stuck with on an old release. So will previously rooted Notes be able to get the necessary files to easily update and maintain root, or does rooting now mean that a tablet may be stuck at the current release? Thanks

sstea said:
Thanks. I appreciate the reply. I have rooted many devices before. I have to admit that it was more of following posted instructions and not fully understanding the details. What gives me pause is how extremely limited the support is for this tablet. I want to root my note if I can make it more responsive, get rid of bloatware, enable more apps for multi-window, titanium backup, etc. I want to make sure that if I root that I don't get stuck with on an old release. So will previously rooted Notes be able to get the necessary files to easily update and maintain root, or does rooting now mean that a tablet may be stuck at the current release? Thanks
Click to expand...
Click to collapse
You can always flash stock firmware via odin

I was just wondering if everyone was having a much easier time with achieving root now? Kies caused me to "Hang" a lot during the Root and custom rom to stick w root... as of right now i can not get the only ONE custom ROM that looks promising, i have found by GWatts (correct me if i am wrong and i apologize if i have typed the wrong screen name handle) i believe his handle is... at this point im not sure what i am doing wrong as of yet but im sure i am missing a step or i just need to start back at unroot back to stock firmware and try and try again lol. not saying anything is wrong with his work at all by any means because people other than me with the same device have gotten it to stick and im just wishing i could as well because its sweet looking ROM! NOT TO MENTION THE ONLY ONE THAT IS OUT (that is which i know about. i haven't been on in a few months idk), SO KUDOS TO WATTS i just haven't been successful at installing his custom rom just yet... Im hoping that its just going to need to be erased again and then reformatted after a factory reset and what not, i pray it sticks because his incorporation of the aroma installer was a nice touch and his ROM really looks good... Now if i can just get it not to stick at samsung boot logo and freeze id be good lol!

sanvara said:
Need a link to the files you mentioned.
Click to expand...
Click to collapse
ok

I followed your instructions but while flashing the cf-auto-root file my screen got all distorted (speckled grains of color), and nothing else happened for about 15 minutes, until I just unplugged it and shut it off.
Now when I power it on it gives me the error "Firmware upgrade uncountered an issue. Please select recovery mode in Kies & try again."
I wonder what I did wrong.

pnuker said:
I followed your instructions but while flashing the cf-auto-root file my screen got all distorted (speckled grains of color), and nothing else happened for about 15 minutes, until I just unplugged it and shut it off.
Now when I power it on it gives me the error "Firmware upgrade uncountered an issue. Please select recovery mode in Kies & try again."
I wonder what I did wrong.
Click to expand...
Click to collapse
**Edit**
I went back and reflashed the twrp file and it got me out of the error screen. I installed supersu, and then re-flashed the cf-auto-root file, and it worked like a charm. I'm not sure if it was the installation of supersu, or just repeating the process that fixed it, but I'm happy either way...

Thank you! I succesfully rooted my SM-P900 after all mentioned problems ( hanging in the cache.img and after a while a disturbed screen etc.) with your guide. I am a very happy rooter now.

Thanks,
Thanks to the poster. I tried rooting with the instructions from a few other sites and thought I bricked it,
Followed your instructions, and presto.. Rooted! :good:

Rooted!
Thanks for your post. This is my first time ever rooting a device. Your method worked perfectly!

your welcome!
frankiecxyz said:
Thanks for your post. This is my first time ever rooting a device. Your method worked perfectly!
Click to expand...
Click to collapse
your very welcome! it took me a bit to get it down but i eventually figured it out and at the time information on rooting the device was hard to find with this specific model. then i discovered what the issues where and felt the need to post it! im glad i could help!:laugh:

Flash SU with TWRP not ODIN
Here's my story...
Received my new UK spec SM-P900 Note Pro 12.2, ran through the initial setup, performed two OTA upgrades to KOT49H.P900XXUANI1, then attempted to flash SU using Odin 3.07 using the various instructions on this forum. Result: failed cache flash and soft brick!
Used Keis 3 to recover the tablet which took two hours! After more reading I discovered the quick boot recovery flash method, so re-attempted on a different PC, with exactly the same result. Re-flashed the boot, tried again, fail, again, fail, etc, etc. Various permutations of PCs, Odin versions and USB ports were tried.
Concluded that the Odin method was NEVER going to work, so had a rethink. Used Odin to flash TWRP v2.8. Downloaded the latest SU-BETA v2.7 flash for TWRP (not Odin), copied it to the root of the tablet SD and then flashed it with TWRP. Worked first time with no messing about!!!
Booted, ran SU and upgraded to Premium, disabled KNOX from within SU. Tablet locked up. Booted, re-ran SU, disabled KNOX again, this time successfully. Ran Titanium, filtered with KNOX and froze all occurrences, then de-installed KNOX completely. :good:
Lesson learnt... DO NOT use Odin to flash SU on a P900 !

soft bricked
Hello!
First of all let me say that I'm a complete newbie, this is my first android device. I tried to root my SM-P900 (P900XXUANI1) using an online guide (image with URL attached, as I am not allowed to paste URLs)
Unfortunately at Step 10 (flashing with Odin) the operation failed and now I ended up with a soft bricked device (I assume this is the correct definition). It will only show the message asking me to connect it to KIES to recover it.
I know i can try to use KIES 3 and restore it, but before that i would like to ask if there is any alternative which will allow me to unbrick the device without losing all my data... (yeah i know...).
If i follow this guide will this help? I'm not sure if I can even put the device in download mode again as it shows the error message about connecting it to KIES...
At this point I don't care about rooting, I just want to unbrick the device.... I understand the guide up to (and including) step 3. But for the rest of the steps I'm lost Could anyone please explain them in a bit more detail? I don't want to install any custom firmware, just to unbrick it...
Any help would be very appreciated!
Thank you

Yemble said:
Here's my story...
Received my new UK spec SM-P900 Note Pro 12.2, ran through the initial setup, performed two OTA upgrades to KOT49H.P900XXUANI1, then attempted to flash SU using Odin 3.07 using the various instructions on this forum. Result: failed cache flash and soft brick!
Used Keis 3 to recover the tablet which took two hours! After more reading I discovered the quick boot recovery flash method, so re-attempted on a different PC, with exactly the same result. Re-flashed the boot, tried again, fail, again, fail, etc, etc. Various permutations of PCs, Odin versions and USB ports were tried.
Concluded that the Odin method was NEVER going to work, so had a rethink. Used Odin to flash TWRP v2.8. Downloaded the latest SU-BETA v2.7 flash for TWRP (not Odin), copied it to the root of the tablet SD and then flashed it with TWRP. Worked first time with no messing about!!!
Booted, ran SU and upgraded to Premium, disabled KNOX from within SU. Tablet locked up. Booted, re-ran SU, disabled KNOX again, this time successfully. Ran Titanium, filtered with KNOX and froze all occurrences, then de-installed KNOX completely. :good:
Lesson learnt... DO NOT use Odin to flash SU on a P900 !
Click to expand...
Click to collapse
Have you got a link to the odin rwrp 2.7 you used and the su 2.7 flash for twrp please?

VenomousViper said:
**NOTE** For the SM-P900! However steps should be the same for SM-P905 EXCLUDING THE FILE TYPES (THEY ARE DIFFERENT DO NOT ATTEMPT TO USE THE FILES FOR THE SM-P900 OR BYE BYE TO YOUR NOTE 12.2 Pro because now you have a problem that may or may not be repairable/reversible). You just have to make sure you have the coordinating files for the process!
If anyone else has issues try this and these steps to complete the Root/Custom ROM/TWRP Recovery installations successfully for a "First time go":
1. Remove Kies and Kies3 files, related files, folders, and everything that has anything to do with the primary installation of either the two programs on your PC and your devices. When/if prompted, select the checkable box and elect not save any type of files... if you want to keep them save them OFF your main PC on a flash or removable storage device.
2. REMOVE ALL SAMSUNG DRIVERS AND REPLACE WITH ONLY OFFICIAL SAMSUNG DRIVES!!! THIS IS A BIG MUST!.......
Click to expand...
Click to collapse
When i trying root, my SGN freeze in "cache". Odin show error and tablet goes to Emergency Firmware Recovery. Аnd it does not matter what program I use and how I do it.

Mine Reboots Constantly
I rooted my SM-900 about two weeks ago.
It worked great for a week until the device started rebooting by itself.
The first time a couple times a day, now it does it whenever as often as twice in 5 minutes.
Is there a way to see which app is causing this or does anyone know why this might be happening?
Though I rooted I haven't been poking around. I figured it'd be like using Linux but now I see it's not quite like that.
Thanks in advance.

sunnykhs said:
I rooted my SM-900 about two weeks ago.
It worked great for a week until the device started rebooting by itself.
The first time a couple times a day, now it does it whenever as often as twice in 5 minutes.
Is there a way to see which app is causing this or does anyone know why this might be happening?
Though I rooted I haven't been poking around. I figured it'd be like using Linux but now I see it's not quite like that.
Thanks in advance.
Click to expand...
Click to collapse
Have you cleared dalvic cache and cache in TWRP recovery? Be forewarned the process takes a while for cache wipe.
Sent from my SM-P900 using Tapatalk

[Completed] HTC Vivid won't boot, possibly after build.prop change

Hello,
Pretty new to rooting, tried to root my HTC Vivid to install some apps which are "incompatible" with my device. Unlocked bootloader and rooted successfully by installing TWRP recovery and installing the supersu zip. After copying the build.prop file to another folder I proceeded to make some minor changes to the build.prop file with ES File Explorer. Essentially changing the model ID of the phone to another device to try to prompt Google Play to show the incompoatible apps, didn't touch anything boot-related or anything else. Phone was working fine at that point, rebooting ok, but Google Play still showed the apps as incompatible, so I temporarily brought back the old build.prop file by copy/pasting it from the folder I made. The system indicated the copy was made successfully, and I tried to reboot once more. That is where the problem started.
When the power button is pressed for a second or so, the phone vibrates once and shows the starting splash screen (HTC) as it did when working, and then the screen goes blank, although the LED backlight is still on (so phone has power). Nothing comes after, no "HTC quietly brilliant" logo nor the chime that indicates it's booting up. At that point it stops responding to any stimulus except the removal of the battery, at which point the LED backlight finally goes off. Waiting for ~10min solved nothing, still blank black screen with backlight on. Upon reinserting the battery, the phone once again responds to the power button, with the same results.
I can boot to recovery by holding down Vol down and pressing power, and there I get the usual options including Fastboot, Recovery, etc. I tried doing a factory reset. It gives a bunch of error messages along the lines of "can't mount emmc", then says it's starting the reset, and gives a successful completion prompt after half a minute or so. However, that seems to do nothing at all to fix the problem (tried 4x times, with SD card in and out).
The only change that comes to mind is the last replacement of the build.prop file I did, which should have just restored the original. Assuming the factory reset doesn't actually reset that file (where would it get a copy to do so?) perhaps it being broken is preventing me from booting after the reset. Just my theory though, and could be something else.
From what I understand I could try putting a recovery image on the micro sd from a PC, then doing a recovery rather than a factory reset from the TWRP menu to replace all the files, including the potentially problematic build.prop. However, I didn't make a backup of the system before this happened (learning experience) and have no such image. Could anyone perhaps point me to a clean image for the Vivid that I could download and flash to my phone with recovery? Or otherwise shed some light on what could be causing the problem? I also realize there are various unbricking tutorials online, but after many hours of this I'm a bit too exhausted to follow all of those just to see if they work or not.
Edit: Upon further research I realize I can try to flash a new rom to the Vivid, but no matter how much I search I can't find a working link for a stock ICS .zip. There is a RUU .exe file from HTC but my phone can't get past fastboot, so I'd need to do this with a zip file. Anywhere I can get a working one? I could also try a custom rom, I just have 0 knowledge of those so don't know which would be a safe bet.
Would appreciate any help, and hope the post isn't overly long. Tried to give as much info as I could. I already spent a ton of time on both the root procedure and trying to fix this and would really like to hear professional opinions before breaking anything else. Thanks for reading.

Hi, thank you for using XDA Assist. The best place to get help is in your device's specific forum here, http://forum.xda-developers.com/htc-vivid They are the experts on your device. You may have already seen this but it's a good place to start, http://forum.xda-developers.com/showthread.php?t=1486024 If it were me I'd return the device to stock and start over. If you're messing with your phone you will want to be comfortable on how to return it to stock as you'll probably have to do that more than once as you learn more about your device.

jd1639 said:
Hi, thank you for using XDA Assist. The best place to get help is in your device's specific forum here, http://forum.xda-developers.com/htc-vivid They are the experts on your device. You may have already seen this but it's a good place to start, http://forum.xda-developers.com/showthread.php?t=1486024 If it were me I'd return the device to stock and start over. If you're messing with your phone you will want to be comfortable on how to return it to stock as you'll probably have to do that more than once as you learn more about your device.
Click to expand...
Click to collapse
Thanks for the advice, I basically got into rooting from scratch a day ago, so many resources I don't know about. Trying to return to stock, but I need a rom of the stock in .zip form since the phone can't get past recovery, and having trouble finding that. Perhaps due to age of phone, but most links to those seem to no longer be functional.
rohanreddy277 said:
Actually u shouldnt have rooted with that zip file containing supersu u actually should have done it with kingo root. anyway, the best waty to revive it is to install cyanogenmod. download the version for ur device and google how to install cyanogenmod. this will give a new life to ur phone. hope it helps.
Click to expand...
Click to collapse
Right, I basically learned as I went along for this root, haven't even heard of kingo before. I was very careful, but apparently something still went wrong. Thanks for the suggestion, I'll try that mod and see if it works.
Edit: I'm only finding a nightly build for the Vivid on the CyanogenMod website, with no stable versions. Nightly build is dated two years ago, so clearly no stable versions coming. While I'm in no position to be picky, and I'll try it if needed, I'd rather not break what's still functioning in my phone. Any mods out there that are stable for the Vivid?
Edit2: the nightly cyanogen build seems to have brought the phone back online, but besides the different look and feel from what I'm used to, it doesn't seem to have Google Play... so I can't download anything. It also isn't seen by HTC Sync so I can't run the RUU from there, but I did successfully extract the rom.zip file using some instruction on this forum from the stock ICS RUU .exe. However, installing that from twrp recovery fails as it cannot open the zip, and an attempt to use the "fastboot flash zip rom.zip" command fails saying it's not allowed. Integrity of zip fail is tested to be ok with an archiver program. The zip file extracts properly, and I can flash things like boot.img and recovery_signed.img to the phone, yet system.img cannot be flashed (data length too large error). Not sure what to try next.

Thread closed.

Bootloop 2013 Moto G Boost Mobile XT1031 8GB

Hey guys!
To start, I want to say what an amazing place XDA is and how much information and knowledge you can get from here and how awesome the moderators are. I don't think I could ever find another amazing and/or helpful community such as those found here! Thanks to all who have helped me out with my Android issues!
Now to my issue and I apologize ahead of time if there is another thread (or related thread) found in the forum.
As the title states, I have a 2013 Motorola Moto G XT1031 Boost Mobile device. I had upgraded it to Lollipop 5.0.2 or 5.1 when it came out (I can't remember which one it was) and I had then decided to root it. I can say that I believe I was successful in rooting the device because I was able to install Supersu and use RootChecker to verify the install. Everything was going okay until i decided to research and eventually install a custom recovery and attempt to install a custom ROM. Well, let's just say that the recovery install was a bust...
In doing my research for a custom recovery, I found that TWRP had a custom recovery for my phone and apparently for my firmware via TWRP's app on the Play Store. So, I searched for my device in their in-app search for a custom recovery, downloaded it and installed it from the app. Now, my gut told me that this probably wouldn't work and that I should probably be installing a custom recovery via CLI. Nope. I didn't do this. Instead, like I said, I installed a custom recovery from the app itself. That screwed things up for me. I have no idea if it was the install, but my phone began to act incredibly strange. When in the TWRP recovery, my screen had this line that would continuously scroll from top to bottom. It wasn't a completely solid line, but it was transparent, almost like an empty thermometer glass stick was going down the screen. It was weird and not normal. I figured the phone's software was partially broken. It only did this in the TWRP recovery. Nowhere else did this happen. It was slightly annoying.
Later on I decided to install a custom ROM. Again, I did the necessary research to find out if there were any ROMs available for my phone (using XDA of course and others) and found that there were a few out there. So, I downloaded one (wish I could remember which one) and attempted to install it...keyword there. After attempting the install, my phone would not boot. Like at all. Dead. So back to the drawing board I went to try and reverse the damage. Using XDA (ironically) and a plethora of other sites, I tried to resurrect my phone and bring it back to life. After countless hours of trying and trying and trying and more and more research, I just gave up. The phone is dead. Great. $170 spent on a phone to break it a year later.
It's been roughly 4-5 months since I have attempted to redo the process and after another minor attempt, somehow I was able to remove the root completely, including the custom recovery and ROM. I don't know what the heck I did, but it worked....sort of. The phone is now stuck in a bootloop on the logo and sometimes the "bootloader has been unlocked" screen when try and factory reset the phone from the default recovery. When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set and to have this and that. I have this and that installed on my PC, but obviously cannot enable USB-debugging which is needed for ADB and fastboot to recognize my device.
So, my question for anyone who would like to help me out is this: what are my options? Is the phone recoverable? Is there any way I can get ADB/fastboot to see my device and finally install the stock firmware on the phone? I have the proper drivers installed and ADB/fastboot are on my PC. Any help would be amazing, even if you have to tell me to junk it.

blckdragn22 said:
When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set
Click to expand...
Click to collapse
This is incorrect, where did you read that? To reinstall the stock firmware using fastboot, you must be able to boot to the bootloader menu only.

I heard this from a few websites actually, although I could never find a situational fix for my phone. I am trying to restore back to Lollipop without a custom recovery, because within the past hour I found out TWRP was never fully removed when I tried booting into recovery from the AP Fastboot menu when doing to power+vol down option. The TWRP logo shows for about 10 seconds and then the phone tries booting normally, showing the unlocked bootloader warning.
So, yes I can boot into the bootloader menu all day long with no problems. It's just an selection I make doesn't get me anywhere. My question I guess now is: how do I go about reinstalling stock firmware via the bootloader menu. I have Minimal ADB and Fastboot installed on my PC. If I need the full ADB, I can download that. And of course I'd need the firmware, too.

You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795

_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
This thread had the firmware I was looking for thank you. I believe I have the flashing stock firmware process down, I hope. I'l refer to the guide if I need help. Thank you so much!

_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
I am trying to follow the steps listed here http://forum.xda-developers.com/showthread.php?t=2542219&page=35 and for some reason I cannot run any of the commands pertaining to the sparsechunks. This is what I get:
Is there anything you could tell me about that?
Edit: I was able to figure what the issue was when trying to write the sparsechunks. I had to insert a "." after 'sparsechunk' because that is how the file is named in the folder. However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?

blckdragn22 said:
However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
Click to expand...
Click to collapse
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).

_that said:
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
Click to expand...
Click to collapse
I will try that. There was a ...sparsechunks.0 as well apart from sparsechunks.1, sparsechunks.2 and sparsechunks.3. Shall I include that, too?
And adding the screenshot was an amateur mistake. My bad.

@_that this worked like a charm. Phone is 100% working ans usable now. Incredibly helpful. Thank you so much!

Database Info

welcome