Short version: Nexus 4 is stuck on bootloop but it's as good as new with the stock ROM and everything.
Long version: My nexus 4 has stock kernel, stock ROM of Lollipop that was updated when google rolled it out few months back. I did have my bootloader unlocked via Nexus Root Toolkit few months back while i still had KitKat, but apart from that, i have NEVER ROOTED, NEVER INSTALLED A CUSTOM RECOVERY, NEVER CHANGED KERNEL, NEVER INSTALLED ANY OTHER CUSTOM ROMs. The only tampering i did was unlock the bootloader and never bothered anything else. But suddenly, my phone got stock on bootloop last night. I powered it off normally, full charged the phone, and when i turned it on, it got stuck ever since. It did happen once when the phone updated to lollipop for the first time, but a simple restart solved it that time. I have tried wiping cache, factory resetting and wiping cache again, but no luck so far.
All posts related to stuck bootloop in XDA are because of tampering the phone, installing a custom ROM, going back to stock etc. I didn't find a relevant post if this happens while still in stock with never tampered phone. If there is a post like that, please kindly redirect me there. I am left without a clue here with very less experience outside stock stuff.
PLEASE HELP !
cart00nist said:
Short version: Nexus 4 is stuck on bootloop but it's as good as new with the stock ROM and everything.
Long version: My nexus 4 has stock kernel, stock ROM of Lollipop that was updated when google rolled it out few months back. I did have my bootloader unlocked via Nexus Root Toolkit few months back while i still had KitKat, but apart from that, i have NEVER ROOTED, NEVER INSTALLED A CUSTOM RECOVERY, NEVER CHANGED KERNEL, NEVER INSTALLED ANY OTHER CUSTOM ROMs. The only tampering i did was unlock the bootloader and never bothered anything else. But suddenly, my phone got stock on bootloop last night. I powered it off normally, full charged the phone, and when i turned it on, it got stuck ever since. It did happen once when the phone updated to lollipop for the first time, but a simple restart solved it that time. I have tried wiping cache, factory resetting and wiping cache again, but no luck so far.
All posts related to stuck bootloop in XDA are because of tampering the phone, installing a custom ROM, going back to stock etc. I didn't find a relevant post if this happens while still in stock with never tampered phone. If there is a post like that, please kindly redirect me there. I am left without a clue here with very less experience outside stock stuff.
PLEASE HELP !
Click to expand...
Click to collapse
Did it just spontaneously reboot and go into a bootloop? Will it boot into the Bootloader? If so, you might try reflashing the image files directly and see if that fixes it. You can do that using Wug's NRT and selecting the Soft-Brick option under Stock + Unroot.
Hopefully that works. If not, it could be a hardware failure, but exhaust software side fixes first.
ariesgodofwar said:
Did it just spontaneously reboot and go into a bootloop? Will it boot into the Bootloader? If so, you might try reflashing the image files directly and see if that fixes it. You can do that using Wug's NRT and selecting the Soft-Brick option under Stock + Unroot.
Hopefully that works. If not, it could be a hardware failure, but exhaust software side fixes first.
Click to expand...
Click to collapse
No, i turned it off myself. Then charged the battery to 100% and then turned it back on. It got in the bootloop ever since. After u suggested, i downloaded the stock ROM and tried flashing it using Wug's NRT selecting the soft-brick option. Everything went smoothly but I am still stuck with the bootloop. If it's a hardware problem, i'm as good as screwed. There is no LG Service Center in Nepal!
cart00nist said:
No, i turned it off myself. Then charged the battery to 100% and then turned it back on. It got in the bootloop ever since. After u suggested, i downloaded the stock ROM and tried flashing it using Wug's NRT selecting the soft-brick option. Everything went smoothly but I am still stuck with the bootloop. If it's a hardware problem, i'm as good as screwed. There is no LG Service Center in Nepal!
Click to expand...
Click to collapse
How long did you wait after booting it after flashing the stock ROM? It can sometimes take a while to boot the first time.
theminikiller said:
How long did you wait after booting it after flashing the stock ROM? It can sometimes take a while to boot the first time.
Click to expand...
Click to collapse
About 10 minutes.
In another note, I don't have custom recovery or root access. But i found that i can install a custom ROm i.e. cyanogenmod using Nexus Root Toolkit. Will i run to any known problem if i do that?
cart00nist said:
About 10 minutes.
Click to expand...
Click to collapse
I would suggest you try again and wait maybe a little over half an hour to see if it boots then.
theminikiller said:
I would suggest you try again and wait maybe a little over half an hour to see if it boots then.
Click to expand...
Click to collapse
Ok, will try again.
In another note, I don't have custom recovery or root access. But i found that i can install a custom ROm i.e. cyanogenmod using Nexus Root Toolkit. Will i run to any known problem if i do that?
cart00nist said:
Ok, will try again.
In another note, I don't have custom recovery or root access. But i found that i can install a custom ROm i.e. cyanogenmod using Nexus Root Toolkit. Will i run to any known problem if i do that?
Click to expand...
Click to collapse
You shouldn't, just make sure it's for the same android version.
theminikiller said:
You shouldn't, just make sure it's for the same android version.
Click to expand...
Click to collapse
I flashed it again and It's been exactly half an hour but it's still stuck with the same four colorful dots rotating screen. Could it be because of the ROM build? I saw that there is a previous build of the same lollipop 5.1.1 in google's link.. Should i try flashing that instead?
cart00nist said:
I flashed it again and It's been exactly half an hour but it's still stuck with the same four colorful dots rotating screen. Could it be because of the ROM build? I saw that there is a previous build of the same lollipop 5.1.1 in google's link.. Should i try flashing that instead?
Click to expand...
Click to collapse
You could, you could also try flashing a custom recovery and then installing a custom ROM to see if that helps.
theminikiller said:
You could, you could also try flashing a custom recovery and then installing a custom ROM to see if that helps.
Click to expand...
Click to collapse
How do i flash a custom recovery from fastboot mode? Since i cannot go to the homescreen and turn on USB debugging, i cannot root the device. The NRT only has root+custom recovery together in a single button. Since i only need the custom revovery and that also i need to install it by staying in the fastboot mode, how do i do it? This is the only phone i have and i cannot afford another phone anytime soon. Thankyou so so much for helping me
cart00nist said:
How do i flash a custom recovery from fastboot mode? Since i cannot go to the homescreen and turn on USB debugging, i cannot root the device. The NRT only has root+custom recovery together in a single button. Since i only need the custom revovery and that also i need to install it by staying in the fastboot mode, how do i do it? This is the only phone i have and i cannot afford another phone anytime soon. Thankyou so so much for helping me
Click to expand...
Click to collapse
Try following this guide: http://forum.xda-developers.com/showthread.php?t=2018179
Your bootloader is already unlocked so you can ignore that part of the guide. Follow the instructions to install adb and fastboot. Then instead of using adb commands to boot into the bootloader do it by first powering off your phone, then power it on while holding the volume down button.
When you are there follow the instructions to flash a recovery image, but instead of using CWM as is suggested there use TWRP instead from this link: http://forum.xda-developers.com/showthread.php?t=2002326 there will be a link in the post to their webpage where you can download the image file. The reason I recommend TWRP over CWM is that CWM is discontinued and haven't been updated in a while.
Then use the same command as in the guide to flash the recovery image, just use the TWRP image file instead. You can ignore the root part since custom Rom's come pre-rooted. Then to flash a custom ROM follow the guide to boot into recovery. Once there you should be able to copy files from your computer and to your phone.
To then install a custom ROM find a ROM you want to try, some stable ones right now are XenonHD and Chroma. Download the zip file from their thread, download a GApps package. There is usually a link to one in the ROM threads. Then copy those two files to your phone.
Then in recovery choose to do a factory reset. Then choose to install first the ROM zip and then the GApps zip, and then wipe cache. You should then try to boot it up normally.
Let's hope that works, but ask if something is unclear. ☺
theminikiller said:
Try following this guide: http://forum.xda-developers.com/showthread.php?t=2018179
Your bootloader is already unlocked so you can ignore that part of the guide. Follow the instructions to install adb and fastboot. Then instead of using adb commands to boot into the bootloader do it by first powering off your phone, then power it on while holding the volume down button.
When you are there follow the instructions to flash a recovery image, but instead of using CWM as is suggested there use TWRP instead from this link: http://forum.xda-developers.com/showthread.php?t=2002326 there will be a link in the post to their webpage where you can download the image file. The reason I recommend TWRP over CWM is that CWM is discontinued and haven't been updated in a while.
Then use the same command as in the guide to flash the recovery image, just use the TWRP image file instead. You can ignore the root part since custom Rom's come pre-rooted. Then to flash a custom ROM follow the guide to boot into recovery. Once there you should be able to copy files from your computer and to your phone.
To then install a custom ROM find a ROM you want to try, some stable ones right now are XenonHD and Chroma. Download the zip file from their thread, download a GApps package. There is usually a link to one in the ROM threads. Then copy those two files to your phone.
Then in recovery choose to do a factory reset. Then choose to install first the ROM zip and then the GApps zip, and then wipe cache. You should then try to boot it up normally.
Let's hope that works, but ask if something is unclear.
Click to expand...
Click to collapse
Installed TWRP, and then installed XenonHD. Everything went ultra smooth. Again got stuck in the same boot screen. Tried factory reset, doesn't work! I'm screwed!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
cart00nist said:
Installed TWRP, and then installed XenonHD. Everything went ultra smooth. Again got stuck in the same boot screen. Tried factory reset, doesn't work! I'm screwed!
Click to expand...
Click to collapse
I'm afraid that the only suggestion I have left is to try flashing a factory image manually instead of using the toolkit. This is a guide on how to do it: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
theminikiller said:
I'm afraid that the only suggestion I have left is to try flashing a factory image manually instead of using the toolkit. This is a guide on how to do it: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
Click to expand...
Click to collapse
Haha. I was out for a while and my stupid brother flashed a Droid ROM of about 900MB. I don't know what he was thinking. I cannot even scold him because he his my cousin. lol
Now the phone doesn't even turn on. It probably is on because when i connect it to the PC, the new hardware is detected and the driver is also probably installed, because the windows doesn't say the driver installation was failed. But i cannot see anything on the screen. I am about to throw my phone in the trashcan. lol I feel so stupid. Do you have any last suggestion for me?
cart00nist said:
Haha. I was out for a while and my stupid brother flashed a Droid ROM of about 900MB. I don't know what he was thinking. I cannot even scold him because he his my cousin. lol
Now the phone doesn't even turn on. It probably is on because when i connect it to the PC, the new hardware is detected and the driver is also probably installed, because the windows doesn't say the driver installation was failed. But i cannot see anything on the screen. I am about to throw my phone in the trashcan. lol I feel so stupid. Do you have any last suggestion for me?
Click to expand...
Click to collapse
Do you get any feedback if you use the command "fastboot devices"?
theminikiller said:
Do you get any feedback if you use the command "fastboot devices"?
Click to expand...
Click to collapse
Oh rite i forgot to tell you. i did fastboot devices and so far it doesn't show up the serial number of my phone.
cart00nist said:
Oh rite i forgot to tell you. i did fastboot devices and so far it doesn't show up the serial number of my phone.
Click to expand...
Click to collapse
In that case I unfortunately don't have any more ideas, sorry. I wish you luck with your phone tho, maybe some other member here at xda has any other ideas.
Related
Hi,
Last night i was playing with my N4 (with some root applications) and an app asked for a reboot. I just pressed yes so that the phone will reboot (I have done this earlier without any issues). Suddenly the device doesn't boot up. My N4 is stuck at a black screen. While trying to boot up, the Google logo appears and then a black screen. It doesn't advance to the 'X' logo. I'm running on stock, rooted phone (used N4 toolkit by Wugfresh to root).
I'm able to boot into recovery although. I tried all the possible means, wiped cache, dalvik cache, did a factory reset, backed up the system and tried to restore the same. Nothing happened.
Then i tried the "Back to Stock" option in the N4 toolkit and chose the option "Soft-brick/Bootloop" to recover my N4. These are what happened:
Downloaded the 4.2.2 image from Google servers and tried to flash in the device with prior instruction from the toolkit. Everything went fine until the flashing process. In the last step the CMD window opens up saying it is unrooting and flashing stock and immediately it'll bring up a complete message saying the flashing is complete and to wait until the device boots up. But nothing happens again.
I tried the automatic flashing and on the downloading window it saying download failed and hash checks failed meaning its not downloading.
I searched all the possible threads in a day to find a similar problem but in vain. I'm not a noob but i'm too lazy . But i would do anything to bring my N4 back to life. Anyone please show me a direction.
In short:
Status: Soft-Bricked (guess so), black screen after Google logo
Version: Stock 4.2.2 (rooted+busybox+supersu+twrp)
Able to boot to recovering: Yes, bootable to recovery and bootloader.
Tried Nexus toolkit recovery: Yes but in vain.
Gave up: No and never, I'm searching and searching for answers and I'm worried if I'll end up in a hard brick. :crying:
Guys, please help.
Thank You!
Aghil
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
ameinild said:
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
Click to expand...
Click to collapse
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
aghilvr said:
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Click to expand...
Click to collapse
No, my suggestion would require that the ROM is still on the phone, so you should restore your ROM prior to my suggestion. And I'm by no means an expert (therefore the disclaimer), but I *think* that since it's a bootup problem, it could be solved by flashing a new boot.img (which is essentially flashing a new kernel to the system).
But yeah, let's see if others think this might help, haven't researched it, is at work right now. Just throwing in a suggestion, that's all...
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
I *think* (again, I'm totally not sure about this, as I haven't tried it) that you can sideload a ROM via zip file from recovery, but since I haven't tried it I'm not sure - can anybody confirm???
EDIT: Chromium's suggestion is better, by pushing the ROM.zip to the device and flashing from recovery (check md5 first, just in case).
aghilvr said:
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
Yes there is. Your nexus is not bricked and this is why you shouldnt use toolkits to do things. This is honestly an extremely easy and simple fix. Use adb to push a rom onto the n4.
Code:
adb push \path\to\rom.zip /sdcard
Boot into recovery, do a full wipe, and flash the rom.
You said you downloaded the Google images.
Just boot your phone into the bootloader and run the flashall.bat that is in the Google image folder.
Note this will probably fully wipe you're phone in the process
Sent from my Nexus 4 using xda app-developers app
try this it may help u this toolkit is damn easy to use :
http://forum.xda-developers.com/showthread.php?t=1995688
Okay, thanks guys. I'm on it. Will let you know when I'm done.
That same thing happened to me once. I had to extract the google file and look for the 4 img files(bootloader, system, userdata, recovery) and flash them with toolkit manually and it fixed it, but it erased everything on my sd
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
aghilvr said:
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
Click to expand...
Click to collapse
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
chromium96 said:
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
Click to expand...
Click to collapse
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
aghilvr said:
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
chromium96 said:
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
Click to expand...
Click to collapse
Oh that's why it didn't work all the time
Thanks chromium :fingers-crossed:
Hey thanks guys, my device is back to normal. Chromium a special thanks for you for helping me out. See you guys with my next problem/queris!
Hello everyone,
today I rooted + bootloader unlocked my N4 with Towelroot and after that I installed Multirom because I wanted to try the Android L developer Preview.
After realizing that a rooted device with a custom recovery won't get official OTA updated anymore I want to have my stock N4 back
I did not install any rom.
Is there a way I can get my stock recovery back WITHOUT having to set up my device again?
I mean, only the recovery should have changed.
I have a mac and a Win XP PC for any tools. I am running stock Android 4.4.4 and kernel 3.4.0-perf-ga6edd5e
Very thankful for any help
If all you need to do is get the stock recovery back you can do that in fastboot. The factory image includes recovery.img. Flash that
fastboot flash recovery recovery.img
Sent from my Nexus 5 using XDA Free mobile app
will this bring me back the ability to get OTA updates?
If so.. is there a tutorial or anything like that I can follow? I have not worked with ADB and fastboot before but thanks a lot for your quick answer!
unrealmac said:
will this bring me back the ability to get OTA updates?
If so.. is there a tutorial or anything like that I can follow? I have not worked with ADB and fastboot before but thanks a lot for your quick answer!
Click to expand...
Click to collapse
It's easy to do. First Google 15 second adb install xda. That'll set up fastboot on your pc. Then Google nexus 4 factory image. Download that and then extract it using winrar or 7-zip. In there you'll find a zip file. Extract that too and you'll find recovery.img.
Boot your device into the bootloader and then in a command prompt opened in the same directory as recovery.img is located run the commands I gave you earlier. You'll then have the stock recovery on your device.
Sent from my Nexus 5 using XDA Free mobile app
I do not find a second archive in there.
Could it be that the recovery.img is also called 'boot.img' ?
unrealmac said:
I do not find a second archive in there.
Could it be that the recovery.img is also called 'boot.img' ?
Click to expand...
Click to collapse
no. Boot.img is the kernel. There should be a zip file in there. In there is recovery.img
Edit, out should be called image- something or other
Edit, edit. If you found boot.img, recovery should be in the same directory as it
Sent from my Nexus 5 using XDA Free mobile app
Thanks again for your fast help.
Okay I found the recovery.img
just to be sure: this will not any of my data/apps on the phone, right?
If so I think I am ready to proceed
unrealmac said:
Thanks again for your fast help.
Okay I found the recovery.img
just to be sure: this will not any of my data/apps on the phone, right?
If so I think I am ready to proceed
Click to expand...
Click to collapse
It won't delete any data
Sent from my Nexus 5 using XDA Free mobile app
I tried it several times with fastboot on mac (the 15 sec installer on Win XP did not work) but everytime I open fastboot I am not able to type anything in.
In the last row of the screenshot it says something like "process closed"
Is the any other tool I can use for that?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
unrealmac said:
I tried it several times with fastboot on mac (the 15 sec installer on Win XP did not work) but everytime I open fastboot I am not able to type anything in.
In the last row of the screenshot it says something like "process closed"
Is the any other tool I can use for that?
Click to expand...
Click to collapse
I'm not familiar with the Mac, but another alternative is to do it from your phone. Get flashify from the play store and flash the recovery.img in it. Just copy recovery.img to your phone
Sent from my Nexus 5 using XDA Free mobile app
Ha! This worked instantly. After pressing "reboot now" it tried to reboot but a screen with "no service" appeared.
After rebooting the device manually everything booted normally.
Is there Any way I can now check if I now have the "stock recovery" again?
What are the criteria to get official OTA updates again from Google?
Thanks so much!
unrealmac said:
Ha! This worked instantly. After pressing "reboot now" it tried to reboot but a screen with "no service" appeared.
After rebooting the device manually everything booted normally.
Is there Any way I can now check if I now have the "stock recovery" again?
What are the criteria to get official OTA updates again from Google?
Thanks so much!
Click to expand...
Click to collapse
To check just boot into the bootloader and go to recovery. The stock recovery should be there.
To get the ota you can not have any modified or deleted system files.
Sent from my Nexus 5 using XDA Free mobile app
Mmh the stock recovery is the Android lying on the back, correct?
So If I have the stock recovery+no rom installed I should get updates, correct?
Root and an open bootloader has no effects to it?
unrealmac said:
Mmh the stock recovery is the Android lying on the back, correct?
So If I have the stock recovery+no rom installed I should get updates, correct?
Root and an open bootloader has no effects to it?
Click to expand...
Click to collapse
You are correct. You will lose root when you get the ota
Sent from my Nexus 5 using XDA Free mobile app
Thank you very much.
I think in the past 24 hours I have learnt more than I have reading in the forums silently.
You have really helped someone very desperate
unrealmac said:
Thank you very much.
I think in the past 24 hours I have learnt more than I have reading in the forums silently.
You have really helped someone very desperate
Click to expand...
Click to collapse
Glad i could help
Sent from my Nexus 5 using XDA Free mobile app
Hello @jd1639
I was just trying to sideload the lollypop OTA file via fastbootand I does not install correctly. There is always an error.
Could this have anything to do with the root access and the unlocked bootloader?
I think I read somewhere something like rooted devices will get the OTA update but will not be able to install them correctly.
Is there a way to get that to work without erasing my data?
unrealmac said:
Hello @jd1639
I was just trying to sideload the lollypop OTA file via fastbootand I does not install correctly. There is always an error.
Could this have anything to do with the root access and the unlocked bootloader?
I think I read somewhere something like rooted devices will get the OTA update but will not be able to install them correctly.
Is there a way to get that to work without erasing my data?
Click to expand...
Click to collapse
Are you flashing it in the stock recovery? If not flash the stock recovery in fastboot and try it again. To use adb sideload you need to be booted into recovery not fastboot
Sent from my Nexus 5 using XDA Free mobile app
Yeah I did that.
I got everything stock but have been flashing the recovery back to stock (like I described in the thread).
Getting something like a "status 7" error.
I am booted into recovery mode. The sending process works and then it tries to install the update on my phone and then the installation process stops..
unrealmac said:
Yeah I did that.
I got everything stock but have been flashing the recovery back to stock (like I described in the thread).
Getting something like a "status 7" error.
I am booted into recovery mode. The sending process works and then it tries to install the update on my phone and then the installation process stops..
Click to expand...
Click to collapse
I got that status 7 error myself. I fastboot flashed recovery, system, boot, and cache from 4.4.4. It won't wipe anything. Then the sideload worked
Sent from my Nexus 5 using XDA Free mobile app
I've had my Moto X Pure for over a few months now. After rooting it, i installed TWRP 3.0.2 and have had different roms and not come across any problems regarding a hard brick. I was using my phone on the CM 13 Rom, and it was bugging out, so i tried to reboot. After trying to reboot, it would come to the WARNING BOOTLOADER UNLOCKED SCREEN and not boot past that, let alone get into the actual loading screen. Now, i cant boot into twrp. When i try to enter recovery mode, it goes to the TWRP screen, and sits there without proceeding. I cant boot the phone, or boot into recovery. I can only boot into the bootloader. ANY AND EVERY ADVICE IS APPRECIATED THANK YOU!!!
Edit: I fixed it. had to manually extract and reflash some files from a very useful restore to stock tool.
http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905
Thank you for all of the help so quickly.
kagarii said:
I've had my Moto X Pure for over a few months now. After rooting it, i installed TWRP 3.0.2 and have had different roms and not come across any problems regarding a hard brick. I was using my phone on the CM 13 Rom, and it was bugging out, so i tried to reboot. After trying to reboot, it would come to the WARNING BOOTLOADER UNLOCKED SCREEN and not boot past that, let alone get into the actual loading screen. Now, i cant boot into twrp. When i try to enter recovery mode, it goes to the TWRP screen, and sits there without proceeding. I cant boot the phone, or boot into recovery. I can only boot into the bootloader. ANY AND EVERY ADVICE IS APPRECIATED THANK YOU!!!
Click to expand...
Click to collapse
If your able to boot into bootloader you can try to reflashTWRP or flash the original recovery and the original system files.
kagarii said:
I've had my Moto X Pure for over a few months now. After rooting it, i installed TWRP 3.0.2 and have had different roms and not come across any problems regarding a hard brick. I was using my phone on the CM 13 Rom, and it was bugging out, so i tried to reboot. After trying to reboot, it would come to the WARNING BOOTLOADER UNLOCKED SCREEN and not boot past that, let alone get into the actual loading screen. Now, i cant boot into twrp. When i try to enter recovery mode, it goes to the TWRP screen, and sits there without proceeding. I cant boot the phone, or boot into recovery. I can only boot into the bootloader. ANY AND EVERY ADVICE IS APPRECIATED THANK YOU!!!
Click to expand...
Click to collapse
Can you get it into fastboot mode? If you can, it sounds like somehow the recovery is corrupt and you would need to use 'fastboot erase recovery' first, and then 'fastboot flash recovery recovery.img' (using the twrp .img flashable file of course)
I hope that does the trick. Only think I can think of other than that is look for the automated return to stock tool for the moto x 2015 and use that.
thanks
[email protected] said:
If your able to boot into bootloader you can try to reflashTWRP or flash the original recovery and the original system files.
Click to expand...
Click to collapse
fixed it thank you!
thanks
benjmiester said:
Can you get it into fastboot mode? If you can, it sounds like somehow the recovery is corrupt and you would need to use 'fastboot erase recovery' first, and then 'fastboot flash recovery recovery.img' (using the twrp .img flashable file of course)
I hope that does the trick. Only think I can think of other than that is look for the automated return to stock tool for the moto x 2015 and use that.
Click to expand...
Click to collapse
fixed it thank you!
kagarii said:
fixed it thank you!
Click to expand...
Click to collapse
Great news! You're very welcome. I was in that exact same situation with my old Xperia Z2. It's pretty scary.
kagarii said:
fixed it thank you!
Click to expand...
Click to collapse
Can you tell us what fixed it? Do you know if it was firmware related? Was it the recovery? I have multiple people on this device all on custom software, always interested to find the cause of these types of issues for future reference. And most importantly, glad you got it resolved!
Sent from my XT1575 using Tapatalk
DonKilluminati23 said:
Can you tell us what fixed it? Do you know if it was firmware related? Was it the recovery? I have multiple people on this device all on custom software, always interested to find the cause of these types of issues for future reference. And most importantly, glad you got it resolved!
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
I honestly have no idea what the problem was. But i downloaded and used someones lollipop restore to stock tool, literally restoring to the original state you got the phone in, and it worked. I believe it had something to do with the rom, and possibly some xposed modules i had installed, but there was nothing that actually messed around with the phone's system files. I couldn't access recovery in anyway whatsoever, but my advice to you is that if you ever need help because the phone is potentially hard-bricked, see if it connects to PC and if it does use the restore to stock tool.
kagarii said:
I honestly have no idea what the problem was. But i downloaded and used someones lollipop restore to stock tool, literally restoring to the original state you got the phone in, and it worked. I believe it had something to do with the rom, and possibly some xposed modules i had installed, but there was nothing that actually messed around with the phone's system files. I couldn't access recovery in anyway whatsoever, but my advice to you is that if you ever need help because the phone is potentially hard-bricked, see if it connects to PC and if it does use the restore to stock tool.
Click to expand...
Click to collapse
Were you on marshmallow before you used the restore to stock tool? I thought downgrading android versions was a no-no currently.
jDally987 said:
Were you on marshmallow before you used the restore to stock tool? I thought downgrading android versions was a no-no currently.
Click to expand...
Click to collapse
It's possible, through tools like this. I don't know too much of the topic.
jDally987 said:
Were you on marshmallow before you used the restore to stock tool? I thought downgrading android versions was a no-no currently.
Click to expand...
Click to collapse
Mine wouldnt let me factory reset in twrp to flash something else while on cr droid it jist vibrates now it wont even boot into cr droid ive try to flash another rom but nothing since recovery suddenly wont let me wipe. Any advice on whats causing this i have a 64 gb adopted sd catd also i think i accidently repartitioned sd card in twrp.
Sherrillface said:
Mine wouldnt let me factory reset in twrp to flash something else while on cr droid it jist vibrates now it wont even boot into cr droid ive try to flash another rom but nothing since recovery suddenly wont let me wipe. Any advice on whats causing this i have a 64 gb adopted sd catd also i think i accidently repartitioned sd card in twrp.
Click to expand...
Click to collapse
Old thread. But can you at least get into TWRP recovery? Why won't it let you wipe? Like what does it say?
jDally987 said:
Old thread. But can you at least get into TWRP recovery? Why won't it let you wipe? Like what does it say?
Click to expand...
Click to collapse
Nothing it just vibrates as soon as i hit factory reset then bootloops now it wont even go into recovery just fastboot screen but cant get fastboot to work at all and have all drivers android studio etc. Nothing will work need a new solution
It was hash kernel it corrupted all 64 gigs of storage and music etc. Had to return to stock via auto flash firmware.
Mine is XT1572 device. Since the mentioned tool was not available for this model, I took the chance with XT1575 tool. It did all the steps but the issue has become worse. Now, my device is automatically getting On and OFF in seconds and does not boot beyond the bootloader 'unlocked' warning screen. Please please please help !!!!
Hey folks! I am on a T-Mobile Galaxy Note 3, running a S7 Edge port by Dominion. And of course, Pokemon GO 0.37 is throwing the stupid compatibility error message.
Now, before you suggest it, I am already aware of the Magisk solution for rooted phones. In fact I used that exact method to get the app to work on my wife's rooted Note 4.
However, there seems to be more going on with Pokemon GO this ROM than just the root. I was able to unroot this ROM and get Magisk running. The root was fully toggleable, and when root is off, all apps that require root could not get access. So I know Magisk is working properly. However, Pokemon GO still wouldn't run, and when I ran a check for SafetyNet, my phone failed to pass the last check with the error "CTS Profile Mismatch".
I already checked the system/bin and /xbin for leftover SU files, too, and there's nothing there. Now I do know this ROM comes pre-rooted and it has a permissive kernel that checks for root status (TWRP prompts me to install SuperSU whenever I boot into it). I am guessing that may have something to do with it, but... what can I do about it?
anything modifying the system will prompt the safety net to not work viper4android, xposed, ect. you need to remove them. if you do need xposed there is a systemless 84.5 (cant remember exact verison) google it if that's the case also a update-unSU.zip can be flashed and that in my experience does fully un-root
I'm running it well with phh-su (recommended with magisk) coming from superSU its not that bad/different
and the systemless xposed (flash xposed uninstaller) then system-less xposed and for other system dependent tweaks try to find system-less versions
Dr_DjEnder said:
anything modifying the system will prompt the safety net to not work viper4android, xposed, ect. you need to remove them. if you do need xposed there is a systemless 84.5 (cant remember exact verison) google it if that's the case also a update-unSU.zip can be flashed and that in my experience does fully un-root
I'm running it well with phh-su (recommended with magisk) coming from superSU its not that bad/different
and the systemless xposed (flash xposed uninstaller) then system-less xposed and for other system dependent tweaks try to find system-less versions
Click to expand...
Click to collapse
If I may ask, how did you run Uninstaller for supersu? I followed the instructions and others posts on the Magisk thread. But to no avail. I was able to update to jasmine and unlock the bootloader, coming from biggins. But cannot go further than that. Pokémon worked for me on Biggins with no extra root hide or work up until latest update.
nIkbot said:
If I may ask, how did you run Uninstaller for supersu? I followed the instructions and others posts on the Magisk thread. But to no avail. I was able to update to jasmine and unlock the bootloader, coming from biggins. But cannot go further than that. Pokémon worked for me on Biggins with no extra root hide or work up until latest update.
Click to expand...
Click to collapse
No idea what this biggins is (a rom possibly) but I can help with the uninstall I used a update-unSU.zip just flashed in recovery I'm using the latest twrp 3.?.?.? (idk what it is exactly) but should work on anything worked on both my Oneplus 2 (daily driver) and my note 3 (backup/test phone) so it should work I ran pokemans on both using magisk and systemless root. heres the zip
Dr_DjEnder said:
No idea what this biggins is (a rom possibly) but I can help with the uninstall I used a update-unSU.zip just flashed in recovery I'm using the latest twrp 3.?.?.? (idk what it is exactly) but should work on anything worked on both my Oneplus 2 (daily driver) and my note 3 (backup/test phone) so it should work I ran pokemans on both using magisk and systemless root. heres the zip
Click to expand...
Click to collapse
Thank you for the response!
So the path to try is.
Boot to TWRP (3.0.2-0 installed)
Flash UPDATE-unSU.zip
Flash xposed-uninstaller-20160829-arm64.zip
Flash Magisk-v6.zip
Flash phh-superuser-17-magisk.zip
Boot up. Install Magisk manager v1.2
Reboot
Flash xposed-v86.5-skd23-topjohnwu.zip
This seem like the correct course of action?
nIkbot said:
Thank you for the response!
So the path to try is.
Boot to TWRP (3.0.2-0 installed)
Flash UPDATE-unSU.zip
Flash xposed-uninstaller-20160829-arm64.zip
Flash Magisk-v6.zip
Flash phh-superuser-17-magisk.zip
Boot up. Install Magisk manager v1.2
Reboot
Flash xposed-v86.5-skd23-topjohnwu.zip
This seem like the correct course of action?
Click to expand...
Click to collapse
Yes it seem right however..
I flash the xposed with the Magick and uperuser ect and haven't had any problems.... Yet...? Idk if it can depends on use case may save you a reboot idk
Dr_DjEnder said:
Yes it seem right however..
I flash the xposed with the Magick and uperuser ect and haven't had any problems.... Yet...? Idk if it can depends on use case may save you a reboot idk
Click to expand...
Click to collapse
Don't bother letting it reboot and installing the manager? Just flash the xposed.zip before hand worked for you?
nIkbot said:
Don't bother letting it reboot and installing the manager? Just flash the xposed.zip before hand worked for you?
Click to expand...
Click to collapse
After fresh install of rom, immediate unroot with supersu. It gets uninstalled and reboot automatically.
Flash magisk.zip, phh superuser.zip and xposed.zip.
Then install magisk.apk & xposed.apk.
Install phhsupersu from playstore.
Works for me.
Sent from my SM-G925F
Rosli59564 said:
After fresh install of rom, immediate unroot with supersu. It gets uninstalled and reboot automatically.
Flash magisk.zip, phh superuser.zip and xposed.zip.
Then install magisk.apk & xposed.apk.
Install phhsupersu from playstore.
Works for me.
Click to expand...
Click to collapse
Just tested yes that works fine so yeah save yourself the reboots.
(1)Hmm. Gave this a go. All the zips flash except the last one. The xposed-v86.5-sdk23-topjohnwu.zip fails for version support... Try to reboot and get stuck on logo... Rebooted to TWRP wiped reflashed jas and odin'd partial firm and back to square 1 again.
(2)Tried again with the v86.5 sdk21 and it flashed. Go to reboot and in top left screen says.
> Kernal is not SEANDROID enforcing
> set warranty bit : kernal
Then stuck at boot logo looping.
No clue on what's hanging up on this.
(3) Back to twrp, factoryreset, jas,partial, firmwar, twrp again. Square 1 again.
nIkbot said:
Hmm. Gave this a go. All the zips flash except the last one. The xposed-v86.5-sdk23-topjohnwu.zip fails for version support... Try to reboot and get stuck on logo... Rebooted to TWRP wiped reflashed jas and odin'd partial firm and back to square 1 again.
Click to expand...
Click to collapse
The rom is mm?.
And the first time when you're uninstalling supersu, you would be asked to return to stock boot image or something. Choose no.
Sent from my SM-G925F
Rosli59564 said:
The rom is mm?.
And the first time when you're uninstalling supersu, you would be asked to return to stock boot image or something. Choose no.
Sent from my SM-G925F
Click to expand...
Click to collapse
Running the latest Jasmine rom. http://forum.xda-developers.com/showthread.php?t=2760380
Running the SuperSU app and selecting, "full unroot" only prompts a warning with cancel/ok. The next screen is uninstalling and it has hung up there... Thinking this rom is not playing nice with the process or I have something out of place..
(2) WHoooo boy... :/ After doing it that way through the app and having to start over. I cant flash the TWRP zip i've been using each time to get recovery on... Get "Non official verizon sofware" error screen. have to odin the partial firm to get it to boot again...
nIkbot said:
Running the latest Jasmine rom. http://forum.xda-developers.com/showthread.php?t=2760380
Running the SuperSU app and selecting, "full unroot" only prompts a warning with cancel/ok. The next screen is uninstalling and it has hung up there... Thinking this rom is not playing nice with the process or I have something out of place..
(2) WHoooo boy... :/ After doing it that way through the app and having to start over. I cant flash the TWRP zip i've been using each time to get recovery on... Get "Non official verizon sofware" error screen. have to odin the partial firm to get it to boot again...
Click to expand...
Click to collapse
About the unrooting, probably you could choose ok.
The xposed should be sdk21 as the rom is android 5.0.
Sent from my SM-G925F
Never got prompted for an OK on the unroot. It just said the warning prompt then went to uninstalling animation which didn't end. Now I can't flash twrp.zip. so no custom recovery.
nIkbot said:
Never got prompted for an OK on the unroot. It just said the warning prompt then went to uninstalling animation which didn't end. Now I can't flash twrp.zip. so no custom recovery.
Click to expand...
Click to collapse
Sorry to hear that. I thought verizon has already unlock note 3 bootloader. Why it should prompt unathorized software thing?.
Probably no systemless for the rom you're using. The rom you mentioned is way too outdated. Understandable as it's got locked earlier.
Perhaps you could try with clean install 1 more time. Just make sure the xposed version is correct. But I believe the old rom isn't using systemless supersu either, so perhaps that's 1 of the issue. Just few months ago chainfire came up with systemless root.
I personally don't know the different though.
Sent from my SM-G925F
Rosli59564 said:
Sorry to hear that. I thought verizon has already unlock note 3 bootloader. Why it should prompt unathorized software thing?.
Probably no systemless for the rom you're using. The rom you mentioned is way too outdated. Understandable as it's got locked earlier.
Perhaps you could try with clean install 1 more time. Just make sure the xposed version is correct. But I believe the old rom isn't using systemless supersu either, so perhaps that's 1 of the issue. Just few months ago chainfire came up with systemless root.
I personally don't know the different though.
Sent from my SM-G925F
Click to expand...
Click to collapse
Before trying magisk the first time yesterdat i was able to ollow the unlock thread and on the Odin download screen it says I have it unlocked to dev edition so I'm quite confused on that as well..
Should just boot to normal recovery and try to do the factory reset/reflash jasmine one last time?
nIkbot said:
Before trying magisk the first time yesterdat i was able to ollow the unlock thread and on the Odin download screen it says I have it unlocked to dev edition so I'm quite confused on that as well..
Should just boot to normal recovery and try to do the factory reset/reflash jasmine one last time?
Click to expand...
Click to collapse
Probably you can try again. Have you asked in verizon note 3 section and in the rom thread if anybody successfully run magisk on their phones?.
Sent from my SM-G925F
Rosli59564 said:
Probably you can try again. Have you asked in verizon note 3 section and in the rom thread if anybody successfully run magisk on their phones?.
Sent from my SM-G925F
Click to expand...
Click to collapse
Yeah, I posted to the jasmine thread.
Geeze. Running from stock recovery made things worse for a bit. Odin'd back to partial. Had to Re-run bootloader unlock process to get TWRP installed correctly and working again.
Thats working again and fine, download screen says Developer mode again.
One thing out of place now is the xposed app shows the "custom version 71 build is active" with no clickable options now. Running the uninstallers from TWRP does not clear and posts errors...
Another full stop. Really scratching my head on this one
Wondering at this point if it's less trouble to flash a different rom... I haven't been up to speed in a long time with them and thought that coming from Biggins4.4.2 to Jasmine 5.0 was a massive jump.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
nIkbot said:
Yeah, I posted to the jasmine thread.
Geeze. Running from stock recovery made things worse for a bit. Odin'd back to partial. Had to Re-run bootloader unlock process to get TWRP installed correctly and working again.
Thats working again and fine, download screen says Developer mode again.
One thing out of place now is the xposed app shows the "custom version 71 build is active" with no clickable options now. Running the uninstallers from TWRP does not clear and posts errors...
Another full stop. Really scratching my head on this one
Wondering at this point if it's less trouble to flash a different rom... I haven't been up to speed in a long time with them and thought that coming from Biggins4.4.2 to Jasmine 5.0 was a massive jump.
Click to expand...
Click to collapse
The xposed is normal since 5.0. You can't click anywhere except reboot and doft reboot. But it isn't systemless xposed.
It's ok unless you're trying to get systemless xposed to work.
Sent from my SM-G925F
Rosli59564 said:
The xposed is normal since 5.0. You can't click anywhere except reboot and doft reboot. But it isn't systemless xposed.
It's ok unless you're trying to get systemless xposed to work.
Sent from my SM-G925F
Click to expand...
Click to collapse
Neat. Then I'm back to square one. Everything where it should be again at least.
Have to dig around some more and see if there is a more friendly base rom I can work with to get this accomplished. Thanks for the help Rosli!
Hello, I was trying to root my phone last night, I unlocked the boot loader that worked perfectly, easy. Nothing else went well, I was fighting with it TWRP for hours and then Magisk wouldn't install. I gave up on that and tried SuperSu... now the phone just stays on the loading screen instead of booting, It won't boot into recovery either just fastboot. Can it be fixed?
Your phone is soft bricked and can only boot to bootloader, correct?
The only solution is flashing the stock ROM of the device. You can get your device (Tissot) stock ROM from here.
I just got it to boot into TWRP, after it cycled a few times.
Well that may make it easier, you can try wiping dalvik cache then wiping data and see if that works. Needless to say wiping data is going to delete all your personal data, but since you're in TWRP recovery you can back it up.
Wiping it didn't work, I'm trying to use MiFlash I have downloaded "Tissot_9.0_V10.0.10.0.PDHMIXM_Fastboot" my phone is in fastboot. MiFlash detects it but when I try to flash I just get "can not found file flash_all_lock.bat"
How do you tell is MiFlash has successfully installed drivers, it gives me a window in Chinese?
If it's not working - I never thought it would anyway - then your only option is to flash stock ROM.
You can try using fastboot commands through cmd window, if it returns <waiting for device> or something similar then the driver isn't installed properly. Alternatively you can install the driver from here.
Thanks, it detects my phone. How would you recommend flashing the stock ROM? Do I need to use the same version the phone was running before?
galaxymini1 said:
Thanks, it detects my phone. How would you recommend flashing the stock ROM? Do I need to use the same version the phone was running before?
Click to expand...
Click to collapse
You can use any version as long as it is meant for your device. Flashing the latest version might be best option.
Happy to help.
I tried flashing it with TWRP but just got "no digest file found" I'll try again tomorrow.
This must be the most annoying thing I've done with electronics in years, nothing wants to work.
galaxymini1 said:
I tried flashing it with TWRP but just got "no digest file found" I'll try again tomorrow.
This must be the most annoying thing I've done with electronics in years, nothing wants to work.
Click to expand...
Click to collapse
Lemme guess, you have TWRP v3.2.2-0? Try flashing the latest version from here.
XDHx86 said:
Lemme guess, you have TWRP v3.2.2-0? Try flashing the latest version from here.
Click to expand...
Click to collapse
v3.2.1 anyway it's gone now, I got it booting with the guide on https://xiaomifirmware.com/roms/download-official-roms-xiaomi-mi-a1/
probably the best written one I've found.
Now to try and root it again...
galaxymini1 said:
v3.2.1 anyway it's gone now, I got it booting with the guide on https://xiaomifirmware.com/roms/download-official-roms-xiaomi-mi-a1/
probably the best written one I've found.
Now to try and root it again...
Click to expand...
Click to collapse
You can find that in an XDA revised article here.
I got TWRP and Magisk installed no problem. I don't know if I was just tired or it was the crap guides but nothing wanted to cooperate on my first attempt.
Thanks for all the help.