Database Users

Can't boot nexus one or use recovery

Hello,
I come here and make a new thread after I spent the day inside various forums to solve my problem but wasn't able to.
Here is the thing I tried to install the cyanogenmod earlier today. I unlocked my N1 properly and think I rooted it properly as well. But I was unable to install the custom rom. Actually my N1 won't even boot, it's stuck on the cross image with the unlocked lock and I can't boot the recovery either. I tried to install a custom recovery, the amon ra thing, but it still freezes on the cross screen.
I assume my N1 isn't completely bricked since I can still power it up, start the fastboot mode and my computer recognize de USB connection (however ADB won't find the phone even after I re-installed the drivers).
So here I come for help to either bring back my N1 to its former stock rom or any functionning rom.
Thanks.

Try the unroot/restore guide with PASSIMG of FRG33. Look at my signature.

oh thank you !!! It worked perfectly !
EDIT : Well spoke too soon I rebooted the N1 after its apparent recover and it froze again, so I started the operation once more and while updating the files ravio_v2 was checked "fail-pu" instead of "ok"
EDIT 2 : Well I rebooted after the update and the N1 never powered up again ... I guess now it is really bricked... though I can't figure why

olicyr said:
EDIT 2 : Well I rebooted after the update and the N1 never powered up again ... I guess now it is really bricked... though I can't figure why
Click to expand...
Click to collapse
You can't even get into fastboot any more?
Also, you say you followed the right steps to unlock the device and the right steps to root the device... What steps did you take exactly?

Hi,
to unlock the phone I used the oem command in the fastboot mode. Then I tried to install the amon ra custom recovery and I think that is what brought all this trouble.

Can you still see your device through fastboot? If so you should be able to flash a recovery image and a ROM of your choosing.

It should boot up fastboot like Dirk said. You can not brick the phone by flashing a recovery.
Sent from my Nexus One using XDA App

I guess there is some HW fault - might be a recent bad sector in one of the system critical areas. It's not something you can cause with SW - unless you're flashing hboot or radio, which should have been covered in the first restore attempt, which worked.
Anyway, if it doesn't power up at all - and doesn't react to charging - try pulling out the battery for several hours, and then put it back and try again. If it doesn't work - then you're up for a warranty repair...

DirkGently1 said:
Can you still see your device through fastboot? If so you should be able to flash a recovery image and a ROM of your choosing.
Click to expand...
Click to collapse
No the phone doesn't boot anything. I'll try to remove the battery and wait a few hours like said above, if it doesn't work I'm still under warranty I think

L31 bricked by flashing rollback package

Hi All.
I hope someone can help me. I encountered this stupid problem:
I have a L31 device and successfully installed the Nougat (test?)update through Firmware Finder. But since this wasn't the definitive update, I decided to rollback to MM. I installed the C900B300 rollback package and then the B160 package. That went well, BUT the device now refused to activate the Google services. I couldn't enter a Google account. Not from Settings > Accounts and not from any other Google app like Chrome, Play Store, Gmail or others. The screen just kept returning to the Homescreen.
Upon checking About this device, I noticed the version now was C900B160, instead of the expected C432B160. I am very positive I used the C432B160 MM package to flash. This I did with the three button method. But then how come it still showed C900B160?
So I first tried to reflash the C432B160 with the three button method. Flashing worked well, but the problem wasn't solved. Still no Google activation and still the same C900B160 number.
So then I decided to reflash the rollback package...
That turned out to be a mistake... After flashing that (and it did show 100% successfull after flashing) the device is bricked. The Huawei logo shows and then nothing happens. The logo stays in the screen. I can't even turn the device off. Short pressing the ON-OFF button does nothing and long pressing just restarts the logo and nothing more.
I tried to reflash the MM update C432B160 with the three button technique, but that doesn't work anymore!! Entering erecovery with the volume up and ON-OFF also doesn't work anymore!! The only thing that works is Fastboot when connected to a pc. That screen shows phone (and bootloader) is locked, by the way. So I can't flash boot.img and recovery.img .
Has anybody encountered such problems and knows what to do now?? Thanks guys!

