RCA 10" Touchscreen Tablet PC/DVD Combo Featuring Android 6.0 (Marshmallow)
*No idea why it says PC/DVD as its Android not Windows.
ASIN/Model numbers: ASIN: B077L4VBHK Model: DRP2091
RCA typical RCT number: RCT6603W47M7
Chipset/CPU: MT8127
Ports: 1x Mirco USB (supports ADB! etc. unlike VikingPRO), 1xUSB A, 1xHDMI (mini i believe), 1xMicroSD slot (supports up to 128GB)
Special: 1xDVD/CD Reader/Drive. has unlockable bootloader via fastboot oem unlock
Root Attempts: (Failed: KingoRoot, SRS, KingRoot, RootMaster)
MTK Droid Root & Tools and SP Flash Tools don't seem to work right with this cant create scatter etc. (i assume because of MT8127)
Links:
Walmart/Wally World
Amazon
if any dev could help me root this and get custom recovery would be great.
UPDATE: Thanks to NepoRood (and my testing) theres now CWM recovery (attached to post extract zip and flash img via fastboot flash recovery command.) unfortunately we were still unable to get root access.. if anyone has this device or wants to help root this pm me.
Additional files attached maybe someone can build me cwm or twrp for this as i could never get anything to build for mtk devices.
darkensx said:
Additional files attached maybe someone can build me cwm or twrp for this as i could never get anything to build for mtk devices.
Click to expand...
Click to collapse
I found various firmware downloads, but need to know the exact type of firmware you are running.
Example of one I found: rct6603w47m7-android6.0-v23-v2.15.80 (<-- underlined part is what matters)
If you boot into recovery, it should show you the type of firmware you have.
NepoRood said:
I found various firmware downloads, but need to know the exact type of firmware you are running.
Example of one I found: rct6603w47m7-android6.0-v23-v2.15.80 (<-- underlined part is what matters)
If you boot into recovery, it should show you the type of firmware you have.
Click to expand...
Click to collapse
DRP2091-android6.0-v62-v1.19.90-E02
*also says on very bottom of screen "supported API: 3"
**DRP2091 is rct6603w47m7 not sure why there's so many different model/serial numbers referencing the same exact device...
also i managed to dump the whole device via SP tools readback on linux so if anything beyond recovery or boot img are needed i should have it.
darkensx said:
DRP2091-android6.0-v62-v1.19.90-E02
*also says on very bottom of screen "supported API: 3"
**DRP2091 is rct6603w47m7 not sure why there's so many different model/serial numbers referencing the same exact device...
also i managed to dump the whole device via SP tools readback on linux so if anything beyond recovery or boot img are needed i should have it.
Click to expand...
Click to collapse
That version isn't on the site (or any v1.19.x), I'll download the images from the OP in a bit and see what's inside...
NepoRood said:
That version isn't on the site (or any v1.19.x), I'll download the images from the OP in a bit and see what's inside...
Click to expand...
Click to collapse
Had the same issue also I came across a bunch of ota test files on a Chinese site but links were dead and because no ota update is available i can't grab the ota url or file name. So ended up hitting a dead end.
Would it be possible to bypass the activation code screen with cwm or twrp? Or maybe put a different version of android on the tablet, other than marshmallow.?
darkensx said:
Additional files attached maybe someone can build me cwm or twrp for this as i could never get anything to build for mtk devices.
Click to expand...
Click to collapse
I'm having same problem could someone help me root this tablet explain as easy as possible and slow and clear directions
I have no idea
johnnymack said:
I'm having same problem could someone help me root this tablet explain as easy as possible and slow and clear directions
Click to expand...
Click to collapse
I've got the RCT6603W47M7 tablet, but here in the UK it goes by the name of RCA Neptune 10.1L.
Problem is I have bricked it and I am now trying to recover it using SP Flash Tools. I have tried 2 different stock ROMs, only to have nothing but errors and interruptions during flashing. (errors 2004 and 4008). My tablet is fully charged yet it will randomly disconnect during flashing. I've tried both the MTKAllInOne.bin and DA_SWSEC.bin but I still get the same problem either way.
I've tried different USB ports, different cables and the two download agents that I just mentioned but I am stumped.
I wanted to try the ROM found here https://www.needrom.com/download/rca-rct6603w47m7/
But as I don't have a premium account I cannot access it.
Any ideas? This is very frustrating.
BP9375 said:
I've got the RCT6603W47M7 tablet, but here in the UK it goes by the name of RCA Neptune 10.1L.
Problem is I have bricked it and I am now trying to recover it using SP Flash Tools. I have tried 2 different stock ROMs, only to have nothing but errors and interruptions during flashing. (errors 2004 and 4008). My tablet is fully charged yet it will randomly disconnect during flashing. I've tried both the MTKAllInOne.bin and DA_SWSEC.bin but I still get the same problem either way.
I've tried different USB ports, different cables and the two download agents that I just mentioned but I am stumped.
I wanted to try the ROM found here https://www.needrom.com/download/rca-rct6603w47m7/
But as I don't have a premium account I cannot access it.
Any ideas? This is very frustrating.
Click to expand...
Click to collapse
problem with the cwm recovery if i remember correctly is any thing flashed by it doesnt take the device will just bootloop
i no longer have the device currently i might pickup another at some point... i cant remember if i used the micro usb port to flash or if i had to use a usb male to male cable..
darkensx said:
problem with the cwm recovery if i remember correctly is any thing flashed by it doesnt take the device will just bootloop
i no longer have the device currently i might pickup another at some point... i cant remember if i used the micro usb port to flash or if i had to use a usb male to male cable..
Click to expand...
Click to collapse
Thank you for your reply, I was worried that this discussion was dead. That's frustrating to say the least! Damn! Well, I don't know if this will work but I found another device that is also a MT8127 and has exactly the same spec of this tablet. My point being is that I found a TWRP image for that device, and because it's the same chip set I assume that it'll work for this device too?
If I can get my bricked tablet to even turn on I shall try it. It also makes me wonder that if we were able to root the device, would we be able to access the internal storage by normal means? By using the micro USB ? Either way it'd be great to have it rooted.
I stayed up all night last night trying to flash this tablet and still no luck, it keeps disconnecting half way through.
Related
Hi folks,
unfortunately I somehow bricked my ZTE Open. I flashed cwm (worked fine) but after flashing both system AND userdata via flash_image, the phone won't boot and what is much worse it won't boot into cwm anymore as it hangs there with just showing the logo and the cwm version. The menus are missing, it does not react buttons and does not show up in adb. FTM mode is also non-functional, holding volup gets you also into broken recovery.
For earlier ZTE devices like the ZTE Blade it seems to be possible to low level flash them in diagnostics mode. Diagnostics mode is working fine on the ZTE Open (it shows up with the diagnostics port on USB. Luckily I also have all the 20 partitions backed up, but I don't know how to flash them in this diagnostics mode. I tried putting the files into the root of the SD card and including sha1/256/512 plus md5sum files, but it was not impressed by that. Not sure if this only works in FTM mode, though.
Any help would be highly appreciated! I highly assume that the procedure is the same as for the ZTE Blade.
This may help. http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/
At least there is more going on for Firefox Open over there.
Thanks but as you might have noticed I posted several comments there already, but I thought XDA would be the right place for unbricking devices.
Defier525 said:
Thanks but as you might have noticed I posted several comments there already, but I thought XDA would be the right place for unbricking devices.
Click to expand...
Click to collapse
Sorry! Eyes tight shut!
Are there any updates on this one?
I have bricked Open too, I'm attaching the PCB picture, if it is any help to maybe find UART or JTAG pins?
Can someone be really nice and please dump the bootloader from working ZTE Open in send it to me?
I've found some guy, who maybe can help me write bootloder with JTAG.
I think this should work, but no promises: https://sites.google.com/site/zteopenfirmware/download-mode
psywolf said:
I think this should work, but no promises: https://sites.google.com/site/zteopenfirmware/download-mode
Click to expand...
Click to collapse
Thanks for your time to help, but this does not work for me. I get an error, when I press flash button (printscreen under attachments).
I've tried to probe the pins with the multi-meter and found GND and V+ (picture under attachment)
Now it would be nice to have something like this -> http://www.grandideastudio.com/portfolio/jtagulator/
Defier525 said:
Hi folks,
unfortunately I somehow bricked my ZTE Open. I flashed cwm (worked fine) but after flashing both system AND userdata via flash_image, the phone won't boot and what is much worse it won't boot into cwm anymore as it hangs there with just showing the logo and the cwm version. The menus are missing, it does not react buttons and does not show up in adb. FTM mode is also non-functional, holding volup gets you also into broken recovery.
For earlier ZTE devices like the ZTE Blade it seems to be possible to low level flash them in diagnostics mode. Diagnostics mode is working fine on the ZTE Open (it shows up with the diagnostics port on USB. Luckily I also have all the 20 partitions backed up, but I don't know how to flash them in this diagnostics mode. I tried putting the files into the root of the SD card and including sha1/256/512 plus md5sum files, but it was not impressed by that. Not sure if this only works in FTM mode, though.
Any help would be highly appreciated! I highly assume that the procedure is the same as for the ZTE Blade.
Click to expand...
Click to collapse
tpt files for the zte open
https://www.dropbox.com/sh/rnj3rja7gd54s98/_twgXEkMFH/P752D04_DEV_EU_20131212_v1.2.7z
Thank you for the link. But what tool is supposed to be used to flash the files? And is there a way I can use my backup as well? In this case: how can I transform it to TPT files?
Update: I tried flashing it by following the instructions of the link posted by psywolf, but unfortunately I am getting the same error as aversario. I tried also flashing just recovery, but it seems like no single partition is flashed successfully.
So, I've ordered jtagulator and it showed the pins. Now I need jtag programmer, which one do you guys recommend?
And I am still looking for some great guy to share with me his bootloader of a functional zte open.
aversario said:
So, I've ordered jtagulator and it showed the pins. Now I need jtag programmer, which one do you guys recommend?
And I am still looking for some great guy to share with me his bootloader of a functional zte open.
Click to expand...
Click to collapse
on what partition is the bootloader? i have a UK revision 02 one, i would help you out if you tell me how to get the bootloader?
linr76 said:
on what partition is the bootloader? i have a UK revision 02 one, i would help you out if you tell me how to get the bootloader?
Click to expand...
Click to collapse
Well, I don't know the partition names by heart, but as I remember the bootloader is one of the small partitions (so definitely not system or boot or userdata or recovery).
The way to get that small partitions would be installing CWM recovery first -> http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/
then enter adb shell on computer
su # to get root privileges
then it should be something like explained here -> https://www.youtube.com/watch?v=j3GOzUURSgM&feature=player_detailpage#t=153
And thank you very much for your time
If i figure out how to do that without CWM i'll upload it for you. Cannot install CWM because i need to be on stock recovery for development of update packages, sorry
Sent from my V3 using Tapatalk
linr76 said:
If i figure out how to do that without CWM i'll upload it for you. Cannot install CWM because i need to be on stock recovery for development of update packages, sorry
Click to expand...
Click to collapse
OK, I get that. I'm sure there exists a way to do it without changing recovery also. I just can't figure it out because that's the only Firefox OS phone I've had.
try to reinstall
Hi, I bricked my ZTE Open (EU version) too. Had bought it from a German Ebay seller and tried to flash FirefoxOS 2.0 on my device. I don't have the CWM recovery installed, only the "Firefox OS System Recovery" Big mistake, I know . When I switch on the device, the Firefox OS logo appears, then disappeas after a few seconds, and so on, the perfect bootloop
I can't access the device via ADB or fastboot.
When I ty to install any downloaded zip (even from ZTE's homepage) from the SD card, I get following messages:
Code:
--Install /sdcard ...
Finding update package ...
Opening update package ...
Verifying update package ...
E: signature verification failed
Installation aborted.
So there is no valid signature.
Can you help me please? Thank you!
Heinz
Found a solution by myself!:victory:
I downloaded the update.zip file from firefox.ztems.com (Update package of Android GB for OPEN device) and installed it.
After that I could flash the CWM recovery. It seems to work...
Hi fellow xda'rs,
I recently bought a Android TV Stick from Geek(app) from china.
I thought I had found a bargain as its specs were:-
2GB RAM
Quad Core CPU
16GB Storage
I managed to snap this up for £24 which I thought was a bargain but when I got the device delivered and was using it I thought it was a little on the slow side so I began to think it was a clone as its default OS theme was not the same as the usual CX919's aswell.
So I wanted to flash the device with a new ROM specifically the Finless 1.6b ROM.
So after following the instructions to installing the ROM using the software provided with the ROM download I managed to install the drivers and get the software to recognize the device. I then wiped the NAND and attempted to install the ROM but it failed .
Now the device does not boot at all and is not recognized by the PC. Windows just states the device is not recognized and has malfunctioned
So I cannot flash any other or what I believer I have found to be the original ROM for the clone device.
The board states its a GXT_D16_LP_V1.8 150310
I have seen that there are tutorials on putting the device into Mask Flash mode by shorting pins but as this is for the genuine CX919 my board is totally different and does not have the pins available to short I think.
In short could anyone help me to put this device into Mask Flash mode and tell me what id need to do and what pins to short please?
I have attached a couple of pictures of the device and board.
lowery91 said:
hi fellow xda'rs,
i recently bought a android tv stick from geek(app) from china.
I thought i had found a bargain as its specs were:-
2gb ram
quad core cpu
16gb storage
i managed to snap this up for £24 which i thought was a bargain but when i got the device delivered and was using it i thought it was a little on the slow side so i began to think it was a clone as its default os theme was not the same as the usual cx919's aswell.
So i wanted to flash the device with a new rom specifically the finless 1.6b rom.
So after following the instructions to installing the rom using the software provided with the rom download i managed to install the drivers and get the software to recognize the device. I then wiped the nand and attempted to install the rom but it failed .
Now the device does not boot at all and is not recognized by the pc. Windows just states the device is not recognized and has malfunctioned
so i cannot flash any other or what i believer i have found to be the original rom for the clone device.
The board states its a gxt_d16_lp_v1.8 150310
i have seen that there are tutorials on putting the device into mask flash mode by shorting pins but as this is for the genuine cx919 my board is totally different and does not have the pins available to short i think.
In short could anyone help me to put this device into mask flash mode and tell me what id need to do and what pins to short please?
I have attached a couple of pictures of the device and board.
Click to expand...
Click to collapse
problem solved! :d
i found the mask flash mode pins to short by trial and error and luckily enough after 1 hour i solved it and got the pc to flash it back to its original rom. If anyone has the same device or issues and would like to know how to solve this i will be happy to help
I would be interested. I have a very similar clone (was supposed to be mk809iv). I have the same board although possibly different chipset.
I haven't bricked it (yet) but will probably do so if I can't find a way to root it. I think it may have come pre-rooted as super su was preinstalled but it has never worked (possibly because the app updated but not the binary?). I have since tried to update the binary and killed the root access completely.
Questions:
Is the ROM you used pre-rooted or rootable (if you've tried)?
Which pins need shorting? I have a button on the side that may be doing the same thing.
OT. How do I upload images or can I not as a new member?
Thanks in advance
any guide? i have the same device or where to download rom?
If your still looking, i might be able to help with a rom, root, and guide.
Thank you but managed to get root the same day you posted. I may still give it a go when my new tv box turns up though if you dont mind posting the info?
For anyone else interested in how I gained root:
1. Search for, download and install kingroot 4.6.5 (this is the version I used, only the latest version is available from official site and cannot be sure next steps will work with it)
2. Run kingroot and follow steps to gain root (dongle may reboot)
3. BUY super sume from play store.
4. Run super sume and follow steps to replace kingroot with super su.
what pins did you short
I am having problems flashing my hdmi stick . I can't get it to flash mode. which pins did you shorted?
can you email me a picture of it? [email protected] thanks
Lowery91 said:
problem solved! :d
i found the mask flash mode pins to short by trial and error and luckily enough after 1 hour i solved it and got the pc to flash it back to its original rom. If anyone has the same device or issues and would like to know how to solve this i will be happy to help
Click to expand...
Click to collapse
Hello,
Having some problems with this stick .Messed up trying to flash a non rooted rom and now I only get a blue icon in rkbatch tool ( after short pin 5-6 ) and nothing happens. Download boot fail errors for a year...
Can someone help me please?
Is it the same model? What version of rkflash tool are you using. And what version are you trying to flash. In my case I didn't need to short any pins.
spade2be said:
Is it the same model? What version of rkflash tool are you using. And what version are you trying to flash. In my case I didn't need to short any pins.
Click to expand...
Click to collapse
I've used several batchtools from 1.5 ( doesn't see my device at all ) to 1.8, different roms ( neomod, finless, stock cx919 roms )hoping one would give me something. All different bootloaders 1.24, 2.08, 2.13,...
I'm going to check mine out. It's been a minute since I used it. But I got the rock chip tool and the img file. I'll zip it up and pm you the link asap.
spade2be said:
I'm going to check mine out. It's been a minute since I used it. But I got the rock chip tool and the img file. I'll zip it up and pm you the link asap.
Click to expand...
Click to collapse
Thnx a million for your help. I've gone bonkers over this hahaha
Lowery91 said:
problem solved! :d
i found the mask flash mode pins to short by trial and error and luckily enough after 1 hour i solved it and got the pc to flash it back to its original rom. If anyone has the same device or issues and would like to know how to solve this i will be happy to help
Click to expand...
Click to collapse
what pins did you short
I am having problems flashing my hdmi stick . I can't get it to flash mode. which pins did you shorted?
can you email me a picture of it? [email protected] thanks
Hi everybody - any help with the following problem is appreciated, I've thrown everything I can find at it but I'm just over my head at this point!
My LG G watch worked great, up until one morning when it got stuck in a bootloop - if I had to guess, the battery must have run out at the exact wrong time, during an OTA update. Maybe. Anyway, stuck in a bootloop.
I managed to install TWRP bootloader, and apparently uninstalled everything but the TWRP bootloader, as it now has the 'no OS installed!' dialogue whenever I try to exit.
I had minimal success installing ADP drivers, but never managed to make a PC/watch connection past fastboot OEM unlock. At the moment (a few months after i had that working) my PC doesn't recognise the watch at all.
So I've bought an OTG cable, and the plan is to put a flashable ROM (hey, even the stock one if I can find it) on a USB stick, navigate to it on TWRP via install, and take it from there. Anyone know if that's what I should be trying / where I can find that particular ZIP file?
Also worth noting, I never toggled on ADP debugging when the original OS was working.
Here's the info from the fastboot screen- ANY help is appreciated!
Product Name = Dory
Variant = dory 4GB
HW Version - rev_11
Bootloader Version - Doryz11c
Serial Number - 03b1175b02a23642
MSN - 406KPMZ0096923
Signing - production
Secure boot - enabled
Lock state - unlocked
Have you tried the instructions of the thread about fixing adb after the update? May work for you. I don't think the watch supports OTG...
http://forum.xda-developers.com/showthread.php?t=3347122
Use this tool for flashing:
http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863
Should have asked months ago
MihaiSG said:
Use this tool for flashing:
http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863
Click to expand...
Click to collapse
Mate... worked a dream. Thanks so much!
So I got a cheap android tablet and I wanted to root it. I was successful so I decided to install TWRP. I searched for my specific model and found an image on a german forum. I downloaded and flashed it and it got stuck in a reboot loop. So I looked at the image and it was for the QV1030. I tried to get it into recovery but couldn't. Many sources told me to hold Vol Up and Lock, and I tried this and more. Nothing would make it enter recovery mode. Then I read about SP Flash Tool and found the stock rom for the tablet and decided I would try to flash that. It kept coming up with an error, and every source online told me to format the flash except for the bootloader and then I could flash it. So I did. Now it doesn't show anything on screen, and SP Flash Tool comes up with error 6045. But it does show up in device manager under com ports as, "MediaTek USB Port" so I think I can still do something about it. I don't have any backups. I don't know what I'm doing. I require assistance please.
So I reflashed the entire backup and it come up with no error. The logo comes up and it plays the chime. The logo does this little shimmer effect and once it gets to this screen, it shimmers indefinitely. If I plug it in, it begins installing a driver and then stops part way through.
drsinclair said:
So I reflashed the entire backup and it come up with no error. The logo comes up and it plays the chime. The logo does this little shimmer effect and once it gets to this screen, it shimmers indefinitely. If I plug it in, it begins installing a driver and then stops part way through.
Click to expand...
Click to collapse
I left it for about 5 minutes and it finished the driver. I thought it froze but I was wrong. It shows up now on device manager under Portable Devices as, "MTP USB Device". I tried to see if it was listed as a device by ADB. It is not. Lets just say I've already learned a thing or two about this stuff. Good thing I did it on an 80 dollar chinese tablet and not my HTC One M9
drsinclair said:
I left it for about 5 minutes and it finished the driver. I thought it froze but I was wrong. It shows up now on device manager under Portable Devices as, "MTP USB Device". I tried to see if it was listed as a device by ADB. It is not. Lets just say I've already learned a thing or two about this stuff. Good thing I did it on an 80 dollar chinese tablet and not my HTC One M9
Click to expand...
Click to collapse
I got it to work again mostly. So I realized that I wasn't flashing the whole backup. Some things didn't have a path and I had to set it manualy. Now it has CFW for some reason, but I reset it and it works now. The only thing is WiFi is not turning on. Any ideas about that?
drsinclair said:
I got it to work again mostly. So I realized that I wasn't flashing the whole backup. Some things didn't have a path and I had to set it manualy. Now it has CFW for some reason, but I reset it and it works now. The only thing is WiFi is not turning on. Any ideas about that?
Click to expand...
Click to collapse
I actually want to upgrade this from Android 4.2.2 to a more recent version. Do you guys have any ideas about that?
So I've come to the conclusion that while the device is no longer bricked, the current installation is written over the old one and things are conflicting. I know this because I looked through the cache and found filenames referring to apps I had installed before breaking it. So would the solution be to wipe the system partition and reflash the system.img so everything is fresh? Or does the problem lie elsewhere.
I formated the system partition, used SP Flasher to flash system.img and then did a factory reset. The issue has still not been solved. And now that I have done that, I don't have root access anymore. Framaroot says it was successful and I restart and check root explorer on ES File Explorer and it doesn't work.
I gained root access using a different method. However the WiFi still doesn't work. I think it may be that the mac address information was from the backup I flashed from the internet, and therefore doesn't match. I found a guide that tells me how to hex edit a file and put in my real mac address, but it's unavailable under wifi. I don't have the sticker on the back that says it either. How else can I find it?
Turns out the mac address can be anything. I used SN Write tool and an AB DB for my chipset and it still didn't solve the problem. I have no idea what to do. Can anyone help me?
I fixed the issue by grabbing a different backup from some russian website and flashing the system.img and secro.img to it. It now works fine 100%. Thanks
help - link
drsinclair said:
I fixed the issue by grabbing a different backup from some russian website and flashing the system.img and secro.img to it. It now works fine 100%. Thanks
Click to expand...
Click to collapse
Hey man! I have the same problems with my QV 830. Can you give me the link for system.img and secro.img, please?
Hi folks,
Today it's a great day for me : I have successfully patched the kernel to have a 100% working TWRP 3.2.1 for our Maze Alpha 4G.
I have port a Jemmini build for Bluboo S1 and I have patch the kernel to have a working touch panel
I have followed this Thead
For the Maze Alpha 6G version, you can test it and tell me please.
How to flash:
I Fastboot method (must unlock device) :
1- Reboot your phone in bootloader mode : adb reboot bootloader or phone off, press and hold at the same time POWER and Vol+ buttons
2- Connect your phone to your computer with adb/fastboot already installed
3- Unlock your bootloader : fastboot oem unlock (it will erase you data, only data)
4- Flash the recovery : fastboot flash recovery recovery_maze_alpha_4G_twrp-321.img
II SPFlashTool method (no need to unlock device) :
1- Download latest version of SPFlashTools.
2- Execute it and load the provided scatter (the recovery image must be in the same folder as the scatter and must be renamed to recovery.img) then press "Dowbload" button
3a- windows SPFlashTools users : phone off, press VOL+ and connect it to your PC (running SPFlashTool and waiting for phone connetion)
3b- linux SPFlashTools users : phone off and connected to PC , press VOL+ and POWER while your PC is running SPFlashTool (with sudo) and waiting for phone connetion.
Update : you can found here the latest version: TWRP 3.3.0 for MAze Alpha 4Ghttps://github.com/dreambo/android_device_maze_alpha/releases/tag/3.3.0
have a nice day.
Works great on Maze alpha 4G. Thanks.
But I forgot to save original recovery...
super_sonic said:
Works great on Maze alpha 4G. Thanks.
But I forgot to save original recovery...
Click to expand...
Click to collapse
You can get the original recovery from the stock rom designed for SPFlashTool, provided here
dreambo said:
You can get the original recovery from the stock rom designed for SPFlashTool, provided here
Click to expand...
Click to collapse
Thanks. Can you share stock recovery.img, if you have it? I have recovery-verified.img from V05 but I don't know if there is a new update and if size is correct: 11,54MB. Your TWRP recovery has got a size of 14.24MB...
Can you make a small procedure on how to install it? Will help many nOOb's out.
And people need to report back issues and successes !!!! Again I see many questions and people with issues that we seniors try to help out with that end up in no more response which to me is not done and not helping others.
I have a 6GB version that I could test on but at the moment I am using it for other stuff and I can't risk bricking it this week.
Would finally love to start some stuff happening on this phone.
Ok in the process of doing so on my 6GB/64GB version.
edit : congratz I now have a 'phone' that can only go into TWRP . Should have never ever done this!
Says no OS installed ... really nice
Edit 2: after hours wasted was able to get your zipped rom on the Maze but I got no boot with that TWRP, so flashed recovery-verified.img from the 6GB rom from Alpha I had downloaded ... It would then start up but show 4GB out of 6GB. No good but at least all the rest seemed to work. All other effort to get it going back with the proper kernel etc resulted in frustration.
So now to flash the official rom back via their tool... that one got me really frustrated and was completely my fault that I couldn't figure it out. But you know angry, frustrated, must get it back to work, can do this ... After all these years of toying with phones we are so used to pressing 'power and vol+ or vol-' together to make something work. Now in the end I re-read the manual again and saw that you only have to push vol+ and NOT vol+ and power together or it wont go in the mode it should go to make it flash!!
In case this happens : The best advice I can give to people is to download the proper MTK drivers. Search for vcom drivers for MTK and you will find.
Print out the instructions and mark every step you do to the letter. The flashing itself only takes like 3 or 4 minutes
lukesan said:
Ok in the process of doing so on my 6GB/64GB version.
edit : congratz I now have a 'phone' that can only go into TWRP . Should have never ever done this!
Says no OS installed ... really nice
Edit 2: after hours wasted was able to get your zipped rom on the Maze but I got no boot with that TWRP, so flashed recovery-verified.img from the 6GB rom from Alpha I had downloaded ... It would then start up but show 4GB out of 6GB. No good but at least all the rest seemed to work. All other effort to get it going back with the proper kernel etc resulted in frustration.
So now to flash the official rom back via their tool... that one got me really frustrated and was completely my fault that I couldn't figure it out. But you know angry, frustrated, must get it back to work, can do this ... After all these years of toying with phones we are so used to pressing 'power and vol+ or vol-' together to make something work. Now in the end I re-read the manual again and saw that you only have to push vol+ and NOT vol+ and power together or it wont go in the mode it should go to make it flash!!
In case this happens : The best advice I can give to people is to download the proper MTK drivers. Search for vcom drivers for MTK and you will find.
Print out the instructions and mark every step you do to the letter. The flashing itself only takes like 3 or 4 minutes
Click to expand...
Click to collapse
Haha I did the same exact thing..and managed to get it working after flashing it with the spflash tool but the trick is if you have Windows 10 latest version you won't be able to do this..at least I couldn't because of driver incompatibility so in my case:
1 I installed Windows 7 and installed mtk drivers for spflash tool
2.booted into twrp
2.1 if you can't boot into twrp or it doesn't turn on you can still try this
3.Start sp flash tool and download the zip the one(in case of trouble)that the moderator published
4. Load the scatter file and make sure that all of the files and the scatter are in the same folder.
5.click download and leave it like that
6.plug in your phone in fastboot if you can't try one of the following
6.1 just plug it in turned off and monitor spflash tool status
6.2 plug it in holding volume up key (just volume not power)
6.3 in twrp go to boot and boot into bootloader
And the tool should do the rest
If all else fails check the drivers one more time
After all that if you are feeling adventurous flash twrp one more time and do not factory reset through twrp ! Because that was the problem in my case and after you unlock bootloader boot your phone and go through the setup without setting the password because twrp will be locked.
Good luck.
frumac96 said:
Haha I did the same exact thing..and managed to get it working after flashing it with the spflash tool but the trick is if you have Windows 10 latest version you won't be able to do this..at least I couldn't because of driver incompatibility so in my case:
1 I installed Windows 7 and installed mtk drivers for spflash tool
2.booted into twrp
2.1 if you can't boot into twrp or it doesn't turn on you can still try this
3.Start sp flash tool and download the zip the one(in case of trouble)that the moderator published
4. Load the scatter file and make sure that all of the files and the scatter are in the same folder.
5.click download and leave it like that
6.plug in your phone in fastboot if you can't try one of the following
6.1 just plug it in turned off and monitor spflash tool status
6.2 plug it in holding volume up key (just volume not power)
6.3 in twrp go to boot and boot into bootloader
And the tool should do the rest
If all else fails check the drivers one more time
After all that if you are feeling adventurous flash twrp one more time and do not factory reset through twrp ! Because that was the problem in my case and after you unlock bootloader boot your phone and go through the setup without setting the password because twrp will be locked.
Good luck.
Click to expand...
Click to collapse
Wait a sec., missing a couple of things here.
1) Do you have a 6GB ?
2) In case you have a 6GB did you manage to get it working, rooted and all?
Your point 6) well I flashed mine on the latest 64bit win10 ... but.... if the phone is off and you connect the usb cable my phone tried to boot up either in twrp with no com port. Also booting it in bootloader doesn't make the comport visible so you can't flash.
The only way to make mine visible for the flashtool was to press vol+ and then connect the usb cable.
Btw I am glad someone finally responds and spreads information. A very good post! Your first 'thanks' well deserved!
I wonder where the guys are that I was trying to help. Did they throw their phones away or something? Sharing is caring I thought.
I want to root mine to alter the camera settings and the media xml file. I find it strange that our sensor, which is the same as in my wife's Xiaomi's, takes seriously bad pictures.
lukesan said:
Wait a sec., missing a couple of things here.
1) Do you have a 6GB ?
2) In case you have a 6GB did you manage to get it working, rooted and all?
Your point 6) well I flashed mine on the latest 64bit win10 ... but.... if the phone is off and you connect the usb cable my phone tried to boot up either in twrp with no com port. Also booting it in bootloader doesn't make the comport visible so you can't flash.
The only way to make mine visible for the flashtool was to press vol+ and then connect the usb cable.
Btw I am glad someone finally responds and spreads information. A very good post! Your first 'thanks' well deserved!
I wonder where the guys are that I was trying to help. Did they throw their phones away or something? Sharing is caring I thought.
I want to root mine to alter the camera settings and the media xml file. I find it strange that our sensor, which is the same as in my wife's Xiaomi's, takes seriously bad pictures.
Click to expand...
Click to collapse
Sorry forgot to mention I have a 4 GB version but since maze is not providing the roms on their website any further development will be limited..thank God for dreambo he is the only guy doing any work here and like you said nobody is responding to any questions asked..shame really because maze is a great phone with a terrible camera..which drivers did you use on Windows 10? because I tried a hundred of them and non of them recognize my phone..and in adb I can run the command fastboot reboot bootloader but after reboot none of the commands are working .
And yes I did manage to install twrp and root using magisk and I to hope that all those other guys didn't brick their phones
frumac96 said:
Sorry forgot to mention I have a 4 GB version but since maze is not providing the roms on their website any further development will be limited..thank God for dreambo he is the only guy doing any work here and like you said nobody is responding to any questions asked..shame really because maze is a great phone with a terrible camera..which drivers did you use on Windows 10? because I tried a hundred of them and non of them recognize my phone..and in adb I can run the command fastboot reboot bootloader but after reboot none of the commands are working .
And yes I did manage to install twrp and root using magisk and I to hope that all those other guys didn't brick their phones
Click to expand...
Click to collapse
This is the filename I used on Windows 10 VCOM Drivers (All MTK Devices & All Windows OS version).zip I think I downloaded it from XDA somewhere.
Also something you must know https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
Another thing I experienced is that one USB connector is not the other one on a pc. Always connect it to the ones directly on the main board next to the other device outputs like audio etc. and preferably not go through ones that have been extended via a cable like the ones on top of the casing or so. Also a must have application is usbdeview.
Well should be easy to get it going if you can boot it into 'fastboot' then you can try as much as you want to. But djeeeeezzzz the letters are very small when you boot it with a power+volume up . Also check that volume up will toggle between 'fastboot', 'recovery' and 'normal start' and volume minus will select it, not the power button which would be more logical to me.
I might have another go at trying to get it working on my 6GB but it involves having a lot of time and knowing that I will get frustrated. Installing all apps and settings is also a time consuming thing. Once you have TWRP on it it all becomes easy to backup. So many things to test or try.
Maybe dreambo has an idea on how to get mine up to a 6GB one as it is probably only indicated in the kernel.
Anyway I will continue to write down my progress.
Ok more frustration. Done multiple things to try to get this running. It's good to know that the original rom is easy to install again after practice.
Take 1: Try to install clean 6GB rom and immediately install TWRP.
Results: Dreambo forgot 1 step and that is to allow OEM unlock in the developer options. If you do the adb command to unlock press volume up and it will unlock (very hard to see, very small letters on the display in bootloader mode)
Well TWRP starts but immediately I get a message 'mount decrypt data password' which I tried a couple of things but no go. Also googled... different solutions but always ending in a bootloop to TWRP
A possible solution that I read was to create a startup pin .... no go 'pin not valid'
Take 2: Take all the rom files and change the scatter file with the one dreambo provided.... Thought it was successful but ended up with the same Chinese recovery. Trying to figure out why since the filename was correct like indicated in the scatter file. Came to the conclusion that the original file was/is called recovery-verified.img and not recovery.img. Really really strange this one as in the original scatter file it also points to recovery.img. So this one I will have to investigate. Renaming the TWRP file to recovery-verified.img lead to a error during the initial scan of the flashtool.
So moral of the story is that I am back on square 1 and lost 2 hours today (plus putting all apps and settings back) today.
I get a bit lost, is this TWRP method only working with the 6GB or also with the 4GB version?
CYberdog11 said:
I get a bit lost, is this TWRP method only working with the 6GB or also with the 4GB version?
Click to expand...
Click to collapse
There is no fundamental difference between 6G and 4G version.
It must works in boat versions.
If you have issues with SPFlashTool try this (no need to install any drivers on Windows 10) :
Put the preloader.bin (found in the rom package designed for SPFlashTool) in the same folder as the recovery.img without checking it the list of partitions (only recovery must be checked) and click on Download to flash the recovery, as usual.
Perhaps SPFlashTool cannot read by himself the preloader in the EMMC, and we must provide it.
The linux version of SPFlashTool not works at this moment, I do not know why
With the SPflashtool I always get the error:
ERROR:STATUS_DA_HASH_MISMATCH (0xC0070004)
HINT
CYberdog11 said:
With the SPflashtool I always get the error:
ERROR:STATUS_DA_HASH_MISMATCH (0xC0070004)
HINT
Click to expand...
Click to collapse
From another thread:
mmakdz said:
google translate
Hello
I had the same problem, (error BROM ERROR: STATUS_DA_HASH_MISMATCH)
what I did: I use Windows 7 System
1- clear all drivers for smartphones with "usbdeview-2-17"
2- install Drivers "Drivers_Auto_Installer_v1.1236.00"
3- install "PdaNetA4170"
4- use "SP_Flash_Tool_v5.1708_Win" to flash the rom. first flash the preloader alone and then flash the others.
the problem was the bad installation of the drivers, after that everything went well for me.
try it can work for you too.
the mentioned software is easy to find on google
Click to expand...
Click to collapse
dreambo said:
There is no fundamental difference between 6G and 4G version.
It must works in boat versions.
If you have issues with SPFlashTool try this (no need to install any drivers on Windows 10) :
Put the preloader.bin (found in the rom package designed for SPFlashTool) in the same folder as the recovery.img without checking it the list of partitions (only recovery must be checked) and click on Download to flash the recovery, as usual.
Perhaps SPFlashTool cannot read by himself the preloader in the EMMC, and we must provide it.
The linux version of SPFlashTool not works at this moment, I do not know why
Click to expand...
Click to collapse
If there is no difference between the 4GB and 6GB then why did I literally spend days on trying this and documenting what happened?
lukesan said:
If there is no difference between the 4GB and 6GB then why did I literally spend days on trying this and documenting what happened?
Click to expand...
Click to collapse
Do you have the 2 versions of the phone and do you have notice any difference of the flashing procedure ?
dreambo said:
Do you have the 2 versions of the phone and do you have notice any difference of the flashing procedure ?
Click to expand...
Click to collapse
I only have the 6GB version of the Maze Alpha. But you wrote that the procedure should work for both versions. I think I wrote down what happened with mine if I installed TWRP.
I tried both the 'regular' flashing and then the full rom install with the trick to put the files in the directory and rename but both ended up as I've written in my previous post.
lukesan said:
I only have the 6GB version of the Maze Alpha. But you wrote that the procedure should work for both versions. I think I wrote down what happened with mine if I installed TWRP.
I tried both the 'regular' flashing and then the full rom install with the trick to put the files in the directory and rename but both ended up as I've written in my previous post.
Click to expand...
Click to collapse
From times to times, I notice trouble with flashing using SPFlashTools.
First (when I post my first post relating of the root) I use the linux version : no issues it works perfect, no need of any drivers!
Actually, no way to have it working on linux, why I do not know!
I have tried Windows 10 and I notice that we have to provide the preloader to have it working, as I write in my post.
In theory, and only in theory, the SPFlashTool must works the same manner in any phone with a Mediatek SOC.
But in reality, we have notice that with exactly the same phone the flashing procedure works for some users and not for others!
SPFlashTool is a very capricious software, there is no warranty to have it 100% working in any platform, even with the same OS.
dreambo said:
From times to times, I notice trouble with flashing using SPFlashTools.
First (when I post my first post relating of the root) I use the linux version : no issues it works perfect, no need of any drivers!
Actually, no way to have it working on linux, why I do not know!
I have tried Windows 10 and I notice that we have to provide the preloader to have it working, as I write in my post.
In theory, and only in theory, the SPFlashTool must works the same manner in any phone with a Mediatek SOC.
But in reality, we have notice that with exactly the same phone the flashing procedure works for some users and not for others!
SPFlashTool is a very capricious software, there is no warranty to have it 100% working in any platform, even with the same OS.
Click to expand...
Click to collapse
The thing is that I have no issue with flashing the software as I can perfectly flash the original rom. The problem is that when flashing the TWRP file, in both options by the way, so also via method 1, I get a boot loop.