Database Info

Problems Getting Clockwork To Run - Android System Recovery Overriding

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"
}

Need help installing rom into bricked nexus s

Hello guys, right now my nexus s is acting up on me. Right now I have matrix rom and when trying to turn on it gets stuck on the booting animation forever. I tried mounting the sd card adding a few roms even the same one and the original gingerbread one and the system does not allow me to flash it trhu clockworkmod. This is what comes up
{
"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 any of you know what this means.?

juan_carlos__007 said:
Hello guys, right now my nexus s is acting up on me. Right now I have matrix rom and when trying to turn on it gets stuck on the booting animation forever. I tried mounting the sd card adding a few roms even the same one and the original gingerbread one and the system does not allow me to flash it trhu clockworkmod. This is what comes up
. Do any of you know what this means.?
Click to expand...
Click to collapse
The picture isnt showing....
But ur recovery may need to be updated.
Can u flash one of ur backups?
If so, boot up and update ur recovery.
Then just make sure u have correct ROM version for ur phone.
I hope that helps.
Vs Nexus S4G using tapatalk2

vidaljs said:
The picture isnt showing....
But ur recovery may need to be updated.
Can u flash one of ur backups?
If so, boot up and update ur recovery.
Then just make sure u have correct ROM version for ur phone.
I hope that helps.
Vs Nexus S4G using tapatalk2
Click to expand...
Click to collapse
There I fixed the picture, but no I cant flash any of my backups because I deleted them for some reason some earlier backup was not working and the second one I delete it by accident. And the roms form my cell I have been getting the right ones from nexusshacks.com and cyanogen website. I was thinking in something more like pushing the rom thru a computers comand prompt thast my next step.

vidaljs said:
The picture isnt showing....
But ur recovery may need to be updated.
Can u flash one of ur backups?
If so, boot up and update ur recovery.
Then just make sure u have correct ROM version for ur phone.
I hope that helps.
Vs Nexus S4G using tapatalk2
Click to expand...
Click to collapse
I found some tutorial in order to push the rom with command prompt but it's not working neither. does any of you know why not or if I'm doing something wrong here the link of the tutorial and at the end I posted whats what the command prompt came up with. http://forum.xda-developers.com/showthread.php?t=1667929

Do you consider updating your recovery and rom?

My next step will be using the odin called tool for restoring everything. I'll let you know how it goes.

[ROM][9/17/13][Flo] - Stock Rooted Android 4.3 - *JSS15R* - Yes, R! - Odex / De-odex

Stock Rooted JSS15R Hot off the presses!
Features
Fully Stock
Pre-Rooted
De-Odex'ed or Odex (Your Choice)
BusyBox
Init.d Support
Adb as Root (Remount)
{
"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"
}
Download HERE
Please Hit Thanks!​

Attached is the new bootloader. Flash it in recovery!
Info
Dont ask me whats changed, Google it!
Dont use mods from prior builds, such as APM, Tablet Mode, etc. You will boot loop!

All files up!

Hot like fire !
Cool, downloading now :victory:

New bootloaders scare me

New boot loader eh? Have they altered it up unto this point?
Sent from my 2014 Nexus 7 using Tapatalk 4.4

Not sure but they did something to the memory...
There is a DDR partition. Never seen that before.
But then again I never looked. I had to pull it straight from the OTA zip file because there is no factory image yet.

how to install it?
wipe?
install zip from sdcard?

Must i flash the new bootloader separately or is it in the rom ?

With the new bootloader is Secure Boot=enabled new or has it always been there.
Sent from my LG-E980 using xda app-developers app

Installed, flashed bootloader first then Rom in recovery and rebooted. No noticeable difference but then again just installed it. We monitor and report back.

Runs fine, thanks.
After the first boot i lost root, but i flashed supersu and now is everything ok.
*** [email protected] ***

Mayday_XL said:
Runs fine, thanks.
After the first boot i lost root, but i flashed supersu and now is everything ok.
*** [email protected] ***
Click to expand...
Click to collapse
Strange, had no problem with root on my install. Nice thing about the nexus is that a simple reflash of supersu and voila, rooted.

Had no problems with the bootloader or the deodexed rom. Can't wait for the changelog!!

Thanks a lot, no problems at all, rooted and everything.
Ed: do you know if latest franco kernell will work on it

bokoy said:
Thanks a lot, no problems at all, rooted and everything.
Ed: do you know if latest franco kernell will work on it
Click to expand...
Click to collapse
It works fine.

Yep it works, I even installed ElementalX 1.4 kernal, it did blackout after hitting finish but a hard reboot got it back on.

Since I don't see any news about what this update does or anything I will figure it is not super important and just wait for it to hit Clean Rom

I didn't have much problem with the multitouch but it seems improved. I guess is the main reason for this update.

Is it recommended to flash bootloader and ROM in separate recovery sessions with reboot in between or is it ok to flash in the same session?

twrp - can't install this package on top of incompatible data

i have followed all the steps using NRT to unlock boot-loader and root the phone.
Installed TWRT manager and flashed the recovery.
Now i am trying to flash CM12 for the first time and stuck with error message "can't install this package on top of incompatible data" during flashing .
downloaded the following flash zip from CM website: cm-12.1-20150901-SNAPSHOT-YOG4PAO237-hammerhead.zip (281.77 MB)
Can any one help me what needs to be done to proceed further.

i didnt wipe the data before. Now its working and closing the thread

I wiped everything on my phone via TWRP. Still getting this error!

This topic is old but in case someone else gets here I got a solution - Change /data partition filesystem to ext4 or other supported by ROM

mesaj said:
This topic is old but in case someone else gets here I got a solution - Change /data partition filesystem to ext4 or other supported by ROM
Click to expand...
Click to collapse
How did you do that?

dsarcinelli said:
How did you do that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-4/help/guide-detailed-f2fs-manual-format-guide-t3264185
This guide might help, you do it in TWRP by going to Format > Advanced > select partition > Change filesystem > Ext4

Wiping data worked for me
2sumanth said:
i didnt wipe the data before. Now its working and closing the thread
Click to expand...
Click to collapse
In twrp, I had to fumble around to find advance wipe to clear data but worked like charm after that.
Thank you!

xiaomi note 4g dior
Let me tell my story,
My friend gave me an old xiaomi note 4g which was stuck at the MI icon on boot,
Luckily the phone did not lock boot-loader
So I use xiaomi flash rom to flash global room , it worked after i tried sometimes.
Then I booted to the phone, and other problem came, the phone was linked with an Mi Account , and my friend forgot everything about it
not email, no phone number
I did a search and they said the only way to bypass the MiAccount is using a Resurrection ROM or balallala
so I ended up with using
1. fastboot to install twrp
2. open twrp --> open adb sideload mode.
3. Open window command line and install Resurrection ROM though adb sideload
While installing rom though adb slideload , i got the same issue with topic
SO i cleared data and tried again,
IT WORKED , NO MORE ****ING MiAccount
THANK a lot
:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:

{
"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
Playing with my wife's Nexus 5, bootloader unlocked, rooted, and latest TWRP installed but when trying to flash from android 6.0.1 to Lineage, I'm getting an error 7 image shown I hope.....
Is this just because I haven't wiped the data first ? (I'm fairly sure but...)
I dont dare try 'cause if it's not that she'll kill me, so would like to be sure before I wipe all her data..
Thanks
Update, it was that I just wiped all except the SD and flashed, all is just great

Soft brick one sv

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"
}