Related
I am way N00b at this but how do I remove this from my Atrix 2? It is eating up my battery and I can't open some of my apps, they force close. Is it possible to flash back to the point prior to this?
It was backed up before I started but know I cant find the back up. I just want to go back to the point when it was rooted. I used "MotoFail" to root and everything was going great and decided to try this, my bad, any ideas besides buying anoter phone?;-(
ozziedog said:
I am way N00b at this but how do I remove this from my Atrix 2? It is eating up my battery and I can't open some of my apps, they force close. Is it possible to flash back to the point prior to this?
It was backed up before I started but know I cant find the back up. I just want to go back to the point when it was rooted. I used "MotoFail" to root and everything was going great and decided to try this, my bad, any ideas besides buying anoter phone?;-(
Click to expand...
Click to collapse
you have one option, flash the fxz and reroot.
start over.
there is a great nOOb thread telling how to do it.
http://forum.xda-developers.com/showthread.php?t=1396650
ozziedog said:
I am way N00b at this but how do I remove this from my Atrix 2? It is eating up my battery and I can't open some of my apps, they force close. Is it possible to flash back to the point prior to this?
It was backed up before I started but know I cant find the back up. I just want to go back to the point when it was rooted. I used "MotoFail" to root and everything was going great and decided to try this, my bad, any ideas besides buying anoter phone?;-(
Click to expand...
Click to collapse
How did you back up?
If you used CWM (from the A2 Bootstrapper) just reboot into CWM, go to backup and restore, select restore, and select the backup that you made.
If you didn't use CWM or you can't find the backup then you will have to flash the fxz as said above. It will completely remove all of your apps and return you to stock 2.3.5. Make sure that you follow the directions about replacing files.
Thank you matt99017d I will check the link and cogeary I did the back up CWM I'll go that route first if that doesnt work, I'll go back to the beginning. Thank you again for the help
I could not find the backup in CWM so I flashed fxz following the instruction on the link you provided and the info. I'm back to 2.3.6 and it is rooted. Thats as far as I'm going for now, thanks for the help you all provided.
I see at /system/etc/init.d 2 files with sd-card optimization. 03sdtweak and 99override. Is there right or needed to delete one of them?
I highly suggest getting Titanium, for the cases where you don't have a back up, because I lost all my free apps and I don't even remember what all I had. I'm getting things back as I need them.
Douchewithaphone said:
I highly suggest getting Titanium, for the cases where you don't have a back up, because I lost all my free apps and I don't even remember what all I had. I'm getting things back as I need them.
Click to expand...
Click to collapse
https://market.android.com/mylibrary
^ shows everything you've installed from the Android Market. You should have records somewhere if you got things from the Amazon Appstore.
I haven't tried it myself but if you've made a backup in CWM you have the option to only restore apps/data.
Well I decided to give SuperCharged V5 with update 1, and when I disconnected form the charger this morning it was stuck in the boot animation. It has been stuck in that position for the last 30 minutes.
I connected it to PC and it doesnt show as being connected. I've done a search and can't find anything on how to fix it.
I did a battery pull, took SD card out to see if I could maybe transfer something from it to desktop, but everything that was on it is gone.
Don't know what happened.
Can someone point me in the right direction?? In the mean time I'll keep looking.
Ozzie Im in a similar situation. I"m in a bootloop as well (Supercharged Logo just keeps rolling on the screen). I can't get into the Android OS, and I also can't even get into Fastboot to flash back to stock. At this time it appears its bricked. I have been trying to fix this the past 12 hours.
Are you in the same situation??!
ej_424 said:
Ozzie Im in a similar situation. I"m in a bootloop as well (Supercharged Logo just keeps rolling on the screen). I can't get into the Android OS, and I also can't even get into Fastboot to flash back to stock. At this time it appears its bricked. I have been trying to fix this the past 12 hours.
Are you in the same situation??!
Click to expand...
Click to collapse
I am sorry to say, but if you can't get into fastboot it's probably bricked
so i installed V5 and update 2 and i am getting the force closes and my phone won't show up when i plug the usb into my computer
and i can't delete or edit files in my files and i can't open any websites or connect to airdroid on wifi, or use data so i can't get any files onto my phone
help...
flashing the stock fxz worked
Man...and I was gonna do this...flash the supercharged ROM. Nevermind.
after i flashed the 2.3.5 fxz like the bootstrapping thread instructed, i installed the ota update and rooted my phone again and then i tried the custom rom again just for fun
but this time i did v5 and then update 1. then instead of doing update 2, i flashed the image of the rom that's linked right under update 2 in the supercharged thread
it works flawlessly for me now
so i would just recommend that
Okay,
So, I was trying to downgrade to stock 2.3.5 using rsd lite so I could flash ICS. However, RSD gets stuck at 14/18 "flashing system.img" for like 45 minutes. I did replace the files needed to downgrade in the FXZ and all of that and followed the steps down to the period. PLEASE HELP ME!
When I unplug and pull battery and reboot, I get invalid CG version or something like that...
A month or two ago I had the same problem. In one of the new ics threads someone asked about a way they were worried about doing because it replaced the boot image and took off stock recovery. That way works. You can then fxz a second time to completely stock using regular methods and regaining stock recovery.
I'm at the park with my son but I found it with Google. Not gonna try from my phone. Good luck.
Sent from my MB865 using Tapatalk 2
same problem
I have a similiar issue, I'm downgrading from SCV6 to 2.3.5, downloaded FXZ, unzipped, replaced files from replace.zip and started flashing through RSD Lite. Followed all directions on NOOBS guide. Now I am stuck at 14/18 flash system "system.img" for an hour at the moment. Is this normal? If its not, what should I do? Disconnect, don't disconnect? Close program, don't close? Don't wanna mess things up even more
EDIT: Now here's the weird part, I had to stop the application cause I went to work, so I closed RSD, disconnected the phone and rebooted it and... the system loaded, and the phone is working... which is weird because the flashing got stuck at 14/18. Now I have a dilemna, wheter to try to flash 2.3.5 again or wait for some advice from you guys
EDIT2: Second Flash did the trick, took like 10 minutes
Hello everyone, I'm newly joining xda forums but have been a frequent guest since last month. I would like to request for someone's (unlocked, rooted) MB865 AT&T Atrix 2 OTA ICS nandroid backup please, which they are able to share. I don't need/mind any personal settings or apps, I just want to get back to the basic stock ICS.
I recently received my (unlocked, rooted) MB865 AT&T Atrix 2 this week and have been loving it so far. The problems start when I stupidly flashed a mod via CWM for the Razr HD Circles widget without making a prior nandroid backup. After that, it only got worse when I used Titanium Backup to try and remove the modded homescreen,apk, thinking it was all restorable in factory reset and everything. Seeking a way to return to my original ICS rom, I searched the forums and found an ICS rom by alteredlikeness - his StockyEd 404.
But realizing that it wasn't the correct/real ota I had before, I searched for all other ways of getting back and this is one of them. The RSD Lite FXZ method is giving me too many issues and abd/fastboot method is also an issue because my phone is usually not recognized in ap fastboot, no matter what Windows computer or usb port I use. I used both the drivers from Motorola's latest and Motohelper and they only work when the phone is on. I have both windows xp 64 bit and windows 8 64bit. Of there are any other drivers that definnitely work with ap fastboot mode, please share them. Thanks for everything in advance!
Aceofzeroz said:
Hello everyone, I'm newly joining xda forums but have been a frequent guest since last month. I would like to request for someone's (unlocked, rooted) MB865 AT&T Atrix 2 OTA ICS nandroid backup please, which they are able to share. I don't need/mind any personal settings or apps, I just want to get back to the basic stock ICS.
I recently received my (unlocked, rooted) MB865 AT&T Atrix 2 this week and have been loving it so far. The problems start when I stupidly flashed a mod via CWM for the Razr HD Circles widget without making a prior nandroid backup. After that, it only got worse when I used Titanium Backup to try and remove the modded homescreen,apk, thinking it was all restorable in factory reset and everything. Seeking a way to return to my original ICS rom, I searched the forums and found an ICS rom by alteredlikeness - his StockyEd 404.
But realizing that it wasn't the correct/real ota I had before, I searched for all other ways of getting back and this is one of them. The RSD Lite FXZ method is giving me too many issues and abd/fastboot method is also an issue because my phone is usually not recognized in ap fastboot, no matter what Windows computer or usb port I use. I used both the drivers from Motorola's latest and Motohelper and they only work when the phone is on. I have both windows xp 64 bit and windows 8 64bit. Of there are any other drivers that definnitely work with ap fastboot mode, please share them. Thanks for everything in advance!
Click to expand...
Click to collapse
I would recommend trying to get fastboot working; an FXZ is the best option. Uninstall all drivers you have installed, reboot, reinstall, then boot to fastboot mode and see if it is working. Windows 8 and xp could be the problem, my guess would be that most people until recently (including me) have been using 7. you can also do it manually from linux if you have that and it might work better.
I would also recommend just going to a custom ROM! it's much better. Try cm10.1, and if you get a black screen you might have to explore other options.
best of luck!
lkrasner said:
I would recommend trying to get fastboot working; an FXZ is the best option. Uninstall all drivers you have installed, reboot, reinstall, then boot to fastboot mode and see if it is working. Windows 8 and xp could be the problem, my guess would be that most people until recently (including me) have been using 7. you can also do it manually from linux if you have that and it might work better.
I would also recommend just going to a custom ROM! it's much better. Try cm10.1, and if you get a black screen you might have to explore other options.
best of luck!
Click to expand...
Click to collapse
Thanks for your suggestions, I should have mentioned that both windows were 64 bit which might be another cause of the problem. I'm gonna try and a dualboot vista 32 bit I have and see if that will make any difference in detecting the phone in fastboot mode. That's literally been the only thing so far that's been delaying any success with fxz or any other ap fastboot method. If all else doesn't work, then I'll keep the StockyEd until I want to mess around with one of the custom roms.
Back to normal!!!
Hey guys, just wanted to make an update on this issue that I managed to regain all my phone's original ics rom settings! Turns out altered's StockyEd was indeed the official OTA all this time after chatting with him about the matter. There were actually modifications on my phone when I got it (1% Battery mod, etc.) which made me believe it wasn't the same rom.:silly: Well, I've learned a lot this week the hard way and now I made sure to use BMM to make backups everytime I decide to mess with something, lol. Thanks again for the assistance and I look forward to more fun with this forum.
My Atrix 2 is currently having some serious issues. Last night I rooted it. I changed the boot animation to what was supposed to be a human eye turned droid eye or something. When I rooted it and attempted to install Safestrap it didn't install correctly. As I am inexperienced with rooting android phones, I didn't think it'd hurt. I don't know if it did. When I rebooted to see the animation it just said android in silver letters with light flashing across it and it never got past that. I did several hard resets to see if that would fix it, after trying multiple battery pulls of course, and nothing. The phone is now dead and won't charge, when I plug it in it just shows the Motorola logo and doesn't do anything, but if I unplug it the logo doesn't go away. Help, please!
CreativeSin said:
My Atrix 2 is currently having some serious issues. Last night I rooted it. I changed the boot animation to what was supposed to be a human eye turned droid eye or something. When I rooted it and attempted to install Safestrap it didn't install correctly. As I am inexperienced with rooting android phones, I didn't think it'd hurt. I don't know if it did. When I rebooted to see the animation it just said android in silver letters with light flashing across it and it never got past that. I did several hard resets to see if that would fix it, after trying multiple battery pulls of course, and nothing. The phone is now dead and won't charge, when I plug it in it just shows the Motorola logo and doesn't do anything, but if I unplug it the logo doesn't go away. Help, please!
Click to expand...
Click to collapse
Phew, that was close. Hello and welcome to the help section of the A2 forum, for starters the trouble you're facing right now is called soft bricking. It's a very common problem, but is usually solved by flashing the correct ICS sbf for your region.
So firstly, is your phone branded AT&T or is it from another region? Please specify which. Next you need to recharge your battery externally either by an external battery charger or the Mcgyver method. (search the forum for more details).
After you've charged your battery up enough, put it back in your phone and put your phone into fastboot mode by holding the volume down button + power button and make sure it says 'Battery OK'.
After making it this far, you'll need RSD lite order to flash/install the sbf files. If everything goes fine without failure, then your phone will be back to stock and you've saved it! Here's a thread that has content that should guide you with further details: http://forum.xda-developers.com/showthread.php?t=2245825 Good luck!
Sent from the Ace's MB865 using xda-developers app
Aceofzeroz said:
Phew, that was close. Hello and welcome to the help section of the A2 forum, for starters the trouble you're facing right now is called soft bricking. It's a very common problem, but is usually solved by flashing the correct ICS sbf for your region.
So firstly, is your phone branded AT&T or is it from another region? Please specify which. Next you need to recharge your battery externally either by an external battery charger or the Mcgyver method. (search the forum for more details).
After you've charged your battery up enough, put it back in your phone and put your phone into fastboot mode by holding the volume down button + power button and make sure it says 'Battery OK'.
After making it this far, you'll need RSD lite order to flash/install the sbf files. If everything goes fine without failure, then your phone will be back to stock and you've saved it! Here's a thread that has content that should guide you with further details: http://forum.xda-developers.com/showthread.php?t=2245825 Good luck!
Sent from the Ace's MB865 using xda-developers app
Click to expand...
Click to collapse
As RSDLite was rebooting my phone I checked the forums and saw this! Hahah but thank you very much! This is pretty much exactly what I ended up doing. I posted this and then read up on the forums rules and some stuff and realized I should really learn to help myself if I want to . Took some time and a lot of mistakes but I put it together. Thank you very much for the reply.
CreativeSin said:
As RSDLite was rebooting my phone I checked the forums and saw this! Hahah but thank you very much! This is pretty much exactly what I ended up doing. I posted this and then read up on the forums rules and some stuff and realized I should really learn to help myself if I want to .
Took some time and a lot of mistakes but I put it together. Thank you very much for the reply.
Click to expand...
Click to collapse
You're welcome :thumbup: I'm glad it all worked out for you in the end. I still remember the time earlier this year when I just got my phone, went crazy with mods and ended up softbricking it for a whole week. It was hell just to get it working again cuz RSD Lite decided to hate me from the get-go. -_-
So I'm glad to help others out with this, but enough rambling lol, take greater care for the next flashes you do until you get used to it!
Sent from the Ace's MB865 using xda-developers app
Aceofzeroz said:
You're welcome :thumbup: I'm glad it all worked out for you in the end. I still remember the time earlier this year when I just got my phone, went crazy with mods and ended up softbricking it for a whole week. It was hell just to get it working again cuz RSD Lite decided to hate me from the get-go. -_-
So I'm glad to help others out with this, but enough rambling lol, take greater care for the next flashes you do until you get used to it!
Sent from the Ace's MB865 using xda-developers app
Click to expand...
Click to collapse
Thanks! Just got it all rooted again no problem. I'm trying to learn all this, any tips on something I could start working on?
CreativeSin said:
Thanks! Just got it all rooted again no problem. I'm trying to learn all this, any tips on something I could start working on?
Click to expand...
Click to collapse
Well now that you're back and rooted, if you're planning on doing any more flashing any time soon then I recommend you install boot menu manager. If you've previously installed safestrap or bootstrap, clear their data and uninstall them before installing bmm.
With that done, you've just made your phone a little safer from bricking because bmm allows multi rom booting, which are somewhat independent of the primary system. Refer to this thread for more info on how to make systems, etc.: http://forum.xda-developers.com/showthread.php?t=2115715
The first thing you'd want to do is make sure your apps/data is always backed up at all times with apps like titanium backup. Create 2 or more systems so that you can try the bmm compatible custom ROMs which are in the dev section if you want to try any of them. But please, read all instructions, warnings, requirements, etc. carefully before attempting any flashing in general.
The thread I posted in my earlier post above will have links to the specific custom ROMs. If you're doing any other kind of flashing, make sure to again, read instructions carefully and take your time with learning all of this.
Hi, I soft bricked my phone recently.
I was running stock ICS from Moto on a rooted Atrix 2. I wanted to upgrade it to JB so I installed Atrix 2 bootstrap and clicked Bootstrap Recovery (gave superuser permission) and then Reboot Recovery. It went into CWM and I wiped factory data and cache. Before I installed the JB zip I backed up my old ICS via CWM and then installed CyanogenMod-Dev-edison-nightly-20130401-2132-signed.591fan.com zip.
It was upgraded successfully to 4.2.2 but I couldnt get my updated contacts from the Super Recovery app, so I thought to restore the old ICS and backup the contacts once again. I installed Atrix 2 bootstarp apk again and went thought the same process ( Bootstrap recovery > gave Superuser permission > Reboot recovery). As soon as it rebooted the Motorola logo came on and after that the phone gave dark grey screen. I tried rebooting and going into CWM on startup but it didnt give the option of install zip from sd card as it did on my earlier attempt.
I am stuck with a bricked phone and all my work is stuck up.
I read about RSDlite but I have heard it causes hard bricking on several occasion. So, I am a bit cautious about using it and I dont know the exact procedure to use it also. Can you please guide me on how to regain my phone from this soft brick and where i went wrong during my installations.
Any help would be very much appreciated. Thanks a lot in advance.
kunal2711 said:
Hi, I soft bricked my phone recently.
I was running stock ICS from Moto on a rooted Atrix 2. I wanted to upgrade it to JB so I installed Atrix 2 bootstrap and clicked Bootstrap Recovery (gave superuser permission) and then Reboot Recovery. It went into CWM and I wiped factory data and cache. Before I installed the JB zip I backed up my old ICS via CWM and then installed CyanogenMod-Dev-edison-nightly-20130401-2132-signed.591fan.com zip.
It was upgraded successfully to 4.2.2 but I couldnt get my updated contacts from the Super Recovery app, so I thought to restore the old ICS and backup the contacts once again. I installed Atrix 2 bootstarp apk again and went thought the same process ( Bootstrap recovery > gave Superuser permission > Reboot recovery). As soon as it rebooted the Motorola logo came on and after that the phone gave dark grey screen. I tried rebooting and going into CWM on startup but it didnt give the option of install zip from sd card as it did on my earlier attempt.
I am stuck with a bricked phone and all my work is stuck up.
I read about RSDlite but I have heard it causes hard bricking on several occasion. So, I am a bit cautious about using it and I dont know the exact procedure to use it also. Can you please guide me on how to regain my phone from this soft brick and where i went wrong during my installations.
Any help would be very much appreciated. Thanks a lot in advance.
Click to expand...
Click to collapse
Use boot menu manager instead of bootstrap recovery
Sent from my MB865 using XDA Premium 4 mobile app
**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