[Q] How Do I Downgrade TF101 from 8.6.5.21? - Eee Pad Transformer Q&A, Help & Troubleshooting

I have spent hours searching and reading, but I can't find an up-to-date answer.
I have a B70 TF101 that is at 8.6.5.21. I rooted using nachoroot. I want to put on cyanogenmod 9 RC. It does work using ROM Manager. Seems that in spite of telling it to install clockworkmod, it doesn't. I can't get it into APX mode. So I guess I'm ready to try to downgrade it to 8.6.5.19. I find loads of references and links to multiupload for that file, but it no longer is available.
How can I downgrade to 8.6.5.19? I just want to put on Cyanogenmod.
Please help.

Hi Thornthree,
try http://forum.xda-developers.com/showthread.php?p=25385687 step 3.
in this post you find places for the blob file and what to do (step 3)
I think you need the 8.6.6.19 (is for tf101/g, but also for the tf101
But is your TF now able to go into apx mode yes or no?
maybe start with this:
http://forum.xda-developers.com/showthread.php?t=1688012
goodluck......

There's not a need to downgrade.
You could also use PERI.
http://forum.xda-developers.com/showthread.php?p=26737790

Yep, several one-click rooting methods out for the latest versions.
My PERI tool as mentioned above is one of these, just plug-in, run and root.

I could never get into APX mode. I followed all of the instructions to get there that I could find but none of them worked. The power and up volume keys did nothing on my TF101. I finally got power and volume down to get me into clockworkmod, but then it couldn't find the zip file. When I finally got the zip file visible, then chose reboot system now, it just kept looping into clockworkmod. Somehow, in the end, after all kinds of crazy attempts of key combinations, it's somehow worked.
I had to end up going back to factory reset, then all kinds of acrobatics to place a zip file in the right place, then do another factory reset and wipe, which somehow ended up in my having cyanogenmod working. I don't know if I could reproduce the process. Also, it's very frustrating that none of the tutorials did anything to work on my tablet. I'm just thankful that it's where I want it right now. I don't know if I need to install OTA root keeper or not, and I don't know what I'll do if I ever need to upgrade to a different ROM or an updated cyanogenmod.
Thanks for all the replies. I'll keep them in mind for the future.
Sent from my DROID2 using xda app-developers app

Related

Q/A for someone who has some time...

Heres the dealio- I have a Charge I want to root and put a custom rom on. I have done this before, with my Inc and my Archos tablet so I'm not a complete idiot.
I did use Odin and thought everything went fine, followed directions to install a zip from the card but the recovery menu never gave me that option. I am unable to get to the sdcard from the recovery menu. I got the option to install the update.zip but thats all. (I followed one of the many thousand "how to root your charge" threads)
Can someone tell me what happened?
Also, the first time I tried to do it, I realized I didn't have the right file, so I pulled the plug on my Charge while in Odin, also because it kept looping. Now Windows XP on that machine won't recognize the phone anymore.
Anyone have any ideas on that?
One more, I read that you need to downgrade the EE4 in order to root? Is that why recovery didn't work the first time, because I have the EE4? (I did see that info AFTER I installed the recovery)
I've been over these threads hundreds of times but I just don't have alot of time and there is alot of redundant information that makes it hard to get anywhere so I'd appreciate if someone could help me out.
willowave said:
Heres the dealio- I have a Charge I want to root and put a custom rom on. I have done this before, with my Inc and my Archos tablet so I'm not a complete idiot.
I did use Odin and thought everything went fine, followed directions to install a zip from the card but the recovery menu never gave me that option. I am unable to get to the sdcard from the recovery menu. I got the option to install the update.zip but thats all. (I followed one of the many thousand "how to root your charge" threads)
Can someone tell me what happened?
Also, the first time I tried to do it, I realized I didn't have the right file, so I pulled the plug on my Charge while in Odin, also because it kept looping. Now Windows XP on that machine won't recognize the phone anymore.
Anyone have any ideas on that?
One more, I read that you need to downgrade the EE4 in order to root? Is that why recovery didn't work the first time, because I have the EE4? (I did see that info AFTER I installed the recovery)
I've been over these threads hundreds of times but I just don't have alot of time and there is alot of redundant information that makes it hard to get anywhere so I'd appreciate if someone could help me out.
Click to expand...
Click to collapse
1) don't choose the option to select 'update.zip', that option doesn't work on the Charge... also it sounds like you were in the stock recover, you do flashing/wiping in ClockWorkMod recovery (CWM)
2) NEVER pull the cord out during an Odin flash unless its been like 30+ minutes and it looks like it froze or nothings happening, this is probably why your phone can't be recognized now (that is a good way to brick your phone and it sounds like you've got one)... now you will need to get the phone into download mode (if it still will) and flash the stock EE4 rom with the Charge PIT file (can't link from phone but these are in the How To Fix Your Phone sticky in Development) and start over
3) I don't quite understand your last question but no you don't need to be on EE4 to root and you can put CWM on any rom with Odin, EE4 at this point is mostly a 'return to stock' rom
blazing through on my 4G Droid Charge
The phone seems to be working fine, but maybe that is why I was in stock recovery mode, because it looks fine, but won't download now. Because I just tried to install a rom and I get an error. I had tried to install CWM, and thought thats what I was going to when I ended up in the stock recovery. I will try the Charge PIT file that you mentioned and see if that fixes anything, and then start over from there. If not I may be returning the phone since it's fairly new.
Thanks for your time
willowave said:
The phone seems to be working fine, but maybe that is why I was in stock recovery mode, because it looks fine, but won't download now. Because I just tried to install a rom and I get an error. I had tried to install CWM, and thought thats what I was going to when I ended up in the stock recovery. I will try the Charge PIT file that you mentioned and see if that fixes anything, and then start over from there. If not I may be returning the phone since it's fairly new.
Thanks for your time
Click to expand...
Click to collapse
when using the pit file be sure to have the repartition box checked in Odin
blazing through on my 4G Droid Charge
I don't have a PIT option on my Odin, or a repartition. It's version 4.13...is there a better version of Odin to work with and stick with? I'm working with 3 different computers here, so I know I have an Odin at home that was working but this one doesn't seem to connect. It's easier to troubleshoot whats going wrong if the proggies I'm using are at least a consistent version number. I DO know I had PIT on the Odin at home but version I'm using (at work) doesn't have it.
willowave said:
I don't have a PIT option on my Odin, or a repartition. It's version 4.13...is there a better version of Odin to work with and stick with? I'm working with 3 different computers here, so I know I have an Odin at home that was working but this one doesn't seem to connect. It's easier to troubleshoot whats going wrong if the proggies I'm using are at least a consistent version number. I DO know I had PIT on the Odin at home but version I'm using (at work) doesn't have it.
Click to expand...
Click to collapse
You need Odin3 1.82 (not just plain Odin). You can get it from http://forum.xda-developers.com/showthread.php?t=1160580
Thanks for the help guys. I got everything back to normal. Drivers and sdcard working properly now. Rooted. Now I just need to get Clockwork back on, and a different rom. Anyone have any fav roms so far? Would love some input on what everyone sees with the different radio builds.
If anyone can answer this, can we get mobile hotspot working on this? Thats a big part of why I need to root and rom this thing.
willowave said:
Thanks for the help guys. I got everything back to normal. Drivers and sdcard working properly now. Rooted. Now I just need to get Clockwork back on, and a different rom. Anyone have any fav roms so far? Would love some input on what everyone sees with the different radio builds.
If anyone can answer this, can we get mobile hotspot working on this? Thats a big part of why I need to root and rom this thing.
Click to expand...
Click to collapse
Everyone will have an opinion on ROM's and radios. My setup is in my sig. As for hotspot, android-wifi-tether works fine on all rooted roms. I've found 3.0pre12 to work the best. 3.1beta6 requires a reboot to get wifi working normally after tethering, but I don't have that issue on 3.0pre12. Be sure to immediately reboot after you install it, and then go in and set your phone type to Samsung Fascinate, and you should be good to go.

