relock bootloader with a custom recovery - Nexus 5X Q&A, Help & Troubleshooting

I haveunlocked bootloader and a custom recovery, then flashed the PureNexus ROM.
Then I relock the bootloader with a custom recovery.
Now it became a brick, can I fix it?

kukudi said:
I haveunlocked bootloader and a custom recovery, then flashed the PureNexus ROM.
Then I relock the bootloader with a custom recovery.
Now it became a brick, can I fix it?
Click to expand...
Click to collapse
What do you mean it became a brick. What's happening? Bootloop? Not turning on at all?

abaaaabbbb63 said:
What do you mean it became a brick. What's happening? Bootloop? Not turning on at all?
Click to expand...
Click to collapse
If I turn it on, it Bootloop. I can go to the TWRP recovery, but it can't do anything, it need to type a password to decrypt

kukudi said:
If I turn it on, it Bootloop. I can go to the TWRP recovery, but it can't do anything, it need to type a password to decrypt
Click to expand...
Click to collapse
Do you have any data on the phone (apps, etc)? Did it go into a bootloop exactly after you flashed the new ROM, or did you manage to boot it?

Turn on phone with volume down+power to boot into bootloader; using fastboot unlock bootloader as you did first. Then you can do anything, I.E. flash full stock factory image and start over if you want.
Never lock the bootloader if you are not completely stock.

You can't get it to boot back into fastboot?

abaaaabbbb63 said:
Do you have any data on the phone (apps, etc)? Did it go into a bootloop exactly after you flashed the new ROM, or did you manage to boot it?
Click to expand...
Click to collapse
No, I just flashed the PureNexus ROM & gapps, and have not install any apps. Then I reboot to the bootloader and locked the bootloader, when I reboot to the system, I found it go into a bootloop, I have wait 30min, still bootloop. I connected it to the PC, use "adb reboot bootloader", tried to unlock the bootloader, but failed, because I have not turned on the "oem unloclk" in the system.

gpvecchi said:
Turn on phone with volume down+power to boot into bootloader; using fastboot unlock bootloader as you did first. Then you can do anything, I.E. flash full stock factory image and start over if you want.
Never lock the bootloader if you are not completely stock.
Click to expand...
Click to collapse
I can't unlocked the bootloader again. Because I have not turned on the "oem unlock" in the system

jgummeson said:
You can't get it to boot back into fastboot?
Click to expand...
Click to collapse
I can get it boot to fastboot, but I can't unlock the bootloader.

kukudi said:
I can get it boot to fastboot, but I can't unlock the bootloader.
Click to expand...
Click to collapse
Did you set up a password before locking the bootloader? Try putting in your password.
If not, I found this reddit thread, see what happens in TWRP when you type: default_password

SlimSnoopOS said:
Did you set up a password before locking the bootloader? Try putting in your password.
If not, I found this reddit thread, see what happens in TWRP when you type: default_password
Click to expand...
Click to collapse
Thank you, something surprising. I power on the device just now, and go to the TWRP, it do not need a password anymore, and can mont to the PC with MTP.
But still can not be unlocked, and can't go to the system, bootloop.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

kukudi said:
Thank you, something surprising. I power on the device just now, and go to the TWRP, it do not need a password anymore, and can mont to the PC with MTP.
But still can not be unlocked, and can't go to the system, bootloop.
View attachment 3604831
Click to expand...
Click to collapse
Install your rom again then boot into the rom to enable OEM Unlock
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Install your rom again then boot into the rom to enable OEM Unlock
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thank you so much, it works!
I have unlocked the bootloader again.

kukudi said:
Thank you so much, it works!
I have unlocked the bootloader again.
Click to expand...
Click to collapse
You are welcome! Now leave your bootloader unlocked lol
Sent from my Nexus 5X using Tapatalk

Related

[Q] My arc won't boot into recovery