Liebaart said:
Hi All.
I hope someone can help me. I encountered this stupid problem:
I have a L31 device and successfully installed the Nougat (test?)update through Firmware Finder. But since this wasn't the definitive update, I decided to rollback to MM. I installed the C900B300 rollback package and then the B160 package. That went well, BUT the device now refused to activate the Google services. I couldn't enter a Google account. Not from Settings > Accounts and not from any other Google app like Chrome, Play Store, Gmail or others. The screen just kept returning to the Homescreen.
Upon checking About this device, I noticed the version now was C900B160, instead of the expected C432B160. I am very positive I used the C432B160 MM package to flash. This I did with the three button method. But then how come it still showed C900B160?
So I first tried to reflash the C432B160 with the three button method. Flashing worked well, but the problem wasn't solved. Still no Google activation and still the same C900B160 number.
So then I decided to reflash the rollback package...
That turned out to be a mistake... After flashing that (and it did show 100% successfull after flashing) the device is bricked. The Huawei logo shows and then nothing happens. The logo stays in the screen. I can't even turn the device off. Short pressing the ON-OFF button does nothing and long pressing just restarts the logo and nothing more.
I tried to reflash the MM update C432B160 with the three button technique, but that doesn't work anymore!! Entering erecovery with the volume up and ON-OFF also doesn't work anymore!! The only thing that works is Fastboot when connected to a pc. That screen shows phone (and bootloader) is locked, by the way. So I can't flash boot.img and recovery.img .
Has anybody encountered such problems and knows what to do now?? Thanks guys!
Click to expand...
Click to collapse
With fastboot method, unlock bootloader again. Flash recovery. Boot into recovery. Wipe system and boot. Flash stock boot IMG and recovery IMG. Power off. Use dload. Now you are in bootloop. When booting press vol up 3 seconds, on e-recovery press shutdown. Press and hold power and vol up. Go to stock recovery, do factory reset.
Sent from my NEM-L21 using Tapatalk

Thanks for your help.
Trouble is that I can't unlock te bootloader, because I do not know my Product ID and I can't look it up, since I don't have a dialer... The HuaweiProductIDGenerator doesn't help. I tried several codes with it, but none worked.

Liebaart said:
Thanks for your help.
Trouble is that I can't unlock te bootloader, because I do not know my Product ID and I can't look it up, since I don't have a dialer... The HuaweiProductIDGenerator doesn't help. I tried several codes with it, but none worked.
Click to expand...
Click to collapse
Power off, vol up+ power can you go to recovery?
Sent from my NEM-L21 using Tapatalk

Liebaart said:
Thanks for your help.
Trouble is that I can't unlock te bootloader, because I do not know my Product ID and I can't look it up, since I don't have a dialer... The HuaweiProductIDGenerator doesn't help. I tried several codes with it, but none worked.
Click to expand...
Click to collapse
Post here IMEI+SN and i try to get you bootloader unlock code.

Thanks! I sent you a PM.

Anonda said:
Power off, vol up+ power can you go to recovery?
Click to expand...
Click to collapse
No, I can only get into fastboot when connected to a pc.

OK. gtdaniel was so kind to provide me with an unlock code. THANKS!
But, I don't seem te be able to use it...
I can put the phone in bootloader when connected to a pc. When I type "fastboot devices" I do get the correct serial number. But when I type "fastboot oem unlock 343...338" I get a FAILED (remote: command not allowed).
It seems this is because I never could allow OEM unlocking from the Android settings menu. But since my phone is bricked, I can not enter into that menu!
Does anybody know how to solve this??