[Q] big problem with sidekick

bought sidekick sght839 from friend and it worked fine b4 doing reset. now, when it starts, the tutorial comes up on home screen and can`t press arrow to proceed to next page. firmware 2.2.1-kernal 2.6.32.9-build froyo uvkj2. the wireless works and connects to internet fine. can`t use phone as 456 keys dont work and worked b4. can change settings OK. have rooted it. still doesnt want to work as b4. am new here so if someone could let me know if they have any ideas, I would appreciate it. am also new to android phones. I cant find heimdall file to download. Know how to set phone to download and use Odin but cant find proper files online.
Use the search bar on XDA to search for the kj2 stock Odin files, follow the directions given closely, download them, make sure you have the correct drivers so that Odin recognizes your phone, then boot into download mode using the method found in the forums, just do a quick search for download mode. You should have everything operational after download from Odin is finished, hope this helps
Sent from my SGH-T839 using XDA App
trouble installing odin
I have tried numerous times to install Odin but all I get is unregistered device...that is as far as it goes. Dont know how to get around that. 456 keys also work then dont work otherwise the phone works fine as far as internet and making calls goes. Crazy device!
Try this:
http://forum.xda-developers.com/showthread.php?t=1350060&highlight=heimdall
I soft-bricked my phone and this was the only method that worked.
if you havent reflashed your firmware yet, i have a suggestion. install clockworkmod recovery. there is a thread in the sk4g development section of this website. the title is something like cwm for the sk4g. enjoy! so look for that and follow the instructions in the first post of that thread. make sure you grab the update.zip file from that thread and do not flash cwm through rom manager. trust me on this. after you have followed the instructions in that thread, boot into cwm (boot into stock recovery and select reinstall packages. you should then boot into cwm recovery), select advanced, and then select fix permissions. when it finishes, it will say done. reboot your device and see if any of the problems have been fixed. i did this and it stopped my phone from randomly rebooting every 15 to 30 minutes. it might fix the problems on your device. if not, i would move to the next step, reflashing the firmware. flash the kj2 build and then learn how to remove bloatware. kj2 is less buggy to start with. still buggy, but less buggy than KD1, KG2, or the other version (KI2?). if you reflash firmware, you will need to re-root in order to remove bloatware. removing bloatware is key for optimal performance with the stock firmware. you can also flash a custom rom if you wish. most of the custom roms on this site have minimal bloatware, so if you wish to go that route, bloatware shouldnt be much of an issue. i personally am on the stock firmware and dont suggest flashing roms for someone so new to android. but if you feel confident enough, thats your decision. i also suggest booting into cwm and running fix permissions after removing bloatware. i theorize that removing system apps causes permissions errors similar to registry errors in windows.
some success with sk4g
don`t know how or why but I got frustrated with the phone and threw it in the trash on top of coffee grounds...changed my mind and pulled it out and cleaned it and charged it and...voila...it worked. banged it against the sink a couple times. weird! so, now I am trying to install custom rom and keep running into everification error when I try to flash. 456 buttons still dont work and cant take a video with it but it will probably work better if I can find a work-around for these errors I get. I am on a mission now and I cant give up. Hope someone can help me. I think there may be hope for this thing. Thanks for whatever help I can get.
i told you, install clockworkmod and fix permissions. it will probably fix the problems you are having. if you choose not to listen, thats. your choice. but my advice will probably help you without having to through the pain in the rear of reflashing the firmware. reflashing the firmware itself isnt really that difficult, but once you do it, your back to square one with your device. starting from scratch is the frustrating part. i bricked my phone and had to reflash, and it took me a couple weeks to get the phone where i needed it again. im staying on the stock firmware for this reason.
how does one fix permissions
OK OK dont yell. How do I fix permissions? Newbie on board here so I need a little more help than the rest. I dont necessarily want to do the rom thing myself. Thanks.
copy and paste this into your browser: forum.xda-developers.com/showthread.php?t=1124453 and follow the instructions in the first post. after you have followed those instructions, boot into recovery mode. the stock recovery will apear. scroll down and select reinstall packages. the clockworkmod recovery should boot up. the text in the screen will be orange. scroll down and select advanced. scroll down again and select fix permissions. when it finishes, it will say done. reboot your device and see if you have any of the issues you were having. i am not guaranteeing this will fix the issues, but i think it might. if it doesnt, my next suggestion will be reflashing the stock firmware. but try this and post back when finished and let me know if it works.
sk4g problem
didnt work. did exactly what you said and no go. any other suggestions. it works so well for some things like wifi and calling except 456 buttons on and off. it is funky indeed. thanks for the help also, cant take video or manage photo or use front camera as the left side button to choose options doesnt work either. seems like something is up with the rom. cant install anything from samsung or tmobile as it is an unregistered phone.
were you able to boot into clockworkmod recovery?
boot up
yes I did.
then you need to reflash your firmware. you need odin, you need the samsung vibrant drivers, and you need the firmware files. do a search on odin in the dev thread for this device and you should be able to find everything you need, including instructions.
Have tried that too
have the drivers, have odin and have tried that too. that didnt work as the phone is unregistered and not recognized. it is used and I cant register it.
on your phone, go to settings>about phone and scroll down to where it says baseband version. the last 3 characters under that will say either kd1, kg2, or kj2. if its not kj2, then i have a suggestion for you. but post back and lmk.
phone setting
it is kj2. now what? this is all confusing as it has been updated I believe by previous owner. thanks for your time. i am going to try the odin method again. i first did it on a 64bit puter with windows 7 so i can try it on my 32bit machine. have read that sometimes odin doesnt work well on 64bit. am willing to try anything. will let you know. thanks again. cant get the stock rom download anywhere. will just try flashing custom rom.
you cant odin a custom rom unless the dev makes an odin file, which they usually dont. you have to flash through clockworkmod. you can head over to the dev section and pick from many roms that are listed. follow the developers instructions for flashing very carefully or you will brick your device.
Thanks for advice.
I know I can`t odin a custom rom. I can`t seem to odin anything on this machine. I have cwm and have tried using it to flash a rom but I keep getting everification and such error msgs. Gonna let it sit for awhile and think about this. I have the update.zip file on sdcard but can`t seem to get that to install no matter what I do. Very puzzling deal. Thanks anyway for your help.
do you have android sdk installed on your computer? google it and install it, then try odin again.
got sdk
sdk installed and will try odin again...seems a little more complicated than the last time I tried...will google a bit more on this. Thanks.

