Database Info

[Q] root on the go

Is there a way to quickly root your phone without using a computer? I'm tired of having to nandroid a backup and then losing my root. Please give me suggestions or what you do when your on the go. Thanks.

mmanjj said:
Is there a way to quickly root your phone without using a computer? I'm tired of having to nandroid a backup and then losing my root. Please give me suggestions or what you do when your on the go. Thanks.
Click to expand...
Click to collapse
just root your phone once, the right way. flash a custom rom then backup that rooted custom rom. i backup twice a week(because i flash often). when restoring, restore your most current backup. id take your stock backup off your phones sd and put it on your desktop for safe keeping, you dont need to use it. make a backup of your rooted rom before you flash another rom. that way if you need to restore it, youll have root still and all your current apps/data.

mmanjj said:
Is there a way to quickly root your phone without using a computer? I'm tired of having to nandroid a backup and then losing my root. Please give me suggestions or what you do when your on the go. Thanks.
Click to expand...
Click to collapse
I have restored to 3 different nandroid backups today (stock w/root, CM7 with trinity 1.4ghz kernel, and bionix with trinity 1.3ghz kernel) and restored my wife's to stock w/root then back to CM7 (had to bring it in to tmo as there was a data issue so i took it back to stock). So I really don't understand what you mean about losing root. The only way to lose root is if you A) return to a completely stock nandroid or B) are only using something like z4root to get a temp root. You would lose Clockwork Recovery Mod if you didn't follow all the directions to root via a computer but aside from that man...I have no clue what you're talking about.

kenvan19 said:
I have restored to 3 different nandroid backups today (stock w/root, CM7 with trinity 1.4ghz kernel, and bionix with trinity 1.3ghz kernel) and restored my wife's to stock w/root then back to CM7 (had to bring it in to tmo as there was a data issue so i took it back to stock). So I really don't understand what you mean about losing root. The only way to lose root is if you A) return to a completely stock nandroid or B) are only using something like z4root to get a temp root. You would lose Clockwork Recovery Mod if you didn't follow all the directions to root via a computer but aside from that man...I have no clue what you're talking about.
Click to expand...
Click to collapse
i assumed it was either a or b also..

simms22 said:
i assumed it was either a or b also..
Click to expand...
Click to collapse
-_- I see you beat me to the answer. Now I must duel you.
/glove_pull_up
/glove_slap
/glove_pull_down

for instance i just rooted my phone again now. its stock. if i nandroid it now with no customizations other than root and return to this nandroid i will maintain root correct?

mmanjj said:
for instance i just rooted my phone again now. its stock. if i nandroid it now with no customizations other than root and return to this nandroid i will maintain root correct?
Click to expand...
Click to collapse
Umm again, I don't know how you're rooting and I can only vouch for the adb push method as its what I did with mine and my wife's phones. Assuming you did it that way, assuming you installed CWM, and assuming you changed the name of the recovery installer file you will maintain root through nandroid backups and maintain CWM through reboots as well.

kenvan19 said:
-_- I see you beat me to the answer. Now I must duel you.
/glove_pull_up
/glove_slap
/glove_pull_down
Click to expand...
Click to collapse
dude, i just pulled this ban hamster out in another thread here. you dont want to mess with me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

kenvan19 said:
Umm again, I don't know how you're rooting and I can only vouch for the adb push method as its what I did with mine and my wife's phones. Assuming you did it that way, assuming you installed CWM, and assuming you changed the name of the recovery installer file you will maintain root through nandroid backups and maintain CWM through reboots as well.
Click to expand...
Click to collapse
i used the sticky for rooting, "flashing clockwork recovery method". I use in cmd prompt fastboot flash recovery recovery.img so what i basically want to know is if im on my stock rom with root, with recovery-install.sh file renamed and nandroid it now, when i flash back to this will i maintain root?

mmanjj said:
for instance i just rooted my phone again now. its stock. if i nandroid it now with no customizations other than root and return to this nandroid i will maintain root correct?
Click to expand...
Click to collapse
yes. if you have root that is. if, for instance, you decided to flash cyanogenmod7, then after you booted up you went back to recovery and made a backup, you would restore cyanogenmod when you restored it. you can make many backups btw, then chose which one you want to restore.

OK I just want a rooted stock image so I can flash from there to my hearts content.
Sent from my Nexus S using Tapatalk

simms22 said:
yes. if you have root that is. if, for instance, you decided to flash cyanogenmod7, then after you booted up you went back to recovery and made a backup, you would restore cyanogenmod when you restored it. you can make many backups btw, then chose which one you want to restore.
Click to expand...
Click to collapse
For reference to the OP, this is what I do. When I see a new rom I want to try I do a backup through Rom manager (it allows you to name Backups rather than just have a date/timestamp). Then I do a titanium back up of all my apps. Next I flash the rom and/or kernel I want to try and then do a titanium restore of my apps, get everything set up how I like it and then immediately do another NANDroid backup through Rom manager.
Right now I have these backups on my phone:
StockWapps (Stock rom, stock kernel, rooted, with apps set up)
CM7apps (CM7 rom, standard CM7 kernel, rooted, with apps set up)
CM714apps (CM7 rom, trinity 1.4GHz OC kernel, rooted, with apps set up)
Bionixapps (Bionix rom, standard bionix kernel, rooted, with apps set up)
Bionix13apps (Bionix rom, trinity 1.3GHz OC kernel, rooted, with apps set up)
Bionix14apps (Bionix rom, trinity 1.4GHz OC kernel, rooted, with apps set up)
On my wife's:
StockWapps (Stock rom, stock kernel, rooted, with apps set up)
CM7apps (CM7 rom, standard CM7 kernel, rooted, with apps set up)
BionixZuneApps (Bionix rom, standard bionix kernel, ZuneEvo theme, rooted, with apps set up)
If you see the pattern its basically ROMThemeKernelApps for easy reference when restoring. Its so simple that I told my wife this morning to put her phone back to stock and she was able to figure it out with only minimal help getting to the right screen (she is a complete techNOTphile)
Also, I have a backup on my computer of all of the backups. Unlike Simms, I only do backups when I make significant changes to apps, themes etc (by significant I include changing a shortcut on my launcherpro dock lol).

ClockRecovery version5

I updated to Clockwork Recovery. Now my phone is stuck on HTC boot screen. I cant even recover my back up's. it keeps getting stuck on boot screen. Nothing is working. What can I do? Is it bricked? Can someone hook me up? thanks

I don't know if I'm replying too late, but here's what I did.
Hold volume button down while turning the phone on. You'll get the white bootloader screen w/ skating androids and then just scroll til you see the "Recovery" option. Highlight and push the power button.
Reinstall your nandroid backup.
Once you can, double check RomManager to see if it's actually upgraded.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The version numbers should match this image. Clockworkmod RECOVERY 5.0.1.0.

reynaldorivera said:
I updated to Clockwork Recovery. Now my phone is stuck on HTC boot screen. I cant even recover my back up's. it keeps getting stuck on boot screen. Nothing is working. What can I do? Is it bricked? Can someone hook me up? thanks
Click to expand...
Click to collapse
Did you try holding volume down and the power button when powering on the phone? You can get to recovery from the bootloader. If that doesn't work, I think your only opton would be reflashing recovery via fastboot.

You may have an older version of rom manager. To get clockwork 5 to work when I flashed it I had to update my rom manager. This happened today I tried to flash miui to review it and it told me I needed new rom manager. But since your stuck on boot screen your other options would be flash a recovery via fastboot OR run a flash with Cmd prompt (assuming you are on windows)
Sent from my Nexus S 4G using Tapatalk

