[Q] md5 misfit issues - Wildfire Q&A, Help & Troubleshooting

hi all.ok,im a noobish flasher !!!! (lol) i have tried several of the roms etc and i make clockworkmod nandroid backups regular,all of a sudden i am no longer able to restore my nandroid backups due to keep getting md5 misfit i have not changed the name of the folder or anything like that they are put onto my p.c for safe keeping so as to just drag and drop later. i have change the size of the partition on the sd since nandroid back-ups so would this cause the md5 issues ?? i think i might be using a newer rom manager than previous too but why would this affect the nandroid stuff !!!

md5 issues
nobody !!!!!!

what happens if instead of rom manager, you restore through hboot?

ephbee
hi, ive give up and have now accepted that i have lost my original network rom.im still learning this stuff so ive never tried the hboot thing, i just installed wildpuzzle and my phone is working ok.ive still got the rom saved as a backup just in case i get any joy or answers of how to overcome the md5 issue. really annoying though.

Check here:
http://forum.xda-developers.com/showthread.php?t=714114

hi,cheers for the link.too complicated for me all that adb stuff so just gonna keep my trust with the dev roms.using wildpuzzle now since start of feb and its fine for what i use my phone for. regards slymobi.

hi again.ok im not clued up with adb but i have got terminal emulator on my phone. can you give me instructions on how i could try the method in the link you gave me but by using terminal emulator instead of adb ??? like i said its not a must to fix but would be nice to revert back to my orignal three network installed crap if needed. i appriciate your help and replies. regards chris (slymobi)

