Hi *,
I have installed KJY2010 Honeylicious Icy Faux HC 3.2 but it complains about the missing sim card (model wo G3 connectivity).
I'v tried to disable all apk that have to do with telephony but they are started from rild (I guess) in init.rc which is hardwired in boot.img.
Any other solution than to take boot.img from mmcblk0p2 and modifying init.rc in order to disable rild?
Are you running an a501? or an a500?
EDIT: saw your ()
Did you check your build.prop?
Should say ro.carrier=wifi-only
So if you did your 3 wipes, coming from another rom, you shouldn't get the error.
No need to delete or freeze apk's, or do anything with the image files. Relatively few people have the "please insert sim card" on the 500 series. Usually, because some info wasn't completely wiped.
And if in doubt, you can go to Mounts etc.. And format these things. This will ensure you delete all previous info. Also, you can flash the upgrade to a newer Thor Recovery if you wish, now that we mention it.
Also, it may help, to post this in the specific ROM thread in the development forum. This way, the Dev can specifically answer your issue, instead of general Iconia Q&A
Thanks for the prompt answer.
Since I'm a good boy I did wipe all
but you are right I have [ro.carrier]: [unknown]
and I didn't post to development because this is my 4th post and I'm not allowed
I hope I can change ro.carrier wo reflashing by editing /system/build.prop
magnusPI said:
Hi *,
I have installed KJY2010 Honeylicious Icy Faux HC 3.2 but it complains about the missing sim card (model wo G3 connectivity).
I'v tried to disable all apk that have to do with telephony but they are started from rild (I guess) in init.rc which is hardwired in boot.img.
Any other solution than to take boot.img from mmcblk0p2 and modifying init.rc in order to disable rild?
Click to expand...
Click to collapse
If you're running an A500 and followed the install instructions to the letter that are posted in the OP, there's absolutely no reason you should have a sim card message whatsoever. Over 3,000 downloads between the two ROMs, and no errors as such, once again if you're running the A500, and followed the EXPLICIT install instructions (there's also an install video in the OP).
---------- Post added at 05:51 PM ---------- Previous post was at 05:32 PM ----------
Moscow Desire said:
Are you running an a501? or an a500?
EDIT: saw your ()
Did you check your build.prop?
Should say ro.carrier=wifi-only
So if you did your 3 wipes, coming from another rom, you shouldn't get the error.
No need to delete or freeze apk's, or do anything with the image files. Relatively few people have the "please insert sim card" on the 500 series. Usually, because some info wasn't completely wiped.
And if in doubt, you can go to Mounts etc.. And format these things. This will ensure you delete all previous info. Also, you can flash the upgrade to a newer Thor Recovery if you wish, now that we mention it.
Also, it may help, to post this in the specific ROM thread in the development forum. This way, the Dev can specifically answer your issue, instead of general Iconia Q&A
Click to expand...
Click to collapse
Thanks Moscow, you always hit the nail on the head!
magnusPI said:
Thanks for the prompt answer.
Since I'm a good boy I did wipe all
but you are right I have [ro.carrier]: [unknown]
and I didn't post to development because this is my 4th post and I'm not allowed
I hope I can change ro.carrier wo reflashing by editing /system/build.prop
Click to expand...
Click to collapse
There is no ro.carrier line in the build prop on Icy Faux. Attached is the build prop in a text file from the ROM. There is NO ro.carrier line in the build.prop.
You have an old build prop on your tab from a previous ROM from not installing as per instructions in the OP of the ROM!
You can download the file from the attachments below, rename it build.prop, delete your age old build.prop from God knows when, and replace it with the proper one in the attachment.
kjy2010 said:
There is no ro.carrier line in the build prop on Icy Faux. Attached is the build prop in a text file from the ROM. There is NO ro.carrier line in the build.prop.
You have an old build prop on your tab from a previous ROM from not installing as per instructions in the OP of the ROM!
You can download the file from the attachments below, rename it build.prop, delete your age old build.prop from God knows when, and replace it with the proper one in the attachment.
Click to expand...
Click to collapse
And.... don't forget to check your permissions through root explorer when you do it. And.... reboot.
Just to be a tad fair in this, It can happen (no sim card inserted). I get this on my 501 after extended periods on wifi (weekend for example). Reboot typically clears it, and I can promise, I DO have a sim card inserted
Not sure tho why it crops up, maybe I should get an iPad
Also, to be a touch fair, sometimes, the 3 wipes don't get rid of all the leftovers. I ran into this only with Taboonay on a few occassions. Long story. Just seemed there was some leftovers after doing the wipes, and I was forced to wipe again and reflash. Messy business those wipes But extra wipes ensure everything's clean
Moscow Desire said:
And.... don't forget to check your permissions through root explorer when you do it. And.... reboot.
Just to be a tad fair in this, It can happen (no sim card inserted). I get this on my 501 after extended periods on wifi (weekend for example). Reboot typically clears it, and I can promise, I DO have a sim card inserted
Not sure tho why it crops up, maybe I should get an iPad
Also, to be a touch fair, sometimes, the 3 wipes don't get rid of all the leftovers. I ran into this only with Taboonay on a few occassions. Long story. Just seemed there was some leftovers after doing the wipes, and I was forced to wipe again and reflash. Messy business those wipes But extra wipes ensure everything's clean
Click to expand...
Click to collapse
Yes Moscow, but you have a 501, and not a 500. No reason to get that message on a 500.
Furthermore, even just the three wipes will leave residuals on your SDCard, and that's why I have explicit instructions for wiping, and formatting not only typed out in my OP, but in video as well. Impossible to get errors if you follow the instructions to the letter, yet people refuse to, and then have the nerve to post they have a problem, when the problem is in fact "pilot error"!
Moscow Desire said:
And.... don't forget to check your permissions through root explorer when you do it. And.... reboot.
Just to be a tad fair in this, It can happen (no sim card inserted). I get this on my 501 after extended periods on wifi (weekend for example). Reboot typically clears it, and I can promise, I DO have a sim card inserted
Not sure tho why it crops up, maybe I should get an iPad
Also, to be a touch fair, sometimes, the 3 wipes don't get rid of all the leftovers. I ran into this only with Taboonay on a few occassions. Long story. Just seemed there was some leftovers after doing the wipes, and I was forced to wipe again and reflash. Messy business those wipes But extra wipes ensure everything's clean
Click to expand...
Click to collapse
YOU SHOULD WIPE INSTALL THE ROM.. GO BACK INTO CWM.. (BEFORE YOU BOOT FOR FORST TIME) BACK TO WIPE MENUE AND WIPE AGAIN.. .
this has always worked for me.. to keep from these tiny simple issues .
i have very good backups so i format partitions.. then wipe .. install rom then go back and wipe again.. then boot room.. you know its clean when you do this.. . you can also before you boot go into the media folder and delete everything in there if you want TOTAL DISTRUCTION of your personal data..
but im just a chic what do i know..
good luck..
Yeah, like we know, wipe 3 times, check, then wipe some more
You guys are missing the humor
Why so serious?
Oh... to have a 501, the red headed stepchild,,,,
Moscow Desire said:
Yeah, like we know, wipe 3 times, check, then wipe some more
You guys are missing the humor
Why so serious?
Oh... to have a 501, the red headed stepchild,,,,
Click to expand...
Click to collapse
The 501 is not the red headed step child, but there is no reason to get the "insert sim card" notification on this ROMwith an A500 if you do a full and complete wipe according to the instructions and video in the OP.
Sorry, but I have no patience, nor compassion for people that don't take the time to read simple instructions that I've taken the time to not only write, but put up in video format as well.
If they have problems from now on, they can go flash Thor's bug ridden ROM and kernel.
kjy2010 said:
but there is no reason to get the "insert sim card" notification on this ROMwith an A500 if you do a full and complete wipe according to the instructions and video in the OP.
Sorry, but I have no patience, nor compassion for people that don't take the time to read simple instructions that I've taken the time to not only write, but put up in video format as well.
Click to expand...
Click to collapse
I understand that it can be quite annoying to save people from their mistakes
but I read the instructions and I followed them
and I installed on a brand new a500. Probably I did a mistake in wiping.
In any case ro.carrier=wifi-only did the trick.
EDIT: I compared the build.prop I have with the one you posted and they are the same!
I'll experiment with debug.sf.nobootanimation=1 because your bootanimation is very nice but it uses cpu and battery in a world where charge is power
magnusPI said:
Thanks for the prompt answer.
Since I'm a good boy I did wipe all
but you are right I have [ro.carrier]: [unknown]
and I didn't post to development because this is my 4th post and I'm not allowed
I hope I can change ro.carrier wo reflashing by editing /system/build.prop
Click to expand...
Click to collapse
magnusPI said:
I understand that it can be quite annoying to save people from their mistakes
but I read the instructions and I followed them
and I installed on a brand new a500. Probably I did a mistake in wiping.
In any case ro.carrier=wifi-only did the trick.
I'll compare the build.prop I have with the one you posted to see the differences and
I'll experiment with debug.sf.nobootanimation=1 because your bootanimation is very nice but it uses cpu and battery in a world where charge is power
Click to expand...
Click to collapse
The fact that you even had a ro.carrier line in your build prop suggests serious pilot error with regards to following the instructions that were clearly posted in the thread. The build prop from Honeylicious contains no such line.
As to your comment about the boot animation eating up all your battery, I'll leave that one alone, as it speaks volumes on its own lol
magnusPI said:
........ because your bootanimation is very nice but it uses cpu and battery in a world where charge is power
Click to expand...
Click to collapse
...think this comment needs my "boot" where the sun don't shine
kjy2010 said:
The fact that you even had a ro.carrier line in your build prop suggests serious pilot error with regards to following the instructions that were clearly posted in the thread. The build prop from Honeylicious contains no such line.
:
Click to expand...
Click to collapse
You are right and I wrote in a not so precise way.
1) There was no ro.carrier in my build.prop
2) I got ro.carrier undefined from command prompt with getprop
3) I compared the build.prop you posted and it is equal mine (up to the line I added)
diff build.prop build.prop.txt
64,65c64
< # messo da me
< ro.carrier=wifi-only
---
>
magnusPI said:
Thanks for the prompt answer.
Since I'm a good boy I did wipe all
but you are right I have [ro.carrier]: [unknown]
and I didn't post to development because this is my 4th post and I'm not allowed
I hope I can change ro.carrier wo reflashing by editing /system/build.prop
Click to expand...
Click to collapse
magnusPI said:
I understand that it can be quite annoying to save people from their mistakes
but I read the instructions and I followed them
and I installed on a brand new a500. Probably I did a mistake in wiping.
In any case ro.carrier=wifi-only did the trick.
EDIT: I compared the build.prop I have with the one you posted and they are the same!
I'll experiment with debug.sf.nobootanimation=1 because your bootanimation is very nice but it uses cpu and battery in a world where charge is power
Click to expand...
Click to collapse
magnusPI said:
You are right and I wrote in a not so precise way.
1) There was no ro.carrier in my build.prop
2) I got ro.carrier undefined from command prompt with getprop
3) I compared the build.prop you posted and it is equal mine (up to the line I added)
diff build.prop build.prop.txt
64,65c64
< # messo da me
< ro.carrier=wifi-only
---
>
Click to expand...
Click to collapse
Which tab are you using the A500, or A501, even after all this it's still unclear to me.
kjy2010 said:
Which tab are you using the A500, or A501, even after all this it's still unclear to me.
Click to expand...
Click to collapse
A500-10S32
with original android version 3.0.x
kyj2010,
Same thing here tonight! Been using my a500 for about 12+ hours today w/o issue after flashing Honeylicious.
I just got a call and tab locked... When I hit to awake noticed the "insert SIM card" at top of screen and found it odd.
I first went into the build prop to check for the ro.carrier specs but not there! Just as you stated, there is no ro.carrier line...
Searched and found this post...
Also, as a note, I followed your steps to a T after coming from FlexThunder..
iamtek7 said:
kyj2010,
Same thing here tonight! Been using my a500 for about 12+ hours today w/o issue after flashing Honeylicious.
I just got a call and tab locked... When I hit to awake noticed the "insert SIM card" at top of screen and found it odd.
I first went into the build prop to check for the ro.carrier specs but not there! Just as you stated, there is no ro.carrier line...
Searched and found this post...
Also, as a note, I followed your steps to a T after coming from FlexThunder..
Click to expand...
Click to collapse
What do you mean you "got a call and the tab locked"?
Please elaborate on what was going on when this happened. Over 4,000 downloads now and still counting with you two guys on A500s, not A501s are the only ones reporting this issue.
I've got well over 100 flashes into this ROM, and have never seen a sim card message.
It's built on the stock 3.2 image, so there should be no logical reason for it, other than maybe residuals that the wipes and formats aren't cleaning?
Sorry, I got a phone call and my screen locked after 5 minute mark.
I used the Tab since about 5:30am (EST) and can honestly say I do not recall seeing it at any point throughout the day.
At about 9:30pm, my Tab got to 13% battery and I plugged in. I got a phone call and walked away, came back, hit power button to unlock and noticed SIM msg..t
Rebooting now and see if still there. I,ll report back as to status.
BTW: 15+ hours of pretty steady use, installing apps, browsing web, wife streamed MTV shows as I watched NFL games, played a few games on Tab and still have battery!!
Great battery life with Honeylicious!! Thanks!
Update:
Reboot and still present...
iamtek7 said:
Sorry, I got a phone call and my screen locked after 5 minute mark.
I used the Tab since about 5:30am (EST) and can honestly say I do not recall seeing it at any point throughout the day.
At about 9:30pm, my Tab got to 13% battery and I plugged in. I got a phone call and walked away, came back, hit power button to unlock and noticed SIM msg..
Rebooting now and see if still there. I,ll report back as to status.
BTW: 15+ hours of pretty steady use, installing apps, browsing web, wife streamed MTV shows as I watched NFL games, played a few games on Tab and still have battery!!
Great battery life with Honeylicious!! Thanks!
Click to expand...
Click to collapse
If you mean the screen locked at the lock screen, just click the power once, wait a sec, click it again and unlock. I'm working on something right now, give me a few, and I'll have a file posted in this thread for you to try. I need to test it first, but I'll need someone that's getting the message to test it after I make sure it's safe to flash
Related
Here is the OP from the voodoo for fascinate thread in this forum:
EDIT:
okay i got it. Im guessing i choose the "11/11 stable" one. here goes nothin
thanx guys!!!!!!!!!!!1
jt1134 said:
After you read this WHOLE post, read it again. If you are unsure about something, check the links below. kthx
OK guys, here it is.
For those unfamiliar with Voodoo : http://project-voodoo.org/
This kernel includes ONLY the voodoo lagfix, no color fix ATM.
For FAQs : http://project-voodoo.org/faq
Also now included is the option of using aosp style bootanimations. The attached zips include one. If you want to use your own, then place a compatible bootanimation.zip in either /system/media or /data/local.
http://www.droidforums.net/forum/droid-hacks/33932-bootanimation-zip-file-explained.html
http://www.dkszone.net/how-to-create-custom-boot-animation-for
First off, have PATIENCE PATIENCE PATIENCE!!!!!!
It takes a WHILE on the first boot to do the conversion and copy over your data. If you decide to revert back to stock, it will take a WHILE then to convert back. Don't reboot, let it do its thing.
Once you've flashed this kernel, don't just go flashing other kernels. Voodoo changes some key parts of your system and you will have fix them by hand if you flash another kernel without removing voodoo first. To remove, simply do adb shell "> /sdcard/Voodoo/disable_lagfix" and then reboot. If you want to re-enable voodoo, then remove that file.
If you have less than 220mb of space remaining on internal storage, then clean some stuff out before flashing this. I have also included a 1.2GHz overclocked kernel.
For those who get excited from staring at Quadrant all day: I KNOW YOUR SCORES ARE NOT AS HIGH AS THEY ARE WITH THE EXT2 "LAGFIX". This is to be expected. Voodoo does not mess with /dbdata but only /data. THIS RESULTS IN ABSOLUTELY NO LOSS OF FUNCTIONALITY OR USEABILITY.
If you are running the ext2 "lagfix", please uninstall it before using this. If you have problems, wipe data and try again. Voodoo should retain data, but nothing is foolproof. Be prepared to lose your data! If you have problems with force closes after uninstalling, make sure to wipe using the option in the privacy menu.
Thanks to Dirrk and DataSpree for help getting the kernel in a useable condition, and thanks to SuperCurio for the original lagfix and clues on how to get it working with the Fascinate.
If you would like to look at the code for yourself, please check my github @ github.com/jt1134
Enjoy!
******EDIT******
For anyone who flashed v0.1, I made a stoopid. Sorry. I've attached a fixed version. You will need to uninstall the current voodoo before flashing this. To uninstall simply do : adb shell "> /sdcard/Voodoo/disable_lagfix" . or, create a blank file in your favorite manner. You can also do this with a file explorer program such as Astro or Root Explorer. Then reboot. Once you've booted into android successfully, you can install the attached zip. If voodoo does not reinstall for you, make sure you have deleted /sdcard/Voodoo/disable_lagfix. Repeat: this is only if you are running v0.1!
edit: removed attached kernels. newer versions available on rom manager.
If you enjoy the work I do, you can contribute to my beer fund. Beer helps me think!
Click to expand...
Click to collapse
where the hell do i click to download the files. am i losing my mind or what!!!!!!!!!!!
Gotta read, man.
edit:
I should read edits, too
jt1134 said:
edit: removed attached kernels. newer versions available on rom manager.
Click to expand...
Click to collapse
There are a lot of words there... *shrugs*
CouchSpud said:
There are a lot of words there... *shrugs*
Click to expand...
Click to collapse
does it have to be rom manager premium??????????? i got the free one.
EDIT:
okay i got it. Im guessing i choose the "11/11 stable" one. here goes nothin
thanx guys!!!!!!!!!!!1
fupamobile said:
does it have to be rom manager premium??????????? i got the free one.
EDIT:
okay i got it. Im guessing i choose the "11/11 stable" one. here goes nothin
thanx guys!!!!!!!!!!!1
Click to expand...
Click to collapse
you really dont seem like someone capable of handling voodoo atm....there have been plenty of posts on all this stuff for months....use the search button
This is a bad time to flash to voodoo. DJ05 is right around the corner, and removing voodoo has resulted in more "help me" threads than anything else on this forum. That being said...
Who wants to start the bidding? 3:1 says he will have a "HALP ME MY FONE IS RUINED" thread within 2 days of DJ05 release.
Edit: Prediction #2, his plea for help post will include uninterrupted punctuation 10+ symbols long.
Its like you've seen this before or something!
Sent from my SCH-I500 using Tapatalk
Well here is RC2
OMFG Thank's to Mz, Fj, 3rd, Lm, Sh, and last but not least you reading this
See that way i thank everyone no one is missed, thank you once again
Especially thanks' to All the testers that i royally messed their phones up..
Do some of them still turn on? LOL
Ok..... So now that the pleasantries are out of the way, to the nitty gritty <
Governors are back and working!!!
So that means[EDIT] The OC should be @1000 not sure of the vsel depends what you do with it, 68 is stable all the time... due to Camera stability issues} all the time, trust me the batt will not OH and batt life will be awesome
Sqlite3 hacks
160/sms char
Fixed dialer
Fixed Libs!!!
Thank Mz for giving me the wrong utilities that sent me in to dependency hell for about 8 hours....
But it did force me to fix some crappy broken dependency i didn't even knew existed in the filesystem.
MOC working
EXT4 WORKING OMFG the speed and stability OMFG
Email fixed
MMS 3g fix here Thx MZ, Fj + JP8 and Lm
http://forum.xda-developers.com/showpost.php?p=17510536&postcount=452
A2sd Fixed,
Dalvik-cache to ext or cache FIXED yes no more stuck at M <Disable Dalvik Jit in A2sd GUI, it's broken but already enable by default in the ROM.>
Mega standby time
How to,
this one is a little more complicated than before but it due to moving to the new file system.
1. You need to have the New OR put together by Mz and Fj, just copy to root of SD card.
*****NEW*****
Mz and FJ put out a new OR, Very very very nice, and i added Supercharger V6.
+
Now listen Kids DO NOT USE BULLET PROOF!!!
It will cause an immortal loop in killing and starting processes that will kill you bat in no time.
The rest seems fine so far... I Have really tested it and SCV6 does OOM right files and seems to have stabilized a few MEM leaks actually....
Thanks zeppelinrox
http://www.mediafire.com/?ix49xm0r0h448dg
2. If you have ext2 or 3 just format to ext4 with OR SD utilities.
If you already have EXT4 made with OR you are fine, but if formatted from gparted or something else it wont work!
You need format back to ext2 with you fav util and see step 2.
3. Restore back up
http://www.mediafire.com/file/g3xz3d11wygqyly/XDASp_HmE_RC2.zip
Mirror Thanks Lm
http://www.megaupload.com/?d=2Q7S4D3W
Swap fix see attachment
run from shell after swapfix update
Code:
chmod 777 /system/etc/init.d/00_swapon
something broked when setting permissions....
Run your favorite a2sd command like
1. a2sd reinstall
2. a2sd cachesdreset
3. a2sd reswap
Profit!!!!
Use boot2 for fast boot.
None of the above parties are responsible if implementing any of the above changes causes the world to end and kittens to catch on fire or the mail being late, not even if your phone turns into a transformer and takes over the world and enslaves the human race I will not be responsible or any person mentioned above... well maybe Fj, he's Russian like who cares right???
Joking lol, Fj isn't responsible either... <3
Why WIND has issues with SMS and MMs especially if your number was originally ported from another provider or had a temporary number associated to the SIM..
Thanks R-D
http://forum.xda-developers.com/showpost.php?p=17198867&postcount=303
Work around for broken Wind SIM card.
http://forum.xda-developers.com/showpost.php?p=17274125&postcount=410
How to disable Roaming and MMS fix
http://forum.xda-developers.com/showpost.php?p=17166396&postcount=362
After all that update to XDA Special STOCK multi lang stock patch
EXPERIMENTAL NEED TO FULL WIPE AFTER!
http://forum.xda-developers.com/showpost.php?p=17459698&postcount=440
sileshn made a nice mod for us Thanx man
http://forum.xda-developers.com/showpost.php?p=17416499&postcount=1
++Screen SHOTS!!!!
Файл, который Вы пытаетесь открыть, временно недоступен. Повторите попытку позднее.
Translation:
File, that you trying to open, temporary unavailable. Try later..
fjfalcon said:
Файл, который Вы пытаетесь открыть, временно недоступен. Повторите попытку позднее.
Translation:
File, that you trying to open, temporary unavailable. Try later..
Click to expand...
Click to collapse
Im uploading to mediafire now
hellmonger said:
If you want TV out to work you need to flash from singapore SBF/
Will work from anything, but if you want to report bugs please state the following in your post.
Click to expand...
Click to collapse
Thank you for this ROM.
Have you solve problem with umount all mounts on sdcard before reboot?
fjfalcon said:
Have you solve problem with umount all mounts on sdcard before reboot?
Click to expand...
Click to collapse
Not exactly.....
RC1... EXT4 works
Left for final
1. EXT unmount on shutdown
2. make a pretty boot animation.
3. Fix color difference in icons.....
hellmonger said:
Not exactly.....
RC1... EXT4 works
Left for final
1. EXT unmount on shutdown
2. make a pretty boot animation.
3. Fix color difference in icons.....
Click to expand...
Click to collapse
Ok, downloading now..!
I'm very happy with CM6 but hey, I can't resist flashing a new ROM..
Question: So if i don't have EXT4, no issues? Will app2extr still work with my EXT3 partition? Thanks again!
Wow dude, i don't know what to say, I'm literally like a kid at christmas! LMAO! Thanks a lot Hellmonger Been eagerly waiting but know you been workin hard on this Beaut! Awesome work man and thanks for your help Mz you been performing miracles lately! Nice work on ext4 bud! and everyone else. Thanks Peshovic and fjfalcon as well. Trying now!
Know I'm a nub here and all, but I've got an rooted, SIM-Unlocked Cincy Bell XT720. I'll pitch this ROM on (tried out Dexter's 2.2 already) and let you guys know how it works on WIND Mobile (Canada). O-^
Well...I installed it. Went over smoothly, things appeared fine at a first glance. But, I'm still failing to be able to connect to Wind Home (3G - non roaming). The phone's completely SIM-unlocked, sees both WIND Away (Rogers - 2G) and WIND Home, but I'll either get a "Your SIM Card does not allow a connection to this network" problem, or the network just fails to connect outright. I think it may be a problem with the radio or some other form of configuration with this thing...something stupid I'm not finding. Can anyone help me out here? :/
RyanGDI said:
Well...I installed it. Went over smoothly, things appeared fine at a first glance. But, I'm still failing to be able to connect to Wind Home (3G - non roaming). The phone's completely SIM-unlocked, sees both WIND Away (Rogers - 2G) and WIND Home, but I'll either get a "Your SIM Card does not allow a connection to this network" problem, or the network just fails to connect outright. I think it may be a problem with the radio or some other form of configuration with this thing...something stupid I'm not finding. Can anyone help me out here? :/
Click to expand...
Click to collapse
wow, I wonder how you were able to post in development right away with your very first post? Anyway make sure you have background data turned on first then try apn manager maybe.
***Help***
Not sure how to mount ext4 it's saying this ROM may not support it?
***also-- Just seen this clock widget, haven't checked yours out just thought I'd post this fyi BobClockD3-green and here is a pic
LibertyMonger said:
wow, I wonder how you were able to post in development right away with your very first post? Anyway make sure you have background data turned on first then try apn manager maybe.
***Help***
Not sure how to mount ext4 it's saying this ROM may not support it?
Click to expand...
Click to collapse
I'm not sure about how I ended up being able to post here...probably because my account's been around since December '09, I perhaps have some "seniority" factor or something along those lines that defies the post limit. No idea...
Anyways, I can pin it down precisely to a "Your SIM does not allow a connection to this network" error. I've got my APNs configured perfectly and set up, and have all of my data settings on. When I go to manually select a network, WIND Home consistently becomes available. I'll select it though, and I get a "Selected network (WIND Home) unavailable" notification, followed by the SIM error 1-2 minutes later. I can connect to WIND Away with great signal strength, and even pull 3G roaming...I've tried everything in here (http://forum.xda-developers.com/showthread.php?t=974375) including SMSC config and locking the band to WCDMA through the hidden phone menu for detecting WIND Home only.
I hate being a noob here, tromping on this guy's latest release with this problem. I'd just make a separate thread on the matter and get help that way, but it seems a bit excessive to start two discussions on the same topic. Sorry, and thanks in advance for all the help.
RyanGDI said:
I'm not sure about how I ended up being able to post here...probably because my account's been around since December '09, I perhaps have some "seniority" factor or something along those lines that defies the post limit. No idea...
Anyways, I can pin it down precisely to a "Your SIM does not allow a connection to this network" error. I've got my APNs configured perfectly and set up, and have all of my data settings on. When I go to manually select a network, WIND Home consistently becomes available. I'll select it though, and I get a "Selected network (WIND Home) unavailable" notification, followed by the SIM error 1-2 minutes later. I can connect to WIND Away with great signal strength, and even pull 3G roaming...I've tried everything in here (http://forum.xda-developers.com/showthread.php?t=974375) including SMSC config and locking the band to WCDMA through the hidden phone menu for detecting WIND Home only.
I hate being a noob here, tromping on this guy's latest release with this problem. I'd just make a separate thread on the matter and get help that way, but it seems a bit excessive to start two discussions on the same topic. Sorry, and thanks in advance for all the help.
Click to expand...
Click to collapse
Well for starters, I am connected with 3g plus wifi so no probs there for me. Everything is freakin awesome so far! Love the Mean Green Glad to have it back! Nice pic for wallpaper! speed is perfect for me, don't need that Super crazy over the top speed lol.
(EDIT-actually after overclocking to 1000 it is super crazy fast!)
Not sure where your prob is yet first I heard of that issue. Did you start with Singapore SBF? Maybe just wait for someone else to reply since I'm not familiar with that issue bud.
***My only issue so far is can't mount my ext4. I repartitioned and flashed Singapore sbf. Restored all my apps and have about 20mb left it's saying ROM may not support ext4.
hellmonger said:
Not exactly.....
RC1... EXT4 works
Left for final
1. EXT unmount on shutdown
2. make a pretty boot animation.
3. Fix color difference in icons.....
Click to expand...
Click to collapse
If you want, I can make a boot animation.
Say me if you want I post one.
LibertyMonger said:
Well for starters, I am connected with 3g plus wifi so no probs there for me. Everything is freakin awesome so far! Love the Mean Green Glad to have it back! Nice pic for wallpaper! speed is perfect for me, don't need that Super crazy over the top speed lol.
(EDIT-actually after overclocking to 1000 it is super crazy fast!)
Not sure where your prob is yet first I heard of that issue. Did you start with Singapore SBF? Maybe just wait for someone else to reply since I'm not familiar with that issue bud.
***My only issue so far is can't mount my ext4. I repartitioned and flashed Singapore sbf. Restored all my apps and have about 20mb left it's saying ROM may not support ext4.
Click to expand...
Click to collapse
Alright, thanks...I'm dead sure this is a Cincy Bell (saw the links for Cincy Bell website sites with the Moto portal tool when I first got it), but I'll just ask in the General section and leave this thread in peace. Again though, at least I can vouch for the fact that installing this ROM and fiddling around with it didn't screw it up in any way...one more bit of peace of mind for prospective flashers.
Thanks a lot !!!!!
But does an ext3 partition will work ???? Do you have to make an ext4 part? (to make you have to follow the same order than before with the ext3???) Can you move your apps from ext3 to ext4????
Someone have the ext4 working?
B_e_n said:
Thanks a lot !!!!!
But does an ext3 partition will work ???? Do you have to make an ext4 part? (to make you have to follow the same order than before with the ext3???) Can you move your apps from ext3 to ext4????
Someone have the ext4 working?
Click to expand...
Click to collapse
Maybe I will try convert-ext4 -Converts an EXT3 partition to an EXT4 partition.
I have my old sdcard with ext3 still.
Also I tried boot.img, boot2.img and boot5.img, it appears boot.img is the one for now?...
LibertyMonger said:
Maybe I will try convert-ext4 -Converts an EXT3 partition to an EXT4 partition.
I have my old sdcard with ext3 still.
Also I tried boot.img, boot2.img and boot5.img, it appears boot.img is the one for now?...
Click to expand...
Click to collapse
So you haven t apps2ext for the moment?????
B_e_n said:
So you haven t apps2ext for the moment?????
Click to expand...
Click to collapse
No, trying! lol. I am trying ext3 now. I know it's probably something easy to fix. But I have tried all I know with ext4 and apps wouldn't move over...
I got ext3 to work, need to check my apps then try to change to ext4 i guess...
Zachary57 said:
If you want, I can make a boot animation.
Say me if you want I post one.
Click to expand...
Click to collapse
Well i would like the seconnd part of the curent boot animation to fade in and out
"XDA Special" at the top and
Hellmonger Edition" st the bottom.
EXT2 3 and 4 should work EXT4 is isainly fast nd should auto mount at start up
Anyone having errors with v6 supercharger such as bootloops? should go grab the new version posted today. I'm about to try it out now myself.
http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
I hate to sound like robert stack all the time but... Update!: New script works perfect no bootloops anymore and some of the old options are gone such as the integration option. Its fairly automatic after running option 9 and you now can let the script wipe your caches without any problems! Nice! Thanks zeppelinrox!!
heh.. you're welcome!
I felt bad about all the supercharger posts in the CM7 thread so it's better to keep it separate
Feel free to try The Die-Hard Battery Calibrator test 2... it's attatched to the same post.
If it doesn't read your voltage or status (plugged in or not) or battery percentage, run these 2 commands in terminal and copy all and paste it here without formatting anything:
Code:
ls /sys/class/power_supply/battery
cat /sys/class/power_supply/battery/*
First command will list the battery folder's contents (file names)
Second command will show the contents of those files
zeppelinrox said:
heh.. you're welcome!
I felt bad about all the supercharger posts in the CM7 thread so it's better to keep it separate
Feel free to try The Die-Hard Battery Calibrator test 2... it's attatched to the same post.
If it doesn't read your voltage or status (plugged in or not) or battery percentage, run these 2 commands in terminal and copy all and paste it here without formatting anything:
Code:
ls /sys/class/power_supply/battery
cat /sys/class/power_supply/battery/*
First command will list the battery folder's contents (file names)
Second command will show the contents of those files
Click to expand...
Click to collapse
sorry for noob questions.
What does the Die-Hard battery calibrator test 2 do?
Helps calibrate the battery so that you can be sure that mV match up with % level and that it's charging properly.
Sometimes when charging it will say 100% when it really isn't.
If you never flash a new rom you only need to do it once but if flashing different roms, its a good idea to calibrate the battery after each flash.
So I should wait till I'm at 4200mv / 100%, until I actually run the battery calibrator script?
zeppelinrox said:
Helps calibrate the battery so that you can be sure that mV match up with % level and that it's charging properly.
Sometimes when charging it will say 100% when it really isn't.
If you never flash a new rom you only need to do it once but if flashing different roms, its a good idea to calibrate the battery after each flash.
Click to expand...
Click to collapse
So this basically does the same thing as the battery callibration app from the market or is this other way more accurate or informative?
I'll give it a go... script says it needs to be at 4200mv (100%) before running calibration. You can override it and run the script if you want, but it makes sense to calibrate at 100%. I'll report back once I try... only at about 70% now.
Swiftks said:
I'll give it a go... script says it needs to be at 4200mv (100%) before running calibration. You can override it and run the script if you want, but it makes sense to calibrate at 100%. I'll report back once I try... only at about 70% now.
Click to expand...
Click to collapse
Then this script seems exactly the same as the battery callibration app from the market which is also free by the way and completely trouble free cause I use that after every new flash.
Ya I couldn't believe somebody made an app to just do a simple rm command.
At first mv wasn't even used so I had posted on the first page of it's xda thread about it.
I did like the idea to prevent calibration until the battery met certain conditions tho
Since we've got a thread about this..I've got a couple newb questions. I followed the tutorial here:
http://androidforums.com/ascend-all...-run-zeppelinroxs-v6-supercharger-script.html
To install the V6 Supercharger script, and it seems all went fine. I've noticed in other threads people mentioning selecting the +1000HP option, and I'm wondering what i'm missing, as that wasn't even an option in that particular script.
I noticed you've got some other updates and stuff..but i've tried running the 3G Turbocharger script..and still don't see the option for +1000HP?
Rickroller said:
Since we've got a thread about this..I've got a couple newb questions. I followed the tutorial here:
http://androidforums.com/ascend-all...-run-zeppelinroxs-v6-supercharger-script.html
To install the V6 Supercharger script, and it seems all went fine. I've noticed in other threads people mentioning selecting the +1000HP option, and I'm wondering what i'm missing, as that wasn't even an option in that particular script.
I noticed you've got some other updates and stuff..but i've tried running the 3G Turbocharger script..and still don't see the option for +1000HP?
Click to expand...
Click to collapse
Install instructions in my noob guide. See top of general section or my sig for link.
Sent from my MB860 using xda premium
Which version of this in this thread is working on atrix 4g?
nikdimas said:
Which version of this in this thread is working on atrix 4g?
Click to expand...
Click to collapse
The most recent Release Candidate.... see install instructions in my NooB Guide.
Rickroller said:
Since we've got a thread about this..I've got a couple newb questions. I followed the tutorial here:
http://androidforums.com/ascend-all...-run-zeppelinroxs-v6-supercharger-script.html
To install the V6 Supercharger script, and it seems all went fine. I've noticed in other threads people mentioning selecting the +1000HP option, and I'm wondering what i'm missing, as that wasn't even an option in that particular script.
I noticed you've got some other updates and stuff..but i've tried running the 3G Turbocharger script..and still don't see the option for +1000HP?
Click to expand...
Click to collapse
+1000 hp option is number 9 I believe on the 1-30 menu on the rc3.2 script and 3.1
how do you know if the v6 script is running?
andyt315 said:
how do you know if the v6 script is running?
Click to expand...
Click to collapse
as long as you enabled the correct file (can't remember the name right now) to run as root & on boot, it should be running. Upon boot, after launcher loads, you should see a message pop up saying Script Manager has been granted super user permission.
If you need further instruction, see my install guide, in my N00B guide thread.
Im running the At(honeycomb)RIX ROM and Inhave the v0.2.1 1.3 kernel can I run this script or do I need to have CM7????
sk8trix said:
Im running the At(honeycomb)RIX ROM and Inhave the v0.2.1 1.3 kernel can I run this script or do I need to have CM7????
Click to expand...
Click to collapse
yes, you can run it.
Swiftks said:
as long as you enabled the correct file (can't remember the name right now) to run as root & on boot, it should be running. Upon boot, after launcher loads, you should see a message pop up saying Script Manager has been granted super user permission.
If you need further instruction, see my install guide, in my N00B guide thread.
Click to expand...
Click to collapse
you can check this log in super user log right? i didn't see it, can you check yours see it logged in your super user?
andyt315 said:
you can check this log in super user log right? i didn't see it, can you check yours see it logged in your super user?
Click to expand...
Click to collapse
My Superuser log shows it allowed.... if you want to confirm that it installed correctly, you can re-run the script and choose option 1.
hi all,
a few hours ago i install HoneyVillain 1.2 and i have 2 problems,
1) on every boot i got a message " no sim inserted" but my tablet hasnt any working sim slot.is there any way to remove this message?
2) on every boot i got an error message the application systemupdater (process com.FD.updater) has stopper unexpectedly.please try again if i select force close i can work with no further problems.if i left it for a while my tablet rebooting and i get the same message again..any solution??
thanks in advance
android-noob said:
hi all,
a few hours ago i install HoneyVillain 1.2 and i have 2 problems,
1) on every boot i got a message " no sim inserted" but my tablet hasnt any working sim slot.is there any way to remove this message?
2) on every boot i got an error message the application systemupdater (process com.FD.updater) has stopper unexpectedly.please try again if i select force close i can work with no further problems.if i left it for a while my tablet rebooting and i get the same message again..any solution??
thanks in advance
Click to expand...
Click to collapse
You SN is aptly named
Literally two posts below yours http://forum.xda-developers.com/showthread.php?t=1230744&highlight=ro+carrier
Perhaps the response was helpful to android-noob, I'm not sure. However, I have searched for quite a while and don't see anything relating to the questions that result in actual help to fix the problems. I certainly take full credit for being an android idiot but we all start somewhere when we're trying to learn new things. I've been trying to learn from reading and this is quite honestly the best forum for everything that has to do with phones and tablets.
I would appreciate a simple link or response that might be of help to fix the problem of suddenly getting the errors listed by the first poster if you would be so kind.
Thank you for any help you can give.
docvicki said:
Perhaps the response was helpful to android-noob, I'm not sure. However, I have searched for quite a while and don't see anything relating to the questions that result in actual help to fix the problems. I certainly take full credit for being an android idiot but we all start somewhere when we're trying to learn new things. I've been trying to learn from reading and this is quite honestly the best forum for everything that has to do with phones and tablets.
I would appreciate a simple link or response that might be of help to fix the problem of suddenly getting the errors listed by the first poster if you would be so kind.
Thank you for any help you can give.
Click to expand...
Click to collapse
Let's see. I did provide a link in my response, and the last post on the page of the link I gave had the fix for the sim card message. How much more spoon feeding will you require?
first you need file manager with root access
Sim card messages:
Go to system there is a file called build.prop ,open it and add the line ro.carrier=wifi-only,you can add this line on the bottom of the file for example and les and save the file.
Reboot and the simcard message should be gone.
For the fd.updater problem:
That is because the build prop is changed so the update service doesn't recognize it.
That is no problem I delete this in my roms so you won't have that stupid message.
What you can do is go to system/app, find fd.updater.apk and fw.updater (i think that is the correct name) and rename them by putting a .bak behind the name of the apps.
Reboot and the messages should be gone.
civato said:
first you need file manager with root access
Sim card messages:
Go to system there is a file called build.prop ,open it and add the line ro.carrier=wifi-only,you can add this line on the bottom of the file for example and les and save the file.
Reboot and the simcard message should be gone.
For the fd.updater problem:
That is because the build prop is changed so the update service doesn't recognize it.
That is no problem I delete this in my roms so you won't have that stupid message.
What you can do is go to system/app, find fd.updater.apk and fw.updater (i think that is the correct name) and rename them by putting a .bak behind the name of the apps.
Reboot and the messages should be gone.
Click to expand...
Click to collapse
If he's not going to read the same answer on the link I posted, what makes you think he's going to read your post?
kjy2010 said:
Let's see. I did provide a link in my response, and the last post on the page of the link I gave had the fix for the sim card message. How much more spoon feeding will you require?
Click to expand...
Click to collapse
Woweeeeeee.spoon feeding sucks I been there for 12 weeks twice this year while recovering from shoulder surgery.then again less then a month ago.
Op I do not have this or any of the other known issues with the custom roms.thou I know they can bring some extra speed and apps.
Kjy can you go spoon shopping for me.Erica needs some new winter boots.
Giggles.
Goodluck. OP ..
BACKUP THE BUILD .prop file before you edit it.
Thanks for your reply and for being so kind in it. I was able to repair my problems right after I posted, which is why I rarely post. I have no formal computer education, self taught. I normally do pretty well but run into problems once in a while that stump me. This forum is a true Godsend to a 63 year old woman. Thanks again.
Sent from my A500 using XDA Premium App
Thanks so much.
Sent from my A500 using XDA Premium App
kjy2010 said:
If he's not going to read the same answer on the link I posted, what makes you think he's going to read your post?
Click to expand...
Click to collapse
I'm nice to old ladies,
Honeyvillain 1.2 problems
civato said:
I'm nice to old ladies,
Click to expand...
Click to collapse
Yes you are, your Mother would be proud. Seriously, thanks.
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