Database Info

Confused with S5 clone

Hello to all community members.
First, sorry for my english...is not very good.
I post this questions here because I searched a lot on google and on this forum and others, and I can't found a solution.
I tell my situation: Samsung S5 clone, on box SM-G900. Under battery SM-G9008. On droidtool MT6571, SM-G900H, LCD Driver IC : 0-rm68171_fwvga_dsi_vdo_tm., UBIFS. And on recovery GT-I9008. Is made in Korea.
Well, in first moment I can enter to recovery, but triying things now is totally dead, no charge, no recovey, no lights...
I tried a lot of things, but i found a rom from needrom it makes the phone alive, but with black screen.
Knowing this:
1. I found another ROM with that LCD drivers (it means in description), but is not for MT6571 and I can't flash with sp flashtool. Question: Is possible to "extract" drivers from one rom to another?? This is "copy" LCD driver from the rom to needrom's.
2. I found another roms on another forum, for MT6571, but any worked. That it makes me think that the chip is not really MT6571, but if I try to flash a 6572 i get "chip not match" from flashtool. I tried to make a backup and the program droidtool creates a scatter for 6572, is strange. Question: is only droidtools the program needed to know real hardware?? Searching on google for that model, i found a lot of roms for MT6572 with all the characteristics from phone, but only 2 o 3 with MT6571. But, the rom for MT6571 is only the one it flash without errors.
3. Where I can find a stock rom for that phone???
I need a way to unbrick the phone, I think is possible, but I don't have an original backup or any file from the original android
Any suggestions??
I think that these questions are in this section, if I should go elsewhere sorry...
A lot of thanks.

I add some new info about this.
I tried to connect the phone to pc, and I can view the folders and files from inside. My question now is:
The phone is running but black screen, is possible to change lcd driver on any folder?? Where are installed lcd drivers on android device mtk???
Please, I need some clue about this...
Thank you!!

[Completed] Help unbricking Nextbook 7 NX700QC16G

Hi, I'm new to this site and in deep waters with this issue. I'm decent in repairing hardware and basic in doing software changes. Well, I screw this one up.
My mom was having problems with her Next book 7 tablet not having enough memory. Insufficient space with less than 1GB. She really don't know how to download and add apps so there wasn't much on it, maybe 2 or 3 apps she really used other than factory ones. I always have to clean the cache and delete updates so that it would function decent. So I decided to Google this issue and found out that every one of these China made tablets had that issue and the site didn't have the downloads. One site gave instructions on how to fix the lack of memory issue but the tablet had to be rooted and have the firmware updated. Then you can go in a combine the partitions to gain all of the memory. So I started to upgrade it. I followed the instructions carefully. When I got to the "scatter-loading" dialog box, I couldn't find the open scatter file - MT8127_Android_Scatter.txt in the SP flash tool kit. So I Google the info and found MT8127_Android_Scatter.txt and ran the flash tool.
I thought I was good to go but then I got BROM ERROR : S_DL_GET_DRAM_SETTINGS _FAIL (5054). I guess the scatter files were wrong. Now the tablet is dead hard bricked. I still want to fix the memory problem but now I have a bigger problem, a dead tablet.
Can someone please help me get it back going?
Next book 7 16GB NX700QC16C
Mediatek Quad-core MT8127 Arm Cortex A7
4.4.2 kit Kat
Not sure if you might need more info, I will try to find if needed. Thanks in advance

[email protected] said:
Hi, I'm new to this site and in deep waters with this issue. I'm decent in repairing hardware and basic in doing software changes. Well, I screw this one up.
My mom was having problems with her Next book 7 tablet not having enough memory. Insufficient space with less than 1GB. She really don't know how to download and add apps so there wasn't much on it, maybe 2 or 3 apps she really used other than factory ones. I always have to clean the cache and delete updates so that it would function decent. So I decided to Google this issue and found out that every one of these China made tablets had that issue and the site didn't have the downloads. One site gave instructions on how to fix the lack of memory issue but the tablet had to be rooted and have the firmware updated. Then you can go in a combine the partitions to gain all of the memory. So I started to upgrade it. I followed the instructions carefully. When I got to the "scatter-loading" dialog box, I couldn't find the open scatter file - MT8127_Android_Scatter.txt in the SP flash tool kit. So I Google the info and found MT8127_Android_Scatter.txt and ran the flash tool.
I thought I was good to go but then I got BROM ERROR : S_DL_GET_DRAM_SETTINGS _FAIL (5054). I guess the scatter files were wrong. Now the tablet is dead hard bricked. I still want to fix the memory problem but now I have a bigger problem, a dead tablet.
Can someone please help me get it back going?
Next book 7 16GB NX700QC16C
Mediatek Quad-core MT8127 Arm Cortex A7
4.4.2 kit Kat
Not sure if you might need more info, I will try to find if needed. Thanks in advance
Click to expand...
Click to collapse
Greetings and welcome to xda. I am not sure if this is the same device but I found a guide to unbrick
http://forum.xda-developers.com/showthread.php?t=1447707
and a custom rom thread
http://forum.xda-developers.com/showthread.php?t=1410862
Really hope it helps
Good Luck
Sawdoctor

