Related
I got myself into trouble and I hope that someone who knows more than me can answer two questions.
Background:
I bought a new Nexus 7 2013 WIFI (razor / flo). I loaded TWRP recovery, and rooted the device. I decided to encrypt the drive, but TWRP doesn't appear able to do that (when the device reboots to start encryption, it just boots normally into Android). However it does appear that TWRP can mount an encrypted drive, so I decided to flash stock recovery to do the encryption and then reflash with TWRP.
Problem 1:
I accidentally flashed with the wrong stock image. I used the image for the Nexus 7 2013 Mobile (razorg / deb). The flash-all.sh script includes a step for flashing the radio (fastboot flash radio radio-deb-deb-g00_2.37.0_1024.img). It executed the command without error, but I don't think there is a radio partition on this device. Does anyone know if there is a radio partition to control the GPS, WIFI, and/or NFC? Should I do something to undo this problem? I cannot find a radio firmware for this device, and the WIFI and GPS appear to work fine so perhaps I should just move on.
Problem 2:
Even when I use the stock recovery image for the correct device, it does not appear to load correctly. fastboot runs without errors, but when I boot into recovery I get the unconscious android with the red exclamation in his tummy. I have done a full wipe of all partitions, and a full restore. Based on my search in the forums, this appears to be a common problem but the suggested solutions don't seem to apply to my device. Any suggestions?
I should note that re-installing TRWP works fine, and I was able to restore my data from a backup. But I can't encrypt the device or install future updates until I can roll back to the stock restore image.
Thank you in advance for your help.
resplin said:
I got myself into trouble and I hope that someone who knows more than me can answer two questions.
Background:
I bought a new Nexus 7 2013 WIFI (razor / flo). I loaded TWRP recovery, and rooted the device. I decided to encrypt the drive, but TWRP doesn't appear able to do that (when the device reboots to start encryption, it just boots normally into Android). However it does appear that TWRP can mount an encrypted drive, so I decided to flash stock recovery to do the encryption and then reflash with TWRP.
Problem 1:
I accidentally flashed with the wrong stock image. I used the image for the Nexus 7 2013 Mobile (razorg / deb). The flash-all.sh script includes a step for flashing the radio (fastboot flash radio radio-deb-deb-g00_2.37.0_1024.img). It executed the command without error, but I don't think there is a radio partition on this device. Does anyone know if there is a radio partition to control the GPS, WIFI, and/or NFC? Should I do something to undo this problem? I cannot find a radio firmware for this device, and the WIFI and GPS appear to work fine so perhaps I should just move on.
Problem 2:
Even when I use the stock recovery image for the correct device, it does not appear to load correctly. fastboot runs without errors, but when I boot into recovery I get the unconscious android with the red exclamation in his tummy. I have done a full wipe of all partitions, and a full restore. Based on my search in the forums, this appears to be a common problem but the suggested solutions don't seem to apply to my device. Any suggestions?
I should note that re-installing TRWP works fine, and I was able to restore my data from a backup. But I can't encrypt the device or install future updates until I can roll back to the stock restore image.
Thank you in advance for your help.
Click to expand...
Click to collapse
Flash the wifi factory image. I assume you're talking about flashing in adb. Once you flash the correct image it should all be good. I've never even tried to encrypt the drive so can't offer any help there. If you use flash-all you will need to reflash TWRP afterwards then SuperSu.
Still no stock recovery
wantabe said:
Flash the wifi factory image. I assume you're talking about flashing in adb. Once you flash the correct image it should all be good. I've never even tried to encrypt the drive so can't offer any help there. If you use flash-all you will need to reflash TWRP afterwards then SuperSu.
Click to expand...
Click to collapse
Thank you for trying to point me in the right direction, but I had already tried your suggestions.
The link you shared is for the official distribution of twrp. I tried it, and though it flashes fine, it did not help me return to the stock recovery.
I have been flashing the stock recovery from developers.google.com/android/nexus/images. It flashes without error, but when I try to boot to recovery I get the sick android (red exclamation mark). This happens whether I flash just the recovery image, or do a flashall, or an update.
I have been using fastboot instead of adb to flash the images.
Any ideas on why after flashing the stock recovery I cannot boot into it?
resplin said:
Thank you for trying to point me in the right direction, but I had already tried your suggestions.
The link you shared is for the official distribution of twrp. I tried it, and though it flashes fine, it did not help me return to the stock recovery.
I have been flashing the stock recovery from developers.google.com/android/nexus/images. It flashes without error, but when I try to boot to recovery I get the sick android (red exclamation mark). This happens whether I flash just the recovery image, or do a flashall, or an update.
I have been using fastboot instead of adb to flash the images.
Any ideas on why after flashing the stock recovery I cannot boot into it?
Click to expand...
Click to collapse
I'm sorry about the link, not that it does any good now but the link is corrected. Using fastboot to flash the images is correct, I too often use adb as a generic term for both. When you boot into the stock recovery you will see the android with the exclamation mark and that is normal. Finally got the new 2012 N7 I bought as a gift and was updating it. Been a while since I've booted into a stock recovery. So... Boot into stock recovery, when the Android with the red exclamation mark appears, hold down power first, followed quickly by volume up. You should now see the recovery menu. Whoop, Whoop! :laugh:
It works!
Thank you very much for your patient explanation. That helps a lot.
I hadn't realized that there was an additional step after the display of the warning android in order to enter stock recovery. All that time I spent trying to fix something that wasn't broken! <sigh>
I was unable to get the device to display the stock recovery menu, because it appears to require a very precise timing (I just keep rebooting it back to the system by accident). However, encryption did work fine. My confusion with the encryption was compounded by the fact that encryption of the Nexus 7 in 4.4 doesn't always work the first time (see this thread at android central: forums.androidcentral.com/google-nexus-7-tablet-2013/337078-experiencing-difficulty-encrypting-my-2013-n7-after-4-4-build-krt16s-upgrade.html). After trying 4 times in a row, the device encrypted. I was then able to put Team Win Recovery back on the device, and everything works perfectly.
Thank you again for your help. I don't see how to mark the thread as solved, but I am glad that everything appears to work now.
So earlier today I had my Verizon HTC One running smoothly; 4.3, 2.10.605.10, all that jazz. Then firewater came out, so I did S-Off. I then installed Clockworkmod, because TWRP wouldn't (turns out I installed the m7 variant instead of the m7vzw one). I also had the wrong version of clockworkmod, so it wouldn't factory reset or clear cache. I decided I would try to install Cyanogenmod anyway, and right after I started the install I found the correct version of TWRP so I hard reset out of the install with the Power and Volume Down buttons.
Now I am stuck in bootloader, and there is not much I can do. I can't install the RUU that i have because I cant "fastboot oem lock" and I also can't flash or boot directly to the TWRP or Clockworkmod .img files. Any ideas on how to fix it?
tl;dr I stopped a .zip install and now I am stuck in bootloader HELP PLEASE
Billcheese5 said:
So earlier today I had my Verizon HTC One running smoothly; 4.3, 2.10.605.10, all that jazz. Then firewater came out, so I did S-Off. I then installed Clockworkmod, because TWRP wouldn't (turns out I installed the m7 variant instead of the m7vzw one). I also had the wrong version of clockworkmod, so it wouldn't factory reset or clear cache. I decided I would try to install Cyanogenmod anyway, and right after I started the install I found the correct version of TWRP so I hard reset out of the install with the Power and Volume Down buttons.
Now I am stuck in bootloader, and there is not much I can do. I can't install the RUU that i have because I cant "fastboot oem lock" and I also can't flash or boot directly to the TWRP or Clockworkmod .img files. Any ideas on how to fix it?
tl;dr I stopped a .zip install and now I am stuck in bootloader HELP PLEASE
Click to expand...
Click to collapse
Are you able to access fastboot from the boot loader?
If so do
Fastboot reboot recovery
Since you have TWRP installed already? If you can get adb sideload to work you can flash a new ROM of your choice after you clear the dalvik cache and such. If adb won't work for you you may have to order an otg cable to get that ROM to your phone. If you can't access fastboot and/or get into recovery.... RIP M7Vzw
eXperianceHD said:
Are you able to access fastboot from the boot loader?
If so do
Fastboot reboot recovery
Since you have TWRP installed already? If you can get adb sideload to work you can flash a new ROM of your choice after you clear the dalvik cache and such. If adb won't work for you you may have to order an otg cable to get that ROM to your phone. If you can't access fastboot and/or get into recovery.... RIP M7Vzw
Click to expand...
Click to collapse
So I tried the fastboot rebbot recovery and I don't think that is a correct command, because when I do it a list of all the fastboot commands comes back and my phone doesn't do anything. Also it was working before but now my device isn't visible under adb devices, so I don't think sideloading a different rom will work. Plus I can't get to the recovery, or even the stock factory reset or anything. They all just bounce me back to the bootloader menu.
Do you think it would be worth it to order and wait for an otg cable or just order a new phone? I'm not due for an upgrade and I don't think I'm willing to shell out $500 for a new One, or even $400 for a new Moto X, so I think I'll be getting the Moto G (I'm on a student budget here).
Are you running your commands fro the platform tools folder?
Oh well
Thanks for the help guys, I wasn't able to run any adb commands like I could before, so I guess that's that. Again, I am at college, and my parents happened to be visiting so I gave it to them. I have accident insurance on my phone, so they are going to send it back and have the replacement sent to me... so I can try again, hopefully more successfully the second time :laugh:
Hi,
there are several threads on this forum dealing with nexus devices that get stuck at the google logo when booting up, however my case is a little different:
I can not even get into recovery.
Here's the symptoms:
The touchscreen became unresponsive. I read that fixing the cache partition helps and it did.
From time to time my device would get stuck at google logo on boot, but i was still able to get into recovery, wipe cache and it would work again. This happened 2-3 times over the course of the last 3 weeks maybe, so i thought its just some minor hangup
2 days ago the device became unresponsive again and i was unable to get into recovery. I have tried several times and once i was lucky to get into recovery (it showd google logo, but when i pressed the power button to turn it off i got into recovery)
now nothing will work. i can get into the bootloader no problem and fastboot is in a working condition
i have tried flashing the factory image using the files provided by google. So far no success
Does anyone know something else to try?
EDIT: aniket0317 suggested using Wugfresh's Root Toolkit which includes a script to unbrick in case of bootloops. That seems to have worked.
Flashing back to stock is a first step, to ensure it's nothing in the software. What do you mean by "So far no success"?
Use Wugfresh's Nexus Root Toolkit. There is a option named Stock Flash+Unroot (Bootloop). The device should be able to get into fastboot mode, though.
aniket0317 said:
Use Wugfresh's Nexus Root Toolkit.
Click to expand...
Click to collapse
This seems to have done it. I have followed the instructions in the toolkit and rebooted the device several times already successfully. The next days will tell whether the touchscreen freezes still happen. But for now, thank you.:good:
mistermabuse said:
This seems to have done it. I have followed the instructions in the toolkit and rebooted the device several times already successfully. The next days will tell whether the touchscreen freezes still happen. But for now, thank you.:good:
Click to expand...
Click to collapse
Press thanks if I helped you
Sent from my Nexus 7 using Tapatalk
Same problem
Hey,
my Nexus 7 2013 has the same error.
Im stuck in Google screen, only enter in fastboot mode.
Tried Nexus Root Toolkit and other methods but stays the same...
In TWRP, touchscreen doesnt work.
What can i do???
Thanks!
Hey thiago,
I don't really know what to do, but I have the same problem now...
I guess it should be possible to somehow boot clockworkmod recovery from fastboot,
but I'm not sure.
I'll mark this thread not solved again -.-
mistermabuse said:
Hi,
there are several threads on this forum dealing with nexus devices that get stuck at the google logo when booting up, however my case is a little different:
I can not even get into recovery.
Here's the symptoms:
The touchscreen became unresponsive. I read that fixing the cache partition helps and it did.
From time to time my device would get stuck at google logo on boot, but i was still able to get into recovery, wipe cache and it would work again. This happened 2-3 times over the course of the last 3 weeks maybe, so i thought its just some minor hangup
2 days ago the device became unresponsive again and i was unable to get into recovery. I have tried several times and once i was lucky to get into recovery (it showd google logo, but when i pressed the power button to turn it off i got into recovery)
now nothing will work. i can get into the bootloader no problem and fastboot is in a working condition
i have tried flashing the factory image using the files provided by google. So far no success
Does anyone know something else to try?
EDIT: aniket0317 suggested using Wugfresh's Root Toolkit which includes a script to unbrick in case of bootloops. That seems to have worked.
Click to expand...
Click to collapse
EDIT 2: Yes it worked, at first. Now the device is stuck in a bootloop again. I can boot into team win recovery, but touch doesn't work there so I can't do anything. Booting CWM from fastboot is also not suceessful.
What do you mean CWM is not successful, that there's no touch response? If all else fails, you can use the non-touch version of CWM, using the side buttons to navigate. But I'd be concerned if screen touches are not being recognized.
CWM dont start. Only twrp. Is there a TWRP non touch version?
There's no non-touch version of TWRP that I know of, since its design is based on touch.
What do you mean by CWM won't start? It just freezes? Did you flash the correct one?
6.0.4.3 for regular N7 2013: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.7-flo.img
6.0.4.8 for N7 2013 LTE: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.8-deb.img
6.0.4.3 for N7 2013 GSM: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.3-tilapia.img
still frozen
Pandae said:
There's no non-touch version of TWRP that I know of, since its design is based on touch.
What do you mean by CWM won't start? It just freezes? Did you flash the correct one?
[/url]
Click to expand...
Click to collapse
Yes, i used this version for Regular N7 2013, but still frozen in the google screen.
I have the same problem.
Stuck on google logo. It boots Fastboot only. It does not boot system or recovery.
What I have done so far:
Unlocked the bootloader
Flashed preview android L successfully But it did not boot. Then i Installed android 4.4.4. Successfully But still nothing. Then i flashed android 4.3 with the same result. Lastly i flashed TWRP to try and flash a zip, but again it does not go past the google logo. Everything i flash goes successfully or at least there are no errors on the logs. I have used wugs nexus toolkit to flash everything. I can see the bootloader version being changed after flashing different android versions, so i can confirm it is flashing bootloader at least.
My conclusion:
I think there is a hardware problem but I don't know how to troubleshoot what is wrong.
If anyone has any suggestion. It will be much appreciated.
Sent from my SM-G900F using XDA Premium HD app
Send it back to Google
gopin said:
I have the same problem.
Stuck on google logo. It boots Fastboot only. It does not boot system or recovery.
What I have done so far:
Unlocked the bootloader
Flashed preview android L successfully But it did not boot. Then i Installed android 4.4.4. Successfully But still nothing. Then i flashed android 4.3 with the same result. Lastly i flashed TWRP to try and flash a zip, but again it does not go past the google logo. Everything i flash goes successfully or at least there are no errors on the logs. I have used wugs nexus toolkit to flash everything. I can see the bootloader version being changed after flashing different android versions, so i can confirm it is flashing bootloader at least.
My conclusion:
I think there is a hardware problem but I don't know how to troubleshoot what is wrong.
If anyone has any suggestion. It will be much appreciated.
Click to expand...
Click to collapse
What if you flashed the stock factory recovery/ROM, or is that what you mean by 4.4.4 and 4.3? Don't use a recovery to flash the individual .img files, just run flash-all.bat and see what it does.
https://developers.google.com/android/nexus/images
Pandae said:
What if you flashed the stock factory recovery/ROM, or is that what you mean by 4.4.4 and 4.3? Don't use a recovery to flash the individual .img files, just run flash-all.bat and see what it does.
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Yes. I flashed the factory images using wugs nexus toolkit and ticked the option flash stuck + unroot (bricked or bootlooping) to see if it would work as mentioned by OP. All factory images flash successfully all partitions, but it does not boot recovery or system. I tried different android versions hoping it would make a difference and tried booting recovery after flashing each image (4.4.4 and 4.3). I haven't tried typing the command flash all.bat myself to flash the image as you suggested. I've used the toolkit to make it easier. I'll try flashing stock typing command flash all.bat myself and report.
Sent from my SM-G900F using XDA Premium HD app
Use your warranty, send it back to Google.
Hello everyone, today I installed TWRP recovery, it went fine and I am not new to install custom roms, custom recoveries, etc. but this got my phone messed up. It was working perfectly fine and then I turned it off in the night and in the morning, it just got stuck in a bootloop, and knowing me of course, I forgot to create a backup as I installed TWRp. So, is there any kind fellow out there that has a TWRP backup at hand for the ZE551ML?
Just to get the order correct...
Flashed TWRP - No problem
Rebooted to system - No problem
System worked?
Turned off phone
Bootloop on power on?
Is this a bootloop, or does it just sit on the Asus screen? Does it get to the actual boot animation, or are you on the splash screen?
Harfainx said:
Just to get the order correct...
Flashed TWRP - No problem
Rebooted to system - No problem
System worked?
Turned off phone
Bootloop on power on?
Is this a bootloop, or does it just sit on the Asus screen? Does it get to the actual boot animation, or are you on the splash screen?
Click to expand...
Click to collapse
I am getting to the boot animation with the gears turning and then error comes up and boots me into TWRP. The problem is, the Bootloader will not come up so I can do the fastboot flashing, TWRP comes up instead. It comes up and I didn't overwrite the bootloader with TWRP. Problem is I can't access fastboot commands.
Lurkingintheshadows said:
I am getting to the boot animation with the gears turning and then error comes up and boots me into TWRP. The problem is, the Bootloader will not come up so I can do the fastboot flashing, TWRP comes up instead. It comes up and I didn't overwrite the bootloader with TWRP. Problem is I can't access fastboot commands.
Click to expand...
Click to collapse
Give me a few minutes. I'll get you a TWRP flashable boot.img zip.
Try flashing this in TWRP. You might need to sideload it onto your phone if you can't boot into system.
Harfainx said:
Try flashing this in TWRP. You might need to sideload it onto your phone if you can't boot into system.
Click to expand...
Click to collapse
Thank you. But, it won't flash, I've tried about every option now. I think I'm just going to see if I can get a replacement. 2.19 was always causing me problems to install and then now that I finally got it on my phone, I couldn't install another 2.19 on top of it or downgrade. Guess this phone is done for until CM12 gets released. Thanks for the help but it seems it can't be recovered at this point.
Lurkingintheshadows said:
Thank you. But, it won't flash, I've tried about every option now. I think I'm just going to see if I can get a replacement. 2.19 was always causing me problems to install and then now that I finally got it on my phone, I couldn't install another 2.19 on top of it or downgrade. Guess this phone is done for until CM12 gets released. Thanks for the help but it seems it can't be recovered at this point.
Click to expand...
Click to collapse
If you lurk on these forums, there are some Intel flashing tools I've seen that can help you recover from a soft brick.
I am stuck too!
I was in stock recovery and did a cache wipe. It took forever and wouldn't come out of it so i powered it off and tried booting. It got stuck on bootloop. phone is asus zenfone 2 Z00A. It is intel chipset. please help me out.
the worst part is that i cant get into fastboot or recovery modes so i am completely stuck! please help me out.
when i try to get into fastboot mode with vol up+ power key it vibrates but nothing is displayed.
if i just power it on its stuck on bootloop.
i can't get into recovery and fastboot bcoz its at the same place.
can i use adb commands or fastboot commands somehow?
i can maybe use adb reboot recovery to get into recovery and then i can do a wipe and flash new stuff.
please help me out.
UPDATE: I found out u can use adb reboot recovery while on the asus bootanimation.
i tried adb reboot recovery and now getting a flashing android sleeping bot with error!
can't use adb or fastboot commands now though
now in even bigger mess. after using adb reboot recovery, i can't get to bootanimation either.
just stuck at flashing android sleeping bot with error.
can't get to bootloader or fastboot or anything!
Please any suggestions. I'm dying here to fix it.
I have a adb backup.
i couldn't take a nandroid backup. i just entred recovery and wiped cache first. after doing that i was going to flash twrp and then using twrp take a nandroid backup and flash a custom rom. but it got stuck at cache wipe and i powered it off and the whole mess.:
Finally entered bootloader with fastboot now working!
Content and satisfied
I_am_sid said:
I was in stock recovery and did a cache wipe. It took forever and wouldn't come out of it so i powered it off and tried booting. It got stuck on bootloop. phone is asus zenfone 2 Z00A. It is intel chipset. please help me out.
the worst part is that i cant get into fastboot or recovery modes so i am completely stuck! please help me out.
when i try to get into fastboot mode with vol up+ power key it vibrates but nothing is displayed.
if i just power it on its stuck on bootloop.
i can't get into recovery and fastboot bcoz its at the same place.
can i use adb commands or fastboot commands somehow?
i can maybe use adb reboot recovery to get into recovery and then i can do a wipe and flash new stuff.
please help me out.
UPDATE: I found out u can use adb reboot recovery while on the asus bootanimation.
i tried adb reboot recovery and now getting a flashing android sleeping bot with error!
can't use adb or fastboot commands now though
now in even bigger mess. after using adb reboot recovery, i can't get to bootanimation either.
just stuck at flashing android sleeping bot with error.
can't get to bootloader or fastboot or anything!
Please any suggestions. I'm dying here to fix it.
I have a adb backup.
i couldn't take a nandroid backup. i just entred recovery and wiped cache first. after doing that i was going to flash twrp and then using twrp take a nandroid backup and flash a custom rom. but it got stuck at cache wipe and i powered it off and the whole mess.:
Finally entered bootloader with fastboot now working!
Content and satisfied
Click to expand...
Click to collapse
how did you get fastboot working? I can get into bootloader, but cant get my pc to connect with my zenfone2. can't use any adb cmd it would just say "error: can't find devices"
I_am_sid said:
I was in stock recovery and did a cache wipe. It took forever and wouldn't come out of it so i powered it off and tried booting.
Click to expand...
Click to collapse
Just a reminder to everyone, never force shutdown the Phone during a cache wipe procedure, it takes a long time but it finishes.
When I did it on my ZF2, I thought it was taking too long, but I did a search here and found out about it taking long before it was too late.
I'm glad you could recover yours. :good:
I shut mine down because it took too long. Wouldn't start up again. Had to send it in for RMA. Asus Canada reset the OS. I'll never do that again.
Sent from my ASUS_Z00AD using XDA-Developers mobile app
ikkuy said:
how did you get fastboot working? I can get into bootloader, but cant get my pc to connect with my zenfone2. can't use any adb cmd it would just say "error: can't find devices"
Click to expand...
Click to collapse
Dude you can never use adb when in bootloader.
That's why you have fastboot.
just type
fastboot devices
you will get your device.
if you don't then download intel drivers. You will get them in asus website.
if you are stuck without custom recovery i would suggest you to download system image (~1.5Gb) from asus website.
just search for asus zenfone 2 and go to official asus site. in downloads tab you should find both drivers and system image.
download the latest one.
See if you can get into stock recovery.
when in bootloader press vol down and go to recovery mode.
you will see a sleeping android bot with error.
press power key + vol down you will get a list.
choose factory reset and then after wipe is complete choose sideload from adb.
connect your phone and then in adb type
adb sideload filename.zip
obviously place file in your platform-tools folder and replace filename with whatever its name is.
it will take a while and you will get back your system.
---------- Post added at 07:37 PM ---------- Previous post was at 07:21 PM ----------
Marteicos said:
Just a reminder to everyone, never force shutdown the Phone during a cache wipe procedure, it takes a long time but it finishes.
When I did it on my ZF2, I thought it was taking too long, but I did a search here and found out about it taking long before it was too late.
I'm glad you could recover yours. :good:
Click to expand...
Click to collapse
Thanks!
It took a lot of time though.
For anyone stuck,
I first got fastboot working. and then i flashed stock recovery and boot.
got into stock recovery and sideloaded system img into it.
After it booted back into asus stock rom i unlocked bootloader, placed twrp in sdcard and got straight into fastboot again installed twrp and then did a wipe and went ahead and flashed ROM and Gapps. Working fine.
Update:
To get to bootloader:
i was stuck in a bootloop.
When at asus boot animation i connected USB cable and quickly typed
adb reboot bootloader
which seemed to work for me. Though i couldn't get into recovery.
So i had to flash stock recovery again.
Here has more background http://forum.xda-developers.com/note-4-sprint/development/rom-t3330135/page23 but the TLDR is that my phone is stuck in bootloop, even when I flash a stock image in Odin (Does it matter if I use AP in Odin versus BL? I tried both)
All I can think is that in recovery I did a full wipe on every conceivable thing. I also did a nanderase in Odin one time. Maybe shouldn't have.
This is also compounded by the fact that my phone's home button doesn't work so to get to download mode I am forced to use a jig I cobbled together and essentially hotwire my phone into download mode.
Does someone have a safe, stock ROM so I can get things back to square one? I've tried N910PVPS4COK1_N910PSPT4COK1_N910PVPS4COK1_HOME.tar so I am pretty sure I was on OG5 baseband with OK1 build. But still, if your friend who knew nothing about phones gave you one in a bootloop, which rom would you flash?
Thanks guys.
I've helped with a similar issue before. In short, nand erase all will prevent phone from booting.
You need to install just the stock recovery converted from .img to tar.md5, flash with Odin in AP slot and factory reset and wipe the cache and dalvik in recovery.
To start, you need to extract the recovery.img from the stock tar and use utility to convert it and flash in Odin AP slot. This utility may work, I don't recall which utility I used before because my motherboard and hard drive crashed. Lost everything. Try this one.
http://forum.xda-developers.com/showpost.php?p=45629177&postcount=1
With your broken home key, I'm not sure what the phone does with only recovery flashed. Hopefully it auto boots to recovery seeing only that so you can factory reset and wipe. If so, flash stock after that.
If you can't boot to recovery, you may have to install adb on your computer and try to send the command (adb reboot recovery) from either download mode or timed correctly while it's attempting a boot. I'm thinking with nothing but recovery, the phone will either boot recovery or KIES or Smart Switch will recognize it. You may also convert the boot.img (kernel) with that same utility for Odin flash in AP slot if the phone isn't recognized. The bootloader could also be extracted and flashed with Odin in BL slot.
But hopefully you don't have to do all this workaround stuff to recover. I'd start with just stock recovery converted tar.md5 with utility and factory reset and wipe. If it didn't auto boot into recovery, try the traditional boot to recovery pattern. If not working, then try the adb command from download mode, and so on with other means to either boot in recovery or get KIES or Smart Switch to recognize.
Edit: if you're already able to boot stock recovery, just factory reset, wipe cache and dalvik and power down, remove battery for 30 seconds and flash stock tar.
Sent from my SM-N930P using Tapatalk
Can you elaborate on boot to recovery pattern? I flashed the recovery but it still wouldn't boot to recovery. Is that because the stock tar I flashed is still fouling things up?
Should I land erase again so the stock tar is gone, then try flashing the recovery Image? I don't quite understand why taking parts of the stock tar and flashing them separately is any different than flashing the tar file itself.
Got some reason, adb always says device not recognised, even though Odin has no trouble, so it's probably not a driver issue, but the way I'm starting or running adb.exe
Since you already did the nand erase all in Odin and haven't booted successfully, I don't think you could do any further harm by going it again.
I honestly don't know the usefulness of the feature or instructions when using it, just that from some searching, that stock recovery helps to recover from using it.
Sounds like your home switch is still dysfunctional and you want to try the nand erase all, flash only stock recovery and see if it auto reboots into recovery? You could try.
Did you use this adb installer or follow the OP to try to get phone recognized?
http://forum.xda-developers.com/showpost.php?p=48915118&postcount=1
Edit: Still reading the thread above but it looks like win10 users have to run installer in administrative mode and also use the edited version below. Not sure if the OP corrected the issue but typo of version in OP still exists so I'd try this one and make sure the Samsung driver from Samsung support was also installed.
http://forum.xda-developers.com/showpost.php?p=67779874&postcount=821
I'm still getting my new PC updated with tools but will try this adb installer soon.
Sent from my SM-N930P using Tapatalk
Fyi I'm on Windows 7 if it matters
Blakestr said:
Fyi I'm on Windows 7 if it matters
Click to expand...
Click to collapse
Have you tried traditional adb through installation of Android SDK and setting path as outlined in this guide?
http://www.serverdrivers.com/2016/10/universal-adb-driver-download-for.html?m=1
And did you install the Samsung USB driver from Samsung support on Note 4?
http://org.downloadcenter.samsung.c...G_USB_Driver_for_Mobile_Phones_v1.5.45.00.exe
I ask because I'm not sure why you get device not found. The installer thread I mentioned earlier claimed that only adb sideload works with the above adb method. I'm thinking it may be Google limiting access in later updates but just a guess.
Sent from my SM-N930P using Tapatalk