Ooops! Stuck in boot loop with no recovery HELP?!

[flekz]

Hi
After first attempting to install clockworkmod and then replacing my build.prop i have stupidly got my scroll stuck with no access to recovery or anything else other than Fastboot mode. It is recognised by my PC and i can use fastboot commands so as far as I understand this means it is not bricked?

its an 8" resistive
model: scroll 2 (SCR051951)
Android: 2.3.3
Kernel: 2.6.35.7
build: P82B-T0-S3-H02-1087

I have spent hours going through the forum and trying things to resolve this and get the thing to boot normally but to no avail. I somehow need to either fix the build.prop issue so that i can boot into android (and worry about lack of recovery later) , OR get recovery back so that i might be able to factory reset?

Pleeeease can someone help? Unfortunately my backup copy of stock build.prop is on the internal SD of the scroll so i dont think i can get this (or can I..?) If not is this something that someone could kindly post here or email me?

Alternatively, any other suggestions?

Thanks

[suggsy89]

Any backups? Have you tried contacting Storage Options for the firmware?

Via fastboot we can update, or push .img files, but not individual files, for ADB to work, Android must me running on the device.

Code: Select all

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\John>cd C:\Program Files (x86)\Android\android-sdk\platform-tools

C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot
usage: fastboot [ <option> ] <command>

commands:
  update <filename>                        reflash device from update.zip
  flashall                                 flash boot + recovery + system
  flash <partition> [ <filename> ]         write a file to a flash partition
  erase <partition>                        erase a flash partition
  getvar <variable>                        display a bootloader variable
  boot <kernel> [ <ramdisk> ]              download and boot kernel
  flash:raw boot <kernel> [ <ramdisk> ]    create bootimage and flash it
  devices                                  list all connected devices
  continue                                 continue with autoboot
  reboot                                   reboot device normally
  reboot-bootloader                        reboot device into bootloader
  help                                     show this help message

options:
  -w                                       erase userdata and cache
  -s <serial number>                       specify device serial number
  -p <product>                             specify product name
  -c <cmdline>                             override kernel commandline
  -i <vendor id>                           specify a custom USB vendor id
  -b <base_addr>                           specify a custom kernel base address
  -n <page size>                           specify the nand page size. default:
2048

C:\Program Files (x86)\Android\android-sdk\platform-tools>

Any backups?

[flekz]

Hi suggsy,
Thanks for your reply.
I'm not sure what you are asking if I have backed up? But the only backup was build.prop and thats on internal sd. Would be no use anyway if I only have fastboot and not adb right?

I didnt think that, having messed around with the device, I would be able to get any help from the manufacturer. Has anyone managed to get them to send firmware then? Will certainly try if its my only hope.

Would the firmware be in the form of update.zip that I can run from fastboot?

Thanks again.
Craig

P.s. Other problem is I dont know what firmware I have/need. My scroll said it had latest version?

Sent from my Galaxy S using Tapatalk

[flekz]

latest update - I downloaded the firmware for my scroll from Storage Options website. The file is 'scroll-special-ed.zip' and believe this is correct for me.

Problem is, all I can access on my scroll is fastboot mode. I have tried: fastboot update scroll-special-ed.zip
I got the message about missing .txt files. My understanding is that this sort of update cant be installed via fastboot - only via the recovery menu but i have no access to that.

So what can i possibly do!

Any way of using the components within the firmware if i unpack it? I.e. boot.img, recovery-from-boot.p, build.prop (the replacement of which caused the damage in the first place)?

Literally i can only use fastboot - any suggestions would be very very welcome?

Thanks

[suggsy89]

Ill check out that firmware now, just downloading it, i will see what the pagesize is and see if we can fastboot a recovery for you, please be patient

Its a 16k....

Download this recovery image http://dl.dropbox.com/u/4364278/Special_Edition/recovery.img

Place it in your fastboot directory
Do...

Code: Select all

fastboot flash recovery recovery.img

See if you can boot to recovery

Then, do a backup, and upload the backup to an online file server, let me have the link, and ill make an update for you.

[flekz]

Thanks a lot for your help mate.
I didnt get a chance to log back in yesterday evening so have just seen your reply. I will try this when i get home from work tonight and report back... fingers crossed!

thanks again

Craig

[flekz]

Suggsy
you rock!

It worked and i'm in CWM Recovery!! Thanks a lot!

I have done a nandroid backup via CWM and i have:
boot.img, cache.yaffs2.img, data.yaffs2.img (150 MB), nandroid.md5, recovery.img, system.yaffs2.img

Which of these backed up files do you need in order to make me an update?
I trust the update would give me a replacement build.prop (as thats what stopped my device booting)?

thanks

[suggsy89]

No problem

I need boot.img and system.img, please upload to any file share website and PM me the link

Thanks

[suggsy89]

Hang on i just read your posts again, try flashing the special edition zip you downloaded

You have a backup now anyway so wont hurt

[flekz]

hi
i have tried applying the zip of firmware downloaded from the website but it failed:

assert failed: getprop("ro.product.device") == "tcc8900"

not sure what this means?
i used the install from .zip on SD card option.

I have sent you my boot and system files (PM sent) - hope you can help me with a working update

thanks