Root [GSM] evo3d ruu mode issue

[scotty85]

cool,let me know how that goes. you can try the hboot method,or you can try the ruu method:

-phone in fastboot
-flash with following:
fastboot erase cache

fastboot oem rebootRUU

fastboot flash zip zpname.zip

fastboot reboot-bootloader

fastboot reboot

there are some other zips,and .exes you can try here:
Shipped ROMs

just make sure you only use the ones for shooter_u

 

[mofanofa]

i have tried the one u posted and another one and they not flashed
giving remote not allowed

 

[scotty85]

Looks like you are trying to flash from regular fastboot,wich won't work. You'll need to put it in ruu mode,as described in post 27

 

[mofanofa]

Looks like you are trying to flash from regular fastboot,wich won't work. You'll need to put it in ruu mode,as described in post 27

how i put it in ruu mode?

 

[scotty85]

Commands in post# 27

 

[mofanofa]

post #27 is mine

Download 2013-05-13_125250.png file

u meant 26

the same problem.. stuck at WP SYSTEM (


Download 2013-05-13_130152.png file

when it stucks and remove the usb cable it said "failed too many links" then after reboot the screen with four triangles come again

So scotty it looks a hardware issue ?

 

[scotty85]

post #27 is mine

Download 2013-05-13_125250.png file

u meant 26

indeed i did,i was on the phandroid app,and it defaintely made it look like it was post 27

the same problem.. stuck at WP SYSTEM (


Download 2013-05-13_130152.png file

when it stucks and remove the usb cable it said "failed too many links" then after reboot the screen with four triangles come again

So scotty it looks a hardware issue ?

starting to look that way.

in post 19,when you flashed the recovery to originally get out of ruu

mode,were you able to access recovery from the hboot menu?

if you havent,try that now.

 

[mofanofa]

indeed i did,i was on the phandroid app,and it defaintely made it look like it was post 27


starting to look that way.

in post 19,when you flashed the recovery to originally get out of ruu

mode,were you able to access recovery from the hboot menu?

if you havent,try that now.

you mean the screen of 4ext recovery tuch?


yes i can but first it said no sd card and boot without sd card since i remove my sd

and then said recovery is in safe mode because the following partition is inaccessible "cache:

 

[scotty85]

did you try rebooting the phone? give it a couple minutes after it doesnt boot,then try and go back to recovery. hopefully cache will be accessible then.

you can go to recovery,and then,try this,to determine the emmc's condition:

enter recovery

open cmd

adb devices
adb shell
dmesg | grep mmc0

good output(gsm 3d with ext 4 recovery):

c:\miniadb_shooteru>[COLOR="Red"]adb shell[/COLOR]
~ # [COLOR="red"]dmesg | grep mmc0[/COLOR]
dmesg | grep mmc0
<3>[    2.973723] mmc0: No card detect facilities available
<6>[    2.974150] mmc0: Qualcomm MSM SDCC at 0x0000000012400000 irq 136,0 dma 18

<6>[    2.974333] mmc0: Platform slot type: MMC
<6>[    2.974455] mmc0: 8 bit data mode enabled
<6>[    2.974638] mmc0: 4 bit data mode disabled
<6>[    2.974730] mmc0: polling status mode disabled
<6>[    2.974852] mmc0: MMC clock 400000 -> 48000000 Hz, PCLK 0 Hz
<6>[    2.975035] mmc0: Slot eject status = 0
<6>[    2.975127] mmc0: Power save feature enable = 1
<6>[    2.975310] mmc0: DM non-cached buffer at ff007000, dma_addr 0x570ac000
<6>[    2.975432] mmc0: DM cmd busaddr 0x570ac000, cmdptr busaddr 0x570ac300
<6>[    3.099577] mmc0: new high speed MMC card at address 0001
<6>[    3.100005] mmcblk0: mmc0:0001 KLL00M 2.25 GiB
~ #

bad output(from internet):

mmc0: failed to get card ready
mmc0: reinit card
mmc0: Starting deferred resume
mmc0: Deferred resume failed

let me know if your code looks like one or the other,or looks sort of like one,but with errors intermixed. copy and paste it if you want to

 

[mofanofa]

c:\mini-adb>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT22TV203351 recovery

c:\mini-adb>adb shell
~ # dmesg | grep mmc0
dmesg | grep mmc0
<3>[ 3.005797] mmc0: No card detect facilities available
<6>[ 3.006438] mmc0: Qualcomm MSM SDCC at 0x0000000012400000 irq 136,0 dma 18
<6>[ 3.006621] mmc0: Platform slot type: MMC
<6>[ 3.006743] mmc0: 8 bit data mode enabled
<6>[ 3.006926] mmc0: 4 bit data mode disabled
<6>[ 3.007018] mmc0: polling status mode disabled
<6>[ 3.007109] mmc0: MMC clock 400000 -> 48000000 Hz, PCLK 0 Hz
<6>[ 3.007292] mmc0: Slot eject status = 0
<6>[ 3.007414] mmc0: Power save feature enable = 1
<6>[ 3.007597] mmc0: DM non-cached buffer at ff007000, dma_addr 0x570ac000
<6>[ 3.007689] mmc0: DM cmd busaddr 0x570ac000, cmdptr busaddr 0x570ac300
<6>[ 3.150420] mmc0: new high speed MMC card at address 0001
<6>[ 3.150847] mmcblk0: mmc0:0001 HYNIX 2.25 GiB
~ #

 

[scotty85]

hmm that certainly doesnt look like a bad output. maybe try and find a very small footprint AOSP rom(smaller MB,the better) and try and flash that with recovery. maybe there for some reason isnt enuff useable memory in the system partition for the stock image to flash.

 

[mofanofa]

hmm that certainly doesnt look like a bad output. maybe try and find a very small footprint AOSP rom(smaller MB,the better) and try and flash that with recovery. maybe there for some reason isnt enuff useable memory in the system partition for the stock image to flash.

what do you mean by footprint AOSP rom.. do you have any link?

thanks

 

[DonB]

He means a smaller Rom, one that does not have all the bloatware and Google apps, one that is only about 150 Mb's there are many. He simply wants to see if a smaller footprint Rom will flash, he thinks you might have a memory issue.

what do you mean by footprint AOSP rom.. do you have any link?

thanks

 

[mofanofa]

He means a smaller Rom, one that does not have all the bloatware and Google apps, one that is only about 150 Mb's there are many. He simply wants to see if a smaller footprint Rom will flash, he thinks you might have a memory issue.

ok thanks i will try to download one and test

 

[scotty85]

He means a smaller Rom, one that does not have all the bloatware and Google apps, one that is only about 150 Mb's there are many. He simply wants to see if a smaller footprint Rom will flash, he thinks you might have a memory issue.

exactly! we may even have you flash an older hboot,so you could try a GB rom. seems some CM7 roms were 60-70mbs

 

[mofanofa]

exactly! we may even have you flash an older hboot,so you could try a GB rom. seems some CM7 roms were 60-70mbs

i have dowloaded this rom

cm-9-DevilToast-0.6.1-shooteru

but upon flashin it gives

failed <remote: 24 parsing android -info fail>

any help

or tutorial for AOSP flashing

 

[DonB]

I don't have an 3VO anymore, but I am sure as soon as Scotty has a little more time, he will respond.

Not sure which would be best to try, so I would wait for Scotty, but you can take a look in the meantime on the options, but again I would wait for Scotty

EVO 3D GSM Android Development

 

[scotty85]

i have dowloaded this rom

cm-9-DevilToast-0.6.1-shooteru

but upon flashin it gives

failed <remote: 24 parsing android -info fail>

hmmm wonder why i didnt get any notifications of these replies?

well,at any rate,sounds like you tried to flash the rom download in hboot

you will want to flash that rom in recovery,just like you would any.
-put download on sd card
-boot to recovery
-wipe data,cache,dalvik cache
-flash rom
-try and reboot

again,sorry for the late reply

 

[mofanofa]

Spoiler

hmmm wonder why i didnt get any notifications of these replies?

well,at any rate,sounds like you tried to flash the rom download in hboot

you will want to flash that rom in recovery,just like you would any.
-put download on sd card
-boot to recovery
-wipe data,cache,dalvik cache
-flash rom
-try and reboot

again,sorry for the late reply

don't worry man

i have tried the jellybean but the rom failed at creating symlinks?

i also tried cyangenmod 9

gives assert failed : write_raw_image ('tmp/boot.img", "boot")

 

[scotty85]

hmm,im not sure what else to try. sure seems you have some sort of memory or hardware issue preventing things from working correctly.

ill keep pondering it for something else to try,but its not lookin too good

edit: you were trying roms compatible with your current hboot,correct?

also,maybe do a

fastboot getvar all

and paste that output. skimming back thru,i dont believe weve done that.

 

[mofanofa]

also,maybe do a

fastboot getvar all

and paste that output. skimming back thru,i dont believe weve done that.

Spoiler

c:\mini-adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.53.0007
INFOversion-baseband: 10.14.9020.06_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOserialno: HT22TV203351
INFOimei: 356871040858783
INFOproduct: shooter_u
INFOplatform: HBOOT-8260
INFOmodelid: PG8630000
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 5296mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: RUU
INFOcommitno-bootloader: 10e127f0
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.495s

hmm,im not sure what else to try. sure seems you have some sort of memory or hardware issue preventing things from working correctly.

ill keep pondering it for something else to try,but its not lookin too good

edit: you were trying roms compatible with your current hboot,correct?

i have tried all roms available on the internet

 

[DonB]

OK, you gave us a little history on your device, but just curious a little more, you said that has been happening for 3 weeks >> correct. When did you buy the phone, where did you buy it from, how long have you owned it, maybe it came with a bad motherboard or chipset ?? also maybe somewhere along the line you flashed something not GSM related. I agree with Scotty, going back and reading through the post it definitely looks like bad memory, and I believe Scotty has tried everything he could think of, and believe me when I say this if Scotty can't get this revived then there is a problem, he can bring anything back with a slight pulse.

 

[mofanofa]

OK, you gave us a little history on your device, but just curious a little more, you said that has been happening for 3 weeks >> correct. When did you buy the phone, where did you buy it from, how long have you owned it, maybe it came with a bad motherboard or chipset ?? also maybe somewhere along the line you flashed something not GSM related. I agree with Scotty, going back and reading through the post it definitely looks like bad memory, and I believe Scotty has tried everything he could think of, and believe me when I say this if Scotty can't get this revived then there is a problem, he can bring anything back with a slight pulse.

yes the phone is not working 4 weeks ago now.
- When did you buy the phone: one year ago and i bought it used not new
- where did you buy it from: it was used with my friend. i don't know from where he bought it
- how long have you owned it: one year
- maybe it came with a bad motherboard or chipset ?? i don't think. it was working properly and suddenly it stop working giving white htc screen and restart itself . then i tried to install ruu rom downloaded from the internet it stucks at 27 % and give the black screen with 4 triangles.
- also maybe somewhere along the line you flashed something not GSM related: the first ruu that i tried to flash i don't remember what it was since i have no experience that time.

one morething when i flashed the recovery that scotty posted here . the green bar didn't reach 100 % . it reaches 75% but the phone reboot into bootloader normally.

 

[scotty85]

youll find that the green bar doesnt need to reach the far right side. as long as it gets to 100% and says "finished" in the command window,you are good to go.

something is definately wrong with the system partition. maybe just too many bad memory blocks for anything to flash?

i have tried all roms available on the internet

what i meant was,if you read some roms descriptions,some of them will require you to be on a certain hboot. generally i beleive AOSP roms will want you to be on hboot 1.40,while while most stockish roms will need to use 1.53.

might look at the roms youve tried,and see if anywhere in the description it says you needed to be on someting different than the 1.53 youre on

 

[mofanofa]

really i dont know what is the problem with this phone.. i took it to the best repair center and they didn't know to flash it. they said we have a problem the phone is not taking any firmware.

what i meant was,if you read some roms descriptions,some of them will require you to be on a certain hboot. generally i beleive AOSP roms will want you to be on hboot 1.40,while while most stockish roms will need to use 1.53.

might look at the roms youve tried,and see if anywhere in the description it says you needed to be on someting different than the 1.53 youre on

how can i got 1.4 hboot

any new updates scotty?