I just installed CM7RC1.7 and now my phone won't boot nothing but the CM7 rom. I keep getting hung up in the white boot screen. I was trying to use a nandroid of sense to get the GPS working with CM7. So have i punched a one way ticket to CM7 or what? How do get my sense nandroid to load? Im on the most current CWR, so im baffled now. I even tried to just install a sense rom instead of going back to an nandroid. Same result, stuck at boot screen, unless i restore that nandroid of CM7 i just installed.

bamaredwingsfan said:
I just installed CM7RC1.7 and now my phone won't boot nothing but the CM7 rom. I keep getting hung up in the white boot screen. I was trying to use a nandroid of sense to get the GPS working with CM7. So have i punched a one way ticket to CM7 or what? How do get my sense nandroid to load? Im on the most current CWR, so im baffled now. I even tried to just install a sense rom instead of going back to an nandroid. Same result, stuck at boot screen, unless i restore that nandroid of CM7 i just installed.
Click to expand...
Click to collapse
If clockwork is your recovery than you can try to install a backup straight from your recovery in bootloader instead of running your phone. Can you get into your recovery
Sent from my Nexus S 4G using Tapatalk

bamaredwingsfan said:
I just installed CM7RC1.7 and now my phone won't boot nothing but the CM7 rom. I keep getting hung up in the white boot screen. I was trying to use a nandroid of sense to get the GPS working with CM7. So have i punched a one way ticket to CM7 or what? How do get my sense nandroid to load? Im on the most current CWR, so im baffled now. I even tried to just install a sense rom instead of going back to an nandroid. Same result, stuck at boot screen, unless i restore that nandroid of CM7 i just installed.
Click to expand...
Click to collapse
I can't get any sense rom to work but all AOSP ones do so I think we are in the same boat... I get bootloops on all sense roms...

bamaredwingsfan said:
Im on the most current CWR, so im baffled now.
Click to expand...
Click to collapse
Some people were having trouble getting the CWR to stick yesterday. Are you certain it updated properly to the new blue 5.0.1.0? If you think the CWR is the problem, you could try to downgrade it before flashing the Sense Rom. Try this link

perhaps the sense roms are not compatiable yet with the latest recovery. that would be my guess.

