Hi everyone. Please bear with me I am a complete noob at this stuff.
I have a HTC one sv c525e K2_ul 4.2.2 S-on in Aus with optus (maybe LTE??)
The storage space for apps is tiny so I wanted to root the phone to re-compartment space.
I eventually found and followed the tutorial by qbking77 to unlock the phone and root it. I did well up until entering recovery to root the phone. The twrp image I used didn't work on my phone. I tried several of them with same result. Somewhere along the line I got the bootloop. I don't recall if it was before or after I tried to flash this I think I tried some other kernel that I can't find now.
Anyway I went back to twrp and tried more images. One finally worked to get into recovery. It was- twrp-2.8.6.0-k2_cl.img 10.4M the second listing under HTC One SV Boost USA (k2_cl).
So now I could enter recovery mode I went back to qbking77's tutorial. I found the options and process on my phone was different to his and I had a few errors come up like unable to mount sdcard, storage and some other stuff. As a result I was unable to do a back up and unable to install super user. From there I still got the bootloop.
Although internal sdcard and storage was unable to mount the phone did see the external sd card. So I loaded the super user zip direct from pc to sd card and opened the zip in recovery. Still bootloop.
I was wondering if I managed to unwittingly delete some important ****. So in my brilliance to persevere with screwing with it, I loaded the venom ROM (and some kernel) onto the ext sd card and opened it in recovery. Still several errors came up and I wasn't given any options to pick before flashing. It did say installation was a success at the end. Still got bootloop.
So I am hoping someone might see an obvious f-up that would turn into an easy fix ......... :laugh:
So I've been doing some reading :angel: but I'm no better off. I watched closely what I was doing and I was getting an MD5 error. I tried downloading the zips in firefox so as not to corrupt them but the phone is still coming up with 'missing MD5'.
I'm thinking my only option at this point is to run the RUU as I've seen that suggested a few times to others. Looks like a PITA but I guess it's that or new phone
I don't know when I'll get around to doing it.
Looking into RUU I need the S-off. Since I can't boot the system does anyone know how I can switch the S to off through fastboot or recovery?
So I was too lazy to run the RUU. I again attempted to flash the viper ROM. In recovery it says it was a success but I still get the bootloop. I noticed when I went into recovery something would flash up on the screen but it was too quick for me to read so I took a picture of it. Does anyone know what any of it means?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
Hi All,
I've been reading this forum for a good few days now as I am trying to get my Kyros functioning the way I need it to. However, I've run into a few problems and am not 100% sure as to what to do. Before I go on, I'm not very techy, so I would be very greatful if replies could be as straight forward as possible, without much jargon as that really loses me
First off, we've just managed to install the windows and ADB drives. I'm following all the instructions from here: http://forum.xda-developers.com/showthread.php?t=858952. That took some hacks our side, but is now working.
I'm pretty stuck on the clockwork reboot though. Again, followed the instructions from the link above. When it initially rebooted, it went straight into the Android System Recovery mode (the robot with the triangle opening screen.) I've tried it over and over, following the directions exactly as explained in the link, but all I'm getting is the generic Androis system recov.
The Recovery zip file is on my SD card. Do I need to unzip it to get the recovery.img to show? Is that something that I'm doing wrong? I also updated the OS (I guess) from the coby site before I started working on these other changes.
So basically, this is the issue right now. Trying to get the clockwork to run and all I'm getting is the android system...and that's when it doesn't just reboot back to the home screen directly.
Any advice would be great. Thanks
And out of the blue, after an hour of angry TV watching, it's now worked. I can't tell you what I did differently as I followed all the same steps as before. Must just have been lucky I guess.
I am having the same issue, and i tried to unzip the update.zip but i boot back to the recovery mode, can someone assist me with this, i have a galaxy s (Vibrant).
thanks
Try going to your sd folder and delete the clockwork recovery folder then uninstall rom manager and redownload it from the market after it installs open up rom manager and click on flash clockworkmod recovery and let it download the update.zip file and your done
Sent from my SGH-T959 using XDA App
Oh yeah after all those steps and you still get back into the stock recovery system click on reinstall package and it should boot into cwm I hope that helps
Sent from my SGH-T959 using XDA App
ASR
baalcat said:
Trying to get the clockwork to run and all I'm getting is the android system
Click to expand...
Click to collapse
like this ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've been stuck in a boot loop on one of my G-Tabs for about 4 days now. Been trying every fix I can find to no avail so far. I have the Viewsonic to G-Tablet boot loop. I keep noticing people reffering to using NVFlash with the Img9 fix to add in ClockWord mod. Many said to do that flash then to wipe the data, which is where the problem lies. I get this error everytime I try:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any ideas?
Repartition 2048 and 0.
Hello KJ and thanks for replying, I have seen you offer help to alot of people so thanks for dropping by here too.
I have tried that as well and it hasn't done anything. I don't know if it is the order in which I am doing things or what on this tab. My other one works like a dream but it was done before the 4539 (I think that's right) update came out.
I have done the NV Flash and added CWM via Ext SD and then partitioned and that was a no go. I also tried doing Roebeet's example of doing NVFlash and changing te Img9 file as well with a repart and that didn't work either.
I also tried this "fix" and even it didn't work.
http://forum.xda-developers.com/showthread.php?t=974422
I'm not giving up because from all I am reading, these things seem immpossible to fully brick. I also feel pretty safe to say that it is my fault and that maybe I don't have the correct order for doing the entire process but I have tried until I turned blue in the face before giving up and going to bed.
Well... what your tablet is having trouble mounting is the partitions that you should be creating with the repartitioning. /dev/blk/mmcblk3 is the internal memory. Are you familiar with ADB?
No not at all. I googled during this and saw Android Debug Manager. Something with that I should try? I definitely don't claim to be the smartest guy on the block but at the same time I pick up this stuff well and am not really scared to try something if you have an idea.
Congrats, man. I think you're the first to truly brick his gtab.
tunez23 said:
No not at all. I googled during this and saw Android Debug Manager. Something with that I should try? I definitely don't claim to be the smartest guy on the block but at the same time I pick up this stuff well and am not really scared to try something if you have an idea.
Click to expand...
Click to collapse
Unfortunately, I'm not a good enough teacher (I lack the proper patience) to get someone going with ADB from scratch. Especially since my development environment is somewhat unusual so I often have no frame of reference to assist in setting up the tools. So, if you're up to it, you need to do one of two things. Either get ADB installed and running on your computer or get a rooted ROM and a terminal emulator on the device that we need to work on.
Your situation is somewhat different from the others in that you can actually get CWM installed and get into recovery. I still think that perhaps some combination of partitioning, data wipe and fix permissions should be working for you. What I would do in your case is:
1) Data wipe one more time (perhaps use: http://forum.xda-developers.com/showthread.php?t=1030915)
2) Reboot into CWM recovery and repartition
3) nvflash the stock ROM again (without CWM)
4) Factory reset from the ROM settings
If that fails then research setting up ADB for your computer and we'll discuss some diagnostics you can run from that.
Thanks KJ, I will try those when I get home this evening.
Hello guys!
It been like 3 days i've been trying to install a rom on my HTC one x, any rom, just to make it boot up again.
Here's some of what i've done:
Installed a custom recovery (TWRP/CWR)
Copied the rom file into the phone's memory and booted up the phone in recovery mode and tried to install the roms, every single rom failed to install yelling different errors, one that has something to do with the bootloader and after searching the problem here and there it lead me to updating the karnel and i tried million times with no luck
i also tried different versions of recovery modes thinking it was the reason why the installation didn't go through; it all was in vain!
here's a screenshot of the info i get with the fastboot getvar all command.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm really tired guys and started to lose hope :crying: Please Help!
Danaxus said:
Hello guys!
It been like 3 days i've been trying to install a rom on my HTC one x, any rom, just to make it boot up again.
Here's some of what i've done:
Installed a custom recovery (TWRP/CWR)
Copied the rom file into the phone's memory and booted up the phone in recovery mode and tried to install the roms, every single rom failed to install yelling different errors, one that has something to do with the bootloader and after searching the problem here and there it lead me to updating the karnel and i tried million times with no luck
i also tried different versions of recovery modes thinking it was the reason why the installation didn't go through; it all was in vain!
here's a screenshot of the info i get with the fastboot getvar all command.
I'm really tired guys and started to lose hope :crying: Please Help!
Click to expand...
Click to collapse
Hello
Your device is a htc one x "evita", this forum is for htc one x "endeavoru".
You cant install rom for endeavoru on evita device.
Thank you so much for your reply! at least i know what's the problem now.
I'm downloading some "Evita" compatible roms, hopefully it will work this time
Hey guys! i have an issue here. can anyone help me solve this problem.
before i started getting this error i had, they were working well
- AOKP 4.4.4 custom rom
- Philz touch 6.0 Recovery.
from few days i started getting this error, see image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried to flash stock firmware, i downloaded two firmware of INU region (India)
everytime i get the following error on odin,
(Above pic for reference only. im using odin v3.09 and latest)
I tried flashing with PIT files, it didnt work.
I tried flashing TWRP, CWM it flashes recovery but when i go to recovery then still philz is there.
I searched on many forums and Googled, and i came to know that my /data and /sdcard is corrupted. but i can access the content /sdcard from recovery and i can view my files.
I tried flashing other custom rom. It flashes them without any error but when i reboot my Tab its not flashed. its same.
What to do please help me.
Ok so after doing so mush research on this on xda, gsm-hosting, google, etc....
i came to a conclusion that the emmc is corrupted or right protected (Means It has become read only). which is why we are unable to flash through odin or through recovery. even if the flash is successful then after reboot the TAB returns to the earlier state i.e same rom, bootloop and recovery.
so there are three way you can fix it:
1. change motherboard, which is very costly. on ebay it was 13k (India). dont know about local shops or service center. but im sure it will be more or less same.
2. Change emmc. ask the repair guy to change the buggy emmc to a new one. buy the emmc from alibaba online store or other online stores if you cant find it offline.
3. You can get back the same tab to work by directly flashing the stock rom directly to emmc. This process involves soldering the pins of the tab and flashing directly on to the chip using a box called ATF (Advance turbo flasher). This process is little advance, one can do it if you know what pins to solder (You can get the idea from youtube & gsm hosting), but buying atf box would be costly. costlier than the emmc replacement. now if you want to experiment and learn you can go buy a atf and revive your dead tab (it will be called The walking dead. ).
:)
so i am replying to my own thread so that if any body is comes searching for the same gets to know what happened and what to do next.
BTW Android_Andi has done some great research on this he tried every possible thing but unfortunately it didnt work. Thanks to him for his time and effort.
and if anybody figures out how to fix it without using atf box please do post and let me know. because im keeping my dead tab with me and if someone knows any alternate way i can fix mine too. who knows anything can happen.
update errors... 'This package is for "rk3368" devices; this is a "PX5" '
Trying to update my unit from Android 8 to Android 9. Tried the simple and direct update but it failed. But, I didn't get the black screen. So, I made the bootable sdcard and tried that way. SD card runs, does it's thing, says it was successful and tells me to remove it to reboot. When I do, it goes to a black screen and nothing else. Even after leaving it sit for 30min. That SD flash process was waaaay fast for it to have actually flashed the image.
Now, I can't get the unit to do anything without that SD card.
I have found that if I pop the SDcard out between the logo screen and when the flash process starts it errors and takes me to recovery. From there, I've tried many different roms. Hal9k versions, Malaysk versions, stock 8.0, ota 9.0 for my device, and even a 6.1.1 version.
After going to "Installing update..." most give me an error "Warning: No file_contextsE3004: This package is for "rk3368" devices; this is a "px5"" then a couple of other errors before a (Status 7) Installation aborted.
All the roms that didn't do that have some kind of signature error. Likely need to redownload but haven't tried yet.
Not really sure what to try from here...
The device had the MCU of MTCE_GS_V3.01_3 when I started. I was able to update it to MTCE_GS_V3.40
The original build number was px5-userdebug 8.0.0 OPR5.170623.007 eng.hct.201812222.104950 test-keys though I suspect that doesn't really matter.
Couple photo screenshots.
First one is the error.
Second is what it says after the bootable sdcard runs. I see nothing there about installing the update.zip
Last is what I get sometimes if I eject the ad card too soon trying to get to the recovery menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Redmi Note 7 using Tapatalk
And... I fixed it.
Didn't find anything for this error using the search here. Did a search on google and it linked me to a post on this thread https://forum.xda-developers.com/an...5-mtcd-e-head-unit-discussion-thread-t3929597
A reply told the user having the same problem to follow the SD card instructions at the beginning of the thread.
Instructions were the same as what I already followed but the file linked in the first post is different.
So, went through the process again. Installed that recovery and then was able to actually flash Android 9 onto mine.
Now for the fun part of getting everything configured and decide if this custom rom is the rom for me, if I go with the other one, or if I go to a more stock one. Least I can listen to the radio again...