Okay, what am I doing wrong? or is my arc just weird?
For quite some time I want to have Cyanogenmod 7, a Custom ROM or just another kernel. Well I followed some tutorials, like;
- [Guide] All in one 'Namaste guide' to Bootloader unlocking, Rooting, Flashing & more
- [n00bs] Root and Install CyanogenMod7 after Unlock Your Bootloader Step by Step
- Sony Ericsson Xperia Arc: Full Update Guide
- [KERNEL][ARC/ARC S] DooMKernel [Rel:v18-FIX1][Dt:24/Jan][FW:.42/.58/.62]
But everytime I try one off these I get stuck at;
- Reboot phone into recovery
It just doesn't boot then..
So I flashed my firmware back to stock .42 with flashtool..
Is it possible that my Arc just can't update to a new ROM/kernel?
What exactly doesn't work?
Just press the back button while booting to get into recovery
Sent from my iPad 2 using Tapatalk
Flo95 said:
What exactly doesn't work?
Just press the back button while booting to get into recovery
Click to expand...
Click to collapse
You mean volume down button.
dp94 said:
You mean volume down button.
Click to expand...
Click to collapse
I tried, but when I press the power button(to boot), It vibrates ones and after that I press the volume down button, but nothing happens..
You know you have to press it a couple of times?
dp94 said:
You know you have to press it a couple of times?
Click to expand...
Click to collapse
Jep, did that, but nothing happens..
When I remove and replace the battery and press the power button again, I get the same thing..
And when you try to install a custom ROM, you do exactly the following?
dp94 said:
Connect your device with your current ROM to a PC.
Put the ROM (*.zip file) on your sdcard.
Shutdown device.
Connect your device with fastboot mode (pressing menu button) to a PC.
Go to your fastboot folder.
Press shift key, right click and select "Open command window here".
Install kernel by using the command "fastboot flash boot boot.img".
After installing disconnect your device from PC.
Enter CWM recovery by pressing volume down button several times while booting.
Do a full wipe/factory reset, wipe cache, wipe dalvik cache.
Select install zip from sdcard.
Navigate to the folder you've saved the ROM and select it.
After installing select reboot system now.
Click to expand...
Click to collapse
dp94 said:
And when you try to install a custom ROM, you do exactly the following?
Click to expand...
Click to collapse
Yes, but then I get stuck at "Enter CWM recovery by pressing volume down button several times while booting."
And when you flash the kernel, there's everything alright?
dp94 said:
You mean volume down button.
Click to expand...
Click to collapse
No, back button.
At least on DooMKernel
Sent from my iPad 2 using Tapatalk
Flo95 said:
No, back button.
At least on DooMKernel
Sent from my iPad 2 using Tapatalk
Click to expand...
Click to collapse
Okay, I'll try Doomkernel now, but then with the backbutton to go into recovery
UPDATE:
Still no booting..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flo95 said:
No, back button.
At least on DooMKernel
Click to expand...
Click to collapse
Okay, then both are working.
I was just unsure, because I've never used it with back button.
B-vb said:
Okay, I'll try Doomkernel now, but then with the backbutton to go into recovery
UPDATE:
Still no booting..
Click to expand...
Click to collapse
Flashed fine, do you press back and keep hitting the pack button again and again when all LEDs light up @ DooMKernel logo?
Sent from my iPad 2 using Tapatalk
Flo95 said:
Flashed fine, do you press back and keep hitting the pack button again and again when all LEDs light up @ DooMKernel logo?
Sent from my iPad 2 using Tapatalk
Click to expand...
Click to collapse
There's just nothing happening, it's vibrates ones after pressing the power button, and nothing more.. no logo, no leds..
I am thinking ...
Do we not have to Unlock our boot loader first, to be able to get into the Recovery Mode?
Because I am having the same problem ... I even get the blue light, but it just boots up normally ...!
Not anymore, with the help of this Application called Xparts, Available in Google Play,
We can Easily get into Recovery! Without Unlocking the Boot loader! Sweet!
Click to expand...
Click to collapse
!~ Peace ~!
Awarebeyond said:
Do we not have to Unlock our boot loader first, to be able to get into the Recovery Mode?
Because I am having the same problem ... I even get the blue light, but it just boots up normally ...!
Click to expand...
Click to collapse
Yes you need unlocked bootloader for DooMKernel.
I used testhead and S1tool to unlock mine.
You should check that your phone can be unlocked without bricking it.

Galaxy Nexus briked!!!

Hello
Last night i wanted to update my phone from AOKP M4 to B28 and with that ocasion i wanted to update the kernel too. I tried to flash B28 over the M4 with cache wipe and nothing after this i make a full wipe(factory,partition,dalvick and battery stats). And all was good...when i try to flash the Leankernel the phone entered in bootloop. After this i tried all the options(gnex toolkit,fastboot,odin)and nothing, my phone now only enter in fastboot mode or download mode the cwm disappear and instead of cwm is the green robot with a red triangle on it.
I post two screenshot maybe someone can help me with this problem because i think i will lose the warranty.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/URL][/IMG]
First are from the gnex tollkit ant the last is from fastboot.
Did you try to unroot / reroot via fastboot?
Tryed everything but nothing only errors...
Time to buy a new nexus mate.
Eligible XDA Developer GRAVITY 360
Tried adb? If yes congats you are the 1st who achieved to brick gnex. Except someone else have a crazy idea!
Should i comment your post??
flash the stock images http://code.google.com/android/nexus/images.html
everyone should know how to flash it manually with fastboot..you probably need to flash only kernel and system
the common user error is that when you get a bootloop, people went crazy and start doing eveything...the next time when you got a bootloop, you SIMPLY have to go in recovery and restore the backup.
EDIT: what the error with fasboot? the pic is too small to read
andQlimax said:
flash the stock images http://code.google.com/android/nexus/images.html
everyone should know how to flash it manually with fastboot..you probably need to flash only kernel and system
the common user error is that when you get a bootloop, people went crazy and start doing eveything...the next time when you got a bootloop, you SIMPLY have to go in recovery and restore the backup.
EDIT: what the error with fasboot? the pic is too small to read
Click to expand...
Click to collapse
He lost cwm as well so he could't go to recovery and restore. If he can't root/unroot via fastboot i doubt he can flash stock image. I hope he can.
arvylas said:
He lost cwm as well so he could't go to recovery and restore. If he can't root/unroot via fastboot i doubt he can flash stock image. I hope he can.
Click to expand...
Click to collapse
he lost cwm after tring everything, before that he probably can
I make the cwm work but i don't know how to flash the stock image... If i restore my backup i get a bootloop.
Go to fastboot on the phone. Plug it in. Extract the stock factory image somewhere. Open command prompt, navigate to wherever you have GNex toolkit's fastboot binary.
fastboot flash radio radio.img
fastboot flash boot boot.img
fastboot flash system.img
There you go. Start the phone.
So it's not really bricked after all..
Try to restore the google image with the gnex toolkit by putting the zip file in the correct folder (read instruction).
Steelskinz said:
So it's not really bricked after all..
Try to restore the google image with the gnex toolkit by putting the zip file in the correct folder (read instruction).
Click to expand...
Click to collapse
learn to use fastboot
Use this.
http://forum.xda-developers.com/showthread.php?t=1400871
Restore GNex
Enjoy phone
????
Profit
when my phone bootloopt when i wanted to root it using the toolkit i got the same thing android with red triangle in it...i simply rerooted with a boot image and my problem was solved....... isbit a little glitch that sometimes happens when flashing a prerooted rom or something....cuase this is not the first topic on here with this problem
Sent from my Galaxy Nexus using XDA
I tryed with Gnex ToolKIt read what i post the problem is that in fastboot and Gnex ToolKit i receive this error FAILED<status read failed<too many link>> maybe now you understand me. The only way to flash something is in fastboot in cwm i can cwm work to navigate to wipe but when i want to flash something it restarts.I have cwm 5.0.0.2 something like this.
Try installing via fastboot or cwm a stock or aokp again after wiping everything of course... if you have cwm there is no prob.
Sent from my Galaxy Nexus using Tapatalk 2 Beta-2
arvylas said:
Try installing via fastboot or cwm a stock or aokp again after wiping everything of course... if you have cwm there is no prob.
Sent from my Galaxy Nexus using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
Man when i try to flash something in cwm it starts and after reboot it self.
OK, start from the start, when you plug your phone in to the computer in bootloader and type "fastboot devices" does it show up?
If it does then you have no problems.
If not then you may have driver problems.
If it does show up just flash the images one by one and everything will be fine.
The google stock factory images that is.
Toolkits and 1 click methods are the exact reason we have these "OMG I bricked my nexus" threads...... Learn how to use adb and fastboot!!!!!!
Sent from my Galaxy Nexus using xda premium

need some help flashing help. not normal.[SOLVED]

Ive had my phone rooted and.been.flashing since.I got months ago. Imm running ics right now. My issue is I need to flash back to stock and.unroot. Prrrroblem is that my power button is broke. I cantt get into download mode to ODIN it and.cantt get into recovery to flash it. Any thoughts?
Do you have a cwm
Sent from my SPH-D710 using XDA
5FOOTER said:
Do you have a cwm
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
I do.
Download the app called Quickboot from the app store. Had recovery and download mode reboot options.
Sent from my SPH-D710 using XDA
Grab Quick Boot from the Play Store. You can boot straight to recovery or bootloader from that app without the power button. Then flash stock ROM and remove root
Wartouched said:
Download the app called Quickboot from the app store. Had recovery and download mode reboot options.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Thanks. I always think about things like this after the fact. I understand newbie frustration haha.
If you are around a PC, you can also use "extra options" in Auto Root. You'll be presented with options to reboot to recovery (Option N) or odin dl mode (Option O). Alternatively you can use "adb reboot recovery" or "adb reboot download"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
sfhub said:
If you are around a PC, you can also use "extra options" in Auto Root. You'll be presented with options to reboot to recovery (Option N) or odin dl mode (Option O). Alternatively you can use "adb reboot recovery" or "adb reboot download"
Click to expand...
Click to collapse
Does the cmd run if I flashed back in november and havnt done anything but flash since then?? I had to root a kindle fire so i understand the adb commands.
And can anyone point me to a way to unroot so sprint will honor a warranty?? I tried to search I didnt find anything clearly defined at unrooting.
coreyalfredson said:
And can anyone point me to a way to unroot so sprint will honor a warranty?? I tried to search I didnt find anything clearly defined at unrooting.
Click to expand...
Click to collapse
That's in sfhub's autoroot as well I believe
coreyalfredson said:
Does the cmd run if I flashed back in november and havnt done anything but flash since then?? I had to root a kindle fire so i understand the adb commands.
Click to expand...
Click to collapse
Auto Root uses ADB commands, so basically if you can connect your phone to your PC and you have USB debugging enabled, it will work.
If your power button doesn't work, I would use ODIN as a 2nd option. It is probably the quickest to get you back to stock without fuss, but in the remote chance something goes wrong, you'd need your power button to get back into ODIN DL mode.
You might want to have a USB jig available if you use ODIN since it can get you back into ODIN DL mode even if your power button doesn't work.
coreyalfredson said:
And can anyone point me to a way to unroot so sprint will honor a warranty?? I tried to search I didnt find anything clearly defined at unrooting.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1433101
Follow this forum and read down. This will help you get to stock, unrooted, EL29. EL29 is the current stock firmware. Also sprint isn't really to bad about rooted phones. If your problem is mechanical, it shouldn't matter if your rooted or not.

[Q]After using JB FW Easy tool, phone became useless

