Related
I feel I've made a terrible (and stupid) mistake. I decided to unroot my phone from cyanogen roms. I read a how to guide that I guess was outdated because now I have android 1.0 firmware. The guidw was [how to] unroot by tubaking182 (absolutely zero offense to him, not his fault, I'm stupid, etc etc.) So I now have stock version 1.0. There's no check for system updates under about phone in settings so I can't do that. There are file manager apps that I could use to rename the necessary updates into update.zip, but there's no apps available like download crutch so I can download them. I also can't enter recovery. It gives me a triangle with an exclamation inside next to a image of a phone and that's it and I have no idea how to install an update without recovery mode. As I'm sure you've noticed by now, I'm the epitome of newb and feel free to laugh at my failure. I just really need someone to help me and would be eternally grateful. In all likelihood, I'll need step by step instructions on what to do. I know this is a lot to ask and I've really done nothing to earn this help... I really just need assistance. Thank you to anyone who helps me in advance
Not to be an asshole and say "Shoulda Coulda Woulda" but you really should have done your research before embarking on bricking your phone.
ItsAndroidsWorld had many videos on You Tube. Look for ones on how to root, then how to install the death spl, then look for the ones with Super D or FastTest .. as it seems as though they are probably the best roms for everyday use at this point.
I've found that using these videos via You Tube is the easiest way to go.
Good Luck.
^^^ ABOVE POST stolen from another similar thread.
psyko-m1 said:
Not to be an asshole and say "Shoulda Coulda Woulda" but you really should have done your research before embarking on bricking your phone.
Click to expand...
Click to collapse
he didn't brick his phone, don't scare him
To OP: The same happened to me when I was a n00b at this ****.
Dude, google is your friend.
Calm down.
tsk tsk tsk.....Im gonig to say this....WRONG SECTION
but I will be nice as well. just find the updates on google from 1.0 to 1.5 and oh yeah to get back into recovery from the triangle withthe !...alt L...but if you somehow brick ya phone youe fault not mine next time do ya research before you mess with ya phone
Technically speaking he is in a DEFCON 2 "Brick" situation.
Sorry.
psyko-m1 said:
Technically speaking he is in a DEFCON 2 "Brick" situation.
Sorry.
Click to expand...
Click to collapse
Well he's in the wet cement
SeEsAw12 said:
Well he's in the wet cement
Click to expand...
Click to collapse
Or...
You are late for work and have a flat...
click on this http://theunlockr.com/category/howto/android_how_tos/htc-mytouch-3g-magic/:cool:
remove the cool http://theunlockr.com/category/howto/android_how_tos/htc-mytouch-3g-magic/
this website should help you get back on track and you just need to download the nbh file to get it back to cupcake
BUT 0MGAWWZZZ N00BZORZ DO3S 1.0 HAVE A DA SENSE RAOM???
in all seriousness, there's nothing actually wrong with your phone. You completely unrooted it. By following the aforementioned instructions, it'll be easy to reroot and update. What I DO find weird is why you're not getting 1.5 OTA...
although i hate when people post in the wrong section - im in a good mood this morning
http://zenthought.org/content/project/flashrec
not sure if it works in 1.0 - it should as it uses a rather old bug to do so
Easy as pie...just follow the guide in my sig.
=)
To those who say I bricked it, I know that's not the case it still works so I obviously didn't brick it... not that fail thankfully.
To thenameismax, AHA! I did not know about alt+l retrieving text so thank you thank you thank you. I just need to get the necessary updates and copy them to sd card root, rename update.zip/install one at a time... I think lol
Thanks again to all who helped and sorry about the wrong section. When I was rooting, it was in development. I assumed that unrooting would be too and therefore problems with that... further fail.
afiellerddr said:
To those who say I bricked it, I know that's not the case it still works so I obviously didn't brick it... not that fail thankfully.
To thenameismax, AHA! I did not know about alt+l retrieving text so thank you thank you thank you. I just need to get the necessary updates and copy them to sd card root, rename update.zip/install one at a time... I think lol
Thanks again to all who helped and sorry about the wrong section. When I was rooting, it was in development. I assumed that unrooting would be too and therefore problems with that... further fail.
Click to expand...
Click to collapse
yeah man no problem. good luck.
Don't do anything. In a day or two you get an OTA update.
You can force the update like people have mentioned, but as long as you can hold off for a day or two you dont need to.
BTW, at some point you will see the E or 3G icon downloading like crazy and you dont know why. It is downloading the update. Stay away from task killers and in my experience it is good to be around wifi.
Just relax.
Sent Move Request
stubled upon this article instructing users on how to get rooted and install ClockWorkMod through ROM Manager? what? are those guys kidding us.. they just want users to brick their mobiles..
so, androidauthority.com - follow this and you got a bricked mobile.
don't kill the business and do not brick users mobile phones.
your article leads users to brick their mobile, which is not kindly at all. or maybe that website is just anti-LG, could be?
Your article is BS and is lousy journalism and untrustworthy.
extract from their article
You can also download ROM Manager and flash the latest ClockworkMod Recovery, as it should only be a matter of time before we start to see custom ROM’s.
Click to expand...
Click to collapse
- this WILL brick users mobile, if possible.
At least they also mention to update supersu ... something I didn't know
Btw: How does CWM work? I have it on my old 2X, but I never quite understood how it works, where it installs itself and why it is model dependent...
voon said:
At least they also mention to update supersu ... something I didn't know
Btw: How does CWM work? I have it on my old 2X, but I never quite understood how it works, where it installs itself and why it is model dependent...
Click to expand...
Click to collapse
CWM resides on the 'recovery' partition of the handset. A recovery is used to recover your phone in the event of a failure, or to flash an update. CWM overwrites your 'stock' recovery, and allows you to issue more commands to the phone. The largest benefit to CWM, however, is that it can flash unsigned packages, which is how you install a custom, non-OEM verified ROM
Hope this helps!
This is so true. It happened with the nitro HD as well. They instructed is to push the recovery image to the secondary boot loader causing us to get permabricked; I had to send my phone to lg repair.
Sent from my LG-P930 using xda premium
i would have no problems if they instructed on the rooting part alone, but they moved on to how easy it was to get cwm working, thats a bummer.
but ok, i admit, that koush probably would not allow ANY user to install a cwm on a model they did not support anyways. but leading some users to believe it would work.
Dexter_nlb said:
stubled upon this article instructing users on how to get rooted and install ClockWorkMod through ROM Manager? what? are those guys kidding us.. they just want users to brick their mobiles..
so, androidauthority.com - follow this and you got a bricked mobile.
don't kill the business and do not brick users mobile phones.
your article leads users to brick their mobile, which is not kindly at all. or maybe that website is just anti-LG, could be?
Your article is BS and is lousy journalism and untrustworthy.
extract from their article
- this WILL brick users mobile, if possible.
Click to expand...
Click to collapse
Hey Dexter. I write for Android Authority. I did not write he article, but I will look into what you have mentioned and make sure the article gets updated. We can't publish content that could potentially harm a users device due to incorrect instructions. I wish I would have found this earlier. Maybe next time you could reply in the comments on said article so we could resolve the issue. Thanks again for the heads up!
Dexter_nlb said:
stubled upon this article instructing users on how to get rooted and install ClockWorkMod through ROM Manager? what? are those guys kidding us.. they just want users to brick their mobiles..
so, androidauthority.com - follow this and you got a bricked mobile.
don't kill the business and do not brick users mobile phones.
your article leads users to brick their mobile, which is not kindly at all. or maybe that website is just anti-LG, could be?
Your article is BS and is lousy journalism and untrustworthy.
extract from their article
- this WILL brick users mobile, if possible.
Click to expand...
Click to collapse
Dexter, I wrote the article, and it was an honest mistake to include the CWM part. I have addressed the issue in the article. Trust me, I intend to help people, and our website is far from "anti-LG" and I am even further away from "wanting users to brick their mobiles". It was just an incorrect statement, and I meant no harm by posting. My apologies, this was my fault not the fault of Android Authority.
*edit* - also, I do not have the device on hand as I sent it to a co-worker, but could you explain to me why the flashing of CWM would brick your phone? I'm almost positive I did it, and my phone was perfectly fine.
-Clayton Ljungberg
ljungberg3 said:
*edit* - also, I do not have the device on hand as I sent it to a co-worker, but could you explain to me why the flashing of CWM would brick your phone? I'm almost positive I did it, and my phone was perfectly fine.
-Clayton Ljungberg
Click to expand...
Click to collapse
Tegra3 devices got a SBK(secure boot key) + encrypted partitions and it has a checksum of boot/recovery partitions, so if changed/updated the device will go into a brick state,claiming you cannot boot (RED big warning).
so with additional hacks , experienced users can unbrick the device using firmware upgraders. but otherwise just sending it back to the shops is the only way out, for regular owners without xda experience.
currently o4x is a locked device for boot and recovery partition changes, so no writing of recovery partition unless its signed with the signature key, which no one would own unless developing for o4x internals.
note/fyi,
the CWM i did, is not an image and its only bootstrap based, using a trick to re-load init process, so it retain the original recovery partition.
Dexter_nlb said:
Tegra3 devices got a SBK(secure boot key) + encrypted partitions and it has a checksum of boot/recovery partitions, so if changed/updated the device will go into a brick state,claiming you cannot boot (RED big warning).
so with additional hacks , experienced users can unbrick the device using firmware upgraders. but otherwise just sending it back to the shops is the only way out, for regular owners without xda experience.
currently o4x is a locked device for boot and recovery partition changes, so no writing of recovery partition unless its signed with the signature key, which no one would own unless developing for o4x internals.
note/fyi,
the CWM i did, is not an image and its only bootstrap based, using a trick to re-load init process, so it retain the original recovery partition.
Click to expand...
Click to collapse
Well thank you for clarifying, I must have also installed the bootstrap based CWM, as I did have CWM recovery. I downloaded and assumed that I updated cwm through rom manager. Again, to clarify - I meant no harm in posting the article. I am not anti-LG, and I don't want users to brick their phones. I can say for a fact that the root guide is solid other than the CWM reference (which was one sentence within the entire article, mind you)
ljungberg3 said:
(which was one sentence within the entire article, mind you)
Click to expand...
Click to collapse
all it takes is a one-liner!
As i also mentioned previously, i found the article ok, if it was not for the mention of cwm was next step to get it rollling. but good is that you corrected it.
Dexter_nlb said:
all it takes is a one-liner!
As i also mentioned previously, i found the article ok, if it was not for the mention of cwm was next step to get it rollling. but good is that you corrected it.
Click to expand...
Click to collapse
Yes, I did correct it. We want to help our readers as much as possible. I hope that you can hold our website in higher regard than you did previously, when you posted the thread.
ljungberg3 said:
Well thank you for clarifying, I must have also installed the bootstrap based CWM, as I did have CWM recovery. I downloaded and assumed that I updated cwm through rom manager. Again, to clarify - I meant no harm in posting the article. I am not anti-LG, and I don't want users to brick their phones. I can say for a fact that the root guide is solid other than the CWM reference (which was one sentence within the entire article, mind you)
Click to expand...
Click to collapse
Just thinking...
Could it be that you got hold of one of the developer models, and that's why you were able to install CWM via rom manager??
When we first tried to get root, someone made a guide on here. Turned out it only worked for him because he had an unlocked developers phone running software version V08(someting more I don't remember)...
But as I said, just a thought!!!
m_primdahl said:
Just thinking...
Could it be that you got hold of one of the developer models, and that's why you were able to install CWM via rom manager??
When we first tried to get root, someone made a guide on here. Turned out it only worked for him because he had an unlocked developers phone running software version V08(someting more I don't remember)...
But as I said, just a thought!!!
Click to expand...
Click to collapse
I don't have the phone anymore... but I did have a device sent directly from LG as a review device. So, it could have been a dev model.
I always use http://tutznet.com and XDA Developers website for Android Tuts, I have been reading this Android Authority site for a while, looks like one of their writer wrote this crappy article without knowing about it.
Utkarsh.bhatt12 said:
I always use http://tutznet.com and XDA Developers website for Android Tuts, I have been reading this Android Authority site for a while, looks like one of their writer wrote this crappy article without knowing about it.
Click to expand...
Click to collapse
Good one. I wrote the first article on the web about how to root the Optimus 4X HD. I even made the video that is in the article, so don't tell me I don't know what I'm doing.
That might seem like a silly title, but I do have decent reason to ask.
Now, before I start - I have given the forums a nice search. I did check the Wiki. Believe me, XDA's "You're a noob" video gave me enough of a fright to search more thoroughly than I normally would.
Unfortunately, I couldn't find what an answer I was looking for. Either I wasn't broad enough, or I'm among the first to ask.
Even now, I'm not sure if I should be making an entirely new thread, or posting in the 'Ask Any Question' thread.
Either way, since I'm here...
I'm currently running a rooted Xperia Z firmware 4.1.2 with the bootloader locked. I am aware of the most recent firmware update, 4.2.2.
Now, I've only been in the experience of rooting for a little while. The Z is really my first rooted phone, and as such, I haven't got my head wrapped around over what it means to upgrade, or otherwise update a rooted device. Still learning, heh.
Now, I understand that there's a risk - If not a certainty - That if I take the official update, I will lose my root access.
That's all fine and dandy since I'm also aware of DooMLoRD's rootkit update for this software version.
What I'm mostly worried about there though is the fact that the rootkit installs BusyBox.
I already have this installed, and I know it's risky to uninstall it. However, installing it over a current installation sounds like it's going to cause so much unwanted chaos.
So... I really could do with some advise on that.
Also, perhaps this is personal paranoia, but I could do with the reassurance. Taking that update -is- safe enough for my device, considering it's rooted, right? Again, I'd probably lose root access, but is that the only risk?
I'm not gonna end up downloading it and find that the phone won't turn on due to some error caused by the fact that my phone was rooted, am I?
Thanks for reading,
- Sytheriseida
Yes.
...Sent from Zed
XperienceD said:
Yes.
...Sent from Zed
Click to expand...
Click to collapse
... Not particularly helpful, but thanks anyway.
Sytheriseida said:
... Not particularly helpful, but thanks anyway.
Click to expand...
Click to collapse
Sorry, on my Phone. Asking if its safe to update is a bit of a poor question which the short answer is yes. The stickys or existing threads should be the first port of call for most People learning about a new device.
...Sent from Zed
XperienceD said:
Sorry, on my Phone. Asking if its safe to update is a bit of a poor question which the short answer is yes. The stickys or existing threads should be the first port of call for most People learning about a new device.
...Sent from Zed
Click to expand...
Click to collapse
What I mostly meant was if it was safe considering the setup of my phone.
I can understand that it was a poor question - Hence, personal paranoia.
Thanks for tolerating it, heh.
Yeah, I saw the threads regarding such information. But I guess I wanted to be absolutely certain.
That's not a very good excuse, I know. But it's the only one I have.
A bit too paranoid. Just backup your Phone the best you can then go from there, if it goes wrong it's easily sorted by using the flashtool.
...Sent from Zed
XperienceD said:
A bit too paranoid. Just backup your Phone the best you can then go from there, if it goes wrong it's easily sorted by using the flashtool.
...Sent from Zed
Click to expand...
Click to collapse
Perhaps, but BusyBox caused me so much chaos in the past due to a double-installation. I was at the point in which I couldn't get it to connect to the computer to flashtool it to fix the damn thing, so my paranoia is fair. XD
UPDATE.
I went ahead and installed the firmware update. As I thought, I've lost root access. Which is fine.
But BusyBox is still installed, heh. Figures.
So I need to know whether DoomLoRD's rootkit would be safe to use in this case.
Advise?
Thanks.
Just go ahead and update. I was also rooted with bootloader locked, and updated via PC Companion and then used DooMLoRD's kit. No problems at all.
hush66 said:
Just go ahead and update. I was also rooted with bootloader locked, and updated via PC Companion and then used DooMLoRD's kit. No problems at all.
Click to expand...
Click to collapse
I took your word for it, and gave the installer a try.
I guess I didn't have anything to worry about after all. I guess I'm set for a good little while, then.
XperienceD, hush66, thank you very much for your help. You've been beyond calming.
Consider this [Resolved.]
Just bought a brand new N6 and its not downloading any ota's, still on 5.0. The build is LNX07M which is a developer build and apparently will not download any ota's. Has anyone heard of this? Did a quick Google search and there is hardly anything about this build.
I have no access to a computer, am I stuck on this build and 5.0?
csdaytona said:
Just bought a brand new N6 and its not downloading any ota's, still on 5.0. The build is LNX07M which is a developer build and apparently will not download any ota's. Has anyone heard of this? Did a quick Google search and there is hardly anything about this build.
I have no access to a computer, am I stuck on this build and 5.0?
Click to expand...
Click to collapse
no access at all?
simms22 said:
no access at all?
Click to expand...
Click to collapse
Not at the moment. What will I need to do?
This is my first nexus device and the last phone I rooted/flashed was the G1 way back in the day.
I was excited to get my phone today so this kind of sucks....
csdaytona said:
Not at the moment. What will I need to do?
This is my first nexus device and the last phone I rooted/flashed was the G1 way back in the day.
I was excited to get my phone today so this kind of sucks....
Click to expand...
Click to collapse
ohh.. that sucks. i remember my g1
i have a way that will probably work out fine, but this way is highly looked down upon on xda. would you be willing to try? btw, im one of those that would look down on this way, unless in certain situations..
simms22 said:
ohh.. that sucks. i remember my g1
i have a way that will probably work out fine, but this way is highly looked down upon on xda. would you be willing to try? btw, im one of those that would look down on this way, unless in certain situations..
Click to expand...
Click to collapse
OK what is it and why is it frowned upon?
csdaytona said:
OK what is it and why is it frowned upon?
Click to expand...
Click to collapse
because its not "proper", and normally isnt used properly. but ill explaine to you the proper way. you can try an app called kingsroot. you csnt get it at the play store, youll have to search google for it. after you install it, then run it, youll have root. but, youre not done yet. you will want to download the latest twrp recovery for the nexus 6 with your phone and keep it there. then you will unstall flashify from the play store. you will now use flashify to flash the twrp recovery. now, last thing, to get your bootloader unlocked. you will install any bootloader unlock apps, like boot unlocker or similar(that might delete everything from your phone), then youre done. ive never tried this on a nexus, but have on other devices, just so you know.
simms22 said:
because its not "proper", and normally isnt used properly. but ill explaine to you the proper way. you can try an app called kingsroot. you csnt get it at the play store, youll have to search google for it. after you install it, then run it, youll have root. but, youre not done yet. you will want to download the latest twrp recovery for the nexus 6 with your phone and keep it there. then you will unstall flashify from the play store. you will now use flashify to flash the twrp recovery. now, last thing, to get your bootloader unlocked. you will install any bootloader unlock apps, like boot unlocker or similar(that might delete everything from your phone), then youre done. ive never tried this on a nexus, but have on other devices, just so you know.
Click to expand...
Click to collapse
That seems like a lot of work. If I can get to a computer tomorrow, what can I do then?
Btw, thanks for helping me out.
csdaytona said:
That seems like a lot of work. If I can get to a computer tomorrow, what can I do then?
Btw, thanks for helping me out.
Click to expand...
Click to collapse
If you can get to a computer, download this: https://dl.google.com/dl/android/aosp/shamu-mra58k-factory-5b07088c.tgz
It's the Marshmallow (6.0) factory image for the Nexus 6. Run the batch file inside and it'll flash your phone. Note that this WILL wipe it.
Here's the actual Google-supplied information on it: https://developers.google.com/android/nexus/images?hl=en
|Jason8| said:
If you can get to a computer, download this: https://dl.google.com/dl/android/aosp/shamu-mra58k-factory-5b07088c.tgz
It's the Marshmallow (6.0) factory image for the Nexus 6. Run the batch file inside and it'll flash your phone. Note that this WILL wipe it.
Here's the actual Google-supplied information on it: https://developers.google.com/android/nexus/images?hl=en
Click to expand...
Click to collapse
First time doing this, but it's OK to jump straight to 6.0?
csdaytona said:
First time doing this, but it's OK to jump straight to 6.0?
Click to expand...
Click to collapse
It'll be fine. It's the complete system image, so it doesn't matter what you're on currently. Note that you will have to install all sorts of extra crap to get the Android SDK installed and working and the proper drivers, but it's not that hard, just gigs of downloads when everything is all said and done.
Like I said, it WILL wipe your phone completely.
csdaytona said:
That seems like a lot of work. If I can get to a computer tomorrow, what can I do then?
Btw, thanks for helping me out.
Click to expand...
Click to collapse
if you can get to a computer..
you can unlock your bootloader with "fastboot oem unlock"
then fastboot flash twrp recovery
then flash a custom kernel wiyh the latest supersu in your new recovery.
and then boot up with root, an unlocked bootloader, and a custom recovery
|Jason8| said:
It'll be fine. It's the complete system image, so it doesn't matter what you're on currently. Note that you will have to install all sorts of extra crap to get the Android SDK installed and working and the proper drivers, but it's not that hard, just gigs of downloads when everything is all said and done.
Like I said, it WILL wipe your phone completely.
Click to expand...
Click to collapse
Not worried about wiping the phone, I've literally only had it for a few hours and nothing is loaded on it.
Would be possible to just install an ota to get me on the right upgrade path? I'm just trying to do the quickest and easiest method possible.
csdaytona said:
Not worried about wiping the phone, I've literally only had it for a few hours and nothing is loaded on it.
Would be possible to just install an ota to get me on the right upgrade path? I'm just trying to do the quickest and easiest method possible.
Click to expand...
Click to collapse
If it's not grabbing an OTA, not sure what else you can do, short of downloading all the OTAs and flashing via recovery. But no guarantee that'll work as you're on a development build... There probably isn't an OTA to go from your development build to a release build.
csdaytona said:
I have no access to a computer, am I stuck on this build and 5.0?
Click to expand...
Click to collapse
simms22 said:
no access at all?
Click to expand...
Click to collapse
csdaytona said:
Not at the moment.
Click to expand...
Click to collapse
csdaytona said:
That seems like a lot of work. If I can get to a computer tomorrow, what can I do then?
Click to expand...
Click to collapse
Dude, come on... I know this is the Q&A section, and were supposed to be nicer here... But this lazyness is bull****.
You act like using a computer is impossible, then as soon as it takes some work.... You can get at one the next day?
Stop expecting to be spoon fed and at least try to learn something fist. There are a TON of write ups on how to do this. You spend how much money on a phone, and now you don't care to educate yourself on it?
Instead of expecting other to do all the work for you, read through the stickied index thread in the general section
http://forum.xda-developers.com/nexus-6/general/nexus-6-index-thread-t3229412
It has a newbie guide that literally holds your hand through the whole process. Post 2 has info on "how to flash factory images", use method 2 as method 1 in that thread will not work with the MM factory image.
Nice people have already spend a lot of time and effort documenting these things for you, as they are common questions. People like Simms and the other posters in this thread answer questions and offer support for free out of the kindness of their heart... Don't create extra work for them by ignoring all the effort already put out by other members, expecting it all to be regurgitated to you.
|Jason8| said:
If it's not grabbing an OTA, not sure what else you can do, short of downloading all the OTAs and flashing via recovery. But no guarantee that'll work as you're on a development build... There probably isn't an OTA to go from your development build to a release build.
Click to expand...
Click to collapse
Fastboot, as described in the threads mentioned above, will completely overwrite the pertinent partitions, regardless of what was there... dev build or not. No need to flash and apply countless incremental updates. Google provides not only full system images, but the information to use them on their web page...
|Jason8| said:
If it's not grabbing an OTA, not sure what else you can do, short of downloading all the OTAs and flashing via recovery. But no guarantee that'll work as you're on a development build... There probably isn't an OTA to go from your development build to a release build.
Click to expand...
Click to collapse
Gotcha. I'll try to flash 6.0 tomorrow. Wish me luck.
Thanks for the help!
scryan said:
Fastboot, as described in the threads mentioned above, will completely overwrite the pertinent partitions, regardless of what was there... dev build or not. No need to flash and apply countless incremental updates. Google provides not only full system images, but the information to use them on their web page...
Click to expand...
Click to collapse
I linked him to that already. No need to be a **** about it. He was looking for an easy way to do it now, when he doesn't have a computer. **** got crazy, so he asked if it would be easier with a computer, which the answer is yes.
Wouldn't you be excited as **** if you had a new phone? Wouldn't you want to get it up and running as quickly as possible? Well... now he's gotta wait until he has a computer. Obviously installing an OTA and doing the incremental updates would be easier, which is what he was looking for. Since that's not an option, we laid out other ways to go about doing it. So he's getting to a computer tomorrow.
---------- Post added at 09:51 PM ---------- Previous post was at 09:50 PM ----------
csdaytona said:
Gotcha. I'll try to flash 6.0 tomorrow. Wish me luck.
Thanks for the help!
Click to expand...
Click to collapse
No problem man. I wish you luck!
If you do plan on modding it/rooting it/romming it in the future, DEFINITELY unlock your bootloader before you set up the phone or that'll wipe it, too.
|Jason8| said:
Wouldn't you be excited as **** if you had a new phone? Wouldn't you want to get it up and running as quickly as possible? Well... now he's gotta wait until he has a computer. Obviously installing an OTA and doing the incremental updates would be easier, which is what he was looking for. Since that's not an option, we laid out other ways to go about doing it. So he's getting to a computer tomorrow.
Click to expand...
Click to collapse
You act like I was born with a nexus 6... It was a new phone to me too. I was so excited I read as much as I could on it, thanking the people who were so gracious to spend their personal time writing guides so I could understand the process well enough to be comfortable with my phone and help others here.
scryan said:
Dude, come on... I know this is the Q&A section, and were supposed to be nicer here... But this lazyness is bull****.
You act like using a computer is impossible, then as soon as it takes some work.... You can get at one the next day?
Stop expecting to be spoon fed and at least try to learn something fist. There are a TON of write ups on how to do this. You spend how much money on a phone, and now you don't care to educate yourself on it?
Instead of expecting other to do all the work for you, read through the stickied index thread in the general section
http://forum.xda-developers.com/nexus-6/general/nexus-6-index-thread-t3229412
It has a newbie guide that literally holds your hand through the whole process. Post 2 has info on "how to flash factory images", use method 2 as method 1 in that thread will not work with the MM factory image.
Nice people have already spend a lot of time and effort documenting these things for you, as they are common questions. People like Simms and the other posters in this thread answer questions and offer support for free out of the kindness of their heart... Don't create extra work for them by ignoring all the effort already put out by other members, expecting it all to be regurgitated to you.
Fastboot, as described in the threads mentioned above, will completely overwrite the pertinent partitions, regardless of what was there... dev build or not. No need to flash and apply countless incremental updates. Google provides not only full system images, but the information to use them on their web page...
Click to expand...
Click to collapse
i have absolutely no computer nor laptop access, so i completely understand(understood) his side as well.
scryan said:
You act like I was born with a nexus 6... It was a new phone to me too. I was so excited I read as much as I could on it, thanking the people who were so gracious to spend their personal time writing guides so I could understand the process well enough to be comfortable with my phone and help others here.
Click to expand...
Click to collapse
He googled his build number and didn't get many hits on it. So he's asking if there's a way to get it up and running tonight without a computer. Seems valid to me. You jump into the thread offering no help at all and start talking **** about the guy. That's the exact opposite of what you're saying you strive to do. I don't get it.
simms22 said:
i have absolutely no computer nor laptop access, so i completely understand(understood) his side as well.
Click to expand...
Click to collapse
At that point its a legitamate question. This is a very different situation that is not well covered here, and requires a unique solution not many would come up with.
But "I absolutely have no computer nor laptop access" is pretty different then "I can access one TOMORROW. Sheesh, having something 1 day away is pretty far from it not being a possibility.
And I think you would agree it would be a significantly better idea to wait that day then to proceed with the method you gave (not that it was bad of you to give it... but you tried to differentiate and he held out to avoid being told to do it the hard way)
|Jason8| said:
He googled his build number and didn't get many hits on it. So he's asking if there's a way to get it up and running tonight without a computer. Seems valid to me. You jump into the thread offering no help at all and start talking **** about the guy. That's the exact opposite of what you're saying you strive to do. I don't get it.
Click to expand...
Click to collapse
We are told time and time again that their are no bad questions. Truth is there are more bad questions then good ones.
Him asking about a build that provides few google hits is very legitimate.
Him asking about doing it without a computer because he doesn't have one is legitimate.
It only becomes an issue when he doesn't get the answer he wants, and all of a sudden he does have computer access.
And given that he is going to proceed in a computer... It becomes nothing more then "How do I update my phone?", which is VERY well documented.
I not only gave him the link to the information he needed, AND even corrected the information pointing out that the flashall script fails and that he would need to use the second method listed in the instructions I linked him to (since I know he will likely have limited time to fail and figure out whats wrong)
"That's the exact opposite of what you're saying you strive to do. I don't get it."
Then let me explain.
Would you skip your homework, ignore your textbook, then show up to class asking your teacher to explain it again? We are here to help... but how or why should I care more about it then he does? With no attempt made to learn, how much should I care to teach him?
Its a pretty big **** you to all those who have spend countless hours documenting this stuff to help new people to ignore their work and tell someone to do it again.
please help i have a s10+ when i start it after 5 mins it stops reponding i can try to restart it but it will do the same thing can i unroot it or somthing
qomzt said:
please help i have a s10+ when i start it after 5 mins it stops reponding i can try to restart it but it will do the same thing can i unroot it or somthing
Click to expand...
Click to collapse
Expensive phone and you go mess with it.... Do you have twrp install if you do reflash your boot img it should clear magisk
([emoji813]9/[emoji725]/9[emoji813])
PoochyX said:
Expensive phone and you go mess with it.... Do you have twrp install if you do reflash your boot img it should clear magisk
([emoji813]9/[emoji725]/9[emoji813])
Click to expand...
Click to collapse
no man plsease help i dont know these things i watched a video to do it help
qomzt said:
no man plsease help i dont know these things i watched a video to do it help
Click to expand...
Click to collapse
How you rooted without twrp you patched your img and ADB pushed it?
([emoji813]9/[emoji725]/9[emoji813])
PoochyX said:
How you rooted without twrp you patched your img and ADB pushed it?
([emoji813]9/[emoji725]/9[emoji813])
Click to expand...
Click to collapse
i dont know i have not don the twp thing
qomzt said:
i dont know i have not don the twp thing
Click to expand...
Click to collapse
How did you achieve root on your device then... [emoji52]
([emoji813]9/[emoji725]/9[emoji813])
qomzt said:
please help i have a s10+ when i start it after 5 mins it stops reponding i can try to restart it but it will do the same thing can i unroot it or somthing
Click to expand...
Click to collapse
Sounds like you've jumped into the deep end a bit too early... The best option for you is likely to go to your device's forum, here: https://forum.xda-developers.com/s10-plus
There you can probably find information and guidance on how to root, flash and install stuff to your device. And you'll be able to ask for assistance from other users that have the same device as you (not every device works the same, and that is especially true for Samsung).
A couple of tips for you, going forward:
Do your homework. Read as much as you can about the modifications you're trying to do, and Android modification in general (but remember that things can change fast and a guide you find might be very outdated by the time you read it. The forums are usually the best place for up-to-date info).
Make backups! Always make sure that you have a backup of any important data, and don't store it on the device.
Know how to go back to a working state when you mess up, because mess up you will (everyone does at some point). This tip is of course tied to the first one...
Don't follow some guide or video blindly. Make sure you understand what every step of the process does. That way you won't get stuck like this next time.
Good luck.