Advice from JY about Malaysk ROM - MTCD Android Head Units Q&A

Hi, I want to use Malaysk ROM but I've seen an advice at JOYING https://www.carjoying.com/Joying-blog/42.html about damaging the unit.....searching in the forum I understand that the problems only affects the MTCB units....Am I right?
Thanks.

Yes, if you have an mtcd unit, you should not worry about this. The custom ROM does not damage anything.

Its a blanket statement for those that do not know what they are doing. Too many people have tried loading the MTCD ROM on a MTCB device which results in bricking it. If you follow the instructions you won't have any trouble.

Hi!, thanks for the imputs....I was worried about damaging my unit...now I'm ready to put Malaysk on my car

sterod said:
Its a blanket statement for those that do not know what they are doing. Too many people have tried loading the MTCD ROM on a MTCB device which results in bricking it. If you follow the instructions you won't have any trouble.
Click to expand...
Click to collapse
More likely the other way around. Trying to install MTCB sysimage on an MTCD. This was happening before there were any customized sysimages available for MTCD.

One stupid question.....Could I flash the stock ROM after trying Malaysk ROM if I decide to go back? I mean if it wont be a problem due Malayks re-partiioning process......
Thanks !

solmer said:
One stupid question.....Could I flash the stock ROM after trying Malaysk ROM if I decide to go back? I mean if it wont be a problem due Malayks re-partiioning process......
Thanks !
Click to expand...
Click to collapse
Yes you can. I Installed around 10 different roms versions on my MTCD unit , including 2-3 Malaysk going back-forth between different roms. No problem. I found that the fastest / easiest way to flash is to reboot in recovery and dont bother use the Settings menu update option at all.
I even flashed another RK3188 device's kernel (unpacked rom, swapped kernel and repack) and got away with it lol, I could'nt see the screen anymore but I managed to enter recovery and use the good button combination without the screen.

XD XD XD, woops a screen blackout.....that's scary
Flashed the Malaysk ROM and I like it, need more time time to test the ROM. One thing I like so much is the CarMod Launcher.....BTW, I've try to find the CardMod launcher at the Google Play and over Internet but I can't find the page ...Any idea?
Thanks again

I forgot to ask one more thing..... I've noticed that in the ROM is included the xposed framework, I was reading a few days ago about xposed and as far as I know it's not working....Am I wrong?

Related

Stop flashing until usb problem is fixed...

Hi everyone,
Just a word of advice: Rooting + Flashing ROMs for the Desire may og may not brick your devices. As you can see in this thread http://android.modaco.com/content-p...-usb-connectivity-etc-and-root-a2sd/page/540/ we are quite a few with bricked devices - and no way to un-brick them so far.
Nobody yet knows what might have caused this - maybe Apps 2 SD.
I would advice for everyone to wait flashing any further until this issue is clarified!!!
Thanks for the heads up. Not been flashing much as of late but was planning to try out a different ROM. Does this problem affect all customised ROMs or just certain newer builds?
Mastoid said:
Thanks for the heads up. Not been flashing much as of late but was planning to try out a different ROM. Does this problem affect all customised ROMs or just certain newer builds?
Click to expand...
Click to collapse
It is about as random as can be is the best way to decsribe it! Some people flash many times and have no bother, others flash once and the phone is bricked
It so far doesn't seem to be exclusive to any particular rom, people speculate it may be A2SD, but others think it's the actual rooting process. To be honest, no one actually knows why it's happening and how to fix it. All that is certain is that more and more people are posting with the issue.
It could be any ROM.
Sent from my HTC Desire using Tapatalk
socktug said:
It is about as random as can be is the best way to decsribe it! Some people flash many times and have no bother, others flash once and the phone is bricked
Click to expand...
Click to collapse
I take it you have a bricked phone then? I hope this gets resolved soon especially for those who might have turned their phone into nothing more than a paper weight.
It so far doesn't seem to be exclusive to any particular rom, people speculate it may be A2SD, but others think it's the actual rooting process. To be honest, no one actually knows why it's happening and how to fix it. All that is certain is that more and more people are posting with the issue.
Click to expand...
Click to collapse
Since many people have reported this issue, is there not some kind of pattern emerging? Hopefully we can isolate the problem to something in particular, as you stated, whether it be caused by the rooting process, Apps2SD, or a USB driver issue.
For those who are experiencing this, might be an idea to post computer specs, what ROM they attempted to install, and other associated things so we can narrow down the problem.
I've flashed loads so far and have no issues - finally got a ROM I like at the mo so will leave it for now...probably
My guess its the recovery, its not installed to the phone and its very sensitive for connection: do not move phone or cable during flash.
It happens that I flash several time in a day, I have MCR r3 A2SD+ now and I never had such a problem...
The problem is APPS2SD related.
DocRambone said:
My guess its the recovery, its not installed to the phone and its very sensitive for connection: do not move phone or cable during flash.
Click to expand...
Click to collapse
I don't mean do break up the good mood in this thread. But if you have a problem/issue with this, please follow the thread on MoDaCo - any kind of input is welcome in this debate
BTW: If any moderator reads this: Can we make this sticky until problem is solved?
Could this be most of the issue happened to be with people with .80 bootloader??
kuailan said:
Could this be most of the issue happened to be with people with .80 bootloader??
Click to expand...
Click to collapse
This problem has nothing to do with the 0.80 bootloader. It's all to do with APPS2SD, that was discovered weeks ago on MoDaCo.
abc27 said:
This problem has nothing to do with the 0.80 bootloader. It's all to do with APPS2SD, that was discovered weeks ago on MoDaCo.
Click to expand...
Click to collapse
There are people on modaco who have bricked their phones, and were not using A2SD.
I managed to brick mine by knocking it during the flashing process. I did not use A2SD.
socktug said:
I managed to brick mine by knocking it during the flashing process. I did not use A2SD.
Click to expand...
Click to collapse
I think DocRambone is onto something here... he stated a few posts back that he thinks it may be down to the sensitivity of the connection/cable while the phone is in recovery mode during flash, and you mentioned that you bricked your phone while knocking it while flashing in recovery?
From my experience, whenever I attempted to flash Desire cutoms ROMs, I did not move the USB cable at all and it worked fine. Had the phone placed on the desk and kept it stationary while flashing. I have not had any problems with Apps2SD or USB driver issues either.
I did mine from the laptop and the phone on the sette beside me. lol. I initially thought I'd knocked it and the battery came out, but I'm fairly sure now that the battery wasn't the problem, it fits too tight to come out with a simple knock of the hand.
Anyway, all I can say is if you brick it, and can unroot it, and bought it at the carphonewarehouse, you will be fine! They took it back and gave me a new one, no questions asked. I'm not going near a root process untill there is a fix now
Afaik there are two possible solutions for the issue
1. someone needs to security unlock the spl, so that we are able to use all fastboot commands
2. In the modaco thread someone found some helpfull kernel commands
so, if anyone either is experienced in spl modifications or capable of programming c for the kernel commands, pleade send me a pm
millen said:
I don't mean do break up the good mood in this thread. But if you have a problem/issue with this, please follow the thread on MoDaCo - any kind of input is welcome in this debate
BTW: If any moderator reads this: Can we make this sticky until problem is solved?
Click to expand...
Click to collapse
I have read the last few pages of the MoDaCo thread but still I am not clear about the issue.
Is it there are some unknown factors causing the root process to brick the USB? But still you can flash stock RUU in fastboot?
you can flash back to stock cause fastboot is still working and so you can flash the signed stock roms (thoose with release keys or the testrom with testkeys) but due to the fact that adb is nomore working you can't enter the custom recovery to flash cooked roms
millen said:
I don't mean do break up the good mood in this thread. But if you have a problem/issue with this, please follow the thread on MoDaCo - any kind of input is welcome in this debate
BTW: If any moderator reads this: Can we make this sticky until problem is solved?
Click to expand...
Click to collapse
Just send a message to one of the mods, he sure will make that post sticky
--edit---
man, theese guys are fast, now it's sticky
Easy and apparently safer method of rooting?
Not sure if anyone's seen this on modaco but using the tiny core linux has worked well for me, with 3 flashes from a stock HTC ROM and currently running eViL De-SiRe after trying paul's initial boot then the Cyanogen Port.
May flash again tonight with the Kernel release the ROMs will get better and better.

Touchscreen not working after root, but S-Pen works fine

