Hello everybody!
Some of you may know that I got bricked my Lumia 925.
Well... I got another Windows Phone! Lumia 920!
So... I will continue helping others and maybe even making more software for recovery and much more!
:good:
:fingers-crossed: Fingers crossed not to brick this one!
A safe way to brick it: move a partition in MSM mode. The result was the "no bootable..." trick. I "resolved" it by buying a 920 with broken display and swapped the motherboard. Sold the bad unit... Months later I read that a developer ROM this could have fixed.
Related
Just a few words...to say a big thanks to this forum - I´ve learnt a lot from here and tried to give back to the community as much as I could. My Prophet was stolen last week, and I replaced it...with a Nokia E61 PDA. Finally Nokia has a real Symbian OS9 V3 business PDA, and I don´t have to bother with Win Mobile 5 anymore. Only feature missing is A2DP, but Nokia will deliver with next firmware update. Take a closer look at this model, if you want to do serious business comms. Prophet was great, but I need UMTS data now. Good luck to all of you, and keep up the good community work. BTW HTC will soon also sell under it´s own brand...Dopod ))
Well I'm sorry you had to downgrade 8)
Sorry to hear you had to downgrade due to a stolen Prophet!...
Hello All,
So I like many others I have the wicked screen flickering issue and have already talked to the GS manager at my local store. They are awaiting my unit to ship, could be up to a week because the warehouse doesn't have enough in back-stock.
In the meantime I can still use my tablet, but the question is..should I risk rooting it before the swap? I've been rooted and flashing different ROMs and Kernels for awhile on my Gnex but just briefly looking over the Nexus 7 forums it seems like some people are having a tough time with drivers and bricking. I realize the Gnex has been around way longer and the devs know it like the back of their hand, but should I risk rooting over these next few days and possibly running into a snag before swapping it out at Gamestop?
If it helps to know what computer I'd be doing the rooting/flashing from I could either do it on a Win7 32bit machine or a Macbook Pro running Lion.
Any insight would be greatly appreciated. Sorry if this is the wrong forum, but it seemed like a split between development and returns.
-Steve
stevvveo said:
Hello All,
So I like many others I have the wicked screen flickering issue and have already talked to the GS manager at my local store. They are awaiting my unit to ship, could be up to a week because the warehouse doesn't have enough in back-stock.
In the meantime I can still use my tablet, but the question is..should I risk rooting it before the swap? I've been rooted and flashing different ROMs and Kernels for awhile on my Gnex but just briefly looking over the Nexus 7 forums it seems like some people are having a tough time with drivers and bricking. I realize the Gnex has been around way longer and the devs know it like the back of their hand, but should I risk rooting over these next few days and possibly running into a snag before swapping it out at Gamestop?
If it helps to know what computer I'd be doing the rooting/flashing from I could either do it on a Win7 32bit machine or a Macbook Pro running Lion.
Any insight would be greatly appreciated. Sorry if this is the wrong forum, but it seemed like a split between development and returns.
-Steve
Click to expand...
Click to collapse
Is there something specifically you want to do with root? Before you root it, you have to unlock the bootloader [and probably flash cwm/twrp]. The oem bootloader unlock erases all your data [you can back it up beforehand though] too.
So if you're only gonna have it for a few days, I'd say probably not. But if you're an android nerd, and like to flash things, then I'd say go ahead if you don't mind the work of re-locking the bootloader and flashing the stock rom/recovery again later when you go to exchange it.
Drivers aren't really an issue anymore since Asus released official drivers. Only at first were there issues because we DIDN'T have signed drivers, so Windows complained about it and Windows 8 wouldn't even install them without some huge work around.
But yes. I would. You might as well test the waters on that one since it's going back. The Nexus Toolkit can restore the factory image and relock your device before you take it back.
Who knows, a new rom and kernel may fix your screen issues. Remember the N7 that came with ICS? Maybe yours has beta drivers on it or something...
Thanks to both! Sorry I went on an impromptu vacation. But I did test the water with my N7using the toolkit. Returned it. My new one unfortunately has a little backlight bleed, but I don't think Gamestop will keep replacing them.
Thanks again.
Hi guys, I'm new here so please bear with me. Also, I know this is mainly Android website, so sorry in advance.
I have Nokia Lumia 520 for 3 years straight, not yet unlocked, modded or anything. And I know I should buy more powerful Android phone, but this phone is dear to my heart and I don't want to replace it. But here is the deal there are no new apps, old ones don't get new updates (lately even Facebook apps don't work, iE is shutting down by itself). So I was thinking that I should "upgrade" it somehow (read a bunch of posts about my Lumia running on latest Android OS, not yet stable, but if it is capable of doing this, it can do more than this ****ty 8.1)?
Any advice is welcome! Tutorial links for unloking, modding and everything else are welcome too!
I concede defeat...
I'm a brand spanking new owner after my beloved LG G3 shat the bed last week. That phone endured a flashahloics abuse like a champ. It was easy beating up that phone. A sad day to see it finally go lights out.
Unlike the G3, this A2017U (updated to B19) has been giving me grief from day one. I spent the week before arrival reading and collecting tools for the eventual, and immediate, warranty voiding procedure. I felt more than confident in my new abilities to do so. Right from the get go, I was met with an obstacle I couldn't overcome: getting MiFlash to recognize my phone. I have tried everything after scouring the net. Nada. Zilch. No sign of life.
I tried various drivers to no avail. In EDL mode, Windows (8.1 64bit) sees the phone on com4 as a Qualcomm HS-USB QDLoaoder 9008. No matter what version of MiFlash I use, I always get the same error when clicking refresh: Length cannot be less than zero...blah blah blah.
I might be missing the obvious in my attempt to communicate with this phone. While the stock OS is far from horrible, and I could certainly get used to it, unlocking this bad boy is far more attractive. Any help would be greatly appreciated. I'd be happy to answer any questions you may have for me in an effort to troubleshoot.
Cablespider said:
I concede defeat...
I'm a brand spanking new owner after my beloved LG G3 shat the bed last week. That phone endured a flashahloics abuse like a champ. It was easy beating up that phone. A sad day to see it finally go lights out.
Unlike the G3, this A2017U (updated to B19) has been giving me grief from day one. I spent the week before arrival reading and collecting tools for the eventual, and immediate, warranty voiding procedure. I felt more than confident in my new abilities to do so. Right from the get go, I was met with an obstacle I couldn't overcome: getting MiFlash to recognize my phone. I have tried everything after scouring the net. Nada. Zilch. No sign of life.
I tried various drivers to no avail. In EDL mode, Windows (8.1 64bit) sees the phone on com4 as a Qualcomm HS-USB QDLoaoder 9008. No matter what version of MiFlash I use, I always get the same error when clicking refresh: Length cannot be less than zero...blah blah blah.
I might be missing the obvious in my attempt to communicate with this phone. While the stock OS is far from horrible, and I could certainly get used to it, unlocking this bad boy is far more attractive. Any help would be greatly appreciated. I'd be happy to answer any questions you may have for me in an effort to troubleshoot.
Click to expand...
Click to collapse
Uuhh... Custom roms aren't all that good really. They just don't run as good as stock (although rather by a little, but it IS noticeable) and they have some bugs. MiFavor 5.0 is the way to go IMHO. But if you want to try and see for yourself anyways, do this:
Righr click on the QDLoader 9008 stuff, go to Properties, and check the datarate. Should be on 115200 or 128000. It seems that some people have this problem. If not, try with another PC.
But have you tried with axon7toolkit?
I got it going. For some reason my PC and one laptop caused grief with MiFlash not recognizing the phone. I have another laptop with a fresh Win10 install on it and it worked just fine. The Axon7Toolkit took care of the rest. Awesome tool! I'm now unlocked, recovered and rooted.
I did forget to format data after the procedure and was greeted with the 'enter your password' thingamabob. Luckily for me, I did plenty of reading before I got the phone to realize what I needed to do. I'm up and running as of a few minutes ago. I'm pretty stoked to be running AEX on my A7. I loved it on my G3.
Thanks for taking the time to reply, brother. I appreciate it. And thanks to the community for providing a wealth of knowledge for new owners like me. Because of you all, I was able to free my phone of its bondage.
Well, it finally happened. My first no joke, hard brick. I've had every nexus phone, a few HTCs, some motorolas, no hard bricks. But today was my day. :laugh:
I was originally having issues with the device not booting to system on reboot, sometimes it'd boot to bootloader instead.
I thought I'd just do a full reset, BTS, and see if that helped. Nope. Couldn't find partition, max size allowed reached, fail to write, all that.
Looked around, ADB/fastboot out of date? Ripped out windows drivers, uninstalled, drivers from device, used brand new platform-tools. Nada.
Tried different cables, USB ports, and googled modern tech wizardy. Nothing.
Finally got it to write TWRP to both partitions (somehow), thought I'd reboot to recovery and be in the clear. WRONG.
Device started to reboot, windows showed device as "OUSB Bulk" and then my PH1 went black. Unresponsive. Kaput. Donezo.
Brick.
It was real, it was fun, but can't say it was real fun.
I LOVE this phone. Honestly, it's perfect for me. Size, weight. The lot. But it's dead now...
Well, I leased it through Sprint, and as it happens my lease is now up so I can get something new. A bunch of Samsungs and Apples, what to get?
Tbh, I'd get another for exactly the reasons you give. Especially if you can one for a good price.
I'm currently using an op6t as I need a dual SIM phone while working abroad. As good as it is, I can't wait to get back my ph1. I've not seen anything that is a real upgrade.
We have a special topic for questions about choosing a new phone and you should only ask them in it.
Here it is.
Thread closed.