Liebaart said:
OK. gtdaniel was so kind to provide me with an unlock code. THANKS!
But, I don't seem te be able to use it...
I can put the phone in bootloader when connected to a pc. When I type "fastboot devices" I do get the correct serial number. But when I type "fastboot oem unlock 343...338" I get a FAILED (remote: command not allowed).
It seems this is because I never could allow OEM unlocking from the Android settings menu. But since my phone is bricked, I can not enter into that menu!
Does anybody know how to solve this??
Click to expand...
Click to collapse
u can try with
VNS-L21-L22-L31 Toolkit or
SRKToolHuawei-Lod-Chong-V2.0-20161002
But i dont know is that good idea to listen to me anymore

Thanks, but the Toolkit says it can't find the device.

Liebaart said:
Thanks, but the Toolkit says it can't find the device.
Click to expand...
Click to collapse
at command line when u write adb devices u got your phone ?
Maybe is dump question but did you install adb android driver ?
I'm pretty sure that someone wrote in thread that you don't need to have this oem permission in android if you are in fastboot

dragon218 said:
at command line when u write adb devices u got your phone ?
Maybe is dump question but did you install adb android driver ?
I'm pretty sure that someone wrote in thread that you don't need to have this oem permission in android if you are in fastboot
Click to expand...
Click to collapse
OEM permission need for fastboot/unlock bootloader.
Sent from my NEM-L21 using Tapatalk

Anonda said:
OEM permission need for fastboot/unlock bootloader.
Click to expand...
Click to collapse
Yes, that's what I read too. Since I can't change that permission anymore while I can't start Android, I can't unlock. Dammit.
Is DC Unlocker my only option then? It seems their software can do it.

I'm afraid I've got some pretty bad news. Last week the same thing happened to me after I was THAT stupid to actually try and flash the rollback package for the second time. My phone got bricked just like yours, and NOTHING worked to fix it. I tried completely everything I could find on the net and XDA, and in the very end I was forced to bring it in for warranty repairs. Even they COULD NOT fix it and the phone ended up with the entire logicboard changed with a completely new one. I was lucky that it all was done under warranty. Will never do anything as stupid as that!
Really hope you find a fix somehow, but if not, the repair service is your only solution, because otherwise the phone is as good as dead.

markositoo said:
I'm afraid I've got some pretty bad news. Last week the same thing happened to me after I was THAT stupid to actually try and flash the rollback package for the second time. My phone got bricked just like yours, and NOTHING worked to fix it. I tried completely everything I could find on the net and XDA, and in the very end I was forced to bring it in for warranty repairs. Even they COULD NOT fix it and the phone ended up with the entire logicboard changed with a completely new one. I was lucky that it all was done under warranty. Will never do anything as stupid as that!
Really hope you find a fix somehow, but if not, the repair service is your only solution, because otherwise the phone is as good as dead.
Click to expand...
Click to collapse
my phone is also reedy to send to service. I have a lot of phone with android but no rom make so many damage to my phone, like this fc** rollback. finger cross, because huawei service in my country without warranty,takes for new motherboard 175 $ . I bought phone for 233 $ with 3 gb ram..... This will be harsh and pay(in)ful lesson for me.

dragon218 said:
my phone is also reedy to send to service. I have a lot of phone with android but no rom make so many damage to my phone, like this fc** rollback. finger cross, because huawei service in my country without warranty,takes for new motherboard 175 $ . I bought phone for 233 $ with 3 gb ram..... This will be harsh and pay(in)ful lesson for me.
Click to expand...
Click to collapse
Uhh, I am sorry to hear that. But yes, I had the same harsh lesson. They will be forced to changed the motherboard too, cause even they won't be able to re-flash the whole system. Though, what I did to have the warranty not declined, is I brought the phone to the service and said that - "The phone received and OTA update through the updater, I didn't look much into it and just went with it, pressed on update and everything seemed well. It worked until the moment where it installed and restarted, and now the phone is stuck on Huawei logo and you can't possibly do anything with it, not even turn it off." - and that's it. They will have to repair it under warranty because there is no proof left that you had rooted it or done any other installations not authorized by Huawei.
Best of luck!