HTC__622
I used this tool:
http://forum.xda-developers.com/showthread.php?t=1924003
To try and upgrade my phone to JB. Followed the instructions to the tee. Unless I used wrong boot img's. Only thing that works now is fastboot. I've tried installing recovery many times. All I get is a black screen once I select recovery setting.
What can I do to install the bloody recovery successfully?!
In fastboot you need to do fastboot erase cache
then you should be able to boot into recovery.
You might be able to wipe the cache from your toolkit but i can't check as I'm not at a PC
Sent from my HTC One X using xda app-developers app
bagofcrap24 said:
In fastboot you need to do fastboot erase cache
then you should be able to boot into recovery.
You might be able to wipe the cache from your toolkit but i can't check as I'm not at a PC
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Done all that several times.
What I noticed was, when selecting recovery. The screen wouldn't just be black, it'd be lit up. I navigating to where mount USB mode was, lo and behold it actually worked. So my issue is more of, the recovery menu not showing up. It's there and works. Not the menu. Was working previously before I went JB Q_Q
Hmm. That's an odd one.
Just to discount a bad flash can you test just booting the recovery from fastboot rather than flashing it.
Are you capable of using fastboot from the command line.
If so re download your recovery.img and copy it to your fastboot directory and run the command fastboot boot recovery.img
It should boot to recovery again but this version has not been loaded from the recovery partition so it will tell us if you just have a bad flash or not
Sent from my HTC One X using xda app-developers app
Yes I can use fastboot commands. Using the command you provided, phone was stuck on the "htc quietly brilliant" screen.
Is the phone locked or unlocked ?
What is your Hboot version ?
Can you enter recovery mode ? did you "install" the recovery that comes with the tool ?
If you can post a picture to your bootlder , that would help
anameeeen said:
Is the phone locked or unlocked ?
What is your Hboot version ?
Can you enter recovery mode ? did you "install" the recovery that comes with the tool ?
If you can post a picture to your bootlder , that would help
Click to expand...
Click to collapse
Hboot 1.36.0000
Unlocked. I upgraded from 0.94 HBoot. I can install everything with that tool. Issue is, recovery menu isn't visible. I've done research and seen some cases where backlight isn't on, but that's not the case for me. Backlight is on, and screen itself if on. Nothing is visible but I can touch it and same actions occur as if I were to select it normally. As for pic, I'll try. Have no camera to use.
Still no luck. Nothing I've done makes the recovery menu visible. Did the same process on w8/w7. No difference.
nagameno said:
Still no luck. Nothing I've done makes the recovery menu visible. Did the same process on w8/w7. No difference.
Click to expand...
Click to collapse
I had that problem too. reflash all again with easy tool and will be fine
carlowise said:
I had that problem too. reflash all again with easy tool and will be fine
Click to expand...
Click to collapse
I think I've reflashed a good, 10+ times. Time to try again.
OH, one thing I learned, this may be useful for people who are stuck in bootloops:
If you want to force your phone to turn off and charge, go to fastboot mode, scroll down and select power down. Works like a charm! No script needed to barely charge phone.
EDIT: Nope, still nothing. Anyway I can wipe the recovery partition?
Double edit: Forgot to mention, when executing "fastboot boot [nameOfRecoveryImage].img phone always hangs on HTC quietly brilliant screen.
It should only hang if you are locked bootloader or you are running the first hboot that came on phone release 0.46
To erase the recovery do fastboot erase recovery then you can try flashing again
Sent from my HTC One X using xda app-developers app
Just a small question in between, you are sure you have the international ENDEAVORU phone and not the AT&T EVITA type phone ?
bagofcrap24 said:
It should only hang if you are locked bootloader or you are running the first hboot that came on phone release 0.46
To erase the recovery do fastboot erase recovery then you can try flashing again
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
When I got my phone, it's hboot ver was 0.94 I believe.
When trying to erase recovery, I get the following error:
"FAILED (remote: not allowed)"
Here's a screenie of my hboot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@Mr Hofs Yes I'm sure. My HOX is the HTC__622 ver, It's the int version, not the NA ver.
Updated hboot, endeavoru type phone all good.
Try to flash this recovery
http://db.tt/K8Aoto6o
Fastboot erase cache
Fastboot flash recovery name of recovery.img
Fastboot erase cache
Mr Hofs said:
Updated hboot, endeavoru type phone all good.
Try to flash this recovery
http://db.tt/K8Aoto6o
Fastboot erase cache
Fastboot flash recovery name of recovery.img
Fastboot erase cache
Click to expand...
Click to collapse
Result: Same as last time, menu is not visible. I can still screw around with options, such as reboot phone. Not being able to see what I'm doing is just stupid. How's this even possible ._.
I've read this thread 2 times....can't seem to get the link why its not showing up.......it flashes fine but just don't display......this is crazy
Mr Hofs said:
I've read this thread 2 times....can't seem to get the link why its not showing up.......it flashes fine but just don't display......this is crazy
Click to expand...
Click to collapse
View My Video
That recovery that I'm runnin is the CWM you sent. Also, if I'm not mistaken, the first option is reboot phone, which is what I selected and only way I can tell that I have a half ass functioning recovery.
Can I wipe my recovery partition somehow? Maybe that'll fix everything.
Erasing cache is already done by fastboot commands, i don't have a clue how to fix this !
Mr Hofs said:
Erasing cache is already done by fastboot commands, i don't have a clue how to fix this !
Click to expand...
Click to collapse
Thanks for trying, I appreciate it.
And thank bagofcrap too for being the one who started helping ..... its just not an easy problem to fix

