Database Users

Cannot flash webtop

just done a full sbf flash to 1.8.3 and then the puddin sbf and now i am getting
Code:
C:\adb>moto-fastboot flash boot atrix-2.3.4-hktw-boot.img
sending 'boot' (3358 KB)... OKAY [ 0.263s]
writing 'boot'... OKAY [ 0.551s]
C:\adb>moto-fastboot flash system atrix-2.3.4-hktw-system.img
sending 'system' (262144 KB)... OKAY [ 20.649s]
writing 'system'... OKAY [ 13.953s]
sending 'system' (65410 KB)... OKAY [ 5.071s]
writing 'system'... OKAY [ 3.469s]
C:\adb>moto-fastboot flash webtop atrix-2.3.4-hktw-webtop.img
load_file: could not allocate 805177344 bytes
error: cannot load 'atrix-2.3.4-hktw-webtop.img'
C:\adb>moto-fastboot flash recovery recovery-en-goapk-0625-2034.img
sending 'recovery' (4598 KB)... OKAY [ 0.370s]
writing 'recovery'... OKAY [ 0.665s]
C:\adb>
I think my webtop partition is corrupted... I was trying to send the update zip from this thread to my sdcard from adb by using adb push Navalynt_HKTW_v1.7_webtop.zip /sdcard-ext/Navalynt_HKTW_v1.7_webtop.zip and itt sat there for a long time so i unplugged the usb cable. since then this was happening. I can still run GB 2.3.4 and 1.8.3 but for some reason I can't flash the webtop partition

I'm not sure when come from the error but it looks like your computer or may be your phone don't have enought memory to allocate (for the flash process).

That's funny because I've done it before when it was first leaked. i'm not sure what's going on

Seriously? am I the only one this happened to?

