help i think that iv bricked my phone - ONE Q&A, Help & Troubleshooting

Hey.
I tried to go back to 100% , long story short i delet everything oj my phone include the system.
I tried to install flashboot roms throw the fastboot but i cant install the system img, it says that the system file is to large, i tried to install the recovery but after i installed it the phone just come back to the old useles recovery.
Please please anyone, i need your help.

Download opo-toolbox and open your phone in fastboot mode. Then its quite easy to flash the stock cm 11s rom and you can use it to root and install custom recovery. Just search it on xda for it. Or use this link
htt p://inthiaano.com/oneplus-one-toolbox/
Sent from my A0001 using XDA Free mobile app

Don't use the toolbox. Really bad idea. All you need to do is update your adb/fastboot by installing the latest Android SDK.
Transmitted via Bacon

Timmaa, I bricked my phone twice in 20 days since I purchased it. I simply used opo toolbox to fix it. It works like a charm...

manish1ly said:
Timmaa, I bricked my phone twice in 20 days since I purchased it. I simply used opo toolbox to fix it. It works like a charm...
Click to expand...
Click to collapse
That doesn't mean anyone should use a toolkit. The first reason is I've seen toolkits cause so many problems it isn't even funny. The second reason is toolkits allow you to do things to your phone without having a clue about what you're actually doing. They bypass crucial learning, and it's this bypassed knowledge that's going to get you out of trouble in future when something goes wrong. It's much better to learn how to use fastboot and have a firm grasp on everything. The choice is yours, but it's only a matter of time before you regret it.
Transmitted via Bacon

Since I didn't have the stock ROM , I used the opo toolbox, which I had downloaded when I didn't even have the device. But it helped me a lot when my device was bricked while I was trying to multiboot from my opo. But you are right that learning is more important. After all knowledge is power.
Sent from my A0001 using XDA Free mobile app

Related

[Q] Plz Help! Stuck in BootLoader!

Hi all, I'm pretty new to the forums, so please forgive my noob-ousity.
I have got a Nexus S it's a I9020A, I Rooted and unlocked my phone a long time ago, and all was well and good for a while, then I started getting major slow downs, So I started doing a regular format to try and get rid of clutter, and it helped for a while, then last night I got tired of it always bogging down, so I did something very stupid, I went to recovery and formatted/wiped everything that had the option to do so.
Now my phone reboots directly to bootloader, I can go into recovery and I have the clockworkmod v5.8.0.2,
I have tried;
- Updating to the newest clockwork (6.0.3.1), it just makes it so my pc no longer recognizes my phone and I can't copy anything to the sdcard. So I had to revert.
- Using the Sabra One Click Root Tool! to recover things to a normal state, (a google search on my troubles prompted me to try this). It doesn't seem to change anything. When this finishes, just before getting the "congrats ur device is now rooted blah blah blah" I get a few errors that flash on the screen saying;
can't remove recovery-from-boot.p
can't remove install-recovery.sh
postrecoveryboot.sh not found.
- Freeboot and adb, neither seem to want to pick up my device even though everything else seems too.
- Copying update.zip and running it from the clockworkmod interface, it doesnt seem to change anything.
I'm sure I'm just missing something, but when I google my issue I get a lot of people stuck in bootloader unable to do any of the stuff I tried. Nothing that really has my exact problem for my phone.
Try Nexus Root Toolkit. Works flawlessly if you read the instructions carefully.
ej8989 said:
Try Nexus Root Toolkit. Works flawlessly if you read the instructions carefully.
Click to expand...
Click to collapse
I did exactly that, when doing a search, all the different tools one can use, the options can be kind of intimidating, especially when you don't know really what your issue is, the Nexus Root Toolkit does pretty much everything. As you said, it works flawlessly.
I flashed back to stock, and it works again.
Thanks so much for your help
Mr.M.Grey said:
I did exactly that, when doing a search, all the different tools one can use, the options can be kind of intimidating, especially when you don't know really what your issue is, the Nexus Root Toolkit does pretty much everything. As you said, it works flawlessly.
I flashed back to stock, and it works again.
Thanks so much for your help
Click to expand...
Click to collapse
awhere do I find a original Firmware for nexus s, pleace?
dark'em said:
awhere do I find a original Firmware for nexus s, pleace?
Click to expand...
Click to collapse
When I downloaded the Nexus toolkit, it asks you what device you are using and what version, just tell it the newest one, in my case it was android 4.1.2 JZO54K and it will automatically download the original firmware for you, at least that was my understanding.
Mr.M.Grey said:
When I downloaded the Nexus toolkit, it asks you what device you are using and what version, just tell it the newest one, in my case it was android 4.1.2 JZO54K and it will automatically download the original firmware for you, at least that was my understanding.
Click to expand...
Click to collapse
Ooo I see now, thank you
dark'em said:
Ooo I see now, thank you
Click to expand...
Click to collapse
Not a problem, good luck!
Edit: Nevermind!
Sent from my GT-N8013 using xda app-developers app

