[hucqim80]

Read This Guide First Before Open Up Your Apad Or Flashing... This Method Only Known To Work With RK2808 CPU based aPadBefore You Flash Any Custom Rom, Take Note Of Your Original Firmware Revision,Build Number, aPad model, This Might Help In Case Something Wrong Happen, Save Known Working Rom/Fw Or Original/Default Rom/Fw In Case Of Recovery..Firmware download:[ROM] Apad Metal Red LED 9V Metal (Hiapad) Chinese 0802 (bootloader 3.27)run mkupdate.bat to get the update.img in rockdev folder..[ROM] Apad Metal Blue LED 9V/5V Batch 3 Metal (Hiapad) 0806 (bootloader 3.20)for example if you trying to restore and bricked using 0802..then do the needle trick and flash it with 0806..if bricked using 0806 flash it with 0802..Flash Tool:RKAndroidDMhttp://www.multiupload.com/G7EIW4OK4I There is 2 type of bricked:1: Semi Bricked or Soft Bricked2: Total Bricked or Hard Bricked or High Tech Bricked1:Semi Bricked is: 1.You're able to make it detected in windows and RKAndroidDM or RKAndroidTool, 2.When you're trying to flash it, its stopped in the middle of the flashing process (usually stop after 32 second),if you're flash it with incompatible firmware, 3.Some of it able to turn on but looping in the booting process,some does not, 4.Some of it also able to turn on but the screen went blackout in the home screen.This happen because you're flashing it incompatible firmware..which contain different files needed for your apad to start properly (different kernel or bootloader or etc)but lucky enough these bootloader able to register itself to the usb as RKAndroid Loader for flashing back..Solution: Flash/Update it back with the known working firmware..----------------------------------------------------------------------------------------------------------------2:Total Bricked is: 1.You're not able to make it detected in windows and RKAndroidDM or RKAndroidTool even though you tried to press any button (there are many different way)for example the usual way to connect it to the bootloader: Switch toggle off then back on, Press and Hold the Menu button, Plug the usb from the back of the pc to the bottom usb port of the aPad(near the phone jack input ) 2.Won't turn on at all, 3.Its sure look like dead,no sign of life except when you plugged in the charger it will turn on the led only..This happen because of incompatible firmware..but compared to the semi bricked,unfortunately these bootloader won't register itself to the usb as RKAndroid Loader for flashing back..Solution: Just follow my videos tutorial..part 5..Needle Trick to make it recognized in pc as Maskrom loader and flash it with firmware above.. ---------------------------------------------------------------------------------------------------------------When we flash a new firmware we also overwrite the bootloader if we using RKAndroidDM, if we use the RKAndroidTool there is option to flash thing that we only want to flash ie system.img or kernel.img.So this won't overwrite your bootloader.The RKAndroid Loader reside in Nand Flash..if it does not able to speak with your hardware..then it won't able to load itself to the usb or in other case it connected to usb but it failed to test your device during the flashing process..example:16:10:37 203 INFO: Download Boot start16:10:37 250 INFO: Download USB Data OK16:10:37 578 INFO: Download USB Boot OK16:10:38 578 INFO: Test device start16:10:47 593 ERROR:Test device failed,ErrCode(-2)16:10:57 593 ERROR:Test device failed,ErrCode(-2)16:11:07 593 ERROR:Test device failed,ErrCode(-2)16:11:08 593 ERROR:Testing device failedThe RK28 MaskRom reside in the RK2808 CPU itself, it just like BIOS of apad, it allow you to perform restore only in RKAndroidDM incase of total bricked..

 

[gevrik]

Not enough info to help. Which device is it, where exactly did the flashing process stop? Which software did you use to flash?

 

[arminf]

Hello i have the nearly the same issue. Bricked the irobot while flashing. It loops on the android logo while booting.Model E7001Pakage irobot ProdNo 51039i can find the usb drive on windows with rk_android but it tells me after a while it cannot load the driver.W7 Pro x32update image patch 3 thanks!

 

[hucqim80]

[quote name='gevrik;40106]Not enough info to help. Which device is it' date=' where exactly did the flashing process stop? Which software did you use to flash?[/QUOTE'] I,ve Apad Irobot RK2808 ROCKCHIP VERSION 1.2.7 (ruiguan)With Aluminium casing and behind it,there a logo of android and iRobot word...and beside the 9v charger input there is oval hologram sticker with the word YB on it...i flash it HiApad batch 3 0806 firmware using HiApad Flasher..because I thought it was batch 3 version of HiApad..its stopped during the middle of the flashing process..usb suddenly disconnected..it(RKAndroidDM) ask me to plug in back the usb..so I un-plug and re-plug the usb, but the RKAndroidDM does not detect the apad even windows xp 32 does not see it..

 

[hucqim80]

few more pic:

 

[hucqim80]

Do It On Your Own Risk!!!Before this my Apad could not detected by usb flashing...google around and found way to make it detected by pc..here it is Rockchip DEAD Player Recovery Guidei disassemble the apad, run the RKAndroidDM v1.2 and hold the menu button,toggle on, plug the usb, slide the tweezer at the nand flash ic pin,suddenly it detect my apadbut its say "player: RK28 MaskRom"Right now I don't have working firmware for my apad, doesn't know which one could work, I try update with HiApad, but it say it can only restore..but its say "downloading boot file failed,please re-plug device!"if anyboby knows something about this please help..

 

[kessi]

Hello, where do you find a Firmware for the apad as a .rfw instead of an .img image?

 

[xaueious]

That revision bricks all the time with firmware flashesThat isn't even the same device he has linked there...

 

[hucqim80]

