Related
[Solved] Yesterday I tried to root my phone but after do all the steps that were on the sites, I couldn't turn it on anymore. Everytime I try it makes the bootloader but when it ends, the moto x turns off again. I don't know what happened someone told me that it names hardbrick so, can anyone tell me how to fix it? Or if it's possible.
If you need some information to help me, just ask. [Solved]
If you can get to the bootloader is not bricked.
Look up how to use fastboot to flash the system and boot img.
Go to soltrans' thread and you should be fine
Sent from my victara
fastercon said:
Go to soltrans' thread and you should be fine
Sent from my victara
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x-2014/general/guide-update-xt1095-pure-edition-to-t2937074
Start with step "0".
Hi there,
So I just bought a brand new N6.
Did nothing to it, did not unklock the bootloader, di not flash anything.
Just ran it a first time, set my account, donwloaded the 5.1 OTA when proposed to and then it was over.
After the OTA installation my phone displayed a dead android and "Error".
When rebooting my phone, the apps are "optimizing" undefinitely and then the phone will restart.
I tried factory reset from recovery, that did nothing, I mean, the phone will still bootloop endlessly.
My bootloader is not unlocked so I cannot flash my phone..
Is there anything I can do ?
Thank you in advance
Aanze said:
Hi there,
So I just bought a brand new N6.
Did nothing to it, did not unklock the bootloader, di not flash anything.
Just ran it a first time, set my account, donwloaded the 5.1 OTA when proposed to and then it was over.
After the OTA installation my phone displayed a dead android and "Error".
When rebooting my phone, the apps are "optimizing" undefinitely and then the phone will restart.
I tried factory reset from recovery, that did nothing, I mean, the phone will still bootloop endlessly.
My bootloader is not unlocked so I cannot flash my phone..
Is there anything I can do ?
Thank you in advance
Click to expand...
Click to collapse
try fastboot formatting userdata and fastboot formatting cache
simms22 said:
try fastboot formatting userdata and fastboot formatting cache
Click to expand...
Click to collapse
Same story.
Black screen then reboot, then optimizing then reboot and so on...
Aanze said:
Same story.
Black screen then reboot, then optimizing then reboot and so on...
Click to expand...
Click to collapse
Well, since you haven't enabled OEM unlock, there's not much you can do besides RMA at this point.
Aanze said:
Same story.
Black screen then reboot, then optimizing then reboot and so on...
Click to expand...
Click to collapse
unfortunately, that might have been your only option. as you need to boot up first, to enable unlocking of your bootloader, to reflash the factory image. and you cant boot up
Evolution_Tech said:
Well, since you haven't enabled OEM unlock, there's not much you can do besides RMA at this point.
Click to expand...
Click to collapse
That's what I thought.
I thought I could use the fix described here http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518 but my device does not appear as "qhusb_bulk" like specified so I guess its over.
id get the phone refurbished, from google or from motorola, since it wasnt anything that you did, but was the updates fault. btw, that happens, very rarely, but it does happen that updates can cause issues.
simms22 said:
id get the phone refurbished, from google or from motorola, since it wasnt anything that you did, but was the updates fault. btw, that happens, very rarely, but it does happen that updates can cause issues.
Click to expand...
Click to collapse
Well thank you anyway, looks like I have no other choice than send the device back.
One last question, since my phone won't stop rebooting endlessly is there any way to turn it off ? Long press on power does not do anythng, it will stil restart...
Edit: I found how to turn it off through bootloader.
Aanze said:
Well thank you anyway, looks like I have no other choice than send the device back.
One last question, since my phone won't stop rebooting endlessly is there any way to turn it off ? Long press on power does not do anythng, it will stil restart...
Edit: I found how to turn it off through bootloader.
Click to expand...
Click to collapse
exactly. i was just gonna write how to do that.
simms22 said:
exactly. i was just gonna write how to do that.
Click to expand...
Click to collapse
Sorry to come back on this thread.
So now I have noticed that when in fastboot, if I type "fastboot oem unlock" I'm getting the popup proposing to unlock bootloader.
As I never selected USB debugging nor enabled developper option when my phone was working, I doubt it would work properly.
Would I have any chance to recover my phone if choosing to unlock the bootloader ?
Aanze said:
Sorry to come back on this thread.
So now I have noticed that when in fastboot, if I type "fastboot oem unlock" I'm getting the popup proposing to unlock bootloader.
As I never selected USB debugging nor enabled developper option when my phone was working, I doubt it would work properly.
Would I have any chance to recover my phone if choosing to unlock the bootloader ?
Click to expand...
Click to collapse
If getting that it should unlock. Got nothing to lose and if does unlock it is recoverable.
Aanze said:
Sorry to come back on this thread.
So now I have noticed that when in fastboot, if I type "fastboot oem unlock" I'm getting the popup proposing to unlock bootloader.
As I never selected USB debugging nor enabled developper option when my phone was working, I doubt it would work properly.
Would I have any chance to recover my phone if choosing to unlock the bootloader ?
Click to expand...
Click to collapse
yes! if you can unlock the bootloader, then you can flash the factory image via fastboot while youre in your bootloader. which would fix you not booting
prdog1 said:
If getting that it should unlock. Got nothing to lose and if does unlock it is recoverable.
Click to expand...
Click to collapse
Wow.. So I tried.. and.. "Device is unlocked" is displayed... I guess I have a chance to flash something now.
Aanze said:
Wow.. So I tried.. and.. "Device is unlocked" is displayed... I guess I have a chance to flash something now.
Click to expand...
Click to collapse
Your good to go. Just need to fastboot the stock images.
just return it, if you find that you cant recover it after unlocking the bootloader then they wont take it back
Aanze said:
Wow.. So I tried.. and.. "Device is unlocked" is displayed... I guess I have a chance to flash something now.
Click to expand...
Click to collapse
grab a factory image, and read directions for flashing a factory image. you want to flash each individual file inside separately, instead of using the flash-all script.
simms22 said:
grab a factory image, and read directions for flashing a factory image. you want to flash each individual file inside separately, instead of using the flash-all script.
Click to expand...
Click to collapse
Yep, doing it right now.. flashing system currently.. crossing fingers;.
crossing my fingers for you over here as well
It worked !! IT WORKED !
I love you xda ! really do love you.
Thanks a million.
(Although it's a bit strange that I was able to unlock bootloader without usb debbugging mode enabled no ?)
This is very interesting indeed. To the OP, where did you purchase the device? I find it very peculiar that you were able to issue the OEM unlock command without using the toggle in settings.
Ive had this problem for ages and tried everything i can think of. hopefully by now someone has experienced the same problem and solved it.
*My phone is stuck on honor boot logo
*i can access e-recovery
*i can access stock recovery
*i can access fastboot and device is recognised on my laptop
* i can wipe cache and factory reset successully and have done many times
*i can and have used the dload (3 button method) to flash stock rom successfully
Now the problem is that although i have flashed the earliest stock rom NEM-L51C432B102 it fails saying incorrect package!!!i think this is because my phone came with B103 or B104 and you can only flash from what your phone originally had and up.
I have flashed NEM-L51C432b120 and also NEM-L51C432b130 and although it says successful it reboots and remains stuck on honor boot logo!
I have entered fastboot and i can issue commands but they all fail saying REMOTE COMMAND NOT ALLOWED.
I can't use ADB because it doesn't recognise my device. Obviously ADB and FASTBOOT wont work because i can't access developper options and select enable USB debugging or OEM Unlock because the phone is stuck on honor boot logo.
Also my bootloader must be locked. I have the unlock code but i can't issue the command FASTBOOT OEM UNLOCK XXXXXXXXXXXXXXX because as mentioned before it says FAILED REMOTE COMMAND NOT ALLOWED.
I have even tried flashing rollback packages(there isnt one for NEM-L51)for other models, followed by flashing stock rom for my model device.
When i bought the phone it came with either the B103 or B104 package but after months of searching i can't find on the internet.
Is my phone a lost cause??? is it hard bricked? So i am praying that there is a guru out there who can solve this very strange problem.
Many thanks in advance.
iantechie1979 said:
Ive had this problem for ages and tried everything i can think of. hopefully by now someone has experienced the same problem and solved it.
*My phone is stuck on honor boot logo
*i can access e-recovery
*i can access stock recovery
*i can access fastboot and device is recognised on my laptop
* i can wipe cache and factory reset successully and have done many times
*i can and have used the dload (3 button method) to flash stock rom successfully
Now the problem is that although i have flashed the earliest stock rom NEM-L51C432B102 it fails saying incorrect package!!!i think this is because my phone came with B103 or B104 and you can only flash from what your phone originally had and up.
I have flashed NEM-L51C432b120 and also NEM-L51C432b130 and although it says successful it reboots and remains stuck on honor boot logo!
I have entered fastboot and i can issue commands but they all fail saying REMOTE COMMAND NOT ALLOWED.
I can't use ADB because it doesn't recognise my device. Obviously ADB and FASTBOOT wont work because i can't access developper options and select enable USB debugging or OEM Unlock because the phone is stuck on honor boot logo.
Also my bootloader must be locked. I have the unlock code but i can't issue the command FASTBOOT OEM UNLOCK XXXXXXXXXXXXXXX because as mentioned before it says FAILED REMOTE COMMAND NOT ALLOWED.
I have even tried flashing rollback packages(there isnt one for NEM-L51)for other models, followed by flashing stock rom for my model device.
When i bought the phone it came with either the B103 or B104 package but after months of searching i can't find on the internet.
Is my phone a lost cause??? is it hard bricked? So i am praying that there is a guru out there who can solve this very strange problem.
Many thanks in advance.
Click to expand...
Click to collapse
Oh well. Seriously this is the same issue my frn asked me to help. This is soo serious that we can only unbrick through update.app or else service center. Since u said dload method works but stucks device on bootlogo. U need to visit service center if under Warranty
iantechie1979 said:
When i bought the phone it came with either the B103 or B104 package but after months of searching i can't find on the internet.
Is my phone a lost cause??? is it hard bricked? So i am praying that there is a guru out there who can solve this very strange problem.
Many thanks in advance.
Click to expand...
Click to collapse
Flash these files and it should, most probably, be fine.
use dload method as given here- https://forum.xda-developers.com/showpost.php?p=73954487&postcount=240
as there are many different opinions on this method of using only update.app file but thats not true and it should be all the files.
Main file - http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1165/g104/v71812/f1/full/update.zip
Data file- http://update.hicloud.com:8180/TDS/...1812/f1/full/hw/eu/update_data_full_hw_eu.zip
Flash both the files in order. 1st file will restore your system but then you need to have 2nd file so that apps are installed and all working fine.
After 1st file, it may reboot on its own and stuck on honor logo, reboot to recovery and then do factory reset, it will be fine.
Then let it boot to set up. Dont set your phone. Shutdown and flash the 2nd file.
boot and set up.
Good luck. Please provide feedback once done. In case of further issue, let me know and will dig more into this.
Oh this is hard.
chrisleLP said:
Oh this is hard.
Click to expand...
Click to collapse
What is hard?
shashank1320 said:
What is hard?
Click to expand...
Click to collapse
This problem.
chrisleLP said:
This problem.
Click to expand...
Click to collapse
you cant follow simple instructions? you shouldnt be on this forum if youre not ready to lose data or brick your device.
Thanks for your input so far people. Much appreciated. @shashank1320 I am downloading the files you suggested and will flash them exactly according to your instructions. I will get back to you in a couple of days with the result. Fingers crossed.
gopinaidu77 said:
Oh well. Seriously this is the same issue my frn asked me to help. This is soo serious that we can only unbrick through update.app or else service center. Since u said dload method works but stucks device on bootlogo. U need to visit service center if under Warranty
Click to expand...
Click to collapse
Unfortunately my warranty has expired. The annoying thing is that if i had sent my device off six months ago when this first happened it would still be under warranty but in the UK there is only 1 service center, yes 1, and its hundreds of miles away! So i figured i could solve it myself. You live and learn.
Hey there everyone. I still havent managed to solve the issue with my device and its not through lack of trying. I have re downloaded all of the stock firmwares that you can possibly find on the internet. I also found one ive necer seen before. Its a full service repair b355. Fingers crossed, a miracle might happen and it will just boot up like when i first bought it. to begin with tho, i'm going to start with b102 and work through them b120, b130 ,b130rollback ,b350(beta), b350, b355 and then the b355 full service repair! I also got a couple of rollback packages(around 80mb) if all else fails.
I know, i'm nuts!! Finally before i admit defeat i'm going to part with £15 to buy credits for the dc-unlocker and dcPhoenx programs. From what ive read it has a good chance of solving it. I've taken soooo long before considering this option because i think its wrong that someone(s) is making loads of money from this. Why havent huawei/honor included a similar program in hi-suite. Anyway ive gone off on a tangent.
One last question though. Strangely enough i only just thought of it recently....
Is it a necessity to have your sim card in the tray as well as the sd-card????? All this time i havent had a sim in the phone as its in a crappy old one so i can still communicate with the world!!!!
Thank you to everyone for taking your time to read this. I hope a solution is possible.
iantechie1979 said:
Hey there everyone. I still havent managed to solve the issue with my device and its not through lack of trying. I have re downloaded all of the stock firmwares that you can possibly find on the internet. I also found one ive necer seen before. Its a full service repair b355. Fingers crossed, a miracle might happen and it will just boot up like when i first bought it. to begin with tho, i'm going to start with b102 and work through them b120, b130 ,b130rollback ,b350(beta), b350, b355 and then the b355 full service repair! I also got a couple of rollback packages(around 80mb) if all else fails.
I know, i'm nuts!! Finally before i admit defeat i'm going to part with £15 to buy credits for the dc-unlocker and dcPhoenx programs. From what ive read it has a good chance of solving it. I've taken soooo long before considering this option because i think its wrong that someone(s) is making loads of money from this. Why havent huawei/honor included a similar program in hi-suite. Anyway ive gone off on a tangent.
One last question though. Strangely enough i only just thought of it recently....
Is it a necessity to have your sim card in the tray as well as the sd-card????? All this time i havent had a sim in the phone as its in a crappy old one so i can still communicate with the world!!!!
Thank you to everyone for taking your time to read this. I hope a solution is possible.
Click to expand...
Click to collapse
No need of sim card in tray while using dload. Just sd card is fine. Let me go through it again and try to help before you go for 15 dollars for dc phoenix
shashank1320 said:
No need of sim card in tray while using dload. Just sd card is fine. Let me go through it again and try to help before you go for 15 dollars for dc phoenix
Click to expand...
Click to collapse
Yeah i didn't think it made any difference but its good to make sure.
i'll be waiting patiently for any golden nuggets of help you can give me.
thanks shashank1320,:fingers-crossed:
iantechie1979 said:
Yeah i didn't think it made any difference but its good to make sure.
i'll be waiting patiently for any golden nuggets of help you can give me.
thanks shashank1320,:fingers-crossed:
Click to expand...
Click to collapse
Did you flash those files i given? If not can try. Else i will have to look for other alternative
yeah i downloaded those files you had mentioned in your post and followed the instructions to the letter.
I've got a suggestion if you have tried all these above.
Can you try the following on ADB and then try to unlock OEM again.
fastboot oem relock YourUnlockCode
I've done the same and it helped, even when bootloader displayed UNLOCKED. Please try it. :good::good:
Click to expand...
Click to collapse
Click to expand...
Click to collapse
@shashank1320 Hi, i have similar problem with my NEM-L21 device... I tried to flash the Elite ROM v5.1 but i didnt succeed so i decided to restore my old rom from backup with TWRP. When i restored it it just didnt load. It was stuck on honor logo for a long time. I tried the dload method many times but nothing worked so far. I even tried unbrick it with HUAWEI Multi-tool but it also didnt worked.
Now i cant acces anything, just fastboot. I cant even turn off the device. Please can you help me somehow?
NameNotFound74 said:
@shashank1320 Hi, i have similar problem with my NEM-L21 device... I tried to flash the Elite ROM v5.1 but i didnt succeed so i decided to restore my old rom from backup with TWRP. When i restored it it just didnt load. It was stuck on honor logo for a long time. I tried the dload method many times but nothing worked so far. I even tried unbrick it with HUAWEI Multi-tool but it also didnt worked.
Now i cant acces anything, just fastboot. I cant even turn off the device. Please can you help me somehow?
Click to expand...
Click to collapse
Try unlocking the bootloader again even if it is unlocked. It will factory reset the device and it should boot fine. Have stuck on this many a time and this was the method i followed.
Hi friends,
I am telling you the whole story in a short way,
I have needed to root my devices, so I unlocked bootloader as it said on some web sites and install a new rom. Mine was Android 8.1 Nokia 7 plus TA-1046 600CN I think now its Pie 600WW.
After that that Pie did not work well on my devices, especially sensors and notifications was awful. So tried to downgrade to stock rom, but could not.
Right now, there is no rom on my device and bootloader and also locked the critical partitions.
I have TWRP recovery installed but i cant enter the recovery mode, the device is always in download mode even try to enter with volume UP + Power button phone goes directly download mode.
I have done something stupid with locking bootloader I agree but please help me to get out of this situation.
Its too bad without a phone
Thank you very much.
I dont know if it will work. Did you try to switch the partitions from A to B or B to A?
There are tutorials on how to do that via adb. I cant tell you exactly how to do it, i did it also from tutorials.
magiQx said:
I dont know if it will work. Did you try to switch the partitions from A to B or B to A?
There are tutorials on how to do that via adb. I cant tell you exactly how to do it, i did it also from tutorials.
Click to expand...
Click to collapse
in both partitions it is saying Your device is corrupt. It can't be trusted and will not boot.
and
I cant go into recovery
That sounds bad. Sorry, im not that advanced.
Isn't it possible to force it into recovery via adb? I got no idea, just asking.
magiQx said:
That sounds bad. Sorry, im not that advanced.
Isn't it possible to force it into recovery via adb? I got no idea, just asking.
Click to expand...
Click to collapse
Unfortunately I can`t because the bootloader is locked I have to unlock it but I can not because I have to downgrade the bootloader from Pie to Oreo
It sounds like a bad situation indeed. I think you may be SOOL, but hopefully a way forward will become apparent. Otherwise a new device might be indicated ?
1.unlock bootloader
2.reflash firmware with tools.
for piehttps://forum.xda-developers.com/nokia-7-plus/how-to/guide-workaround-flashing-sparse-t3906070
for oreohttps://forum.xda-developers.com/nokia-7-plus/how-to/workaround-flashing-oreo-firmware-t3793791
I ran into a similar situation and I installed the stock rom using NOST (Nokia Online Service Tool) and the stock rom in .NB0 file type.
If you need those files PM me and I can provide them for you, most likely you have them already if you unlocked your bootloader using TechMesto's service.
So.... I removed my Pixel 5 form the beta 13 program, selected update on the devices and had it download Android 12 a few weeks back. On reboot I get the "device is corrupt" error with visit the g.co/ABH link. If I hit the power button that error loops, and trying a hard / factory reset does nothing.
I tried several of the steps but since I cannot get into Dev mode to unlock the bootloader I'm kind of stuck.
The most I have been able to do is with the rescue tool, but that throws a "software on device is newer then this tool" error and wont go forward.
Any suggestions? Should I just send in to a repair shop? Or move on?
I heard from a friend yesterday that this happens with USB C to USB C. Try an A or B port and sideload the OTA
xunholyx said:
I heard from a friend yesterday that this happens with USB C to USB C. Try an A or B port and sideload the OTA
Click to expand...
Click to collapse
Tried both types of cables, no luck...
grmacd said:
Tried both types of cables, no luck...
Click to expand...
Click to collapse
As recommended by @xunholyx try sideloading the OTA, if you're able to get into recovery.
If you didn't have OEM unlocking enabled in Developer Options, you might be SOL.
V0latyle said:
As recommended by @xunholyx try sideloading the OTA, if you're able to get into recovery.
If you didn't have OEM unlocking enabled in Developer Options, you might be SOL.
Click to expand...
Click to collapse
Yeah since the OEM unlock was not in place before the beta downgrade was triggered and failed, I can't get into the OS to turn it on. So SOL I bet
grmacd said:
Yeah since the OEM unlock was not in place before the beta downgrade was triggered and failed, I can't get into the OS to turn it on. So SOL I bet
Click to expand...
Click to collapse
Unfortunate and I feel for you.
It's generally advisable to always unlock the bootloader when running any kind of beta software, just because of this eventuality - if something goes wrong, you need to have a way to recover the device.
grmacd said:
Yeah since the OEM unlock was not in place before the beta downgrade was triggered and failed, I can't get into the OS to turn it on. So SOL I bet
Click to expand...
Click to collapse
You should be able to boot to recovery from the bootloader
I can boot to recovery, but the software wont sideload since the boot locker is locked.
My one hope is the fact Rescue mode on the web is throwing "software on the device older then this tool" so I am hoping once that gets a newer version I will be ok. So into the drawer it goes...
But you don't need an unlocked bootloader to sideload an OTA....
xunholyx said:
But you don't need an unlocked bootloader to sideload an OTA....
Click to expand...
Click to collapse
Ok... perhaps I will give it another try tomorrow.
grmacd said:
Ok... perhaps I will give it another try tomorrow.
Click to expand...
Click to collapse
Try flashing it a second time when you get the error. A friend is mine had trouble with it and a locked bootloader as well. I don't remember how he fixed it, but I think that that was it. I'll get in touch with him later. I'm at work right now
xunholyx said:
Try flashing it a second time when you get the error. A friend is mine had trouble with it and a locked bootloader as well. I don't remember how he fixed it, but I think that that was it. I'll get in touch with him later. I'm at work right now
Click to expand...
Click to collapse
So this AM I downloaded the newest ZIP file and followed the step on the site - after about 10 minutes presto the phone is back up and running with Android 13! Thanks for your help!