yareally said:
perhaps the sense roms are not compatiable yet with the latest recovery. that would be my guess.
Click to expand...
Click to collapse
Yea I just tried it again... :-( I miss sense...

I had to install a fresh from download ROM manager then download cwm 4.0 and recovery worked fine. Somethin is weigh with 5.xx
Sent from my thunderbolt using Forum Runner

dms76 said:
I had to install a fresh from download ROM manager then download cwm 4.0 and recovery worked fine. Somethin is weigh with 5.xx
Sent from my thunderbolt using Forum Runner
Click to expand...
Click to collapse
5.xx is working fine on my phone. Plus I like the blue color he used this time. It might be buggy for other phones but on mine it works like a charm
Sent from my Nexus S 4G using Tapatalk

Have you tried a restore yet?
Sent from my thunderbolt using Forum Runner

dms76 said:
Have you tried a restore yet?
Sent from my thunderbolt using Forum Runner
Click to expand...
Click to collapse
I've done a backup and restore. Working fine for me. I do not use ROM manager. Only do backups from cwm. Flashed 5.0.1.0 from hboot. Downloaded the zip from Absolute_Zero's thread in the development section.

yareally said:
perhaps the sense roms are not compatiable yet with the latest recovery. that would be my guess.
Click to expand...
Click to collapse
Shouldn't be the case. At the point that recovery is running, the ROM itself has NO relevance. The ROM and recovery do not run at the same time. It's like the BIOS on a PC - while it's running, Windows, Linux, etc is NOT running.

Hey all . I had the same problem the new version of clockwork will not backup or restore . I had to flash a fresh ROM also to get booted up then downgrade clockwork again. I also noticed that the backups I tried to restore the img files were turned to tars . What up with that ?
Sent from my ADR6400L using XDA App

Jorge330823 said:
If clockwork is your recovery than you can try to install a backup straight from your recovery in bootloader instead of running your phone. Can you get into your recovery
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
Cyanogen doesn't support recovery before version 4, but I never searched for the reason. I assume the install script for it.

hallstevenson said:
Shouldn't be the case. At the point that recovery is running, the ROM itself has NO relevance. The ROM and recovery do not run at the same time. It's like the BIOS on a PC - while it's running, Windows, Linux, etc is NOT running.
Click to expand...
Click to collapse
It is the case I can confirm. Also some roms have been known in the past to not work with certain versions of recovery so this is nothing new. I went back to 4.x and sense roms work again.

Ok, managed to get back to a sense rom. I looked up the app version of CWR and it was not the most current it was 03 instead of 05. So i updated the app an had the most current recovery(blue one) and tried to restore my nandroid of sense to get out of CM7 Same result, white brick until i wipe everything an restore the CM7 nandroid. Being baffled, i tried some different combinations, but it was getting late, so i had to stay on CM7. Go to work today, and CM7 is just not cutting it, BT was all over the place. So this time i deleted my Ti backup of CWR, an installed new an fresh. Reinstalled the recovery just to make sure everything was the most current. Thank god before i went to bed last night, i copied over a zip of gingeritis3D as a just incase if all else fails. Well, all else failed, so i had to try a fresh install of a new rom instead of going to a nandroid backup. That failed too. One last try, an here is what worked. I wiped everything but dalvic an did the fresh install of gingeritis3D, an bingo, the phone booted! I was never so happy to see sense as i was at that moment. I then preceeded to delete any an everything off my phone that pertained to CM7. I never had a single problem until i installed that CM7 1.7 rom on my phone. Im not saying that is what caused my problem, but something did. Right now im mainly leaning toward the wiping of the dalvic that was causing most of the trouble. Guess we will see in a few days when i try a different sense rom.

i hope a stable build comes soon.

Losing ROOT on ICS ***FIXED***

Ok. Think I got the problem fixed. see my last post # 37........
I keep losing root, no matter what kernel or rom for ICS i install. this only seems to happen when i going system with root explorer to make changes to media sections. i tried to reflash su, busybox, wipe data-cache. The only way to get root back is to revert back 2.3.5 and then install ics rom- but i soon as i go into system and change it from r-o ro r-w it locks up and locks me out. Superuser is even locked out . Is there a fix for this or am i just out of luck. you can see what i get from superuser update.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

If you are doing the design gears exe you are supposed to lose root.
Sent from my SAMSUNG-SGH-I727 using xda premium

Sheolrock said:
If you are doing the design gears exe you are supposed to lose root.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
not running that.
running sliver03wrx rom- even installed mohans kernel to try and fix it.
installing it via cwm flash

follow these steps
flash darkside through cwm
flash designgears
reflash cwm
flash darkside
flash ANY ics rom, ics perfections 4.2 by mhx is good
problem solved, permanent root

icenight89 said:
follow these steps
flash darkside through cwm
flash designgears
reflash cwm
flash darkside
flash ANY ics rom, ics perfections 4.2 by mhx is good
problem solved, permanent root
Click to expand...
Click to collapse
ok i tried this and it did not work. still lost root..
anymore ideas.

galaxyuser88 said:
ok i tried this and it did not work. still lost root..
anymore ideas.
Click to expand...
Click to collapse
Flash superuser zip in cwm.Make sure busybox is installed if its not search for busynox installer in android market, also update su binary under su app in app drawer.
Sent from my SAMSUNG-SGH-I727 using xda premium

cdshepherd said:
Flash superuser zip in cwm.Make sure busybox is installed if its not search for busynox installer in android market, also update su binary under su app in app drawer.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
did that all up to date and still lose root. It seems that when i loose root i can reflash and root back, but as soon as i go into systems/media and then change it from ro to rw it looses root and i have to reflash to get it back.

galaxyuser88 said:
ok i tried this and it did not work. still lost root..
anymore ideas.
Click to expand...
Click to collapse
Wait, what? My instructions completely wipe the phone then put on cwm again and an ics rom. If u followed them precisely im sorry but there's no way you're losing root. Please elaborate and what u did

Ok. I followed your steps to the letter. and i even tried a few different roms for the last step. And nothing seems to help me from losing root. As long as i stay out of the system folder (and i havent tried another sys folder) then i dont lose root. I really do not know what else to do or say..
icenight89 said:
follow these steps
flash darkside through cwm
flash designgears
reflash cwm
flash darkside
flash ANY ics rom, ics perfections 4.2 by mhx is good
problem solved, permanent root
Click to expand...
Click to collapse
icenight89 said:
Wait, what? My instructions completely wipe the phone then put on cwm again and an ics rom. If u followed them precisely im sorry but there's no way you're losing root. Please elaborate and what u did
Click to expand...
Click to collapse

Have you tried flashing romancer's kernel, wait 30 seconds, flash it again, then fix permissions and reboot. (Trying a different mod won't really help)
I tried to fix mine several ways, but just reflashing the kernel a few times and fixing permissions was the best fix
Sent from my SAMSUNG-SGH-I727 using XDA

