Related
I had a rooted AT&T play, rt800at. I recently installed clockwork mod recovery without unlocking the bootloader using the new method in the development section. I then backed up my stock image and downloaded and attempted to install the GSX ROM. I wiped userdata, and cache (including dalvik) before trying to flash the ROM. Now when I start up I get the Sony Ericsson text and the phone hangs there. I can't get back into recovery to restore my nandroid backup. What can I do?
Check in the cwm thread ; i also had a similar brick ; how i fixed it is in the thread in the first few pages i believe.
This one? There's nothing about a brick here though... http://forum.xda-developers.com/showthread.php?t=1130639
No , this one .http://forum.xda-developers.com/showthread.php?t=1390771
Here's my post on how to fix it :
Retrying on SEUS(Sony Ericsson Update Service) several times. NOTE - This means pressing the retry button when it says you have failed ; not closing the app and opening it again - I did this as well and it didnt work.
Thanks for the info. However I already fixed it a different way.
I basically just stumbled around, but this is how I did it:
The phone wouldn't get into recovery, so I couldn't restore the backup I made just before I started screwing around with it. To get around this I used flashtool to flash a random stock .ftf, then rooted that and used the method to install CWM without unlocking the bootloader. All I had to do then was reboot into recovery and restore my backup.
Hi there, I have a Nexus 4 that is bricked (I think) and I don't know of any way of fixing it.
What happened was that when I was trying to flash PSX 4.4 I had stock recovery somehow (had it before, phone is unlocked and rooted) so I went to install that via Nexus root toolkit and it booted into temporary TWRP and it was on the latest version and didn't do anything so I figured it was installed. I proceeded by wiping system, data, cache, and dalvik cache as the PSX post had said to do.
I then proceeded to install PSX 4.4 Kitkat (Latest version) and when it went to boot into it after installing (didn't see it install on the phone via TWRP recovery) it didn't boot into android.
I then went on to find out that TWRP was never actually installed, only booted into temporarly to install itself (which it didn't.) So I tried installing TWRP again from the battery meter, boot up google screen, fastboot mode, and recovery mode. None of these work, and I can't acsess my Nexus 4's internal storage via my PC. My phone is brcked, correct? Is there a way out of this
Please help
I can't see how bootloader was wiped from what you describe
So what happens when you boot your phone, black screen? Absolutely nothing?
And when you hold various combos of volume rocker and power on, nothing?
Plug into PC, led? Nothing?
Sent from my Nexus 7 using Tapatalk 2
Are you using a toolkit to do all this?
Hold Volume Down + Power to get into the bootloader.
xXDustinoXx said:
Hi there, I have a Nexus 4 that is bricked (I think) and I don't know of any way of fixing it.
What happened was that when I was trying to flash PSX 4.4 I had stock recovery somehow (had it before, phone is unlocked and rooted) so I went to install that via Nexus root toolkit and it booted into temporary TWRP and it was on the latest version and didn't do anything so I figured it was installed. I proceeded by wiping system, data, cache, and dalvik cache as the PSX post had said to do.
I then proceeded to install PSX 4.4 Kitkat (Latest version) and when it went to boot into it after installing (didn't see it install on the phone via TWRP recovery) it didn't boot into android.
I then went on to find out that TWRP was never actually installed, only booted into temporarly to install itself (which it didn't.) So I tried installing TWRP again from the battery meter, boot up google screen, fastboot mode, and recovery mode. None of these work, and I can't acsess my Nexus 4's internal storage via my PC. My phone is brcked, correct? Is there a way out of this
Please help
Click to expand...
Click to collapse
lets clarify, can u still see google logo? can u still enter fastboot mode?
Sorry I never relpied, don't even remmber how this happend, or how I fiex
Thanks for all of the answers guys, sorry I never replied to them. don't even remember how this problem happened, or how I fixed it;. I'm experiencing a similar problem and nothing's working; I'll open a new thread now with more info so I hopefully can get it up and running
Hi guys im a bit rusty again in all this since i rooted my S3 and HTC desire years ago ,
I have an Galaxy S5 SM-G900F (bought seperately without any provider)(EU)
after 2-3 months now and getting the official android 5.0 upgrade, i thought it be time to Root my device again ,
i followed this link and how to from ChainFire "http://forum.xda-developers.com/showthread.php?t=2696537"
wich i been using on my Galaxy Tab 7 Lite(T110) as well and worked flawlessly
I followed the exact steps as usual , rooting went fine, phone rebooted as it should , i updated SUPERSU and its binaries and installed Ericson's Busybox,. ,and everything worked as it should ,
then i put off my phone and boot in to recovery mode to flash the Philz_touch_6.26.1-klte.zip (touch recovery)
when im in my stock recovery i facepalm'd myself because i hadnt put the flashable recovery file on my internal storage yet ,
so i wanted to reboot back in the phone so i could put the file on my internal storage so id be able to flash it from stock recovery ,,..
this is where it all got strange,.
My phone stays black after Boot logo, gives me errors like ,. SYSTEM UI STOPPED ,. and so on for about everything that keep the phone running , i mean really everything STOPS , after about 15 minutes and klicking away all the Stopped msg's , it just reboots again to do the same.
i tried starting the phone in SAFE MODE ,. . Same thing,...
this all just came up after i booted to STOCK RECOVERY ,. and back to Android without changing anything,.
Android 5.0
Stock Rom
CF Autoroot klte SM-G900F
Please help ?
Thank you in advance
Mike130784 said:
Hi guys im a bit rusty again in all this since i rooted my S3 and HTC desire years ago ,
I have an Galaxy S5 SM-G900F (bought seperately without any provider)(EU)
after 2-3 months now and getting the official android 5.0 upgrade, i thought it be time to Root my device again ,
i followed this link and how to from ChainFire "http://forum.xda-developers.com/showthread.php?t=2696537"
wich i been using on my Galaxy Tab 7 Lite(T110) as well and worked flawlessly
I followed the exact steps as usual , rooting went fine, phone rebooted as it should , i updated SUPERSU and its binaries and installed Ericson's Busybox,. ,and everything worked as it should ,
then i put off my phone and boot in to recovery mode to flash the Philz_touch_6.26.1-klte.zip (touch recovery)
when im in my stock recovery i facepalm'd myself because i hadnt put the flashable recovery file on my internal storage yet ,
so i wanted to reboot back in the phone so i could put the file on my internal storage so id be able to flash it from stock recovery ,,..
this is where it all got strange,.
My phone stays black after Boot logo, gives me errors like ,. SYSTEM UI STOPPED ,. and so on for about everything that keep the phone running , i mean really everything STOPS , after about 15 minutes and klicking away all the Stopped msg's , it just reboots again to do the same.
i tried starting the phone in SAFE MODE ,. . Same thing,...
this all just came up after i booted to STOCK RECOVERY ,. and back to Android without changing anything,.
Android 5.0
Stock Rom
CF Autoroot klte SM-G900F
Please help ?
Thank you in advance
Click to expand...
Click to collapse
Boot to recovery, wipe the caches, reboot, see how you get on then
*Detection* said:
Boot to recovery, wipe the caches, reboot, see how you get on then
Click to expand...
Click to collapse
thank you for your reply
i have wiped the Cache partitions as its the only cache to wipe in stock recovery,. rebooted ,. but still the same thing
Mike130784 said:
thank you for your reply
i have wiped the Cache partitions as its the only cache to wipe in stock recovery,. rebooted ,. but still the same thing
Click to expand...
Click to collapse
Did you use the latest version of ODIN to flash the CF Root?
Think Odin3 v3.10.6 is the latest current version
If you used an old version, try flashing it again using the new one, other than that, I can only suggest trying to fix permissions in recovery if it has that option, TWRP should have it, and finally a factory reset, which is not ideal
*Detection* said:
Did you use the latest version of ODIN to flash the CF Root?
Think Odin3 v3.10.6 is the latest current version
If you used an old version, try flashing it again using the new one, other than that, I can only suggest trying to fix permissions in recovery if it has that option, TWRP should have it, and finally a factory reset, which is not ideal
Click to expand...
Click to collapse
i used Odin3-v3.07
but after flashing the root everything worked installed superSU and updated it and its binaries and installed busybox,.
it all stopped working after i went into Stock Recovery and back
id prefer not to do a factory reset Wipe,. unless i really have to to fix it ,.
im going to try reflash with the latest version then,.
i have swapped SD card to galaxy tab to put the Flashable touch recovery on the SD card, and swapped back to the phone so i could Flash the Recovery when im in stock ,.
but ill try flashing Root with latest Odin first.. thank you
*Detection* said:
Did you use the latest version of ODIN to flash the CF Root?
Think Odin3 v3.10.6 is the latest current version
If you used an old version, try flashing it again using the new one, other than that, I can only suggest trying to fix permissions in recovery if it has that option, TWRP should have it, and finally a factory reset, which is not ideal
Click to expand...
Click to collapse
the new odin is a bit less informative (to me as beginner)
i managed to use AP to flash the root again
all goes fine , it reboots
and its now upgrading android as it says and opening app's
then Black screen again,. i klick a button,. and it shows me again all the STOPPED msg's of all internal apps that are crashing,. litterally all apps,
what can i do ?
If clearing cache didn't work, fixing permissions in recovery didn't work, only thing left I can think of is factory reset
--
*Detection* said:
If clearing cache didn't work, fixing permissions in recovery didn't work, only thing left I can think of is factory reset
--
Click to expand...
Click to collapse
i cant fix persmission in stock recovery and flashing the philz touch recovery didnt work something about not verify signature,.
al i can do i guess is wipe data factory reset ,.but im affraid it wont fix anything
Try TWRP recovery instead
http://teamw.in/project/twrp2/229
No reason a factory reset won't fix things, worst comes to worst, flash the whole ROM again from ODIN, that will fix everything as it wipes and reinstalls the lot
Grab a stock ROM from sammobile
Thank you for all your replys mate..
I managed to get it working again by doing a factory reset in stock recovery after I flashed root with latest odin
Even tho it was my last resort there was nothing else I guess .
I'm not sure tho if this will happen again when I go back to recovery like I did when this all happend the first time while I actually want to flash a more advanced recovery then stock recovery ..
But I'll take my chances and just leave it as it is
Again thank you for your help and suggestions .
This thread could be closed
Sent from my SM-G900F using XDA Free mobile app
Pleased you got it working again, I would say if you think you might want to flash another advanced recovery in the future, it might be best to do that now since you have already factory reset the phone, that way if this happens again, you don't lose months of data and settings and files that you have gathered between now and whenever you decide to flash recovery
*Detection* said:
Pleased you got it working again, I would say if you think you might want to flash another advanced recovery in the future, it might be best to do that now since you have already factory reset the phone, that way if this happens again, you don't lose months of data and settings and files that you have gathered between now and whenever you decide to flash recovery
Click to expand...
Click to collapse
i have actually ,. i installed the TWRP u mentioned,. by taking there app from the Playstore,. and flashed the new recovery, within android and without rebooting (just in case)
im used to the old CWM thats why i first wanted the Touch recovery as its based on it,
but always open for trying new things
Thank you
Good stuff
Id say the whole entering recovery / apps crashing thing was a problem with the ODIN version you used to root, too old for Lollipop is my guess, so I wouldn't worry about entering recovery again.
Hi,
I have Defy MB525 and I currently flashed JORDN_U3_97.21.51.sbf.
I read most of the guides here, but I'm still in the loop - cannot get working TWRP to install latest CM11.
I flashed Recovery BootStrap v4 (TWRP) but when the phone starts booting, it ends up with the following screen and I cannot go foward.
It doesn't matter, what I choose (Recovery or continue.). When I press the menu button (to choose Recovery), nothing happen, till the 3rd press - than the display goes black and thats all .
Maybe its related to the bootloader version, which is 09.10 or is there any prerequisite to successfully install TWRP?
Any idea where could be the problem or what I'm doing wrong?
Thank you in advance
Issue fixed
Even that nobody replied, I finally fixed this issue, so I will post here the solution, which may help to anybody else:
I finally found the sbf file, which is working with my Defy: http://motoroladefyall.nortol.info/motorola/joe30_236_DFP-231_Magyaritasa/DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf.gz
After flashing this, the phone finally booted and saying its MB526, but never mind...
Then I rooted the phone with Framaroot app and installed the TWRP recovery (bootstrap). This time SuperUser was asking for root permission, so I granted it, flashing recovery was finished and the phone was rebooted.
Then the recovery was finally working, so I flashed the resize.zip, latest CM11 and minimal GAPPS.
And hurray, my Defy is finally running with the latest KK
Hi.
I've run into a bit of a problem.
I have unlocked the bootloader of my XC, and when I install TWRP 3.1.1 it boots fine if I just let it boot right after installation. If, however, I launch TWRP and reboots without doing anything, the phone gets stuck on Sony logo during boot.
I've tried flashing the XC Genesis kernel 1.06 first in fastboot, and then immediately after flash TWRP 3.1.1, which does the same. Boots fine if I don't launch TWRP, but as soon as it has been launched and rebooted, it gets stuck on Sony logo.
I've then tried to create a completely preflashed rom with PRF Creator, but that just bootlooped twice and switched the phone off.
Is there anything else to try? I really want to root my phone, to get rid of stupid bloatware and take control over my phone.
Thunderjew said:
Hi.
I've run into a bit of a problem.
I have unlocked the bootloader of my XC, and when I install TWRP 3.1.1 it boots fine if I just let it boot right after installation. If, however, I launch TWRP and reboots without doing anything, the phone gets stuck on Sony logo during boot.
I've tried flashing the XC Genesis kernel 1.06 first in fastboot, and then immediately after flash TWRP 3.1.1, which does the same. Boots fine if I don't launch TWRP, but as soon as it has been launched and rebooted, it gets stuck on Sony logo.
I've then tried to create a completely preflashed rom with PRF Creator, but that just bootlooped twice and switched the phone off.
Is there anything else to try? I really want to root my phone, to get rid of stupid bloatware and take control over my phone.
Click to expand...
Click to collapse
You have to run a modified kernel to be able to boot into custom recovery and allow modifications, else you end up in this bootloop. The proper procedure is flash the firmware you want, flash the kernel, then flash twrp and format data so that you can get rid of the encryption. From there you will be able to boot into the phone and twrp and can start flashing magisk and xposed.
kekistaneerefugee said:
You have to run a modified kernel to be able to boot into custom recovery and allow modifications, else you end up in this bootloop. The proper procedure is flash the firmware you want, flash the kernel, then flash twrp and format data so that you can get rid of the encryption. From there you will be able to boot into the phone and twrp and can start flashing magisk and xposed.
Click to expand...
Click to collapse
Thanks for the reply. I would prefer to use the stock firmware, but get it rooted. Would that still work? And when you say format, you mean after I've installed TWRP, I format the phone from there and wipe data, dalvik and cache, right? And a last question, can't I use SuperSU? I remember using xPosed once, and I wasn't that big of a fan.
Thunderjew said:
Thanks for the reply. I would prefer to use the stock firmware, but get it rooted. Would that still work? And when you say format, you mean after I've installed TWRP, I format the phone from there and wipe data, dalvik and cache, right? And a last question, can't I use SuperSU? I remember using xPosed once, and I wasn't that big of a fan.
Click to expand...
Click to collapse
This is the procedure for stock firmware, there isn't really anything other than stock firmware available for this phone. The way that I used the XC Genesis kernel was to use the no drm fix one and us ta_poc to put in my stock ta keys so that I have a completely stock phone with unlocked bootloader. The drm patch one should work the same however.
When I say format I'm not saying wiping, I mean format. There is a whole separate option in Wipe that is "format data", that is what you need to do since nougat automatically encrypts your data and doesn't allow modifications, you need to backup whatever you may have on internal memory before doing this. This is essentially a factory reset so do it before setting anything up.
And yes you can use SuperSu but its not recommended as its sold to a chinese company and no longer open source, Magisk is the new thing to root with and still lets you pass safetynet where as superSU does not.
kekistaneerefugee said:
This is the procedure for stock firmware, there isn't really anything other than stock firmware available for this phone. The way that I used the XC Genesis kernel was to use the no drm fix one and us ta_poc to put in my stock ta keys so that I have a completely stock phone with unlocked bootloader. The drm patch one should work the same however.
When I say format I'm not saying wiping, I mean format. There is a whole separate option in Wipe that is "format data", that is what you need to do since nougat automatically encrypts your data and doesn't allow modifications, you need to backup whatever you may have on internal memory before doing this. This is essentially a factory reset so do it before setting anything up.
And yes you can use SuperSu but its not recommended as its sold to a chinese company and no longer open source, Magisk is the new thing to root with and still lets you pass safetynet where as superSU does not.
Click to expand...
Click to collapse
Thank you very much for helping understand this. I will give it another go at some point, hoping I'll get it to work then. Thanks again.
Hello guys,
sorry for archeology but I got exaclty just the same problem.
Yesterday I decided to flash 34.3.A252 onto my XC. SO the soft itself works fine - later I decided to flash newest twrp for Kugo, 3.2.3-0.
So exactly as Thunderjew has said - after I enter TWRP once I got stuck on Sony logo.
So whats the right order of things here?
I flash stock rom -> then I flash kernel -> and then TWRP?
What about the Encryption - should I apply any? I'd very much like to have my device encrypted. Is it even possible?
But - anyone knows wher I can find working Kernel file for this firmware? Or which version from ggow would work?