I rooted my ATT GNote using Odin from GNote rootICS. After root was completed and my phone rebooted same computer I used Odin on, a message kept popping up everytime I connected the phone back with PC. The message was "missing identity of the device...contact manufacturer". After trying several times it finally recognized my phone as mass storage device and didn't see SDstorage to transfer after trying a couple if times again I was finally able to see SDstorage and then I moved zip file of PA to storage. After all this struggle when I flashed ROM using CWM. The installation failed and some status 7 error popped up...can anyone please guide me where did I go wrong?
P.S Phone is not bricked becoz I was able to restore it back nandroid copy I made before flashing PA ROM.
Sent from my Galaxy Nexus using xda app-developers app
The latest ROMs have had issues with CWM, which is why everyone seems to be using TWRP--the one the Paranoid Android developer linked to, and suggested in the PA thread. He included it in his tutorial.
To rehash:
Copy the TWRP .zip file to your device,
(or install goomanager, then hit menu, and selet install openscripts)
Flash TWRP
Download PA (a newer version may or maynot be available on another site).
Check the MD5, ensuring you got a good download, and that the upload wasnt bad.
Flash.
Enjoy.
In short, make sure you have a good download, and flash the TWRP recovery .zip , then flash the ROM from TWRP.
Jamesyboy said:
The latest ROMs have had issues with CWM, which is why everyone seems to be using TWRP--the one the Paranoid Android developer linked to, and suggested in the PA thread. He included it in his tutorial.
To rehash:
Copy the TWRP .zip file to your device,
(or install goomanager, then hit menu, and selet install openscripts)
Flash TWRP
Download PA (a newer version may or maynot be available on another site).
Check the MD5, ensuring you got a good download, and that the upload wasnt bad.
Flash.
Enjoy.
In short, make sure you have a good download, and flash the TWRP recovery .zip , then flash the ROM from TWRP.
Click to expand...
Click to collapse
Thanks. I have twrp on my GNEX and have been flashing ROMs without trouble.
The way I rooted GNote it installed CWM but even before I even have problem flashing rom. I am having problem with my computer reading my GNote when I connect it with data cable. Every time I connect a message pops up saying missing identity of your device call manufacturer.
Sent from my Galaxy Nexus using xda app-developers app
Okay, so I was trying to install CM 10.2.1, but I got a missing md5 file error, so it didn't work out. I am using TWRP as my recovery, and naturally I wiped everything before flashing, so I then went into some of the recoveries on my sd card to try to restore from those, unfortunately all attempts at restoring have failed,. My next attempt was trying to use the adb sideload feature of TWRP to try to put a new ROM zip file into it, and try to flash that, but TWRP just hangs at "Starting sideload feature" and never really starts it so I am unable to do that. Any ideas on how to get things working? Also why is TWRP unable to do anything correctly? (TWRP v2.6.31)
Phone_BrickerT_T said:
Okay, so I was trying to install CM 10.2.1, but I got a missing md5 file error, so it didn't work out. I am using TWRP as my recovery, and naturally I wiped everything before flashing, so I then went into some of the recoveries on my sd card to try to restore from those, unfortunately all attempts at restoring have failed,. My next attempt was trying to use the adb sideload feature of TWRP to try to put a new ROM zip file into it, and try to flash that, but TWRP just hangs at "Starting sideload feature" and never really starts it so I am unable to do that. Any ideas on how to get things working? Also why is TWRP unable to do anything correctly? (TWRP v2.6.31)
Click to expand...
Click to collapse
Why don't you just take the SD card out of your phone and then put it into your computer and move the ROM file and gapps file to it that way?? Unless you don't have the SD card adapter.
I was having random problems with TWRP myself and got Philz Touch and now I'm good. Just a thought.
Sent from my SCH-I545 using XDA Premium 4 mobile app
TWRP 2.5.0.2 is supposedly the most stable loki recovery for our phone. I would try "downgrading" to that first, If you still have problems with 2.5.0.2 then I would switch to Philz Touch. I had to switch to Philz because TWRP just doesn't like my S4 for some reason. It sucks though, TWRP has a way better UI than CWM.
joshm.1219 said:
TWRP 2.5.0.2 is supposedly the most stable loki recovery for our phone. I would try "downgrading" to that first, If you still have problems with 2.5.0.2 then I would switch to Philz Touch. I had to switch to Philz because TWRP just doesn't like my S4 for some reason. It sucks though, TWRP has a way better UI than CWM.
Click to expand...
Click to collapse
I agree with you there I rather TWRP. Philz takes some getting used to but m actually really liking it now.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Mistertac said:
I agree with you there I rather TWRP. Philz takes some getting used to but m actually really liking it now.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's just the little things like there's no real graphic interface, it's just a throwback Windows menu, or the fact that dalvik cache needs to be wiped separately, etc.
I'm running CM 11 nightlies, usually the latest.. I've been running CWM 6.0.4.4 for as long as I can remember after initially rooting/loki patching my phone.
Last week, Rom manager notified me that there was an update to CWM, 6.0.4.7. I thought "cool" - and I flashed it via Rom manager, which reported this was a success.
However, whenever I rebooted into recovery, I still had CWM 6.0.4.4. I tried again, fail. Decided to clean flash my next nightly and try again. Same thing. Could not get Rom manager to update.
I flashed over to Twrp using goo manager which worked fine. I used Twrp to flash over to Philz touch which worked fine.. anytime I use Rom manager now though, it seemingly does nothing even though it reports a success. For example, if I am on TWRP and use rom manager to flash the latest CWM, I'll be met with a success but a reboot into recovery leaves me still with TWRP and no CWM.
I guess I'm just wondering if anyone can help me figure out what's going on -- I know I've seen others at least in the CM forum post about Rom manager acting similarly, but I also hear reports that it works fine for others. Ultimately I just ended up making a 6.0.4.7 flashable zip of my own to upgrade but I'd rather get things figured out vs make a new flashable zip anytime an updated version of CWM comes out.
vanberge said:
I'm running CM 11 nightlies, usually the latest.. I've been running CWM 6.0.4.4 for as long as I can remember after initially rooting/loki patching my phone.
Last week, Rom manager notified me that there was an update to CWM, 6.0.4.7. I thought "cool" - and I flashed it via Rom manager, which reported this was a success.
However, whenever I rebooted into recovery, I still had CWM 6.0.4.4. I tried again, fail. Decided to clean flash my next nightly and try again. Same thing. Could not get Rom manager to update.
I flashed over to Twrp using goo manager which worked fine. I used Twrp to flash over to Philz touch which worked fine.. anytime I use Rom manager now though, it seemingly does nothing even though it reports a success. For example, if I am on TWRP and use rom manager to flash the latest CWM, I'll be met with a success but a reboot into recovery leaves me still with TWRP and no CWM.
I guess I'm just wondering if anyone can help me figure out what's going on -- I know I've seen others at least in the CM forum post about Rom manager acting similarly, but I also hear reports that it works fine for others. Ultimately I just ended up making a 6.0.4.7 flashable zip of my own to upgrade but I'd rather get things figured out vs make a new flashable zip anytime an updated version of CWM comes out.
Click to expand...
Click to collapse
get the latest cwm 6.4.7 zip and flash through philz recovery make sure to apply auto loki patching (i think thats already checked never hurts to make sure though) hit power options and reboot recovery. thats my thought and u should have on screen cwm 6.4.7
FordNate said:
get the latest cwm 6.4.7 zip and flash through philz recovery make sure to apply auto loki patching (i think thats already checked never hurts to make sure though) hit power options and reboot recovery. thats my thought and u should have on screen cwm 6.4.7
Click to expand...
Click to collapse
Where do you get the 6.0.4.7 zip? I've only been able to find the .img file on the rom manager/cwm website...
Going back to my htc days n adb using it was fastboot flash flash {recovery name}.img. maybe using something like flashimgui or flashify.. just thoughts of course other than that u would need to convert to a zip file
FordNate said:
Going back to my htc days n adb using it was fastboot flash flash {recovery name}.img. maybe using something like flashimgui or flashify.. just thoughts of course other than that u would need to convert to a zip file
Click to expand...
Click to collapse
Nice! Flashify does it beautifully. CWM touch even. I cannot believe I'm just now trying this app!
What's been improved between 6.0.4.4 & 6.04.7?
Sent from my HTC6600LVW using XDA Premium 4 mobile app
joshm.1219 said:
What's been improved between 6.0.4.4 & 6.04.7?
Sent from my HTC6600LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nothing immediately apparent, I'm just OCD about running the latest/greatest.
I tried to root my Samsung Galaxy S5 using Odin and an autoroot file. After that failed, I researched how to restore my phone to its original OS. I have not been able to do that either. I either can only boot to the Odin Mode screen or am locked on the T-Mobile logo screen.
BTW, I am new to phone rooting so more detailed explanations would be appreciated.
Are you able to boot to recovery? [ home+volume up+power]
If so you can reset from there.
If not you should be able download the stock firmware and flash it with Odin.
FOL1 is the latest - it takes a long time to download from Sam's.
http://www.sammobile.com/firmwares/database/SM-G900T/
Jim
otisdog is right, sammobile takes forever to download which is why you should download the exact same file they linked to, but from here:
https://www.androidfilehost.com/?fid=24407100847293882
Since cf-autoroot didn't work for you, you should just install TWRP with Odin and use TWRP to flash supersu zip, that's more or less what cf auto-root is doing anyway. Boot your phone into Odin mode (home, vol down, and power), connect your phone to PC with USB, and install twrp-3.0.0-0-klte-klte.img.tar with Odin (AP button, auto-reboot option disabled). When the status bar is filled, you need to immediately boot into TWRP without rebooting system (this is where you hold down home, vol up, and power). In TWRP, install supersu zip file. Now wipe cache and dalvik
If you reboot to normal android before booting into TWRP and flashing the supersu zip when TWRP is first installed, the operating system will overwrite TWRP with the stock recovery, and you have to try again.
Thanks OtisDog and thisisapoorusernamechoice.
While I am downloading TMB-G900TUVS1FOL1-20160111153316, I tried your directions for installing TWRP and had success. I was able to boot into TWRP. (First boot success since I started 10 days ago.) I downloaded supersu zip and have it on my Windows 10 computer. I assume that I do not unzip it in Windows, correct?
From TWRP I clicked on Install and got the phone's files. When I clicked on Select Storage, the USB storage choice has 0MB so the option is disabled. Should I have started TWRP with my USB cable still connected? My computer still recognizes that I am connecting something to it while TWRP is running.
If that is not the problem, how do I install supersu zip into my phone?
Dave4237 said:
Thanks OtisDog and thisisapoorusernamechoice.
While I am downloading TMB-G900TUVS1FOL1-20160111153316, I tried your directions for installing TWRP and had success. I was able to boot into TWRP. (First boot success since I started 10 days ago.) I downloaded supersu zip and have it on my Windows 10 computer. I assume that I do not unzip it in Windows, correct?
From TWRP I clicked on Install and got the phone's files. When I clicked on Select Storage, the USB storage choice has 0MB so the option is disabled. Should I have started TWRP with my USB cable still connected? My computer still recognizes that I am connecting something to it while TWRP is running.
If that is not the problem, how do I install supersu zip into my phone?
Click to expand...
Click to collapse
The supersu zip needs to be in your phone's internal storage or micro SD card. USB storage is not used for this
thisisapoorusernamechoice said:
The supersu zip needs to be in your phone's internal storage or micro SD card. USB storage is not used for this
Click to expand...
Click to collapse
Since my phone has no SD card slot, this sounds like a Catch 22. I can't get my phone to work without installing the supersu zip, but I can't install the supersu zip without getting my phone to work.
Fortunately, the file that OtisDog suggested DID work. THANK YOU. THANK YOU. THANK YOU.
My wife is also thrilled that I don't have a $160 brick. She sends hugs to both of you.
Dave4237 said:
Since my phone has no SD card slot, this sounds like a Catch 22. I can't get my phone to work without installing the supersu zip, but I can't install the supersu zip without getting my phone to work.
Fortunately, the file that OtisDog suggested DID work. THANK YOU. THANK YOU. THANK YOU.
My wife is also thrilled that I don't have a $160 brick. She sends hugs to both of you.
Click to expand...
Click to collapse
You don't need the SD card, you can put the supersu zip file in your phone's internal memory and flash it from there in TWRP. Also if you have a Galaxy S5, you have an SD card slot. It's on top of, yes literally on top of the SIM card slot, can be a little confusing and hard to see until you know what you're looking for (see attached pic for clarification, sorry for my halfassed paint job lol).
thisisapoorusernamechoice said:
You don't need the SD card, you can put the supersu zip file in your phone's internal memory and flash it from there in TWRP. Also if you have a Galaxy S5, you have an SD card slot. It's on top of, yes literally on top of the SIM card slot, can be a little confusing and hard to see until you know what you're looking for (see attached pic for clarification, sorry for my halfassed paint job lol).
Click to expand...
Click to collapse
Thanks for the photo. That helps.
My latest problem is that every time I restart my phone, some shortcuts (Hi, Google; Gallery; magazines; exercise; camera) are added to my home screens and the default home screen is changed. I suspect that by clearing one of the caches, I can fix this. What do I need to do?
You can go into settings and find "backup and reset".
In there uncheck the backup and then do the factory reset. This will wipe all data and reload the os like when the phone was new - you can then put on it what you want.
MAKE SURE you have anything that's on the phone now, that you want, backed up on your computer because it will get wiped off the phone.
Once you get the phone to where you want it we can work on rooting it.
Jim
The instructions from thisis... worked great for me, although I accidentally did a full wipe from TWRP - no biggie, I was backed up. Thanks!
I appreciate the clear and concise instructions I've seen so far, I got as far as flashing superSU zip and wiping cache and dalvik, what next?
NexMortifer said:
I appreciate the clear and concise instructions I've seen so far, I got as far as flashing superSU zip and wiping cache and dalvik, what next?
Click to expand...
Click to collapse
Reboot lol
Sent from my SM-N920G using XDA Labs
ShinySide said:
Reboot lol
Click to expand...
Click to collapse
wouldn't it be nice if that just worked?
sorry, enough sarcasm, I'll clarify, I got that far with everything going as intended, but after reboot, it's not rooted (according to rootchecker) and I don't know why. Additional device info:
SM-G900T
running 4.4.2 (it doesn't want to let me update for some reason, and I thought maybe old versions might be easier to root)
Baseband Version G900TUVU1CNK2
Build # is KOT49H.G900TUVU1CNK2
(if there's other info you need, let me know.)
NexMortifer said:
wouldn't it be nice if that just worked?
sorry, enough sarcasm, I'll clarify, I got that far with everything going as intended, but after reboot, it's not rooted (according to rootchecker) and I don't know why. Additional device info:
SM-G900T
running 4.4.2 (it doesn't want to let me update for some reason, and I thought maybe old versions might be easier to root)
Baseband Version G900TUVU1CNK2
Build # is KOT49H.G900TUVU1CNK2
(if there's other info you need, let me know.)
Click to expand...
Click to collapse
Yeah that's weird. Since you're running kit Kat should of installed system root. Or maybe I'm wrong on the zip being able to root kitkat/use system root instead of systemless.
Open the supersu app and see if it asks to update su binary
Otherwise I'd just try flashing it again in twrp or finding a much older supersu zip to flash. (Probably a 1.×× version)
You don't need to wipe caches tho.
Sent from my SM-N920G using XDA Labs
ShinySide said:
Open the supersu app and see if it asks to update su binary
Click to expand...
Click to collapse
App isn't showing up either, don't know if that's useful info or not.
NexMortifer said:
App isn't showing up either, don't know if that's useful info or not.
Click to expand...
Click to collapse
You are flashing it in twrp correct?
Because you should have SuperSU installed then
Sent from my SM-N920G using XDA Labs
ShinySide said:
You are flashing it in twrp correct?
Because you should have SuperSU installed then
Sent from my SM-N920G using XDA Labs
Click to expand...
Click to collapse
Yes, I did, and no, it didn't.
Well, I eventually gave up on that root technique, and ended up using This instead, so now I'm running 6.0.1, and it seems to be working alright, but SuperSU says "The SU bianary needs to be updated!" and when I click it, it offers me the options of "normal" and "TWRP/CWM" as ways to install the SU bianary.
I know just enough to know that I don't know what I'm doing, and thought I'd get some advice before I proceed to screw something up.
Which option should I go for, and if TWRP, do I need to re-flash it with Odin like I did to install the 6.0.1 ROM, or is the process different now?
NexMortifer said:
Well, I eventually gave up on that root technique, and ended up using This instead, so now I'm running 6.0.1, and it seems to be working alright, but SuperSU says "The SU bianary needs to be updated!" and when I click it, it offers me the options of "normal" and "TWRP/CWM" as ways to install the SU bianary.
I know just enough to know that I don't know what I'm doing, and thought I'd get some advice before I proceed to screw something up.
Which option should I go for, and if TWRP, do I need to re-flash it with Odin like I did to install the 6.0.1 ROM, or is the process different now?
Click to expand...
Click to collapse
I always just click normal. Then it'll ask to reboot and just allow it and you'll be good to go
Sent from my SM-N920G using XDA Labs
https://forum.xda-developers.com/tm...l/root-how-to-root-sm-g900t-firmware-t3358190
use that guide, follow it precisely and you will be fine