Hi.
I have a defy plus .2.3.6 rooted with 2ndinit recovery.
every ROM I've tried to flash makes the phone stuck in bootloader menu, so i had to flash SBF again.
am i do something wrong? I've flashed a lot of roms on defy mb525, and everything worked fine.
thanks and sorry for my terrible english.
Sow now you are stuck in bootloop or you can not flash a custom rom?
I just flash SBF and go back to stock rom.
try wiping data in stock recovery .
(if you access it)
No access to recovery. boot right to the bootloader.
Reply!
Firstly is your defy rooted? If yes, install 2ndint and go to recovery by switching off your phone and press volume+ and power on button.
The problem you are facing is because you are not clearing cache before flashing a custom rom. Happened to me once so i know! Follow this procedure to the line and you should be fine!
http://forum.xda-developers.com/showthread.php?t=1663613
Hmmmmm
What bootloader you have? I think... v7
Teoretically you can use any 2.3.6 ROM
Yup, V7.
The only rom I was able to install it is CM9.
I'd tried this:http://forum.xda-developers.com/showthread.php?t=1667536 with the same results.
Before the problem, I had a 4.1.1 rooted unlocked N7 with original ROM. I decided to apply the OTA update (03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip) from TWRP recovery using the option to manually install zip updates.
The tablet rebooted, and I used Voodoo OTA RootKeeper to regain root access. Everything worked fine, I had no error messages at any moment during the procedure and the 4.1.2 update was applied successfully, as I could verify in the info section and by testing the landscape mode.
But, when I try to reboot in recovery using the option in ROM Manager, all I get is the little robot on his back image without any message. The only way to get out of this screen is to press the power button for a few seconds until it reboots into Android. Everything is fine except the recovery mode.
I tried to reflash the recovery image using Wug's Toolkit to no avail. I tried CWM, TWRP and stock recoveries but none worked. I always get the same screen with the robot on his back when I try to boot into recovery. Booting normally is always fine, only recovery seems to be affected. If I use Wug's toolkit to boot a temporary TWRP recovery image, it works but I want to be able to boot as before, with ROM Manager.
Any ideas? Is there a solution other the wipe it all and restart from scratch?
[edit] I can start into Fastboot but if I try to go to recovery from there, the same thing happens...
I fixed it by flashing the older 3.34 bootloader. So something is wrong with the new 3.41 bootloader.
There is nothing wrong with the process.
Its the users interpretation of how it works.
After updating, the file that flashes the stock recovery on boot is put back.
So he flashed in custom recovery.
Booted at which point the custom recovery is replaced with stock
Then wonders why he can't access custom recovery anymore.
Just reflash custom recovery
Sent from my HTC One X using xda app-developers app
bagofcrap24 said:
There is nothing wrong with the process.
Its the users interpretation of how it works.
After updating, the file that flashes the stock recovery on boot is put back.
So he flashed in custom recovery.
Booted at which point the custom recovery is replaced with stock
Then wonders why he can't access custom recovery anymore.
Just reflash custom recovery
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Not true. I flashed the update through cwm and everything went fine. When you reboot the system, cwm asks if you want to flash recovery and keep root. I denied to flash the stock recovery and I kept the root. After that you can't get into recovery at all (stock or cwm or whatever). but if I downgrade my bootloader to 3.34 everything is ok. I also installed new bootloader through cwm manually again and after that I can't boot into recovery.
Btw... How to flash bootloader.raw with fast boot???
Sent from my Nexus 7 using Tapatalk 2
sikagoon7 said:
I think you are a bit misinformed. When you flash the OTA the recovery-from-boot.p is installed by default. It resets the recovery to stock every time you reboot. CWM does nothing to remedy this. The only way to fix it is to remove or rename the file to disable its function. After and ONLY after this will you be able to flash recoveries by choice and boot into them.
And while it is your choice to use whatever recovery you desire I personnaly think using stock recovery and adb sideload is the safest when it comes to signed stock OTA.zips. After that you can root and flash your recovery of choice as if you have a brand new device.
When it comes to the bootloader. Stock system, boot, and recovery verify which bootloader you are using. JRO03D looks for 3.34 and JZO54K looks for 3.41. I don't know the implications of switching them but I don't think I will test that. I've already had a bad experience with dismantling a bootloader. The bootloader is an IMG file. Download the JRO03D factory image from Google's website and extract it. Inside will be a file named bootloader-grouper-3.34.img. THAT is the stock JRO03D bootloader and that is what you need to flash using: fastboot flash bootloader bootloader-grouper-3.34.img.
Click to expand...
Click to collapse
Yes I know that and did that from the beginning (renamed the file) but the point is that you can't boot into recovery (stock or whatever). It tries to boot into recovery I think but it reboots again and loads the OS. I'm using 3.34 booatloader with 4.12 and haven't got any probs yet.
Finally Got it Working
I tried one last thing yesterday. I got into ROM Manager and used the option to flash CWM Recovery. Then I rebooted in CWM (using the ROM Manager option). All was fine and when I chose the option to reboot, CWM asked me if I would like to make the custom recovery permanent because it would otherwise be rewritten at boot (this is what caused my problems, I believe). I choose to do so and it worked normally after that.
I then downloaded the TWRP recovery (http://www.teamw.in/project/twrp2/103) and installed it with Wug's Toolkit using the option to flash a permanent Recovery from a file. I didn't modify the "recovery-from-boot.p" file because I thought that CWM already did that. Tested booting into recovery again and all is finally OK with TWRP.
One of the benefits of the 4.1.2 update is that I can now boot into recovery from the Fastboot menu.
I'm in the same boat, ended up flashing the factory image for jz054k (which included the new bootloader) to try and fix.. now I'm without root and without a recovery..
I'm unlocked, but flashing alternative recoveries just doesn't work right now.. can't boot them up.
Did the original author ever get this resolved?
-m
diomark said:
I'm in the same boat, ended up flashing the factory image for jz054k (which included the new bootloader) to try and fix.. now I'm without root and without a recovery..
I'm unlocked, but flashing alternative recoveries just doesn't work right now.. can't boot them up.
Did the original author ever get this resolved?
-m
Click to expand...
Click to collapse
There are mixed reports on bootloader 3.41 and booting recovery. I have not been able to properly boot recovery from 3.41 under any circumstances. If you have this issue as well, flash the 3.34 bootloader from JRO03D. Doing this has allowed me to use recovery again.
I was running 4.1.2 with old bootloader 3.34 and had a SOD while my Nexus was charging last night.
In Faux123's kernel thread, he told me:
You should use the new boot loader and stick with CWM for now until TWRP get their stuff compatible with 4.1.2. Boot loader initialize the power regulators to some know state for the machine to boot until the kernel takes over.. and the new kernel is expecting it to be initialize certain ways... This was the biggest difference between 4.1.1 and 4.1.2... so I HIGHLY recommend using the matching bootloader...
Click to expand...
Click to collapse
Steps I had to take to get 4.1.2 (rooted, stock rom, custom kernel):
flash stock 4.1.1 boot.img and recovery.img
flash 4.1.1 bootloader 3.34
flash recovery TRWP recovery
flash SuperSU (regain root)
flash CWM lastest recovery 6.0.1.5 (beta) based on Faux123 advice above
flash 4.1.2 bootloader 3.41
No problems so far. This whole process has taken days...
I'm finally where I want to be.
Oops, wrong thread...
I unlocked my bootloader awhile back when the exploit first came to light and have been enjoying it mostly problem free since.
I've been using CWM with CM10.1 for the most part but the issues I was having with CM were finally getting to me so I thought I'd just try a debloated stock ROM, and thought it was a good time to try out TWRP while I was clearing everything out.
So I loaded up Matt's tool and flashed the stock ROM back (because for some reason my computer doesn't like to recognize CM over USB), no problems there. At the suggestion of the tool I also flashed the stock recovery (since I intended to flash TWRP I figured it was a good idea). Here's where my problem lies now: The phone boots fine back into stock ROM and I can get back into fastboot no problem but if I try to get into recovery (after flashing stock, CM or TWRP) I only get the opened up Android with the red triangle/exclamation.
Is there some step I need to take that I'm not?
I boot into fastboot and flash recovery (stock). Boot normally wait a couple min (skip setting up accounts, etc) then flash the custom recovery but I seem to end up back at the broken android every time.
EDIT: I might just be an idiot. I completely forgot to root the stock ROM before trying to put the custom recovery back.
Broken android is stock recovery...
Sent from my XT907 using Tapatalk 4
I have the Tmobile G2 d801, with the modified rooted stock KitKat Rom posted by dr87. I tried to flash the zip for Philz recovery through twrp 2.7, but rebooting just brought me to the black screen that said something about Fastboot.
I rebooted back into the ROM and tried using Flashify to flash either one with the same result.
Tried flashing the extracted twrp recovery image using Rom Installer only to get a boot certification verify error and had to do a hardware reset to get the phone to boot back into my ROM.
Is there a way to get a recovery back on my device?
Trying to install the zip through twrp manager also results in a boot certification verify error, but I can boot back into the Rom via the hardware buttons. Any advice?
Never mind, I held my breath and tried Autorec, that fixed it
I'm currently downgraded my phone back to Jellybean (98.30.1) because the Kitkat firmware was a huge battery hog. I then decided to flash TWRP 2.6.3.0. Everything goes well, and then I flashed the pacman msm8960jbbl rom. After that, the phone no longer goes beyond the splash screen. I can still go to recovery and ap fastboot but no matter how many times i wipe my phone, the results always stay the same. The rom worked the first time, but the next few flashes were a trainwreck. Any idea how to fix this problem?
Try returning to stock ROM with RSD lite after that repeat the process to install the custom ROM
Sent From My Razr M (Bliss Stalk ROM) xt907