That revision bricks all the time with firmware flashesThat isn't even the same device he has linked there...

Sorry:confused: no..its not the same device..just a way to make the apad detected by windows if not seen in hardware device nor RKAndroidDM v1.2... not really recommended though..1: you could damaged your nand flash..2: there is no rk2808 SDK(inside the sdk there is nandtool to erase bad flash)..but for the rk27xx(the player i've link before) they have the rk27SDK..i've downloaded it and give it a try but could not work for rk28xx.

 

[hucqim80]

[quote name='kessi;41602]Hello' date=' where do you find a Firmware for the apad as a .rfw instead of an .img image?[/QUOTE'] if i'm right .rfw is recovery firmware..that come from rockchip SDK..for apad rk2808 SDK..they yet not release it..or maybe not release at all..the rk27xx sdk was leaked, not release officially..

 

[okay]

Red led? I bricked one of those too.[quote name='hucqim80;40407]I' date='ve Apad Irobot RK2808 ROCKCHIP VERSION 1.2.7 (ruiguan)With Aluminium casing and behind it,there a logo of android and iRobot word...and beside the 9v charger input there is oval hologram sticker with the word YB on it...i flash it HiApad batch 3 0806 firmware using HiApad Flasher..because I thought it was batch 3 version of HiApad..its stopped during the middle of the flashing process..usb suddenly disconnected..it(RKAndroidDM) ask me to plug in back the usb..so I un-plug and re-plug the usb, but the RKAndroidDM does not detect the apad even windows xp 32 does not see it..[/QUOTE']

 

[hucqim80]

yes red led, but with 9v charger..i think batch 3..

 

[Sazabi]

Hi there!Bricked absolutely the same apad while trying to update it. Hiapad guy sad my they do not have metal apad with red led and 9v charger, strange. Tried hard reset - it was founded on PC, but could not upgrade or restore. Cannot connect it with hard reset again, looks like it's complitely dead.Is it possible to dumb Samsung Nand somehow and load dump to bricked APad?

 

[hucqim80]

i'm thinking the same way too..if someone who had the same device could dump the firmware for us...the only same device i've seen is at aPad iRobot gets new board MD01-V6.0 ? cnPad.info ? aPad iRobot Moonse...one thing i'm sure is nand flash was not detected after the upgrade..it maybe because of the bootloader in hiapad fw is different than in this new board..before this i've short- circuit the nand flash to make it detected in windows..but its not register as rkandroid loader but as rk28 maskrom..so i use the hot air gun to remove the nand flash..than i connect it to pc using normal method of flash upgrade..and it connect to pc straight away..and register itself as rk28maskrom..so obviously the rk28 maskrom was not in nand flash..and because of the wrong fw..the cpu instruction to communicate with the nand flash has failed..

 

[janvitos]

Same thing hapened to me today.Just received my aPad Red Led V2 Aluminum Casing 8 GB.Tried to flash it with the custom firmware but it failed right after it started.I guess it failed because the aPad lost connectivity to the USB, not sure why.The aPad does not boot at all anymore (plugged in or not).I've tried "Rockchip DEAD Player Recovery Guide" with SOFT reset but it did not work.Will try HARD reset later.Anyone had success restoring their dead aPad V2 ?

 

[hucqim80]

before this i have the plastic back apad...when i bricked it, it still able to re flash because it still able to connect to pc..but i return that apad because it had fade spot on the screen and always turn off..and they give me aluminium back version..on the same day i flashed it bricked..so now i'm experimenting with this apad but we really need help from the senior to troubleshoot this..i'm going to buy the old one back next week..

 

[hucqim80]

[quote name='janvitos;45047]Same thing hapened to me today.Just received my aPad Red Led V2 Aluminum Casing 8 GB.Tried to flash it with the custom firmware but it failed right after it started.I guess it failed because the aPad lost connectivity to the USB' date=' not sure why.The aPad does not boot at all anymore (plugged in or not).I've tried "Rockchip DEAD Player Recovery Guide" with SOFT reset but it did not work.Will try HARD reset later.Anyone had success restoring their dead aPad V2 ?[/QUOTE'] i think you should return it...coz you just get it for one day just tell them it won't turn on

 

[djxs]

i'm thinking the same way too..if someone who had the same device could dump the firmware for us...the only same device i've seen is at aPad iRobot gets new board MD01-V6.0 ? cnPad.info - aPad iRobot Moonse...one thing i'm sure is nand flash was not detected after the upgrade..it maybe because of the bootloader in hiapad fw is different than in this new board..before this i've short- circuit the nand flash to make it detected in windows..but its not register as rkandroid loader but as rk28 maskrom..so i use the hot air gun to remove the nand flash..than i connect it to pc using normal method of flash upgrade..and it connect to pc straight away..and register itself as rk28maskrom..so obviously the rk28 maskrom was not in nand flash..and because of the wrong fw..the cpu instruction to communicate with the nand flash has failed..

Or at least try and get the proper settings.. maybe something in HWDEF was changed? (Would different offsets and sizes effect that?)One question though, was your build, RK-1.3.2.eng.root.20100729.130751?

 

[hucqim80]

One question though, was your build, RK-1.3.2.eng.root.20100729.130751?

yes i think i'm sure it was that build..

 

[djxs]

[quote name='hucqim80;46016]thanks' date=' i'll try that...yes i think i'm sure it was that build..[/QUOTE'] Same one I have then... I still have access to the bootloader though, but unfortunately can't get any firmware to flash.I also don't know if they use a new bootloader version, maybe it's 3.27 and not 3.20 like the older ones use.. I have contacted the supplier I bought the device from and he said he will check with the factory regarding 0729 firmware.