Database Develop

Problem with flashing & booting recovery? Go here!

Hey guys,
when I tried flashing CWM on my new HTC One it just booted in normal mode over and over.
I tried every recovery-image available and it nerver worked.
While playing around I finally got it working without flashing the recovery image to the boot partition!
No need to copy root files and CFW files before flashing the recovery!
Instructions
Unlock your device at http://www.htcdev.com/bootloader/
Reboot into bootloader
> fastboot flash boot boot.img - thanx to Paul O'Brien
> fastboot reboot-bootloader
> fastboot flash recovery recovery.img - thanks to Flyhalf205
> fastboot erase cache
After this you should be able to enter recovery via bootloader or 'adb reboot recovery'.
The recovery image is CWM Touch 6.0.2.8 which worked great for me, didn't try the other ones right now.
I hope I could help

I had issues booting recovery if I used the All in One kit to flash recovery.
So people should flash it manually instead to avoid problems.

Nekromantik said:
I had issues booting recovery if I used the All in One kit to flash recovery.
So people should flash it manually instead to avoid problems.
Click to expand...
Click to collapse
I had problems with AiO-Kit and doing it manually, too.
Only this method worked for me.

zantekk said:
I had problems with AiO-Kit and doing it manually, too.
Only this method worked for me.
Click to expand...
Click to collapse
Ah ok.
only issue for me now is aroma freeze issues.

Nekromantik said:
Ah ok.
only issue for me now is aroma freeze issues.
Click to expand...
Click to collapse
Didn't have that on my One until now.
I flashed my friend's One and it froze 3 times...then it worked.
I think it's recovery-related. Maybe wait for a fix.

zantekk said:
Didn't have that on my One until now.
I flashed my friend's One and it froze 3 times...then it worked.
I think it's recovery-related. Maybe wait for a fix.
Click to expand...
Click to collapse
It is AROMA related, amarullz have to update the binary
You can flash it 3 times or more, should work.
You can also use Hardware Buttons instead of Touch.. will help as well.

Device still rebooting
Can't flash recovery

same here - no access to recovery so far

Same for me too
Why ?

Got a HTC One from Orange france, and NO RECOVERY seems to stick. That thing boots, but i cannot enter recovery

I've tried using the AiO-Kit to flash CWM touch and normal as well as TWRP as well as the two CWMs manually and then this method. Still can't get access to recovery though

Try this? http://forum.xda-developers.com/showthread.php?t=2208029
Sent from my Nexus 4 using xda premium

Lothaen said:
Try this? http://forum.xda-developers.com/showthread.php?t=2208029
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
If you mean clearing the cache as mentioned in that thread I've tried it with no success

SoLdieR9312 said:
It is AROMA related, amarullz have to update the binary
You can flash it 3 times or more, should work.
You can also use Hardware Buttons instead of Touch.. will help as well.
Click to expand...
Click to collapse
Had the same problem again and again flashing TrickDroid on my HTC One (M7). Can confirm, that avoiding touch will relieve things but freezes can still occur. A few times I even could not reset the phone long-pressing the power + volume up buttons, means I was completely stuck on the frozen aroma screen (since a battery pull is not possible with this device). For anybody who may be in the same situation, try the "[FONT="Courier New]fastboot reboot[/FONT] command, this still came through and rebooted the device.

has this method worked for anyone else?
i'd like to try, but since i currently can't access recovery, i'm afraid to flash a new boot.img

pwr2wh8 said:
has this method worked for anyone else?
i'd like to try, but since i currently can't access recovery, i'm afraid to flash a new boot.img
Click to expand...
Click to collapse
Yes, worked for me. I had the same issue. While flashing Renovate rom, Aroma crapped out right at the end where it was installing the kernel. I was then stuck on boot image until i found this thread.
Also, for what it's worth, i thought I'd flash the boot image again after i got my device running again but it killed my wifi. I had to reflash the rom as wifi in settings was `out of order`....
//edit: okay. i've been able to reproduce the crashing. seems it's an aroma/rom issue (i couldn't tell one way or the other). what matters here is flashing boot image with the provided image does the trick. whatever magic it does, i'm able to flash cwm recovery 6.0.3.1 but I have to flash boot image before, else flashing recovery is fruitless.
anyways, thanks. this thread help me solve what i thought was `bricked` device.

