Database Users

1 Click root brick?!

So i read thru a lot of the root threads & none of them made anh sense to me.I downloaded ADB,moto drivers, sdk,jdk,etc.But still none of it made any sense. So i tried the 1 click root & soft bricked my xoom. It gets stuck at the Motorola screen. I tried getting into the options & wiping user data,factory reset.But it would still get stuck at the dual core screen. So i tried a suggestion of using 1 click root to undo the root. But it said the xoom would say "done" twice on the screen but it only said "done" once. So then i relocked it hoping it would reboot & work but it didn't. I see 1 guy was able to fix his using a rooting guide.I hope someone here can help me out.
Sent from my DROIDX using XDA App

Arun01 said:
So i read thru a lot of the root threads & none of them made anh sense to me.I downloaded ADB,moto drivers, sdk,jdk,etc.But still none of it made any sense. So i tried the 1 click root & soft bricked my xoom. It gets stuck at the Motorola screen. I tried getting into the options & wiping user data,factory reset.But it would still get stuck at the dual core screen. So i tried a suggestion of using 1 click root to undo the root. But it said the xoom would say "done" twice on the screen but it only said "done" once. So then i relocked it hoping it would reboot & work but it didn't. I see 1 guy was able to fix his using a rooting guide.I hope someone here can help me out.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Motorola published the factory files for Xoom awhile back so if you still have fastboot, you can recover from it.
http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard

I relocked it using the 1 click root and all it says now is "Failed to boot LNX 0x0004" "Starting RSD mode 2".I'm now trying to use the 1 click root to try to get it back to where it was..I just don't understand all of the rooting methods even after downloading adb,sdk,,etc..It may as well be written in Chinese.I'm sure if i saw someone actually do it i could catch on to it but right now rooting is confusing..hence i went with the 1 click.I had no problem 1 click rooting my droid x with a 1 click root.

Stop using one click crap. If you don't know what you're then you should not be messing with your device.

Sent from my DROIDX using XDA App

I can. Just won't.

Arun01 said:
I relocked it using the 1 click root and all it says now is "Failed to boot LNX 0x0004" "Starting RSD mode 2".I'm now trying to use the 1 click root to try to get it back to where it was..I just don't understand all of the rooting methods even after downloading adb,sdk,,etc..It may as well be written in Chinese.I'm sure if i saw someone actually do it i could catch on to it but right now rooting is confusing..hence i went with the 1 click.I had no problem 1 click rooting my droid x with a 1 click root.
Click to expand...
Click to collapse
Type oem unlock again and then flash the stock images...youll be good to go...also there are really good stickies in here that help..pleasedont forget to search before starting a new thread.

albundy2010 said:
I can. Just won't.
Click to expand...
Click to collapse
And this is rude and uncalled for

The OP stated he read quides etc and none of it made sense to him etc. So instead of asking for help a explanation he tries a one click method. Which is stupid. He than softbricks the device and asked for help here.
Then he is told that moto released the factory images and use fastboot if he still has it to recover the device. He then decides to ignore that entirely and go back and try to unroot/restore with the one click BS again. Then he tries to use it again to go back to where he was. Just flat out stupid. He did something when he had no idea wtf he was doing. Was told what to do. Did not do it. He even said it is like Chinese to him.
So I told him to stop messing with one click crap. Which is correct. I told him to stop messing with the ****ing thing. Which is also correct. He needs to learn/understand wtf he is doing. Instead of basically button mashing/trying crap and hoping it will basically fix itself.
On top of that this posted in the wrong section. Uncalled for my ass. He is the one that was rude when told to not mess with the one click or the device. Now this part is rude. **** his stupid ass.

csseale said:
Type oem unlock again and then flash the stock images...youll be good to go...also there are really good stickies in here that help..pleasedont forget to search before starting a new thread.
Click to expand...
Click to collapse
How do i get to that ..and where do i type it at ..i looked in device manager & does recognize the xoom..it says "Motorola USB Device:Motorola Flash Interface"..In properties under "Driver" it has options for driver details..update driver..disable & uninstall.Can i do anything with them?
I tried opening SDK manager but it never lets me type anything in the box as it's always trying to do some kind of update in another window so when i close the window it closes all of the windows.

Sent from my DROIDX using XDA App

Arun01 said:
So i read thru a lot of the root threads & none of them made anh sense to me.I downloaded ADB,moto drivers, sdk,jdk,etc.But still none of it made any sense. So i tried the 1 click root & soft bricked my xoom. It gets stuck at the Motorola screen. I tried getting into the options & wiping user data,factory reset.But it would still get stuck at the dual core screen. So i tried a suggestion of using 1 click root to undo the root. But it said the xoom would say "done" twice on the screen but it only said "done" once. So then i relocked it hoping it would reboot & work but it didn't. I see 1 guy was able to fix his using a rooting guide.I hope someone here can help me out.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
If they didnt make sense to you in the first place you probably shoud not be attempting to root... U went straight to an old method that even the developer has marked in hs thread can full brick you and should not be used. The xoom costs like 600 bucks... Why wouldnt you do extensive research on how to root? If you did not understand the terms why didn't you research the methods and learn it?
I hope you can flash the factory imagines back through fastboot and adb, but i just do not understand why people attempt this stuff when they have no idea what the terms even mean...
You need to have sdk, hook up to usb on your computer, and follow one of the unlock guides posted on this site... A real one using adb... Then you need to follow a root one...
Sorry that is not more helpful, but half of this experience is that you need to learn what you are doing and the instructions are out there. If they do not make sense at this point im afraid you are stuck. Now the way your device is you have to figure it out...

Arun01 said:
I relocked it using the 1 click root and all it says now is "Failed to boot LNX 0x0004" "Starting RSD mode 2".I'm now trying to use the 1 click root to try to get it back to where it was..I just don't understand all of the rooting methods even after downloading adb,sdk,,etc..It may as well be written in Chinese.I'm sure if i saw someone actually do it i could catch on to it but right now rooting is confusing..hence i went with the 1 click.I had no problem 1 click rooting my droid x with a 1 click root.
Click to expand...
Click to collapse
Please check out this thread.It is called Root heaven for a reason. Just about every viable rooting guide, all the files and explanations you will need are here.
http://forum.xda-developers.com/showthread.php?t=1209341
I urge you to just calm down, read about what is the sdk, what is adb, how to recover from a soft brick and so on. The xda xoom forum is all about learning and teaching. We were all noobies once. The Xoom is a very complex device with many models and vesions and one clicks just don't cut it. There are rooting methods that are relatively simple but you really need to be prepared before you get started.
Good luck and don't despair. You'll get there.

Thanks for the help guys.I'm reading through all of the threads and i see a typo in a post that in the command window would've never let me find the sdk tools on my c drive. But after i retyped it i did it & a bunch of writing came up. Trying to figure out now how to flash the stock images to the xoom.
Sent from my DROIDX using XDA App

Arun01 said:
Thanks for the help guys.I'm reading through all of the threads and i see a typo in a post that in the command window would've never let me find the sdk tools on my c drive. But after i retyped it i did it & a bunch of writing came up. Trying to figure out now how to flash the stock images to the xoom.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
at first, make sure you install android sdk correctly. then go to android sdk-folder in your computer, u will find a folder named platform-tool. Press shift+ right click on it, then choose open command window here. After that, type in "adb devices" or "fastboot devives" to check if your xoom is connected. If yes,you good to go. If no, check your android sdk installed process

After i type in abd devices it says list of devices attached but shows nothing..i did copy the sdk tools folder to the c drive like i was told.

@OP
If you can't do it yourself, getting somebody to help you (in person) is always an option. If you live in a major city, advertise on Craigslist or some equivalent. Offer $50 for debricking + some tutorial.

In order for the device to show up in adb the device needs to actually booted into the os and have USB debugging enabled. Which you can't do.
What you're supposed to do is use fastboot.
Boot the device into fastboot mode.
Use fastboot devices to see if the computer see's it/everything is set up etc.
If bootloader is locked unlock it with fastboot OEM unlock.
Then flash the official images for your exact device. Fastboot flash boot boot.img and so on.
The last command on restoring to stock guides is optional. Fastboot OEM lock. I would not do it. No reason to relock it. If do learn decide to root later you would have to unlock again and loose all data.

albundy2010 said:
In order for the device to show up in adb the device needs to actually booted into the os and have USB debugging enabled. Which you can't do.
What you're supposed to do is use fastboot.
Boot the device into fastboot mode.
Use fastboot devices to see if the computer see's it/everything is set up etc.
If bootloader is locked unlock it with fastboot OEM unlock.
Then flash the official images for your exact device. Fastboot flash boot boot.img and so on.
The last command on restoring to stock guides is optional. Fastboot OEM lock. I would not do it. No reason to relock it. If do learn decide to root later you would have to unlock again and loose all data.
Click to expand...
Click to collapse
That's good advice...no reason to re-lock. But get back to square one so that you're functional and then when you're ready to try again, do it the right way.
Again, good luck!

albundy2010 said:
In order for the device to show up in adb the device needs to actually booted into the os and have USB debugging enabled. Which you can't do.
What you're supposed to do is use fastboot.
Boot the device into fastboot mode.
Use fastboot devices to see if the computer see's it/everything is set up etc.
If bootloader is locked unlock it with fastboot OEM unlock.
Then flash the official images for your exact device. Fastboot flash boot boot.img and so on.
The last command on restoring to stock guides is optional. Fastboot OEM lock. I would not do it. No reason to relock it. If do learn decide to root later you would have to unlock again and loose all data.
Click to expand...
Click to collapse
Thanks a lot.I was able to unlock it then it rebooted & stopped at the Motorola screen then i started the 1st command: fastboot flash boot boot.img & it says waiting on device..but nothing happens so far.Should i move on to the next step or retry?

[Q] Please help!! can't recover from soft brick, tried lots of methods, Atrix 4G

So i was trying to get Gingerblur on my Atrix, because Orange has not released it yet and are being very slow at it, but anyway I followed the instructions on a site I visited quite carefully, but when I tried to turn the phone on it just came up with the Motorola start up picture and the red light starts blinking, I have tried a few methods, but I really need the phone working.
Please help.
Thanks in advance...
Sorry if I didn't explain it fully enough, please feel free to ask for a better explanation.

Tomn4569 said:
So i was trying to get Gingerblur on my Atrix, because Orange has not released it yet and are being very slow at it, but anyway I followed the instructions on a site I visited quite carefully, but when I tried to turn the phone on it just came up with the Motorola start up picture and the red light starts blinking, I have tried a few methods, but I really need the phone working.
Please help.
Thanks in advance...
Sorry if I didn't explain it fully enough, please feel free to ask for a better explanation.
Click to expand...
Click to collapse
Does it say anything? Does it power off after? Can you get into fastboot or android recovery?
Sent from my MB860 using xda premium

Yeah I can get into fastboot, and android recovery and all that stuff, but i'm not sure but I think I may have deleted the OS(or something like that) and it does turn off after a few minutes

Have you unlocked the phone? Can you get into rsd flash protocol? Might just flash the bootloader unlock and unlock it, after that flash a custom rom. Search for pudding or ihop to unlock.

