I have had some issues with my System Data being HUGE
I have done full on resets, including Dalvik cache and factory reset at recovery mode
It's still 4.38 GB when I look in Settings > Storage
Any ideas why this is happening or a way to eliminate it?
I don't see how Android can be taking up that much space, especially since this is a freshly wiped device.
I've looking into it some more and with DiskUsage and other explorer apps I see that there is 5.8GB of space accounted for, 3.4GB for Storage and 2.42GB for "System"
However, this is an 8GB device. I have gone through the whole thing on file explorers and it seems almost like it isn't even seeing the remaining 2.1GB I should have.
As if another Android system is there but unused or unrecognized.
I have the sprint v430 version if that makes any difference.
I'm having the same issue with the same version of the same tablet. It's driving me nuts.. constantly out of space, even with an sd card and having moved everything I can to it. Have not found a fix... or a root.
-Jay
joshka89 said:
I've looking into it some more and with DiskUsage and other explorer apps I see that there is 5.8GB of space accounted for, 3.4GB for Storage and 2.42GB for "System"
However, this is an 8GB device. I have gone through the whole thing on file explorers and it seems almost like it isn't even seeing the remaining 2.1GB I should have.
As if another Android system is there but unused or unrecognized.
I have the sprint v430 version if that makes any difference.
Click to expand...
Click to collapse
jayntguru said:
I'm having the same issue with the same version of the same tablet. It's driving me nuts.. constantly out of space, even with an sd card and having moved everything I can to it. Have not found a fix... or a root.
-Jay
Click to expand...
Click to collapse
I also have the same problem with my LG G Pad 7 400 tablet. I hope to find a solution here.
Thanks,
dovwork said:
I also have the same problem with my LG G Pad 7 400 tablet. I hope to find a solution here.
Thanks,
Click to expand...
Click to collapse
Same problem here.. seems like Sprint version LK430 is only 8GB and 4.5GB is taken by system data. Anybody got any luck clean up that system data ?
This thread just seems to have died i too am searching for a fix for this issue does anyone have an update or is this tablet just garbage
only solution is to root and use Link2Sd guys, no other way
brainvision said:
only solution is to root and use Link2Sd guys, no other way
Click to expand...
Click to collapse
im still trying to find reliable root.. :/
bscabl said:
im still trying to find reliable root.. :/
Click to expand...
Click to collapse
What variant do you own? I think the so called "New method to root LG devices" should still work for every GPad (and many more LG)
brainvision said:
What variant do you own? I think the so called "New method to root LG devices" should still work for every GPad (and many more LG)
Click to expand...
Click to collapse
i have the sprint variant. the one click root i tried didnt work
brainvision said:
What variant do you own? I think the so called "New method to root LG devices" should still work for every GPad (and many more LG)
Click to expand...
Click to collapse
just stops here..
bscabl said:
just stops here..
Click to expand...
Click to collapse
I see.. lots of us had that issue.. If I recall correctly what I did was to add a blank space before pasting the last command so as you can see from your cmd print you have
Code:
#sh ETC ETC
just try to add a space before pasting so tyo have
Code:
# sh ETC ETC ETC
it could take a while but it should work..
also if it doens't work after trying two or three times try using a new USB port or another pc, if available (don't ask why, I'm reporting what other users reported )
brainvision said:
I see.. lots of us had that issue.. If I recall correctly what I did was to add a blank space before pasting the last command so as you can see from your cmd print you have
Code:
#sh ETC ETC
just try to add a space before pasting so tyo have
Code:
# sh ETC ETC ETC
it could take a while but it should work..
also if it doens't work after trying two or three times try using a new USB port or another pc, if available (don't ask why, I'm reporting what other users reported )
Click to expand...
Click to collapse
tried that too. just sits there.
also, windows7. not windows 10 [just because a lot of people have reported windows 10 inability to map com ports properly]
truthfully.. this little tablet is my first device i havent been able to root
bscabl said:
tried that too. just sits there.
also, windows7. not windows 10 [just because a lot of people have reported windows 10 inability to map com ports properly]
truthfully.. this little tablet is my first device i havent been able to root
Click to expand...
Click to collapse
sorry but you said sprint variant but what G Pad? 7 8 or 10? I don't think there could be lots of difference but did you try googling if other owners of your exact tablet reported rooting issues?
Also I saw from your screenshot that you execute the reg command to detect the COM port where to send the sh command; maybe you could try to follow the guide exactly like wrote, so open the port.bat to detect the port, then close the new cmd window and then execute the sh command. I don't think ot could be an issue but maybe the reg command leave the port open and so the command fails.. really I'm just going random here
last but least, imo, you should try from scratch restarting the guide from the start, but I think you already do it..
---------- Post added at 09:19 PM ---------- Previous post was at 09:13 PM ----------
hey mate try this one: https://www.smartphoneclinics.com/easy-root-sprint-lg-pad-70-lk430/ - it the same root method as the one tyou're trying but fully automated (there should be a thread here on xda too but cannot find it now)
brainvision said:
sorry but you said sprint variant but what G Pad? 7 8 or 10? I don't think there could be lots of difference but did you try googling if other owners of your exact tablet reported rooting issues?
Also I saw from your screenshot that you execute the reg command to detect the COM port where to send the sh command; maybe you could try to follow the guide exactly like wrote, so open the port.bat to detect the port, then close the new cmd window and then execute the sh command. I don't think ot could be an issue but maybe the reg command leave the port open and so the command fails.. really I'm just going random here
last but least, imo, you should try from scratch restarting the guide from the start, but I think you already do it..
---------- Post added at 09:19 PM ---------- Previous post was at 09:13 PM ----------
hey mate try this one: https://www.smartphoneclinics.com/easy-root-sprint-lg-pad-70-lk430/ - it the same root method as the one tyou're trying but fully automated (there should be a thread here on xda too but cannot find it now)
Click to expand...
Click to collapse
yea. so.. i guess im going to stop here.. ive been rooting phones since the palm pre.. and while i may not be a coder, i can follow written instructions without issue. even king root doesnt work on this tablet.. [tab7 k430 variant, thought i mentioned that, or at least that it was the gtab sprint variant.. but i digress]
also, the link you posted, is simply an automated script to do exactly what is failing here. it may have worked in 2015 when the tablet was released and article was written.. but.. alas, its very very outdated.
thanks anyway
bscabl said:
yea. so.. i guess im going to stop here.. ive been rooting phones since the palm pre.. and while i may not be a coder, i can follow written instructions without issue. even king root doesnt work on this tablet.. [tab7 k430 variant, thought i mentioned that, or at least that it was the gtab sprint variant.. but i digress]
also, the link you posted, is simply an automated script to do exactly what is failing here. it may have worked in 2015 when the tablet was released and article was written.. but.. alas, its very very outdated.
thanks anyway
Click to expand...
Click to collapse
yep it is an automated script for this same process but you can't never tell.. can't say why but htis process does not work at the first time for lots of people, as you can read into the main thread.. for me it worked a lot of times both for my G Pad 7 Wifi (first year release) both for my G 2, sometimes it hanged but after trying a bunch of times it alwasy did the work..
so it's not a pointless method.. and it's from 2015 too, same as the automated zip, they never update it because it worked..
anyway after searching for your specific variant I find this specific thread: https://forum.xda-developers.com/android/help/sprint-lg-g-pad-f7-0-lk430-t3180261
maybe you already read it but someone says kingroot + remove kigroot for supersu is the way, but you said it did not work for you..
last I was not telling you that you are not able to follow istructions, but I saw you did something different form the screenshot, instead of opening the port.bat file, just that.. if you don't think it worths to try as they say in the guide it's up to you, no prob
Related
Hi,
I finally managed to import all my messages from my N95 to Hero and here is a tutorial I wrote for the same.
http://vinodmishra.com/2009/09/how-to-import-smss-from-nokia-to-htc-android-devices/
RemoteSojourner said:
Hi,
I finally managed to import all my messages from my N95 to Hero and here is a tutorial I wrote for the same.
http://vinodmishra.com/2009/09/how-to-import-smss-from-nokia-to-htc-android-devices/
Click to expand...
Click to collapse
Has anyone got this to work, i can't get the Date formate changed over to, i copied and pasted the string in the post but it doesn't change it over.
niktheman said:
Has anyone got this to work, i can't get the Date formate changed over to, i copied and pasted the string in the post but it doesn't change it over.
Click to expand...
Click to collapse
Ok got it to work,
okay my converter sux I got it .D if you could post more info to: http://forum.xda-developers.com/showthread.php?p=4385729 your tutorial for Hero could be much more simpler...
and dont forget to give credits plx .D
best regards
I had mentioned your thread as a credit in my blog post. Maybe I will make it bold now . And I know it could be simpler. When I have time I could write a tool to insert the xml generated by Amber Nokia convertor into the SQL Lite databases directly without doing all the hacks i.e. merging a tutorial to convert NOkia->WM and then WM->Android. The WM bit isn't really necessary tbh.
Sorry I just noticed.. I forgot to include the link to your post and only included the modaco ones SOrry for that.. Done it now
iphone to htc hero???
anyone?
Almost there, but a little help needed please
Hi, have followed all the steps and got a saved copy of import.xml.
Next I connected the phone using the USB cable. (Didn't mount it as a USB device)
Then I opened Command Promt on my PC and changed to the android SDK tools directory.
Then I type "adb shell" (without quotes)
It says:
adb server is out of date. killing...
* daemon started successfully *
$
At this point the phone disconnects from HTC Sync and I have to end adb.exe (which appears twice) in windows task manager to get it to reconnect to sync.
Any suggestions please?
If it disconnects from HTC Sync, it's fine as long as you get the shell prompt
RemoteSojourner said:
If it disconnects from HTC Sync, it's fine as long as you get the shell prompt
Click to expand...
Click to collapse
But then if I type "su" after the $ it says su: permission denied...
I assume your phone isn't rooted then.
RemoteSojourner said:
I assume your phone isn't rooted then.
Click to expand...
Click to collapse
Maybe not. To be honest I'm starting to feel a bit out of my depth here. I don't really have any programming knowledge and haven't really used dos much before. I'll go and research 'rooting' now, but if you can come back with a quick instruction in the meantime that'd be great
Ok, so I've found various instruction for how to root my phone. Only problem is that they each seem to relate to what network I'm on. I was originally on T-Mobile, but paid to have it unlocked so I can use my 3 sim. Should I just use the instruction relating to T-Mobile? Sorry for so many questions, but I'm a bit worried about permanently wrecking the phone
RemoteSojourner said:
I assume your phone isn't rooted then.
Click to expand...
Click to collapse
Ok, if I use the instructions here (my ROM version is 2.73.+) http://forum.xda-developers.com/showpost.php?p=4525393&postcount=1 do you think it should be ok? I am a bit worried about the part where it says "flashrec is using an exploit that isn't patched yet in the current kernel used by HTC, however if/when HTC patches this, flashrec will stop working. So for now it's ok but a next version might have patched this, so keep this in mind !"
retroscendence said:
Ok, if I use the instructions here (my ROM version is 2.73.+) http://forum.xda-developers.com/showpost.php?p=4525393&postcount=1 do you think it should be ok? I am a bit worried about the part where it says "flashrec is using an exploit that isn't patched yet in the current kernel used by HTC, however if/when HTC patches this, flashrec will stop working. So for now it's ok but a next version might have patched this, so keep this in mind !"
Click to expand...
Click to collapse
Yup that one should work.
I've been following the progress on official Ubuntu Touch port to Galaxy Tab 10.1 for a while and today they have updated the wiki for a dedicated session and early build install instructions.
This is an early build, some things work, some things are unknown and wifi is work in progress.
Installation
1. Download the ubuntu preinstalled and the p4wifi specific cyanogenmod image from the unlock instruction section below.
2. Put both zip files onto your sdcard
3. Enter recovery mode and do a wipe data/factory reset
4. Flash in this order:
First the cyanogenmod image (e.g. cm-10.1-20130325-UNOFFICIAL-p4wifi.zip)
Then the ubuntu image (this may take a while)
5. reboot
fix screen pixel ratio (this will become obsolete once the config file is included by default):
1. download p4wifi.conf: http://ubuntuone.com/688wubidavYnvfKvBWV7cY
2. copy p4wifi.conf into /etc/ubuntu-session.d/
3. reboot
Unlocking instructions
link to images
1. Ubuntu stuff:
Current: http://cdimage.ubuntu.com/ubuntu-to...urrent/quantal-preinstalled-phablet-armhf.zip
2. CyanogenMod image:
Current: http://ubuntuone.com/6V0ZxZ8cqB2AGcF8nImrDV
*Note: I am not involved with the development and I do not own this project, for more details please go to the link below.
https://wiki.ubuntu.com/Touch/Devices/p4wifi
Thanks, friend! I'm gonna test it soon :good:
AW: Official Ubuntu Touch for Galaxy Tab 10.1 is here!
I tried it. Installation worked fine and the first start (reboot after install) also went fine. Can't test more things than boot up right now - no time so far. I'll have a look this evening.
But why are there already users exsisting an how do i log in?
Sent from my One S using xda app-developers app
They say it's a test-only version and you can only log in to guest account...
and if you read the ubuntu-part file's name it is "quantal-PREINSTALLED", which means it is an installed image of Ubuntu that was tested on some previous devices by Ubuntu devs...
it's my thought, though...
AW: Official Ubuntu Touch for Galaxy Tab 10.1 is here!
Yes. It's a tech demo. But it already looks nice. I hope development goes on quickly.
Sent from my One S using xda app-developers app
customromfan said:
Yes. It's a tech demo. But it already looks nice. I hope development goes on quickly.
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
I'm testing this now, but I cannot find /etc/ubuntu-session.d/
Wifi not working after returning image back to Cyanogenmod
I followed your instructions and got Ubuntu touch working. After playing around with it for a while I decided to go back to my Cyanogenmod rom. For some reason now I cannot turn on the wifi. It is the same image that was working before. Can you offer some advice or assistance?
Thanks
Can someone make a video of this running? I want to do it myself but can't find the 10.1's charger
GazaIan said:
Can someone make a video of this running?
Click to expand...
Click to collapse
I've installed it with no problems, just followed the instructions in the first post...
I'm now attempting to get screen pixel ratio fixed and wifi running, and then will upload a video to youtube (probably in the next few hours)
Sorry, but I just can't find etc\ubuntu-session.d\ and can't make a persistent local directory in /data/ ...
If anyone can help me with these problems, please tell me...
(I chmodded the userinit.sh file for wifi and tried to fix the screen pixel ratio, but couldn't find or create the directories to put them)...
I'll upload a video anyway...
Dingles666 said:
I followed your instructions and got Ubuntu touch working. After playing around with it for a while I decided to go back to my Cyanogenmod rom. For some reason now I cannot turn on the wifi. It is the same image that was working before. Can you offer some advice or assistance?
Thanks
Click to expand...
Click to collapse
Not sure why you're having this problem. Maybe try format everything before flashing back or use a nand backup if you have one?
I think we must put the p4wifi.conf into ubuntu-session.d folder in the quantal before we install the image, right?
The proof I can provide is that there are folders named ubuntu-session.d and data in the quantal, but they're extracted to somewhere else during installation...
Video coming soon...
arashtarafar said:
Sorry, but I just can't find etc\ubuntu-session.d\ and can't make a persistent local directory in /data/ ...
If anyone can help me with these problems, please tell me...
(I chmodded the userinit.sh file for wifi and tried to fix the screen pixel ratio, but couldn't find or create the directories to put them)...
I'll upload a video anyway...
Click to expand...
Click to collapse
My memory is a bit vague on this, but I think it's in the /ubuntu folder, as well as the rest of the filesystem. It confused the hell out of me when I had it on my Sensation, it seemed like there was an entire filesystem at the root of the storage, then another inside /ubuntu where everything seemed to be.
You could use the search in Nautilus to find it as well, just make sure it's searching all subdirectories
I had a problem adding the p4wifi.conf file to /etc/ubuntu-session.d/ folder. This is how I solved it.
My problem basically was that when using adb shell to access the device I was inside the android system. And you need to get inside the ubuntu-system.
My way to get shell access to the ubuntu-system was the following:
>adb root
>adb shell
You should now see something similar to [email protected]:/ #
Then enter:
>ubuntu_chroot shell
You should now see something similar to [email protected]:/#
You are now in the ubuntu-system.
to get the p4wifi.conf file into /etc/ubuntu-session.d I did the following:
>cd /etc/ubuntu-session.d
>echo -e "GRID_UNIT_PX=10\nQTWEBKIT_DPR=2.0\nFORM_FACTOR=\"tablet\"" | sudo tee p4wifi.conf
For some reason there is a space between " and tablet. This space should be removed! It seems as if the forum adds it when rendering my post.
Now for the changes to take effect you will need to reboot your device. You can do that by writing the following
>reboot
I hope this helped someone that just as me struggled to get the pixel-ratio fix applied to the system.
Thanks, my friend.
I'm gonna try this and then will upload a video...
if we can find the way to fix WiFi according to this post:
http://forum.xda-developers.com/showpost.php?p=38988110&postcount=44
it will be awesome!
thanks again
arashtarafar said:
Thanks, my friend.
I'm gonna try this and then will upload a video...
if we can find the way to fix WiFi according to this post:
http://forum.xda-developers.com/showpost.php?p=38988110&postcount=44
it will be awesome!
thanks again
Click to expand...
Click to collapse
Yeah I read about this post too, I'm a bit busy this week but maybe I'll try it out this weekend.
I finally fixed screen pixel ratio by flashing the .zip package linked in post 15 in this thread ... simply adb push it and flash using CWM (ubuntu won't erase CWM after being flashed)...
I'm now going to fix WiFi to upload a video that's worth seeing ...
arashtarafar said:
Thanks, my friend.
I'm gonna try this and then will upload a video...
if we can find the way to fix WiFi according to this post:
http://forum.xda-developers.com/showpost.php?p=38988110&postcount=44
it will be awesome!
thanks again
Click to expand...
Click to collapse
I have tried this but no success Please share if anyone solves the wifi-issue.
---------- Post added at 03:38 PM ---------- Previous post was at 03:33 PM ----------
Does iwlist work for anyone? For me it dosen't even recognise the command.
does 3G work on this?
3G doesn't work yet, but I'm testing the OS on my galaxy tab 3G
yeah, I too have tried putting userinit.sh file in /data/loca/ with no success... but note that you must put the file using ubuntu_chroot shell... did you try that?
maybe we can put the commands in afterflash-p4.zip and then flash it, like the way we solved the screen pixel ratio issue...
inform us if this method worked for you
I am relatively new here, but was reading some threads and a couple people have said that the community hasn't found the 13.3.2.7 update to manually force a rollback. A couple days ago I called Amazon because I had updated to 4.5 and needed to go back to root.
Since then I have been looking around for where the patch was saved to and found the scripts that setup for the OS update and the scripts to run it. The scripts show where it is and what commands are called to do the update, but the actual 13.3.2.7 OS seems to be hidden. I know where it says it should be, but its hidden somehow. If this is something anyone wants copies of my files on let me know, if this isn't something the community needs I apologize, just trying to help get this tablet further along.
Either post here or message me if you want/need what I have.
Why don't you just post your findings so far on this thread?
I was under the impression that OTA files are downloaded to the /cache folder, therefore inaccessible without root.
Either way, updates are still verified (see: /system/app/otaverifier.apk) by the system, so I'm not sure how you'd get around that.
EncryptedCurse said:
Why don't you just post your findings so far on this thread?
I was under the impression that OTA files are downloaded to the /cache folder, therefore inaccessible without root.
Either way, updates are still verified (see: /system/app/otaverifier.apk) by the system, so I'm not sure how you'd get around that.
Click to expand...
Click to collapse
I see, that part is already known then. Other posts I read people were still looking for it, but I was sure if i found it many others have too. I'm still looking around though, I found the verification coding also, thanks for that. I am thinking about updating my tablet again, and having them roll it back again, but this time running a packet sniffer. Might possibly get some really good info about the verification process or at least the steps it takes to make the rollback. I did a search but haven't seen anyone try this, it's probably heavily encoded though.
Another thing I noticed while looking around... They put a kill switch fuse in it? That's pretty rough, and what causes it to activate? Software modification or Hardware like Jtags?
Eclipsys said:
I see, that part is already known then. Other posts I read people were still looking for it, but I was sure if i found it many others have too. I'm still looking around though, I found the verification coding also, thanks for that. I am thinking about updating my tablet again, and having them roll it back again, but this time running a packet sniffer. Might possibly get some really good info about the verification process or at least the steps it takes to make the rollback. I did a search but haven't seen anyone try this, it's probably heavily encoded though.
Another thing I noticed while looking around... They put a kill switch fuse in it? That's pretty rough, and what causes it to activate? Software modification or Hardware like Jtags?
Click to expand...
Click to collapse
once rooted again .it may be possible to modify your build.prop like we were on past firmware to achieve rollback just to initiate download ,it will ultimately fail once it downloaded it and trys to install it will check a few more things it will fail and erase it ...the trick would be not too let the device idle..or to have the battery below I believe 30 percent it may be as high as 40 I'm not sure but I believe under 30 it will refuse to install update delay till charged ,anyway it may buy you time to find it
jimyv said:
once rooted again .it may be possible to modify your build.prop like we were on past firmware to achieve rollback just to initiate download ,it will ultimately fail once it downloaded it and trys to install it will check a few more things it will fail and erase it ...the trick would be not too let the device idle..or to have the battery below I believe 30 percent it may be as high as 40 I'm not sure but I believe under 30 it will refuse to install update delay till charged ,anyway it may buy you time to find it
Click to expand...
Click to collapse
That is actually a very good idea, something I am testing right now is getting the FireOS to run in VMware. I have a standard Android KitKat OS running, but getting the Kindle's OS to run is giving me a few issues. I am very skittish to try this stuff on my actual device as it's brand new and I don't have a backup... But if I can I will give you idea a shot. Might be able to save it before it deletes. Also if I can get it going in VMware it might be possible to use a debugger to examine the ASM code in great detail.
Eclipsys said:
That is actually a very good idea, something I am testing right now is getting the FireOS to run in VMware. I have a standard Android KitKat OS running, but getting the Kindle's OS to run is giving me a few issues. I am very skittish to try this stuff on my actual device as it's brand new and I don't have a backup... But if I can I will give you idea a shot. Might be able to save it before it deletes. Also if I can get it going in VMware it might be possible to use a debugger to examine the ASM code in great detail.
Click to expand...
Click to collapse
I didn't have any problem doing the modifications myself and I'm no Pro that's for sure. Never written a line of code in my life. I just tend to thoroughly research and understand before I attempt things and I've been practicing here for a while if you go to the, rollback .0.1 and safestraped thread there is quite detailed instructions serval times throughout the thread I would skim it.you will just be substituting version numbers and kind of a inverse idea compared to what we were doing there but it should accomplish it. I used rOM Toolbox lite I believe as an editor and saved each timeI didn't have any problems with the permissions getting screwed up while tampering with it rOM Toolbox took care of that issue. I have seen tons of people brick trying to make these modifications. But I don't think they understood completely what they were attempting to do it's actually very simple and as long as you do it thoroughly and get all of them changed I have not seen any problems other than maybe having to repeat the process.there are a couple of lines that only use the last section of your version numbers I even changed those back then.
Eclipsys said:
I am relatively new here, but was reading some threads and a couple people have said that the community hasn't found the 13.3.2.7 update to manually force a rollback. A couple days ago I called Amazon because I had updated to 4.5 and needed to go back to root.
Since then I have been looking around for where the patch was saved to and found the scripts that setup for the OS update and the scripts to run it. The scripts show where it is and what commands are called to do the update, but the actual 13.3.2.7 OS seems to be hidden. I know where it says it should be, but its hidden somehow. If this is something anyone wants copies of my files on let me know, if this isn't something the community needs I apologize, just trying to help get this tablet further along.
Either post here or message me if you want/need what I have.
Click to expand...
Click to collapse
Please upload the file somewhere (preferably to mega). If it doesn't pass the version check we can use my hack to bypass it.
p1gl3t said:
Please upload the file somewhere (preferably to mega). If it doesn't pass the version check we can use my hack to bypass it.
Click to expand...
Click to collapse
https://mega.co.nz/#!wlQl2bZD!Kk-rcWtcMPWxoEH5VcHrtZb7nOsJet9si1pm5FYhT44
5.2 build prop file
Hello all, I found a method to Root and get a custom recovery on our cricket variant, no donations required! You need to find a copy of sugar qct with a username and password, I don't remember exactly where I found it but it shouldn't be too difficult to find. Then you need to let it update to the latest build, which includes the programmer for our phone. If you don't see 6055u in the list it's not up to date. From there, Hook up your phone (may need to manually put it in download mode. Press upgrade and then navigate to the install directory, look in /bin and find where it downloads all the mbm files. Replace the one that starts with an r with the TWRP recovery for 6055. You may have to overwrite it multiple times during the process. If you did it correctly you will be able to boot into TWRP, if not try again. If you don't close sugar I believe it won't overwrite the firmware files, but I haven't messed with it much. I will try to write a tool to make it easier when I have the time but I'm pretty busy. Feel free to pm me with any questions and I will help the best I can.
To get root just install supersu
F
dbgr said:
Hello all, I found a method to Root and get a custom recovery on our cricket variant, no donations required! You need to find a copy of sugar qct with a username and password, I don't remember exactly where I found it but it shouldn't be too difficult to find. Then you need to let it update to the latest build, which includes the programmer for our phone. If you don't see 6055u in the list it's not up to date. From there, Hook up your phone (may need to manually put it in download mode. Press upgrade and then navigate to the install directory, look in /bin and find where it downloads all the mbm files. Replace the one that starts with an r with the TWRP recovery for 6055. You may have to overwrite it multiple times during the process. If you did it correctly you will be able to boot into TWRP, if not try again. If you don't close sugar I believe it won't overwrite the firmware files, but I haven't messed with it much. I will try to write a tool to make it easier when I have the time but I'm pretty busy. Feel free to pm me with any questions and I will help the best I can.
To get root just install supersu
Click to expand...
Click to collapse
Did a Google search for "sugar qct" and I see a couple of million hits for "The Sugar Act"... :laugh:
Tried Root Genius, and it, of course doesn't work...
If you happen to find a link for the app or method you stated, I would be eternally grateful... My lovely wife and I upgraded our phones to the Cricket 6055U, and, since, while not an Android developer, per se, can find my way around the device without being scared off...
So, with due respect, I'd ask if you have the app or name correct?
Thanks, friend, and best respect.
--- edit ---
Oops... was premature... found it and am giving it a try... I'll post my results after I give it a shot...
http://forum.gsmhosting.com/vbb/f606/vf-895n-smart-prime-6-stock-rom-flash-tool-2033867/
This should help with setting up sugar. The only difference here is to update it and you also need a username and password that I don't have on me at the moment. It will be a few hours until I get home but I will update asap.
Edit: nevermind lol, good luck friend. You may need a decent battery percentage as well
pauljulian said:
F
Did a Google search for "sugar qct" and I see a couple of million hits for "The Sugar Act"... :laugh:
Tried Root Genius, and it, of course doesn't work...
If you happen to find a link for the app or method you stated, I would be eternally grateful... My lovely wife and I upgraded our phones to the Cricket 6055U, and, since, while not an Android developer, per se, can find my way around the device without being scared off...
So, with due respect, I'd ask if you have the app or name correct?
Thanks, friend, and best respect.
--- edit ---
Oops... was premature... found it and am giving it a try... I'll post my results after I give it a shot...
Click to expand...
Click to collapse
----- edit 2 -----
OK... apparently I'm an idiot... Running Windows 10 Pro, and the installer says it's going to install to an appropriate folder on C:\... yet, trying to find it, it really is weird.... I'm going to try on a VMWare Win 7 virtual PC, and see if I'm able to find it there, and move it to my actual C: drive...
If it works, I'll be grateful for your contribution and praise you to the highest heaven! :laugh:
pauljulian said:
----- edit 2 -----
OK... apparently I'm an idiot... Running Windows 10 Pro, and the installer says it's going to install to an appropriate folder on C:\... yet, trying to find it, it really is weird.... I'm going to try on a VMWare Win 7 virtual PC, and see if I'm able to find it there, and move it to my actual C: drive...
If it works, I'll be grateful for your contribution and praise you to the highest heaven! :laugh:
Click to expand...
Click to collapse
Can't seem to get the beast to work...
If you would be so kind, would there be any way you'd be able to write up a concise step-by-step thing, if you've made it work... I've got the .chm file open on my desktop, and have spent a few hours trying to make it work to no avail.
Again, if it worked for you, your process would be welcome.
Cricket Alcatel Idol 4, 6055U
---------- Post added at 03:36 PM ---------- Previous post was at 02:40 PM ----------
pauljulian said:
Can't seem to get the beast to work...
If you would be so kind, would there be any way you'd be able to write up a concise step-by-step thing, if you've made it work... I've got the .chm file open on my desktop, and have spent a few hours trying to make it work to no avail.
Again, if it worked for you, your process would be welcome.
Cricket Alcatel Idol 4, 6055U
Click to expand...
Click to collapse
My point is that the site recommended seems to insist on Lollipop on the small beast... and there doesn't seem to be a recommendation for the .bin files, and, when installing on Win 10, it seems to install the Sugar app into some directory on my C: drive that is really not that accessible... Did it using a VMWare Win 7 32-bit virtual, and was able to access the directory, copy and paste to my regular C: drive (old Windows geek since Win 3.11... and DOS 3), and it seemed to run... (of course, running as Administrator), but it really doesn't seem to work for me... Again, I freely admit that I'm likely not doing something right, but even after some research and the included .chm file, I seem to be missing something.
Again, and begging your indulgence for seeming like a noob or a rube, but if I'm not making it happen, I rather think that the tips would be lost on someone for whom this is their first Android device...
Kinda frustrating, as, even though I've been a tech-support guy and database developer for more than 30 years, this thing has me stymied...
I found it fascinating for the *#*# command, earlier, from another noble soul, and, obviously, I also found that the device as configured says, basically... "Don't give a damn... you can turn this sucker on, but as soon as you exit this menu, I'm gonna turn it off again."
Just a little frustrating, and it seems that most of the tips and tricks elsewhere seem to be thinking that new owners of the 6055U are running Lollipop.... aaarrrgggghhh....
If it needs Lollipop to work, and if there's a relatively painless way to downgrade, and then upgrade from a ROM, I'm good with that... the Idol 3 seemed to require that, and it worked well for me, with just an evening's work. This one? Cricket seems to have had a warped sense of humor about it... I seriously dig the device, and, since my Idol 3 broke, and my lovely wife's LG G-Stylo (which was a pain in the ass, and next-to-impossible to root, and then be just perpetually stuck at the logo screen with an unfixable boot loop, if one screwed it up, and just required sending the beast back to LG, as long as one took out Cricket's warranty plan... <sigh>), we took the plunge on this one...
Not much for which I require root, but, since I spent good money on some legit apps (and lucked into a few ... ahem... not legit apps that worked for me), these things require root... I know there's a way to do it, and the Sugar app seems promising, but, mildly autistic guy that I am (and 60 years old, with a memory that doesn't work as it used to), a slimmed-down step-by-step doc would be helpful... should some noble soul put such together...
Apparently, the root method has worked for at least one member here.... But this weird old Jewish hippie doesn't see the mental diagram....
Any help would be welcome, my friends and mishpocheh... ("dear family" --- been here enough years, albeit a relatively quiet member, that y'all might as well be family... )
Hey everyone, sorry about the confusion. I installed on Windows 10 pro with no issues. As far as the page I linked you can disregard everything but the app itself. The update that downloads is marshmallow, and I've had no issues overwriting the latest version. I may have gotten sugar from a different location though, as soon as I get a chance I will do a better write up with everything. A helpful way to find the install directory would be right click on the shortcut from the start menu and click find Target / open file location. If it brings you to the folder with the shortcuts do it again and you will have the install directory. The app should be in (install dir)/tool and the downloaded updates go in (install dir)/bin under a folder that only shows up once you start the process within sugar. I will try to compile the information into a more user friendly format tonight but I can't make any promises on that.
Also just to clarify, I didn't use any chm file
I'm wondering if you could upload your version you have on your pc. I just spent the last month in jail here in Orlando fighting a case and the only proof I've got is on my phone on a phone that I deleted my videos on. I really need the videos back too get a not guilty if I gotta pay for it it's cool but I'm out on bond and all the recover videos apps require root
I got this to work last night. Typed up some instructions but didn't get them posted. They're on my PC at home and I'm at work.
Basically use the copy of sugar in the download package in this thread and then start it and let it update https://forum.xda-developers.com/android/development/recovery-vodafone-prime-tab-7-t3548560
Those are the basic instructions too except we don't need to swap out bout and use the TWRP from deckersu thread.
Once flashed it'll automatically reboot. I found you had to make sure you caught this and booted into TWRP right away don't let the phone boot. Then transfer SuperSU in TWRP and flash.
---------- Post added at 11:29 AM ---------- Previous post was at 11:23 AM ----------
Asadullah said:
I'm wondering if you could upload your version you have on your pc. I just spent the last month in jail here in Orlando fighting a case and the only proof I've got is on my phone on a phone that I deleted my videos on. I really need the videos back too get a not guilty if I gotta pay for it it's cool but I'm out on bond an ind all the recover videos apps require root
Click to expand...
Click to collapse
FYI this root method wipes your phone so I don't know if this will help your situation or not.
In sugar there is an option to not wipe, it's under session settings or something to that effect
dbgr said:
In sugar there is an option to not wipe, it's under session settings or something to that effect
Click to expand...
Click to collapse
Wish I had noticed that!! Oh well, stoked to have root and it's good to start fresh. Got Xposed installed today and finally got that annoying charging light turned off. Working on getting wifi tetherng working. Then if I can figure out how to get the dialer to be friends with Google voice this phone will have all its annoyance fixed
Thanks so much for figuring this out and sharing!!
dbgr said:
In sugar there is an option to not wipe, it's under session settings or something to that effect
Click to expand...
Click to collapse
Appreciate the help
woodi5359 said:
https://forum.xda-developers.com/android/development/recovery-vodafone-prime-tab-7-t3548560.
Click to expand...
Click to collapse
Thank you for finding this thread, it is the same one I found but I couldn't remember where it was the other day when I started this thread. Hopefully this will help the people who have been having issues, although I will admit a more painless method would be preferable. I'm currently working on modifying a dirtycow exploit to simply flash the recovery and reboot into twrp, if I get it to work I will zip it all up and post it here.
woodi5359 said:
Wish I had noticed that!! Oh well, stoked to have root and it's good to start fresh. Got Xposed installed today and finally got that annoying charging light turned off. Working on getting wifi tetherng working. Then if I can figure out how to get the dialer to be friends with Google voice this phone will have all its annoyance fixed
Thanks so much for figuring this out and sharing!!
Click to expand...
Click to collapse
I got wifi tethering working I did a lot of things but I believe that did it was adding net.tethering.noprovisioning=true to my build.prop then I went into system/app and changed serviceentitlement.apk into serviceentitlement.oat using es file Explorer
Asadullah said:
I got wifi tethering working I did a lot of things but I believe that did it was adding net.tethering.noprovisioning=true to my build.prop then I went into system/app and changed serviceentitlement.apk into serviceentitlement.oat using es file Explorer
Click to expand...
Click to collapse
I just tested this and it indeed does work. Great find friend!
Asadullah said:
I got wifi tethering working I did a lot of things but I believe that did it was adding net.tethering.noprovisioning=true to my build.prop then I went into system/app and changed serviceentitlement.apk into serviceentitlement.oat using es file Explorer
Click to expand...
Click to collapse
Thanks for figuring this out!!! I'd been messing with it for a few days. The renaming the apk to .oat was the piece I was missing. That and a reboot got it working!!
dbgr said:
Hello all, I found a method to Root and get a custom recovery on our cricket variant, no donations required! You need to find a copy of sugar qct with a username and password, I don't remember exactly where I found it but it shouldn't be too difficult to find. Then you need to let it update to the latest build, which includes the programmer for our phone. If you don't see 6055u in the list it's not up to date. From there, Hook up your phone (may need to manually put it in download mode. Press upgrade and then navigate to the install directory, look in /bin and find where it downloads all the mbm files. Replace the one that starts with an r with the TWRP recovery for 6055. You may have to overwrite it multiple times during the process. If you did it correctly you will be able to boot into TWRP, if not try again. If you don't close sugar I believe it won't overwrite the firmware files, but I haven't messed with it much. I will try to write a tool to make it easier when I have the time but I'm pretty busy. Feel free to pm me with any questions and I will help the best I can.
To get root just install supersu
Click to expand...
Click to collapse
so im getting ready to purchase this device so there is root and twrp for it or no
Dude, did you read the thread at all? I don't mind helping but you gotta do your part. Yes there is TWRP and Root
dbgr said:
Hello all, I found a method to Root and get a custom recovery on our cricket variant, no donations required! You need to find a copy of sugar qct with a username and password, I don't remember exactly where I found it but it shouldn't be too difficult to find. Then you need to let it update to the latest build, which includes the programmer for our phone. If you don't see 6055u in the list it's not up to date. From there, Hook up your phone (may need to manually put it in download mode. Press upgrade and then navigate to the install directory, look in /bin and find where it downloads all the mbm files. Replace the one that starts with an r with the TWRP recovery for 6055. You may have to overwrite it multiple times during the process. If you did it correctly you will be able to boot into TWRP, if not try again. If you don't close sugar I believe it won't overwrite the firmware files, but I haven't messed with it much. I will try to write a tool to make it easier when I have the time but I'm pretty busy. Feel free to pm me with any questions and I will help the best I can.
To get root just install supersu
Click to expand...
Click to collapse
do you hold volume down when it reboots
link22534 said:
do you hold volume down when it reboots
Click to expand...
Click to collapse
It's volume up and power
Delete... Now obsolete on current OS
Hello.
I have a Fire TV Stick Lite running 7.2.2.8.
Gone through the post and applied the "Debloat the Lite of Unnecessary Sh*te", installed all the apks. I went with Wolf 0.1.7 as the launcher.
When running FTVLaunchX I had to run the below two lines first and then perform the permissions.
settings put secure enabled_accessibility_services de.codefaktor.ftvlaunchx/de.codefaktor.ftvlaunchx.HomeService
settings put secure accessibility_enabled 1
The original Amazon launcher still loads first and then Wolf kicks in. I can still access the Amazon launcher by pressing the home key. Also there doesn't seem to be that much change on the main Amazon launcher if any at all.
Am I missing something? Or was I expecting too much?
***** UPDATE
I have tried "Launcher Manager (FireOS 6 & 7)_1.0.2" instead of LaunchX and this seems to work fine for me. Boots straight into Wolf and the Home button also links to Wolf.
Thanks
Deleted Thread, Obsolete tutorial
I now have it running like a dream with Wolf 0.1.7, looks really nice just how I would want it from stock. Thanks for your help.
Delete Thread.... OBSOLETE TUTORIAL ( No good to anyone now running latest firmwares)
Hello.
After the full debloat I noticed that I wasn't able to connect to the fire stick from my phone with app like you tube and prime video. The phone was just hanging on "connecting to fire stick" when clicking on the "cast" button. After a few attempts I found out that the service "com.amazon.avod" was responsable for making the connection possible from phone. When I enabled it back it started working as normal.
OBSOLETE TUTORIAL FOR FIRESTICK SHELDON. MODS/ADMIN PLEASE DELETE THIS THREAD.. THANKS
Still running a version of 7228 but this must have been patched now, just get loads of Java exceptions when trying to do anything
brezzz said:
Still running a version of 7228 but this must have been patched now, just get loads of Java exceptions when trying to do anything
Click to expand...
Click to collapse
Should be working fine ... If you're using remote adb shell try pasting in smaller groups of the disable commands.
I noticed it tends to produce errors and crashes the remote adb app when pasting large clusters or the whole list of commands.
I just used it today on a Lite edition Firestick 2020 running 7.2.2.8 new UI.
I kanged @0815hoffi hardwork as some people I know were asking for a debloat AND Custom Launcher guide.... I just copied and pasted hoffis scripts minus the (adb shell part)
E.G "pm disable-user --user 0 *****"
Regards
Edit : OP updated...double tested again on two different models Lite and Newer FTVS-2021
Anything like this for the latest OS?
Bertonumber1 said:
Delete Thread.... OBSOLETE TUTORIAL ( No good to anyone now running latest firmwares)
Click to expand...
Click to collapse
well you usually don't delete something ! you can just ADD a note " with latest firmware is not working " .. by doing what you did " obsolete .. " " delete " .. you just created more confusion !
EVERYTHING become obsolete.. if you are worried about it just add a note
simika said:
well you usually don't delete something ! you can just ADD a note " with latest firmware is not working " .. by doing what you did " obsolete .. " " delete " .. you just created more confusion !
EVERYTHING become obsolete.. if you are worried about it just add a note
Click to expand...
Click to collapse
Not that i need to explain myself however i will in this case.
Firstly, due to the amount of people notifying me this was not working on newer fota update i had no choice but to remove it and prevent error.
Secondly, i wrote the post and decided it was best to delete it for the time being because... It was my post.
And finally.. The adb commands given in the first post do not work on any newer ota past 7.2.2.8 due to amazon telemetry within the ui/ launcher... so... until i have time to add my new tutorial for debloating/launcher replacement the post remains as is to prevent user error and screwed devices.
"simply adding a note" is a dumb idea as people being people would still attempt the commands on newer fireos... And who gets the stick for that when it goes wrong? Not you... Me.
Regards
Bertonumber1 said:
Not that i need to explain myself however i will in this case.
Firstly, due to the amount of people notifying me this was not working on newer fota update i had no choice but to remove it and prevent error.
Secondly, i wrote the post and decided it was best to delete it for the time being because... It was my post.
And finally.. The adb commands given in the first post do not work on any newer ota past 7.2.2.8 due to amazon telemetry within the ui/ launcher... so... until i have time to add my new tutorial for debloating/launcher replacement the post remains as is to prevent user error and screwed devices.
"simply adding a note" is a dumb idea as people being people would still attempt the commands on newer fireos... And who gets the stick for that when it goes wrong? Not you... Me.
Regards
Click to expand...
Click to collapse
for sure you got your reason ( unless you would have gone out of your mind lol )
i'm just saying that is better to edit the original post and write NOT WORKIN ON LATEST FIRMWARE ( or after 7.2.2.8) than if people are not able to read the post well they should learn !