Discussion in 'Android Devices' started by Sebastian404, Dec 1, 2011.
I flashed the new recovery and I still get stuck at the green android bootloader. Too bad :/
Any error messages? I wonder if we should be using super user in adb and doing it through shell?
I did it with adb and fastboot on my pc with no errors, pushed and flashed just fine. Go right ahead and try it through shell.
hmm, ok, this is proving interesting... couple more things to try tho..
here is a another version of clockworkmod recovery, built differently:
if that still does not work, can you try to flash this:
its a stock recovery image, just to prove that the process works and I'm using the right files.
if it works, can you then try this:
which is the stock image that I have taken apart and rebuilt, this would prove that method for creating recovery images is valid..
b3 didnt work
stock rebuilt worked also
Sebastian i see you are still having technical difficulties getting this to work do you think that you could get it to work if you actually had the phone or some help ? because i think that people would be willing to donate to fundraise to get a phone for the cause!
and if you need help let me know as i need the learning experience in android deving
I was thinking more along the lines of remote access.
Hmm, I'm stuck with no real Internet access till next week, when I'm back home, it seems this needs a bit more research
I'll carry on wfh it next week. Thanks for the help so far tho guys
I'll be waiting.
Just as an after thought, if you flash r3 and reboot into recovery, while your just stuck at the green andoid, id adb working? if you do a 'adb-windows.exe devices' does it show up? and if so can you get a shell (adb-windows.exe shell) ?
I just went to work and wont be able to test it until I get home in 10 hours.
Yes to both. See screenshot.
Excelent. Can you do the following:
Adb-windows pull /sdcard/dmesg.txt
Adb-windows pull /sdcard/mount.txt
And then upload those two txt files somewhere?
I'm about to catch a flight home so hopefully more progress tomorrow
Ok here they are.
ah, sorry I should of been clearer, can you install r3 and then restart into recovery, and then once it is sat at the green android logo then do those commands?
also can you do a
adb-windows.exe pull /cache/recovery/log
adb-windows.exe pull /proc/cpuinfo
hopefully one of those files will give me a clue as to why its not booting.
Ok when I try to pull recovery log it say it does not exist. Kinda makes since cuz its never been used. Heres the rest.
Looking at dmesg it seems to be having problems mounting stuff.. so.. hmm..
if its still not working can you do the dmesg thing again?
All I show is still the bootloader image. However, the touch buttons light up and respond to haptic feedback. So it will vibrate if I touch home and do a system reboot, just like recovery.
hmm, sounds like it is actally working, but the display is not...
if you press vol down and then home, does it still reboot?
It did the same except the buttons at the bottom lit up and screen is brighter. Still hung though.
No nothing have to pull battery
No it doesn't reboot. Hopefully its asking to apply an update from the sd card
Is there now a log file in cache/recovery/log ?
It sounds like its working but the screen is not working... If so nearly there..
I did a backup and it showed up in clockworkmod folder!
not for me. No log file present