Thanks SawDoctor for that info.
In both of those threads, the NextBook 7 Premium YF1011 was mentioned. I'm not sure if the one I'm trying to fix is a premium tab, the SN# is YFG0914006160. I guess I can still try it, I don't think it can get any worst. Thanks

[email protected] said:
Thanks SawDoctor for that info.
In both of those threads, the NextBook 7 Premium YF1011 was mentioned. I'm not sure if the one I'm trying to fix is a premium tab, the SN# is YFG0914006160. I guess I can still try it, I don't think it can get any worst. Thanks
Click to expand...
Click to collapse
Hi, its [email protected] again on trying to unbrick this Nextbook 7. I haven't made any progress in finding the right firmware in order to unbrick. I have the files for the SP Flash Tool kit but they are giving me Brom errors (4032) (5054). I tried the Rockchip Batch tool kit but couldn't find the firmware image file and I also tried LiveSuit; all progress at negative. This is not too hard to do but i'm banging my head against the wall because I can't find the right files in order to complete the flash.
Am I missing something?

My Hard Brick incident

My hardbrick incident
I had a mediatek phone few years back.I found in some website or somewhere else the word "root" and benefits of rooting an android device.So I searched the internet and found several apps to root android phone.I found a chinese app called vroot.I ran the app and successfully rooted my phone.So the es file explorer app now does not bother me to activate root explorer feature.I navigated many system directories where I could not go in past without root.I deleted the framework-res.apk file from the /system/framework folder.Then all the apps on my phone just started to close.I got a feeling that I had done something wrong by deleting that file and if I rebooted now my phone would never boot again.But I still rebooted my phone with the hope that everything would be all right after the reboot.But the feeling became true and my phone never booted.I visited many local phone repairing stores but could not get my phone repaired.I thought this is not fair,all the hardwares within my phone were all right,it was just a software problem but still I had to throw my phone away because the local phone shops could not repair it.I disagreed that and kept my phone safe.I managed to get my parents to buy me another phone.Few months after I rooted that phone as well and this time a knew the importance of the system files.So I did not ever tried to delete any of the system files again.But as I had seen in the system tuner app that changing the lines in the build.prop file can make your phone faster.I changed probably the dalvik.vm.heapsize parameter to a much lower value from within the system tuner app.And I rebooted the phone and this time I faced the pain again,loosing the phone,listening to the bad comments of my sister,mother and father.Again no local phone repairing shop can repair it although all the hardwares in my phone were perfectly ok.I again disagreed to the choice of throwing the phone away.Few months after I got a Laptop.Then I tried to search about repairing the last phone.I found that these problems are very common in the internet although very rare to all the local phone repairing shops.I downloaded the entire rom of my device and flashed the rom by following each provided instruction.I learned about the sp tools program in the process.I proved to my family that I did not break my phone,it was just a software problem.I leaned about making back ups of the whole rom using sp tools and mtk droid tools programs.I learned about custom recovery and how to make a cwm recovery using the sp tools and mtk droid tools.I made one cwm recovery with mtk droid tools and sp tools and flashed it using the sp tools.I learned about custom roms.I found a custom rom and the guide to port it for my device.I learned about dsixda's Android Kitchen from the guide.I successfully ported the rom for my device but could not flash it using the cwm recovery that I made with sp tools and mtk droid tools.The solution was to get a latest working twrp or philz recovery using magic twrp program or magic philz program.So I got a latest working twrp using magic twrp program.I flashed the rom I previously made successfully.Meanwhile I found some where about the word "hardbrick" in which situation my phone would respond to nothing no physical button not even charger,and I would not be able to flash my back up rom from the computer anymore.I did not believe in that.I thought how was it possible whenever my phone would not boot I would always be able to flash the backed up rom using sp tools.So I found android to be non breakable at the software level.I also successfully downloaded and flashed the stock rom of my first soft bricked phone.
Few months after I had a phone named LYF F1 but this time it was a qualcomm phone.Before even getting the phone in my hands I planed to get a backup of the stock rom using the sp flash tools and mtk droid tools.Now when I got the phone in my hands I did as I planed.But mtk droid tools could not identify the phone.I wondered what was happening.After searching the internet I found qualcomm phones can not be backed up using sp tools and mtk droid tools these tools are for mediatek devices.So I searched the internet for few days in hope that I would found a way to backup my qualcomm phone.I found only one video tutorial to backup any non-rooted qualcomm phone using qpst tools otherwise there were many back up solutions if the phone is rooted.I tried to root my phone using almost each and every provided apps in the internet but failed,and also the back up method for the non-rooted qualcomm phones also failed.I searched the internet to found the stock but I failed.Then I downloaded some custom recoveries made for other devices with same cpu.By following some post at some where I tried to port it for my device,but again porting the recovery needed me to have my stock recovery.I thought if I could only flash the downloaded recovery and the recovery worked then I would get root access and I would be able to back up my stock rom.But the only way to flash the downloaded recovery to my qualcomm phone was to use the fastboot commands.But computer can recognise my device with the command "fastboot devices" but any other fastboot command just failed with an error remote device unknown command.Few weeks after I found the stock of my phone in the internet with someone's help.So I downloaded the whole rom,ported the recovery successfully and flashed it using the provided qcmdl program by replacing the stock recovery from the stock rom's folder with the twrp recovery.Then I got root in my this phone after a long wait through the twrp recovery.Now I tried to port a rom for my this phone.But I could not found a rom provided in the internet in the sense that it could be ported to any qualcomm device with same cpu.All the roms were made for a particular device and they were saying not to flash it on any other device.It was not the case with the mediatek phones that I had because I always found some roms which were provided in the internet in the sense that it could be ported to any mediatek device with same cpu and even the full guides to port the roms for my phone were also provided with each rom.I since then already ported many roms for my mediatek phones by following the guides provided with the roms.I took a rom made for the same device whose twrp recovery helped me to port my phone's twrp recovery.The phone was ZTE nubia z11 mini.The rom was mokee 7.1.2,the zip file contained boot.img,system folder,cmnlib.mbn,emmc_appsboot.mbn,file_contexts.bin,hyp.mbn,keymaster.mbn,modem.img,rpm.mbn,sbl1.mbn,splash.img,tz.mbn.Now when I flashed that rom I was thinking I had only seen system folder and boot.img before when I ported roms for my mediatek devices.So what were those other files? I thought they would probably make the rom work better.There were no informational file neither inside that zip file nor at their website which could suggest me what those other files were and what could happen to my device if I flash them.I flashed the rom successfully through twrp and rebooted into system.After few moments I saw my phone yet had not started to boot.I pressed the power button for few seconds and there was no response,I got a thought that my phone has hardbricked.So I tried again and again to power it on but my phone was really hardbricked.The fact that I refused to accept when I was working with roms for my mediatek devices,just came in reality.My phone would not respond to anything not for any physical button,not for charger,I could not restore the stock rom from my computer.I searched the internet day and night and tried almost each provided method and programs to restore the stock rom from my computer or from sd card but each of the methods and programs failed.Fortunately I found a fact in many places from other users in the internet that in a hardbrick situation if my phone is under warranty then service centre would repair the phone with minimum cost or without any cost at all.I send the phone to the LYF care and was thinking what did I do wrong when flashing the rom,which of the files in the zip file caused this.I searched the internet to know what are the exact work of those partition files but could not found what I was looking for,I tried my best to know the exact file with in the zip for which my phone was hardbricked,but I failed to know that.LYF service centre was saying that they had found some trace of liquid in the phone which had caused my phone to be dead and I have to pay a huge amount almost the actual price of my phone to get it repaired under warranty,I knew this was not true.So I contacted higher LYF consumer services to know them that my phone was never near any liquid so that my phone could have been harmed by it,they took the phone from the service centre and checked again,they now said some different reason and increased the amount to be paid to get my phone repaired under warranty.So I have to pay a huge amount to get my phone repaired,I do not know which of the files or the folders within the zip file caused that hardbrick,I have not been able to sleep well for last one month,and I have completely lost all faith on myself to flash anything in my phone,listening bad comments from my parents.Yeah that's my hardbrick incident.