[Q] Official CM Installation Method Confusion

Greetings,
My name is Tim and I'm looking for some assistance with getting CM 10.1.3 up and running on my GS3 (d2vzw / SCH-i535). I'm not a complete noob, as I managed to successfully flash CM to my Galaxy Tab 2 10.1, and my Droid X2 after countless hours of reading through XDA forum posts for each of the devices, however...I'm still pretty new to a lot of this stuff as I usually don't mess with it once I get CM up and running, and struggle with command prompts still, so I apologize for any/all idiocy posted herein.
I am using the instructions found on the CM site under the d2vzw device (I'd link you but it doesn't appear as though I'm allowed to), and after reading that I don't need to root my device to install CM, I'd prefer to stick with this method (I'm also uncomfortable using Odin or any other such software, as I've heard bad things and already managed to soft brick my GS3 once with it.)
I've got all the appropriate files listed at the above page, but I'm confused with several aspects of the "official" install instructions, and would like some clarification, if possible. Any assistance would be greatly appreciated.
1) USB drivers: I installed the Samsung drivers, but when I ran heimdall print-pit in CMD, it failed giving me an error 12 (can't remember what, specifically, but apparently it has to do with USB drivers). A bit of Google-ing, and I was able to determine that Samsung drivers = bad. Okay, I can deal with that and have uninstalled them. However, does that mean I need to NOT let Windows 7 Update auto install drivers? Further, do I need to use the zadig app to install drivers before I can use Heimdall appropriately? I ask because after I uninstalled the Samsung drivers and rebooted, I tried to flash but it failed.
2) Wording of CMD commands confuses me. Heimdall flash --ABOOT aboot.mbn - okay, I get that I'm typing "heimdall flash" as the preface, but the actual aboot.mbn file is within a .tar file...so do I just flash to the location of the actual tar file? Or do I extract it with 7zip (as I initially tried) and try to flash to the location of the actual aboot.mbn file? Further, --ABOOT doesn't show up on the list of viable options within CMD, which confuses me (is it part of the command, or is it a place holder for some command I'm not understanding).
3) Same question for the other CMD commands.
I've looked around on XDA, the Heimdall site, and elsewhere for more detailed "official" install guides, but they all seem to either involve Odin or rooting, and as I mentioned I want nothing to do with either of them, if possible.
Thank you kindly for your time.
Sure you can do all that, but there are some easy one click root apps for the gs3. Then install cwm recovery. Then flash CM and GAPPs.
Just search the forum and you should be able to find the thread.
Good luck!!
Sent from my SCH-I535 using xda app-developers app
stolo said:
Sure you can do all that, but there are some easy one click root apps for the gs3. Then install cwm recovery. Then flash CM and GAPPs.
Just search the forum and you should be able to find the thread.
Good luck!!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
The only "one-click app" I know of is Framaroot which does not work on the VZW varient of the GS3. So what app are u referring to?
Sent from my SCH-I535 using Tapatalk
I was not referring to an apk on the phone, meant pc app.
I have not personally used this, but looks like it will do the trick.
http://forum.xda-developers.com/showthread.php?t=2332825
stolo said:
I was not referring to an apk on the phone, meant pc app.
I have not personally used this, but looks like it will do the trick.
http://forum.xda-developers.com/showthread.php?t=2332825
Click to expand...
Click to collapse
I thought I downloaded that before and it ended up being a jumble of files...but I just downloaded it now and it looks promising. Thanks for the suggestion, I'll give it a try tomorrow!
Swatpro004 said:
I thought I downloaded that before and it ended up being a jumble of files...but I just downloaded it now and it looks promising. Thanks for the suggestion, I'll give it a try tomorrow!
Click to expand...
Click to collapse
If you want just go try out the cyanogenmod installer from the play store. It should root, unlock, and install for you. Just follow the instructions in the app.
Sent from my AOSP on Grouper using Tapatalk HD
Well, I just tried using the "casual" root one-click thing.
I successfully rooted, but it took ~10 minutes on the flashing of aboot. It claimed to be done, but when I tried to flash CWM it rebooted into the "unauthorized software, contact verizon" screen.
Any ideas? This makes me sad. I don't know why this is so much more difficult than my other devices.
-e- I can still get into download mode, but when I try to go into recovery it just loops back to the main samsung screen with the custom icon and then hops into the verizon unauthorized stuff. Also, when I plug it in to charge it just vibrates once every ~5 seconds without doing much else.
Additionally, I still don't know which USB drivers I want for doing all of this. I'm relying on the ones Windows 7 auto-installs currently, if that helps with troubleshooting. Thank you in advance, again.
Swatpro004 said:
Well, I just tried using the "casual" root one-click thing.
I successfully rooted, but it took ~10 minutes on the flashing of aboot. It claimed to be done, but when I tried to flash CWM it rebooted into the "unauthorized software, contact verizon" screen.
Any ideas? This makes me sad. I don't know why this is so much more difficult than my other devices.
-e- I can still get into download mode, but when I try to go into recovery it just loops back to the main samsung screen with the custom icon and then hops into the verizon unauthorized stuff. Also, when I plug it in to charge it just vibrates once every ~5 seconds without doing much else.
Additionally, I still don't know which USB drivers I want for doing all of this. I'm relying on the ones Windows 7 auto-installs currently, if that helps with troubleshooting. Thank you in advance, again.
Click to expand...
Click to collapse
you just didn't unlock your bootloader that's all. Flash stock (or stock recovery) using Odin. Then root using the same method above. When rooted unlock your bootloader using EZunlock1.2. Its an app that runs on your phone. Then flash recovery. Done.
Edit: at this point it may be easier to just flash a prerooted stock ROM using Odin.
Sent from my SCH-I535 using Tapatalk
Sandman-007 said:
you just didn't unlock your bootloader that's all. Flash stock (or stock recovery) using Odin. Then root using the same method above. When rooted unlock your bootloader using EZunlock1.2. Its an app that runs on your phone. Then flash recovery. Done.
Edit: at this point it may be easier to just flash a prerooted stock ROM using Odin.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Thank you, Sandman. I will try this right now.