[solved] Can't update.

First of all I feel bad for making a thread because I feel like the answer is out there and I just cant find it.
The unit is a TF101G and WW version B9O.
Basically I used this to return to stock http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
This worked fine but now i can't seem to update to stock ICS the tablet does not find any updates automatically (or going into settings and forcing a search)
and when manually downloading ICS from Asus both 9.2.2.4 and 9.2.2.6, neither work.
I was originally using CWM but with no luck there i tried using stock recovery current firmware version is 8.2.3.13
I cant seem to figure this out.
Do a factory reset then update thatll do it
Hit the thanks button if i helped
You need to be completely stock for the update to go, as in no CWM and sometimes it matters which SKU you are on. You can always NVFlash stock ICS if nothing else works
Nvflash does not work for tf101G
So ive got 3 files on my microsd card now after wipingdata as ROM CHIEF suggested the orifinal file name unchanged(yes its unzipped once) the same file called EP_UPDATE.zip and the same file again called UPDATE.zip still when i boot into stock recovery it shows a progress bar for a few seconds then goes to the android and '!' sign and no combination of vol up/down power on seem to activate any controls (like it does on my phone)
Edit: I'm now trying to root VIA PERI and it does not work i get "cannot open for write access is denied" i also tried using wolfs method manually (Im pretty sure PERI just automates wolf) to flash the ICS blob directly and get the same access denied. I guess the exploit isn't working ?
What fw are you on? You need to be on a ICS firmware, yes PERI automates wolf's exploit.
Thing O Doom said:
What fw are you on? You need to be on a ICS firmware, yes PERI automates wolf's exploit.
Click to expand...
Click to collapse
yeah I was on 8.2 something which i think was the problem. managed to get it to update by renaming the zip to EP101_SDUPDATE.zip. It didnt really help that i had 5 different people telling me to rename it to different things. I'm happy I got it to work in the end.
PERI saved me in the first place when i originally couldn't flash anything (CWM was from rom manager) so thanks for the nifty program.

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

