Related
Hi everyone. I've been reading these forums for quite some time and I have been flashing some of the custom roms that the developers have made (I think they're all awesome). I thought that I was confident enough with flashing to give the CM7 rom a try. I followed FBis directions (not the one click but the slighter harder version) and upon flashing using heimdall I had an error saying that the PIT was flashed but the Kernel wasn't (unfortunately I was too stupid to write down the exact error).
I tried unplugging my phone from the computer and put it back in download mode where I get the screen "Firmware upgrade encountered....". I know from reading other posts that usually a Heimdall flash or Hemindall One-Click will fix the issue but another problem exists, my computer (win 7) upon plugging in the phone only sees it as a unknown device. I tried changing the driver manually to Samsung USB composite but it gives an error saying device is not working properly. Is there anything I can do to fix this brick? I just can't get my computer to recognize that my phone is connected so it's not possible to heimdall since it also thinks no device is connected.
Any help is greatly appreciated it. I have searched the forums for a similar situation but I think mine is unique so I made a new post, I know people don't like to repeat what is widely available.
Whenever i had that happen trying to install cm7 i just used the 1 click gremlin remover and it flashed back to stock for me.
http://forum.xda-developers.com/showthread.php?t=1500427
Sent from my SGH-T959V using XDA
Hi, nvm I fixed my issue
Yes I've tried to heimdall back to stock (or rather the new AntonX one-click that Bryan had made) but my phone was unrecognized. Instead of trying to update the driver manually through Device Manager I downloaded the Samsung 64bit drivers for our phones and ran the setup.exe. That seemed to overwrite the drivers and next time I put my phone into download mode it was recognized and all was well.
Sorry for taking up your time.
Turns out I haven't fixed my problem. My computer is able to recognize my phone now and so I've tried One-click heimdall back to Stock UVKJ6 under Bryan's thread. I flash it, however, I get the Samsung splash screen and nothing else happens. I go into recovery and it is still the blue CWM and it gives me errores that it cannot mount or open /cache/recovery/log. If a try a nandroid restore it cannot format volume and says make_extf4fs failed on /dev/block/stl10
I tried the one-click again, I flash once, let it restart, the flash again with bootloaders but still get blue CWM. Even if I try to flash bryan's SMSKJ6bml-rc2 kernel, I still end up with the blue CWM.
Anyone have ideas on what can be wrong?
http://sourceforge.net/projects/tea...T959VUVKJ6_STOCK-UVKJ6-One-Click.jar/download
oh wow, I was just flashing the one-click kernel, I'm a noob.
Thanks a lot FBis, I should have known better.
How did you solve it, now?
johndeere5 said:
I tried unplugging my phone from the computer and put it back in download mode where I get the screen "Firmware upgrade encountered....". I know from reading other posts that usually a Heimdall flash or Hemindall One-Click will fix the issue
Click to expand...
Click to collapse
Hi! I'm having a similar problem with that "firmware upgrade encountered an issue" message, driving me crazy. I gather you fixed the issue? Maybe I'm dense, but I can't figure out exactly how you did it. What exactly is Heimdall? Is that what you used? Other posts in this thread mention Gremlin Remover, did you use that? Where can I get Heimdall, and how do I use it if I do get it? I'm definitely a noob, but my need is real, any help will be appreciated. Thanks! R
The screen you see is download mode. Use the guide in the second link of my signature to flash back to stock and start over.
Why Not ODIN?
lumin30 said:
The screen you see is download mode. Use the guide in the second link of my signature to flash back to stock and start over.
Click to expand...
Click to collapse
Thanks, a few things I want to clear up though? I've heard that Heimdall doesn't work with Galaxy S2. Is that correct? In any case, isn't it just the same kind of program that ODIN is? I've been trying to use ODIN to flash a file called
recovery-cmw-hercules.tar
but it always fails. What will Heimdall do differently?
You can tell I'm pretty new to this, have patience with me please.
Incidentally, when I try to run ODIN, on the assumption that I'm seeing a download mode screen, I can get ODIN to detect the phone and I see COM(6) usually in the yellow-highlighted screen. I check only "auto reboot" and "PDA," and in the PDA field I insert the location of the tar file (above). Here's the result:
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Every single time.
Kindly, R
Galaxy S 2? Wrong forum. Anything from here will truly brick your phone.
Make sure you're using a samsung galaxy s 4g sgh-t959v. If that is not your phone stop flashing, look up the correct forums and only flash files from THAT forum, not from any other one.
lumin30 said:
Galaxy S 2? Wrong forum. Anything from here will truly brick your phone.
Click to expand...
Click to collapse
Oops! Where should I go then? Thanks, R
The T-Mobile galaxy s2 forums would be my first guess
Hi,
I'm trying to flash another firmware for my GIalaxy Note 10.1 N8000. I have read all tutorials etc. and prepared all according to it.
I was able to succesfully root to Clockwork Recovery so i though flashing another firmware to turn the Note into a European one instead of Chinese would be easy too. WRONG!!
Every time i want to flash with Odin it fails in the beginning of the process, see below:
Is there anyone who could comment me on what to do? I was able to recover from the failed flash attempt but i really want to flash another firmware from Europe for this Chinese version.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXCLL3_N8000OXECLL1_N8000XXCLL1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> modem.bin
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried already two different Firmwares but both seem to fail at the same point. I only installed the USB drivers not KIES so i guess it is not the reason.
Any help what is going wrong or what i should try to do?
Thanks a lot far any help.
Dave
Usual reply would be a faulty firmware file download another .
Other reply would usually be try a different Odin try different motherboard usb port .
A guess is that Chinese one is somehow different if nothing works .
jje
JJEgan said:
Usual reply would be a faulty firmware file download another .
Other reply would usually be try a different Odin try different motherboard usb port .
A guess is that Chinese one is somehow different if nothing works .
jje
Click to expand...
Click to collapse
Hi, thanks for your comment although it does not help me much.
I tried already 2 different firmwares which seemed to work with others and also tried different USB port.
As i mentioned both firmwares fail when reaching modem.bin however because the second firmware flashed in a different sequence doing the system.img before modem.bin it somehow added all the google apps on it and working so that's good news as it was not present before.
The PDA also shows the correct flashed version but CSC shows unkown now.
Anyway i want to be able to flash without any failures.
Also i thought that Galaxy Note 10.1 GT-N8000 would be the same nomather if its from China or elsewhere, just the firmware.
Now i'm stuck with what it seems a working Note with Google apps but with CSC unknown.
I still hope someone had this before and solved it.
Thanks for any comments.
davaze said:
Hi, thanks for your comment although it does not help me much.
I tried already 2 different firmwares which seemed to work with others and also tried different USB port.
As i mentioned both firmwares fail when reaching modem.bin however because the second firmware flashed in a different sequence doing the system.img before modem.bin it somehow added all the google apps on it and working so that's good news as it was not present before.
The PDA also shows the correct flashed version but CSC shows unkown now.
Anyway i want to be able to flash without any failures.
Also i thought that Galaxy Note 10.1 GT-N8000 would be the same nomather if its from China or elsewhere, just the firmware.
Now i'm stuck with what it seems a working Note with Google apps but with CSC unknown.
I still hope someone had this before and solved it.
Thanks for any comments.
Click to expand...
Click to collapse
perhaps a different version of ODIN? just spit balling here
EDIT: oops jje already said that, wipe cache, dalvik, factory reset??
davaze said:
Anyway i want to be able to flash without any failures.
No such animal exists .
Also i thought that Galaxy Note 10.1 GT-N8000 would be the same nomather if its from China or elsewhere, just the firmware.
Lot different / fake / clone stuff from China posted on XDA that does not update flash or root properly .
Now i'm stuck with what it seems a working Note with Google apps but with CSC unknown.
CSC is not required to use a phone enter APN settings manually .
Try CSC changer from the market .
jje
Click to expand...
Click to collapse
JJEgan said:
davaze said:
Anyway i want to be able to flash without any failures.
No such animal exists .
Also i thought that Galaxy Note 10.1 GT-N8000 would be the same nomather if its from China or elsewhere, just the firmware.
Lot different / fake / clone stuff from China posted on XDA that does not update flash or root properly .
Now i'm stuck with what it seems a working Note with Google apps but with CSC unknown.
CSC is not required to use a phone enter APN settings manually .
Try CSC changer from the market .
jje
Click to expand...
Click to collapse
Hi thanks for your comments!
Is there anyway to flash without modem.bin? What does modem.bin include?
Rooting the device works with no problem, installed the clockwork recovery and SU succesfully.
When trying the CSC changer it gives me no options.
The device seems to work normal but i must say that i never cleared any cache before starting to flash. The reason is that in some tutorials it is not mentioned unitl after the flashing completed. Also i'm a little affraid now to try it before flashing because i don't know what will happen if it fails again and i cleared cache etc. before.
I'm still hoping someone experienced the same issue and found a reason or solution to this. Untill now i'll do nothing as it seems to work inlcuding the google apps. Not sure if the unknown CSC will cause any issues in the future with specific functions though.
Will keep following this topic to hopefully find someone with similar experience.
Thanks to all that leave some help or comments!
Click to expand...
Click to collapse
Modem.bin is the radio you use to make and receive calls, use 3g internetsms and mms with. You should be able to flash a separate modem.bin file either through cwm or through ODIN...
I have similar issue. My tablet crashed outta nowhere when peel remote tried updating. My tablet never been unlocked or rooted. It stays stuck on nite 10.1 boot screen. Tried using Odin to reflash firmware. But it gets stuck on "NAND Write". I've left it there for hours/all night. I'm pissed because my tablet has performed flawless up till this point.
ODIN recognizes and confirms it connected/communicating. I properly unzipped firmware to show file with proper extension needed for flashing.
Can anyone give any insight or help. Or else I will have to call customer service since I'm still coveted under 1yr. Manufacturer warranty. I have so many pics n video of family on it. I really hope I don't loose anything. I may to try to install Odin on my second laptop to see if it makes a difference.
demandarin said:
I have similar issue. My tablet crashed outta nowhere when peel remote tried updating. My tablet never been unlocked or rooted. It stays stuck on nite 10.1 boot screen. Tried using Odin to reflash firmware. But it gets stuck on "NAND Write". I've left it there for hours/all night. I'm pissed because my tablet has performed flawless up till this point.
ODIN recognizes and confirms it connected/communicating. I properly unzipped firmware to show file with proper extension needed for flashing.
Can anyone give any insight or help. Or else I will have to call customer service since I'm still coveted under 1yr. Manufacturer warranty. I have so many pics n video of family on it. I really hope I don't loose anything. I may to try to install Odin on my second laptop to see if it makes a difference.
Click to expand...
Click to collapse
ODIN 3.07 didn't work for me, switched to 3.04 and that worked, not sure the version you have
I have rooted, unrooted and flashed a bit on mine with no issues, you seem to have attention to detail, but just make sure it's the right firmware for your model some folks have flashed regular galaxy tab ROMs with tragic results
EDIT: does KIES recognize it?
Ill check which version I have. Nit sure. I do have the correct firmware for 8013 model.
Kies doesn't recognize it in regular mode anymore. Now if I put the tablet in recovery/download mode, it recognizes but hangs on connecting. Before I never had issue with kies. I was gonna try restore through lies but since it didn't work, I went Odin route. Now Odin recognizes and confirms its linked/communicating with tablet in download mode. The process starts off good then stops on "nand write". Ill try different version of Odin to see if that works.
Thanks for reply. I hope I can recover it.
edit: my version says Odin3 v1.85
where do i find the newer ones or the ones you used? i got mines from the sticky thread i believe.
update: i found the other versions. i tried 3.04. it got passed Nand Write start. but then said failed. it went straight from nand write to operation failed. i didnt see the other stuff in between like op has. at least its progress..lol ill try again then try a different usb port. if those still dont work then ill try to download another firmware file from somewhere. anyone has a link to latest jellybean firmware for 8013 model? one thats known to work.
demandarin said:
Ill check which version I have. Nit sure. I do have the correct firmware for 8013 model.
Kies doesn't recognize it in regular mode anymore. Now if I put the tablet in recovery/download mode, it recognizes but hangs on connecting. Before I never had issue with kies. I was gonna try restore through lies but since it didn't work, I went Odin route. Now Odin recognizes and confirms its linked/communicating with tablet in download mode. The process starts off good then stops on "nand write". Ill try different version of Odin to see if that works.
Thanks for reply. I hope I can recover it.
edit: my version says Odin3 v1.85
where do i find the newer ones or the ones you used? i got mines from the sticky thread i believe.
update: i found the other versions. i tried 3.04. it got passed Nand Write start. but then said failed. it went straight from nand write to operation failed. i didnt see the other stuff in between like op has. at least its progress..lol ill try again then try a different usb port. if those still dont work then ill try to download another firmware file from somewhere. anyone has a link to latest jellybean firmware for 8013 model? one thats known to work.
Click to expand...
Click to collapse
does auto play pop up when you plug the tablet in? that's how I manage my media anyway. I only use KIES if I have to, only recognizes the note like every third time I plug it in. and it says that my gs3 is unsupported. I feel like the Samsung drivers get screwy sometimes
EDIT: just curious can you get into recovery mode?
jaydubbbbs said:
does auto play pop up when you plug the tablet in? that's how I manage my media anyway. I only use KIES if I have to, only recognizes the note like every third time I plug it in. and it says that my gs3 is unsupported. I feel like the Samsung drivers get screwy sometimes
EDIT: just curious can you get into recovery mode?
Click to expand...
Click to collapse
i get the notification thing on computer going off only when tablet is in recovery mode. by recovery mode you mean by pressing power and volume down at same time. then when it gets on warning screen you press volume up. then it goes into ODIN/Downloading mode. i can get there. i tried 3.04 and 3.07. both give me same deal. After Nand Write goes through its paces then itll say all threads or operations complete. Write Nand Failed. then itll show Failed up top in that other box also. i tried different usb ports also. so not sure what in the world is the deal. the firmware i got from the official firmware download thread. then i got the one for 8013. its a zip. i extracted it so the file with proper md5 extension would be visible.
before all this, i had no issues with KIES with my Note 10.1 or SG3. now KIES wont recognize it. Only ODIN will, once tablet is in ODIN MODE.
demandarin said:
i get the notification thing on computer going off only when tablet is in recovery mode. by recovery mode you mean by pressing power and volume down at same time. then when it gets on warning screen you press volume up. then it goes into ODIN/Downloading mode. i can get there. i tried 3.04 and 3.07. both give me same deal. After Nand Write goes through its paces then itll say all threads or operations complete. Write Nand Failed. then itll show Failed up top in that other box also. i tried different usb ports also. so not sure what in the world is the deal. the firmware i got from the official firmware download thread. then i got the one for 8013. its a zip. i extracted it so the file with proper md5 extension would be visible.
before all this, i had no issues with KIES with my Note 10.1 or SG3. now KIES wont recognize it. Only ODIN will, once tablet is in ODIN MODE.
Click to expand...
Click to collapse
recovery is hold power and volume up, I added a pic of what it looks like. A factory reset will erase everything on your tablet. I'm not a pro, but thats why I asked if you could access the tablets files through auto play
EDIT: I need to learn ADB there might be a way to fix your problem through that. wish I could be more helpful
EDIT 2: it always takes me a couple times to get into recovery, it seems to be a timing thing
jaydubbbbs said:
recovery is hold power and volume up, I added a pic of what it looks like. A factory reset will erase everything on your tablet. I'm not a pro, but thats why I asked if you could access the tablets files through auto play
EDIT: I need to learn ADB there might be a way to fix your problem through that. wish I could be more helpful
EDIT 2: it always takes me a couple times to get into recovery, it seems to be a timing thing
Click to expand...
Click to collapse
ok...nope...cant reach that screen. when i try it tells me "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" only mode that works is ODIN mode from pressing power and volume down.
hmm....i kinda know how to adb from my Nexus7 usage as i recovered one of my n7 that had a similar crash. but i havent seen a guide or whatever for commands to enter in for galaxy note 10.1. or any kind of tool like n7 has. ill check the other tools i have loaded as i think some were capatilble with more than one device. ill keep trying to see if i can get in recovery mode. i had redownloaded and extracted the correct firmware. so ima see if that changes anything.
demandarin said:
ok...nope...cant reach that screen. when i try it tells me "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again" only mode that works is ODIN mode from pressing power and volume down.
hmm....i kinda know how to adb from my Nexus7 usage as i recovered one of my n7 that had a similar crash. but i havent seen a guide or whatever for commands to enter in for galaxy note 10.1. or any kind of tool like n7 has. ill check the other tools i have loaded as i think some were capatilble with more than one device. ill keep trying to see if i can get in recovery mode. i had redownloaded and extracted the correct firmware. so ima see if that changes anything.
Click to expand...
Click to collapse
like I said, it takes me like three tires to get the timing on the recovery mode. wish I knew more, good luck!
since i cant get into recovery, i tried using ODIN to reflash stock recovery. everything goes fine at first. then it says Write failed. for some reason anything i try to write to my tablet is failing. i see in odin 3.07 version they have an option called Nand erase/reset or something. i guess thats to erase everything i have on NAND. but i thinking that would clean tablet clean of everything. do you know anything about that option?
just tried a second time to flash stock recovery. its failing. i think i might be left with no choice but to call samsung customer service for a warranty claim.
this is crazy because my tablet was pure stock. no root or unlocking. and a simple update of that damned peel remote app crashed my $%^^ and put it in the state its in now. this is the only issue ive ever had since owning the tablet since summer time. makes no sense!
i appreciate the ideas though.
demandarin said:
since i cant get into recovery, i tried using ODIN to reflash stock recovery. everything goes fine at first. then it says Write failed. for some reason anything i try to write to my tablet is failing. i see in odin 3.07 version they have an option called Nand erase/reset or something. i guess thats to erase everything i have on NAND. but i thinking that would clean tablet clean of everything. do you know anything about that option?
just tried a second time to flash stock recovery. its failing. i think i might be left with no choice but to call samsung customer service for a warranty claim.
this is crazy because my tablet was pure stock. no root or unlocking. and a simple update of that damned peel remote app crashed my $%^^ and put it in the state its in now. this is the only issue ive ever had since owning the tablet since summer time. makes no sense!
i appreciate the ideas though.
Click to expand...
Click to collapse
No idea about the NAND options, ODIN 3.07 didn't work for me, I have 3.04 and haven't used it since I updated to 4.1.2. That sucks that the peel update borked your %¢#! . Especially because it's a stock app! I updated peel about a week ago with no issue. Not being able to get into recovery is probably a bad sign. I keep hoping someone smarter than I would chime in. I hope Samsung takes care of you
thank you for the suggestion to use another version of ODIN....i have been screwing with this for a day and half thinking that every version of stock rom that i tried was broken in some way....turned that ODIN v3.07 does not work so well...found ODIN v3.04 and worked perfectly.
Recovery mode is easy, from power off hold down volume up and power. Hold both buttons in until you see the samsung logo, release power but keep holding volume up until recovery appears... Works everytime...
Same problem - half solved
davaze said:
Hi,
I'm trying to flash another firmware for my GIalaxy Note 10.1 N8000. I have read all tutorials etc. and prepared all according to it.
I was able to succesfully root to Clockwork Recovery so i though flashing another firmware to turn the Note into a European one instead of Chinese would be easy too. WRONG!!
Every time i want to flash with Odin it fails in the beginning of the process, see below:
Is there anyone who could comment me on what to do? I was able to recover from the failed flash attempt but i really want to flash another firmware from Europe for this Chinese version.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXCLL3_N8000OXECLL1_N8000XXCLL1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> modem.bin
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried already two different Firmwares but both seem to fail at the same point. I only installed the USB drivers not KIES so i guess it is not the reason.
Any help what is going wrong or what i should try to do?
Thanks a lot far any help.
Dave
Click to expand...
Click to collapse
Hi Dave and all
I am i EXACTLY the same situation - Just bought n8000 in china with chinese firmware and wanted to change for European. I encounterted the same problem.
After formum research and many tests of softwares/ usb ports/ odin versions. I got to a point when after crashing during instalation (like in davids situation) i couldnt turn on the device anymore (black screen saying that i should do recovery via kies)
I installed CWM via Odin and it helped.
The tablet started again with european system and applications and seemd to work well.
UNFORTUNATELY: The S note is crashing before it's even loaded and while using tablet i experiece lags for ex when typing address in internet app.
I made a factory reset and cleaned cache - still nothing.
Please help if you have any ideas.
David: How did you managed to solve your problem? Did you managed to finish the update withou a crash?
Best regards
Filip
After trying unsuccessfully for 6hrs to unlock and root my new S3, i finally found this thread. i just got this phone in the mail from my insurance plan. I had just unlocked and unrooted without any problem on the last phone i got a few months ago. i have no idea what version this phone was on before i tried flashing and i can't see now either but after seeing that thread I'm suspecting vrucml1. whenever i press the power button i get a "Firmware upgrade encountered an issue. Please use Software Repair assistant and try again."
As i was trying to flash images odin kept getting hung up at
Code:
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Also, i am able to get into a stock recovery. don't know if that makes a difference or not.
After reading that discussion i linked, i'm afraid i may have bricked my phone bc i can't seem to even get it to boot past the error screen. If this thing is bricked, I'm seriously switching carriers. Can somebody help?
I've been running the latest Darthstalker rom on my T-mobile Galaxy Note 5 (SM-N920T). After midnight New Years.. I powered the phone off and then later powered it on and I get this message Custom Binary Blocked by FRP Lock. I can't mount anything via my WIndows laptop and I can't get into Recovery. Since it's a note 5 I can't even open it to get the serial number or any thing or pull the SIM chip. I've seen some posts telling me to use Kies 3 and some saying using Odin to install stock and reroot. A lot of these posts seem to have been using Darthstalker as a ROM.
Is there any path I can follow that will allow me to get back and up and running without data loss? What's the best steps to take?
Thanks in advance and Happy New Years XDA!
mryanmarkryan said:
I've been running the latest Darthstalker rom on my T-mobile Galaxy Note 5 (SM-N920T). After midnight New Years.. I powered the phone off and then later powered it on and I get this message Custom Binary Blocked by FRP Lock. I can't mount anything via my WIndows laptop and I can't get into Recovery. Since it's a note 5 I can't even open it to get the serial number or any thing or pull the SIM chip. I've seen some posts telling me to use Kies 3 and some saying using Odin to install stock and reroot. A lot of these posts seem to have been using Darthstalker as a ROM.
Is there any path I can follow that will allow me to get back and up and running without data loss? What's the best steps to take?
Thanks in advance and Happy New Years XDA!
Click to expand...
Click to collapse
If you can't even mount it on Windows or get into recovery that's not good.
True Dat!
MrMike2182 said:
If you can't even mount it on Windows or get into recovery that's not good.
Click to expand...
Click to collapse
The other examples I read said the same thing.. at this point I'm going to try to find a stock and odin it and root again and see if I even get my files back.. Unless someone has a better idea?
mryanmarkryan said:
The other examples I read said the same thing.. at this point I'm going to try to find a stock and odin it and root again and see if I even get my files back.. Unless someone has a better idea?
Click to expand...
Click to collapse
I would suggest pushing the root kernel to it anyway just to see if it will go.. I do have an FRPbypass but it's an apk meaning you need to install it and if you cannot mount to push it and then try to do adb shell pm install FRPbypass.apk then there's no point in that either.. Can you even get into download mode? If not the last thing I could suggest is the PIT file to repartition it. Unless someone else has a better idea? I do have the PIT file for odin too.
Also I think you're past the point of losing your data and if you can hold the volume down button and power button at the same time until it shuts off and turns back on again you can select factory reset and that's going to ruin all data..
My god, this happened to me on my first Note 5 I had. I was trying to restore it to stock before selling it and like an asshole I forgot to check for "OEM Unlock" and ran into that exact message. It put the fear of god into me. Like you I didn't have the serial number written down and I couldn't get it from anywhere. T-Mobile tech reps tried to tell me the IMEI number acts as a serial number, cool, that doesn't help me. I gave up on Kies and just played around with Odin after I was FINALLY able to find a stock firmware. I can't believe how difficult that was to get. I managed to flash the stock firmware thru Odin and I got the phone back! Stock as it came out the box.
I can't remember how I was able to get it into download mode but whatever button order I kept trying I finally did because Odin recognized the mofo and I flashed that stock firmware as fast as I could. It rebooted and I saw that beautiful stock welcome screen once more. Try to do this, I didn't need to do anything else.
For this reason I now keep a copy of stock firmware along with screen shot of my phone's status screen showing the serial number and everything else. All that's backed up to one of my external drives. Alone with several nandroid backups of various stages of owning this second Note 5 I have now. I'm running V10 of Darthstalker but I haven't heard of other users running into FRP lock. That would mean something tripped their OEM unlock option but how would that happen without you doing it? Is there something inside the ROM (a bug) that's tripping the option in Developer Options?
Best of luck with this, I know how stressful this can be. As far as getting your data back, yeah that's likely a no go. At this point you should be hopeful of getting a working phone back, let alone recover any personal data. Hope you can sort this.
More Info
MrMike2182 said:
If you can't even mount it on Windows or get into recovery that's not good.
Click to expand...
Click to collapse
I can get it into download mode.. just not into recovery. The only thing I can think I did was I changed my password about 4 days ago to google. I don't have any screen security setup so that is not a factor. Last night we were trying to figure out how to push Gear VR to a tv so everyone could watch and I recall disabling (by mistake) the developer options and then re-enabling it. I also turned on a secondary screen option and later turned it off. SO who knows? I do have a twrp backup on a sim so I'm going to go ahead and try to get stock going and so on.. Keep ya posted..
mryanmarkryan said:
I can get it into download mode.. just not into recovery. The only thing I can think I did was I changed my password about 4 days ago to google. I don't have any screen security setup so that is not a factor. Last night we were trying to figure out how to push Gear VR to a tv so everyone could watch and I recall disabling (by mistake) the developer options and then re-enabling it. I also turned on a secondary screen option and later turned it off. SO who knows? I do have a twrp backup on a sim so I'm going to go ahead and try to get stock going and so on.. Keep ya posted..
Click to expand...
Click to collapse
Yeah if you can get it into download mode and you've got the stock firmware you should be good to go and flash tru Odin. That's key. If I were you I'd be like, "To hell with my personal data! Get me a working phone back!".
Good luck.
{
"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"
}
mryanmarkryan said:
I can get it into download mode.. just not into recovery. The only thing I can think I did was I changed my password about 4 days ago to google. I don't have any screen security setup so that is not a factor. Last night we were trying to figure out how to push Gear VR to a tv so everyone could watch and I recall disabling (by mistake) the developer options and then re-enabling it. I also turned on a secondary screen option and later turned it off. SO who knows? I do have a twrp backup on a sim so I'm going to go ahead and try to get stock going and so on.. Keep ya posted..
Click to expand...
Click to collapse
Ohh I see what you did now and unfortunately all your data is gone because there's only one way to fix this now and that's to either flash TWRP again and then re-flash the rom you want or use odin to flash stock firmware to at least get your phone going.. The mistake you made was disabling developer options which in turn, turned around and re-disabled oem unlock and turned debugging off.. Never ever turn that off while using a custom rom and kernel!!
MrMike2182 said:
Ohh I see what you did now and unfortunately all your data is gone because there's only one way to fix this now and that's to either flash TWRP again and then re-flash the rom you want or use odin to flash stock firmware to at least get your phone going.. The mistake you made was disabling developer options which in turn, turned around and re-disabled oem unlock and turned debugging off.. Never ever turn that off while using a custom rom and kernel!!
Click to expand...
Click to collapse
Ahhh that makes sense.. never heard of the FRP feature until now though.. oh well.. So far I've tried flashing TWRP (failed) and tried flashing a stock rom.. (failed).. I was using Odin 3.10.6
I'll keep at it..
mryanmarkryan said:
Ahhh that makes sense.. never heard of the FRP feature until now though.. oh well.. So far I've tried flashing TWRP (failed) and tried flashing a stock rom.. (failed).. I was using Odin 3.10.6
I'll keep at it..
Click to expand...
Click to collapse
Try downloading the newest odin version sometimes that can help.. Can you tell me how it's failing? Like what exactly happens when you try to do all the flashing? Did you try the adb commands that I suggested? You only need to install minimal adb and Fastboot on the windows pc and then connect your device and then open a terminal in the same exact folder where adb and Fastboot were installed and then type Fastboot devices or adb devices if it give you a bunch of numbers it means that it can see the device and we can then manually push and install the firmware. The other thing I suggest you try to do is flash the Lollipop 5.1 T-mobile firmware because I think it doesn't have frp on it yet and before flashing it go into the actual firmware you downloaded and delete cm.bin then rezip the firmware again and flash that one without the cm.bin but first try flashing the entire firmware as is with the md5 and all before resorting to deleting cm.bin.. Don't try flashing the Marshmallow 6 rom because that's where they started that frp bullcrap if you ask me. FRP stands for Factory Reset Protection... I understand the need for it and it's importance but Google could have been a lot more open about it and explaining to its customers what it's for and what it does not just do it and let most of us learn the hard way!!
When you try to flash in Odin tell me what file it fails on.
If none of this works this page is your last bet buddy
https://www.sammobile.com/forum/showthread.php?t=31136
I'm working on it now! Give you guys a summary of what happened as I as check off your suggestions..
SO far I have the ADB and Fastboot installed (found the link on XDA). However, when I plug my phone in and issue adb devices or fastboot device it does not show. I did also hook up a note II which is my older phone. It used to be rooted and had ROMs installed but I snafued it up one day and didn't bother with it. It says System software not authorized by Verizon Wireless has been found on your phone.. blah blah.. SO that phone doesn't appear in adb devices either.. I've already updated and re-installed the samsung drivers.. Shouldn't the Note II have shown up? There is no FRP for that old model..
I"ve also got Odin and am currently downloading the 5.1.1 firmware.. the free way lol
Progress!
mryanmarkryan said:
SO far I have the ADB and Fastboot installed (found the link on XDA). However, when I plug my phone in and issue adb devices or fastboot device it does not show. I did also hook up a note II which is my older phone. It used to be rooted and had ROMs installed but I snafued it up one day and didn't bother with it. It says System software not authorized by Verizon Wireless has been found on your phone.. blah blah.. SO that phone doesn't appear in adb devices either.. I've already updated and re-installed the samsung drivers.. Shouldn't the Note II have shown up? There is no FRP for that old model..
I"ve also got Odin and am currently downloading the 5.1.1 firmware.. the free way lol
Click to expand...
Click to collapse
I was able to install the 5.1.1 firmware and it reboots, has tmobile's (or samsung's) recovery and boots to a TMOBILE logo and stops. Thinking it is not rooted anymore and Perhaps I should try to re-root.. I did try to install twrp and it failed.. Twrp 2.8.7.1 alpha.. and also the most recent..
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Advice?
I'm afraid I'm thrashing around at this point. I have the firmware for 5.1.1 installed. It boots to a tmobile logo and stops. I can get into the default recovery. I can't flash twrp.. I still can't get my files mounted via USB.. Perhaps I need to do a wipe data / factory reset? Also because I know you are gonna ask, adb still does not list any devices, nor does fastboot..
mryanmarkryan said:
I was able to install the 5.1.1 firmware and it reboots, has tmobile's (or samsung's) recovery and boots to a TMOBILE logo and stops. Thinking it is not rooted anymore and Perhaps I should try to re-root.. I did try to install twrp and it failed.. Twrp 2.8.7.1 alpha.. and also the most recent..
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
mryanmarkryan said:
I'm afraid I'm thrashing around at this point. I have the firmware for 5.1.1 installed. It boots to a tmobile logo and stops. I can get into the default recovery. I can't flash twrp.. I still can't get my files mounted via USB.. Perhaps I need to do a wipe data / factory reset? Also because I know you are gonna ask, adb still does not list any devices, nor does fastboot..
Click to expand...
Click to collapse
Your gonna have to flash the LATEST 6.0.1 ROM and firmware thru Odin. I don't think 5.1.1 will boot your phone up completely.
mryanmarkryan said:
I'm afraid I'm thrashing around at this point. I have the firmware for 5.1.1 installed. It boots to a tmobile logo and stops. I can get into the default recovery. I can't flash twrp.. I still can't get my files mounted via USB.. Perhaps I need to do a wipe data / factory reset? Also because I know you are gonna ask, adb still does not list any devices, nor does fastboot..
Click to expand...
Click to collapse
It stopped right while trying to flash the recovery part of it so here's what I suggest you try to do.. unzip the 5.1.1 firmware you downloaded and unzip it again until you can see all the files in it and then manually flash them 1 by 1 in the AP slot but don't allow the phone to auto reboot uncheck that option and after 1 files flashed hold the volume down button and power button until you can select shut down device or turn off whichever then again hold the buttons to get into download mode again and continue until they are all flashed and then finally again hold the volume down button and power button and when it comes back on then select factory reset.
---------- Post added at 08:31 PM ---------- Previous post was at 08:28 PM ----------
E-POUND said:
Your gonna have to flash the LATEST 6.0.1 ROM and firmware thru Odin. I don't think 5.1.1 will boot your phone up completely.
Click to expand...
Click to collapse
If he flashes the latest firmware with the security updates he can never go back to 5.1.1 so I don't suggest he do that yet
Ok, potentially some progress.. I flashed all the .bin files . Then I converted all the img files to tar.md5 and flashed those including the recovery and system.img. I rebooted the phone into download each time. Afterwards I rebooted and it did a system update icon for a bite and then the samsung animation.. Now it's at t-moile.. and sitting. I'll let it sit for a while.. maybe it's just rebuilding the cache.. I didn't see an option for factory reset, but I could go into recovery and do it there?
Update: It finally rebooted and has done so 3 times after sitting at the T Mobile (white screen) ..
Update2: I tried to flash the contents of file twrp-3.0.2-0-nobleltetmo.img.tar.. it failed so I extracted the recovery.img file and converted it back to tar.md5 (I know probably just a circle). It failed too..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Does this mean I'm not rooted anymore?
mryanmarkryan said:
Ok, potentially some progress.. I flashed all the .bin files . Then I converted all the img files to tar.md5 and flashed those including the recovery and system.img. I rebooted the phone into download each time. Afterwards I rebooted and it did a system update icon for a bite and then the samsung animation.. Now it's at t-moile.. and sitting. I'll let it sit for a while.. maybe it's just rebuilding the cache.. I didn't see an option for factory reset, but I could go into recovery and do it there?
Update: It finally rebooted and has done so 3 times after sitting at the T Mobile (white screen) ..
Update2: I tried to flash the contents of file twrp-3.0.2-0-nobleltetmo.img.tar.. it failed so I extracted the recovery.img file and converted it back to tar.md5 (I know probably just a circle). It failed too..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1101)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Does this mean I'm not rooted anymore?
Click to expand...
Click to collapse
You're not rooted at all right now but you should not have needed to turn the imgs back into md5s again you should have just flashed them the way they were they don't need md5 just to flash. Try holding the volume down button and power button until it shuts off and turns back on again then select factory reset if that doesn't work then go into download mode again and connect to a Windows pc and use Smart Switch to try and fix it.
The reason I converted them was because Odin wouldn't find the files.. I tried just running them by typing a *.img but it didn't work. I'll go read about smart switch.. I"m learning stuff here
Update,: On a hunch I went back and ran the firmware install again, but just in it's original format. It succeeded and I'm setting up the phone now.. Thanks for your help MrMike. I appreciate you putting the time in..
mryanmarkryan said:
Ahhh that makes sense.. never heard of the FRP feature until now though.. oh well.. So far I've tried flashing TWRP (failed) and tried flashing a stock rom.. (failed).. I was using Odin 3.10.6
I'll keep at it..
Click to expand...
Click to collapse
You are using the wrong stock firmware. Download the DPG1 firmware since that is was darthstalker v.11 is on. If you backed up your ROM then you don't have any troubles at all. Just ODIN back to stock, root, twrp recovery data only and done. But not all at once. First get the firmware going and reboot your phone. Once you know it's working the try rooting. Once you are rooted download TWRP and recover your data only.
Btw - FRP is when you log into your google account in the beginning of the setup so don't do that if you want to flash other ROMs.
P.S. I'be been running Darthstalker v.11 since it came out with no problems.
Software brick on a tab 2(5113) ?? unable to do anything with the "cache" folder...
HiYall, got my tab 2 (5113 and using Candy6 ROM for 5110) that I carry around cause my memory sux. The other night (4 days ago) was transferring some maps onto my tab 2 and I fell asleep, with the tablet unplugged. To wake up with the tablet's battery dead. Of course, the first thing I did was plug it in (3 mornings ago) to find later a nice message saying that encryption failed? I didn't tell it to encrypt. Now, when I boot, I get that message about failed encryption and 2 options; the back arrow (does nothing) or reset the tablet, ok, s'all good, don't care as I did a backup of all the important things 2 days before. Now, I'm okay with full wipe and reinstall. I searched for the last 3 days all over this forum and google search with no solution.
I have TWRP 3.0.0.0 recovery installed
unrooted ages ago
Candy 6 ROM was installed, love it, oc'ed at 1.5ghz, stable, rarely & very little heat.
I also have an OEM ROM 4.2.2, tried to flash it with ODIN, no go, FAIL
tried the Shakatu 4.2.2 ROM as well, same
tried reflashing the Candy 6, same (using TWRP)
always the same, unable to mount /data (invalid argument)
using TWRP, unable to wipe, format, factory reset
unable to change the file system as well in the cache folder as pointed in a great many threads, it's in EXT4 in the candy 6 ROM, tried all the formats available, EXT3, EXT2, FAT, exFAT, F2FS, all the same error, (unable to mount storage).
Don't take me wrong, I know practically nothing about Linux and only followed instructions to the letter on the procedures to do. I only wish to give you the information that is relevant.
Thanks in advance
So,
Big
Can you post the odin log when it fails?
Lightracer said:
Can you post the Odin log when it fails?
Click to expand...
Click to collapse
Would be my pleasure....
This is the ROM I have:
HTML:
P5113UEUCMK3_P5113XACCND2_HOME.tar.md5
and here is the most recent log, running the flash as I'm typing this...
HTML:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1205)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> Sbl.bin
<ID:0/005> system.img
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Judging by the green process bar, seem to be at 40something% - 45% maybe???
"Auto Reboot" & "F. Reset Time" are the only boxes ticked on
I also tried the stock bootloader, pit & kernel to no avail... but this log is with AP only...
HTML:
P5110_JB_SBL.tar.md5
signed_espresso_20120220_16G.pit
espresso-any-root-kernel.tar.md5.zip
I also tried ADB, Simple and full install, none of it successful and I didn't mention that I also killed Skies...
oh yeah, am also using an OEM Samsung cable and running Odin as admin, firewall & AV are off...
diesel13 said:
Would be my pleasure....
This is the ROM I have:
P5113UEUCMK3_P5113XACCND2_HOME.tar.md5
and here is the most recent log, running the flash as I'm typing this...
<ID:0/005> Added!!<OSM> Enter CS for MD5..<OSM> Check MD5.. Do not unplug the cable..<OSM> Please wait..<OSM> Checking MD5 finished Sucessfully..<OSM> Leave CS..<ID:0/005> Odin engine v(ID:3.1205)..<ID:0/005> File analysis..<ID:0/005> SetupConnection..<ID:0/005> Initialzation..<ID:0/005> Get PIT for mapping..<ID:0/005> Firmware update start..<ID:0/005> SingleDownload.<ID:0/005> Sbl.bin<ID:0/005> system.img<ID:0/005> Complete(Write) operation failed.<OSM> All threads completed. (succeed 0 / failed 1)
Judging by the green process bar, seem to be at 40something% - 45% maybe???
"Auto Reboot" & "F. Reset Time" are the only boxes ticked on
I also tried the stock bootloader, pit & kernel to no avail... but this log is with AP only...
P5110_JB_SBL.tar.md5signed_espresso_20120220_16G.pitespresso-any-root-kernel.tar.md5.zip
I also tried ADB, Simple and full install, none of it successful and I didn't mention that I also killed Skies...
oh yeah, am also using an OEM Samsung cable and running Odin as admin, firewall & AV are off...
Click to expand...
Click to collapse
The only thing i can think of is that your system partition seems to be corrupted because Odin failed to flash the system image. Some of our devices have the emmc brickbug which can make the device not boot or do anything (sudden death) or have corrupted partitions. I think the only way to fix it is to either have the motherboard replaced or update the emmc firmware. I might be wrong though but the symptoms and the logs do suggest it could be the emmc brickbug. (Unless your kernel has been patched which fixes this bug)
Lightracer said:
The only thing I can think of is that your system partition seems to be corrupted because Odin failed to flash the system image. Some of our devices have the emmc brickbug which can make the device not boot or do anything (sudden death) or have corrupted partitions. I think the only way to fix it is to either have the motherboard replaced or update the emmc firmware. I might be wrong though but the symptoms and the logs do suggest it could be the emmc brickbug. (Unless your kernel has been patched which fixes this bug)
Click to expand...
Click to collapse
ok, so I reflashed the Kernel I mentioned higher, it passed in Odin, however, when I rebooted, all was the exact same. trying to reflash the most recent publication of the 4.2.2 Samsung ROM, we'll see... edit: just finished and it's a big "O fat failed... "I'll repost the results, thanks a bunch, oh well, if it's dead, it's dead time to blow some money and get another tablet, was thinking of the Chuwi hi13, should do well for me, got very little requirement for power, just want a clear clean large screen to be able to read, check the news and play some Klondike solitaire.
:crying:
diesel13 said:
ok, so I reflashed the Kernel I mentioned higher, it passed in Odin, however, when I rebooted, all was the exact same. trying to reflash the most recent publication of the 4.2.2 Samsung ROM, we'll see... edit: just finished and it's a big "O fat failed... "I'll repost the results, thanks a bunch, oh well, if it's dead, it's dead time to blow some money and get another tablet, was thinking of the Chuwi hi13, should do well for me, got very little requirement for power, just want a clear clean large screen to be able to read, check the news and play some Klondike solitaire.
:crying:
Click to expand...
Click to collapse
Maybe all hope is not lost yet. Have you tried reflashing twrp? :fingers-crossed:
Lightracer said:
Maybe all hope is not lost yet. Have you tried reflashing twrp? :fingers-crossed:
Click to expand...
Click to collapse
nope, didn't even think of that, will try it right now, let you know how it goes
ok ,so here we are...
downloaded the latestTWRP, CMW and Philz(pretty old)
twrp-3.1.0-0-p5110.img
CWM Recovery v6.0.3.6.tar
philz_touch_6.57.8-p5110.tar.md5
Click to expand...
Click to collapse
tried all 3 via ADB and Odin
via ADB, transfer does not progress
via Odin, success but still reboots in TWRP 3.0.0.0
diesel13 said:
nope, didn't even think of that, will try it right now, let you know how it goes
ok ,so here we are...
downloaded the latestTWRP, CMW and Philz(pretty old)
tried all 3 via ADB and Odin
via ADB, transfer does not progress
via Odin, success but still reboots in TWRP 3.0.0.0
Click to expand...
Click to collapse
Well I'm out of ideas, time to get a new tablet I guess ✌
Lightracer said:
Well I'm out of ideas, time to get a new tablet I guess
Click to expand...
Click to collapse
Well I do appreciate your input and am yuppin' a big Kudos and Thank You, Life is Life, we'll all go at some points, the tablets just get there first
Thanks Lightracer :highfive: