Hi,
I have an unknown tab working under android 4.2.2 , how can i install TWRP or CWM on it? the apps on playstore don't help me ..
help me please
Thank you
saywow said:
Hi,
I have an unknown tab working under android 4.2.2 , how can i install TWRP or CWM on it? the apps on playstore don't help me ..
help me please
Thank you
Click to expand...
Click to collapse
is it rootable? if you dont know any information of the device you probably have to build a custom recovery yourself.
Yes it's rooted , all the information that i have aren't similar to these of the others android device (all of them start with ATLAS10 (the device name)) , what kind of information you need ? how can i creat my own recovery mod? am wondering if there is any way to backup my frimeware and creat a custom rom for it? because the stock rom is using 4xx\1024 Mo of memory (when boot) and there is no custom rom for my device
saywow said:
Yes it's rooted , all the information that i have aren't similar to these of the others android device (all of them start with ATLAS10 (the device name)) , what kind of information you need ? how can i creat my own recovery mod? am wondering if there is any way to backup my frimeware and creat a custom rom for it? because the stock rom is using 4xx\1024 Mo of memory (when boot) and there is no custom rom for my device
Click to expand...
Click to collapse
There are a few ways to make your own recovery, you would just have to look at guides, does it have a mediatek CPU? If so I don't know if you can, I could be wrong but still.
Trozzul said:
There are a few ways to make your own recovery, you would just have to look at guides, does it have a mediatek CPU? If so I don't know if you can, I could be wrong but still.
Click to expand...
Click to collapse
How can i know if i have mediatek CPU or not ?!
saywow said:
How can i know if i have mediatek CPU or not ?!
Click to expand...
Click to collapse
There are a few apps on the playstore that can tell your device information. Most Chinese tablets are mediatek
Trozzul said:
There are a few apps on the playstore that can tell your device information. Most Chinese tablets are mediatek
Click to expand...
Click to collapse
i have processor = ARMv7 Processor rev0 (v7l)
Cpu max/min clock : 1608/312 MHZ
MEMTOtAL = 1GB
is that good ?
saywow said:
i have processor = ARMv7 Processor rev0 (v7l)
Cpu max/min clock : 1608/312 MHZ
MEMTOtAL = 1GB
is that good ?
Click to expand...
Click to collapse
At least its clocked kinda high, still need to find out what CPU version is it
how can i ?!
saywow said:
how can i ?!
Click to expand...
Click to collapse
Download atuntu and run it, it should tell you. At least it has 1gig of ram.
Trozzul said:
Download atuntu and run it, it should tell you. At least it has 1gig of ram.
Click to expand...
Click to collapse
do you mean antutu benchmark ?!
saywow said:
do you mean antutu benchmark ?!
Click to expand...
Click to collapse
yes benchmark, sorry meant what CPU it has not CPU version. at the end of the test it shoudl tell you your device specs.
Ok thank you , once i will connect to wifi i will re download it and i will answer you because i don't have it anymore , by the way i have already benchmarked it and the result was better then s3's result (+20.000Points)
saywow said:
Ok thank you , once i will connect to wifi i will re download it and i will answer you because i don't have it anymore , by the way i have already benchmarked it and the result was better then s3's result (+20.000Points)
Click to expand...
Click to collapse
haha my moto x is 22k how many cores?
Trozzul said:
haha my moto x is 22k how many cores?
Click to expand...
Click to collapse
Quad if my memory is good
and the results was before i "optimize it" with any thing
saywow said:
do you mean antutu benchmark ?!
Click to expand...
Click to collapse
my cpu is rk3188
saywow said:
my cpu is rk3188
Click to expand...
Click to collapse
Crap rockchip, i dont know about their partitions, you said its rooted? type this in the terminal app (you can get it off the play store) type in SU first
Code:
cat /proc/mtd
tell me the outcome.
also see here http://androtab.info/clockworkmod/rockchip/ im not positive on it
Trozzul said:
Crap rockchip, i dont know about their partitions, you said its rooted? type this in the terminal app (you can get it off the play store) type in SU first
Code:
cat /proc/mtd
tell me the outcome.
also see here http://androtab.info/clockworkmod/rockchip/ im not positive on it
Click to expand...
Click to collapse
That's hurt my feelings
dev: size erasesize name
mtd0: 00400000 00004000 "misc"
mtd1: 01000000 00004000 "kernel"
mtd2: 01000000 00004000 "boot"
mtd3: 02000000 00004000 "recovery"
mtd4: 22800000 00004000 "backup"
mtd5: 18000000 00004000 "cache"
mtd6: 40000000 00004000 "userdata"
mtd7: 00400000 00004000 "kpanic"
mtd8: 20000000 00004000 "system"
mtd9: 33b800000 00004000 "user"
saywow said:
That's hurt my feelings
dev: size erasesize name
mtd0: 00400000 00004000 "misc"
mtd1: 01000000 00004000 "kernel"
mtd2: 01000000 00004000 "boot"
mtd3: 02000000 00004000 "recovery"
mtd4: 22800000 00004000 "backup"
mtd5: 18000000 00004000 "cache"
mtd6: 40000000 00004000 "userdata"
mtd7: 00400000 00004000 "kpanic"
mtd8: 20000000 00004000 "system"
mtd9: 33b800000 00004000 "user"
Click to expand...
Click to collapse
Alright cool it has a mtd partition, so that's a good thing. You SHOULD be able to follow any guide with making a cwm port, some people will direct you to make cyanogenmod along with it because it follows along side it. I can't direct you to a guide but there should be lots you can check out, did you look at that link I showed you?
Trozzul said:
Download atuntu and run it, it should tell you. At least it has 1gig of ram.
Click to expand...
Click to collapse
I didn't really understand, what should i do after downloading the file for my cpu?! (i'm talking about the link that u gave to me)
Related
---------------------------------
Overview
---------------------------------
*RZrecovery*:
-=overclock settings=-
-=Arbitrary update.zip selection (with folders) (don't have to rename files to update.zip).=-
-=rom.tgz support (of course)=-
-=Unsigned update.zip support=-
-=ability to wipe system, data, boot, dalvik-cache, battery stats, cache-
-=No automatic backup when installing a rom.tgz=-
-=update.zip from folder support=-
-=Ability to install APK's, IMG's, ZIP's, TAR's, TGZ's from the same menu=-
-=Wipe battery statistics=-
-=Battery charging!=-
-=clockwork nandroid restore=-
-=Ability to root any ROM=-
-=12 predefined colors + random color selection=-
-=Rave mode: random color every time screen is redrawn=-
-=preinstall update.zip menu=-
-=battery status (charging status, temperature and charge level) display=-
-=android_secure nandroid / wipe support=-
-=Hold volume keys to scroll=-
-=Touch screen scrolling on some devices=-
-=Davlik bytecode verification disable/enable=-
---------------------------------
Background
---------------------------------
Last year I made RZRecovery for the original droid. It was a huge success, since then I have been asked to port to other devices. So here, about 1 year later, I have done just that. This will bring all the features of the old RZR plus a few new ones including the epic rom.tgz install format from the days of yore to any device. I have built this recovery specifically to handle all devices without the need for a recompile (except for Tegra2-based devices, they have to be recompiled because of some libc bugs). I have made img files for a few devices to start with:
---------------------------------
CONFIRMED
---------------------------------
HTC Thunderbolt
Samsung Nexus S
Samsung Nexus S 4G
Motorola Droid
HTC Incredible/Incredible S/ Incredible 2
HTC EVO 4G
---------------------------------
EXPERIMENTAL
---------------------------------
HTC MyTouch 4G/Slide
HTC Leo
HTC Dream/Sapphire/Magic
HTC Click/Tattoo
HTC Aria
HTC Wildfire
HTC Legend
HTC Desire/Desire CDMA/Desire S/ Desire HD
HTC Hero/Hero CDMA
Samsung Fascinate (need to find out where recovery is stored for mtd)
LG Optimus S
LG Optimus 1
LG Optimus V
LG Optimus 2X
Huawei Ideos
Huawei u8220/u8150
Motorola Cliq/ Cliq XT
Motorola Backflip
Motorola Atrix
PLEASE: IF ANY OF THSE EXPERIMENTAL BUILDS WORK, PLEASE POST AND LET ME KNOW SO THAT I MAY MOVE THEM TO THE CONFIRMED SECTION
In order to port RZR to anything, I need to know the base kernel address, the boot command line, the page size and the partition layout.
---------------------------------
SCREENSHOTS
---------------------------------
{
"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"
}
View all (in case forums limit the amount of images shown): http://rzdroid.com/ftp/recovery/screenshots/2.1.0/view.html
---------------------------------
CREDITS
---------------------------------
(without any of these individuals/organizations none of this could be possible)
CyanogenMod - for being completely open and having a huge database of device information
koush - for clockworkmod, where I got support for other partition types and filesystems
rbox - for repeat scroll and touch screen scrolling
cvpcs - for helping with anything I have ever asked
slayher - for showing me how to enable capacitive buttons on HTC devices
bekit - for showing me the bionic commits to get recovery built for tegra2's
trevorj - for the original battery charge knowledge
my wife - for giving me all the time I needed to get this done
all the testers for testing and encouragement!
---------------------------------
DOWNLOADS
---------------------------------
I will link img files for use with fastboot or flash_image and any applicable zips.
DISCLAIMER: Not that this needs to be said, but by downloading any of the files below, you take full responsibility for what happens with them. Make sure you have a way out if something goes wrong. The devices above are in the experimental section for a reason
EVO 4G: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-supersonic-update.zip
SAMSUNG FASCINATE: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-fascinate-update.zip
MYTOUCH 4G: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-glacier-update.zip
HTC THUNDERBOLT: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-mecha-update.zip
SAMSUNG NEXUS S: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-nexusS-update.zip
SAMSUNG NEXUS S 4G: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-ns4g-update.zip
HTC INCREDIBLE 2: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-vivow-update.zip
HTC INCREDIBLE S: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-vivo-update.zip
LG OPTIMUS S: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-thunderc-update.zip
LG OPTIMUS 1: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-thunderg-update.zip
LG OPTIMUS 2X: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-p990-update.zip
MOTOROLA DROID: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-sholes-update.zip
HTC LEO: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-leo-update.zip
HTC MAGIC: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-magic-update.zip
HTC DREAM: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-dream_sapphire-update.zip
HTC MARVEL: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-dream_sapphire-update.zip
HTC ACE: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-ace-update.zip
HTC DESIRE http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-bravo-update.zip
HTC DESIRE (CDMA): http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-bravoc-update.zip
HTC WILDFIRE: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-buzz-update.zip
HTC CLICK: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-click-update.zip
MyTouch Slide: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-espresso-update.zip
HTC HERO: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-hero-update.zip
HTC HERO (CDMA): http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-heroc-update.zip
HTC LEGEND: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-legend-update.zip
HTC ARIA: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-liberty-update.zip
MOTO CLIQ: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-morrison-update.zip
MOTO BACKFLIP: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-motus-update.zip
MOTO ATRIX: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-olympus-update.zip
HTC SAGA: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-saga-update.zip
HUAWEI U8150: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-u8150-update.zip
HUAWEI U8220: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-u8220-update.zip
HTC VISION: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-vision-update.zip
MOTO CLIQ XT: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-zeppelin-update.zip
HTC ZERO: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-zero-update.zip
---------------------------------
SOURCE
---------------------------------
https://github.com/raidzero/RZrecovery/tree/gingerbread
---------------------------------
WALKTHROUGH
---------------------------------
Volume up/down - scroll (can hold down to repeat scroll)
HTC - touch screen - scroll
Home - select
Back/Power - back
Code:
Main screen
Reboot android
Reboot recovery
Reboot bootloader
Power off
Wipe menu
Wipe all - wipe everything on the device except recovery
Wipe system (the ROM)
Wipe data (your applications and settings)
Wipe .android-secure (other applications and settings on sdcard)
Wipe boot (the main android kernel)
Wipe cache
Wipe battery stats
Wipe dalvik cache (cache of optimized dalvik executables)
Mount menu
Mount/unmount system (the ROM)
Mount/unmount data (apps and settings)
Mount/unmount sdcard
Enable/Disable USB Mass storage
Nandroid menu
Nandroid Backup
Perform backup
choose boot,data,android-secure,system to back up
Nandroid restore
Choose backup
choose boot,data,android-secure,system to restore
Clockwork nandroid restore
choose backup and immediately restore the whole thing
Install from sdcard
choose item to install:
APK, ZIP, IMG, (must end in rec.img or boot.img) .TAR, .TGZ
Preinstall Menu
Abort Install
Backup before install (make a quick backup of the device naming it preinstall-date-time)
Wipe data
Perform install
if(APK)
Abort APK install
Install to system
Install to data
Extras menu
Custom Colors
Random - randomly generated color, will save to sdcard
Any other color - will save to sdcard
Rave mode - a totally random color each time the screen is redrawn (every key press)
Show battery status - will show charge status, level, temperature if available
Recovery overclocking
Kernel will report the available CPU slots, pick one and it will set the max to your selection. Saves to sdcard
ROM tweaks
Disable OTA update downloads in ROM - will prevent android from downloading updates OTA
Activate Root access in ROM
Yes - roots the current ROM (still requires the superuser.apk from chainsdd)
No - does nothing
Dalvik bytecode tweaks
Disable bytecode verification
Enable bytecode verificaion
this deserves some explaining. saved the best for last :) In android, when executables are loaded, the dalvik VM will go
through each line of instructions and make sure it is valid, if it isn't (poorly written application) it will fix it to the best of its ability. This verification process takes time. Disabling this will speed up all the operations on the phone and might even save some RAM. If it doesn't work for you or causes apps to crash, re-enable the verifier here.
So please, if you want this for your device just post here and I will try to get it done for you
POSSIBLE CAVEATS
Update.zip status 2: this means the update.zip you re trying to flash has an outdated update-binary (META-INF/com/google/android/update-binary). Please replace this file in your zip with my version (from gingerbread) here: http://rzdroid.com/ftp/recovery/gingerbread/APIlevel3-update-binary
Update.zip status 7: This means the script is not compatible with the update-binary. This will most likely happen after you replace the update-binary in an outdated update.zip. The most common errors are that the mount and format commands now take extra arguments. you must pass the filesystem type like so:
OLD:
Code:
format("MTD", "system");
mount("MTD", "system", "/system");
NEW:
Code:
format("MTD", "yaffs2", "system");
mount ("MTD", "yaffs2", "system", "/system");
I have changed the API level to 2, to help alleviate some of these issues. It is still evel 3 but all level 2 update.zips should work fine.
Not the addition of the filesystem type. No idea why they changed this, seems like since it now uses recovery.fstab that this info could simply be figured out. or maybe I will implement a method of checking for status 7 and possibly telling it the filesystem information myself. Either way, this info will get you rolling now.
Can you make one for the lg optimus gt540 dont no it this helps
Partitions
dev: size erasesize name
mtd0: 00500000 00020000 "boot"
mtd1: 04000000 00020000 "cache"
mtd2: 00500000 00020000 "recovery"
mtd3: 00060000 00020000 "splash"
mtd4: 0f500000 00020000 "system"
mtd5: 002c0000 00020000 "lgdrm"
mtd6: 08a80000 00020000 "userdata"
mtd7: 00100000 00020000 "misc"
mtd8: 00080000 00020000 "usd"
mtd9: 005a0000 00020000 "pkg"
mtd10: 1cfc0000 00020000 ""
Cmdline
mem=214M console=ttyMSM2,115200n8 androidboot.hardware=swift uart.mode=arm11_uart_disable crash=off
Sent from my LG GT540 Swift using xda premium
eoghan2t7 said:
Can you make one for the lg optimus gt540 dont no it this helps
Partitions
dev: size erasesize name
mtd0: 00500000 00020000 "boot"
mtd1: 04000000 00020000 "cache"
mtd2: 00500000 00020000 "recovery"
mtd3: 00060000 00020000 "splash"
mtd4: 0f500000 00020000 "system"
mtd5: 002c0000 00020000 "lgdrm"
mtd6: 08a80000 00020000 "userdata"
mtd7: 00100000 00020000 "misc"
mtd8: 00080000 00020000 "usd"
mtd9: 005a0000 00020000 "pkg"
mtd10: 1cfc0000 00020000 ""
Cmdline
mem=214M console=ttyMSM2,115200n8 androidboot.hardware=swift uart.mode=arm11_uart_disable crash=off
Sent from my LG GT540 Swift using xda premium
Click to expand...
Click to collapse
The only other thing I am missing is the pagesize and base address. Is there a Cyanogenmod for it? thats the quickest way to get all that info
raidzero said:
The only other thing I am missing is the pagesize and base address. Is there a Cyanogenmod for it? thats the quickest way to get all that info
Click to expand...
Click to collapse
There is kernel source would that help? Thanks
Edit: no cm repo but heres the kernel source:
https://github.com/wingrime/android_kernel_swift_lg/
Sent from my LG GT540 Swift using xda premium
About to try this
nobody calls my EVO a fizzle and gets away with it!!
Well mate any luck?
Sent from my LG GT540 Swift using xda premium
with some research I have found the base address for that device to be
0x00200000
I will make an img for it tonight. Do you have google talk? I will need to experiment to find the correct pagesize for the device.
raidzero said:
with some research I have found the base address for that device to be
0x00200000
I will make an img for it tonight. Do you have google talk? I will need to experiment to find the correct pagesize for the device.
Click to expand...
Click to collapse
Yeah i do ill pm you the address
Sent from my LG GT540 Swift using xda premium
For wildfire s??
Would you mind bringing this to the HTC Wildfire S?????
And as for the info you need.......there is an unofficial port of cm7
here
HD2
i like what u have here...if u can i hope i can use it on HD2
THX
Can it be made for Dell streak 5 PLease PLease..................
anyone try this on NS4G yet?
TheBurgh said:
anyone try this on NS4G yet?
Click to expand...
Click to collapse
ns4g is the phone I have. it works great
Would you mind making this available to HTC G1 please?
Thanks in advance.
ahmadns said:
Would you mind bringing this to the HTC Wildfire S?????
And as for the info you need.......there is an unofficial port of cm7
here
Click to expand...
Click to collapse
marvel? http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-marvel-update.zip
BeenAndroidized said:
Would you mind making this available to HTC G1 please?
Thanks in advance.
Click to expand...
Click to collapse
dream & magic:
http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-dream-update.zip
http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-magic-update.zip
(they are the exact same thing)
raidzero said:
dream & magic:
http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-dream-update.zip
http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-magic-update.zip
(they are the exact same thing)
Click to expand...
Click to collapse
Thank you. I will download it when I have a chance.
EDIT: OK, since there is no instruction on this. I am assuming that I flash it through my current recovery from SD card. Is that right?
BeenAndroidized said:
Thank you. I will download it when I have a chance.
EDIT: OK, since there is no instruction on this. I am assuming that I flash it through my current recovery from SD card. Is that right?
Click to expand...
Click to collapse
that is correct. flash it like any other update.zip please let me know if it boots and how it works!
eoghan2t7 said:
Yeah i do ill pm you the address
Sent from my LG GT540 Swift using xda premium
Click to expand...
Click to collapse
try this: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-swift-update.zip
let me know if it boots and how it runs
seaman2k said:
i like what u have here...if u can i hope i can use it on HD2
THX
Click to expand...
Click to collapse
htc leo, right? http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-leo-update.zip
same story as the rest...
NO MORE LINUX OR CYGWIN NEEDED!!!
...now it`s easy as 123...
Boot.img structure should be the same as shown here http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
1. For MTK (chineese) phones - use MTK_unpack.bat (MTK_pack.bat)
2. For android standart phones - use STD_unpack.bat (STD_pack.bat)
To unpack: - drag boot.img (recovery.img) to unpack.bat ("unpack.bat boot.img" in command line)
- will be created "boot" ("recovery") folder with unpacked ramdisk inside - you can make changes and:
To pack back: - drag output folder ("boot" or "recovery") to pack.bat
- will be created new_image.img
I did this successfully on Lenovo A789 MTK6577 - it 100% works fine.
I`ve repack boot and recovery for phones listed below - but have no possibility to check out on the phone - so any volunteers appreciated...
- Samsung Galaxy S i9001, Galaxy III, Note II
- HTC Desire V sense 4
Not work with:
- Samsung Galaxy Note I, Tab I
But be careful - make backup and be ready to flash bricked phone with your flash utility.
UPD. v4 - win8 x64 support
Yeoh michfood, good job man...
i've been hunting up & down for something similar so that fellow xda member will be able to port compatible MT65xx cwmr to their device in Windows without the need of cygwin... :laugh:
Would you like to KANG my Android Kitchen plugins script here... :fingers-crossed:
yuweng said:
Yeoh michfood, good job man...
i've been hunting up & down for something similar so that fellow xda member will be able to port compatible MT65xx cwmr to their device in Windows without the need of cygwin... :laugh:
Would you like to KANG my Android Kitchen plugins script here... :fingers-crossed:
Click to expand...
Click to collapse
glad to hear smth like that :victory:
hope it`ll helps to make some things easily
but TWRP is much better for me for a while
and I`ve my own kitchen to work around with apks and jars and all firmware at all - odex and deodex them, but I didn`t translate it to english yet http://forum.china-iphone.ru/viewtopic.php?f=31&t=19708
Wow, i didn't know you are a
Master Shifu...
Hope you do get it translated to english so that the world will benefit from your hard work too...
yuweng said:
Wow, i didn't know you are a
Master Shifu...
Hope you do get it translated to english so that the world will benefit from your hard work too...
Click to expand...
Click to collapse
i`m just modest user of chineese phone - and while I`ve making it better - I`ve made some scripts - a lot of things i`ve got from this forum
wow... I`m really sorry - yesterday I forgot to attach STD bat files in archive - so please - reload files!
Thanks for the tool, it's compact and fast to work with.
Now at my first attempt to decompile it doesn't find some file and the ramdisk folder inside boot remains empty:
Code:
[total hits/matching patterns/non-matching patterns]
[298/1/0] bin\off2.txt
1 files checked, 1 changed.
- pagesize - 2048
- size of image - 7232000 byte
- ram_disk offset - 3272704
- split kernel...
3268608 bytes copied.
- extract ram_disk.gz...
3959296 bytes copied.
- unpack ram_disk.gz...
- unpack ram_disk.cpio...
[B]The system cannot find the file specified.[/B]
- copy source F:\Porting\ALL_phones_Boot_Recovery_repack_util_for_WINDOWS\boot.img to unpacked folder (to keep source image)...
Press any key to continue . . .
Smth. went wrong... can You give me your boot?
I have to say one thing - not ALL boot can be unpacked - some phones have they own boot structure - it is not correspond to this: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images - so my utility cannot process them.
For example it is Samsung Note (1) Samsung Galaxy Tab (1)... maybe other.
ps _polimorph_ - by the way... I have an interesting idea.
after unpacking gz archive - You should receive a file without extension in /boot folder - usually it is named "ram_disk" - and after that, my script uses it as source cpio archive to extract.
BUT! if in your boot this file was named "rmdisk" for example - script will stop after gz extraction - because were is no right-named cpio file to decompress.
this is easy to check
Works on I9001, but not on I9003.
Alex93917
the structure of stock ROM for i9003 is:
and (!) my utility works fine with normalboot.img - but not (!) with boot.bin - it`s different part of ROM
Now Allowed to Post
michfood said:
NO MORE LINUX OR CYGWIN NEEDED!!!
...now it`s easy as 123...
Boot.img structure should be the same as shown here http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
1. For MTK (chineese) phones - use MTK_unpack.bat (MTK_pack.bat)
2. For android standart phones - use STD_unpack.bat (STD_pack.bat)
To unpack: - drag boot.img (recovery.img) to unpack.bat ("unpack.bat boot.img" in command line)
- will be created "boot" ("recovery") folder with unpacked ramdisk inside - you can make changes and:
To pack back: - drag output folder ("boot" or "recovery") to pack.bat
- will be created new_image.img
I did this successfully on Lenovo A789 MTK6577 - it 100% works fine.
I`ve repack boot and recovery for phones listed below - but have no possibility to check out on the phone - so any volunteers appreciated...
- Samsung Galaxy S i9001, Galaxy III, Note II
- HTC Desire V sense 4
Not work with:
- Samsung Galaxy Note I, Tab I
But be careful - make backup and be ready to flash bricked phone with your flash utility.
UPD. v2 - fixed some bags with STD unpack/pack
Click to expand...
Click to collapse
Hi michfood!
A massive thanks for this fantastic recovery and for all your help getting it to work on my MTK6575 GB v2.3.6 device :angel:
I was not allowed to post here earlier because I was a noob but i am sure you have helped many people without knowing it. Please Please keep up the great work us noob's would be toltally lost without you. :good:
Regards bigrammy.
uboot & nvram backup mtd is it possible?
Hi michfood,
Could I call upon you for help once again
TWRP is without any doubt the best most user friendly recovery :good:
It works flawlessly on my Zopo zp300+ MT6577 Android 4.0.4 (ICS) :good:
With the help you provided me already TWRP also works great on my HDC A9300 MT6575 Android v2.3.6 (GB)
I was wondering if I we could get TWRP to backup uboot & nvram on the mtd version like it does on emmc version
I am unsure of the difficulty in doing this or is it a matter of simply editing a few lines of text.
Could you please advice once again which file's script's I need to edit etc
Here are the mtd partitions again from my device for your info.
adb shell
$ cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00020000 "preloader"
mtd1: 000c0000 00020000 "dsp_bl"
mtd2: 00300000 00020000 "nvram"
mtd3: 00020000 00020000 "seccnfg"
mtd4: 00060000 00020000 "uboot"
mtd5: 00500000 00020000 "boot"
mtd6: 00500000 00020000 "recovery"
mtd7: 00120000 00020000 "secstatic"
mtd8: 00060000 00020000 "misc"
mtd9: 00300000 00020000 "logo"
mtd10: 000a0000 00020000 "expdb"
mtd11: 12700000 00020000 "system"
mtd12: 03c00000 00020000 "cache"
mtd13: 07f20000 00020000 "userdata"
Hope you can help :fingers-crossed:
Thanks. bigrammy
I suppose it`s better to ask such question in TWRP thread.
Possibly You can achieve that with changing smth. like vold.fstab.
But possibly not - because it may need to change source codes and recompile again whole recovery binary
michfood said:
I suppose it`s better to ask such question in TWRP thread.
Possibly You can achieve that with changing smth. like vold.fstab.
But possibly not - because it may need to change source codes and recompile again whole recovery binary
Click to expand...
Click to collapse
Thanks for your reply :good:
So not quite so easy then I thought it maybe a bit more complicated but I had to ask :laugh:
I will post the question over on the TWRP thread as you suggest to see if anyone there can help :fingers-crossed:
Thanks again michfood for your help & hard work on this tool :angel:
Regards. bigrammy
bigrammy said:
but I had to ask
Click to expand...
Click to collapse
- no question, no answer
U understand that I mean... in Russia there`s a good saying - "follow to Kiev by tongue" - means do not shy to ask - it`s much better to be "know-hothing"
Experts,
Can you give any idea on Xperia boot structures!
Pls!
And would this work on Xperia 2011 series!
If not,why?
Sent from my MT11i using xda premium
I have problems to repack recovery.img for my Tegra3 device.
The script always say : access denied, pack rmdisk to cpio..., after this file not found , error unsupported page size0,....
Last try was simply repack the successfully unpacked folder. but fails
Any Idea ?
Best regards
cm
cmoegele said:
I have problems to repack recovery.img for my Tegra3 device.
The script always say : access denied, pack rmdisk to cpio..., after this file not found , error unsupported page size0,....
Last try was simply repack the successfully unpacked folder. but fails
Any Idea ?
Best regards
cm
Click to expand...
Click to collapse
which OS You use to? I hope it`s not win8? There are known problems with admin`s permissions
Ghostfreak NB said:
Experts,
Can you give any idea on Xperia boot structures!
Pls!
And would this work on Xperia 2011 series!
If not,why?
Click to expand...
Click to collapse
I haven`t, have You?
I`ve no answer because I never repacked Xperia boots. To do so, at first I need a Xperia boot.img
michfood said:
which OS You use to? I hope it`s not win8? There are known problems with admin`s permissions
Click to expand...
Click to collapse
Windows 7 locks the rmdisk folder so the script will fail.
Exec: %~dp0bin\chmod og=xr rmdisk
Then Cd rmdisk will give:
Access is denied.
- pack rmdisk to cpio...
/usr/bin/find: `./rmdisk': Permission denied
28482 blocks
The system cannot find the file specified.
- pack rmdisk.cpio to gzip...
- make new image...
The system cannot find the file ../pagesize.txt
- pagesize
error: unsupported page size 0
The system cannot find the file specified.
- done.
Press any key to continue . . .
Just picked one of these up from Walmart. So far, not a bad tablet for the price. Their website is reporting it will have a KitKat update on July 15, 2014.
Rooting instructions for Nextbook 8 Quad Core (NX785QC8G).
1. Connect to PC via USB, enable USB debugging on tablet, then use Cydia Impactor to create ADB device Driver. (USB>Driver Scan>Create Driver).
2. While connected USB, use Kingo after device driver is installed to complete rooting.
Please post any Rom/Mod information on this thread. There's really no other resource available currently for this tab on XDA.
mjj777 said:
Just picked one of these up from Walmart. So far, not a bad tablet for the price. Their website is reporting it will have a KitKat update on July 15, 2014.
Rooting instructions for Nextbook 8 Quad Core (NX785QC8G).
1. Connect to PC via USB, enable USB debugging on tablet, then use Cydia Impactor to create ADB device Driver. (USB>Driver Scan>Create Driver).
2. While connected USB, use Kingo after device driver is installed to complete rooting.
Please post any Rom/Mod information on this thread. There's really no other resource available currently for this tab on XDA.
Click to expand...
Click to collapse
Thanks for this! I just picked up this tablet today.
mjj777 said:
Please post any Rom/Mod information on this thread. There's really no other resource available currently for this tab on XDA.
Click to expand...
Click to collapse
Ok, let us have a deeper look into the firmware.
Download a Terminal Emulator from Play Store. Boot the tab fresh and type:
Code:
su
dmesg >/mnt/sdcard/dmesg.txt
cat proc/cmdline >/mnt/sdcard/cmdline.txt
cat proc/mtd > /mnt/sdcard/mtd.txt
dd if=/dev/mtd/mtd1 of=/sdcard/kernel.img bs=4096
dd if=/dev/mtd/mtd2 of=/sdcard/boot.img bs=4096
dd if=/dev/mtd/mtd3 of=/sdcard/recovery.img bs=4096
dd if=/dev/mtd/mtd8 of=/sdcard/system.img bs=4096
Zip the files, upload them to a file-hoster und post the link here.
- Oma -
Oma7144 said:
Ok, let us have a deeper look into the firmware.
Download a Terminal Emulator from Play Store. Boot the tab fresh and type:
Code:
su
dmesg >/mnt/sdcard/dmesg.txt
cat proc/cmdline >/mnt/sdcard/cmdline.txt
cat proc/mtd > /mnt/sdcard/mtd.txt
dd if=/dev/mtd/mtd1 of=/sdcard/kernel.img bs=4096
dd if=/dev/mtd/mtd2 of=/sdcard/boot.img bs=4096
dd if=/dev/mtd/mtd3 of=/sdcard/recovery.img bs=4096
dd if=/dev/mtd/mtd8 of=/sdcard/system.img bs=4096
Zip the files, upload them to a file-hoster und post the link here.
- Oma -
Click to expand...
Click to collapse
https://www.dropbox.com/s/2ealpbnxribauqr/nextbook files.zip
Ok, this seems to be a generation 2 loader build. System is on /mtd9.
dev: size erasesize name
mtd0: 00400000 00004000 "misc"
mtd1: 00c00000 00004000 "kernel"
mtd2: 00c00000 00004000 "boot"
mtd3: 02000000 00004000 "recovery"
mtd4: 04000000 00004000 "backup"
mtd5: 08000000 00004000 "cache"
mtd6: 3fc00000 00004000 "userdata"
mtd7: 00400000 00004000 "metadata"
mtd8: 00400000 00004000 "kpanic"
mtd9: 60000000 00004000 "system"
mtd10: 130c00000 00004000 "user"
Click to expand...
Click to collapse
So, pls dump system.img again:
dd if=/dev/mtd/mtd9 of=/sdcard/system.img bs=4096
Click to expand...
Click to collapse
- Oma -
Oma7144 said:
Ok, let us have a deeper look into the firmware.
Download a Terminal Emulator from Play Store. Boot the tab fresh and type:
Code:
su
dmesg >/mnt/sdcard/dmesg.txt
cat proc/cmdline >/mnt/sdcard/cmdline.txt
cat proc/mtd > /mnt/sdcard/mtd.txt
dd if=/dev/mtd/mtd1 of=/sdcard/kernel.img bs=4096
dd if=/dev/mtd/mtd2 of=/sdcard/boot.img bs=4096
dd if=/dev/mtd/mtd3 of=/sdcard/recovery.img bs=4096
dd if=/dev/mtd/mtd8 of=/sdcard/system.img bs=4096
Zip the files, upload them to a file-hoster und post the link here.
- Oma -
Click to expand...
Click to collapse
Oma7144 said:
Ok, this seems to be a generation 2 loader build. System is on /mtd9.
So, pls dump system.img again:
- Oma -
Click to expand...
Click to collapse
It tells me permission denied...even after a fresh reboot.
Type su first.
- Oma -
Oma7144 said:
Type su first.
- Oma -
Click to expand...
Click to collapse
It's working to upload this huge file to dropbox. It'll be available shortly.
---------- Post added at 10:17 PM ---------- Previous post was at 10:10 PM ----------
Oma7144 said:
Type su first.
- Oma -
Click to expand...
Click to collapse
https://www.dropbox.com/sh/9xqb49glypcwy7x/AADOiH0tnPZqrIgFLhIgH6BJa
Can you pls check to dropbox link?
- Oma -
Oma7144 said:
Can you pls check to dropbox link?
- Oma -
Click to expand...
Click to collapse
Sorry about that! here ya go: https://www.dropbox.com/s/uppez7giz0szlc8/system.zip
Ok, well done
Build:
ro.build.display.id=V3.0.8.JDQ39.eng.root.20140401.231924
ro.product.model=NX785QC8G
ro.product.brand=Nextbook
ro.product.name=M865FD
ro.product.device=NXM865FD
ro.rksdk.version=RK31_ANDROID4.2.2-SDK-v1.04.00
ro.rk.bt_enable=false
ro.vendor.name=YFMID
Kernel: 3.0.36+ ([email protected]) (gcc version 4.4.3 (GCC) ) #570 SMP PREEMPT Tue Apr 1 23:48:15 CST 2014
Wifi: Realtek 8188EU USB WiFi driver (Powered by Rockchip,Ver 3.50.WFD) init.
No BT, right?
Are the nextbook apps in the system needed for some reason?
- Oma -
Oma7144 said:
Ok, well done
Build:
ro.build.display.id=V3.0.8.JDQ39.eng.root.20140401.231924
ro.product.model=NX785QC8G
ro.product.brand=Nextbook
ro.product.name=M865FD
ro.product.device=NXM865FD
ro.rksdk.version=RK31_ANDROID4.2.2-SDK-v1.04.00
ro.rk.bt_enable=false
ro.vendor.name=YFMID
Kernel: 3.0.36+ (br[email protected]) (gcc version 4.4.3 (GCC) ) #570 SMP PREEMPT Tue Apr 1 23:48:15 CST 2014
Wifi: Realtek 8188EU USB WiFi driver (Powered by Rockchip,Ver 3.50.WFD) init.
No BT, right?
Are the nextbook apps in the system needed for some reason?
- Oma -
Click to expand...
Click to collapse
Correct, no BT. I've frozen or removed (with Titanium) most of the Nextbook apps.
Nextbook 8 QC by Oma JB 4.2.2 build v1.0
– stock 4.4.0 recovery, CWM 6.0.3.1 recovery
– system ext4
– kernel bryan #570
– internal storage 2 GB
– Multi-User
– ethernet support
– init.d support
– gameloft compatible
– USB-Hub enabled
– gamepad compatible (PS2, XBox, …)
– kernel modules (cifs, tun, lan, serial, audio)
– latest hosts, su, su-binary, busybox
– Reboot Menue, sEFix, FX Sound
– Dateimanager HD (Root)
– Nova Launcher
Instructions are included in the download pack.
Please report any problem with this firmware, I can't verify this custom firmware
works as I don't have the tablet to fully test the custom firmware.
Be aware: it is your own risk!
- Oma -
Oma7144 said:
Nextbook 8 QC by Oma JB 4.2.2 build v1.0
– stock 4.4.0 recovery, CWM 6.0.3.1 recovery
– system ext4
– kernel bryan #570
– internal storage 2 GB
– Multi-User
– ethernet support
– init.d support
– gameloft compatible
– USB-Hub enabled
– gamepad compatible (PS2, XBox, …)
– kernel modules (cifs, tun, lan, serial, audio)
– latest hosts, su, su-binary, busybox
– Reboot Menue, sEFix, FX Sound
– Dateimanager HD (Root)
– Nova Launcher
Instructions are included in the download pack.
Please report any problem with this firmware, I can't verify this custom firmware
works as I don't have the tablet to fully test the custom firmware.
Be aware: it is your own risk!
- Oma -
Click to expand...
Click to collapse
Thanks so much! I"m downloading it now. I'll report back.
I can't get it into flash mode. I killed the battery trying repeatedly. It's now charging. WIll try again after it charges back up.
Oma7144 said:
Nextbook 8 QC by Oma JB 4.2.2 build v1.0
– stock 4.4.0 recovery, CWM 6.0.3.1 recovery
– system ext4
– kernel bryan #570
– internal storage 2 GB
– Multi-User
– ethernet support
– init.d support
– gameloft compatible
– USB-Hub enabled
– gamepad compatible (PS2, XBox, …)
– kernel modules (cifs, tun, lan, serial, audio)
– latest hosts, su, su-binary, busybox
– Reboot Menue, sEFix, FX Sound
– Dateimanager HD (Root)
– Nova Launcher
Instructions are included in the download pack.
Please report any problem with this firmware, I can't verify this custom firmware
works as I don't have the tablet to fully test the custom firmware.
Be aware: it is your own risk!
- Oma -
Click to expand...
Click to collapse
I got it! Now, I'm going to play around with it! Thank you so much!
There is a column with 3 dots (Address, Name, Path, ...), click the empty box.
- Oma -
Oma7144 said:
There is a column with 3 dots (Address, Name, Path, ...), click the empty box.
- Oma -
Click to expand...
Click to collapse
Thank you! Yes, I finally tried that and it worked! I'm so happy!
Can we start a forum on here for this tablet to encourage further development?
This ROM works fantastic! It has worked out the kinks in the Nextbook firmware completely (not saving personalization settings). I'm digg'n it, Oma!
---------- Post added at 05:20 PM ---------- Previous post was at 05:15 PM ----------
http://imgur.com/tbcfWzf
Sent from my Nextbook 8 using XDA Free mobile app
zombiegirl2010 said:
Can we start a forum on here for this tablet to encourage further development?
Click to expand...
Click to collapse
Sure.
- Oma -
As many of you are aware, flashing roms to our phone comes with risk. That risk is dimished by the availability of an RUU for our phone.
I have made this available as a standalone APP (.exe) for PC use as well as a SINGLE zip file for SD card loading.
This is for s-off users only. I repeat...s-off only.
This WILL wipe your phone (internal memory). IF you are able...backup data prior to using this. This works EXACTLY like an RUU for s-off users. Two options exist for using this zip. This will land you on STOCK yummy lollipop 5.0.1 pre-rooted with stock recovery.
NOTE...This is a COMPLETE single file solution. No stickers file needed.
IF you get PU failed for data partition you need to factory reset from hboot and re-run the RUU. This means the RUU could not write to your data partition like it should have (size is wrong or encrypted etc)...
if you ever end up on the android 4 ! screen simply fastboot flash the hboot.img to clear the error state. Our phones go into this protect mode when a partition fails to update and it will NOT clear until it successfully flashes a zip.
Please download and flash the L hboot from here.
- https://www.androidfilehost.com/?fid=95916177934537709
.
Option 1
Rename file to 0P6BIMG.zip and Copy 0P6BIMG.zip to root of a physical SD. No exfat! No internal storage!
Reboot phone to bootloader and follow prompts once RUU is detected by phone.
Option 2 (App/EXE)
Download file. Double click. Wait a couple minutes for it to extract and it will install supporting files automatically. Then follow the onscreen prompts to flash RUU.
## expect a good 5 minute plus first boot!
You CAN use the app flashify (free on google play) to flash custom recovery of your chosing.
Optional If you wish to flash a custom recovery before leaving RUU mode you can. This is helpful if you have relocked for any reason as you CAN flash a recovery using this method while locked (since s-off). Download the ruuM8TWRP_2_8_7.zip below and place it in your working fastboot/adb directory. Once in place, issue the following command.
fastboot flash zip ruuM8_TWRP_2_8_7L.zip
##example output
Once completed you can issue the command "fastboot reboot-bootloader" to return to hboot so you can enter recovery.
Many thanks to @Sneakyghost for sharing the fuu for the cause!!
Downloads Do NOT mirror these elsewhere.
RUU links
4.17.605.9 (Stagefright patched)
APP/EXE version
- https://www.androidfilehost.com/?fid=24052804347812372
Standalone zip
- https://www.androidfilehost.com/?fid=24052804347812371
4.17.605.5
APP/EXE version
- https://www.androidfilehost.com/?fid=95916177934538714
md5 c846d8a3ba6932eccad5010a59727ba4
Standalone zip
- https://www.androidfilehost.com/?fid=95916177934538677
md5 87c598422e10657e5b4c9794e6468ee7
RUU Mode TWRP 2.8.7.0 TWRP that will flash while in RUU mode (great for phones that have bootloader locked)
- https://www.androidfilehost.com/?fid=24052804347812392
HTC backup app (highly recommend this gem)
- http://www.androidfilehost.com/?fid=23329332407589902
md5 b7ec08c021b5fb8b1b86a0ab3535c1dd
Tweaks zip to unlock tether/disable max password wipe/enable music channel
- https://www.androidfilehost.com/?fid=24052804347801368
NOTE partition changes here...
[email protected]_m8wl:/ # cat /proc/emmc
cat /proc/emmc
dev: size erasesize name
mmcblk0p1: 00100000 00000200 "sbl1"
mmcblk0p2: 076f7c00 00000200 "pg1fs"
mmcblk0p3: 00004000 00000200 "board_info"
mmcblk0p4: 00800000 00000200 "reserve_1"
mmcblk0p5: 00040000 00000200 "mfg"
mmcblk0p6: 017afc00 00000200 "pg2fs"
mmcblk0p7: 00040000 00000200 "sbl1_update"
mmcblk0p8: 00040000 00000200 "rpm"
mmcblk0p9: 00200000 00000200 "tz"
mmcblk0p10: 00008000 00000200 "sdi"
mmcblk0p11: 00400000 00000200 "hboot"
mmcblk0p12: 00500000 00000200 "sp1"
mmcblk0p13: 00100000 00000200 "wifi"
mmcblk0p14: 00008000 00000200 "ddr"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p17: 00500000 00000200 "wcnss"
mmcblk0p18: 00800000 00000200 "radio_config"
mmcblk0p19: 00180000 00000200 "fsg"
mmcblk0p20: 04b00400 00000200 "radio"
mmcblk0p21: 00400000 00000200 "tool_diag"
mmcblk0p22: 03200000 00000200 "custdata"
mmcblk0p23: 00effc00 00000200 "reserve_2"
mmcblk0p24: 00100000 00000200 "misc"
mmcblk0p25: 00180000 00000200 "modem_st1"
mmcblk0p26: 00180000 00000200 "modem_st2"
mmcblk0p27: 01400000 00000200 "fataldevlog"
mmcblk0p28: 00001000 00000200 "debug_config"
mmcblk0p29: 00040000 00000200 "pdata"
mmcblk0p30: 00004000 00000200 "control"
mmcblk0p31: 00140400 00000200 "local"
mmcblk0p32: 00010000 00000200 "extra"
mmcblk0p33: 00100000 00000200 "cdma_record"
mmcblk0p34: 00000400 00000200 "fsc"
mmcblk0p35: 00002000 00000200 "ssd"
mmcblk0p36: 00040000 00000200 "skylink"
mmcblk0p37: 01900000 00000200 "carrier"
mmcblk0p38: 00040000 00000200 "sensor_hub"
mmcblk0p39: 01e00000 00000200 "devlog"
mmcblk0p40: 00002800 00000200 "cir_img"
mmcblk0p41: 00a00000 00000200 "vzw_quality"
mmcblk0p42: 00a00000 00000200 "vzw_logger"
mmcblk0p43: 019e6000 00000200 "reserve"
mmcblk0p44: 01000000 00000200 "boot"
mmcblk0p45: 01800000 00000200 "recovery"
mmcblk0p46: 05800000 00000200 "reserve_3"
mmcblk0p47: a8000000 00000200 "system"
mmcblk0p48: 40000000 00000200 "cache"
mmcblk0p49: 30000000 00000200 "userdata"
absolutely amazing job!
Hats off for doing it so fast!Incredibly grateful to you!!A million thanks!!
Hey mate,
I have further refined the FUU packages to include the VCRedist, which usually comes with HTC Syncmanager and is required by ARUWizard.
I also have this saved into WinRAR profiles for my different FUU's and RUU repacks and whatnot.
Just let me know if you want profile exports for your FUU and the resource folders to go along with them.
You can have it.
You know where to find me
Is it just me or are there no files for flashing or adb? I might also be an idiot, so I apologize. I see a TWRP zip and an apk for HTC backup.
rhodyvik said:
Is it just me or are there no files for flashing or adb? I might also be an idiot, so I apologize. I see a TWRP zip and an apk for HTC backup.
Click to expand...
Click to collapse
We are just waiting on AFH right now.... gotta love it...
dottat said:
We are just waiting on AFH right now.... gotta love it...
Click to expand...
Click to collapse
i can hear it....if you listen...u can actually HEAR him working/typing away! Dottat rocks!
<bows and worships>
dottat said:
We are just waiting on AFH right now.... gotta love it...
Click to expand...
Click to collapse
Thank you for letting me know I'm not losing my vision.
rhodyvik said:
Thank you for letting me know I'm not losing my vision.
Click to expand...
Click to collapse
RUU zip is up... along with updated TWRP zip. Last thing I'm waiting on is the EXE version to upload.
Little bit of a noob question, but flashing this RUU from any previous android version should work, right?
No need to go to 4.4.4 and then upgrade?
dottat said:
RUU zip is up... along with updated TWRP zip. Last thing I'm waiting on is the EXE version to upload.
Click to expand...
Click to collapse
Dude youre the best!
dottat said:
RUU zip is up... along with updated TWRP zip. Last thing I'm waiting on is the EXE version to upload.
Click to expand...
Click to collapse
I used your FW from here...what's the difference? This one worked beautifully. I changed it to 0P6BIMG and went through hboot. Color me confused. Rooted, S-Off, ViperOneM8 4.3.0 and CM11 with MultiROM. Please tell me the difference and if I'm good?! Thanks man.
http://forum.xda-developers.com/showthread.php?t=2723159
rhodyvik said:
I used your FW from here...what's the difference? This one worked beautifully. I changed it to 0P6BIMG and went through hboot. Color me confused. Rooted, S-Off, ViperOneM8 4.3.0 and CM11 with MultiROM. Please tell me the difference and if I'm good?! Thanks man.
http://forum.xda-developers.com/showthread.php?t=2723159
Click to expand...
Click to collapse
Since you are custom rom.. you are good.. RUU is the whole stock rom/firmware as a single file..
dottat said:
Since you are custom rom.. you are good.. RUU is the whole stock rom/firmware as a single file..
Click to expand...
Click to collapse
Perfect my dude...thank you for the clarification. I'm in the midst of another huge snowstorm (this one no one predicted) so I get to play with my phone for the rest of the day! No more work ?
Are there new radios with this RUU, too?
syphix said:
Are there new radios with this RUU, too?
Click to expand...
Click to collapse
Yes.. new radios.
Excuse my lack of knowledge but I haven't used an update file like this through TWRP. I've used hboot plenty but whats the difference? And if I choose to use the TWRP route do I keep my data and custom rom that is installed.
rhodyvik said:
I used your FW from here...what's the difference? This one worked beautifully. I changed it to 0P6BIMG and went through hboot. Color me confused. Rooted, S-Off, ViperOneM8 4.3.0 and CM11 with MultiROM. Please tell me the difference and if I'm good?! Thanks man.
http://forum.xda-developers.com/showthread.php?t=2723159
Click to expand...
Click to collapse
Can I use the zip in the link to flash to Lollipop while staying on ViperOne 4.3.0 or does yours only work because you have CM11 too?
Sorry if this takes slightly off on a tangent, but what's the difference between this thread and Tigerstown's?
Is this the full "stock" ROM that's rooted, etc.?
WorldOfJohnboy said:
Sorry if this takes slightly off on a tangent, but what's the difference between this thread and Tigerstown's?
Is this the full "stock" ROM that's rooted, etc.?
Click to expand...
Click to collapse
Yes.. this is the FULL firmware/rom rom update utility. the firmware i posted in tigerstown has zero OS files.
ROM build is now up links are at the bottom,
This is for the HS_Q6_MB_V1.0 revision board,
ZMA_12_MB_V1.0 revision boards see the last post on thread for a working incomplete modded firmware.
Personally rebuilt stock OS installed on the R11 max china phone firmware with all mods done by myself apart from the optional modified boot.img
------------------------DISCLAIMER------------------------
Flash this Firmware at your own risk i am in no way responsible for any damage that can occurr flashing your MTK device with flash tools, such as
•Hardbricked devices
•Soft Bricked devices
•Lost imei or baseband issues
or anything else for that matter, you are solely responsible for the actions you make when flashing this firmware, however following instructions below you shouldnt have a problem with the device and you can enjoy your new updated R11 max Firmware.
______________________________________
R11 MAX DEVICE INFO
______________________________________
Android OS : 4.4.2 Kit Kat SDK:19
Kernel Version: 3.4.67
ROM ispre-rooted with SU & Busy Box binaries which will remain after factory reset.
File System: UBIFS
BaseBand CPU: MT6572_S00
BaseBand CPU Secure Version: FF
BaseBand CPU Bootloader Version: 01
INT RAM: 128KB SDRAM
EXT RAM: 512MB DRAM
NAND: (4GB + 4096MB) [HYNIX] - H9DA4GH4JJAMCR_4EM
Boot Style: NAND BOOT
Size: 0×20000000 [0.500GB]
BlockSize: 2048 SpareSize: 64 BMT blocks: 80
_____________________________________
REMOVED
_____________________________________
• Cooee launcher ( spyware )
• Marshmallow game ( adware )
• Browser
• calander
• gallery
• camera
• music fx
• exchange2
• email
• Volume control
• framework.jar
• calculator
• music player
• File manager
• system/vendor apps/FBlite/Whatsapp
• Stock boot animation
• Stock shutdown animation
• Stock start tone
• Stock Shutdown tone
• Stock UI sounds
• Stock Notifications sounds
• Stock Ringtone Sounds
• Stock Boot Logo
• Libs from removed apps
• framework from removed apps
• -res from removed apps
• Build.prop (Edited)
• Test Keys (they should be release)
• Wallpapers
• Live wallpapers
• Network Restriction lock (network Lock )
• Modem (connectivity & imei issues )
Plus alot more crap removed that i cant remember right now....
___________________________________________
ADDED OR REPLACED
___________________________________________
• SU Binary pre installed to system, will remain even after factory reset.
• BUSY BOX 1.28 binary pre installed to system, will remain even after factory reset.
• Nova Launcher as new stock launcher
• Opera mini browser (fast with inbuilt DL manager
• Google Calander
• Gmail
• Google wallpaper picker
• FOTO gallery 3.3
• Open Camera
• MTK Video Wallpapers
• Vivo Wallpapers
• Bubbles Live Wallpaper
• JRD Music Player
• JRD File Manager
• JRD Calculator
• updated exchange2
• JRD Secure container
• JRD FOTA & services
• JRD plugger
• Gmail
• MTK Sim Engineering mode
• Updated music FX
• CDS info.apk
• AVG mobile antivirus PRO* 365 day subscription free free from me
• JRD video player
• JRD video favourites
• JRD media container
• JRD Facelock
• Mobile Log
• Modem log
• Alcatel one touch manager agaent (wifi data sync)
• VIVO Boot Animation
• VIVO Shutdown Animation
• VIVO Boot Tone
• VIVO Shutdown Tone
• Updated Boot Logo
• Samsung G930F oreo Ringtone Sounds
• Samsung G930F oreo Notification Sounds
• Samsung G930F oreo UI sounds (where available)
• Build prop edited to display as VIVO R11 max
• Other .prop edits
• Updated to Release Keys (was test keys)
• updated libs for Jrd app support
• updated framework for Jrd app support
• updates -res for Jrd app support
• a few JRD -res and libs interswapped from alactel 4027A 4.4.2 EMMC with 3.4.67 Kernel also for use of some JRD features
• root set to function without the need for Su manager app binaries can run themselves.
• changed format of FAT from yaffs_img to normal_rom in scatter for use of the 37.8mb usb partition to be also used for for system storage aswell,
• UPDATED 3G modem to fix connectivity issues (pulled from HTC desire 310)
• added mount points to system for better SD card support and to mount as internal device storage when SD card is inserted.
•Replaced some system apps and some other apps from and alcatel OT 5050 MT6575 for faster UI and system stability.
•integrated framework2 into /system/framework/ as was completely absent, NOTE you cannot remove framework2 or any of its components you will break the system
Everything added or replaced came from the followimg devices.
•ZTE luna MT6572 EmmC
•Alcatel 4027 MT6572 EmmC
•Alcatel 5050 MT6575 EmmC
•HTC 310 MT6572 EmmC
•Samsung S7 Exynos8890
------------STORAGE CAPACITY--------------
storage free space is as follows without an SD card inserted before and after flash of new firmware
BEFORE
/data 20mb
/system 9.0kb
/usb storage 37.8mb (not usable)
AFTER
/DATA 62.9mb
/SYSTEM 25.2mb
/USB STORAGE 37.8mb (usable)
---------☆☆☆MODIFIED BOOT IMG☆☆☆---------
as these R11 max only come with a 512mb NAND chip with OS installed there is only 62.9mb Data storage after flash of my firmware,using the modified boot.img this allows you to use the devices SD card as the devices ROM & internal storage, info on my device with 15GB SD card,
/DATA 12.9GB
/SYSTEM 25.2MB
/USB storage 37.8MB
/internal storage 1.02GB
This has not been implemented into the build due to firmware size when pulling,
If you wish to use the modifed Boot.img and SD card you MUST partition the SD card BEFORE flashing the firmware if you wish to use the boot.img which is OPTIONAL rom will work fine without it,
partition your SD card as follows with 2 partitions
•PRIMARY partition - FAT32
•PRIMARY partition - EXT4
You should name your EXT4 partition that you made as "mmcblk0p2".
To flash with modified boot.img follow steps above for SD card, and steps below for flashing.
NOTE
if you use the boot.img you will need to reconfigure NOVA launchers looks in the Nova settings once flashed everything else is fine
WORKING
• everything is working unless stateded below
NOT WORKING
• VIVO wallpapers (not showing need to rubuild framework-res to set default as vivo)
• FaceLock (due to root installed secure container wont run, unroot and it should)
__________________________________________
FLASHING THE FIRMWARE
__________________________________________
********This is a "UBIFS" filesystem*********
EMMC storage devices are NOT compatible
Unless you change the scatter to support your file system and even then it may require porting still.
Open SP flash tool, and open the scatter.file and change flash method to download only and click download, plug the device in while switched off and the device will flash,
DO NOT USE "format all + download" unless you have a backup of your firmware and security partition or you WILL lose your imei.
________________________________________
LINKS
________________________________________
SP FLASH TOOL :
https://spflashtool.com/download/SP_Flash_Tool_v5.1824_Win.zip
FIRMWARE DOWNLOAD:
https://drive.google.com/file/d/1mK3lnvqSzvtMajyWm1S1YplfQvPlgcgY/view?usp=drivesdk
MODIFIED BOOT IMG :
https://drive.google.com/file/d/1IRwW4SY-mcRfRrFLYw45CpKacmoRRRW3/view?usp=drivesdk
all credits go to Luca Roggero for building this boot .img to allow SD card to be used as system & rom storage.
_______________________________________
☆☆EDIT☆☆
You must change the storage to SD card and "let the system decide" in preferences on initial fieat boot or you will get a soft reboot when installing any app for the first time it can be changed back after if wanted
Also all other MT6572 nand devices that are not an R11 max chinaphone flash only the android file in firmware first with download only to see if will boot (give it 5 or so minutes) and dont forget to take a partition information table backup to change to your addessses in the scatter of this firmware if no boot do a full flash with download only option again allow 5 minutes to boot dont forget to change addresses and lengths also to match your partition info.
Take a firmware backup also, NCK_MTK dongle can obtain the PIT info, backup your firmware and userdata also and has a variety of other usefull finctions such as formatting & network unlocking & imei and baseband backups aswell
Attention all users of R11 max,
New build will be up in a week maximum, Google play is functional, and has been completely rebuilt, i have also built a custom recovery for this model R11_Max however wont be released until the new rom is released.
Thread will be updated here with new links when its ready.
New rom is not far away now for the R11 MAX im just finishing up some minor touchups in the meantime i have built a number of custom recoveries for the phones due to 1 there not being any available at all for it & 2 all recovery porting tools do not work with this phone so manually built a number of different styles,versions etc theres TWRP, CTR, CWM, etc even an OPPO touch recovery even that i also managed to build enjoy,
https://forum.xda-developers.com/android/development/recovery-t3892041
Ti ringrazio
Sei un genio!!!! non ne potevo più di vedere memoria piena e questo launcher pietoso
---------- Post added at 10:30 ---------- Previous post was at 09:44 ----------
Problema: ho flashato la rom, flash andato ok nessun errore, però ora non si accende. Poco dopo che premo il pulsante di accensione fa solo una vibrazione e basta :/
metrovinz said:
Sei un genio!!!! non ne potevo più di vedere memoria piena e questo launcher pietoso
---------- Post added at 10:30 ---------- Previous post was at 09:44 ----------
Problema: ho flashato la rom, flash andato ok nessun errore, però ora non si accende. Poco dopo che premo il pulsante di accensione fa solo una vibrazione e basta :/
Click to expand...
Click to collapse
?? English please
Note all R11 max users,
A new rom will be released for this device by me in the near future when released it is advised to update to the latest build, modded with CM but stock 4.4.4 unfortunately that is all i am able to upgrade it to, 6.0 build i am scrapping for now i can get 6.0 apps to install but they just will not run most not at all,
Another note though ive managed to modify the boot.img some more to swap not only the data from
"ubifs" "UBI" "userdata" "/data" to
"Ext4 "EMMC" "/dev/block/platform/mtk-msdc.1/by-num/p2 (EXTERNAL SD)
but also system from
"ubifs" "UBI" "system" "/system" to
"ext4" EMMC" "/dev/block/mmcblk0p3" "/system" (SDCARD)
Not sure if i can get a rom functional to boot from it but TWRP recognises it aswell as mounts & formats it correctly, some useful info incase anyone else wants to give it a go also
I'm seeking ROM for my R11-1 device which is similar to R11 max.
I'm seeking ROM for my R11-1 device which is similar to R11 max.
The big difference between my R11-1 device and R11 max is the partition size for system.img.
R11-1 is 360MiB and R11 max is 310MiB.
I got some info of R11-1, but now it's bricked. I flashed wrong ROM..
Thank you for reading and I'm happy if you could help me.
______________________________________
R11-1 DEVICE INFO
______________________________________
[email protected]_ctx_jr151_p113m_r10_nd44_2k_2g_fl:/ $ df
Filesystem Size Used Free Blksize
/dev 238.2M 128.0K 238.1M 4096
/sys/fs/cgroup 238.2M 12.0K 238.2M 4096
/mnt/secure 238.2M 0.0K 238.2M 4096
/mnt/asec 238.2M 0.0K 238.2M 4096
/mnt/obb 238.2M 0.0K 238.2M 4096
/system 320.0M 235.7M 84.3M 4096
/data 80.5M 68.4M 12.1M 4096
/.cache 7.0M 772.0K 6.2M 4096
/fat 20.0M 2.6M 17.4M 4096
/protect_f 1.5M 784.0K 752.0K 4096
/protect_s 1.5M 780.0K 756.0K 4096
/mnt/cd-rom 1.2M 1.2M 0.0K 2048
/mnt/media_rw/sdcard0: Permission denied
/mnt/secure/asec: Permission denied
/storage/sdcard0 17.8M 352.0K 17.5M 4096
[email protected]_ctx_jr151_p113m_r10_nd44_2k_2g_fl:/ $ cat /proc/partitions
major minor #blocks name
7 0 1254 loop0
7 1 18304 loop1
253 0 393216 zram0
31 0 512 mtdblock0
31 1 1024 mtdblock1
31 2 1536 mtdblock2
31 3 1536 mtdblock3
31 4 1536 mtdblock4
31 5 128 mtdblock5
31 6 384 mtdblock6
31 7 6144 mtdblock7
31 8 6144 mtdblock8
31 9 256 mtdblock9
31 10 384 mtdblock10
31 11 1024 mtdblock11
31 12 2048 mtdblock12
31 13 20480 mtdblock13
31 14 368640 mtdblock14
31 15 7168 mtdblock15
31 16 94848 mtdblock16
[email protected]_ctx_jr151_p113m_r10_nd44_2k_2g_fl:/dev/block $ cat /proc/mtd
dev: size erasesize name
mtd0: 00080000 00020000 "preloader"
mtd1: 00100000 00020000 "pro_info"
mtd2: 00180000 00020000 "nvram"
mtd3: 00180000 00020000 "protect_f"
mtd4: 00180000 00020000 "protect_s"
mtd5: 00020000 00020000 "seccnfg"
mtd6: 00060000 00020000 "uboot"
mtd7: 00600000 00020000 "boot"
mtd8: 00600000 00020000 "recovery"
mtd9: 00040000 00020000 "secstatic"
mtd10: 00060000 00020000 "misc"
mtd11: 00100000 00020000 "logo"
mtd12: 00200000 00020000 "expdb"
mtd13: 01400000 00020000 "fat"
mtd14: 16800000 00020000 "system"
mtd15: 00700000 00020000 "cache"
mtd16: 05ca0000 00020000 "userdata"
[email protected]_ctx_jr151_p113m_r10_nd44_2k_2g_fl:/system $ cat build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KOT49H
ro.build.display.id=ALPS.KK1.MP7.Band1.2.5.V1.3-2018-10-09_12-33
ro.build.version.incremental=eng.daiweiping.1539059404
ro.custom.build.version=DW_MT6580_ZM9_FWVGAJ_CXT_RJ151_P113_R10_hhx_ZHX_FL_V1.0_20181009
ro.build.version.sdk=19
ro.defwidth2=480
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.date=2018年 10月 09日 星期二 12:33:14 CST
ro.build.date.utc=1539059594
ro.build.type=user
ro.build.user=daiweiping
ro.flash=yes
ro.build.host=user
ro.build.tags=test-keys
ro.product.model=R10
ro.product.name=R10
ro.product.device=zm9_ctx_jr151_p113m_r10_nd44_2k_2g_fl
ro.product.board=zm9_ctx_jr151_p113m_r10_nd44_2k_2g_fl
ro.product.brand=alps
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=alps
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=zm9_ctx_jr151_p113m_r10_nd44_2k_2g_fl
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=zm9_ctx_jr151_p113m_r10_nd44_2k_2g_fl-user 4.4.2 KOT49H eng.daiweiping.1539059404 test-keys
ro.build.fingerprint=alps/zm9_ctx_jr151_p113m_r10_nd44_2k_2g_fl/zm9_ctx_jr151_p113m_r10_nd44_2k_2g_fl:4.4.2/KOT49H/1539059404:user/test-keys
ro.build.flavor=
ro.build.characteristics=default
persist.sys.launcher=com.shly.theme.s6
dw.control.2d=true
ro.sversion=8200
# end build properties
# begin mediatek build properties
ro.mediatek.version.release=ALPS.KK1.MP7.Band1.2.5.V1.3
ro.mediatek.platform=MT6572
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=MAIN2.1
ro.mediatek.version.sdk=2
# end mediatek build properties
#
# from out/target/product/zm9_ctx_jr151_p113m_r10_nd44_2k_2g_fl/obj/CUSTGEN/config/system.prop
#
#
# system.prop for generic sdk
#
rild.libpath=/system/lib/mtk-ril.so
rild.libargs=-d /dev/ttyC0
# MTK, Infinity, 20090720 {
wifi.interface=wlan0
# MTK, Infinity, 20090720 }
# MTK, mtk03034, 20101210 {
ro.mediatek.wlan.wsc=1
# MTK, mtk03034 20101210}
# MTK, mtk03034, 20110318 {
ro.mediatek.wlan.p2p=1
# MTK, mtk03034 20110318}
# MTK, mtk03034, 20101213 {
mediatek.wlan.ctia=0
# MTK, mtk03034 20101213}
#
wifi.tethering.interface=ap0
#
ro.opengles.version=131072
wifi.direct.interface=p2p0
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapsize=128m
# USB MTP WHQL
ro.sys.usb.mtp.whql.enable=0
# Power off opt in IPO
sys.ipo.pwrdncap=2
ro.sys.usb.storage.type=mtp,mass_storage
# USB BICR function
ro.sys.usb.bicr=yes
# USB Charge only function
ro.sys.usb.charging.only=yes
# audio
ro.camera.sound.forced=0
ro.audio.silent=0
ro.zygote.preload.enable=0
ro.operator.optr=CUST
ro.kernel.zio=38,108,105,16
persist.sys.timezone = Asia/Dubai
ro.camera.front.sizeindex=0
ro.camera.back.sizeindex=0
persist.sys.sign_3g_4g=3
persist.sys.frontcamera=800W
persist.sys.backcamera=1600W
ro.defwidth=960
ro.defwidth2=960
isWallpaperSlide=true
bluetooth.HostName = X21
persist.sys.resolution=1920x1080
persist.sys.fingerprint2=true
persist.sys.hidenavigation=true
persist.sys.isshowrealrom=1
persist.sys.isshowrealram=1
factory_code=*#66*#
engineering_code=*#*#3646633#*#*
imei_code=*#0623#
hideSwitch_code=*#0011#
isshowUSB=false
ishotseatAllAppsRank=true
ro.product.name=R10
#
# ADDITIONAL_BUILD_PROPERTIES
#
persist.gemini.sim_num=2
ro.gemini.smart_sim_switch=false
ro.gemini.smart_3g_switch=0
ril.specific.sm_cause=0
bgw.current3gband=0
ril.external.md=0
ro.btstack=blueangel
ro.sf.hwrotation=0
ril.current.share_modem=2
curlockscreen=1
ro.mediatek.gemini_support=true
drm.service.enabled=true
fmradio.driver.enable=1
ril.first.md=1
ril.flightmode.poweroffMD=1
ril.telephony.mode=1
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
persist.mtk.anr.mechanism=1
mediatek.wlan.chip=mediatek.wlan.module.postfix=_
ril.radiooff.poweroffMD=0
ro.config.notification_sound=Proxima.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.config.ringtone=Backroad.ogg
persist.mtk.wcn.combo.chipid=-1
ro.fota.oem=MTK_KK
ro.fota.platform=MTK_KK
ro.fota.type=phone
ter.service.enable=0
mediatek.extmd.usbport=0
ro.lte.dc.support=0
ril.active.md=0
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.4_r5
persist.sys.dalvik.vm.lib=libdvm.so
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Hey mate,
Youve got the R10
In which i dont have one of those unfortunately, when you flashed the wrong firmware did you flash PRELOADER, UBOOT & BOOT ?
if so youve deffo messed it up,
Im assuming you didnt take a firmware backup first either ? If you did flash it back with SP flash tool if you didnt then i wont be able to help you i dont think unless by some miracle they both use the exact same kernel, either way i have 3 R11 firmwares
2 are ubifs NAND firmwares for the R11 max & the 3rd is an ext4 eMMC for R11 im happy to upload the UBOOT, PRELOADER & BOOT files from all 3 to see if you can get some life back into the device as they are all made from the same chinese manufacturer.
If you can get the device to at least turn on to the boot screen then after flash then the files are good you can then flash the ANDROID, CACHE & USRDATA from my firmwares here on xda and it should come back to life as i have tested this on the R11 EMMC i flashed my UBIFS system.img to the device & worked no problem,
system size also does not matter as long as the ANDROID file is not bigger than your system partition so that should also be fine,
You should never ever flash another devices preloader, uboot or boot.img as the kernels are compiled differently on each device in most cases,
If you cant get any power to the device to flash then take the backing off and take all the screws out take the backing off and look for a series of 4 -6 gold circular points.
These are called test points plug the device in and start the flash on pc then touch all the points with your finger you should now hear the VCOM connect to the device and flash the files youve loaded into SP
#edit ive just looked at your partition info you have the exact same layout as the R11 MAX ubifs models i have so ill upload the boot.img, preloader & uboot from my 2 variations for nand as both have different kernels so hopefully one will work for you & get power back.
Hello Matty1993,
Thank you very much for your reply!
It was good to find out my device name, R10!
>did you flash PRELOADER, UBOOT & BOOT ?
Yes,sir. I formatted all without taking any backup! I'm foolish..
>ill upload the boot.img, preloader & uboot from my 2 variations for nand as both have different kernels so hopefully one will work for you & get power back.
Thank you for your kindness,I wanna try it!
[email protected] said:
Hello Matty1993,
Thank you very much for your reply!
It was good to find out my device name, R10!
>did you flash PRELOADER, UBOOT & BOOT ?
Yes,sir. I formatted all without taking any backup! I'm foolish..
>ill upload the boot.img, preloader & uboot from my 2 variations for nand as both have different kernels so hopefully one will work for you & get power back.
Thank you for your kindness,I wanna try it!
Click to expand...
Click to collapse
Hey mate,
No worries at all,
For future references on your mtk devices it is always advisable to take a firmware backup using SP Flash tool you can do this by entering the readback menu or by using MTK nck dongle there is a free version in which works quite well which outputs the pulled files directly into there segregated partitions eg preloader, uboot, boot, secro,usrdata,system,cache files aswell as generating a scatter ready to be loaded into SP flash tool great program i use it all the time,
Anyhow give me 5-10mins & ill upload both of my variations of the R11 boot preloaders & uboot as youll need to flash them all to get rid of the other ones both have diff kernels as i mentioned so give them both a try and see how you go,
Let me know if they dont work also as i can ask a few people to see if maybe they have one they can pull a backup from.
#edit my google drive isnt working ill upload as soon as it is
Hey mate google drives back up now heres the links for preloader, uboot, & boot
R11 max ubifs ZMA_12_MB
https://drive.google.com/file/d/1kW34rLGyWGcUT04i3ThXGMM703frVHPr/view?usp=drivesdk
R11 max ubifs HS_Q6_MB
https://drive.google.com/file/d/1tTZjnGN5jQQ2lIl_4FmqPtyuoXsH1dJm/view?usp=drivesdk
See how they go
Hello Matty1993,
Thank you for your time and ROMs.
I flashed them and my device got power back with ZMA_12_MB.
I'm very happy to see NOT black screen!!
I took pictures.
I don't know the boot screen is working or freezing.
The title logo is 'boost mobile' and there are vertical stripes and flickling a little.
Anyway,I got advance a little! Thank you,again.
[email protected] said:
Hello Matty1993,
Thank you for your time and ROMs.
I flashed them and my device got power back with ZMA_12_MB.
I'm very happy to see NOT black screen!!
I took pictures.
I don't know the boot screen is working or freezing.
The title logo is 'boost mobile' and there are vertical stripes and flickling a little.
Anyway,I got advance a little! Thank you,again.
Click to expand...
Click to collapse
Hey mate,
Your device isnt R10 yours is R11 ZMA Variant ive confirmed this by looking at the pics youve provided,
The logo will look like that due to either 2 things the firmware or logo is still on the device,
1 either the logo is to small or to big for the device causing the lines, or 2 the firmware you flashed is using a diff LCD driver,
Give me a bit when i get home from work ill upload a full firmware for the ZMA_12_MB variant for you, its not the best but once ive finished on the R11_HS_Q6_MB firmware ill be doing the ZMA_12_MB after, the firmware ill be uplaoding is somewhat modified however,
Also did you know that there a storage fix available for these R11, all it requires is a modified boot.img which im happy to do now i know the zma12 kernel is your model for sure, & a decent class 10 sd card with an ext4 partition on it, ive already got a modified boot.img for the hsq6 variant i made a 14GB ext4 partition now data is 14GB instead of 20MB lol no lag at all or anything due to the sd being class10
Hello Matty1993,
Thank you for your informative insight.
I'm happy to hear that my device may revive and also transform to a practical device!:good:
I'm look forward to flashing your firmware!!
[email protected] said:
Hello Matty1993,
Thank you for your informative insight.
I'm happy to hear that my device may revive and also transform to a practical device!:good:
I'm look forward to flashing your firmware!!
Click to expand...
Click to collapse
Hey mate sorry i couldnt get the firmware up for you last night having troubles with PC being slow reinstalling windows on it now and ill get the FW up for you as soon as its booted up as its all stored on my 2TB external HD
Hey mate wow didnt realise it been 3 days will have the firmware up for you today some time 100% been doing some modifications to it as i didnt realise how crap the OS was still, ive also modified a stock boot.img aswell as a modifed storage boot.img with CM sources and im just about finished making the OS look a bit better, still gonna look bad as it was a quick job but it will be alot better than what it was before until i get around to properly building the firmware for the zma variant,
Ill update this post with the link soon as its uploaded sorry again for the wait mate
Hello Matty1993,
Pls don't worry about making me wait.
This is not a job,we do because we like it,isn't it?
Let's do it slowly.
[email protected] said:
Hello Matty1993,
Pls don't worry about making me wait.
This is not a job,we do because we like it,isn't it?
Let's do it slowly.
Click to expand...
Click to collapse
Hey mate,
Link will be up soon for you firmwares uplaoding to google drive still needs work but ive redone quite a bit considering what it used to look like youll see anyhow, some of the stuff ive done is modded the camera app & gallery app to run on 4.4, modded system to run cyanogenmod trebuchet launcher, redone the settings & dropdown and also built a setupwiz for it aswell which you will see,
I will finish it up after im done with the HS_Q6 variant, if theres anything majorly wrong with calls or anything etc let me know and ill get it sorted,
I cant test the ril as these are 2G network handsets, Australia dosent have 2G network anymore but it should be all good i know what im doing
## EDIT ##
Link for firmware is here,
https://drive.google.com/file/d/1Ix-k9Myjt1Mc9Rs36wQgRHXuQtU58Pwg/view?usp=drivesdk
Theres a readme id strongly suggest to read it before flashing as theyre are some extra files i have added, also the flash layout is very diff from normal MTK firmwares for 6572 as ive modifed most partitions already just never got around to the theming side of things on the zma variants
Anyhow let me know how you go
Hello Matty1993,
Thank you for your great works.
I flashed R11_Max_ZMA_12_MB_1.0_GT18_MT6572_NAND+UBIFS_20190322.
Then when I power on,the boot screen is shown with google logo 'G'.
But after that,it seems like to be freezing.
When I connect my device to my linux pc,my device is recognized as USB device.
[201999.116029] usb 1-4: new high-speed USB device number 7 using ehci-pci
[201999.248871] usb 1-4: New USB device found, idVendor=0bb4, idProduct=0001
[201999.248878] usb 1-4: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[201999.248883] usb 1-4: Product: MT65xx Android Phone
[201999.248887] usb 1-4: Manufacturer: MediaTek
[201999.248891] usb 1-4: SerialNumber: 0123456789ABCDEF
[201999.249986] usb-storage 1-4:1.0: USB Mass Storage device detected
[201999.254160] scsi host6: usb-storage 1-4:1.0
[202000.252799] scsi 6:0:0:0: Direct-Access Linux File-CD Gadget 0000 PQ: 0 ANSI: 2
[202000.253292] scsi 6:0:0:1: Direct-Access Linux File-CD Gadget 0000 PQ: 0 ANSI: 2
[202000.258682] sd 6:0:0:0: Attached scsi generic sg2 type 0
[202000.261076] sd 6:0:0:1: Attached scsi generic sg3 type 0
[202000.262946] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[202000.265932] sd 6:0:0:1: [sdc] Attached SCSI removable disk
OPPO RECOVERY Ver 1.0 seems to be working good!
However there are vertical stripes and flickling a little,I can select menu like wipe data etc.
I took pictures below.
I'm very very happy if your custom_boot_storage_modified_zma_12_mb_1.0.img could work on my device!