[Q] Bootloader error / Soft brick

So as Im sure everyone already knows I done messed up. I literally had the tablet(asus tf700) for less than a day. Im not very linux savvy but i know enough about electronics that i can usually get by, well not this time. I had rooted and unlocked my device, downloaded cm 11 that was to be installed via twrp recovery. Everything went gravy and then i had a loop problem with cyanogenmod, im guessing i didnt have the correct bootloader to use cm 11 in the first place. So i tried to just go back to stock only to find out that my backups had been corrupted and the names of the files were there but nothing on them. So I looked around for a bit and tried to figure out how to just flash a new rom in there, low and behold my pc laptop stopped working leaving me with only a mac to use right now. The pc will turn on and work for a bit but there is a fan out so it overheats very quickly. So i tried to use the nexus toolkit to possibly go back to stock via the nexus 10 or nexus 7 options they have. Needless to say this was very stupid and now instead of being in a bootloop with cyanogenmod I am stuck looking at the asus letters when it starts up, it doesnt even bootloop it just stays there and to top it off i now have a bootloader error 0x00000000 and i cant do anything other than the sync looking thing hich i am assuming is fast boot. I can plug it in and the computer shows the device as fastboot but just dont know what to try anymore. I have read the buster post and i know this is kind of a repost but i just dont understand the linux portion of his response. Im guessing my tablet still has a fighting chance but im just devastated at this point to have lost its use within a day of having it. Ive really learned a lot by this happening so i dont beieve i will make these mistakes again but can someone please help me get this beauty back to her prime " pun intended ".
Try writing in smaller paragraphs - that is really hard to read
From what I can tell you appear to have flashed something form a nexus into your bootloader partition?
If so I think you can say goodbye to the device unless you previously did the flatline nvflash backups to make it unbrickable?
ah wait! you said you have fastboot? Can you fastboot devices from a cmd prompt and get a device id back?
NobleXperiment said:
So as Im sure everyone already knows I done messed up. I literally had the tablet(asus tf700) for less than a day. Im not very linux savvy but i know enough about electronics that i can usually get by, well not this time. I had rooted and unlocked my device, downloaded cm 11 that was to be installed via twrp recovery. Everything went gravy and then i had a loop problem with cyanogenmod, im guessing i didnt have the correct bootloader to use cm 11 in the first place. So i tried to just go back to stock only to find out that my backups had been corrupted and the names of the files were there but nothing on them. So I looked around for a bit and tried to figure out how to just flash a new rom in there, low and behold my pc laptop stopped working leaving me with only a mac to use right now. The pc will turn on and work for a bit but there is a fan out so it overheats very quickly. So i tried to use the nexus toolkit to possibly go back to stock via the nexus 10 or nexus 7 options they have. Needless to say this was very stupid and now instead of being in a bootloop with cyanogenmod I am stuck looking at the asus letters when it starts up, it doesnt even bootloop it just stays there and to top it off i now have a bootloader error 0x00000000 and i cant do anything other than the sync looking thing hich i am assuming is fast boot. I can plug it in and the computer shows the device as fastboot but just dont know what to try anymore. I have read the buster post and i know this is kind of a repost but i just dont understand the linux portion of his response. Im guessing my tablet still has a fighting chance but im just devastated at this point to have lost its use within a day of having it. Ive really learned a lot by this happening so i dont beieve i will make these mistakes again but can someone please help me get this beauty back to her prime " pun intended ".
Click to expand...
Click to collapse
Wow, you beat me on the unlock your new device within one day of usage...
You can see the post above to see if you still can use your fastboot. If your fastboot is still working, you can download the full latest firmware from Asus website and install it with fastboot command...good luck....:fingers-crossed:
Yeah sorry bout the length, i know a lot of times everyone asks for more details so i figured id get that out of the way, honestly didnt even know if i would get a response so much appreciated, i will be home shortly to try the download, def a huge failblog learning experience at best. when you do that what exactly is the point of making two blops. ?
To be honest with all the amazing kits that have come out of this forum Im quite baffled there is not one to reestablish things like the nexus toolkit. With my computer overheating i basically only have time to install a kit and run it before it stops working, so hopefully i have enough time to cmd prompt, but thats really the stuff i dont get. Is it possible to go into a little depth as far as the command prompts?the busters solution would be an easy guide to work from i would imagine.
NobleXperiment said:
To be honest with all the amazing kits that have come out of this forum Im quite baffled there is not one to reestablish things like the nexus toolkit. With my computer overheating i basically only have time to install a kit and run it before it stops working, so hopefully i have enough time to cmd prompt, but thats really the stuff i dont get. Is it possible to go into a little depth as far as the command prompts?the busters solution would be an easy guide to work from i would imagine.
Click to expand...
Click to collapse
Yes the are a number of tool kits in the dev forum But unlocking and setting up recovery and the bootloader on the asus transformer is different to the nexus devices so you can't have such a simple route I'm afraid.
sbdags said:
Yes the are a number of tool kits in the dev forum But unlocking and setting up recovery and the bootloader on the asus transformer is different to the nexus devices so you can't have such a simple route I'm afraid.
Click to expand...
Click to collapse
Would I be able to us nvflash to install custom bootloader and then progress towards installing new rom? or does tht not really have anything to do with my situation? the asus website isnt working for me either so I cant download the proper firmware.
NobleXperiment said:
Would I be able to us nvflash to install custom bootloader and then progress towards installing new rom? or does tht not really have anything to do with my situation? the asus website isnt working for me either so I cant download the proper firmware.
Click to expand...
Click to collapse
Your tablet is very close to becoming a paper weight - not the ideal situation to generate your nvflash blobs.
First step should be to get a working fastbooot connection. Either fix the PC or get fastboot set up on your Mac. http://forum.xda-developers.com/showthread.php?t=1917237
A half-dead tablet and non-working PC is just a little more challenge than you need right now.
Without fastboot you cannot fix this. So get that set up and we can help more.
Sent from my K00C using Tapatalk
berndblb said:
Your tablet is very close to becoming a paper weight - not the ideal situation to generate your nvflash blobs.
First step should be to get a working fastbooot connection. Either fix the PC or get fastboot set up on your Mac. http://forum.xda-developers.com/showthread.php?t=1917237
A half-dead tablet and non-working PC is just a little more challenge than you need right now.
Without fastboot you cannot fix this. So get that set up and we can help more.
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
I got fast boot setup on the Mac and it did show that it connected but I can't download the asus firmware on my Mac for some reason?
NobleXperiment said:
I got fast boot setup on the Mac and it did show that it connected but I can't download the asus firmware on my Mac for some reason?
Click to expand...
Click to collapse
You tried all the links? I use Global and it works.
Which SKU are you? I think I have the US .10 firmware lying around somewhere - can upload it to Dropbox.
Sent from my K00C using Tapatalk
Thank you for the firmware offer but I went thru and fixed my pc and then got everything working with busters mothod:victory: I had to try it about 3 times and use my eSATA usb for some reason but i actually ended up going from stock 4.1.1 to 4.2.1 so all in all great success. honestly baffled that i pulled this off.
NobleXperiment said:
Thank you for the firmware offer but I went thru and fixed my pc and then got everything working with busters mothod:victory: I had to try it about 3 times and use my eSATA usb for some reason but i actually ended up going from stock 4.1.1 to 4.2.1 so all in all great success. honestly baffled that i pulled this off.
Click to expand...
Click to collapse
:Good:
Now generating your NVflash blobs will be a breeze
Sent from my K00C using Tapatalk
berndblb said:
:Good:
Now generating your NVflash blobs will be a breeze
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
Should i go the route of NVflash now? I only mentioned it because I saw you could download blob files but does it really make you device unbrickable? Is this something i should go for or just be happy i fixed the tablet?
NobleXperiment said:
Should i go the route of NVflash now? I only mentioned it because I saw you could download blob files but does it really make you device unbrickable? Is this something i should go for or just be happy i fixed the tablet?
Click to expand...
Click to collapse
It makes it unbrickable. You can recover from any brick with the nvflash blob files.
NobleXperiment said:
Should i go the route of NVflash now? I only mentioned it because I saw you could download blob files but does it really make you device unbrickable? Is this something i should go for or just be happy i fixed the tablet?
Click to expand...
Click to collapse
Entirely up to you. You were a half-step away from hard bricking your tablet. If this is a typical pattern for you (try first - ask/read later) it may be a very good idea to get those blobs squared away
You have to flash a modded bootloader and modded recovery just for generating the blobs (and flash back afterwards), so it may be a good idea to get this done before you get everything set up.
Sent from my K00C using Tapatalk
With all of this being a first to me I certainly underestimated how easy it is to brick a device, but I did manage to fix it which seems much harder to do so i would have to think i can get the nvflash done. Appreciate the support here and everything people do within the forums, if somebody could direct me to an approved guide that would be quite nice, im assuming its very similar to what i just went through?
NobleXperiment said:
With all of this being a first to me I certainly underestimated how easy it is to brick a device, but I did manage to fix it which seems much harder to do so i would have to think i can get the nvflash done. Appreciate the support here and everything people do within the forums, if somebody could direct me to an approved guide that would be quite nice, im assuming its very similar to what i just went through?
Click to expand...
Click to collapse
Follow these instructions to the letter.
https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
I anything is unclear, ask in this thread:
http://forum.xda-developers.com/showthread.php?t=1901479
Sent from my K00C using Tapatalk
So yeah while i thought the upgrade to 4.2.1 was a lucky mistake but now i cant use kingo to root my phone, any suggestions without having to go back to an earlier firmware?
or would getting the nvflash unroot the device again anyway?

