[Troubleshoot] PIT FILE Bootloader CSC Modem, firmware and Debrick Image for s7562 - Samsung Galaxy S Duos

I am not responsible for any damages that happen by using this guide to you or your mobile or your pc. this guide is only meant for samsung s dous gt-s7562 which might had been bricked and have no other option to get it back, can try this guide to bring it back to life or return to a factory default state completely, yet there is no guarantee that it will work with every device. don't blame me.
These files here are to be used with care and only on Samsung Galaxy S Dous GT-S7562.
Information about what we are going to do here
basically these files will flash, re-partition and write data to your device the way it was shipped to you. so whatever changes you have made to the device system, boot or recovery will be replaced to default sorting out any bugs within the different partitions.
you may hesitate to flash this firmware rather than your country firmware, but the first thing we should do here is make your phone start working again. after that you can flash to your baseband. the files are all here on xda. and you can always find a way around.
Requirements
1. A bricked gt-s7562 where you can only have access to the download mode by pressing Down+Power button+Home button if its hard brick where you can't even reach download mode and recovery and looks like its dead, check thread post #4
2. Working Data cable
3. PC with windows
4. Make sure your recovery is dead have you been pressing all the up down home and power button and releasing after seeing the samsung screen?
Instructions. (follow it or stay dead)
1. Download the zip file S7562DXBMD1_S7562OLBBMD1_S7562XXBMD2_Android_4.0.4_4 and save it on your pc.
2. Extract the files using any winzip, winrar, 7zip
3. Open odin3 v3.07.exe
4. Browse PIT and navigate to the downloaded folder to find the file "signed_kyle_v2_0604.pit"
5. Browse Bootloader and open file BOOTLOADER_S7562XXBMD2_1216076_REV02_user_low_ship.tar.md5
6. Browse PDA and open file CODE_S7562XXBMD2_1216076_REV02_user_low_ship.tar.md5
7. Browse Phone and open file MODEM_S7562DXBMD1_1216076_REV02_user_low_ship.tar.md5
8. Browse CSC and Open file CSC_OLB_S7562OLBBMD1_1216076_REV02_user_low_ship.tar.md5
9. Check that auto reboot, re-partition and f-reset time are ticked. (see screenshot to cross check.)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
10. You sure? then start the process and wait for it to complete.

Thanks for ur post
Have tried ur method 4-5 times still phone stuck at Samsung bootanimation. Only download mode is accessible
Any help would be appreciated

daneal2u said:
Thanks for ur post
Have tried ur method 4-5 times still phone stuck at Samsung bootanimation. Only download mode is accessible
Any help would be appreciated
Click to expand...
Click to collapse
Have you tried removing the battery then switch on again and try to get into recovery mode?
If you can get into recovery mode after flashing pit and pda through odin. wipe cache and factory reset then try again.
also it would be helpful if you can provide a screenshot if there are any errors while flashing in odin