I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
Thanks,
Reffu
Hi,
same issue here. Today the touchscreen stopped working suddenly after i flashed the Android Revolution HD 5.0 Rom yesterday. However, the S-Pen is still working fine. Installing other ROMs and the Stock ROM via Odin did not help. Issue allso appears in Touch-enabled-Recovery.
I see no reason, why this should be a hardware issue, although my N8000 came back from service a few days ago, where they also replaced the screen and digitizer.
Had anyone this issue before and was abled to resolve it?
Greets
I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2
to read this as a Note 10.1 newbie is not very encouraging. are there any similar facts between all of you like
which Note model do you have
how did you jaibreak (which method)
which rom did you have before
which rom do you have now
how did you flash a new rom
...
is there a way to find out whether the touchscreen is really "dead for touch"?
This is a bit scary - my Note 10.1 is arriving today, and I plan to root it at a minimum. I actually don't mind Touchwiz all that much on my Note 2 (which is running CleanROM ACE), so I think I might just root the 10.1 for now.
So restoring completely back to stock (via Odin) doesn't fix it? That is really odd that ROM-ing this thing might cause a hardware failure...
jiggyman said:
I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?
kkretch said:
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?
Click to expand...
Click to collapse
Did anyone solve this, I'm having the same problem.
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
Just curious - did you just root, or did you root and install a ROM?
I am only rooted so far - haven't felt the need to ROM yet - partially due to worries about this happening. I bought a refurb from Best Buy and only get 90 days of warranty.
reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
If they say you got a new one, you got one. They'll tell you otherwise if there's an issue over the phone.
But I wouldn't be afraid of ROMs, but to be more diligent and wise when it comes to choosing them. It's like choosing a poisonous mushroom versus an edible one to make stroganoff or stir fry. If you know what to avoid for the next time and follow the correct process to doing the root and flashing, there will not be an issues.
This is from someone who has soft-bricked my first tablet and learned how to unbrick my SIM-less Captivate and Note 10.1. It's how you apply the method and how much attention you practice not getting stuck into these situations is what matters. Especially since I bricked my tablet via experimentation and un-bricked it on the same day with ease.
It's not some big complex deal of rocket science or something only the mere geniuses can do, its how you perceive yourself and how you act. If you believe that you will suck and brick it to kingdom come , it will happen intentionally or subconsciously.
In this case, it was a freak accident where the file/s accessed and deleted the wrong files which allowed for capacitive touchscreen use, and it should be reported to x developers if you have not done so already.
I have rooted and used the Revolution HD rom, the Rom where you customize the colors of the bar/other things, and on the Captivate, the AOKP Collective. I further customized the latter with the Xperia launcher as it zips.
Did anyone find a repair for this besides replacement? My Note 2 is doing the same thing now.
Has anyone found a fix for the touch screen not working yet??
Anyone have any ideas?
Technicians input for touch problem
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain that follows the instructions on the mod sites exactly as shown step by step will never have a problem, all those that do end up with paper weights or bricks didn't follow the instructions in numerical order.
Believe it or not even if after you have modded a rom and brought it back to standard they know it has been modded as they have a list of problems associated with repairs after roms have been modded so you are only fooling yourself they don't.
Same as the smoker that tells his Dr he has given up even though all the symptoms prove he really didn't.
So in my expert opinion if you play with modding and stuff it up why should you be eligible for a warranty claim ? The manufacturer has sold you or supplied a working item that you decided to f_ck around with and because of your stupidity expect some one else to pay for it.
I am not saying don't mod your phone with all the great roms out there but please to save yourself a lot of pain and cost some poor smuck trying to run a business in these economic times a lot of out of pocket from sending items back for replacement or warranty plus the time it takes to do all the paperwork and such, please please please read the instructions 300% or triple check you are doing everything exactly as the instructions say and you will be enjoying all the new benefits of that customised rom and laughing at all the noobs stuffing up their brand new device from not doing so.
I know this won't fix your problem but reread that last bit it was your problem as you are to clever to follow some one else's instructions
anyone have solution regarding this issue, mine have issue also, can anyone spare how to fix it without changing hardware?
---------- Post added at 06:47 AM ---------- Previous post was at 06:28 AM ----------
i hope anyone can solve my issue with touch not responding
WOW.. on TOPIC Flashing .pit might help ???
Gardum said:
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain
Click to expand...
Click to collapse
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck
erica_renee said:
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck
Click to expand...
Click to collapse
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir
popohunters said:
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir
Click to expand...
Click to collapse
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .
erica_renee said:
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .
Click to expand...
Click to collapse
thanks sir, im done the flashing with pit files+ official firmware but touch screen is still missing, is there a modem file for touch screen maybe i missed it while its in downloading process before i brick the touch screen
any hope out there?????
confused and need help
i have a n8000 , base band version N8000XXCLL1, my touch screen stoped responding while playing a game , only Spen works , tried resetting , but no help, I'm a no-voice when it comes to programing and need a step by step guide >>>> many thanks in advance for all your help
reffu said:
I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
I got the same problem after rooting my phone.... I used the following method and got ride of that Problem. ..
type this star code in in it Phone dialler *#2663#
Now you should see "TSP"
<update>
TAP on TSP ......it will take 5 seconds only....
......
NOW ENJOY ☺☺
Click to expand...
Click to collapse

