I'm quickly finding the D2G is the least supported of the Droid devices and have the feeling I should have just bought the D2. It's been a bear trying to get information on this phone, let alone any decent ROMs that are working. That said I've got some issues with flashing backups, so here's the details.
Droid 2 Global
- CM7.1 (DROID2WE version) installed.
- Droid 2 Bootstrapper 1.0.0.5
- Clockwork Mod 5.0.2.3
First off, all the online documentation, including CM's site that CWM can be loaded by: "Hold the X key on the keyboard & the Power button until the device boots to the recovery." is incorrect. Doing so pulls up the PHONE recovery; the best way to get CWM to boot is to wait until the "M" logo comes up and the backlight on the screen turns off, then pressing and holding the power button for 5-10 seconds.
Now, I've tried both entering into recovery from ROM Manager, then creating a back up and rebooting into CWM recovery, then creating a backup. In both instances, the recovery will not restore; each and every time I've tried, I get this error: "Error while formatting /system". Keep in mind that I did NOT change the name of the backup (which I'm told can cause this error).
Supposedly, according to ROM Manager's page on the Market, the latest update was supposed to resolve the error/restore problem, but I've flashed 5.0.2.3 several times with no avail. I emailed Koush, but haven't received a response. To add to the issue, I haven't been able to get any other ROM to flash to the phone, like Liberty 3, for example, unless I flash SBF back to 2.4.330; it's almost like the phone doesn't like dealing with more than one ROM.
Anyone know what I'm doing wrong? I can't find anyone else with the same issues in a finite post and certainly no wikis to explain the matter. I have an OG Droid that doesn't have any of these problems so I assume this is related to the D2G and not because I'm doing something wrong.
**EDIT** Scroll to last post for the resolution.
D2G has a locked bootloader. The custom ROMs are made for a certain kernel. A GB-based ROM won't load on the 2.4.x base, and vice versa, a Froyo ROM won't start on the 4.5.x base.
To install CWM, you need to use Droid 2 Recovery Bootstrap from the Market. With stock ROMs booting into CWM is only possible by first booting into the OS, and then choosing Reboot Recovery in the Droid 2 Bootstrap Recovery app you installed before.
(I have never used ROM Manager because it's not really supposed to work well with the D2G.)
Also, it's worth noting that the “official” CM7.1 ROM is based on the Froyo kernel from 2.4.x firmware.
I've got the Droid 2 Recovery Bootstrap installed. But that still doesn't explain why all the videos and people I see online can switch in between ROMs on other phones, but it's so hard on the D2G, or that I can't get a backup to install properly.
I've read online that using the Droid 2 Recovery Bootstrap to reboot into recovery isn't advised; can anyone confirm?
It's not advised for CM7 and MIUI; those have their own recovery access methods, and CWM comes preinstalled. In CM7, you have to long press the power button, tap “Reboot”, and choose “Recovery” from the reboot menu.
On the most current (ICS-based) MIUI, you have to use the boot menu (press the Volume Down button during power on when the notification LED turns blue while the red Motorola logo is still displayed).
On stock firmware, however, the only way to access CWM is using koush's Droid 2 Recovery Bootstrap and its Reboot Recovery option.
For most other phones, you just replace the stock recovery with CWM, and that gives you the same version of CWM whenever you boot into it.
On Motorola phones with locked bootloaders, CWM versions might differ between different ROMs, because CWM is installed as just another system component with the ROM itself, not outside the ROM inside the boot/recovery partition.
I am, however, unsure why are there such issues for you with backup and restore; I was able to use backup and restore on multiple occasions, and last time I did it was just 2 days ago when I switched between MIUI and stock about 7 times without resorting to SBF even once.
I thought the first few times it didn't 'restore' was because I installed CM7 incorrectly or that I didn't install the bootstrap correctly, but I've SBFd and installed CM7 at least 4 times now and I've never been able to restore; every time I do, I get the 'Error while formatting /system' message.
I really hope I'm just doing this wrong (though I don't see how) and someone can steer me in the right direction.
Wipe data/ cache?
If u use rom manager, go recovery via rom manager
I've done that every time, including wiping the cache partition AND Dalvik under 'advanced'. I found out it was the CM7 version I had installed, which was the 'stable' version that installs over Froyo. It was messing up all sorts of things. I installed one of the RevNightlies over the Gingerbread OTA and most of my problems resolved. I've still had a few instances of a backup not restoring right though... is that a common issue?
**EDIT**
Problem solved, thanks to the guys over @ Rootzwiki. If you have the D2G, you need to flash CWM for the Droid X (2nd-init). I did and backups/restores are working perfectly.
This is a HUGE issue, IMO. There's zero documentation on CWM online, so hopefully people will see this thread if they encounter the same issues I did.
beepea206 said:
**EDIT**
Problem solved, thanks to the guys over @ Rootzwiki. If you have the D2G, you need to flash CWM for the Droid X (2nd-init). I did and backups/restores are working perfectly.
This is a HUGE issue, IMO. There's zero documentation on CWM online, so hopefully people will see this thread if they encounter the same issues I did.
Click to expand...
Click to collapse
I was also having this issue. Thank you for doing the research!
It's pretty frustrating because in ROM Manager, there's a Droid 2 Global option which you would think would be the obvious choice. Apparently D2G's really need DX-2ndInit.
I'm in DX-2ndInit Recovery on my D2G and it's actually doing functions instead of pretending. It's happily restoring a Nandroid backup that I made under the old original version of CWM that the D2Bootstrapper installed.
Edit: Nandroid Restore worked perfectly! All's going very well now and my phone is now running on AT&T on a GoPhone SIM. Looks like it can even jump on HSDPA!
Related
The Three Network (recently bought by Vodafone here in Australia) released the Desire HD with a ?slightly different ROM to Vodafone. It has a higher build number and includes the customary links to "Planet 3" services. After installing Paul's unofficial clockworkmod, I did a factory reset and then used clockworkmod recovery mode to backup the ROM (so there's no personal info in the data image file). I'm completely new to Android, but I was thinking along the lines that Three Network customers might want the option of getting their device back to stock condition (after messing with it like I did). I know these factory roms can be regarded as 'bloated', so I doubt other Androphiles will be interested in flashing it. Well done to Paul and the other Desire HD developers on Modaco and XDA developers. The link is:
http://rapidshare.com/files/4316185...8b.60.140eU_26.03.02.26_M_Clockwork-BACKUP.7z
MD5: 784020B4697024E75BA2B7E9BDC5EB09
Hey, i am a Three Australia DHD user as well, I was wondering with this ROM, does it flash the HBOOT to S-ON as well? Or is there a method for me to flash back my Hboot to S-ON if required?
No. The rom is S-off. I had to install ENG HBOOT (S-OFF) in order to install clockworkmod and make the backup. Happy Three Networking . I think (but am not sure) that you can use the "DHD script for flashing hboot" found elsewhere on this forum from Android terminal emulator to restore your original HBOOT (as long as you made a back up of it when you first used that script to flash the Eng hboot).
The script I referred to above is available here:
http://forum.xda-developers.com/showthread.php?t=835746
Sent from my Desire HD using Tapatalk
I am on Vodafone Au and have slightly older build as described by OP. The major issue that I noticed was my cousin's Three one doenst have proximity issue that I have during calls.
I'm looking for a fix.
Sent from my Desire HD using XDA App
I am Vodafone Au and have slightly older build as described by OP. The major user that I noticed was my cousin's Three one doenst have proximity issue that I have during calls.
I'm looking for a fix.
Click to expand...
Click to collapse
You could flash my Three rom. Before you do that, make a note of your Vodafone APN's (Settings -> Wireless and Networks -> Mobile Networks -> Access Point Names). After flashing the Three rom, you'll need to change the APNs (which were 3services on the Three Network) to Vodafone's equivalent. In order to flash the rom, you'll need Paul's Visionary permaroot and clockwork recovery (the Restore option). As they say on the threads, all at your own risk.
On second thoughts, go with LeeDroid, if your gonna flash a new rom
... And consider buying him a beer.
Walker Street said:
You could flash my Three rom. Before you do that, make a note of your Vodafone APN's (Settings -> Wireless and Networks -> Mobile Networks -> Access Point Names). After flashing the Three rom, you'll need to change the APNs (which were 3services on the Three Network) to Vodafone's equivalent. In order to flash the rom, you'll need Paul's Visionary permaroot and clockwork recovery (the Restore option). As they say on the threads, all at your own risk.
Click to expand...
Click to collapse
Thanks mate for updating me with where the rooting and rom application status is on DHD. I was basically after a stock (clean/unbranded) rom with no tweaks. I think in my recent Android phones, DHD probably has the best factory rom.
fawaad said:
Thanks mate for updating me with where the rooting and rom application status is on DHD. I was basically after a stock (clean/unbranded) rom with no tweaks. I think in my recent Android phones, DHD probably has the best factory rom.
Click to expand...
Click to collapse
My Planet 3 rom is a backup of a 'stock' rom (made using clockworkmod recovery's nandroid backup feature), with no tweaks or user data added. So, you could use it. You'd need to follow the method described above though. You need clockworkmod recovery in order to restore it.
Help
Hello.
I also have a 3 mobile Desire HD here in australia. I am having a little trouble. Was wondering if you's could help.
I want to load a different rom. Leedroid or Defrost. Not sure yet but i am struggling.
I have used visionary r14 to permaroot the phone. I have done a backup with titanium and i have rom manager. This is where i get stuck.
All the stuff i have read does not make this really clear. I want to make a backup of the rom that is loaded just incase i ever want to turn it all back.
I go into rom manager and i click on Backup Current ROM
phone reboots and a pic of the phone comes up and it has a red ? above it. phone restarts and nothing happens.
I am unsure what to do and where to go from here.
Any help would be great.
--------------------------------------------------------------------------------------------------------------------------
Doesent matter. I got it sorted and was able to do a backup.
Took me a while but got there. Has anybody put on a different rom yet like either of the ones i have mentioned?
Hi jonkers71
Rom manager does not work for the desire HD yet. The guy who writes the rom manager app also writes the 'official' clockwork mod recovery. Paul's clockworkmod for the desire HD is not supported yet by rom manager. By the way, Paul is the same guy who wrote visionary. My file is a backup of a blank planet 3 rom, so you can keep it as a backup. You need Paul's clockwork mod installed (after you root your phone) in order to make backups and do restores. Clockwork mod does exactly the same thing as rom manager except it runs after you take the battery out, put it back in, and boot while pressing volume down. It runs in text mode (like a dos program or a BIOS in a PC). Its really simple. Just choose backup or restore. Most custom roms are installed using clockworkmods 'install from zip' option. See the tutorial thread by Paul which tells you how to install clocmworkmod. Its by far the easiest way to install, backup and restore roms. The backup command backs up all your data too. This is also a more reliable backup in most situations than titanium because its a bit like a ghost or acronis disk image in a PC.
Sent from my Desire HD using Tapatalk
just edited first post.
Was able to get it up and running. Just wasnt reading the info correctly.
Is there any way of installing leedroid or defrost then after i have the back up?
Follow the tutorial on rooting the phone and installing 'eng hboot' (which is simply a text based menu that appears when you boot the phone while pressing volume down). Install Paul's clockwork mod using his tutorial. Download leedroids rom and put it on your SD card. Turn off the phone by pressing power for 2 secs and selecting turn off. Take the battery out. Put it back in. Press and keep pressing volume down, while you tap the power button. A text menu appears, select 'recovery', then select 'install from zip'. 2 minutes later you have a new rom. Select reboot from the menu.
Sent from my Desire HD using Tapatalk
Thanks for the info. Was pretty sure i knew how to do it. ran into a slight snag though and thats why i asked.
Guess it works better when you have the right rom to flash. hahaha. anyways all on and running now.
yep leedroid 1.2, 1.3, 1.3a and just now 1.4.
I am on 3 network also.
A couple of family have DHD from 3 with stock roms and they are shockingly slow.
Hey guys i am in need of help. I am getting terrible battery life with cm7 because every radio i try gives me bad reception for wifi and singal causing a greater battery drain could anyone recommend the best radio for cm7 gingerbread?
By the way my location is Australia Victoria if that is any help. Thanks in advance
has anyone got 2.37.861.8 ota yet? if so could someone please post it? A rooted version would be nice
wineds said:
has anyone got 2.37.861.8 ota yet? if so could someone please post it? A rooted version would be nice
Click to expand...
Click to collapse
hi Guys i am after the ship rom for this 3 aus to revive a dead DHD.
thanks in advanced
I've noticed other people seem to be having this same problem and there hasn't really been a distinct solution that I can see, so hopefully this question will be helpful in the future and not repeatative.
I've been trying to update to CM7 from CM 6.1.2 on my Evo. I followed instructions from here http://forum.xda-developers.com/showthread.php?t=902051 and downloaded all the recommended software. First I tried to just flash the rom, then the kernal, then the gapps. All seemed well at first, and I got past the Evo 4G screen, but it got stuck booting on the Cyanogen animation (the arrow just keeps going!)
Then I tried to wipe the Davlik-Cache, and rebooted again. I left the phone alone for about 45 minutes, and it still got stuck on the Cyanogen animation.
Finaly, after searching through the forums, I found another post which suggested I do a hard reset then flash the rom, kernal and gaaps then clear the cache and davlik-cache. Still, I'm stuck on the animation. I have a nandroid backup, so I can get back to 6.1.2, but I'd really like to get CM7 working, anything else I should try?
You should't have to do the kernel separately unless you have a specific reason for doing so the ROM comes with a kernel for you. I had a similar problem with my HTC however I was able to get it resolved by installing gapps. Here's what I did -->
Used ROM Manager to go back to working ROM
From working ROM, accessd ROM Manager and chose rebooted into recovery mode
Once in recovery cleared/wiped everything (cache, data, delvik) installed gapps then cm7
Restarted
It did take awhile after restart to get going however once it did it worked marvelously!
Hope this helps and good luck!
Reboot
Similar Problem, Defy CM7 Bootloop
The first time i tried installing CM7 I got a boot-loop. I have tried at least 7 different tutorials all with different variations of flashing this and wiping that yet none yield results. Still stuck at boot-loop.
The most recent thing i have done was used RSD Lite to flash
"JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P016_A016_HWp3_Service1FF.sbf"
this got my phone running again, i then pulled off some magic by rooting using a combination of super1click, Z4 and installing superuser myself. after that i copied the files for a bootmenu into my /data/ folder. using CWM Recovery v2.5.1 flashed
"freq_F_US_342_107-850-1700-2100-signed.zip"
to get my 3G running again, and gave up of CM7.
If anyone has anything that could help id appreciate it.
(ps. i've tried many variations of wiping things and re-flashing things)
I said I would flash cyanogenmod on a friends G1 because he was fed up with 1.6. I've flashed many custom ROM's on several different devices before but I've made a mess of things with this G1 and I can hardly hand back an unusable phone so I would really appreciate your help.
I rooted the phone using Androot, backed up the apps and settings using titanium backup and then the texts using a text backup app. I then downloaded Rom manager and flashed the latest clockworkmod recovery. Next I downloaded the latest official cyanogenmod rom for the dream/g1 and placed it on the phones SD card using my computer. I then re-opened rom manager and used it to select the zip file from the sd (to flash it) on prompt I checked two boxes one to wipe data and one to wipe the dalvik cache and pressed ok.
The phone rebooted into the recovery wiped the stuff, supposedly flashed the rom and rebooted. However it got stuck on the t-mobile g1 boot screen(it never showed anything else first or anything after) I left it for ages with no joy. I then tried wiping from the recovery and flashing again - same thing so i put cm5 on and tried flashing that. Same problem. Then i realised that it probably would not work because I would need to use DangerSPL as the /system partition is too small on the dream/g1. To be honest at this point I can't be bothered with to do that and this guy will be happy with anything above 1.6 to be honest so I thought I would try and flash CM4 because that's based on Eclair I believe (and so it not require I use DangerSPL or any other method to repartition the NAND). However, I tried it twice and still no luck.
At this point I'm somewhat panicking as I cannot seem to make the phone boot and it isn't even mine! Is anyone able to help?
Anyone? Please?
Look, at this stage I will forget custom roms etc. If anyone can tell me the easiest way to get this phone booting android again i would be very grateful.
Even if you could just tell me exactly how to restore it to stock 1.6 from here?
I have flashed roms on phones before - never had a problem but this is driving me crazy - please help!
wollac11 said:
Hi I said I would flash cyanogenmod on a friends G1 coz he was pissed off with 1.6 but im having trouble and I can hardly hand back an unusable phone so i really need your help.
I rooted the phone using Androot, backed up the apps and settings using titanium backup and then the texts using a text backup app. I then downloaded Rom manager and flashed the latest clockworkmod recovery. Next I downloaded the latest official cyanogenmod rom for the dream/g1 and placed it on the phones SD card using my computer. I then re-opened rom manager and used it to select the zip file from the sd (to flash it) on prompt I checked two boxes one to wipe data and one to wipe the dalvik cache and pressed ok.
The phone rebooted into the recovery wiped the stuff, supposedly flashed the rom and rebooted. However it got stuck on the t-mobile g1 boot screen(it never showed anything else first or anything after) I left it for ages with no joy. I then tried wiping from the recovery and flashing again - same thing so i put cm5 on and tried flashing that. Same problem. Then i realised that it probably would not work coz i would need to use DangerSPL coz the /system partition is too small on the dream/g1. Tbh i'm tired so I cba to do that and this guy is not that technical so he will be happy with anything above 1.6 so I thought I do CM4 coz thats 2.0 or 2.1 i seem to remember (and it not require I use DangerSPL) - tried it twice and still not luck.
HOW THE HELL CAN A GET THIS STUPID THING TO WORK AGAIN!??
MAJOR PANIC AS THIS IS NOT MY PHONE - PLEASE HELP!!!
Click to expand...
Click to collapse
Try this thread: http://forum.xda-developers.com/showthread.php?t=803482. I hope it helps.
It's been way too long since I rooted mine to be of any real help but I shall try nonetheless.
Firstly, there is a guide in the G1 forum to unroot and get back to stock firmware: Here (but note that I've never done this).
I must stress though (admittedly from memory) that if you have flashed an SPL or radio image at all, be VERY careful about the order in which you revert back to stock (or go to get a custom ROM depending on which way you decide to go). The G1 is very picky, and flashing things (mostly SPL and radio IIRC) in the wrong order will brick the device. That said, if you follow the instructions you find to the letter you should be OK. But yeah, read twice, flash once.
There is a lot of information in the stickies in the G1 forum. It could take a while to wade through but it should all be there. Failing that, post in the Q&A or General G1 subforums and I'm sure a current user will help you out.
I apologise if I've just posted a bunch of stuff you already know/have read - like I said, I've not used the phone in a while - just trying to offer what I can.
Thanks
No worries now guys i've done it! It was quite complicated but its all sorted now. If anyone is trying this and has the same (or similar) issue then pm me and I will tell you how I sorted it.
Otherwise thanks guys and you can conciser this thread:
---------------------closed--------------------------
Hi everyone, I had a problem with my previous nexus s (I have since gotten a working replacement) and I was wondering where exactly I messed up so in the future I can avoid this
Here is what I did on my previous phone:
1. I flashed ics onto my device from the ota update package from androidcentral, it was 4.0.3. (This worked great and I had it on my phone for 2-3 months before I tried the next steps.)
2. I rooted my device successfully using the guide at nexusshacks.
3. I also flashed TWRP recovery (fastboot) and superuser using the above guide/links
4. When I would turn off my phone it would boot to a screen with a red triangle and an opened android bot. So what I would have to do is flash twrp recovery everytime I turned the phone on just to get it to work.
5. What I wanted to do was keep the stock rom but still have twrp recovery without it making me reflash it on every boot. So I clicked install and tried to flash the stock rom (update package from the link in step 1) with twrp recovery. It then turned off my phone and hard bricked it. I couldn't turn it on anymore and a new battery didn't fix it.
I was able to get a replacement now and I was just wondering at which step did I go wrong? I THINK that I should have wiped my cache before I tried to reflash the stock rom but maybe I'm way off base here. This is why I posted a question here so hopefully some of you guys can help.
I did think about posting in another thread, but I didn't wanna threadjack or anything... and his problem also seemed a bit different then mine. Also, sorry about not being able to provide the specific links it won't let me post them until I've posted 8 times.
I don't know for sure but team win recovery has been reported to corrupt the device's efs directory. I've even had problems myself using clockwork recovery. I've moved on to razor recovery and haven't looked back.
This is the most flash-friendly phone I've ever owned, and razor recovery rivals amon ra (which was awesome on my g1 and evo). I really think it may have just been the recovery you were using... Somebody correct me if i'm wrong.
Sent from my Nexus S 4G using Tapatalk
I had once corrupted one of the partition. I fixed to by flashing stock recovery and stock rom.
Use adam outler's unbrickable mod tool. It can be found in android development section.
Sent from my Nexus S using XDA
Thanks for the replies.
That's interesting about twrp... I didn't know that. Truth be told, the only reason I went for it over other ones like clockwork mod was because the UI looked pretty nice and easy to use. Also the guide I followed at nexusshacks used that, so I wanted to stay consistent with it.
jishnu7, it's a little late for that now however as I actually have already received a working replacement from my carrier, but in the future if something ever does go wrong (hopefully not) I will definitely check that out.
The main thing I'm wondering is if it messed up because I tried to reflash the stock rom essentially over top itself (was hoping that by doing that, it would stop making me reflash twrp on every reboot) or if it was because I didn't wipe the cache before the flash.
Also, what I really wanted to do with my phone was to keep the stock rom but be able to overclock my cpu/gpu. I was hoping I could set different overclocks for different things (I've heard of kernels where you can downclock your phone when the screens off and have it overclocked slightly while you're using it, that would be something I'd like to have). I figured to install those kernels I would have to root my phone, replace stock recovery and install superuser so that's why I tried to do that. Once again, I'm pretty new to all this stuff for my phone.
Sorry to bump this thread again, but I would really like to know how I could avoid what happened to me for the future. I think it's because I flashed the stock 4.0.3 rom over itself (was hoping that by doing that twrp recovery would stay on the phone after reboot).
What I would like to do is install something like CM9 or AOKP and use the Matr1x kernel so I could undervolt or overclock my phone.
I seriously dont get how u hard bricked your phone...
the reason you are thinking is you reflashed stock rom without wiping cache, as per my experiece its not at all the reason
now, whats my experience??
...I have some fault with my nexus device and I'm working on it,,and I did everything I could do...one of the thing out of those things was reflashing stock rom without wiping,and i did it quite a several times...my device never hard bricked,,however it was soft bricked for many times,,and i recovered from it
so reflasing a stock rom over stock rom, over ICS, over some themed custom rom,will not hard brick your device, you must be missing something none of your steps sounds suspecious
P.S:- pulling out battey while flashing something like this sounds suspecious, never tried though
I'm not sure what happened either to be quite honest with you. Since giving it another shot now with my new fresh phone I have had great success!
I did everything I wanted to do all in one go. Rooted it, install CWM touch, install AOKP (went with milestone 4 cuz I heard newest build 29 has some bugs) + gapps and installed matr1x kernel 18.5 bfs.
The only thing I did different from last time was installing CWM touch (instead of twrp) and flashed aokp this time (instead of reflashing 4.0.3 over itself).
I would just avoid step 2 at all cost.
The nexus s hacks dude is a tool.
Good morning,
While not a noob to rooting or flashing (currently active on Galaxy tab 2 boards) I appear to have made a noob mistake, and even though I searched and read stickies, etc - still made the mistake.
I rooted the Rogers Infuse 4G using this thread http://forum.xda-developers.com/showthread.php?t=1197248 and it worked without issue.
Decided to try the enable lag fix option - deleted the voodoo file on the sd card, and rebooted the phone. Phone got stuck on SAMSUNG screen (unfortunately - did not notice that the volume was off on the phone) and I did not hear the "voice" telling me what was going on - so rebooted the phone by holding the power button until it rebooted.
Spent a couple of hours after that re-reading, and since I was able to get into download mode - was able to reflash stock package through odin. When the phone did finally reboot (thankfully, as this is my daughter's daily driver) I noticed there was already a voodoo file on the sd card, with another file inside named "logs" Just in case, I deleted that file, and added a new one called "disable-lagfix" as per the original instructions.
Just to be sure - went back and ran the rooting procedure, and can confirm that we have root.
From there, I decided to flash the 100% working CWM Recovery file through Rom Manager - found the details on this thread http://forum.xda-developers.com/showthread.php?t=1107881 and can confirm that after rebooting into recovery - the phone has CWM Version 2.5.1.2
The phone is currently fully functional, no issues with network or wifi, playstore, etc - but would like to know if anyone can confirm that we are good to go should we decide to upgrade to a custom rom. I've done so much reading - that the recovery version confuses me ( red or blue, etc). I realize that some of the threads are back from early to mid 2011 - so not sure if they are still completely valid - so am asking before proceeding.
Phone settings are the following:
Kernal 2.6.35.7-I997RUXKG3-CL366622
Build GB.UXKG3
Baseband I997RUXKG3
Firmware 2.3.3
CWM 2.5.1.2
Currently have the voodoo/disable-lagfix file on the sd card
If anyone has gotten this far into the thread - and can offer up some feedback or recommendations - it would be appreciated
Thanks in advance,
Bill
I usually don't trust Rom manager, but if you are able to boot to recovery then I would say you are good.
If you want the red one (don't remember the version) you could flash a custom kernel with sgs kernel flasher (available on play store).
Infusion should work for you
andros11 said:
I usually don't trust Rom manager, but if you are able to boot to recovery then I would say you are good.
If you want the red one (don't remember the version) you could flash a custom kernel with sgs kernel flasher (available on play store).
Infusion should work for you
Click to expand...
Click to collapse
Thanks for the reply - appreciate your time
Guess it's time to turn that volume up, delete the voodoo folder, and cross my fingers....
Just to confirm - do I delete the voodoo folder itself, or the disable-lagfix folder inside the voodoo folder only ?
Again, thanks
:good:
What were you planning on flashing?
You can probably leave it there for now, and after you have flashed then you can dispose of the folder.
Sent from my Transformer using xda app-developers app
andros11 said:
What were you planning on flashing?
You can probably leave it there for now, and after you have flashed then you can dispose of the folder.
Sent from my Transformer using xda app-developers app
Click to expand...
Click to collapse
First off andros11 - thank you so much for your time in replying to my issue.
My daughter has been looking over the development site - and,
as it stands right now, she has her mind set on the Dark Night Rom by VortexJunior.
Here is the link, if it helps http://forum.xda-developers.com/showthread.php?t=1662280
The install instructions, while relatively simple - and similar to what I am used to doing - but no mention of lagfix
Installation: From Gingerbread
1. Download Zip
2. Wipe Data/Factory Reset
3. Wipe Cache Partition
4. Flash
5. Reboot into recovery(Advanced>Reboot recovery)
6. Flash again
7.BAMM!
Thanks again for your time and replies,
Regards
Once on ICS I don't think you have to mind about lag-fix..
Also, I suggest you just reboot instead of rebooting into recovery. That often causes recovery bootloops.
When you reboot, the phone will hang at the kernel splash screen (this is normal). Just take out the battery, place it back in and boot into recovert with 3-finger combo (vol +, vol - and power, and let go when samsung logo pops up)
My personal suggestion is that you move on to JB. It performs much better, and mostly all development is now there.
Perfect - thanks
Am running CM 10.1 on my tablet, and love it
Will have my daughter research JB ROMs instead.....
Happy Holidays to you and your family
Regards,
sent from my GT-P3113 using Tapatalk 2
Lag fix??
I am confused.. what exactly is the lagg fix? My GF has a JB (one of phablet ROMS) installed and all the JB ROMS I have installed on this phone (and I think all ROMS besides JB) have had lagg problems. So I would really like to know how to fix this phone.
About that lagfix...
If I remember correctly voodoo lag fix was originally designed for the Galaxy S to change the file system it ran at to something that made the phone feel more responsive and access recourses quicker. It was ported to other ROMs so if a ROM includes it then you're ok to use it but I don't think you can just apply it to any JB ROM. Plus after using a GB ROM with this lagfix for some time, any 4.0 and above ROM I have used after that has been a LOT quicker in comparison. So I would probably look into the way you JB roms were installed maybe do a data wipe/factory wipe in CWM and reinstall the ROM from the beginning. What ROMs are you using exactly?