My Win HD stopped working after a botch from the insider app. It goes into a reboot cycle. Whenever I try to ask Microsoft for advice or info on my phone being supported by the recovery tool, they stop responding. BLU tells me it's microsoft's problem. Sometimes they both tell me to contact the seller for help. The seller unfortunately is amazon, and they can't do anything. I need a new method since all three are refusing to help me. Is there any other way I can reflash my device since the recovery tool doesn't support my specific model? I already tried factory reset and that didn't do any good.
Related
I have BUILD phone from Microsoft and it start random rebooting. I then tried to reset it using the hardware reset method. Saw gears for hours, finally decided to power it off and now it just runs battery down rebooting to Nokia logo.. then off... Nokia logo.. then off...
I have Nokia Care Suite and have tried to re-flash it and been successful with only one ROM but it was an ATT one that now has the logo but the rebooting started again.
Questions:
I would like to try to salvage this phone to any ROM that will allow me to have a Windows Phone 8 os again. I don't know which versions to try. I have tried a lot of the rogers, euro, and others and get a message on not supported for device.
I will gladly 'donate' to someone that can help me out with this device. Ultimately, I would like to have something that would give my internet tethering back on my unlimited AT&T plan if possible.
Any help?
bryanb2 said:
I have BUILD phone from Microsoft and it start random rebooting. I then tried to reset it using the hardware reset method. Saw gears for hours, finally decided to power it off and now it just runs battery down rebooting to Nokia logo.. then off... Nokia logo.. then off...
I have Nokia Care Suite and have tried to re-flash it and been successful with only one ROM but it was an ATT one that now has the logo but the rebooting started again.
Questions:
I would like to try to salvage this phone to any ROM that will allow me to have a Windows Phone 8 os again. I don't know which versions to try. I have tried a lot of the rogers, euro, and others and get a message on not supported for device.
I will gladly 'donate' to someone that can help me out with this device. Ultimately, I would like to have something that would give my internet tethering back on my unlimited AT&T plan if possible.
Any help?
Click to expand...
Click to collapse
The only version I can seem to flash to so far is:
(059L848) RM820_059L848_1232.5962.1314.0001_961.vpl (RM-820 NDT AMERICAATT Black)
Since it's an American model, you could try 059R2L5 RM-820 AT&T DEVELOPER DEVICE BLK or 059R4W6 RM-820 GLOBAL BLACK SWAP and see if that fixes your issue.
Recovery failed
When I try both of those, I get:
0xFA001304: Platform ID check fails. Reason(s): The FFU file is not meant for this product. The platform ID of image does not match with platform ID of the device.
I don't think the \\BUILD phone is an american model.
Now first of all let me get started. I really will tip over PayPal for a beer for anyone who helps with that, because I've spent the whole day and can't get it to work.
Let me first of all explain my situation. I bought a Kindle 7 yesterday for the family business so that the staff can consult e-mails and access Google while being able to block most apps such as Facebook so they don't mess around (they already do it enough with their personnal phones ) and having read a bit about applications that would allow me to creates multiple users, I realised that I had to be rooted.
Now I had rooted my Galaxy S4 in the past and remembered it being an incredibly easy process so I figured, eh, might aswell give it a go, and that's when all the issues started.
I realised that this needs to be done using Bin4ry's method after installing the ADB drivers (hopefully I got all of this right). But here's where the first issue starts.
When I try to install the ADB drivers, I get the following error code :
So at first I was trying to restart my computer but came to the conclusion that it wasn't the issue. So I tried another method !
I tried installing the ADB directly from the Android SDK, using the link and such, which seemed to work well since I didn't have an error message and now the device was actually asking me to authorize for usage as ADB or whatever the message it says.
So I was optimistic and all, but then came the second problem... I tried running Bin4ry's program but now the issue was something else. When it tried running it, instead of saying device absent, it was now saying the the ADB was out of date (see below). After reading online, I was told thats its because the Android ADB and Bin4ry's one are conflicting, so some people suggested killing them in task manager, which I tried but also said they would come back automatically (which they also did). After that I found an ADBFIX little program, but had no clue where to find the Android ADB....
The reason I'm saying all that and making such a long post is to basically say that I've tried as far as my knowledge goes... I've checked the forums and everything, but most ''killing issues'' applied to HTC devices and not directly Amazon...
Please, I'd love help of any kind ...
Thanks..
Simon
s15.postimg(dot)org/ccwn8hbaz/ADB1.jpg
s14.postimg(dot)org/uf795dlz5/ADB2.png
s24.postimg(dot)org/y4ni1pf05/ADB3.jpg
I was told that since I had under 10 posts, I couldn't post any links, but had taken screenshot of my error messages.. Please replace the (dot) in the links above to hopefully help you understand my issues.
You may just want to use Towelroot and not mess with ADB at all. I've seen reports that it works on the newer hdx, so it might work on our kindles as well.
http://lifehacker.com/towelroot-roots-android-kitkat-devices-in-one-tap-no-p-1592226618
Just tried, unfortunately was told that this device isn't supported ...
What generation Kindle did you buy?
Korgot said:
Let me first of all explain my situation. I bought a Kindle 7 yesterday . . .
Click to expand...
Click to collapse
You know the newest Kindle (4th gen) isn't rootable yet. 2013 models (3rd gen) use Firerooter (KFSOWI modding community on Google+). This forum is for earlier models.
Greetings everyone!
Few weeks ago, I gave my device to a friend of mine to manually update it. Something went wrong so he decided not to go any further. Yday i tried to "Factory reset", after reset some error pop'd in the left upper corner of the phone.It says:
[LGE_SECURITY] ERROR: boot image signature
Critical failure: Unable to start kernel.
Unrecoverable bootloader error (0x00000002).
Anyone had any similiar or even the same problem as i am facing right now? Thanks in advance.
best regards, Milan
Guy didn't know what he was doing apparently. Your handset is still locked and he apparently tried installing a 3rd party ROM, lemme guess, you wanted a newer version of Android than 4.1., which is a reasonable enough thing. Problem is that out of the box you can't do that because it only boots images signed by LG and they abandoned development after releasing 4.1 and a couple of minor point releases. You aren't totally screwed but if you were having somebody else do it for you, you might need to get some help. You can find the details elsewhere here, or more likely point a more skilled friend at it, but here it is in a nutshell.
You need to get LG's official updating software (from the LG website) and you need to fiddle with it a bit until you get it to do a rescue because it expects to have already paired up with the phone while it was still working. If you already had it installed, great because it will make it easier. Anyway, you will probably have to manually pick your model and input the IMEI since it won't already know those things and it will go out and fetch the most recent image. You will push VOL Down and insert the USB cable from a powered down state, it will then do the rest. Good chance you will even retain your data unless that 'factory reset' you mention actually succeeded.
Of course that will only get you back to stock 4.1. Read around for the official way and several un-official ways to unlock your boot loader. Once that is done you can install a better recovery and then a newer version of Android. But the first step is to restore the stock software since you have to have a running phone to be able to unlock it.
And no, nobody has ever been able to explain WHY they lock them, but every single manufacturer seems determined to do it, chipmakers put a lot of work and ad copy into how extensive and unbreakable the locks on their newest chip is, etc. And then they either bow to customer demand and add an unlock feature or we here at xda do it for them... as a courtesy of course. Truly we do live in the asylum. Wonko the Sane was onto something.
Hi. So I decided it was time to move to EMUI 9 and after looking at various posts on here I believe the easiest way was to you EMUI Flasher to flash the ROM (coming from 8.1 rooted).
The phone restarted and went to EMUI installer but after 10% or so I got an error. It asked if I wanted to go to erecovery or reboot the device (I think). As far as I was concerned it was only checked that the ROM was OK and hadn't installed anything so I selected reboot. Now the phone won't come on. I've tried holding the power button for an inordinate period of time but it's not happening.
Is there anything I can do?
EDIT - I've tried a different USB port on my PC and can see something in the device manager now ---- Kedacom USB Device > Android Bootloader Interface ---- which gives me a sliver of hope this can be fixed.
EDIT2 - I could send img files through fastboot all day (phone was recognised even though it wouldn't turn on) but couldn't fix this. Gave DC Phoenix a try but no luck there either. Think I've killed it.
EDIT3 - Just in case anyone ever comes across this. I tried below but nothing would work so I contacted someone on Telegram who said the only option was to open the phone up and short it out. No way I was attempting that so I eventually contacted Huawei UK and told them it had died during an update, never let on that it was MY fault! Anyway, they sent out a prepaid envelope to send to a their repair partner. I won't name them here but they have terrible reviews on Yelp so I was a bit apprehensive. I know the phone arrived with them last Friday as I checked the post tracking but I never heard anything from them. Today out of the blue my phone has come back to me in full working order, repaired under warranty! Considering there was only one thing I was really using root for and it was only a slight convenience, I think I'll just leave it as is.
Are you able to flash anything in fastboot?
Are you able to boot to recovery via fastboot? Disconnect the cable after you give the reboot recovery command in fastboot.
You may be able to flash each component of emui, system, vendor, oeminfo, kernel etc. Seems that it's missing most or all of it.
Bootloader sounds like it's intact.
Btw. The easiest way to update to emui would be to wait for an OTA from Huawei.
Personally I don't see a point, pie is not as efficient as Oreo nor does it have any features to merit an upgrade, in fact you would lose features (4k zooming, functional TWRP)
Good day all. Long time lurker of these forums, and I am officially throwing in the towel on my amateur attempts to update my P20 Pro (CLT-L29 C636) from Android 8 to something newer. I've managed to soft brick the thing, getting stuck in a boot loop. I can get to fastboot, and I can (sometimes) get it to enter dload mode with an OTG cable and a thumb drive. I messed something up early on in the process and I am completely unable to go any further. Dload gets to 5% then fails every time, with every thumb drive I've used.
I am willing to accept that I just don't have the technical ability to take this journey any further. Being that I live in the US (Western New York), Huawei lists no official repair centers in the states. Are there any trusted 3rd party repair services I could send my phone to and have an expert attempt to repair the software? At this point it's been bootlooping so long the Huawei logo is ghosted onto the AMOLED screen. I would love to have this phone operational again.
Any thoughts I would greatly appreciate it!
Hold Both Vol + Power until Emergency Rescue pops up.
After that, restore Stock, unlock Bootloader, install any android 10/11/12 GSI u want.
Tried that. It's stuck in bootloop and only occasionally responds to boot prompts. On the couple of times it got past dload failed and prompted me with invalid install and offered to boot to Emergency Recovery, it fails to load the recovery dialog and drops back into a boot loop.
I promise, I have been back and forth with attempts on this phone for four months, and if I thought there was any new surface level tip or trick I haven't tried, I would still be searching. I feel like it's at a point where only specialized software or a physical test point, or something else beyond my technical ability will fix this phone.
I do appreciate the suggestion, though.
Unlocked Phone? So it *might* be possible to recover i imagine if u get twrp running, might need some dirty work, but not impossible.
Edith did forget to mention; Can u see ur Phone via adb/fastboot on your PC?
aLcaTr4z said:
Unlocked Phone? So it *might* be possible to recover i imagine if u get twrp running, might need some dirty work, but not impossible.
Edith did forget to mention; Can u see ur Phone via adb/fastboot on your PC?
Click to expand...
Click to collapse
Sorry if I sent the wrong impression. The bootloader is still locked. It is only carrier unlocked.
I can locate it on DC-Unlocker on fastboot but it won't let me load any files to it.
With locked BL is not much hope left i guess. Hisuite Recovery fails too i imagine?
aLcaTr4z said:
With locked BL is not much hope left i guess. Hisuite Recovery fails too i imagine?
Click to expand...
Click to collapse
Oh yeah. HiSuite recovery states that this model isn't compatible with eRecovery and to take the phone to a service center.