[ROM][ODIN] P500VPBMB3 Sprint 4.1.2 Firmware

P500VPBMB3 Sprint 4.1.2 Firmware
For some unusual reason there is little to no development for the SPH-P500 and absolutely ZERO official firmware available for the Sprint model. This means, if you soft brick the tablet trying to install something you should not have, you have no easy way of getting back to the stock firmware. In addition, getting to the 4.1.2 version of the firmware is a royal pain due to the massive amount of "PATCH CHECKS" and assert checks built in to the OTA update. This means any deodexed system or a number of other reasons will be rejected if you try the OTA update while on non-official or approved firmware. So, for your convenience, I have compiled a simple ODIN-Flashable TAR file which will jet you up to speed installing the latest official Sprint 4.1.2 firmware.
Details:
P500VPBMB3 Stock w/ MB3 Modem
Package Includes: BOOT, RECOVERY, SYSTEM, MODEM AND CACHE ZONES
Download:
P500VPBMB3 Sprint 4.1.2 Firmware
Password on the archive is: www.mobiletechvideos.com
How To Flash:
BACKUP YOUR FILES AND DATA BEFORE FLASHING...ALWAYS. First extract this file using WinRAR or a program capable of extracting a RAR package as the package inside it is the TAR file you need. This was done to save time on the download. Once extracted, using ODIN, select PDA and choose this file. Now place your tablet in DOWNLOAD MODE by having it powered off, then power on by holding POWER and VOLUME DOWN until you see the on-screen text come up. Release the buttons and press VOLUME UP to enter DOWNLOAD MODE. Now click START on ODIN. Once completed (takes around 10 minutes), it is advised to enter RECOVERY MODE and perform a FACTORY DATA RESET for the best bug free experience since I don't know what ROM you are flashing from.
Did this help you out? Great, I'm glad it did! Click that THANKS button next to my name if you have the time. Please note, if you find yourself in a hard/soft brick situation of any type on any advice, give me a shout via PM or email through the contact page on our site. We also offer repairs on a number of other issues.
27 downloads and nothing? I'd love some feedback so others can be confident in the firmware.
It´s a disease from all P31XX and P51XX useres don´t hitting the thanks button and don´t giveing feedback... maybe they don´t want any support.... (?)...
i don´t have a P51XX - i can´t give other feddback then this... sorry....
Haha it seems that way! Well thanks for your response. Nice to hear from somebody about this. For some reason the Tab 2 10.1 forum members seem to be dead but want development anyhow without any input!
There are a lot of people here in a german forum there is mostly nobody ...
i hope you get some feedback! if not: there is not problem first things that will reported are problems
Haha, how true! No news is good news right?
problem and feedback if it works...
Hi. I am pretty new here (although I have been a member for a while, I have not really been active). I do have a Sprint Samsung Galaxy tab 2 10.1 inch display model P500VPBMB3. Perhaps I can try out what you are talking about if it helps me with my problem below and then I will be more than happy to give you feedback.
PROBLEM
I never really rooted a device before but I am at a loss here since the current version of Android that I have on my device is 4.1.2 . It's working OK but I run out of space very often since I only have 16GB of main memory. I would love to upgrade to 4.2.x so that I have the option of storing apps on the external SD card. I am not clear exactly what you are giving us here on your thread. If you can explain it to me and especially if it does what I am outlining above I would want done, I would love to give it a shot and then give you some feedback.
Either way thank you for helping is Sprint tablet people whether or not what you have above will help me.
Thanks
shmusie said:
Hi. I am pretty new here (although I have been a member for a while, I have not really been active). I do have a Sprint Samsung Galaxy tab 2 10.1 inch display model P500VPBMB3. Perhaps I can try out what you are talking about if it helps me with my problem below and then I will be more than happy to give you feedback.
PROBLEM
I never really rooted a device before but I am at a loss here since the current version of Android that I have on my device is 4.1.2 . It's working OK but I run out of space very often since I only have 16GB of main memory. I would love to upgrade to 4.2.x so that I have the option of storing apps on the external SD card. I am not clear exactly what you are giving us here on your thread. If you can explain it to me and especially if it does what I am outlining above I would want done, I would love to give it a shot and then give you some feedback.
Either way thank you for helping is Sprint tablet people whether or not what you have above will help me.
Thanks
Click to expand...
Click to collapse
You will actually want to look into custom recovery combined with a custom ROM to enable this type of option. What I have provided here is a stock firmware (stock operating system). This is actually already what you have installed on the device.
connexion2005 said:
You will actually want to look into custom recovery combined with a custom ROM to enable this type of option. What I have provided here is a stock firmware (stock operating system). This is actually already what you have installed on the device.
Click to expand...
Click to collapse
Thank you very much for your prompt reply. You seem to be a helpful sort of person. I am sorry to be so dense but I have no idea what those things are. Is there a place where I can, sort of begin from scratch to learn all about these things or can you please fully explain what I need to do here?
I get that yo said that what you are offering is what I already have. What I don't understand is what exactly what to look for. I do know that if I install the wrong thing, I can brick my device. What I don't know if how to find what I am looking for. I already tried it in the search box-that's how I got to your thread.
This is honestly a very tough section as the P500 is a rare unit that has little to no development. You are in the right sub-forum but finding any mods for your unit may not be possible at this time unfortunately.
Thank you, thank you, thank you!!!!! You can root with Kingo root and make modifications with xposed. I just have been so busy with work.
I will flash this when I have time. Now I can be more risky with flashing because I can now go back to stock ROM.
Sent from my SM-N900P using Tapatalk
Android-Andi said:
It´s a disease from all P31XX and P51XX useres don´t hitting the thanks button and don´t giveing feedback... maybe they don´t want any support.... (?)...
i don´t have a P51XX - i can´t give other feddback then this... sorry....
Click to expand...
Click to collapse
Hello, I know its been almost a year, but I tried to flash this ROM and get stuck after the tab reboots with the message "POWER RESET or UNKNOWN UPLOAD MODE", is there anything I can do to restore the tab (I did not do any backup).
Thanks a bunch
Do you have the Sprint model? If so, try re-downloading it and flashing again. Afterwards, perform a factory data reset.
connexion2005 said:
Do you have the Sprint model? If so, try re-downloading it and flashing again. Afterwards, perform a factory data reset.
Click to expand...
Click to collapse
The tab comes from China but in the options i've seen SPH-P500 so I supposed it was a model made for Sprint.
I did flash again and reset factory but nothing changed.
meresis said:
The tab comes from China but in the options i've seen SPH-P500 so I supposed it was a model made for Sprint.
I did flash again and reset factory but nothing changed.
Click to expand...
Click to collapse
That is definitely unusual though the fact it came from China. This likely is NOT the right firmware for your model. The back of the unit should have the model number. See what it says...
connexion2005 said:
That is definitely unusual though the fact it came from China. This likely is NOT the right firmware for your model. The back of the unit should have the model number. See what it says...
Click to expand...
Click to collapse
Indeed the back says P5110 ... Chinese devices ... Thanks a lot ! :good:
P500
Wow!! I made a mistake!! I bought this tab to have some fun rooting and installing custom roms. I should have checked the forums first to see if there was any support. Thanks for what you've provided here. I'm going to at least try to root and install xposed.
I have a sprint gtab2 10.1 that's out of contract, so i'm willing to start working on things if needed.
if we no longer need to use the Sprint data can we flash a SPH-P5100 rom for wifi only ?
resurrecting an old thread. Need to find the original firmware for sph-p500. This appears to be it, but I can't find or get the password to the .rar file. I can't find the firmware anywhere else after a TON of google searches. any help appreciated in either getting the password to the .rar file, or a different place to download the firmware.