burgeswe said:
Have you tried flashing romancer's kernel, wait 30 seconds, flash it again, then fix permissions and reboot. (Trying a different mod won't really help)
I tried to fix mine several ways, but just reflashing the kernel a few times and fixing permissions was the best fix
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
Yeah i have tried rom racers kernel.. tried to fix permissions, (that really locked me out, where flashing su wouldnt take, even flashing su 10 times to try and get it to take) only way to get root back was to wipe and reflash the complete rom..
And before anyone asks. my phone is ATT samsung sgh-i727. so iam not trying to flash anything that doesnt belong to another carrier or phone.. Yes i have rooted and flashed serveral different devices on different carriers with out any issue, except for bricking a galaxy tab 7, but got that back up by doing the unbrickable mod to it. So iam not a newbie by any means..

Flash this in CWM;
http://forum.xda-developers.com/showthread.php?t=1565126
Flash a few times it should let you through.
Fix permissions before reboot.
Then install BusyBox.
let us know.

Curious, do you have the same problem going thru an adb shell to modify the system?

fongz27 said:
Flash this in CWM;
http://forum.xda-developers.com/showthread.php?t=1565126
Flash a few times it should let you through.
Fix permissions before reboot.
Then install BusyBox.
let us know.
Click to expand...
Click to collapse
ok did this a few times, root and busybox installed, but it still does the same thing, as soon i go into system and mount rw, it lets me mount it and then it locks me out again, and then i lose it it again. It seems that root holds as long i stay out of the system files. Seems like the sys/system files have a security measure or something in there to prevent unwanted access.
Even i when i go back to the earlier version 2.3.5 and try to flash ics with no wipe- it gets stuck at a boot loop, samsung- samsung- android, samsung-samsung-blank screen, samsung-samsung-android, etc. I have wait 10 mins for this bootloop to go thru, and nothing. I would have to pull battery, go into recovery and do a wipe, and then reboot into ICS.
This is very confusing and fustrating trying to get this to work.
I am able to regain root when i reflash su and busybox but it seems no matter what rom/kernel-version of cwm- version of superuser, version of busybox, i try i get the same outcome.

If you are going back to 2.3.5, it is recommended you do a FULL WIPE; you are changing kernels and system files and everything else. A clean wipe will give u the cleanest install. You are getting bootloops bcuz of non-clean wipes.
Do an ODIN install to 2.3.x with stock recovery. Then flash the original ICS leak in dev section using ODIN. Then use darkside wipe, then flash your choice of ICS rom; most ICS roms should come with root now. Just need to add busybox.
Seems like you aren't wiping correctly or something.

