[Q&A] Hyperdrive Rom Note 10.1 2014 ║ Non-Development Discussion ║ Support

Zionator

Senior Member
Jan 28, 2009
2,120
640
198
Birmingham
www.Infowars.com
I was recently facing that the tablet wouldn't wake up from deepsleep so I thought it was something I installed that was causing it. After a fresh refalsh of this ROM and of course a full wipe including the internal SD I was still facing this issue so then I tried flashing another ROM like the cm lollipop ROM but was still having the same issue and now I have to hold the power button down until it reboots every time I want to use the tablet.

Does anyone know what is causing this issue ?
I really would like to get this problem fixed before hyperdrive 5 is released ;(
 

mikep2323

Senior Member
Dec 14, 2011
626
180
43
I was recently facing that the tablet wouldn't wake up from deepsleep so I thought it was something I installed that was causing it. After a fresh refalsh of this ROM and of course a full wipe including the internal SD I was still facing this issue so then I tried flashing another ROM like the cm lollipop ROM but was still having the same issue and now I have to hold the power button down until it reboots every time I want to use the tablet.

Does anyone know what is causing this issue ?
I really would like to get this problem fixed before hyperdrive 5 is released ;(
What kernel are you using? I had the same problem when I used xulocso kernel. After going back to stock kernel the problem went away. If your using stock kernel I don't know what the problem is.
 
  • Like
Reactions: Zionator

evetsnameloc

Member
Nov 3, 2014
15
2
0
67
Colorado Springs
"Your device is not compatible with this version."

I have had an odd problem since installing RLS5. After a clean install, I noticed that a game that I had had installed previously (on RLS4.1), namely "Boggle Free" from EA, failed to be restored after logging into my Google account. When I went to the Play Store to try to reinstall it manually, it told me "Your device is not compatible with this version". I then dirty-flashed RLS4.1 on top of RLS5 after wiping cache and dalvik cache, and was then able to install the game with no problem. I then dirty-flashed RLS5 on top of RLS4.1, again after wiping cache and dalvik cache, and Boggle was there and it ran with no problems.

Any insight into what's going on here?
 

bendjou69

Member
Dec 5, 2014
14
1
0
No intuitive text

Hello, I have no intuitive text on keyboards(each type of keyboard) but intuitive (or predictive...I don't know how to say in english) text is activate. French language.
Any idea?
 
Last edited:

matcoder

Senior Member
Jan 17, 2011
69
2
0
Names of icons are cuted with TW Tab S ....
No problem with TW Note Pro.
Any idea?
Thx for your job!!
Same problem.

I tried to change on xposed appsetting but l can't. Also changed dpi but still cutted icons name

SM-P600 cihazımdan Tapatalk kullanılarak gönderildi
 

¿Will-it-Blend?

Senior Member
May 27, 2013
736
490
0
Atlanta, GA
plus.google.com
Same problem.

I tried to change on xposed appsetting but l can't. Also changed dpi but still cutted icons name

SM-P600 cihazımdan Tapatalk kullanılarak gönderildi
He modded the original Tab S launcher so what you need to do is replace it with the original, unmodified version. First thing you need to do is go into system/priv-app and delete anything that says TW Launcher or has the word Magazine in it. This will get rid of everything related to the modified Tab S launcher. Next download Jazzespresso's Tab S Launcher (link below) and unzip it. There are 3 files you need to move from the priv-app folder in this zip to the priv-app folder on your device:
'MagazineWidget.apk'
'MagazineLauncher.apk'
'MagazineBriefingWidget.apk'

(make sure the original magazine launcher and TW launcher stuff is deleted!!!)

Set permissions and reboot and your good to go! :good:

Tab S Launcher: https://drive.google.com/file/d/0B-r_9_Q4cq6ZeWtISlYybWV5Yjg/view?usp=sharing
 

Athinira

Member
Dec 25, 2013
12
2
0
Wi-Fi issues and UI restarts

ROM generally works VERY well. No battery-drain issues etc. on my P600. I have, however, two bugs to report (currently running RLS 5.1).

1) Wi-Fi networks running channels 12 + 13 cannot be detected
When i installed the ROM (full clean install), i noticed that it couldn't detect my home Wi-Fi network, but saw my neighbours and my phones Wi-Fi hotspot fine.
After twiddling a bit with the settings in my router, i discovered that whenever a Wi-Fi network utilizes Channel 12 and 13 og the 802.11n standard (haven't tested 802.11b/g), the device won't pick up the network. Switching my router to channels 1-11 fixed the issue.

2) The system UI restarts when the tablet is charging and at full battery
Sometimes i charge my tablet and it hits 100%, the system UI keeps crashing, reloading and crashing. The issue stops when i disconnect the charger (original Samsung). I've experienced this running with and without battery mods enabled (only using the ones build into HyperTweaks).

I'll try to get a logcat for problem 2 as soon as I'm able to reproduce the issue again.

Edit: Logcat attached. Dumped after 5 consecutive crashes. There's a crash report on com.android.systemui right at the end of the log.
 

Attachments

Last edited:

sbreen94

Inactive Recognized Developer / Inactive Recognize
Apr 18, 2012
5,292
22,655
0
ROM generally works VERY well. No battery-drain issues etc. on my P600. I have, however, two bugs to report (currently running RLS 5.1).

1) Wi-Fi networks running channels 12 + 13 cannot be detected
When i installed the ROM (full clean install), i noticed that it couldn't detect my home Wi-Fi network, but saw my neighbours and my phones Wi-Fi hotspot fine.
After twiddling a bit with the settings in my router, i discovered that whenever a Wi-Fi network utilizes Channel 12 and 13 og the 802.11n standard (haven't tested 802.11b/g), the device won't pick up the network. Switching my device to channels 1-12 fixed the

2) The system UI restarts when the tablet is charging and at full battery
Sometimes i charge my tablet and it hits 100%, the system UI keeps crashing, reloading and crashing. The issue stops when i disconnect the charger (original Samsung). I've experienced this running with and without battery mods enabled (only using the ones build into HyperTweaks).

I'll try to get a logcat for problem 2 as soon as I'm able to reproduce the issue again.

Edit: Logcat attached. Dumped after 5 consecutive crashes. There's a crash report on com.android.systemui right at the end of the log.
I just tested this and the ui does not force close on me at a full charge on rls5.1. Try reflashing the rom again and see?
 

Athinira

Member
Dec 25, 2013
12
2
0
I just tested this and the ui does not force close on me at a full charge on rls5.1. Try reflashing the rom again and see?
I will at some point (i use the device for work, so reflashing and reconfiguring the settings all the time isn't practical). It's probably some setting at some place that might have screwed things up somewhere. You'll hear from me later. As i said, i love the ROM :)

Were you able to reproduce the Wi-Fi issue?
 
Last edited:

sbreen94

Inactive Recognized Developer / Inactive Recognize
Apr 18, 2012
5,292
22,655
0
I will at some point (i use the device for work, so reflashing and reconfiguring the settings all the time isn't practical). It's probably some setting at some place that might have screwed things up somewhere. You'll hear from me later. As i said, i love the ROM :)

Were you able to reproduce the Wi-Fi issue?
No i haven't been able to as the WiFi is working perfect for me. Sorry buddy
 

mikmock

Senior Member
Dec 16, 2012
87
48
48
Bosque Farms
/EFS HELP!!!

Hello, sbreen94, Xluco & all other Galaxy Guru's Hopefully that raised some eyebrow’s If not: HELP!!!!
I am sorry for such a long post but my brain has turned to mush and I need some guidance.

Short Version: "E: failed to mount /efs (Invalid argument)" Stuck at animated logo screen.

Longer Version:
I have been running Hyperdrive v4.1 with Xluco’s v3 Kernel (Stock FW: NK1) without any issues since I bought my SM-P600 in December. About a month ago I began using Xposed Framework with the Xblast module just for a dark blue “Halo Dark Background”. Again no issues whatsoever.

A couple weeks back I flashed Xluco's V4b3 release (which was working quite well initially). Of course before the kernel flash I uninstalled Xblast/Xposed, backed up with TWRP & Titanium, cleared all caches and then flashed the kernel and all was well.
A couple hours later I installed Xposed & Xblast without incident but when I opened Xblast, I started getting bootloops; everytime I opened xblast. So say good bye to my background, time to back out…

…uninstalled Xblast/reboot (all good)… uninstalled Xposed/reboot (NOT good). After the reboot, it became stuck at the animated Hyperdrive logo. I can boot into Recovery & Download mode and thru all this I still can.

I have tried all my nandroids, including the first one I made after rooting. I then wiped & reflashed Hyperdrive (which lets me go thru the whole aroma procedure) but never boots past the hyperdrive boot screen. I have used the older TWRP 2.6.3.3 and Philz CWM.

Flashed all available stock firmware with Odin3 (1.85, 3.07, 3.09, 3.10.6) and even tried Kies3. All with the same results, except now i have the "Glowing" Samsung Logo. But now at least, I have seen my first error message, Stock Recovery gives me:

"E: failed to mount /efs (Invalid argument)" it now happened the first time & every time I use stock firmware and end up with stock recovery.

So I have tried all kinds of fixes on the internet short of flashing a PIT File which sounds great in theory but several people made their tablets worse & I am not 100% sure I even have the right PIT file. I also have 3 types of /efs backups (.img .tar .zip) the .img & .tar actually show 20MB which according to my searches is correct but never could get anywhere with them, tried EFS Pro & Dr Ketan EFS backup.

I have also tried the ADB fix but no go. The only other thing I can think of is that everything I flash seems to make it on to the tablet. Looking at it with the file manager in recovery.

Since this has turned into a novel I will stop here and beg for help!!! :crying:
I'm sure I left a lot out that I will gladly provide if needed. I am so ready to move on & up to Hyperdrive 5.1!!! I can actually flash it too but it just gets stuck at the logo screen.
I have tried to pull a log of some kind and I either end up with nothing or I get a couple lines saying everything was successful (minus the /efs error)
Thank you for even reading this nightmare & if you have any suggestions that would be EXTREMELY COOL :D

UPDATE: Spoke too soon about the /EFS backups, they were from my N5110. (oh well)
I tried Odin 3.10.6 again because there is a dedicated Tab for "PIT" so i tried to click on it and it came back indicating that if a .pit was required, it would pull it from the CSC portion of the ROM (Huh? first time i had heard that). Anyway, at the time i was trying to flash the brand new "0B2" firmware,. which like all the "XAR" firmware seems to unzip to one single .tar.md5 file So just for the sport, I added OB2 rom into the CSC box in odin. Actually it ran thru the flashing procedure twice and "Error" free. Unfortunatly, didn't do a thing, still at square 1.
At this point my motivation is to fix this tablet, but also to help awareness of this Samsung anomily. I am a hardcore backup freak & it bit me. In my travels since this issue began, I have seen quite a few people unaware of PIT files & /EFS. If anything, maybe someone will take percautions before flashing new firmware.

UPDATE: I don't know if I feel smart or dumb. There was alot of information out there but it was more of a piece meal.
It was mostly old post & Phone related (losing your IMEI)
I also found that using CWM to mount system with ADB worked best, TWRP never seemed to respond to the commands.

So, then i took half of one post:
adb shell
mke2fs /dev/block/mmcblk0p3
then half of another
mount -w -t ext4 /dev/block/mmcblk0p3 /efs
the "/efs" was missing from the first post. I'm not even sure if the last line was necessary.

I rebooted, and everything was back like magic!, no corruption, no factory mode. Just a wiped clean tablet ready for Hyperdrive 5.1.
I guess /efs folder was just lost & luckily all the secret information, including the all important IMEI was intact.
BTW...Hyperdrive 5.1 Rockz! running perfectly.
 
Last edited:
  • Like
Reactions: ezwalker63