Related
I wondered if anyone knows of a way to 'repair' the system files on a fully locked Windows Phone without wiping the phone?
I've got a problem on my phone, which I've posted in various places but had no help with yet.
I'm on a Lumia 620 these days. It's a troublesome little thing, but I suppose it is new and teething so I'm sticking with it.
Thanks loads for any help!
My dear friend...
If you need to repair the system files it's because you have an unlocked one and started to play with some files or an update failed.
but since the phone is "fully locked", full flashing is the solution...
My advice, get rid of the official ROM and install any custom that can work with WP Backup, that way you'll have a backup to restore apps and its respective data to the phone, if you do a hard reset or change the ROM you can set your phone the way it was before the change.
WP Backup only work with customs...
Any help about the use PM me.
Remember, goodbye official ROM, HELLO CUSTOM...:good:
faustolg said:
If you need to repair the system files it's because you have an unlocked one and started to play with some files or an update failed.
Click to expand...
Click to collapse
It's brand new, unmodified, and never been updated. It may surprise you to learn that files can be corrupted because of file system errors.
And also that you can't unlock Nokia WPs or WP8s.
And that resetting is quicker and easier than re-flashing.
And that I asked about repairing the system files without having to do either. Obviously I know I can reset since I mentioned it in my post.
So well done. A really outstanding reply. So good that I didn't finish reading it. I'll skip the PM thanks.
at45 said:
It's brand new, unmodified, and never been updated. It may surprise you to learn that files can be corrupted because of file system errors.
And also that you can't unlock Nokia WPs or WP8s.
And that resetting is quicker and easier than re-flashing.
And that I asked about repairing the system files without having to do either. Obviously I know I can reset since I mentioned it in my post.
So well done. A really outstanding reply. So good that I didn't finish reading it. I'll skip the PM thanks.
Click to expand...
Click to collapse
your on a Windows phone 8 phone and that isn't unlocked/hacked in any way.
sorry to say this to you but there is no way for you to mod/fix System files on a unhacked phone
this means that you Need to do a Hard reset or Flash a new stock Rom (when possible)
So Mr. "PERFECT"...
You ask, and then you insult...
Why don't you sell that phone and get an android, since you are whining about WP, also the post is another idiotic misplaced post, since you have WP8, you have a serious sight problem: "Windows Phone 7 General" <-- This rings any bell for you?
you're asking about WP8 on WP7, you are incredibly "perfect"
I don't really care if you don't like my answers or if it helps you or not at all; next time don't even ask, since you already know the answer and you like to ask only to bash anyone who tries to give you help.
I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
Thanks,
Reffu
Hi,
same issue here. Today the touchscreen stopped working suddenly after i flashed the Android Revolution HD 5.0 Rom yesterday. However, the S-Pen is still working fine. Installing other ROMs and the Stock ROM via Odin did not help. Issue allso appears in Touch-enabled-Recovery.
I see no reason, why this should be a hardware issue, although my N8000 came back from service a few days ago, where they also replaced the screen and digitizer.
Had anyone this issue before and was abled to resolve it?
Greets
I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2
to read this as a Note 10.1 newbie is not very encouraging. are there any similar facts between all of you like
which Note model do you have
how did you jaibreak (which method)
which rom did you have before
which rom do you have now
how did you flash a new rom
...
is there a way to find out whether the touchscreen is really "dead for touch"?
This is a bit scary - my Note 10.1 is arriving today, and I plan to root it at a minimum. I actually don't mind Touchwiz all that much on my Note 2 (which is running CleanROM ACE), so I think I might just root the 10.1 for now.
So restoring completely back to stock (via Odin) doesn't fix it? That is really odd that ROM-ing this thing might cause a hardware failure...
jiggyman said:
I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?
kkretch said:
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?
Click to expand...
Click to collapse
Did anyone solve this, I'm having the same problem.
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
Just curious - did you just root, or did you root and install a ROM?
I am only rooted so far - haven't felt the need to ROM yet - partially due to worries about this happening. I bought a refurb from Best Buy and only get 90 days of warranty.
reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
If they say you got a new one, you got one. They'll tell you otherwise if there's an issue over the phone.
But I wouldn't be afraid of ROMs, but to be more diligent and wise when it comes to choosing them. It's like choosing a poisonous mushroom versus an edible one to make stroganoff or stir fry. If you know what to avoid for the next time and follow the correct process to doing the root and flashing, there will not be an issues.
This is from someone who has soft-bricked my first tablet and learned how to unbrick my SIM-less Captivate and Note 10.1. It's how you apply the method and how much attention you practice not getting stuck into these situations is what matters. Especially since I bricked my tablet via experimentation and un-bricked it on the same day with ease.
It's not some big complex deal of rocket science or something only the mere geniuses can do, its how you perceive yourself and how you act. If you believe that you will suck and brick it to kingdom come , it will happen intentionally or subconsciously.
In this case, it was a freak accident where the file/s accessed and deleted the wrong files which allowed for capacitive touchscreen use, and it should be reported to x developers if you have not done so already.
I have rooted and used the Revolution HD rom, the Rom where you customize the colors of the bar/other things, and on the Captivate, the AOKP Collective. I further customized the latter with the Xperia launcher as it zips.
Did anyone find a repair for this besides replacement? My Note 2 is doing the same thing now.
Has anyone found a fix for the touch screen not working yet??
Anyone have any ideas?
Technicians input for touch problem
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain that follows the instructions on the mod sites exactly as shown step by step will never have a problem, all those that do end up with paper weights or bricks didn't follow the instructions in numerical order.
Believe it or not even if after you have modded a rom and brought it back to standard they know it has been modded as they have a list of problems associated with repairs after roms have been modded so you are only fooling yourself they don't.
Same as the smoker that tells his Dr he has given up even though all the symptoms prove he really didn't.
So in my expert opinion if you play with modding and stuff it up why should you be eligible for a warranty claim ? The manufacturer has sold you or supplied a working item that you decided to f_ck around with and because of your stupidity expect some one else to pay for it.
I am not saying don't mod your phone with all the great roms out there but please to save yourself a lot of pain and cost some poor smuck trying to run a business in these economic times a lot of out of pocket from sending items back for replacement or warranty plus the time it takes to do all the paperwork and such, please please please read the instructions 300% or triple check you are doing everything exactly as the instructions say and you will be enjoying all the new benefits of that customised rom and laughing at all the noobs stuffing up their brand new device from not doing so.
I know this won't fix your problem but reread that last bit it was your problem as you are to clever to follow some one else's instructions
anyone have solution regarding this issue, mine have issue also, can anyone spare how to fix it without changing hardware?
---------- Post added at 06:47 AM ---------- Previous post was at 06:28 AM ----------
i hope anyone can solve my issue with touch not responding
WOW.. on TOPIC Flashing .pit might help ???
Gardum said:
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain
Click to expand...
Click to collapse
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck
erica_renee said:
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck
Click to expand...
Click to collapse
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir
popohunters said:
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir
Click to expand...
Click to collapse
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .
erica_renee said:
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .
Click to expand...
Click to collapse
thanks sir, im done the flashing with pit files+ official firmware but touch screen is still missing, is there a modem file for touch screen maybe i missed it while its in downloading process before i brick the touch screen
any hope out there?????
confused and need help
i have a n8000 , base band version N8000XXCLL1, my touch screen stoped responding while playing a game , only Spen works , tried resetting , but no help, I'm a no-voice when it comes to programing and need a step by step guide >>>> many thanks in advance for all your help
reffu said:
I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
I got the same problem after rooting my phone.... I used the following method and got ride of that Problem. ..
type this star code in in it Phone dialler *#2663#
Now you should see "TSP"
<update>
TAP on TSP ......it will take 5 seconds only....
......
NOW ENJOY ☺☺
Click to expand...
Click to collapse
Because crowds keep sending me PMs about their blocked devices here is tutorial how to fix it:
SEND YOUR PHONE TO REPAIR SERVICE. YOU NEED A NEW MAINBOARD.
lozohcum said:
Because crowds keep sending me PMs about their blocked devices here is tutorial how to fix it:
SEND YOUR PHONE TO REPAIR SERVICE. YOU NEED A NEW MAINBOARD.
Click to expand...
Click to collapse
If i relock bootloader and go back to stock, will this regain me warranty?
It may give you big chance that they will take it to warranty.
lozohcum said:
It may give you big chance that they will take it to warranty.
Click to expand...
Click to collapse
Im sending it in after hollidays ( approx 2 weeks, still need music on the plane ) and I'll let you guys know.
No need fo dat.
There must be a better solution
Hi lozohcum,
Please can you explain how this problem comes about further for us. At the moment I am failing to see why this has to be the only solution.
I'm no expert but have been messing around with this sort of thing for years and I have never come across something that cannot be fixed through a software hack. The only thing that comes close is the S4's flash counter - and users are only speculating that it is some sort of hardware counter, there are work arounds to avoid increasing it and seasoned devs such as ChainFire[pretty sure it was him] say that it will be reversible. Now if all that is correct I can't see Sony implementing something such as this - that can't be undone on a older and much cheaper device.
Also, I have read your post about how dev's should avoid it from happening while building their ROMs but it didn't explain why this makes it irreversible.
So, like I have asked - please explain to us whats going on that there is no way we can fix this. I feel like there must be a way!
Kind regards
Jono
PS: Taking my friends Xperia J into the service centre tomorrow
JonoIrwinRSA said:
Hi lozohcum,
Please can you explain how this problem comes about further for us. At the moment I am failing to see why this has to be the only solution.
I'm no expert but have been messing around with this sort of thing for years and I have never come across something that cannot be fixed through a software hack. The only thing that comes close is the S4's flash counter - and users are only speculating that it is some sort of hardware counter, there are work arounds to avoid increasing it and seasoned devs such as ChainFire[pretty sure it was him] say that it will be reversible. Now if all that is correct I can't see Sony implementing something such as this - that can't be undone on a older and much cheaper device.
Also, I have read your post about how dev's should avoid it from happening while building their ROMs but it didn't explain why this makes it irreversible.
So, like I have asked - please explain to us whats going on that there is no way we can fix this. I feel like there must be a way!
Kind regards
Jono
PS: Taking my friends Xperia J into the service centre tomorrow
Click to expand...
Click to collapse
I'll try answer it.
the custom rom trigger sony's security system and lock the phone. you need to flash the security system partition to fix it. the stock rom tft bundle doesn't have the image file needed to flash the security partition. thus, reflash a stock rom won't fix it. sony's security system is also very secure and at this time no one is able to hack it.
S4's flash counter - and users are only speculating that it is some sort of hardware counter, there are work arounds to avoid increasing it and seasoned devs such as ChainFire[pretty sure it was him] say that it will be reversible. Now if all that is correct I can't see Sony implementing something such as this - that can't be undone on a older and much cheaper device.
Click to expand...
Click to collapse
samsung have similar security system on their galaxy phone but it relatively not as secure as sony's. on samsung device, the security partition can be modified simply by bmtunlock tool. nevertheless, in the case of sony devices, no one know how to modify sony's security partition.
EDIT: if you're on stock rom, you can dial this code to get your lock status *#*#7378423#*#* . there's a 'simlock.ta' file in sony's tft bundle and it might related to how simlock still work after phone got locked. you can try to remove it from the tft bundle and reflash your stock rom and see what'll happen. i think it's worth to try.
Thanks for the info kurotsugi! Lock status = full lock and I've flashed it about 20 times with different roms in different ways. This one isn't coming back
I hope someone comes up with a solution soon. There must be many people with the same problem. Also I hope the issue gets stickied a bit more - I'm not blaming anyone but myself, I know the dangers of flashing, however I never knew of the issue until it was too late.
Jono
Sent from my GT-I9500 using XDA Premium 4 mobile app
kurotsugi said:
I'll try answer it.
the custom rom trigger sony's security system and lock the phone. you need to flash the security system partition to fix it. the stock rom tft bundle doesn't have the image file needed to flash the security partition. thus, reflash a stock rom won't fix it. sony's security system is also very secure and at this time no one is able to hack it.
samsung have similar security system on their galaxy phone but it relatively not as secure as sony's. on samsung device, the security partition can be modified simply by bmtunlock tool. nevertheless, in the case of sony devices, no one know how to modify sony's security partition.
EDIT: if you're on stock rom, you can dial this code to get your lock status *#*#7378423#*#* . there's a 'simlock.ta' file in sony's tft bundle and it might related to how simlock still work after phone got locked. you can try to remove it from the tft bundle and reflash your stock rom and see what'll happen. i think it's worth to try.
Click to expand...
Click to collapse
thanks @kurotsugi
Flashtool skip simlock.ta file while flashing btw
lozohcum said:
thanks @kurotsugi
Flashtool skip simlock.ta file while flashing btw
Click to expand...
Click to collapse
It's (i think) not in the TA partition, because I had a TA backup from my phone and it didn't unlock again after restoring it.
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! 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: