anybody here that can help me? I was trying to install a custom rom but apparently i messed up big time ... First i followed a tutorial that says that i have to unlock my device first so that's what i did.... then it got stuck on a black screen with the text "your device has been unlocked and can't be trusted .... Your device will boot in 5 seconds .... " But it doesn't. It just keeps displaying that screen. The only thing i can do is going into TWRP (3.2.1-0) .... what should i do now? i just want the phone back to normal, so no custom roms or anything .... Is it possible or is the phone ready for the garbage bin?
For now : Should be easy to fix.
jer194 said:
For now : Should be easy to fix.
Click to expand...
Click to collapse
How??
How long did you leave your device booting on that 'your device is unlocked' screen? Sometimes the initial boot after unlocking can be up to 5 minutes as your device got wiped by the unlock.
What state is your device in at the moment - i.e what firmware do you have on your device and is it just TWRP you have flashed? If you tried to flash a custom ROM did you erase /system, /data and /cache in TWRP before installing the custom ROM? Which custom ROM have you tried to flash?
fiestaboyke said:
How??
Click to expand...
Click to collapse
If you want to go to stock, check this:
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
However:
Anything you want to backup before?
If so, and if not done yet, do it first, via TWRP.
Also: you already have TWRP, so you did more than just unlocking bootloader I think.
Maybe you missed to flash one of the custom ROMs, which could explain
'nothing happening, after bootloader screen'.
There is just too many unknowns to tell exactly what happened.
Ok, it's fixed now. after a long and stressful search i finally found a perfect guide for my problem and everything works fine now, so no more custom roms for me anymore
Related
So basically I am not smart and factory reset my phone in settings. The bootloader was unlocked and rooted. First phone I have ever rooted and this is all just a lot of information to take in. Trying to read and look into my problem but nothing I am trying is working.
When I turn my phone on it goes immediately into TWRP. When TWRP came up I wiped the data, cache, and dalvik. Not sure what all I have tried but I can't figure anything out. I am assuming I need to flash a stock ROM back onto my phone? Not sure how to do that. I have a stock rom downloaded. When I try to flash it just says 'waiting for device'. It is plugged in but I am assuming USB debugging is not turned on which is why it doesn't locate it?
Not really sure if my assumptions are correct but I am failing horribly here and would love if someone could explain this to me step by step like I am a cave person. Would even be willing to paypal someone $5 if that kind of thing is allowed for help. Thanks for helping a moron out.
hegro said:
So basically I am not smart and factory reset my phone in settings. The bootloader was unlocked and rooted. First phone I have ever rooted and this is all just a lot of information to take in. Trying to read and look into my problem but nothing I am trying is working.
When I turn my phone on it goes immediately into TWRP. When TWRP came up I wiped the data, cache, and dalvik. Not sure what all I have tried but I can't figure anything out. I am assuming I need to flash a stock ROM back onto my phone? Not sure how to do that. I have a stock rom downloaded. When I try to flash it just says 'waiting for device'. It is plugged in but I am assuming USB debugging is not turned on which is why it doesn't locate it?
Not really sure if my assumptions are correct but I am failing horribly here and would love if someone could explain this to me step by step like I am a cave person. Would even be willing to paypal someone $5 if that kind of thing is allowed for help. Thanks for helping a moron out.
Click to expand...
Click to collapse
Some more information please? Were you on stock rooted or custom rom. Best bet then is clean flashing a custom rom.
GtrCraft said:
Some more information please? Were you on stock rooted or custom rom. Best bet then is clean flashing a custom rom.
Click to expand...
Click to collapse
Pretty sure I was just stock rooted. How would I go about doing that? Like I said, I have a stock rom downloaded on my PC. Tried to flash it but all I get is 'waiting for device' in the cmd window after directing it towards the zip file.
Also as I said, trying to learn and absorb as much info as I can here, never done this before so I am a little slow. =/
just tried using THIS method but when I plug my phone in it is not recognized in RSD Lite. I keep reading I need USB debugging on. I can't turn it on from recovery screen, no? Is there anything I can do?
hegro said:
just tried using THIS method but when I plug my phone in it is not recognized in RSD Lite. I keep reading I need USB debugging on. I can't turn it on from recovery screen, no? Is there anything I can do?
Click to expand...
Click to collapse
Boot to twrp and flash a custom rom zip like lineage os. Or a modified stock rom like stoneware
Yes, wiped phone, put stoneware on my phone, booted to twrp, installed stoneware, reboot, back to twrp. I have to be doing something wrong but I don't know what it is. I have tried doing this with multiple different ROMs, flashing in TWRP.
hegro said:
Yes, wiped phone, put stoneware on my phone, booted to twrp, installed stoneware, reboot, back to twrp. I have to be doing something wrong but I don't know what it is. I have tried doing this with multiple different ROMs, flashing in TWRP.
Click to expand...
Click to collapse
I had this issue when I did (like a idiot) a Ota update. Only fix I got was running g5 plus tool kit and flashing stock Rom though it by following instructions on the program..
Factory reset shouldn't have caused this issue.. Unless you formated your data in twrp.. But if the boot is altered or damaged and you just put a custom Rom on top I think you might find you won't have a baseband (no mobile network).. The original stock Rom is available via links in the windows toolkit 1.6 gig
Go into fastboot and just type fastboot continue
fixed
alevity said:
I has this issue when I did (like a idiot) a Ota update. Only fix I got was running g5 plus tool kit and flashing stock Rom though it by following instructions on the program..
Factory reset shouldn't have caused this issue.. Unless you formated your data in twrp.. But if the boot is altered or damaged and you just put a custom Rom on top I think you might find you won't have a baseband (no mobile network).. The original stock Rom is available via links in the windows toolkit 1.6 gig
Click to expand...
Click to collapse
So I ran the tool kit and put on a stock rom. My phone turns on now! Except when I turn it on it says that the device is unlocked and can't be trusted. ID: bad key.
hegro said:
So I ran the tool kit and put on a stock rom. My phone turns on now! Except when I turn it on it says that the device is unlocked and can't be trusted. ID: bad key.
Click to expand...
Click to collapse
boot into twrp again and reboot system
it should fix it
next time remember just go into fastboot and type "fastboot continue"
no need to wipe or reflash
power off your phone then volume down and power together until bootloader screen appearing than select factory mode and then press power button to select factory mode
hegro said:
So I ran the tool kit and put on a stock rom. My phone turns on now! Except when I turn it on it says that the device is unlocked and can't be trusted. ID: bad key.
Click to expand...
Click to collapse
That's completely normal we all have that just means it's unlocked bootloader. Enjoy your device normally
---------- Post added at 12:47 PM ---------- Previous post was at 12:44 PM ----------
bornlivedie said:
boot into twrp again and reboot system
it should fix it
next time remember just go into fastboot and type "fastboot continue"
no need to wipe or reflash
Click to expand...
Click to collapse
Why would doing that remove the hard coded warning that the bootloader is unlocked? Op had a functioning phone now and just didn't know the warning boot is perfectly OK.
pretty sure my twrp got replaced? idk but when I try to go to recovery all I get is the little dead android guy with the red triangle.
hegro said:
pretty sure my twrp got replaced? idk but when I try to go to recovery all I get is the little dead android guy with the red triangle.
Click to expand...
Click to collapse
That's stock recovery
alevity said:
That's completely normal we all have that just means it's unlocked bootloader. Enjoy your device normally
---------- Post added at 12:47 PM ---------- Previous post was at 12:44 PM ----------
Why would doing that remove the hard coded warning that the bootloader is unlocked? Op had a functioning phone now and just didn't know the warning boot is perfectly OK.
Click to expand...
Click to collapse
I wouldn't know about "perfectly ok" but I had that bad key thing before, and read the rebooting into TWRP fixes the "issue". It's true, it works. I have N/A now and not "bad key".
I am looking unlock and root my European Axon 7 running Android 7.1, and all of the guides seem to be for The US version and for Android marshmallow, do I need to revert my phone to an older version (if so how would I go around doing so?). Is there any up to date guides for rooting my version of the phone?
King Norman said:
I am looking unlock and root my European Axon 7 running Android 7.1, and all of the guides seem to be for The US version and for Android marshmallow, do I need to revert my phone to an older version (if so how would I go around doing so?). Is there any up to date guides for rooting my version of the phone?
Click to expand...
Click to collapse
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
I used this guide 2 weeks ago to unlock my wife's german axon 7, her phone was on 7.1 stock too, but no issue, you don't have to be on marshmallow. Only advice I can give you is to read the guide 2 times or more and take your time.
Btw after you done everything use the b05 modem, my wife has no call issues with this version. I flashed the dark rom to her phone, works nearly perfect.
King Norman said:
I am looking unlock and root my European Axon 7 running Android 7.1, and all of the guides seem to be for The US version and for Android marshmallow, do I need to revert my phone to an older version (if so how would I go around doing so?). Is there any up to date guides for rooting my version of the phone?
Click to expand...
Click to collapse
coremania said:
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
I used this guide 2 weeks ago to unlock my wife's german axon 7, her phone was on 7.1 stock too, but no issue, you don't have to be on marshmallow. Only advice I can give you is to read the guide 2 times or more and take your time.
Btw after you done everything use the b05 modem, my wife has no call issues with this version. I flashed the dark rom to her phone, works nearly perfect.
Click to expand...
Click to collapse
Why though? I also used that one, but you should try axon7toolkit. It seemingly does everything automatically and with an ok CMD interface
Choose an username... said:
Why though? I also used that one, but you should try axon7toolkit. It seemingly does everything automatically and with an ok CMD interface
Click to expand...
Click to collapse
Yes that's a nice option too, but reading, understanding and knowing what you're doing always works. I'm not a fan of Kit's.
personal choice I think. But you're right.
coremania said:
Yes that's a nice option too, but reading, understanding and knowing what you're doing always works. I'm not a fan of Kit's.
personal choice I think. But you're right.
Click to expand...
Click to collapse
It seems like very few people actually use the kit. Kinda defeats the purpose.
But yeah, that guide was how I learnt how to install TWRP via axon7tool whenever I needed it.
coremania said:
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
I used this guide 2 weeks ago to unlock my wife's german axon 7, her phone was on 7.1 stock too, but no issue, you don't have to be on marshmallow. Only advice I can give you is to read the guide 2 times or more and take your time.
Btw after you done everything use the b05 modem, my wife has no call issues with this version. I flashed the dark rom to her phone, works nearly perfect.
Click to expand...
Click to collapse
Thanks for the help! Unfortunately I must have done something wrong and I think I've soft bricked my phone! :'(
King Norman said:
Thanks for the help! Unfortunately I must have done something wrong and I think I've soft bricked my phone! :'(
Click to expand...
Click to collapse
Toolkit or step by step with the guide ? just start from scratch again, or try with the kit.
coremania said:
Toolkit or step by step with the guide ? just start from scratch again, or try with the kit.
Click to expand...
Click to collapse
Step by Step, I managed to unlock it and flash the bootstack, but I hit an error when trying to flash LOS and so decided to reboot the system and try again, however when rebooting the system I got the error "Your device software can't be checked for corruption, Please lock the bootloader". And I cant seem to access TWRP anymore, just the stock recovery.
Im just wondering if I can just flash stock because I cant use my phone at all atm
King Norman said:
Step by Step, I managed to unlock it and flash the bootstack, but I hit an error when trying to flash LOS and so decided to reboot the system and try again, however when rebooting the system I got the error "Your device software can't be checked for corruption, Please lock the bootloader". And I cant seem to access TWRP anymore, just the stock recovery.
Im just wondering if I can just flash stock because I cant use my phone at all atm
Click to expand...
Click to collapse
Then flash twrp again, if your on stock recovery. You need twrp. Something must replaced twrp with the stock recovery.
After you flashed twrp use the files from the official Los thread
Bootloader and modem.
coremania said:
Then flash twrp again, if your on stock recovery. You need twrp. Something must replaced twrp with the stock recovery.
After you flashed twrp use the files from the official Los thread
Bootloader and modem.
Click to expand...
Click to collapse
Unfortunately I cant seem to view the phone as an adb device, unless i select the "Apply update from adb" option in the stock recovery, however this only lets me sideload and i cant reboot it to edl mode or anything like that to install TWRP.
What happens if you are on stock recovery and type adb reboot edl. Another way to get to edl mode can be to shut down the phone and press both volume keys while connecting the USB cable, I read that somewhere here, may need some trys.
Btw,
"Your device software can't be checked for corruption" this is normal if your unlocked.
coremania said:
What happens if you are on stock recovery and type adb reboot edl. Another way to get to edl mode can be to shut down the phone and press both volume keys while connecting the USB cable, I read that somewhere here, may need some trys.
Btw,
"Your device software can't be checked for corruption" this is normal if your unlocked.
Click to expand...
Click to collapse
I tried the volume button thing and it must have worked because i redid the scripts and managed to get TWRP back up!
now I just need to do the universal bootstack, the N_Modem thing, and then LOS Right?
Thanks so much for your help
King Norman said:
I tried the volume button thing and it must have worked because i redid the scripts and managed to get TWRP back up!
now I just need to do the universal bootstack, the N_Modem thing, and then LOS Right?
Thanks so much for your help
Click to expand...
Click to collapse
Good, you did it. Yes, after you flashed the latest official twrp,
flash the bootloader zip and modem zip which are linked at the first page of the Los thread, then your prefered rom with gapps and root if you like.
DON'T relock your bootloader !!!
Have fun!
Hi Guys can somebody tell me can we install custom rom in fastboot mode without help of twrp recovery if not..then is that any possibilities to make the fastboot custom rom with twrp preflash..for moto g4 plus 1643.
"cutom" ROM, hmm that's interesting name
siddhesh9146 said:
"cutom" ROM, hmm that's interesting name
Click to expand...
Click to collapse
Ya but know one can help here
chouhanprem said:
Hi Guys can somebody tell me can we install custom rom in fastboot mode without help of twrp recovery if not..then is that any possibilities to make the fastboot custom rom with twrp preflash..for moto g4 plus 1643.
Click to expand...
Click to collapse
Can i ask you, why do you want this kind of custom ROM? TWRP flashing works fine, and it is easy to manage everything. Then why ???
____Mdd said:
Can i ask you, why do you want this kind of custom ROM? TWRP flashing works fine, and it is easy to manage everything. Then why ???
Click to expand...
Click to collapse
becz i am unable to go in twrp my moto g4 plus was hard brick and i try all this things given in this thread but after all its still stuck in bootloop in M logo..
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
but still there is no work ..so that i want it..
chouhanprem said:
becz i am unable to go in twrp my moto g4 plus was hard brick and i try all this things given in this thread but after all its still stuck in bootloop in M logo..
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
but still there is no work ..so that i want it..
Click to expand...
Click to collapse
I read it and if i remembered correctly, there was someone else too, whose phone was getting stuck on the same and flashing of nothing worked.
In such case, as echo92 said you there, service center can be better for this.
Here is the same that discussed before: https://forum.xda-developers.com/moto-g4-plus/help/device-unlocked-trusted-key-n-t3656686/page2
____Mdd said:
I read it and if i remembered correctly, there was someone else too, whose phone was getting stuck on the same and flashing of nothing worked.
In such case, as echo92 said you there, service center can be better for this.
Here is the same that discussed before: https://forum.xda-developers.com/moto-g4-plus/help/device-unlocked-trusted-key-n-t3656686/page2
Click to expand...
Click to collapse
Ok may be this is the last option for me.
One thing I can perhaps suggest is that at any point did you change the file system of your device partitions via TWRP? I recall that having cache set as f2fs formatting might cause bootloops. Cache is ext4, system is ext4 and data is f2fs on my device.
If your device is still in the same state as last time, where you flashed the stock ROM and still is bootlooping, I'd suggest take it to a service centre.
Granted, the cost of a new motherboard is expensive (up to 10000 rupees or your regional equivalent, from what I read).
Ask them first to attempt to re-flash the latest stock ROM onto your device. They may have to fully wipe your device. See if they can check the partition formatting of your device.
It sounds like when you hard bricked previously, something other than your bootloader might have been corrupted and not properly repaired, but remotely determining that won't be easy...
Besides, if the Motorola stock ROM fails to boot, what's the chances of a custom ROM, assuming you could flash via fastboot, or working?
Hi,
I was really unhappy with Pie and tried to prepare my device for Oreo downgrade.
What I did was
- unlock bootloader
- tried to install TWRP
- mixed something up in that processs
- realized TWRP cannot be installed apparently on Pie right now
- MiFlash seems to be not working as well when trying to install stock rom (says flashing but nothing happens)
Well Pie is running right now, but when trying to lock the bootloader again for future updates, the phones is only showing a black screen.
After that I am trying to unlock bootloader again (fastboot oem unlock) and everything works again, except when I try to boot into recovery ("the system is destroyed" or something like that).
Trying to "hotboot" into TWRP currently is also not working, "unable to mount..." and after that automatically reboots into the system itself.
Any idea how I can either put a standard Pie installation with working recovery and locked bootloader on?
Or how I can maybe install Oreo instead? As I said, the MiFlash tool doesn't do anything (tells me "flashing" but actually doesn't do anything).
Thanks for your help!
cyrrel said:
Hi,
I was really unhappy with Pie and tried to prepare my device for Oreo downgrade.
What I did was
- unlock bootloader
- tried to install TWRP
- mixed something up in that processs
- realized TWRP cannot be installed apparently on Pie right now
- MiFlash seems to be not working as well when trying to install stock rom (says flashing but nothing happens)
Well Pie is running right now, but when trying to lock the bootloader again for future updates, the phones is only showing a black screen.
After that I am trying to unlock bootloader again (fastboot oem unlock) and everything works again, except when I try to boot into recovery ("the system is destroyed" or something like that).
Trying to "hotboot" into TWRP currently is also not working, "unable to mount..." and after that automatically reboots into the system itself.
Any idea how I can either put a standard Pie installation with working recovery and locked bootloader on?
Or how I can maybe install Oreo instead? As I said, the MiFlash tool doesn't do anything (tells me "flashing" but actually doesn't do anything).
Thanks for your help!
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a1/development/treble-twrp-installer-treble-manager-t3793637
Hi,
I somehow managed to put 8.1 on and everything is back to normal.
Thanks
cyrrel said:
Hi,
I somehow managed to put 8.1 on and everything is back to normal.
Thanks
Click to expand...
Click to collapse
can you explain us the procedures that you have followed to downgrade. It would be really helpful. i have tried this
method but it didn't work for me. i am facing IMEI 0/no signal issues using this method.
Thanks
well I have done a lot of stuff that made my phone not working anymore because using a wrong .img file and didn'T understand the tutorial (same link you have provided) fully.
But at the end it was quite close to the link you have sent, the MiFlash tool I needed for example to try like 10 times per step until it worked, maybe a bad cable - I don't know.
But finally it was working, after March update without network signal, but with /boot & /efs partitions and Nov fastboot image, it was working.
If you need any more detail for a specific step, you can of course ask and I can check if there was anything special I can remember
cyrrel said:
well I have done a lot of stuff that made my phone not working anymore because using a wrong .img file and didn'T understand the tutorial (same link you have provided) fully.
But at the end it was quite close to the link you have sent, the MiFlash tool I needed for example to try like 10 times per step until it worked, maybe a bad cable - I don't know.
But finally it was working, after March update without network signal, but with /boot & /efs partitions and Nov fastboot image, it was working.
If you need any more detail for a specific step, you can of course ask and I can check if there was anything special I can remember
Click to expand...
Click to collapse
Are your imei & mac same as original? won't the imei/mac get affected by restoring someone else efs?
I don't know about mac, but imei is ok
[email protected]
thx for taking a look on my Problem
3month old note 3 no root, stock Rom, 3months no Problems,
was last week outside and i guess i was low on battery it was off as i had it in Hand
was loading all the evening and the battery is fully green
it starts, i can see mi logo, it changes to Android with loading dots at the Bottom and then it goes off
tried several times
fastboot is available
and main menu with reboot/wipe data/connect with mi assistant
i already tried:
wipe data - finished with ok (all my data gone) but still same issue
connect with mi assistant - no connecttion to Software
someone any ideas - thanks for any help
greetz
Since you already lost your data, try to flash the ROM again. I don't remember if you can transfer/flash the stock ROM without an unlocked bootloader (I suppose it is locked), if you can at least dirty install it as an update it may work too (google it). Unfortunately, providing more information over unlocking the phone is inappropriate.
GreatApo said:
try to flash the ROM again.
Click to expand...
Click to collapse
How?
GreatApo said:
I don't remember if you can transfer/flash the stock ROM without an unlocked bootloader (I suppose it is locked)
Click to expand...
Click to collapse
yes it locked
GreatApo said:
Unfortunately, providing more information over unlocking the phone is inappropriate.
Click to expand...
Click to collapse
can u pm me please?
u are the onle one who relied to my post
thanks in advance
Since your bootloader is locked, your options are limited.
To expand a little what i mentioned, your best try it may be to try and update the current from from the stock recovery. That may fix a potential corrupted partition. To do so, you can follow the steps of method 2 in this article. However, I am not aware if you can transfer the update.zip in the phone... I suppose that the stock recovery doesn't mount the phone to the PC. Thus, you probably need to try and transfer if through fastboot but that may not be possible too (could check if adb push works or if you can boot a twrp recovery, not flash just boot, but you probably wont be able)...
If you can't do the above steps, you are in a half-brick mode right now with a locked bootloader. Generally, there is no official way to get around this.