Related
Hello guys,
as a last resort I turn to you for help. Have been searching for the answer for the last 2 days. I am running CWM-based Recovery v.6.0.1.1 and have a rooted x10 together with an unlocked bootloader. I flashed the recovery without any problems and installed miui v4 but an older file which was very unstable (without any problems). Then I decided to install the newer version so i downloaded it, placed it on my sdcard and in the same recovery flashed rom. Unfortunately I had my usb cable plugged in all the time (during installation). Installation got stuck in the middle and nothing could be done so i removed the battery and started the phone again (this time without the usb cable). When I tried to reinstall that rom again it gave me status 7 error installation aborted, assert failed:getprop,error in sdcard and things like that. So I tried the ROM which had already worked on my phone but received exactly the same message. What is more usb storage mounting in the recovery doesnt work anymore (but it already worked!). Now the problem is that I don't have any system installed and when i try to flash the recovery again, flashtool does not recognize my phone (so does windows) and so it leads me nowhere. I think this is definitely problem with the recovery, after the failed attempt to install rom when i had to remove the battery it does not behave normally. Is there any way that I can maybe install another recovery from .zip - i do not even know whether it will install or just sends me another error. Any help would be greatly appreciated
SqU33z3R said:
Hello guys,
as a last resort I turn to you for help. Have been searching for the answer for the last 2 days. I am running CWM-based Recovery v.6.0.1.1 and have a rooted x10 together with an unlocked bootloader. I flashed the recovery without any problems and installed miui v4 but an older file which was very unstable (without any problems). Then I decided to install the newer version so i downloaded it, placed it on my sdcard and in the same recovery flashed rom. Unfortunately I had my usb cable plugged in all the time (during installation). Installation got stuck in the middle and nothing could be done so i removed the battery and started the phone again (this time without the usb cable). When I tried to reinstall that rom again it gave me status 7 error installation aborted, assert failed:getprop,error in sdcard and things like that. So I tried the ROM which had already worked on my phone but received exactly the same message. What is more usb storage mounting in the recovery doesnt work anymore (but it already worked!). Now the problem is that I don't have any system installed and when i try to flash the recovery again, flashtool does not recognize my phone (so does windows) and so it leads me nowhere. I think this is definitely problem with the recovery, after the failed attempt to install rom when i had to remove the battery it does not behave normally. Is there any way that I can maybe install another recovery from .zip - i do not even know whether it will install or just sends me another error. Any help would be greatly appreciated
Click to expand...
Click to collapse
Flash tool recognize your phone? if yes flash any stock firmware and start over
quintas84 said:
Flash tool recognize your phone? if yes flash any stock firmware and start over
Click to expand...
Click to collapse
When I want to flash .tft file and i go to flash mode it does not recognize my phone in windows even though I have installed all the necessary drivers. It starts to flash but then says flashing aborted (this did not happen before, i could flash without any problems). Another problem is that i do not have any rom installed right now so i cannot even switch debugging on and if i remember right, i left debugging off in my previous rom.
Use Sony Update Service. Download from Sony site and install on PC. Follow the instruction, and this will reflash Stock Rom and Kernel (GB 2.3.3). Then, with latest Flashtool, first Root phone again, then flash whatever you want (custom kernels, roms..). You don't need to unlock bootloader again. It remains unlocked.
Sent from my X10i using xda premium
Dzufa said:
Use Sony Update Service. Download from Sony site and install on PC. Follow the instruction, and this will reflash Stock Rom and Kernel (GB 2.3.3). Then, with latest Flashtool, first Root phone again, then flash whatever you want (custom kernels, roms..). You don't need to unlock bootloader again. It remains unlocked.
Sent from my X10i using xda premium
Click to expand...
Click to collapse
Omg - I found solution to my problem - I just changed usb port and it started to flash even using flashtool. Still, many thanks since it helped me find solution
I am a new Transformer Prime user, but not new to Android. My Prime is stuck on the initial "ASUS" splash screen (with NVIDIA logo).
I got my TFP yesterday and decided to put CM10 on it to see if it would fix the lag I was having (came with JB 4.1.1). Since it came with JB, I knew I couldn't use nvflash so I used the ASUS unlock tool which worked fine. I then downloaded TWRP 2.4.1 and flashed the JB blob file via fastboot.
Upon entering TWRP for the first time, everything seemed fine. I went in, did a backup (which I subsequently deleted by mistake) and wiped cache/dalvik/data/system and installed the official CM10 nightly. After flashing, I wiped cache/dalvik again and rebooted.
EDIT: So I flashed the Unofficial CM 10.1 here on XDA and it is now booting. So is the official CM 10 not for our devices with the JB BL?
Official CM10 nightlies are still made for the ICS bootloader, as you discovered. Until they update, you're better off downloading the unofficial builds here.
thefsfempire said:
I am a new Transformer Prime user, but not new to Android. My Prime is stuck on the initial "ASUS" splash screen (with NVIDIA logo).
I got my TFP yesterday and decided to put CM10 on it to see if it would fix the lag I was having (came with JB 4.1.1). Since it came with JB, I knew I couldn't use nvflash so I used the ASUS unlock tool which worked fine. I then downloaded TWRP 2.4.1 and flashed the JB blob file via fastboot.
Upon entering TWRP for the first time, everything seemed fine. I went in, did a backup (which I subsequently deleted by mistake) and wiped cache/dalvik/data/system and installed the official CM10 nightly. After flashing, I wiped cache/dalvik again and rebooted.
EDIT: So I flashed the Unofficial CM 10.1 here on XDA and it is now booting. So is the official CM 10 not for our devices with the JB BL?
Click to expand...
Click to collapse
I'm at the same screen, got there a lil different then you but along the same lines. I've switched out roms alot with no issues, but after flashing jellybean, i haven't been able to boot into recovery by power + vol down button. So i tried going into goo manager to boot into recovery and since then its just sitting at the first screen with this device is unlocked in the top left corner and nv in bottom left. When i hold the power button to reboot it, it just comes right back. Even when i let the battery die and try'ed it after that its just the same thing. Is there any hope out there for me?
foxhound08 said:
I'm at the same screen, got there a lil different then you but along the same lines. I've switched out roms alot with no issues, but after flashing jellybean, i haven't been able to boot into recovery by power + vol down button. So i tried going into goo manager to boot into recovery and since then its just sitting at the first screen with this device is unlocked in the top left corner and nv in bottom left. When i hold the power button to reboot it, it just comes right back. Even when i let the battery die and try'ed it after that its just the same thing. Is there any hope out there for me?
Click to expand...
Click to collapse
Can you access the stock recovery menu? If you can, you might be able to flash a custom recovery using fastboot.
Voyager2k said:
Can you access the stock recovery menu? If you can, you might be able to flash a custom recovery using fastboot.
Click to expand...
Click to collapse
No i can't access anything.
foxhound08 said:
No i can't access anything.
Click to expand...
Click to collapse
I am also stuck at this screen. I have access to nothing including adb, fastboot, recovery, bootloader, and everything else. All I did was use the asus bootloader unlock apk, fastboot flash recovery clockwork.img, boot back into android normally, and then I reboot into the bootloader wiped data, and now it is stuck.
dunngh said:
I am also stuck at this screen. I have access to nothing including adb, fastboot, recovery, bootloader, and everything else. All I did was use the asus bootloader unlock apk, fastboot flash recovery clockwork.img, boot back into android normally, and then I reboot into the bootloader wiped data, and now it is stuck.
Click to expand...
Click to collapse
Same here. I unlocked it and flashed CWM. For a while I used the tablet without any custom rom nor any problem, however it just stopped booting suddenly. I dont know what to do.
eec_ said:
Same here. I unlocked it and flashed CWM. For a while I used the tablet without any custom rom nor any problem, however it just stopped booting suddenly. I dont know what to do.
Click to expand...
Click to collapse
same here as well so at least you guys arent alone does show up as an apx device but not sure how useful that could be at the moment its just a paper weight just need someone to write an automated recovery from apx mode to flash the appropriate files if thats even possible
Exact same problem. Still no fix?
Just developed the same problem after installing Androwook2.2. Flashed the JB bootloader, then flashed the rom, after completing the initial Android setup the tablet started to download updates, which then froze. The screen stopped responding to any inputs, only the power and volume buttons did anything, but wouldn't restart it.
I hit the reset button with a pin which allowed me to enter recovery, which also didn't respond to screen touches, another reset button hit and there's now no USB connection in bootloader
Another restart and I can't get into bootloader either.
So no recovery or ADB = paperweight unless someone finds a solution
swatsbiz said:
Just developed the same problem after installing Androwook2.2. Flashed the JB bootloader, then flashed the rom, after completing the initial Android setup the tablet started to download updates, which then froze. The screen stopped responding to any inputs, only the power and volume buttons did anything, but wouldn't restart it.
I hit the reset button with a pin which allowed me to enter recovery, which also didn't respond to screen touches, another reset button hit and there's now no USB connection in bootloader
Another restart and I can't get into bootloader either.
So no recovery or ADB = paperweight unless someone finds a solution
Click to expand...
Click to collapse
Your problem was different to theirs and you have been fixed in the Androwook thread. Yours was caused by the pad firmware not installing properly the first time and freezing your screen and buttons.
I have the same problem...
hbhorat said:
Exact same problem. Still no fix?
Click to expand...
Click to collapse
any fixes to this ?
sraghav20 said:
any fixes to this ?
Click to expand...
Click to collapse
Me too.. looking for a fix on this with no luck so far
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.
I have a SGP311 and started to root by following the guide at http://forum.xda-developers.com/xperia-tablet-z/development/root-sp321-ftf-10-5-1-0-283-t2873377. Works prefectly! Unlocked using the guide at http://wiki.cyanogenmod.org/w/Install_for_pollux_windy which also worked.
But once I flashed the boot.img it start bootlooping. The option "backup and restore" isn't visable in the recovery mode. I can't find install from zip either. I can install from external storage, but that doesn't work either.
I managed to get in to the tablet again by replacing the boot.img to another boot.img, but that doesn't help me to get CyanogenMod 12 though.
I'm new to this, so I might have made something wrong here, please tell me if so
I have a little problem of my own also when I try to unlock the bootloader following the Sony web page everything looks ok but when I boot the tab it's stuck in a bootloop at the xperia logo.....
i had the same issue, once i tried to flash the boot.img from the cyanogen site, it stopped working and went into a boot loop. Here is how I fixed it.
Hold Power + Volume Up until the LED light flashes 3 times in a row. this does a hardware reset and shuts down the tablet.
THen from there i basically just went through the flashing process again to restore it. That brought it back for me.
I think the reason is that the boot.img on the cyanogen website is expecting the stop kernel, but when we flash it using that guide, it is using the FOTA kernel. So it gets tripped up some how. I am still looking around on how to get around it.
skift said:
i had the same issue, once i tried to flash the boot.img from the cyanogen site, it stopped working and went into a boot loop. Here is how I fixed it.
Hold Power + Volume Up until the LED light flashes 3 times in a row. this does a hardware reset and shuts down the tablet.
THen from there i basically just went through the flashing process again to restore it. That brought it back for me.
I think the reason is that the boot.img on the cyanogen website is expecting the stop kernel, but when we flash it using that guide, it is using the FOTA kernel. So it gets tripped up some how. I am still looking around on how to get around it.
Click to expand...
Click to collapse
it seems that you just haven't unlocked you bootloader or using boot.img with broken recovery.
The bootloader was unlocked fine. Went through Sony to get the code and unlock it. I was even able to flash Previously using flashtool. I re ran the flashing to get back to where I was and tried it again and it seemed to work. The only way I could reboot was to hold power and volume up till I got the 3 flashing lights. Then I could get into recovery.
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.