SolidHelix said:
error: cannot load 'atrix-2.3.4-hktw-webtop.img'
Click to expand...
Click to collapse
If you look at that error, it looks like its looking for another file named "atrix-2.3.4-hktw-webtop.img"
SolidHelix said:
and itt sat there for a long time so i unplugged the usb cable. since then this was happening.
Click to expand...
Click to collapse
From the Developers post:
**DOWNLOAD v1.7a HERE (WITH Webtop fix)**
*Please ignore that when the script runs it still says v1.6, it's really v1.7 I just forgot to update that line before uploading!
FYI -The Webtop takes a few minutes to install ... so once you start flashing the zip let it be a few minutes (it's working, not frozen)!
SolidHelix said:
Seriously? am I the only one this happened to?
Click to expand...
Click to collapse
Dude chill out. Its only been a hour since you posted. Check back in a day or two.

If you look at that error, it looks like its looking for another file named "atrix-2.3.4-hktw-webtop.img"
Click to expand...
Click to collapse
Isn't that the file I'm attemting to flash?
From the Developers post:
**DOWNLOAD v1.7a HERE (WITH Webtop fix)**
*Please ignore that when the script runs it still says v1.6, it's really v1.7 I just forgot to update that line before uploading!
FYI -The Webtop takes a few minutes to install ... so once you start flashing the zip let it be a few minutes (it's working, not frozen)!
Click to expand...
Click to collapse
I don't think you are following.. I didn't pull the plug while flashing this update in CWM. I was in CWM and connected via adb and typed command adb push Navalynt_HKTW_v1.7_webtop.zip /sdcard-ext/Navalynt_HKTW_v1.7_webtop.zip to load the zip onto my sd-card so that I COULD flash it with cwm. rather than booting up my phone and copying via usb host. I'm after installing this zip I know it takes a while to get past the webtop part.
anyway I still can't see why I can't flash the webtop partition. I have done so several times since the bootloader got unlocked.
Dude chill out. Its only been a hour since you posted. Check back in a day or two.
Click to expand...
Click to collapse
Agreed

bump..... obviously not gonna get any help here pushed to the second page with no replies... guess i'll have to get flamesd for bringing it to the development section

Just want to say, I found the problem.. It was my USB 3.0 port. ****ty Asus drivers, it never worked right. copying large files cause it to fail. Who would have thought? Oh well back to normal.
btw
THANKS FOR THE SUPPORT EVERYONE!!!
just kidding... no one could help me with that one

Interesting, I have the same problem.

Not sure if this could have fixed it too.
I flashed CG58.SMG from 1.8.3 sbf. That is the webtop original webtop image from 1.8.3. I used depacker to split the 1.8.3 sbf into smg files, found CG58.smg and renamed to CG58.IMG and flashed with mot-fastboot. The thing is, when it fixed i was flashing from a different computer so that's why figured it was the USB that was the problem
Download depacker 1.3 here
Open 1.8.3 sbf with it and click split
browse to the folder it created and find CG58,smg and rename to CG58.img
put img in same dir as moto-fastboot
in cmd promt run moto-fastboot flash webtop CG58.img
Like I said I'm not sure it was this that fixed it or the fact that I flashed from a different computer this time
Sent from my MB860 using XDA Premium App

Yeah, did what you did with the depacker, still having same problem. I am guessing it is the usb drivers. I tried using flash_image script from cyanogen mod, but that spits out a syntax error(great...). I am gonna try to rewrite the mmcblk0p13 partition with the dd command, is that the same as flashing?
I should ask tenfar if he can add an option to backup/restore/flash /osh to cwm. That would be nice.

[GUIDE] Restore to stock after soft BRICKED | Install TWRP, Root, Kernel --March 2017

EDIT: UPDATED March 6th, 2017 for March Google Security Updates Image
-------------------------------------------------------------------------
-------------------------------------------------------------------------
Stey-by-Step for Newbies Guide for restoring a bootloader-unlocked Pixel XL back to factory stock
This guide is ideal for soft-brick situations where you can't boot to your operating system​
***Verizon users should research before doing ANYTHING.
***Europe users should be researching before using North American images, though it's usually okay to do so.
SOFT BRICK vs. HARD BRICK:
-What is a hard brick? Well, if you cannot access your bootloader then you're probably hard-bricked and need to do a warranty repair.
-A soft brick is when you CAN access your boot loader. Because if you can access your boot loader then you can repair your own software issue by following this guide.
If your phone is soft bricked and you send it in for warranty then you're a twat.
BOOTLOADER:
How do I access my bootloader? Power off your phone. Hold down the power button and volume down button at the same time, for 20-40 seconds. If you just now shut down the phone, then it takes longer for the bootloader to come up. If the phone has been powered down at least 30 seconds then the bootloader should come up quicker. If your phone is stubbornly upset then it may take several tries and also holding down the two buttons for 40-60 seconds. Another thing that may prevent you from accessing the bootloader is a low battery of course. Never do any software trickery without at least a half full battery for multiple random reasons.
The directions below are for Windows 7 and may need to be modified for other OS's.
***Anyone who doesn't want to lose their setup/apps/user data, just edit the flash-all.bat to remove the -w from the script. Then it won't wipe anything.
You can use this modified flash-all.bat. It's for the latest March "B" image:
http://www.filedropper.com/flash-all_1
1) Install the Google Android driver if your Pixel XL isn't already recognized by your computer when booted to fastboot mode.
https://developer.android.com/studio/run/win-usb.html#download
2) Download the factory system image for Pixel XL (Marlin) to C:/Google
https://developers.google.com/android/images
---Here is the direct link for March "B - NOF27B" for All Other users (what we're using in this guide):
---https://dl.google.com/dl/android/aosp/marlin-nof27b-factory-2259c206.zip
---Here is the direct link for March "C - NOF27C" for Rogers users:
---https://dl.google.com/dl/android/aosp/marlin-nof27c-factory-b49c0e7b.zip
3) This is what the folder should look like after the download:
4) Now extract the file.
Your folder should look like this:
5) Go into the extracted folder:
6) The contents of the extracted folder should look like this:
7) Download Google's ADB/Fastboot files to this same folder:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
8) Now extract the ADB download to this same folder. Edit the path to look like it does below:
9) The folder should now look like this:
10) Go into that new folder and CUT all the contents:
11) Go up one folder and PASTE the files into the factory image folder:
12) The folder should now look like this:
13) Now boot your phone to Fastboot mode.
Power off the phone & disconnect from USB cable.
Wait 30 seconds.
Then press Power + Volume Down until you see this screen on your phone:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
14) Now connect your phone to your computer via USB-C cable.
15) Wait 30 seconds.
16) Then double-click the ever famous "flash-all.bat" to restore your phone to stock.
17) You'll see a black command prompt window pup up and start restoring your phone to stock image.
It'll take 5-15 minutes and when completed, the output should look just like this, except for the "A" vs. "B" designations may be swapped around, and that's fine.
Code:
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32976 KB)...
OKAY [ 0.876s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 4.705s]
finished. total time: 5.583s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.048s
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'radio_a' (57192 KB)...
OKAY [ 1.457s]
writing 'radio_a'...
OKAY [ 0.562s]
finished. total time: 2.022s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.048s
< waiting for any device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1701181700
Baseband Version.....: 8996-012511-1701091826
Serial Number........: HT6920203793
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.049s]
checking version-baseband...
OKAY [ 0.048s]
sending 'boot_a' (26173 KB)...
OKAY [ 0.690s]
writing 'boot_a'...
OKAY [ 0.299s]
erasing 'system_a'...
OKAY [ 0.265s]
sending sparse 'system_a' 1/4 (515613 KB)...
OKAY [ 13.636s]
writing 'system_a' 1/4...
OKAY [ 5.355s]
sending sparse 'system_a' 2/4 (514104 KB)...
OKAY [ 13.720s]
writing 'system_a' 2/4...
OKAY [ 6.234s]
sending sparse 'system_a' 3/4 (499613 KB)...
OKAY [ 13.263s]
writing 'system_a' 3/4...
OKAY [ 5.738s]
sending sparse 'system_a' 4/4 (32756 KB)...
OKAY [ 0.891s]
writing 'system_a' 4/4...
OKAY [ 0.359s]
erasing 'system_b'...
OKAY [ 0.297s]
sending sparse 'system_b' 1/4 (517080 KB)...
OKAY [ 13.672s]
writing 'system_b' 1/4...
OKAY [ 5.247s]
sending sparse 'system_b' 2/4 (514384 KB)...
OKAY [ 13.502s]
writing 'system_b' 2/4...
OKAY [ 10.252s]
sending sparse 'system_b' 3/4 (524287 KB)...
OKAY [ 13.766s]
writing 'system_b' 3/4...
OKAY [ 13.995s]
sending sparse 'system_b' 4/4 (85786 KB)...
OKAY [ 2.280s]
writing 'system_b' 4/4...
OKAY [ 2.969s]
erasing 'vendor_a'...
OKAY [ 0.250s]
sending 'vendor_a' (235322 KB)...
OKAY [ 6.049s]
writing 'vendor_a'...
OKAY [ 5.236s]
Setting current slot to 'a'...
OKAY [ 0.172s]
erasing 'userdata'...
OKAY [ 5.251s]
sending 'userdata' (138957 KB)...
OKAY [ 3.550s]
writing 'userdata'...
OKAY [ 1.298s]
rebooting...
finished. total time: 158.668s
Press any key to exit...
`
You're done.
There is no reason to continue reading this thread unless you want to "go the extra mile".
=================================
=================================
18) The phone automatically reboots at this point.
15) After it finished booting, I let it settle for five minutes.
16) I then reboot the phone (unnecessary step, just something I like to do).
17) I then log in and tell Google to restore my account from the cloud.
18) I set Display to stay on for 30 minutes so the phone doesn't go to sleep and my apps can restore without interruption.
19) After all apps are restored, I reboot and then update any remaining apps that need updates.
***OPTIONAL TIP*** Just prior to doing the flash-all.bat, it may not be a bad idea to make the additional step of flashing stock boot.img to both the A & B partitions.
Why not, right? This step is entirely optional and is only for good measure
Make sure you extracted the Google Image you downloaded, to the point where you find the boot.img and place it into the C:/Google folder.
The fastboot commands to install it are as follows:
Code:
fastboot flash boot_a boot.img
then...
Code:
fastboot flash boot_b boot.img
The output should look like this:
Code:
C:\Google>fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (26229 KB)...
OKAY [ 0.718s]
writing 'boot_a'...
OKAY [ 0.296s]
finished. total time: 1.030s
C:\Google>fastboot flash boot_b boot.img
target reported max download size of 536870912 bytes
sending 'boot_b' (26229 KB)...
OKAY [ 0.718s]
writing 'boot_b'...
OKAY [ 0.265s]
finished. total time: 0.983s
C:\Google>
20) Boom, you're all done.
Either go find something else to do or continue reading this guide to root your phone, install TWRP and custom kernel.
=================================
=================================
*** MAY UPDATE USERS SEE THIS POST BEFORE GOING ANY FURTHER:
https://forum.xda-developers.com/showpost.php?p=72329767&postcount=176
TWRP, ROOT AND CUSTOM KERNEL INSTALL
****The next steps are only if you want to install TWRP, Root your phone and install ElementalX kernel.****
1) I enabled SystemUI Tuner (OPTIONAL).
2) I enabled Developer Options (OPTIONAL).
3) I enabled USB Debugging in Developer Options (OPTIONAL).
4) I enabled "Unknown Sources" in Security (OPTIONAL).
5) Download SuperSU root v2.79 SR3:
https://plus.google.com/+Chainfire/posts/27xToSqi5em
-----------Support thread for SuperSU
6a) Download TWRP RC1 IMG file:
https://dl.twrp.me/marlin/twrp-3.0.2-0-RC1-fastboot-marlin.img.html
6b) Download TWRP RC1 zip file:
https://dl.twrp.me/marlin/twrp-pixel-installer-marlin-3.0.2-0-RC1.zip.html
-----------Support thread for TWRP
7) Download ElementalX-P-1.07 kernel:
http://elementalx.org/devices/pixel/
-----------Support thread for ElementalX
8) Copy the TWRP, kernel and Root zip files to your Pixel's /sdcard (filenames in pic are outdated, sorry):
9) Copy TWRP's RC1 IMG file to C:/Google
10) Right-click any white spot in C:/Google and select the option to "Open Command Window Here"
11) Copy and paste the command "fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img".
The output should look like this after you press enter.
Code:
C:\Google>fastboot boot twrp-3.0
.2-0-RC1-fastboot-marlin.img
downloading 'boot.img'...
OKAY [ 0.710s]
booting...
OKAY [ 0.858s]
finished. total time: 1.578s
C:\Google>
The Pixel will automatically reboot to TWRP RC1 recovery.
12) Put a checkmark on the box "Never show this screen during boot again" and then swipe to allow modifications.
Click "Install".
Scroll down and click on the file named "twrp-pixel-installer-marlin-3.0.2-0-RC1.zip"
Swipe to confirm flash.
13) Reboot to Recovery.
14) Click the "Install" button.
15) Install the root file "SR3-SuperSU-v2.79-SR3-20170114223742.zip".
16) Reboot phone and verify root works. Do NOT install kernel yet. You need Superuser running first to gain ElementalX's advanced install options.
17) Now reboot to TWRP RC1 Recovery to install Kernel.
18) Install the kernel file "ElementalX-P-1.07.zip".
Go through the prompts to select your kernel options you want.
I recommend choosing the defaults unless you're a kernel expert who knows what to expect.
Now reboot normally.
Wait five minutes after bootup for the kernel to "settle".
Enjoy your modded Pixel XL!
=================================
=================================
TWRP BACKUP AND RESTORE
This section is if you installed TWRP and want to do a full ROM backup.
It's not as "obvious" on how to do this vs. older phones with TWRP.
The initial method is the same.
1) Boot to TWRP
2) Select the "Backup" option
3) Back up the "Boot", "System", "Vendor" and "Data". The Vendor option is important and may be new to some of you (it was to me).
If you want a "bit-for-bit" backup, then also select "System Image" and "Vendor Image". This will make your backup file size much larger than usual.
To restore, just do as normal.
Locate your backup and restore all items listed above.

I love this guide, but when I rebooted, it turns out I took the OTA, unintentionally and lost root. Any idea how I can block the OTA?

dablitzkrieg said:
I love this guide, but when I rebooted, it turns out I took the OTA, unintentionally and lost root. Any idea how I can block the OTA?
Click to expand...
Click to collapse
in developer settings....make sure automatic updates is not turned on

v2.2v said:
in developer settings....make sure automatic updates is not turned on
Click to expand...
Click to collapse
I'll try that and report back. Thanks
---------- Post added at 12:56 PM ---------- Previous post was at 12:21 PM ----------
v2.2v said:
in developer settings....make sure automatic updates is not turned on
Click to expand...
Click to collapse
I had that turned off and it still automatically pushed the update to X. How do I root now?

dablitzkrieg said:
I'll try that and report back. Thanks
---------- Post added at 12:56 PM ---------- Previous post was at 12:21 PM ----------
I had that turned off and it still automatically pushed the update to X. How do I root now?
Click to expand...
Click to collapse
Same method as before
Flash SuperSU in bootloader mode
Sent from my sailfish using XDA Labs

sd_shadow said:
Same method as before
Flash SuperSU in bootloader mode
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
I'm on Verizon X. I am now stuck at the bouncing balls screen when I tried this suggestion. Any help would be appreciated.

dablitzkrieg said:
I'm on Verizon X. I am now stuck at the bouncing balls screen when I tried this suggestion. Any help would be appreciated.
Click to expand...
Click to collapse
There is lots of discussion about this in the SuperSU thread.
I'm not VZW so I can't help much, sorry.

maybe very stupid question ( and also very stupid from me to not look for it) but i dont know whitch version i have to select P, L or H. And cant watch it anymore Is there a way to find it out ?
Never mind i got it
---------- Post added at 10:51 PM ---------- Previous post was at 10:02 PM ----------
thanx for the great guide !!!!

dablitzkrieg said:
I'm on Verizon X. I am now stuck at the bouncing balls screen when I tried this suggestion. Any help would be appreciated.
Click to expand...
Click to collapse
WHat GB model do you have? flash-all flashed userdata, which cannot be flashed on 128GB model, I am searching for a manual way like the nexus 6P, flash each partition manually, in this thread, http://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478 it shows the output and I think to do it manually must flash everything but userdata and do not format userdata if you want to keep internal memory in tact. I have seen some other guides, but they have not worked for me, because it is fastboot system system.img and I think it is fastboot system_a and fastboot system_b, like I said follow the commands and output

yung40oz84 said:
WHat GB model do you have? flash-all flashed userdata, which cannot be flashed on 128GB model, I am searching for a manual way like the nexus 6P, flash each partition manually, in this thread, http://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478 it shows the output and I think to do it manually must flash everything but userdata and do not format userdata if you want to keep internal memory in tact. I have seen some other guides, but they have not worked for me, because it is fastboot system system.img and I think it is fastboot system_a and fastboot system_b, like I said follow the commands and output
Click to expand...
Click to collapse
I am actually all set. Thx for the response though! It was simply an outdated adb/fastboot.

There is a possibility that Minimal ADB & Fastboot has some slightly older code buried in it so I recommend installing it, then updating the files using the link in step 2 just to be on the safe side.
Here's the link again. Thanks, Scott.
http://ul.to/6f5616c3

CZ Eddie said:
There is lots of discussion about this in the SuperSU thread.
I'm not VZW so I can't help much, sorry.
Click to expand...
Click to collapse
WHat GB model is yours? 128 or 32? I ask because previously on nexus 6P or older nexus devices you could not flash userdata on anything higher than 32GB model as it would only allocate 32GB on a 128Gb or 64GB model and mess internal size up. Also, this took you completely back to stock, like fresh out of the box setup, when I followed this manually it only was like an OTA, I still had my apps, data. etc.

yung40oz84 said:
WHat GB model is yours? 128 or 32? I ask because previously on nexus 6P or older nexus devices you could not flash userdata on anything higher than 32GB model as it would only allocate 32GB on a 128Gb or 64GB model and mess internal size up. Also, this took you completely back to stock, like fresh out of the box setup, when I followed this manually it only was like an OTA, I still had my apps, data. etc.
Click to expand...
Click to collapse
I'm 32GB.
But Google only offers one image and script for the 32 and 128.

CZ Eddie said:
I'm 32GB.
But Google only offers one image and script for the 32 and 128.
Click to expand...
Click to collapse
They only offer one image for the 6P and 5X as well regardless of memory size, but you still CANNOT flash userdata on a 64GB or 128GB 6P, it will leave you with only 32GB of space when booting up your phone, I know this for a fact, it is most likely the same for the Pixel and Pixel XL.
Note: You should never flash the userdata image. It doesn't take into consideration the storage capacity of the device and always allocates 32gb of storage. This is ok for the 32gb model, but for the 64gb and 128gb models you'll end up with much less storage capacity than you should have. If you wish to wipe your internal storage you'd use the following command instead:
Which I do not wipe internal memory anyway, but still cannot flash userdata for bigger storage models.

Can anyone other than yung40oz84 confirm that the flash-all.bat on a 128GB phone causes partition size issues?

CZ Eddie said:
Can anyone other than yung40oz84 confirm that the flash-all.bat on a 128GB phone causes partition size issues?
Click to expand...
Click to collapse
I used the flash all script on my 128gb version with no issues.

Thank God you fixed my Phone. I wanted to use the only rom out there and it killed my phone. Thank you for a clear instruction on how to restore my phone! Wish every one would be a little more clear.

Ok have a issue. When I run flash-all.bat I get waiting on device. Phone is already in bootloader mode. And device is recognized by adb.

moosc said:
Ok have a issue. When I run flash-all.bat I get waiting on device. Phone is already in bootloader mode. And device is recognized by adb.
Click to expand...
Click to collapse
It's clearly a lack of communication issue.
Wrong driver?
Are you sure you're in Bootloader and not in Recovery?
Recovery uses ADB and Bootloader uses fastboot.

Yeah I'm in bootloader. Also redid USB drivers. Tried using skip soft it rebooted into bootloader then hung up on waiting for any device
CZ Eddie said:
It's clearly a lack of communication issue.
Wrong driver?
Are you sure you're in Bootloader and not in Recovery?
Recovery uses ADB and Bootloader uses fastboot.
Click to expand...
Click to collapse

Where is logo.bin located?

I've managed to unlock the bootloader on my Athene. And, like everyone else, I got the logo screen replacement telling me that my device is now nasty and untrustworthy. I have done the fastboot flash logo method of replacing it and now it shows a black screen with "N/A" in white (which is better than the nasty-gram that was there). Just wondering what I missed. I have tried a TON of logo.bin files, dialog says it flashed fine, but I still get the N/A. So, I'm thinking if I just delete the logo.bin at it's current location, and replace it with a "known good" one, that I would have a "normal" logo instead of the N/A.
Suggestions?

Hi I tried several methods until the only one that worked for me was. https://www.youtube.com/watch?v=Rf41ls5hF6c&t=8s

i tried replacing my logo.bin file as well. looking for suggestions as well

mikemelbrooks said:
Hi I tried several methods until the only one that worked for me was.QUOTE]
That's the method I used... over and over. I used different logo.bins from various sources but the result is the same... I have N/A on black.
Thanks, though, for your response. :good:
Click to expand...
Click to collapse

apparently its stored on the radio/moodem section of storage which is why its not accessible with a file browser.

Can you use something like root Explorer?
Sent from my LGL41C using Tapatalk

tekweezle said:
Can you use something like root Explorer?
Sent from my LGL41C using Tapatalk
Click to expand...
Click to collapse
I've tried Rom Toolbox Pro, Root Explorer, and Total Commander. None of them find it during a search.

When you flash logo.bin do you get this in command I reflashed mine tonight.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (1267 KB)...
OKAY [ 0.043s]
writing 'logo'...
OKAY [ 0.041s]
finished. total time: 0.085s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>

Haven't removed the logo yet but for me it says bad key whenever I launch instead of N/A. When I boot into TWRP it does say N/A though.
Sent from my Moto G (4) using XDA-Developers mobile app

Install Fire HD 8 8th generation firmware on a HD 8 7th gen?

Hi all,
with the procedured descibed here:
https://forum.xda-developers.com/hd...nt/fire-hd8-2017-amonet-debrick-root-t3897841
it should be possible to unlock the bootloader of the Fire HD 8 7th generation (2017).
I know that there aren't any custom ROM for HD 8 7th, but I would like to use a Fire OS based on Nougat (the current firmware 5.6.4.0 is still based on Lollipop).
So my question is: is it possible to flash the HD 8 7th gen with the firmware 6.3.0.1?
This is the latest version of the HD 8 8th firmware.
I know that the hardware of the 8th generation is almost the same of the 7th generation.
The 6.3.0.1 firmware can be downloaded here:
https://www.amazon.com/gp/help/customer/display.html?nodeId=202144610
Thanks is advance

Isn't possible, because your Fire tablet can be bricked.

Really sad that Amazon doesn't support its devices with software updates for more than 1 year.

im gonna try it, ive been thinking about it too
Edit 1: First issue is that the system image is too big for the current system partition size. Gonna work on that.
Edit 2: I resized the partition, which got me further into flashing system.img via fastboot, but then it gets suck on this part:
Code:
[email protected]:~/Downloads/6300$ sudo fastboot flash system system.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/21 (109856 KB) OKAY [ 5.693s]
Writing 'system' OKAY [ 6.485s]
Sending sparse 'system' 2/21 (106632 KB) OKAY [ 5.586s]
Writing 'system'

CPVideoMaker said:
im gonna try it, ive been thinking about it too
Edit 1: First issue is that the system image is too big for the current system partition size. Gonna work on that.
Edit 2: I resized the partition, which got me further into flashing system.img via fastboot, but then it gets suck on this part:
Code:
[email protected]:~/Downloads/6300$ sudo fastboot flash system system.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/21 (109856 KB) OKAY [ 5.693s]
Writing 'system' OKAY [ 6.485s]
Sending sparse 'system' 2/21 (106632 KB) OKAY [ 5.586s]
Writing 'system'
Click to expand...
Click to collapse
Don't modify the gpt manually. You can **** up it.
Also it's not possible due kernel problems too.

Rortiz2 said:
Don't modify the gpt manually. You can **** up it.
Also it's not possible due kernel problems too.
Click to expand...
Click to collapse
Ah okay :/
edit: I just reflashed stock and it seems that the device survived the repartitioning, luckily.

Can someone help me to install the official original system of the Amazon fire 8 7th tablet? It's in the logo help

New ColorOS 6 and new kernel? (+ a few issues with old ROMs)

The old kernels were 4.4.78 - but in the latest ColorOS 6 (based on Android 9 instead of 8) I noticed the kernel is now 4.4.153 - not far behind the very latest commit at the time of writing (193) - but has the source code been published anywhere??? Perhaps we can find that kernel source under a different Realme device. I could then have a go at turning on virtualization again via the built-in KVM kernel module (enabled through make menuconfig just prior to compilation).
The kernel is dated August 24th - so would that make it newer than Firmware version A21? The firmware is named up as RMX1807EX_11_C.24 or RMX1801EX_11_OTA_0240
I've uploaded it here in normal ZIP format if you need it. You can flash it with the latest TWRP or R2X2:
https://eu.dl.twrp.me/RMX1801/
https://forum.xda-developers.com/realme-2-pro/development/stable-r2x2-recovery-t3899121
If you've already unlocked the bootloader: just reboot and hold volume DOWN to get to Fastboot and plug into a Windows 10 PC via USB:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.3.1-1-RMX1801.img
target reported max download size of 536870912 bytes
sending 'recovery' (24412 KB)...
OKAY [ 0.524s]
writing 'recovery'...
OKAY [ 0.110s]
finished. total time: 0.637s
OR
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery R2X2.img
target reported max download size of 536870912 bytes
sending 'recovery' (25165 KB)...
OKAY [ 0.560s]
writing 'recovery'...
OKAY [ 0.120s]
finished. total time: 0.684s
Copy RMX1801EX_11_OTA_0240_all_HRfI3IQiI3cB.zip to disk along with Magisk-v19.3.zip. Boot into Recovery, wipe everything except Internal storage and the last 2-3 under cache, and then click on Install to flash each ZIP file in turn.
The problem for me though: I'm not then able to install @SamarV-121's LineageOS 16 nor LinegageOS 15 anymore - even after installing the old vendor.img! And for some reason I have to keep manually mounting the data partition for files to appear in recovery. Lastly, I have a different "bootloader unlocked" screen during fastboot (might that be a secure boot screen that could be turned off?). At one point my Wifi even stopped working - so not sure what's going!? But everything seems stable right now under ColorOS 6 - still unlocked and rooted - except for that flashing message in red at the top of the screen "Rooting of your phone.... Tap to fix...".