It's a too long story bro, maybe you can find a IT-guy and ask for help

Do you expect any1 to read it all? You could just make it short, so some1 helps
Sent from this galaxy

Tarasantan said:
My hardbrick incident
Click to expand...
Click to collapse
Hi @Tarasantan! Dude You only mentioned trying to use the power button! do you still have the phone? If you do;
Try holding All three buttons for 50 secs.
Then, connect it to the charger for at least an hour (let it gather some juice).
Now try holding the Power and Volume Down button! for like another 50 secs!
In a few moments it should run! If it didnt PM me we will Discuss A few things! and I really appreciate If I have a new friend!
What we are doing here is draining the battery and discharging the phone! thus a HARD reset! like we do it with PC!
Next letting it take Up Juice to give it a Defibrillator kinda treatment!
Not resetting it by the Combo! (Power & Volume Down)
Reply Man! I can understand how worried you are I recently bought a new phone so I could use Beta Stuff on my phone! you are the reason for my phones root!
You are older member Here (atleast older than me!) I respect you Bruv! Imma Try helping you as much as I could. You give soo much and people seem TOO damn busy here! -.- I hope More active people become my BFFS!!! (^_^):highfive: (^_^)

Need help rooting Sky Devices Elite Octa 5.5 (MT6753)

So I got this cheap cell phone on Ebay for $50 (Sky Devices Elite Octa 5.5 with MT6753). It has great specs for that price. However, I'm now paying for it as I can't root the device.
I've tried one click tools but none of them worked. So now I'm asking the XDA community hoping that I can get some pointers.
I've found various tutorials online but they've all come to a dead end. If you find one that you think I should try, please let me know and I'll check it out.
I tried contacting the OEM but they were d-bags and refused to provide stock ROM or scatter file. Which makes me want to root it even more!
The furthest I got was I can dump about 2 GB from the device's memory to a raw file on my PC using SPF (Smart Phone Flash) Tool. One of the tutorials I found is here:
https://cmflare4guides.wordpress.com/2016/08/25/how-to-create-spft-rom-dump/
The Instructions section works but the Continuation section does not. In MTK Droid Root, the button "To process file ROM_ from FlashTool" is disabled and I can't click it.
Any ideas?
I can unlock the boot loader.
I think what I need to do is:
- "extract" the ROM that I downloaded via SPF Tools into various partitions (no idea how though)
- mount the partitions as a loop back device in Linux
- modify some file that will disable permissions on the device (allowing me to install SuperSU)
- "package" the modifications back to some ROM image
- upload the image to the device
However, I currently can't figure out what to do with the ROM_FULL that I downloaded from the device using SPF Tools.