[Q] Stuck on Splash Screen

Need serious help.
I flashed dirty unicorns and data and sms wasn't working so I tried to restore my phone but TWRP didn't see anything to restore. So desperately, i saw that it still saw my ViperRom zip so i flashed that and now I'm stuck in the splash screen. I tried to get the phone back to recovery with the toolkit and it doesn't see my phone.

TheSignor said:
Need serious help.
I flashed dirty unicorns and data and sms wasn't working so I tried to restore my phone but TWRP didn't see anything to restore. So desperately, i saw that it still saw my ViperRom zip so i flashed that and now I'm stuck in the splash screen. I tried to get the phone back to recovery with the toolkit and it doesn't see my phone.
Click to expand...
Click to collapse
more info:
I just tried the button combo light trick and was able to enter recovery. but alas I am at a loss what to do now. I still can't see my backups. I'm now doing a standard wipe and reinstalling ViperRom. Please God let this work.
update: Phone is alive.......but, i'm stuck on EVDO and Goomanager doesn't seem to see any of my original stuff. I'm aware this is the 4.2.2 thing but I am not really educated on how to deal with that.

TheSignor said:
more info:
I just tried the button combo light trick and was able to enter recovery. but alas I am at a loss what to do now. I still can't see my backups. I'm now doing a standard wipe and reinstalling ViperRom. Please God let this work.
update: Phone is alive.......but, i'm stuck on EVDO and Goomanager doesn't seem to see any of my original stuff. I'm aware this is the 4.2.2 thing but I am not really educated on how to deal with that.
Click to expand...
Click to collapse
Look here Q14

bigdaddy619 said:
Look here Q14
Click to expand...
Click to collapse
Thanks. Only one question though. I just finished copying my restore from the 0 folder and pasted it, now TWRP can see it and is finally willing to restore. Will the restore solve this issue just as easily or is it that as soon as you flash a 4.2.2 is your system forever changed without this fix? I only ask because I don't want to flash that zip and create a new issue if the restore will quite literally send me back in time to before I even flashed 4.2.2.

TheSignor said:
Thanks. Only one question though. I just finished copying my restore from the 0 folder and pasted it, now TWRP can see it and is finally willing to restore. Will the restore solve this issue just as easily or is it that as soon as you flash a 4.2.2 is your system forever changed without this fix? I only ask because I don't want to flash that zip and create a new issue if the restore will quite literally send me back in time to before I even flashed 4.2.2.
Click to expand...
Click to collapse
TBH I only use sense roms ask your question in the 4.2.2 > 4.1.2 thread

problem after installing Android Revolution HD 40.3

Hi everyone,
I've intslled the Android Revolution HD 40.3 on my HTC One.
The process went well. But when it finished the phone keep rebooting, entering recovery mode and exiting and re-rebooting again and again and again ...
I do not have any idea about what to do !!
Help please !!!

Medarioth said:
Hi everyone,
I've intslled the Android Revolution HD 40.3 on my HTC One.
The process went well. But when it finished the phone keep rebooting, entering recovery mode and exiting and re-rebooting again and again and again ...
I do not have any idea about what to do !!
Help please !!!
Click to expand...
Click to collapse
This happened to me a lot on my old Desire HD. Have you tried re-flashing the rom or trying a different one? Also did you clean flash?

JasSingh93 said:
This happened to me a lot on my old Desire HD. Have you tried re-flashing the rom or trying a different one? Also did you clean flash?
Click to expand...
Click to collapse
I can't access the recovery mode to re-flash the rom or try another one.
What exactly do you mean by "clean flash" ? I'm quite a nweebie with HTC and english is not my usual language ^^

Medarioth said:
I can't access the recovery mode to re-flash the rom or try another one.
What exactly do you mean by "clean flash" ? I'm quite a nweebie with HTC and english is not my usual language ^^
Click to expand...
Click to collapse
Ah okay. I would then flash a custom recovery. You can access the bootloader correct? What method did you use to install the rom? Clean flash or wipe is when you erase all the phone's system files, leaving a blank slate for a new rom to be installed on, and should be done before installing a brand new rom to avoid any issues.
http://forum.xda-developers.com/showthread.php?t=2568662
This is the link to the recovery image I used, it's the latest clockwordmod touch recovery. Very easy to flash as long as you have fast boot setup correctly. Once you have a working recovery you should be able to try a re-flash.

JasSingh93 said:
Ah okay. I would then flash a custom recovery. You can access the bootloader correct? What method did you use to install the rom? Clean flash or wipe is when you erase all the phone's system files, leaving a blank slate for a new rom to be installed on, and should be done before installing a brand new rom to avoid any issues.
http://forum.xda-developers.com/showthread.php?t=2568662
This is the link to the recovery image I used, it's the latest clockwordmod touch recovery. Very easy to flash as long as you have fast boot setup correctly. Once you have a working recovery you should be able to try a re-flash.
Click to expand...
Click to collapse
Well I entered Recovery mode through Rom Manager[/URL]clokworkmod () then used "install zip from sdcard".
I chose to keep my old data and don't make a factory reset.
The link you gave redirect me for a post of yours.

Medarioth said:
Well I entered Recovery mode through Rom Manager[/URL]clokworkmod () then used "install zip from sdcard".
I chose to keep my old data and don't make a factory reset.
Click to expand...
Click to collapse
Was the recovery still stock or was a custom one flashed? Which process did you follow to root the phone? Since you can't access the recovery at the moment is suggesting it is stock. A failed rom install shouldn't corrupt recovery

JasSingh93 said:
Was the recovery still stock or was a custom one flashed? Which process did you follow to root the phone? Since you can't access the recovery at the moment is suggesting it is stock. A failed rom install shouldn't corrupt recovery
Click to expand...
Click to collapse
I remember I've unlocked the bootloader.
I used the method described on this french website : phonandroid.com/tutoriel-comment-rooter-son-htc-one.html
On the bootloader now, i can do a factory reset. Can it be a solution ? will it or not delete the root ?

Medarioth said:
I remember I've unlocked the bootloader.
I used the method described on this french website : phonandroid.com/tutoriel-comment-rooter-son-htc-one.html
On the bootloader now, i can do a factory reset. Can it be a solution ? will it or not delete the root ?
Click to expand...
Click to collapse
I'm not sure, since you have tried to flash another rom, a factory reset might not solve the issue. Trying shouldn't brick the phone but I can't say for sure, sorry!
The method looks similar to the one I used. Could you try following from step 6? but using a different recovery.img. I used the clockwokmod touch from http://forum.xda-developers.com/showthread.php?t=2173863

JasSingh93 said:
I'm not sure, since you have tried to flash another rom, a factory reset might not solve the issue. Trying shouldn't brick the phone but I can't say for sure, sorry!
The method looks similar to the one I used. Could you try following from step 6? but using a different recovery.img. I used the clockwokmod touch from http://forum.xda-developers.com/showthread.php?t=2173863
Click to expand...
Click to collapse
yehaaaa! I can now access the ClockworkMod Recovery
Should I try to re-install the rom ? a simple reboot ? ^^

Medarioth said:
yehaaaa! I can now access the ClockworkMod Recovery
Should I try to re-install the rom ? a simple reboot ? ^^
Click to expand...
Click to collapse
Nice! Glad you have working recovery. Yes I would reinstall the rom now, and I would recommend that you wipe the system files, (except SD Card partition of course) to reduce the chance of boot loops etc

JasSingh93 said:
Nice! Glad you have working recovery. Yes I would reinstall the rom now, and I would recommend that you wipe the system files, (except SD Card partition of course) to reduce the chance of boot loops etc
Click to expand...
Click to collapse
ok will try and keep you updated

Medarioth said:
ok will try and keep you updated
Click to expand...
Click to collapse
Ok, you shouldn't have any problems anymore :fingers-crossed:

Medarioth said:
ok will try and keep you updated
Click to expand...
Click to collapse
doesn't work :/ after finishing the installation the phone reboot but it's stuck on the boot logo

Medarioth said:
doesn't work :/ after finishing the installation the phone reboot but it's stuck on the boot logo
Click to expand...
Click to collapse
Could you send me a link to the rom you flashed? Try downloading a different rom. As you can't boot a ROM your only option may be to use ADB to push a new ROM onto your phone's storage.
See this: http://forum.xda-developers.com/showthread.php?t=2317989
EDIT: Sorry, that link is for the other recovery. Use this one instead http://forum.xda-developers.com/showthread.php?t=1667929
My bad

JasSingh93 said:
Could you send me a link to the rom you flashed? Try downloading a different rom. As you can't boot a ROM your only option may be to use ADB to push a new ROM onto your phone's storage.
See this: http://forum.xda-developers.com/showthread.php?t=2317989
EDIT: Sorry, that link is for the other recovery. Use this one instead http://forum.xda-developers.com/showthread.php?t=1667929
My bad
Click to expand...
Click to collapse
I used the rom on this link : androidrevolution.nl/downloader/download.php?file=Android_Revolution_HD-One_40.3.zip

Medarioth said:
I used the rom on this link : androidrevolution.nl/downloader/download.php?file=Android_Revolution_HD-One_40.3.zip
Click to expand...
Click to collapse
It may have been a bad download. There isn't really any reason for it to not work, although it does say on the page it "You need TRWP 2.6.3.3 custom recovery!"
Not to worry, you can flash it in no-time. Ok so just as before, just flash a new recovery (again) and use the latest image from here: http://techerrata.com/browse/twrp2/m7/
This should allow you to install the rom as the developers intend. It is strange though, i've never encountered a rom where a specific recovery was needed.

JasSingh93 said:
It may have been a bad download. There isn't really any reason for it to not work, although it does say on the page it "You need TRWP 2.6.3.3 custom recovery!"
Not to worry, you can flash it in no-time. Ok so just as before, just flash a new recovery (again) and use the latest image from here: http://techerrata.com/browse/twrp2/m7/
This should allow you to install the rom as the developers intend. It is strange though, i've never encountered a rom where a specific recovery was needed.
Click to expand...
Click to collapse
done. waiting in progress ....... :fingers-crossed:

Medarioth said:
done. waiting in progress ....... :fingers-crossed:
Click to expand...
Click to collapse
It should definitely work this time! I've actually just flashed TWRP recovery, and I can already say I prefer it over ClockWorkMod!

Medarioth said:
done. waiting in progress ....... :fingers-crossed:
Click to expand...
Click to collapse
Hallelujah after 5 min for rebooting
Just have to reconfigur and reinstal all the apps
thx for your help bro :good:

Medarioth said:
Hallelujah after 5 min for rebooting
Just have to reconfigur and reinstal all the apps
thx for your help bro :good:
Click to expand...
Click to collapse
Yayyy!!! Nice one! Good teamwork we got there in the end! Happy to help
Have fun!!

phone stuck on att screen after cm11 installation

ok here it goes
This is the first time i touch this Vivid, a few days ago I rooted it withou issues and has TWRP installed, i also did 2 full backups at that time just in case.
This morning i tried to install a new ROM, CyanogenMod 11 - Android 4.4.2 - KitKat. Basically the steps i took were
1. boot into twrp recovery
2. Did a factory reset
3. Did a System Reset
4. Clared cache and Dalvik cache
5. install the rom
6. install PA gapps
7. booted the phone wich got stuck in the htc screen forever
8. remembered that i was s-off and didnt flash the boot.img
9. repeated steps 1 thru 8 and after that flashed boot.img using fastboot
10. rebooted the phone but it was still getting stuck on htc screen
After all this i decided it was not worth it so i went back into twrp to restore my backup, unfortunately after restoring an booting the phone i am able to go past the htc screen, get the beats audio and att splash screen but it stays there, now stuck on att screen.
I have tried also to restore my second backup with basically the same results
any ideas or suggestions on what could i do next?

cantuluis said:
ok here it goes
This is the first time i touch this Vivid, a few days ago I rooted it withou issues and has TWRP installed, i also did 2 full backups at that time just in case.
This morning i tried to install a new ROM, CyanogenMod 11 - Android 4.4.2 - KitKat. Basically the steps i took were
1. boot into twrp recovery
2. Did a factory reset
3. Did a System Reset
4. Clared cache and Dalvik cache
5. install the rom
6. install PA gapps
7. booted the phone wich got stuck in the htc screen forever
8. remembered that i was s-off and didnt flash the boot.img
9. repeated steps 1 thru 8 and after that flashed boot.img using fastboot
10. rebooted the phone but it was still getting stuck on htc screen
After all this i decided it was not worth it so i went back into twrp to restore my backup, unfortunately after restoring an booting the phone i am able to go past the htc screen, get the beats audio and att splash screen but it stays there, now stuck on att screen.
I have tried also to restore my second backup with basically the same results
any ideas or suggestions on what could i do next?
Click to expand...
Click to collapse
Do you know if you had the original Gingerbread or had upgraded to ICS? If you were still on GB, then you should be able to run the RUU for that, if ICS there is an RUU you can install. Read all the directions carefully, most things seem easy but have pitfalls if you are not careful enough.