Root lost after 4.4.4 OTA update?

Hi, i updated to 4.4.3 via ota update. After that i tried to open SuperSU and it says 'There is no SU binary instanned and superSU cannot install it.'
Did i lost root? Do i need to start from the beggining ?
I was trying to flash Franco Kernel and i realized that there is a problem after i tried to enter recovery mode. My device failed to enter recovery mode showing me a dead android with a red exclamation mark.
Thanks in advance !!
1) the dead android is stock android recovery
2) yes you lost root
solution: reflash a custom recovery in fastboot and then flash the supersu zip and you're done.
there are a ton of threads about this issue and how to solve it all over the place. please search next time.
Actually he is not alone. I too updated ota to 4.4.3 and lost root. I searched and searched and I am sure the answer is buried "somewhere" but I couldn't find the answer to *my* question.
I previously rooted my Nexus 5, 4.4.2 using adb and Fastboot, but my question is which image do I use for TWRP and 4.4.3? Is 4.4.3 still called hammerhead or something else? Those names are confusing to non experts and flashing the wrong img can brick the phone.
Which TWRP recovery image do I use?
Which Supersu do I use?
And where do I find them?
Thanks.
Anderson2 said:
Actually he is not alone. I too updated ota to 4.4.3 and lost root. I searched and searched and I am sure the answer is buried "somewhere" but I couldn't find the answer to *my* question.
I previously rooted my Nexus 5, 4.4.2 using adb and Fastboot, but my question is which image do I use for TWRP and 4.4.3? Is 4.4.3 still called hammerhead or something else? Those names are confusing to non experts and flashing the wrong img can brick the phone.
Which TWRP recovery image do I use?
Which Supersu do I use?
And where do I find them?
Thanks.
Click to expand...
Click to collapse
The device is hammerhead. The latest official twrp is fine and same with super su. Don't use tool kits that way you know what to do when something like this happens.
This will take you start to finish you were rooted so im assuming your bootloader is unlocked and you can start with flashing recovery image just be sure to read it all .
http://forum.xda-developers.com/showthread.php?t=2507905
Sent from my Nexus 5 using Tapatalk
Anderson2 said:
Actually he is not alone. I too updated ota to 4.4.3 and lost root. I searched and searched and I am sure the answer is buried "somewhere" but I couldn't find the answer to *my* question.
I previously rooted my Nexus 5, 4.4.2 using adb and Fastboot, but my question is which image do I use for TWRP and 4.4.3? Is 4.4.3 still called hammerhead or something else? Those names are confusing to non experts and flashing the wrong img can brick the phone.
Which TWRP recovery image do I use?
Which Supersu do I use?
And where do I find them?
Thanks.
Click to expand...
Click to collapse
Of course you lost root, that's normal. For twrp go to goo.im. for super su Google chainfire supersu xda. Very simple, very easy
Sent from my Nexus 5 using XDA Free mobile app
Got this puppy in the mail today and fastboot unlocked the BL before I even saw a start screen. Took 4.4.3 then fastboot flashed TWRP. Installed SuperSU in recovery.
Boom! Rooted, unlocked and updated.
P.S. howdy y'all
Sent from my Nexus 5 using Tapatalk
Howdy
Sent from my Nexus 5 using Tapatalk
Just use Nexus Root Toolkit its so easy google it.:cyclops:
Lost root 4.4.4
If you (and you will) loose root after installing the zip for 4.4.4 go to http://download.chainfire.eu/446/SuperSU/ and download the zip. use recovery to install.
CliffordS
Sent from my Nexus 5 using Tapatalk[/QUOTE]
people...!
this is exactly tbe same as the very first android update ever in 2008.. if you update via ota or stock manually, YOU WILL LOSE ROOT. stock rom is not rooted by default. you can not expect to have root when updating stock! this is just silly people. the simplest search on google brings you years, yes years, of the same exact question being asked thousands of times over.. and yes, you will also lose your custom recovery.
chainsuk said:
Just use Nexus Root Toolkit its so easy google it.:cyclops:
Click to expand...
Click to collapse
Yes, easy to make you think you "bricked" your phone.
Sent from my Nexus 5
simms22 said:
people...!
this is exactly tbe same as the very first android update ever in 2008.. if you update via ota or stock manually, YOU WILL LOSE ROOT. stock rom is not rooted by default. you can not expect to have root when updating stock! this is just silly people. the simplest search on google brings you years, yes years, of the same exact question being asked thousands of times over.. and yes, you will also lose your custom recovery.
Click to expand...
Click to collapse
Oh dear. So much this.... I have but one thanks to give to this post...
It's like people are completely baffled at this when it literally happens with every freaking update...
#stayparanoid
Just use wugs nexus tool I lost root and fixed it with the root option. No messing just a few clicks its idiot proof
Sent from my Nexus 5 using xda premium
stewartk said:
Just use wugs nexus tool I lost root and fixed it with the root option. No messing just a few clicks its idiot proof
Sent from my Nexus 5 using xda premium
Click to expand...
Click to collapse
Yes, but it also makes you look like an idiot when you post on here complaining something doesn't work because of use of a toolkit.
Rooting is just flashing a custom recovery then flashing SuperSU. If you need a toolkit to assist with something as simple as that then I suggest you revert back to stock factory images and stay away from anything regarding "root".
Sent from my Nexus 5
simms22 said:
people...!
this is exactly tbe same as the very first android update ever in 2008.. if you update via ota or stock manually, YOU WILL LOSE ROOT. stock rom is not rooted by default. you can not expect to have root when updating stock! this is just silly people. the simplest search on google brings you years, yes years, of the same exact question being asked thousands of times over.. and yes, you will also lose your custom recovery.
Click to expand...
Click to collapse
Yep, I'm surprised people still ask this question. If you know how to flash an OTA, you should know what happens after. On a side note, when I flashed the 4.4.3 OTA, I actually didn't lose the TWRP. I just used the OTA from the OTA thread. I just thought it strange.
Not true i have used it thousands of others have without a problem, i could say people have bricked their phone with fastboot NOTHING is 100% safe....
chainsuk said:
Not true i have used it thousands of others have without a problem, i could say people have bricked their phone with fastboot NOTHING is 100% safe....
Click to expand...
Click to collapse
ok, i dont know what youre talking about but ill bite.. show me one person thats bricked their phone with fastboot.
I cant show you i can only tell you what ive read on these very forums for whatever reason ppl have reported on xda that their phones have bootlooped and bricked, it my have been user error on commands or glitches i dont know,and all i was saying about Nexus root toolkit is that i have used it many times without a problem as have other ppl but im sure that some ppl have come unstuck but for me its been fine....
Lethargy said:
Yes, but it also makes you look like an idiot when you post on here complaining something doesn't work because of use of a toolkit.
Rooting is just flashing a custom recovery then flashing SuperSU. If you need a toolkit to assist with something as simple as that then I suggest you revert back to stock factory images and stay away from anything regarding "root".
Sent from my Nexus 5
Click to expand...
Click to collapse
I've never had a problem using root kits. I also know how to do it other ways. But some idiots like to do it root kit ways.
Sent from my Nexus 5 using xda premium
stewartk said:
I've never had a problem using root kits. I also know how to do it other ways. But some idiots like to do it root kit ways.
Sent from my Nexus 5 using xda premium
Click to expand...
Click to collapse
Maybe you should talk to this guy
http://forum.xda-developers.com/showthread.php?p=53573890
Sent from my Nexus 5 using XDA Free mobile app