Unbricking a softbricked TF101

Hi all, a few months ago i had a perfectly running rooted TF101 with stock asus firmware. It has CWM recovery v6.0.1.3 and i had the CWM app installed.
somewhere along the timeline i decided it was a good idea to backup the whole thing using the CWM app just in case anything funny happens. Now don't ask me how or why it went the way it did, but the CWM app seemingly performed its backup, there was a disclaimer warning somewhere about possibly losing root access, to which i think i said "yes", the device rebooted and my entire image was gone - only left with CWM recovery mode.
I have been trying to reflash it with stock recovery image, but the SD card won't mount. I am also unsure whether i still have root access or not.
in terms of connectivity, all i was able to get back was ADB access, which i was able to search xda and find threads such as these to try and fake an sdcard then reflash
https://forum.xda-developers.com/showthread.php?t=911228
I've tried katkiss image and stock image but everytime i get a status 7 error or an error 21
https://forum.xda-developers.com/nexus-6p/help/zip-file-signature-verification-error-t3561054
https://www.**********.com/fix-status-7-error-while-installing-ota-update-or-roms/
I'm not exactly an ADB crackhead and I'm not able to get past it so i've searched some more and found on xda again threads on using EasyFlasher, I've followed the instructions but can't get the APX drivers installed on windows 10.
https://forum.xda-developers.com/showthread.php?t=1688012
basically, at this stage i've read many articles, many posts, none have worked because links are outdated or instructions are outdated and mostly i'd rather stop trying all i am finding without really understanding before i brick this device for good out of ignorance.
sure it's old but it was functioning properly and was being used actively by my kids. if i can get it back to life, that'd be nice.
has someone experienced (and fixed) something similar or feel can contribute to unbricking my device?
Thanks guys.
I'm a noob myself, but I managed to get the APX driver installed on Win 10 (just now) by following the directions at how to geek dot com. I used "Option two: Use an Advanced Boot Option."
Good luck!

Categories

Resources