Failed editing of EBR, in trouble now. - Android Q&A, Help & Troubleshooting

Short story. Bought a local cheap china tablet based on MTK6852 chipset with 8GB internal storage, running KitKat 4.4.2, but only 500MB available for apps. Being a complete android noob, but a savvy computer guy, started investigating and playing with link2sd, which did not work. Eventually found out I can simply edit EBR1 and EBR2 and that will increase internal storage to ~4G which would be great. Again, being an android noob, I installed droid tools for MKT, did a scatter backup and a whole system backup.
then, just when I was about to manually edit EBR files, I discovered this app: youtube video id: V9aFPNcwajw (sorry as I a new poster I am unable to post outer links) Being super happy about it and forgot to read comments I just went to run it. It failed. Later I discovered its only for MTK6577 devices and it most likely messed up my EBR.
Now I am stucked; I cen get into recovery mode, but factory reset does not work, leading into "mount /data error force format /data" error (my guess is because my EBR is messed up recovery cannot find /data folder?). SP flash tools worked and I have downloaded a couple of different EBR files, but none worked.
The biggest problem: my recovery seems to be incorrect, no idea why thou. All I see is: firmware.info mount.info, phone.info, scatter.txt file and a big "system" folder. Now to do a SP flash tools ready file I would have to select "prepare blocks for flash" in the MTK droid tools, but that requires "files.md5" file, which I dont have (again, no idea why not as I've done a complete backup from same droid tools, unless I forgot to thick something?)
Also the company that makes this tables, actually brands them, refuses to send me any files and wants me to bring in the tablet.
Is there anything else I can do on my own or its time for repair service? My guess is I cant do much without EBR files, but have no idea where to find the correct ones as this is a small country based company and I have yet not found under what other brands it is sold.

Related

[Q] Mlais MX28 mounting /system read-write

Please excuse asking questions as a first post, but I'm at the stage where I'm stumped and a search isn't helping.
Mlais MX28 fresh from MM pre-rooted. Managed to get the ROM backed up and CWM installed with Rua1's excellent MTK Droid Root & Tools. However, removing the Chinese useless (for me - no offence intended) apks proved not to be happening from the one-click button in that excellent piece of software. No bother, thought I, I'll just use adb and remove the relevant apks manually from /system/app. Famous last words.
Here's where things get really odd. I can mount root fine using the usual procedure but mount -o rw,remount /[email protected] /system works once and once only. Even stranger is that the first time gets you a rw mounted filesystem for about 10 seconds, at which point it gets remounted ro and no amount of faff will get it back to rw without a full power off and restart. All it does is spits out
Code:
mount: Read-only file system
Any ideas, please? I suspect there's some write protection going on but I haven't the first idea where to look.
Edit: Having done a little more searching on this issue, it seems there's a few Acers with the same behaviour, caused by a compiled-in kernel option. Looks like it may well be "wait for a custom ROM" is the answer. Not sure if rolling our own is possible unless anyone knows where to get the Mediatek sources for this device from?
Anyway, :good: to all those who have viewed my question. It's appreciated.
Edit 2: There's an S4UI ROM on needrom<dot>com that is rumoured to have solved this issue. Note that if you have installed CWM using the "magic" MTK Droid Root & Tools method, chances are you can't mount /system rw using ADB in CWM either - I suspect they share the same kernel. I haven't tried the S4UI ROM myself as the recovery needed to install it seems to be in Chinese. Possible solution for anyone with a grasp of that language and script but that someone isn't me
[Q] Mlais MX28 Recovery in Chinese Any help with translation
Hello, bud Any help yet also gut stuck in this.
I'm afraid not at the moment. The S4UI ROM on needrom does indeed enable /system rw but the WiFi and Bluetooth will not activate. Replacing mtk_stp_wmt.ko in /system/lib/modules/ with the version from the stock ROM that should fix this issue, doesn't fix this issue. It's a shame as the S4UI ROM is rather pleasant to use and if I could get that fully operational I expect I would be quite happy with this device. Oddly, the stock ROM came back with a different MAC for the WiFi. As I restored from a backup created with MTKDR&T, this is a little perplexing.
I'll update if I find any more clues.
{Possible solution/nasty hack]
Here's a way to get full /system access on the stock ROM. It requires
Clockwork Mod recovery
ADB
Courage
Install/create Clockwork Mod with MTKDR&T. Now boot into recovery by holding Vol+ and power until the boot selection screen appears and then select recovery with Vol+ and press Vol- to accept.
Do not mount /system in CWM.
On your ADB equipped computer, start
Code:
adb shell
Now issue the following at the root shell prompt:
Code:
tune2fs -e continue /dev/block/mmcblk0p5
Reboot the system and enjoy the power of full root.
This may well be a nasty hack. I was convinced the issue was a protected kernel module but it seems the ext4fs image of the system block is corrupt in some way and the default error action is to mount -o ro. We're disabling that default action and letting the mount remain unchanged.
As always with these things, proceed at your own risk. If you break it, you have the privilege of keeping both bits.
Good way around mate, but risky as no CWM yet installed, seem's the mobile gut some bug problem, should expect an official update rom soon enough, Root method you used for this? i intend flashing Clockwork Mod can seem to understand fully as i'm new to android development and customizing, again problem with battery do you get a full day (few moment on screen) light usage? Feel its no actual 25000mah on board.
codedmax said:
Good way around mate, but risky as no CWM yet installed, seem's the mobile gut some bug problem, should expect an official update rom soon enough, Root method you used for this? i intend flashing Clockwork Mod can seem to understand fully as i'm new to android development and customizing, again problem with battery do you get a full day (few moment on screen) light usage? Feel its no actual 25000mah on board.
Click to expand...
Click to collapse
It appears there's an fsck implementation in the shell of CWM as well.
Code:
e2fsck -pfv /dev/block/mmcblk0p5
That should fix most of the errors in the filesystem.
The device came with su and SuperSU installed but it was fairly useless without /system access.
CWM can be easily installed using MTK Droid Root & Tools to extract the boot image, auto-patch, build CWM and install the lot. It really is a slick piece of software.
As for the battery, an even bigger issue is the supplied charger which is puny. Of course, looking at the battery and then looking at a proper, honest-to-goodness 2.2Ah Panasonic 18650 cylindrical cell you have to wonder if 2.5Ah isn't awfully optimistic.
Chron0s said:
It appears there's an fsck implementation in the shell of CWM as well.
Code:
e2fsck -pfv /dev/block/mmcblk0p5
That should fix most of the errors in the filesystem.
The device came with su and SuperSU installed but it was fairly useless without /system access.
CWM can be easily installed using MTK Droid Root & Tools to extract the boot image, auto-patch, build CWM and install the lot. It really is a slick piece of software.
As for the battery, an even bigger issue is the supplied charger which is puny. Of course, looking at the battery and then looking at a proper, honest-to-goodness 2.2Ah Panasonic 18650 cylindrical cell you have to wonder if 2.5Ah isn't awfully optimistic.
Click to expand...
Click to collapse
Very Well concerned,
once again good job, but how do i go about implementing this,
would you be kind enough to put in some more details on the file system code and CWM flashing with MTK Droid root & Tool did you manage to get a translation on the chinese langauage recovery problem,
(a tutorial is just fine) Thanks alot bud.
Okay, give me a little time to set it all up for screenshots as I don't generally use Windows unless I have to. It's all fairly straightforward. The CWM installation is four clicks and some waiting and repairing the /system block is a couple of commands.
Oscarblue48 has a tutorial on installing CWM on Mediatek devices here or here if your MX28 isn't rooted which is the procedure I followed. Then it's just a case of booting into CWM, connecting your device to USB and using adb's shell to fsck the filesystem on that block.
really nice, okay as you say,
i would look forward to it (some screen shots aid), in the main time with full study & concentration on the CWM tutorial you gave, quite interesting if you ask me.
#back to studying, looking forward to a bug free final optimization of the Mlais MX28 as its a great buy for such a price.
codedmax said:
really nice, okay as you say,
i would look forward to it (some screen shots aid), in the main time with full study & concentration on the CWM tutorial you gave, quite interesting if you ask me.
#back to studying, looking forward to a bug free final optimization of the Mlais MX28 as its a great buy for such a price.
Click to expand...
Click to collapse
Sorry for the delay, I ran into a few issues and had to work out what was going on. Basically the e2fsck in CWM cannot write back to the block device so is useless. I extracted the system.ext4.img, added it as a file backed memory disk on my main computer and ran an e2fsck from there, which found and fixed the errors in the FS image. Writing that back after changing a few MD5sums in the file MTKDR&T creates allowed me to flash it back.
However it makes absolutely no difference to the mount behaviour. It still drops back to ro without the tune2fs -e continue set so that is, barring someone else coming up with a more elegant fix, the workaround. In a nutshell, follow the guide for either root or CWM recovery installation that others have posted linked above (no point wasting board space on repetition) and then simply follow my instructions for setting the error behaviour on the mmcblk0p5 slice and you should be good to go.
It's still an awful hack IMHO but, since there's nothing else so far that works, it's the uncomplicated way to get full root. Most of us will install CWM anyway, so it's no big chore just to boot into recovery and type one command "tune2fs -e continue /dev/block/mmcblk0p5" at the ADB shell.
Chron0s said:
Sorry for the delay, I ran into a few issues and had to work out what was going on. Basically the e2fsck in CWM cannot write back to the block device so is useless. I extracted the system.ext4.img, added it as a file backed memory disk on my main computer and ran an e2fsck from there, which found and fixed the errors in the FS image. Writing that back after changing a few MD5sums in the file MTKDR&T creates allowed me to flash it back.
However it makes absolutely no difference to the mount behaviour. It still drops back to ro without the tune2fs -e continue set so that is, barring someone else coming up with a more elegant fix, the workaround. In a nutshell, follow the guide for either root or CWM recovery installation that others have posted linked above (no point wasting board space on repetition) and then simply follow my instructions for setting the error behaviour on the mmcblk0p5 slice and you should be good to go.
It's still an awful hack IMHO but, since there's nothing else so far that works, it's the uncomplicated way to get full root. Most of us will install CWM anyway, so it's no big chore just to boot into recovery and type one command "tune2fs -e continue /dev/block/mmcblk0p5" at the ADB shell.
Click to expand...
Click to collapse
Greetings bud, gut CWM installed, all thanks to you (indeed greatful), have you been lucky with any custom rom as of now that works efficently on your device?
I seem to find a few bug here and there on the manufacturer stock, puny wifi & gps lock in, slight screen maulfuctions a little times.
As with most mtk gps can not finding a lock in hows it with your device.
codedmax said:
Greetings bud, gut CWM installed, all thanks to you (indeed greatful), have you been lucky with any custom rom as of now that works efficently on your device?
Click to expand...
Click to collapse
None of the custom ROMs on needrom work correctly which is a shame. The stock ROM's UI is awful.
codedmax said:
I seem to find a few bug here and there on the manufacturer stock, puny wifi & gps lock in, slight screen maulfuctions a little times. As with most mtk gps can not finding a lock in hows it with your device.
Click to expand...
Click to collapse
Now you have root you can use FasterGPS from FDroid to intialise the gps.conf file with appropriate settings for your location. My GPS is rock solid now, even in a moving vehicle. Not had any screen malfunctions. What version is your stock ROM? Mine's the 20140221 update.
Chron0s said:
None of the custom ROMs on needrom work correctly which is a shame. The stock ROM's UI is awful.
Now you have root you can use FasterGPS from FDroid to intialise the gps.conf file with appropriate settings for your location. My GPS is rock solid now, even in a moving vehicle. Not had any screen malfunctions. What version is your stock ROM? Mine's the 20140221 update.
Click to expand...
Click to collapse
Hello great bud,
Sorry for late reply, been up with alot on my plate from work lately, gps has been improved upon using that wonderful app "FasterGPS" now able lock in under a split couple of min not as before were it take like forever *Nice*
gut the same stock version "20140221" gusse its down to my own unit with the screen ish
Did a little searching around found a recent update from a online retailer outlet via their forum "merimobiles"
forum.merimobilesdotcom.previewdnsdotcom/showthread.php?465-Unified-thread -for-Mlais-MX28-stock-ROM-updates
Hope im not infringing on any xda TOS as i just seek some help.
Thanks
Please i need help, i have a mlais mx28 buy in buyincoins, with the refer gordete200, it´s all ok.
i´m very happy with the mlais mx28, but i used a 8 gigas sd card, it´s all ok.
My problem: i have install with flashtools the new rom stock update : mx28_0312_N2.rar from the official mlais mx28 web
When i have install this ultimate ( update ) ROM, it´s was with reebots, and the wifi and blutooth crash 0_0 !!! what happend?
I back to the Rom stock : 0115 but the sd partitions was changed : 1 gb for apps, and 1.75 gb for internal memory, it´s very strange, before install the Update, i had 2,3 gb for apps and 256 gb for internal memory...
I´m very worry, the actual problem is the sd card:
With 8 gb sd card class 10, it´s all ok, all correct, but when i put the 16 gb sd card class 10, it´s don´t mount sd correctly always.
I´m very crazy for all...
codedmax said:
Hello great bud,
Sorry for late reply, been up with alot on my plate from work lately, gps has been improved upon using that wonderful app "FasterGPS" now able lock in under a split couple of min not as before were it take like forever *Nice*
Click to expand...
Click to collapse
Good stuff. Once you have the gps.conf set up, try using Mobileuncle Tools to pull in the EPO (extended prediction orbit, basically a nice big list of keplers for the satellites so it knows which to expect to be in view at a given time without having to scan the sky for what's actually there) data which should stabilise the GPS even further.
codedmax said:
gut the same stock version "20140221" gusse its down to my own unit with the screen ish
Did a little searching around found a recent update from a online retailer outlet via their forum "merimobiles"
forum.merimobilesdotcom.previewdnsdotcom/showthread.php?465-Unified-thread -for-Mlais-MX28-stock-ROM-updates
Hope im not infringing on any xda TOS as i just seek some help.
Thanks
Click to expand...
Click to collapse
I wonder if it's the bodged Trebuchet they're using? It's a bit of a disaster as they've taken the CM launcher, bodged bits of MIUI into it and given the whole thing a "that'll do" look and feel. I replaced it with the real Trebuchet after a thorough decrapify, along with the AOSP stock keyboard. There's a "modified" apk of Trebuchet (all the dev did was lower the base API level so it would install on 4.1) floating about on the 'net somewhere. The various KitKat-alikes work fairly well but I wanted something open source that I could slam into /system/app without worrying.
It has taken a lot of faff to get to this stage but I now have a very usable and fast device for not a great deal of outlay.
gordo100 said:
Please i need help, i have a mlais mx28 buy in buyincoins, with the refer gordete200, it´s all ok.
i´m very happy with the mlais mx28, but i used a 8 gigas sd card, it´s all ok.
My problem: i have install with flashtools the new rom stock update : mx28_0312_N2.rar from the official mlais mx28 web
When i have install this ultimate ( update ) ROM, it´s was with reebots, and the wifi and blutooth crash 0_0 !!! what happend?
I back to the Rom stock : 0115 but the sd partitions was changed : 1 gb for apps, and 1.75 gb for internal memory, it´s very strange, before install the Update, i had 2,3 gb for apps and 256 gb for internal memory...
I´m very worry, the actual problem is the sd card:
With 8 gb sd card class 10, it´s all ok, all correct, but when i put the 16 gb sd card class 10, it´s don´t mount sd correctly always.
I´m very crazy for all...
Click to expand...
Click to collapse
Do you have a backup of the original ROM and scatter (partition layout) file? You really should (read: MUST) back up these devices before flashing new firmware as there's often bits missing, as you found with the WiFi and Bluetooth issue. MTK Droid Root & Tools will create a useful backup of the partition layout and contents for you without too much difficulty.
Please do not write to the preloader partition with the SP flash tool. Once the preloader is corrupt, your device is a brick which only JTAG will recover. I seriously doubt anyone has a JTAG solution for this device right now. There is no need to rewrite the preloader at all in any case so simply deselect the preloader block in SP Flash tool before downloading.
As for the SD cards, you need to make sure your card is formatted FAT, not NTFS, and the card must be partitioned correctly, i.e. the FAT partition must be the first primary. The MX28 will accept a card of up to 32GB if I recall correctly, which is the limit of SD-HC. Clockwork Mod can format your card for you.
Chron0s said:
Do you have a backup of the original ROM and scatter (partition layout) file? You really should (read: MUST) back up these devices before flashing new firmware as there's often bits missing, as you found with the WiFi and Bluetooth issue. MTK Droid Root & Tools will create a useful backup of the partition layout and contents for you without too much difficulty.
Please do not write to the preloader partition with the SP flash tool. Once the preloader is corrupt, your device is a brick which only JTAG will recover. I seriously doubt anyone has a JTAG solution for this device right now. There is no need to rewrite the preloader at all in any case so simply deselect the preloader block in SP Flash tool before downloading.
As for the SD cards, you need to make sure your card is formatted FAT, not NTFS, and the card must be partitioned correctly, i.e. the FAT partition must be the first primary. The MX28 will accept a card of up to 32GB if I recall correctly, which is the limit of SD-HC. Clockwork Mod can format your card for you.
Click to expand...
Click to collapse
Many thanks for your help. I have a back up of my mlais, i have a back up with mtk droid and tools 2.5.3 ( new version ), but when i put it on the flash tools, the cache and user is missing, and it´s imposible to download it. and then i put a recovery CWM on the mlais with droid and tools ( very easy ), and use a nandroid back up, it´s no problem, but the internal sd partition is always changed : 1 gb for apps and 1.75 for sd internal, i´m very sad because i would like back to the 2,3 gb for apps ( original partition )
Yes... always fat32 sd cards of course, but i have problems with the sd up to 8 gb, the mlais freeze, or sd desmount ( it´s imposible sometimes write in sd external ) i don´t find the problem with this... i have the rom stock : 115.
Other problem, i would like to up the ultimate ROM stock 221. but the wifi and bluetooth crash, and reboot the phone sometimes ( terrible...) , what can i do ? your solution is don´t stick the PRELOADER on the Flashtool when i upload the firmware ? it´s correct? ( i think that if don´t mark the preloader it´s imposible flash... ?¿ )
Many thanks for your help !
gordo100 said:
Other problem, i would like to up the ultimate ROM stock 221. but the wifi and bluetooth crash, and reboot the phone sometimes ( terrible...) , what can i do ? your solution is don´t stick the PRELOADER on the Flashtool when i upload the firmware ? it´s correct? ( i think that if don´t mark the preloader it´s imposible flash... ?¿ )
Click to expand...
Click to collapse
No, what I'm saying is we don't yet know why the WLAN and Bluetooth stop working when a different ROM from the one flashed at the factory is installed. There is clearly some mechanism at work here that is blocking those two devices after an update and it's not the usual shared objects as it is on other devices. It also doesn't seem to be NVRAM related as the MAC and BDaddr remain once the old firmware is re-flashed.
This same problem occurs with all the custom ROMs on needrom.
The reason I say do not needlessly flash the preloader is the danger of a full brick from which you cannot recover. The preloader code very rarely changes - its only purpose is to provide an interface to SP flash tools or boot; think "BIOS" in PC terms - so it is a pointless risk. You most certainly can flash the other blocks with the preloader block deselected.
The bottom line right now is stick with the factory ROM, install CWM, apply the system mount fix and use Xposed and suchlike to customise until we come up with something a little more sensible or at least find out why the WLAN and Bluetooth stop working.
Given that the Wiko Darkmoon is based on the same SoC and has full sources available <EDIT: It isn't. It's just the kernel as usual.>, it may be prudent to wait until someone with more clue than I has a look at what makes these things tick.
Chron0s said:
No, what I'm saying is we don't yet know why the WLAN and Bluetooth stop working when a different ROM from the one flashed at the factory is installed. There is clearly some mechanism at work here that is blocking those two devices after an update and it's not the usual shared objects as it is on other devices. It also doesn't seem to be NVRAM related as the MAC and BDaddr remain once the old firmware is re-flashed.
This same problem occurs with all the custom ROMs on needrom.
The reason I say do not needlessly flash the preloader is the danger of a full brick from which you cannot recover. The preloader code very rarely changes - its only purpose is to provide an interface to SP flash tools or boot; think "BIOS" in PC terms - so it is a pointless risk. You most certainly can flash the other blocks with the preloader block deselected.
The bottom line right now is stick with the factory ROM, install CWM, apply the system mount fix and use Xposed and suchlike to customise until we come up with something a little more sensible or at least find out why the WLAN and Bluetooth stop working.
Given that the Wiko Darkmoon is based on the same SoC and has full sources available <EDIT: It isn't. It's just the kernel as usual.>, it may be prudent to wait until someone with more clue than I has a look at what makes these things tick.
Click to expand...
Click to collapse
Many thanks Chronos!, The problem is also with the official ROMS on mlais.com/mlaismx28 i don´t understand it...
Please i need help to back restore the partitions of my sd internal ( ROM ), i would like back to 2,3 gb for apps, actually i have only 0,98 gb and 1,75 gb internal store.
I think that the solution is back up for flash tools and reflash with the rom stock ( the back up of mlais mx28 of my friend, he have other new mx28 )
But my BIG problem with the flash with flash tools is the USER DATA and CACHE is always empty, and then it´s imposible to reflash it it´s always and error : Rom changed PTM ...
Please, what can i do for have USER DATA and CACHE with mtk droid and tools 2.5.3 versión?? ( in this version to click User data and Cache with to do the back it´s imposible, this option is missing in 2.5.3. version )
http://dl.xda-developers.com/attachdl/b2f11c741aab592a8f66616d932af983/533c2dcc/2/6/6/4/5/2/2/Sin_t_tulo.jpg
[ROM] Official Update
Hello guys, there's a new rom update for the mx28
Official Mlais MX28 version: Mlais_MX28_20140312
www.needrom.com/mobile/mlais-mx28-2/
Try it out seems, it works perfect.
Cheers!!

[Q] Lenovo Lepad S6000-H with 3G bricked

This has been posted elsewhere on XDA however it was suggested that this would be a better location to post so here goes:
'Good day all,
I have the above tablet which has been bricked . (We sell these and a customer has returned a unit to claim warranty so I am not 100% sure what has occurred to make the device what it currently is.) Basically I have another identical unit and have created a backup image with MTK Droid Tools. However when I try to load this image with SP Flash Tools I get errors. These state that the image I have is not correct (as it is from an identical unit I can safely say this is not correct) to the device storage not being available. The second error is the one I believe may be the problem. Is there a way that the internal storage may have been compromised and if is is there a way the storage can be fixed?'
I have tried to study the posts relating to partition dumping but am simply not bright enough to figure it out. Is there a way I can make a 'ghost' image of the working tablets partition table and then tranfer that to the bricked unit?
Thanks in advance for the help and time.
Alternately is anyone able to confirm a partition backup and restore tool?

how to unbrick my phone with cpu MTK MT6735

hello guys, I'm new in the forum, I have a mobile lower-middle-bought band, his name is Master "smartphone 504-4g", owns the mediatek mt6735 cpu 1 GHz, has 1 GB of RAM, Android 5.1, and 4 GB of rOM.
I tried to extract the rom with MTK droid v2.5.3d tool, but at the end of extraction known that there is only the folder / system saved in the PC, and the program has reported to me the error "No space left on device "thing I was aware through consultation of guides on the internet.
now that I broke the phone after trying to install Xposed (bootloop), how can I enclose all the files in the folder / system I have in the PC, in an IMG to flash file with sp flash tool?
Thanks for help
There are ways to uninstall xPosed Framework if you can get into Recovery:
http://forum.xda-developers.com/xposed/xposed-lollipop-stuck-bootloop-t3055816
Check Needrom.com for your specific device ROM, if it is a common device, or even uncommon, there may be a ROM there. I've also backed up using that tool, and left with unusable files. If you know your device info, Kernel and Fingerprint, use that info when searching Needrom, usually it's listed with the available ROMs.
This came up in a search, I don't know if it is your device:
http://iris504qdevelopment.blogspot.com/
X-weApon-X said:
There are ways to uninstall xPosed Framework if you can get into Recovery:
http://forum.xda-developers.com/xposed/xposed-lollipop-stuck-bootloop-t3055816
Check Needrom.com for your specific device ROM, if it is a common device, or even uncommon, there may be a ROM there. I've also backed up using that tool, and left with unusable files. If you know your device info, Kernel and Fingerprint, use that info when searching Needrom, usually it's listed with the available ROMs.
This came up in a search, I don't know if it is your device:
http://iris504qdevelopment.blogspot.com/
Click to expand...
Click to collapse
hello, thanks for answering.
I searched in needrom.com for the Rom, inputting the fingerprint, the kernel etc. but could not find anything.
the phone of which you wrote me the link is not what I have.
This is the fingerprint:
Code:
alps/full_x5_g518ql/x5_g518ql:5.1/LMY47D/1456459901:user/test-keys
This is the kernel:
Code:
3.10.65 ([email protected]) (gcc version 4.9.x-google 20140827 (mtk-20150409) (GCC) ) #1 SMP Fri Feb 26 12:20:51 CST 2016
and this is the version of the baseband:
Code:
MOLY.LR9.W1444.MD.LWTG.MP.V42.P7
LMY47D seems to be the version of Lollipop
https://www.google.com/search?q=LMY47D/1456459901&ie=utf-8&oe=utf-8#safe=off&q=LMY47D
Using only that at Needrom, I found only this:
http://www.needrom.com/download/real-android-5-1/
Sorry, usually searching the fingerprint brings up SOMEthing useful. but in this case, there are absolutely no results.
I found references to the Kernel too, but nothing useful.
ok , I had also tried on google but to no avail .
how can I do then to put it back ?
I considered the idea to buy some one the same , but I do not know other ways to extract the ROM and then perform the flash procedure on the broken device .
What do you advise me to do?
Are there any tutorials on this site about using MTK droid tools? Its not just about backing up the system.IMG file, there should be a boot.IMG and a recovery.IMG, and then you have to create Scatter files. But I don't know what I'm supposed to do. I've used other tools, it seems that all it gave me was a system.IMG. its highly likely that this file contains everything, but it appears that there is an extra step that we don't know about.
Your device may simply be uncommon, especially with the lack of usable info available for it. I've looked up fingerprints before and there is usually some info. Which was why i suggested it.
Give me a few days to research this issue. Also, have you tried device Safe Mode? Reboot, hold both volume up+down as it starts, see if you can get it to boot. If it does, remove xPosed.
Also, do you have any recovery that works? Because you can send the xPosed removal zip through ADB and it will remove xposed. Check my first link.
Sent from my 6S Plus using XDA-Developers mobile app
---------- Post added at 06:57 PM ---------- Previous post was at 06:51 PM ----------
I was trying to replace Kingroot with SuperSU late last night and my device was stuck at the boot screen. But I was able to ADB into the device and run a shell and look around, you might be able to copy the Xposed removal tool that way and then run it
Sent from my 6S Plus using XDA-Developers mobile app
I forgot one detail that I have not written in my previous posts. besides the problem of Xposed I made bull**** to install a rom that I thought was compatible with this device, and the ROM is that of Doogee X5 Pro, which is very similar in characteristics to the my device. only after doing the flash with sp flash tool, the phone will not turn on anymore. Now It is only detectable by usb connection without battery and pressing the volume up button. I apologize if I have not written before.
the recovery of my phone I remember is that stock, and I replaced it with the ever TWRP of Doogee x5 pro, but it did not work.
You bricked it. Time for a new device.
it is very unrecoverable @zelendel?
gae1991 said:
it is very unrecoverable @zelendel?
Click to expand...
Click to collapse
Yes it is dead. You messed up flashing something for another device.
I saw on the internet that there is a box to be able to flash the ROM even if the phone is dead. This box is called MTK-box. I have already had experience in the past with the atf-box for Nokia, you say that might work?
I've used ROM's for wrong device on an MT6582 device I had, effectively bricking it. But I was able to find the correct ROM and flash with that, presto, fixed. The problem here, is that we can't FIND the correct ROM.
I highly suggest contacting the seller, was it DHgate? Try to find out. I bought a brand new iPhone 6S+ 1:1 clone from a seller named iBaby888, and I bricked the device while trying to use SuperSU Me. I contacted iBaby and she pointed me to the correct ROM which fortunately had JUST been posted at Needrom by [email protected] I even Bricked it again 2 nights ago, using Vicki Bonick's KR2SU script. Boom, flashed again.
Any device can be reverted to stock I believe, it's just a matter of having the right ROM. Now in the case of using MTK Droid Tools, I think you missed a step:
http://forum.xda-developers.com/showthread.php?t=2730031
5. Start MTK Droid Tools, and connect your phone with the USB cable to the PC. (if Windows install some drivers, then let it install them automatically).
6. Now on the first page of MTK Droid Tools, it should display all infos about the phone when you connect it.
7. If the sqare is Green, then you have root shell and ready, if its not green, press the ROOT button to the right in MTK Droid tools.
8. Click the "IMEI/NVRAM" button and then Backup to backup your IMEI/NVRAM, the backup files will be inside of the MTK Droid Tools folder.
Also you can manually write down your IMEI number just in case it should be lost.
9. Now go to the tap "root, backup, recovery" (in MTK Droid Tools).
10. Click the Backup button, and it will create a complete backup of your ROM. (in the end it will ask, if you want to pack it, just answer no)
11. When it is finished then also click "To prepare blocks for FlashTool", that will convert the backup to be compatible with Spflashtool. (choose the files.md5 inside the backup folder)
12. After the backup is done it will be inside "backup" in the MTK Droid Tools folder. And inside it there will also be a new folder called "!Files_to_FlashTool" Inside there the files for Spflashtool is. So when loading your backup with Spflashtool you must load the scatter file from inside there.
13. Now to install CWM (clockworkmod recovery) In MTK Droidtools, choose "To use boot from phone" and click the "Recovery and Boot" button. It will ask you a lot, just say yes every time, and it will end of sending CWM recovery to the phone and reboot into it on the phone. After you see CWM on the phone you know it is done. You can switch the menu with the volume keys, and the power is the select button.
14. Inside CWM you can also do a complete backup of your phone (remember to have enough space, you can do the backup to the internal storage OR to the SDcard - try "backup" if that fails then choose instead "backup to external sd" or vice versa). I recommed doing that because CWM makes another backup than the one made with MTK Droid Tools. So if you should get problems or loose something, you can always run your CWM backup into your phone and it will be as before.
15. After your done the backup, copy the backup also to a safe place on your PC. Just in case!
Click to expand...
Click to collapse
There may be a way to convert the backup you made.
I used ROMdump on one of my Goophones, and it created 3 files: config.gz, system.info.gz and system.tar. The System.tar file is a large archive. I suppose I have to convert this into somehting that SPFlash can use, but from what I am reading, I think files like this are supposed to be flashed from Recovery. If you can connect while the device is powered off, you may be able to ADB into the device and start a shell, copy the files in and then start s flash. I have only started working with ADB so I'm not clear on it.
I think best bet, contact the Seller of the device, if that wasn't you have the person who ordered the device send a message, ask if they have access to the ROM, sometimes they will offer to send it to you via Skype, iBaby888 offered that for me, but I found the exact Rom I needed on Needrom. If they don't have it, you can ask for the rom over there, make a post identifying the device and just say "need ROM", provide the fingerprint and Kernel if you do that.
gae1991 said:
I saw on the internet that there is a box to be able to flash the ROM even if the phone is dead. This box is called MTK-box. I have already had experience in the past with the atf-box for Nokia, you say that might work?
Click to expand...
Click to collapse
SPFlash and other flashing tools all work that way, even Odin, the device must needs be powered off and in some cases the battery removed. They even have tools to reset the device, if your device does not have a reset button hidden somewhere, the developers of the Flash tools sometimes tell you to disconnect the battery, but in the case of a device not having access to the battery, there is the reset button. Always trip that before each attempt to Flash.
It's basically the same thing, I'm sure OP can flash the device, but we can't find the stock ROM anywhere.
with respect to paragraph 11 forgotten, the program in my case has not created any file called "files.md5", the guide I've read (which is the same that you posted you) I knew I would have to be after the backup, but so was not . In the folder "backup" I only have the folder "/ system" with subfolders "app", "priv-app" etc.
I remember also that the program at the end of the backup asked me if I wanted to compress zip, I clicked "no" and in the right part of the program I read "activities ended in error," I read above and I see the another error "no space left on device", and the guide I've read this error occurs with only the devices with 4 GB of ROM for perform the backup also in the device. anyway thank you for helping me.
my phone id dead
please if you can help me too.
I have an allview phone that has a mediatek mt8735m processor is(dead)does not start,but when I plug it into the usb port of the pc,the your pc recognizes it but does not stay connected
what could I do about it?

[Q] Recover Data From Formatted Internal Storage Raw Dump?

Before I start, I'm aware there are great data recovery guides on this forum and elsewhere. Unfortunately, I was unable to find one pertaining to Nougat and my specific circumstances. Thank you for bearing with me.
How the Data Was Wiped
I ran "fastboot format userdata" to fix a "Decryption Unsuccessful" error message after going from LineageOS 14.1 to 15 on a Xiaomi Mi 5 Pro. Because I was in a hurry to get my phone back online, I foolishly assumed the wipe would leave /data/media intact, just like TWRP, without making sure of it. I know the assumption was wishful thinking at best and I can see the irony in then spending the rest of the day trying to undo the damage.
How the Data Was Dumped
Immediately after finishing the fastboot format, I booted back into TWRP 3.1.1-0 where I discovered the extent of the data loss. Since I hadn't flashed a ROM and didn't want to write anything else to my /data partition, I did a "adb pull /dev/block/sda14 sda14.img" on my computer over USB with my phone still in recovery. With a 128GB phone, the process took a whopping 8102.059s to finish.
How I attempted to Recover Data
I let both R-Studio 8.3 and UFS File Explorer Professional Recovery 5.23.4 scan through my dump to no avail. All they found were meaningless, small files, mostly in a .txt or .so format. I also attempted to mount the image using DiskInternals Linux Reader 2.6, but PhotoRec didn't recognise the volume.
Where do I go From Here?
Christian Weiske wrote about his attempt at recovering photos from a Galaxy S5 mini, running Marshmallow. He noted that data he pulled in Windows was broken using various commands until he tried "adb exec-out". Does the problem lie in my pulled data also being broken/incomplete, or is "fastboot format" actually capable of completely destroying more than 100GB worth of data in mere seconds on TRIM-enabled devices? If I am to do a second /data dump using a different method, I would have to do it directly to my computer as my phone doesn't have a microSD slot. I should add that, to the best of my memory, I never encrypted the storage, as I went directly from CyanogenMod to LineageOS using the experimental migration build.
To anyone who chimes in, if only to tell me that I should suck it up and stick to whatever data I have backed up and move on, I'll be most appreciative! Even more so if anyone can shed some light on modern-day Android data recovery/wiping and limitations.
I'm going thru a recovery process myself. Using a few guides. First I completed a raw dump of the whole phone w/out installing any os over the phone. I'm about to check that and see if testdisk can find something via https://roubert.name/joakim/androidfilerecovery/
In the background, I have another dump going on from https://forum.xda-developers.com/ga...de-internal-memory-data-recovery-yes-t1994705 guide. Hopefully, something comes up.

[SOLVED] MTK6580 build.prop soft-brick problem solved NO ADB

Hello there,
I'm wondering if there's anyone knowledgeable to point me in the right direction. Coronavirus (or I) messed up the build.prop file in a Chinese-made JTY-K107 (MT6580 architecture) tablet and now stuck in a soft-brick state. I cannot use adb push or adb sideload (doesn't detect device probably because I had attached another MT device, a Huawei on the PC before and that is the device I pulled the build.prop from to mess with the bigger tablet and now all seems jumbled driver-wise on my Win 10). In any case, I am able to copy to the SD card an update.zip but factory recovery installation is not possible ("installation aborted" - signing issue?). I tried these two zips inside which the original build.prop files are now nestled. It's maybe the commands/scripts that are at fault or it's some signing issue (that hopefully can be tackled). I don't know. I am very reluctant to think about flashing ROMs at this stage. (Porting MT-architecture ROMs are not exactly easy or risk-free, from what I have seen around other threads/forums.)
The link to the folder with the non-working update zips I pulled from other sites or threads (not knowing how I should go about building these files from scratch on my own):
https://app.box.com/s/7byabibx2j0jfo2zlgmg0oi0ca66vkyn
Thanks very much for any info (or possibly a fix of the zips to make it compatible with MT6580 to install the update).
Cheers,
Zoltán
@zanodor
IMHO a simple factory reset may solve your problems.
jwoegerbauer said:
@zanodor
IMHO a simple factory reset may solve your problems.
Click to expand...
Click to collapse
Today I was thinking, people like overcomplicating things: there must be some easy solution. I actually had done that out of frustration (knowing that I had a Titanium Backup on SD) but the boot issue persists (I tried again but all I see is the Android logo for minutes now).
I thought maybe there was a way to repackage my full Titanium Backup into a zip that could be used in Factory Recovery for a restore solution? I perused the net in vain for that too.
I really don't fancy reinstalling Win 10 to fix the driver issues or trying on one of my Linux machines (I am a noob on those too).
Thanks for the answer, anyway.
In the end I managed to restore the tablet (took me 2-3 days of looking around). I'm only writing this up so others facing adb probs can solve their issues on their MTK-built devices. (Actually probably this will work on any device that is not Samsung or whatever old famous brands.)
The first thing to do was sorting out VCOM drivers. There's a Nigerian-sounding guy whose forum Hovatek I followed for tricks on how to go about it (had to download and install Virtual Serial Port Driver to sort out connection issues in Miracle Box/Thunder). Whenever you have some problem, I suggest you include Hovatek in the search string, cause chances are he has a tool and a tut.
Using Miracle Thunder and acting on Hovatek's instructions I made a copy of my firmware. All I really needed was the sytem.img, of course. My bootloader being fine (messing up your device with build.prop only results in a soft brick), it didn't need fixing. Using Assayyed's Kitchen and Hovatek's tutorial again I unpacked the system.bin I extracted with Miracle (which must be all the time used with virus protection off) after renaming system.bin to sytem.img. I exchanged the build.prop and repacked system but didn't wait for the update.zip to be made, instead I took the img file I wanted in the Kitchen. Then tried SP Flash tool to flash system.img on the device but I had issues with the scatter file. So I downloaded a firmware from Boycracked or whoever and used that scatter (in the meantime I overwrote the system.img with mine). I flashed device, turned on the tablet and voila. I hope this helps peeps out there with similar issues.

Categories

Resources