Getting into ADB to recover from bootloop?

[Guest Jinx13]

Hello, so I tried to pre-root my Lollipop build and I'm in bootloop. I can get to this screen but cannot do anything else. My kids are going to go mad tomorrow haha

 

. 

 

Can anyone help?

 

Thanks in advance

[Guest samac]

can you use the volume buttons to change the title at the top of the page?

 

[Guest Jinx13]

Yup

 

Power Off = Power off

Restart Bootloader = Back to this screen

Normal Boot = Bootloop

Recovery = Back to this screen

 

Tried Windows and Linux ADB and Fastboot commands aswell

Edited October 17, 2015 by Jinx13

[Guest samac]

Just a thought, unfortunately that's as far as my expertise stretches.

[Guest Jinx13]

Thank you for the reply anyway :)

[Guest vampirefo]

Looks like you didn't install or patch kk boot and recovery image to lollipop.

Can you explain exact what you did to try and root?

[Guest Jinx13]

Well I was in update loop and couldn't install the 300+ preliminarily update due to boot.img verification. So I extracted that update from /cache/ and opened it opened the meta to not check. Next was fastboot.img.

I did the same with that and then updated without issues. Then I downloaded the new lollipop update and rooted and extracted that from /cache/

I went to tethered recovery and flashed it then while in recovery I flashed the latest supersu.zip

The update finished and then bootloop

 

I think I am bootlooping because DM-VERITY https://source.android.com/devices/tech/security/verifiedboot/dm-verity.html

Which is the reason that most lollipop roms cannot be rooted. What I should have done with the lollipop rom was tried to switch off the dm-veriry trigger

If I could get bback into recovery I would just reflash the Lollipop rom and leave it at that 

[Guest vampirefo]

So you have KitKat recovery boot and fastboot, and lollipop system.

Have you tried tethered recovery on your current setup?

[Guest Jinx13]

Nope I should have lollipop recovery, boot, fastboot and system as I flashed the whole rom then while still in recovery flashed the supersu zip. 

 

I cannot get to tethered recovery as the hudl is in bootloop

 

Thanks for your replies

[Guest vampirefo]

The edits you made prevented recovery, boot and fastboot from upgrading, you only have lollipop system.

You are going to need boot, recovery, fastboot from lollipop, fastboot them to your tablet to allow tablet to boot into recovery or regular boot.

To get those you will need some to root their tablet and dump them for you via adb.

[Guest Jinx13]

Do you think?

My thinking was because I hadn't previously messed with the boot.img file at all that there was a small update which updated then failed which then stopped me updating to the 300mb+ update.

I think at that point the mismatch was because I already had boot updated and not from the old rom.

So because I believe I had already an updated boot I disabled the boot.img check and updated fine.

Then came the big lollipop update which I updated myself through tethered recovery which includes the lollipop boot so in theory should have all updated fine as there wasn't any errors.

I then installed the supersu zip which in turn installs to system however with lollipop dm-verity system fails to boot because the check fails at boot time.

I am stuck with this theory about it all as had bootloop trying to pre-root my Sony Xperia Z when lollipop was available dm-verity was the reason for not booting.

 

Also I never seen this menu in the picture at all on Kitkat maybe I am wrong.

 

Do you think there is any way of me to access adb? I think I have chance if I can however I have tried on ubuntu and windows :(

 

On another note I blagged my kids and said that the update failed so I need to get it fixed haha

 

Thanks again

[Guest Jinx13]

Another note I think it maybe a driver issue that I cannot connect to fastboot because it does say at the bottom of the bootloader screen "FASTBOOT CMD WAITING"

I have though tried every driver under the sun :( And my girlfriends hudl connected fine with ADB

[Guest Sparkey159]

I don't think thats a fastboot issue, If I remember correctly, You need to add "-I 0x1D4D" after fastboot.

Example: "fastboot -i 0x1d4d flash system rom.img" <-- (Taken from Paul's Hudl 2 Root Thread)

Please ignore this if you already knew about it.

Edited October 18, 2015 by Sparkey159

[Guest Jinx13]

Ah thank you I did know that but only thought it was for flashing I did "fastboot -i 0x1d4d devices" and returned a result now I might be able to return to normal

Does anyone know what file formats can be flashed with fastboot? Is it only .img

 

Maybe I could try flash a recovery.img

Edited October 18, 2015 by Jinx13

[Guest vampirefo]

So you have tried tethered recovery on your current setup? I don't think your lollipop update contained a boot.img My thinking is you had a patch. The patch was designed to updated your KitKat boot.img to lollipop same with fastboot and recovery. It passed due to no checks, the first update that you failed was checking to make sure your tablet was ready to be patched, you edit out check, so lollipop tried to patch without checking, but unable to patch it just installed lollipop system and left boot, recovery, fastboot as KitKat.

[Guest Jinx13]

Nope I just tried to install it by editing all the fastboot commands in the script to include -i 0x1d4d and although fastboot was online in the program the flash commands are not permitted :(

I looked at the image and the boot.img is included and I never edited the boot.img in anyway previously

 

Surely if I had kitkat boot then I would have been able to install tethered recovery just now

Edited October 18, 2015 by Jinx13

[Guest vampirefo]

OK so there is no boot patch? Windows sometimes hide extensions. So boot.img could be boot.img.pl

[Guest Jinx13]

Nope definitely not it's recorded as a disk image as well

 

 

BTW hope you didn't mind me editing the recovery script

Edited October 18, 2015 by Jinx13

[Guest Jinx13]

Thanks for the help I sent it back to Tesco and they repaired it. Funny enough it came back with 4.4.2 and no updates do you think they may have disabled the ability to update? So anyway think now I'll just disable apps instead of delete them

[Guest J6655]

i have got exactly the same problem as Jinx13. But i bought it from gumtree so no chance to send it back to Tesco. It cant into recovery. Can any body help please

[Guest J6655]

My hudl 2 is stuck at fastboot, there is optiona at the top to boo in recovery mode but its not working and im not very familiar with development and hacking, will tethered recovery work without usb debugging? I love my hudl 2 but i was too restless for lollipop update but was not happening so i decided to manually flash it in stock recovery but it went into boot loop.

 

 

[Guest J6655]