Whenever I try to flash TWRP I am getting error: target reported max download size of 536870912 bytes
You can only flash recovery under 53 mb size. Check your recovery.img
Came across this and just wanted to make a note that it's 536 MB, not 53 MB.
I found a solution. Might work for others:
Target reported max download (solution) - file naming issue
I had this issue and it was driving me nuts. I'm on Linux, but I think it might work on Windows, too. I created a folder called "Flash" in the home directory (C drive on Win) and moved the recovery and ROM files there, then changed their names to...
forum.xda-developers.com
Related
How to replace the ADVENT logo on the boot screen.
The screen resolution is 1024x600.
How to replace your Boot Screen:
Create and save your bootscreen as a PNG (if it is smaller than 1024x600, your bootscreen will be centered, transparency will result in the ANDROID boot glare effect).
1. Connect your Vega to your PC's usb.
2. Turn USB Debugging on in the Applications menu.
3. In command prompt / terminal, browse to the directory containing adb.exe, type:
Code:
adb-windows pull /system/framework/framework-res.apk /framework-res.apk
This will copy the framework-res.apk from your Vega and save it in the directory adb.exe is located.
4. Open framework-res.apk in WinZIP / WinRAR or similar and browse to /assets/images/
5. Replace android-logo-mask.png with your bootscreen and save the apk in the same format, overwriting the original.
6. In your already open command prompt / terminal window type:
Code:
adb-windows remount
adb-windows shell rm /system/framework/framework-res.apk
adb-windows push framework-res.apk /system/framework/
7. Reboot your Vega.
********* Reducing the file size *******************
If you want to reduce the file size of your new framework-res.apk file, you could delete the following files from /res/drawable/:
nvidia_wallpaper01.jpg
nvidia_wallpaper02.jpg
nvidia_wallpaper03.jpg
nvidia_wallpaper04.jpg
nvidia_wallpaper05.jpg
nvidia_wallpaper06.jpg
nvidia_wallpaper07.jpg
nvidia_wallpaper_dual01.jpg
nvidia_wallpaper_dual02.jpg
nvidia_wallpaper_dual03.jpg
nvidia_wallpaper_dual04.jpg
nvidia_wallpaper_dual05.jpg
nvidia_wallpaper_dual06.jpg
nvidia_wallpaper_dual07.jpg
Also you can remove all *.ogg from the following directory /system/media/ringtones
Boot Screens:
File name: Advent_Vega_Leather.jpg File size: 235.60 KB
File name: android3d.jpg File size: 366.66 KB
File name: Androidboot.jpg File size: 1.24 MB
File name: androidlogomask.png File size: 807.17 KB
File name: Androidwall.jpg File size: 136.15 KB
File name: Android_green.jpg File size: 123.04 KB
File name: Android_logo.jpg File size: 86.83 KB
File name: android_logo_mask.png File size: 18.18 KB
File name: android_logo_mask2.png File size: 40.21 KB
File name: boot.jpg File size: 1.25 MB
File name: Bootphotoshop.jpg File size: 337.77 KB
File name: Bootphotoshop2.jpg File size: 337.44 KB
File name: Bootphotoshop3.jpg File size: 354.39 KB
File name: Bootphotoshop4.jpg File size: 233.84 KB
File name: stealboot.jpg File size: 513.15 KB
File name: Vega_Black_Leather.jpg File size: 434.97 KB
File name: Vega_Glow.jpg File size: 321.36 KB
File name: wallpapergrey.jpg File size: 77.28 KB
******** Thanks to JordanT92 who provided the original information.
******** And boffboff, remlap, morchuboo, arad85, wobblydoggy, Higgsy, donalkeane from MoDaCo who provided the graphics.
@percy25 - are you just copy/pasting all this stuff from the modaco forums?
Everytime I come and refresh here, it seems there's another thread with the same info...
At least give some credit to the users from other places, who've done the work already?
monkeyboy451 said:
@percy25 - are you just copy/pasting all this stuff from the modaco forums?
Everytime I come and refresh here, it seems there's another thread with the same info...
At least give some credit to the users from other places, who've done the work already?
Click to expand...
Click to collapse
Good point Monkeybot451, Updated Post.
I have moved my Post "Advent Vega - ROMs / Software Updates / Guides / How Tos, Links to ROMs, Flash Updates, Guides, Misc apk's" from Modaco to here as from now will only be maintaining it here.
percy25 said:
Good point Monkeybot451, Updated Post.
I have moved my Post "Advent Vega - ROMs / Software Updates / Guides / How Tos, Links to ROMs, Flash Updates, Guides, Misc apk's" from Modaco to here as from now will only be maintaining it here.
Click to expand...
Click to collapse
Seriously that just sucks and I think unfair I honestly don't see this community growing the numbers MoDaCo has.
Good luck with it though but these kinds of attitudes make me dislike this forum. Seems like cutting and running for no reason to me.
remlap said:
Seriously that just sucks and I think unfair I honestly don't see this community growing the numbers MoDaCo has.
Good luck with it though but these kinds of attitudes make me dislike this forum. Seems like cutting and running for no reason to me.
Click to expand...
Click to collapse
I didnt mean to upset anyone!
I have just found the XDA Developers fourm more open to development as its free to all (Instead of the charging scheme modaco uses). I believe updates should be available to all for the community to benefit.
To keep everyone happy I will maintain both post to benefit all.
Hi Percy, yeah thats true, still you don't have to pay MoDaCo still use the forums I honestly like the idea of two separate forums doing different things that I can take the best from both and hopefully contribute where I can
Cheers mate
Please note that this is a very easy way to lock your device.
I tried to change my boot screen and got stock in booting due to "insufficient disk space" issue, and had to reflash the device.
Harplo said:
Please note that this is a very easy way to lock your device.
I tried to change my boot screen and got stock in booting due to "insufficient disk space" issue, and had to reflash the device.
Click to expand...
Click to collapse
True, I been in that situation many times. I sometimes find if you use a "adb shell rm" command to remove old framework.apk first, this can help.
percy25 said:
I have just found the XDA Developers fourm more open to development as its free to all (Instead of the charging scheme modaco uses). I believe updates should be available to all for the community to benefit.
Click to expand...
Click to collapse
Could not agree with your more. Welcome to xda dev, hope we can all do great things to are vegas.
You are keeping me happy with all of your useful info. Helped loads with the performance pack. Thanks
I have updated the attached framework-res.apk to include the following:
Android Boot Screen
Battery Colour changed to Blue (instead of Green by default)
Removed the Nvidia Wallpapers to keep file size down.
Link to File:
File name: framework-res.apk File size: 6.49 MB
See the first post for instructions on how to install.
So my NookTouch finally arrived!
But I'm having trouble writing images to a SD card.
It's a 16gb micro SD HC class 6 card...
i thought that would be ok?
Windows Image writer says `Not enough space` so I used dd for windows but after this the disk isn't readable. The same for linux (remembered to use bs=1M).
edit::
Solved answer - confusion using windows tools, don't really know why it wasn't working but it could have been due to an incorrect dd command on linux beforehand.
You need to write to /dev/sdcardRoot (aka masterbootpartition) rather than /dev/sdcard1 (partition1). After you've rooted though and written the image you can format the card and partition the SD card.
I had a similar problem with my 5 in 1 built in card reader.
Some apps would say "not enough space" while some would write the img without complaints, but the Nook wouldn't boot it, no matter what.
I ended up pushing the image file to my phone (X10) and using that to write the image to the sd card, worked perfectly.
Are you using WinImage?
Thanks for fast reply!
Verfied the image is ok with winimage.
Wierd. After writing TouchNooter to sd card via the sd card drive in the laptop the card is no longer readable. After putting it in the NookTouch the nook can't see it either and I can't get linux mount it. But... with the card in the Nook and USB plugged in I get 2 drives come up; `Nook` and `TouchNooter`
Nook software version is `1.0.0`.
In linux the disk looks like this:
Code:
Disk /dev/sdb: 251 MB, 251641856 bytes
8 heads, 60 sectors/track, 1023 cylinders
Units = cylinders of 480 * 512 = 245760 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
Disk /dev/sdc: 16.0 GB, 16038952448 bytes
128 heads, 32 sectors/track, 7647 cylinders
Units = cylinders of 4096 * 512 = 2097152 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdc1 * 1 38 77808 c W95 FAT32 (LBA)
/dev/sdc3 7 7 0 0 Empty
Partition 3 does not end on cylinder boundary.
[email protected]:/media/WindowsStorage/download/nook$
With WinImage I can read the contents of the image but if I try to write it I get `The current image format is not supported by the disk drive` --- ***correction, it's writing now after I reformatted the card***....
now testing...
`nook is starting up...` aha `Rooted forever!!` hmm.. seems to be taking a very long time....
ok, nothing's happening... i wonder if it's turned on or crashed! ok trying usb now... ah, got a different device recognised by windows (omap3630).. trying apb etc...
perhaps I should be using noogie only for the touch though... hmm...
right, need to find the omap3630 driver in the android sdk to get those 7 partitions mounted... this is my first android device I've used... no usb driver listed in the sdk under available packages.. perhaps I should try linux...
Ok, got the shell. What next to install? I'll have a search.
The confusing thing was the android sdk. It took me a while to find the USB driver comes through via google's distro service on Windows and that the adb command is in there too. The location of the USB driver has also moved to the google/usbdriver subdirectory now too.
Next stop, trying to install some android .apk's...
Thanks one and all!
edit::
I'll use this as a diary for a moment to note what I'm finding until I'm sure enough to put it in the Wiki.
In general I'm finding some things that work on the color work on the touch but not all. VNCServer works but we only have /dev/input/event0-2 - the server notes the input clicks but doesn't do anything about them ("injectTouchEvent (x=0, y=0, down=1)" even when specifying -k trying each of those events...
this could be related to the NookTouch using infared rather than a touchscreen. Perhaps there's a new B&N dev file in there rather than a custom resident running program or something.
VNCViewer on the NookTouch seems to work but personally I couldn't get it to connect to my server. I'll try linux to confirm.
WiFi locker doesn't work, complaining that's it's an incompatible app: http://nookdevs.com/Nook_WiFi_Locker the wiki is the only place for a download link, there appears to be no mention now of it on the nooktools page:
Code:
E:\ProgramFiles\androidSDK\platform-tools>adb install "h:\nookWifiLocker.apk"
503 KB/s (40277 bytes in 0.078s)
pkg: /data/local/tmp/nookWifiLocker.apk
Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]
E:\ProgramFiles\androidSDK\platform-tools>
Plugging in my USB stops the nook turning off while using adb though. Need to turn off wifi and connect over usb...
Nooklets look like a great idea - could it be scripted to allow direct access to webpages saved via scrapbook extention for firefox?
Other things to improve the wiki:
-suggest putting adb.exe in path
Any problems?
-because I don't have any other android devices I can't see how to get access to apk's from android market... http://phandroid.com/2011/02/04/sol...-android-phones-associated-with-this-account/ "No phones associated with this account"
This confused me:
adb -d shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
adb push NookColorTools_0.2.apk /system/app
adb reboot
Click to expand...
Click to collapse
- was that an old way to install apps before `adb install`? Because any app I install via adb install isn't listed in /system/apps, yet it is installed because if I try to install again it tells me so...
edit: note for myself regards the confusion over google accounts, gmail and missing libaries:
Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY]
To set this up correctly, there are 2 key files that need to be copied to the system:
com.google.android.maps.xml
com.google.android.maps.jar
These files are located in the any of these google app packs:
http://android.d3xt3r01.tk/cyanogen/gapps/gapps-gb-20110120-signed.zip
http://goo-inside.me/gapps/gapps-gb-20110120-signed.zip
http://android.local.host.name/gapps/gapps-gb-20110120-signed.zip
After unzipping any of these files, you want to copy the files to your system, like-ah-so:
adb remount
adb push system/etc/permissions/com.google.android.maps.xml /system/etc/permissions
adb push system/framework/com.google.android.maps.jar /system/framework
adb reboot
Read more: http://nookdevs.com/Honeycomb_Google_Apps_and_Market#ixzz1ZUFM1yei
Under Creative Commons License: Attribution Non-Commercial Share Alike
Click to expand...
Click to collapse
this probably works better than:
http://senk9.wordpress.com/2010/12/03/how-to-install-google-apps-gapps-on-your-android-device-phone/
jago25_98 said:
- was that an old way to install apps before `adb install`? Because any app I install via adb install isn't listed in /system/apps, yet it is installed because if I try to install again it tells me so...
Click to expand...
Click to collapse
No
adb install (or Market for that sake) will push apps to /data/app where apps normally reside.
/system/app is where the pre-packaged apps normally live, some choose to put them there to save space, but there might be other differences as I've seen that some apps needs to be put there in order to work properly .. haven't really looked into it tho.
/data/app, ah ok thanks Ros
I see you're on Netcom. Are they still super expensive? I was on pay as you go on holiday in Norway and man they still had per mb charging for both netcom and telenor when I was there, it was super expensive!
What I don't understand is how I'm supposed to install the market app... in order to get access to the market, seeing as I don't have another android device... the market apk says it needs some kind of dependency, but I can't find any mention of this, or get adb to tell me what the dependency is I need to satisfy
...
I must have plugged and unplugged the usb port a 50x already... need a port saver I can tell it's going to break quick!
jago25_98 said:
/data/app, ah ok thanks Ros
I see you're on Netcom. Are they still super expensive? I was on pay as you go on holiday in Norway and man they still had per mb charging for both netcom and telenor when I was there, it was super expensive!
Click to expand...
Click to collapse
Sorry for the late reply mate
I have no idea when it comes to personal plans, but neither one of them is particularly bad when it comes to business plans.
Ofc they make a lot of money on people not choosing the right plans and services for their needs, but if you do it right it's not bad at all
---------- Post added at 01:17 AM ---------- Previous post was at 01:10 AM ----------
jago25_98 said:
What I don't understand is how I'm supposed to install the market app... in order to get access to the market, seeing as I don't have another android device... the market apk says it needs some kind of dependency, but I can't find any mention of this, or get adb to tell me what the dependency is I need to satisfy
Click to expand...
Click to collapse
Market requires a ****load of stuff in order to work at all.
A successful TouchNooter should give you Market access assuming you followed the instructions (logging into youtube with your gmail account etc)
Problem with TouchNooter Market is that search doesn't work, so you have to use a web browser to log into market and push the apps you want to your Nook.
I find some topic to make multi boot for X5 but I don't know exactly how do it !
http://forum.donanimhaber.com/m_59231411/tm.htm
And here:
-------------------------------------
Multi-boot
In fact, users in China use the U8800, multi-system has been used for a long time.
So, now I will use my broken English to tell you how to use multi-system
First, you need The extra two partitions in the 4G space. you could use twosys-partition.zip to get The extra two partitions 15&16
download partition package:http://forum.xda-developers.com/atta...1&d=1321675310
And
The second system-specific recovery system
http://forum.xda-developers.com/atta...1&d=1321675310
put the twosys-partition.zip and you like rom's zip into Sdcard
rename the recovery_4.0.1.5_en_sys2.img to recovery2.img , then place it to /cust
Boot into recovery,flash this package directly, same as flashing a ROM.
After flashing go to advanced options, choose to reboot to recovery.
Go into recovery again, flash this package again directly, same as flashing a ROM.now you will have The extra two partition 15 and 16
OK, let's flash two system into you phone
Go into recovery again, flash you like rom's zip
boot into first system, you could use RootExplorer access /cust, rename the recovery.img to recovery1.img, rename the boot.img to boot1.img,rename the recovery2.img to recovery.img.
reboot you system into recovery, now you recovery is second system recovery,you could flash the 100911-cm7,it will auto flash into second system.
reboot system, you will into second system (CM7)
if you want change you system to first, you could use RootExplorer access /sbin/gk, you will found some .sh files,Execution the 8-ChangeSys will auto rename all
img file then auto reboot to first system.
you could copy the 8-changesys.sh to any place let you change system easy.
restore offical partition ： download
Important：only the 100911-CM7 can flash into second system, other ROM only flash into first system
please backup your data, because you will lost all data in phone
Attached Thumbnails
Click image for larger version Name: IMG_20110507_215751.jpg Views: 12861 Size: 82.6 KB ID: 589834 Click image for larger version Name: CAP201106210959.jpg Views: 7380 Size: 23.3 KB ID: 631536 Click image for larger version Name: CAP2011062109581.jpg Views: 11102 Size: 29.6 KB ID: 631537
Attached Files
File Type: zip offical-partition-2sys.zip - [Click for QR Code] (1.29 MB, 1459 views)
File Type: zip twosys-partition.zip - [Click for QR Code] (1.19 MB, 525 views)
File Type: zip recovery5.0.2.7_en_sys1.zip - [Click for QR Code] (4.20 MB, 788 views)
File Type: zip recovery5.0.2.7_en_sys2.zip - [Click for QR Code] (4.20 MB, 633 views)
Click to expand...
Click to collapse
So any one who can held us to make multi boot for X5 Actual Fine ?
http://forum.donanimhaber.com/m_59231411/tm.htm is my guide and it's for 35 kernels
Multi-boot
In fact, users in China use the U8800, multi-system has been used for a long time.
So, now I will use my broken English to tell you how to use multi-system
First, you need The extra two partitions in the 4G space. you could use twosys-partition.zip to get The extra two partitions 15&16
download partition package:http://forum.xda-developers.com/atta...1&d=1321675310
And
The second system-specific recovery system
http://forum.xda-developers.com/atta...1&d=1321675310
put the twosys-partition.zip and you like rom's zip into Sdcard
rename the recovery_4.0.1.5_en_sys2.img to recovery2.img , then place it to /cust
Boot into recovery,flash this package directly, same as flashing a ROM.
After flashing go to advanced options, choose to reboot to recovery.
Go into recovery again, flash this package again directly, same as flashing a ROM.now you will have The extra two partition 15 and 16
OK, let's flash two system into you phone
Go into recovery again, flash you like rom's zip
boot into first system, you could use RootExplorer access /cust, rename the recovery.img to recovery1.img, rename the boot.img to boot1.img,rename the recovery2.img to recovery.img.
reboot you system into recovery, now you recovery is second system recovery,you could flash the 100911-cm7,it will auto flash into second system.
reboot system, you will into second system (CM7)
if you want change you system to first, you could use RootExplorer access /sbin/gk, you will found some .sh files,Execution the 8-ChangeSys will auto rename all
img file then auto reboot to first system.
you could copy the 8-changesys.sh to any place let you change system easy.
restore offical partition ： download
Important：only the 100911-CM7 can flash into second system, other ROM only flash into first system
please backup your data, because you will lost all data in phone
Attached Thumbnails
Click image for larger version Name: IMG_20110507_215751.jpg Views: 12861 Size: 82.6 KB ID: 589834 Click image for larger version Name: CAP201106210959.jpg Views: 7380 Size: 23.3 KB ID: 631536 Click image for larger version Name: CAP2011062109581.jpg Views: 11102 Size: 29.6 KB ID: 631537
Attached Files
File Type: zip offical-partition-2sys.zip - [Click for QR Code] (1.29 MB, 1459 views)
File Type: zip twosys-partition.zip - [Click for QR Code] (1.19 MB, 525 views)
File Type: zip recovery5.0.2.7_en_sys1.zip - [Click for QR Code] (4.20 MB, 788 views)
File Type: zip recovery5.0.2.7_en_sys2.zip - [Click for QR Code] (4.20 MB, 633 views)
Click to expand...
Click to collapse
this guide for 32 kernels.
forumber2 said:
http://forum.donanimhaber.com/m_59231411/tm.htm is my guide and it's for 35 kernels
Click to expand...
Click to collapse
Can you translate it?
Google translate is s**t
Sent from my U8800 using Tapatalk 2
Qqqxxxzzz said:
Can you translate it?
Google translate is s**t
Sent from my U8800 using Tapatalk 2
Click to expand...
Click to collapse
i will try but i dont have enough time.
Please !
Could you transalate to English please ?
on p8 lite ale-l21, when i want to flash system.img, size is more than 1.5gbs, the adb refuse with these sentence;
TARGET REPORTED MAX DOWNLOAD SIZE OF 471859200 BYTES,. what anyone guide how to flash system.img.
Q.2: i extracted update.app, it has files with .img extension, how to edit/repack these and make a flashable.zip file?
huawei2016 said:
on p8 lite ale-l21, when i want to flash system.img, size is more than 1.5gbs, the adb refuse with these sentence;
TARGET REPORTED MAX DOWNLOAD SIZE OF 471859200 BYTES,. what anyone guide how to flash system.img.
Q.2: i extracted update.app, it has files with .img extension, how to edit/repack these and make a flashable.zip file?
Click to expand...
Click to collapse
Try with Minimal ADB & Fastboot... Default ADB & Fastboot cannot flash large files...
it just failed.
huawei2016 said:
it just failed.
Click to expand...
Click to collapse
Even with Minimal AFB & Fastboot?
That shouldn't happen..
Put the system.img in Minimal ADB & Fastboot folder (C:/Program Files (x86) / Minimal ADB & Fastboot) and then try to flash.. That should do the job...
i'll tell later, this worked or not. thanks
Now i tested, it also failed. but no problem.
i just flashed the whole update.app.
but curious, how to modify system.img and make flashable zip of rom.
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...".