cmerlyn said:
Do you know if you had the original Gingerbread or had upgraded to ICS? If you were still on GB, then you should be able to run the RUU for that, if ICS there is an RUU you can install. Read all the directions carefully, most things seem easy but have pitfalls if you are not careful enough.
Click to expand...
Click to collapse
I dont know what i was running originally. However i am back in business!!!
I found the superguide followed it regarding the RUU and luckily i got my phone to work again.
I want to try flashing the CM11 again, i am guessing that either i am doing something wrong or maybe TWRP is not working correctly on my phone and not flashing the rom as it should.
Any known issues with TWRP and the vivid? shall i try another recovery?
Are the following steps pretty much what i should do to flash it
1. factory reset
2. system reset
3. clearing caches
4. flash boot.img (i am s-on)
5. flash rom
6. flash gapps
any suggestion is welcomed

Hboot version from the boorloader?
Sent from my Vivid 4G using Tapatalk

rignfool said:
Hboot version from the boorloader?
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
it is 1.85.0025
additional info:
After recovering the phone i decided to lock the bootloader and start all over again. I re-root and then, instead of installing TWRP i used CWM and obviously, got a nand backup.
O tried flashing again CM11 and got the exact same results. Stuck in the initial HTC screen forever. Tried to restore my NAND Backup and the result was also exactly the same as before, phone would get the htc screen, then the beats audio and att animations and then will stuck onthe att screen forever.
This is weird, i must be doing something wrong here...

Reading thru a few times. You did indeed flash the image? fastboot flash boot boot.img on command line. Make sure boot.img was extracted from the rom to the folder you are typing that in. You do that after flashing rom and gapps. It has to be done from bootloader not recovery.
How long are you letting it sit. Had a phone that I thought was doing that, just took a few extra minutes to boot up.

"Small mistake"
Sorry for your problem, I think there was a small mistake before installing CM11, and was what you describe in step 3 "Did a System Reset" when the installation instructions say: "Wipe data, cache, and dalvik cache". I'm afraid you can only recover your VIVID through JTAG on any site that offers the service, it seems you deleted your operating system. The other option is to try [unbrick] HTC Unbricking Project By dexter93 developers forum, http://forum.xda-developers.com/showthread.php?t=1627886;
All the best. Just a recommendation, read, read and read each post and comments to take no surprises. Good luck.:fingers-crossed
I would appreciate your comments

I don't think that post is relevant. You still have access to bootloader and recovery right? Then it isn't bricked.

Yuskow said:
I don't think that post is relevant. You still have access to bootloader and recovery right? Then it isn't bricked.
Click to expand...
Click to collapse
Yes i do have access to bootlader and recovery, i actually was able to bring back to life the phone using RUU. So the issue now is not that the phone is bricked but that anything i try to load on it fails, being CM11 or even the NAND backup that i took with this same phone just after installing recovery, nothing seems to work.
I was googling around and so another person that had similar behavior on his vivid but didn't posted if he was ever able to fix it...

Yuskow said:
Reading thru a few times. You did indeed flash the image? fastboot flash boot boot.img on command line. Make sure boot.img was extracted from the rom to the folder you are typing that in. You do that after flashing rom and gapps. It has to be done from bootloader not recovery.
How long are you letting it sit. Had a phone that I thought was doing that, just took a few extra minutes to boot up.
Click to expand...
Click to collapse
Yes indeed. I used fastboot to flash the boot.img, i will try to do it again today and make sure that i do this after flashing rom and gapps. I might as well try another rom.
Anyone ROM that you recomend me to try?

You tried reading the following post: http://forum.xda-developers.com/showthread.php?t=2642575,? It's different from what I showed above, there describes another way to recover your vivid by projectisaac:fingers-crossed:

cantuluis said:
Yes indeed. I used fastboot to flash the boot.img, i will try to do it again today and make sure that i do this after flashing rom and gapps. I might as well try another rom.
Anyone ROM that you recomend me to try?
Click to expand...
Click to collapse
CM11 kicks ass. http://69.10.54.187/nightly/holiday/ is where you might find the latest nightlies.
Seems to be the only vivid rom that has been worked on for a while.
First time I tried running a custom rom I had a similar issue to what you experience. Do you happen to be on bell? After restoring with the RUU and unlocking again, all went well.
The best guide is http://forum.xda-developers.com/showthread.php?t=1416836 but just use it as a guide line and use this software instead.
http://forum.xda-developers.com/showthread.php?t=2437705
Some people say to run the fastboot command 2x. I've been following that advice. Figured it can't do anything bad.

Yuskow said:
CM11 kicks ass. http://69.10.54.187/nightly/holiday/ is where you might find the latest nightlies.
Seems to be the only vivid rom that has been worked on for a while.
First time I tried running a custom rom I had a similar issue to what you experience. Do you happen to be on bell? After restoring with the RUU and unlocking again, all went well.
The best guide is http://forum.xda-developers.com/showthread.php?t=1416836 but just use it as a guide line and use this software instead.
http://forum.xda-developers.com/showthread.php?t=2437705
Some people say to run the fastboot command 2x. I've been following that advice. Figured it can't do anything bad.
Click to expand...
Click to collapse
ok guys i am now officially an idiot.
Problem came down to be that i was using the wrong boot.img, i didnt know that the correct one is INSIDE the rom zip. I tried it once more and now i am running CM11
thanks for your suggestions and sorry for taking your time on this newb learning experience

alosegon said:
Sorry for your problem, I think there was a small mistake before installing CM11, and was what you describe in step 3 "Did a System Reset" when the installation instructions say: "Wipe data, cache, and dalvik cache". I'm afraid you can only recover your VIVID through JTAG on any site that offers the service, it seems you deleted your operating system. The other option is to try [unbrick] HTC Unbricking Project By dexter93 developers forum, http://forum.xda-developers.com/showthread.php?t=1627886;
All the best. Just a recommendation, read, read and read each post and comments to take no surprises. Good luck.:fingers-crossed
I would appreciate your comments
Click to expand...
Click to collapse
Please... Do not scare people like that...
AFAIK... You only need a JTAG if your phone reads qhusb_download... Or something like that...
I have erased my OS literally hundreds of times...
Sent from my Vivid 4G using Tapatalk

rignfool said:
Please... Do not scare people like that...
AFAIK... You only need a JTAG if your phone reads qhusb_download... Or something like that...
I have erased my OS literally hundreds of times...
Sent from my Vivid 4G using Tapatalk
Click to expand...
Click to collapse
thanks for clarifying that

Glad you're up and running.

Btw, this ROM is amazing, so much better than the stock at crap
Sent from my Vivid 4G using Tapatalk

[Q][Helprequest]repartitioning gone wrong?

I followed the steps in Neo's thread about repartitioning and ended up in sh** where I can not see sdcard0 (internal memory) and phone says there is no micro sd card inserted even though it is.
I tried with terminal commands to fix storage permissions, but it doesn't allow me anything as it says files are read only.
I flashed the uninstaller as well which says it should help and did not help.
Any other ideas? :/

_ronin_ said:
I followed the steps in Neo's thread about repartitioning and ended up in sh** where I can not see sdcard0 (internal memory) and phone says there is no micro sd card inserted even though it is.
I tried with terminal commands to fix storage permissions, but it doesn't allow me anything as it says files are read only.
I flashed the uninstaller as well which says it should help and did not help.
Any other ideas? :/
Click to expand...
Click to collapse
Which recovery is installed? Try AdrianDC's latest TWRP. Also CM13 might help as it will repartion the storage.