Hard Brick to Unbrick image Recovery Method
Method Not working
Here is another Method that I've found but, still haven't come across a situation like this to try and test out myself, see If anyone whose Samsung S dous s7562 (Only this device) has a Problem where he can't even reach the download mode or the recovery mode Only then you should try this.
if You're able to either get to download mode or recovery, please don't try this at all unless you're a scientist or an engineer.
Requirement
1. An external sd card 4gb(class 10) (1st priority) or 16gb (both untested) (2GB and 8GB won't work, must be class 10)
2. Card reader and
3. PC.
Procedure
1st Connect the external sd card to the card reader move all the files to your pc and format it.
2nd. Download and extract this debrick.img image from debrick.zip
3rd Download and extract this software win iso burner
4th. Open the software win32diskimager.exe and browse the debrick.img
6th. Write the debrick.img onto it.
After it's successfully written, close it and remove battery and put the sdcard in your device and switch it on.
if you can then get into download mode, you should follow the instructions from the 1st post above.

Sometimes getting into recovery could be quite a tricky task with this device, before concluding that you can't reach your recovery.
Please try holding power button + home button + up and down button both at the same time(at the center) and keep holding untill you see the samsung S dous 7562 screen then leave the button.

No result Billysam
Nothing happened
I even made my own jig that woks fine with other Samsung phones
But mine nothing it start the phone though but no download mode
And isn't there any other program that can detect the phone on PC while its off like android commander .. as you suggest resting might be the only solution ... or might be some hardware ic problem !!!!

Adb won't work, unless your device had usb debugging enabled or a matter of fact your device to be readable enough to know it is usb debugable. But I am sorry to say it looks more like the storage is all messed up with bruises so much that even kernel is not readable. Your was not a case of bad flashing rom or kernel, it was a physical damage. And when that happens to any storage device, be it a cd, dvd, hard disks or a mobile emmc. You change it.
I am not really a hardware expert, but dwelling into this matter further, trying to repair it, wouldn't be easy at all, because maybe I am right about the chip, and it solves to some extent but what if you replace it, then come to know that there were more damages suffered?

Hello Billysam,
5 points and 5 points only needed to mention .. May be you are right troubleshooting is over .. But for future consideration .. And small brainstorm ..
Point No. 1 :
Mobile repair store actually did not damage, broke or misplace and thing in my phone because they did not open it at all ... As soon as they saw the phone they its software related problem though I mentioned that the phone has an accident .. One of them actually told that if its hardware related (emmc ic) it will show the samsung logo and then restart .. even that one them told the solution is JTAG ..
Point No. 2 :
I had second S duos which I gifted after I did mix of the parts and reached to conclusion that the problem is the board which has every thing intact
piece by piece cause I separated every little part camera, led, speaker and antenna even the screen with the touch working perfectly fine the accident did not harm the screen in any way not a scratch ... And also I rooted, custom rom, stock rom with odin and custom rom again and phone was working fine with no problems till it hit the wall .. I know pretty much every thing about boot, recovery, recovery mode, fast boot and adb shell and also download mode ..
Point No. 3 :
The phone show the start screen and even download mode but as soon as it shows those it restarts .. I even made my own JIG .. whic works perfectly with other samsung phone goes immediately to download mode .. but my phone starts but nothing on the screen and restart like before ..
Point No. 4 :
Debrick !! what does it do ??? !!!! because it didn't do any thing to my phone ... it need little explaining so may be I did some wrong with the steps .. And I used 2 g.b. external sd card .. Is it compulsory to use more then 2 g.b. sd card ??!! ... ( what it had to do with starting dead phone and how ?? ) ..
Point No. 5 :
Used to and currently also using Nokia phones in their flashing program there was a mode of dead phone flashing which does not require starting phone full dead and flashes fine .. Isn't there a method like that for samsung a program or something ... yeah may its the JTAG ... I mean some thing with usb cable like fastboot or any other android commander or event trough connecting it with another phone ...
Sorry for inconvenience ... thanks alot ....

MaxxiMillian said:
Hello Billysam,
5 points and 5 points only needed to mention .. May be you are right troubleshooting is over .. But for future consideration .. And small brainstorm ..
Point No. 1 :
Mobile repair store actually did not damage, broke or misplace and thing in my phone because they did not open it at all ... As soon as they saw the phone they its software related problem though I mentioned that the phone has an accident .. One of them actually told that if its hardware related (emmc ic) it will show the samsung logo and then restart .. even that one them told the solution is JTAG ..
Point No. 2 :
I had second S duos which I gifted after I did mix of the parts and reached to conclusion that the problem is the board which has every thing intact
piece by piece cause I separated every little part camera, led, speaker and antenna even the screen with the touch working perfectly fine the accident did not harm the screen in any way not a scratch ... And also I rooted, custom rom, stock rom with odin and custom rom again and phone was working fine with no problems till it hit the wall .. I know pretty much every thing about boot, recovery, recovery mode, fast boot and adb shell and also download mode ..
Point No. 3 :
The phone show the start screen and even download mode but as soon as it shows those it restarts .. I even made my own JIG .. whic works perfectly with other samsung phone goes immediately to download mode .. but my phone starts but nothing on the screen and restart like before ..
Point No. 4 :
Debrick !! what does it do ??? !!!! because it didn't do any thing to my phone ... it need little explaining so may be I did some wrong with the steps .. And I used 2 g.b. external sd card .. Is it compulsory to use more then 2 g.b. sd card ??!! ... ( what it had to do with starting dead phone and how ?? ) ..
Point No. 5 :
Used to and currently also using Nokia phones in their flashing program there was a mode of dead phone flashing which does not require starting phone full dead and flashes fine .. Isn't there a method like that for samsung a program or something ... yeah may its the JTAG ... I mean some thing with usb cable like fastboot or any other android commander or event trough connecting it with another phone ...
Sorry for inconvenience ... thanks alot ....
Click to expand...
Click to collapse
You shouldn't have used a 2gb card, thats why I said more than 2GB dear. The reason I am not sure about this is clear, I havent tested this method.
the debrick.img is basically a image that contains boot files, by writing this img on an external sdcard, we are making the device use the external sdcard as an internal to boot, like a live linux cd or a bootable windows cd. our device is 4GB internal if I am not mistaken, my guess would be try with a 4GB sdcard preferably a class10, if that also doesnt work try another card 8 or 16gb.
people have used this method on other devices with success too, but on our devices, if you can make it work, it would be the first, and you my friend will be the first one.

Hard bricked s duos 7562
Phone turn on with little vibration after that the screen remains black screen. Whatever changes that i done with 3 button combination it still remains black screen.
Even i tried the "Debrick" method with 8gb SD card. No use..!!!
And finally done my DIY USB Jig also but still no use..
Think so the phone get hard bricked. So what can i do further??

My phone just stuck in firmware upgrade encountered an issue please select recovery mode in kies and try again after try your method
what should i do?
thanks before

just_saprol said:
My phone just stuck in firmware upgrade encountered an issue please select recovery mode in kies and try again after try your method
what should i do?
thanks before
Click to expand...
Click to collapse
Sorry for the late reply, please quote or mention my username ID with an @ so that I can get notified and reply sooner.
which method did you used exactly? did it get interrupted or lost power in the middle of the process? can you still access download mode?
always take care when flashing that you don't lose power in between the process and don't force close and wait patiently.

gvprasad said:
Phone turn on with little vibration after that the screen remains black screen. Whatever changes that i done with 3 button combination it still remains black screen.
Even i tried the "Debrick" method with 8gb SD card. No use..!!!
And finally done my DIY USB Jig also but still no use..
Think so the phone get hard bricked. So what can i do further??
Click to expand...
Click to collapse
So, 8GB card also didn't worked. I am sorry that it didn't worked out for you. the debrick method it's still not been successfully done for our device. although I have seen other people doing it on their device for some reason, it's not taking on our device. there a 16GB card was used. (the result varied for different users) I don't know what can do further than this to say try with a 16GB card as well or give it to your local shop.
last resort is a JTAG that a professional should try. which I am not and myself had given to the expert local shop when faced a hard brick.

@billysam thank u a zillion for ur guide.
I had this phone lying around for an year or 2 & I just tried this & bam.. it booted up
Cant thank u enough.
ur the best

daneal2u said:
@billysam thank u a zillion for ur guide.
I had this phone lying around for an year or 2 & I just tried this & bam.. it booted up
Cant thank u enough.
ur the best
Click to expand...
Click to collapse
Wow! Congrats buddy and thank you for letting me know that it did some good for you at least. you were the first to try my method from the 1st post which failed the first time. but which one did worked for you exactly? the debrick? can you share what you did?
it will help others as well too.

billysam said:
Wow! Congrats buddy and thank you for letting me know that it did some good for you at least. you were the first to try my method from the 1st post which failed the first time. but which one did worked for you exactly? the debrick? can you share what you did?
it will help others as well too.
Click to expand...
Click to collapse
I did the 1st one
followed each & every step & got my s duos resurrected thanks 2 u @billysam

the 4th post doesn't help me !!!! i used two 8GB sd cards and doesn't work for me!!!! (one with class 10 and the other class 4)
i neeeeeeeeeeeeed another solution please !!!! :crying: :crying: :crying:
sorry for bad english !

billysam said:
Here is another Method that I've found but, still haven't come across a situation like this to try and test out myself, see If anyone whose Samsung S dous s7562 (Only this device) has a Problem where he can't even reach the download mode or the recovery mode Only then you should try this.
if You're able to either get to download mode or recovery, please don't try this at all unless you're a scientist or an engineer.
Requirement
1. An external sd card 4gb(class 10) (1st priority) or 16gb (both untested) (2GB and 8GB won't work, must be class 10)
2. Card reader and
3. PC.
Procedure
1st Connect the external sd card to the card reader move all the files to your pc and format it.
2nd. Download and extract this debrick.img image from debrick.zip
3rd Download and extract this software win iso burner
4th. Open the software win32diskimager.exe and browse the debrick.img
6th. Write the debrick.img onto it.
After it's successfully written, close it and remove battery and put the sdcard in your device and switch it on.
if you can then get into download mode, you should follow the instructions from the 1st post above.
Click to expand...
Click to collapse
Could you explain what that debrick image does and where its from?
Gesendet von meinem GT-S7562

KlinkOnE said:
Could you explain what that debrick image does and where its from?
Gesendet von meinem GT-S7562
Click to expand...
Click to collapse
well the debrick image is from my samsung s duos GT-S7562, the debrick img was taken out from running the dd command
if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=128
where mmcblk0 is the location where all the partition layout information is stored.
it copies the files AMSS.MBN and AMSSHD.MBN and puts them onto the image file which are the files responsible for the fast boot.
so basically its an image of s duos device boot. so we are writing the files on an external card the same way its written on our internal card.
Now, I have read on xda forum itself of other samsung S III users(or you can say mobiles using snapdragon) have this wiring setup where in case internal card is not readable it shifts to the external card.
Hope this answer your Question?
But seriously, It's just a theory in our case. there haven't been any report of anyone from our S Duos users getting this to work.
although I feel it should work, if not, might take some hardware wiring to make this work. that would be practical.

billysam said:
well the debrick image is from my samsung s duos GT-S7562, the debrick img was taken out from running the dd command
if=/dev/block/mmcblk0 of=/sdcard/debrick.img bs=1M count=128
where mmcblk0 is the location where all the partition layout information is stored.
it copies the files AMSS.MBN and AMSSHD.MBN and puts them onto the image file which are the files responsible for the fast boot.
so basically its an image of s duos device boot. so we are writing the files on an external card the same way its written on our internal card.
Now, I have read on xda forum itself of other samsung S III users(or you can say mobiles using snapdragon) have this wiring setup where in case internal card is not readable it shifts to the external card.
Hope this answer your Question?
But seriously, It's just a theory in our case. there haven't been any report of anyone from our S Duos users getting this to work.
although I feel it should work, if not, might take some hardware wiring to make this work. that would be practical.
Click to expand...
Click to collapse
Yes thanks...
i already tried that without success.
I found the information in that thread http://forum.xda-developers.com/android/apps-games/app-partitions-backup-t3003599
which lead me to the s3 threads too.
Without using dd commands the app does it for you.
That method is propably not supported.
damn i still have a hard bricked s7562 lying around waiting for its time

Related

[RECOVERY AND UPDATE] how to recover your SGS gt-i9000 Famous Black screen of death.

This is all thanks to the awesome threads on this website.. No credit of programming will be claimed by me.
*warning* this can be done only if you have a device that forces the samsung galaxy s g or gt i9000 to go in to download mode.
Ok so here is the story, when the samsung galaxy S froyo beta was out I kind of editted the regedit of samsung to be able to install it...
What I didn't know and wasn't noticed by anyone as I've surfed down google to the 200th pages... was that after the reg edit update the Volume down + home button + off switch combination falls of and will not work anymore.
So I waited untill it was out officially in the Netherlands (eindhoven)
What I did was the folowing:
I went to vodafone and they tried to update it. with the force device (big blue box with 12 buttons on it with the buttons 2 and 6 were clicked down).
When they tried to update the phone went off and it lost it's complete firmware. aka PHONE - ! - COMPUTER.. I went home and searched of the web and found here that there was a kind off update.zip. (when I find it I will edit this post and upload it) I downloaded the file and extracted the contents on a SD card. I went back to vodafone and let them force the phone in to download mode again. after that odin instantly recognized and updated the phone to Android 2.2 Froyo update for Galaxy S.
So here are the simple steps.
1. Don't panic.
2. Surf this forum for the update.zip if I still haven't uploaded it. and mainly search for the tag: black screen of death. or phone + ! + computer.
When you have the file. follow step 3.
3. Extract the contents of the update.zip file to the removable SD card of your phone with another device note like root:Sd/update/(files) but like root:sd/(files) the files must be directly available to the phone without having to be searching in to another folder. and plug the sd-card back in the phone.
4. If you have such blue device to force in to download mode then just use odin and update phone. if not, then go to the nearest and trustworthy phone store and make them force it into the download mode... and follow the rest of the steps.
5. step 5 is the most attention worthy part there is: Either bring your own laptop with the correct odin and the correct files and USB cable for when it's in download mode to update it. or either give it to the person behind the counter and let him update it.
6. When froyo is installed give it time to run and scan all it needs to do, otherwise it will lagg and only frustrate you.
7. after couple of minutes froyo is ready for use. after this.look for a reliable lagg fixer because froyo laggs the same way the mind of your mother-in-law does when you're trying to talk sense in to her mind...
If I'm correct after these steps you should be able to use your phone again and have froyo installed and working.
If this hasn't worked, then I advice to either repeat these steps (hence the bring your own laptop) or let the phone-store guy do his thing and force the install. REMEMBER these people usually give up after 1 or 2 try's but it's your phone and they don't care.. so just stand firm and say, I would like you to give it another try..and if he refuses. you can just tell him you won't leave untill he has done it over and over untill it's done or let you self try it and crawl behind the counter.
ALL CREDITS GO TO THE PEOPLE THAT HAVE WRITTEN THE PROGRAMS AND GIVEN ME THE OPPORTUNITY TO COMBINE THE STEPS AND FIX THIS.
But hey if you think the credits belong to me since I wrote this guide. then by all means
I can't access the recovery mode, but I can access the download mode. I also used the Kies registry hack to upgrade to 2.2.
Which update.zip file you are talking about? There are a million different ones!
I do not have an external SD card. Is it still possible to fix the phone? No offense but your solution doesn't really offer a solution at all. It only tells us to go somewhere else to get it fixed!
What is the correct Odin, what are the correct files? PIT, PDA, PHONE, CSC, update.zip? Links?

[GUIDE]Root/Recovery Hapai X710D MTK6577

Here are all the steps to root and install a custom recovery on your X710D
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1. Download files HERE
2. Extract 'Android flash' anywhere to your desktop
3. Open the folder within called 'USB VCOM Driver' and chose the folder then file that is your operating system (the .inf) and paste it to your desktop
4. Pull the battery out of your phone and connect the phone to you computer whilst holding the volume up button
5. Open device manager. You should see your phone (it re-appeared every 5 seconds for me). Right click on your phone and press update driver, then browse manually for the .inf file you put on your desktop. Once you've done that disconnect your phone
6. Open 'Android flash' and open Flash_tool and select all the files to make it look like the picture below
7. Press download, then plug in your phone whilst pressing volume up button
8. Done! You now have CWM and have rooted your phone! There are also some other apps that are added too
If you are having issues with your IMEI code read this post here: http://forum.xda-developers.com/showpost.php?p=30534835&postcount=32
There's also a issue with external sd cards which is currently being worked on. (phone can't write to sd card. if you attempt, phone reports sd card as damaged and sd card will need to be re-formatted)
Big thanks to yiminghung, he helped me figure out how to do it.
If I've made any errors in this please tell me I will fix asap, and if anyone has any updates/ROMs, please message me and I'll post them here.
Looks Good!
additional information
for additional information look here:
http://forum.xda-developers.com/showpost.php?p=30534835&postcount=32
good work!
help for the mtk6577 n9770
Hi,
Please help me
This is what happen first
After I root the phone (n9770 mtk6577) then wipe all data from user and system apps the camera now doesnt work, I press the app and is in black, I dont know if it is the boot image rooted is giving me the problem but I flash again the original boot image and get nothing the same, then I did a factory reset and is same no camera, maybe is not software faulty but hardware? I will try reflashing the stock rom 4.0.9, could you give me some direction on how to flash because I used SP_Flash_Tool_v3.1222.00 and i have installed the usb driver for win 7 64bit, please let me know what direction I should follow.
Now is what i have done after that
I have flash with the tool the custom recovery but I did not read that i had to uncheck boot and preloader, and now the phone is not booting, pleasee pleasee help me
I have donwload the rom but i dont know how to reflash or simply fix the preloader issue
ztrike said:
Hi,
Please help me
This is what happen first
After I root the phone (n9770 mtk6577) then wipe all data from user and system apps the camera now doesnt work, I press the app and is in black, I dont know if it is the boot image rooted is giving me the problem but I flash again the original boot image and get nothing the same, then I did a factory reset and is same no camera, maybe is not software faulty but hardware? I will try reflashing the stock rom 4.0.9, could you give me some direction on how to flash because I used SP_Flash_Tool_v3.1222.00 and i have installed the usb driver for win 7 64bit, please let me know what direction I should follow.
Now is what i have done after that
I have flash with the tool the custom recovery but I did not read that i had to uncheck boot and preloader, and now the phone is not booting, pleasee pleasee help me
I have donwload the rom but i dont know how to reflash or simply fix the preloader issue
Click to expand...
Click to collapse
doppelpost!
see here
http://forum.xda-developers.com/showpost.php?p=30604249&postcount=40
Getting warning message "not all images are correctly loaded"
Followed all step to the "click Download", when i click download a warning dialog tells me that not all images are correctly loaded, which may cause boot up issue!, do I want to continue"
I have checked many times and all images are set as you have shown in your screen shot?
Any Idea what is not right?
Edit: it appears to be caused by DSP_BL not being selected??
info
hi
may I ask an information.
I'm going to buy a zp900 9300+ is a clone of the zoppo zp900
with mtk6577 and 512mb of ram... with android 4.1.1
do you think is possible to use the same procedure for the root
of the phone? do I have to uncheck something? or change any file?
thanks
Antonio
paperinik77 said:
hi
may I ask an information.
I'm going to buy a zp900 9300+ is a clone of the zoppo zp900
with mtk6577 and 512mb of ram... with android 4.1.1
do you think is possible to use the same procedure for the root
of the phone? do I have to uncheck something? or change any file?
thanks
Antonio
Click to expand...
Click to collapse
i bought the same phone and would love to know if this root method works for this phone, it has the same MTK6577 CPU as the haipai X710D
Hi all. I am a new registered. My name is Filippo and I'm Italian (sorry for my English googltraslate).
In a few days I will come to me x710d. I wanted to ask you questions.
1) What improvements does the root of the phone? Have to wait at the root with the update to Android 4.1 bj?
2) Before you root, I have to make a backup / image of the system for use in case I have a problem? If it is, how should I do it?
3) This root change the size of the internal memory or I'll do it later? In the second case, how can I swap the memory card with the internal one?
The last question is that there is risk in doing these operations? You advise me to do to its?
Excuse my inexperience and thank you all in advance.
Thank you so much for posting this. The Flash tool is quite confusing to use. Your instructions really helped.
---------- Post added at 11:30 AM ---------- Previous post was at 11:26 AM ----------
Technica said:
Followed all step to the "click Download", when i click download a warning dialog tells me that not all images are correctly loaded, which may cause boot up issue!, do I want to continue"
I have checked many times and all images are set as you have shown in your screen shot?
Any Idea what is not right?
Edit: it appears to be caused by DSP_BL not being selected??
Click to expand...
Click to collapse
Just click "YES". you dont have to check any of the images.
Hi, i´m seller of this model ( X810d ) and it work´s like a charm too!
Thanks so much!
WWW.HIPHONEBRAZIL.BLOGSPOT.COM
Filippo.digi said:
Hi all. I am a new registered. My name is Filippo and I'm Italian (sorry for my English googltraslate).
In a few days I will come to me x710d. I wanted to ask you questions.
1) What improvements does the root of the phone? Have to wait at the root with the update to Android 4.1 bj?
2) Before you root, I have to make a backup / image of the system for use in case I have a problem? If it is, how should I do it?
3) This root change the size of the internal memory or I'll do it later? In the second case, how can I swap the memory card with the internal one?
The last question is that there is risk in doing these operations? You advise me to do to its?
Excuse my inexperience and thank you all in advance.
Click to expand...
Click to collapse
nobody can help me?
silvacrest said:
i bought the same phone and would love to know if this root method works for this phone, it has the same MTK6577 CPU as the haipai X710D
Click to expand...
Click to collapse
i've just got this model too
great work
i've just want to know how to root it
Success or Failure
I have tried many ways\suggestions to root my X710D and this is the only one I have not yet tried.
Before I do try this procedure It would be helpful if people that have done this on the X710D could report their success or failure.
I would like to know this because I do not know enough and do not want the get into more trouble with the device.
Thanks for sharing your experiences....
I successfully rooted my x710d using the steps given. Before I rooted my phone, I updated it to the latest 4.0.9 (latest firmware is in another forum read here).
This root also comes with the custom recovery (probably taken from HTC because there is an HTC boot screen logo). However, I encountered three main problems after the I successfully executed everything.
First, my IMEI got erased (solved this using ZOPO). (read here there is an explanation how to put your IMEI's back. )
Second, external Sd-card gets no write permissions and also it errors damaged sd-card from time to time (still finding ways to solve this).
Third; Since, I live in Japan, I am still finding ways how to enable MMS on this thing through sofbank.
for the good side;
Rooted phone is awesome.
This phone is quite fast for its price especially with the new firmware.
Sofbank APN settings where automatically there already (I dunno if this was because of ICS or X710d firmware just came in with these settings). Everything else is working very well. Camera, Bluetooth, GPS, WIFI, Radio, etc....
GreatPharaoh Thanks for such a clear and detailed post, this is what makes XDADevelopers such a great community.
Your reply is just what I needed to hear, me being new to this platform.
I purchased one of these as a development machine with the intention of using it as my phone also, but I had been highlighted that some sellers just are not in a position to support the products they sell. We also order two more from another seller to edge our bets on delivery times, but when we discovered some issues and the second seller also demonstrated that they have poor after sales support when managed to cancel these additional two X710D (with an insulting response from this seller).
I my case I asked very specific questions about the product and got nothing but positive replies before purchase, in addition I needed the device to have a working compass and magnetic sensor which also received a "Yes" but once we confirmed payment communication with the delivery and questions dried up. Once delivered, we found that while the X710D does have a Compass and Magnetic sensor they are not implemented.
Now we are concerned about the IMEI bug and these seller does not want to know about it.
So, while we accepted some risk in purchasing a Chinese phone at reasonable price, we really are concerned about this model and did not anticipate the amount of risk.
Now being a software developer (not Android or Linux) I had the approach the we can fix anything, but at this time in a new OS world it has proven to be again high risk and we can not afford to brick this device. So we have decided to return it for a refund.
I will continue to monitor these posts, because I am keen to see if things get resolved and to learn from the experiences of others. It is great to see many members with far greater skills than mine helping each other.
I have also had great hand-holding from ColonelZap through some of out attempts to resolve these issues, so a huge thanks to him.
Again thanks GreatPharaoh for a great post and I am sure that it will help others looking at the X710D and maybe they will find a solution to your remaining issues.
Technica
GreatPharaoh said:
I successfully roThamy x710d using the steps given. Before I rooted my phone, I updated it to the latest 4.0.9 (latest firmware is in another forum read here).
This root also comes with the custom recovery (probably taken from HTC because there is an HTC boot screen logo). However, I encountered three main problems after the I successfully executed everything.
First, my IMEI got erased (solved this using ZOPO). (read here there is an explanation how to put your IMEI's back. )
Second, external Sd-card gets no write permissions and also it errors damaged sd-card from time to time (still finding ways to solve this).
....
Click to expand...
Click to collapse
The X710D is a copy of the HTC Evo 4g LTE which will explain the boot logo.
Thank you for mentioning the sd card issue, i bought a rather expensive 32gb class 10 card to find it didnt work in my phone. Its very difficult to get it to work and when it does work my phone cant write to it. If you find a fix ill update the maim post.
Ive noticed lots of people mentioning issues with their imei codes. I havent come across this issue but there is a fix at post 3. Ill update the main post with it later.
Im posting from my phone sp sorry for typing errors. Whats th best keyboard for this phone? Im currently usibg swype but as you can see its.pretty bad. The defaultkeyboard it even more difficult to type.on
x710d sd card issue
jaw2floor said:
The X710D is a copy of the HTC Evo 4g LTE which will explain the boot logo.
Thank you for mentioning the sd card issue, i bought a rather expensive 32gb class 10 card to find it didnt work in my phone. Its very difficult to get it to work and when it does work my phone cant write to it. If you find a fix ill update the maim post.
Ive noticed lots of people mentioning issues with their imei codes. I havent come across this issue but there is a fix at post 3. Ill update the main post with it later.
Im posting from my phone sp sorry for typing errors. Whats th best keyboard for this phone? Im currently usibg swype but as you can see its.pretty bad. The defaultkeyboard it even more difficult to type.on
Click to expand...
Click to collapse
did you get a chance to see what the fix is for sd card problems? its driving me crazy
Lost IMEI on x710D
Is this issue of losing IMEI only related to the X710D or is this a common problem with Chinese Android phones?
Once again, deepest Thanks to Jaw2Floor for posting the steps.
@Technica; yup, I couldn't agree with you more about these sellers. Seems like these phones where probably manufactured in someones old garage with one or two developers who couldn't do much english. And they would just send em to these vendors for retail. These sellers, However, are so smart with marketing, they would flood youtube and google with fake reviews (although most of em are just unboxings) and lead us with just curiosities. This is probably why they are so good at selling but very bad in support. Long story short, we are only paying for the hardware here.
For the Imei case: I wonder why everyone is not having this problem..?. Maybe this is also hardware related. This was the first problem I faced right after my first ever Factory Default Reset on the phone. I was so terrified that moment, I thought I bricked or fried the modem.
The Sd-card issue is still there: "My temporary fix is reformat card in PC and recopy your media. Do this every time you get the damaged sd-card error."
I can access my card with read permissions only. My media gallery and other media apps can see the card and the contents. However, as soon as I start to write the card (e.g. making new folder or deleting a file from any file explorer app) the "Damaged sd-card error" will start to appear and you wont be able to get rid of this until you take the card out, format it in your PC, recopy all your media, then mount it again in your x710d. This is what ive been doin for the past couple of days to enjoy music in this phone.
The Headphone Jack is also too deep. If you compare side by side the stock headphone/mic with any other regular headphone, this one came in with a much longer jack. I was able to fix this problem by widening the headphone hole on the phone's back casing and also splicing an mm of rubber on my regular headphone jack.
The stock Email-app are having problems setting up with Yahoo's mail servers. So, im using K-9 mail for now.
As for now, I am enjoying this phone. I get a lot of eye's whenever I take this out of my pocket in Tokyo trains. Its not a note! Its the money-saver version.

[Fix] EMMC brick bug issue on P6200/P6210 16gb? Give this a go!!!

For those who have been living under a rock, problematic leaked builds of ICS were released for several different Samsung devices a few months ago. Users of those Devices for instance soon discovered that their devices were being ffected by what came to be known as the MMC_CAP_ERASE bug. Shortly after this*occurred, XDA Senior Member hg42 came up with a way to revive downed devices.
Now thanks to some more ingeniuty on his part, hg42 has also developed a companion application known as Partition Scanner to assist in this process.*The application features:
emmc_scan_all_partitions_once.zip
emmc_scan_all_partitions_infinitely.zip
these allow fast scanning of all blocks of all emmc partitions in 1MiB steps.
The main purpose is to access each emmc block to find any bricked block in the partitions after repartitioning.
The “infinitely” variant runs checks infinitely, which may help to find emmc brick effects which only occur sporadically (if such effect really exists). Run this as long as you want. Reboot to finish.
If this freezes the last partition shown may have a bricked block inside.
emmc_find_brick_start.zip
emmc_find_brick_end.zip
these scan the whole emmc device.
emmc_find_brick_start starts scanning from the beginning of the device upward.
emmc_find_brick_end searches the end of the device and then scans downward.
If this runs up to the end or down to zero (showing a message with “completed –> OK”), no bricked block was found.
If it freezes, the block shown last with “…” at end of line is the first bricked block in that direction.
The line before with “-> ok” is the first usable block before/after the brick.
The application has received excellent reviews, so if you’re one of those people currently facing an EMMC issue, or you had the issue previously and gave up on your device, head on over to the companion thread and give this a go.
Click to expand...
Click to collapse
Original xda news: http://www.xda-developers.com/android/partition-scanner-helps-your-emmc-bricked-devices/
Original thread by hg42: http://forum.xda-developers.com/showthread.php?t=1667886
He even provides PITs for our devices, so get a bit into Linux, and fix it by yourself, You can't make it worse I guess..
Anything more to say? Hang onto it, unbrick it and kick Samsungs ass once again!!
Greetings from Australia!
Sent from my GT-P6200 using xda app-developers app
Bad2hold said:
Original xda news: http://www.xda-developers.com/android/partition-scanner-helps-your-emmc-bricked-devices/
Original thread by hg42: http://forum.xda-developers.com/showthread.php?t=1667886
He even provides PITs for our devices, so get a bit into Linux, and fix it by yourself, You can't make it worse I guess..
Anything more to say? Hang onto it, unbrick it and kick Samsungs ass once again!!
Greetings from Australia!
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
@Bad2hold - have you tried this yourself as I am desperate for help in unbricking my device that Samsung refuse to repair as it is the P-6200L (non-UK model).
I can't use ADB as my pc won't recognise the Tab, have tried flashing the .pit file and firmware but no joy, can't use the partition scanner as I can't get it to scan the internal memory (it scans the external SD card instead).
I can install CWM recovery and also get to stock recovery but the Tab will not go past the white Galaxy Tab logo.
Any help is highly appreciated
There is good chance you can recover. try multiple factory resets. flash earlirst odin package, preferrably with a boot.bin, after flash, and stuck on logo, boot to recovery and factory reset. try wiping a few more times if it is still stuck. i usually have to do this when going back to stock. one time i had to wipe from custom recovery, and a combonation of other things..
If you have recovery, youre lucky.
If you give up, you can for JTAG, normally for hard bricks. mobiltechvideos.com saved me from hardbrick.
Id play around a bit before I send to JTAG.
best of luck..
chrisrotolo said:
There is good chance you can recover. try multiple factory resets. flash earlirst odin package, preferrably with a boot.bin, after flash, and stuck on logo, boot to recovery and factory reset. try wiping a few more times if it is still stuck. i usually have to do this when going back to stock. one time i had to wipe from custom recovery, and a combonation of other things..
If you have recovery, youre lucky.
If you give up, you can for JTAG, normally for hard bricks. mobiltechvideos.com saved me from hardbrick.
Id play around a bit before I send to JTAG.
best of luck..
Click to expand...
Click to collapse
Thanks for the advice mate.
Am going to flash it with the honeycomb firmware it came with from Sammobile and try a few factory resets to see if that works.
If not have found a place in the UK that will JTAG it for £38 if all else fails...:good:
UPDATE: Honeycomb doesn't let me access recovery so no way to wipe from there. Recovery is available on an ICS rom but am reluctant wipe in stock recovery as that's how I go in this mess to begin with :crying:
I currently cant help, as iam travelling without a pc... but this guy who developed this scanner, has pit files available for our device. So there is a good chance to get help from him. And iam sure, with some hours off every week, where u get bored, u can actually fix it by yourself as u already figured out that much... i would love to help, its a challange you know? maybe iam gonna buy a laptop... =p
Update: just curious, is it scanning without a external sd inserted? Because internal and sd are swapped in cwm recovery since 3 versions too...
Sent from my GT-P6200 using xda app-developers app
@Bad2hold - Thanks for the reply, have tried flashing the .pit file but no joy.
Can't get the scanner to scan internal card as it's loaded on my external sd and can't push it to the internal which then means I can't remove the external sd.
Have tried flashing various honeycomb and ICS firmwares with a combination of .pit files, the process flashed fine without errors but still no boot past the white Samsung writing
Sent from my GT-I9300 using xda premium
Just one question:
do I use it if my device got bricked (fortunately it s not the case), or do I use it to remove the brick bug risk from my device?
Thanks for your answer...
unclefab said:
Just one question:
do I use it if my device got bricked (fortunately it s not the case), or do I use it to remove the brick bug risk from my device?
Thanks for your answer...
Click to expand...
Click to collapse
I think we cannot remove the brickbug on stock ICS...that pit file just for solving hardbrick issue...
Sent from my GT-P6200 using xda premium
U can actually remove the brick bug issue, this is, what this post is about.
Basically, you just have to find the bad blocks in your sd partition.
After you found them, all is left, is to repartition your sd around the bricked blocks, which you have to delete from your partition.
He mentions several methods to use adb and other tools, helping to do this.
And i really recommend reading a bit through his first post, found the same problem after a minute:
I also had the following problem:
I couldn't format my internal sdcard with the cm9 recovery. I think it's too big for the mkfs.vfat tool of current cm9. So I installed another recovery, formatted the internal sd (I thought).
This erased all my current backups and downloads, because in reality it was my external sd. Fortunately I had a backup of the external sdcard from before rescuing my phone.
So, you may want to create a backup of your external sdcard first.
Then double check which is your internal sdcard (the UMS partition) and which is your external sdcard.
Or you could remove the external sd completely. But think about when to remove it, because you might need it for some files (e.g. to use the emmc partition scanner).
Click to expand...
Click to collapse
Of course, if u r not familiar with linux, u probably wont fix it in an hour.
But you can learn a lot within an hour. First of all, figure out how to connect your device to adb. (Which is still possible, if you didnt smash your tab against the wall or so...) After that, it should be lot easier to follow his instructions.(not just because u have adb working, but because you know what he is actually talking about.)
And he is really willing to help, so figure out as much as possible after connected to adb and just ask in his post if you get stuck.
Dont forget: if its not a issue by malfunctioning/broken hardware, then you actually can fix everything with your pc, you just need to know how.. so dont give up!!!
here his post again: http://forum.xda-developers.com/showthread.php?t=1667886
And @kersey: what pit file did u flash? The pits he provides are to repartition your SD AFTER you located the bricked blocks. But you cant know, if you cant get his scanner running..? You have to format data partition in recovery after flashing one of those, because of missing file system.
Note: Never flash a stock ICS after you fixed it. It will brick your device again. But u r safe with cm9 and others.
Sent from my GT-P6200 using xda app-developers app
Good news all, after much trial and error and more flashing than your average pervert I have revived my tablet from the dead with a big thank you to hg42 for his scanner and extra advice.
Thanks to all those who helped in this post too :good:
Dude, if you dont mind, what exactly have you done to revive your tab?
Not exactly, just a quick guide to avoid the most common mistakes.
Thanx!
Sent from my GT-P6200 using xda app-developers app
Bad2hold said:
Dude, if you dont mind, what exactly have you done to revive your tab?
Not exactly, just a quick guide to avoid the most common mistakes.
Thanx!
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
It was pretty simple to revive it with hg42's help.
The first thing you need to do is ensure you have CWM recovery, as the scanning tools only work with that.
Download hg42 emmc partition scanner from the link on the first page of this topic and copy to all 5 zip files to your external sd card. You will also need to download hg42's patched .pit file for your model of tab.
Boot into CWM recovery and flash emmc_find_brick_start.zip. This will scan you tab and will freeze on a bad block. Make a note of the number it freezes on.
Now flash the emmc_find_brick_end.zip file and once again make a note of the number the tab freezes on.
You now need to select the patched .pit file that falls within the range of brick start and brick end. e.g. my brick_start was 1074 and brick_end was 2147 so the patched .pit file I flashed with Odin was "P6200_tabplus--patched--brick-between-281-and-2160-MB--FACTORYFS-moved-by-1792-MiB"
I once again entered CWM recovery and did a scan using emmc_scan_all_partitions_once.zip. Which verified there were no errors.
I then booted up the Tab and hey presto it was alive again.
Feeling brave I then flashed the latest Austrian 4.0.4 firmware followed by permanent CWM recovery making sure that I can never do a factory reset using stock recovery which cause the brick to begin with.
Hope the above makes sense to those who need it, I'm sure as you go through the processes above it will.
I'd also like to encourage anyone who uses hg42's emmc tools to offer a donation as without him I would have had a very expensive paperweight or would have had to pay to get it JTAG'd
Happy Boy
Hi all
While trying to root and install custom rom I bricked my friends phone. I have been going crazy trying everything I could to get this brick back to life.
ITS ALIVE AGAIN!!!!!!!!
Thank you kersey for your post on how you got your Tab back.
This is what I did.
I installed the 5 files on the SD card.
120824-151927-emmc_find_brick_end
120824-151927-emmc_find_brick_start
120824-151927-emmc_scan_all_partitions_infinitely
120824-151927-emmc_scan_all_partitions_once
120824-220105-emmc_scan_write
I put the phone into recovery mode and ran 120824-151927-emmc_find_brick_start.
The program started scanning the memory and first froze on 2188.
I got back into recovery and ran 120824-151927-emmc_find_brick_end
once again the program started counting down and froze about 3189.
For this phone the correct pit files were in " pits-N7000_16GB "
I unzipped pits-N7000_16GB and looked for the nearest pit file , which was
N7000_16GB_Q1_20110914--patched--brick-between-1174-and-3321-MB--DATAFS-moved-by-2048-MiB.pit
I then put the phone back into download mode and using Odin flashed the patched pit file above.
Disconnecting the phone from computer I went back into recovery and ran120824-151927-emmc_scan_all_partitions_once
For the first time I was able to do a full scan without the program freezing.
Next step was installing Abyss Kernel 4.2. I then did the regular data wipe/cache wipe/dalvik wipe.
And finally I installed Rocketrom 11.
The phone rebooted and then came back to life.
I checked the internal memory and it was down to 9gb, but who cares as long as its ALIVE AGAIN !!!!
hg42 you sir are an absolute legend. Donation coming your way.
This method definitely works . Just be patient. I hope This helps others aswell
EDIT:
Is there any not so hard way to install the original rom with the pit i need? cm10 works, but i dont like it so much.
p6201dbtlpc_p6201xxlpc_p6201xxlp3_home.tar i would like to use
but i only know to flash this in odin, becouse it is no zip, i have no clue how to flash it in cwm
thanks for an answer!
-----------------
Your post should be on first post added =)
And in http://forum.xda-developers.com/showthread.php?t=1807002 !
Thanks for it!
kersey said:
It was pretty simple to revive it with hg42's help.
The first thing you need to do is ensure you have CWM recovery, as the scanning tools only work with that.
Download hg42 emmc partition scanner from the link on the first page of this topic and copy to all 5 zip files to your external sd card. You will also need to download hg42's patched .pit file for your model of tab.
Boot into CWM recovery and flash emmc_find_brick_start.zip. This will scan you tab and will freeze on a bad block. Make a note of the number it freezes on.
Now flash the emmc_find_brick_end.zip file and once again make a note of the number the tab freezes on.
You now need to select the patched .pit file that falls within the range of brick start and brick end. e.g. my brick_start was 1074 and brick_end was 2147 so the patched .pit file I flashed with Odin was "P6200_tabplus--patched--brick-between-281-and-2160-MB--FACTORYFS-moved-by-1792-MiB"
I once again entered CWM recovery and did a scan using emmc_scan_all_partitions_once.zip. Which verified there were no errors.
I then booted up the Tab and hey presto it was alive again.
Feeling brave I then flashed the latest Austrian 4.0.4 firmware followed by permanent CWM recovery making sure that I can never do a factory reset using stock recovery which cause the brick to begin with.
Hope the above makes sense to those who need it, I'm sure as you go through the processes above it will.
I'd also like to encourage anyone who uses hg42's emmc tools to offer a donation as without him I would have had a very expensive paperweight or would have had to pay to get it JTAG'd
Click to expand...
Click to collapse
ICS update and emmc bug
Hi; not sure if right forum, but here goes ,
I updated my tab plus to ics 4.0.4 using alpn and xlpn file from sammobile using odin from pc,
tab was never rooted only used a launcher
so my question is after i have installed ics and will not root or use cwm ,will i still have to worry about the emmc bug and if yes
is it best just to go back to honeycomb
btw all is running well on ics just worried about bricking
thank you in advance
doaft said:
Hi; not sure if right forum, but here goes ,
I updated my tab plus to ics 4.0.4 using alpn and xlpn file from sammobile using odin from pc,
tab was never rooted only used a launcher
so my question is after i have installed ics and will not root or use cwm ,will i still have to worry about the emmc bug and if yes
is it best just to go back to honeycomb
btw all is running well on ics just worried about bricking
thank you in advance
Click to expand...
Click to collapse
If you chose to do a factory restore via stock recovery, which is what you have due to not being rooted and not having CWM installed there is a very big chance you may brick your device. I speak from experience!!!
If you are that worried I would flash back to honeycomb rather than risking having an expensive paperweight
Sent from my GT-I9300 using xda premium
A little of my own experience with superbrick
Bad2hold said:
Dude, if you dont mind, what exactly have you done to revive your tab?
Not exactly, just a quick guide to avoid the most common mistakes.
Thanx!
Sent from my GT-P6200 using xda app-developers app
Click to expand...
Click to collapse
You guys can follow this guide I wrote for the Galaxy Tab 7.7 (which also suffers from mmc_cap_erase) : http://forum.xda-developers.com/showthread.php?t=1862294
Just replace the partition numbers with the ones parted shows you.
The problem is, either way you followed, after being revived your tab will :
- rebrick everytime you flash anything
- Have less than 1gb of internal storage
- Hang everytime you want to download an app or whatever
To fix the last 2 problems, you need to make an ext2sd script to swap your internal-sd and external-sd.
To do so, go to /dev/block/vold : you'll see two files named with numbers (i.e : 22:48 179:48), note the name of those 2 files (one of them is your external-sd mount point)
Then replace the "xxx:xx" in the following script with the name of the first file :
Code:
mount -t vfat -o umask=0000 /dev/block/vold/xxx:xx /storage/sdcard0
mount -o bind /data/media /storage/sdcard1
Save this script in a file called ext2sd1.sh and use Script Manager to run it "as root" and "at boot", now reboot and go to settings/storage : if the first file was your extsd mount point your internal and external storage should now be swapped (i.e : if you have a 64gb external sdcard the settings will show : internal storage : 64gb, and you can actually install 64gb of apps).
If it didn't work, replace the xxx:xx in the script with the name of the second file, then it should work.
Good luck guys, this superbrick is a damn pain in the ass, we can thank sammy for it
P6200
Hello man... I saw your post ''Good news all, after much trial and error and more flashing than your average pervert I have revived my tablet from the dead with a big thank you to hg42 for his scanner and extra advice.
Thanks to all those who helped in this post too'' ... I have the same problem with my P6200. Please give me that scanner to fix it or tell me how to put my tablet back On... Thanks
Androguide.fr said:
You guys can follow this guide I wrote for the Galaxy Tab 7.7 (which also suffers from mmc_cap_erase) : http://forum.xda-developers.com/showthread.php?t=1862294
Just replace the partition numbers with the ones parted shows you.
The problem is, either way you followed, after being revived your tab will :
- rebrick everytime you flash anything
- Have less than 1gb of internal storage
- Hang everytime you want to download an app or whatever
To fix the last 2 problems, you need to make an ext2sd script to swap your internal-sd and external-sd.
To do so, go to /dev/block/vold : you'll see two files named with numbers (i.e : 22:48 179:48), note the name of those 2 files (one of them is your external-sd mount point)
Then replace the "xxx:xx" in the following script with the name of the first file :
Code:
mount -t vfat -o umask=0000 /dev/block/vold/xxx:xx /storage/sdcard0
mount -o bind /data/media /storage/sdcard1
Save this script in a file called ext2sd1.sh and use Script Manager to run it "as root" and "at boot", now reboot and go to settings/storage : if the first file was your extsd mount point your internal and external storage should now be swapped (i.e : if you have a 64gb external sdcard the settings will show : internal storage : 64gb, and you can actually install 64gb of apps).
If it didn't work, replace the xxx:xx in the script with the name of the second file, then it should work.
Good luck guys, this superbrick is a damn pain in the ass, we can thank sammy for it
Click to expand...
Click to collapse
hey dude it's my first post in xda
i've succeded to unbrick my device but my internal memory is shrink a lot into 700+ mb but i don't understand how to use the script so
can u explain step by step ?
one can help me ??
hai everybody.... i'm from indonesia.., my friend just give me samsung galaxy tab 7 plus... ( GT-P6200 ) without any boxes, last day i try to get ICS update from kies , but the application won't update my firmware , so i try the alternative direction.
i try another application - Odin3-v1.85 and download the firmware..., but the fact is after few second running it self , the prosess can't continues get fail after
Note : i;m using : P6200OXALQ1_P6200XXLQ1_P6200XXLQ1_HOME.tar.md5 firmware
<ID:0/017> Firmware update start..
<ID:0/017> cache.img
<ID:0/017> NAND Write Start!!
<ID:0/017> factoryfs.img
<ID:0/017> hidden.img
<ID:0/017> recovery.img
<ID:0/017> Sbl.bin
<ID:0/017>
<ID:0/017> Complete(Write) operation failed. >>> FAIL...
anyone can help me .... please

Karbonn Smart Tab 8 version 2 Root, Recovery,etc.

Warning: This thread is for Karbonn smart tab 8 version 2
Version 2 tablets can be identified by S/N: ST*********** ver 2 at the back panel of the device
Root on Karbonn ST-8 Ver 2:
DISCLAIMER: ROOTING YOUR TABLET WILL PROBABLY VOID YOUR WARRANTY FROM THE MANUFACTURER. IF YOU DO NOT WISH TO ACCEPT FAULT FOR ANY ADVERSE EFFECTS OF ROOTING, THEN DO NOT READ ANY FURTHER. HERE BE DRAGONS.
Click to expand...
Click to collapse
Rooting
Download the utoo-root-signed.zip from here and copy it to a microSD card (do NOT extract it)
Charge up the battery in your Karbonn ST-8_version2, Power Off and remove the charger cable.
Insert the microSD card into your tablet
Get into Recovery mode( Power+volume down ) .
In the recovery you can move with the Volume down button, you can select with Power or Volume up
Select the apply update from EXT option
Select the utoo-root-signed.zip, this will install the package
Wait for the update to finish
Select reboot system now
This is a tried and tested method and has worked for everyone till now.
Attached zip credit goes to xda user @Lannig
Lag-free Tweak
Install SetCPU app
Download the file Setcpu.txt from here
Paste it into the root of your SD Card
Open SetCPU, first change the governor from "conservative" to "performance2"(This is the most important thing)
Click on options button(three dots) and then click Device Selection
Select Custom Frequencies
Now Set Min frequency to 48 MHz and Max frequency to anything according to your preference(Now you'll have the choice of setting the frequency upto 1.5 GHz)
Note:
When you wan't to conserve more battery lower the Max Frequency(while browsing or listening to music maybe) and when playing HD games up the Max Frequency(Most games will run perfectly with even 1200 MHz)
48MHz of Min frequency will give more battery in in standby mode.
Try not to Clock the CPU above 1.2 GHz for a long time as it could cause heat issues. The governor itself should speedup everything for you.
Low Internal Memory
The fact that our devices have only 1.51 GB of Internal Storage limits the capabilities of our devices. Especially with HD Games.
I recommend using GL2SD for games at the moment.
Get used to using the app, its pretty easy..
Also SEE THIS
Battery Tips
Build.prop edits
hw.nophone=true(was false)
hw.hasdata=false(was commented out and true)
ro.carrier=wifi-only(was unknown)
wifi.supplicant_scan_interval=240(was commented out)
hw.hasethernet=false(was true)[ I dont use ethernet ]
I use Greenify a lot
Also i had
1)phone.apk and odex
2)telephony.apk and odex
I removed them ( to stop displaying of cell signal usage in battery stats )
Also for ppl who want to unbrick st8-v2
Get the stock firmware package from HERE
Get the amlogic flash tool from HERE or HERE
Follow the instructions for the flash tool using the instruction manual from HERE or HERE
See the above posts and remember...........do not do things blindly........read the details completely and understand and then implement
Press Thanks if I helped U..........cheers
Stock Karbonn ST-8 Ver 2
Karbonn ST-8 v2 Stock ROM Dump And Unbricking ur bricked tablet
For a complete dump head to :
Mirror 1 [Box.com]
Mirror 2 [Mediafire.com]
For ppl who have flashed wrong TWRP in a hurry SEE THIS
also attached to this post is the Stock Recovery for Karbonn ST-8 Ver 2
Press Thanks if I helped U..........cheers
TWRP ON ST-8 V2
1. TWRP Testing for interested ppl
2. Partially tested TWRP
Link1
Link2
Press Thanks if I helped U..........cheers
Reserved...
waiting for twrp
TWRP Recvoery For smart tab 8 ver 2 Stock flashable
The attached file contains TWRP for Smart tab8 ver2.
It is initial release so it contains many bugs.
As i'm very lazy to do so myself so, if u tell me i'll resolve the bugs accordingly.
AND PLEASE NOTE I Don't have the tab so u have to check the releases yourself. My friend needs the twrp because he screwed his tablet. So i just made one for him to recover his tablet Just As is basis.
fizzy177 said:
The attached file contains TWRP for Smart tab8 ver2.
It is initial release so it contains many bugs.
As i'm very lazy to do so myself so, if u tell me i'll resolve the bugs accordingly.
AND PLEASE NOTE I Don't have the tab so u have to check the releases yourself. My friend needs the twrp because he screwed his tablet. So i just made one for him to recover his tablet Just As is basis.
Click to expand...
Click to collapse
EDIT: ur zip dosent flash in stock recovery....i got the recovery.img from zip and flashed it using flash_image binary
1. TWRP menu is visible and can be navigated
2. All buttons working
3. Reboot and settings menu fully working
4. Backup and Restore working ( tried system and data backup )
5. Mount menu ....only external sdcard can be mounted
6. Advanced menu copy log to sd working ....terminal command and file manager not working( flickering of recovery -->slide to unlock then black out)
7. Didnt try install and wipe options
need help.. please, White screen boot
I had just received my 'smart tab 8 Ver 2' two days ago and i was trying to root and install fuser-invent custom rom in it.. one thing led to another and by the time i realized the firmware of ver1 is diff than ver 2, the damage was already done.. now my tab displays a white screen and nothing else.. it wont even boot into stock recovery. can some one please help me. :crying::crying:
Root.....Check!
Thanks for the Root dude! It worked Awesome!!
Now if only we can have the Custom bugless roms the V1 users have and then it would be an icing on the cake!
I'm prepared to help out in anyway to be able to experience that goodness!! :fingers-crossed:
I am also facing the same problem , but when i connect my tablet to pc it shows "M3 CHiP" a new hard ware found . But i dont know how to fix my tablet . i knows M3 chip is amlogic processor and AML flash tool can be used to flash it ( i found it from google) . Somebody please help me to fix my tablet .
UP
unbrick
Aviast11 said:
I am also facing the same problem , but when i connect my tablet to pc it shows "M3 CHiP" a new hard ware found . But i dont know how to fix my tablet . i knows M3 chip is amlogic processor and AML flash tool can be used to flash it ( i found it from google) . Somebody please help me to fix my tablet .
Click to expand...
Click to collapse
Steps to unbrick ur tab:
Unbrick st-8-V2
1. Download the above zip extract the above zip to the root of an empty sdcard. It should look like this
2. Put the sdcard in your tablet
3. Press Power+Volume down and let it update the tablet
for furthur assistance see this link
the method i mentioned is the first one,sdcard one ....report after ur trial so that it may help others...
2012katas said:
Steps to unbrick ur tab:
1. Download the above zip extract the above zip to the root of an empty sdcard. It should look like
2. Put the sdcard in your tablet
3. Press Power+Volume down and let it update the tablet
for furthur assistance see
the method i mentioned is the first one,sdcard one ....report after ur trial so that it may help others...
Click to expand...
Click to collapse
Hi
I tried the way u mentioned , but nothing happend , still its showing white screen.
the way i did is :-
1. extract the zip and put all files inside my SD card (same as the image u showed)
2. put SD card in my tablet and pressed vol down+power (i tried with all key combinations)
3. only white screen.
also i downloaded "usb image tool" but i dont have image file to load ..
please help me to fix my tablet.
i am a newbie, I wanted to know if there is any method to upgrade Smarttab ver-2 to android 4.2.2
I want to use multiple useraccount feature in 4.2.2
I have read the forum threads and it isnt quite clear if such an upgrade is possible and tested.
recovery
the above method aborted after starting update.please guide to recover my karbon velox smat tab 8 v2 .it is always booting to recovery screen.
unbricking st8 version2
nickrulez13789 said:
I had just received my 'smart tab 8 Ver 2' two days ago and i was trying to root and install fuser-invent custom rom in it.. one thing led to another and by the time i realized the firmware of ver1 is diff than ver 2, the damage was already done.. now my tab displays a white screen and nothing else.. it wont even boot into stock recovery. can some one please help me. :crying::crying:
Click to expand...
Click to collapse
Aviast11 said:
I am also facing the same problem , but when i connect my tablet to pc it shows "M3 CHiP" a new hard ware found . But i dont know how to fix my tablet . i knows M3 chip is amlogic processor and AML flash tool can be used to flash it ( i found it from google) . Somebody please help me to fix my tablet .
Click to expand...
Click to collapse
assipposi said:
the above method aborted after starting update.please guide to recover my karbon velox smat tab 8 v2 .it is always booting to recovery screen.
Click to expand...
Click to collapse
Ok guys,This the first and last time I am posting this....
To unbrick ur tab......
1. Post what u did
2. What is wrong with the tablet according to your understanding
If you want to be helped the above two points really matter........
3. See this link
4. All info about unbricking various types of bricks can be found on the thread....
5. Also i would suggest you go through the thread fully and understand every detail
6. Another alternative for you guys would be Karbonn service center, But I feel it is useless as they take minimum 30-45 days to repair things
7. The method i mentioned is the first one,sdcard one
At this moment we have an experimental unbrick package with us thanks to developer @fuser-invent
This package is to be used in the STEP 3 of SOFT BRICK UNBRICK SDCARD method
Step 3
This only works if the first method completed far enough to allow you into the Stock Recovery or if the Alternative Methods worked and you now need to install the correct firmware.
0. Restore your SD card back to normal capacity with the SD Formatter software. This can take a long time, be patient. Choose the following options:
- FORMAT TYPE -> FULL (Overwrite)
- FORMAT SIZE ADJUSTMENT -> ON
1. Get THIS firmware package
2. Download the above zip extract the above zip to the root of an empty sdcard( less than 2gb ). It should look like this all four files should be in the root of the sdcard.
3. Just FYI, the zip folder among those four files is the stock rom ( it has boot.img,bootloder.img,system,recovery.img,aml_logo.img,logo.img )
Also this package is a recovery package for soft bricks....
4. Put the sdcard in your tablet
5. Hold down the Power and Vol - buttons to enter the Stock Recovery
6. Flash your firmware package and reboot the tablet.
7. If it worked, either plug your tablet into the computer and use USB mode or shut down your tablet and remove the SD card, then remove the "u-boot.bin" and "uImage_recovery" files from your SD card.
8. Boot back into recovery and make sure that the firmware package correctly installed the Stock Recovery on your device.
Your tablet is now back to it's original Factory Settings.
6. For furthur assistance see this link
7. If you are successful plz report back...........it will help others
2012katas said:
Ok guys,This the first and last time I am posting this....
To unbrick ur tab......
1. Post what u did
2. What is wrong with the tablet according to your understanding
If you want to be helped the above two points really matter........
At this moment we have an experimental unbrick package with us thanks to developer @fuser-invent
1. Get THIS frimware package
2. Download the above zip extract the above zip to the root of an empty sdcard( less than 2gb ). It should look like this
3. Just FYI, the zip folder among those four files is the stock rom ( it has boot.img,bootloder.img,system,recovery.img,aml_logo.img,logo.img )
Also this package is a recovery package for soft bricks....
4. Put the sdcard in your tablet
5. Press Power+Volume down and let it update the tablet
6. For furthur assistance see this link
The method i mentioned is the first one,sdcard one ....report after ur trial so that it may help others...
7. All info about unbricking various types of bricks can be found on the thread....
8. Also i would suggest you go through the thread fully and understand every detail
9. If you are successful plz report back...........it will help others
10. Another alternative for you guys would be Karbonn service center, But I feel it is useless as they take minimum 30-45 days to repair things
Click to expand...
Click to collapse
As 2012katas said, it's very important to go to the thread he links in #6. Yes, it is a HUGE thread, but it is detailed for a reason. 99% of your questions will be answered in that thread.
For example, the thread clearly says to use the ELF2 rescue image and the USB image tool to prepare your card first, then delete the ELF2 files from it and replace them with the files for your tablet. It also says that if that doesn't work you can try the SD Formatter software with my suggested settings to try and prep your card. I have no idea if the package will work until someone tries it the correct way and reports back.
On another note. If it doesn't work the first time, try to delete the u-boot.bin file only and then try again. Also mentioned in the thread, some people need to press and hold the power and vol- buttons and then when the tablet starts lighting up, start pressing the power button repeatedly, but that is rare.
As for the people with deep bricked tablets (showing the M3/M6 chip), you don't have anything to loose at this point so you best bet is to download the ST10_20121129.zip package, remove the patch.zip and update.zip, put the ST8 v2 firmware package zip I made in that folder, edit the config_progress.xml so the firmware package name is correct and no longer called update.zip, delete the part for the patch.zip, renumber the remaining steps, zip the whole thing back up and load it into the AML USB Burning software.
That might work or it might not work. You have to intelligently experiment because there is no official release for the tablet. Also you will notice that in the unbricking thread I say that if you can get the tablet showing some signs of life after the M3/M6 chip deep brick, you can then move to the SD card method. So if the usb_spl.bin and u-boot-orig.bin for the ST10 work with the ST8 to at least get the tablet out of M3/M6 mode then you could use the SD card method.
Lastly, to 2012katas, I'm rarely on XDA so if you have more questions, I see them more often on DragonDevs. You seem into this Dev stuff and smart, so feel free to get in touch to troubleshoot more.
Awesome TAB
I love this tab...
Runs Asphalt 8 flawless on 1.5ghz OC'ed.............totally awesome no lags..
btw OC'ed for battery=100% to battery=6%
tablet heats up a little on back side...........but okay for gaming........
Hi All,
I accidentally flashed TWRP recovery before routing. On Karbon Smart tab 8 Ver 2
Now, I can't do any thing...
I tried factory reset it not working.
Also failed to get into fastboot mode...
Need help to go back and flash stock recovery..
if anyone have all he junks that is pre-installed in the tab, please upload.

