Hey! I don't know if this is the right place, but I'll try to explain my problem.
Yesterday I got a notification of an update(think it's 6.0.0 (MRA58N)). Today, when I tried to install it I just got an "Error!" message.
I tried to reboot the phone, but nothing happened. It doesn't turn on. However, I can get it into that fastboot screen or what it's called.
Haven't had any problems before, and Im kind of a beginner on these technical issues regarding phones.
So could someone please explain what I should do(hopefully nothing to complicated).
Thanks!
That sounds like a rooted phone. Is it? Have you owned the phone from new, or is it second-hand?
dahawthorne said:
That sounds like a rooted phone. Is it? Have you owned the phone from new, or is it second-hand?
Click to expand...
Click to collapse
It was new when I bought it (april 2014). I have only installed updates when getting a notification on the phone. I got a notification to do an update yesterday. Did it today. But while updating it just stopped and said "Error!". Turn the phone off, tried to turn it on but nothing happened.
What's the easiest way to make the phone work again?
Have in mind that Im not experienced at all with these stuff . Never had had any problems before
Thanks
Were you already on a version of Marshmallow? They are both version 6.0.0 regardless of the name (MRA58K/N).
Was there any message apart from just "Error"? Do you remember what it looked like?
I take it that you have enough battery?
I have no idea of the answer, just trying to get some clues.
(Oh, and at worst you can probably flash a new ROM. Don't get too worried just yet... )
dahawthorne said:
Were you already on a version of Marshmallow? They are both version 6.0.0 regardless of the name (MRA58K/N).
Was there any message apart from just "Error"? Do you remember what it looked like?
I take it that you have enough battery?
I have no idea of the answer, just trying to get some clues.
Click to expand...
Click to collapse
Yes, I updated to marshmallow a couple of weeks ago.
Yes, I was on about 75% battery when trying to update.
As far as I recall it was just the android guy and a red text saying Error! (well it said Fel! because it's in swedish.)
It started to install the updates, but just stopped halfway(rough estimate).
Hmm :/
EDIT: Yes, I've asked on other forums, and they have been saying to flash(it's called taht right?) But since I'm new to this stuff, I want to check all possible alternatives first. And if I decide to do this, I'll have to feel fully prepared on what to do, don't want to screw up things even more
To give you at least some hope have a look at this thread:
http://forum.xda-developers.com/google-nexus-5/help/stuck-launching-flashstock-bat-t3244470
If you've never done any flashing before, I recommend that you install Wugfresh's Nexus Root Toolkit. It can be used to flash a new ROM, but I'm becoming more convinced that the people in these forums are right in saying that it's good to try things manually rather than relying on a toolkit. I suggest that you use the toolkit's tutorial to set up your PC with all the right drivers & programs (ADB/Fastboot) so that you're prepared for typing in the commands.
dahawthorne said:
To give you at least some hope have a look at this thread:
http://forum.xda-developers.com/google-nexus-5/help/stuck-launching-flashstock-bat-t3244470
If you've never done any flashing before, I recommend that you install Wugfresh's Nexus Root Toolkit. It can be used to flash a new ROM, but I'm becoming more convinced that the people in these forums are right in saying that it's good to try things manually rather than relying on a toolkit. I suggest that you use the toolkit's tutorial to set up your PC with all the right drivers & programs (ADB/Fastboot) so that you're prepared for typing in the commands.
Click to expand...
Click to collapse
Thanks, I'll have a look at it.
Just to be sure. A factory reset wont work, right?
I don't know - I suppose it's worth trying. But if the phone doesn't turn on, you'll have to go through the PC setup anyway so that you can work on the phone. Besides, it will come in very useful when you need to do any maintenance on the phone in future (if that's what you want).
Or is there a factory reset in stock recovery? I don't use it myself, so I don't know.
CoJonees said:
Thanks, I'll have a look at it.
Just to be sure. A factory reset wont work, right?
Click to expand...
Click to collapse
Wug's toolkit needs a fix. It will not load the new Mashmellow either
Want to learn something instead of using a toolkit to do stuff for you?
1) http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
2) http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Both these threads are unavailable, possibly deleted.
Sent from my Nexus 5 using Tapatalk
beekay201 said:
Want to learn something instead of using a toolkit to do stuff for you?
1) http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
2) http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
@beekay
"Want to learn something instead of using a toolkit to do stuff for you?"
You convinced me, but I think that the NRT has a lot of great help in setting up a PC so that you can actually start learning about ADB/Fastboot manual commands.
Although I'd done some minor fastboot stuff before, I'd never done the full Monty and installed a ROM, but I found the experience strangely pleasurable...
@op found help yet :what::what::what::what:
Related
i have searched, read and read more. but i am totally stuck on getting a custom theme and dock setup on my rooted phone. is there a how to that is better written than the ones i have come across on start to end on programs, apps, w/e i need to get one of these custom themes working. seems i follow what is there, but get stuck on area's of it, than i search on that to come up with nothing or no info. maybe im just over doing it all in one day on learning all this, lol. im a video person, but havent seen a install video of this. any help or links or something? thanks
tyhodge07 said:
i have searched, read and read more. but i am totally stuck on getting a custom theme and dock setup on my rooted phone. is there a how to that is better written than the ones i have come across on start to end on programs, apps, w/e i need to get one of these custom themes working. seems i follow what is there, but get stuck on area's of it, than i search on that to come up with nothing or no info. maybe im just over doing it all in one day on learning all this, lol. im a video person, but havent seen a install video of this. any help or links or something? thanks
Click to expand...
Click to collapse
Youre asking how to install a theme?? Find once compatible for your rom. Stick it on your sd card. Boot into recovery, and flash it.
Post what problems you are having. Good luck.
Sent from my PC36100 using XDA App
Dredge said:
Youre asking how to install a theme?? Find once compatible for your rom. Stick it on your sd card. Boot into recovery, and flash it.
Click to expand...
Click to collapse
im not even sure which rom to use, i have tried a couple but the adk is where i am stuck at, when i go to command prompt it isnt at the c://adk/etc.. like what all the write ups are at, its at c://user/applications or something of that nature and i type what should be typed in on the /adk part of it and says it can not be found. i tried reinstalling the adk again and same problem, im doing something wrong somewhere i assume or stuck in a spot that i keep doing wrong and not noticing. i just rooted it, so whatever rom i have i am assuming is the stock one since i havent gotten past this yet.
Your in over your head man, seriously, YOU put the sdk where you want it, me, I just put it in C:\sdk to make my life easy when changing directories.
If command line work is not something your familiar with, have patience, enjoy your rom as it is right now and wait until the super easy one click gui programs are created.
Did you buy the phone already rooted, or did you root it yourself?
Dredge said:
Did you buy the phone already rooted, or did you root it yourself?
Click to expand...
Click to collapse
i rooted it myself. also when i right click on tools and im supposed to see open in comand promp or something, that doesnt appear?
tyhodge07 said:
i rooted it myself. also when i right click on tools and im supposed to see open in comand promp or something, that doesnt appear?
Click to expand...
Click to collapse
You say you rooted it yourself, which is great, but the questions you're asking are so far out that it makes it urprising that you did.
UNLESS... you rooted using simpleroot or some ****? If sooooooo, that makes ur questions make a lot more sense.
Anyways you just boot into recovery, and flash the zip from that menu.
It has nothing to do with adb, cmd, or any of that other bull**** you're talking about. Just do what's bolded and stop going 3 miles outside of the box.
TJDuckett said:
You say you rooted it yourself, which is great, but the questions you're asking are so far out that it makes it urprising that you did.
UNLESS... you rooted using simpleroot or some ****? If sooooooo, that makes ur questions make a lot more sense.
Anyways you just boot into recovery, and flash the zip from that menu.
It has nothing to do with adb, cmd, or any of that other bull**** you're talking about. Just do what's bolded and stop going 3 miles outside of the box.
Click to expand...
Click to collapse
I agree, OP, you are way over complicating it dude. What is your build number? Settings> about phone> software information.
If I didn't know better I would almost bet you're trying to troll us. Being a brand new account and all.
Dredge said:
I agree, OP, you are way over complicating it dude. What is your build number? Settings> about phone> software information.
If I didn't know better I would almost bet you're trying to troll us. Being a brand new account and all.
Click to expand...
Click to collapse
build number
1.17.651.1 cl160858
ive tried the reboot and flash thing and nothing happened, said missing filie or something and erased my phone and now vibrate doesnt work? this is after placing them theme on there i want to use and trying to load it in the boot screen. dont know all these names for the android system. prob just so used to messing with the iphones which is what is making this so hard for me, lol.
tyhodge07 said:
build number
1.17.651.1 cl160858
ive tried the reboot and flash thing and nothing happened, said missing filie or something and erased my phone and now vibrate doesnt work? this is after placing them theme on there i want to use and trying to load it in the boot screen. dont know all these names for the android system. prob just so used to messing with the iphones which is what is making this so hard for me, lol.
Click to expand...
Click to collapse
I don't believe you anymore. Even Root tutorials direct you to install a rom after rooting, which would put you at 1.47.65 or whatever even without 2.2 upgrading.
Trying to flash a zip that isn't valid doesn't do anything at all to your phone... it just... doesn't work and sends you on your way. Absolutely nothing you type comes off as a "real" problem.
Anyways, I'm just going to say straight out, that I think you're trolling and that it's sad that you made an account just to waste your time.
I'm done with this thread.
TJDuckett said:
I don't believe you anymore. Even Root tutorials direct you to install a rom after rooting, which would put you at 1.47.65 or whatever even without 2.2 upgrading.
Trying to flash a zip that isn't valid doesn't do anything at all to your phone... it just... doesn't work and sends you on your way. Absolutely nothing you type comes off as a "real" problem.
Anyways, I'm just going to say straight out, that I think you're trolling and that it's sad that you made an account just to waste your time.
I'm done with this thread.
Click to expand...
Click to collapse
think what you would like, im not a kid. ive answered your questions. computers or phones is nothing new to me. family works for sprint, but will not mess with the rooting part of it. so i was left alone on this. ive searched and searched and what u have read is where i am at. basically i am wanting a custom theme. i have tethering and all that crap that works fine. but a theme wont work and a rom to be 1.47 or whatever was never put on, i have what i posted and have everything a rooted phone should have. obviously im stuck on that rom part of it. no reason to be a **** or call someone a troll or say their trolling, when their asking questions. if ur intentions wernt to help, than dont reply. u wasted ur own time.
First time ever trying to root a phone, and I tried using the one click method to root my phone, and when I got to the point of installing the radio, it wouldn't work because I stupidly forgot to turn off my anti virus.
So when I attmepted to go back and give it a second try, the program will not restart the daemon server, this is what shows in my command prompt.
"HTC Inspire 4G Simple One Click S-OFF, Downgrade, Clockwork, Root
Scripted by bubby323 of XDA-Developers
Press any key to continue . . .
Press any key to continue . . .
Before we begin: Make sure your phone is plugged into your computer via USB and
"Charge Only" mode is selected.
Press any key to continue . . .
Also make sure you have installed, then uninstalled the "HTC Sync" program.
We need its drivers to root your device. If you have not done this, exit the pro
gram, then try again when you are finished.
Press any key to continue . . .
Changing directory to use the needed resources...
We will now stop, then restart the ADB server. When it's ready, it will say "Dae
mon started successfully "...
Restarting adb server...
"
and it just gets stuck there.
If anyone can help me with this, it would be GREATLY appreciated.
You need to make sure that USB Debugging is enabled. It's possible that during your initial run, some things worked, and thus the USB Debugging was unselected. Go to Menu>Settings>Applications>Development and make sure that it is indeed ticked.
I've made sure it was in charge only, made sure fast boot was off, and the unknown sources was turned on, as well as USB debugging turned on god only knows how many times thinking I had made a stupidly simple mistake like that.
Edit: I just tried it again, and now it repeatedly says that the daemon server is not started, and says it cannot connect to daemon
I'm no pro, having just rooted my first Android. I would consider the possibility of the following. 1) Corrupted usb drivers, reinstall drivers. 2) Antivirus deleted some one click files, remove and redownload.
Sent from my Desire HD using Tapatalk
I guess it's worth a shot, I'll try it when I get home from work tonight.
fernandezhjr said:
I'm no pro, having just rooted my first Android. I would consider the possibility of the following. 1) Corrupted usb drivers, reinstall drivers. 2) Antivirus deleted some one click files, remove and redownload.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Number 2 was the most common issue when I read through Bubby's thread a month or so ago (all 3200 posts). If you use MS Security Essentials, you have to completely uninstall BEFORE downloading the program.
I didnt even have security essentials on my PC, all I use is Eset smart secuirty, and I had it completely closed down, shut down the process from task manager.
Alright, I went back and followed everything from scratch. Uninstalled Eset smart security, removed all of the HTC drivers, then reinstalled them, and started the process over completely
seems to have worked flawlessly so far, but I haven't tested the radio yet.
Edit: it works, flawless victory
You should realize that you may not completely kill the antivirus from process manager. You would need to shut it down from within the program. There are many processes running that are in task manager that belong to the antivirus, some which you may not recognize.
Sent from my Desire HD using Tapatalk
like I said in my above post, I completely uninstalled it, and everything works now.
I hope I'm not asking a bit much, but could someone showed me a detailed instruction set for my first time trying to install a new ROM on my droid?
I want to put Cyanogen on it, but have no clue how to go about doing so.
chaosrde said:
I hope I'm not asking a bit much, but could someone showed me a detailed instruction set for my first time trying to install a new ROM on my droid?
I want to put Cyanogen on it, but have no clue how to go about doing so.
Click to expand...
Click to collapse
There's one stickied to the general section.
[For the life of me, I'll never understand how a thread that's stickied and should be so clearly visible, gets missed/ignored by so many people.]
Well I have it working for the most part, but I can't find the Kernal needed for Cyanogen 7.0.3(Is it included with the rom?), and would I need a different radio for it as well?
chaosrde said:
Well I have it working for the most part, but I can't find the Kernal needed for Cyanogen 7.0.3(Is it included with the rom?), and would I need a different radio for it as well?
Click to expand...
Click to collapse
I would think that both the kernel and the recommended radio questions you ask would probably be addressed in that roms thread.
If not in the original post, then by someone asking in the comments.
I apologize if I seem like a complete idiot to this stuff, It just never really occurs to me to go searching for things like this, because 90% of the time when I try that in the past, it doesn't work for my specific issues.
Thanks for taking the time to respond though, I'll go take a look through the rom thread.
chaosrde said:
I apologize if I seem like a complete idiot to this stuff, It just never really occurs to me to go searching for things like this, because 90% of the time when I try that in the past, it doesn't work for my specific issues.
Thanks for taking the time to respond though, I'll go take a look through the rom thread.
Click to expand...
Click to collapse
I know, a lot of people feel the same way.
ROM threads are unique in that they are focused on the ROM in question. Comments/questions/answers are by/from users of that specific ROM.
I visit many of them, most of which I've never even flashed on my phone, just to get myself educated on little quirks that people are experiencing.
Hi guys, I'm pretty new to rooting so tell me if i need to give more info etc cause I know i can be a bit vague.
So I rooted my phone no problem via the all in one kit thing and installed cyanogen, but this was right before the big android update so I wanted to switch back and update to that, but somewhere along the line i got rid of all the Roms (I think)
The stage it's at now: I can boot normally but the startup wizard fails, I assume this is because the stock operating system isnt hooked up to run, regardless I can't find a copy or figure out how to run it. (before my TWRP seemed to stop running on startup)
Bootloader: I don't know how it ended up relocked after I'd unlocked it but am guessing that is why i cant access the custom recovery at the moment (twrp)
If anyone is able could you walk me through, or point me to a guide to show:
How to unlock a relocked phone,
How to get a Stock version of Android (anything after 4.0 I guess because it will auto update?) running on there
Tell me if I'm being dumb in any part of this (apart from pissing about with things I don't understand, haha)
OK, So i'm unlocked and back onto TWRP, that was easy though, What I do need help with is working out how to install the factory Operating system again, last time I tried that is what caused the relocking etc so any help would be amazing.
Thanks, Simon
Redijedeye said:
OK, So i'm unlocked and back onto TWRP, that was easy though, What I do need help with is working out how to install the factory Operating system again, last time I tried that is what caused the relocking etc so any help would be amazing.
Thanks, Simon
Click to expand...
Click to collapse
Is this the same device as the one you are asking about in? [Q] How do I know what RUU to use, and more by Redijedeye
sd_shadow said:
Is this the same device as the one you are asking about in? [Q] How do I know what RUU to use, and more by Redijedeye
Click to expand...
Click to collapse
Sorry yes, meant to close this post now that this particular problem was kinda sorted but didnt get round to it last night. Unless you know a way to get the correct firmware for the wifi? Just seems strange it'd update wrong.
Redijedeye said:
Sorry yes, meant to close this post now that this particular problem was kinda sorted but didnt get round to it last night. Unless you know a way to get the correct firmware for the wifi? Just seems strange it'd update wrong.
Click to expand...
Click to collapse
No, I don't.
I consider this [Completed] and have thread closed.
Hey everyone.
I was using a custom ROM, just to try Lollipop, and saw the OTA rolling out today.
I started Bacon Root Toolkit and returned my phone to stock, with the 4.4.4 original ROM, with the automatic download.
Then I tried updating it through the phone, but the OTA was not available for me yet. So I downloaded the file everyone was using to manually update it (cm-12.0-YNG1TAS0YL-bacon-signed.zip).
Used to same option on BRT to return to stock but this time selected the zip file I downloaded.
It started ok, with the prompt window showing the files pushed to the phone, like modem, system, cache, etc.
But then it stopped, waiting for the device.
I looked at it and the screen was turned off. I had full battery.
Waited some minutes and nothing. The phone was not recognized anymore. And it's also not turning on.
Any idea what happened and what I can do?
Thanx.
Cappelletti said:
Hey everyone.
I was using a custom ROM, just to try Lollipop, and saw the OTA rolling out today.
I started Bacon Root Toolkit and returned my phone to stock, with the 4.4.4 original ROM, with the automatic download.
Then I tried updating it through the phone, but the OTA was not available for me yet. So I downloaded the file everyone was using to manually update it (cm-12.0-YNG1TAS0YL-bacon-signed.zip).
Used to same option on BRT to return to stock but this time selected the zip file I downloaded.
It started ok, with the prompt window showing the files pushed to the phone, like modem, system, cache, etc.
But then it stopped, waiting for the device.
I looked at it and the screen was turned off. I had full battery.
Waited some minutes and nothing. The phone was not recognized anymore. And it's also not turning on.
Any idea what happened and what I can do?
Thanx.
Click to expand...
Click to collapse
You used an OTA zip to return your phone to stock? That's your problem. An OTA zip isn't a full system, it's a partial system that builds on top of the existing previous build to update the phone. So by not fully understanding what you're doing you've caused a catastrophic failure on your device.
At the moment your only hope is this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
If anything is going to save your phone it's that, so have a read and give it a try.
And get rid of that toolkit. I get it, toolkits might seem like they make things so much easier, but they're nothing but trouble. In this instance it's allowed you to flash an incomplete system to your phone, possibly bricking it. I'm not blaming the toolkit for this situation, this situation was caused by human error. But, if you had never used a toolkit in the first place you wouldn't have bypassed some crucial, basic, elementary knowledge. Knowledge that's needed to know what you're doing when flashing.
Toolkits allow the user to do things to their phone without actually having a knowledge of what's going on. Had you not used this toolkit in the first place you might have a better working knowledge of flashing, and you might not be in this situation right now. So yeah, maybe they seem easier, but in the long run you're better off without them. You're much better off properly learning the ins and outs of flashing and owning a modified phone.
Transmitted via Bacon
timmaaa said:
You used an OTA zip to return your phone to stock? That's your problem. An OTA zip isn't a full system, it's a partial system that builds on top of the existing previous build to update the phone.
Click to expand...
Click to collapse
The OS12 OTA zip is actually a full zip like the CM12 nightlies (the partition images are exactly the same as in the 20150411 nightly apart from boot.img & system).
You can't use the BRT to flash it though because it doesn't contain a system.img - /system is flashed using the same method as the nightlies (system.new.dat & system.transfer.list)
Spannaa said:
The OS12 OTA zip is actually a full zip like the CM12 nightlies (the partition images are exactly the same as in the 20150411 nightly apart from boot.img & system).
You can't use the BRT to flash it though because it doesn't contain a system.img - /system is flashed using the same method as the nightlies (system.new.dat & system.transfer.list)
Click to expand...
Click to collapse
Thanks man, good to know.
Transmitted via Bacon
Spannaa said:
The OS12 OTA zip is actually a full zip like the CM12 nightlies (the partition images are exactly the same as in the 20150411 nightly apart from boot.img & system).
You can't use the BRT to flash it though because it doesn't contain a system.img - /system is flashed using the same method as the nightlies (system.new.dat & system.transfer.list)
Click to expand...
Click to collapse
That's why I tried it. People were using it on TWRP.
As I had just returned the phone to stock I didn't have a modified recovery. So I used BRT.
I had flashed lots of times before. On previous phones and tablets. Found BRT just yesterday.
I'll take a look at the provided link in a moment. I'll let you guys know if it worked for me.
Thanx.
timmaaa said:
You used an OTA zip to return your phone to stock? That's your problem. An OTA zip isn't a full system, it's a partial system that builds on top of the existing previous build to update the phone. So by not fully understanding what you're doing you've caused a catastrophic failure on your device.
At the moment your only hope is this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
If anything is going to save your phone it's that, so have a read and give it a try.
And get rid of that toolkit. I get it, toolkits might seem like they make things so much easier, but they're nothing but trouble. In this instance it's allowed you to flash an incomplete system to your phone, possibly bricking it. I'm not blaming the toolkit for this situation, this situation was caused by human error. But, if you had never used a toolkit in the first place you wouldn't have bypassed some crucial, basic, elementary knowledge. Knowledge that's needed to know what you're doing when flashing.
Toolkits allow the user to do things to their phone without actually having a knowledge of what's going on. Had you not used this toolkit in the first place you might have a better working knowledge of flashing, and you might not be in this situation right now. So yeah, maybe they seem easier, but in the long run you're better off without them. You're much better off properly learning the ins and outs of flashing and owning a modified phone.
Transmitted via Bacon
Click to expand...
Click to collapse
I didn't try it yet, but I forgot to mention that the phone is totally dead. No lights or whatever. Neither the charging light is turning on.
Cappelletti said:
I didn't try it yet, but I forgot to mention that the phone is totally dead. No lights or whatever. Neither the charging light is turning on.
Click to expand...
Click to collapse
Numerous people who had phones which were showing absolutely no signs of life whatsoever have revived their phones using that unbrick tool I linked you to. All indications from these phones were that they were hard bricked but that tool saved them, it might take several attempts and a few hours but it's worth a try.
Transmitted via Bacon
timmaaa said:
Numerous people who had phones which were showing absolutely no signs of life whatsoever have revived their phones using that unbrick tool I linked you to. All indications from these phones were that they were hard bricked but that tool saved them, it might take several attempts and a few hours but it's worth a try.
Transmitted via Bacon
Click to expand...
Click to collapse
I'll try it, for sure.
Thanx.
timmaaa said:
You used an OTA zip to return your phone to stock? That's your problem. An OTA zip isn't a full system, it's a partial system that builds on top of the existing previous build to update the phone. So by not fully understanding what you're doing you've caused a catastrophic failure on your device.
At the moment your only hope is this:
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
If anything is going to save your phone it's that, so have a read and give it a try.
And get rid of that toolkit. I get it, toolkits might seem like they make things so much easier, but they're nothing but trouble. In this instance it's allowed you to flash an incomplete system to your phone, possibly bricking it. I'm not blaming the toolkit for this situation, this situation was caused by human error. But, if you had never used a toolkit in the first place you wouldn't have bypassed some crucial, basic, elementary knowledge. Knowledge that's needed to know what you're doing when flashing.
Toolkits allow the user to do things to their phone without actually having a knowledge of what's going on. Had you not used this toolkit in the first place you might have a better working knowledge of flashing, and you might not be in this situation right now. So yeah, maybe they seem easier, but in the long run you're better off without them. You're much better off properly learning the ins and outs of flashing and owning a modified phone.
Transmitted via Bacon
Click to expand...
Click to collapse
IT WORKED!
It was 1am yesterday when I messed up, so I decided to create the thread here and go sleep, after some troubleshooting that didn't work. I believe I'd come accross that thread you pointed, but thanks for it.
I mean... really, THANX!
Cappelletti said:
IT WORKED!
It was 1am yesterday when I messed up, so I decided to create the thread here and go sleep, after some troubleshooting that didn't work. I believe I'd come accross that thread you pointed, but thanks for it.
I mean... really, THANX! [emoji14]
Click to expand...
Click to collapse
Awesome, no worries, glad to help.
Transmitted via Bacon
I spent half yesterday, into the wee hours of the morning trying to get my pixel back to life. Figured I'd post my goof as it may help someone later.
I flashed the aosp build using the android flash tool just out of curiosity. Realizing dual sim did not work on asop without gapps of some sort, I decided to go back to the public builds. That's where things went crashing down, fast and hard. Literally 6 hours trying everything I knew and everything I could find. Tried 3 different computers, multiple different cables, made sure adb and fastboot were updated like 5 times, tried using the flash tool, tried downloading and using flash all, tried erasing everything and starting over, tried lineage, tried side loading via adb, tried fastboot flashing individual images... All failed, flash tool complaining about not enough space, local installs complaining about missing partitions, not valid files, just everything that could go wrong did. The only thing I could successfully get installed was aosp.
The solution? What was preventing it? I use ublock and privacy badger. Disabling those, off to the races, everything went smoothly and I'm back up and running. What puzzled me, how could I used the flash tool to go to aosp but not back? Why, or how was it interfering with a local flash? Maybe things got screwed up somehow and that was messing with the local flash...idk but if you're in my position try disabling those and give it a whirl.
Which flash tool are you talking about? Everything you're doing sounds overly complicated.
I recommend sticking with cmd for windows, and terminals in linux .
noidea24 said:
Which flash tool are you talking about? Everything you're doing sounds overly complicated.
I recommend sticking with cmd for windows, and terminals in linux .
Click to expand...
Click to collapse
I tried that, I tried using the flash all bat for windows and then I tried flashing individual images via adb. Nothing worked. I have no clue why the local installations kept failing unless, as I said something got messed up using the android flash tool via chrome.
Here's the flash tool which I used to load aosp.
I can't understand what problem you were facing:
use newest platform tools
use newest Google USB drivers
use firmware image of google developers page
reboot into fastboot (by volDown + Power or via adb)
flash-all
working smooth like butter if you can read
hanni2301 said:
I can't understand what problem you were facing:
use newest platform tools
use newest Google USB drivers
use firmware image of google developers page
reboot into fastboot (by volDown + Power or via adb)
flash-all
working smooth like butter if you can read
Click to expand...
Click to collapse
I'm guessing you can't read, I did all that. I'm simply posting this in case someone else runs into the same issue I did. As I said, I'm not sure if trying the aosp build changed anything or any of my numerous attempts fouled something. The only way back was disabling ublock and privacy badger and using the flash tool. For clarification, I've been doing this since the very first android, the T-Mobile G1 and am not new to this game.
You were right, I didn't read carefully enough, or to call it by it's name, I misunderstood your posts. The title of your thread lets believe that you have trouble returning to stock and you need help on that.
That something goofy kicked you out of routine I didn't read (was reading from newest to oldest post, so tbh, that was not clever)
I'm also not new to this, so let us stay calm. Nice that you share your experiences.
I would suggest to change the title in: 'try this if you have trouble with returning to stock' I r something similar.
Have a good time!
hanni2301 said:
You were right, I didn't read carefully enough, or to call it by it's name, I misunderstood your posts. The title of your thread lets believe that you have trouble returning to stock and you need help on that.
That something goofy kicked you out of routine I didn't read (was reading from newest to oldest post, so tbh, that was not clever)
I'm also not new to this, so let us stay calm. Nice that you share your experiences.
I would suggest to change the title in: 'try this if you have trouble with returning to stock' I r something similar.
Have a good time!
Click to expand...
Click to collapse
No problem. I'm still at a loss as to what went wrong but needless to say, for myself, I won't be trying AOSP via the flash tool again.
Little late on this, but I was in a rut as well then realized I had adblockers on which caused issue with the flash tool.
Easiest way to get back to stock is by using Android Flash Tool https://flash.android.com/back-to-public