fongz27 said:
If you are going back to 2.3.5, it is recommended you do a FULL WIPE; you are changing kernels and system files and everything else. A clean wipe will give u the cleanest install. You are getting bootloops bcuz of non-clean wipes.
Do an ODIN install to 2.3.x with stock recovery. Then flash the original ICS leak in dev section using ODIN. Then use darkside wipe, then flash your choice of ICS rom; most ICS roms should come with root now. Just need to add busybox.
Seems like you aren't wiping correctly or something.
Click to expand...
Click to collapse
I did a super wipe using darkside wipe. I wiped everything even both int-ext sd cards. Tried this method as stated in one of the earlier posts.

cschmitt said:
Curious, do you have the same problem going thru an adb shell to modify the system?
Click to expand...
Click to collapse
yup just tried it. let me remount rw system once. closed went back and tried again and mount: read-only file system
lost root again

galaxyuser88 said:
yup just tried it. let me remount rw system once. closed went back and tried again and mount: read-only file system lost root again
Click to expand...
Click to collapse
Are you running one of the insecure kernels? That will put you into root at adb shell without issuing su. From there you an remount system as rw and modify system, give it a shot.
Running stocked, rooted UCALC4 ROM with the mohan_kr insecure kernel and have not problems writing in /system/media with either an adb shell or ES File Explorer.
Didn't do anything special as far as wipe scripts, etc. Just flashed the one click, then CWM, insecure kernel, superuser zip, installed busybox.
Maybe try thru adb shell or a different file explorer app and see if you get different results.

I have a similar problem but only with some roms. I can't use the collective rom even after formatting data as I get locked out from accessing system files