MTCD_MX recovery.img (TWRP)?

Hi, developers and users of mtcd units... I'm looking to change the recovery of my HU (mtcd_mx) with TWRP recovery and I dont konw if TWRP supports our MTCD units.
I'm interesting for this recovery because with this I can do a full backup of HU, and I want to keep my hu safe. I have experienced TWRP on my phone and this kind of recovery it's a big deal...
So is there a twrp support for mtcd?
Thx!
I miss it too, but I don't think there's a compatible version for our HU
Yeah...
Right now I finished and sent a letter(mail) to TWRP team, to have mercy for us and start/extend in future their project on any kind of HeadUnit(MTCB/C/D)... Maybe someone will read my words and maybe we hear good news!
ZeligPC said:
I miss it too, but I don't think there's a compatible version for our HU
Click to expand...
Click to collapse
I'm hoping for TWRP too. This would make things easy.
I have come across some older versions of TWRP for these similar units, but I do not know if they are still compatible. I believe there was a TWRP 2.7 I saw but this was back in 2014.
I imagine since the hardware is still basically the same, if we had the proper memory locations and the driver source was still the same it would not be too difficult to compile a credible version.
EDIT:
I came across these guys, they were pretty deep with this stuff, granted there have been some changes since 2014, but they seem to know these systems very well.
http://freaktab.com/forum/main-category/freaktab-downloads/11780-twrp-2-7-0-0-for-rockchip-s
Also, here is a guide on custom compiling of TWRP.
https://forum.xda-developers.com/showthread.php?t=1943625
XX
Its been done before on MTCB/C units (theres a thread about it in the MTCB forums), every time you want to flash an MCU you have to re-flash the std recovery so pretty pointless. To make TWRP compatible youd have to have a fair bit of knowledge about the STMicroelectronics MCU these devices use and I dpobt anyone at TWRP has that.
I´m working in a trwp version based on twrp from h**ttps://github.com/Magendanz/android_device_rockchip and already get to boot twrp in my device (mtcd-xrc px3) with android 7.1.2 but can't get to mount partitions from internal memory.
Any help it will be apreciated.
tuga_z said:
I´m working in a trwp version based on twrp from h**ttps://github.com/Magendanz/android_device_rockchip and already get to boot twrp in my device (mtcd-xrc px3) with android 7.1.2 but can't get to mount partitions from internal memory.
Any help it will be apreciated.
Click to expand...
Click to collapse
You realise if you get it working you wont be able to flash MCUs ? Youd have to reflash the original recovery to flash them.
typos1 said:
You realise if you get it working you wont be able to flash MCUs ? Youd have to reflash the original recovery to flash them.
Click to expand...
Click to collapse
Yes but it's easy to do it with the app Rashr
tuga_z said:
Yes but it's easy to do it with the app Rashr
Click to expand...
Click to collapse
Ok, cool.
Personally I cant see the benefit of TWRP on these units, dont get me wrong, I use TWRP on my phone, just cant see the point here, thats just my opinion though.
Finally I got to work. After doing a lot of testing on the twrp.fstab file it worked fine.
If anyone is interested in how I got it, just ask. Now I will try also in a mtcc-kld6 unit.