Need Sky devices Elite 5.5 0cta (MT6753) Flash file(ROM)
Ey mate!,,hope you're doing good.. lucky I finally found your post over here. I kinda bricked that same phone when I been tryna flash a custom rom on it.
I managed to root it, had to use Miracle box( Cracked) ....side-loaded TWRP recovery via fast boot (felt like a champ:victory
but then things got wacky the moment I flashed a custom rom and now it can't even boot into any mode ,..almost scanned the whole web for its firmware but dang!, couldn't find it anywhere. If u still have that Sky Elite 5.5 Octa thing.. or the ROM,please do help a brother man, I am so in need of it...

The Maze speed ssb504r... And rooting?

I recently tried to root a maze speed ssb504r with spflash tools and accidently hard bricked my phone can any body help me unbrick it i didn't make a back up file but I found one on android forums and it is lacking the preloader. If anybody has a complete back up of the ssb504r it would be much appreciated or even just a compoatible preloader would be great.

[email protected] said:
I recently tried to root a maze speed ssb504r with spflash tools and accidently hard bricked my phone can any body help me unbrick it i didn't make a back up file but I found one on android forums and it is lacking the preloader. If anybody has a complete back up of the ssb504r it would be much appreciated or even just a compoatible preloader would be great.
Click to expand...
Click to collapse
I did a similar thing, but I have twrp from this forum https://androidforums.com/threads/recovery-unofficial-twrp-recovery-maze-speed-ssb504r-android-8-1-go-edidion-obama-phone.1292241/
this dude did a lot for us lol
idk what screen you are at, if you could detail what it is that you see, I may be able to help. I'm "Windows Desktop" on that thread btw.
As for rooting the device, if you're hard bricked there may be no way unless you can get through.
I'm assuming u were frp locked(Google locked) leading you to this problem.
-Edit
After some research i found out that if this happens you can enter "default_password" and it could let you in, apparently it's only some Android phones, and on top of that only some versions of those kernels, even if you didn't put a PIN/Password. If it doesn't work it could be some other number associated with the phone, I've tried all that i could think of with nothing helping so idk what to say. Well give it a try and lemme know what happens.