I just got done using Flatline (http://forum.xda-developers.com/showthread.php?t=2455925) to generate my nvflash blobs (yay!!). The process for Flatline has you install a modded bootloader and custom recovery to generate the nvflash blobs, as I unstand it. With that completed, I was looking to reinstall a standard bootloader and custom recovery.
I managed to get fastboot to cooperate and install CWM Touch 6.0.4.4, but I haven't been able to get fastboot to load the "us_bootloaderblob" file for the 10.6.1.14.4 bootloader. The page for the bootloader (http://forum.xda-developers.com/showpost.php?p=40623406&postcount=1997) has links to 4 files - 2 zip files that can be flashed via recovery, and 2 other files to be installed via fastboot. Unfortunately the file linked to for the US version of the zip files is no longer available, but the fastboot file for the US version is, so I've been trying to reinstall it that way without much success. The tablet connects via fastboot ("fastboot devices" reports a device present), but issuing the command (copied and pasted from the page) seems to attempted to send the file to "staging" but does not respond after that. I've waited a good 10 to 15 minutes without the command finishing.
I could dig more into whether I have the right drivers installed, although all the commands through the flatline process worked just fine, but I think I'd rather try just flashing a zip file through CWM recovery.
So the big question: Where can I find a bootloader zip file to flash? Also, which bootloader is now recommended? I had 10.6.1.14.4 installed shortly after dasunsrule32 posted it, but I've seen references to 10.6.1.14.8 and 10.6.1.14.10. Do the newer bootloaders fix or improve anything?
Any help is greatly appreciated!!
montec77 said:
Also, which bootloader is now recommended? I had 10.6.1.14.4 installed shortly after dasunsrule32 posted it, but I've seen references to 10.6.1.14.8 and 10.6.1.14.10. Do the newer bootloaders fix or improve anything?
Click to expand...
Click to collapse
No, they only change the version number (I compared the binaries). So any bootloader from 10.6.1.14.4 to 10.6.1.14.10 is fine for all current ROMs.
_that said:
No, they only change the version number (I compared the binaries). So any bootloader from 10.6.1.14.4 to 10.6.1.14.10 is fine for all current ROMs.
Click to expand...
Click to collapse
Any chance you have a bootloader zipped up that I can flash in CWM or a link where I can download it? :fingers-crossed:
montec77 said:
Any chance you have a bootloader zipped up that I can flash in CWM or a link where I can download it? :fingers-crossed:
Click to expand...
Click to collapse
Forgive my asking, but you do have the bootloaderblob file in the same directory as your fastboot.exe, right?
I don't know where you can get the bootloader only, but here's a link where you can get a flashable bootloader/TWRP package. If you're willing to try TWRP download it from the OP.
http://forum.xda-developers.com/showthread.php?t=2425383
berndblb said:
Forgive my asking, but you do have the bootloaderblob file in the same directory as your fastboot.exe, right?
I don't know where you can get the bootloader only, but here's a link where you can get a flashable bootloader/TWRP package. If you're willing to try TWRP download it from the OP.
http://forum.xda-developers.com/showthread.php?t=2425383
Click to expand...
Click to collapse
Yes -- the bootloaderblob is in the same directory. It could be that I'm just not giving it enough time to write before I give up on it, but I've given it upwards of 15 minutes or so without the command finishing.
I tried using one of the flashable bootloader/TWRP packages, and flashing it fails, too, with:
"asset failed: write_raw_image("/data/media/blob", "staging")"
It's as if it won't let anything be written to staging.
I'm going to ask this in the Flatline thread, but I do thank you for your reply!!
*UPDATE* I guess I'm not going to post this in the Flatline thread because I'm not allowed to post in Dev threads -- haha... oh well.
Has anyone who's gone through the Flatline procedure for extracting nvflash blobs followed up and returned back to a stock bootloader? Neither fastboot nor flashing a package in recovery seem to want to write to staging for some reason. I read in another thread that it might be because the bootloader isn't unlocked (double-negative, I know..). Upon booting, the tablet says the bootloader is unlocked in the upper-left corner, but issuing "fastboot -i 0x0b05 getvar all" returns:
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno: xxxxxxxxxxxxxxxx
(bootloader) mid: 001
(bootloader) product: Cardhu
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) uart-on: yes
(bootloader) partition-size:bootloader: 0x0000000000800000
(bootloader) partition-type:bootloader: basic
(bootloader) partition-size:recovery: 0x0000000000800000
(bootloader) partition-type:recovery: basic
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: basic
(bootloader) partition-size:system: 0x0000000030000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001ac00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x00000006e5680000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.105s
(I've replaced my serial number with x's) Is it normal for this command to report back that the bootloader not unlocked, or is that bit of information referring to something else?
montec77 said:
Is it normal for this command to report back that the bootloader not unlocked, or is that bit of information referring to something else?
Click to expand...
Click to collapse
IIRC this is normal.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
_that said:
IIRC this is normal.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
That's a relief that's it's still unlocked (not that it was behaving like it was locked again).
Another thought -- could my problem be that the staging partition is not mounted in fastboot since it didn't show up in the list of partitions from my previous post? After all, the bootloaderblob is supposed to get written to staging, so if it's not there, maybe that's why it's getting stuck..?
montec77 said:
That's a relief that's it's still unlocked (not that it was behaving like it was locked again).
Another thought -- could my problem be that the staging partition is not mounted in fastboot since it didn't show up in the list of partitions from my previous post? After all, the bootloaderblob is supposed to get written to staging, so if it's not there, maybe that's why it's getting stuck..?
Click to expand...
Click to collapse
I'm no expert on this, but I seriously doubt it. There's a bunch of partitions on this device and they aren't listed either.
I wonder if you might have better luck with TWRP instead of CWM. Why don't you try to fastboot TWRP 2.6.1 to your tablet and try to flash the BL/TWRP package from the CROMi-X thread again?
berndblb said:
I'm no expert on this, but I seriously doubt it. There's a bunch of partitions on this device and they aren't listed either.
I wonder if you might have better luck with TWRP instead of CWM. Why don't you try to fastboot TWRP 2.6.1 to your tablet and try to flash the BL/TWRP package from the CROMi-X thread again?
Click to expand...
Click to collapse
Happy Happy Happy
That did the trick! Just about the only combination I probably hadn't over the last week or so.
I flashed the TF700-specific TWRP 2.6.3.1 (without the bootloader in it) found in this post: http://forum.xda-developers.com/showpost.php?p=47153833&postcount=488&nocache=1&z=3454984016028628 , which finally allowed me to flash the bootloader/recovery package in the OP of the CROMi-X thread. Every time I had tried to flash the same bootloader/recovery package within CWM 6.0.4.4 it would fail at trying to update the bootloader, so neither the bootloader nor TWRP recovery were getting installed.
Expert or not, I can't thank you enough for your help, berndblb!! :highfive:
A follow up question for those in-the-know: So the custom recovery that I was using (CWM 6.0.4.4) was stopping flashing a new bootloader to staging through fastboot, or was that just a coincidence? I'm not going to try to fastboot the bootloader again to test it -- I'm on 10.6.1.14.10 US and I'm happy to leave it alone until I *have* to update it again.
The reason I'm asking it to try to better understand the purposes and relationship between APX, Fastboot, recovery. By all means, someone please correct me where I go wrong with this since I'm just speculating:
APX is a very low-level interface, maybe comparable to the BIOS in a PC, where as long as the hardware isn't damaged or corrupted, this interface will be available to read and write (primarily) to memory locations in the internal sdcard?
Fastboot is one level up, providing a fairly low-level interface, with more options for dealing with partitions created on the sdcard?
The recovery (as in CWM or TWRP, etc) is another level up, providing an user interface on the device to install packages and deal with system-level stuff before Android actually boots up and takes over?
I don't even know if any of that is even close to correct, but following teh above, that's why I would be surprised and why I'm asking if the custom recovery would have been able to stop fastboot from installing the bootloaderblob -- I would have thought that the custom recovery would not have been started yet while in fastboot mode.
I am glad this did the trick for you! :GOOD:
I can't tell you why CWM didn't work - I just have no experience with it.... My guess: The bootloader/recovery combo does not work....
About APX, fastboot etc. you're pretty much dead on. Except that APX mode is useless to you if you didn't generate the NVflash blobs to use in APX BEFORE you actually need them.
If you want to make your tablet brickproof, check out this guide from the good people at AndroidRoot who gave us the option of flashing away with peace of mind: https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash/
Note: This requires you to flash a customized bootloader and recovery! You can fastboot back to your current setup afterwards, but maybe you want to give yourself a week or so to just enjoy what you just obtained
Read the guide very carefully and check out the corresponding thread on XDA. This is not for the faint of heart, but I made it work - so it's not that hard
Re-reading your post, there's maybe a little more info I can provide. When you flash a bootloader, it actually gets written to the staging partition. During the next boot it will be written to it's proper partition. That's why you cannot flash a bootloader in recovery and in the same session flash a rom. You have to boot in between for the bootloader flash to take hold.
Already have my multiple copies of my nvflash blobs stashed safely away, and yes, all thanks to the amazing work by the guys at AndroidRoot! I had been kicking myself for just about a year because the first thing I did after I got the tablet was to install any Asus system updates to see if I could live with the tablet stock. Little did I know Asus had *just* pushed the 9.4.5.30 bootloader which blocked access to the nvflash blobs (yeah, and that was the first thing I installed within the first 15 minutes of owning it!! D'oh..).
The Flatline procedure worked great, and exactly as described on the AndroidRoot site and in the Flatline thread. After I had the blobs, I wanted to restore CWM and a standard bootloader. I managed to get CWM installed first, and, well,.. got stuck trying to reinstall the bootloader.
I understood how the bootloader was supposed to get installed -- I've been avidly lurking through the forum for quite a while. But I could not for the life of me get anything to actually transfer it to staging. Apparently the culprit was CWM -- installation would just fail. Perhaps this is a heads up for anyone else using CWM Recovery if we have to update the bootloader again?
Again though, many thanks for your help!!
PS. New Golden Rule: **NEVER** install a manufacturer's system update until you've read all the relevant XDA posts about what is does and what it blocks!! (I stupidly lost root on a Droid 2 Global for about 3 or 4 months that way -- seriously considered getting rid of the phone until someone found away to get root back and I could start flashing roms again!.)
Related
Now I have your attention.
Yeah, I have no idea when it will be released but I thought I would just post a heads up on what has been going on over with the TF300 guys.
There are a lot of people who have now hard bricked their devices (probably 10 to 20 reported cases).
The issue is around the way Asus have implemented their latest boot loader - they seem to have changed the type of partitions it wants to use. I don't understand the full technical details but if you upgrade with the wrong combination of custom recovery it seems very easy to brick the device.
If you are unlocked and are not on TWRP 2.4.4.0 and don't flash a full ASUS STOCK FIRMWARE first it seems this is the most likely cause.
So for every one who is unlocked:
1. Don't try to flash OTA updates under any circumstances - this is the fastest way to hard brick. Noone has recovered from this
2. Make sure you are on TWRP 2.4.4.0 before updating and that includes flashing the FULL ASUS FIRMWARE hosted on their site. CWM is not supported currently.
3. Do not flash just a bootloader blob file from recovery until it can be confirmed it is safe to do so.
Anyway - no news from Asus yet but hopefully enough people will read this so we don't end up like the unfortunate TF300 crowd who have more bricked devices appearing every day as people don't read and think they can just update as they have been used to doing in the past.
BTW there is difficulty downgrading from 4.2.1 to 4.1.1 although one user has successfully done it - it seems very complicated to achieve. I will write it up once we understand it fully.
Please heed the warning folks. (This does not apply to stock locked users who can OTA from 4.1.1 to 4.2.1)
Here is some info from PJC21 (does one of my themes) that may hep some of our expert users understand moreL
pjc21 said:
Thought I'd start new thread for 4.2.1 Update Discussions, issues and other info
So first thing:
I have found out on 4.2.1 if you do fastboot command
Code:
fastboot -i 0x0b05 getvar all
The "bootloader" "recovery" & "boot" partitions are now in basic format, which means the fastboot format command will no longer work on these partitions as it is not a recognized format in fastboot, I never did try this on 4.1.1 when these partitions where in emmc format but believed it would have worked - anyone confirm this?
Code:
C:\android-sdk\platform-tools>fastboot -i 0x0b05 getvar all
(bootloader) version-bootloader: 1.0
(bootloader) version-baseband: 2.0
(bootloader) version: 0.4
(bootloader) serialno:
(bootloader) mid: 001
(bootloader) product: Cardhu
(bootloader) secure: yes
(bootloader) unlocked: no
(bootloader) uart-on: yes
(bootloader) partition-size:bootloader: 0x0000000000800000
(bootloader) partition-type:bootloader: basic
(bootloader) partition-size:recovery: 0x0000000000800000
(bootloader) partition-type:recovery: basic
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: basic
(bootloader) partition-size:system: 0x0000000030000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001ac00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x00000006b3680000
(bootloader) partition-type:userdata: ext4
all:
finished. total time: 0.105s
Not sure what this means as I cannot find any info on basic format & android
Anyone got any info on this?
Click to expand...
Click to collapse
sbdags said:
Here is some info from PJC21 (does one of my themes) that may hep some of our expert users understand moreL
Click to expand...
Click to collapse
It rather helps confuse me more.
Bootloader, recovery and boot partitions never had a filesystem and could never be formatted with fastboot. It can only format ext4. Other partition types can simply be erased or flashed as raw image.
(At least I learned something new - I didn't know that fastboot has ext4 support at all)
I'll just wait until you release cromi 4.2.1 . Asus can shove their update up their collective Assus, see what I did there, ah good times.
Great thread!
Damn important stuff!
Who knows what will come of this.
Man I feel for those guys who bricked
The TF300 forum hasn't been a real happy place since the push.
CROMI 4.0 for the TF300 is already out. I've been moonlighting. Not bad going since I don't actually have a TF300.
Been a long week
Thread Temp Stickied as possible Warning
In light of what happened in the 300 forums as of late, I will temporarily Stick this as a Notice to 700 users.
Remember folks, don't be so quick to start flashing away with new updates. You never know what can happen.
MD's Rule #1 - NEVER take an OTA on a rooted device with unlocked Bootloader. Just asking for trouble. (yes, some people have been lucky)
Give the Dev's a chance to look things over first before you just "assume" everything is OK.
MD
iamborba said:
I'll just wait until you release cromi 4.2.1 . Asus can shove their update up their collective Assus, see what I did there, ah good times.
Click to expand...
Click to collapse
Redditor? I saw what you did there. Hehehe.
hi to poster number one every time i do a full system update with asus full firmware via TWRP ir deletes TWRP will that make a difference?
dady613 said:
hi to poster number one every time i do a full system update with asus full firmware via TWRP ir deletes TWRP will that make a difference?
Click to expand...
Click to collapse
If you flash a full Asus firmware, it will remove your custom recovery (twrp). You need to reflash twrp again.
Good looking out dudes.....
Added a warning to my signature, others should do the same! I would hate for this to happen to any tf700 owners.
"Once you go CHROMI, you never go back to stock"
- Unknown
Ali I Hagen said:
"Once you go CHROMI, you never go back to stock"
- Unknown
Click to expand...
Click to collapse
Something similar
Tylorw1 said:
The Cromi Rom over stock Rom? If that is the question then crazily lol. Once you use Cromi, you never will go back.
Tylor
Click to expand...
Click to collapse
Also will add a link to this thread in the coming days into my signature.
Tylor
Another 5+ people bricked today. It's like a horrible car crash
sbdags said:
Another 5+ people bricked today. It's like a horrible car crash
Click to expand...
Click to collapse
Wowch...Is there a stickied warning thread on the TF300 forum?
Thats OK said:
Wowch...Is there a stickied warning thread on the TF300 forum?
Click to expand...
Click to collapse
Yep people don't read though. In my CROMI 4.0 thread for the TF300 I posted in RED CAPTALS BIG SIZE that you must be on Stock Asus JB 4.2.1, latest bootloader & TWRP 2.4.4.0 before attempting to flash the rom. Already had 2 people ignore this today. One installed straight over 4.1.1. Luckily you can't brick ths way as I do not incude the new bootloader. Another installed from CWM and now has a brick.
Others are bricking because they either flash the bootloader from a previous custom recovery or they install a previous recovery after going to 4.2.1 Currently both are perma-bricks.
There seems to be a general feeling amongst the TF300 users that nvflash no longer restores on the new bootloader..... Let's hope not. I have asked for some confirmation on that one.
I wonder if Asus has completely messed up with this new bootloader?
sbdags said:
There seems to be a general feeling amongst the TF300 users that nvflash no longer restores on the new bootloader..... Let's hope not. I have asked for some confirmation on that one.
I wonder if Asus has completely messed up with this new bootloader?
Click to expand...
Click to collapse
I pray people that have the tf300 are gonna get more cautious. And that people who have the tf700 when the new rom comes out reads. It is a terrible thing that people are bricking their tablets people they are not following proper procedure.
Tylor
Sent from my ASUS Transformer TF700T Infinity Pad Using Tapatalk HD
Rom: CleanRom Inheritance 3.4.6 Odex
Kernal: _That's Stock V4 Kernal
Theme: Timberwolf's Blues & Jazz Theme V1.9
sbdags said:
Yep people don't read though. In my CROMI 4.0 thread for the TF300 I posted in RED CAPTALS BIG SIZE that you must be on Stock Asus JB 4.2.1, latest bootloader & TWRP 2.4.4.0 before attempting to flash the rom. Already had 2 people ignore this today. One installed straight over 4.1.1. Luckily you can't brick ths way as I do not incude the new bootloader. Another installed from CWM and now has a brick.
Others are bricking because they either flash the bootloader from a previous custom recovery or they install a previous recovery after going to 4.2.1 Currently both are perma-bricks.
Click to expand...
Click to collapse
Sorry if that sounds nitpicking ... but in theory, if someone installed the stock Asus v4.2.1 ROM, wouldn't he then have the "latest bootloader" automatically? I was under the impression, Asus stock firmware comes bundled with bootloader and ROM.
Just want to be very exact to be prepared properly for the day "our" v4.2. ROM is unveiled
TF700T Bricked "booting recovery kernel image booting failed unrecoverable bootloader
TF700T Bricked "booting recovery kernel image booting failed unrecoverable bootloader error 0x00000000"
bootloader error is 0x00000000
I can gain access to fastboot and atx mode. No recovery though. Need someone to help me. Give me a tutorial if this is possible to fix. Am moderately familiar with fastboot but prefer instructions with the code so I can just copy and paste. I think if I could get a kernel on it I'd be good. And maybe there is hope since the computer sees it. Windows vista x86. tf700t firmware 10.6.1.14.1-20130329 A03.
Thank you in advance.
Cole:crying:
33colburn said:
TF700T Bricked "booting recovery kernel image booting failed unrecoverable bootloader error 0x00000000"
bootloader error is 0x00000000
I can gain access to fastboot and atx mode. No recovery though. Need someone to help me. Give me a tutorial if this is possible to fix. Am moderately familiar with fastboot but prefer instructions with the code so I can just copy and paste. I think if I could get a kernel on it I'd be good. And maybe there is hope since the computer sees it. Windows vista x86. tf700t firmware 10.6.1.14.1-20130329 A03.
Thank you in advance.
Cole:crying:
Click to expand...
Click to collapse
Reading is your friend
http://forum.xda-developers.com/showthread.php?t=1926286
Seriously though, you can use those directions to flash the recovery. Replace the recovery-jb-touch.img with twrp or whatever recovery you want to use.
Tried Fastboot Kernel/Recovery but Failed
dasunsrule32 said:
Reading is your friend
http://forum.xda-developers.com/showthread.php?t=1926286
Seriously though, you can use those directions to flash the recovery. Replace the recovery-jb-touch.img with twrp or whatever recovery you want to use.
Click to expand...
Click to collapse
I tried that one. But no go. I will attach pic. Do you have any other ideas? Or now and expert I might PM.
Thank you.
Cole
33colburn said:
I tried that one. But no go. I will attach pic. Do you have any other ideas? Or now and expert I might PM.
Thank you.
Cole
Click to expand...
Click to collapse
Tell us what you did that cause this issue?? make sure you stated what software version, bootloader/cwm version during the incident.
33colburn said:
I tried that one. But no go. I will attach pic. Do you have any other ideas? Or now and expert I might PM.
Thank you.
Cole
Click to expand...
Click to collapse
I had this too, when flashing with the 700 attached to a back USB port (which is the primary set, should be fine in tiself), but via an extension cable (apparently NOT OK). I really recommend playing around with your ports and cables -- it gained me my NvFlash blobs after an evening of hair-pulling.
What driver(s) shave you been using/trying?
Thank you.
MartyHulskemper said:
I had this too, when flashing with the 700 attached to a back USB port (which is the primary set, should be fine in tiself), but via an extension cable (apparently NOT OK). I really recommend playing around with your ports and cables -- it gained me my NvFlash blobs after an evening of hair-pulling.
What driver(s) shave you been using/trying?
Click to expand...
Click to collapse
I exchanged the tablet for a new one. I still think I could have brought it back from the dead. One of the questions I asked in another thread was "would it be possible to make a blob with my device specific code from a TWRP backup"? I also understand that nvflash can only be used with the 9.x.x.x bootloaders but those are not compatible with Jelly Bean 4.2. Kinda stinks since I would have liked to stayed on a 9.x.x.x bootloader but, AFAIK you have to update the bootloader to 10.x.x.x in order do install Jelly Bean.
I am only asking for the sake of knowledge as I am one who does not like not being able to solve a problem. Also maybe the infromation contained in a TWRP backup file does not go deep enough to rebuild a blob from it to restore your device?
Thanks for the help.
Cole:good:
33colburn said:
"would it be possible to make a blob with my device specific code from a TWRP backup"?
Click to expand...
Click to collapse
You mean a blob for wheelie&nvflash that contains your bootloader? No.
33colburn said:
I also understand that nvflash can only be used with the 9.x.x.x bootloaders
Click to expand...
Click to collapse
Not true. You can only create the blob file for wheelie with a hacked 9.4.5.30 bootloader, and to install that, you must be on a <= 9.4.5.26 bootloader. After you have this blob and the other backup files, you can upgrade to whatever bootloader you want and still use nvflash with your saved blob. Just don't ever lose it, it's your unique key to nvflash.
Hey guys,
Tonight I went to install cleanrom on my Verizon HTC One M8. I made a nandroid backup as I always do before flashing a new ROM and then proceeded to flash the new ROM. That went great but then I did something I wouldn't normally do I wiped my data just because I wanted a fresh start and all of my important stuff was backed up online. But when I went to boot I'm stuck on the HTC logo. I have an OTG cable so I proceeded to put the ROM on a flash drive and flash it. Same problem. So I put my old ROM ViperOne 2.4 on the flash drive and flashed it. Now I instantly boot into fastboot. This all seems really strange to me but I'm sure its caused by me stupidly formatting data. I need a bigger flash drive to install the original nandroid backup I found online so I will get one today and post my results. I'm almost positive that will fix my problem but I know there might be an HTC guru out there that knows exactly what my problem is and it may be more then what I'm thinking. Sorry this is scattered ive been messing with my phone all night and kinda tired now. Any help is greatly appreciated and thank you in advance for taking time to help me with this issue. And if I missed anything let me know and I will be sure to post it.
Edit
Sorry I completely forgot to add that I put my nandroid backup on my flash drive but when I went to use it it did not work. I believe this is because I did not have a big enough flash drive so it did not completely back up. LOL! Tonight was not my night.
radiowavedev said:
Hey guys,
Tonight I went to install cleanrom on my Verizon HTC One M8. I made a nandroid backup as I always do before flashing a new ROM and then proceeded to flash the new ROM. That went great but then I did something I wouldn't normally do I wiped my data just because I wanted a fresh start and all of my important stuff was backed up online. But when I went to boot I'm stuck on the HTC logo. I have an OTG cable so I proceeded to put the ROM on a flash drive and flash it. Same problem. So I put my old ROM ViperOne 2.4 on the flash drive and flashed it. Now I instantly boot into fastboot. This all seems really strange to me but I'm sure its caused by me stupidly formatting data. I need a bigger flash drive to install the original nandroid backup I found online so I will get one today and post my results. I'm almost positive that will fix my problem but I know there might be an HTC guru out there that knows exactly what my problem is and it may be more then what I'm thinking. Sorry this is scattered ive been messing with my phone all night and kinda tired now. Any help is greatly appreciated and thank you in advance for taking time to help me with this issue. And if I missed anything let me know and I will be sure to post it.
Click to expand...
Click to collapse
Did you flash newest "firmware" as well? The 2.xx.xxx.x ROM's need newest firmware to boot correctly. (Radio, hboot). Old hboot would cause it to hang at boot.
When I flash ROMs in TWRP I go into advanced and check data, dalvik cache, system, and data every time, never had an issue.
andybones said:
When I flash ROMs in TWRP I go into advanced and check data, dalvik cache, system, and data every time, never had an issue.
Click to expand...
Click to collapse
+1
andybones said:
When I flash ROMs in TWRP I go into advanced and check data, dalvik cache, system, and data every time, never had an issue.
Click to expand...
Click to collapse
That is why this was so strange to me. The hboot firmware sounds promising though.
bigblueshock said:
Did you flash newest "firmware" as well? The 2.xx.xxx.x ROM's need newest firmware to boot correctly. (Radio, hboot). Old hboot would cause it to hang at boot.
Click to expand...
Click to collapse
Thank you for the response. I never even knew it was necessary to flash hboot. I've flashed a couple of ROMs before and never flashed hboot. I will try this tonight. Is this just as simple as flashing a zip? And I pick the newest available version?
radiowavedev said:
Thank you for the response. I never even knew it was necessary to flash hboot. I've flashed a couple of ROMs before and never flashed hboot. I will try this tonight. Is this just as simple as flashing a zip? And I pick the newest available version?
Click to expand...
Click to collapse
not just hboot my friend.
the whole firmware.
if you were to take the OTA you would get this firmware installed.
since we are S-OFF and we don't want to take the OTA, as it's MUCH easier to just fastboot the firmware.zip once someone takes the OTA and pulls all the needed files..
here is the thread you want - here
here is a direct copy and paste from the thread full credit to the OP
"4.4.3 DOWNLOADS BELOW no boot or recovery included in this (what this means is that you won't have to re-flash a custom recovery after the firmware, they removed it to make things easier on us.)
https://www.androidfilehost.com/?fid=23622183712470028
CREDIT TO dottat as he posted it 1st so no need for me too well just use his. Be sure to thank him if you see if around.
Flash via fastboot or Sd card method. Flash at your own risk.
directions for flashing firmware via fastboot an radios below.
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip (rename file to firmware.zip)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip firmware.zip
Then fastboot reboot-bootloader��
FYI on my m8 i did not need to be reflushed on 1.55 but on the new update it did.
credit for these directions also come from santod "
andybones said:
not just hboot my friend.
the whole firmware.
if you were to take the OTA you would get this firmware installed.
since we are S-OFF and we don't want to take the OTA, as it's MUCH easier to just fastboot the firmware.zip once someone takes the OTA and pulls all the needed files..
here is the thread you want - here
here is a direct copy and paste from the thread full credit to the OP
"4.4.3 DOWNLOADS BELOW no boot or recovery included in this (what this means is that you won't have to re-flash a custom recovery after the firmware, they removed it to make things easier on us.)
https://www.androidfilehost.com/?fid=23622183712470028
CREDIT TO dottat as he posted it 1st so no need for me too well just use his. Be sure to thank him if you see if around.
Flash via fastboot or Sd card method. Flash at your own risk.
directions for flashing firmware via fastboot an radios below.
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip (rename file to firmware.zip)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip firmware.zip
Then fastboot reboot-bootloader��
FYI on my m8 i did not need to be reflushed on 1.55 but on the new update it did.
credit for these directions also come from santod "
Click to expand...
Click to collapse
Thank you for all of the useful information I will give this a shot tonight.
radiowavedev said:
Thank you for all of the useful information I will give this a shot tonight.
Click to expand...
Click to collapse
Quite welcome, be sure to go into the thread I posted and thank them, it's all their words, I simply copy and pasted it for you.
andybones said:
Quite welcome, be sure to go into the thread I posted and thank them, it's all their words, I simply copy and pasted it for you.
Click to expand...
Click to collapse
Yeah I'm quite used to the ways of XDA but honestly had no idea about hboot. And I definitely will be thanking them. I'm now home and will test it out. I'll post my results afterwards.
andybones said:
Quite welcome, be sure to go into the thread I posted and thank them, it's all their words, I simply copy and pasted it for you.
Click to expand...
Click to collapse
Okay so I downloaded m8.443.firmware.zip does this have to be flashed via fastboot? And once I flash it should I flash my custom rom cleanrom 2.0 rc and that should be it for my issue?
radiowavedev said:
Okay so I downloaded m8.443.firmware.zip does this have to be flashed via fastboot? And once I flash it should I flash my custom rom cleanrom 2.0 rc and that should be it for my issue?
Click to expand...
Click to collapse
well in bootloader/fastboot yes.. but you DO NOT run the fastboot command..
this is exactly what you do
1) the file you downloaded, m8.443.firmware.zip - rename this to firmware.zip
2) adb reboot bootloader (or however you get there)
3) fastboot oem rebootRUU - this is the important part you will be brought to a black screen with a gray HTC logo IIRC, run the next command - the green bar may stop 3/4 of the way this is because you when you run the last command it will finish it.
4) fastboot flash zip firmware.zip
5) fastboot reboot-bootloader
Im sorry this might be stupid but what do you mean by not running fastboot command? And you say reboot-bootloader shouldn't I do reboot-recovery and flash my custom rom after factory resetting of course. Sorry im just trying to make sure im thorough. I would think messing up hboot would permanently brick my phone.
andybones said:
well in bootloader/fastboot yes.. but you DO NOT run the fastboot command..
this is exactly what you do
1) the file you downloaded, m8.443.firmware.zip - rename this to firmware.zip
2) adb reboot bootloader (or however you get there)
3) fastboot oem rebootRUU - this is the important part you will be brought to a black screen with a gray HTC logo IIRC, run the next command - the green bar may stop 3/4 of the way this is because you when you run the last command it will finish it.
4) fastboot flash zip firmware.zip
5) fastboot reboot-bootloader
Click to expand...
Click to collapse
Would it just be easier to use a nandroid backup?
I figure in the meantime ill fill you in on everything I know about my phone. I was previously running the newest version of ViperOne which was 2.5.0 This problem came up after flashing cleanrom 2.0 RC. I am S-off and unlocked of course and I am running CWM-based Recovery v6.0.4.8 and my hboot stats are as follows:
***UNLOCKED***
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.16.0.0000
RADIO-0.89.20.0321
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.55.605.2
eMMC-boot 2048MB
I have searched the forums looking for anything related to my issue and cant seem to come up with anything. I have come across a few people with the same issues as me but there questions go unanswered which makes me very nervous... I do believe it is related to my hboot firmware but I cant seem to find a thorough explanation of hboot. Sorry I am a former Motorola guy. This HTC stuff is really mixing it up for me. LOL!
I really appreciate all of the help you have given me and am grateful that you are hanging in with my HTC stupidity and phobia of bricking this 700 dollar piece of aluminum and magnesium.
radiowavedev said:
I figure in the meantime ill fill you in on everything I know about my phone. I was previously running the newest version of ViperOne which was 2.5.0 This problem came up after flashing cleanrom 2.0 RC. I am S-off and unlocked of course and I am running CWM-based Recovery v6.0.4.8 and my hboot stats are as follows:
***UNLOCKED***
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.16.0.0000
RADIO-0.89.20.0321
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.55.605.2
eMMC-boot 2048MB
I have searched the forums looking for anything related to my issue and cant seem to come up with anything. I have come across a few people with the same issues as me but there questions go unanswered which makes me very nervous... I do believe it is related to my hboot firmware but I cant seem to find a thorough explanation of hboot. Sorry I am a former Motorola guy. This HTC stuff is really mixing it up for me. LOL!
I really appreciate all of the help you have given me and am grateful that you are hanging in with my HTC stupidity and phobia of bricking this 700 dollar piece of aluminum and magnesium.
Click to expand...
Click to collapse
Separate the terminology "ROM" and "Firmware" for a moment. Firmware should/will never change regardless of what ROM's you flash. Think of firmware as a computers BIOS, And ROM as your computers operating system.
First, turn your phone off. Second, hold volume down + power button and do NOT let go of volume down until you're in the boot loader screen. Step 3) switch the boot loader into fast boot within that screen(Fast boot or fast boot USB may come up by default it will be highlighted in red). If you're plugged up to your computer via USB, it should automatically say "Fastboot USB". Then you can execute the commands in the command prompt andybones was talking about.
Did i loose you anywhere?
You could just nandroid back to your previous ROM... but that defeats the purpose. You'll never be able to go to a newer Sense ROM without the firmware upgrade anyway. You might as well get it done because it may improve your network signal, boot times, etc. Usually only benefits you,
After you upgrade firmware, it will say hboot 3.18.0000, Radio: 1.09.20.0702,
radiowavedev said:
Would it just be easier to use a nandroid backup?
Click to expand...
Click to collapse
I didn't just waste my time to write you up a STEP BY STEP FOOL proof guide.
I am not doing this for my benefit...
You made a thread.
You asked for help.
I gave detailed, if you mess up you didn't follow them exactly..
Why would you have me give you exact directions to fix your phone, then ask about a nandroid?
NO. If it were that simple my friend, don't you think I would have let you known this?
I'm sorry if this comes off rude, but I went out of my way to give you exact detailed instructions and you blow them off.
Why make a thread and then not take the advice from a Recognized Contributor to this site!?
I hope you can understand how frustrating this is.
I don't do this because it's fun for me to help get your phone fixed, I do it because you asked for help, and I like to help, but when my help goes un-heard and blown off - I walk away. - Best of luck my friend.
I am still going to help because that's the kind of guy I am..
Run the RUU since you are S-OFF if nothing else works.
You are a SOFT-brick. Very easy to fix.
Andybones, I totally understand. I wasnt trying to be rude im just confused and trying to come up with ideas. I understand it was dumb to mention the nandroid now. I hope you can accept my sincerest apology. I appreciate everything you have done for me and understand if you dont want to help me any longer. Like I said it was not my intention to be rude but I see how it can look like that. I just dont know what im doing.
Hi there, I believe I may have been in the same position as you at some point. What actually is happening is that you are trying to flash a new ROM (4.4.3 I believe) with the old hboot. The ROM should still boot but it will take up to 20min.
How to fix this:
1. Boot into boot loader, (manually or adb)
2. Choose fastboot
3. Connect to USB
4. Open command prompt
5. Fastboot devices
6. fastboot oem rebootRUU
7. You should see a black screen with a dark HTC logo.
8. fastboot flash zip (nameofzip).zip
9. When it finishes type fastboot reboot-bootloader (hyphen required)
10. You just flashed the new firmware but it has no os. You now need to flash a ROM or restore a nandroid backup.
Sent from my HTC One M8 GPE converted using XDA Premium mobile app
Q&A for [ROM] CM 11.0 (Android 4.4) for RazrHD XT925/XT926
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Is this the ROM for the XT926 from Dhacker? Sorry for a noob type question, but sometimes the ROMS have 926 in the file name which makes it easier for guys like me to know I am getting the right one.
androidhosting.org/Devs/Dhacker29/cm-11-20140207-UNOFFICIAL-vanquish.zip
Poor call quality
Has anyone else had the issue where there is poor audio quality in the earpiece? The audio is all crackly and fuzzy, and makes it very hard to understand. I'm not sure if it's hardware or software related right now, and am trying to find out. Another issue which I've had for the past couple months is that the maximum speakerphone volume is SUPER low, much lower than equivalent speaker volume for a youtube video or something. Might this be related (for example, the earpiece volume, which can now go to a deafeningly high level is actually using the gain meant for the speaker and vice versa (resulting in clipping of the signal going to the earpiece, and poor quality)?
Stuck in a boot loop between Motorola boot animation and CWM Recovery menu
Hi guys, Im looking for some help.
I'm a Razr HD (XT925) owner, unlocked bootloader, rooted and CWM 6.0.4.4.
I was running the latest CM 11 KK4.4.2 nightly. Lately it was a bit unstable (freezing and rebooting...sometimes stuck into the CM animation). Due to that I decided to give Epinter's [ROM] CM 11.0 (Android 4.4) for RazrHD XT925/XT926 a try.
Everything ran smoothly, without any sort of error but after the reboot, it got stuck into a loop between the Motorola boot animation, which keeps on my screen for approximately 30 secs, after that the screen turns black, the same Motorola boot animation pops up again, this time for a bit short time and finally, it brings me to the CWM Recovery menu.
I've tried to restore my CM11 KK4.4.2 image but it quickly shows me a message saying
"Checking MD5 sums...
MD5 Mismatch!"
Another strange facts:
After performing the wipe data/factory reset there are the following messages:
(Please note that Bold/Italic ones seemed sorta strange for me...maybe just because I'm being a noob though!)
"__Wiping data...
Formatting /data...
Formatting /cache...
Formatting /SD-ext...
Formatting /sdcard/.android_secure...
E:unknown volume "/sdcard.android_secure"
Data wipe complete"
E:unknown volume for path [/sd-exit]
MD5 checksum mismatch"
While trying to wipe Delvik cache the following message pops up:
"E:unknown volume for path [/sd-ext]"
So, atm, as you can imagine, my cell phone is sorta useless!
Can anyone help me?!?
Thank you in advance for your time and attention!
Cheers!
Edit 1: I've performed Wipe data/Factory reset, Wipe cache partition and Wipe Delvik cache before applying the Epinter's .zip and ggapps from my SD card. I did the same right before Epinter's .zip and ggapps both got installed without any sort of error message. I've did the same several times after the problem starts as well. In my last attempt of solving it by myself, I've repeated it all again since the the 1st step...all wipes and reinstalling both Epinter's and ggapps!
Edit 2:
I've managed to install from CWM an old .zip I found on my storage and my cell phone came back to life in the very same state it was!
Now, I was reviewing each step in order to try to install Epinter's CM11 KK4.4.4 and I've seen he wrote the following:
Recent versions (July/2014) requires an updated (KitKat) bootloader
After that, a doubt came to my mind...Could it be the cause of this mess I was stuck into? Is my unlocked bootloader JB or KK? How can I know it?!? If it is JB, how can I change it to KK?
If you don't updated to official KK you still on jbbl (Jelly Bean Bootloader)... So install latest snapshot (M11) or latest nightly from here: http://download.cyanogenmod.org/?device=moto_msm8960_jbbl instead epinter's old builds
Thanks and a heads up
DorianX said:
If you don't updated to official KK you still on jbbl (Jelly Bean Bootloader)... So install latest snapshot (M11) or latest nightly from here: (Ive had to delete the link because of my low number of posts) instead epinter's old builds
Click to expand...
Click to collapse
Thanks a lot bro!
Well, in this case I'm pretty sure I'm running a JBBL then!
Believe it or not, after several wipe data/cache it is running...with some freeze outs and restartings more often than Id like but still...its running!
The link for the latest JBBL build is kinda broken (After choosing the latest build, it brings me to a 404 not found error page).
Thanks again and Ill come back in a few days when the link to the latest JBBL is working! As for the compatible GAAPS for the latest JBBL build...the same one Ive used alongside with Epinter's should be ok?!?
Cheers!
Yep CyanogenMod servers are having problems since yesterday... Try later, about gapps use a newer ones maybe from here:
http://forum.xda-developers.com/showthread.php?t=2779598
Or here:
http://forum.xda-developers.com/showthread.php?t=2397942
Thanks again and...
DorianX said:
Yep CyanogenMod servers are having problems since yesterday... Try later, about gapps use a newer ones maybe from here:
(Links not allowed yet for me)
Or here:
(Links not allowed yet for me)
Click to expand...
Click to collapse
Thanks again!
Taking as true the assumption that from now on the vast majority of ROMs to come will be made to be used on KKBL, wouldn't it be worth to upgrade to a KKBL now? Would it be too complicated since I'm not sure what was my default cell phone OS since I'm the 2nd owner and I've bought it from an ebay like site here at Brazil! Any tutorial links?
Cheers again!
What is gcm services and is it safe to force close it? It's eating my battery.
[XT925] Stock ROM with KK BL to install CM11
Hi all!
Im looking a ROM to install in my RAZR HD with the KK Bootloader, needed for flash CM11 moto_msm8960 builds
Does anybody knows which ROM comes with that bootloader? Is posible to upgrade bootloader using a jb rom?
Thanks!
cristian04 said:
Hi all!
Im looking a ROM to install in my RAZR HD with the KK Bootloader, needed for flash CM11 moto_msm8960 builds
Does anybody knows which ROM comes with that bootloader? Is posible to upgrade bootloader using a jb rom?
Thanks!
Click to expand...
Click to collapse
As it has been widely discussed multiple times on multiple threads on all the msm8960 device pages, if your device has not been given the official Moto Kitkat, or if you have not taken the official Moto kitkat update, you will use the moto_msm8960_jbbl builds. If your device has been updated to the official Moto Kitkat, you will use the moto_msm8960 builds.
All bootloaders come from Moto, not CM or another third party ROM developer, so no it is not possible to upgrade or downgrade your bootloader with a custom ROM. You can only do this using the sbfs and the guides here on xda.
Sent from my ATRIX HD using XDA Free mobile app
Camera not initialise
Hey i tried the copy/paste method( placing the files in system/app), But then i'm getting the error "Camera not initialize". Can anybody help me, it will be Thankful...
As of late I'm experiencing problems with the Wifi tethering dropping my service. I've been running CM11 for awhile now with no major issues until recently
The problem I'm having is once I enable wifi tethering, hotspot becomes active and all is well. As soon as I connect a device to that network, my phone drops service. This will happen repeatedly. Every once in awhile the service will hold but it's only a matter of time before it drops again. This problem gradually became worse over time until it happens everytime.
Anyone experiencing this issue? I was hoping it was an issue with my current 20140609-SNAPSHOT but I just updated to cm-11-20141008-SNAPSHOT-M11-moto_msm8960_jbbl and still receiving the same problems.
expired link
Hi
it seems the download link for epinter roms is temporary (hope so) dead
"This Domain Name Has Expired"
But I do no read this thread very often; may be I have did'nt read something about this fact
Kind regards,
Serge
Kbbl problem
Dear developer i own two razr hd's (xt925) both currently running stock kitkat uk build ota.when i install any kkbl rom i get E: Error executing updater binary in zip '/external_SD/roms/cm-11-20141008-SNAPSHOT-M11-moto_msm8960.zip'.
I have tried 6 of your builds and some pa too on both devices I have also tried it on twrp 2.8.1.0,2.8.0.0,2.7.0.0 and Phil adv cwm,cwm 6.0.3? . The problem is probably something wrong with my razr hd but I really need to know what it is . Please could you help PS I have downgraded to jb and the jbbl is working fine but a bit slow sometimes.(EDIT)
Fixed by editing update script. Changed ro.boot.secure_hardware from 1 to 0
Wondering if anyone can help me. I've spent all night trying multiple ways to get this to work but it keeps on failing:
I have already unlocked my bootloader. However whenever I try to install CWM I get the following:
G:\PROGRA~1\Android\android-sdk\platform-tools>fastboot flash recovery cwm.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (10146 KB)...
OKAY [ 0.774s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.913s
----------------------------------------------------------
FASTBOOT SHOWS:
AP Fastboot Flash Mode (S)
10.9b(*) (sha-07671a2, 2014-10-15 04:59:29)
eMMC Info: Size 16GB
Device is UNLOCKED, Status Code: 3
----------------------------------------------------------
Current Recovery Shows:
Android system recovery <3e>
KDA20.117-3
---------------------------------------------------------
After trying all night Im beyond frustrated now. Ive tried doing data wipe as well as cache partition wipe as well with no success, so I hope someone can tell me what im doing wrong. Prior to this I was already on the most recent OTA update from Fido Canada (4.4.2?) however this morning when I woke up it wouldn't turn on, when I finally got it to reboot it was stuck on NON-Animated Batwings logo.
Thanks in advance.
Wizard1Canada said:
Wondering if anyone can help me. I've spent all night trying multiple ways to get this to work but it keeps on failing:
I have already unlocked my bootloader. However whenever I try to install CWM I get the following:
G:\PROGRA~1\Android\android-sdk\platform-tools>fastboot flash recovery cwm.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (10146 KB)...
OKAY [ 0.774s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.913s
----------------------------------------------------------
FASTBOOT SHOWS:
AP Fastboot Flash Mode (S)
10.9b(*) (sha-07671a2, 2014-10-15 04:59:29)
eMMC Info: Size 16GB
Device is UNLOCKED, Status Code: 3
----------------------------------------------------------
Current Recovery Shows:
Android system recovery <3e>
KDA20.117-3
---------------------------------------------------------
After trying all night Im beyond frustrated now. Ive tried doing data wipe as well as cache partition wipe as well with no success, so I hope someone can tell me what im doing wrong. Prior to this I was already on the most recent OTA update from Fido Canada (4.4.2?) however this morning when I woke up it wouldn't turn on, when I finally got it to reboot it was stuck on NON-Animated Batwings logo.
Thanks in advance.
Click to expand...
Click to collapse
Boot into fastboot and type "fastboot getvar all" we need more info to help
Sent from my ATRIX HD using Tapatalk
---------- Post added at 09:41 AM ---------- Previous post was at 09:35 AM ----------
http://www.android.gs/install-twrp-recovery-on-motorola-razr-hd-xt925/
Sent from my ATRIX HD using Tapatalk
I think taking that ota might have made your device incapable of flashing the recovery ur trying.
Sent from my ATRIX HD using Tapatalk
G:\PROGRA~1\Android\android-sdk\platform-tools>fastboot getvar all
< waiting for device >
(bootloader) version-bootloader: 109B(*)
(bootloader) product: vanquish_u
(bootloader) secure: yes
(bootloader) mid: 0056
(bootloader) version: 0.5
(bootloader) serialno: TA24000XCM
(bootloader) qe: qe 0/1
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 31457280
(bootloader) emmc-size: 16GB
(bootloader) reason: Boot menu selected
(bootloader) revision-hardware: 0x8300
(bootloader) cpu: MSM8960 CS
(bootloader) uid: D42FFD0102000100000000000000
(bootloader) cid: 0x0e
all:
finished. total time: 0.083s
U should be able to flash a recovery since your BL is unlocked. What exploit did u use to unlock it? I know myth tools can help with most Motorola's.
Sent from my ATRIX HD using Tapatalk
I have a Google version Pixel 2 and have unlocked the bootloader (unlocked/relocked multiple times) and cannot flash any bootloader. I have tried flashing the "production" BL and the Dev Preview BL. I get the same error each time.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38728 KB)...
OKAY [ 0.110s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.125s
I have tried using the fastboot flashing unlock and fastboot flashing unlock_critical commands. I have relocked the BL then booted into the OS and used ADB to reboot to the BL, I still get the same error. I have tried changing the active slot to with no change.. I have tried the google version of platform tools, minimal adb, and another adb version I had from previous phones. I have downloaded the latest drivers from google no change.. I can flash and format other partitions, just not the BL (although I haven't tried format/erase bootloader, and I don't plan to)
I have tried different USB C cables, Google OEM, Samsung OEM, AUKEY .. different USB ports, different computers (although both with Windows 10 64bit).
Any suggestions?
lazarus2297 said:
I have a Google version Pixel 2 and have unlocked the bootloader (unlocked/relocked multiple times) and cannot flash any bootloader. I have tried flashing the "production" BL and the Dev Preview BL. I get the same error each time.
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38728 KB)...
OKAY [ 0.110s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 0.125s
I have tried using the fastboot flashing unlock and fastboot flashing unlock_critical commands. I have relocked the BL then booted into the OS and used ADB to reboot to the BL, I still get the same error. I have tried changing the active slot to with no change.. I have tried the google version of platform tools, minimal adb, and another adb version I had from previous phones. I have downloaded the latest drivers from google no change.. I can flash and format other partitions, just not the BL (although I haven't tried format/erase bootloader, and I don't plan to)
I have tried different USB C cables, Google OEM, Samsung OEM, AUKEY .. different USB ports, different computers (although both with Windows 10 64bit).
Any suggestions?
Click to expand...
Click to collapse
Your not the only one there are others that have had similar issues, though i don't know the fix.
There is a script somewhere on another thread that might help. I will link.
---------- Post added at 05:19 AM ---------- Previous post was at 05:18 AM ----------
Hey you go.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Hopefully something in that will help
Just to be clear, are you using the latest fastboot? That's often an issue.
Some have had trouble with computers with usb-c ports. Have you tried a computer with usb-a and, of course, a usb-a to usb-c cable.
razrlover said:
Your not the only one there are others that have had similar issues, though i don't know the fix.
There is a script somewhere on another thread that might help. I will link.
---------- Post added at 05:19 AM ---------- Previous post was at 05:18 AM ----------
Hey you go.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Hopefully something in that will help
Click to expand...
Click to collapse
Nope that didn't work same error as before..
What's weird is although i can't flash the bootloader using this script did flash the Dev Preview.. So I know that fastboot is working correctly it will just not flash the bootloader..
foosion said:
Just to be clear, are you using the latest fastboot? That's often an issue.
Some have had trouble with computers with usb-c ports. Have you tried a computer with usb-a and, of course, a usb-a to usb-c cable.
Click to expand...
Click to collapse
I have latest everything, i have even tried older versions i have from previous downloads
i am using OEM Google USB a to USB C cable.. I have tried USB 2.0 and 3.0 ports. Running CMD "as administrator" and also tried not using the "as admin" command..
I even dug out my old Windows 7 64bit machine and get the same error.. It's maddening..
lazarus2297 said:
Nope that didn't work same error as before..
What's weird is although i can't flash the bootloader using this script did flash the Dev Preview.. So I know that fastboot is working correctly it will just not flash the bootloader..
I have latest everything, i have even tried older versions i have from previous downloads
i am using OEM Google USB a to USB C cable.. I have tried USB 2.0 and 3.0 ports. Running CMD "as administrator" and also tried not using the "as admin" command..
I even dug out my old Windows 7 64bit machine and get the same error.. It's maddening..
Click to expand...
Click to collapse
I'm not sure if this question will help, are you flashing the bootloader into the correct slot? I had issue early on with this and found that I needed to direct the flash to the correct slot. Just a thought
phonefreedom said:
I'm not sure if this question will help, are you flashing the bootloader into the correct slot? I had issue early on with this and found that I needed to direct the flash to the correct slot. Just a thought
Click to expand...
Click to collapse
Not exactly sure but I have tried changing the active slot to a or b.
I am using the command Fastboot flash bootloader "filename.img" (no quotations) I don't know how I would tell it to flash a specific slot other than whatever is the current active slot..
lazarus2297 said:
Nope that didn't work same error as before..
What's weird is although i can't flash the bootloader using this script did flash the Dev Preview.. So I know that fastboot is working correctly it will just not flash the bootloader..
I have latest everything, i have even tried older versions i have from previous downloads
i am using OEM Google USB a to USB C cable.. I have tried USB 2.0 and 3.0 ports. Running CMD "as administrator" and also tried not using the "as admin" command..
I even dug out my old Windows 7 64bit machine and get the same error.. It's maddening..
Click to expand...
Click to collapse
lazarus2297 said:
Not exactly sure but I have tried changing the active slot to a or b.
I am using the command Fastboot flash bootloader "filename.img" (no quotations) I don't know how I would tell it to flash a specific slot other than whatever is the current active slot..
Click to expand...
Click to collapse
+Natahranta had shared the following with me and I hope it helps in your case...
"Download factory image from Google, unpack it, insidebis another zip, there is boot.img file
Flash it to both slots A and B. It must be the same version/update your phone was on.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
If you're not sure which exactly stock rom build your phone is on, use the flash_all.bat to flash the whole image on your phone, to be sure you have no mismatch between system and boot. Just remove "-w" from the bat file so it doesn't erase your user data"
So i got it working here is what I did..
I used the factory image to flash back 100% stock and relocked the bootloader, I then signed my device up for the Dev Preview, and surprisingly I got the notification to install DP pretty quickly. After DP installed I rebooted into the bootloader and noticed that my bootloader version had changed to the DP BL version. I then unlocked with the standard Fastboot Flashing Unlock command and unlocked the bootloader. After the phone rebooted I shut it down and booted into the BL and flashed the stock BL (a downgrade) it was successful, so i flashed the DP BL version and it was successful as well. Rebooted normally into the OS and all is well.
Hopefully this will help anyone else having the same problem.
lazarus2297 said:
I have relocked the BL then booted into the OS
Click to expand...
Click to collapse
I don't have any suggestions for your issue. But don't relock it, ever. You are playing with fire, if it goes bad and it's locked you are done.
lazarus2297 said:
So i got it working here is what I did..
I used the factory image to flash back 100% stock and relocked the bootloader, I then signed my device up for the Dev Preview, and surprisingly I got the notification to install DP pretty quickly. After DP installed I rebooted into the bootloader and noticed that my bootloader version had changed to the DP BL version. I then unlocked with the standard Fastboot Flashing Unlock command and unlocked the bootloader. After the phone rebooted I shut it down and booted into the BL and flashed the stock BL (a downgrade) it was successful, so i flashed the DP BL version and it was successful as well. Rebooted normally into the OS and all is well.
Hopefully this will help anyone else having the same problem.
Click to expand...
Click to collapse
I had this problem and created a thread about it a month ago: https://forum.xda-developers.com/pixel-2/help/failed-remote-command-flash-error-t3701929. A couple other people in that thread are now also reporting the problem.
No one seemed to know what the " FAILED (remote: Command Flash Error)" means. I never figured it out.
At the time of the November update, however, I was able to sideload OTA images with adb without problem. I assume that the OTA method also updates the bootloader, like the Dev Preview did for you. I couldn't tell with the November update, though, because it had the same version of the bootloader in it as the one that shipped with the phone.
So I'm wondering if simply sideloading the current December OTA image with adb would accomplish the same thing you did, without having to lock the bootloader, unlock it again, and go through the pain of wiping the device. I wonder if there was just something weird about the original version of the bootloader. Weirdness like this was discussed early on with the Pixel 2 in this XDA article: https://www.xda-developers.com/pixel-2-failing-flash-factory-images/ If I'm right, then once one sideloads the December OTA image and gets a new bootloader, there may not be an issue flashing bootloaders with fastboot in the future. I assume that the Dev Preview also used the OTA method to update the device.
In other words, I'm wondering if the step of unlocking and relocking the bootloader was not necessary. You just had to do it to get the Developer Preview (right?).
Just guessing here. I haven't had time yet to try this.
Okay, I tried my idea above and I was correct. Simplying sideloading the December OTA image updates the bootloader. After that the problem is solved. I can successfully flash the bootloader .img file directly (from the factory image zip) using fastboot. So I assume going forward there should not be any problems flashing factory images, instead of sideloading OTA images.
This solution also avoids having to lock and unlock the bootloader and wipe the whole device in the process.
cb474 said:
Simplying sideloading the December OTA image updates the bootloader.
Click to expand...
Click to collapse
My problem is that I have TWRP installed and it won't sideload nor flash the OTA file. I am trying to figure out how to flash the factory recovery. Unlike the factory images of before, there is no obvious recovery image in the zip.
-----------
Nevermind. I figured out that recovery is part of boot now. I flashed the factory boot and flashing OTA now.
snovvman said:
My problem is that I have TWRP installed and it won't sideload nor flash the OTA file. I am trying to figure out how to flash the factory recovery. Unlike the factory images of before, there is no obvious recovery image in the zip.
Click to expand...
Click to collapse
I'm not really sure how to solve that problem. Perhaps you should ask in the TWRP thread. I thought that when you install TWRP it backs up the recovery and has a way to restore it. But I could be wrong about that. You're correct that the recovery image does not seem to be included in the factory image zip like it used to be. I have seen other people mention that.
cb474 said:
I'm not really sure how to solve that problem. Perhaps you should ask in the TWRP thread. I thought that when you install TWRP it backs up the recovery and has a way to restore it. But I could be wrong about that. You're correct that the recovery image does not seem to be included in the factory image zip like it used to be. I have seen other people mention that.
Click to expand...
Click to collapse
Thanks for replying. Silly me, I was thinking the old way of doing business, where the recovery had its own image/partition. I figured out that recovery is part of boot, so I flashed boot and got the factory recovery back. I'm on 8.1 now.
snovvman said:
Thanks for replying. Silly me, I was thinking the old way of doing business, where the recovery had its own image/partition. I figured out that recovery is part of boot, so I flashed boot and got the factory recovery back. I'm on 8.1 now.
Click to expand...
Click to collapse
Glad you solved your problem. Interesting to know how the recovery works now. Perhaps that will be useful knowledge for me in the future. I'm kind fo waiting until TWRP comes out of beta and hopefully works in a more straightforward way, until I get into that. It is sad that the great old days of the Nexus devices being so developer friendly seem to really be over.
cb474 said:
Glad you solved your problem. Interesting to know how the recovery works now. Perhaps that will be useful knowledge for me in the future. I'm kind fo waiting until TWRP comes out of beta and hopefully works in a more straightforward way, until I get into that. It is sad that the great old days of the Nexus devices being so developer friendly seem to really be over.
Click to expand...
Click to collapse
So you know, TWRP for the first gen Pixels never left beta. They worked well enough... For Pixel 2s, I use the current beta for backups and they are handy for certain things. For now I am booting to TWRP to flash Magisk. For me, it is more convenient than patching.
cb474 said:
Glad you solved your problem. Interesting to know how the recovery works now. Perhaps that will be useful knowledge for me in the future. I'm kind fo waiting until TWRP comes out of beta and hopefully works in a more straightforward way, until I get into that. It is sad that the great old days of the Nexus devices being so developer friendly seem to really be over.
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php
kendong2 said:
https://forum.xda-developers.com/showpost.php
Click to expand...
Click to collapse
That link leads to nothing.
---------- Post added at 01:13 AM ---------- Previous post was at 01:11 AM ----------
snovvman said:
So you know, TWRP for the first gen Pixels never left beta. They worked well enough... For Pixel 2s, I use the current beta for backups and they are handy for certain things. For now I am booting to TWRP to flash Magisk. For me, it is more convenient than patching.
Click to expand...
Click to collapse
Yeah, I saw that. I'm just hoping with what was learned from the original Pixel and given that supposedly most phones will eventually use the A/B partition scheme that maybe TWRP will advance further on the Pixel 2. I really miss nandroid backups. I miss LineageOS too. Everything was so much simpler on my old Nexus 4. And I wasn't constantly feeling like I was going to brick my device every time I tried to do something.
cb474 said:
That link leads to nothing.
Click to expand...
Click to collapse
Sorry, did that on the phone. Was supposed to go here: https://forum.xda-developers.com/showpost.php?p=74704694&postcount=155
TWRP 3.2.0.0 final release (as I understand it) has been announced a few days ago. Don't know why the thread title still says beta.
This is freaking weird. Anyway, followed post #11 to sideload DEC OTA zip in stock recovery, and now finally I have a bootloader that is 0066 on both slot a and b. Thanked @cb474 !