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"
}
Related
Disclaimer: Searching for this brings up far too many results to be useful.
Just attempted a Root of 3.2 using http://forum.xda-developers.com/showthread.php?t=1185104
I'd post this there, but don't have access rights.
Anyways, process went well, rebooted, but once the initial splash screen has cleared, this happens:
{
"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 tried using the same tool to restore to stock, but nothing doing at the moment. Help would be appreciated.
EDIT: Annnnnd I've fixed it. This is why I never post. Carry on.
How did you fix it? I ended up bootlooping after flashing the WW HC3.2 boot image. I assume you also flashed the WW version?
Greetz,
speedstra
i had the same thing happening to mine when i first rooted to 1.4 prime. however now ive upgraded the rom to 1.6 and so far no artifacts
I had the same problem. I found it was able to fix it by downloading the latest version of the batch script root method zip file and using it to flash my tablet. You need to MAKE SURE you are using the latest version v5 beta5 because the older version had a problem flashing HC3.2 and gave me that error.
here's the link to the forum entry
http://forum.xda-developers.com/showthread.php?t=1185104
here's the link to v5 beta5
http://www.mediafire.com/?59rzqn61jl445lh
Speedstra said:
How did you fix it? I ended up bootlooping after flashing the WW HC3.2 boot image. I assume you also flashed the WW version?
Greetz,
speedstra
Click to expand...
Click to collapse
I had actually attempted to flash the 3.1 image instead of the 3.2 image. Thus the reason for edit on the original post.
The latest version of the tool should restore it.
EDIT: Annnnnd I've fixed it. This is why I never post. Carry on.
Click to expand...
Click to collapse
Please stop using the incorrect term for 'brick.' IT IS NOT A BRICK when your device turns on. Just stop, please.
Just had this same issue, got the same screen - blood pressure went through the roof, had to go water the plants to calm down
I was following this procedure: http://forum.xda-developers.com/showthread.php?p=14760983#post14760983
My mistake was not replacing the boot.img in the root folder with the newer 8659 .img file (linked at the top of the post, but not called out in the otherwise very detailed instructions).
HOWEVER: I did have an issue in that after flashing the wrong .img and getting the "oh sh!t" screen, I could not get adb to list a connected device, which kind of threw me. I could get it into APX mode by holding down the vol-up and power keys (and paying close attention to the "usb connected" notification sound - hold them down for about 10 seconds, hear the "disconnected" sound, then almost immediately hear the "connected" sound and let them go. The screen should stay dark instead of going to the boot logo) and I could see the driver being used, but "adb devices" returned nothing.
So I just ran root.bat again, as I had nothing to lose - and BOOM! Success!
Followed the rest of the procedure with no issues. Hope this helps someone!
Cheers
PatMan
Hey guys I need help.
I want to root my Prestigio multipad PMP5080CPRO but I can´t find the Debugg-mode and I can´t find the adb driver.
Could anybody tell me how to root it??
Thanks :laugh::laugh:
Found an excellent thread on ROOTING the PRESTIGIO MULTIPAD 5080 C PRO
HERE:
http://www.slatedroid.com/topic/36909-prestigio-pmp5080c-pro-rooting/
In case the thread is lost in time and space, I will copy and paste parts of it below here:
Original post by user xenonification on slatedroid.com:
***
Okay, here it is:
http://www.mediafire...gxa50m45c15zm5v
Installation instructions:
1)Plug in USB and turn on Mass Storage mode.
2)Unrar update.rar and copy update.img to SD card.
3)Unplug USB, A message should appear on the tablet saying something like "Would you like to update?". Press yes.
4)Phone will reboot and start installing firmware (Make sure you have power cable plugged in just in case).
5)Done
Notes:
-The file is much larger than the firmware file from the website. The reason for this is that when I rebuilt the system.img file, I made the image the max size that it could be.
-This is only for the Prestigio PMP5080c Pro. Do not try this on any other device.
-You lose your warranty by rooting your device (I'm pretty sure you can unroot it and remove all evidence though.)
-If something happens with the firmware (Tablet boot loops or freezes), remember, there is a reset button at the back of the tablet. Pressing the POWER button while holding in the volume down key will put the phone in recovery mode, where you can flash the firmware from here: http://www.prestigio...ad_PMP5080C_PRO
-I am not responsible for anything that happens to your device. Although if you are REALLY unlucky and something does happen, I'll try my best to help you sort it out
Just flashed it on my PMP5080C and it worked perfectly. None of the applications got deleted either. You can test if the root is working by downloading Root checker from android market. Follow the instructions and you'll be A for away
Good luck :clapping:
***
another user, bagy on slatedroid.com comments:
***
I did the same. Except I copied su and Superuser.app directly into the image (you can do that as root from terminal .. and IMHO if you open the file explorer as a root, you can do it that way too). I'm flashing as we speak (new FW 1.0.6). If it's alright, I can post a tutorial (I've done it with Xubuntu in VirtualBox) on how to do it, or just upload the file.
PS: The device just booted, root is enabled! Yay!
***
Confirmed, above method works.
Just in case, here is the rooted 1.03 ROM mirrored.
Link
"Pics or it didn't happen."
{
"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"
}
do you think i can get something like this for 5580c? thanks in advance
Sent from my PMP5580C using xda app-developers app
ki2luminati said:
do you think i can get something like this for 5580c? thanks in advance
Sent from my PMP5580C using xda app-developers app
Click to expand...
Click to collapse
Here is the link for the thread
http://forum.xda-developers.com/showthread.php?t=2360964
You are welcome for more help
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"
}
Hi,
I never saw this problem
My phone is unlocked (since a year more or less) and I can't install TWRP nor CWM. I tried many tutorials such as all the root methods listed on XDA for this smartphone.
{
"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 idea would be really appreciated!
Thanks
There might be a problem with your drivers. You can try uninstalling and reinstalling them. Also, try using fastboot commands manually
Sent from my Mate
unlock again
Thank you. I'd like not to have to relock it as it's already done and rooted. Could you please tell me what drivers to install? I tested many of them (https://i.imgur.com/wBgsezr.png) but it seems I don't have the right ones then.
I'm using Win7 64bits.
Thanks again!
Use adbdriveinstaler and when it's install you can push recovery to add folder and try this command
cd C:/adb
Fastboot flash recovery recovery.img
Change name your twrp or cwm to recovery
Send frome globe
Okay. Here we go
ADB driver installed (https://i.imgur.com/PWrZoHH.png)
Went to flash and... still not allowed.
And in fastboot/rescue mode on my phone it's written PHONE Unlocked.
WTF
BTW, is there any other way to upgrade the phone? Cause every time I go to the software update in the menu i'm told it's up-to-date, but it's not... Android 4.4.2 & EMUI 3.0.
I read about a "local update" but can't find out how to update from the SDcard, I only have OTA.
Bud64 said:
Okay. Here we go
ADB driver installed (https://i.imgur.com/PWrZoHH.png)
Went to flash and... still not allowed.
And in fastboot/rescue mode on my phone it's written PHONE Unlocked.
WTF
BTW, is there any other way to upgrade the phone? Cause every time I go to the software update in the menu i'm told it's up-to-date, but it's not... Android 4.4.2 & EMUI 3.0.
I read about a "local update" but can't find out how to update from the SDcard, I only have OTA.
Click to expand...
Click to collapse
In your screen you have locked bootloader. Unlock againg
Send frome globe
Okay, I sent an email to Huawei, I'll get back in a few days.
Hello guys, so basically you are my last hope since I cannot find a solution for my problem (at least with my level of knowledge).
Lets start from the beginning: I (someone with no experience in this topic) decided to try out a new OS on my old Samsung Galaxy S3 since a lot of apps stopped working on Android 4.3. I tried a tutorial on youtube on how to install a new custom ROM. I installed TWRP (3.5.2_9-0-i9300) and later with the help of TWRP Lineage OS 17.1 (an unoffical version for my type of phone) and everything worked perfect.
I started to download all apps I need and to customise my OS. In the end when everything was set up I decided to do a full backup using TWRP and thats where the problem started. In the development section I checked the function, that when you press the power button you can directly boot your phone into recovery mode. So my phone rebooted and ended up in a constant boot loop where at first the Samsung Galaxy logo appears (first picture) and then TWRP appears (second picture) and this process goes on and on...
{
"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"
}
Sadly there is no way to get into recovery mode since this loop just continues. If tried it many times also with taking out the battery and putting it back in. The only thing I have access to is the download mode.
So my question to you: is there anything I could do in the download mode to solve this problem? I saved the important data before so a full wipe wouldnt be a problem. Maybe I can do something with odin?
I really hope you can give me some ideas to try out. Every help is appreciated. Thanks!
Try reflashing a stock ROM first of all.
Then reflash TWRP. Make a TWRP backup (especially the EFS ! That is a "must-do first and foremost" !) of your working system and progress from there.
And in the future, instead of reinstalling all your apps piecemeal I strongly recommend you use Titanium backup (paid version. The free version is very limited), that is a wise invesment for the small sum it'll cost you
@Snakeforhire reflashing stock ROM worked, thank you so much.
I will take a closer look on Titanium backup. Used it in the past but with root access. On the new Lineage OS I dont have root although it shouldnt be hard to get from what I read.