St.Jimmy90 said:
Which recovery is installed? Try AdrianDC's latest TWRP. Also CM13 might help as it will repartion the storage.
Click to expand...
Click to collapse
Thank you very much for answer, almost gave up on the phone pretty much.
Twrp is 2.8.xxx something (one supplied with Neo's rom), I tried with 3.0 did not help. Tried with Clockworkmod didnt help either.
I will search for AdrianDC TWRP and give it a go.
Cm13 I tried but did not want to apply the storage change because it could not find "system" partition, (almost bricked it I guess) but I managed to fix that with stock rom, and could later reflash cm 12.1
But I will try flashing CM13 again, and come back with info in case you will be able to give some input again!
Thanks for now!

_ronin_ said:
Thank you very much for answer, almost gave up on the phone pretty much.
Twrp is 2.8.xxx something (one supplied with Neo's rom), I tried with 3.0 did not help. Tried with Clockworkmod didnt help either.
I will search for AdrianDC TWRP and give it a go.
Cm13 I tried but did not want to apply the storage change because it could not find "system" partition, (almost bricked it I guess) but I managed to fix that with stock rom, and could later reflash cm 12.1
But I will try flashing CM13 again, and come back with info in case you will be able to give some input again!
Thanks for now!
Click to expand...
Click to collapse
No worries.
For the recovery, go here:
http://forum.xda-developers.com/xpe...t/recovery-twrp-3-0-0-touch-recovery-t3319588
And CM13 here:
http://forum.xda-developers.com/xperia-t-v/orig-development/rom-cyanogenmod-13-0-xperia-t-t3415827
I'm using it on my T and it's pretty awesome

St.Jimmy90 said:
No worries.
For the recovery, go here:
http://forum.xda-developers.com/xpe...t/recovery-twrp-3-0-0-touch-recovery-t3319588
And CM13 here:
http://forum.xda-developers.com/xperia-t-v/orig-development/rom-cyanogenmod-13-0-xperia-t-t3415827
I'm using it on my T and it's pretty awesome
Click to expand...
Click to collapse
Cheers for links, Tried with CM13, no success like before getting error when flashing the zip:
"sdcard could not be mounted (ext4/exfat ?) please verify your partition file system
You are agreeing to format your SDCard
UserData partition still contains files"
so doesnt let me flash 13.
And to repair the partitions I guess I just try the TWRP and under advance the repair option right?
Terribly sorry to bother so much, but I like the phone, and would love to fix it again!

_ronin_ said:
Cheers for links, Tried with CM13, no success like before getting error when flashing the zip:
"sdcard could not be mounted (ext4/exfat ?) please verify your partition file system
You are agreeing to format your SDCard
UserData partition still contains files"
so doesnt let me flash 13.
And to repair the partitions I guess I just try the TWRP and under advance the repair option right?
Terribly sorry to bother so much, but I like the phone, and would love to fix it again!
Click to expand...
Click to collapse
Try to flash twrp first. Then do a reboot and try again to flash cm13.
Please report back how it goes
Good luck

St.Jimmy90 said:
Try to flash twrp first. Then do a reboot and try again to flash cm13.
Please report back how it goes
Good luck
Click to expand...
Click to collapse
Done and done, but I basically ended up on the same spot where it said unable to mount /system + previous error about sdcard
and now can not flash anything anymore (so have to flash official rom again to start up my phone)
Maybe im doing something wrong with flashing, but i doubt it. (flashtool64 is which im using) fastboot, and under the option of select kernel to flash.
then rest is done in recovery anyway with installing, right?
At the moment I am installing official rom, so I can start over with flashing twrp, rebooting, then flashing cm13
One thing I learned to always backup working system before doing anything!

_ronin_ said:
Done and done, but I basically ended up on the same spot where it said unable to mount /system + previous error about sdcard
and now can not flash anything anymore (so have to flash official rom again to start up my phone)
Maybe im doing something wrong with flashing, but i doubt it. (flashtool64 is which im using) fastboot, and under the option of select kernel to flash.
then rest is done in recovery anyway with installing, right?
At the moment I am installing official rom, so I can start over with flashing twrp, rebooting, then flashing cm13
One thing I learned to always backup working system before doing anything!
Click to expand...
Click to collapse
I'm sorry to hear that.
Once stock rom is on it, try to flash neos kernel and then boot into recovery. In there flash Adriandc's twrp (the zip file).
After that reboot and try to flash cm13. If this still doesn't work you could try Adriandc's files for repartitioning. He did some awesome work.
I'm on my phone right now so I'll keep it short, if you need further assistance I'll try to help you as soon as i get to my PC

St.Jimmy90 said:
I'm sorry to hear that.
Once stock rom is on it, try to flash neos kernel and then boot into recovery. In there flash Adriandc's twrp (the zip file).
After that reboot and try to flash cm13. If this still doesn't work you could try Adriandc's files for repartitioning. He did some awesome work.
I'm on my phone right now so I'll keep it short, if you need further assistance I'll try to help you as soon as i get to my PC
Click to expand...
Click to collapse
Thanks!
Tried exactly like that, same error when trying to flash cm13 :"Updater process ended with ERROR:7
Error installing zip file ".zip"
I guess I ruined something really bad when trying to repartion following neo's guide, (twrp says about partitions this:
- Internal storage: (1812mb)
- Legacy SDCard (0mb)
- Micro SDCard (7488mb)
-USB OTG (0mb)
If you have any more suggestions I can try, otherwise we can give up! feels like nothing would work, though much love for taking your time trying to help me! <3

_ronin_ said:
Thanks!
Tried exactly like that, same error when trying to flash cm13 :"Updater process ended with ERROR:7
Error installing zip file ".zip"
I guess I ruined something really bad when trying to repartion following neo's guide, (twrp says about partitions this:
- Internal storage: (1812mb)
- Legacy SDCard (0mb)
- Micro SDCard (7488mb)
-USB OTG (0mb)
If you have any more suggestions I can try, otherwise we can give up! feels like nothing would work, though much love for taking your time trying to help me! <3
Click to expand...
Click to collapse
It doesn't look that bad at all. Which version of TWRP is currently on your phone? (also the build date)
It looks like basketbuild is down right now, but once it's back up again you could try this zip:
https://basketbuild.com/devs/AdrianDC/CyanogenMod/XperiaBlue
it will repartition your phone to it's original partition table

St.Jimmy90 said:
It doesn't look that bad at all. Which version of TWRP is currently on your phone? (also the build date)
It looks like basketbuild is down right now, but once it's back up again you could try this zip:
https://basketbuild.com/devs/AdrianDC/CyanogenMod/XperiaBlue
it will repartition your phone to it's original partition table
Click to expand...
Click to collapse
Oh that sounds exactly what I would need yea!
At the moment I reflashed cm12.1 (neo's) which installs 2.8.6.x twrp. Build date was january i think. (phone is booting up still)
I will try this zip as soon as basketbuild is up and will let you know what happens. (I guess i just reboot into twrp and flash the zip)?

_ronin_ said:
Oh that sounds exactly what I would need yea!
At the moment I reflashed cm12.1 (neo's) which installs 2.8.6.x twrp. Build date was january i think. (phone is booting up still)
I will try this zip as soon as basketbuild is up and will let you know what happens. (I guess i just reboot into twrp and flash the zip)?
Click to expand...
Click to collapse
Yeah, boot into TWRP, flash a new TWRP (I think it was 20th july or newer), then reboot straight into recovery again and flash the restore_sd zip

My phone booted up now with the 12.1, and there is internal memory back, 11gb out of 11gb free, accessable, and everything.. No idea what caused it to appear again but something what you said basically helped me and restored it back to original.
So thank you a lot! I kinda want to try and repartition it again to have more space for apps, but im afraid ill just blow it again.
You think I should try installing cm13 now as storage looks normal again?

_ronin_ said:
My phone booted up now with the 12.1, and there is internal memory back, 11gb out of 11gb free, accessable, and everything.. No idea what caused it to appear again but something what you said basically helped me and restored it back to original.
So thank you a lot! I kinda want to try and repartition it again to have more space for apps, but im afraid ill just blow it again.
You think I should try installing cm13 now as storage looks normal again?
Click to expand...
Click to collapse
I'm really glad you managed to restore it! Mint is still a great device.
Yeah, but CM13 will repartition your phone again (automatically). It will warn you once that all data will be lost, on second attempt it will flash just fine.
Good luck

St.Jimmy90 said:
I'm really glad you managed to restore it! Mint is still a great device.
Yeah, but CM13 will repartition your phone again (automatically). It will warn you once that all data will be lost, on second attempt it will flash just fine.
Good luck
Click to expand...
Click to collapse
Yep it did just that. Im very grateful for all help, running cm13 now as well, and storage wont be an issue anymore it seems!

_ronin_ said:
Yep it did just that. Im very grateful for all help, running cm13 now as well, and storage wont be an issue anymore it seems!
Click to expand...
Click to collapse
Awesome. Have fun with CM13, it's really a great rom.