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

Root This is an ugly problem. Need some serious help.

I've been curious about that Kyocera device...but for now, I'll still stick with my 3vo.
 
Well it uses the same user made root application by giantpune as my Optimus Elite used. So root it without even leaving the UI. Just uses Ministro 2 libs and open the "poot" app and hit "poot" and voila it's rooted in less than 5 seconds. Than install Superuser. BUT, updating the binary breaks root so it doesn't like the newest binary. Bootloader is locked. No recovery. No roms. No nothing, there are only 7 threads for the entire device on this forum for the All Things Root hahaha. So there is literally only root. You can use custom boot anims, and underclock but that's it. I have noticed it charges the battery incredibly fast even with the screen on with auto brightness. It uses a 1ghz processor. Has 1.2gb's phone storage. 1gb's of app storage. Once you insert an sdcard it switches phone storage to your sdcard. So it has internal and external memory. It's pretty snappy. Android 4.0.4. It is a smaller device which is my only other CON for it besides no support at all. It's basically between 3 devices. This one being lowest end. Kyocera Rise has the qwerty keyboard, and Kyocera Hydro is just the same as the Event but with a water proof ability. Other than those, they have the same hardware I believe. There is no way to restore anything at all so if I do anything ugly with root... Well its garbage lol. But it was only 54 bucks so I don't care haha. It's just a temporary phone until I switch to Verizon in like 2 or 4 weeks. I'd say it's a nice phone tho. It has better battery life than the Evo V did that's for sure. That thing would die in my pocket with all my apps killed and screen locked. And my battery stats were messed up on the Evo so I could make it last like 4 hours on 1% battery! Haha!
 
I wanna give it another shot guys! I wanna fix this phone. Okay, so as I sit when I turn the phone on it immediately boots into bootloader without holding the volume down button with power. The HTC Logo shows up for about 1 second, it vibrates, and goes into the bootloader, which is the jbear 1.5050 hboot. Any ideas? I've just finally done the dmesg | grep mmc0 code and it reports a good input just with a few values different then the ones prinny copy pasted into this thread, but NO errors. I believe i'm just getting bad RUU downloads, wrong permissions, and an unzipping failure. Bad signature on the system.img? One thing I thought of today... What would happen if I loaded the system.img to the root of a 4GB sd card and then did the dd=/if command and dd'd it onto the correct system partition? Or is it too big to apply? It's 814mb's.
 
HaTrEd360 said:
I've just finally done the dmesg | grep mmc0 code and it reports a good input just with a few values different then the ones prinny copy pasted into this thread, but NO errors.
Click to expand...

what was the output?

HaTrEd360 said:
What would happen if I loaded the system.img to the root of a 4GB sd card and then did the dd=/if command and dd'd it onto the correct system partition? Or is it too big to apply? It's 814mb's.
Click to expand...

you could try that. however,if other means of installing something to the /system partition have failed,i wouldnt have much hope for that working either.

get your system image to the sd card,then:

dd if=/sdcard2/imagename of=/dev/block/mmcblk0p22
 
scotty85 said:
what was the output?



you could try that. however,if other means of installing something to the /system partition have failed,i wouldnt have much hope for that working either.

get your system image to the sd card,then:

dd if=/sdcard2/imagename of=/dev/block/mmcblk0p22
Click to expand...
22? I thought it was block 23 according to the cyanogenmod port project partition map. I checked partition 23 using the command adb shell then e2fsck -c /dev/block/mmcblk0p23 and that returned atleast 300 errors that it asked me to fix each one. End result is I have about 50 megabytes of corrupted blocks and I need to delete the partition completely and recreate it for the system to be installed on. The guide I got this idea from is located here An easy guide to relocate faulty partition for super-brick Note

you'll notice the command I posted has the partition it checks changed to 23 but in the guide I put up above uses partition 7 as it is for a different phone. But near the bottom it mentions if you cant resolve the bad block errors then you can remove the partition and recreate it. As thats a different phone I will NOT be following those exact instructions, but can someone modify them for me to recreate the system partition? I'm going to scan the data and cache ones in a moment as well.

I AM DETERMINED TO FIX THIS WITH MUMBO JUMBO MAGIC, lol.
My friend even said it might need to be sent back to HTC and have the entire chip reflashed.

