Related
Hello, all. I'm running a rooted At+t locked dell streak. I've install ROM Manager and "Successfully" flashed Clockwordmod several times. However, every time i try to use it (Boot into recovery mode, for instance) it will just reboot, as if you didn't ask. More over, when I try to access it normally (pressing both volume buttons on boot) it launches into stock recovery mode (with the four options - Factory reset, install from pkg, etc).
What should I do?
Stock firmwares automatically replace the recovery image on boot every time, you need to be on a custom rom for it to not do that
Silly me, I was trying to boot into the Clockworkmod recovery mode so that I could install a custom rom...how do I go about circumventing this?
use fastboot -i 0x413c reboot (after installing the recovery)
as it's rebooting IMMEDIATELY hit vol up+down + power, if you hit the dell logo, repeat it because you're too late
if you hit it fast enough, you can use cwm/streakmod once on stock (it'll still overwrite it with stock recovery after reboot)
The ROM Manager app doesn't play well with the Streak.
I recommend Streakmod recovery. I use this version.
If you aren't installing a custom ROM you can make a custom recovery stick by renaming install-recovery.sh to something else (IE - install-recovery.sh.norun). On my phone I found the file in /etc and /system/etc , you would need a root explorer or other root method to do this.
It appears I am more noobish than I had originally considered. Is there a step by step guide to installing a recovery mod? For instance, I am not sure what relevance "fastboot -i 0x413c reboot" has here. Is this something I should type in, and if so, where and under what circumstances?
Thanks!
This streakdroid guide may help.
You flash the recovery image with fastboot and the command to reboot that was in a previous post lets you restart the phone without pulling the battery.
What exactly is on your phone now? Menu->Settings->About phone
Example attached.
On the stock roms go to /system/etc and rename install-recovery.sh to install-recovery.sh.bak (or delete it if you would like) and then whatever recovery you flash will persist after a reboot
Hello xda every I have an major problem I tried to flash an rom today via the rom manager app and cleared cache and others that was requires now I cannOt get into recovery mode it's just shows the htc logo and boots up regular but I can acres fastboot I'm on 1.50 s-on all help would be very appreciated other i I searched other threads to no avail
If you tried flashing a rom with a custom kernel through rom manager it won't work. You have to flash that through fastboot. You say that your phone "boots up regular" as in boots into android?
Sent from my PG86100 using XDA App
Sofocused504 said:
Hello xda every I have an major problem I tried to flash an rom today via the rom manager app and cleared cache and others that was requires now I cannOt get into recovery mode it's just shows the htc logo and boots up regular but I can acres fastboot I'm on 1.50 s-on all help would be very appreciated other i I searched other threads to no avail
Click to expand...
Click to collapse
Not all of your infmration is easy to follow or understand.
Essentially, if you're looking to flash a kernel or ROM (which many times also include a kernel), there are three basic methods (two seem the easier) with hboot 1.50 and htc's unlock method:
1) For Kernel Flashing: From Android mode, using my application, Flash Image GUI. Put the kernel .zip file on your sdcard, select from inside the application and flash.
If flashing a ROM, pull out the kernel file (usually named boot.img), push to sdcard and flash using Flash Image GUI.
If you're away from a computer and want to flash a kernel, this is a great tool.
2) Load the custom recovery, NOT using the traditional method (reboot recovery, bootloader -> recovery, etc), but a specific method for Hboot 1.5. From the prompt use: fastboot boot c:\downloads\cwm-recovery.img.
This will temporarily boot the custom recovery image and the HTC unlock method will grant it write access to the boot partition while in this mode.
In this temporarily booted recovery mode, when a full ROM (with kernel included) is flashed, the kernel will flash correctly.
3) Boot into recovery using the traditional methods, reboot recovery, bootloader -> recovery, etc, and after the custom recovery has loaded, flash the ROM. Reboot into fastboot mode and then separately flash the kernel from the computer: fastboot flash boot c:\boot.img.
Downside to this method would be if a zImage is included instead of the boot.img for the kernel, won't flash correctly.
If you're issues are with not entering a custom recovery mode when following step 3, there are a few options. If you're able to boot into normal android mode w/o any issues and you seem familar with ROM manager, flash the custom recovery again from there.
My app, Flash Image GUI, also offers the same feature, select the recovery.img or PG86IMG.zip file off the sdcard and Flash Image GUI will flash it.
Another option is to flash it via fastboot: fastboot flash recovery c:\downloads\cwm-recovery.img
Hope that helps clarify!
flonker said:
If you tried flashing a rom with a custom kernel through rom manager it won't work. You have to flash that through fastboot. You say that your phone "boots up regular" as in boots into android?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
yes i meant boots into android regular just cannot get into custom recover I navigate to it and press power the htc logo appears and the phone shuts itself off and booth back into android
Sofocused504 said:
yes i meant boots into android regular just cannot get into custom recover I navigate to it and press power the htc logo appears and the phone shuts itself off and booth back into android
Click to expand...
Click to collapse
If the device does not make it past the splash screen this usually indicates a bad kernel (or ramdisk) or bad flash.
Either flash the same recovery file again or download a new recovery file.
Sometimes a bad flash can occur, usually rare. Sometimes the recovery file can corrupt while downloading, usually rare. But these things do occur.
Good luck!
I have the castor windy version 16gb SGP511. I was previously rooted but not unlocked. I unlocked the boot loader. Installed the twrp image on the pac man thread which i think was dual recovery cause Philz,Cwm came out, so I can install lollipop version of the rom. Made a backup of the stock rom. Followed this instructions - Install the Lollipop ROM + GApps+SuperSU using whatever Recovery you have.
- Turn off device completely.
- Press <Volume Up> and plug USB cable.
- LED should turn blue.
- Send command: "fastboot erase recovery"
- Send command for Castor_Windy: "fastboot flash recovery TWRP_Castor_Windy.img"
- Send command for Castor: "fastboot flash recovery TWRP_Castor.img"
- Unplug USB cable.
- Device will reboot.
- When LED turns pink press <Volume Up> and <Volume Down> several times.
- You should now see TWRP
I wasnt fast enough so stock rom booted. I used Adb reboot recovery to access recovery and did as the above mentioned. Wiped i tried to install the rom which failed. Rebooted back to system and got stuck in Sony boot up screen. I can access fastboot. Read though the forums I have to find a ftf or a system image file and use a flash tool. What ftf file or system image my I use use which will let me root my device again.
Thanks Steve
Kamaleon said:
What ftf file or system image my I use use which will let me root my device again.
Thanks Steve
Click to expand...
Click to collapse
Try this Xperia downloader tool. Should let you see which versions are which. If you want an easy root, then stay away from the KitKat builds, unless you want to unlock bootloader.
http://forum.xda-developers.com/cro...xperifirm-xperia-firmware-downloader-t2834142
Use Flashtool to flash your downloaded ftf file. Just make sure your device is charged.
http://forum.xda-developers.com/showthread.php?t=2335555
I believe flashtool will even install the drivers for your 511
Thanks for the reply. Flashed ftf file and my tablet is up an running. Do I have to unlock my bootloader again or is it unlocked already?
Kamaleon said:
Thanks for the reply. Flashed ftf file and my tablet is up an running. Do I have to unlock my bootloader again or is it unlocked already?
Click to expand...
Click to collapse
Well, now this depends.
If you previously had KK running, and flashed a original version JellyBean ROM, then it probably locked the bootloader again.
If you flashed the same version as you had previously installed, then it didn't lock it again.
Moscow Desire said:
Well, now this depends.
If you previously had KK running, and flashed a original version JellyBean ROM, then it probably locked the bootloader again.
If you flashed the same version as you had previously installed, then it didn't lock it again.
Click to expand...
Click to collapse
Thanks. Yes i was unlocked already, went through the process again to verify. Trying to upgrade my firmware which is 17...........402. to a kk build firmware. I have the old cwm recovery 6.0.4.6. being trying to upgrade or even change recovery to any recovery except dual recovery. Through fastboot which none of them stick. Fastboot erase recovery
fastboot flash recovery recovery.img all of them(CWM,TWRP,PHILZ). The process goes smoothly but when I access recovery the old recovery comes up. What seems to be problem? I cant change my recovery or even upgrade it. I never have had this problem before some insight needed before i take a wrong turn. LOL.
Kamaleon said:
Thanks. Yes i was unlocked already, went through the process again to verify. Trying to upgrade my firmware which is 17...........402. to a kk build firmware. I have the old cwm recovery 6.0.4.6. being trying to upgrade or even change recovery to any recovery except dual recovery. Through fastboot which none of them stick. Fastboot erase recovery
fastboot flash recovery recovery.img all of them(CWM,TWRP,PHILZ). The process goes smoothly but when I access recovery the old recovery comes up. What seems to be problem? I cant change my recovery or even upgrade it. I never have had this problem before some insight needed before i take a wrong turn. LOL.
Click to expand...
Click to collapse
You mean the "factory" recovery comes up.
Well, just for info, you don't need to run the fastboot "erase" command when installing a recovery. Not necessary as the new image file will overwrite the existing.
Also, you don't exactly need to flash a recovery either. You can connect via USB, boot to bootloader, and run the "fastboot boot recovery.img (or whatever you named it) as long as your custom recovery is in the same folder as the fastboot.exe. This will just the custom recovery without installing it, thus allowing you to flash stuff.
As to why your fastboot flash isn't sticking, I'm new to the Sony tab, so haven't learned all the quirks yet as compared to Acer tabs.
Moscow Desire said:
You mean the "factory" recovery comes up.
Well, just for info, you don't need to run the fastboot "erase" command when installing a recovery. Not necessary as the new image file will overwrite the existing.
Also, you don't exactly need to flash a recovery either. You can connect via USB, boot to bootloader, and run the "fastboot boot recovery.img (or whatever you named it) as long as your custom recovery is in the same folder as the fastboot.exe. This will just the custom recovery without installing it, thus allowing you to flash stuff.
As to why your fastboot flash isn't sticking, I'm new to the Sony tab, so haven't learned all the quirks yet as compared to Acer tabs.
Click to expand...
Click to collapse
I mean cwm recovery v6.0.4.6 comes up the one I installed Doomlords thread with the advanced kernel. I ran fastboot erase recovery command to see if the new recoverys would stick and replace it but it didn't. I have done your instructions before hand thats how I am accessing the bootloader. "fastboot boot recovery.img all add this command to see If the new recovery would pop up. Thanks for the reply.
Kamaleon said:
I mean cwm recovery v6.0.4.6 comes up the one I installed Doomlords thread with the advanced kernel. I ran fastboot erase recovery command to see if the new recoverys would stick and replace it but it didn't. I have done your instructions before hand thats how I am accessing the bootloader. "fastboot boot recovery.img all add this command to see If the new recovery would pop up. Thanks for the reply.
Click to expand...
Click to collapse
Well, here's what I think is going on.
1. You installed Doomlords kernel. Note that this is a foto-kernel, which means the kernel itself has a partition that contains a recovery. What this means, is that as long a the fota-kernel was not replaced, then that specific recovery will be there.
2. You flashed a normal recovery. Now, I think this is there, but because of the fota-kernel, the fota-kernel is taking precedence.
Like I said, I don't know a lot about this Sony tab and the different partitions,as they are different from other tablets I am familiar with.
What puzzles me, is that if you flash a new "ftf" without changing any options in Flashtool, it "should" rewrite "every" partition on the tab, and install Stock recovery.
Now, based on my experience with Acer A500x and A700x tablets, I can say there are times when your issue happens. Rare, but it does happen. Things say they flash ok, but the old stuff still remains. The only option at that point, was to go back to a totally original version of the firmware.
Not sure I'm helping you on this. But the good thing, is that you can Fastboot Boot Recovery.
MD
Moscow Desire said:
Well, here's what I think is going on.
1. You installed Doomlords kernel. Note that this is a foto-kernel, which means the kernel itself has a partition that contains a recovery. What this means, is that as long a the fota-kernel was not replaced, then that specific recovery will be there.
2. You flashed a normal recovery. Now, I think this is there, but because of the fota-kernel, the fota-kernel is taking precedence.
Like I said, I don't know a lot about this Sony tab and the different partitions,as they are different from other tablets I am familiar with.
What puzzles me, is that if you flash a new "ftf" without changing any options in Flashtool, it "should" rewrite "every" partition on the tab, and install Stock recovery.
Now, based on my experience with Acer A500x and A700x tablets, I can say there are times when your issue happens. Rare, but it does happen. Things say they flash ok, but the old stuff still remains. The only option at that point, was to go back to a totally original version of the firmware.
Not sure I'm helping you on this. But the good thing, is that you can Fastboot Boot Recovery.
MD
Click to expand...
Click to collapse
I started from zero again flashed ftf Firmware SGP511_17.1.1.A.0.402. Verfied that i was bootloader unlocked I still was. Used fastboot to flash Dooms Kernel, without a problem used cwm revovery to flash Supersu. Tried to upgrade my firmware with the prerooted rooms in thread flashed with out a problem but no difference was provided. Verified in settings and initial firmware stands (SGP511_17.1.1.A.0.402). Tried to flash CM12 got stuck on a bootloop. Fastboot flashed the boot img provided didn't work for me so I flahed Teslas rom Followed instructions provided
1. Make sure you have CWM installed and a working nandroid backup
2. Download the ROM.
3. Place the ROM on your SD-Card.
4.Extract boot.img included in zip and fastboot flash it via Flashtool or CMD
5. Reboot to recovery.
6. Wipe data-factory reset/cache partition/dalvik cache
7. Flash the ROM.
Flash went through but when I try to access recovery through the rom or adb recovery doesnt come up. The tablet just stays black on recovery screen and the tablets led turns yellow. I have adb access so went to access fastboot flashed different recoverys. None of them (flashed without a problem), work but if a flashed Dooms I have access to recovery again, but loose functionality of the rom it gets stuck on sony screen. I have to do the steps all over again without a working recovery. This has being a learning experience I am HTC guy so the process with sony products is new to me as well. So where do you think I should go on from here; flash a newer ftf or lock and unlock my bootloader again to see if something happens or just move on jajajajj . Anyways thanks a lot for your help.
Kamaleon said:
I started from zero again flashed ftf Firmware SGP511_17.1.1.A.0.402. Verfied that i was bootloader unlocked I still was. Used fastboot to flash Dooms Kernel, without a problem used cwm revovery to flash Supersu. Tried to upgrade my firmware with the prerooted rooms in thread flashed with out a problem but no difference was provided. Verified in settings and initial firmware stands (SGP511_17.1.1.A.0.402). Tried to flash CM12 got stuck on a bootloop. Fastboot flashed the boot img provided didn't work for me so I flahed Teslas rom Followed instructions provided
1. Make sure you have CWM installed and a working nandroid backup
2. Download the ROM.
3. Place the ROM on your SD-Card.
4.Extract boot.img included in zip and fastboot flash it via Flashtool or CMD
5. Reboot to recovery.
6. Wipe data-factory reset/cache partition/dalvik cache
7. Flash the ROM.
Flash went through but when I try to access recovery through the rom or adb recovery doesnt come up. The tablet just stays black on recovery screen and the tablets led turns yellow. I have adb access so went to access fastboot flashed different recoverys. None of them (flashed without a problem), work but if a flashed Dooms I have access to recovery again, but loose functionality of the rom it gets stuck on sony screen. I have to do the steps all over again without a working recovery. This has being a learning experience I am HTC guy so the process with sony products is new to me as well. So where do you think I should go on from here; flash a newer ftf or lock and unlock my bootloader again to see if something happens or just move on jajajajj . Anyways thanks a lot for your help.
Click to expand...
Click to collapse
Well, I'm not sure which route to take.
However, I will tell you what I have learned the other day.
I have the 521 with unlocked bootloader. Rooted with my own boot.img, flashed SuperSU using "flashboot boot recovery.img" (yeah, sometimes it doesn't show on the display, so it takes a few times).
Now, other day I was going to check out the new LyPop pre-rooted. Fastboot flash recovery recovery,img, and it won't boot it to recovery like it should. Like it's not flashed. Tried it a couple times. Now, I didn't install the dual recovery as I'm not sure how that kernel (boot.img) will interact with my current tabs OS. Not to mention I need it for my work until tomorrow. But strangely it sounds like the same issue you have.
This weekend I will investigate it. As for me, I will probably flash the Stock ftf lyPop build, and just root it using a modified boot.img.
One thing I do know, is flashing a custom recovery to the "recovery" partition, doesn't seem to work like it used to work on other devices. It seems the flashing to the "Fota kernel" partition seems to be the only method that works. This is what happens when you flash that dual recovery, or any recovery that has a boot image using "Fota". Probably explains why you can't get rid of it using "fastboot erase recovery". because it's erasing the wrong partition. Only flashing a full ftf gets rid of it, because the ftf has a new FotaKernel it flashes.
Eh, something like that. Will look at it this weekend.
Hi, I oem unlocked my Nexus 9, installed TWRP and SuperSU, but I think I missed a step before I can go to custom ROMs and all. I've looked for instructions but I'm just getting confused. I firstly cannot reboot into TWRP unless I fastboot boot recovery from my PC every time. If I don't do that, it just boots into the Flounder PVT Ship white screen with Fastboot USB in red and below that HBOOT, REBOOT, REBOOT FASTBOOT, and POWER DOWN.
What step am I missing in this process? Do I need some sort of custom image or what am I doing wrong?
Thanks,
Chris
Hello,
It can get a bit confusing sometimes and people generally expect you to just know lol.
You've not missed a step. Getting into recovery is irritating lol. For as long as I've had it if booted into recovery from the power menu lol xD.
Reboot the Google Nexus 9 by holding the Power and the Volume Down buttons at the same time and wait until the tablet display shows a Google splash screen before releasing the buttons.
If you get a android with an exclamation mark then you've made a boo boo. Dw, even us pros muck up ;]
Go back to your fastboot. Flash twrp like you do. But this time once you've flashed it type
Code:
fastboot boot recovery twrp.img
That should boot your device into recovery after flashing it.
There it should be stuck on there nicely of it takes a while Dw. That's just the fun of owning a N9 lol. That should Do it .
Happy Flashing.
Give us a Thanka if I helped
ChrispyChris said:
Hi, I oem unlocked my Nexus 9, installed TWRP and SuperSU, but I think I missed a step before I can go to custom ROMs and all. I've looked for instructions but I'm just getting confused. I firstly cannot reboot into TWRP unless I fastboot boot recovery from my PC every time. If I don't do that, it just boots into the Flounder PVT Ship white screen with Fastboot USB in red and below that HBOOT, REBOOT, REBOOT FASTBOOT, and POWER DOWN.
What step am I missing in this process? Do I need some sort of custom image or what am I doing wrong?
Thanks,
Chris
Click to expand...
Click to collapse
If you installed TWRP using
Code:
fastboot flash recovery twrp.img
The only ways I know to get into recovery are to reboot to recovery from the Power menu of your ROM
OR
Boot to fastboot, select HBOOT, then select Recovery. If TWRP is installed as your recovery this will boot TWRP. If it goes to the dead droid screen then you need to install TWRP properly, using the fastboot flash command above.
I can't get my nexus 9 to run twrp as well.
I go to fastboo, select Hboot, then I get the android with exclamation, volume up and power brings up the original android recovery menu, not twrp. I've unlocked the bootloader, wiped everything and tried again, no luck. Always the same result
Mephisto_POA said:
I can't get my nexus 9 to run twrp as well.
I go to fastboo, select Hboot, then I get the android with exclamation, volume up and power brings up the original android recovery menu, not twrp. I've unlocked the bootloader, wiped everything and tried again, no luck. Always the same result
Click to expand...
Click to collapse
Are you using the newest TWRP? 3.1.0.0? It's not working for me either, can't boot to recovery. Use 3.0.2.2 or whatever the last version was
I used the 3.1.0.0
the trick was, after installing it, reboot straight back into recovery, so it doesn't get overwritten
Hello! This is my first thread on the forum;
I'm writing because I think I soft bricked my Xiaomi Mi Pad 4 LTE, let me explain from the very beginning.
It's a brand new device, bought today, and with a custom italian ROM which was sold with.
I just wanted to root it, and the bootloader was already unlocked because it was a custom ROM, so I tried to install TWRP (mocha version for Mi Pad) with Fastboot and then I wanted to install Magisk.
The issue is that, when I tried to flash TWRP to recovery with fastboot flash recovery twrp.img, it all went "OK" but then TWRP was not actually flashed and couldn't boot it with key combinations, it just looked like it wasn't there. I also tried to boot it without flashing, with fastboot boot twrp.img but it gave me
"Failed to load/authenticate boot image: 00000050" error
Looking on the web, I found someone who told to try fastboot flash boot twrp.img and so, without even thinking, I did it.
That's the main issue. I rebooted, and found that TWRP started, but now I couldn't boot my device anymore, because the default boot.img file was replaced by twrp.img. So, practically, TWRP replaced my device's default system (I think?).
Then, I tried to find a stock firmware for Mi Pad 4 (Clover) on the web, and I found it, so I flashed the stock firmware boot.img, fastboot flash boot boot.img, but when I rebooted, the device was stuck in the loading screen with three dots loading over a "Powered by Android" logo. I waited 20 minutes, nothing, it looks stuck, so this stock boot.img doesn't seem to work.
I can actually flash TWRP and that stock boot image both whenever I want and switch between them; the first works, the latter doesn't.
So, in poor words: I flashed twrp.img as boot.img and now I can't boot normally, but TWRP starts when turning on my device.
But I just want to get my default boot.img or system, or any other way to reaccess to my device. That's fine even if I have to hard reset or wipe everything, it's fine even if I am going to lose data, but please, just help me.
Can someone help me? I'm just a newbie in this world, please help me unbricking my device.
Thanks in advance.
Try installing twrp again and boot to it
Download custom rom.of your choice ( im using hovac and it been great for a year now )
Move it to your mipad via comouter
Format everything in twrp and install the rom and gapps
--- I just remembered havin same issue u having and if im not mistaking : u should reboot to recovery right after installing twrp ( you dont reboot to system )
Im not really sure about it cause it happened long time ago
@DanielVipx
Sorry, seems you tried that already. Did you try the mi flash tool?
This might help:
https://osdn.net/projects/xiaomifirmwareupdater/storage/Stable/V10/clover/