Liebaart said:
Yes, that's what I read too. Since I can't change that permission anymore while I can't start Android, I can't unlock. Dammit.
Is DC Unlocker my only option then? It seems their software can do it.
Click to expand...
Click to collapse
I know that i read somewhere how to manage to this oem lock. I was 50 % right.
https://forum.dc-unlocker.com/forum...61751-huawei-mate-9-mha-l29-erase-frp-problem
Some user got the same problem that you have and flash boot.
But truly if u don't have "your device has been unlock" only bootloop on huawei logo, is more simple to send it back to warranty and play dump.
I have now "your device is unlock" and i pray for miracle.

Liebaart said:
Hi All.
I hope someone can help me. I encountered this stupid problem:
I have a L31 device and successfully installed the Nougat (test?)update through Firmware Finder. But since this wasn't the definitive update, I decided to rollback to MM. I installed the C900B300 rollback package and then the B160 package. That went well, BUT the device now refused to activate the Google services. I couldn't enter a Google account. Not from Settings > Accounts and not from any other Google app like Chrome, Play Store, Gmail or others. The screen just kept returning to the Homescreen.
Upon checking About this device, I noticed the version now was C900B160, instead of the expected C432B160. I am very positive I used the C432B160 MM package to flash. This I did with the three button method. But then how come it still showed C900B160?
So I first tried to reflash the C432B160 with the three button method. Flashing worked well, but the problem wasn't solved. Still no Google activation and still the same C900B160 number.
So then I decided to reflash the rollback package...
That turned out to be a mistake... After flashing that (and it did show 100% successfull after flashing) the device is bricked. The Huawei logo shows and then nothing happens. The logo stays in the screen. I can't even turn the device off. Short pressing the ON-OFF button does nothing and long pressing just restarts the logo and nothing more.
I tried to reflash the MM update C432B160 with the three button technique, but that doesn't work anymore!! Entering erecovery with the volume up and ON-OFF also doesn't work anymore!! The only thing that works is Fastboot when connected to a pc. That screen shows phone (and bootloader) is locked, by the way. So I can't flash boot.img and recovery.img .
Has anybody encountered such problems and knows what to do now?? Thanks guys!
Click to expand...
Click to collapse
I am exactly in the same situation with the difference that I don't have Fasboot! How do you get to Fastboot? Mine hangs on the screen that says the phone is unlocked and the device is booting... Vol+/Vol- and Power doesn't boot into Fastboot and my minimal ADB doesn't recognize the phone in the stages that it hangs...
---------- Post added 16th April 2017 at 12:04 AM ---------- Previous post was 15th April 2017 at 11:52 PM ----------
I have the same situation. I tried everything, Three button method, letting the battery run out completely, Vol+ and Power, Vol- and Power, connected to PC, not connected to PC. Every time I disconnect the charger, and reconnect it starts from 0. I read some other people here have the same problem. Send it to warranty and explain your rollback process unlocked the bootloader somehow (I mean the phone does do a lot of sh*ty sh*t, so this shouldn't seem very odd as well!!!) and hope that you get a repair/replacement and after that sell it on ebay hoping some stupid people like us in the first place will buy it and spend your money on a phone more reliable!

I managed to access the fastboot using the 3 button method in cold boot. Hold the Power key until the screen goes off and then release and hold down the Vol- key and immideately connect the usb cable to PC right before it vibrates or exactly when it vibrates (it's a matter of timing), and bingo you are in fastboot and you can flash system.img, recovery.img, cust.img, cache.img and boot.img from there, but this is not how I revived my phone. I used the 3 button method again when the phone was charged for like half an hour or so and the did the same cold boot trick and I could boot into the force upgrade environment (strangely this still didn't work whitout connecting the usb cable to PC), but it somehow didn't want to read the UPDATE.APP that I had in dload folder on my SD card and wanted to have it from my PC (I just felt it nad there was no indication of it ) so then I installed the DC Phoenix tool and payed 15 euros to be able to inject the complete UPDATE.APP to my bricked phone and the installation went well to 99% and failed, but I rebooted the phone and I could boot normally. Just to make sure I did a factory reset afterwards. Hope this helps.

Cannot get into Bootloader
Hey there!
Essentially as stupid as I am i flashed the Rollback Image at Android 6.0 too, because i wanted to get rid of C900. So now my phone is stuck in the Startup screen too. As mentioned here, I wanted to unlock bootloader again; The Button combination does not work, and if I want to start in bootloader via ADB, it just says "waiting for device"
i am really desperate and i don't know what i should do now
Thanks for the help
EDIT: Somehow managed to got it into Bootloader. At the moment i am unlocking it. Where do i get TWRP and the needed things? Please help, i'm just some noob who doesn't know how it's done
EDIT2: Solved, got Stock Recovery Re-installed, Flashed with the Force Update Method the Main Package of the Rollback (so not the temp rollback data), and worked. But Still C900 and no Google sign-in possible. Someone know how to solve?

I need the assistance of XDA wizards on recovering a poor students p9 lite

I'm in dire need of immediate assistance. I had previosly rooted my phone with this guide https://forum.xda-developers.com/huawei-p9lite/how-to/guide-unlock-bootloader-twrp-root-t3405701 and unlocked the bootloader. Long story short I made the decision to unroot and lock the booloader. Now im faced with a bootloop and this error message: https://imgur.com/a/ksz1kYY
I can't afford to lose this phone. If someone can help me recover this phone I can even throw in an extra 20$. The phone isn't recognised by pc and thus I cant run adb commands.

Sadly due to huawei becoming the new apple, you can't do anything to restore it, unless you pay for a new motherboard.
If you are lucky enough, drain the battery until the phone no longer boots then charge it. You will have a very small chance for the device to boot and from there unlock the bootloader. If it can't boot up, then try it many times until it no longer boots in error mode.
The error means that the recovery mode cannot check if the device is valid or not, thus locking the device from unwanted access. I hope you get it fixed

MapBreak said:
I'm in dire need of immediate assistance. I had previosly rooted my phone with this guide https://forum.xda-developers.com/huawei-p9lite/how-to/guide-unlock-bootloader-twrp-root-t3405701 and unlocked the bootloader. Long story short I made the decision to unroot and lock the booloader. Now im faced with a bootloop and this error message: https://imgur.com/a/ksz1kYY
I can't afford to lose this phone. If someone can help me recover this phone I can even throw in an extra 20$. The phone isn't recognised by pc and thus I cant run adb commands.
Click to expand...
Click to collapse
Hello, already tried to boot directly in fastboot mode ?
If not, turn off the device then connect it to cpu.
Press and hold vol - and power button until it boot.
Once booted ( hope so ) open adb/fastboot command and see if works now... :fingers-crossed:

Dadditz said:
Hello, already tried to boot directly in fastboot mode ?
If not, turn off the device then connect it to cpu.
Press and hold vol - and power button until it boot.
Once booted ( hope so ) open adb/fastboot command and see if works now... :fingers-crossed:
Click to expand...
Click to collapse
Would try this but the device doesn't exactly turn off. Holding down the power button just shuts it down for a second and then it boots automatically back. And can you explain what you mean by connecting it to cpu?

MapBreak said:
Would try this but the device doesn't exactly turn off. Holding down the power button just shuts it down for a second and then it boots automatically back. And can you explain what you mean by connecting it to cpu?
Click to expand...
Click to collapse
Ooops...
Yes, i was meaning connect it to your computer.. .
Connect it and try doing the way i told you.
If doesn't work let it completely discharges, then reconnect it to the computer and try again.
Wish you the best

Have you tried my method?

The Restless Soul said:
Have you tried my method?
Click to expand...
Click to collapse
I took my phone to a repair shop and I just got it back from there. They said that the phone just turned on like regular, and it appeared to be working so they didn't charge me for a repair. I rebooted to check if they actually had done anything but the error came up once more. I guess the battery had run out and it turned on when they charged it? If I run out the battery again and charge it will it turn on again? If so, what should I do once I'm able to boot? I still can't access the recovery from there to try anything.
EDIT: I'm waiting for the phone to run out of battery again

MapBreak said:
I took my phone to a repair shop and I just got it back from there. They said that the phone just turned on like regular, and it appeared to be working so they didn't charge me for a repair. I rebooted to check if they actually had done anything but the error came up once more. I guess the battery had run out and it turned on when they charged it? If I run out the battery again and charge it will it turn on again? If so, what should I do once I'm able to boot? I still can't access the recovery from there to try anything.
EDIT: I'm waiting for the phone to run out of battery again
Click to expand...
Click to collapse
Let it run out of battery and try to boot it into the rom. From there try to use firmware finder to reinstall your rom.

The Restless Soul said:
Let it run out of battery and try to boot it into the rom. From there try to use firmware finder to reinstall your rom.
Click to expand...
Click to collapse
I've tried several times now to let it run out of battery and try to boot it into fastboot, but every time I'm unsuccessful and it boots up regularly. I've tried holding power + vol- and power + vol- + vol+ and every combination of those. Not sure how to proceed since running adb command -adb reboot bootloader but that just ends up getting me to the same error screen. I don't know what I can do. Is it possible to flash the stock recovery and rom without fastboot?

MapBreak said:
I've tried several times now to let it run out of battery and try to boot it into fastboot, but every time I'm unsuccessful and it boots up regularly. I've tried holding power + vol- and power + vol- + vol+ and every combination of those. Not sure how to proceed since running adb command -adb reboot bootloader but that just ends up getting me to the same error screen. I don't know what I can do. Is it possible to flash the stock recovery and rom without fastboot?
Click to expand...
Click to collapse
Do not use adb or anything else.
Use firmware finder from Google play. Huawei has it's own eRecovery which is used for updates (OTA), so you shouldn't worry.
If you want to flash stock recovery, simply extract the update file and get the recovery.img, then flash it. It's a long method and hard to explain. Google it. Success

The Restless Soul said:
Do not use adb or anything else.
Use firmware finder from Google play. Huawei has it's own eRecovery which is used for updates (OTA), so you shouldn't worry.
If you want to flash stock recovery, simply extract the update file and get the recovery.img, then flash it. It's a long method and hard to explain. Google it. Success
Click to expand...
Click to collapse
Yeah but the thing is I can't flash anything without getting into fastboot.

MapBreak said:
Yeah but the thing is I can't flash anything without getting into fastboot.
Click to expand...
Click to collapse
Then use Firmware finder method.

The Restless Soul said:
Then use Firmware finder method.
Click to expand...
Click to collapse
How do I use firmware finder? I can download a update.app and something but those need to be flashed via fastboot right?
EDIT: Just tried to use firmware finder and update via proxy. I'm not able to get an update to show up despite multiple tries. Feels like I'm running out of options here.

MapBreak said:
How do I use firmware finder? I can download a update.app and something but those need to be flashed via fastboot right?
EDIT: Just tried to use firmware finder and update via proxy. I'm not able to get an update to show up despite multiple tries. Feels like I'm running out of options here.
Click to expand...
Click to collapse
Download the update file using firmware finder, put the update into your sd card (update.app), dial *#*#2846579*#*#, press update then wait.

The Restless Soul said:
Download the update file using firmware finder, put the update into your sd card (update.app), dial *#*#2846579*#*#, press update then wait.
Click to expand...
Click to collapse
You mean *#*#2846579#*#* ? It brings up a selection but the one ending in *#*# dorsn't. Software upgrade option said that it didn't find an update file. The factory reset option tries to reboot and then the error shows up again.

I got software upgrade to recognize the file but when I tried to update it just reboots back into error mode.

It's hard for me to explain how to fix it. Idk why it doesn't work to you. Have you tried going to a service and ask them to fix it for you?

The Restless Soul said:
It's hard for me to explain how to fix it. Idk why it doesn't work to you. Have you tried going to a service and ask them to fix it for you?
Click to expand...
Click to collapse
Yeah I guess getting the mainboard replaced is the only thing I can do now. Should I go to a Huawei service center or a regular phone repair shop? Thanks for all your help.

MapBreak said:
Yeah I guess getting the mainboard replaced is the only thing I can do now. Should I go to a Huawei service center or a regular phone repair shop? Thanks for all your help.
Click to expand...
Click to collapse
If you have the warranty tell them you got a bad update and it will fix them for free (there were cases where you would get bad updates via OTA, so you are covered)
If not, then a third party store but you will have to pay cash

VNS-L31 Soft Bricked?

Hello
So the problem - unlocked bootloader, flashed TWRP recovery and here is the catch - flashed the wrong one, for my other phone, Motorola G2.
When i wrote command to the abd to reboot into bootloader my phone become "bricked" - it just goes to show the "your device is booting now... " screen and does not load further.
Is there a way to either
1. flash the correct TWRP recovery? But how to do that if cant get computer to detect a phone....
2. Cancel the last order I have to phone -to reboot into bootloader. I know the first time i wrote it wrong (adb reboot boAtloader) and nothing happend, phone just restarted even when it had flashed wrong TWRP. So Im guessing if I somehow canceled my last order, phone would restart and I would be able to flash the correct TWRP.
As is stands now the phone is displaying the "your device is booting now... " message. If i press any of the known key combinations phone just restarts and go the the same position.
So, how to do anything if I cant get anywhere?
Tnx

windpowah said:
Hello
So the problem - unlocked bootloader, flashed TWRP recovery and here is the catch - flashed the wrong one, for my other phone, Motorola G2.
When i wrote command to the abd to reboot into bootloader my phone become "bricked" - it just goes to show the "your device is booting now... " screen and does not load further.
Is there a way to either
1. flash the correct TWRP recovery? But how to do that if cant get computer to detect a phone....
2. Cancel the last order I have to phone -to reboot into bootloader. I know the first time i wrote it wrong (adb reboot boAtloader) and nothing happend, phone just restarted even when it had flashed wrong TWRP. So Im guessing if I somehow canceled my last order, phone would restart and I would be able to flash the correct TWRP.
As is stands now the phone is displaying the "your device is booting now... " message. If i press any of the known key combinations phone just restarts and go the the same position.
So, how to do anything if I cant get anywhere?
Tnx
Click to expand...
Click to collapse
Hello dude,
you may have missed the opportunity to do
a rollback / reflash, depending on the version of the current system.
This will re-lock the bootloader ...
(no problem to re-unlock if you still have the unlock code )
Informations can be found in main thread
Guides, News and Discussions
> UNIFIED HELP THREAD, post number # 6.
It's just a tip to use as a last resort
before taking it to a service center or...
using it like paperweight ... lol
Cheers

Dadditz said:
Hello dude,
you may have missed the opportunity to do
a rollback / reflash, depending on the version of the current system.
This will re-lock the bootloader ...
(no problem to re-unlock if you still have the unlock code )
Informations can be found in main thread
Guides, News and Discussions
> UNIFIED HELP THREAD, post number # 6.
It's just a tip to use as a last resort
before taking it to a service center or...
using it like paperweight ... lol
Cheers
Click to expand...
Click to collapse
Thank you, worked like a charm .
Now my paper weight is back to being operational. Now I hope I will flash the correct recovery onto it

windpowah said:
Thank you, worked like a charm .
Now my paper weight is back to being operational. Now I hope I will flash the correct recovery onto it
Click to expand...
Click to collapse
Glad your device works again ! :highfive:

Phone in bootloop, cant access recovery

Hi guys,
this is my first x compact. I unlocked the bootloader per sony's instructions on their site + what I read here.
I flashed twrp, booted to recovery, and wiped and installed the lineage 16.0 which is stickied.
Everything worked great but various rootcheckers said still not rooted. This bothered me.
I followed the thread (https://forum.xda-developers.com/x-compact/how-to/stock-8-0-root-recovery-t3747479).
I used flashtool to flash stock oreo. After that, bootloops. And can't access recovery.
I can still enter flash mode and fastboot mode, but using the CMD in platform-tools, phone not recognized.
There must be something I can do? Thank you.

pleasuremann said:
Hi guys,
this is my first x compact. I unlocked the bootloader per sony's instructions on their site + what I read here.
I flashed twrp, booted to recovery, and wiped and installed the lineage 16.0 which is stickied.
Everything worked great but various rootcheckers said still not rooted. This bothered me.
I followed the thread (https://forum.xda-developers.com/x-compact/how-to/stock-8-0-root-recovery-t3747479).
I used flashtool to flash stock oreo. After that, bootloops. And can't access recovery.
I can still enter flash mode and fastboot mode, but using the CMD in platform-tools, phone not recognized.
There must be something I can do? Thank you.
Click to expand...
Click to collapse
Use Flashtool again, and this time, before clicking , in the box that says "wipe", check 'userdata'.
Back up anything you want to save in internal storage.

levone1 said:
Use Flashtool again, and this time, before clicking , in the box that says "wipe", check 'userdata'.
Back up anything you want to save in internal storage.
Click to expand...
Click to collapse
Thank you so much. I've seen your name a lot around here, I appreciate you taking the time to help. I'm booting now and starting the root process

pleasuremann said:
Thank you so much. I've seen your name a lot around here, I appreciate you taking the time to help. I'm booting now and starting the root process
Click to expand...
Click to collapse
No problem - I'm messing around with a Samsung at the moment, but I still check in here from time to time. I think XC is my favorite phone so far... XZ2C was really nice too, but (unofficially) official Sailfish OS puts XC on top for me...

levone1 said:
No problem - I'm messing around with a Samsung at the moment, but I still check in here from time to time. I think XC is my favorite phone so far... XZ2C was really nice too, but (unofficially) official Sailfish OS puts XC on top for me...
Click to expand...
Click to collapse
Hi friend, please maybe you can help me. I have almost the same issue. But after using LineageOS for some days, my phone stuck in boot logo. I managed to use Flash Tool to flash latest original stock ROM (Customized IBE). Strangely the flash process ended OK, but the phone still stuck in boot logo. I'm only able to force shut down with Volumen Up+Power Off (3 vibrates). Not possible to enter Recovery Mode.
I'm 98% sure that I have flashed with check in wipe USERDATE and also in CUST-RESET. But I wanted to try again, and now Im not able to enter flashmode. Phone gets green light, when volume down, but Flashstool is not recognizing the phone.
Thanks in advance

jayeffpee said:
Hi friend, please maybe you can help me. I have almost the same issue. But after using LineageOS for some days, my phone stuck in boot logo. I managed to use Flash Tool to flash latest original stock ROM (Customized IBE). Strangely the flash process ended OK, but the phone still stuck in boot logo. I'm only able to force shut down with Volumen Up+Power Off (3 vibrates). Not possible to enter Recovery Mode.
I'm 98% sure that I have flashed with check in wipe USERDATE and also in CUST-RESET. But I wanted to try again, and now Im not able to enter flashmode. Phone gets green light, when volume down, but Flashstool is not recognizing the phone.
Thanks in advance
Click to expand...
Click to collapse
Does fastboot work? Also, what do you ultimately want to do, return to stock?

levone1 said:
Does fastboot work? Also, what do you ultimately want to do, return to stock?
Click to expand...
Click to collapse
yes, after hard work to install drivers, I managed to get the phone to be recognized by Flashtool in fastboot mode. But the phone is not charging when turned off, and its not rebooting. I wanted to try again with stock ROM, since I got some battery issues with LineageOS (phone turned off while playing some games, and worked fine while doing the same with usb cable charging to laptop or AC charger.)
But I cannot do anything right now. Only fastboot mode and force restart works, but it stuck in Sony logo (after normal bootloader unlock 5 seconds warning). What can I do?