First time making a new thread and I have been on these forums for a while. Mostly because anything I could possibly need to do for my phone has already been posted.
I am having issues with my new Dell Streak. I got this unit as a replacement for an older one that ended up with a cracked screen (Best Buy lost it in the repair process (long story)). My old Streak I was able to flash just fine, this one no such luck. I have tried StreakMod Recovery, ClockworkMod Recovery, as well as the MultiRecoverFlasher, and finally the stock recovery image. It seems every custom recovery I flash ends up giving me a blank screen. The only one I have successfully flashed is the stock recovery image.
Any ideas?
Again, I have done this before, successfully! So I know how the process with fasboot works.
goyjuss said:
First time making a new thread and I have been on these forums for a while. Mostly because anything I could possibly need to do for my phone has already been posted.
I am having issues with my new Dell Streak. I got this unit as a replacement for an older one that ended up with a cracked screen (Best Buy lost it in the repair process (long story)). My old Streak I was able to flash just fine, this one no such luck. I have tried StreakMod Recovery, ClockworkMod Recovery, as well as the MultiRecoverFlasher, and finally the stock recovery image. It seems every custom recovery I flash ends up giving me a blank screen. The only one I have successfully flashed is the stock recovery image.
Any ideas?
Again, I have done this before, successfully! So I know how the process with fasboot works.
Click to expand...
Click to collapse
How did you go about flashing these recoveries? Did you fastboot to 'push' a recovery, or did you try Rom Manager'ing them?
On my previous Streak I had used the simple fastboot method.
Using Windows cmd I did:
fastboot.exe -i 0x413c flash recovery recovery.img
fastboot.exe -i 0x413c reboot
I used StreakMod on that one.
I am trying to do the same on this new Streak with all possible custom recover.img but none of them seem to be working. I keep getting the blank screen.
Related
regardless of what i try the command prompt says "sending..." and goes nowhere from that. i cant flash anything. any ideas?
US Dell Streak for att (not from att) rooted with first leaked 2.1 rom
It would be easier to diagnose if you would be more specific.
Please copy-paste the command you gave and response you got.
smokku said:
It would be easier to diagnose if you would be more specific.
Please copy-paste the command you gave and response you got.
Click to expand...
Click to collapse
smokku's right, does it say 'fastboot' on the streak screen?
Is the device in fast boot mode?
Sent from my Dell Streak using XDA App
phone is in fastboot mode and says as much on the phone screen. what i am currently trying to do is flash back to 1.6 and the guide i was following said flash stock dell recovery. i downloaded the stock recovery file and in cmd i typed
fastboot flash recovery recovery.img
i was in the correct directory and the recovery.img file was there
the cmd then says sending recovery.img... and sits there. it doesnt fail it just does nothing. ive tried flashing several different recoveries including the clockworkmod recovery and i still get nothing but sending...
Try this worked for me
http://www.streaksmart.com/2010/08/...d-16-on-dell-streak-after-21-update.html#more
lufc said:
Try this worked for me
http://www.streaksmart.com/2010/08/...d-16-on-dell-streak-after-21-update.html#more
Click to expand...
Click to collapse
still getting no response from fastboot. i had this problem before and i just kept unlplugging the usb and reinstalling drivers. but its not working for me this time
Right the way to do it is download the recovery image from the last link download the stock recovery from here
http://android.modaco.com/content/d...1-6-downloads-how-tos-rom-superboot-recovery/
open them both up
in the r1-4399-streak-recovery delete the RECOVERY and copy over the recovery from the other file and rename it recovery
put device in fastmode and start the windows batch and the recovery will install
If i ever need to install a stock recovery just install it into the r1-4399-streak-recovery rename it recovery and it will install every time
lufc said:
Right the way to do it is download the recovery image from the last link download the stock recovery from here
http://android.modaco.com/content/d...1-6-downloads-how-tos-rom-superboot-recovery/
open them both up
in the r1-4399-streak-recovery delete the RECOVERY and copy over the recovery from the other file and rename it recovery
put device in fastmode and start the windows batch and the recovery will install
If i ever need to install a stock recovery just install it into the r1-4399-streak-recovery rename it recovery and it will install every time
Click to expand...
Click to collapse
i'll give it a try. thanks
well i finally was able to flash recovery, boot, and system after a reboot of my pc and phone and reinstaling drivers before each flash. now im stuck at the dell logo. ugh...
update: was able to flash to stock 02 1.6 rom. via the link lufc provided (thank you) i guess i'll have to retry flashing back to stock att 1.6 after a few more people have tweaked it and make an update.pkg for it.
punkrckriot said:
well i finally was able to flash recovery, boot, and system after a reboot of my pc and phone and reinstaling drivers before each flash. now im stuck at the dell logo. ugh...
update: was able to flash to stock 02 1.6 rom. via the link lufc provided (thank you) i guess i'll have to retry flashing back to stock att 1.6 after a few more people have tweaked it and make an update.pkg for it.
Click to expand...
Click to collapse
Yeah i got stuck at the dell log a couple times before it successfully flashed. I think something is up with fastboot not properly writing the files because i'll flash the clockworkmod recovery 3 or 4 times in a row with no result. give up on it and flash stock recovery then when i go into recovery mode, its the clockworkmod one :/
fone_fanatic said:
Yeah i got stuck at the dell log a couple times before it successfully flashed. I think something is up with fastboot not properly writing the files because i'll flash the clockworkmod recovery 3 or 4 times in a row with no result. give up on it and flash stock recovery then when i go into recovery mode, its the clockworkmod one :/
Click to expand...
Click to collapse
i just think my PC and fastboot dont agree with eachother. before i can flash anything i have to uninstall the drivers, restart my pc, reboot phone into fastboot again, reinstall drivers, and then flash what im trying to flash one at a time, then restart the whole process to get any results on what i try to flash next. I have no idea whats up with the recoveries because i ran into the same issue of flashing clockworkmod and having it work fine till next reboot and its back to stock.
lufc said:
Try this worked for me
http://www.streaksmart.com/2010/08/...d-16-on-dell-streak-after-21-update.html#more
Click to expand...
Click to collapse
Used this yesterday to go back to 1.6 so my streak gould go off for repair, worked a treat.
spences10 said:
Used this yesterday to go back to 1.6 so my streak gould go off for repair, worked a treat.
Click to expand...
Click to collapse
yeah im on an att streak though so i needed to get back to the US stock rom. its good to go now. thanks though
Early today, I was working on a G2 trying to get it rooted with a custom ROM installed. I managed to root the phone and disable the bootloader security. From here, I attempted to install clockwork recovery via rom manager... here's where the disaster starts.
Everything seemed to be going well (no errors), so I tried to load a custom ROM. The Rom installation started but failed partway through. This is when I noticed that the clockwork recovery wasn't working properly. It was flickering and none of the options worked (screen just flashed or turned black if you selected anything). So at this point, the phone would not boot since the ROM installation didn't complete, and I had a buggy recovery image installed.
Unfortunately, the fun doesn't stop here. I figured that I should load the PC10IMG.zip and start from scratch... bad idea. This flashed the bootloader (relocking it) then failed-- leaving me with a bad ROM, bad recovery image, and a locked bootloader. Luckily for me, I was able to use adb via the buggy recovery to unlock the bootloader again.
At this point, I got a bit antsy and jumped the gun. I decided to use fastboot to erase and load a new recovery image. Unfortunately, I realized that I didn't have a recovery.img file to flash... just after I used the fastboot erase recovery command.
I'm hoping that someone here has a recovery.img file compatible with the T-Mobile G2 so I can flash the recovery partition with fastboot. If anyone has any better ideas I'm open to suggestions.
Thanks in advance for any help.
Install amon recovery. It's much better then clockword. Do it using adb
Sent from my HTC Hero using XDA App
Just an update. I couldn't get into adb but I was able to flash clockwork via fastboot. For whatever reason, the amon recovery would go through. Nevertheless, I installed cyanogen using clockwork and everything is gravy!
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 guys, I have stumbled upon a problem and any help found here is not helping. I have decided to finaly root moto E (I thought I am too old for rooting now, but I am not) and the problem I got is pretty simple.
Bootlocked unlock is ok.
But then I decided not to reflash stock recovery and just to boot into recovery for once to flash superSU to avoid martyrium caused by getting original recovery (since HTC different retarded versions for every country and every retailer, I am very cautious). I have tried 2 versions of TWRP, one CWM, after "fastboot boot recovery.img" phone boots forever, never finishes, but phonw is fully operational still, so no damage done. I have even tried to reflash recovery in the end, none of them worked. Well, command prompt told me OKAY OKAY, but nothing really happened, like while just booting into recovery. I have even tried several USB cables (happened once with desire X that everything was due to broken USB cable).
I am out of ideas, could please someone point me to some direction of what is wrong?
It runs 4.4.4
mindlesSheep said:
Hi guys, I have stumbled upon a problem and any help found here is not helping. I have decided to finaly root moto E (I thought I am too old for rooting now, but I am not) and the problem I got is pretty simple.
Bootlocked unlock is ok.
But then I decided not to reflash stock recovery and just to boot into recovery for once to flash superSU to avoid martyrium caused by getting original recovery (since HTC different retarded versions for every country and every retailer, I am very cautious). I have tried 2 versions of TWRP, one CWM, after "fastboot boot recovery.img" phone boots forever, never finishes, but phonw is fully operational still, so no damage done. I have even tried to reflash recovery in the end, none of them worked. Well, command prompt told me OKAY OKAY, but nothing really happened, like while just booting into recovery. I have even tried several USB cables (happened once with desire X that everything was due to broken USB cable).
I am out of ideas, could please someone point me to some direction of what is wrong?
It runs 4.4.4
Click to expand...
Click to collapse
Please post screenshot of terminal.
Try these steps
1: adb reboot bootloader
2: fastboot devices
3: fastboot flash recovery name-of-the-recovery.img
not at pc atm,but as I said,devices list my device, fastboot flash gives okay twice,same as fastboot boot, and reboot bootloader... I think it would not help me at all, bootloader is accesible
edit: adb reboot recovery does notghing else than manualy booting into recovery (=nothing)
I didn't pay attention to HTC part, recently I faced same problem after flashing recovery and worst part was when I did Factory Reset. It got stuck on forever Boot Loop. Try this Go through Recovery 1. Wipe Dalvik Cache 2. Factory Reset. This worked for me hope same for you. And correct me if I couldn't get your problem.
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/