Hey all, Let me start by apologizing for not posting this in the right place (More than likely). i didnt see any threads for LG p505 Phoenix.
On to buisness, i had an error booting into ClockWorkMod Recovery. My phone is booting incorrectly ever since. ive tried to take the battery out and replace it, but that didnt work. I tried to follow some repair work listed on the forums, but i need further assistance. ive gotten as far as the SDK dev package and attempting to restart the bootloader, but no luck. it keeps saying it cant detect the device. the computer recognizes it as ASUS Android Bootloader Interface. Any help?
Where did you learn how to put CWM on you phone? If it wasn't here, why not try those forums where you did?
Try this
http://forums.androidcentral.com/t-lg-phoenix-thrive/
Well, i got CWM on my phone via the Rom Manager App on the Market. but, after toying around with my phone trying to fix it, it appears that it is stuck on the bootloader, and not CWM. when it DOES "boot up", it only displays lines of code that varies when i plug it into a power source or my PC.
Are you rooted?
yeah i am. couldnt have gotten this far without that step.
FawkesPhone said:
yeah i am. couldnt have gotten this far without that step.
Click to expand...
Click to collapse
Just didn't want you thinking you could flash cwm by installing rom manager.
What exactly is going on. Give lots of details.
* iTouched Epic
Well, good for you. im such a rookie that would be entirely possible. lol. anywho, i asked for help on another forum, who a couple people on have some experience with programing and such, and i pretty much explained everything there is to explain there.
however, the website wont let me post a link to said post, so im going to try to copy/paste because i REALLY dont feel like typing all that out again if i dont have to.
Copy link and put (dot) as the dot .
* iTouched Epic
the story is, i tried to boot my phone (LG phoenix [p505], running CarloROM, standard Kernnel) into ClockWorkMod Recovery Mode, but upon booting up, teh device went to a black screen, save for a couple words, most partial. the readable text says "UDC_Start()". on pluging it into the PC, it displays the following text:
-- suspend --
-- reset --
EP1/out FAIL nfo=40 pg0=74000
-- portchange --
usb_read() transaction failed
-- reset --
-- portchange --
fastboot: oops !
fastboot: Processing commands
i am trying to utilize the only fix ive found, which is to reboot the bootloader via andriod developer debug window. i tell the command prompt to run the "adb reboot bootloader" function but it says it cant find the device.
it also appears on the PC as "ASUS android bootloader interface"
Click to expand...
Click to collapse
here's all the details ive got thus far
Try flashing stock recovery on it. Flash back to complete stock. Did you check to make sure cwm was compatible with your device?
Was the other forum not helpful to you?
* iTouched Epic
boborone said:
Try flashing stock recovery on it. Flash back to complete stock. Did you check to make sure cwm was compatible with your device?
Was the other forum not helpful to you?
* iTouched Epic
Click to expand...
Click to collapse
First, not the other forum isnt helping as it's a small user group and no one's responded yet. second, as previously stated, after posting this thread, ive determined that the phone did NOT boot to CWM. and second, yes, CWM is compatable and has worked in the past. i heard about it from someone that has used it on his p505 and it works perfectly.
There are a lot of devices that only run a modded version of cwm. I have a Samsung intercept that won't run with standard cwm.
* iTouched Epic
people on the android central forum you posted a link to say the phoenix runs just fine with standard CWM
Did you try flashing the touch version of cwm? My epic touch sgsll bricks with that?
* iTouched Epic
i rooted my phone, downloaded ROM Manager, gave it Super user permissions, and flashed Optimus One (Old BaseBand). exactly as instructed.
Where did you learn about doing this? You said you tried asking on another forum. What did they say? Did you try what they said? Have you tried what I said about going stock?
* iTouched Epic
i learned all this from here: http://forums.androidcentral.com/t-lg-phoenix-thrive/138186-how-clock-workrecovery-mod-cwm.html
no one has responded on the other forum as previously stated
i have learned that my device is booting to the bootloader, not CWM, also as previously stated.
thus, flashing a new ROM of any sort is impossible.
FawkesPhone said:
i learned all this from here: http://forums.androidcentral.com/t-lg-phoenix-thrive/138186-how-clock-workrecovery-mod-cwm.html
no one has responded on the other forum as previously stated
i have learned that my device is booting to the bootloader, not CWM, also as previously stated.
thus, flashing a new ROM of any sort is impossible.
Click to expand...
Click to collapse
You never said you didn't get any responses from the other forum. If you posted the question yesterday and gave it a couple hours, no responses, then started flipping out cause your is phone is messed up and so you decided to join for the soul reason of using it as a technical support and post in off topic cause this site doesn't even develop (notice I didn't say support) your phone, I say you need to chill out and go back to other site and get a lil bit more in depth with your question. Cause honestly I would have overlooked your question with how it was written and the little information given. Those guys know about your bootloader. I don't. Not many here do. LG doesn't make flagship devices, hence why they're not here.
I can tell you that if nobody does help you, you need to read up on how to shell into the phone and flash something else like that.
* iTouched Epic
FawkesPhone said:
First, no, the other forum isnt helping as it's a small user group and no one's responded yet.
Click to expand...
Click to collapse
Also, why waste an hour of my time? If you're gonna tell me to eff off, why not do it at the beginning?
FawkesPhone said:
Also, why waste an hour of my time? If you're gonna tell me to eff off, why not do it at the beginning?
Click to expand...
Click to collapse
I didn't tell you to f off, but, in all seriousness, I don't like it when people join this site just to ask a question.
Then you post in the wrong forum about a phone that isn't even developed on here.
Sub-Forums : General discussion
Forum
Last PostStats
About xda-developers.com
Anything to do more with the site than with the phones. Feature requests, announcements, praise, moaning, etc.
General
Anything that involves all of the phones and doesn't fit in any of the other fora.
Paid Software Announcement and Discussion
Are you a developer wanting to promote for-pay software? Feel free to post announcements about your apps here and have the community discuss them.
Questions and Answers
This forum is for all questions, big or small, you might have. Please read the rules in this forum before asking.
Hardware Hacking
For discussion of development boards, hardware interfaces, datasheets, circuit modification and related tools
NFC Hacking
For discussion of Near Field Communication (NFC) hacking and development
Upgrading, Modifying and Unlocking
Some of the more advanced issues, involving multiple phones.
Accessories
For accessories that involves multiple phone-types. Car-kits, headphones, cables, chargers, extra batteries, replacement screens, sources for connectors, etc.
Networking
GPRS or WAP-settings, WiFi, ... This forum is for anything to do with getting your device talking to the rest of the world.
XDA TV
Here's your chance to communicate directly with the stars of XDA TV!
Off-topic
Anything not related to the phones.
^ Just wanted to point that out. ^
And I did try to help you. I don't know LG bootloaders. But I went through seeing if you made some noob mistake that I could help with. Then when that was sorted out, I told you how to help yourself. If you're are going to take someone telling you how to help yourself as telling you to f off, not sure you are going to make it here on XDA. Good luck with that attitude.
---------- Post added at 10:20 AM ---------- Previous post was at 10:16 AM ----------
Did you try to search here on this site?
Searched here on XDA and found this:
http://forum.xda-developers.com/showthread.php?t=1289265&page=3
You see, we don't mind helping people at all, it's the people that won't help themselves that get on people's nerves. Look man, I will help you as much as I can. But you have to be willing to help yourself, too. Finding threads like the one I posted above is what I mean by searching and reading on how to shell into the phone, using adb to fix your problems. You have a jacked up phone, don't get frustrated and mad at the world, calm down, chill out. You can fix it.
Related
Ive been at it, probably for 6 hours total. Let me give a rundown of what I have done.
I started here
http://www.simplehelp.net/2009/10/04/how-to-install-cyanogenmod-4-1-99-on-your-g1-android-phone/
but since I did not already have Cyanogen Recovery 1.4 installed.
I had to go here:
http://www.simplehelp.net/2009/09/21/the-complete-step-by-step-guide-to-rooting-your-android-phone/
I followed the steps, to the letter, untill I got to number 15, at which point. I kept getting "BACKUP FAILED"
as did a ton of other people apparently. From reading, I deduced.. incorrectly perhaps, that I needed to DOWNGRADE from RC33, to a lower one, pre donut.
I managed to downgrade to RC29.
at which point I went back and started to process of installing Recovery 1.4.
Well, it turns out the Backup program.. will not work with RC29 I need (apparently) RC30..
Well I CANNOT find a vanilla version of RC30.. I have searched and searched, all I can find is the RC30 MOD software. Which I tried.
As per the directions I renamed update_TC4-RC30_full_xda-dev_v1.2.zip to update.zip.
disconnected the phone rebooted into recovery, then ALT-S to install it.
and I get:
E: No signature (382 files)
E: verification failed.
Installation aborted.
so now, long story short, Im stuck in RC29, unable to update to RC30 so that I can begin the process of installing cyanogen.
I have searched, searched until i could taste colors and see sounds.. I get lots or results, and they are all people having the same or similar problem, asking the same question.
I think once I get RC30 back on the phone, I can work it out from there.
But at this point my brain feels like a melted plastic bag. This sort of stuff is "not my thing" I was able to get my HTC Excalibur done with little fuss, but the G1 is turning out to be one of those projects where you get half way, then go off on a tangent trying to find a fix, then cant get the fix to work and get trailed off trying to find a fix for the fix.. and well you get the idea.
Thanks for any help.
Please god help LOL
http://wiki.cyanogenmod.com/index.php/Main_Page#How_do_I_upgrade_to_the_latest_CyanogenMod.3F
Just follow the instruction at CyanogenMod Wiki. Even my girlfriend can do it by herself...
At my wits with noobs making topics in the wrong section.
All your answers are here.
and for the hell of it
here might help too!
firstly, wrong section, this belongs in the QnA section
secondly, email me at [email protected] if those instructions dont work
i prefer to solve issues on a 1-2-1 basis
tengtengvn said:
http://wiki.cyanogenmod.com/index.php/Main_Page#How_do_I_upgrade_to_the_latest_CyanogenMod.3F
Just follow the instruction at CyanogenMod Wiki. Even my girlfriend can do it by herself...
Click to expand...
Click to collapse
I already went there, thats where I started.
Wingnutt said:
I already went there, thats where I started.
Click to expand...
Click to collapse
Why? :'(
Why can't people follow simple step-by-step tutorials?
Why do they always post questions in development instead of Q&A ? :'(
G1-evolve said:
All your answers are here.
and for the hell of it
here might help too!
Click to expand...
Click to collapse
You know what, this is the exact kind of thing that makes the search function less effective, and pisses me off.
Because guess what I find when I try to search for my problem. Lots of posts of people, also asking about the same or similar problem, and being told to search.
I stated in my first post that I have tried searching, this post was a last resort.
If you do not have an answer, dont answer.
Thanks
maxisma said:
Why? :'(
Why can't people follow simple step-by-step tutorials?
Why do they always post questions in development instead of Q&A ? :'(
Click to expand...
Click to collapse
WELLLLL
perhaps you should ask the other 100 plus people that have had similar issues..
The problem Im running into is typical of someone with no knowledge of the issue, reading a how to written by someone who knows it very well.
in that, tiny steps, that the person who wrote the turtorial see as "no duh" self evident things, that need not be stated.. are total greek to me.. so I got stuck,
you complain about that yet you post in the wrong place....genius
and you were offered plenty of advice, not just "search"
mods, please move this
Wingnutt said:
WELLLLL
perhaps you should ask the other 100 plus people that have had similar issues..
The problem Im running into is typical of someone with no knowledge of the issue, reading a how to written by someone who knows it very well.
in that, tiny steps, that the person who wrote the turtorial see as "no duh" self evident things, that need not be stated.. are total greek to me.. so I got stuck,
Click to expand...
Click to collapse
not to be a jackass or anything, but if you don't know what you're doing, then you really shouldn't be trying to do any of this in the first place.
i agree...i get people emailing me asking "how do i root" "what is root" "what is cyanogenmod" "" ]
and i just tell them "if you dont know what root is, you shouldnt root" and "you need to do your own research, me spoonfeeding you will no doubt lead to you having problems somewhere down the line and blaming me"
and if you aint tech-minded and cant fill in the blanks, you shouldnt be fukin with ur phone
first this belongs in Q&A, second your not suppose to install RC30, installing RC30 defeats the purpose of going to RC29 to get root
Let me restate this again..
all I need, I think, is to update to RC30.. not a mod version.. just the regular.. I think I can get it rolling from ther..
still with me?
I cannot find a regular version of RC30.. only the mod versions..
still there?
when I try to install the mod version VIA the directions listed.. I get
E: No signature (382 files)
E: verification failed.
Installation aborted
thats it.. that is where I stand..
why goes it say verification failed..
EDIT: im trying to get root now on RC29 will update..
BTW, i posted this HERE because I figured PHONE Q&A was Q&A about the damn phone!! and that mods and the issue im dealing with seem more like something that would be considered DEVELOPMENT.
SORRY
Wingnutt said:
Let me restate this again..
all I need, I think, is to update to RC30.. not a mod version.. just the regular.. I think I can get it rolling from ther..
still with me?
I cannot find a regular version of RC30.. only the mod versions..
still there?
when I try to install the mod version VIA the directions listed.. I get
E: No signature (382 files)
E: verification failed.
Installation aborted
thats it.. that is where I stand..
why goes it say verification failed..
Click to expand...
Click to collapse
and let me restate what others have said:
this belongs in the Q&A section.
start with part 1 - method b
http://androidandme.com/2009/08/news/how-to-root-a-t-mobile-g1-and-mytouch-3g-android-phone/
read the whole thing twice, and then two more times after that
there are so many threads with directions on how to do this. the reason search didn't find anything is because so many people are starting these threads. it's ridiculous that the search button needs a search button.
FYI - start with the sticky threads at the top of each forum. they will tell you everything you need to know or at least where to find it
u relise that by going to R30 stock, not mod....u will lose root
u WANT R29, then do the telnet thing to get root, (then cm1.4 recovery if it disappears) then flash the HTC 1.6 image, wipe, THEN cyanogens latest
dont even bother asking any more questions here, start again in the QnA section or just flash stock and dont bother with custom roms
WEll I got rc29 rooted, and have it flashed to RC30 with root.
so now Hopefully I can get the rest rolling.
Ill post any followup questions in the Q&A.
thanks for all the help, smug and elitist as it was.
Wingnutt said:
WEll I got rc29 rooted, and have it flashed to RC30 with root.
so now Hopefully I can get the rest rolling.
Ill post any followup questions in the Q&A.
thanks for all the help, smug and elitist as it was.
Click to expand...
Click to collapse
WELLLLLLLL
We are not being "smug and elitist" we just know that when people post questions not understanding how to do something that if you don't know how to follow the instructions you shouldnt be doing in the first place the next post (Probably in the wrong forum) will be along the lines of "OMG I THINK I BRICKEDED MY PHONE!!!!!!!! OMG PLZ HELP!!!!!!!"
ANd being a crabby **** won't win you any friends either...
Wingnutt said:
WELLLLL
perhaps you should ask the other 100 plus people that have had similar issues..
The problem Im running into is typical of someone with no knowledge of the issue, reading a how to written by someone who knows it very well.
in that, tiny steps, that the person who wrote the turtorial see as "no duh" self evident things, that need not be stated.. are total greek to me.. so I got stuck,
Click to expand...
Click to collapse
You're a moron. If 100+ people have had similar issues, maybe you should read the suggestions they received. I'm sure one of those 100+ has had the exact issue you have.
Besides, if everyone who had a personal issue opened up a new thread, do you really think any substantive development would be achieved in this forum?
Like others have said, if you have no knowledge of Android modding, don't do it. If you can't figure out how to root -- with all of the tutorials and past threads -- you shouldn't be rooting.
http://getyourdroidon.com/wiki/index.php5?title=OTA_/_Un-Root_/_Official_Builds
For future reference.
It does not like our phones. Has great options but.......it sucks. Everytime I flash it on my phone my recovery goes bad in a cpl days. Never had this problem with RA. Do a search rom manager pops up all over the place with bad recoveries. Stop using it ppl. Im sure ill get flamed for this but oh well. Kinda tired of reading of noobs that fall victim to a .apk that seems very easy to use until it craps out and then your stuck at the airport with a bad recovery and ADB no where in sight. Or even if u had ADB you still have no clue how to fix it!!!!!!!!!!!
http://forum.xda-developers.com/showthread.php?t=742007
http://forum.xda-developers.com/showthread.php?t=762325
http://forum.xda-developers.com/showthread.php?p=7443928&highlight=revovery#post7443928
I couldn't agree more.
never used it thank goodness.........
Never happened to me
EDIT: Sorry for my rudeness, anyways, people should know that it's not the greatest idea to use rom manager with cm5/cm6. It has already been established that it may be a bad idea to use the program with the following roms. Sorry I get really cranky in the mornings, not the best idea to come onto the forum with some old news :|
protomanez said:
Never happened to me, you're obviously too stupid to use it.
Click to expand...
Click to collapse
I have never used it and I agree with him just from all the posts I have seen related too it messing up people's recovery images. Does that make me stupid?
I've used it for a few weeks now with no problems on my MyTouch on 1.6, 2.1, and 2.2 ROMs. Not saying others aren't having legitimate issues, but people in general are much more likely to post negative reports than positive ones.
protomanez said:
Never happened to me, you're obviously too stupid to use it.
Click to expand...
Click to collapse
hahahahaha good one. Not to stupid to use it. the ui is very simple and easy to use. Flash clockwork or flash alternate. What im to stupid to do is figure out how to fix it after it kills recovery. but thank you for your input, I'm sure it will help someone out.
protomanez said:
Never happened to me, you're obviously too stupid to use it.
Click to expand...
Click to collapse
Please lead us retartds through your install procedure, current rom, set-up so we can be as learndededed as you. I have had cm5&6 with ra installed upon initial set up. No swap/ noext1234, stock mt3g spl 2.22.23.02 radio. Nothing special. I even did it with the donut mytouch rom w/root.I only use basic apps, nothing that would interfere with recovery. to me it seems that when u flash a cpl different roms a day is when it hangs up. I can usually get the phone to boot back up, which gives me a chance to get back into rom manager and flash ra recovery back to the phone. the last cpl times I had to wipe cache before it would actually flash RA recovery. so basically if u can get the phone to boot past the splash screen go to rom manager and flash the **** out of ra recovery until it works. First we found out that clockwork didnt like flashing zip's and backups on low batteries 30% and lower. then the always fun recoverly log issue(cant recall the exact error right now) and of course the cant get to recovery issue. I know it's not a widesporead problem but it is a problem that renders phones useless until u can find someone nice enough to help u and not treat u like a retard. Not everyone knows as much about phones as you guys do....congratulations you know all there is about phones. go learn some ****ing human decency, if u have nothing helpful to say then shut up.
have been using it without Rom manager and highly disagree with the poster.doing it 'wrong' or without knowing 'how to' can certainly cause problems but that should not be described as the problem of the product. lot of people can not use nuclear power correctly (look at the USA) and now we call describe nuclear power as menace which is lame :/
Sent from my T-Mobile G1 using XDA App
arefin said:
have been using it without Rom manager and highly disagree with the poster.doing it 'wrong' or without knowing 'how to' can certainly cause problems but that should not be described as the problem of the product. lot of people can not use nuclear power correctly (look at the USA) and now we call describe nuclear power as menace which is lame :/
Sent from my T-Mobile G1 using XDA App
Click to expand...
Click to collapse
hmmmmm. Maybe since its flashing clockwork from inside rom manager is what might be killing it for some of us. tonight I will try just flashing clockwork outside of rom manager and see how that goes. i like clockwork's set up and it is easy to use, just kinda freaks me out when my recovery goes bad.
arefin said:
have been using it without Rom manager and highly disagree with the poster.doing it 'wrong' or without knowing 'how to' can certainly cause problems but that should not be described as the problem of the product. lot of people can not use nuclear power correctly (look at the USA) and now we call describe nuclear power as menace which is lame :/
Sent from my T-Mobile G1 using XDA App
Click to expand...
Click to collapse
but at the same time thats why it is a part of rom manager. one click recovery flasher. to make it "easy". i highly doubt you can go into rom manager and incorrectly flash clockwork recovery. its a one click thing
it's also spoken out at many threads at xda that flashing the recovery from within the OS causes issues, so trying to install the recovery from PC or even RA1.7 should be a better option.
I'm considering that you already know the commands for that. better luck! remember, clock work will allow you to flash anything without signing - meaning? you can edit any update.zip to your liking and then forget about all the trouble of signing it before flashing. a simple toggle should do the trick while you are in recovery mode happy flashing.
Sent from my T-Mobile G1 using XDA App
It is either a case of your phone, sd card setup/left over files etc..
I use rom manager on every phone I root with no problems since its release. 6 G1's, 3 Fender LE's, 7 Mytouch 1.2 and 4 Evos. Sometimes, it takes couple seconds to show up or go into recovery, but that doesnt mean its gone. Recovery cant just dissapear without something either trying to over write it or it being erased.
crypysmoker said:
It is either a case of your phone, sd card setup/left over files etc..
I use rom manager on every phone I root with no problems since its release. 6 G1's, 3 Fender LE's, 7 Mytouch 1.2 and 4 Evos. Sometimes, it takes couple seconds to show up or go into recovery, but that doesnt mean its gone. Recovery cant just dissapear without something either trying to over write it or it being erased.
Click to expand...
Click to collapse
Im gonna give it one more try. I dont think I have ever.....
flashed clockwork from rom manager
reboot into recovery from rom manager right then (read some where that on some roms when u reboot to recovery using the regular way it might mess up....not sure about this one).
wipe everything (clockwork wipes more that amon ra)
reflash any rom
in my case... above steps then in this order
flash fireats custom mtd part 1.1
super E
Gapps
overclock update
fireats custom mtd part 1.2
anyone see a issue with what I have done so far??
Ok I will post back when clockwork fails again.....and if not f-in sweet
chrisgto4 said:
It does not like our phones. Has great options but.......it sucks. Everytime I flash it on my phone my recovery goes bad in a cpl days. Never had this problem with RA. Do a search rom manager pops up all over the place with bad recoveries. Stop using it ppl. Im sure ill get flamed for this but oh well. Kinda tired of reading of noobs that fall victim to a .apk that seems very easy to use until it craps out and then your stuck at the airport with a bad recovery and ADB no where in sight. Or even if u had ADB you still have no clue how to fix it!!!!!!!!!!!
http://forum.xda-developers.com/showthread.php?t=742007
http://forum.xda-developers.com/showthread.php?t=762325
http://forum.xda-developers.com/showthread.php?p=7443928&highlight=revovery#post7443928
Click to expand...
Click to collapse
chrisgto4 said:
hahahahaha good one. Not to stupid to use it. the ui is very simple and easy to use. Flash clockwork or flash alternate. What im to stupid to do is figure out how to fix it after it kills recovery. but thank you for your input, I'm sure it will help someone out.
Click to expand...
Click to collapse
You found your answer within the first example link that you provided, look at post #3:
http://forum.xda-developers.com/showthread.php?t=742007
rom manager is not for idiots like yourself. rom manager is a great tool for many different phones. sometimes it doesnt flash a recovery correctly maybe it be poor service to download the recovery, or low memory when flashing it. an advanced user (who its made for) can still flash recovery via fastboot, and have all the helpfulness and easy ui of rom manager and easy access to cm nightlies.
dont knock a dev who works on many different phones, and dont rely on noob application reports and bad reviews. anyone who finds rom manager crap is just a poor android user.
tehseano said:
sometimes it doesnt flash a recovery correctly maybe it be poor service to download the recovery, or low memory when flashing it.
dont rely on noob application reports and bad reviews. anyone who finds rom manager crap is just a poor android user.
Click to expand...
Click to collapse
i didn't want to get into this pointless discussion, but you have made a ****ty argument for rom mgr, you have confirmed that it doesn't work properly in certain circumstances, which is a good enough reason to not bother with it.
also, why shouldn't we rely on bad reviews? that's the point of a review, to give some idea about what experience to expect.
(i have never used it myself, amon ra recovery is enough for me.)
I agree it is an 'easy' shortcut that is not the best decision.. Like for example I think it killed my phone. I repaired permissions via rom manager, rebooted as it told me to and now my g1 wont boot past the g1 logo. I could install from a backup but the backup is 1+ month old (my error oops!). I am hoping to find a solution... Really dont wanna wipe everything..
warsng said:
i didn't want to get into this pointless discussion, but you have made a ****ty argument for rom mgr, you have confirmed that it doesn't work properly in certain circumstances, which is a good enough reason to not bother with it.
also, why shouldn't we rely on bad reviews? that's the point of a review, to give some idea about what experience to expect.
(i have never used it myself, amon ra recovery is enough for me.)
Click to expand...
Click to collapse
I made a perfectly good argument. Yes it can "mess up", but thats not at the fault of the app. It's at the fault of the phone. There are things that can go wrong that Koush cannot control. It is for ADVANCED users as a quick helpful UI for recovery-based operations. People that don't know what they're doing, or only half-way do shouldn't be using it. However, too many Android users *think* they are advanced enough, yet 5 minutes after using it, post a "PLEASE HELP, PHONE IS BROKEN", because they DON'T know what they're doing.
I'm not saying that all bad reviews are missguied, but I can assure that 90% of them are from noobs that have no idea what they're doing. They rooted their phone because someone told them it was cool, and they have absolutetly no idea whats in their hands and what they can do with it. Let alone, how to properly work it and fix problems. It's easy as pie to point out noobs from those crowds of users, those 3 links in the OP's post are all perfectly examples. People who came to XDA, signed up, never posted anything, then messed up and came crying to the board asking for help (usually in Android Development because people like them, and the OP too, don't how to to post in the correct section).
So for the last time, if you don't know what you're doing on your phone, don't do it. Just because you have root, and an app says "for root users", doesn't mean its for you, which EVERYONE assumes it is. It's piss-poor users like that, that ruin app reviews and the name of Android everywhere.
tehseano said:
I made a perfectly good argument. Yes it can "mess up", but thats not at the fault of the app. It's at the fault of the phone. There are things that can go wrong that Koush cannot control. It is for ADVANCED users as a quick helpful UI for recovery-based operations. People that don't know what they're doing, or only half-way do shouldn't be using it. However, too many Android users *think* they are advanced enough, yet 5 minutes after using it, post a "PLEASE HELP, PHONE IS BROKEN", because they DON'T know what they're doing.
I'm not saying that all bad reviews are missguied, but I can assure that 90% of them are from noobs that have no idea what they're doing. They rooted their phone because someone told them it was cool, and they have absolutetly no idea whats in their hands and what they can do with it. Let alone, how to properly work it and fix problems. It's easy as pie to point out noobs from those crowds of users, those 3 links in the OP's post are all perfectly examples. People who came to XDA, signed up, never posted anything, then messed up and came crying to the board asking for help (usually in Android Development because people like them, and the OP too, don't how to to post in the correct section).
So for the last time, if you don't know what you're doing on your phone, don't do it. Just because you have root, and an app says "for root users", doesn't mean its for you, which EVERYONE assumes it is. It's piss-poor users like that, that ruin app reviews and the name of Android everywhere.
Click to expand...
Click to collapse
Get a clue , its a program any gimp, including you, can install from the market, it is made in such way ...the fact that it dosent fail to write the recovery in fastboot mode means nothing!
This program shouldnt let the G1 user flesh any rec image. Till that happens it is the DEV's fault. Shouldnt be in the G1 CM's either.
Basically my phone is stuck on the GT-N7000 Samsung Logo screen.
Would love if somebody could make my day and tell me how I can restore my phone with it's pictures.
I know this is not as simple as it sounds but I have read a thread that explains something about non-wiping ROMs / upgrade ROMs? Is this true?
Notes:
I have a stock ROM (I bought the phone via Amazon Germany though).
Never tried to place another ROM onto phone.
I cannot go into recovery mode.
I am able to go into download mode.
I have heard of this ODIN but not familiar.
Heeelp!
This is a good thread to learn about odin
http://forum.xda-developers.com/showthread.php?t=1424997
Sent from my GT-I9500 using xda premium
nokiamodeln91 said:
This is a good thread to learn about odin
http://forum.xda-developers.com/showthread.php?t=1424997
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
501 pages to the thread don't suppose you know anything about upgrade ROM's?
Makkand said:
501 pages to the thread don't suppose you know anything about upgrade ROM's?
Click to expand...
Click to collapse
If you do not want to listen and do not want to read yourself (at least the first few posts with the tutorials) then why do you cry for help?
And answer in such an idiotic behavior?
Don't you think that it is this way of ignorance that is resulted in your "bricked" device?
ThaiDai said:
If you do not want to listen and do not want to read yourself (at least the first few posts with the tutorials) then why do you cry for help?
And answer in such an idiotic behavior?
Don't you think that it is this way of ignorance that is resulted in your "bricked" device?
Click to expand...
Click to collapse
Are you kidding me!? You're honestly a senior member? Calling my response idiotic is probably a little ironic. Let me explain why...
Firstly, I'm not going to waste too much of my time replying to you but my concern was that during the 501 pages of the thread something may changed from the start, I can't be sure how accurate the first posts are, which I feel is a valid point 1.
As for the bricked device, the phone became bricked itself due to no fault of my own, other people have experienced the same thing, I have avoided popping ROM's onto the phone to avoid voiding my warranty, I did not tamper with anything, this is valid point 2.
If you have nothing positive to contribute to this thread please refrain from adding any further comments, or take a chill pill and use a little empathy senior member.
I should also add that:
- I eeked at the 501 pages - I was not being condescending.
- I believe that there is a difference between ROM's that completely flash the whole memory and upgrade ROM's that will retain, hence why I asked the question, about 'upgrade' ROM's.
If you want to pull the pictures from the phone internal memory you can use a pc program called adb.exe, but you need to be in download mode.
Makkand said:
Are you kidding me!? You're honestly a senior member? Calling my response idiotic is probably a little ironic. Let me explain why...
Firstly, I'm not going to waste too much of my time replying to you but my concern was that during the 501 pages of the thread something may changed from the start, I can't be sure how accurate the first posts are, which I feel is a valid point 1.
As for the bricked device, the phone became bricked itself due to no fault of my own, other people have experienced the same thing, I have avoided popping ROM's onto the phone to avoid voiding my warranty, I did not tamper with anything, this is valid point 2.
If you have nothing positive to contribute to this thread please refrain from adding any further comments, or take a chill pill and use a little empathy senior member.
I should also add that:
- I eeked at the 501 pages - I was not being condescending.
- I believe that there is a difference between ROM's that completely flash the whole memory and upgrade ROM's that will retain, hence why I asked the question, about 'upgrade' ROM's.
Click to expand...
Click to collapse
Except he is right. This has been discussed. You're method is to read that thread. This is a website (or at least is supposed to be) for users that are willing to read the guides people have slaved to create
Everything you need to know is there.
And absent hardware failure, a phone doesn't brick itself.
Read dr.ketan thread on how to flash a stock ROM via PC Odin from download mode. The guide is current. This is the only answer you will receive here.
AndroidSlave said:
Except he is right. This has been discussed. You're method is to read that thread. This is a website (or at least is supposed to be) for users that are willing to read the guides people have slaved to create
Everything you need to know is there.
And absent hardware failure, a phone doesn't brick itself.
Read dr.ketan thread on how to flash a stock ROM via PC Odin from download mode. The guide is current. This is the only answer you will receive here.
Click to expand...
Click to collapse
Thai and AndroidSlave are right, if they are harsh they are being truthful and trying to help. Cherish their advice, the answer is there, lets not fight please.
Sent from my GT-N7000 using Tapatalk 2
rangercaptain said:
If you want to pull the pictures from the phone internal memory you can use a pc program called adb.exe, but you need to be in download mode.
Click to expand...
Click to collapse
Thanks Ranger Captain! Much appreciated. I'll look into this!
The expert on adb.exe is a user nemed studacris. I think it would be ok to PM him and get the specifics of the command.
Roughly, connect the phone to the pc in download mode, open a command window, navigate to your adb directory, type adb device to confirm the connection, then type adb pull \directory name\all files /directory on pc and the files will transfer from the internal phone memory to your pc.
AndroidSlave said:
Except he is right. This has been discussed. You're method is to read that thread. This is a website (or at least is supposed to be) for users that are willing to read the guides people have slaved to create
Everything you need to know is there.
And absent hardware failure, a phone doesn't brick itself.
Read dr.ketan thread on how to flash a stock ROM via PC Odin from download mode. The guide is current. This is the only answer you will receive here.
Click to expand...
Click to collapse
When you come across a 501 page thread and say the answer is there and current for people who are willing to read there is a bit of a problem here.
I was hoping a tech Guru on here who is familiar with my problem could help summarise key points relevant to my problem.
I am willing to concede after some of you have eluded to much of the information is in the first few pages. Thank you.
As for bricking - there has been corruption of what seems to be the firmware, which not is of the question, what point are you making? If you read a few other threads, others have experienced similar issues with attempting to update their ROM's.
baz77 said:
Thai and AndroidSlave are right, if they are harsh they are being truthful and trying to help. Cherish their advice, the answer is there, lets not fight please.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Sorry Tapatalk you have not taken my view into consideration at all. But I appreciate your intervention.
rangercaptain said:
The expert on adb.exe is a user nemed studacris. I think it would be ok to PM him and get the specifics of the command.
Roughly, connect the phone to the pc in download mode, open a command window, navigate to your adb directory, type adb device to confirm the connection, then type adb pull \directory name\all files /directory on pc and the files will transfer from the internal phone memory to your pc.
Click to expand...
Click to collapse
You are the man!! Thank you kindly!
Makkand said:
When you come across a 501 page thread and say the answer is there and current for people who are willing to read there is a bit of a problem here.
I was hoping a tech Guru on here who is familiar with my problem could help summarise key points relevant to my problem.
Click to expand...
Click to collapse
Hey man. All you need to do is read the first post of dr.ketan's thread. Good luck. If flashing a stock ROM via PC Odin doesn't work, per the isnstructions on that thread, I will personally be more than glad to help. But that IS your first step.
There is nothing to summarize. Follow the procedure in that thread OP. You don't have to read ANY of the thread except the guide. If it doesn't help you get up and running, feel free to PM me or post here. But when someone tells you to read a thread you must realize they are probably referring to the Original Post. If you are told to search (xda users rule #1), then that is a different story. For example, if you said 'how do I Use an OTG cable', I would say 'search this thread for the keyword otg'. Nevertheless, that is not the case here. There is a specific guide in the OP of that thread that describes what your first step to fix your device should be. Once that has been exhausted, please feel free to ask for further guidance.
Take care and good luck.
AndroidSlave said:
Hey man. All you need to do is read the first post of dr.ketan's thread. Good luck. If flashing a stock ROM via PC Odin doesn't work, per the isnstructions on that thread, I will personally be more than glad to help. But that IS your first step.
There is nothing to summarize. Follow the procedure in that thread OP. You don't have to read ANY of the thread except the guide. If it doesn't help you get up and running, feel free to PM me or post here. But when someone tells you to read a thread you must realize they are probably referring to the Original Post. If you are told to search (xda users rule #1), then that is a different story. For example, if you said 'how do I Use an OTG cable', I would say 'search this thread for the keyword otg'. Nevertheless, that is not the case here. There is a specific guide in the OP of that thread that describes what your first step to fix your device should be. Once that has been exhausted, please feel free to ask for further guidance.
Take care and good luck.
Click to expand...
Click to collapse
That was a meaningful considered response and appreciated, thank you.
Makkand said:
That was a meaningful considered response and appreciated, thank you.
Click to expand...
Click to collapse
did you solve your problem?
AndroidSlave said:
did you solve your problem?
Click to expand...
Click to collapse
I have seen that this is something that I need to sit down and concentrate on however I have not had a spare moment. I will have a crack at over the next few days and feedback in...most likely I will have more questions but watch this space!
AndroidSlave said:
did you solve your problem?
Click to expand...
Click to collapse
I was reading. There is something not quite clear. Although the thread tells you a lot about how to do something, it doesn't say what it does or what it's for.
I've downloaded the software but further threads highlight that data may still be deleted.
Would you mind advising of how the thread can ensure that my data will not be deleted?
Makkand said:
I was reading. There is something not quite clear. Although the thread tells you a lot about how to do something, it doesn't say what it does or what it's for.
I've downloaded the software but further threads highlight that data may still be deleted.
Would you mind advising of how the thread can ensure that my data will not be deleted?
Click to expand...
Click to collapse
Which data you refer to?
Question: is your data nor backed up via Google?
As for SD card data, like photos, is that what you're talking about?
I have the model SM-G920T S6, I was attempting to root my phone and must of used the wrong file and now its stuck in bootloop with "Recovery Is Not Seandroid Enforcing" in red in the upper left corner. I've attempted to put it into recovery mode to flash my ROM...which it wouldn't allow me. I'm not quite sure how to fix this issue, I've been trying some videos I've seen on YouTube with no results. Does anyone know the way to fix this?
Use ODIN "Attached below" Flash the Stock ROM: https://www.androidfilehost.com/?fid=24269982086998283
That will get it back to Stock.. Just select AP
Then use odin to flash recovery..
Edit any recovery other than Stock will give you "Recovery Is Not Seandroid Enforcing", anyone with a custom recovery will have the same notification.. If you need further assistance, feel free to PM me..
Also, you asked a very easy question that you could of done on your own time, we all learned the same way..
XDA is not a place where simple questions get answered trust me on that one..
I managed to get it to work last night after a bit of messing around on Odin. Thank you for the help though, I am new to the whole rooting phones, flashing the ROM, etc. Gradually learning but there are a many of things I don't know how to proficiently do.
Tcrazz said:
I managed to get it to work last night after a bit of messing around on Odin. Thank you for the help though, I am new to the whole rooting phones, flashing the ROM, etc. Gradually learning but there are a many of things I don't know how to proficiently do.
Click to expand...
Click to collapse
Flashing is a very dangerous thing to the uninitiated, before attempting to do something that can make your 700 dollar device into a worthless brick..
It is good to read as much as you can, don't rush the process or you will end up here asking a question that no one will answer..
I know because everytime I ask a question that to me appears to be legit, it ends up being ignored..
Now not everyone will ignore, but a good 98 percent will.. XDA is not a Support site, its a development directed at development..
Zaphodspeaks said:
Flashing is a very dangerous thing to the uninitiated, before attempting to do something that can make your 700 dollar device into a worthless brick..
It is good to read as much as you can, don't rush the process or you will end up here asking a question that no one will answer..
I know because everytime I ask a question that to me appears to be legit, it ends up being ignored..
Now not everyone will ignore, but a good 98 percent will.. XDA is not a Support site, its a development directed at development..
Click to expand...
Click to collapse
Are there any sites that you might suggest that would help me learn a bit more. At the moment I have just been trying to root my phone before attempting anything else.
Someone has to do something about this. Beginners like myself are bricking their phones every day and getting frustrated. Sure there is a fix but with how hard this is to learn for beginners its really frustrating.
Edit: This was meant to try to help beginners understand that the chainfire root method is for Lollipop and not for Marshmallow. I do not believe this should be taken down, just labeled for Lollipop so beginners don't soft brick their phones using this guide on a phone with Marshmallow.
Clay said:
Someone has to do something about this. Beginners like myself are bricking their phones every day and getting frustrated. Sure there is a fix but with how hard this is to learn for beginners its really frustrating.
Click to expand...
Click to collapse
root process for lollipop..
unlock your bootloader
fastboot flash twrp recovery
flash supersu via your new recovery
reboot and youll have root.
how hard is that? if its too hard, id suggest doing some reading about the process first, its all over google.
There's a new post every day about someone following the root process for lollipop when they have Marshmallow. I am far from computer illiterate and from the number of posts on this I think it speaks for itself.
At least label it more obviously that it's for lollipop.
I used chainfires root method and personally I don't see how anyone that's got a brain could screw this up. All ya gotta do is read and read then read some more. It's not hard people's . Chainfires method is about as simple as it can get. @Chainfire is a genius I hope he doesn't see this post, hell I'm embarrassed for him.
Sent from my HTC6600LVW using Tapatalk
the difference bwtween lollipop and marshmallow is that you also have to flash a custom kernel in twrp right before you flash supersu. besides that, its identicle.
I'm agree with you if you're talking about Android M. It's really crazy.
But as far as I remember, there was no notable obstacle on LP version root.
Unlock bootloader. Flash recovery and flash supersu....any other step?
If they are not familiar with adb, I guess they may face trouble. Actually the problem occurs from the start at downloading adb tool(platform_tools on SDK) with that sucking google tool.
..However, if they are, they shouldn't do root. It's too risky if they don't even know the basics.
So the instructions for how to root lollipop should be removed because some people don't take the time to read everything and confirm which version of Android they have on their phone?
PielunA said:
I'm agree with you if you're talking about Android M. It's really crazy.
But as far as I remember, there was no notable obstacle on LP version root.
Unlock bootloader. Flash recovery and flash supersu....any other step?
If they are not familiar with adb, I guess they may face trouble. Actually the problem occurs from the start at downloading adb tool(platform_tools on SDK) with that sucking google tool.
..However, if they are, they shouldn't do root. It's too risky if they don't even know the basics.
Click to expand...
Click to collapse
actually, wrong. if you have issues with adb, thats nice, but adb has NOTHING to with rooting a nexus device. rooting uses fastboot, not adb.
---------- Post added at 01:01 PM ---------- Previous post was at 12:59 PM ----------
Rodeojones said:
So the instructions for how to root lollipop should be removed because some people don't take the time to read everything and confirm which version of Android they have on their phone?
Click to expand...
Click to collapse
removed, no. it should stay to show the history of rooting, among other things. but people should edicate themselves before ever rooting their devices. stupid people isnt an excuse to get rid of our history.
simms22 said:
actually, wrong. if you have issues with adb, thats nice, but adb has NOTHING to with rooting a nexus device. rooting uses fastboot, not adb.
---------- Post added at 01:01 PM ---------- Previous post was at 12:59 PM ----------
removed, no. it should stay to shiw the history of rooring, among other things. but people should edicate themselves before ever rooting their devices. stupid people isnt an excuse to get rid of our history.
Click to expand...
Click to collapse
Ah.. you're right. Fastboot flash and unlock, right. I was talking about Android SDK(platform-tools) but it seems that I mistaked it, since I'm with adb console window for pulling something now(..)
PielunA said:
Ah.. you're right. Fastboot flash and unlock, right. I was talking about Android SDK(platform-tools) but it seems that I mistaked it, since I'm with adb console window for pulling something now(..)
Click to expand...
Click to collapse
thats alright.. seems as most accidentally say adb instead of fastboot, which isnt a big deal. unless youre a new user and keep trying to use adb to root.
Hey just trying to help the beginners. Take a look at this thread and tell me where it mentions its for lollipop.
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Or where it mentions its not for Marshmallow. I'll save you the trouble. Nowhere.
I don't deserve all the ignorant remarks here. Uncalled for.
Some of you are right, taking it down is not the right path, but mentioning what version of Android its for is the right path.
Clay said:
Hey just trying to help the beginners. Take a look at this thread and tell me where it mentions its for lollipop.
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Or where it mentions its not for Marshmallow. I'll save you the trouble. Nowhere.
I don't deserve all the ignorant remarks here. Uncalled for.
Some of you are right, taking it down is not the right path, but mentioning what version of Android its for is the right path.
Click to expand...
Click to collapse
then you have to think when it was written.. before marshmallow. before marshmallow, rooting was exactly the same for any nexus, all the way back to the nexus one. they had no idea that marshmallow would change things. what we can do as people is inform others of the changes.
Look at it from a beginners standpoint, which this site is always going to have plenty of. For them to know all that you mentioned is asking a lot. I am no longer going to bicker with everyone in this thread. Just wanted to help the beginners and share my view point as a beginner. I have learned a lot and appreciate all those that contribute to this site. Looking forward to rooting my phone and trying out some roms. Have a good day all.
Clay said:
Someone has to do something about this. Beginners like myself are bricking their phones every day and getting frustrated.
Click to expand...
Click to collapse
I can imagine your disappointment or frustration. But I can't agree with this post.
New things or methods do not need to work immediately for 100%. It is a process of creating, trial and error. And make things better every time. Stopping this process is fortunately impossible, but it should be also wrong. Because it's a free choice for everyone to be a part of it or not.
simms22 said:
then you have to think when it was written.. before marshmallow. before marshmallow, rooting was exactly the same for any nexus, all the way back to the nexus one. they had no idea that marshmallow would change things. what we can do as people is inform others of the changes.
Click to expand...
Click to collapse
NLBeev said:
I can imagine your disappointment or frustration. But I can't agree with this post.
New things or methods do not need to work immediately for 100%. It is a process of creating, trial and error. And make things better every time. Stopping this process is fortunately impossible, but it should be also wrong. Because it's a free choice for everyone to be a part of it or not.
Click to expand...
Click to collapse
So you believe that labeling a root method with the version of Android it works for and which version the method knowingly soft bricks you phone is not a good idea? Brilliant.
Clay said:
So you believe that labeling a root method with the version of Android it works for and which version the method knowingly soft bricks you phone is not a good idea? Brilliant.
Click to expand...
Click to collapse
well, if you root marshmallow the way you root any other nexus before marshmallow, it wont soft brick the device, it just wont gain root. i guess a soft brick is possible, but thats an easy fix. if it hard bricked devices, then thats a different story. but a soft brick can happen in a typical day of modding your device, and learning to fix a soft brick should be done before ever rooting your device.
Clay said:
Someone has to do something about this. Beginners like myself are bricking their phones every day and getting frustrated. Sure there is a fix but with how hard this is to learn for beginners its really frustrating.
Edit: This was meant to try to help beginners understand that the chainfire root method is for Lollipop and not for Marshmallow. I do not believe this should be taken down, just labeled for Lollipop so beginners don't soft brick their phones using this guide on a phone with Marshmallow.
Click to expand...
Click to collapse
Just read. Seriously. The last 10-20 pages of that thread are non-stop warnings and info, repeated over and over and over and over.
When you follow a guide, check the date, check the versions applicable, and read recent commentary for up-to-date information. If that is two hard, XDA DEVELOPERS is too hard for you...
Lets not encourage people to rampantly flash anything unless it has flashing red warnings... That is the wrong mentality. People should learn enough to understand what they are doing, not just be encouraged to follow the flashing red arrows.
We have the guide that we have, because it was the last one someone took the time to write, or because no one has written one the matches it since. All the information is in it... Even if you maybe have to read more then one post.
If you don't make something better, you have little right to complain. Its open source community development. We only have the things people made for us.
how i see any android mods or ways you do things.. if its 1 month or older, i assume that its out of date first. if no newer ways exist, then i try it. but i always make a backup in my recovery first, just in case. things move by within android relatively fast, so one month old can easily be out of date.
OK everyone. I get it. I am a beginner and should have gained complete knowledge of everything rooting and Android before starting this process.
I started this thread to try to help beginners that seem to, on a daily basis, use the chainfire root method on Marshmallow and soft brick their phones. Nothing more, nothing less. If having interest in helping these guys out before they go down the wrong road is wrong then tell me what is right. I am walking away from this thread as nothing good will come of it.
Clay said:
OK everyone. I get it. I am a beginner and should have gained complete knowledge of everything rooting and Android before starting this process.
I started this thread to try to help beginners that seem to, on a daily basis, use the chainfire root method on Marshmallow and soft brick their phones. Nothing more, nothing less. If having interest in helping these guys out before they go down the wrong road is wrong then tell me what is right. I am walking away from this thread as nothing good will come of it.
Click to expand...
Click to collapse
theres much good that has come from this thread already!
anyways, i learned all that i could learn before i ever first rooted(to an extreme maybe). i started with android two weeks before the g1 ever was released(got mine two weeks early). at the time, nobody knew anything about android. so, we all learned along the way. before rooting, i became the leader in the biggest android forums(at the time). only about 6 months after, i rooted my g1, before any legit root method ever existed. we learned, and we taught.. before any real methods existed. now that there are real methods, they change constantly as well, so we keep on learning and teaching