Hi all,
As the title says pretty much. I tried to install the SlimKat rom, being new to installing ROMs I followed the instructions and somehow my phone has pretty much been bricked. I hold the power button and the phone vibrates, but nothing on the screen turns on and nothing gives me hints that it is working in any other manner. I can't boot into recovery either when I hold power button + volume up. Any solutions on how I could possibly reset or get the ROM working?
The1Dirk said:
Hi all,
As the title says pretty much. I tried to install the SlimKat rom, being new to installing ROMs I followed the instructions and somehow my phone has pretty much been bricked. I hold the power button and the phone vibrates, but nothing on the screen turns on and nothing gives me hints that it is working in any other manner. I can't boot into recovery either when I hold power button + volume up. Any solutions on how I could possibly reset or get the ROM working?
Click to expand...
Click to collapse
1. non stock based custom roms require you to unlock your bootloader as not doing so will result in a brick
anyway try this to recover your device -> http://forum.xda-developers.com/showpost.php?p=53968631&postcount=35
you should be able to exclude wipe data when your about to flash a Stock FTF to prevent data loss as your internal will be wiped with your user data
see Step 4
Envious_Data said:
1. non stock based custom roms require you to unlock your bootloader as not doing so will result in a brick
anyway try this to recover your device -> http://forum.xda-developers.com/showpost.php?p=53968631&postcount=35
you should be able to exclude wipe data when your about to flash a Stock FTF to prevent data loss as your internal will be wiped with your user data
see Step 4
Click to expand...
Click to collapse
I previously unlocked the bootloader but then did a factory reset, perhaps that re-locked the bootloader? Anyways, thanks for the link, will get back to you in a few hours.
The1Dirk said:
I previously unlocked the bootloader but then did a factory reset, perhaps that re-locked the bootloader? Anyways, thanks for the link, will get back to you in a few hours.
Click to expand...
Click to collapse
i think this depends on how you reset
try checking if your bootloader is unlocked after you repair your device, try looking on the service menu
You can also use this method to Install stock Android OS on your Device :
http://forum.xda-developers.com/sony-xperia-c/general/how-to-install-restore-stock-android-t2832005
And this website to unlock your Bootloader:
http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
Related
Anyone know how to go about this on my GSII?
Planning on flashing to Stock and would prefer a fresh start, would just flashing the firmware be sufficient?
I do remember seeing a reset option when pressing power+home+vol down on start. Would ideally like everything to go back to factory and all data deleted, basically factory fresh.
Thanks Guys.
Chronicles404 said:
Anyone know how to go about this on my GSII?
Planning on flashing to Stock and would prefer a fresh start, would just flashing the firmware be sufficient?
I do remember seeing a reset option when pressing power+home+vol down on start. Would ideally like everything to go back to factory and all data deleted, basically factory fresh.
Thanks Guys.
Click to expand...
Click to collapse
Have you rooted and flashed anything or changed anything on /system?
If not, the reset option in recovery would be fine.
If you have, you would need to reflash.
pulser_g2 said:
Have you rooted and flashed anything or changed anything on /system?
If not, the reset option in recovery would be fine.
If you have, you would need to reflash.
Click to expand...
Click to collapse
Thanks for the prompt reply.
Rooted yes, though not sure if anything is changed on/system as a result (I personally haven't).
I've an O2 Handest so would like to unbrand, hence I would be flashing to the actual stock Rom so I'm assuming I would need to Root again anyhow?
Just wondering If I would need to reset then flash, or would flash be sufficient and get rid of everything in the process?
A flash should be enough to clear out anything left behind.
You would obviously flash the O2 UK firmware, and you would want to reset the download mode counter (see the dev section) before you presented it as an "untouched" phone
So I attempted to get my phone from Paranoid to back to stock but I completely messed up. I basically restored my phone to CM 10, then I tried to relock my phone from there. So I used this video:
youtube.com/watch?v=5yS7yy4XVA4
and now I have fastboot with no rom and no recovery (also everytime i reboot from fastboot, it goes straight back to it). If anyone could help, what should my next step be? it would greatly be appreciated.
If you locked the bootloader you will have to unlock it first, then flash recovery and a rom. Did you unlock manually or with regawmod?
om4 said:
If you locked the bootloader you will have to unlock it first, then flash recovery and a rom. Did you unlock manually or with regawmod?
Click to expand...
Click to collapse
I have noticed a lot of poeple have this same problem coming from cm10/aosp/aokp thier OS and recovery disappear
Some people are just wiping system by mistake
om4 said:
Some people are just wiping system by mistake
Click to expand...
Click to collapse
It happened to a friend of mine and now this is maybe the 10th time I have seen this
Yeah, I'll agree it's happening too often but all aosp ROMs are still in pretty early development despite working as well as they do
I actually got it back unlocked (manually) but to get back to sense, what would you suggest?
You still need to flash twrp if you haven't done so and for a bare stock rom there's stock with goodies and there is another one with out
Now that we have root and are able to backup the TA partition (which I have done) I now feel comfortable with flashing custom recoveries/roms/kernels however I'm unsure of a few things as I haven't owned a modern sony device having had HTC as my previous android smartphones (and WinMo too although messing about on WinMo was super fun and easy and pretty much bulletproof.... I miss those days).
From what I gather, unlocking the boatloader is a fairly straight forward process much similar to the htcdev method necessary for the One X, send info to Sony, receive unlock token, proceed with unlock.
With this in mind I want to do 3 things: -
1. Use Philz touch recovery. I used this on the One X so I'm familiar with it and find it to be easy and robust to use
2. Use doomkernel - being able to fine tune power usage and cpu usage interests me greatly
3. Use RomAur, I'm always a fan of stock looking roms with great customisability for example on my One X, I used Mike1986's ARHD Rom.
So far as I understand, for my purposes points 1 and 2 are combined as doomlord included Philz touch recovery in his kernel, is this correct?
Now this is where I'm a little confused or perhaps mislead, some guides are saying to install .402 ftf before flashing anything else if on a previous version rom, in my case official .55 but if I'm doing a full system wipe and install, is it not simpler just to flash the recovery and boot into recovery and flash a new rom from there (having the new rom located on sd card like traditionally done) if so then this leads me on to the next stage.
I understand that to flash the kernel/recovery, I turn the phone off, hold volume up or down I think it must be volume up as volume down is to enter flashmode correct? And connect to the pc and perform the actions "fastboot flash boot boot.img" exactly like that on the HTC One X, is this also correct? After that, how do I boot into recovery?
I apologise for the longwinded thread but whenever I do this kind of thing, I like to be thorough and have everything correct, you know, the measure twice cut once mentality. If anyone can confirm these details and if necessary point me in the right direction of what to do if I have anything wrong, I'd greatly appreciate it. Thanks
TheOnlyIntruder said:
Now that we have root and are able to backup the TA partition (which I have done) I now feel comfortable with flashing custom recoveries/roms/kernels however I'm unsure of a few things as I haven't owned a modern sony device having had HTC as my previous android smartphones (and WinMo too although messing about on WinMo was super fun and easy and pretty much bulletproof.... I miss those days).
From what I gather, unlocking the boatloader is a fairly straight forward process much similar to the htcdev method necessary for the One X, send info to Sony, receive unlock token, proceed with unlock.
With this in mind I want to do 3 things: -
1. Use Philz touch recovery. I used this on the One X so I'm familiar with it and find it to be easy and robust to use
2. Use doomkernel - being able to fine tune power usage and cpu usage interests me greatly
3. Use RomAur, I'm always a fan of stock looking roms with great customisability for example on my One X, I used Mike1986's ARHD Rom.
So far as I understand, for my purposes points 1 and 2 are combined as doomlord included Philz touch recovery in his kernel, is this correct?
Now this is where I'm a little confused or perhaps mislead, some guides are saying to install .402 ftf before flashing anything else if on a previous version rom, in my case official .55 but if I'm doing a full system wipe and install, is it not simpler just to flash the recovery and boot into recovery and flash a new rom from there (having the new rom located on sd card like traditionally done) if so then this leads me on to the next stage.
I understand that to flash the kernel/recovery, I turn the phone off, hold volume up or down I think it must be volume up as volume down is to enter flashmode correct? And connect to the pc and perform the actions "fastboot flash boot boot.img" exactly like that on the HTC One X, is this also correct? After that, how do I boot into recovery?
I apologise for the longwinded thread but whenever I do this kind of thing, I like to be thorough and have everything correct, you know, the measure twice cut once mentality. If anyone can confirm these details and if necessary point me in the right direction of what to do if I have anything wrong, I'd greatly appreciate it. Thanks
Click to expand...
Click to collapse
1.Take note that if you restore your TA on a custom kernel it will brick because its equivilent to relocking on a custom kernel
2. Volume up is fastboot mode ususaly used for flashing kernels, volume down is flashmode (usualy firmware flashing n fixing)
3.to boot into recovery using doomkernel you press the camera button when the purple LED with vibrate shows, if ur using philz reovery advanced stock then it would be volume up
(Doomkernel has TWRP (vol down) and CWM (vol up))
4.you can flash directly to 402 with the respective kernel, you do need to wipe since your jumping a firmware set, going to from 55 to 69 is fine but not 402 because its B 402 and not A 402 un like 17.1.A.55 or 69 its 17.1.1.B.402 (or something of a new set)
If i missed something just ask
Sent from my D6503 using XDA Premium 4 mobile app
Envious_Data said:
1.Take note that if you restore your TA on a custom kernel it will brick because its equivilent to relocking on a custom kernel
Click to expand...
Click to collapse
Yeah I wont be relocking the bootloarder, I understand that to restore the TA the kernel and rom need to be on stock for that so that's no problem.
Envious_Data said:
3.to boot into recovery using doomkernel you press the camera button when the purple LED with vibrate shows, if ur using philz reovery advanced stock then it would be volume up
(Doomkernel has TWRP (vol down) and CWM (vol up))
Click to expand...
Click to collapse
So I have to powerup the phone and wait for the LED to flash before pressing the button or is it a case of hold camera and turn on power?
Envious_Data said:
4.you can flash directly to 402 with the respective kernel, you do need to wipe since your jumping a firmware set, going to from 55 to 69 is fine but not 402 because its B 402 and not A 402 un like 17.1.A.55 or 69 its 17.1.1.B.402 (or something of a new set)
Click to expand...
Click to collapse
Yeah that's what I intend to do, flash kernel, boot into recovery, install new rom from SD card doing full wipe in the process or do I have to push the rom from my pc over usb cable?
With the recovery press the camera button a couple of times when the LED shows
Put the files on your Sd and flash, i tested and its only your internal storage which is wiped but id still backup your Sd contents
Sent from my D6503 using XDA Premium 4 mobile app
Excellent, thank you so much!
The process is pretty much very similar to that of the HTC One X then.
Unlock bootloader, flash kernel, reboot into recovery, flash rom - Enjoy customised Xperia Z2.
Thanks again
Hi,
I am using 8 GB version. I had rooted it some time back. Now since the phone was hanging few times, i did factory reset (as i understand now, may be was not a good option). Phone did boot one or two times since then, but crashed immediately. Afterwords, phone gets stuck at lenovo logo if I try rebooting.
I am a novice in this, so couldn't figure out the exact process (from the numerous related threads). Would greatly appreciate any help.
Chinmay
kchinmay14 said:
Hi,
I am using 8 GB version. I had rooted it some time back. Now since the phone was hanging few times, i did factory reset (as i understand now, may be was not a good option). Phone did boot one or two times since then, but crashed immediately. Afterwords, phone gets stuck at lenovo logo if I try rebooting.
I am a novice in this, so couldn't figure out the exact process (from the numerous related threads). Would greatly appreciate any help.
Chinmay
Click to expand...
Click to collapse
Hi. If its not too late look what you must do(this are some guide lines you must read alot in Q&A section):
1. First you must install Lenovo drivers. At the bottom of the page.
2. Now you must know if you have stock or custom recovery. To do that you must power down your phone and start with volume - and + and power buttons pressed all toghether. The phone must start in something called TWRP, CWM or stock recovery witch is very simple.
3. from there are few choices: go to wipe and wipe cache and data then reboot and see what happent, maybe the phone will start.... or you must flash another custom firmware and the phone will allso start. For custom firmware you must know and tell us what was your base firmware: chinese or ROW. ORRRR.... flash with SP Flash Tool another base firmware .... This is more difficult. Needs some basic knowledge about flashing.
Good Luck.
stympy said:
Hi. If its not too late look what you must do(this are some guide lines you must read alot in Q&A section):
1. First you must install Lenovo drivers. At the bottom of the page.
2. Now you must know if you have stock or custom recovery. To do that you must power down your phone and start with volume - and + and power buttons pressed all toghether. The phone must start in something called TWRP, CWM or stock recovery witch is very simple.
3. from there are few choices: go to wipe and wipe cache and data then reboot and see what happent, maybe the phone will start.... or you must flash another custom firmware and the phone will allso start. For custom firmware you must know and tell us what was your base firmware: chinese or ROW. ORRRR.... flash with SP Flash Tool another base firmware .... This is more difficult. Needs some basic knowledge about flashing.
Good Luck.
Click to expand...
Click to collapse
Thanks a lot Stympy ! The Q &A section was very helpful and I was able to figure out the way. In fact, the google pay store issue (i had messaged you about) was after flashing S228 ROW version.
Hi, I rooted my phone using the method that's listed under root info on this forum. Everything went well, and I successfully rooted my phone using TWRP (I checked using an app, I even had the pop up from 'super su' to allow access), however the final step of the video was to install a kernel. I can't link it due to being a new user, but it's called "[Kernel][surnia] Squid Kernel for Moto E LTE (2015)" and it's in the description for the video. I copied the .zip file to my sd card, went into fastboot and recovery and installed it. Afterwards, I was looking through the options, and saw the option to remove the dalvik cache. From my understanding, the dalvik cache is a useless cache space that you can free up for more space, so I deleted it. I then went to the reboot system and hit 'system', as given the other options I assumed that would just be a regular restart. When I opened it back up, I was stuck at the 'warning unlocked bootloader' for a good 10-15 minutes. I went to turn it off by holding down the power button, which turned off the screen momentarily but when I released the button the screen turned back on. I went into fastboot mode successfully and did a factory reset from TWRP, after which my phone went back into the unlock bootloader mode, for which it stayed for a few minutes then went into the normal boot screen (you know, the one with the globe). After that it went back to bootloader, then back to globe, repeated a couple of times, then started up and gave me the default setup process it makes when you first get it. I tried doing a factory reset through the settings, same thing happened again. SuperSU is installed as is TWRP, however my phone isn't recognizing the SIM card and wifi isn't working. I'm considering flashing a stock recovery image however given how badly I've ****ed up so far, I don't want to try anything else without advice. I still plan to root it, however I just won't install the kernel since that's what seemed to mess it up the first time. I did not create a backup image though I suppose it doesnt matter anyways, I had nothing on it after unlocking the bootloader. What I'm asking here is: what do I do to restore my phone?
Thank you in advance!
EDIT: I should mention that my model is XT1527, and I can't find any stock images for that model.
wlftmoi said:
EDIT: I should mention that my model is XT1527, and I can't find any stock images for that model.
Click to expand...
Click to collapse
Stock images can be found here: http://forum.xda-developers.com/moto-e-2015/general/stocks-firmwares-moto-e-t3113235
If you're in the US and it's a Moto-direct model (not a model sold by carriers), it's XT1527_SURNIA_RETUS_5.1_LPI23.29-18.9_cid9_subsidy-DEFAULT_CFC.xml.zip
xtermmin said:
Stock images can be found here: http://forum.xda-developers.com/moto-e-2015/general/stocks-firmwares-moto-e-t3113235
If you're in the US and it's a Moto-direct model (not a model sold by carriers), it's XT1527_SURNIA_RETUS_5.1_LPI23.29-18.9_cid9_subsidy-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
I'm downloading that one right now and I'm going to follow the instructions listed here: http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3044936
Thank you!
Sounds to me like you may have flashed a version of squids kernel that is not compatible with your ROM. Make sure the kernel is appropriate for whichever version of Android your ROM is.
And I assume you cleared (rather than "removed") dalvik cache - it is necessary for the device to function, and clearing it after flashing software is generally advised - when cleared it will rebuild itself on the next boot.
Sent from my XT1526 using Tapatalk