I wiped everything earlier before trying any of these commands by the way and tried to install the JMZ stock Odex rom. It completed in 15 seconds, but you go down under to Info tab in 4ext and it says my system has all of its space free as much as before I installed it. I installed again and it just hangs for an hour+ and wont do anything during install so I have to pull battery. Rebooting to recovery, checking info, says that I still have all of my free memory in system. So I assume the bad blocks are located in the very first set of blocks, and not letting me install anything past them.

Can you tell i've been doing my research? ;)
 
Oh and I should mention, that after I ran that command to check for bad blocks, it filled up my system partition and I now only have 67mb's free. Hmm. Do you guys think doing a cat zero command on the system would clear it out at all?
 
HaTrEd360 said:
22?
Click to expand...

correct. mmcblk0p22=system

entering cat /proc/emmc yields the following in snapdragon 3 powered htc devices:

Code: 
shell@android:/ # [COLOR="Red"]cat /proc/emmc[/COLOR]
cat /proc/emmc
dev:        size     erasesize name
mmcblk0p32: 000ffa00 00000200 "misc"
mmcblk0p21: 00fffc00 00000200 "recovery"
mmcblk0p20: 01000000 00000200 "boot"
mmcblk0p22: 31fffc00 00000200 "system"
mmcblk0p24: 077f5c00 00000200 "cache"
mmcblk0p23: 4aabc400 00000200 "userdata"
mmcblk0p28: 01400000 00000200 "devlog"
mmcblk0p30: 00040000 00000200 "pdata"
mmcblk0p25: 00008000 00000200 "extra"
mmcblk0p17: 02800000 00000200 "radio"
mmcblk0p19: 01000000 00000200 "adsp"
mmcblk0p18: 007ffa00 00000200 "radio_config"
mmcblk0p26: 00400000 00000200 "modem_st1"
mmcblk0p27: 00400000 00000200 "modem_st2"
shell@android:/ #
 
Then why would running the commands I ran earlier fill up the system and not the data partition like it should? On this page if you scroll down you can see that mmcblk0p23 is system but i'm confused, lol. I tried running cat /dev/zero on the system partition I thought was 23 and it deleted it so in recovery after I rebooted to it it went into safe mode and told me that system was not accessible and needed to be formatted. Same thing that happens to cache when you change the hboot. So I format it, and it's the same as before. Every time I format after I run that command to check for bad blocks, it deletes whatever data is put in there. So I'd run the command again and all the bad block errors are back. Strange huh? I'm not worried about Snapdragon 3 powered phones, i'm worried about this phone specifically the Evo V. To my understanding, from that page to the Cyanogenmod official project, said 23 is the block for system and my errors in recovery prove it.

Either way, I am certain I need to remove the partition and redo it.
 
Wow nice work here! Just stumbled across this by total accident, walked right into a Cinderella story.

Great persistence there HaTrEd. :thumbup:
 
HaTrEd360 said:
Then why would running the commands I ran earlier fill up the system and not the data partition like it should? On this page if you scroll down you can see that mmcblk0p23 is system but i'm confused, lol. I tried running cat /dev/zero on the system partition I thought was 23 and it deleted it so in recovery after I rebooted to it it went into safe mode and told me that system was not accessible and needed to be formatted. Same thing that happens to cache when you change the hboot. So I format it, and it's the same as before. Every time I format after I run that command to check for bad blocks, it deletes whatever data is put in there. So I'd run the command again and all the bad block errors are back. Strange huh? I'm not worried about Snapdragon 3 powered phones, i'm worried about this phone specifically the Evo V. To my understanding, from that page to the Cyanogenmod official project, said 23 is the block for system and my errors in recovery prove it.

Either way, I am certain I need to remove the partition and redo it.
Click to expand...

cant answer that for certain,other than the possibility that the layout is different in a cdma device. if thats the case, entering the cat /proc/emmc command in a shell would verify it.

glad you were able to fix it,i didnt think that would have worked but im happy to have been wrong :D

if you still have access to your cmd window,you might sort thru it and try and gather up what actually worked into a form that may help folks with similar issues in the future.

good jop,your persistance and determiniation definately paid off :cool:
 
adamhos1234 said:
Here is the ruu pg86img
http://db.tt/3zVol

Rename it pg86img
Make sure its the only pg86img.zip on your SD