The struggle... (64 bit recovery porting)

I've got the Oukitel WP16 which a 64 bit and has an octa-core MediaTek Helio P60 MT6771V on Android 11. Actually a pretty decent rugged phone. Originally tried to root it through fastboot and bricked it about 2 weeks after getting it. For the life of me, I couldn't bring it back to life. Finally after 4 months of it just sitting in a drawer, I went about flashing it to bring it back to life a little differently than I was before and it stuck. Very thankful that it was working again because in those months I had destroyed 3 of your average break if you touch them phones. However me being me, getting it going again wasn't enough. So I gave rooting it a try again. Got it! Rooted with Magisk. Now because I have one of those devices I believe is under rated and under developed, I can't find any kind of development done on it whatsoever and want to build/port TWRP so I'm able to try a GSI ROM. My problem is that every tutorial I read or watch has nothing like what is my stock ROM. Either names of files are different or I find the files in other folders, I've got more folders than what I'm trying to port, and, I would need to double check again, but I wanna say that I've even found them in different partitions. So my question is, what do I do? Like fstab is not in the recovery but in something else. That something else that has fstab in it, my port doesn't have that folder at all. And there are others like that. I've tried several, I repeat SEVERAL different tutorials and cannot figure out what to do. I know it's beyond the capabilities of the tool, but I even tried one of those Hovatek port tools. Obviously didn't work because of the kernel. So to say I'm lost is an understatement. This isn't the first phone I've tried this with. Had another 64 bit with the same chipset that actually had a unofficial TWRP built for it. But when it came to try to port a ROM, I was left with files in different folders and things that weren't in the ROM i was trying to port. I eventually just have up because I kind of had to since scuba diving with the phone here in the Mexican Caribbean finally took it's toll on the phones external hardware. But yeah, back to my only question. What do I do in this situation? I'm mainly concerned about it because this WP16 has a night vision camera on it which I use quite often and don't want to lose that. Recovery has nothing to do with the camera but the ROM I'd like to port will. So figuring out what to do with the recovery could eventually lead me to my answer with the ROM. Anyway, kind of a long winded explanation just to get to what may seem like a simple question to some. Any help would be greatly appreciated.
finnroth69 said:
I've got the Oukitel WP16 which a 64 bit and has an octa-core MediaTek Helio P60 MT6771V on Android 11. Actually a pretty decent rugged phone. Originally tried to root it through fastboot and bricked it about 2 weeks after getting it. For the life of me, I couldn't bring it back to life. Finally after 4 months of it just sitting in a drawer, I went about flashing it to bring it back to life a little differently than I was before and it stuck. Very thankful that it was working again because in those months I had destroyed 3 of your average break if you touch them phones. However me being me, getting it going again wasn't enough. So I gave rooting it a try again. Got it! Rooted with Magisk. Now because I have one of those devices I believe is under rated and under developed, I can't find any kind of development done on it whatsoever and want to build/port TWRP so I'm able to try a GSI ROM. My problem is that every tutorial I read or watch has nothing like what is my stock ROM. Either names of files are different or I find the files in other folders, I've got more folders than what I'm trying to port, and, I would need to double check again, but I wanna say that I've even found them in different partitions. So my question is, what do I do? Like fstab is not in the recovery but in something else. That something else that has fstab in it, my port doesn't have that folder at all. And there are others like that. I've tried several, I repeat SEVERAL different tutorials and cannot figure out what to do. I know it's beyond the capabilities of the tool, but I even tried one of those Hovatek port tools. Obviously didn't work because of the kernel. So to say I'm lost is an understatement. This isn't the first phone I've tried this with. Had another 64 bit with the same chipset that actually had a unofficial TWRP built for it. But when it came to try to port a ROM, I was left with files in different folders and things that weren't in the ROM i was trying to port. I eventually just have up because I kind of had to since scuba diving with the phone here in the Mexican Caribbean finally took it's toll on the phones external hardware. But yeah, back to my only question. What do I do in this situation? I'm mainly concerned about it because this WP16 has a night vision camera on it which I use quite often and don't want to lose that. Recovery has nothing to do with the camera but the ROM I'd like to port will. So figuring out what to do with the recovery could eventually lead me to my answer with the ROM. Anyway, kind of a long winded explanation just to get to what may seem like a simple question to some. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Your device already have TWRP [Firmware version: OUKITEL_WP16_RU_V04_20220621 ] but you not need Custom Recovery for install GSI. Use stock recovery.
About GSI with a night vision camera support so is much expensive solving that. You can try but need very experience and patience of the tests and solutions.
lopestom said:
Seriously? Thank you! I'm guessing the link is gonna be in 4pda being that it's Russian? I've spent a month searching and haven't found anything whatsoever. And since I don't read Russian, I always overlook 4pda even though it's been a great resource in the past. And yes, I'm aware you don't "need" custom recovery for GSI's. It does make things a little easier for me though.
Click to expand...
Click to collapse
The recovery issue will be solved since there is a recovery out there. That still doesn't solve the mystery and problem i have of files being in different places though. In that case what do I do if the files isn't in the same place in the port as it is in the stock, or the other way around? Add the stock file to the same folder it is in for the port? Or should I make a new folder in the port that's name is the same as in the stock? If neither, what do I do?
finnroth69 said:
Seriously? Thank you! I'm guessing the link is gonna be in 4pda being that it's Russian? I've spent a month searching and haven't found anything whatsoever. And since I don't read Russian, I always overlook 4pda even though it's been a great resource in the past. And yes, I'm aware you don't "need" custom recovery for GSI's. It does make things a little easier for me though.
Click to expand...
Click to collapse
No! Search my repository in the github in the release option.
finnroth69 said:
The recovery issue will be solved since there is a recovery out there. That still doesn't solve the mystery and problem i have of files being in different places though. In that case what do I do if the files isn't in the same place in the port as it is in the stock, or the other way around? Add the stock file to the same folder it is in for the port? Or should I make a new folder in the port that's name is the same as in the stock? If neither, what do I do?
Click to expand...
Click to collapse
As I wrote before, it is very difficult to solve issues like the original stock ROM camera. There are even one or two people who managed to get this to work.
Now what you don't understand: If you want a Custom ROM, use GSI and adapt, solve, analyze and test by changing some stock ROM files in GSI. You must understand that you need experience and time. You can even compile a Custom ROM - any GSI - specifically for your device. So you just need to have the source code of your device, have the GSI source code and know how to compile the file so that you can do the tests. Again, you must understand that you need experience and time.
If you haven't researched what is GSI and still think that Custom ROMs portability that happened before until Android 7.1 then look, read and update yourself.
In your questions, be as detailed as possible. You write a lot of parts and you scramble the words.
As for having GSI normally I already wrote where there is an instruction to install and you follow. As for TWRP, look it up on my github.
As for solving something in the GSI, if you managed to install it and still used the phh options to try to fix any bad part, then it is only you who will be able to solve any error/adaptation/bug/extra installations that there.
Trust me when I say I understand what you're saying. I have done some testing I have watched tutorials, I have studied. but everything that I have seen is basically switching a file from a folder on the stock ROM to a folder in the ported ROM with the same name as what's in the stock ROM, and possibly adding a little script to something. What I'm trying to figure out is what I asked. Fstab is not in recovery on my phone's stock ROM. It is in something else. But fstab is in and a part of recovery for TWRP. So even though there might be a TWRP for my phone doesn't help me to know if I should be creating that same folder that's in my stock ROM in the ported one for fstab or other files that are like it. I have downloaded the TWRP from your profile and I've gone to the 4pda and discovered that you're the dev who ported it with and without encryption. Nice work and thank you! I would like to move beyond being a flash baby though. So I'm simply trying asking that one specific question to help me learn because it is something I am lost on. Whether it is to port recovery, port a ROM, or whatever, I don't know what to do when the location of the files I need to port from the stock aren't matching with the with the location of the files in the port itself. Fstab is just one example. I'm gonna send you a friend request. Later when I fire up my laptop, I'll take screenshots to physically show you exactly what I mean. Please be patient and don't get upset at me for trying to learn. As well as please take your time in responding. It's no rush since I've got a business to run and this is something I'm trying to teach myself on the side. It really is something I'm lost on, and if I'm lost on it, how many others has it confused as well?
As for the camera app issue. We can forget I asked that also. I understand completely what you're saying about it being far beyond my reach right now. Thank you for the heads up on that.
Mr. Lopestom can you please help me with your recovery images? I cannot seem to get any of them to boot. I've tried the with script found on 4pda, without that script, I've tried flashing an empty vbmeta, but nothing is getting the images to boot. See attachment for script I'm talking about. Attachment only shows me running it, but I have tried without.
What sense does it make to flash an empty VBMETA ? You typically pull the existing VBMETA and pass this file to Fastboot what rewrites 2 bytes in that file.
finnroth69 said:
Mr. Lopestom can you please help me with your recovery images? I cannot seem to get any of them to boot. I've tried the with script found on 4pda, without that script, I've tried flashing an empty vbmeta, but nothing is getting the images to boot. See attachment for script I'm talking about. Attachment only shows me running it, but I have tried without.
Click to expand...
Click to collapse
The problem is not in the vbmeta file. You can use this one if you can: Post in thread 'Looking for a walkthrough on installing a custom ROM on a BLU G90 PRO' https://forum.xda-developers.com/t/...om-rom-on-a-blu-g90-pro.4253737/post-85180967
The big fact is that the company put a recovery.img stock file inside /vendor/etc/ and you should know how to deal with it. So only removing this recovery.img and repacking modified vendor.img made by u; install that in your device so you can have TWRP.
jwoegerbauer said:
What sense does it make to flash an empty VBMETA ? You typically pull the existing VBMETA and pass this file to Fastboot what rewrites 2 bytes in that file.
Click to expand...
Click to collapse
I'm not sure to be honest with you. Like I told lopestom, I'm just trying to teach myself as I can in my free time. A lot of what I do is imitate what I see or read. While reading post about flashing twrp i had read something about flashing an empty vbmeta file.

Categories

Resources