Related
I get this message when I boot up.
I cannot access settings so I cannot perform a factory reset.
Is there any way to factory reset when you cannot access "Settings" because of constant force closes.
I am running stock but with lots of side-loaded apps.
I can access the file explorer. That is the only thing I can open that will remain open even though I get constant force close popups like "android.process.acore has stopped... android.process.media has stopped unexpectedly...
Is my gtab toast? Can it be saved or should I return it?
I get this all the time, with all the mods I do. Don't worry, your system is fixable.
For me, I use clockworkmod recovery .08. There's a "fix permissions" option and this always fixes the problem for me. It also allows a data wipe within recovery.
If you are 100% stock, you could try one of the stock ROM's here as well - that might get you working. You have a few options, here. Check out the FAQ in my signature. I'm actually posting up the new stock update that I pulled from TnT, today.
EDIT: Direct link the the stock ROM updates -- http://forum.xda-developers.com/showthread.php?t=842000. You'd need to understand how to actually run these, which I mention in the FAQ section.
thx Roebeet, I was able to update to the new stock rom.
But I still have the same problem. Is there any other way to wipe my data. Can it be done while connected by usb or do i have to root it?
Is there any hardware button method to do a factory reset?
I still cannot open settings... it gets canceled by the force closes.
I am ready to give upon my G-Tab which I was enjoying so much.
Does anyone know how to wipe the date if you cannot open settings???
Try clockworkmod - it really is a great tool. You can find it in the Tnt Lite dev section as I have a link for .08.
For UID issues, "fix permissions" will correct it. And you can wipe data via clockworkmod as well. You can even remove it by flashing back to stock -- the latest stock firmware works as I've done it myself, the other day.
Btw, there are so many threads here that I sometimes miss replying. I dont ignore, I just might miss a post. Always feel free to PM me if you have a question.
I had a similar issue where something got corrupted in my user data and I was completely unable to start the settings or open the keyboard. I had to flash back to the full vanilla ROM because it contained clockworkmod, which was the only option available to accomplish a factory reset. That wasn't a fun day.
Think I figured out a key reason for sudden UID issues
People including me are getting UID errors even after having a stable rom and several reboots with no issues. Based on guinea piggin' my G, I can confirm the issues happen on apparently stable installs anytime you update a Google app.
Case in point, I updated Google Voice and Gmail and soon after I rebooted the G- UID city. I have started with a clean rom and installed many different apps to test. The only apps that hose the device at reboot are the GAPPS and it is not just if you update with the package. Simply updating from market will work fine, until you reboot and then it is a few minutes for trying to shut the device down and then perhaps two reboot attempts using fixed permissions.
TnT 2.20 (at least) does NOT like GAPP updates. How could VS bork this up so bad that fundamental apps for Android bork the device?
Again, the Tap UI team and who hired them and approved it on the Gtablet should be fired, rehired for a minute and then fired for good. Word.
This sounds kind of "preachy," but don't give up.
There is a learning curve to the G-Tablet, and it takes a good bit of reading on this site and assimilating the info.
I will testify that I had a hugely bad malfunction and and even worse fix on my tablet.
Using suggestions from helpful folk -- and carefully researching what I needed to do -- I was able to get my tablet back working just fine. To be sure, it's not stock any more!!! But I actually believe that with all I learned about flashing, mods, etc., I now could go back and make it stock again if I wanted to.
Don't give up. Just keep reading and researching the learning.
Rev
rushless said:
People including me are getting UID errors even after having a stable rom and several reboots with no issues. Based on guinea piggin' my G, I can confirm the issues happen on apparently stable installs anytime you update a Google app.
Case in point, I updated Google Voice and Gmail and soon after I rebooted the G- UID city. I have started with a clean rom and installed many different apps to test. The only apps that hose the device at reboot are the GAPPS and it is not just if you update with the package. Simply updating from market will work fine, until you reboot and then it is a few minutes for trying to shut the device down and then perhaps two reboot attempts using fixed permissions.
TnT 2.20 (at least) does NOT like GAPP updates. How could VS bork this up so bad that fundamental apps for Android bork the device?
Click to expand...
Click to collapse
Not true for me, I installed the new Gmail from the Market with no problems. I am on TNTLite 2.2.1.
Google Voice has always been a hack for a tablet, since it is not actually phone. You might want to pull it out and see if your issues are solved.
I am back up and running thanks to clockwordmod. Thanks again!
ninjaprofessor said:
I am back up and running thanks to clockwordmod. Thanks again!
Click to expand...
Click to collapse
Good to hear and thanks for the update!
I am currently having this problem. I am hoping to sell my 10" Android 2.2 Tablet PC on Craigslist... I need to fix this Error... I've only used it 10 times to play Angry Birds. The forum with the links I am confused as to what one to use... I am younger I must say. I am not a 21 year old "computer whiz"/.NET/OS maker... I do make websites. Besides that... I do not know how to "Wipe my system partition" as my Error message says to. Especially due to the fact I cannot open Settings. PLEASE HELP. I may have repeated things said above in his problems but I would like a "NOOB" walk through... (Because I am one). Please help. Thanks in advance. -Sophomoric
Hey, I had a same after my phone battery was empty and it turned off. I kept it off and recharged it, then I had the feeling "I'm feeling Lucky" -.-' so nice from google. xD
Had to wipe everything then full reinstall... such a pain.
Probably the cleanest solution HERE
I've been ripping my hair out the last couple days trying to figure this out.
In the process of flashing a ROM and kernel I did a number of things:
-Carrier unlock (I feel like this is the culprit)
-Unlocked the bootloader
-Flashed Wet Dream (2.3.6 build)
-Installed webtop
-Attempted to root, unsuccessfully (let me know when the 2.3.6 root is available, haha)
After all this, everything was working fine--including wifi. But somewhere along the lines, maybe 15 minutes after I complete all these steps, out of the blue my wifi won't connect. It just says "obtaining IP address" and never connects.
So I got pissed and went on a wiping/reflashing spree. Got everything reset. The wifi was working great again. Then randomly, it just stopped working again.
Question:
Does anyone know why this is happening and what I can do to fix it?!
I'm dying here. Just as a side note in case you need this information, I think I'm going to flash to the 2.3.4 Wet Dream so I can root my device. Also, I don't mind going back to stock. If that's what fixes, it then I'll be more than happy to go stock. I plan on running webtop2sd as well.
Thanks in advance.
Mankey Magic said:
I've been ripping my hair out the last couple days trying to figure this out.
In the process of flashing a ROM and kernel I did a number of things:
-Carrier unlock (I feel like this is the culprit)
-Unlocked the bootloader
-Flashed Wet Dream (2.3.6 build)
-Installed webtop
-Attempted to root, unsuccessfully (let me know when the 2.3.6 root is available, haha) <-- i think this one no need to do
After all this, everything was working fine--including wifi. But somewhere along the lines, maybe 15 minutes after I complete all these steps, out of the blue my wifi won't connect. It just says "obtaining IP address" and never connects.
So I got pissed and went on a wiping/reflashing spree. Got everything reset. The wifi was working great again. Then randomly, it just stopped working again.
Question:
Does anyone know why this is happening and what I can do to fix it?!
I'm dying here. Just as a side note in case you need this information, I think I'm going to flash to the 2.3.4 Wet Dream so I can root my device. Also, I don't mind going back to stock. If that's what fixes, it then I'll be more than happy to go stock. I plan on running webtop2sd as well.
Thanks in advance.
Click to expand...
Click to collapse
try check in: settings-- battery & data manager--battery mode ( see what presets u use).
then try check: settings--wireless & network settings--wifi settings--advanced (press menu key(the left touch key in bottom)--wifi sleep policy-- set to never.
btw, wetdream should be already rooted. correct me if im wrong.
hope this help.
benjat said:
hope this help.
Click to expand...
Click to collapse
Benjat, thanks for the reply.
My battery settings were set to "Nighttime saver". I set it to "Performance mode".
I set my wifi sleep policy to Never.
Still have the same problem.
My understanding was that WD was already rooted, but Busybox wasn't installing so I ran Root Check Basic from the Market and it said my device did not have root access
Mankey Magic said:
Benjat, thanks for the reply.
My battery settings were set to "Nighttime saver". I set it to "Performance mode".
I set my wifi sleep policy to Never.
Still have the same problem.
My understanding was that WD was already rooted, but Busybox wasn't installing so I ran Root Check Basic from the Market and it said my device did not have root access
Click to expand...
Click to collapse
maybe try reboot the phone after change the setting?
im not sure about busybox. what apps u running that require busybox? i want to try install it.
*i just try download root check basic. got message "your device isn't compatible with this item" hehe
Reboot and still no dice.
Ahhhh! So frustrating!
I was mid webtop2sd install and busybox is required for one of the steps to work. I'm actually not sure what it does.
Mankey Magic said:
Reboot and still no dice.
Ahhhh! So frustrating!
I was mid webtop2sd install and busybox is required for one of the steps to work. I'm actually not sure what it does.
Click to expand...
Click to collapse
last try.. remove all wifi network added.. double check all the things i post before.. switch off wifi.. power off ur phone.. 10 sec then switch it on back, then on wifi. if still cant, i dont have anymore idea..
Thanks for all the help benjat. Unfortunately, it didn't work. Hopefully, someone else who has gone through this can help me out.
Mankey Magic said:
Thanks for all the help benjat. Unfortunately, it didn't work. Hopefully, someone else who has gone through this can help me out.
Click to expand...
Click to collapse
nvm.. maybe do full wipe again..
what ver of WD u using? with what addon? im using WD 1.4.3 full
I've already done a cache/date wipes to no avail.
I'm using 1.4.4 lite. I'm thinking of flashing the 2.3.4 based WD though (is that 1.4.3?).
I could flash something else too, I guess. I really need webtop (with xfce mod) and I heard Wet Dream works well with it.
If this really is a software problem and it is the ROM's fault, then does anyone have a webtop compatible ROM recommendation?
Mankey Magic said:
I've already done a cache/date wipes to no avail.
I'm using 1.4.4 lite. I'm thinking of flashing the 2.3.4 based WD though (is that 1.4.3?).
I could flash something else too, I guess. I really need webtop (with xfce mod) and I heard Wet Dream works well with it.
If this really is a software problem and it is the ROM's fault, then does anyone have a webtop compatible ROM recommendation?
Click to expand...
Click to collapse
i cant tell if its problem with rom or what.. 1.4.3 is 2.3.6 base. and yes webtop work well with it.
here's normaly what i do..
Boot CWM Recovery
Wipe data/factory
wipe cache
wipe dalvik
flash rom
reboot to fastboot and do fastboot-w & then fastboot reboot.
let it boot for 1st time (until stable/full load) i left it around 10 mins
then reboot back to CMW to flash addon. usually i flash 1 then boot.. continues untill flash all.. maybe a bit fussy step.. but i prefer all loaded before flashing another
*i never tried webtop2sd yet.. still dont buy bigger mem card coz funding for lapdock
** maybe can try this one to make it clean wipe.. http://forum.xda-developers.com/showthread.php?t=1421522&highlight=fastboot+-w
Yeah I realized too late that everything cost me way more than I had originally intended to spend. SD cards have come down in price but still pretty pricey for a 32 GB card.
And thank you for the link. I'll try it out tomorrow and report back. It's 1:00 AM here in Seattle!
Hey Mankey,
Have you tested different Wifi networks to ensure that the issue is not with the phone or the ROM at all?
Also, check if someone else on Wet Dream thread had WiFi issues, if this happened with someone else, then they should have fix for sure!
Usually I do what bejnat mentioned and usually works.
Also, about the root, try to follow a root process again. It happened with me before, then I had to install a .zip file through Recovery mode to have root access again.
Hope this helps!
wouldn't just flashing the radio or a newer radio maybe fix his issue??
Yeah it doesn't work with other networks either. And as for root I don't think there's a direct way to root 2.3.6 yet.
Sk8trix, I think I'll try that after I flash back to stock 2.3.4. I've tried just about everything but the radio. Kernels don't fix it.
I'll post an update in a couple days. I really want to get this fixed.
I had the same problem with my dark side when I 1st got it and to fix it I flashed another ROM ,loaded it then flashed back ,cleaned delvik cache and flashed gapps then rebooted and 1st boot fixed my problem was using 2.3.6 with webtop2sd+nebtop app hope this helps you
Sent from my ics+darkside multiboot mb860 using xda premium
Hello.
I know that you are all incredibly busy and I sincerely hope that this does not inconvenience anyone.
Yesterday, I was following this very helpful guide for my Samsung Fascinate, (http://forum.xda-developers.com/showthread.php?t=1238070), and I encountered a big problem.
On Section 4, Step 18 ("Once the rom finishes installing reboot."), I did not get the option to immediately reboot. With this Jelly Bean rom, Super Nexus (http://forum.xda-developers.com/showthread.php?t=2238075), I immediately found myself in Team Win Recovery 2.5.0.0.
After initially failing to install Super Nexus via this new Recovery software, I found out that I must have both the "Inject TWRP after Install" and the "Zip file signature verification" options disabled before it will succeed.
However, even after doing this, I noticed that the phone would not restart into the Super Nexus ROM properly. For some reason, it went right back to Team Win Recovery Project 2.5.0.0. Powering off the phone, removing the battery, and then putting it back in and starting the phone again allowed me to access the Rom properly. Afterward, I was able to install the GAPPS file which was provided by the Super Nexus thread (http://forum.xda-developers.com/showthread.php?t=2238075), but rebooting the phone via the power menu did not send me back into Clockwork Mod. Again, I was directed to TWRP and had to install it through there. Frankly, it seems this is all I can access now and Clockwork Mod is simply gone forever. This isn't really a problem I guess, but it is rather strange.
Besides this, my only real functional problem is that Google Search is unworkable. I get the infamous "Unfortunately Google Search has stopped" error message, but everything else seems to run fine. (It is certainly much faster than the Stock Gingerbread ROM.)
My question then is simply this: Why is this ROM so very different from all the others? The guide linked above (http://forum.xda-developers.com/showthread.php?t=1238070) seems to work for 99% of all users....
Why was I so different? Did I do something obviously wrong that anyone can think of? I tried to follow the steps slowly and accurately but I'm still left with a broken Google Search and tons of confusion.
Have you updated the Google Search app using the Play Store? Updating usually fixes any issue I have with it
Sent from my SCH-I500 using Tapatalk 4
SimplyShane said:
Hello.
I know that you are all incredibly busy and I sincerely hope that this does not inconvenience anyone.
Yesterday, I was following this very helpful guide for my Samsung Fascinate, (http://forum.xda-developers.com/showthread.php?t=1238070), and I encountered a big problem.
On Section 4, Step 18 ("Once the rom finishes installing reboot."), I did not get the option to immediately reboot. With this Jelly Bean rom, Super Nexus (http://forum.xda-developers.com/showthread.php?t=2238075), I immediately found myself in Team Win Recovery 2.5.0.0.
After initially failing to install Super Nexus via this new Recovery software, I found out that I must have both the "Inject TWRP after Install" and the "Zip file signature verification" options disabled before it will succeed.
However, even after doing this, I noticed that the phone would not restart into the Super Nexus ROM properly. For some reason, it went right back to Team Win Recovery Project 2.5.0.0. Powering off the phone, removing the battery, and then putting it back in and starting the phone again allowed me to access the Rom properly. Afterward, I was able to install the GAPPS file which was provided by the Super Nexus thread (http://forum.xda-developers.com/showthread.php?t=2238075), but rebooting the phone via the power menu did not send me back into Clockwork Mod. Again, I was directed to TWRP and had to install it through there. Frankly, it seems this is all I can access now and Clockwork Mod is simply gone forever. This isn't really a problem I guess, but it is rather strange.
Besides this, my only real functional problem is that Google Search is unworkable. I get the infamous "Unfortunately Google Search has stopped" error message, but everything else seems to run fine. (It is certainly much faster than the Stock Gingerbread ROM.)
My question then is simply this: Why is this ROM so very different from all the others? The guide linked above (http://forum.xda-developers.com/showthread.php?t=1238070) seems to work for 99% of all users....
Why was I so different? Did I do something obviously wrong that anyone can think of? I tried to follow the steps slowly and accurately but I'm still left with a broken Google Search and tons of confusion.
Click to expand...
Click to collapse
Twrp should be the recovery that is included with this ROM.
If you want a cwm recovery,, look at my thread in the general section.
Unjustdev said inject doesn't work.
For Google search:
I would try wiping dalvik cache and fixing permissions from recovery.
skepticmisfit said:
Have you updated the Google Search app using the Play Store? Updating usually fixes any issue I have with it
Sent from my SCH-I500 using Tapatalk 4
Click to expand...
Click to collapse
This did indeed fix the issue. :laugh:
Now, why it was there to begin with...I don't know. The Super Nexus thread makes no mention of this...
SimplyShane said:
This did indeed fix the issue. :laugh:
Now, why it was there to begin with...I don't know. The Super Nexus thread makes no mention of this...
Click to expand...
Click to collapse
I think Google just automatically updates for most people since they may have other devices running JB or they ran other ROMs. Starting with 4.1, Google automatically backs up every app you install, and when you set up a new device, it'll restore all the apps you had installed previously and it usually updates apps as well.
I take that back, you have to update all system apps manually. But I think most people know to do that.
Sent from my SCH-I500 using Tapatalk 4
skepticmisfit said:
I think Google just automatically updates for most people since they may have other devices running JB or they ran other ROMs. Starting with 4.1, Google automatically backs up every app you install, and when you set up a new device, it'll restore all the apps you had installed previously and it usually updates apps as well.
I take that back, you have to update all system apps manually. But I think most people know to do that.
Sent from my SCH-I500 using Tapatalk 4
Click to expand...
Click to collapse
Thanks for the info.
I don't know what happened. Or why it won't work.
When Safestrap was originally finished, I installed Hyperdrive without a problem. An update came, I downloaded and installed. It made it so I couldn't use HotSpot anymore. So, I figured it was the Rom, and I installed Jellybean Rom. I didn't like it. I tried to install the original Hyperdrive I had, and once its installed and reboots, the lights come on for one second and shut off. Downloaded the newest Hyperdrive, same issue.
The instructions say wait for 10 minutes. I did, and longer. (Range usually 20-40 minutes)
Last night I wanted to try again, (downloaded newest hyperdrive. I have sloooooow internet. Took 5 hours to finish). So, I tried installing today following the instructions, same issue. It installs and says everything is fine, reboot, safestrap pops up, loads normally through that, and the lights are on after like it starts with Stock, lights shut off, phone stops working.
When this happens, the phone does not respond to anything. Power does nothing. I waited 45 minutes the 3rd time trying to reboot after install. The phone will not turn on, respond, or anything unless I pop the battery out and put it back in. I can get back into Safestrap that way.
I really want to use Hyperdrive, but it just won't reboot for my phone.
I do have the Verizon i545 version, ME7, Safestrap, Rooted, and newest Hyperdrive Rom. Used the Safestrap Kernel, but the phone locks up.
I've tried default settings, different Rom settings, (2gb and 3gb), removing almost everything from install, adding what I want, adding what I like, etc. No combination of settings will let me phone boot into Hyperdrive.
Any thoughts?
Are you completely removing then re-creating the slot when trying all these flashes?
Are you flashing the ME7 kernel module.zip ?
I redo the rom slot each time and act like it's the first time.
And i can't install the module... Tried multiple times but it fails almost instantly through ss.
Sent from my SCH-I545 using xda app-developers app
Excessumcarcer said:
I redo the rom slot each time and act like it's the first time.
And i can't install the module... Tried multiple times but it fails almost instantly through ss.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Have you tried to re-download the module? Preferably on the computer then transfer to your ExtSDCard with the ROM.
So... The one I downloaded to my computer failed, but the one I did with my phone worked.
Still the same issue. Won't boot past the SS message.
Sent from my SCH-I545 using xda app-developers app
Excessumcarcer said:
So... The one I downloaded to my computer failed, but the one I did with my phone worked.
Still the same issue. Won't boot past the SS message.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
While you were trying to install did you notice if zip signature was checked if so uncheck when you install and uncheck when you install module other than that don't know what else to say. When i first started i found that to be my problem.
The zip signatures were not checked. : /
Sent from my SCH-I545 using xda app-developers app
And I've tried the older version Hyperdrive with the new ME7 Modules, still won't work. I can't understand because everything says it was successful and ready to go, but it just doesn't.
Also double checked my i545 version, it is still ME7 and not the new one. The new update is pushy and wants to be installed more aggressively than the ME7 did. Highly annoying...
Excessumcarcer said:
And I've tried the older version Hyperdrive with the new ME7 Modules, still won't work. I can't understand because everything says it was successful and ready to go, but it just doesn't.
Also double checked my i545 version, it is still ME7 and not the new one. The new update is pushy and wants to be installed more aggressively than the ME7 did. Highly annoying...
Click to expand...
Click to collapse
Get off 3.62 and go back to 3.6 if you can. use root uninstaller to get rid of the current SS and shut down normally. ( all in stock rom ) reboot to stock recovery and factory reset. put the 3.0 SS back on and install twrp through that and reboot fully. then you can go into SS and reboot to recovery and you should be good
EDIT: go back to 3.6 SS not 3.0 haha
EDIT 2: always wipe even after you just created the slot and flash the modules with HD10 and advanced wip the dalvik and the cache only. and chill for 10 and boot her up..... and make sure you didnt accdentally get the dreadful OTA!!!
!Led*Eyes! said:
Get off 3.62 and go back to 3.6 if you can. use root uninstaller to get rid of the current SS and shut down normally. ( all in stock rom ) reboot to stock recovery and factory reset. put the 3.0 SS back on and install twrp through that and reboot fully. then you can go into SS and reboot to recovery and you should be good
EDIT: go back to 3.6 SS not 3.0 haha
EDIT 2: always wipe even after you just created the slot and flash the modules with HD10 and advanced wip the dalvik and the cache only. and chill for 10 and boot her up..... and make sure you didnt accdentally get the dreadful OTA!!!
Click to expand...
Click to collapse
FINAL EDIT!!! always pick the safestrap kernel during the Aroma install
If I helped at all, shoot me a Thanks and happy flashing!!
!Led*Eyes! said:
FINAL EDIT!!! always pick the safestrap kernel during the Aroma install
If I helped at all, shoot me a Thanks and happy flashing!!
Click to expand...
Click to collapse
I promise you this makes no sense....and I think there was something wrong with the stock rom...only thing I can conclude. I did a factory reset and bricked my phone. I can't even get into Safestrap now...whatever the issue was with the custom rom is now the issue with the stock rom. So, i'm just going to wipe my phone and start over from scratch as that is the only available step. Ill let you know if it fixed the issue or not.
Excessumcarcer said:
I promise you this makes no sense....and I think there was something wrong with the stock rom...only thing I can conclude. I did a factory reset and bricked my phone. I can't even get into Safestrap now...whatever the issue was with the custom rom is now the issue with the stock rom. So, i'm just going to wipe my phone and start over from scratch as that is the only available step. Ill let you know if it fixed the issue or not.
Click to expand...
Click to collapse
Did you have 3.62? my buddy did and his phone wouldnt let him delete it! crazy. i dont like 3.62 but i was running HDrls10 like a champ. not a single issue. With the me7 base i want to say i didnt even flash the modules over it but i cant remember. but basically ( by what i wrote down) you were going to start from scratch anyway.. there is a better root out now anyway. use the dialer codes and get a REAL factory reset!! There are a lot of people that arent digging the 3.62..... it was causing bootloops for a while but there are def still some lingering issues i think.
!Led*Eyes! said:
Did you have 3.62? my buddy did and his phone wouldnt let him delete it! crazy. i dont like 3.62 but i was running HDrls10 like a champ. not a single issue. With the me7 base i want to say i didnt even flash the modules over it but i cant remember. but basically ( by what i wrote down) you were going to start from scratch anyway.. there is a better root out now anyway. use the dialer codes and get a REAL factory reset!! There are a lot of people that arent digging the 3.62..... it was causing bootloops for a while but there are def still some lingering issues i think.
Click to expand...
Click to collapse
Well...nothing has worked.
Update for everyone, I was using the older SS, 3.60.
I killed everything, put the original Verizon ME7 Rom on the phone, re-rooted, put 3.62 SS on, (Done like it), installed the HDrls10, Installed the module, (both successful), restarted, exact same thing. Right after Safestrap Enabled pops up, the phone goes dark and the battery needs to be removed and put back in for it to turn on again.
So, I tried something crazy and for whatever reason it worked as far as HD is concerned...but...I went outside of the instructions.
I have the HD rls9 Final. I installed it through SS, used the modded Kernel, (non SS), and restarted. It popped right up in about 45 seconds. (Wasnt working before I reset everything and started over)
I tried HD rls10 Final that way, and nothing.
I will be redownloading it tonight to make sure it isn't the download. (I have slow internet, itll take all night likely.) : /
If anyone is looking to actually uninstall SS (which you need to do to roll back a version) you need to use the commands hashcode has provided. Using Terminal Emulator on the stock side will accomplish that. Read up on hashcode's SS OP.
My phone will not accept HDrls 10....no matter what I try. It accepted HDrls9 without issue, minus the hotspot not working. But it will not accept HDrls10...
Im out of ideas...
EDIT: I downloaded the HDrls 10 rom from two locations, tried both, both failed this morning.
Excessumcarcer said:
My phone will not accept HDrls 10....no matter what I try. It accepted HDrls9 without issue, minus the hotspot not working. But it will not accept HDrls10...
Im out of ideas...
EDIT: I downloaded the HDrls 10 rom from two locations, tried both, both failed this morning.
Click to expand...
Click to collapse
All I can think of is somehow you are getting bad downloads. Have you checked the MD5s to match per the download sites listing?
lazer9 said:
All I can think of is somehow you are getting bad downloads. Have you checked the MD5s to match per the download sites listing?
Click to expand...
Click to collapse
I just double checked the MD5. It matches the download. How frustrating. Double checked the build, double checked the MD5, double checked install procedure, etc. It flat doesn't work on my phone, and there is no logical reason to it. I tried from a fresh build twice now, doing the rooting and SS install from stock everything.
It locks up right after SS, still.
Electronics hate me, it has been determined before. This is just further proof.
: /
So, I've done pretty much everything feasible. Guess Ill have to stick with an older HD or different rom. : (
Also, hotspot doesn't work HD 9 for me, (nor Jellybeans). I installed the module when I did the rom, but there is no hotspot for one. And two, when I download and use FoxFi, which I paid for to use on the Stock Rom before SS, it will try to turn it on and then it freezes and crashes.
All I want is a non-Verizon Rom with working Hotspot!!!! AHHHHH!!!! Looks like that aint happening.
Well played Verizon...well played. Perahps I should get an international phone and go to another company. Expensive, but tempting.
So, the final verdict for those following -
Hyperdrive 10 - Does not work on my i545 no matter what I tried.
Hyperdrive 9 - Works but the hotspot is glitched and froze no matter what I tried.
Jellybean - Works the same as HD 9
Synergy - Works. Everything on it works, hotspot, install, etc.
Not sure why the others did not work. But, for whatever reason Synergy works flawlessly for my i545. Installed and downloaded the same ways as the others, yet it worked.
: /
I was planning on trying a few others first, but Synergy claims to block Samsung from logging information from my phone. I realize this doesn't stop every company from doing it, but its the thought that counts. lol. So, Im trying this Rom out now. It's no hyperdrive, but it works.
After a BUNCH of tries I finally got it to work!!
I have a Verizon i545 with ME7. I basically started as if I'd never installed HD 9.1 in the first place.
Here's what I did.
1. Double check that your device is rooted. I used Root Checker Basic. I actually re-rooted my device just to be sure (I venture to guess it might have been unnecessary) and it worked.
2. I used a 4GB SD formatted to ex-fat and put the HD RLS10 AND the ME7 modules .zip file on it (Both on the SD)
3. I then booted into recovery.
4. Make a new ROM slot.
5. Name it whatever you like.
6. When you go to flash HD, hit the add zip button and select the ME7 modules.zip
7. When HD gets done flashing UNCHECK the "Reboot" box up top and then hit the reboot tab at the bottom right.
8. It will automatically flash the ME7 modules next. When it says 'Successful', then reboot.
9. Give it a few seconds and hopefully it will work for you as well. Good luck.
Latest installable version for Me7?
What is the latest installable version of HD for verizon locked Me7 bootloader, i currently have rls10.0 installed and ive tried 10.1, 10.2, and now 12 and none of them boot up.
Before continuing reading, please keep in mind that the problem I am asking support for was already solved for my own. What I want to know is how did it happen. For prevention, you know.
It all started when I flashed the Black Box ROM 2.0.2 (http://forum.xda-developers.com/showthread.php?t=1834915) It flashed normally, without any problem. But, since it lacked the Xposed Framework, I installed it manually, downloading from its thread, and choosing a full install. Using the Framework I downloaded Gravity Box and the Youtube Adaway, before downloading Youtube. Since the modules needed a reboot to work, I rebooted. And this is when the bad things started to happen.
The ROM did not start. It went through the BlackBox logo, but when it appeared that the SIM unlock was going to pop up, then the phone turned off. This happened many times. So I decided to do a full wipe and install another ROM. The problem was that the phone didn´t allowed me to access the recovery.
I was using the PhilZ Touch 6, but when I pressed Volume up+Menu+Power it did not work. The only thing that worked was the Odin Menu, and I got stuck at it, I couldn´t get out the Odin Menu. So, seeing that the phone wasnt going to work anyways, I flashed a 4.3 stock ROM through Odin.
As I suspected, the ROM got stuck at boot, and got a bootloop. So then I flashed another recovery, and flashed good ol´ CWM. And It worked..for a while. The phone would shut down after some seconds. So then I tried to flash TWRP, but it lasted about one second and then the phone shut down again.
Since I was using Odin 3.03, I downloaded Odin 3-04 Moded Edition, from the Modem thread, and then reflashed CWM. In this time, it worked without failing, and I could do a full wipe and flashing an old Cyanogenmod 4.2.2 ROM, finally solving the problem. The day after I flashed Ultima ROM and at the moment it goes fine, without any problem. Which is weird, because it too uses Gravity Box and Xposed Modules. I even installed new modules, rebooted the phone and it works fine, without any problem.
What I want for the people here is that someone explains to me what happened, because the BlackBox ROM looked gorgeous and I wanted to give it a long try. And because I spent an entire night solving that problem, and well, I wont sleep in peace until I get to know what happened to that bastard
r1k1v1 said:
Before continuing reading, please keep in mind that the problem I am asking support for was already solved for my own. What I want to know is how did it happen. For prevention, you know.
It all started when I flashed the Black Box ROM 2.0.2 (http://forum.xda-developers.com/showthread.php?t=1834915) It flashed normally, without any problem. But, since it lacked the Xposed Framework, I installed it manually, downloading from its thread, and choosing a full install. Using the Framework I downloaded Gravity Box and the Youtube Adaway, before downloading Youtube. Since the modules needed a reboot to work, I rebooted. And this is when the bad things started to happen.
The ROM did not start. It went through the BlackBox logo, but when it appeared that the SIM unlock was going to pop up, then the phone turned off. This happened many times. So I decided to do a full wipe and install another ROM. The problem was that the phone didn´t allowed me to access the recovery.
I was using the PhilZ Touch 6, but when I pressed Volume up+Menu+Power it did not work. The only thing that worked was the Odin Menu, and I got stuck at it, I couldn´t get out the Odin Menu. So, seeing that the phone wasnt going to work anyways, I flashed a 4.3 stock ROM through Odin.
As I suspected, the ROM got stuck at boot, and got a bootloop. So then I flashed another recovery, and flashed good ol´ CWM. And It worked..for a while. The phone would shut down after some seconds. So then I tried to flash TWRP, but it lasted about one second and then the phone shut down again.
Since I was using Odin 3.03, I downloaded Odin 3-04 Moded Edition, from the Modem thread, and then reflashed CWM. In this time, it worked without failing, and I could do a full wipe and flashing an old Cyanogenmod 4.2.2 ROM, finally solving the problem. The day after I flashed Ultima ROM and at the moment it goes fine, without any problem. Which is weird, because it too uses Gravity Box and Xposed Modules. I even installed new modules, rebooted the phone and it works fine, without any problem.
What I want for the people here is that someone explains to me what happened, because the BlackBox ROM looked gorgeous and I wanted to give it a long try. And because I spent an entire night solving that problem, and well, I wont sleep in peace until I get to know what happened to that bastard
Click to expand...
Click to collapse
OK first black box already has xposed in ROM control settings.. so maybe because you manually installed it it may have caused conflicts... Don't know why you got a recovery bootloop... but maybe due to same problems... And I am also using blackbox 2.1 and so far it is fantastic...
Sent from my GT-I9300 using xda app-developers app
Partition structure on these phones is very fragile, one bad shutdown can corrupt one or more partitions at the same time. I'd suggest the combination of mods applied caused the kernel panic, while data was being written.
Subsequent events read like normal solution to corruption, it shouldn't happen again but best to apply framework mods one at a time.
Sent from my GT-I9300 using Tapatalk
kunal1540 said:
OK first black box already has xposed in ROM control settings.. so maybe because you manually installed it it may have caused conflicts... Don't know why you got a recovery bootloop... but maybe due to same problems... And I am also using blackbox 2.1 and so far it is fantastic...
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Hmm, I don´t remember that the BlackBox 2.0.2 had any Framework...thats why I did a manual installation. But I will try the new version 2.1. Hopefully the problems may have been solved.
boomboomer said:
Partition structure on these phones is very fragile, one bad shutdown can corrupt one or more partitions at the same time. I'd suggest the combination of mods applied caused the kernel panic, while data was being written.
Subsequent events read like normal solution to corruption, it shouldn't happen again but best to apply framework mods one at a time.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Interesting. So I have to apply mods one by one? Or can I add multiple mods because corruption has already been solved?
On a side note, when I boot the phone the red exclamation mark that used to appear has disappeared. Does that means that I somewhat reseted the flash counter to 0?