PLEASE IGNORE THIS QUESTION, IT IS SOLVED, IF A MODERATOR SEES THIS, PLEASE DELETE THE THREAD
Hi.
Today I wanted to install Lolliop for my Z2, and created a .ftf and then used PRFCreator to root it. I then got a zip file "Flashable.zip". I put it onto my SD card, and was ready to flash it. When I tried to boot into recovery, it was just stuck at the Sony Logo. The light turned green, I spammed the down volume and the light turned purple.
Why can't I get into recovery?
I have eXistenz ROM installed, and I am using nuts dual recovery. So I know that the recovery is installed. It worked perfectly before..
Thanks for any help(and sorry for the english )
edit the title to say [Solved]
so how was this solved? i am on the same rom and i cant get into recovery or bootloader, even though they are apparently there
OP, please don't leave us with the problem you have hanging. How were you able to get recovery back on the rooted stock lollipop build?
Related
hey guys, searched the forum, found some stuff matching my post but figured i would put out an update. just rooted tonight, ive done these before and i used to be a member awhile ago but forgot what email used. anyway, galaxy s2 sch-r760. recovery problem. CWM doesnt seem to offer a proper recovery and im new to using odin so im not sure where to go from here. how can i go about making a backup if i cant get into recovery? i would like to do a new rom and back this thing up asap. need a new recovery or ideas for one. any help would be appreciated guys!
You need to expand on this.What did you do to root,do you have stock or cwm recovery?
Followed http://forum.xda-developers.com/showthread.php?t=1928566 to root. Its a generic CDMA. Root went fine. It tells me that it has root access. I am trying to flash CWM recovery and it won't boot into recovery from the CWM option. It shows the unpacking screen for a few seconds then reboots. As of now I am assuming its stock recovery because I can't get it to boot into recovery from CWM like I was saying
Tried doing a manual boot into recovery and it turned on, said galaxy s2, turned off then rebooted. Its acting like there is no recovery at all....
No help on this guys? Anybody mod generic s2 before?
hi guys,
my find 5 was having some reboot issues (it was rebooting a few times per day) and that was a bit anoying. I was using an old original FW so i decided to update to a newer one. Heard good stuff about the Omni so i went for that, so i was using TWRP 2.4.1.0 (i think... i'm sure it was 2.4.x) and on the omni page they said we have to use TWRP 2.6 so i went for an update.
here, i think, i've created my problem. I used the new flashify app to install the TWRP but instead of choose recovery img i choosed to flash the boot and i guess i'd flashed the TWRP on the boot.
well anyaway, now i'd installed the TWRP 2.6.3.1 i manage to start the phone in fastboot and recovery all good here, i install every rom nice and easy over TWRP but the phone simply doesn't start, it gets stuck on Touchscreen Firmware Update please wait.... this happens ALWAYS with what version of TWRP or even if i install CWM...
my guess is that i'd messed up some partition or so i don't really know what but i'd tried to format every partition that TWRP let me and still getting the freackin Touchscreen Frim updt screen... so need some Pro help to help me undo the mistake i'd done...
i'd tried to manualy flash the boot with my current firms boot.img and still no go... the damn touchscreen update screen keeps showing on no matter what....
thanks for everything
i change the firmware and start logo changes too so booting it's changing why the hell the touchscreen update keeps appearing... grrrrr i even installed a chinese firmware and a equivalent screen appeared i'm pretty sure it says: "Touchscreen Firmware Update in Progress Please Wait" but in chinese XD really don't know what to do anymore...
some ideas please?
i just don't know what to do anymore... does anyone knows what makes the phone try to update the touchscreen firm? today i installed the CWM in boot not in recovery just to test if the damn thing would go to the touch updt screen again and it just boot to the CMW like it should (normal because i'd flashed the CMW in the boot place). now i flash a new firmware (that will flash the correct boot.img) and the thing keeps holding on the touch update... i'm really out of ideas now
one other thing it's that if i install the TWRP in boot it won't boot in TWRP like it shoul... it stucks on oppo logo.
well i managed to install the same firm i had and have no touchscreen update... but if i install any other firm the message appear...
long story short, I bricked my device after I installed the GPE on my non Google edition i wanted to go back to monx rom, so I went into recovery did advance wipe and deleted everything except the external sd card.
When I wanted to flash the rom in twrp it was unable to flash so now I am stuck with a non functioning phone, with the google words on the screen and the device does not turn off.
I wanted to flash an ftf using flashtool, but it does not get recognized as I can't enter flashmode
So please help
hykhleif said:
long story short, I bricked my device after I installed the GPE on my non Google edition i wanted to go back to monx rom, so I went into recovery did advance wipe and deleted everything except the external sd card.
When I wanted to flash the rom in twrp it was unable to flash so now I am stuck with a non functioning phone, with the google words on the screen and the device does not turn off.
I wanted to flash an ftf using flashtool, but it does not get recognized as I can't enter flashmode
So please help
Click to expand...
Click to collapse
Can you power off the phone by long pressing power and volume up together?
finally solved it, it took me 4 hours, fumbling around
i could not even turn off the phone, I did so many things that all I can say be careful when u revert back from GPE to sony rom
You really like to overdramatize everything don't you? It wasn't bricked. The problem is you not reading before you do anything.
What I would of done is flash a 209 base rom via twerp etc recovery and then use flash tool to flash stock 209 sony firmware which should work.
After I attempted to install the CM 11 preview that just came out it seems as though I get stuck in a boot loop. I am able to get into the bootloader but not the recovery. The reason I think I am stuck in the boot loop is because I did not know you had to flash the boot.img that was inside the .zip file, and went ahead and flashed the .zip in my current recovery. I am just wondering if I could still fastboot flash the boot.img file without causing even more problems.
Yes, in the forum the ROM was posted (http://forum.xda-developers.com/xperia-z2-tablet/orig-development/z2-tabletdevelopment-cm11-android-4-4-t2809793) but I guess I didn't see that he said it was in the zip :silly:.
Nonetheless, I just don't want to hard brick the device so that is why I am asking. Thanks in advance for anyone that can help!
cmd-line34 said:
After I attempted to install the CM 11 preview that just came out it seems as though I get stuck in a boot loop. I am able to get into the bootloader but not the recovery. The reason I think I am stuck in the boot loop is because I did not know you had to flash the boot.img that was inside the .zip file, and went ahead and flashed the .zip in my current recovery. I am just wondering if I could still fastboot flash the boot.img file without causing even more problems.
Yes, in the forum the ROM was posted (http://forum.xda-developers.com/xperia-z2-tablet/orig-development/z2-tabletdevelopment-cm11-android-4-4-t2809793) but I guess I didn't see that he said it was in the zip :silly:.
Nonetheless, I just don't want to hard brick the device so that is why I am asking. Thanks in advance for anyone that can help!
Click to expand...
Click to collapse
Just to clarify first, do you have a 4G tablet or wifi version? And which one did you flash (castor or castor_windy)
kbroh said:
Just to clarify first, do you have a 4G tablet or wifi version? And which one did you flash (castor or castor_windy)
Click to expand...
Click to collapse
Opps, meant to mention that. I have the castor_windy version (Wi-Fi) model and flashed the castor_windy zip. I also meant to mention that I have an unlocked bootloader with the CWM based recovery (found here: http://forum.xda-developers.com/showthread.php?t=2708194). I don't think this is as important but I do have the 16GB storage. I earlier said I could not get into that recovery that I have installed, but the violet light still goes on when I boot, but nothing else.
cmd-line34 said:
Opps, meant to mention that. I have the castor_windy version (Wi-Fi) model and flashed the castor_windy zip. I also meant to mention that I have an unlocked bootloader with the CWM based recovery (found here: http://forum.xda-developers.com/showthread.php?t=2708194). I don't think this is as important but I do have the 16GB storage. I earlier said I could not get into that recovery that I have installed, but the violet light still goes on when I boot, but nothing else.
Click to expand...
Click to collapse
Ok no problem, Have you tried flashing CWM through fastboot, then reinstalling ROM through CWM?
If that can't be done, Can you flash this castor_windy version https://mega.co.nz/#!mJ5VTATR!Rb9pX0a4drAkVX53Mjf6_vZr8FqX0UzXcf1nSTzj_Fk
through fastboot, then immediately flash CWM to secure a recovery.
The link is the castor_windy ROM without having to flash a boot.img separately. Thats your safest solution instead of flashing boot.img
Thank you, just re-flashing the recovery from the thread I linked seemed to do the trick. Maybe I will try and flash Cyanogenmod later now that I got the stock ROM working again. At least I was smart enough to make a nandroid backup in CWM before hand though!
Again, thanks alot!
cmd-line34 said:
Thank you, just re-flashing the recovery from the thread I linked seemed to do the trick. Maybe I will try and flash Cyanogenmod later now that I got the stock ROM working again. At least I was smart enough to make a nandroid backup in CWM before hand though!
Again, thanks alot!
Click to expand...
Click to collapse
Good to hear!
Sent from my Xperia Z2 Tablet Wifi using XDA Premium 4 mobile app
Hi all,
bad day for me... It seems that I bricked my Z2 Tablet tonight.
At the beginning, I just wanted to install CM11.
My Z2 is a SGP512 Wifi only. So, regarding the page http://www.xperiablog.net/2014/07/12/cyanogenmod-11-nightly-builds-start-for-xperia-z2-tablet/ , it says : "There are currently nightly builds for the Wi-Fi variants (SGP511, SGP512) of the Xperia Z2 Tablet under codename “Castor Windy”" .
So I downloaded Castor Windy and put it in the tablet.
After that, I did had to install a recovery. I succeeded to install XZDualRecovery (http://forum.xda-developers.com/showthread.php?t=2794175). Once installled, I went into TWRP Recovery , started to wipe all. And next step, I began to install zip Castor Windy. At this time, TWRP tells me that Castor Windy is not for my tablet model. And I have to use Castor. Problem. I wiped all. So, I have to mount the Tablet systems and drives to put the new Castor zip downloaded. But I'm unable to mount. Nothing is mounted. I tried to use adb to connect while I was in TWRP but nothing worked. I wanted to use adb to send on one of partitions the new downloaded rom. I was unable to do that.
Finally, I shut down my tablet. I took the SD Card to put it into my PC and to put on it the downloaded Rom. And when I wanted to restart the Tablet, only the Sony Logo appears and I'm not anymore able to enter in recovery mode. ADB and Fastboot fail to detect my tablet.
I'm totally lost, and I fear that all is lost.
Please, help me, I just would like to enter recovery and flash Castor Rom.... :crying:
Thanks a lot by advance.
Tom.
See this thread: http://forum.xda-developers.com/xpe...ed-tablet-tried-to-install-cm-failed-t2838765
Good luck :good:
It seems a bit trendy to mess with the recovery, resulting in a brick or bootloop.
Just making a new thread cause my case is a bit different.
I was on Existenz 4.7.0 when I decided to flash 5.0.
Wasn't a clean install, resulted in some app fc'ing and restarting, so i went back to trwp and used my backup, keeping in mind to come back and make a clean install when I can take the time it needs.
Made a few backups today and wanted to start the trwp backup when I realised that I wasn't able to enter recovery.
Installed the trwp app, which wasn't able to reflash the recovery.
So I read another posting and I decided to delete the chargemon and rename the chargemon.stock, but that wasn't that smart, I decided later.
So back home I downloaded the dual recovery software from NUT's website to totally reinstall the recovery. After some ADB trouble I managed to get everything running, the batch file installed the recovery, everything looked pretty, at the end of the process the Z2 rebootet and e voila, I'm stuck in bootloop, clueless.
When I power the phone you can feel the first small vibration, then the Sony logo appears, stays, and it reboots.
Reset Button, powering on and holding Volume up isn't doing anything, so is Volume down.
What can I Do?
I know I made a few mistakes, but help is still needed!
Bro, Please read carefully before installing recoveries.
Nut's Recovery is NOT for Marshmallow. and it will cause bootloop and same problem you encounter here.
Only Solution is to flash via flashtool and re-root.(personally i would flash a kitkat .ftf then root it with any of the available methods. you can try kingroot it is the easiest) after that install Nut's recovery and flash your MM rom which will come with its own working recovery.
Oh, ok, so thats the cause. Didn't know that, shame on me.
So Existenz 5 messed up my recovery and maybe the silly try of reflashing killed it totally or just the bootloader.
So I will try to setup a Win7 PC and setup flash tool properly (didn't seem to work on win10)
Thanks for that finger point I the right direction
Flashtool works on windows 10 no problem for me.
Just install the right drivers and install 0.9.18.6 version of flashtool and try different drivers it shall work
Will do, thanks a lot. Seems to me that I had a 4.7 Existenz Rom with bootloader/recovery from MM, which I destroyed.
Is it possible to reflash the old bootloader? Or will flash tool spare my datas on internal SD card?
why to flash a boot loader?? is your device unlocked bootloader??
It's locked.
So it can't be a broken bootloader?
So it's just because the recovery is messed up?
JackDCalloway said:
It's locked.
So it can't be a broken bootloader?
So it's just because the recovery is messed up?
Click to expand...
Click to collapse
yes bro don't worry.
It seems that you are new to sony or you re coming from samsung or any other device with recovery partition.
By default, Sony doesn't have a recovery partition like in samsung. that is why developers made the recovery a part of the system (your ROM) the chargemon files are the one responsible for the recovery. so when you install a recovery it is like you are installing a system application which can be messed up if it is not compatible with your rom version.
PS:Be carefull never wipe the system partition from recovery and restart your phone before installing a new rom because if you restart without having installed your rom your phone won't have a recovery(part of the rom) neither a system----> Bootloop and need to reflash.
you can unlock your bootloader and make a recovery partition and install aosp roms. but on sony once you unlock your bootloader you will loose a lots of features and camera enhancements. so better keep it Locked and use stock based roms like existenz and MIUI roms which are stock based.
I hope i have been able to clarify all
OK, makes sense.
Seems like I'm still pretty new to Sony. Came from Samsung last December, just got enough knowledge to flash and improvise, quick and dirty.
So if I could get hands on my old chargemon file, (from when I didn't tried to install Existenz 5) I may get the Z2 running again?
Of course a pretty clean install afterwards.
Just asking, cause of backup reasons
Edit: I knew that unlocking the BL has a few disadvantages. I'm happy with Existenz but now I know a few things more, thanks michel090428
it is very difficult now even if you have the chargemon file. i don't know what could be messed up with the system. go for a clean flash it is the most safe way to do it.
Read this guide if you want a help with flashing it is very easy and detailed. and remember it is better to flash kitkat .ftf as it is easily rootable.
http://www.gizmobolt.com/2015/04/09...z3-23-1-a-0-690-ftf-using-flashtool-manually/
Hey folks, I'm back again!
Managed to setup a Win7 PC, installed the correct drivers, setup Flashtool, found correct ftf file and so on.
Problem is that I'm only able to get into fastboot mode with my Z2, for me it seems like Flashtool won't work when the device is only in fastboot mode.
What can I do?
why you can't start your device with flashmode?
You need to shutdown the device then when flashtool ask you to start in flash mode you press volume down(keep pressed then you plug in USB cable and it should start in flash mode directly.
have you tried to follow the guide i posted in the first page? where are you stuck? which step?
michel090428 said:
why you can't start your device with flashmode?
You need to shutdown the device then when flashtool ask you to start in flash mode you press volume down(keep pressed then you plug in USB cable and it should start in flash mode directly.
have you tried to follow the guide i posted in the first page? where are you stuck? which step?
Click to expand...
Click to collapse
Was a bit tricky, did the 'vol down + plug in' thing several times and it worked suddenly, flashtool flashed the ftf. Now it's FCing several tasks while it would do the android setup. Trying to flash a 4.4.2 ROM now, thanks for patience and help, appreciated this!
WIPE DATA
JackDCalloway said:
Was a bit tricky, did the 'vol down + plug in' thing several times and it worked suddenly, flashtool flashed the ftf. Now it's FCing several tasks while it would do the android setup. Trying to flash a 4.4.2 ROM now, thanks for patience and help, appreciated this!
Click to expand...
Click to collapse
You re Welcome Bro,
Concerning the FC You need to check the WIPE DATA option in flashtool i think it will solve the FC's
I'm with 23.1.A.1.28 now and it's fine. Just need to get root, there should be an exploit but it's not working for me, reasons unknown. Going to have a look at it later. Want to flash Existenz, that's the goal.
Bro , Use KINGROOT it is able to root .28 firmware.
there is a thread here for kingroot.