I can get into RSD protocol, I tried a method on here last night which used RSDLite (this one http://forum.xda-developers.com/showthread.php?t=991072&highlight=flash+sbf )
it didn't work though it got to a certain point the said flash failed

Try the script I made here.

Is it suppose to take a while to boot up after flashing a new ROM?
Never mind it failed again...

matthew5025 said:
Try the script I made here.
Click to expand...
Click to collapse
I tried that but now on the phone is just says:
"Failed to boot 2
Starting RSD mode"

If your phone is unlocked. Flash the same exact version u had with this link. http://forum.xda-developers.com/showthread.php?t=1125944
This is an sbf. Download the correct version, install Motorola drivers, place in folder with least file paths ( ie: C:>atrix4g>sbf file ) use latest version of rsdlite or recommended. Follow sbf procedures. I am not responsible blah blah, but this should fix it. Don't panic. I have actually used this when I failed to unlock my bootloader. So in essence, it worked for my locked bootloader. Still, there is risk, try only if u feel comfortable.
Sent from my MB860 using xda premium

Phone will not install PC36IMG.zip file, tried a couple sd cards, stuck on boot loop

My friend gave me his Evo to try to fix. It isn't rooted so S-on. I tried put a recovery file on to see if I can change the rom, but it just won't recognize it. Someone else posted a similar problem, but he got is to work. I tested the card and file and my evo asked if I wanted to update, but his phone will not work. It is stuck in boot loop. Not sure how he got stock on that. He doesn't mess with phones. There was an unbrick program I tried and it didn't seem to work, but I probably wasn't using it correctly since it kept changing the rom to the same rom from what I could tell.
It boots up sometimes to seem to work for a minute then boots again. I get the red triangle when I try to go into recovery. It probably doesn't have a recovery img since we haven't tried to root it.

ask your friend what exactly was he doing prior to this happeing, also whats the info when you go into the bootloader? i only ask cause the more info you provide the better chances are someone can help solve this issue. also you cant put a recovery or a custom rom on till your rooted.

ok
dzee206 said:
ask your friend what exactly was he doing prior to this happeing, also whats the info when you go into the bootloader? i only ask cause the more info you provide the better chances are someone can help solve this issue. also you cant put a recovery or a custom rom on till your rooted.
Click to expand...
Click to collapse
I can hold the power and down vol and go into bootloader. It goes through the zip file loading instructions and can't find the PC36IMG image and never asks if I want to update. I think I read a post where someone was told their bootloader is "locked".

if your bootloader is S-on, then yes; your bootloader is locked and you can't flash any custom roms. what you might be able to do is download an RUU rom and flash from your computer.
Look at the bootloader version and tell us what that says..

ok
Hypeo said:
if your bootloader is S-on, then yes; your bootloader is locked and you can't flash any custom roms. what you might be able to do is download an RUU rom and flash from your computer.
Look at the bootloader version and tell us what that says..
Click to expand...
Click to collapse
I believe it was version .79 or something like that. I'll check it when I get home.
As soon as he gets back from China I'll ask him what he did when started bootlooping. The phone might work for 30 seconds before going into reboot over and over so RUU might not work. But I can go into bootloader and into fastboot and was able to get a unbrick program to run and it seemed to be able to install another rom, but the rom it said it was installing was the same that was on the phone so maybe they needs S-off to function.

If you find your phone is rooted and can turn it on long enough to download an app from the market called Flash Image GUI, in the description it will say for the EVO 3d but it works on the og as well, you can also download off the devs xda thread just google (flash image GUI xda) and it should pop up, another thing make the file is on the root of your sd card and not in a sub folder. Good luck.
Sent from my PC36100 using xda premium

Oh and you can't flash custom roms with s on period, if it is on that's your problem there.
Sent from my PC36100 using xda premium

here it is
Hypeo said:
if your bootloader is S-on, then yes; your bootloader is locked and you can't flash any custom roms. what you might be able to do is download an RUU rom and flash from your computer.
Look at the bootloader version and tell us what that says..
Click to expand...
Click to collapse
S-on
HBOOT-0.79.0000
MICROP-041f
RADIO-1.39.00.04.26
Apr 14 2010, 15:41:34
Does this give any idea of what I can do.

Zenfone 2 Lazer (ZE500KL) Stock Files Needed

Hi All.
I am in a bit of a situation right now.
My video recording app filled up internal storage and corrupted system files (because i forgot to point it to my external SD card).
This caused a boot loop, so I went into recovery and (regrettably) wiped the internal storage. Now when I try to flash or install a new (stock) rom, none will work. I have tried sideloading, installing through (TWRP) recovery and wiping the cache multiple times as I comb through the internet for files like the system.img, boot.img, and droidboot.img, to no avail.
TLDR; I need either a backup of someone elses Zenfone 2 ZE500KL, or the system files required to get me up and running, otherwise I have a brick on my hands.
Thanks for any help
Matt

Unlock bootloader, flash the official firmware, I think you can find it on the internet. Have you tried that? You can even get a deodexed rom from here and extract files needed and flash them...
Sent from my Tab3 Lite 7.0 using XDA Labs

Yep, found it on the official asus site...
Sent from my Tab3 Lite 7.0 using XDA Labs

jocamucko said:
Yep, found it on the official asus site...
Sent from my Tab3 Lite 7.0 using XDA Labs
Click to expand...
Click to collapse
Yeah, I have.
I've tried 2 different stock roms (Marshmallow, Lollipop) about 10 different times in both stock recovery and TWRP, mixing in some full wipes and just wiping the cache. I've been looking at a whole lot of tutorials on how to go back to stock, to no avail. I've tried modifying the rom so I no longer get the status 7 error (which I dont believe I should need to do) because I get signature verification errors on both my unmodified stock roms.
Sometimes it does do through the installation fine with the modified roms (in TWRP) and everything seems fine until I click reboot. On the screen it says that there is no OS installed, and when I do reboot to the OS I get stuck on the ASUS logo.
Not gonna give up, but a bit of a headache anyway.
I dont believe I have ever unlocked the bootloader, but how would I do that from outside Android?
Thanks in advance, Matt

mapooo said:
Yeah, I have.
I've tried 2 different stock roms (Marshmallow, Lollipop) about 10 different times in both stock recovery and TWRP, mixing in some full wipes and just wiping the cache. I've been looking at a whole lot of tutorials on how to go back to stock, to no avail. I've tried modifying the rom so I no longer get the status 7 error (which I dont believe I should need to do) because I get signature verification errors on both my unmodified stock roms.
Sometimes it does do through the installation fine with the modified roms (in TWRP) and everything seems fine until I click reboot. On the screen it says that there is no OS installed, and when I do reboot to the OS I get stuck on the ASUS logo.
Not gonna give up, but a bit of a headache anyway.
I dont believe I have ever unlocked the bootloader, but how would I do that from outside Android?
Thanks in advance, Matt
Click to expand...
Click to collapse
That's the problem, locked bootloader. forum.xda-developers.com/zenfone-2-laser/general/talking-ze500kl-g-unlock-bootloader-t3352776 there you got the old content, try it, it's from the outside of the phone. If your phone boots after that normaly, you got bootloader unlocked and your phone unbricked.

jocamucko said:
That's the problem, locked bootloader. forum.xda-developers.com/zenfone-2-laser/general/talking-ze500kl-g-unlock-bootloader-t3352776 there you got the old content, try it, it's from the outside of the phone. If your phone boots after that normaly, you got bootloader unlocked and your phone unbricked.
Click to expand...
Click to collapse
Thanks for your help.
My phone is now up and running.
Now I can close my 10 tabs on the Zenfone 2 lol.

mapooo said:
Thanks for your help.
My phone is now up and running.
Now I can close my 10 tabs on the Zenfone 2 lol.
Click to expand...
Click to collapse
It's nothing, that's the least I can do, put that phone to good use! :good:

Help !! you can give me all the files * img
Please

trongnguyen(vietnamese) said:
Help !! you can give me all the files * img
Please
Click to expand...
Click to collapse
Why do you need it? I can only assume that you haven't unlocked your bootloader. More info?

mapooo said:
Why do you need it? I can only assume that you haven't unlocked your bootloader. More info?
Click to expand...
Click to collapse
unbick
help

trongnguyen(vietnamese) said:
unbick
help
Click to expand...
Click to collapse
have you tried unlocking your bootloader?

mapooo said:
have you tried unlocking your bootloader?
Click to expand...
Click to collapse
I want file "img (system.img,boot.img...)

trongnguyen(vietnamese) said:
I want file "img (system.img,boot.img...)
Click to expand...
Click to collapse
I'm not sure if you understand, but it would be helpful if you told us your problem, rather than continuing to nag for an img file. I didn't need it to fix my phone, so without you giving us more info all I can say is try unlocking your bootloader.
I know you want an img file, but if life was that simple, you wouldn't need an img file in the first place *insert inception music*

OK, this is a loooong story. Can someone save my xperiac4?PLS...........

I have a xperia c4 e5303, is a awesome device and 5-6 days ago i wanted to use xposed firmware to enable a fake gyroscope.
AND THE HELL STARTED.
I had the device rooted with custom recovery twrp when i was in lollipop 5.1, i installed the firmware for xposed and the phone was stucked in "android optimization", for hours. I restarded it sometimes but nothing, so i formatted my device and when i rebooted it, i was stucked in "sony" logo screen, some minutes ago i founded that my phone was totally empty.
c: *internal screaming*
I waited the next day, i downloaded the ftf of original marshmallow 6.0 firmware for sony xperia c4 and i installed it on my device, then everything worked perfectly luckely.
Easy peasy lemon squeezy, or not?
Some hours after i founded that i couldn't use the recovery mode!
I searched and searched and i founded that the problem could be the bootloader,so i used a sony official guide to unlock that.
I couldn't finished that guide becouse with any connection, on any computer, android sdk can't install his components(such as google usb driver, that are required for that method), and the program just install everytime the same package in loop. I tried aaaallll the method in the universe for that, i tried also to install once per once the zip files of the downloaded package but it was totally useless.
So i founded another method after some days of searching (with flashtool) and now my bootloader is fully unlocked, if i use flashtool to unlock the bootloader, it says that is unlocked and ask me if i want to relock it so i think now the bootloader unlock is done. FINALLY.
Then, i turned off the phone and started it by pressing the volume down+power botton, and all the device did was reboot himself repitetly until i release hard keys and when i do it the phone start automatically.
I think my device now reboot himself instead of going in recovery mode.
What can i do i am totally frustrated about this and i really don't want to buy a new device becouse i don't have a gyroscope. I love my xperia c4, i just don't know why i can't get the recovery mode back to install twrp, for rooting the device, for retry to get xposed virtual sensor and then finally enjoy my vr experience...
In the end, i have a Xperia C4 5303 with original Marshmallow 6.0 firmware installed, that can't go in recovery mode in any ways.
Pls someone help me..

no one?..
No one here know hot to save my smartphone?

update: now i can use fasboot and adb commands becouse i installed the drivers properly.
but i still can't flash a custom recovery to get the root..

asnachan said:
update: now i can use fasboot and adb commands becouse i installed the drivers properly.
but i still can't flash a custom recovery to get the root..
Click to expand...
Click to collapse
Digging through XDA (next time use the website's search bar, tee hee hee) I found this thread:
https://forum.xda-developers.com/xp.../bootloader-unlocked-custom-recovery-t3285521
Edit: I know it says C5 Ultra whatever but the thread says it also works with your model (C4 E5303 no?)
Before trying anything, I'd seriously recommend reading all eleven pages so you don't miss anything and end killing your phone (or back at square 1).
I'm not an expert on Android or anything (I personally have only owned 1 device — a first gen Moto G), but the method presented in the thread is very odd. Are all Xperia phones this weird?
Read carefully — some steps might be unnecessary (after all, you already unlocked your bootloader [maybe?])
P.S. you lost the recovery because by installing the original firmware it basically got erased (original firmware didn't have TWRP after all!)
P.S.S. you should create a backup once you get TWRP up and running, just in case.
I can't help you more than this because I do not own the device, so I cannot share ~personal wisdom~ with you (beyond recommending the Moto G series).
Good luck!
( And search the forums and threads before posting — that's an XDA rule! )
Sent from my Motorola Moto G using XDA Labs

thx
Bludwurst said:
Digging through XDA (next time use the website's search bar, tee hee hee) I found this thread:
https://forum.xda-developers.com/xp.../bootloader-unlocked-custom-recovery-t3285521
Edit: I know it says C5 Ultra whatever but the thread says it also works with your model (C4 E5303 no?)
Before trying anything, I'd seriously recommend reading all eleven pages so you don't miss anything and end killing your phone (or back at square 1).
I'm not an expert on Android or anything (I personally have only owned 1 device — a first gen Moto G), but the method presented in the thread is very odd. Are all Xperia phones this weird?
Read carefully — some steps might be unnecessary (after all, you already unlocked your bootloader [maybe?])
P.S. you lost the recovery because by installing the original firmware it basically got erased (original firmware didn't have TWRP after all!)
P.S.S. you should create a backup once you get TWRP up and running, just in case.
I can't help you more than this because I do not own the device, so I cannot share ~personal wisdom~ with you (beyond recommending the Moto G series).
Good luck!
( And search the forums and threads before posting — that's an XDA rule! )
Sent from my Motorola Moto G using XDA Labs
Click to expand...
Click to collapse
Thanks a lot for your time, but i am using that thread to root this, and i am stucked at the last point becouse i don't know what he means with:
"THIS IS IMPORTANT
The rom has
Code:
recovery.from.boot.p"
I did all the steps except for that, and i get no errors but when i try to boot in recovery the phone just stay on the logo and then after some minutes reboot himself and starts normally.
i already ask what the last point is in that thread
p.s.: i know i will not have twrp if i reinstall stock fw, but the point is that i don't have also the normal recovery, i can't access to that via adb or via hard keys..

asnachan said:
Thanks a lot for your time, but i am using that thread to root this, and i am stucked at the last point becouse i don't know what he means with:
"THIS IS IMPORTANT
The rom has
Code:
recovery.from.boot.p"
I did all the steps except for that, and i get no errors but when i try to boot in recovery the phone just stay on the logo and then after some minutes reboot himself and starts normally.
i already ask what the last point is in that thread
p.s.: i know i will not have twrp if i reinstall stock fw, but the point is that i don't have also the normal recovery, i can't access to that via adb or via hard keys..
Click to expand...
Click to collapse
Ah. You should've mentioned it (i.e. linked to the guide). Sorry sorry!
Read further down. The "recovery.from.boot.p" is this thing that overwrites TWRP with the stock recovery. Following the «THIS IS IMPORTANT» indication are instructions to get rid of the thing, and so being able to keep TWRP permanently.
You need that last step to succeed.
Sent from my Motorola Moto G using XDA Labs

in the other thread they said to me to roll back to 5.1 i am doing it now

nvm i got hard brick, the phone is dead and i can't enter in download mode....

asnachan said:
nvm i got hard brick, the phone is dead and i can't enter in download mode....
Click to expand...
Click to collapse
I'm very sorry to hear that ?
Sent from my Motorola Moto G using XDA Labs

Is fine, i had to buy another phone that is why is tarted to root the xperia.
just..i'm out from the world of rooting i think. i broke 2 devices 1 by flashing a original rom with sony original flashtool and 1 by installing a root with kigroot, and now on that i can't read the sim.
i wait until the world of rooting will be more stable and with more official custom roms...

RIP