Related
I think I semi-bricked my xoom.
I installed the new VTL-Launcher posted here http://www.xda-developers.com/android/tablet-oriented-launcher-vtl-launcher-now-in-beta/
and upon reboot, the xoom just stays looping the honeycomb boot animation.
My xoom was not rooted, and completely stock before this.
I tried to recover doing a hard reset as detailed here: https://motorola-global-portal.cust...rola-xoom---master-reset-/-factory-data-reset
but this also does not work. The option of recovery never presents itself.
I can still access the device with fastboot, but thats it really... I do not know what to do with it.
Please help, as I do not really know what to do beyond this.
If you can still access the fastboot you should be able to reflash the stock image.
3G/4G - http://forum.xda-developers.com/showthread.php?t=980803
WiFi - http://forum.xda-developers.com/showthread.php?t=1017398
Wow, really?
I've just downloaded this, and debating if I should or should not install... I guess I wont.
I hope you can get your issues resolve.
Have a look here
http://forum.xda-developers.com/showthread.php?t=973355
happened to me too with vtlauncher... i reflashed all my partitions and relocked my boot loader, then used the one click gui to root with the latest tiamat kernel
Hi, i`ve owned an infuse for a couple months now and i`m loving it. I bought it off somebody and it came pre-rooted. Superuser was working great, i was running rooted apps and everything was pretty awesome. However, i`ve just recently wanted to try something new. Such as flashing a new rom. I downloaded the zeus rom (i also have others), went into rom manager and tried to install. That didn`t work. So i tried to manually boot into clockworkmod recovery and install. That didn`t work. I think the main problem is how do i get into clockworkrecovery? Whenever i boot into it i lack very many options that i keep seeing from others. Everytime i try to boot into it it says
Copying media files
Successfully copied meida files
Manual Mode
Appling Multi-CSC
Installing Multi-CSC
can't access to system/csc/RWC/system/
Successfully applied multi-csc
and the options are
Android system recovery <3e>
Samsung Recovery Utils for BML
Enter: Power Key, Select: vol up/ vol down
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
Everytime i try to apply update from sdcard it says:
Failed to verify whole-file signature
Installation aborted.
I can't remember all of it but you get the just of the idea
I can't seem to figure this out and i dont think this is clockwordrecovery. I've tried various methods of rebooting using the CWM app, Rom Manager app, and the button pressing.
All i want to do is flash a new rom! Can anyone help?
P.S. It isn't a typo when i put "Successfully copied meida files", they actually spelt it meida.
Xparks said:
Hi, i`ve owned an infuse for a couple months now and i`m loving it. I bought it off somebody and it came pre-rooted. Superuser was working great, i was running rooted apps and everything was pretty awesome. However, i`ve just recently wanted to try something new. Such as flashing a new rom. I downloaded the zeus rom (i also have others), went into rom manager and tried to install. That didn`t work. So i tried to manually boot into clockworkmod recovery and install. That didn`t work. I think the main problem is how do i get into clockworkrecovery? Whenever i boot into it i lack very many options that i keep seeing from others. Everytime i try to boot into it it says
Copying media files
Successfully copied meida files
Manual Mode
Appling Multi-CSC
Installing Multi-CSC
can't access to system/csc/RWC/system/
Successfully applied multi-csc
and the options are
Android system recovery <3e>
Samsung Recovery Utils for BML
Enter: Power Key, Select: vol up/ vol down
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
Everytime i try to apply update from sdcard it says:
Failed to verify whole-file signature
Installation aborted.
I can't remember all of it but you get the just of the idea
I can't seem to figure this out and i dont think this is clockwordrecovery. I've tried various methods of rebooting using the CWM app, Rom Manager app, and the button pressing.
All i want to do is flash a new rom! Can anyone help?
P.S. It isn't a typo when i put "Successfully copied meida files", they actually spelt it meida.
Click to expand...
Click to collapse
You don't have cwm recovery yet.
Don't use ROM manager.
I made a thread on "how to." It's a collection of some things I've learned.
Start there.
The link is on my signature line
So where should i start? At the flashing part?
Xparks said:
So where should i start? At the flashing part?
Click to expand...
Click to collapse
Start here:
[REF] [HOW TO] [ROM Installation] Where to start?
Xparks said:
So where should i start? At the flashing part?
Click to expand...
Click to collapse
yes..follow gtg's CWM instruction set
So. I already started with the odin UCKD5 one. http://forum.xda-developers.com/showthread.php?t=1092021
and i already started into download mode. However, it now says downloading. and my computer was like "installing new hardware" then "could not install new hardware" and now my phone is stuck in the downloading screen that says do not turn off target. Odin has yet to pick up my phone....what now?
if you have root you can flash a cwm enabled kernel with sgs kernel flasher.
if you have froyo use the defuse or community kernel. or use gtgs thread for cwm without flashing a kernel.
if you have gingerbread then you will need to flash one of the custom kernels such as entropy dd, hellraiser, or infusion. gtgs cwm thread will not work on gingerbread.
My phone is rooted and running on gingerbread. But um. i have a more pressing concern at the moment....this downloading screen is freaking me out...
okay well i can't seem to figure any of this stuff out. any noone has replied so i just reset my phone so i can actually use it.
Some more information for those who can help is that the firmware is 2.3.3
Baseband version is I997RUXKG3
Kernel version
2.6.35.7-I997RUXKG3-CL366622
Build number
Gingerbread.uxkg3
Xparks said:
okay well i can't seem to figure any of this stuff out. any noone has replied so i just reset my phone so i can actually use it.
Some more information for those who can help is that the firmware is 2.3.3
Baseband version is I997RUXKG3
Kernel version
2.6.35.7-I997RUXKG3-CL366622
Build number
Gingerbread.uxkg3
Click to expand...
Click to collapse
that's Rogers firmware. use kernel flasher (easiest) and flash one of the popular gingerbread kernels. entropy dd is popular. once the kernel is on there You will have red cwm. that will allow you to flash whatever.
if you flash a rom it will include a kernel so don't worry about the minor incompatibilities that exist with att based roms.
So i'm currently on this thread
http://forum.xda-developers.com/showthread.php?t=1212795
with this in the other tab
http://forum.xda-developers.com/showthread.php?t=1289460
I'm not sure which kernel to download. But i'll try flashing a couple anyway
also i tried using heimdall/odin or whatever. It wouldn't pick up my phone in download mode. and thus couldn't install drivers.
well. I tried flashing one of the kernels. specifically
DD_02162012_A.zip - [Click for QR Code] (5.16 MB, 118 views)
So i flashed it using SGS kernel flasher. it said flashing....rebooting. And now it's stuck at the rogers logo. I have no clue what to do and i think it might be bricked. So if i could get someones help, perhaps step-by-step as i obviously cannot do this following the other instructions.
Xparks said:
well. I tried flashing one of the kernels. specifically
DD_02162012_A.zip - [Click for QR Code] (5.16 MB, 118 views)
So i flashed it using SGS kernel flasher. it said flashing....rebooting. And now it's stuck at the rogers logo. I have no clue what to do and i think it might be bricked. So if i could get someones help, perhaps step-by-step as i obviously cannot do this following the other instructions.
Click to expand...
Click to collapse
You are stuck in bootloop. Not bricked or even close to it. Read infused rom and flash it. If you cannot figure that out you should not be flashing. It's dead simple. Promise. Search it. It's in the dev thread. Called infused by gtg
Sent from my SAMSUNG-SGH-I997 using Tapatalk
thanks for the help so far. but i went here. http://forum.xda-developers.com/showthread.php?t=1116251
and the link no longer works. so what now. I can't get the files and therefore can't put anything into odin.
sigh. so i downloaded the files from someone who uploaded it again. Did everything. Succesful. only to have it be stuck in bootloop and samsung screen. Did what it said. pulled battery, replace, vol buttons and power key until recovery shows up. That doesn't happen. Instead i notice that instead of a rogers screen it says at&t and then goes to samsung screen. and then restarts again by going back to at&t. If i let go of the buttons it goes back to begin stuck at the samsung one. This has made so many problems for me.... just by trying to get clockworkmod. what do i do now?
Xparks said:
thanks for the help so far. but i went here. http://forum.xda-developers.com/showthread.php?t=1116251
and the link no longer works. so what now. I can't get the files and therefore can't put anything into odin.
Click to expand...
Click to collapse
Xparks,
You really should read up a bit. If you looked toward the end of that thread,
you will see that the file has been uploaded by another user to another site:
http://forum.xda-developers.com/showthread.php?t=1116251&page=40
i got that one already. i've passed that step. I'm now stuck in bootloop with at&t and samsung logo. Bootloop was supposed to be a rare occurence...and the instructions to work around it aren't working right now. I can't access recovery mode. Or anything for that matter.
Xparks said:
i got that one already. i've passed that step. I'm now stuck in bootloop with at&t and samsung logo. Bootloop was supposed to be a rare occurence...and the instructions to work around it aren't working right now. I can't access recovery mode. Or anything for that matter.
Click to expand...
Click to collapse
Download the drivers for the phone on the computer. If it does not work then, try heimdale. If you can not do this, then just ask me for the jtag guy, ill give you the link to the website. Mobiletechvideos uses jtag to recover the phone (taking it apart, hooking it up with a ton of wires lol). Keeps personal data, just recovers rom, or you can pay a little extra for him just to install whatever rom. It worked for me, you may have a broken usb controller like me all of a sudden.
I have kies but when i start it up it says please connect your mobile phone. And it doesn't pick up my phone. It probably shouldn't seeing how my phone is stuck. But i went to menu in kies and pressed install driver. But i'm not sure how to download my exact driver if kies can't even pick up my phone. But i ran the "zazig" program. and i'm installing the drivers from there. And i'm going to attempt to reflash using that since Odin didnt work before. The link is this http://forum.xda-developers.com/showthread.php?t=1331381
And it did that. But i don't what to do. I've been on xda reading forums all day and the only thread i can see relevent to mine is someone advising them to bring it back under warranty. Mines rooted. no warranty for me. I hope if it ever works again i can use it on rogers still because it says AT&T.....and i'm afraid to try and unlock it. because we know the last time i tried to do something.....
Odin can still detect it and i tried reflashing the unbrick stuff. No dice.
My friend gave me his bricked Xoom, which I accepted as a challenge, because I've been rooting and flashing my phones for years, but after 10+ hours of searching in the last couple weeks, I have been unable to locate coherent information on how to un-brick a Xoom that has had its internal storage wiped. My friend was trying to do a thorough wipe, and he succeeded in that, if nothing else.
My first obstacle was finding a driver, because Motorola Device Manager wants nothing to do with the Xoom, and whenever I finally found a link to a driver, it was at developer.motorola.com, and there apparently is no such domain, because every link takes me straight to motorola.com/us/home, where all that's waiting for me is the bloody Moto Device Manager.
The only post I found that seemed like it was aiming at where I want to get is at http://forum.xda-developers.com/showthread.php?t=2317986, but I ran into problems that weren't foreseen by the author, and I haven't been able to find anything pertinent that doesn't direct me to developer.motorola.com again.
The Xoom has TWRP v.2.6.3.0(runandhide05 edition) for a recovery; and I'm aware that there is a 3.3 version, but I'm nervous about flashing a recovery update when there is no OS on the tablet. It was running EOS 4.2.2 I think, before the bricking.
According to the guide I found, I put TWRP into adb sideload and was able to get my PC to communicate by installing a universal adb driver from https://github.com/koush/UniversalAdbDriver, so in my system Device Manager, the Xoom is listed as a GOOGLE GALAXY NEXUS ADB INTERFACE.
When TWRP is in adb sideload, I can interface with the Xoom via cmd.exe, but when I try to push a ROM, I keep getting an error on TWRP:
Code:
file_getprop:failed to stat "/system/build.prop" no such file or directory
...whatever that means. Another thing that kind of worries me is that when I type adb devices, it shows my device as 1234567890ABCDEF, which doesn't seem right.
I have yet to try fastboot, because I don't know what .img files I need to flash, and I don't think blind flashing is going to make things any better.
I think I have all the pieces, SDK and JDK are installed and updated, and I have the stock rom (HWI69.zip). I reckon if I can get the stock 3.x OS running, I'll have a jumping-off point, and be good to go; the process from there is well-documented.
Can anyone give me a nudge in the right direction, please?
~Fake
Status 7 errors
Those are usually caused by either a not-so-compatible recovery image. Some TWRP versions have issues with certain ROMs. I had this happen to me with my Asus TF300, ended up trying a few different TWRP versions before I found one that worked right.
The other cause is an invalid ROM image, if you open the ROM.zip file on your PC, does it look ok, did you check its MD5sum???
Were you able to wipe the Xoom from TWRP without error???
-Mike
When I got it, it had been wiped completely, so I presume that twrp wiped okay.
Not sure about the MD5sum, just that twrp didn't find one during the adb installation. Do you think flashing cwm might help?.
I got it worked out, opened up the HWI69.zip stock image and fastboot flashed the individual .img files, and it booted right up. Thanks!
**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
OK, been searching for a week, obsessively, to find a fix for this. No luck.
I tried flashing the aosp ROM from official miui v5 through twrp and have been left with this.
1. Bootloader locked, Tamper bit engaged, and running stock recovery with a signature that cannot verify anything. (I mean anything, cannot even reflash the same ROM, factory signed, nothing)
2. What's this? It starts up? It can't be bricked? Oh wait why did it just reboot upon network connection? Right! Persistent has been destroyed/corrupted! Fun stuff.
3. SDD called internal? Sdd gone? Yes, yes it is. Everything has changed which is why I can't DD/ the persistent!!
4. Tried every toolkit (except the mac os one which resets tamper) and been through every internet page ever. Before i embarked upon this mission to unbrick the unbrickable id never heard of a data dump, persistant, or .tar. Now I never want to hear of them again. I have tried everything except the backdoor adb route because the Qualcomm drivers won't install on my 64bit win8.1.
If anyone, anywhere, knows how I can put back to stock, aosp, caulkins, anything, have a heart, help a man!
jpilch said:
OK, been searching for a week, obsessively, to find a fix for this. No luck.
I tried flashing the aosp ROM from official miui v5 through twrp and have been left with this.
1. Bootloader locked, Tamper bit engaged, and running stock recovery with a signature that cannot verify anything. (I mean anything, cannot even reflash the same ROM, factory signed, nothing)
2. What's this? It starts up? It can't be bricked? Oh wait why did it just reboot upon network connection? Right! Persistent has been destroyed/corrupted! Fun stuff.
3. SDD called internal? Sdd gone? Yes, yes it is. Everything has changed which is why I can't DD/ the persistent!!
4. Tried every toolkit (except the mac os one which resets tamper) and been through every internet page ever. Before i embarked upon this mission to unbrick the unbrickable id never heard of a data dump, persistant, or .tar. Now I never want to hear of them again. I have tried everything except the backdoor adb route because the Qualcomm drivers won't install on my 64bit win8.1.
If anyone, anywhere, knows how I can put back to stock, aosp, caulkins, anything, have a heart, help a man!
Click to expand...
Click to collapse
This honestly is very confusing. I had to read what you wrote a couple of times to try and comprehend what the problem is.
Have you tried using fastboot without any toolkit? I ask because you haven't mentioned it anywhere. Persist can be fixed by fastbooting back to pure stock, and Mike's fix on the OnePlus forums, and/or updating to 44S.
Can you tell us what errors you get when you try to reflash the same rom? What recovery are you running? Which rom were you trying to reflash?
I have to agree with @nicholaschum, your post is very vague and confusing in its present form, and I'm a pretty seasoned troubleshooter on XDA.
What's needed? Less emotion, less comic type speech, less sarcasm, more specifics and facts.
Transmitted via Bacon
1328
If I try to sideload, it says either signature failed or whole signature failed.
Anything i push does not get pushed and I have tried multiple drivers from the galaxy ones that come in the reflash.zip from the one plus tech support to the Google ones I am using now.
If I try to fastboot through toolkit it says failed, not unlocked can't flash/erase. If I fastboot through cmd it says error: closed. I do all my checks, and it shows up in fastboot and adb but won't let me send anything.
The phone boots up for about 15 in is before restarting, the only way to get files on are to drop them in explorer within these 15secs, to internal storage, which used to be my sdcard.
I have tried flashing/side loading multiple ROMs from miui, 44s, 33r all signed to caulkins and mahdi. Nothing has worked (and the aosp OTA).
I cannot unlock bootloader, cannot reset tamper, cannot load GUI for more than 15 secs, and cannot root (although kermal already says it is, I suspect su needs to be in place).
I have also tried fastboot -c boot recovery.IMG (and recovery recovery.IMG) but no luck still. Is there a PC version of the Mac toolbox that can reset tamper? At least then I could unlock bootloader and install twrp and flash.
Thanks for the help
Josh
Still sounds like a driver issue imo.
First uninstall ALL previous drivers you have tried from device manager.
Installing one driver after another often causes conflicts.
Then download the official Android SDK and install Google USB driver. Google for instructions if needed but everything is pretty much straight forward.
This driver has the biggest chance of success.
After that you're off to start fixing your phone using fastboot and adb.
OK have done this on both a 32 and 64 bit win 8.1 systems. Exact same result. Error: closed or not unlocked no flash/erase for everything fastboot, and e: can't verify signature/whole-signature e: verification failed. I tried adb explorer through adb sideload and error:closed again. Does this mean the adb protocol for accepting is closed? No idea.
I have a feeling it is something on the phone rather than computer now? Done everything on a 32 bit now and everything is the same and had no drivers previously. And just to be clear when I say stock recovery, I don't mean cwm I mean
android system recovery 3e
KTU84P. 1.2.0 dev-keys
jpilch said:
OK have done this on both a 32 and 64 bit win 8.1 systems. Exact same result. Error: closed or not unlocked no flash/erase for everything fastboot, and e: can't verify signature/whole-signature e: verification failed. I tried adb explorer through adb sideload and error:closed again. Does this mean the adb protocol for accepting is closed? No idea.
I have a feeling it is something on the phone rather than computer now? Done everything on a 32 bit now and everything is the same and had no drivers previously. And just to be clear when I say stock recovery, I don't mean cwm I mean
android system recovery 3e
KTU84P. 1.2.0 dev-keys
Click to expand...
Click to collapse
For the fastboot bit, I've seen this happen a lot. Many people used this to solve their issue: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912