So, I dun goofed...

[Guest Justice™]

Well, after a little too much adventurous experimentation with bringing KK to the Hudl, I made a bad mistake and ended up "hard bricking" so to speak, (I say hard bricking as the Hudl is in a permanent recovery/flash mode state and is always met by erase idb errors when trying to reflash the device). Now, as I can't find any documentation on the nand/emmc (Samsung klmag2we4a-a001 by the looks of things), I have no idea on how to erase the NAND or put it into a mask rom mode (Some RK3188 users were doing this on devices with Hynix NAND), I'm not quite sure what to do now with the device. I'm considering contacting samsung in hope of receiving some kind of specific datasheet/pinout but aside from that, I'm left with a hudl shaped paperweight for now.

 

 

 

(If anyones curious about the KK port. Yeaaaah,it didn't go so great, I did get the Pipo U8 kk build barely running though for anyone interested!)

[Guest Lister Of Smeg]

Hi Justice™,

Thank you for taking the time to look into, and trying to bring KK to our Hudl's (i'd still bet your version would of come quicker than Tesco's) and sorry to hear you've ended up with a brick in the process.... :(

How bad does it look, does it look like you've played around with it... Or could you play dumb and take it back to Tesco's and say "we was watching a film, and all of a sudden it shut down..... and this is now all we see it do"  blah blah blah "Can I have a new one please???" and see what they do...??

If it boots up into ClockWorkMod, then I guess ya can't really get around that... But if ya presented with a lot of jibberish, that doesn't show any signs of KK (more recent Android) then I'd play dumb to it all, and see if they'd swap it???

Got nowt to lose, and everything to gain... ;)

Cheers, Lister

[Guest colzilla]

im in the same boat..

did you ever find a fix?

my NANDS blank lol

have full connection to the writing tools ie   rkbatch & rkandroid etc etc

all fail due to idb fail!!

some one help please

[Guest]

From memory, idb errors are generally the death nail in the original hudl - normally caused by attempting to flash the wrong boot version - this was generally always unticked in the list of partitions to flash.

Have you tried flashing partitions via the linux command-line tools, where all you need is the hudl in boot-loader mode and the correct usb android driver loaded in linux?

It's something I've asked people before in this situation but don't get a reply..... just thinking of other options.

[Guest colzilla]

Found a solution..

TThis how unbricked 

Need original USB cable that came with hudl or a series one.

Download

Bootloader rk3188Loader(L)-V1.04.bin and Helios ROM v1

Install rkflashtool and upgrade_tool on linux

Unzip Helios ROM on windows 

On linux put device into loader mode. Hold volume up and press reset pin. 

Plug in usb and start rkflashtool

Command 

./rrkflashtool b 3

Run upgrade_tool 

Should list device as maskrom mode

If not just keep repeating rkflashtool b 3

Once in maskrom take to windows and flash using androidflashtool that's in Helios ROM zip.

Erase IDB and flash all boxes 

Goodluck.

[Guest dooderooni]

colzilla, I wonder if you can elaborate on your solution above as I'm a bit stuck.

Long story short, I dropped my Hudl and now it keeps asking for my Google credentials before rebooting ad infinitum.

Googling the issue brought me here.

I've tried flashing the Helios ROM and the stock images from here, but each time I get the IDB fail error indicating that it's bricked.

I can get it into ROM MASK MODE using rkflashtool in Linux (Mint, Kali & Debian tried so far) and then I run the upgrade_tool, but when I go back to my PC I have to switch the Hudl back into flash mode and get the IDB Fail issue again.

Any chance you can give a more detailed walkthrough before I defenestrate my Hudl permanently?