Related
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.
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
Dear all,
I have flashed my MZ605 (32GB) using EOS 3.0 for MZ601 with TWRP and that has worked quite well for some time, but last week I was fiddling with the navigation app and the tablet suddenly froze. The only way to get it back to life was doing a volume-up+power. Now the system still boots: i get to the lock screen, but as soon as I unlock (no password, just swiping to the right), I receive a shower of f/c messages and no icons apear. The settings screen still seems to work, but since the stream of f/c messages doesn't stop, it's very hard to do anything at all. I tried all the standard stuff first: Flashing EOS 3.0 using TWRP and Factory Reset: It seems to do nothing at all. Everything stays the same! When trying to delete cache, userdata, etc. Right after displaying the message "updating partition details", it complains that it is not able to access certain files in /data/media (a bunch of mp3 files)
Figuring that something must be wrong with the filesystem, I fired up the console of TWRP and did an e2fsck (e2fsck -vfcp) on partition 8,9 and 10, resulting simply in "unable to set superblock flags". I tried formatting the thing by hand but when doing mke2fs, it acts like it it's creating the fs (you see the numbers fly by), but when mounting the fs again, nothing changed at all!
About the partition table: Accessing the kernel messages (dmesg) with ADB says that the primary gpt table is corrupt and will try to use the backup table. It then merrily continues booting. However, when checking the partition table with gdisk (using ADB): it says nothing is present. Using the recovery options show that the primary table contains garbage and the backup partition table doesn't seem to contain anything. :S This contrasts with the fact that kernel still sees the partitions and that they are mountable both when booting normally as well as with TWRP
As a last resort I downloaded RSDLite 5.7 and the most recent SBF image. It flashes the whole thing without any errors, but when booting the system: nothing changed at all???
For the tl;dr people: Sorry! In a nutshell: fs seems to be frozen: mke2fs does nothing, fastboot flash does nothing and even sbf flash doesn't do anything at all. However the device still boots, albeit with a shower of f/c on unlock screen.
Any suggestions what to? I have been googling for many days now and reading this forum. Nothing has helped so far...
My next try would be to redefine the gpt partition table using gdisk and then hope that'll fix the frozen that. After that I would of course do a wipe all and flash a new ROM. The problem is, I can't find the standard partition layout details for the Xoom anywhere, nor do I have any other ideas what to do in case this does not work
If anyone has any hint or idea, please let me know. Thanks!
Nobody?
If anyone could please tell me their partition layout, like start - end - type for each partition. It'd really appreciate it!
Thanks!
No one?
Hello,
have you fixed it ?
Nope
jkd said:
Hello,
have you fixed it ?
Click to expand...
Click to collapse
Unfortunately I haven't been able to fix it. I still have the tablet though, hoping that one day I will come across a fix. I have two theories as to what may have caused it:
1) Physicalically the write pin of the internal flash got disconnected
2) Somehow a readonly command was send to the flash and made it read-only. I don't know if this is possible neither how to undo it.
If you have a solution, please let me know. I'm also willing to do tests and experiments to try to solve the problem.
ioish said:
Unfortunately I haven't been able to fix it. I still have the tablet though, hoping that one day I will come across a fix. I have two theories as to what may have caused it:
1) Physicalically the write pin of the internal flash got disconnected
2) Somehow a readonly command was send to the flash and made it read-only. I don't know if this is possible neither how to undo it.
If you have a solution, please let me know. I'm also willing to do tests and experiments to try to solve the problem.
Click to expand...
Click to collapse
Actually I have the same problem, I have read several forums and I have not found an answer
jkd said:
Actually I have the same problem, I have read several forums and I have not found an answer
Click to expand...
Click to collapse
That's too bad
Did you by any chance install a custom rom or performed any non-official other update?
ioish said:
That's too bad
Did you by any chance install a custom rom or performed any non-official other update?
Click to expand...
Click to collapse
my xoom caracteristic:
- Recovery: TWRP v2.6.3.0 (RunAndHide05 Edition), I can not tell if it's a bigpart or no recovery. Also I am unable to change recovery is cwm or another version of TWRP. I always find my TWRP recovery v2.6.3.0.
- ROM omni: 4.4.2-20140102-1218 + 0100-wingray-HOMEMADE (I don't know if is bigpart rom)
- kernel:2.6.39.4-ElementalX-Xoom-2.1+
Hi.
Here, i have a very difficult issue with my unlocked transformer tf700t.
I wanted to install cyanogenmod ... I was to wipe data but it got interrupted
I have read many threads already like those:
http://www.2toer.com/2012/10/reset-button-transformer-pad-infinity-tf700t.html
(held for more than 50 seconds and it shaked but didn't help. tried to reset repedeatly too.)
http://www.transformerforums.com/fo...oot-into-android-after-jelly-bean-update.html
I also download "universal naked driver"
http://forum.xda-developers.com/showthread.php?t=2263822
But i am totally unsure how to install the driver and windows itself won't see its .inf files as valid. (windows 8).
I could use my cellphone's SD card but i can't run the recovery tool, can't boot, the very initial screen says "device is unlocked" and it is... But i can't enter the recovery mode and run RCK or wipe data.
http://www.technipages.com/how-to-soft-and-hard-reset-asus-eee-pad-transformer.html
However how eternally i could hold vol down + power ... it won't launch into recovery mode... It's much like freezing.
I should maybe have directly run rck instead of doing wipe data...
Is there a way to send any signals to the tablet via usb with a windows tool?
[edit]
Right now i'm checking with the .blob solution...
http://www.transformerforums.com/fo...overy-bootloop-fix-tested-my-c10-windows.html
Yes, there is a method to access your tab from your computer, it's called Fastboot. But you don't seem to be able to get to the bootloader menu at all to get into fastboot mode, are you? By booting holding Power and Volume Down buttons?
If that is true, you are hard bricked, I am sorry to say, and my only suggestion would be to try this method I read about on the TF300 forum:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Win 8 seems to really suck for fastboot and adb, try to get a Win7, XP or Linux machine.
Good luck!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
Click to expand...
Click to collapse
I really can't... The procedure won't trigger anything or it freezes before it could. It may have got corrupted while the wipe data has been interrupted... :\
Matthieu.s said:
I really can't... It may have got corrupted while the wipe data has been interrupted... :\
Click to expand...
Click to collapse
Sorry friend - it's a brick :crying:
You can send it to Asus to have the motherboard replaced or try to find one sold for parts on ebay and replace it yourself.
Just for forensic purposes: Did you execute "Wipe Data" from the bootloader menu?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Yes... From the boot menu. What parts do i need to replace? Any workaround possible before giving up hope?
Can you get back to recovery at all or the bootloader?
Matthieu.s said:
Yes... From the boot menu. What parts do i need to replace? Any workaround possible before giving up hope?
Click to expand...
Click to collapse
You need to replace the motherboard.
My guess is, you flashed a custom recovery and then used 'Wipe Data' from the bootloader menu.
The instructions you followed probably advised you to wipe data before flashing the rom, but you had to do that from your custom recovery - not the bootloader menu. 'Wipe data' from the BL menu with a custom recovery installed is a very, very risky business.
Sorry mate.....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
you mean... That from all tutorials that i've read, not a single author had the idea of putting a screenshot of "don"t wipe" from menu...
Or shouldn't have the utility's author chose a synonym instead of using the same word as the device makers did?
Or that this nearly 600$ crap that's keyboard is almost worth the half of itself and doesn't even come along, that doesn't even charge on USB, that has the crappiest android interface and that lags like hell even after a factory reset with its useless 4 cores... doesn't even come with an emercency secure-rom partition?
Dude. I should have bought a laptop.
It's like... This wipe data utility has only one use: autodestruction? that's it? Is it a way to make sure that the richest of us will buy a new one as soon as the old new one breaks?
I don't understand why this process also erased ... the bios? It's like... How would anyone be able to do anything without the bios?
Hmm... It discharged by night. The battery icon still loads and at its current state... It still checks for its charge state... It's still alive... There must be a way to wake it up from its sleep...
Maybe the interface isn't frozen but just doesn't respond to the voldown+power button?
Maybe there exists something to plug on the 60 pins plug that could force-access the partition?
Matthieu.s said:
you mean... That from all tutorials that i've read, not a single author had the idea of putting a screenshot of "don"t wipe" from menu...
Or shouldn't have the utility's author chose a synonym instead of using the same word as the device makers did?
Or that this nearly 600$ crap that's keyboard is almost worth the half of itself and doesn't even come along, that doesn't even charge on USB, that has the crappiest android interface and that lags like hell even after a factory reset with its useless 4 cores... doesn't even come with an emercency secure-rom partition?
Dude. I should have bought a laptop.
It's like... This wipe data utility has only one use: autodestruction? that's it? Is it a way to make sure that the richest of us will buy a new one as soon as the old new one breaks?
Click to expand...
Click to collapse
Do you still be able to fastboot or access from your pc? You might have a chance to flash a new blob for you device..
Matthieu.s said:
you mean... That from all tutorials that i've read, not a single author had the idea of putting a screenshot of "don"t wipe" from menu...
Or shouldn't have the utility's author chose a synonym instead of using the same word as the device makers did?
Or that this nearly 600$ crap that's keyboard is almost worth the half of itself and doesn't even come along, that doesn't even charge on USB, that has the crappiest android interface and that lags like hell even after a factory reset with its useless 4 cores... doesn't even come with an emercency secure-rom partition?
Dude. I should have bought a laptop.
It's like... This wipe data utility has only one use: autodestruction? that's it? Is it a way to make sure that the richest of us will buy a new one as soon as the old new one breaks?
I don't understand why this process also erased ... the bios? It's like... How would anyone be able to do anything without the bios?
Hmm... It discharged by night. The battery icon still loads and at its current state... It still checks for its charge state... It's still alive... There must be a way to wake it up from its sleep...
Click to expand...
Click to collapse
I understand that you are upset - I would be if I were you. But you can hardly blame Asus or the author(s) of whatever instructions you were following for bricking your tablet.
The disclaimer you have to read before you unlocked could not be more clear: They strongly discourage you to do it and make it abundantly clear you are on your own if you do.
Every set of instructions on flashing I have read also states: "Don't blame me if something goes wrong - you are doing this at your own risk" in one or the other form.
You did it anyway and made a mistake.
I do feel for you! It's a huge bummer to wreck a $600 device, no doubt about it.
Wipe Data from the bootloader menu is a feature of the stock rom. If I understand it correctly (and please someone correct me, if I'm not) it's a last ditch method to reflash the tablet with stock firmware.
It wipes everything except the stock recovery and assumes that you have a copy of the stock firmware on a microSD waiting to be flashed.
Asus provided a safe Factory Reset option from the settings menu for the average user and I bet they do not want users to access the bootloader and mess with it's options at all. There's a reason it's not exactly intuitive to get there.
Yes, I agree, there should be a warning before Wipe Data does it's thing.
Unfortunately there isn't....
But again, you can hardly blame Asus for a feature of the stock system not working with custom software you installed.
And again, I am sorry for your loss....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
LetMeKnow said:
Do you still be able to fastboot or access from your pc? You might have a chance to flash a new blob for you device..
Click to expand...
Click to collapse
maybe if i had the files on a sd card it could load them indeed..
Something like putting usual partition files on the sd card and see if it loads... It may check for its missing files on the SD if i'm lucky... Can i do this and go directly to cyanogen? I'll check the topics that discusses it furthermore... But my situation may vary... Major thing is that i really can't access it from PC from boot welcome screen so it discards all topics that asks for a usb connection... And the boot-to-CRW button makes no effect meaning it's also broken... Maybe putting CRW on the SD card and process the cyanogen file that should still be on the storage's base folder?
berndblb said:
I understand that you are upset - (...)
But again, you can hardly blame Asus for a feature of the stock system not working with custom software you installed.
And again, I am sorry for your loss....4
Click to expand...
Click to collapse
Don't worry friend i still have hope... Maybe the solution is in what you spoke of and is to use SD in some way i spoke in the previous comment but i'll need just a bit of help and guidance ... and links I'll use my cellphone's sdcard and backup>format it and do whatever required to wake the tablet's system up just enough to restore its missing files... Like... If the machine does check for SD (maybe bootscreen isn't frozen but just idle) maybe it could check for its required files like CWM or base firmware... I really believe the SD card plan is a good idea but the only thing is that it must be made automatically or if isn't i probably won't be able to trigger from vol_down+power... Or maybe could... Let's see ^^
What do you believe about this post? It's not tf700t related but it discusses the method a bit? http://forum.doozan.com/read.php?6,8904
And this thread is interesting but i'm unsure... http://www.transformerforums.com/fo...irmware-tf700-tf300-tf101-possibly-tf201.html
This is what i will attempt. http://androidforums.com/nookcolor-...rkmod-twrp-bootable-sd-card-06-04-2013-a.html
Citation from site
Now what can you do with your new bootable CWM/TWRP sd card?
You can flash a rom. Plug it into your computer and copy your rom file to it
You can backup your rom. (under "backup and restore" menu.)
You can restore a recovery backup, should your new rom never boot.
Click to expand...
Click to collapse
x( Failed :/ I need something to trigger the system to bypass its instructions and run SD instead... Trigger from USB or something...
I'm still not clear. Do you have access to the bootloader or not.
It sounds like you do in which case all is not lost. Give up on the SD method though. The trick here is to ensure you have the right PC USB drivers installed.
Is the device registered in device manager when plugged into the PC?
See this post here
http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
sbdags said:
I'm still not clear. Do you have access to the bootloader or not.
It sounds like you do in which case all is not lost. Give up on the SD method though. The trick here is to ensure you have the right PC USB drivers installed.
Is the device registered in device manager when plugged into the PC?
See this post here
http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Click to expand...
Click to collapse
I don't think he can get to the bootloader, if you read post #3. I referred him to exactly the same method and it didn't seem to work....
Sent from my DROID4 using Tapatalk 2
Here's what i get from device manager (it finally shown up in the list)
Code:
Unknown device
Tab 1
Device type: other devices
Maker: unknown
Location: Port_#0004.Hub_#0005
Windows stopped this device because it had problems (code 43)
Tab 2
All marked unavaillable/not signed
Tab 3
USB\DEVICE_DESCRIPTOR_FAILURE
Tab 4
Device configured (null)
Device USB\VID_0000&PID_0002\6&1512c192&0&4 was configured.
Driver Name: null
Class GUID: {00000000-0000-0000-0000-000000000000}
Driver Date:
Driver Version:
Driver Provider:
Driver Section:
Driver Rank: 0x0
Matching Device ID:
Outranked Drivers:
Device Updated: false
Device not started
Device USB\VID_0000&PID_0002\6&1512c192&0&4 had a problem starting.
Driver Name: null
Class GUID: {00000000-0000-0000-0000-000000000000}
Service:
Lower Filters:
Upper Filters:
Problem: 0x2B
Status: 0x0
It shows signs of life.
The drivers were already installed on Windows... But i guess that they are not meant for this procedure? What about universal naked drivers?
I'll continue researches tomorrow... Thanx ^^
Hi did you ever get the fix for this ? also same boat tried 2 3rd party cables no luck .. first error code I got was 43 then forces drivers got code 10 then I got what you get in events
Matthieu.s said:
Here's what i get from device manager (it finally shown up in the list)
Code:
Unknown device
Tab 1
Device type: other devices
Maker: unknown
Location: Port_#0004.Hub_#0005
Windows stopped this device because it had problems (code 43)
Tab 2
All marked unavaillable/not signed
Tab 3
USB\DEVICE_DESCRIPTOR_FAILURE
Tab 4
Device configured (null)
Device USB\VID_0000&PID_0002\6&1512c192&0&4 was configured.
Driver Name: null
Class GUID: {00000000-0000-0000-0000-000000000000}
Driver Date:
Driver Version:
Driver Provider:
Driver Section:
Driver Rank: 0x0
Matching Device ID:
Outranked Drivers:
Device Updated: false
Device not started
Device USB\VID_0000&PID_0002\6&1512c192&0&4 had a problem starting.
Driver Name: null
Class GUID: {00000000-0000-0000-0000-000000000000}
Service:
Lower Filters:
Upper Filters:
Problem: 0x2B
Status: 0x0
It shows signs of life.
The drivers were already installed on Windows... But i guess that they are not meant for this procedure? What about universal naked drivers?
I'll continue researches tomorrow... Thanx ^^
Click to expand...
Click to collapse
I have an Intenso 814s tablet
motherboard: MID8306_AML8726-MXS_MXL_V1R1
Amlogic 8726-MXS cpu
1GB Ram/8GB Rom
Android 4.2.2
Actually I have two, but the one is having trouble booting.
All begun when the internal memory started filling up resulting the tablet being unable to install any new apps. The odd thing was that the tablet had very few apps. On the storage menu it stated that there where a total 5.8GB of ROM, and 5.3GB used, 500MB free, but the apps only occupied 400MB. Some 5GBs where unaccounted for. The even odder think is that even after many times restoring/wiping cache+data from the recovery menu, the 5GB space was still occupied, nothing could delete it.
After some research I found that sometimes there is a dumpstate/log file that keeps increasing in volume somewhere in a hidden folder and the only way to clean/delete it was with the device rooted. So I started trying to find the proper root procedure. The problem was that the tablet wasn't always rebooting on the first try, anytime I was trying a new method. And eventually stopped rebooting at all.
The second tablet have similar problems, only difference, the available internal space was a bit bigger (2GB vs 500MB), but nevertheless it was obviously suffering from the same problem.
All I get now after rebooting the troublesome tablet is
1) The "Intenso" logo
2) The "A9 Dual Core" logo and then it gets stuck....forever.
Sometimes it daesn't even get to the A9.
I still have access to the recovery options, but so far it wasn't helpfull.
In the meantime I found out, after experimenting with the second, working same tablet, that with KingoRoot, the tablet can be rooted and the logfiles where succesfuly wiped, freeing all 5.8GB of internal ROM. But since then I was never given the chance to try it on the first tablet, because I'm stuck at boot.
So far, I wasn't able
1) To find the original stock ROM. I've found for the 814 but NOT for the 814s. I even contacted Intenso and the answer was
Dear Mr. XXXX,
thank you for your request to our support-team. We are sorry to inform you that there´s no firmware (4.2.2 ROM) for the Tab 814S available by the part of Intenso which can be installed afterwards.
with kind Regards
Mxxxx Vxxxx
(Support Team)
2) To find a proper root.zip to install through Recovery->SD Card option. I've tried many (10-12) AML8726 compatible zips but everytime I get the same result "Verification Failed"
Can you please suggest something?
I suppose mine is a "Soft-Brick" so I guess there must be some hope for me.
Is there a way that I can extract some files/bins/zips or whatever from the working tablet and pass them to the faulty one?
Remember I only have access through Recovery. The tablet doesn't boot and when stuck on the "A9" logo, my PC doesn't recognize it as external drive.
Is there something that I can do through Recovery->Update through ADB ?
Please help.
After many trials, the only thing that lets me interact with a PC is the "adb sideload" command, on "Load from adb" option in recovery. But still, when I's sideloading zips, I get veryfication failed.
Any ideas? Anything please... Even if radical, I'm willing to try. The tablet is unusable anyways
i have excacly the same problem did u find anything for how to fix it?