• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Boost Mobile] Testers wanted

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:

http://android.podtwo.com/beta/ztewarp/b3_recovery-clockwork-4.0.1.5-arthur.img

if that still does not work, can you try to flash this:

http://android.podtwo.com/beta/ztewarp/stock_recovery.img

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:

http://android.podtwo.com/beta/ztewarp/stock_recovery_rebuilt.img

which is the stock image that I have taken apart and rebuilt, this would prove that method for creating recovery images is valid..
 
Sebastian404 said:
hmm, ok, this is proving interesting... couple more things to try tho..

here is a another version of clockworkmod recovery, built differently:

http://android.podtwo.com/beta/ztewarp/b3_recovery-clockwork-4.0.1.5-arthur.img

if that still does not work, can you try to flash this:

http://android.podtwo.com/beta/ztewarp/stock_recovery.img

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:

http://android.podtwo.com/beta/ztewarp/stock_recovery_rebuilt.img

which is the stock image that I have taken apart and rebuilt, this would prove that method for creating recovery images is valid..
Click to expand...

  1. b3 didnt work
  2. stock worked
  3. stock rebuilt worked also
 
Sebastian404 said:
hmm, ok, this is proving interesting... couple more things to try tho..

here is a another version of clockworkmod recovery, built differently:

http://android.podtwo.com/beta/ztewarp/b3_recovery-clockwork-4.0.1.5-arthur.img

if that still does not work, can you try to flash this:

http://android.podtwo.com/beta/ztewarp/stock_recovery.img

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:

http://android.podtwo.com/beta/ztewarp/stock_recovery_rebuilt.img

which is the stock image that I have taken apart and rebuilt, this would prove that method for creating recovery images is valid..
Click to expand...

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
 
Mr Freeze said:
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
Click to expand...
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
 
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) ?
 
Sebastian404 said:
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) ?
Click to expand...
I just went to work and wont be able to test it until I get home in 10 hours.
 
Excelent. Can you do the following:

Adb-windows.exe shell
dmesg >/sdcard/dmesg.txt
mount >/sdcard/mount.txt
exit
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 :)
 
Woodstock77 said:
Ok here they are.
Click to expand...

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.
 
Sebastian404 said:
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.
Click to expand...
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.
 

Attachments

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.
 
attrapp said:
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.
Click to expand...

hmm, sounds like it is actally working, but the display is not...

if you press vol down and then home, does it still reboot?
 
You must log in or register to reply here.
Back
Top Bottom