[Stock ROM] CAT B15Q ROM development

CAT has not yet managed to put official stock images or the kernel source code available - even for their oldest phones (even though they are required to)... so here's at least a beginning.
Every firmware archive contains the four partitions UBOOT, BOOTIMG, RECOVERY and ANDROID (/system). These are flashable using spFlashTool, a howto is here: http://forum.xda-developers.com/android/help/howto-firmware-flashing-cat-b15q-t2989627.
Please note that these firmware files were dumped from an EMEA B15Q, dual-sim - there are reports of other models being available under the B15Q model name. In doubt, always make a full backup using spFlashTool's readback mode before flashing one of these. (You should be doing these anyway before every firmware upgrade, CAT doesn't test stuff like compatibility with root!)
Credits for the scatter file go to bigal1337. Credits for spFlashTool and the driver package go to Russian website mtk2000.ucoz.ru.
1.019: https://mega.co.nz/#!UEp0hS7b!6aiqETvAu1Q9voNZtMLWoztbF7FGX0j9Pnj4rBhwoD4
1.022: https://mega.co.nz/#!YEAwmbxI!rVonLybVo6PL2bhNloGStR0EacKwE3-3hILzY9ri0NY
Scatter file: https://mega.co.nz/#!UEp0hS7b!6aiqETvAu1Q9voNZtMLWoztbF7FGX0j9Pnj4rBhwoD4
Tested tools:
MTK Driver package: http://mtk2000.ucoz.ru/down12/MTKUsbAll_0.9.2.rar
spFlashTool: http://mtk2000.ucoz.ru/down12/SP_Flash_Tool_exe_windows_v5.1420.00.rar
Do note that the drivers appear to be modified Google drivers and thus have no digital signature; you will need a 32-bit system to use them.
Flash mode needed for spFlashTool is achieved by removing the battery, starting the flash/readback in spFlashTool and then plugging in the USB cable. You may put in the battery afterwards.
The recovery, fastboot and factory test methods are entered by shutting down the phone and then:
recovery mode: press power + volup for 2 seconds, then release power, release volup as soon as recovery has booted
fastboot mode: press power + center for 2 seconds, then release power, release volup as soon as recovery has booted
test mode: press power + voldn for 2 seconds, then release power, release volup as soon as recovery has booted
In case that a B15Q or general CAT board is opened (for the B15, B15Q and the flagship S50), I request that this thread is moved into its rightful place. And in case anyone wants to help me with a CyanogenMod port, please PM me.
CWM Recovery
Using mtkdroidtools, I have built a CWM Recovery image to be flashed with spflashtool, all based on 1.022 firmware. There are two variants:
using stock Mediatek USB IDs: https://mega.co.nz/#!FRxxiRSC!EN5gORcYPtFONlH3V8-Yco3_w9RGhE8jevicedlT2kI
using Samsung USB IDs: https://mega.co.nz/#!8MowBZCJ!fhs-mXpGZR36g9JJh3IONIlOKBHIktFBDIrpynlK84M
The difference between them is that recovery #1 uses the same Mediatek USB id's as the stock image (and thus requires the Mediatek drivers in Windows, which sucks because these are not signed), and recovery #2 uses the USB IDs from a Samsung tablet - so you need the Samsung ADB driver instead, which is digitally signed and far more stable than the Mediatek.
Samsung USB ID fix
See above for the reason; the boot.img with Samsung USB IDs is at:
1.022: https://mega.co.nz/#!gcREQJKD!FCrxl9-PWSWM0_2Nh9D1KeA-zFV4nS9dmd6zjVnqPLc
Hybrid SD Card
And the CWM Recovery + boot.img for those who want to try out the "hybrid SD card" from http://forum.xda-developers.com/android/help/howto-external-sd-card-internal-storage-t2989650, the two images of 1.022 are here:
boot.img: https://mega.co.nz/#!MMYx1BYY!Rlnrxl1MURMgnx2luvPdYKJjMmNMbYVIGyFlGeRVcMY
recovery.img: https://mega.co.nz/#!wZQ1FIrS!iXAYfF3pgSySYsQ3f8ygGkDWE3Ulebx3JFgzRKXWNjs
I used this, it's great! Now I have 16gb of "internal phone memory" and 14 of "external" sd card. Did not see any performance issues with my SanDisk Extreme III. Do not need root anymore, I wanted it only for link2sd. Thanks harddisk_wp!!!
walckenaerius said:
I used this, it's great! Now I have 16gb of "internal phone memory" and 14 of "external" sd card. Did not see any performance issues with my SanDisk Extreme III. Do not need root anymore, I wanted it only for link2sd. Thanks harddisk_wp!!!
Click to expand...
Click to collapse
Great to hear someone was crazy enough to replicate my hack But I strongly advise you to keep off OTA updates with the hack enabled.
harddisk_wp said:
Great to hear someone was crazy enough to replicate my hack But I strongly advise you to keep off OTA updates with the hack enabled.
Click to expand...
Click to collapse
i have got a message that my sd card is damaged... and there is no way to remove that notification? any ideas?
thanks!
mccloud90 said:
i have got a message that my sd card is damaged... and there is no way to remove that notification? any ideas?
thanks!
Click to expand...
Click to collapse
With or without the SD hack? Try putting the SD card into a Windows machine, chkdsk the fat32 partition. Then plug it into a linux machine and run e2fsck on the data partition.
harddisk_wp said:
With or without the SD hack? Try putting the SD card into a Windows machine, chkdsk the fat32 partition. Then plug it into a linux machine and run e2fsck on the data partition.
Click to expand...
Click to collapse
I tried the sd hack. There was a problem with my sd card partitions... but i reformated it with partition magic and now it works like a charm. No lag or anything.
Better than i was thinking
Greatings!
after one week
OKAY,
after one week of usage my phone became laggy and unstable.
Maybe this is because of my sd card but.... its 10class, i dont know
So i reflashed with the original partitions and now its fast and stable
Custom Rom
Will there be any possibility to create a Lollipop rom for this device?
proximity sensor problem
Do someone have the problem with the proximity seonsor that i have? There is a screen turning on immediately after turning of when the phone is placed next to my head when i am calling. This leads to a lot of changes in settings and everything that my face is changed durring the phone call.
I tried a lot of apps from play store that "fix" the problem but... they work not on 100% proper.
The sensor is working at 100% i have checked it already.
Please give me suggestions because its very annoing!!
Hi!
mccloud90 said:
Do someone have the problem with the proximity seonsor that i have? There is a screen turning on immediately after turning of when the phone is placed next to my head when i am calling. This leads to a lot of changes in settings and everything that my face is changed durring the phone call.
I tried a lot of apps from play store that "fix" the problem but... they work not on 100% proper.
The sensor is working at 100% i have checked it already.
Please give me suggestions because its very annoing!!
Click to expand...
Click to collapse
I had the same problem. CAT support told me to reset the phone to factory. I tried a lot of other things but only the factory reset helped me. My sensor was also working correctly, I also tried several Apps to chack this.
Give it a try. I know it's a lot of work, but it was (in my case) worth it. I changed the time an date settings with my face which lead to missed alarms and oversleeping
Greets,
Doggy
Current ersion?
Doggy77 said:
Hi!
I had the same problem. CAT support told me to reset the phone to factory. I tried a lot of other things but only the factory reset helped me. My sensor was also working correctly, I also tried several Apps to chack this.
Give it a try. I know it's a lot of work, but it was (in my case) worth it. I changed the time an date settings with my face which lead to missed alarms and oversleeping
Greets,
Doggy
Click to expand...
Click to collapse
You have hard reseted to what rom version? 1.19 or 1.22
I will give it a try
I need the phone rooted and i am not sure if the cwm recovery can be flashed over 1.19 as it was my original rom and i flashed it to 1.22 from files here on the forum
any news about any cyanogenmod rom?
Just to tell you that the new official update is awsome!!! Upgrade as fast as possible Greatings!
CAT B15 help
Hi guys, i'm sorry i have to ask this in this forum but i've been asking for a couple of months now, and got no answer. I have a CAT B15 (not the B15Q). It is single sim version (IMEI write on the back) and i managed to do plenty of things in it. I swapped memory and worked fine, and even i installed a Dual Sim android rom and i managed to use the secondary Sim bay in it (that was tapped with a plastic fake sim) and used the phone with 2 sims for like 2 weeks. Then i started to play with deodex and build.prop and softbricked the phone, but it was piece of cake since it is easy to unbrick. The problem was that i wrongly flashed the phone with scatter file, and flashed all partitions in it, EBR1, MBR, UBOOT, etc, etc. The result was a non-working dual SIM phone. Everything works, but the SIMS, it does not detect any SIMs in it, in any of the SIM bays, and the IMEIs are wrong numbered. I did no buckup of the phone so i'm pretty screwed. I've been asking for someone to upload the EMEA_SS or US_SS ROM for the CAT B15, but nobody responded. I thaught maybe the CAT B15Q has a similar software/bands flashing partitions, but that i leave to you for answer. Anyway, if any of you has the possibility of taking the images of a single sim CAT B15 it would save me this awesome phone for me. I'm also willing to give a 20GB account of ownCloud server for 1-year free of charge if storage space is needed, no problem. This are the links i've been searching and asking.
All About CAT B15: http://forum.xda-developers.com/showthread.php?t=2430904
Root for Catterpillar B15: http://forum.xda-developers.com/showthread.php?t=2263455
Best regards,
proximity sensor problem
I also have the proximity sensor problem.
I have tried the factory reset but the problem is the same.
It has 1.026 rom.
Can anybody post the 1.026 software? Thanks!
yo2lzp said:
I also have the proximity sensor problem.
I have tried the factory reset but the problem is the same.
It has 1.026 rom.
Click to expand...
Click to collapse
Hallo my friend,
i had the same problem and that was so anoyng... so i went back to the shop where i bought my phone and told them about the problem.
After one week they called me and my phone was with changed whole display with everything inside and now i have working proximity sensor
So... i suggest you to go back to the store and tell them about your problem !
All the best!!

Categories

Resources