Well I decided to sell this Atrix HD I just recently acquired and of course because I have no luck at all not even 5 mins after posting the ad on craigslist I ended up potentially bricking it, sadly. I've spent the better part of the past 2 hours scouring threads and posts hoping for a solution but so far I've had no luck so I'll take this last step and ask if anyone might have any advice or solutions. Here's the situation:
- Atrix HD, originally with JB 4.1.1 on it (pre-final AT&T update, mind you)
- rooted with motochopper then bootloader unlocked with motopocalypse, no issues over the past 10 days or so that I've owned this AHD at all)
- was running CM11 nightly without issues (installed with CWM 6.0.5.1, had flashed several ROMs over the past 10 days including CM12, the Mexican retail ROM, and then back to pure AT&T several times, actually
- about 2 hours before making this post I listed it on craigslist and then used Myth Tools to go back to stock (stock being MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27)
- no issues with the flashing process, booted up as expected, worked fine for a few mins then I connected to Wi-Fi and grabbed the final JB update released by AT&T, when it finished I clicked "Install now" to do the reboot and install it
- rebooted into the install and seemed to finish ok, didn't glitch or error out in any respect
- somewhere in the middle of the final reboot after the upgrade it crapped out and then went into the bootloader loop to AP Fastboot (S) mode
- got the following error (which is known to a few other members in the past based on postings I located):
Code:
(typical info at the top of the screen)
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
downgraded security version
update gpt_main version failed
failed to hab check for gpt_backup:0x35
failed to load GPT
CID Read Failure
Invalid CID status 0x69
No SP partition found
Fastboot Reason: Invalid GPT
usb connected
As stated, this AHD was bootloader unlocked without any issues but for whatever is now showing as LOCKED. The thing that concerns me is that if I use fastboot devices it doesn't show the proper info as it used to (the typical TA00etcetcetc model number) - it's showing an 8 digit alphanumeric number I've never seen before so that's a big red flag right there.
I've attempted every process I can locate so far and had zero success at all - only one single fastboot command gives me an OKAY message and that's fastboot oem fb_mode_clear. Every other fastboot command offers up a FAILED (remote failure) error, all of them and I've tried pretty much all of them.
I cannot flash anything to the AHD it seems so I'm guessing that means it's 100% "bricked" in the sense that it's powering up, can be seen from the PC/laptop using fastboot devices, but that's it just not actually there at all for whatever reason.
I've attempted to use 2 different laptops, 1 desktop, multiple various USB ports, cables, you name it I'm pretty confident I've attempted to use it in some respect and still nada, zip, zilch, nothing has come from my efforts. If it's totally bricked then so be it, I'll live, but I keep holding out hope that something I missed will help but it's starting to look like this is beating a dead horse now.
I've attempted using RSD Lite to push the Mexican retail ROM to it (with the edited xml file), the AT&T retail ROM, etc - I can't locate any FXZ files at all so that might still be an option but I simply cannot find any of them if they exist.
So apparently for whatever reason the final JB update pooched this device (even in spite of it not doing it in the past week when I rolled back to stock at least 3 prior times in testing). I'm suspecting - but can't say for certain - that potentially the CWM 6.0.5.1 which I just installed like 2 days ago could be the culprit here; previously using 6.0.4.4 I had no issues whatsoever and that is the only variable that's changed in my flashing process that I can recall.
Anyway, that pretty much covers the situation - if anyone has any advice that might bring this AHD back to life I'm definitely interested in hearing it. I don't have JTAG hardware, don't have a factory cable (if one is required), don't have anyone in the area that does that I'm aware of, etc. Basically if I can't get it resolved on my own then it's a dead device I'll toss in a drawer till that miracle comes along...
Thanks for reading, regardless.
br0adband said:
Well I decided to sell this Atrix HD I just recently acquired and of course because I have no luck at all not even 5 mins after posting the ad on craigslist I ended up potentially bricking it, sadly. I've spent the better part of the past 2 hours scouring threads and posts hoping for a solution but so far I've had no luck so I'll take this last step and ask if anyone might have any advice or solutions. Here's the situation:
- Atrix HD, originally with JB 4.1.1 on it (pre-final AT&T update, mind you)
- rooted with motochopper then bootloader unlocked with motopocalypse, no issues over the past 10 days or so that I've owned this AHD at all)
- was running CM11 nightly without issues (installed with CWM 6.0.5.1, had flashed several ROMs over the past 10 days including CM12, the Mexican retail ROM, and then back to pure AT&T several times, actually
- about 2 hours before making this post I listed it on craigslist and then used Myth Tools to go back to stock (stock being MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27)
- no issues with the flashing process, booted up as expected, worked fine for a few mins then I connected to Wi-Fi and grabbed the final JB update released by AT&T, when it finished I clicked "Install now" to do the reboot and install it
- rebooted into the install and seemed to finish ok, didn't glitch or error out in any respect
- somewhere in the middle of the final reboot after the upgrade it crapped out and then went into the bootloader loop to AP Fastboot (S) mode
- got the following error (which is known to a few other members in the past based on postings I located):
Code:
(typical info at the top of the screen)
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
downgraded security version
update gpt_main version failed
failed to hab check for gpt_backup:0x35
failed to load GPT
CID Read Failure
Invalid CID status 0x69
No SP partition found
Fastboot Reason: Invalid GPT
usb connected
As stated, this AHD was bootloader unlocked without any issues but for whatever is now showing as LOCKED. The thing that concerns me is that if I use fastboot devices it doesn't show the proper info as it used to (the typical TA00etcetcetc model number) - it's showing an 8 digit alphanumeric number I've never seen before so that's a big red flag right there.
I've attempted every process I can locate so far and had zero success at all - only one single fastboot command gives me an OKAY message and that's fastboot oem fb_mode_clear. Every other fastboot command offers up a FAILED (remote failure) error, all of them and I've tried pretty much all of them.
I cannot flash anything to the AHD it seems so I'm guessing that means it's 100% "bricked" in the sense that it's powering up, can be seen from the PC/laptop using fastboot devices, but that's it just not actually there at all for whatever reason.
I've attempted to use 2 different laptops, 1 desktop, multiple various USB ports, cables, you name it I'm pretty confident I've attempted to use it in some respect and still nada, zip, zilch, nothing has come from my efforts. If it's totally bricked then so be it, I'll live, but I keep holding out hope that something I missed will help but it's starting to look like this is beating a dead horse now.
I've attempted using RSD Lite to push the Mexican retail ROM to it (with the edited xml file), the AT&T retail ROM, etc - I can't locate any FXZ files at all so that might still be an option but I simply cannot find any of them if they exist.
So apparently for whatever reason the final JB update pooched this device (even in spite of it not doing it in the past week when I rolled back to stock at least 3 prior times in testing). I'm suspecting - but can't say for certain - that potentially the CWM 6.0.5.1 which I just installed like 2 days ago could be the culprit here; previously using 6.0.4.4 I had no issues whatsoever and that is the only variable that's changed in my flashing process that I can recall.
Anyway, that pretty much covers the situation - if anyone has any advice that might bring this AHD back to life I'm definitely interested in hearing it. I don't have JTAG hardware, don't have a factory cable (if one is required), don't have anyone in the area that does that I'm aware of, etc. Basically if I can't get it resolved on my own then it's a dead device I'll toss in a drawer till that miracle comes along...
Thanks for reading, regardless.
Click to expand...
Click to collapse
Did you edit the script when flashing the stock JB with Mythtools or RSD lite?
Sent from my ATRIX-RAZR HD using XDA Free mobile app
Yep, it even states that in my post:
I've attempted using RSD Lite to push the Mexican retail ROM to it (with the edited xml file), the AT&T retail ROM, etc - I can't locate any FXZ files at all so that might still be an option but I simply cannot find any of them if they exist.
Click to expand...
Click to collapse
Nothing will flash to the device which is the biggest issue of all; if I could flash the gpt_main0.bin file I'd be getting somewhere (since as I understand it that sets the partition layout for the partition img's that will follow in the flashing process).
As stated, the only thing that works in terms of a fastboot command is fb_mode_clear which gets an OKAY response (although fb_mode_set does too, actually). But no other fastboot commands are functional - I tried fastboot -w and get:
Code:
D:\motopocalypse\motopocalypse>fastboot -w
erasing 'userdata'...
Invalid partition name userdata
FAILED (remote failure)
finished. total time: 0.140s
so then I try:
Code:
D:\motopocalypse\motopocalypse>fastboot erase userdata
erasing 'userdata'...
Invalid partition name userdata
FAILED (remote failure)
finished. total time: 0.141s
and so on and so forth. No attempts to erase data nor write it in any manner are successful. RSD Lite basically is useless as well (pic attached below). Since I can't write any data to the device at all then as I've said, it's dead in the water unless a miracle comes along. Was looking at eBay in the hopes of finding a busted/broken AHD (damaged glass, etc) and swapping the mobo from that one back into my housing but they're a bit expensive for busted ones at the moment, guess I'll just keep hoping for that miracle.
I've never used a JTAG or factory cable on any devices I've ever owned but I have to wonder if such a contraption might get this back to a working state. Suppose I'll need to do some research into things - I tried to contact Motorola about it but of course since the AHD is so old now and I'm not the original owner, even though I registered the device in my name they won't honor the warranty without a proof of purchase (meaning the retail one years ago when it was new).
Out of over 100 smartphones and other devices I've owned over the decades this is the first time one's actually up and died on me and go figure: it died when doing an OTA update on a clean stock ROM installation.
How ironic...
Have you tried this http://forum.xda-developers.com/showthread.php?t=2259661
Sent from my LG-D850 using XDA Free mobile app
bmatney said:
Have you tried this http://forum.xda-developers.com/showthread.php?t=2259661
Sent from my LG-D850 using XDA Free mobile app
Click to expand...
Click to collapse
Yep, it's all the same basic process whether it's done scripted or manually, same result: as stated, nothing will flash to the AHD and kicks back the same error each time (partition errors). I have no idea what that damned OTA did but it totally wrecked the whole thing...
Even tried doing this under Linux - the issue isn't with fastboot or the builds, it's with the AHD itself because it's not writing anything I'm trying to flash to the device and I'm confident it's because the partition structure is pooched for whatever reason.
I'm still wondering about using a factory cable (will have to buy one off eBay I suppose) will make any difference at all, I just have no experience using them and if the phone isn't flashing/writing data to the device because the partitions are pooched, I can't imagine using a different albeit specific cable will make that much of a difference.
Bleh... I hate it when crap goes wrong, I really do.
Related
UPDATE
It is clear from many users now that the 2.3.4 / 4.5.91 OTA burns a fuse, specifically in ReservedOdm[1], which switched from:
Code:
old: 0000 0000 0000 0001 0000 0000 0000 00[B]0[/B]1
new: 0000 0000 0000 0001 0000 0000 0000 00[B]1[/B]1
So, if you see something in /sys/firmware/fuse/ReservedOdm like:
Code:
10000000000010001000[B][U]3[/U][/B]00004000
You *should not* SBF to anything except PUDDING or an SBF with PUDDING, or AT&T 4.5.91.
Any official motorola .sbf, EXCEPT 4.5.91, will leave you in hard-brick nvflash land...
(I will make a new post and call for more data for Chinese 0x1000 errors)
Here is an AT&T specific putative explination for their 0x1000 issues:
Our phones have a fuse, a set of one-time-programmable bits, called 'ReservedOdm' (reserved for the original design manufacturer, Motorola.) Using a fuse in this set, the unreleased 2.3.3 bootloader implemented 'fastboot oem unlock' which burns a bit in ReservedOdm[0] and sets these 32 bits (represented as 8 hex values) to 0x00004000. There are 8 ReservedOdm[] 32bit values, or 8x32 (256) fuses. Once one is burned (set to 1) it cannot be un-burned. Hence, a 'fuse'.
You can view the state of your ReservedOdm by looking at /sys/firmware/fuse/ReservedOdm, if you are root. Mine looks like this:
10000000000010001000100004000
(before unlock:
10000000000010001000100000000)
Broken down (Odm as short for ReservedOdm):
Code:
Odm[3] | Odm[2] | Odm[1] | Odm[0]
00010000 | 00000001 | 00010001 | 00004000
We don't really understand Odm[3], but it likely gets burned by flashing an .sbf or some other process, not everyone has a 1 there. You don't see Odm[7] through [4] because leading zeros are dropped from the printf output. Also, some people (pre-first-sbf?) seem to have 00000001 not 00010001 in Odm[1].
Why discuss unlocking? Because although downgrade bricking is not directly related to unlocking, in the end it is caused by another fuse, in ReservedOdm[1].
Talented dev nothize has disassembled bootloaders and determined that AT&T 1.8.3 and earlier, and most chinese bootloaders, expect that only the last bit of Odm[1] is 1. By burning the next-to-last bit, Moto broke ability to downgrade.
Basically, SVF:105:1:2 means, at lower word (16bits) of Odm[1], (called "105" dunno why) we expect the first '1' to be in position '1' but we found it at position '2', barf. Ie, for AT&T bricking case, we wanted Odm[1] should have been 0x????0001 (binary 0001 for last 4 bits) but we got 0x????0003 (last 4 bits, binary 0011) instead. By barf I mean drop to nvflash mode which only motorola service can use, since only they have our 'secure boot key' which nvflash requires. Thus, the hard brick when certain (older and/or chinese) bootloaders find this unexpected fuse burned.
Now although 4.5.91 OTA & sbf burn a fuse, you only brick if you run a bootloader that expects it not to be burned (ie, stock 1.8.3 or below.) Similarly, you can burn the Odm[0] fuse to get 0x00004000, but it won't do you any good unless your bootloader cares. So far there is one bootloader which cares, from 2.3.3, 4.5.47 (unreleased build) and lets you 'oem unlock', burning that Odm[0] fuse, and if it's burned, lets you fastboot, skips signature checks, etc.
If you run any other bootloader besides 'Pudding', it doesn't matter if your fuse is burned, you're 'effectively' locked (other BLs don't care to give you permissions.) But since fuse burning is irreversible, once you go back to the unlockable bootloader, it will notice you burned that fuse, and print 'Unlocked' in the corner. So although your fuse is burned, you don't get the benefits of it, unless you flash 'Pudding' (4.5.47) or an sbf with 'Pudding' in it.
Pudding/4.5.47-BL is also a special for another reason. Although it also does not like Odm[1] to be 0x00010003 (like 1.8.3/pre) and displays error 0x1000, it lets you escape. It gives you a really nice menu of options so you can flash something higher (only 4.5.91 right now) if you want to stay locked, or it lets you enter fastboot and 'oem unlock.' Then, in the future, even if it notices this 'bad' fuse is burned in Odm[1], because you have the Unlocked fuse burned in Odm[0] it gives you a pass, and boots anyway. So flashing Pudding or something+Pudding after 4.5.91 might give you a little heart attack, but in the end it should be harmless.
Preserved for posterity below (if you have a Chinese/Korean/Hong Kong Atrix please continue to post your ReservedOdm plus model, location, carrier, current build/sbf please, until I start a new thread.)
ATTENTION
The purpose of this thread is to assist currently 'hard' bricked users seeing 0x1000 on boot, and to understand why this happens. People who have un-bricked please skip to the end of the post. Talented dev nothize has disassembled some bootloaders and thinks perhaps this is a fuse check failure. Also, he has been able to glean some info from the chinese-language threads about this same error some weeks ago. It has been very hard to try to make sense of this issue after being away by combing through hundreds of posts. Let's keep this thread uncluttered.
HOW TO HELP
Everyone who has seen 0x1000:
Post a short description of how you got there, what you see (ie, do you boot loop?) For example, ATT users: Did you OTA from 1.8.3 to 4.5.40 or 4.5.91? Had you flashed 'Pudding' before OTA? Were you locked or unlocked? Did you see any messages about 'BP' during any RSD flash or OTA upgrades? If you recovered, exactly how (full Pudding+1.8.3 or just Pudding. If you were locked, did you have to unlock? etc.) INCLUDE SVF STRING (if any.) Be concise and specific.
If you managed to un-brick:
0. (Root your phone, see: here)
1. As root, cd to /sys/firmware/fuse
2. Run: "for i in * ; do echo $i `cat $i`; done"
3. Post output here, especially of "ReservedOdm" fuse
(Include: carrier, previous .sbfs & bootloaders used, if unlocked, current BL)
(The following is depreciated, probably not worth doing... 0x1000 on 1.8.3 bootloader [or older] is different to the Hong Kong/China 0x1000, and also different for users lucky enough to flash 2.3.3/Pudding after OTA)
If you are currently bricked:
[Note, this is not a fix, but we'd like to know if you can 'see' your device on your PC's USB. If you have, or can make, a factory cable this test will be more conclusive, especially if you see any sort of 'Nvflash' message]
0. (Be sure your battery is charged!!)
1. Unplug phone, remove battery, leave disconnected for at least 10s
2. Hold down the volume-up before and during battery insertion
3. Continue to hold down volume-up (never release it!) and connect to PC
(If you've held volume-up more that 30s after inserting battery, you can release)
4. Try to see your device in RSD
5. If Step #4 fails, try to see your device in linux 'lsusb' (like: "watch -n .1 lsusb" before connecting phone to PC)
6. Post your results in this thread!
(PM me if you use windows freeware lsusb or usbview. I don't run windows and can't test, but would gladly post instructions)
Good thread for our bricked friends. Nice one!
Ronaldo_9 said:
Good thread for our bricked friends. Nice one!
Click to expand...
Click to collapse
This is exactly the kind of spam I do not want on this thread. If this starts to happen I will close this thread.
Please respect the big red underlined request in the first post and do not post in this thread unless you have experienced 0x1000 yourself, and have something useful to contribute.
Thanks in advance for valuing our time.
Six step plan is a no go for me. I tried it quite a few times with two different batteries.
One battery is low-ish on charge and it reads the following under the traditional error:
Code:
Entering NVFlash recovery mode
Battery is too low to flash
The other battery is full. It reads the error for about three seconds and then quickly flashes the "NVFlash recovery mode" line before it turns blank. The screen just goes dark. Still, the device must be on, because it won't let me reboot without battery pull.
@kenneth that's exactly what happened with me.
I have already gotten a new atrix and dumped the busted one back to AT&T (on the pretense of a battery dying while doing an OTA update.) So unfortunately I cannot help figure this out.
But for my two cents, im still a firm believer that using a factory cable to connect the phone w/o a battery to a PC holds the solution we seek.
I attempted to make my own, but at 7am after going all day at work (im in the US Marine Corps Infantry ) I was falling asleep while soldering. Im going to work on it again this weekend though.
Sent from my MB860 using XDA App
I had the 0x1000 error yesterday morning by flashing pudding. I don't think was a hard brick due too the fact that I was able to recover.
Sent from my MB860 using XDA Premium App
Same issue as jakew02, how ever I still have my bricked atrix. I will get a fully charged battery and try to get some results but I have the same symptoms as Kenneth as well as in phone starts for about 3 seconds and immediatley needs a battery pull. I'm off work in a few hours and will post results then.
Sent from my MB860 using XDA App
Sthony said:
I had the 0x1000 error yesterday morning by flashing pudding. I don't think was a hard brick due too the fact that I was able to recover.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Please guys... the more descriptive the better.
Sthony, you OTAd to 4.5.91 from 1.8.3 by putting the .zip in /sdcard and fastboot menu into Recovery? Then, you flashed Pudding and soft-bricked. How did you recover? Were you unlocked before OTA? Or you only unlocked after flashing pudding?
Can those of you who recovered please cat /sys/firmware/fuse/ReservedOdm ? (as root)
We would like to determine what prevents you all from downgrading (and maybe, possibly, get the still-bricked out of nvflash mode, but this will probably require cable + SBK). So it will help knowing exactly what versions you went FROM and TO (with OTA inbetween) and the type of 0x1000 you got (bootloop with RSD option using battery during volume-up method, VS. nvflash, VS. fastboot menu) including the SVF (usually 105:1:2) message if possible.
kennethpenn said:
Six step plan is a no go for me. I tried it quite a few times with two different batteries.
One battery is low-ish on charge and it reads the following under the traditional error:
Code:
Entering NVFlash recovery mode
Battery is too low to flash
The other battery is full. It reads the error for about three seconds and then quickly flashes the "NVFlash recovery mode" line before it turns blank. The screen just goes dark. Still, the device must be on, because it won't let me reboot without battery pull.
Click to expand...
Click to collapse
Kenneth, same here.
the 6-step thing is a no go for me. It flashes the NV thing very quickly, then goes dark. At least I know what I did wrong, and quite stupidly so
- On 2.3.4 stock
- tried to push a de-odexed services.jar , deleting the services.odex (stupid in hindsight)
- pushed kenneth's boot.img and system.img (without reading that the system needs to be UNLOCKED)
- since the only thing left was RSD, tried to flash 1.2.6, which failed. BOOM. hard brick.
I only hope my stupidity helps people not make the same mistakes.
Will try to give it to a moto service center tomorrow, see if they can fix it.
*EDIT* doing the steps in the first posts without battery but plugged into wall outlet leaves the phone in "starting nvflash... battery too low to flash." If you push in the battery, and then pull out the cable, the screen stays on. Not sure if that helps anything, since I don't know how to do nvflash, and don't have the right tools to begin with.
Please fill out and use the following template when posting to this thread:
1. Before the 2.3.4 (4.5.91) OTA upgrade, did you flash a fresh install of 1.8.3 .sbf from RSD?
2. If the answer to #1 was no, what mods (if any) did you have installed at the time of your 2.3.4 (4.5.91) OTA flash (cwm, pudding, root, et cetera...), also what version of software were you on if not 1.8.3?
3. After flashing the 2.3.4 (4.5.91) OTA by putting the update.zip in the root of your /sdcard-ext/ and booting into the stock recovery, did you install any mods (cwm, pudding, root, et cetera...)?
NOTE: If you did not flash the 2.3.4 (4.5.91) OTA by putting the update.zip in the root of your /sdcard-ext/ and booting into a stock recovery, please detail what method you used to get to the 2.3.4 (4.5.91) OTA. This thread is only for users who flashed with this method.
4. Did you use RSD to flash anything else while on the 2.3.4 (4.5.91) OTA, such as pudding?
5. Did you use fastboot to flash anything else while on the 2.3.4 (4.5.91) OTA, such as cwm or preinstall root?
6. Did you then try to flash back to the stock 1.8.3 .sbf via RSD? If so, what version of RSD Lite did you use?
7. If the answer to #6 was no, what version of .sbf did you flash via RSD, also what version of RSD Lite did you use?
8. Did you encounter the 0x1000 error after trying to downgrade to a lower version .sbf?
9. Have you been able to recover from the 0x1000 error and resume normal functionality? If so, what software version are you currently on?
10. Please detail below exactly what had occurred during and after the downgrade to a lower version .sbf via from the 2.3.4 (4.5.91) OTA. If you were able to recover, please detail the steps that led up to your recovery. Also what type of 0x1000 you got (bootloop with RSD option using battery during volume-up method, VS. nvflash, VS. fastboot menu) including the SVF (usually 105:1:2) message if possible.
Also include everything required from the first post of this thread. This is very important.
If you can also provide filenames for the files you've flashed, that would be optimal.
=>
Well, I had this issue some days ago following the Pudding stickied topic.
I had 4.1.8.3 with old Tenfar's CWM so following the steps in that topic flashed 4.1.8.3 again with RSD Lite. It was a service SBF.
Then I booted in Android recovery mode and flashed the OTA. Everything went fine, I had 4.5.9.1 with all my data and apps.
Then I flashed Pudding.
Instantly after RSD rebooted my phone, I had this 0x1000 error. I didn't know what to do, I followed the guide step by step and I was confused. So I tought "Maybe I need to unlock my bootloader". So I booted the phone in fastboot mode and unlocked my bootloader through fastboot.
Then I did a fastboot reboot and voila, the phone booted again in 4.5.9.1.
I notice I have a "Unlocked" text in the Motorola boot screen.
Well, I hope this info helps someone.
Let me know how it went.
Failed to boot 0x1000
I have the same issue that you guys have...
I did the update to Gingerbread 2.3.4 and then I tried to roll back to froyo so I used RDSlite 5.3.1 and this .sbf: OLYFR_U4_1.2.6_SIGNED_OLPSATTSPE_P012_HWolympus_1g_1FF.sbf and the phone got hard bricked...
I left it with the battery inside yesterday and today the phone drain the battery completely... I took it off, charge it for 2 or 3 minutes and put it back, connect it to my pc and it displays:
SVF: 105: 1:2
Failed to boot 0x1000
Entering nvflash recovery mode
Battery is to low to flash
But if i take the battery from my other atrix, fully charged it just turn on, display the error and for a second "Entering in nvflash recovery mode" and then Black Screen.
Just going to point this out in a new post for everyone to see on unbricking transformer: http://forum.xda-developers.com/showthread.php?t=1123429
I am wondering if sth like this could work (with the right .cfg and .sbf). I am going to take a look at the nvflash package in any case.
bl0wf1sh said:
Just going to point this out in a new post for everyone to see on unbricking transformer: http://forum.xda-developers.com/showthread.php?t=1123429
I am wondering if sth like this could work (with the right .cfg and .sbf). I am going to take a look at the nvflash package in any case.
Click to expand...
Click to collapse
You would need your SBK which is why the NVFlash issue is a 'hard' brick in the first place.
First i would like to apologize if this post is not of much use to you guys as I have not hard bricked my device. However I have flashed the 4.5.91 OTA and I noticed something intersting.
1 I unlocked my bl the night pudding was released.
2 I flashed a fresh 1.83 sbf
4 OTAd form android recovery to 4.5.91
5 on the very first reboot after OTA I entered into RSD protocol and once I connected to RSD lite 5.3.1 I noticed RSD identified my device as SE-Olympus insted of the normal NF-Olympus.
6. I flashed zomgunlock-lite.sbf. After it completed SE-Olympus changed back to NF-Olympus.
I may be wrong but i dont ever recall RSD seeing my device as SE-Olympus.
Anyways I hope this may useful and good luck!
kennethpenn said:
Six step plan is a no go for me. I tried it quite a few times with two different batteries.
One battery is low-ish on charge and it reads the following under the traditional error:
Code:
Entering NVFlash recovery mode
Battery is too low to flash
The other battery is full. It reads the error for about three seconds and then quickly flashes the "NVFlash recovery mode" line before it turns blank. The screen just goes dark. Still, the device must be on, because it won't let me reboot without battery pull.
Click to expand...
Click to collapse
On my bricked Atrix, it just shows the error, and stays there until a battery pull (no other text shows up)
When you see the LOW battery warning, it's a false warning. On Olympus, NvFlash can only be accessed with external power from the factory cable (without ANY battery inserted). That's why your devices are "flashing" and powering themselves down. It's a "protection" implemented by Moto (as factory cable should be only built by Moto for repairing bricked devices).
Anyway, why are you hardbricking your devices flashing an old bootloader?
...At least, do you know why your device isn't relockable?
The new bootloader writes a bit into a fuse (in the ODM Reserved set) that isn't already blown. When it reads it back, if it's set to 1, it shows the "Unlocked" message and disables security checks.
Still, why can't I relock the device?
As you might know, when a fuse is blown, its programming power ramp is literally blown, so, you can't reprogram a fuse that has been burned.
And still, so, after so many hours of boring reading of your post, can you tell me why the **** my device is bricking with an old bootloader?
...The bootloader reads the entire ODM Reserved fuse set. When it reads it, it won't read fuse 1,2,3,4.... but the ENTIRE set.
If another fuse is blown, the old bootloader can't recognize why the damn there's an 1. It doesn't know what it is.... so boot fails, MotoBoot stops its execution and passes it to the Emergency NV3p Server (Emergency NvFlash Mode, from nVidia MicroBoot).
I think those infos should clear some doubts in your mind.
Cheers!
very nice of you I offered to possibly fix some bricks but with out knowing actual facts as to what is going on with their devices it would be hard . have you talked to any of them ? you know they dont talk to me , do they actually have access granted to NV3p server or nvflash or are they still locked out?
as per the first post, the OTA DOES CHANGE YOUR BP, THIS IS NOT A ?, as i was graceful enough to enter irc under another handle and post earlier in the week.
on a side note the irony of this entire situation is that i was booted from #moto-atrix after arguing the subject of blindly flashing back to older versions with a sbf, true at the time i was concerned with 1.84 - 1.29 , but now just a short time later ...
Regardless a fix maybe possible but need to know exactly what access you have once powering on device
*edit* for the sake of giving you what you asked here is my output , I am unlocked, rooted, I did use OTA I never bricked , I am now running my own stuff after flashing a CWM and building
Code:
DeviceKey FFFFFFFF
JtagDisable 0
KeyProgrammed 1
OdmProduction 1
ReservedOdm 10000000000010001000300004000
SecBootDeviceConfig 0
SecBootDeviceSelect 7
SecBootDeviceSelectRaw 0
SecureBootKey
SkipDevSelStraps 0
SpareBits
SwReserved 0
kfuse_raw ��j�s��Q��'��[email protected]�C��%57�ܠ� ��.����fm���vp��^����D}�G������K�*^V��w�+�����6:��YяmTq���;bH9�٩$M��nT&�7����4.�ŷX{�J������[�;N{�,(Ay���V��K=tTD���!$�{%�f��y;v��~�\�C:L-|��w���)�g#�!mv���+W�T�����(����|�3LNP�HV�J��|q��b�Wfa��/
�.���^df�6�6�e�n��U�Sj��j}�_g��i��c�i�h��0$ bz)�ߋ�Cd|ge-G���oU�GF��w���YLn2E,�rU����5�V��3.�V��NjY�m�v*Bt�����2�[email protected]�?��ؘ��#w��&6�+rdb;TK_r��� �,�F_���vQ�NJ
�2��}(�8mg�ȯ#nv������M$�Oǹ=E��I�v��E�9tP"�[`�'�a#X�E��S+�4 �u/�ö4�B|y�1bd��*��N��/"U��p���� F���%4>X�0H�xx�����
sku F
So here is my basic info now that I am home.
I was on stock att 1.83, flashed 2.3.4 via zip through sd card. Tried to install pudding, phone went into bootloop then flashed the red led. upon reboot showed error and message of "no os available cannot boot."
After panicking a bit, I loaded the 1.26 sbf, got to the moto boot screen and the phone shut off, no led, no message, nothing. I pulled the battery and restarted, then all I got was the 0x1000 message for 3 seconds, then the NVflash message and immediately a blank screen.
Now that I am home I have tried the steps provided and haven't been able to see the phone through rsd lite, and it still has the same symptoms. If you need any other info, or if i have forgot anything please let me know I will help where I can since I now have a paperweight and a brand new functioning atrix, thank god my mother-in-law was due for an upgrade.
They're still locked out. No SBK no party.
"No OS to boot" implies that you need to repartition/reflash without absolutely touching the MotoBoot. So, someone make a recovery SBF that won't flash the bootloader or you'll see plenty of bricked devices.
They can't recover with NvFlash.
Hey ,
seems like you guys are my last chance. I will try to explain my situation:
So today I was just messaging when suddenly some process.google.media (cant recall exactly) error was spamming my phone. I restarted the phone and then the problems started happening. The moto X was stuck in the boot screen.
I read that i should install TWRP and factory reset. So after doing that I was pretty much stuck in recovery.
Whenever i turned the phone on, It was immediately booting the TWRP.
So I thought fine, I will probably have to install a ROM, so it can actually boot something.
I went for the xt1052 Lollipop 5.1 untouched EU version of the forum. Still It somehow didnt boot.
Next I came across the following youtube video: youtube /watch? v=ne46LQ3n7nA
(cant post url)
Followed all the instructions in the video and it actually got my phone to work.
I thought that now everything would be just like when I bought my phone.
So I installed the official lollipop update which popped up on my screen.
And now Im stuck again...
Im sitting in Fastboot Mode and get the following error:
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
CID Read Failure
Invalid CID status 0x69
CustomerID error. Contact Dealer: 0xdead
Fastboot Reason: Invalid CID
Dont know how many threads I read by now on here to find a solution but I cant find any..
I installed RSDLite, but Im not sure which version to use to flash now.
Tried two zip folders, but apparently the xml file was missing.
Im kinda scared to use the wrong zip anyways and screw my phone completely if it isnt already.
Id really appreciate any help since im currently clueless.
Thanks boys!
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
This is likely your problem and the result of flashing a lower version onto your Moto x. I would start looking how/if you can recover from a downgrade.
I might add some additional error description to make ppl find this thread in the future :
Stuck in bootloader - Fastboot - cant enter recovery - when choosing any options from fastboot: Load kernel (boot) failed
-----------------------------------------------------------------------------------------------------------------------------------------
Alright seems like i got it working again.
Since this forum helped me so much I want to contribute something to it by giving u guys my solution.
So I stumbled across alot of threads with @KidJoe replying. He really knows his stuff, when it comes to the MotoX.
I dont know how to quote off of other threads, but this quote of KidJoe got me on the right track:
" GPT.BIN is the partition table. Its important. When GPT.BIN and MOTOBOOT.IMG are mismatched from the rom on your phone you could brick when taking an upgrade.
In most cases, the GPT.BIN has matched from model to model when on the same rom (i.e. GPT.BIN from XT1060 4.4.4 rom has matched GPT.BIN of XT1053 4.4.4 rom).
However, try Option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html and see what happens. "
Alright so, here is what I grasped:
before things went bad for my phone, I was already on lollipop. Following the youtube video I downgraded it from 5.1 to 4.4.4.
While downgrading I already noticed that some commands failed, which was the gpt.bin stuff.
So after my phone was working on 4.4.4 and I used the Motorola Upgrade to 5.1 , there must have been a problem with the gpt.bin and motoboot.img , just like KidJoe said. Hence why I got stuck in Fastboot.
As I said in the first post, I had to find the right image for my phone.
In the Fastboot mode I saw that I was on 30.BE, and from what I understand that means im on lollipop and since I cant downgrade, I had to find the right lollipop version for my device.
Im also german, so I found this version:
XT1052_GHOST_RETDE_5.1_LPA23.12-15.5_cid7_CFC.xml.zip
KEEP IN MIND, my problem was having the wrong version all along, so you have to find the right version for your smartphone, dont make the same mistake I did!
I found my file on filefactory through this link here:
http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347
(EDIT: I recommend using something like jdownloader to manage the download)
After I had the right version, I used rsdlite, chose my new file and my phone was working again.
However, I noticed that even tho my phone was working, the rsdlite actually failed somewhere between the lines. (I think it was step 7 or 9)
I was really happy to see my device boot up again, but wasnt happy with those errors and followed this link:
http://mark.cdmaforums.com/MotoX-ReturnToStock.html
Option 5.
Now finally all the commands went OKAY in my cmd window.
After the motorola took some time to boot up again, I performed a factory reset via settings.
Just to make sure its fine and it seems like it is.
To end this thread off, I hope KidJoe will read this post.
Big thanks to you, your the man!
And even tho on some posts you came along a bit harsh, which really got me worried my phone would be completely dead, I wish you a nice christmas time dude!
Hi everyone,
I tried to install the CM 13 in my moto X 2014, but I forgot to install Gapps before rebooting my phone. So I had to flash android 6.0 and try all over again. I dont´t know if my mistake in the procedure has something to do with the problems below.
I realized that my phone is not vibrating anymore and the battery drain has been drasticaly increased, like 10% per hour while in idle. When I use my phone (whatsapp, chrome etc) the battery drain seens to be like in idle (no apps running on background).
A full charge takes 4 hours with normal charger or 8 hours if connected to my computer.
I Tried android versions 4.4.4, 5.0, 5.1, 6.0, NX 10.1 and CM13. I don´t know what to do. Motorola assistance said the motherboard is the source of my problems just because i unlocked my bootloader.
Rodrigo_Codina said:
Hi everyone,
I tried to install the CM 13 in my moto X 2014, but I forgot to install Gapps before rebooting my phone. So I had to flash android 6.0 and try all over again. I dont´t know if my mistake in the procedure has something to do with the problems below.
I realized that my phone is not vibrating anymore and the battery drain has been drasticaly increased, like 10% per hour while in idle. When I use my phone (whatsapp, chrome etc) the battery drain seens to be like in idle (no apps running on background).
A full charge takes 4 hours with normal charger or 8 hours if connected to my computer.
I Tried android versions 4.4.4, 5.0, 5.1, 6.0, NX 10.1 and CM13. I don´t know what to do. Motorola assistance said the motherboard is the source of my problems just because i unlocked my bootloader.
Click to expand...
Click to collapse
What is currently installed on each of the phones partitions?
JnNn98 said:
What is currently installed on each of the phones partitions?
Click to expand...
Click to collapse
You mean the S.O. version?
I´ve flashed these firmwares via fastboot/RSD Lite 6.2.4.
mega.nz/#F!kd9WULBb!m_X_fQGJ6UnEOMJXzcv-Yw
Rodrigo_Codina said:
You mean the S.O. version?
I´ve flashed these firmwares via fastboot/RSD Lite 6.2.4.
mega.nz/#F!kd9WULBb!m_X_fQGJ6UnEOMJXzcv-Yw
Click to expand...
Click to collapse
I feel like it's possible that you downgraded the bootloader in the process, and that could be the only problem. In that case flash this to get stock, as it'll be the latest firmware.
http://www.filefactory.com/file/13ee8myr4sjh/VICTARA_RETBR_XT1097_6.0_MPE24.49-18_cid12_CFC.xml.zip
Use the instructions from this thread.
http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
Also check the cable you're using to charge the phone, with regards to the slow charging.
If there's still things wrong afterwards it is probably a hardware problem. Good luck.
JnNn98 said:
I feel like it's possible that you downgraded the bootloader in the process, and that could be the only problem. In that case flash this to get stock, as it'll be the latest firmware.
http://www.filefactory.com/file/13ee8myr4sjh/VICTARA_RETBR_XT1097_6.0_MPE24.49-18_cid12_CFC.xml.zip
Use the instructions from this thread.
http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
Also check the cable you're using to charge the phone, with regards to the slow charging.
If there's still things wrong afterwards it is probably a hardware problem. Good luck.
Click to expand...
Click to collapse
Sorry I did not reply you earlier, canaval holidays... back to real life today.
I tried what you suggested but without success.
When I try to execute "fastboot flash partition gpt.bin" it fails (I´m not at home right now and I don´t remember exactly the message I got), but all other commands runs like expected.
I saw this thread " forum.xda-developers.com/moto-x-2014/help/managed-to-screw-phone-bootloader-to-t3309241?nocache=1 ". It has a command that in the other you suggested has not.
"fastboot getvar max-sparse-size"
What is it for?
Rodrigo_Codina said:
Sorry I did not reply you earlier, canaval holidays... back to real life today.
I tried what you suggested but without success.
When I try to execute "fastboot flash partition gpt.bin" it fails (I´m not at home right now and I don´t remember exactly the message I got), but all other commands runs like expected.
I saw this thread " forum.xda-developers.com/moto-x-2014/help/managed-to-screw-phone-bootloader-to-t3309241?nocache=1 ". It has a command that in the other you suggested has not.
"fastboot getvar max-sparse-size"
What is it for?
Click to expand...
Click to collapse
The error for the flash partition may be a result of using fastboot and not motorola's own fastboot. I've attached a motorola fastboot in a zip, so you can try again using that fastboot file. The extra commands don't help with anything really because they do not affect the flashing of partitions.
The fastboot getvar command is literally "get variable", so in that case it would just return the maximum file size that can be flashed I believe, and in case you were wondering:
fastboot oem fb_mode_set - Makes the phone automatically reboot into bootloader mode.
fastboot oem fb_mode_clear - Just resets the above commands setting back to normal booting.
The message I mentioned when I execute the command "fastboot flash partition gpt.bin"
sending 'partition' <32KB>...
OKAY [ 0.030s]
writing 'partition'...
<bootloader> Preflash validation failed
FAILED <remote failure>
finished. total time: 0.130s
Nevermind... I was trying to flash an old gpt.bin.
I guess that's the end, I give up. I don't know what to do, nothing works.
I'm thinking of buying an used device with broken screen for 1/3 of the price of a new one (350 reais, almost 100 dollars), disassemble everything and assemble only the motherboard in my device.
I really appreciate your help but I guess I need the Blanckflash and I searched and no one has it because motorola did not released for us.
--> From Motorola, but do at your own risk, as always! <---
Lenovo Motorola Smart Assistant - "lmsa"
I've played with, and done some more research on lmsa.
I am wondering if this would help some folks here.
Please report back success or failure and your particular symptom so others will know.
NOTE: my phone is bootloader unlocked XT1900-1 One fi which OTA'ed itself up from 8.1 to 9 Oct 1 '19 security.
If you are able to back anything up, do so before you do this - if successful, it will flash your phone.
go here
https://www.motorola.com/us/lenovo-motorola-smart-assistant
and download it.
Watch the video for software issues(lower left of that page).
Install it.
Start it up.
You want flash/ rescue.
follow the instructions and put your phone into fastboot mode and connect to PC via USB.
If it offers you something(takes a minute), click the little download arrow and when it's downloaded, click rescue.
This is what it looks like for me before I would click the download arrow.
I believe this tool is for people who have a locked bootloader, never unlocked? LMSA won't recognize my device. RSD lite won't either.
Persistent memory has some value that is not overwritten by Wipe All twrp? Of course I will never relock.... just a heads up to others.
I am one of the few.... 1900-1 Fi working fine on Aug Pie factory and wanted to try ionOS. Flashed fine and working good. Now 3 carriers in my area only US Cellular has service. T-Mob--, Sprin- coverage area 10 - 0% Found as I have before No ROM other than stock for ME can get Data services to work on all three carriers in my area. So for data services trying to reflash back to stock. NO factory image successfully flashed will have modems working. For me. Tried many forms of flash modems only via fastboot, nope.
Different flavors of ADB don't help. Now I haven't tried "Hardware tools loader" style because if wrong will brick it. Unless some one has? Various forms of flashing modems, flash all scripts, ADB versions, Hardware only flash from two ROMs (which is why I am here I think) the Wipe All needed for those two roms some how did it? No blame, just for some reason can't flash back to stock. Others have but....I can't. So hoping a forward update by Motorola Factory Image will do a complete modem working Flash.
kkjb said:
I believe this tool is for people who have a locked bootloader, never unlocked? LMSA won't recognize my device. RSD lite won't either....
Click to expand...
Click to collapse
My phone IS bootloader unlocked - I bought it used(ebay) and it came to me that way with a fresh 8.1 It gives the usual bootloader unlocked error message on boot. It has OTA updated itself to 9 Oct 1 '19 security. I have not tried to modify it because that would prevent me from getting future OTAs.
RSDlite latest (6.2.4) does not recognize my phone. That is RSDlite's fault. I don't think it is yet capable of an A/B phone, let alone a full Treble (ours, on 9, are not full Treble, only partial but DO have A/B sets of partitions).
From the attached pic you can see it was ready to flash my phone with the latest stock ROM appropriate for my device which is a 1900-1 One fi, even though it was unlocked.
I am guessing that Motorola invented lmsa to stem the flow of trashed phones to Moto factory repair. It wouldn't surprise me if it would auto blankflash if necessary.
Try it - it only takes a minute or 2 to test! The worst it can say is "no"!
Understand, tried all the options and LMSA needs I think a stock recovery, boot, fastboot flash mode. The various options show "phone not recognized" no mode available with twrp installed to goto Factory Flash as LMSA appears to wait for in Bootloader Mode. So the drop down box screen will not appear since not recognized.
This post was just a update as you had asked for others to give their results. So going to do hand flash of factory images again, see if try many times... and some how one works
kkjb said:
Understand, tried all the options and LMSA needs I think a stock recovery, boot, fastboot flash mode. The various options show "phone not recognized" no mode available with twrp installed to goto Factory Flash as LMSA appears to wait for in Bootloader Mode. So the drop down box screen will not appear since not recognized.
This post was just a update as you had asked for others to give their results. So going to do hand flash of factory images again, see if try many times... and some how one works
Click to expand...
Click to collapse
Thanks.
Bummer this didn't work for you.
Yeah phone definitely needs to be in fastboot mode.
Hopefully it will help others.
Yeah, back when RSDlite worked you could "sledge hammer" just about anything if it would boot to fastboot! Hopefully they will upgrade it...
No Thank You, you gave me some ideas about the a/b devices thoughts. We have the odd ball not 9.0 at release device so the a/b script is different than some devices. So with the newest ROMs using fastboot "flash all zip scripts" for a/b boot slots I think the problem is factory images want something else for the modems. Oddly the factory images flash fine with no errors just that no modems...imei, wifi, blutooth. 8.0,8.1,9.0 all. Its a weird problem.
kkjb said:
No Thank You, you gave me some ideas about the a/b devices thoughts. We have the odd ball not 9.0 at release device so the a/b script is different than some devices. So with the newest ROMs using fastboot "flash all zip scripts" for a/b boot slots I think the problem is factory images want something else for the modems. Oddly the factory images flash fine with no errors just that no modems...imei, wifi, blutooth. 8.0,8.1,9.0 all. Its a weird problem.
Click to expand...
Click to collapse
Yeah I was thinking a-/b prob
If you ran the "flash all fi bat" to install ionOS it would have worked well since, with Aug 9, you were in a 2 file system phone. so i am guessing
a) you would only have success flashing a 9 stock (fi or not)
b) you would probably have to do a preliminary flash with just the stock 9 bootloader etc (the stuff before the ping. as well as maybe the 2 modem erases later in the command stack - some playing needed there...) tons of guesswork and luck needed here!
c) I found it humorous that ionOS script made b active but I hope the dev knew what he/she were doing.
edit d) so what partitions set is active after you flash your tests? ie you flash something, but what are you then booting to - unless you set something active... I don't believe there is a default - just last successful - though I assume if one fails it will try the other. Perhaps endlessly.
But, yeah, I can see why that flash went well. But of course you are then stuck with the modems they flashed and how that particular opsys planed to use them. US cellular is apparently known to be iffy on the X4 since I saw that caveat on a number of ebay x4 sales - "not guaranteed for...". And Sprint, of course is cdma but is supposedly accessible as LTE by fi??? I have zero knowledge there!!!
WARNING WHEN DEALING WITH ME - I TEND TO MAKE A POST AND THEN KEEP EDITING IT ENDLESSLY>>> SORRY!
Hello all fellow pixelers
After upgrading to 11 i am faxing a ton of issues with my pixel 4 xl such as "clean the top bar", phone calls going to speakerphone etc.
I have tried multiple factory resets with CMD but one thing i am experienced and have never had before is that whenever i am almost done with the reset option via CMD, the message i get is:
E: (libfs_mgr) failed to mount / metadata; formatting: Invalid argument
E: (libfs_mgr) fs_mgr_do_format: Format /dev/block/by-name/metadata as "ext4|""
E: (libfs_mgr) make2fs returned 255
E: (libfs_mgr)failed to format /metadata: Permission denied
E: Cannot mount /metadata/ota
formating /data...
formatting /metadata...
Wiping Titan M..
E:can"t send spi message: Try again
it repeats for 30 times
Data wipe complete
This being said i sure hope someone can and will help me solve this issue as it is becoming a pain, i thank you all in advance for your efforts
It sounds like you're only trying factory resets at the moment. I don't know how to fix this issue, so the only suggestion I have is to try flashing the factory image (which includes a userdata wipe). Don't do the OTA update method. I've been able to fix all my phone problems by flashing the factory image. If that still doesn't work, then I'm thinking there's something physically wrong with the phone.
Colonel_Kosova said:
Hello all fellow pixelers
After upgrading to 11 i am faxing a ton of issues with my pixel 4 xl such as "clean the top bar", phone calls going to speakerphone etc.
I have tried multiple factory resets with CMD but one thing i am experienced and have never had before is that whenever i am almost done with the reset option via CMD, the message i get is:
E: (libfs_mgr) failed to mount / metadata; formatting: Invalid argument
E: (libfs_mgr) fs_mgr_do_format: Format /dev/block/by-name/metadata as "ext4|""
E: (libfs_mgr) make2fs returned 255
E: (libfs_mgr)failed to format /metadata: Permission denied
E: Cannot mount /metadata/ota
formating /data...
formatting /metadata...
Wiping Titan M..
E:can"t send spi message: Try again
it repeats for 30 times
Data wipe complete
This being said i sure hope someone can and will help me solve this issue as it is becoming a pain, i thank you all in advance for your efforts
Click to expand...
Click to collapse
Have you tried factory resetting the phone? You do not need a computer. If you do factory reset you'll lose all your data.
Hey there Neo
Thnx for the reply and yes I flashed the phone 4 times now with cmd. I get all the bugs and the messages only when I am flashing Android 11.
I reverted once to 10 I had no issues whatsoever, once I upgraded to 11 again both with cmd and ota I get the same issue.
It is really really is a nuisance, was hoping maybe someone can finde a fix?
Just got the darn phone saved up most a year just to get it, what a dissapointment.
Again thank u
Homeboy76 said:
Have you tried factory resetting the phone? You do not need a computer. If you do factory reset you'll lose all your data.
Click to expand...
Click to collapse
I did and it didn't help, just feel mad I hate to have to sell this phone.
Thank you for the reply
Colonel_Kosova said:
I did and it didn't help, just feel mad I hate to have to sell this phone.
Thank you for the reply
Click to expand...
Click to collapse
Do you have the latest Android SDK Platform-tools r34.0.4?
What cmd are you using to flash the phone?
Guide
This Factory Reset: Settings -> System-> Advanced->Reset options-> Erase all data (factory reset)
Homeboy76 said:
Do you have the latest Android SDK Platform-tools r34.0.4?
What cmd are you using to flash the phone?
Guide
This Factory Reset: Settings -> System-> Advanced->Reset options-> Erase all data (factory reset)
Click to expand...
Click to collapse
Yes I do all the latest versions
I use this as a guide
https://youtu.be/cKXa5iL1kfQ
Ok, Hopefully, someone has a solution to this problem.
Your error messages seem like it's somehow incompatible or you're not allowed to flash. So that made me wonder if you're downloading the right factory image for the right phone variant. (I think I only saw one variant for the android 11; can't recall at the moment.)
From your responses, it sounds like you're using the ota image. I've had problems with ota in the past, so my suggestion is to flash the factory image instead, which is different from ota. (I've had the pixel 4 xl for a year and never had issues with flashing.)
I also don't input the cmd commands manually. I run the "flash all.bat" which comes with the factory image and it does everything for me.
Colonel_Kosova said:
Hey there Neo
Thnx for the reply and yes I flashed the phone 4 times now with cmd. I get all the bugs and the messages only when I am flashing Android 11.
I reverted once to 10 I had no issues whatsoever, once I upgraded to 11 again both with cmd and ota I get the same issue.
It is really really is a nuisance, was hoping maybe someone can finde a fix?
Just got the darn phone saved up most a year just to get it, what a dissapointment.
Again thank u
Click to expand...
Click to collapse
Neo thank you very much for the reply and the hints.
Could you please maybe find and link the right file for me!?
I have never used the method with flash all bat file, this being said i would really appreciate if you could do me that favor and maybe guide me on how to.
I really love my 4 xl and hate the fact that I have these issues, I have been using it like this for some days hoping a fix will pop out there before I install everything back again.
I sincerely thank you for the effort and time
QUOTE=neo_lithic3K;83692801]Your error messages seem like it's somehow incompatible or you're not allowed to flash. So that made me wonder if you're downloading the right factory image for the right phone variant. (I think I only saw one variant for the android 11; can't recall at the moment.)
From your responses, it sounds like you're using the ota image. I've had problems with ota in the past, so my suggestion is to flash the factory image instead, which is different from ota. (I've had the pixel 4 xl for a year and never had issues with flashing.)
I also don't input the cmd commands manually. I run the "flash all.bat" which comes with the factory image and it does everything for me.[/QUOTE]
Opps! Wrong thread, stay safe.
Sorry @neo_lithic3K.
Check to make sure your proximity sensor is working. Mine quit working some time around 11 beta 3 and flashing back to 10 stopped the clean the top bar thing but not the speakerphone problem (screen was staying on up against my ear) Google replaced mine under warranty
(1a) First, here are the preliminary steps. There are alot of instructions at the top of Google's page at: https://developers.google.com/android/images
I assume that you've already followed all those instructions .... especially unlocking your bootloader, enabling USB Debugging from Developer Options, and adding fastboot to your PATH environment variable (and then rebooting your PC).
***NOTE: There are better guides on xda that give you more thorough instructions, so you may want to check those out instead of reading mine below.***
(1b) I assume that you have an unlocked Pixel 4 XL and that you purchased google's version of the phone from the Google Store. I don't know all the different ways someone can buy the Pixel 4 XL. For example, I think Verizon used to sell it but I don't know if Verizon variants can be flashed. If you didn't buy the phone from the US Google store or you bought the phone from another country, then there could be restrictions there that I don't know about.
(1c) I also assume you have a Windows PC. I've never flashed from other types of operating systems.
(2) Download the latest android 11 'coral' factory image at: https://dl.google.com/dl/android/aosp/coral-rp1a.201005.004-factory-1eb5827f.zip
That link is for the file posted on google's webpage for this version: 11.0.0 (RP1A.201005.004, Oct 2020) 1eb5827f98ec68b71bfd651d667a7cf557832f2e2850540d322d2a3a6fcc07a8
(3) Connect your computer to your phone using the usb cable. I assume your phone's usb debugging is already enabled & fastboot is already in your PATH environment variables as mentioned in the instructions earlier. You may get a pop up on your phone to trust the PC. I don't remember the exact wording but you should accept or trust it.
(4) After you download the zip file, unzip it somewhere (preserve the folder structure). You'll find the flash-all.bat located at: \coral-rp1a.201005.004-factory-1eb5827f\coral-rp1a.201005.004\flash-all.bat
(5) NOTE that everything on your phone will be wiped so first backup anything you need.
(6) Boot your phone to the bootloader using the hardware buttons (or you can use the cmd command: adb reboot bootloader).
While your phone is still connected to your PC, run flash-all.bat. (I usually just double-click on the bat file from my Windows PC)
(7) The cmd window will run through a series of commands and your phone screen may change or reboot. At one point (on the fastbootd phone screen), it will look like your phone is not doing anything or waiting for something. Don't do anything.... just wait. You'll know the flashing is done when the cmd window says "Press any key to exit..."
(8) When it's all done, your phone should automatically boot into android and you should see the pixel setup screen.
(9) This resets your phone to factory image. You'll need to follow other steps to root your phone.
Colonel_Kosova said:
Neo thank you very much for the reply and the hints.
Could you please maybe find and link the right file for me!?
I have never used the method with flash all bat file, this being said i would really appreciate if you could do me that favor and maybe guide me on how to.
I really love my 4 xl and hate the fact that I have these issues, I have been using it like this for some days hoping a fix will pop out there before I install everything back again.
I sincerely thank you for the effort and time
QUOTE=neo_lithic3K;83692801]Your error messages seem like it's somehow incompatible or you're not allowed to flash. So that made me wonder if you're downloading the right factory image for the right phone variant. (I think I only saw one variant for the android 11; can't recall at the moment.)
From your responses, it sounds like you're using the ota image. I've had problems with ota in the past, so my suggestion is to flash the factory image instead, which is different from ota. (I've had the pixel 4 xl for a year and never had issues with flashing.)
I also don't input the cmd commands manually. I run the "flash all.bat" which comes with the factory image and it does everything for me.
Click to expand...
Click to collapse
[/QUOTE]
Colonel_Kosova said:
Neo thank you very much for the reply and the hints.
Could you please maybe find and link the right file for me!?
I have never used the method with flash all bat file, this being said i would really appreciate if you could do me that favor and maybe guide me on how to.
I really love my 4 xl and hate the fact that I have these issues, I have been using it like this for some days hoping a fix will pop out there before I install everything back again.
I sincerely thank you for the effort and time
Click to expand...
Click to collapse
I know it's been 4-5 days since you last responded, but I'm going to assume you still need help. Flashing a full factory image (Not OTA) using the included flash-all.bat script will return your phone to "out of the box" condition. It's a fool proof way to get the phone completely factory stock, so you can then test your hardware (proximity sensor). Instructions can be found on the image download page. It's possible you have a sensor issue, but flashing the full image is the first step. Best of luck and be sure to come back and let us know how it went.
Hello, everyone.
I have a similar issue, though nothing related to the bootloader. I did flash the entire factory image and the process went smoothly until the very end where it showed:
Erasing 'userdata'
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata'
Erase successful, but not automatically formatting.
File system type raw not supported.
Rebooting
Finished. Total time 253.513s
Press any key to exit...
The phone booted up just fine but I can't stop being worried something might eventually not work properly because of this.
Is there anything else I can try?
Rocio19 said:
Hello, everyone.
I have a similar issue, though nothing related to the bootloader. I did flash the entire factory image and the process went smoothly until the very end where it showed:
Erasing 'userdata'
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata'
Erase successful, but not automatically formatting.
File system type raw not supported.
Rebooting
Finished. Total time 253.513s
Press any key to exit...
The phone booted up just fine but I can't stop being worried something might eventually not work properly because of this.
Is there anything else I can try?
Click to expand...
Click to collapse
No. You used the flash-all without removing the -w. That is the reason your userdata was erased. You're good!
Homeboy76 said:
No. You used the flash-all without removing the -w. That is the reason your userdata was erased. You're good!
Click to expand...
Click to collapse
Thank you very much for your reply. My main concern is the part about not being able to format it. Is that normal?
Rocio19 said:
Thank you very much for your reply. My main concern is the part about not being able to format it. Is that normal?
Click to expand...
Click to collapse
Yes! I don't think you'll have any problems.
Homeboy76 said:
Yes! I don't think you'll have any problems.
Click to expand...
Click to collapse
Phew! That's a relief. I just got the phone yesterday and I was so worried I had blessed it up somehow :crying:
Think I'll stay with stock for a while before I attempt any more flashing lol. Thank you!
I got tired of dealing with face unlock being broken and other issues related to the proximity sensor (screen wouldn't light up during a call if i moved it away from my face).
So I decided to flash back to the latest Android 10 image prior to 11 coming out. Everything is back to working buttery smooth.
If anyone else wants to do this and needs help let me know.
A few tips:
I used https://flash.android.com to perform the factory flash
I used this build 10.0.0 (QQ3A.200805.001, Aug 2020)
After flashing, the phone wants you to upgrade to Android 11, but you can enable developer options and turn off Android System Update notifications.