There does seem to be some problem with different versions of CWM not working as well as others with kernel flashing
Personally, I've had far more luck with
http://forum.xda-developers.com/showthread.php?t=1472954
Than any others
Flash that, then flash the unsecure kernel, then flash su. (I don't think another wipe is needed, might be wrong)
Sent from my SAMSUNG-SGH-I727 using XDA

Help me, cannot flash CM9

I flashed the first build of CM9. so sweet, and now I have problem. Battery is 50% and after 2 hours, battery 0%, cannot charge phone.
I stock my phone back 2.2, original rom and download 4th build CM9.
Get stuck at Samsung Screen, follow the instruction, I cannot choose rom in CWM, screen cannot display full option and I can re-flash 4th CM9?
Plz, help me

You Can reflash again..? Did you get blue cwm?

I had this problem with CM9 too. What I did was I let it do its freezing thing on the charger for about 2 minutes, then I tried turning it on off the charger, just until the samsung logo disappears, then quickly replug in the phone and it'll charge! I'm assuming that's what your issue is, at least. As for the battery life, I'm not sure what to tell you there.

bigjoe2675 said:
You Can reflash again..? Did you get blue cwm?
Click to expand...
Click to collapse
yes, I cannot reflash again after got stuck at samsung screen.
back to blue CWM, the screen cannot display full options, cannot choose rom to reflash

kitarodo said:
yes, I cannot reflash again after got stuck at samsung screen.
back to blue CWM, the screen cannot display full options, cannot choose rom to reflash
Click to expand...
Click to collapse
Are you having rainbows?

Bjray said:
Are you having rainbows?
Click to expand...
Click to collapse
yes, rainbow display a half screen, and cannot choose rom or whatever you want ...

kitarodo said:
yes, rainbow display a half screen, and cannot choose rom or whatever you want ...
Click to expand...
Click to collapse
Two methods you can use...go back to stock and it will put gb boot loaders and CWM, so that you can flash CM9 with CWM visible/working.
Read all details on these OPs...
Odin
http://forum.xda-developers.com/showthread.php?t=1613523
One click
http://forum.xda-developers.com/showthread.php?t=1524081

ocesite 159
bigjoe2675 said:
Two methods you can use...go back to stock and it will put gb boot loaders and CWM, so that you can flash CM9 with CWM visible/working.
Read all details on these OPs...
Odin
http://forum.xda-developers.com/showthread.php?t=1613523
One click
http://forum.xda-developers.com/showthread.php?t=1524081
Click to expand...
Click to collapse
I will try it , thanks bro

so bad, stock 2.3.6 cannot flash any rom, cannot stock back to 2.2, odin cannot connect ??? what's happened ?

kitarodo said:
so bad, stock 2.3.6 cannot flash any rom, cannot stock back to 2.2, odin cannot connect ??? what's happened ?
Click to expand...
Click to collapse
Which method did you use? More details please, and we can get you flashing from 2.3.6. Don't go back to 2.2.
If you flashed one of the Odin to stock 2.3.6 options w/ root, you just need to use SGS Kernel Flasher (in market) to flash a kernel w/ cwm recovery. See the FAQ in the first link that bigjoe gave you.
If you used Heimdall one click, read further down in qkster's thread for how to get cwm recovery. You need cwm recovery to flash roms.
You don't need to Odin again, but to get it to see your phone, try a different USB port. Sounds like you're trying to use your Heimdall port (Heimdall libusb installs to and takes over one specific port.).
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2

God feels like this everytime a thread like this is posted due to the lack or research and reading
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
lol

jscott30 said:
Which method did you use? More details please, and we can get you flashing from 2.3.6. Don't go back to 2.2.
If you flashed one of the Odin to stock 2.3.6 options w/ root, you just need to use SGS Kernel Flasher (in market) to flash a kernel w/ cwm recovery. See the FAQ in the first link that bigjoe gave you.
If you used Heimdall one click, read further down in qkster's thread for how to get cwm recovery. You need cwm recovery to flash roms.
You don't need to Odin again, but to get it to see your phone, try a different USB port. Sounds like you're trying to use your Heimdall port (Heimdall libusb installs to and takes over one specific port.).
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
thanks bro, after flash Heimdall on click, I came back to 2.2 - original rom, and now, I can flash CM9 and no problem so far

kitarodo said:
thanks bro, after flash Heimdall on click, I came back to 2.2 - original rom, and now, I can flash CM9 and no problem so far
Click to expand...
Click to collapse
If you went back to 2.2 bootloaders with a back-to-stock package, I hope that you like rainbows in your recovery. You didn't have to go back to Froyo to get to CM9. Either way, though, if it's working for you, then glad it worked out.

jscott30 said:
If you went back to 2.2 bootloaders with a back-to-stock package, I hope that you like rainbows in your recovery. You didn't have to go back to Froyo to get to CM9. Either way, though, if it's working for you, then glad it worked out.
Click to expand...
Click to collapse
This time, I didn't get any problems, rainbows in recovery It's worked good for me, but 22/04 build, wireless work not good, turn on wireless too slow, sometimes need reboot to connect wireless

[Q] TWRP Q&A

Dont want to muck up the CM7 thread and no thread was started.
FB Im wondering if twrp is fully wiping when you run the wipe option. I used the kj6 heimdall one-click to get back from a bad flash. However once I finally was able to get everything set back up I had restored some apps through Titanium Backup, but only app no data. Amazon app store was one and I had to delete the backup and uninstall the app, reboot clear cache and then re-install it to get it to work. The theme chooser app was fcing on me until I did the same thing.
After I did this I applied a theme apk that borked me. I was stuck on the team acid logo. No boot loop just stuck. I then one clicked to kj6 again, then used antonx kernel one click. Made a new backup of my efs, wiped everything including boot img. Flashed the twrpcm7 zip and followed the directions to finish.
I know anything is possible but is it likely that twrp is seeing something not wiped in the bml to mtd conversion and its causing conflicts?
If your not comfortable with the possibility of bricking your phone do not follow my steps and format everything. Formatting boot has the possibility to brick your device.

Hmm, well /data isn't getting wiped in R11. Bryan submitted a patch for updater.sh that should take care of this though I haven't tested it. I haven't tested a BML->MTD (cm7-twrp) flash though, but I'll have to look into it in the next few days. I'm running a rom build right now, so I'll probably test that out tonight.

I didn't wipe anything, I just flashed the twrp boot.img. I am running Team Kick Asses MIUI Revenge (MTD). After I flashed and the phone booted, wifi would not turn on, and it said error underneath the button. Pulled a logcat but all it said was wifi failed to initialize. Is that error due to the fact I didn't wipe anything or factory reset/fix perms?
Either way, it is super sweet recovery!

Max says its a driver issue. Ill find the post and link it.
m4xm4n said:
The reason wifi didn't work is because the wifi module needed to be from the same kernel build. I'm not sure how FB built the two builds, so I don't know if he included a module from a different kernel build or not.
Try the R11B with TWRP and then install R11(not B) with inject TWRP enabled.
Sent from my SGH-T959V using XDA
Click to expand...
Click to collapse

Now that you have twrp make a cwm zip for the r11 kernel, flash it via twrp and leave the "inject twrp" option enabled. You should get working wifi and twrp
Sent from my SGH-T959V

Like I said on cm thread the wifi module is different from the one Max used on his new boot.img which is why twrp and the new boot.img doesn't work with the current miui build ...the first release of dianxin os had the new boot.img fb sent me and that was the wifi issue.
sent from my batcave

I flashed miui on with twrp doing a wipe firs and it installed miui fine, with wifi and everything seems to be fully functional. Just to be safe I wanted to test out twrp on miui, however the only way I could get to it was volume up+down+ power. But that loads it right up, and I flashed a few different modems to see which gave me the best signal, and it worked each time. Btw, nice work fb twrp is great.
Sent from my SGH-T959V using xda premium

Which modems did you flash? If the modem flash DID work you should be able to go into Settings > About Phone and check under baseband version. I'm not sure if that's the exact menu on MIUI but there should be something very similar.

I just flashed kg4 and that's what it says under baseband version, I flashed kd1 earlier and that's what it said before I just flashed kg4. Just to make sure it was working. I think it says t959vuvkg4 or something to that effect, it definately just changed though from kd1
Sent from my SGH-T959V using xda premium

Hey guys just a progress report on this. I've been messing with a twrp injection cwm zip all evening. After some discussion with bhundven, the way we're going to go about this is to NOT include twrp by default in cm7. It's been really hard to get a working copy compiled and included with cm7 and if we can't do this automatically there's no point to doing it at all.
The CWM zip will (hopefully) allow us to give you the option of using TWRP even if you're using CWM at the moment. The benefits are the following:
You won't need to mess around with kernel features that don't work (wifi was broken, ffc was broken)
You only really need to inject twrp once via CWM since twrp comes with an inject option before you flash a CM7 update.
It'll make it easier on us since we'll have less releases and thus have to provide less support.
At the moment I'm trying to have something for you guys tonight, but the chances are slim for that happening.

FB
For some reason TWRP can't Flash Zip file like Mtd modem kd1. I try to make a nandroid bk and didn't work. Also I try to save error logs on sd card didn't work.
My english is not the best, sorry
Sent from my SGH-T959V using xda premium

Please post the logs here.
What errors did you get when trying to flash the kd1 modem or make the nandroid backup? I've tried making and restoring a nandroid backup using CM7 R11 with twrp injected by the zip and it's worked fine for me.
What rom/kernel combination are you using?

Error: Unable to open zip file
I try nandroid backup again and for some reason did work but wasn't working.
Am using CM7 R11B & CWM TWRP
Everyting else is working good thanks!!!!
Sent from my SGH-T959V using xda premium