[Solved] upgrade to 1.1.2, and backup, then stuck to "rooted forever" - Nook Touch General

I just upgraded my unrooted nst to 1.1.2, it succeeded and I can enter into the system.
Then I backup my nst and restore to an old image in win7, using DiskImage 1.6, but it failed and report "failed to write section 0" or sth like that.
Seeing that error, I unplugged the usb and removed SD, then the nst stuck on "Rooted Forever", and cannot access the disk from win7 anymore.
I have tried:
1. hold on pwb 30s, release, wait 5s, hold on again -- no response, even no a flash
2. hold pwb, left, rigth -- nothing
What else can i do to recover my nst?
Thanks very much for any help.

You arent stuck on the Root Forever screen, probably you killed your nooks boot partition, so it just wont refresh the screen, nor boot.
Try the normal procedure to restore a backup, it should work.
http://forum.xda-developers.com/showthread.php?t=1142983

Thanks for reply.
It solved, I just put SD back to nook and it is able to restart and enter into the unroot system.
Thanks anyway

Related

[Q] accidentally formatted Nook Touch -- stuck on Rooted Forever screen

I hope I'm posting in the correct place.
I think I've bricked my Nook Touch (tell me it isn't so!). The problem is as stated in the subject line. Now it won't turn off or respond at all to hardware or touch. Is there at least a way to get the screen back to "Read Forever"?
Please help, and let me know if you need more information!
I'll be so grateful if this problem can be at least partially solved.
try to remove sd-card and reboot it
I tried that; the Nook Touch will not reboot. Thanks for replying.
Would the zip file Nook Simple Touch Full_Factory_Restore.zip work for me in this scenario? If so, where can I get the file?
Its almost impossible to brick this device. Try this first.
Hold power firmly for 30 seconds.
let it go
Wait 10 seconds
Hold power again for about 10 or so seconds the screen should change and you should reboot.
Try this with the SD card in and out. You can also try and repeat the step of writing the .img to your SD card. Download the file again or verify the checksum in case you got a bad download.
The screens will not necessarily change if you are stuck in a boot loop and power down. Regardless if it doesn't boot 8 times it will revert its pretty much impossible to brick the unit. You can also try to power off via ADB and or try the script that forces the 8 failed reboots.
____________________
Edit I missed that it appears you intentionally formatted the device? What exactly did you do?
Also if you made a back up of the partition prior to formatting (not sure exactly what you did or why you did it) but that should have been your first step prior to doing anything exotic so you can replace the files necessary. I'm not at home otherwise I'd post the partition contents for your restore I'm sure you can find them on the net somewhere or here. I think the nook color root wiki may have the Nook touch back up files I'm not sure though. Either way its trivial to pull them and post them. Those of you that may do this make sure your account information is wiped first prior to making the back up for him.
Exactly which partition you formatted? The one normally exposed during USB connection? In this case power it off (by holding the power button for few seconds and selecting power off) and then do a hard reset
Hold power button and the bottom two side buttons until the screen starts to flicker. Release power button but hold the side bottom buttons until you see a hard reset screen
After reset the data partition will be as good as new.
Rooted Foreve screen - the brick
Hello everyone. I'm from Russia. And I have the same problem: Rooted Forever on the screen (I have formatted sd card by Mini Tool Partitition Wizard - Delete all partititions) when the SD card was into Nook and my Nook is the brick. And i can't send my Nook to B&N. None of your advices did not work. But I still have some hope. Maybe my experience will be usefull for you.
I have pushed 2 bottom buttons & power button for 30 seconds. Then 10 seconds pause. Then I have pushed 2buttons+pwr for 30 seconds again. And Nook has turned off. But the screen was completely dark. Then I turned it on and saw Rooted Forever. After that I repeated 3 buttons holding and turned the nook off. Right now my screen is completely white.
And one other thing. I also have tried nookrestorer program . I've mount an image on SD. Put it into nook. Turned it on. Script on the screen: wait for 10 sec, turn off yor nook. Take out SD. But it does not work.
I managed to lock my Nook up on boot right after I rooted it, but got it to unlock and revert to factory settings. Mine was frozen on the "Read Forever" screen and would only flash when I turned it off (something I've not read anywhere else) but this may help some of you... Don't try to do a factory reset and immediately root it again, because you may have to update the Nook again first!
First, remove the SD card, then power it off (hold the power button for 20 seconds until the screen flashed) then, letting go of the power button and immediately pressing and holding the power button again and the two bottom side buttons (I think for 10 seconds?)
The Nook would still sit on the "Read Forever" screen a minute or so, then started doing a factory reset, wiped everything including the data section and the updated software.
I had to re-update the Nook to 1.1 and then could re-root it.
---
Edit:
I realized after I posted this that I lied. Sorry. That didn't work for me, but I discovered that I could still access ADB over USB with my Nook while it was frozen on the loading screen... so I did this from my PC:
adb shell
echo -n -e "\x08\x00\x00\x00" > /rom/devconf/BootCnt
reboot
Credit to page nookdevs dot com/Flash_back_to_clean_stock_ROM (Not enough posts to post links yet, sorry!)
Note that you do have to have the ADB installed, but I think that's key to a lot of the root methods...
Aridon said:
Its almost impossible to brick this device. Try this first.
Click to expand...
Click to collapse
Bricking the NST is quite easy, just boot with Noogie and write some garbage onto the flash.
Lots of people do this by trying to write incomplete backups back to their NST.
If what you write is big enough to reach the /rom partition you're basically hosed.
Aridon said:
I'm not at home otherwise I'd post the partition contents for your restore I'm sure you can find them on the net somewhere or here. I think the nook color root wiki may have the Nook touch back up files I'm not sure though. Either way its trivial to pull them and post them. Those of you that may do this make sure your account information is wiped first prior to making the back up for him.
Click to expand...
Click to collapse
This is a very bad advice, the /rom and /factory partition contains data unique to every NST such as MAC address, serial, board serial, EAN, private and public keys, etc..
Using a backup from another NST can and will cause troubles for you and the person owning the NST the backup came from.
My NST was bricked as well, after a Salsicha-image write session failed. Permanently stuck in the "Rooted forever" screen no matter what I pressed. Prior to the write, I have deleted ALL the partitions on my NST and then it wouldn't boot, so it seemed gone forever.
Yet it turned out that my NST can still boot with the Nookie image on a microSD
( from the BACKUP/RESTORE N2E Win7 thread). Connect it via USB to the PC and managed to restore it using my backup image. Eventually I did did the Salsicha root successfully. My NST is now rooted with 1.1.
I don't have specific advices, but the NST does seemed hard to be properly bricked. Given my experiences, I actually wonder if the NST hardware could bootstrap itself entirely from the microSD, irrespective of the state of its internal flash.
Just solved this thing: formatted microSD with Noogie Image, then deleted all partitions and than flashed my backup image back and Nook is working fine now!
jack ng said:
I actually wonder if the NST hardware could bootstrap itself entirely from the microSD, irrespective of the state of its internal flash.
Click to expand...
Click to collapse
Yes it can.
Bricked Nook
I've also formatted my Nook when I was thinking that I was formatting the sdc. I've tried installing the nookRestore img and nT2-Recovery but both of these get to the screen where it says to wait but then the Nook won't reboot. My Nook can no longer be seen by my computer so isn't showing up in device manager. I've also tried the various boot tricks manually. I also lost my backup of my Nook when I had to reinstall Windows a week ago. If anyone could help that would be great!
Thanks.
Edit---
I've found my backup image but it says Install Failed: Please power off and back on. I do this but it says the same thing. It shows up for a few seconds in device manager right after I power it on but the device id is wrong, USBSTOR\DISK&VEN_B&N&PROD_EBOOK_DISK&REV_0100\11223344556677&0. And then it disconnects in a few seconds.
aknas22 said:
I've also formatted my Nook when I was thinking that I was formatting the sdc. I've tried installing the nookRestore img and nT2-Recovery but both of these get to the screen where it says to wait but then the Nook won't reboot.
Click to expand...
Click to collapse
If you formatted your NST, Factory Restore (and thus n2T-Recovery) will not work as you removed the partition containing the actual Restore image (partition 3)
aknas22 said:
Edit---
I've found my backup image but it says Install Failed: Please power off and back on. I do this but it says the same thing. It shows up for a few seconds in device manager right after I power it on but the device id is wrong, USBSTOR\DISK&VEN_B&N&PROD_EBOOK_DISK&REV_0100\11223344556677&0. And then it disconnects in a few seconds.
Click to expand...
Click to collapse
What size is your backup image?
The unknown device you see for a split second at boot can be ignored, this is normal behavior.
It's 77.5 megabytes, I made it with Roadkill but I'm not sure if I did it right. I got it best the install fail screen. I'm not absolutely sure that I formatted the Nook but since none of the recovery methods or other images work that's the only thing I can think of. Also its no longer communicating with my computer properly.
Thank you for your reply.
I remember that there was a file(image) that works on the same principle as Noogie, but it will start the factory reset instead. Have you tried that ??? Unfortunately I don't know whether it uses/refers to the "formated" factory partition or it makes it's own. I think yo might find it in one of the threads, about rooting the Nook.
P.S. : the size of your backup file is too small ... it has to be about 1.8G
aknas22 said:
It's 77.5 megabytes, I made it with Roadkill but I'm not sure if I did it right. I got it best the install fail screen. I'm not absolutely sure that I formatted the Nook but since none of the recovery methods or other images work that's the only thing I can think of. Also its no longer communicating with my computer properly.
Thank you for your reply.
Click to expand...
Click to collapse
Your backup is worthless, don't bother with it.
Also Factory Restore, n2T-Recovery etc won't help you.
Check your PM in a few mins.
zholy said:
I remember that there was a file(image) that works on the same principle as Noogie, but it will start the factory reset instead. Have you tried that ??? Unfortunately I don't know whether it uses/refers to the "formated" factory partition or it makes it's own. I think yo might find it in one of the threads, about rooting the Nook.
P.S. : the size of your backup file is too small ... it has to be about 1.8G
Click to expand...
Click to collapse
Thanks for your reply, yea my backup is missing something, I thought I found a my good one but it doesn't seem to be. I found those other images but as ros87 said they don't work either.
Keep getting "Install failed" screen
Well, I seem to have bricked my NST as well.
I was trying to unroot from TouchNooter by restoring what I now know was a bad backup image (only 77MB). I am also certain that the NST was reformatted as well.
When there is no SD card in the NST it is stuck in the "Install Failed" screen. It can reboot but just goes back to the "Install Failed" screen.
I have located the original backup image of the NST when it was fresh out of the box and think it's a good one (1.92GB), but I am unable to restore it while the nookie image is mounted in the SD drive. I have also tried the two manual restore images (NST-Recovery) and although they ran succesully they did not fix the problem.
Is there anything else I can try to get my NST working again or is it bricked forever?
UPDATE: SUCCESS!
Just in case anyone else runs into this problem:
I was using roadkil's disk image program to restore the known good backup image and kept getting an error message: "Error #5 occured while writing to disk at sector 0". A google search of that error turned up a in a blog where I learned that roadkil doesn't play well with windows 7. What you have to do is run a program called lockdismount.exe version 0300 (google it), lock that physical drive, and leave that program running. THEN run disk imager and restore the backup image to the NST. When disk imager is done, exit that program, go back to lockdismount, unlock that drive, and then exit lockdismount.
Note: When disk imager was finished restoring it gave me an error, but I went ahead and booted up the NST anyways. My Simple Touch is back to it's factory-fresh state and all is well again
*Many* thanks to everyone who posts in this forum. Going through all the posts helped me troubleshoot and eventually unbrick my Nook SimpleTouch.
Life saver!!!! Thank you!!!
ajjdowning said:
Well, I seem to have bricked my NST as well.
I was trying to unroot from TouchNooter by restoring what I now know was a bad backup image (only 77MB). I am also certain that the NST was reformatted as well.
When there is no SD card in the NST it is stuck in the "Install Failed" screen. It can reboot but just goes back to the "Install Failed" screen.
I have located the original backup image of the NST when it was fresh out of the box and think it's a good one (1.92GB), but I am unable to restore it while the nookie image is mounted in the SD drive. I have also tried the two manual restore images (NST-Recovery) and although they ran succesully they did not fix the problem.
Is there anything else I can try to get my NST working again or is it bricked forever?
UPDATE: SUCCESS!
Just in case anyone else runs into this problem:
I was using roadkil's disk image program to restore the known good backup image and kept getting an error message: "Error #5 occured while writing to disk at sector 0". A google search of that error turned up a in a blog where I learned that roadkil doesn't play well with windows 7. What you have to do is run a program called lockdismount.exe version 0300 (google it), lock that physical drive, and leave that program running. THEN run disk imager and restore the backup image to the NST. When disk imager is done, exit that program, go back to lockdismount, unlock that drive, and then exit lockdismount.
Note: When disk imager was finished restoring it gave me an error, but I went ahead and booted up the NST anyways. My Simple Touch is back to it's factory-fresh state and all is well again
*Many* thanks to everyone who posts in this forum. Going through all the posts helped me troubleshoot and eventually unbrick my Nook SimpleTouch.
Click to expand...
Click to collapse
THANK YOU soooo much!!! lockdismount.exe save my NOOK. Couldn't restore my backup img using roadkil's utility but after reading your post I'm all set.
Thanks again.
overwritten rom and factory partition
ros87 said:
Bricking the NST is quite easy, just boot with Noogie and write some garbage onto the flash.
Lots of people do this by trying to write incomplete backups back to their NST.
If what you write is big enough to reach the /rom partition you're basically hosed.
This is a very bad advice, the /rom and /factory partition contains data unique to every NST such as MAC address, serial, board serial, EAN, private and public keys, etc..
Using a backup from another NST can and will cause troubles for you and the person owning the NST the backup came from.
Click to expand...
Click to collapse
Hello, i am one of those unlucky/incompetent user who overwrite those partition. My experience is this: I can use (read, browse etc) other device's ROM (with different serial etc) on my NOOK, but if I want to deregister/or re-register my device at B&N, the process leads me to an ERROR message at the end.
I have no idea how to solve this problem. Maybe editing several files on Boot partition and Factory partition. Or maybe there is a way to erease these data from these file (resetting) I d not know. Or maybe there is an ORIGINAL rom without any device specific data, I don't know... and I am a bit hopeless.
Do You have any idea?
People at B&N do not understand the problem at all...
Thanks in advance for any help!
Tamas

Android boot loop...and can't revert!

...my effort to install Android on my new NOOK Color went smoothly until it started to boot and the boot screen just keeps spinning.
Read many posts appearing to address this issue but reverting to a stock reader seems to require various apps only for a PC. Being a Mac weenie this leaves me out in the cold.
...is there a Mac-centric reader here who can help me return my NOOK into the reader it originally was?
I'm a bit gun shy now of making the device both an Android tablet and a reader! Thanks much in advance.
...addendum!
...playing around with the NOOK I was able to raise a reboot option which, to my surprise, cured whatever fault was behind the boot loop. A couple of spins and CM7 in all its glory appeared.
...but now I can only reboot into CM7...seems to be no option to boot into the original B&N book/magazine reader.
What am I missing? What's the "open sesame" to choose the reader? Tnx again.
MacFreddie said:
...playing around with the NOOK I was able to raise a reboot option which, to my surprise, cured whatever fault was behind the boot loop. A couple of spins and CM7 in all its glory appeared.
...but now I can only reboot into CM7...seems to be no option to boot into the original B&N book/magazine reader.
What am I missing? What's the "open sesame" to choose the reader? Tnx again.
Click to expand...
Click to collapse
One thing your missing is giving us information regarding your setup and what you want and/or are expecting.
Is this a SD install of CM7? If so... when you power it up... press and hold "n" button to get the boot menu... selecting eMMC / Normal boot will boot into stock.
DizzyDen said:
One thing your missing is giving us information regarding your setup and what you want and/or are expecting.
Is this a SD install of CM7? If so... when you power it up... press and hold "n" button to get the boot menu... selecting eMMC / Normal boot will boot into stock.
Click to expand...
Click to collapse
...thanks much for the quick response.
...yes, I did an SD install of CM7 with all the Google apps, etc.
My objective is to be able to toggle back and forth between the B&N reader and the Android tablet. If this isn't possible I'd like to go back to the reader.
Unfortunately I can't get the boot menu with the "n" button when I power up. Andoid mounts and a white screen offers only "power off" or "re-boot"...no other options.
...following the instructions I used from the web for installing CM7 I removed the SD card before I formatted, etc. Is this an issue?
Looping Problem
Okay so I think I may have the same problem hopefully someone can help. So first I install CM7 and then it gave me when I tried opening the market so I was like okay... so then I downloaded and install manuelnooker and now im boot looping .. So I insert the SD and turn it on but it doesnt boot up to recovery. I only see CM7 and then it boot loops into Nook Color With the big N on top and the small android bottom right corner. Can anyone help me out on what is the best way to get back into recovery. I know if I turn it on while holding the N its says CM7 and in the bottom it shows recovery but never goes to it. Much help please..
Okay so I finally got into CWR but now it gives me an error formatting data when I select mounts and storage and select format data? Im trying to revert back the nook color using nook complete restore 1.0.1. and I try doing it format data in the opening screen but I flash the zip and boot loops. any help is much appreciated.. Thanks
...some progress!
...less sleep but some progress.
...after several unsuccessful attempts I finally got the NOOK to restore to factory specs with the "8 interrupted boot" sequence [can't post the URL because I don't have eight posts yet :-( ].
Wasn't necessary to do the second step described in the post...NOOK automatically did the restore after zeroing the data and my B&N account can be accessed without more.
...but now I no longer have Android capability. Is there any way to install a simple toggle mechanism for both on the same tablet?
MacFreddie said:
...less sleep but some progress.
...after several unsuccessful attempts I finally got the NOOK to restore to factory specs with the "8 interrupted boot" sequence [can't post the URL because I don't have eight posts yet :-( ].
Wasn't necessary to do the second step described in the post...NOOK automatically did the restore after zeroing the data and my B&N account can be accessed without more.
...but now I no longer have Android capability. Is there any way to install a simple toggle mechanism for both on the same tablet?
Click to expand...
Click to collapse
You never fully described what you did to begin with. Did you follow specific steps on a site? If so, let's have the URL.....
http://www.youtube.com/watch?v=lmmmm8cBpe0
URL for CM7 install shown in msg title...server wouldn't let me enter it in msg body!

[Q] "Your Nook encountered an error that need to restart

I bought a new NST because I wanted to root it and use it as a summertime reader in place of my rooted Nook Color. I downloaded the required files from
[N2E][1.1] TouchNooter 2.1.31. Stupidly rushing though the install, I made two mistakes.
One, I didn't check to see what version of B&N software was running. Since it was newly opened, I'm suspecting that it was the earliest version.
Two, I inadvertantly left the NST plugged into the laptop when I did the install. When it booted up I get the Read Forever screen, then the scrolling dots, then it flashes a couple of times. When I slide the slider I see
[Q] "Your Nook encountered an error that need to restart
No matter how many restarts I try it shows this error everytime.
I tried both fixes in n2T-Recovery - Nook Simple Touch - Factory Restore / Recovery [v:0.2 17.11.11]. Neither helped. The .2 version indicates that it is doing a factory restore and it takes a bit of time. However, upon reboot, I am stuck in the same situation.
I am currently thinking I should try the initial TouchNooter 2 process and see if it helps.
Does anyone have any suggests? Thanks
I had similar problem. my problem was due to a disorder in "Media" drive.
I've solved this way:
I plug in device to pc and restart nook. after it booted up , nook drive and sdcard appear in My Computer. I format nook drive and restart it again and my problem solved ...
Thanks for the input. I tried the steps you outlined. When I rebooted the Nook showed up as another disk drive. I could see the contents of the drive. When I attempyed to format it, it immediately disappeared and says there is no disk in drive G:
I repeated the process and was able to created a folder in drive G:. I tried to do a chkdsk this time and got the same message as before.
Any other ideas?
did you test this tutorial :
http://forum.xda-developers.com/showthread.php?t=1360994
my idea is : first use "sd_128mb_clockwork-rc2.zip" image only.
with CWM ram you can format data and cache and system drives.
after solving error message , you can restore nook and root again...
Sounds reasonable. I'll make the CWM recovery card now. Would anyone else like to comment on this idea? I would hate to make things worse.
Well, I tried this. I booted to CWM.
First, I did a factory reset and rebooted. Still got the error.
Next, I formatted cache and data and rebooted. Same error.
Next, I formatted system. When I rebooted, I was stuck at the Read Forever screen.
I did some more reading at this point and thought I would try
n2T-Recovery - Nook Simple Touch - Factory Restore / Recovery [v:0.2 17.11.11]
I installed and rebooted. The system rebuilt itself and I am successfully running again. Thanks for all the advice and thanks to the developers

[Q] Stuck Rooted Forever..and ever

Hi there, I've done a fair amount of searching and have read up and down similar posts but haven't been able to get to a resolution.
I have an NST fw 1.2, I initially tried using noogie to root it, but i made a backup image of my device using dd before i started messing with it. upon having problems with adb i switched gears. at that point it was still booting up into normal nook homescreen and all functional. later i attempted touchnooter 2.1.31 but couldn't make it past the install screens (eg, step 1 wait for the black screen flash, then reboot never got me any progress). after multiple times rebooting i was able to attempt a factory reset, but it never completed. at this point it wouldn't respond to any combination of key holds/reboot sequences and was not recognized via usb by my ubuntu machine. currently with noogie on a sd card inserted in the nook, i can hold the power button and the screen will flash but never does anything other than show the 'rooted forever' screen. in this mode with the usb attached, i can see the 7 partitions (factory, cache, userdata, rom, nook, boot, and a 302 MB fs). so i feel like it's not totally dead (right?)
so i'm thinking, gosh i'd like to restore that backup image, or attempt another factory reset.. what would you do?
cgonxda said:
currently with noogie on a sd card inserted in the nook, i can hold the power button and the screen will flash but never does anything other than show the 'rooted forever' screen
Click to expand...
Click to collapse
Remove the sdcard!
If you reboot the nook with the noogie sdcard, then it will return to the Rooted Forever screen.
Remove the sdcard, then press and hold the power button for a few seconds, repeat a few times. It takes a fair bit of effort but will restart.
The power button is the button at the rear of the nook, not the 'n' button on the front of the nook.
cgonxda said:
i'd like to restore that backup image, or attempt another factory reset.. what would you do?
Click to expand...
Click to collapse
I would ...leave in the noogie sdcard
restore your backup
http://blog.the-ebook-reader.com/20...-and-restore-nook-glow-and-nook-simple-touch/
then remove the noogie sdcard, reboot, and check that the nook still works.
Since you have NST fw 1.2 you will need to root with Tinynoot.
Tinynoot for US Nook 1.2
http://forum.xda-developers.com/showthread.php?t=1650593
I didn't find any other rooting method that works for the US Nook 1.2
Tinynoot only has a few basic apps, ADB wireless, Button Savior, NookColorTools.
It has no google apps, and no access to google / android market.
You will need to use ADB to install apps.
If you have a UK Nook 1.2, then Tinynoot works, and there is Alpha TFU
http://forum.xda-developers.com/showthread.php?p=34216660#post34216660
thanks for the info, restoring from my backup image worked..
i used dd and got back to original and everything worked fine
Code:
dd if=my_backup.img of=/dev/sdb bs=1M
i checked out the TinyNoot info in the link you provided and was able to perform that root with no problems on my 1.2 firmware
Glad to hear it!

[solved] Note 3 bricked for good? No ADB interface to reflash manually.

Hi everybody.
TL;DR
Recovery hangs upon booting and fastboot mode doesn't show up ADB interface on my PC. How to flash the phone?
Long version:
I wonder if you can help me. My old faithful Note 3 is badly misbehaving. Yesterday I filled almost all its internal memory with some movies before heading out on a trip, but some time later when I reset the phone after unusually long boot all user settings were lost. Well, something went wrong, couple of hours later there was reset after reset so I wanted to restore previous backup... but couldn't. TWRP was showing error messages (TAR something something, 255) very shortly into restoring process. It couldn't restore backup but also couldn't make new one as well (similar error with TAR and code 255 when trying to backup user data).
Something was very wrong, so I thought maybe I will flash newer TWRP 3.0 and give it a try but suddenly after next reset I couldn't even get into recovery anymore - TWRP gives me black screen after several seconds into booting it. No icons, no reaction to key presses, nothing. Even holding power button does nothing.
Ooooookay, it's time to enter fastboot mode then and flash new recovery manually. So I enter it, connect phone to my laptop and... nothing! No ADB interface. Some kind of samsung driver is installing, but the most important one, for ADB, just doesn't show up. It's really weird. Reinstalling drivers doesn't help, only the same one device that shows up gets different names, but that's it - no ADB interface, and, effectively, I can't flash anything because fastbot and ADB can't see any device. Odin can't see the phone too.
What's going on? Is the internal flash dying or what? But if so what does it have to do with ADB not showing up? Do you have any ideas that I can try out in this situation? I checked my laptop with a tablet that I have on hand and it shows up its ADB interface without problem in fastboot mode even though it's the first time I connect it to this laptop, so laptop and it's system are fine.
If nothing helps then, well, One+ 3, here I come.
EDIT: Problem solved. Turns out f2fs on data partition crashed and therefore TWRP couldn't start at all. I managed to flash Philz CWM via Odin somehow (after messing with drivers for some more time) which told me there is something wrong with /data because it couldn't mount it at all. It couldn't format it either. Fortunately SlimLP managed to start and after throwing up some errors I managed to do factory reset which formatted the internal memory back to ext4. Then flashing TWRP, formatting data back to f2fs, restoring backup and voila! It works again. Good, I'll wait until Note 8 if there ever will be one.

Categories

Resources