Hi Guys,
I have installed paranoid android cm10 last night. I was good but gmail was force closing, so I tried to install latest version thru goo manager app. I have installed recovery which it told me to get it but once i reboot my phone into recovery its no more moving a head. all I see is teamwin wallpaper and system reboots... any help is greatly appreciated.
Thanks
/bin/ said:
Hi Guys,
I have installed paranoid android cm10 last night. I was good but gmail was force closing, so I tried to install latest version thru goo manager app. I have installed recovery which it told me to get it but once i reboot my phone into recovery its no more moving a head. all I see is teamwin wallpaper and system reboots... any help is greatly appreciated.
Thanks
Click to expand...
Click to collapse
It probably didn't flash a kexec recovery. Just boot into recovery and flash a non kexec ROM ...hopefully you have one sitting on your SD card. If not your have to get one there or dd a kexec recovery with adb and reboot with the ROM you currently have installed
I guess he can't even get into recovery, as he said all he sees is wallpaper. He used TWRP recovery, which is NOT Kexec enabled. In order to flash CM, you needed to flash CWM 6.0.1.0. Now, basically your only choice is to either adb the cwm recovery, or just reflash stock using odin (easier option), flash cwm, then reinstall CM.
Vorfidus said:
I guess he can't even get into recovery, as he said all he sees is wallpaper. He used TWRP recovery, which is NOT Kexec enabled. In order to flash CM, you needed to flash CWM 6.0.1.0. Now, basically your only choice is to either adb the cwm recovery, or just reflash stock using odin (easier option), flash cwm, then reinstall CM.
Click to expand...
Click to collapse
It's odd his recovery won't open I wonder if goo flashed the incorrect version.
Related
not sure if this is what everyone is already doing, but I was trying to figure out how it might work
stock ota 2.3.1 os
fastboot oem unlock
flashed clockworkmod recovery
boot into recovery nandroid backup stock non-rooted os (just in case )
flash su-2.3.6.1....zip
nandroid backup again
take the boot.img from this nandroid backup and fastboot flash boot
onicrom said:
not sure if this is what everyone is already doing, but I was trying to figure out how it might work
stock ota 2.3.1 os
fastboot oem unlock
flashed clockworkmod recovery
boot into recovery nandroid backup stock non-rooted os (just in case )
flash su-2.3.6.1....zip
nandroid backup again
take the boot.img from this nandroid backup and fastboot flash boot
Click to expand...
Click to collapse
No.
10chars
fastboot oem unlock
flash cwm recovery
nandroid backup
mount /system
flash the su-2361 zip
boot up
rename/delete /etc/recovery.sh (or whatever the exact file is)
download rom manager, flash latest cwm (as of right now it's 3.0.0.5)
reboot to recovery to make sure cwm loads properly and updated.
done.
nxt said:
download rom manager, flash latest cwm (as of right now it's 3.0.0.5)
Click to expand...
Click to collapse
Caution with the 3.0.0.5 latest CWM. I can't get into CWM recovery with that one; I had to downgrade back to 3.0.0.0. The phone just stalls at the Google screen on boot up with it.
Another person's reported the issue in another thread here. I emailed koush, but no response yet.
@nxt, you've tested 3.0.0.5 and it works as expected?
distortedloop said:
Caution with the 3.0.0.5 latest CWM. I can't get into CWM recovery with that one; I had to downgrade back to 3.0.0.0. The phone just stalls at the Google screen on boot up with it.
Another person's reported the issue in another thread here. I emailed koush, but no response yet.
@nxt, you've tested 3.0.0.5 and it works as expected?
Click to expand...
Click to collapse
Not nxt, but I haven't had any issues with 3.0.0.5. Flashing, restoring, or anything at all.
unremarked said:
Not nxt, but I haven't had any issues with 3.0.0.5. Flashing, restoring, or anything at all.
Click to expand...
Click to collapse
Interesting. I wonder what the quirk is on mine and the other guy's. I haven't tried flashing it from fastboot, but selecting reboot to recovery from within ROM Mgr will not load recovery, it just hangs. No issues with 3.0.0.0.
distortedloop said:
Interesting. I wonder what the quirk is on mine and the other guy's. I haven't tried flashing it from fastboot, but selecting reboot to recovery from within ROM Mgr will not load recovery, it just hangs. No issues with 3.0.0.0.
Click to expand...
Click to collapse
Works fine for me normally. I personally don't use rom Manager to do anything though. I manually reboot into recovery and do recovery stuff. I have not tried selecting reboot to recovery via ROM Manager. That might be the issue.
Im trying to flash the Clockwork Recovery mod to my sidekick but every time I boot in recovery I keep getting the stock recovery screen. First of all I rooted my phone using the latest version of SuperOneclick Root. Once the phone was rooted I installed both root explorer and rom manager.
I downloaded the modified binary recovery file and replaced it in system/bin using Root Explorer. I used Rom manager to flash the CWM and it supposedly intalled it (it says version 4.0.0.2). I tried to reboot on recovery but it doesnt boot the CWM recovery screen. I the tried donwloading the CWM and placing the update.zip file in the root of my SD card. I then rebooted into recovery and selecte reintall packages and i get the following:
E: signature verification failed.. installation aborted?
Im guessing its the binary recovery file that's causing the problem but I've tried replacing the file again and it wont work. Anyway, does anyone have any idea whats going on and how I can successfully install the clockwork recovery mod??
Yes that would say that it isn't using the correct modded recovery binary. use my modded oneclickroot script to push the correct recovery and update, and it should work.
http://forum.xda-developers.com/showpost.php?p=15831175&postcount=124
Thank you so much it worked like a charm!! One question, every time I boot in recovery now, it boots in the stock recovery. In order to boot CWM i have to select reinstall packages every time is this normal??
Currently that's normal. I've got the same thing on mine.
sly_fox said:
Thank you so much it worked like a charm!! One question, every time I boot in recovery now, it boots in the stock recovery. In order to boot CWM i have to select reinstall packages every time is this normal??
Click to expand...
Click to collapse
Yes that CWM is a fake flash and doesn't actually replace your stock recovery so you would have to reinstall packages everytime, unless you flash bali kernel which has the red CWM that replaces the stock recovery when you boot into recovery mode
Sent from my SGH-T839 using XDA App
EDIT: sniped by ayoteddy.
That is normal, as that script uses the "fake flash" instead of having CWM built into the kernel.
A fake flash technique uses a modded recovery binary that doesn't check for signature verification, allowing us to boot into CWM from a stock looking recovery, even on a stock kernel.
In order to have recovery boot straight to CWM, you need to have it built into the kernel, which currently only exists on the Bali kernel (as there's no need to build it for another kernel).
Hi all,
I am stuck in a bootloop and I do not know how to get out.
Phone is on SlimROM 2.8 (i9000), wanted to install GAPPS.zip via CWM, for whatever reasons I ended up in "install via sideload" instead of "install ZIP",
powered off phone while it was prompting s.th. about "adb install" (forgot the exact wording)
Now phone is booting, showing Semaphore image for a while and reboots automatically. CWM (VolUP+Home+Power) not available anymore.
I tried to flash Semaphore_JB_2.4.4s.tar via ODIN and phone continued with ROM boot. The next reboot -> same things as described above. The "trick" with kernel flash unfortunately worked only ONCE. Re-flashing kernel with ODIN has no effect (anymore?) ???
What is the best way to continue, if possible without data loss? Install new CWM? I expected some kernel settings to be responsible for the bootloop, hence the kernel flash.
Help is highly appreciated. Thanks in advance.
Install recovery manually through fastboot. You can use Android Flash Recovery if you're not comfortable with using fastboot yourself.
post-mortem said:
Install recovery manually through fastboot. You can use Android Flash Recovery if you're not comfortable with using fastboot yourself.
Click to expand...
Click to collapse
Well... am not sure if fastboot is available for I9000 at all (after some search in this forum)? How do I get into fastboot mode with this phone?
Anyhow, thanks for your reply. Solved my problem by flashing Devil kernel via ODIN, then reflashing SlimBean2.8. System work again as before.:good:
BTW, Devil Kernel for SlimBean produced some strange errors for me: no audio, some FCs, no camera. Was just good to get back to recovery.
Hey guys.
I just got a very nice condition used TF700T. I am trying to get recovery to install so I can flash a rom. I used the Transformer Toolkit to unlock it, which worked, it says device unlocked when booting.
But I absolutely cannot get it to Root, or flash recovery. If I try using debugfs root generic 2.3 it fails to write everything. If I try to flash any recovery with the toolkit it downloads and says flashing but just sits at about 25%, it boots my device into the screen that says usb fastboot mode with the three icons that say RCK Android and factory wipe. If I click the RCK it says rebooting and then goes to android mascot installing icon, but then the one with an X and error appears. What on earth am I doing wrong?
Is it the latest 4.2 update locking me out? Can I downgrade? I just can't get anything to root or flash recovery no matter what I do. I feel a little defeated being a long time member and 3 phone habitual rom flasher :crying:\
Any ideas what i'm missing?
benjmiester said:
Hey guys.
I just got a very nice condition used TF700T. I am trying to get recovery to install so I can flash a rom. I used the Transformer Toolkit to unlock it, which worked, it says device unlocked when booting.
But I absolutely cannot get it to Root, or flash recovery. If I try using debugfs root generic 2.3 it fails to write everything. If I try to flash any recovery with the toolkit it downloads and says flashing but just sits at about 25%, it boots my device into the screen that says usb fastboot mode with the three icons that say RCK Android and factory wipe. If I click the RCK it says rebooting and then goes to android mascot installing icon, but then the one with an X and error appears. What on earth am I doing wrong?
Is it the latest 4.2 update locking me out? Can I downgrade? I just can't get anything to root or flash recovery no matter what I do. I feel a little defeated being a long time member and 3 phone habitual rom flasher :crying:\
Any ideas what i'm missing?
Click to expand...
Click to collapse
What custom recovery are you installing? You may want to try with fastboot or adb method to flash your custom recovery which doesn't require rooted device, good luck....
LetMeKnow said:
What custom recovery are you installing? You may want to try with fastboot or adb method to flash your custom recovery which doesn't require rooted device, good luck....
Click to expand...
Click to collapse
Well I tried TWRP 2.7.1.1 I believe and also CWM , and Phil's custom touch CWM that all three are options to flash with the all in one ADB Toolkit app via USB from windows (http://forum.xda-developers.com/showthread.php?t=2094746)
How do I do the Fastboot method? I read about that, but have no idea how the process goes. I'm ok with skipping root and going straight to recovery and a rom because I can just flash superuser after if the rom isn't rooted already.
benjmiester said:
Well I tried TWRP 2.7.1.1 I believe and also CWM , and Phil's custom touch CWM that all three are options to flash with the all in one ADB Toolkit app via USB from windows (http://forum.xda-developers.com/showthread.php?t=2094746)
How do I do the Fastboot method? I read about that, but have no idea how the process goes. I'm ok with skipping root and going straight to recovery and a rom because I can just flash superuser after if the rom isn't rooted already.
Click to expand...
Click to collapse
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
benjmiester said:
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
Click to expand...
Click to collapse
Unlocked bootloader is allowed you to install the custom recovery so you can install the custom ROM, I believed..... You can check this guide out to see if you can setup your fastboot/adb. It is very easy to follow for the beginners, good luck....:fingers-crossed:
http://forum.xda-developers.com/showthread.php?t=2688891
benjmiester said:
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
Click to expand...
Click to collapse
Once you unlocked the bootloader you can flash a custom recovery and after that - the sky's the limit.
Flashify works great, and it is a wonderful tool as long as you're able to boot into Android.
My problem with Flashify and Goomanager and TwrpManger is that it saves users from setting up a proper ADB/fastboot connection from PC to tablet.
As long as you can boot Android, these apps are great. But what if you can't? Once the tablet doesn't boot it's so much harder (and often too late) to get the correct drivers installed for ADB and fastboot.
So if you flash your recovery with any of those apps still make sure you have access with ADB and fastboot from your PC.
You will regret it if you don't - I (almost) guarantee it.
That's an excellent point. Thanks. I did actually get the Fastboot method to work. The problem was that I kept clicking into RCK recovery when I ws supposed to just leave it on that screen to push twrp instead. I got recover and just got done doing a backup. I'm about the flash my first rom (http://forum.xda-developers.com/showthread.php?t=2672751). Do we need to do factory reset / wipe data/system etc? The instructions on the ROM post say to just flash it from twrp so I'm guessing it has a built in wipe feature during install?
benjmiester said:
That's an excellent point. Thanks. I did actually get the Fastboot method to work. The problem was that I kept clicking into RCK recovery when I ws supposed to just leave it on that screen to push twrp instead. I got recover and just got done doing a backup. I'm about the flash my first rom (http://forum.xda-developers.com/showthread.php?t=2672751). Do we need to do factory reset / wipe data/system etc? The instructions on the ROM post say to just flash it from twrp so I'm guessing it has a built in wipe feature during install?
Click to expand...
Click to collapse
The instructions in the OP actually say that you have to do a full wipe (Factory Wipe) in TWRP coming from a different rom base. Which would be you unless you had a version of CROMBi-KK installed prior to this.
It's the default selection under the Wipe menu in TWRP. Just do that and then flash the rom and your ok.
Do not use the Factory Reset option from Settings or the Wipe Data option from the BL menu! Do this in TWRP only!
Cool thanks. I figured so because that's the norm with roms on all my phones. Thanks a lot for the help guys. So happy to be get KK running on my new toy!
Just wanted to update. KK 4.4.3 rom flashed and booted in. It's much nicer. The stock was a little laggy, and KK breathed a lot of new life into my ancient single core 1.0 ghz Galaxy S that I use as a music player so I figured it would help make the tab real nice and snappy too. Gotta go now, much fun to be had!!
I'm screwed. I attempted to install an updated TWRP, so i selected that option in ROM Toolbox Pro. Everything installed correctly (TWRP 2.7??). I decide let me see if TWRP installer will replace that with the updated 2.8.5. I run TWRP installer and it installs correctly. My assumption was that the TWRP installer would overwrite the ROM Toolbox version. Well, i reboot into the 2.8.5 recover (like it suggested) and i hit Reboot and then it reboots into 2.7. From there it thinks there is no OS installed. Rebooting from there just reboots me back in 2.7 recovery. I can get into Fastboot, and then back in 2.8.5 recovery. I flashed a new ROM, but that didn't fix it. I attempted to flash an RUU but i can't seem to get that working either. Am I completely screwed and should i call insurance on it?
Help me XDA, you're my only hope.
theoden144 said:
I'm screwed. I attempted to install an updated TWRP, so i selected that option in ROM Toolbox Pro. Everything installed correctly (TWRP 2.7??). I decide let me see if TWRP installer will replace that with the updated 2.8.5. I run TWRP installer and it installs correctly. My assumption was that the TWRP installer would overwrite the ROM Toolbox version. Well, i reboot into the 2.8.5 recover (like it suggested) and i hit Reboot and then it reboots into 2.7. From there it thinks there is no OS installed. Rebooting from there just reboots me back in 2.7 recovery. I can get into Fastboot, and then back in 2.8.5 recovery. I flashed a new ROM, but that didn't fix it. I attempted to flash an RUU but i can't seem to get that working either. Am I completely screwed and should i call insurance on it?
Help me XDA, you're my only hope.
Click to expand...
Click to collapse
To solve this, you could get phone into Fastboot and flash Dottat's RUU for the M8 - he made several versions.
For sure, add HTC_Fastboot.exe to your ADB folder and use it, NOT regular fastboot.
It will overwrite your previous recovery with stock and fix your phone. Then later, you could flash TWRP 2.8.7 thru Fastboot.
I put Dottat's RUU on my external SD card and it loaded, however, whenever it goes to reboot, it still goes back into the wrong recovery.
It's probably not necessary to run an RUU. You incorrectly flashed the new recovery to the wrong partition. Flash the new recovery VIA FASTBOOT, boot into it through the bootloader screen, and either flash a rom or restore a backup and you should be good to go. You definitely don't need to be worrying about an insurance claim for now.
Edit: by VIA FASTBOOT I mean with the command fastboot flash recovery <nameofrecoveryfile>.img
cntryby429 said:
It's probably not necessary to run an RUU. You incorrectly flashed the new recovery to the wrong partition. Flash the new recovery VIA FASTBOOT, boot into it through the bootloader screen, and either flash a rom or restore a backup and you should be good to go. You definitely don't need to be worrying about an insurance claim for now.
Edit: by VIA FASTBOOT I mean with the command fastboot flash recovery <nameofrecoveryfile>.img
Click to expand...
Click to collapse
I would flash firmware or ruu, if indeed he flashed recovery to wrong partition, that partition needs the correct one which firmware wlil do, and ruu will 100% do.
Personally I'd run ruu, go to stock recovery and run a factory reset.
theoden144 said:
I put Dottat's RUU on my external SD card and it loaded, however, whenever it goes to reboot, it still goes back into the wrong recovery.
Click to expand...
Click to collapse
Gotta use ADB and HTC_Fastboot.exe
Thanks for all the tips. I tried re-installing the old ROM after I ran the RUU and it worked. Hopefully it cleared out the incorrect recovery. Lesson learned: don't use apps to update the recovery!
Again thanks for all the help!
theoden144 said:
Thanks for all the tips. I tried re-installing the old ROM after I ran the RUU and it worked. Hopefully it cleared out the incorrect recovery. Lesson learned: don't use apps to update the recovery!
Again thanks for all the help!
Click to expand...
Click to collapse
Twrp manager is not a safe way to flash recovery because they aren't flashing by block name yet. They are still hard-coded to block number. The partitions have changed during ota already...so the app does hose things up a bit.
Sent from my Nexus 6 using Tapatalk