While I do not know whether it will work using the Android Terminal (Don't use Terminal much. Prefer using ADB), I would recommend you read up some ADB tutorials. There are loads of them, and really, ADB is a must-have, and, not complex at all.

[/QUOTxxxxxxxxx

slymobi said:
hi again.ok im not clued up with adb but i have got terminal emulator on my phone. can you give me instructions on how i could try the method in the link you gave me but by using terminal emulator instead of adb ??? like i said its not a must to fix but would be nice to revert back to my orignal three network installed crap if needed. i appriciate your help and replies. regards chris (slymobi)
Click to expand...
Click to collapse
Why make things so hard? There's eaier ways.

lambofgod13 said:
Why make things so hard? There's eaier ways.
Click to expand...
Click to collapse
Read what the senior membors post.

ephbee said:
what happens if instead of rom manager, you restore through hboot?
Click to expand...
Click to collapse
Hboot is htc drivers. It wont work.

slymobi said:
hi, ive give up and have now accepted that i have lost my original network rom.im still learning this stuff so ive never tried the hboot thing, i just installed wildpuzzle and my phone is working ok.ive still got the rom saved as a backup just in case i get any joy or answers of how to overcome the md5 issue. really annoying though.
Click to expand...
Click to collapse
Man read up before you jump into stuff.

Related

OTA Simple Root not working!!! Neither is anything else?

Hey Guys,
im not new to rooting i have a nexus one that i rooted perfectly first time around, i am using the OTA simple-root now because my phone version is 1.47.651.1. So step 3 i run the link in my evo browser it doesn't do anything...but one time it did and then step 4 got stuck on "starting part2..." what's going on? i've been trying for hours and hours...please some1 help me i really want to root and get custom roms running.
Thanks guys
Did you refresh the browser page on step 3?
JelloB said:
Did you refresh the browser page on step 3?
Click to expand...
Click to collapse
yea i refreshed it like 10 times but nothing happens...i think its because im using windows 7...should i try on a xp pc?
You can also try unrevoked3, that gets you su permissions then do toasts part 2 then use whiteslacks "how to start over method. Seems the long way around but you can usually avoid the problems simpleroot seems to cause some people.
youngdhillon said:
yea i refreshed it like 10 times but nothing happens...i think its because im using windows 7...should i try on a xp pc?
Click to expand...
Click to collapse
Also when or if i try to run the PC36IMG.zip it says "older version" and it asks to reboot the phone.
youngdhillon said:
yea i refreshed it like 10 times but nothing happens...i think its because im using windows 7...should i try on a xp pc?
Click to expand...
Click to collapse
ifly4vamerica said:
You can also try unrevoked3, that gets you su permissions then do toasts part 2 then use whiteslacks "how to start over method. Seems the long way around but you can usually avoid the problems simpleroot seems to cause some people.
Click to expand...
Click to collapse
can you please give me links to those threads so i don't have to look all over for them? i would appreciate that!!!!
Thanks
Try here... ig you got 147.651.1 will be the bottom . explain step by step , easy and useful
http://forum.ppcgeeks.com/showthread.php?t=123714 (Right now the page is under maintenace) As soon they finish go here and do step by step . Easily
Enjoy it
I have win7 x64 and it worked fine once I refreshed the browser and manually put the files on my SD
Sent from my PC36100 using XDA App
They are easy to find, just run a forum search, use advanced search then forum title only, i dont have the links in front of me i would have to search for them too, you can also try this
http://forum.xda-developers.com/showthread.php?t=701835
This will only work if you have su permissions though. give it a try and let me know how it works. You can also pm me if you like so i can find out exactl where you are in the process.
ok guys good news...i tried the OTA simpleroot on the xp pc and everything went perfectly without any error, my phone is currently updating files in bootloader as we speak, but i have a question how do i user RA recovery instead of clockwork? does it matter or make a difference? or should i just leave clockwork and load a custom rom
personal preference really, i use Ra, just boot to recovery then flash away, either one is good, some say clockwork does not completely wipe ... I havent had any problems with either personally.
I had problems loading DC 3.2.X with clockwork... but ROM manager needs clockwork and is amazing
Sent from my PC36100 using XDA App
ive heard if u connect to wifi during step 3, that will fix your probelm, i had an issue like that too, plus i had one where it said "unable to find device" in part 2

LCD density changer keeping my evo from booting

First of all, I am sorry for posting this here, but I am kind of in a bind, and hope someone can help me out..
EVO, rooted with new unrevoked, running stock everything, on a mac
I downloaded and installed LCD Density Changer today, and changed my number form 240 to 200, as everyone suggested.
When I rebooted, my boot screen started, but then the display went blank, and I keep hearing the Sprint music, but the phone's display wont come up..
I can get into recovery mode, so I am thinking of just doing a wipe data/factory reset, and starting all over, which wont be a problem, since I am all backed up.
someone suggested doing an ADB push, but I am on a mac, and cant find detailed instructions on how to do that..
Can someone give me a idea on which way to go?
I am fine with wiping data/factory reset, if it gets my phone started again..
Again, sorry if I posted this in the wrong place, but I know there are some great people here that will give me some direction
thanks so much!
i don't know what this has to do with development... but restore the backup that you made before you did the patch. didn't backup? wipe.
yup... no back up... shame on you..
your only choice is to wipe.
i dont know why people use this app, just edit the build.prop file yourself with rootexplorer or what ever app you have that can browse and edit the phones files.
Depending on what ROM you're running, you may also have to option of simply flashing it again without wiping. This would revert your build.prop and keep your installed apps and settings provided the updater-script in the ROM doesn't format /data/. I would try this before you go all out and wipe everything.
I really recommend you get ADB set up.
good news; got it to work with a zip file that a great member of this board gave to to flash; sorry if this post was placed in the wrong spot, and mods you are welcome to delete /lock it now..
BTW, doing a nandroid backup IMMEDIATELY!
you guys are the best, and SHAME on me for not doing that the minute I was rooted...
illogic6 said:
Depending on what ROM you're running, you may also have to option of simply flashing it again without wiping. This would revert your build.prop and keep your installed apps and settings provided the updater-script in the ROM doesn't format /data/. I would try this before you go all out and wipe everything.
I really recommend you get ADB set up.
Click to expand...
Click to collapse
can you do ADB on a mac computer?
thanks
wase4711 said:
can you do ADB on a mac computer?
thanks
Click to expand...
Click to collapse
If your Mac is of the Intel-based flavor, yes.
http://developer.android.com/sdk/index.html
illogic6 said:
If your Mac is of the Intel-based flavor, yes.
http://developer.android.com/sdk/index.html
Click to expand...
Click to collapse
thank you, it is an Intel!
I appreciate the link

help possible brick not sure!!!!!!!!

I HAVE SEARCHED FOR THE PAST HOUR PLEASE DON'T HATE!!!! I ALWAYS SEARCH WHICH IS WHY MY POST COUNT IS LOW!!!
K so here is my issue was installing an app and it just rebooted in the middle of the install and is now stuck in a bootloop on the white htc evo 4g screen but can still access the bootloader. have already tried flashing a pc36img.zip still nothing. if anyone can help i would greatly appreciate it. and also can't access recovery.
Thanks in advance!!!
UPDATE:NO FIX!!!!!!!! guy at sprint repair store said to file a claim and get a new one, also said say it was lost since it was rooted.
What Rom were u on?
Sent from my amazing Evo on king bliss beta v7
If you can access the bootloader then you are not bricked. If you can get into recovery then the first thing that you should try is to wipe the Cache and Dalvik Cache. If that does not work then something in your data partition may be messed up. The next step would be to wipe Data. You will lose all of you system settings and data by doing this and you will have to reconfigure your accounts and install all of your apps again. If you have a backup (using MyBackup or Titanium) you can restore that just be sure not to restore any system settings that were from a different ROM.
m20120 said:
If you can access the bootloader then you are not bricked. If you can get into recovery then the first thing that you should try is to wipe the Cache and Dalvik Cache. If that does not work then something in your data partition may be messed up. The next step would be to wipe Data. You will lose all of you system settings and data by doing this and you will have to reconfigure your accounts and install all of your apps again. If you have a backup (using MyBackup or Titanium) you can restore that just be sure not to restore any system settings that were from a different ROM.
Click to expand...
Click to collapse
Same bootloop when trying to access recovery. Also forgot to add that in op
evo4gnoob said:
What Rom were u on?
Sent from my amazing Evo on king bliss beta v7
Click to expand...
Click to collapse
was trying out the runnymede beta sense 3.5 rom everything was working great so i decided to start reinstalling apps and was gonna run it for a couple of days
Try flashing a new recovery manually. I believe amon RA thread has manual instructions
Deck's + SZ + SuperCharger script + ViperMod script.
What Hboot and radio versions do you have?
shortydoggg said:
What Hboot and radio versions do you have?
Click to expand...
Click to collapse
hboot-2.10.0001
radio-2.15.00.11.19
edit: downgraded to eng-0.76
Can you access fastboot usb on your phone (volume down +power buttons at the same time, then power button again on FASTBOOT)? If so, plug your phone to your computer and see what driver you have installed in the device manager from your computer's control panel, under Android Devices.
shortydoggg said:
Can you access fastboot usb on your phone (volume down +power buttons at the same time, then power button again on FASTBOOT)? If so, plug your phone to your computer and see what driver you have installed in the device manager from your computer's control panel, under Android Devices.
Click to expand...
Click to collapse
problem with this is i have a macbook pro.
edit: and im a bit of a noob with the fastboot and adb stuff.
odie145 said:
problem with this is i have a macbook pro.
edit: and im a bit of a noob with the fastboot and adb stuff.
Click to expand...
Click to collapse
Try this PC36IMG file on your SD card, maybe it will work, or maybe not.
http://dl.dropbox.com/u/38127313/Root 2.2/PC36IMG.zip
or try running a RUU file from your computer with your phone in Fastboot USB. One can be found here:
http://www.fileserve.com/file/PckGRqz
I'm not sure if it will work on a macbook.
will give those a try and maybe i can find a windows machine soon but at least i still have my hero as a back up
odie145 said:
I HAVE SEARCHED FOR THE PAST HOUR PLEASE DON'T HATE!!!! I ALWAYS SEARCH WHICH IS WHY MY POST COUNT IS LOW!!!
K so here is my issue was installing an app and it just rebooted in the middle of the install and is now stuck in a bootloop on the white htc evo 4g screen but can still access the bootloader. have already tried flashing a pc36img.zip still nothing. if anyone can help i would greatly appreciate it. and also can't access recovery.
Thanks in advance!!!
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
Did you use anything like firerat? That really screwed me up once... Might be a bad zip on your card also...
dropzeroc said:
Did you use anything like firerat? That really screwed me up once... Might be a bad zip on your card also...
Click to expand...
Click to collapse
wasn't doing anything out of the norm. had just flashed the runnymede beta that morning and decided to keep a few days so i ran my restore from titanium backup and in the middle of the install of one of the apps it did a random reboot and been stuck ever since.
one thing i haven't been able to try is a ruu, has to i haven't got a windows machine to run it on yet.
If anyone has the fastboot binaries for mac and can share it i would greatly appreciate it. it seems all the links im finding for it is now sending me to the new htcdev.com site.
odie145 said:
If anyone has the fastboot binaries for mac and can share it i would greatly appreciate it. it seems all the links im finding for it is now sending me to the new htcdev.com site.
Click to expand...
Click to collapse
try this link, there is a download zip in there for a MetroPCS Android phone. Inside that zip files there are two mac files adb-mac and fastboot-mac. Try it out.. hope it helps
Thanks for that link. i did finally get fastboot to recognize my evo on my mac but when i try flashing or erasing anything it say failed(status malformed)
Aso had no luck with tha RUU cant get it to connect to my device what do i need to do to get it to even run (somewhat of a noob question)
You've got to put the ruu on your SD card, as PC36img.zip
Mistress of Mischief
odie145 said:
Thanks for that link. i did finally get fastboot to recognize my evo on my mac but when i try flashing or erasing anything it say failed(status malformed)
Aso had no luck with tha RUU cant get it to connect to my device what do i need to do to get it to even run (somewhat of a noob question)
Click to expand...
Click to collapse
did you do a google search for what that meant?

Rooting Gnex GSM/HSPDA v4.0.2 Optus Stock

Hey guys!!,
Yet another of my noob questions BUT, this time I think I'm going to take the plunge and root my Gnex!!! *scared* haha
I'm just having to many frustrating things happening on my stock Gnex, low responsiveness to the touch, slow-ish and well, isnt this what its all about!! =)
So a quick one, if anyone can point me in the most normal, simple and customizable direction, what do I do? I have searched for a while now so I have an idea where i want to go, either, Cynagon or AOKP...I'm hearing great things about AOKP...there from the same devs yeah?? (a guess)
So, I have a Samsung updated Gnex, in Aus and with optus. I'm technical so I'm getting a grasp on whats what but still not to clear on Kernels and radios....bit worried about that. Clockwork I'm guessing is like a boot manager?? Just asking that while I was here...
So Odin? Wug? CF-Root? I'm just not sure...
Thanks soooo much in advance guys.... I already appreciate your help. =)=)
*Excited!!!*
Cheers!!
P.S. I'd also very much like to return to stock form later on if I want...like locked oem and restored stock rom... =)
Helmet321 said:
Hey guys!!,
Yet another of my noob questions BUT, this time I think I'm going to take the plunge and root my Gnex!!! *scared* haha
I'm just having to many frustrating things happening on my stock Gnex, low responsiveness to the touch, slow-ish and well, isnt this what its all about!! =)
So a quick one, if anyone can point me in the most normal, simple and customizable direction, what do I do? I have searched for a while now so I have an idea where i want to go, either, Cynagon or AOKP...I'm hearing great things about AOKP...there from the same devs yeah?? (a guess)
So, I have a Samsung updated Gnex, in Aus and with optus. I'm technical so I'm getting a grasp on whats what but still not to clear on Kernels and radios....bit worried about that. Clockwork I'm guessing is like a boot manager?? Just asking that while I was here...
So Odin? Wug? CF-Root? I'm just not sure...
Thanks soooo much in advance guys.... I already appreciate your help. =)=)
*Excited!!!*
Cheers!!
P.S. I'd also very much like to return to stock form later on if I want...like locked oem and restored stock rom... =)
Click to expand...
Click to collapse
Try my ToolKit in the dev forum. Its simple, straightforward, easy to understand, there is a 1-click option which will do everything and every step is explained in detail.
http://forum.xda-developers.com/showthread.php?t=1392310
You can also use my ToolKit to flash a Stock Google Rom if you ever want to in the future.
With regards to Roms there are lots available to try by very experienced developers that will make your phone better and plenty of kernels to make it run ALOT faster. I use bigxie's Rom and franco's kernel.
Mark.
Hi!!,
Thanks so much for your reply!
Funny as, I was JUST reading your guide. Awesome work man, very informative.=)=) and it would of taken some time to compile!. =/
Arm, I'm just wondering what file I need to backup to got back to the rom I'm on now? I want to be able to go back, if needed.
I don’t know what kernels are all about, and what do I need to do about Radios?? If I have the wrong one or something, does that mean I wont have signal?? Or bad call/signal reliability?
I'm looking at the build 23 of AOKP...I'm hearing its the go...and if i have a wrong kernal rom radio combo, what’s that going to do??, that’s if they correlate?? haha
Is security as issue?? Since these are built "freely" is there any exposure of private info?
I'm sorry for smashing you with all this, I'm just trying to get all the info before I do anything and to have a failsafe if I need to return for warranty.... =/
Thank you in advance!!! =)
Cheers.
P.S. Is Bigxie Apex?? I hear good things about that too!! haha. Its so hard, theres so many out there... Apex, Gummy, AOKP look great. I also really want a responsive, battery lasting, fast and importantly "stable" phone. So, not sure what you recommend. =)
Thanks already!! =)=)
Helmet321 said:
Hi!!,
Thanks so much for your reply!
Funny as, I was JUST reading your guide. Awesome work man, very informative.=)=) and it would of taken some time to compile!. =/
Arm, I'm just wondering what file I need to backup to got back to the rom I'm on now? I want to be able to go back, if needed.
I don’t know what kernels are all about, and what do I need to do about Radios?? If I have the wrong one or something, does that mean I wont have signal?? Or bad call/signal reliability?
I'm looking at the build 23 of AOKP...I'm hearing its the go...and if i have a wrong kernal rom radio combo, what’s that going to do??, that’s if they correlate?? haha
Is security as issue?? Since these are built "freely" is there any exposure of private info?
I'm sorry for smashing you with all this, I'm just trying to get all the info before I do anything and to have a failsafe if I need to return for warranty.... =/
Thank you in advance!!! =)
Cheers.
P.S. Is Bigxie Apex?? I hear good things about that too!! haha. Its so hard, theres so many out there... Apex, Gummy, AOKP look great. I also really want a responsive, battery lasting, fast and importantly "stable" phone. So, not sure what you recommend. =)
Thanks already!! =)=)
Click to expand...
Click to collapse
If you goto settings, about phone then it will tell you all about your current rom build. If its a yakju build then its a stock google rom and can easily be found and reflashed via my ToolKit. If its been put on by your operator then you wont be able to obtain it online and you are best backing it up (unless you dont mind putting the google stock rom back on).
To do that you will need to set your drivers up first. This is important as nothing else can be done without this step. If you have Windows xp or 7 then its pretty easy, you can install the drivers automatically via the GNex ToolKit, then reboot your pc. Goto settings, developer options on your phone and tick 'usb debugging' then connect the usb cable to your phone (with it booted into Android). This should install adb drivers which are needed for communication when your phone is booted into Android. Start the ToolKit and select your current build version (which can be found in settings, about phone). At the top of the Main Menu you should see a serial number under adb mode which means your device is recognised in this mode. Select reboot options (19) in the ToolKit and Reboot phone to Fastboot (3). This is a bootloader mode for the phone outside of Android where you can flash and manipulate certain parts of your phone. As this mode is at a much lower level then the operating system it can be your saviour if your phone locks or wont start and you need to flash back to stock.
Once the phone has rebooted to fastboot mode the fastboot drivers should be installed on your pc. If nothing happens try unplugging and replugging the usb cable to initiate the drivers. If the drivers have installed before the ToolKit refreshes then you should now see the serial number at the top under fastboot mode this time. You NEED both fastboot and adb drivers installed on your pc for everything to work.
After the drivers have been set up you will need to Unlock the Bootloader to be able to have access to system areas on your phone. BE AWARE that unlocking the bootloader will erase EVERYTHING all data on your phone including the Internal Storage (virtual SD Card) so copy anything you need to from your Internal Storage accross to your pc and use the Backup option in the ToolKit to save any installed apps and associated user data that you want to keep. This is done in adb mode so your phone will need to be in Android.
If you want to back up your current Rom then Unlock the Bootloader, reboot your phone into Android, go through the setup quickly (as the phone will have been wiped), then goto settings developer options and enable usb debugging. Start the ToolKit and in the Main Menu select 19, 3 to reboot back to fastboot mode. Then you can BOOT into CWM Recovery without flashing it (9) and select backup/restore to backup your Rom/user data/boot image to a datestamped folder inside a folder called Clockworkmod on your Internal Storage. The rebooting into Android step after unlocking the Bootloader is important as cwm will not work properly without doing that.
Once that is all done you are ready to reboot into Android from cwm, get back to fastboot mode as before and select 1-click option (7). You will get a message on the unlock stage saying that your device is already unlocked but then it will just skip to the next stage. Be aware that when the device boots into Android the first time this is to let the user enable usb debugging for adb operations and if you have already done this then the ToolKit will wait for about 3 minutes before carrying on. Be patient as the ToolKit hasnt frozen, its just set to pause before carrying on.
Ok now thats all over with, on to your other questions lol. I would advise trying either romanbb's AOKP (build 24 should be up today) or bigxie's Apex 1.02 to start. Personally I use Apex as it has loads of customisation and runs very well but saying that I will be trying romanbb's new build when it is out.
Kernels are like the drivers of your phone. They set up how it works and what it can do. Custom Kernels can give better battery life and more power, performance, stability so its well worth trying them once you are rooted. They will tell you what builds they are compatable with but if you are thinking about the above Roms then you will be on Android build 4.0.3 and most new kernels work with that. I use franco's kernel but there are ALOT of established kernel developers working with the Nexus so you could try fugumod by nikademus or trinity by morfic. These are all flashed via cwm (download file, copy to Internal Memory, reboot to recovery mode once you have cwm flashed). You can enter cwm by rebooting to fastboot and using the volume buttons to select recovery, then press power to select, or from the reboot phone options in the ToolKit (19,4 in adb mode).
Bootloaders and Baseband/Radio updates are something to think about but not really needed if your phone is running fine. You wont notice any change if you update the bootloader as its just like updating your bios on a pc. Just gives some extra functionality or updates some deep down settings. Radios control the communication part of your phone and updating to a new one may improve battery, signal, wifi, gps lock. You can update them by either grabbing a premade zip and flashing via cwm or download the .img file and flash that via the ToolKit.
Dont worry about malware included in custom roms as long as its by an established developer. They would never put anything dangerous to the end user in one of their roms as it would harm their reputation and if anything was found by a user the rom would be taken down imediately by us mods to keep you safe.
I think thats everything you will ever need to know lol. Sorry theres alot I wanted to make sure you had all the ammunition you needed to continue and it took soo long to write I had lunch half way through
good luck.
Mark.
Ohhh man, thank you sooo much. That’s a lot of info and I really appreciate you taking the time to explain that to me Mark. Thank you!!!!
Ok, I’ve been watching some videos, one off of GalaxyNexusRoot.com. I think its his YouTube chan… He's seems pretty cool. Shows you what to do. I sort of want to do it manually so I'm understanding it all?, if that makes sense? I like to know exactly what my device is doing, why and how? haha. I'm a bit pedantic like that.
Arm, only a couple of things....I'm draining your life here...haha
I have a Samsung updated Gnex, throwing that in FYI. =) Not sure if the warranty centre would realise, probably so I should back it up as it is...on this note quickly, I do want to have a yakju (Google) updated phone though...hehe.
When I back up, does it flash everything? the rom, kernels and radios? (Mostly for my Stock setup for reversion, and understanding...)
With roms, where can I get the G'apps from? (If needed) And or the SupUser/Root files? (Separately I mean, so I can do this manually...if I'm understanding it properly... =/ )
Also, do these apps and others update as normal? Or di i have to update the whole ROM to update them? Like Maps (Navigation more importantly), GTalk, MarketPlace etc...?
And finally....phew...haha arm, sorry....
I'm looking at doing this because currently my device just seems a little non-responsive, laggy-ish and its turned off once.. =/ Is this all normal?? I thought for a minute my screen was faulty, like touches don’t always respond...I mean 90% of the time they do...I know, I'm nuts but it just ruins it for me... I uninstalled Beautiful Widgets and it’s sort of been better…maybe some apps aren’t configured with ICS yet also…I'm thinking it just could be the build? What do you think??
It's kind of weird to think that an individual dev has made. and is making more progress than the developers of the phone/software?? hahah...Anyway, I hope I've made some sense and I really, really, really appreciate all this Mark, all your time and patience with me. =)
Thanks again!!!!
P.S.... This should be it I SWEAR!! haha....
Just wanted to put these here...these are "some" of the problems I've been having... =/
http://forum.xda-developers.com/showthread.php?t=1500545
http://forum.xda-developers.com/showthread.php?t=1490335
http://forum.xda-developers.com/showthread.php?t=1500236
http://forum.xda-developers.com/showthread.php?t=1487946
Thank you...again!!!
I just want to thank the OP for asking the right questions and taking the time to figure out how "hack" his/her phone correctly instead of jumping in blind.
I hope other beginners follow the OP's lead.
That is all.
Sent from my Galaxy Nexus using xda premium
Helmet321 said:
Ohhh man, thank you sooo much. That’s a lot of info and I really appreciate you taking the time to explain that to me Mark. Thank you!!!!
Ok, I’ve been watching some videos, one off of GalaxyNexusRoot.com. I think its his YouTube chan… He's seems pretty cool. Shows you what to do. I sort of want to do it manually so I'm understanding it all?, if that makes sense? I like to know exactly what my device is doing, why and how? haha. I'm a bit pedantic like that.
Arm, only a couple of things....I'm draining your life here...haha
I have a Samsung updated Gnex, throwing that in FYI. =) Not sure if the warranty centre would realise, probably so I should back it up as it is...on this note quickly, I do want to have a yakju (Google) updated phone though...hehe.
When I back up, does it flash everything? the rom, kernels and radios? (Mostly for my Stock setup for reversion, and understanding...)
With roms, where can I get the G'apps from? (If needed) And or the SupUser/Root files? (Separately I mean, so I can do this manually...if I'm understanding it properly... =/ )
Also, do these apps and others update as normal? Or di i have to update the whole ROM to update them? Like Maps (Navigation more importantly), GTalk, MarketPlace etc...?
And finally....phew...haha arm, sorry....
I'm looking at doing this because currently my device just seems a little non-responsive, laggy-ish and its turned off once.. =/ Is this all normal?? I thought for a minute my screen was faulty, like touches don’t always respond...I mean 90% of the time they do...I know, I'm nuts but it just ruins it for me... I uninstalled Beautiful Widgets and it’s sort of been better…maybe some apps aren’t configured with ICS yet also…I'm thinking it just could be the build? What do you think??
It's kind of weird to think that an individual dev has made. and is making more progress than the developers of the phone/software?? hahah...Anyway, I hope I've made some sense and I really, really, really appreciate all this Mark, all your time and patience with me. =)
Thanks again!!!!
P.S.... This should be it I SWEAR!! haha....
Just wanted to put these here...these are "some" of the problems I've been having... =/
http://forum.xda-developers.com/showthread.php?t=1500545
http://forum.xda-developers.com/showthread.php?t=1490335
http://forum.xda-developers.com/showthread.php?t=1500236
http://forum.xda-developers.com/showthread.php?t=1487946
Thank you...again!!!
Click to expand...
Click to collapse
A cwm backup will back up system, data, boot, recovery and cache but it will not back up your radio image so check your version in the about phone screen first so you know what you need.
The latest gapps flashable zip can be found in the development forum. Did the youtube channel not give a link to the root files? If not then I have attached the 2 files you need to push. Make sure to set their permissions too after pushing.
Without knowing exactly what you have put on your phone its hard to comment about responsiveness but as stock roms dont have all the optimisations that custom roms have they are definitely slower. A custom rom and kernel will surely sort out your problems
Mark.
What does stock stand for?
udmbrian said:
What does stock stand for?
Click to expand...
Click to collapse
It means the version that the manufacturer put on the phone before it was shipped or a version that is supplied by the manufacturer. Unaltered by developers.
Mark.
mskip said:
A cwm backup will back up system, data, boot, recovery and cache but it will not back up your radio image so check your version in the about phone screen first so you know what you need.
The latest gapps flashable zip can be found in the development forum. Did the youtube channel not give a link to the root files? If not then I have attached the 2 files you need to push. Make sure to set their permissions too after pushing.
Without knowing exactly what you have put on your phone its hard to comment about responsiveness but as stock roms dont have all the optimisations that custom roms have they are definitely slower. A custom rom and kernel will surely sort out your problems
Mark.
Click to expand...
Click to collapse
Thanks again!!!!
Ok cool. So when new versions of the apps come out on the market, I wont be able to update them normally will I? Which is ok but just wondering how that is going to go down. Haha.
Lastly, sorry man, I'm almost there. Haha. CWM doesn't backup kernel? Like my stock one?
So it basically makes a "phone" image, ExtPartition and all? Or can you choose these options?
Right, I'm so close now I reckon, today will be the day... I can feel it!!! Haha.
Thank you again!!!!!!!!!
Sent from my Galaxy Nexus using XDA App
Helmet321 said:
Thanks again!!!!
Ok cool. So when new versions of the apps come out on the market, I wont be able to update them normally will I? Which is ok but just wondering how that is going to go down. Haha.
Lastly, sorry man, I'm almost there. Haha. CWM doesn't backup kernel? Like my stock one?
So it basically makes a "phone" image, ExtPartition and all? Or can you choose these options?
Right, I'm so close now I reckon, today will be the day... I can feel it!!! Haha.
Thank you again!!!!!!!!!
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Yes of course you can update google apps via the market as normal.
Cwm will back up your boot image which contains the kernel. So yes it does back up the kernel.
You can not choose which options to back up but you can choose which parts you want to restore via the advanced restore option in cwm.
Let me know how it all goes
Mark.
El Daddy said:
I just want to thank the OP for asking the right questions and taking the time to figure out how "hack" his/her phone correctly instead of jumping in blind.
I hope other beginners follow the OP's lead.
That is all.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Hey El Daddy,
Thanks man. I try to reframe from being a pain in butt.... not sure how I've gone with that but, Haha. I appreciate what your saying. I just want to be sure what I'm doing and to have, as Mark said, all the "ammo" I need.
Cheers.
Sent from my Galaxy Nexus using XDA App
Great questions and answers from both of you. Just got this phone and trying to figure out where to start. Briefly read the toolkit instructions. Just haven't had the time to sit down and plow through it. Thanks both of you.
mskip said:
A cwm backup will back up system, data, boot, recovery and cache but it will not back up your radio image so check your version in the about phone screen first so you know what you need.
The latest gapps flashable zip can be found in the development forum. Did the youtube channel not give a link to the root files? If not then I have attached the 2 files you need to push. Make sure to set their permissions too after pushing.
Without knowing exactly what you have put on your phone its hard to comment about responsiveness but as stock roms dont have all the optimisations that custom roms have they are definitely slower. A custom rom and kernel will surely sort out your problems
Mark.
Click to expand...
Click to collapse
Thanks so much again Mark...This is Great!!
Ok, just before I do this...I'm like right here at the PC...ready! haha...
I understand all of it now, well. in theory...
Thank you for the DL link to the root.zip...
I DL'd the android SDK Kit zip also, but there’s no fastboot.exe??? Or anything like what I need?? haha, I may just be missing something here...
One of you links on you manual guide is broken...I think, that’s where you had it...I didnt want to harass you again but just some final things. =)
I'm really after all of what I need to this manually...for knowledge etc?? Hope you understand... You made this wicked awesome Kit, and I'm stupid and not using it...hahah...
So as far as I can see, I need:
- Samsung Drivers - which I have and that bits done... =)
- fasboot.exe etc (Android SDK Gear)
- Latest CWM.zip
- **Rom of my choice, which I'm going to take your advice and go with Apex. =) Latest 1.02 yeah??
- Franco Kernel, I'll try stock, but my feeling on it is that that’s probably been my major issue, or the cause of most of them... =)
Phew....I think that’s it...am I on the right track??
I cant thank you enough with all this Mark....seriously...your a very patience man. haha
Cheers. =)
**Update**
P.S. I have attached a file. Mark can you check it out and see if that what I need in regards to Android SDK stuff? I just got this now after I posted the above....
Thanks again... =)
***Update...again....haha***
Arm, just looking at these files, whats the boot.img? does that get copied over to the phone? Or is it just a command? The su & Superuser files in this zip are like a different size and modified later than your ones (newer??? =/)....I'm not sure what that would really mean...probably has nothing to do with anything but just thought I'd check with you....
Helmet321 said:
Thanks so much again Mark...This is Great!!
Ok, just before I do this...I'm like right here at the PC...ready! haha...
I understand all of it now, well. in theory...
Thank you for the DL link to the root.zip...
I DL'd the android SDK Kit zip also, but there’s no fastboot.exe??? Or anything like what I need?? haha, I may just be missing something here...
One of you links on you manual guide is broken...I think, that’s where you had it...I didnt want to harass you again but just some final things. =)
I'm really after all of what I need to this manually...for knowledge etc?? Hope you understand... You made this wicked awesome Kit, and I'm stupid and not using it...hahah...
So as far as I can see, I need:
- Samsung Drivers - which I have and that bits done... =)
- fasboot.exe etc (Android SDK Gear)
- Latest CWM.zip
- **Rom of my choice, which I'm going to take your advice and go with Apex. =) Latest 1.02 yeah??
- Franco Kernel, I'll try stock, but my feeling on it is that that’s probably been my major issue, or the cause of most of them... =)
Phew....I think that’s it...am I on the right track??
I cant thank you enough with all this Mark....seriously...your a very patience man. haha
Cheers. =)
**Update**
P.S. I have attached a file. Mark can you check it out and see if that what I need in regards to Android SDK stuff? I just got this now after I posted the above....
Thanks again... =)
***Update...again....haha***
Arm, just looking at these files, whats the boot.img? does that get copied over to the phone? Or is it just a command? The su & Superuser files in this zip are like a different size and modified later than your ones (newer??? =/)....I'm not sure what that would really mean...probably has nothing to do with anything but just thought I'd check with you....
Click to expand...
Click to collapse
Looks like everything in that zip is ok for what you want to do. The superuser.apk is a different size but im sure it doesnt matter.
In order to push the 2 files across to your phone you need to have booted into Android using an insecure boot image. This is a stock boot.img that has has some simple text changes to allow temporary root access (otherwise the files wouldnt copy across) Using fastboot you boot the boot.img file and then once you are in Android you push the files across and set their permissions. When you reboot your phone your original boot image will be used and you should have permanent root via the files.
Looks like you are all set
MArk.
Oh ok. So it doesn't stay on the phone?, its temporary??
So if this file say, is corrupted or malicious, (not really possible probably byt...) I'm in trouble? haha
Sorry, I have everything I think now, I grabbed the SDK of the Android website and I'm comfortable with that cause its "legit" I suppose. It doesn't have a boot.img file though. Can I make one myself so I know where its coming from? And where does this normally come from?
Silly stuff I know but, I told you, I'm CRAZY!! haha....
One very last thing...the permissions, whats that part all about...
Other than that, I'm pretty sure I'm sweet now...I also grabbed the latest CWM zip off the website too...so I'm cool with that.
......geez.... I'm killing you aren't I....I think you deserve (need) at LEAST 1 beer after all this....haha...
Thanks x 1,000,000...seriously.... =)
Helmet321 said:
Oh ok. So it doesn't stay on the phone?, its temporary??
So if this file say, is corrupted or malicious, (not really possible probably byt...) I'm in trouble? haha
Sorry, I have everything I think now, I grabbed the SDK of the Android website and I'm comfortable with that cause its "legit" I suppose. It doesn't have a boot.img file though. Can I make one myself so I know where its coming from? And where does this normally come from?
Silly stuff I know but, I told you, I'm CRAZY!! haha....
One very last thing...the permissions, whats that part all about...
Other than that, I'm pretty sure I'm sweet now...I also grabbed the latest CWM zip off the website too...so I'm cool with that.
......geez.... I'm killing you aren't I....I think you deserve (need) at LEAST 1 beer after all this....haha...
Thanks x 1,000,000...seriously.... =)
Click to expand...
Click to collapse
Its perfectly possible to make your own boot image but to be honest you might take another day or 2 to get all the required components and research what you need to do lol
If you go to your settings, about phone screen and tell me the build version (4.0.1, 4.0.2) and whether its a gsm or lte device (im assuming gsm as lte is america/canada) then I will attach the boot image I made for that device so it will definitely be right and safe. You can also use the su and superuser.apk files I attached earlier if you are unsure about them.
I dont mind all the questions as long as you end up feeling confident enough to get your phone rooted mate I would rather people ask too many (but the right) questions than just go blindly into something have no understanding about and end up in trouble.
Mark.
Your a legend Mark, I swear!!....haha
Ok, well, its a GSM, 4.0.2 Samsung updated Nexus....I think... I can attach some images. =)
The end of the line here...haha, arm, I just watched a video that completely skipped the boot.img part...weird...anyway, with the "su" part, I have 2 files there, as you've kindly provided, but in that step doesnt it need to be a su.zip sort of configuration? Just running it by you before I do this...
P.S....again....haha, arm, if I'm thinking about this right, does the step with "fastboot boot boot.img" will that affect the stock image?? As I think, if I'm right you have to do that "before" you flash your recovery?? In my mind would it be right in assuming....
-Unlock bootloader
-Flash recovery
-Make a Back up (so to get all the rom, including the auto restore recovery??)
-Set SU perms...with su.zip or su+superuser.apk... (if I'm right also, this step only if you want root perms on stock?, not sure what you would do with it though, only if you want to remain this way I suppose... =/ )
Is this right??
I was reading your "manual" post and I'm a little confused...as in, you cant reboot into Android after flashing recovery (to back up) as it will delete it, but to do so, you need to reboot into Android to delete the auto recovery flash file?? And you need su perms yeah?? Am I right here, I'm probably going crazy-ier...haha cause I've been at this for 2 days...haha...
Seems the boot.img step is the same as if you would flash a su.zip...(which I dont have, only the su file (no extension) and the su.apk...) not sure if thats the same...just getting my head around it here.... =)
Maybe I'm thinking CWM will "back up" the su perms etc and affect the "stock rom"...if you back it up with the perms, wouldnt that be included?? Maybe thats were I'm getting it wrong...haha.
Finally...........serious.....
If and when you delete the auto recovery file (if that really does delete it completly, I'm probably wrong about that too...) how does it restore??
Thanks mate. =)=)
I think thats it...when I have my head around these final things...and the last couple of files...Its time.... =)=)
Helmet321 said:
Your a legend Mark, I swear!!....haha
Ok, well, its a GSM, 4.0.2 Samsung updated Nexus....I think... I can attach some images. =)
The end of the line here...haha, arm, I just watched a video that completely skipped the boot.img part...weird...anyway, with the "su" part, I have 2 files there, as you've kindly provided, but in that step doesnt it need to be a su.zip sort of configuration? Just running it by you before I do this...
P.S....again....haha, arm, if I'm thinking about this right, does the step with "fastboot boot boot.img" will that affect the stock image?? As I think, if I'm right you have to do that "before" you flash your recovery?? In my mind would it be right in assuming....
-Unlock bootloader
-Flash recovery
-Make a Back up
-Set SU perms...with su.zip or su+superuser.apk...
Is this right??
I was reading your "manual" post and I'm a little confused...as in, you cant reboot into Android after flashing recovery (to back up) as it will delete it, but to do so, you need to reboot into Android to delete the auto recovery flash file?? And you need su perms yeah?? Am I right here, I'm probably going crazy-ier...haha cause I've been at this for 2 days...haha...
Seems the boot.img step is the same as if you would flash a su.zip...(which I dont have, only the su file (no extension) and the su.apk...) not sure if thats the same...just getting my head around it here.... =)
Maybe I'm thinking CWM will "back up" the su perms etc and affect the "stock rom"...if you back it up with the perms, wouldnt that be included?? Maybe thats were I'm getting it wrong...haha.
Finally...........serious.....
If and when you delete the auto recovery file (if that really does delete it completly, I'm probably wrong about that too...) how does it restore??
Thanks mate. =)=)
I think thats it...when I have my head around these final things...and the last couple of files...Its time.... =)=)
Click to expand...
Click to collapse
There are 2 ways of rooting your phone. The easier (and non learning way) is to flash cwm recovery and flash the superuser.zip straight to the phone. If this is what you watched then tbh you might as well be using my ToolKit as you wont learn anything from the experience. The other way is the method my ToolKit uses which is to boot the phone with the insecure boot image to gain temporary root, then using adb to push the 2 files that I sent to your phone and set their permissions, then rebooting to complete the root procedure. The 2nd method is the one I thought you was gearing up towards and the best way if you want to actually learn something, otherwise as I said you may as well use the ToolKit.
I have attached every file you will need for the 2nd method and if yo uread below these are the instructions you will need to follow to root your phone. Extract the attached files to a folder on your pc, browse to this folder then HOLD the Shift button on your pc while right clicking on a blank area of the Windows Explorer. Select 'Open command window here' which will open a command prompt in the correct folder where your adb and fastboot files are.
These instructions are for after you have installed drivers:
fastboot-toolkit devices
Click to expand...
Click to collapse
this will return a serial number if your drivers are installed.
fastboot-toolkit oem unlock
Click to expand...
Click to collapse
and follow the instructions on the phone to unlock your bootloader.
Now if you boot into Android RIGHT after unlocking the bootloader it will restart the boot half way through so you want to do this normally BEFORE using your insecure boot or the reboot half way through will lose your insecure access (if you get me)
fastboot-toolkit reboot
Click to expand...
Click to collapse
to get your first boot in. Once the phone has booted up and you have gone through the setup wizard, go to settings, developer tools and select 'usb debugging' to enable adb control.
adb-toolkit devices
Click to expand...
Click to collapse
should return a serial number if your adb drivers are installed.
adb-toolkit reboot bootloader
Click to expand...
Click to collapse
to get back into fastboot so you can boot from the insecure boot image
fastboot-toolkit boot boot_gsm_ICL53F_insecure.img
Click to expand...
Click to collapse
to boot your phone into Android from the insecrure boot image. Once your phone has booted into the lockscreen you can carry on with
adb-toolkit root
adb-toolkit remount
Click to expand...
Click to collapse
to mount your /system folder for root access.
adb-toolkit push su /system/bin
adb-toolkit push Superuser.apk /system/app
Click to expand...
Click to collapse
pushes the 2 files across to the correct folders on your phone.
adb-toolkit shell chmod 06755 /system/bin/su
adb-toolkit shell chmod 06755 /system/app/Superuser.apk
Click to expand...
Click to collapse
sets their correct permissions.
Lastly if you are flashing cwm then you will need to rename the recovery restore file if you are on a samsung rom. If this file is present on your phone and cwm is flashed, then on the next reboot the stock recovery will be restored and you will lose cwm. To get back to stock recovery in the future you just flash a stock recovery image.
adb-toolkit shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p-old
Click to expand...
Click to collapse
will rename the file is it is present.
Thats it! Reboot your phone and you should have root You can check this by downloading root checker from the market or just download a root app such as adfree or setcpu.
Mark.
I see you are replying to my thread already as I was making some changes so re-read the instructions as I rearranged them a bit to make more sense lol.
MArk.

[Q] Unknown problems with my wildfire

Hi everybody. I canot understand what's happening with my phone.It was rooted using revolutionary method. A half of a year everything was fine,then it begins....once I have installed a rom,and when I was changing maybe the kernel or just installing a script,the rom stucks on bootscreen and i couldn't even restore it from backup.. other case I changed once my recovery from 5.0 to 2.5 and when i decided to install back 5.0 i couldn't because none of the known methods helped me....today i tryed to nandroid my current rom(rempuzle) and it was written that it couldn't find the folder android secure(even if the folder exist) and i can't nandroid,after rebooting,my phone couldn't even find my sd card and i couldn't use my apps,now i saved the most important things from my sd and i want to ask you for advice....I am not sure but i still suppose that it could be a bad rooting process or something happened untill i use my phone,what can i do,i thought about restoring my phone to it's original state(cancelling root) and then root it again with another method or there is another logical explication to this issues? pls help.
anyone?
Presumably you can still get in to hboot. If so connect the phone to your pc and put the phone in fastboot USB mode then run a RUU to restore the phone back to stock. You can then start the rooting process again if you so desire.
hans moleman said:
Presumably you can still get in to hboot. If so connect the phone to your pc and put the phone in fastboot USB mode then run a RUU to restore the phone back to stock. You can then start the rooting process again if you so desire.
Click to expand...
Click to collapse
I want to root my phone again,but I want to know if this method will solve my problem :s I want to know if it's worth it...
dreamkill3r said:
Hi everybody. I canot understand what's happening with my phone.It was rooted using revolutionary method. A half of a year everything was fine,then it begins....once I have installed a rom,and when I was changing maybe the kernel or just installing a script,the rom stucks on bootscreen and i couldn't even restore it from backup.. other case I changed once my recovery from 5.0 to 2.5 and when i decided to install back 5.0 i couldn't because none of the known methods helped me....today i tryed to nandroid my current rom(rempuzle) and it was written that it couldn't find the folder android secure(even if the folder exist) and i can't nandroid,after rebooting,my phone couldn't even find my sd card and i couldn't use my apps,now i saved the most important things from my sd and i want to ask you for advice....I am not sure but i still suppose that it could be a bad rooting process or something happened untill i use my phone,what can i do,i thought about restoring my phone to it's original state(cancelling root) and then root it again with another method or there is another logical explication to this issues? pls help.
Click to expand...
Click to collapse
I'm not sure - just guessing - but do you have the possibility to use a different sdcard? Or do a complete format (you said you already did a backup) of the sdcard and apply the stuff you need again (apps, ext partition?). In case the card got corrupted a nandroid restore might not help there.
But like I said: just guessing...
You're s-on - right?
eventcom said:
You're s-on - right?
Click to expand...
Click to collapse
right,but I don't understand why I can't do a nandroid I am waiting nearly a half of an hour and at the end it's not done properly,it's corrupted :S
dreamkill3r said:
right,but I don't understand why I can't do a nandroid I am waiting nearly a half of an hour and at the end it's not done properly,it's corrupted :S
Click to expand...
Click to collapse
yep that's what I'm thinking. Due to the fact that the android secure folder resides on the sdcard (FAT32) it could be the card (and you can't do partial nandroid...) - but again: just guessing.
ok,I will try
oh yes,btw I don't know if it's important but for me the PC36IMG method never worked....can the sd be the problem here?
I changed the sd and i have done a nandroid(instead of waiting 1 h i waited 10 mins) but the same result Error while making a backup image of /sdcard/.android_secure ! (((
dreamkill3r said:
I changed the sd and i have done a nandroid(instead of waiting 1 h i waited 10 mins) but the same result Error while making a backup image of /sdcard/.android_secure ! (((
Click to expand...
Click to collapse
It might be some minor problem that could be solved easier, no idea, you could either remove your apps and their data one by one, check your filesystem if you see something suspicious or wait if someone has a better idea. If you don't want to waste too much time with that I'd suggest you make a full backup of your apps (e.g. with titanium backup), check if contacts, calendar & stuff is synced with google, do a full wipe/factory reset and reflash the ROM.
What ROM are you using at the moment?
dreamkill3r said:
the PC36IMG method never worked....can the sd be the problem here?
Click to expand...
Click to collapse
I hope you are aware of these things :
>Make sure you don't rename the file "PC49IMG.zip.zip"(Windows hides known file extensions by default)
>Drop the zip file on the root of the SD Card
>Boot to BOOTLOADER and select yes to update
Try different SD card and/or SD card adapter.
PC36IMG.zip!!!!! dont you mean PC49IMG.zip???
R.V.3
slymobi said:
PC36IMG.zip!!!!! dont you mean PC49IMG.zip???R.V.3
Click to expand...
Click to collapse
Oops,sorry,my mistake!!
Yep,that's PC49IMG.zip file of the recovery.
optimusodd said:
Oops,sorry,my mistake!!
Yep,that's PC49IMG.zip file of the recovery.
Click to expand...
Click to collapse
hopefully dreamkill3r is also aware of that
I used rempuzle
now I installed a cm based rom and I hope that I will not have problems with it
about the PC49IMG.zip problem,I used a tutorial for flashing roms with this method.so my phone couldn't find this file and ofc it was located at the root of my sd.....but now whe I enter in bootloader,it was written that the system is looking for another file,not PC49IMG.zip but i can't remember the name,can it be a different filename for my phone?
O_O omg,now i rebooted my phone in bootloader to try to read the name of the file and now my phone got stuck on bootscreen....it's done again.......what can i do,i want finally a cm7(i think) based rom maybe with the interface changed(sometimes i dislike the standart look) wich i can use more then a month at least,tu have the best kernel for it and if it's necessary a normal radio version,to not see those troubles again...I don't want to change this phone,but I hate when I nedd to flash a new rom every half of a month and meet those problems again....help pls) or again my interesting question,can a restore and rooting again process solve these problems?
dreamkill3r said:
can it be a different filename for my phone
Click to expand...
Click to collapse
Nope,It always checks for PC49DIAG.ZIP and PC49IMG.ZIP files.
I hate when I nedd to flash a new rom every half of a month and meet those problems again.
Click to expand...
Click to collapse
LOL,Why do you need to flash a new ROM every 15 days ?
can a restore and rooting again process solve these problems?
Click to expand...
Click to collapse
What is your HBOOT version ?
I think you need to flash the stock ROM then S-OFF and Re-root the phone.
Take a complete backup of your data as eventcom suggested and follow this guide.
optimusodd said:
LOL,Why do you need to flash a new ROM every 15 days ?
Click to expand...
Click to collapse
because it's crashing every 15 days lol,because it become laggy etc
my hboot version is 6.01.1002
dreamkill3r said:
my hboot version is 6.01.1002
Click to expand...
Click to collapse
Are you S-ON ?
optimusodd said:
Are you S-ON ?
Click to expand...
Click to collapse
S-OFF

Categories

Resources