HELP bootlooping sony logo!

hi, tried to install aosp lollipop, the installtion went fine. but not touchscreen as usual, this is not the problem my problem is i cant turn my phone on or go to fastboot or flash mode, if i plug it to charger it bootloops on sony logo. i have no idea what happend to it. anyone can help?
bigsmoke9250 said:
hi, tried to install aosp lollipop, the installtion went fine. but not touchscreen as usual, this is not the problem my problem is i cant turn my phone on or go to fastboot or flash mode, if i plug it to charger it bootloops on sony logo. i have no idea what happend to it. anyone can help?
Click to expand...
Click to collapse
i think that i have the weirdest things ever in here :\
it boots now, i can see the lockscreen, if i try to use the off button near simcard it functions as a vol down key! seriously what the hell is going on?
i cant turn it off until it runs out of battery
Can anyone help me, I flashed stock rom from remix rom by flashtool but I can not start, just boot into Sony logo then blue screen then restart again and again ? B4 that it functioned well on remix rom
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bigsmoke9250 said:
hi, tried to install aosp lollipop, the installtion went fine. but not touchscreen as usual, this is not the problem my problem is i cant turn my phone on or go to fastboot or flash mode, if i plug it to charger it bootloops on sony logo. i have no idea what happend to it. anyone can help?
Click to expand...
Click to collapse
Did you try PC Companion repair? Start there. Are you sure no fastboot or flash mode? I'm surprised that flashing a rom would break that. Is that all you did? Did you use fastboot to flash AOSP?
seaxxz said:
Can anyone help me, I flashed stock rom from remix rom by flashtool but I can not start, just boot into Sony logo then blue screen then restart again and again ? B4 that it functioned well on remix rom
Click to expand...
Click to collapse
If you can get fastboot mode, flash a CM bootand recovery img, boot into recovery, do a full wipe, and flash a rom zip. It sounds like you're having trouble with either a dirty flash or wrong boot img, or both.
levone1 said:
Did you try PC Companion repair? Start there. Are you sure no fastboot or flash mode? I'm surprised that flashing a rom would break that. Is that all you did? Did you use fastboot to flash AOSP?
Click to expand...
Click to collapse
Thank you. I've tried pc companion and it works
---------- Post added at 08:26 AM ---------- Previous post was at 07:58 AM ----------
levone1 said:
If you can get fastboot mode, flash a CM bootand recovery img, boot into recovery, do a full wipe, and flash a rom zip. It sounds like you're having trouble with either a dirty flash or wrong boot img, or both.
Click to expand...
Click to collapse
Thanks for your help. Problem was solved )
levone1 said:
Did you try PC Companion repair? Start there. Are you sure no fastboot or flash mode? I'm surprised that flashing a rom would break that. Is that all you did? Did you use fastboot to flash AOSP?
Click to expand...
Click to collapse
yes i flashed it using fastboot, and again yes i had no fastboot and flash mode but thank god flash mode worked this morning and i am back to stock again. i dont know why that happend or the broken touchscreen on other custom roms? maybe bad luck or doing something wrong

Categories

Resources