I know it works
Its helped several folks
Good luck
Click to expand...
It was this EXACT RUU that fixed it. I believe all the other ones I have been linked to were corrupted somehow, because each and every one were different sized and this one was the largest I believe. But I have confirmed that I tried about 4 other RUU's and none of them worked except this one.
 
HaTrEd360 said:
It was this EXACT RUU that fixed it. I believe all the other ones I have been linked to were corrupted somehow, because each and every one were different sized and this one was the largest I believe. But I have confirmed that I tried about 4 other RUU's and none of them worked except this one.
Click to expand...

well,i dont think there was anything special about the ruu that you used. what fixed your prollem was deleting out all the memory blocks(wich included the bad ones) and allowing the phone to rewrite them when the ruu flashed. after you deleted p23,you could prolly have run any ruu to get back to a working device... the likelyhood of getting several corrupt files or downloads is pretty slim.

for S&Gs,i tried checking a few partitions,then deleting them on a semi-functional amaze that i have. tho it didnt fix the issue in my case,it did find several bad blocks in /system(leaving me hopeful for a few minutes :mad: ;) ). after zeroing out system,boot,and userdata,my phone would not boot to anything other than the bootloader :eek: i didnt have partition hangs when running ruus prior,and didnt have them when i ran the ruu after. the ruu flashed just fine,and the phone booted up just fine. neat :p

in the process of fixing your own device,youce added something new to our aresnal to try in extreme cases :cool: so your persistance may have helped not only you,but several others in the future as well! ill have to dig back to some of me "couldnt rescue" threads and see if this may help there as well.

when you erased p23,were you left with an "error: cant write,device out of room" or similar error? i was going to paste tht exact output,but when i ran the ruu,it pushed all the hcecking/erase commands out of range of the cmd window :mad: im also interested in seeing your cat /proc/emmc so we can verify what p23 is on your device.

thanks again for your efforts and persistance,and im glad you got it working. :)
 
I went back to PAC Rom and now the problem is happening again, all I did just now was reboot to make a backup of PAC Rom to have a restore point if all my shit goes wrong and now it won't boot back up and it even froze on the boot animation and completely shut the phone off. Something is seriously wrong with PAC Rom and my phone...
 
I just reactivated it yesterday god damnet I hate this phone lol. I guess I can try to RUU again and redo everything ughhh. I'm done with PAC Rom that pisses me off. I love that ROM but if it destroys my phone then hell to the no lol.
 
No I can. I can access all of that. I went and cleared dalvik and cache and it booted, then it completely shut off a minute later after freezing and did a full reboot. Now it booted again, and we'll see what happens I guess. I even have it underclocked to 1.2 ghz on ondemand governor on noop scheduler. I'm gonna go back to cfq.
 
Annnnddd now it seems to be fine... Glitchy as F***! This is kind of scary xD But thanks for being so available to help guys :]
 
C:\android-sdk\platform-tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # e2fsck -c /dev/block/mmcblk0p23
e2fsck -c /dev/block/mmcblk0p23
e2fsck 1.41.6 (30-May-2009)
/dev/block/mmcblk0p23: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/block/mmcblk0p23: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p23: 11/51296 files (0.0% non-contiguous), 6429/204799 blocks

So... Haha it happened again. I'm stuck to having a corrupted partition again and this above is what I got using that one command. And here is a log of cat proc/emmc for Prinny. :)

~ # cat proc/emmc
cat proc/emmc
dev: size erasesize name
mmcblk0p34: 000ffa00 00000200 "misc"
mmcblk0p22: 00fffc00 00000200 "recovery"
mmcblk0p21: 01000000 00000200 "boot"
mmcblk0p23: 31fffc00 00000200 "system"
mmcblk0p32: 00140200 00000200 "local"
mmcblk0p25: 06ebde00 00000200 "cache"
mmcblk0p24: 4aabc400 00000200 "userdata"
mmcblk0p28: 01400000 00000200 "devlog"
mmcblk0p30: 00040000 00000200 "pdata"
mmcblk0p18: 02800000 00000200 "radio"
mmcblk0p19: 007ffa00 00000200 "radio_config
mmcblk0p26: 00400000 00000200 "modem_st1"
mmcblk0p27: 00400000 00000200 "modem_st2"
mmcblk0p8: 00c00200 00000200 "wimax"
mmcblk0p33: 007ffa00 00000200 "udata_wimax"
 
You must log in or register to reply here.
Back
Top Bottom