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?

Cant leave fastboot after unlocking bootloader....

So just got the axon 7 mini yesterday and was so excited I decided to try to root it with my laptop while my girl was driving us home from Las Vegas..... Ell I got as far as unlocking the boot loader.... now i get this odd screen after i try to exit fastboot. (pic-1) and no matter what option I pick the only thing that will come up is this screen. The only time its different is if I try to chose start from this screen then I get (pic-2) The best thing about this is that I can still go back to fastboot anytime. And it shows up in fastboot devices. Do I need to reflash stock thru fastboot? If so How and Where can i find it. Can I just flash nougat? I'm new to ADB/Fastboot.... Thank you for your time and consideration ahead of time for any help.

Hi, jcole6197, I think you can do as the screen told, there are steps in the screen.

Perhaps you can use tuliptool to relock the boot loader and flash the corresponding no verity boot file found in the development section. It almost seems like the boot binary was corrupted or lost during the process.

William Guo said:
Hi, jcole6197, I think you can do as the screen told, there are steps in the screen.
Click to expand...
Click to collapse
I tried the thing were saying over and over

MrWhite0429 said:
Perhaps you can use tuliptool to relock the boot loader and flash the corresponding no verity boot file found in the development section. It almost seems like the boot binary was corrupted or lost during the process.
Click to expand...
Click to collapse
so I was stuck all day yesterday trying anything and everything. BY THE WAY...Im very knowledgable but im pretty much a newb in rooting dept. especially fastboot. Well it seems I erased everything including the bootloader then battery died and no I have NOTHING on screen, no vibrations. Pretty much looks bricked. But when I try to put it in my computer to charge it it still shows up in my devices. BUT its not being found in adb/fastboot. I've tried every key combo/and length of holding them which doesnt do nothing

Can you place the device in edl? It will not display any lights or images when it is in edl.

How do I unroot & go back to stock rom /recovery?

I am on USA Mediapad 3 BTW-W09. I'm rooted, bootloader unlocked. I'd like to go to stock rom without root, bootloader locked. I want to sell this tablet like stock.
Thanks!

That's rather simple reflash the stock Rom that came with your phone... (Hint SRKTools) would be handy here..

I was able to relock the bootloader with that tool - thanks!
BUT now I have another problem. It reset and Huawei eRecovery popped up and said there was partition damage and asked to repair it. I said yes. Then it reboot but came to eRecovery screen again and asked to Download latest version and recovery. I did and it failed. Then the cycle starts over again. Won't boot.
What do you suggest now?

elcidroyale said:
I was able to relock the bootloader with that tool - thanks!
BUT now I have another problem. It reset and Huawei eRecovery popped up and said there was partition damage and asked to repair it. I said yes. Then it reboot but came to eRecovery screen again and asked to Download latest version and recovery. I did and it failed. Then the cycle starts over again. Won't boot.
What do you suggest now?
Click to expand...
Click to collapse
Quick question did you remove the "root", trwp before re-locking your BL.. this is why I suggested flashing your stock rom.. now go check out the bottom of this thread as it may be able you help you out..https://forum.xda-developers.com/mediapad-m3/help/bricked-mediapad-m3-t3746893

Ah yes I just saw this before you responded. I got the tool downloaded, got it to extract an update.zip that I found BUT there are two files missing. The CUST.img & USERDATA.img. Any ideas?

I see I need update_data_full_hw.zip. Do you know where to find for USA? I found one for EU - does it matter?

I ****ed it now! I found the appropriate zips and uploaded through Huawei Media Tools. Then I have no bluetooth, keyboard or stock apps. Then I "downgraded" to MM I thought. Got some error message in Huawei Media Tools saying I flashed wrong rom. Now it is stuck on boot screen. Now what??

You need to stop while your ahead.. first off probably should have tried to stop you when you failed to mention what model you have as you haven't stated as much. and you just seem to be flash happy. All I will suggest now is either you can can try to recover it through Huawei HiSuite or take it to your local shop an let them re-flash it..

damn you said it. I was FLASH HAPPY. No way to get into Hi Suite as it won't get out of boot logo. If I could get into the bootloader mode, I could reflash the correct files but can't do that. Oh well, lesson learned!
lilbrat said:
You need to stop while your ahead.. first off probably should have tried to stop you when you failed to mention what model you have as you haven't stated as much. and you just seem to be flash happy. All I will suggest now is either you can can try to recover it through Huawei HiSuite or take it to your local shop an let them re-flash it..
Click to expand...
Click to collapse

elcidroyale said:
damn you said it. I was FLASH HAPPY. No way to get into Hi Suite as it won't get out of boot logo. If I could get into the bootloader mode, I could reflash the correct files but can't do that. Oh well, lesson learned!
Click to expand...
Click to collapse
Ok..first get the correct Rom for your phone..don't do anything else till you do that.. the put you phone on the charger we don't want it to die and it needs to be charged.. now see if you can manually but your phone in fastboot mode either manually or by ADB commands .. and read up how to flash the rom that way..

WOW the gods have smiled down upon me and my and my tablet this morning! It was surely dead but I held power down and then plugged in cable then voila, fastboot mode!
Bootloader was locked so I unlocked it so I could flash correct files. I unlocked then it automatically reboot normal which was not good. The back to same frozen boot screen. I kept trying and couldn't get back into fastboot or any other useful mode. Then I went away and came back and tried again - hold down volume & plug cable - BOOM it work again.
I flashed the stock files and good news is back to square one with a mostly working tablet. Just same issue of no bluetooth, keyboard (I downloaded from web), stock apps missing & no "updater" section in settings.
Any fix for this? Any link to OFFICIAL stock rom for USA version?
Thanks for you help man!

elcidroyale said:
WOW the gods have smiled down upon me and my and my tablet this morning! It was surely dead but I held power down and then plugged in cable then voila, fastboot mode!
Bootloader was locked so I unlocked it so I could flash correct files. I unlocked then it automatically reboot normal which was not good. The back to same frozen boot screen. I kept trying and couldn't get back into fastboot or any other useful mode. Then I went away and came back and tried again - hold down volume & plug cable - BOOM it work again.
I flashed the stock files and good news is back to square one with a mostly working tablet. Just same issue of no bluetooth, keyboard (I downloaded from web), stock apps missing & no "updater" section in settings.
Any fix for this? Any link to OFFICIAL stock rom for USA version?
Thanks for you help man!
Click to expand...
Click to collapse
Hit the thanks button.. try hooking it up to HiSuite and see if it will repair it through there.. (look here.. https://www.getdroidtips.com/huawei-mediapad-m3-stock-firmware/ ) if it has what you need you can fastboot or srktool it..

lilbrat said:
Hit the thanks button.. try hooking it up to HiSuite and see if it will repair it through there.. (look here.. https://www.getdroidtips.com/huawei-mediapad-m3-stock-firmware/ ) if it has what you need you can fastboot or srktool it..
Click to expand...
Click to collapse
UPDATE FIX:
It was indeed bricked. Luckily it was under warranty so I sent it to Huawei Service Center and they sent me a brand new tablet in a few days.
Now back to square one with no 5ghz and SLOW AND ****TY 2.5ghz. ugh
Sent from my BTV-W09 using Tapatalk

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?