Hi everyone, I have fixed the latest CM Recovery, files are attached below,
Thanks to defer from #teamdesire @freenode.
Download and flash with fastboot,
Code:
fastboot flash recovery recovery.img
There is also an alternative version which may work for people who get the black screen, please try the alternative version if the first one doesnt work
Worked great for me!
I wanted to test but after the upgrade to 2.1 is not an android I run mode fastboot...........
I tried to install this. All looked to be written OK.
I hold down vol up\down and power on.
The basic recovery menu appears. I select option 2. The screen now just goes black and I have to remove battery to get back into android. Do I actually need a file on the SD card for the CM menu to be displayed?
UK unlocked streak direct from dell - BB=00 - Rom= 4399
Thanks
be_vigilant said:
I tried to install this. All looked to be written OK.
I hold down vol up\down and power on.
The basic recovery menu appears. I select option 2. The screen now just goes black and I have to remove battery to get back into android. Do I actually need a file on the SD card for the CM menu to be displayed?
UK unlocked streak direct from dell - BB=00 - Rom= 4399
Thanks
Click to expand...
Click to collapse
No but you may need the alternative recovery I made, try that one instead.
Thanks for the quick response.
However I still get a black screen using the alt too.
When I flash 1.8.1.7 that loads up OK and I get the CM menu
I just get a black screen with both your fixed and alt versions.
I guess it works for some though. Thanks again mate.
first one works for me with the 2.1 rom
I did get black screen then I pressed volume key and power button..
if I pressed the power button while in the menu I got the black screen again, so repeated the volume then power to get the menu back
so if you get black screen try volume up or down and then power button,
of course the clockwork recovery is a great way of clearing the cache
pressing all the button (no camera button) you get blank screen
re-pressing all the button the screen reappears
but, me too, with a sim free 00 Streak, I can't do anythings, no menu, no update, nothings
be_vigilant said:
I tried .....
UK unlocked streak direct from dell - BB=00 - Rom= 4399
Click to expand...
Click to collapse
the same here
The 2 kernels I have available for recovery are for baseband 21, I would need a dump of stock recovery or boot image from 00 devices to get it working on other devices.
... Obviously its cosmetic, and I dont get my streak till monday, but can that be flipped to be right side up?
AdamG said:
Hi everyone, I have fixed the latest CM Recovery, files are attached below,
Thanks to defer from #teamdesire @freenode.
Download and flash with fastboot,
Code:
fastboot flash recovery recovery.img
There is also an alternative version which may work for people who get the black screen, please try the alternative version if the first one doesnt work
Click to expand...
Click to collapse
I dont understand what do it?When i must use it.
Hmm...
Been working with a trashed recovery partition for a few days.. No biggy, tried pulling off what was on recovery_1 and placing it on etc.. No luck..
But yeah, the first image did work for me (though nandroid failed, my filesystem is pretty trashed.) Do a bit of screwing around replacing files in the system directory and kill my system. I'd already 'fixed' the failed nandroid backup, so I go to restore it, only to see the standard recovery has somehow resurrected itself and clockwork was no longer on.
Magic I tell you.
kwaaq said:
Hmm...
Been working with a trashed recovery partition for a few days.. No biggy, tried pulling off what was on recovery_1 and placing it on etc.. No luck..
But yeah, the first image did work for me (though nandroid failed, my filesystem is pretty trashed.) Do a bit of screwing around replacing files in the system directory and kill my system. I'd already 'fixed' the failed nandroid backup, so I go to restore it, only to see the standard recovery has somehow resurrected itself and clockwork was no longer on.
Magic I tell you.
Click to expand...
Click to collapse
Nandroid only fails because of the path to /data, I should be able to fix this.
how to make a stock recovery image?
Hi I was just wondering how do we go about making a dump of our stock recovery images? Would be nice to be able to backup and restore back to stock if something goes wrong. I have a US streak with BB=31 and Build 6601
AdamG said:
The 2 kernels I have available for recovery are for baseband 21, I would need a dump of stock recovery or boot image from 00 devices to get it working on other devices.
Click to expand...
Click to collapse
help please?
the cmd prompt and device hangs at <waiting for device>
Funk2641 said:
help please?
the cmd prompt and device hangs at <waiting for device>
Click to expand...
Click to collapse
Have you installed the Dell PC suite to get the fastboot driver?
be_vigilant said:
Have you installed the Dell PC suite to get the fastboot driver?
Click to expand...
Click to collapse
Yeah, it's all good. Works great. Only downside is the 30fps limit, but ah well
cemian said:
Hi I was just wondering how do we go about making a dump of our stock recovery images? Would be nice to be able to backup and restore back to stock if something goes wrong. I have a US streak with BB=31 and Build 6601
Click to expand...
Click to collapse
Enable development, so you can run adb, then in adb shell type the following
cat /dev/mtd/mtd1 > /sdcard/recovery.dump
zip the file and upload it here so I can repack it
No mtd1 folder
The command failed saying no such directory...I looked myself and confirmed there is a mtd folder but nothing inside... No mtd1 Folder exists...hmmm
AdamG said:
Enable development, so you can run adb, then in adb shell type the following
cat /dev/mtd/mtd1 > /sdcard/recovery.dump
zip the file and upload it here so I can repack it
Click to expand...
Click to collapse
Related
Hello,
I decided tyo go ahead and try to flash CM10 on my phone and when I did it got stuck at the HTC boot screen upon reboot.
I followed all the detailed instructions and this still happened to me. I figured that I could go ahead and apply the stock rom back just like in other cases of a soft-brick. However, this time upon updating it gave me the "Main version is older! error Press Power to reboot" when installing the stock RUU. Seeing as hansoons tool has a fix for that I apply it and it gives me now "Hboot version is older Press Power to reboot." This is now where I am stuck at. My phone is S-ON and I cannot find a way to turn S-OFF without actually booting into the actual OS. Is there a way and a different route I could take to un-brick my phone? Thanks.
glyphs said:
Hello,
I decided tyo go ahead and try to flash CM10 on my phone and when I did it got stuck at the HTC boot screen upon reboot.
I followed all the detailed instructions and this still happened to me. I figured that I could go ahead and apply the stock rom back just like in other cases of a soft-brick. However, this time upon updating it gave me the "Main version is older! error Press Power to reboot" when installing the stock RUU. Seeing as hansoons tool has a fix for that I apply it and it gives me now "Hboot version is older Press Power to reboot." This is now where I am stuck at. My phone is S-ON and I cannot find a way to turn S-OFF without actually booting into the actual OS. Is there a way and a different route I could take to un-brick my phone? Thanks.
Click to expand...
Click to collapse
are you using 43xt recovery? if not you need to use it since your s=on
and to get it to boot, use his tool to put that recovery on. and then reflash the cm10 rom. then it should work.
i believe that when you flashed it the kernel didnt boot.
ziggy46 said:
are you using 43xt recovery? if not you need to use it since your s=on
and to get it to boot, use his tool to put that recovery on. and then reflash the cm10 rom. then it should work.
i believe that when you flashed it the kernel didnt boot.
Click to expand...
Click to collapse
Nice, got it working thanks for your help and speedy reply man I was stuck for a second.
cheers +1
glyphs said:
Nice, got it working thanks for your help and speedy reply man I was stuck for a second.
cheers +1
Click to expand...
Click to collapse
no problem
Use the thanks button
Sent From My Amaze.
glyphs said:
Hello,
I decided tyo go ahead and try to flash CM10 on my phone and when I did it got stuck at the HTC boot screen upon reboot.
I followed all the detailed instructions and this still happened to me. I figured that I could go ahead and apply the stock rom back just like in other cases of a soft-brick. However, this time upon updating it gave me the "Main version is older! error Press Power to reboot" when installing the stock RUU. Seeing as hansoons tool has a fix for that I apply it and it gives me now "Hboot version is older Press Power to reboot." This is now where I am stuck at. My phone is S-ON and I cannot find a way to turn S-OFF without actually booting into the actual OS. Is there a way and a different route I could take to un-brick my phone? Thanks.
Click to expand...
Click to collapse
I had this same problem yesterday and corrected it by doing the following you need to put the phone into fastboot mode hold down power + power down once bootloader comes up click power again plug your USB in go into CMD (If On windows) CD to C drive then cd to the folder you put the files in below and run fastboot flash boot boot.img. The boot.img is going to be the boot.img from the rom you are using. This worked for me yesterday. When installing a rom make sure you clear Dalvik Cache,Cache & Wipe Data Factory Reset as well as formating your SD Card. Then toggle USB and copy the ROM over I would use 4EXT it is the best recovery out there.
Code:
https://dl.dropbox.com/u/102426750/XDA%20Dev/HTC%20Amaze.zip
Put these files in a folder in the root of your C drive. Once you cd into that folder with these files run the commands above
jared407 said:
I had this same problem yesterday and corrected it by doing the following you need to put the phone into fastboot mode hold down power + power down once bootloader comes up click power again plug your USB in go into CMD (If On windows) CD to C drive then cd to the folder you put the files in below and run fastboot flash boot boot.img. The boot.img is going to be the boot.img from the rom you are using. This worked for me yesterday. When installing a rom make sure you clear Dalvik Cache,Cache & Wipe Data Factory Reset as well as formating your SD Card. Then toggle USB and copy the ROM over I would use 4EXT it is the best recovery out there.
Code:
https://dl.dropbox.com/u/102426750/XDA%20Dev/HTC%20Amaze.zip
Put these files in a folder in the root of your C drive. Once you cd into that folder with these files run the commands above
Click to expand...
Click to collapse
Thank you so much, i made an account just to personally thank you for this.
I was stuck on the Bootscreen for cm10 and couldn't figure out what was wrong, but i tried your reply And it worked for me.
Thank you so much sir.
Isn't 4EXT like... the *COUGH*BEST RECOVERY FOR HTC DEVICES*COUGH*
Hi All,
Long time lurker and I appreciate all the work everyone does here. It makes owning an android device a great amount of fun...but as you can see by the title of the thread, a great amount of stress as well :laugh:
My device is unlocked and I've used CWM and recenlty noticed that along one of my flashes TWRP 2.4 installed over CWM. All is well because I was meaning to switch over and try this recovery out. Smooth, fast, I like. But I recently installed CM 10.1 using the october version with the JB bootloader because I did not have it. Everything was nice, but I wanted to update CM 10.1 to a more recent UNOFFICIAL build so I flased the 3/20 version on my device. Everything was smooth but the WiFi dropped all the time so I decided to wait out a more stable "official" version of CM 10.1. Take note that I have(had) TWRP 2.4. Now I wanted to stick with JB 4.2.X so I decided to flash Energy's 3/21 build but this hung up on the ASUS screen... So I decided to reflash the rom but first installing the JB bootloader and partitions zip. Still no luck and while exiting TWRP, I noticed that it stated that my device isn't rooted and would I like to root? So I swiped and did it but it seems that the JB bootloader and partitions zip file erased everything on my device, Roms, GAPPS, SU, backups...gone.
The next thing I did was execute Urkels fresh root and fresh start and that seemed to go through all the steps with no issue. When I went back into recovery I noticed that I now have TWRP 2.2.2.1 with a JB bootloader... so what ever I did downgraded TWRP? Ok... Now I wanted to play it safe and stick to the October version of CM 10.1 with the JB bootloader but while flashing the rom (ext SDCARD) i receive an error. I decided to re-execute Urkels fresh root and fresh start and now all my device does is boot into TWRP 2.2.2.1. I can't use fastboot even with holding the power button and vol down.
At this point I feel lost and defeated, I can't use external SD anymore and I can only mount the system. So I decided to see if ADB works. ADB works great in recovery and am able to send files to the device. I sent a ROM to see if I can install but it fails because it can't mount the cache and this is where I am now. Lost... confused and desperate for help :crying: I'll make sure XDA gets a nice donation if anyone can help me out!
What works -
boot to TWRP 2.2.2.1 (thats all)
ADB in recovery
What doesn't-
No rom installed
No backup
No fastboot
My troubleshooting
Again ANY help is appreciated!
Mike
Would I be able to update TWRP within TWRP using a 2.4.4.0 zip file?
TheYoz said:
Would I be able to update TWRP within TWRP using a 2.4.4.0 zip file?
Click to expand...
Click to collapse
This is happening because you are now on 4.2.1 bootloader with an old TWRP which is not compatible with the new bootloader.
When you say you cannot access fast boot do you mean the usb icon is missing? If you do that is part of the new bootloader. As soon as you get to where the icons are you are automatically in fast boot unless you select one of the icons.
I'm out at the moment but if you reply letting me know that you can get to the icons I will post a file when I get back and some instructions to downgrade you to old bootloader and compatible TWRP.
flumpster said:
This is happening because you are now on 4.2.1 bootloader with an old TWRP which is not compatible with the new bootloader.
When you say you cannot access fast boot do you mean the usb icon is missing? If you do that is part of the new bootloader. As soon as you get to where the icons are you are automatically in fast boot unless you select one of the icons.
I'm out at the moment but if you reply letting me know that you can get to the icons I will post a file when I get back and some instructions to downgrade you to old bootloader and compatible TWRP.
Click to expand...
Click to collapse
I figured my TWRP version might have been the culprit...
When I restart and hold the vol down button it normally would activate fastboot, now it goes directly to TWRP, no icons whatso ever. Before I would get the recovery icon, a usb (I think) and an option to wipe data. I can't get to that screen anymore. Is there a command in adb that will allow me to restart to fastboot from recovery? I myself am at work too so I will test anything I can in 3 - 4 hours. Thanks for taking the time to respond! :good:
So basically I won't be able to put TWRP 2.4.4.0 within my current version of TWRP?
TheYoz said:
I figured my TWRP version might have been the culprit...
When I restart and hold the vol down button it normally would activate fastboot, now it goes directly to TWRP, no icons whatso ever. Before I would get the recovery icon, a usb (I think) and an option to wipe data. I can't get to that screen anymore. Is there a command in adb that will allow me to restart to fastboot from recovery? I myself am at work too so I will test anything I can in 3 - 4 hours. Thanks for taking the time to respond! :good:
So basically I won't be able to put TWRP 2.4.4.0 within my current version of TWRP?
Click to expand...
Click to collapse
The version of TWRP you have will not mount the partitions you need to flash anything. You either need to downgrade the bootloader so that version of TWRP will work or get the version of TWRP back on there that was edited to work with the new 4.2.1 bootloader.
When you installed that partition.zip from energy rom it installed the new bootloader and the compatible twrp the same time. To go back he also has a zip that will restore old bootloader and old twrp. This is what you should have done.
What I am worried about now is the fact that you cannot even get to fastboot from the buttons.
Try adb reboot bootloader.
If that lets you in then download this .. http://flumpster.lolcakes.com/android/blob and place it in your fastboot directory.
Now type.
fastboot -i 0x0B05 flash staging blob
wait for it to fully flash and then type
fastboot -i 0x0B05 reboot
Give it about 20 seconds, if it doesn't restart then you will have to hold the power button down for 10 seconds to force a restart.
When it restarts it should now start to fill the blue line on the Asus screen which will flash the old bootloader and compatible TWRP. If it does this then great, just wait until it has finished and it should put you back into twrp where you will be able to install a rom off your external SD.
If it does not do the blue line then we have bigger probs and I hope you have nvflash backup files.
flumpster said:
The version of TWRP you have will not mount the partitions you need to flash anything. You either need to downgrade the bootloader so that version of TWRP will work or get the version of TWRP back on there that was edited to work with the new 4.2.1 bootloader.
When you installed that partition.zip from energy rom it installed the new bootloader and the compatible twrp the same time. To go back he also has a zip that will restore old bootloader and old twrp. This is what you should have done.
What I am worried about now is the fact that you cannot even get to fastboot from the buttons.
Try adb reboot bootloader.
If that lets you in then download this .. http://flumpster.lolcakes.com/android/blob and place it in your fastboot directory.
Now type.
fastboot -i 0x0B05 flash staging blob
wait for it to fully flash and then type
fastboot -i 0x0B05 reboot
Give it about 20 seconds, if it doesn't restart then you will have to hold the power button down for 10 seconds to force a restart.
When it restarts it should now start to fill the blue line on the Asus screen which will flash the old bootloader and compatible TWRP. If it does this then great, just wait until it has finished and it should put you back into twrp where you will be able to install a rom off your external SD.
If it does not do the blue line then we have bigger probs and I hope you have nvflash backup files.
Click to expand...
Click to collapse
Crossing my fingers... I will try what you mentioned and no, I don't have NVFLASH. Something that I have been meaning to do for a few weeks now too. Thanks for the help I will update when I get a chance to try.
Mikw
TheYoz said:
Crossing my fingers... I will try what you mentioned and no, I don't have NVFLASH. Something that I have been meaning to do for a few weeks now too. Thanks for the help I will update when I get a chance to try.
Mikw
Click to expand...
Click to collapse
You cannot do the nvflash process now. You could only do it while on ICS and there is no way back to ICS without having nvflash backups.
flumpster said:
You cannot do the nvflash process now. You could only do it while on ICS and there is no way back to ICS without having nvflash backups.
Click to expand...
Click to collapse
I am able to adb reboot bootloader, and it brings me to fastboot!
I successfully executed the steps you gave me but I didn't get the android screen with the blue line... it went back to TWRP 2.2.2.1. Can I fastboot the new version of TWRP?
TheYoz said:
I am able to adb reboot bootloader, and it brings me to fastboot!
I successfully executed the steps you gave me but I didn't get the android screen with the blue line... it went back to TWRP 2.2.2.1. Can I fastboot the new version of TWRP?
Click to expand...
Click to collapse
Tried one more time with no success... Please let me know if I have any other options since I can get to fastboot via ADB.
I think the reason I am running into this mess is because I didn't download the JB update from ASUS and move the system.blob file according to Urkel fresh start
TheYoz said:
Tried one more time with no success... Please let me know if I have any other options since I can get to fastboot via ADB.
I think the reason I am running into this mess is because I didn't download the JB update from ASUS and move the system.blob file according to Urkel fresh start
Click to expand...
Click to collapse
I have even tried installing the TWRP.blob (newest JB version) file using this method but still reverts to version 2.2.2.1. I'm stumped
TheYoz said:
I have even tried installing the TWRP.blob (newest JB version) file using this method but still reverts to version 2.2.2.1. I'm stumped
Click to expand...
Click to collapse
I was worried about this. I have seen loads of people with the same problem you have over on the tf300 forums.
They can access fastboot thru adb reboot fastboot and it appears to send the file over ok but then it doesn't work.
When you mentioned you couldn't get to fastboot by holding button combo it looked like the same prob as them.
Have a look at this thread. http://forum.xda-developers.com/showthread.php?t=2179874
flumpster said:
I was worried about this. I have seen loads of people with the same problem you have over on the tf300 forums.
They can access fastboot thru adb reboot fastboot and it appears to send the file over ok but then it doesn't work.
When you mentioned you couldn't get to fastboot by holding button combo it looked like the same prob as them.
Have a look at this thread. http://forum.xda-developers.com/showthread.php?t=2179874
Click to expand...
Click to collapse
So I probably need to send it to ASUS or wait for a solution? That is for the TF300 would I be able to use any steps for that device with mine?
Also,
I purchased this in January 2012 from best buy, any possibility I can go through them to have this issue fixed?
TheYoz said:
I have even tried installing the TWRP.blob (newest JB version) file using this method but still reverts to version 2.2.2.1. I'm stumped
Click to expand...
Click to collapse
Flash the .img not the blob that should fix your issue.
Loco0729 said:
Flash the .img not the blob that should fix your issue.
Click to expand...
Click to collapse
I doubt it will but he can try.
No luck flashing the .img file instead. This is the worst
Flumpster thanks a bunch for all of your help. I ended up sending in the tablet, as expected they had to replace the motherboard.:
They quoted me this origionally:
Parts: $165
Labor: $65
Shipping $10
TOTAL $240!!!
I called and complained until my eyes popped out of my head and they ended up replacing the motherboad and shipped it back to me for $150. Now I think I'm going to sell this thing with the dock and buy a Nexus 10. Again, thanks for your help.
Another note... It will probably be a pain to unlock and root this thing again after the RMA im assuming. No more ASUS.
I was trying to create more space. I saw the apps folder and moved it to somewhere else. Then my phone started crashing, so i turned it off. When i turned it back on i got a bootloop. My phone is rooted and i have an alacatel one touch 983. It keeps showing the o2 logo. I think this is because there is no launcher. Help please
If you have adb set up then pull the app folder from where you put it and push it to system/app. I presume you don't have a custom recovery or nandroid backup.
sinkster said:
If you have adb set up then pull the app folder from where you put it and push it to system/app. I presume you don't have a custom recovery or nandroid backup.
Click to expand...
Click to collapse
I think i put it in custect (or a something like that) but not sure, can i just push a folder called app and then add the launcher?
Bump - Please help. CMD says error: device not found, but i have sdk. Im trying to change the driver but it keeps saying its up to date.
If you're not sure where you put the folder then using adb could be pretty tedious anyway... You'd need the whole file, the bootloop probably won't be caused solely by having no launcher. If you've got a custom recovery then flash the Aroma file manager to find/move the folder, or find a CWM/TWRP flashable home launcher. If not, then your best bet is probably to use One touch support to update your rom, i,e, reflash back to stock.
sinkster said:
If you're not sure where you put the folder then using adb could be pretty tedious anyway... You'd need the whole file, the bootloop probably won't be caused solely by having no launcher. If you've got a custom recovery then flash the Aroma file manager to find/move the folder, or find a CWM/TWRP flashable home launcher. If not, then your best bet is probably to use One touch support to update your rom, i,e, reflash back to stock.
Click to expand...
Click to collapse
Well, i have a system.img that i want to flash with fastboot. i also found an o2 rom for my phone. So if i could get adb or recovery mode to work i could restore it. I have a rough idea of where it is, so i could get it, but adb and fastboot don't recognise my device. I tried hard resetting it by holding the volume up button but im still stuck at the o2 screen. I have tried the alcatel driver but that doesn't work. It doesn't recognise it when i try to put it into recovery mode. If you know the combination for the alcatel 983 please say. Maybe it is because hard resetting it disabled usb debugging, but my pc recognises it fine. (cannot open sd card), but it recognises it and it's name. So i do not know why adb doesn't recognise it.
I'm not familiar with Alcatel phones, but it should be volume down while turning on for fastboot. If you can get into fastboot you should be able to flash a custom recovery.
sinkster said:
I'm not familiar with Alcatel phones, but it should be volume down while turning on for fastboot. If you can get into fastboot you should be able to flash a custom recovery.
Click to expand...
Click to collapse
Holding up while turning on makes it to hard reset and holding down does makes it freeze. So how can i make it work with adb on my pc. Should i try a different pc? There are no other buttons, it is touch screen.
Actually holding down while it says waiting for device works, testing some stuff out now thanks. will show my resuslts
When you switch on/press down, the freeze is the phone in fastboot (apparently), so try that, connect to your pc, open cmd window where you'd normally open adb and try 'fastboot erase cache' and see if you get a response. should return a message saying cache erased, or similar. If so, you're in fastboot and you can use it to flash a custom recovery (obviously one for your phone)
This post seems to be a similar issue/resolution. There's no custom recovery yet for the phone.
sinkster said:
When you switch on/press down, the freeze is the phone in fastboot (apparently), so try that, connect to your pc, open cmd window where you'd normally open adb and try 'fastboot erase cache' and see if you get a response. should return a message saying cache erased, or similar. If so, you're in fastboot and you can use it to flash a custom recovery (obviously one for your phone)
Click to expand...
Click to collapse
ok ill try thanks.
Well i done that, but now it is frozen at the o2 screen. I flashed boot, recovery and system img. Lower buttons work but its stuck at o2 screen. What do i do next?
Can you connect with adb yet?
sinkster said:
Can you connect with adb yet?
Click to expand...
Click to collapse
Nope still no adb, still saying device not found. Is there an adb mode that i can get to?
Adb needs the system to respond, out may be borked due to the move of the system/app folder. What commands did you use in fastboot? Fastboot flash system xxx.img?
sinkster said:
Adb needs the system to respond, out may be borked due to the move of the system/app folder. What commands did you use in fastboot? Fastboot flash system xxx.img?
Click to expand...
Click to collapse
Yes i did fastboot flash system/boot/recovery for each their img's. Well i am trying the alcatel one touch update now. Ill see if that fixes it. Ill report back when its done
ok, good luck.
sinkster said:
ok, good luck.
Click to expand...
Click to collapse
Well, that didn't work. Got any other tips? Im still stuck at o2 screen. Thanks
supernovakid said:
Well, that didn't work. Got any other tips? Im still stuck at o2 screen. Thanks
Click to expand...
Click to collapse
It has worked, thanks a lot for your help! You are a great person thanks!
No probs.
Hi all,
I was frustrated with the performance of stock ROM on my xperia sola and tried to flash it with custom ROM (CyanogenMod 11). Something went wrong. And now I can't boot device This is my firts try, so probably I did something wrong during the process.
What I did
In general I followed this procedure and did not managed to get to their step 12.
Details:
1. At first I unlocked bootloader (using official Sony procedure)
2. Then I iInstalled RecoverX from Play.
3. Then rooted the device.
4. Then downloaded stable CyanogenMod 11 (cm11.0-0-pepper.zip), copied it to SD card. I've also extracted boot.img and flashed it using fastboot (with no errors).
The problem
After the steps above the device does not boot. I see "sony xperia ste" screen, then it disappears and screen is grey.
I've tried to enter the recovery mode (by holding volume down button), but the result is the same - grey screen.
What I tried (and it did not worked)
I'm still able to enter fastboot mode. So I tried the step 4. with latest nightly build (cm11.0-14-pepper.zip). I've flashed boot.img successfully, but the result is the same (grey screen).
Any ideas what can be done to reanimate the device?
Thanks in advance!
lvivets said:
Hi all,
I was frustrated with the performance of stock ROM on my xperia sola and tried to flash it with custom ROM (CyanogenMod 11). Something went wrong. And now I can't boot device This is my firts try, so probably I did something wrong during the process.
What I did
In general I followed this procedure and did not managed to get to their step 12.
Details:
1. At first I unlocked bootloader (using official Sony procedure)
2. Then I iInstalled RecoverX from Play.
3. Then rooted the device.
4. Then downloaded stable CyanogenMod 11 (cm11.0-0-pepper.zip), copied it to SD card. I've also extracted boot.img and flashed it using fastboot (with no errors).
The problem
After the steps above the device does not boot. I see "sony xperia ste" screen, then it disappears and screen is grey.
I've tried to enter the recovery mode (by holding volume down button), but the result is the same - grey screen.
What I tried (and it did not worked)
I'm still able to enter fastboot mode. So I tried the step 4. with latest nightly build (cm11.0-14-pepper.zip). I've flashed boot.img successfully, but the result is the same (grey screen).
Any ideas what can be done to reanimate the device?
Thanks in advance!
Click to expand...
Click to collapse
Maybe try to hold vol up while "Sony Xperia STE" showing up.
Cwikla said:
Maybe try to hold vol up while "Sony Xperia STE" showing up.
Click to expand...
Click to collapse
Thanks for suggestion!
I've already tried it and it does not help
1) Have you unlocked the bootloader?
2) In the terminal could you try issuing a "reboot recovery" command?
OR
Hold the back button while booting..
Same problem
I have exactly the same problem, also with Cyanogenmod 11.
I'm not able to get in android or recovery, maybe there is a way to fix this in fastboot? (That's the only solution I can think of)
Thanks for your suggestions!
rlvl said:
1) Have you unlocked the bootloader?
Click to expand...
Click to collapse
Yes!
rlvl said:
2) In the terminal could you try issuing a "reboot recovery" command?
Click to expand...
Click to collapse
Could you, please, provide more details when should I run this command?
This is not working with fastboot, and I don't know of other options.
rlvl said:
Hold the back button while booting..
Click to expand...
Click to collapse
Back is "software" button on sola. Nevertheless, I tried holding it but this did not helped.
lvivets said:
Thanks for your suggestions!
Yes!
Could you, please, provide more details when should I run this command?
This is not working with fastboot, and I don't know of other options.
Back is "software" button on sola. Nevertheless, I tried holding it but this did not helped.
Click to expand...
Click to collapse
In adb try the "reboot recovery" command
rlvl said:
In adb try the "reboot recovery" command
Click to expand...
Click to collapse
Unfortunatelly adb is not able to connect to the device. Probably that's because the device does not not reach "far enough" in boot process.
Solution
What you've done wrong is to flash the boot image before the rom. As now the new boot images contain TWRP recovery, it loades after the rom is booted and the rom wont boot because of boot image mismatch. The solution is to use an older boot image which contains the CWM recovery which loads before the rom has even booted. Try THIS rom's boot image then flash the rom and then your new boot image.
HIt like if it helps :fingers-crossed: :highfive:
Solved
INDIAN-MAfIA said:
What you've done wrong is to flash the boot image before the rom. As now the new boot images contain TWRP recovery, it loades after the rom is booted and the rom wont boot because of boot image mismatch. The solution is to use an older boot image which contains the CWM recovery which loads before the rom has even booted. Try THIS rom's boot image then flash the rom and then your new boot image.
HIt like if it helps :fingers-crossed: :highfive:
Click to expand...
Click to collapse
Thank you!
Using AOSX boot.img I was able to get into TWRP recovery. I did not flashed CM11 yet, it's late night right now here.
Another solution is to flash experimental v12 kernel (ensure your version of android matches it!). For me it was 4.0.
This solution was proposed by @pippoaacc here. So, all credits go to him. Also he was very nice to explain me more details regarding the solution (which were not obvious to me).
Using this one I'm able to boot my stock android and use it. However I can't flash any ROM doe to CWM recovery errors.
Anyway. There are at least 2 ways to resolve original problem (gray screen after flashing boot.img from CM11).
So, I believe this thead is solved.
Hello,
I just purchased this phone knowing that it has this problem and I am trying to fix it but I do not know much about the original firmware or anything except of the following:
SKU: 6233A, MFG: 2014/05/30, HW: R1.6
I need to restore the Firmware and preferably be able to use the Dock Station (reason I bought it).
I also like to use it with T-Mobile and do not know if these phones are locket to ATT or not.
I am not a developer but have good technical knowledge.
Any advice will be appreciated.
Thank you
Mike
MH928 said:
Hello,
I just purchased this phone knowing that it has this problem and I am trying to fix it but I do not know much about the original firmware or anything except of the following:
SKU: 6233A, MFG: 2014/05/30, HW: R1.6
I need to restore the Firmware and preferably be able to use the Dock Station (reason I bought it).
I also like to use it with T-Mobile and do not know if these phones are locket to ATT or not.
I am not a developer but have good technical knowledge.
Any advice will be appreciated.
Thank you
Mike
Click to expand...
Click to collapse
Hopefully you can enter in to fastboot mode.
Try to reflash this ATT_userdebug rom from TWRP recovery, and then restore this backup.
1. Turn on the fastboot mode(vol up + power), plug in the cable to PC, open CMD, Boot in to twrp(fastboot boot recoveryyouchoose.img) and use "adb push filename.zip /sdcard"
2. install .zip then reboot
3. boot up, then boot back to TWRP recovery, make a backup.
4. boot up, copy the downloaded backup, boot back to recovery
5. restore it.
hope it works
paleszgergo said:
Hopefully you can enter in to fastboot mode.
Try to reflash this ATT_userdebug rom from TWRP recovery, and then restore this backup.
1. Turn on the fastboot mode(vol up + power), plug in the cable to PC, open CMD, Boot in to twrp(fastboot boot recoveryyouchoose.img) and use "adb push filename.zip /sdcard"
2. install .zip then reboot
3. boot up, then boot back to TWRP recovery, make a backup.
4. boot up, copy the downloaded backup, boot back to recovery
5. restore it.
hope it works
Click to expand...
Click to collapse
The second link (to restore) redirects to another Thread but most of the links there do not work, can you send me a direct link to the file?
MH928 said:
The second link (to restore) redirects to another Thread but most of the links there do not work, can you send me a direct link to the file?
Click to expand...
Click to collapse
I think he meant these for the second link.
http://forum.xda-developers.com/showpost.php?p=60403709&postcount=34
Edit: you must use twrp to flash these backups after user debug.
Justatechie said:
I think he meant these for the second link.
http://forum.xda-developers.com/showpost.php?p=60403709&postcount=34
Edit: you must use twrp to flash these backups after user debug.
Click to expand...
Click to collapse
Yeah, thats what i mean!
Please help. the same problem. Invalid boot. TWRP recovery i have already. please help step by step...
(why invalid boot? i flashed new recovery from Quarx to a boot partition )
Sirocco.ukr.lviv said:
Please help. the same problem. Invalid boot. TWRP recovery i have already. please help step by step...
(why invalid boot? i flashed new recovery from Quarx to a boot partition )
Click to expand...
Click to collapse
Is your Bootloader unlocked?
Justatechie said:
Is your Bootloader unlocked?
Click to expand...
Click to collapse
Locked bootloader. Where i can see for sure?
When VolUp+Power i can see this window
I need adb driver.
TWRP that i have on this phone is old one ported from nexus device and it can't see SD card.
Sirocco.ukr.lviv said:
Locked bootloader. Where i can see for sure?
When VolUp+Power i can see this window
I need adb driver.
TWRP that i have on this phone is old one ported from nexus device and it can't see SD card.
Click to expand...
Click to collapse
To find out, you have to put your phone into fastboot.
To do that power down your phone, then hold volume up and power button at the same time. There, the asus logo will pop up like normal and hang on that screen to show that you are in fastboot mode.
Open up command prompt and verify your device is connected, by typing in fastboot devices.
If it shows up good then all you have to do is type in fastboot oem device-info.
If it says device unlocked: true that means your BL is unlocked.
If its not, you have to download crowlock from the cm12 thread and flash it.
It works better with cwm but since you are stuck its worth a shot to flash it under old twrp.
Then check the BL status again, if its good great.
You could restore your device from some backups posted or if you could find a boot.img from the stock image, you could use the new version of twrp to flash the boot image under image flashing.
This is the adb/fastboot driver I use http://forum.xda-developers.com/showthread.php?t=2588979
Justatechie you are only one who help. i appreciate it. god bless you!
i've done it. unlocked already. i watched bootloop so i wiped everything. what rom to install?
del
Nice to hear that.
Well it depends if you want to install one or you want to keep it stock.
For keeping it stock unfortunately you must restore from backups posted.
If its custom well Cm is a good way, just the dock does not work, but it will work hopefully soon when the developer receives it soon.
Justatechie said:
Nice to hear that.
Well it depends if you want to install one or you want to keep it stock.
For keeping it stock unfortunately you must restore from backups posted.
If its custom well Cm is a good way, just the dock does not work, but it will work hopefully soon when the developer receives it soon.
Click to expand...
Click to collapse
My asus padfone x T00D with full wipes identifies like T00N (padfone s) and reboots on first welcome screen on your rom...
please see video:
https://www.youtube.com/watch?v=aMB9Ctvrk0Q
Sirocco.ukr.lviv said:
My asus padfone x T00D with full wipes identifies like T00N (padfone s) and reboots on first welcome screen on your rom...
please see video:
https://www.youtube.com/watch?v=aMB9Ctvrk0Q
Click to expand...
Click to collapse
Dont worry about the asus_toon, it will turn back into padfone x when you are finally able to restore to the at&t factory rom
What is very strange,is that you cannot wipe certain things, I guess It may be due to a tampered bootloader. (something must have tripped it up)
My bootloader is unlocked but not tampered.
But the reason why it says ASUS_T00N is because you installed cm or miui and it changed build prop and the partitions. (all of quarx roms are built from the pfs source but work on the pfx too) its not a big deal don't worry.
Have you tried any other recoveries, perhaps the older version of twrp Here
Try booting them through fastboot using the fastboot boot filename.img (of the recovery file that should be located inside a folder containg fastboot/adb files)
See if they can wipe cache data(no media) and system. Remember, booting from fastboot is just temporary
Then try flashing a rom, doesnt matter what it has to be but it should work after its done. Maybe flash without gapps, it could sometimes cause a random problem and besides you can always install it later.
I never had to use fastboot to wipe cache either because well I could do that in recovery, plus its safer