nexus 5 stock rom help

hey guys so I recently got my nexus 5, messed around with a few roms but now I wanna go back to stock, well I downloaded the rom and before I reset my phone I forgot to transfer it, Iv got linux mint so i quicky downloaded adb, im trying to sideload the file and everything worked great expect this line comes up wile trying to install. E: cant open /tmp/update.zip (bad)
IM running clockworkmod recovery 6.0.4.5.
Can anyone help? my phones a paper weight now ):
p.s when installing I used adb push files dic and file name, (yes i made sure they where correct)
You obviously know how to restore with Fastboot, or you wouldn't be flashing ROMs in the first place
As mentioned, returning to stock needs fastboot. All guides are in general. Not hard to find.
Sent from my Nexus 5 using Tapatalk
rootSU said:
As mentioned, returning to stock needs fastboot. All guides are in general. Not hard to find.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thats why i posted because I dont know, like i do now how to flash roms but for some reason its not working, the sideload does not work. and I cant seem to install sdk on linux nothings coming up. please help id like to use my phone again.
All guides are in general. There is even a link in my signature. I won't spoon feed what is already written
Sent from my Nexus 5 using Tapatalk
evilxhakz said:
Thats why i posted because I dont know, like i do now how to flash roms but for some reason its not working, the sideload does not work. and I cant seem to install sdk on linux nothings coming up. please help id like to use my phone again.
Click to expand...
Click to collapse
Why would you need to install the SDK?
Adb and fastboot are in the repos
#stayparanoid

Categories

Resources