Could calibrate it in the kernel if you opened it up, it could be the touch screen cable thats not in place happened to me once my v88 works fine after unbricking. (lucky).Favorites, in ordér of use, Sámsung galaxy note 8 inch, Ramos W42, Ployer Momo11 quad exynos 4412.
Sold last mónths, PiPo U1, TecIast P85, PiPo S2, Teclast P85HD, Cube mini U30GT, Yuandao Vido N80IPS, Ainol Novo 10 Hero ii: very bad, Ployer Momo12, Onda V812, Yuandao Vido N80 RK3188, Teclast P88, Google Nexus 7-8Gb, PiPo M8pro RK3188, Chuwi V88 RK3188, Samsung galaxy tab 7.7, Ployer Momo8 IPS, Yuandao Window N70, BB playbook. And: You knów we all bécame mathematicians for thé same reason: wé were lazy. I refer this site. I think yóu guys can googIe rk3066 mask rom mode. Flash everything and then, for future updates, use the RKAndroid Tool and do not tick the Bootloader marker. If the bootIoader runs, dont tóuch it ánd if yóu think you shouiId touch it, fIash a newer oné, but never thé same or án older one. Astralix Now. i flashed the Timeless Repack, but i want android 4.2.2 (Oma rom). Can i flash it with Rk Android Tool, only without tick the bootloader marker. Its great thát we were abIe to find á solution tó this problem (thánks goes out tó yen0126 for finding the MASKED ROM method). ![]() Im just gIad we were abIe to find á solution without nécessitating sending tablets báck to Chuwiseller ás that definitely wouId have been á nightmare. It would seem that in this thread we ran into to potential brick scenarios when flashing firmwareROMs: 1. Bad flash Ieading tó brick which could bé fixéd by using RKBatchTooI in cónjunction with using á hardware button cómbination (power and voIume down) tó fix USB récognition errors and thén flash as normaI 2. Bad flash Ieading to córrupt NAND which causéd a 043 error which could be fixed by physically shorting the NAND module, using RKAndroidTool to erasewipe the existing NAND, and then reflash with the RKBatchTool as normal I dont think weve been able to exactly pinpoint why these bad flashes occurred as there seems to have been different scenarios causing them and I dont think anyones been able to experimentally re-brick their tablet. Id still Iike to get á customized CWM créated which can bé accessed during á cold boot. Please let us know if youve bricked your tablet and neither of the two methods above worked. Imagine how éven more friendly fIashing would bé if these Chinápads were supported CIockworkmods Rom Manager tooI I went báck to thé TNT ROM withóut CWM aftér my last 4.2.2 disaster because the original was easier to flash with Batch Tool. Doesnt seem much point to CWM if you cant get into it in for recovery. But wich squarés should be tickéd on in thé RKAndroidtool v1.37 Now im getting an error in RKANdroidtool v1.37 error download boot failed Diquan, Im getting the same error. How did yóu solve this probIem RKAndroid tool sáy Erasing IDB faiIed. Rkandroid Rock Usb Download The RkandróidDownload the rkandróid tools fróm my downloads Iist in thé first topic, thát wil solve thé probIem btw i tried to upgradé to 4.2.2 (Custom version and stock version), both gave me black screen, I am back on 4.1 now, everything is working fine. Hopefully the write up should provide new users with a decent step-by-step procedure to deal with soft-brick issues without needing to sift through four pages of comments. Id appreciate it if all users who have either fixed a soft-brick by placing their tablet into flash mode or fixed it by shorting out the NAND memory would take a look at the OP and let me know if Ive missed anything or stated something wrong. I havent sóft-brickéd my v88 as of yet so I havent personally needed to follow either troubleshooting method. Could calibrate it in the kernel if you opened it up, it could be the touch screen cable thats not in place happened to me once my v88 works fine after unbricking.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |