Related
I've seen a couple threads that Clockwork is wiping Wimax on newer phones or hboot? Can someone please explain the problem to me so I can fix it and Unrevoked works again?
Koush said:
I've seen a couple threads that Clockwork is wiping Wimax on newer phones or hboot? Can someone please explain the problem to me so I can fix it and Unrevoked works again?
Click to expand...
Click to collapse
Hi Koush, I'm sure someone else can chime in on the specifics of unrevoked with the new hboot.. as far as I know unrevoked just doesn't work on hboot 2.02 yet.
As a slight aside if you're going to be updating CWM, the two main issues with clockwork right now IMO are:
1) Wimax partition is not backed up when you do a nandroid
2) Seems to be some inconsistencies with wiping dalvik and possible cache
Hope those things can be fixed so that we can go back to using CWM!
I also noticed yesterday that CWR says signatures are invalid that ARR verifies without any trouble.
posguy99 said:
I also noticed yesterday that CWR says signatures are invalid that ARR verifies without any trouble.
Click to expand...
Click to collapse
You can turn off signature checking in CWR. ARR is using the old Cupcake/Donut sig checking which has a few security bugs in it.
bump... 10chars
I have had the problem, I am not able to use 4g any more since last update I did with Clockworkmod.
Let me know what you would like me to do to help you out.
The only changes I need done to Clockwork recovery is to get some sort of confirmation with wiping dalvik cache and battery stat.
I like Clockwork the way it is as far as not touching with Wimax at all. I have more problem with 4g connecting when restoring nandroid with other recovery that suppose to backup wimax partition.
I have never had a problem with my 4G once I go back to Clockwork recovery. Easy way for me to fixed my 4G again was to repeat Toast method number 2 and just use Clockwork recovery that don't touch the wimax.
Koush said:
I've seen a couple threads that Clockwork is wiping Wimax on newer phones or hboot? Can someone please explain the problem to me so I can fix it and Unrevoked works again?
Click to expand...
Click to collapse
Koush....
As one of the devs that actully helped find the issues I will point you to the thread that discusses the problem
http://forum.xda-developers.com/showthread.php?t=843342
However it will not fix unrevoked not working on the new evos. But It would be nice to have recovery options again.
thanks for your help...
Another issue is apparently that the wimax secure keys are not backed up in the CW nandroid. So if something goes awry you cannot restore them. Apparently the alternative recovery does backup the keys.
Sent from my PC36100 using Tapatalk
Koush said:
I've seen a couple threads that Clockwork is wiping Wimax on newer phones or hboot? Can someone please explain the problem to me so I can fix it and Unrevoked works again?
Click to expand...
Click to collapse
Anything in the works? Just curious...
Koush - this isn't related to the 4G - but it's been an ongoing problem that we have with wiping dalvik and cache. I have physically checked via ADB after choosing to wipe dalvik (/data/dalvik-cache) and it's still there. After a few times of wiping it finally works.
The issue seems to be that with new hboots (2.02/2.10) on the Evo that partition information has changed.
I'm still running cwm though and for me it's OK, I'm on hw v003, hboot 2.10 - I think the issue might be with 004 models.
thefredelement said:
The issue seems to be that with new hboots (2.02/2.10) on the Evo that partition information has changed.
I'm still running cwm though and for me it's OK, I'm on hw v003, hboot 2.10 - I think the issue might be with 004 models.
Click to expand...
Click to collapse
+1 it is the partitions, not all new phones come with the new partition set up though. The new hboots are backward compatible but you can't use the new phones with the old hboots.
Swapping out the kernel with the new recoveries kernel should do the trick (i think)
Sent from my PC36100 using XDA App
Miss using CWM, so I'm hoping this gets resolved soon!
http://pastebin.chiznillen.net//view.php?id=19
Koush that's from my hboot 2.10 Evo.
This is from a .97 hboot:
http://pastebin.chiznillen.net//view.php?id=20
Cheers.
Here's a post with partition info from newer Evos (late hardware version 003 and 004 that came with hboot 2.02+)
http://forum.xda-developers.com/showthread.php?t=883636
I've not run into the cache wiping issues but then I have an older EVO so I may just be hardware blessed.
The only concern for me is the 4G RSA keys. I like that generally it's not touched, but an advanced option for the occasional backup would be very welcome (especially with a beta WIMAX in CM6 just around the corner).
Justin.G11 said:
I've not run into the cache wiping issues but then I have an older EVO so I may just be hardware blessed.
The only concern for me is the 4G RSA keys. I like that generally it's not touched, but an advanced option for the occasional backup would be very welcome (especially with a beta WIMAX in CM6 just around the corner).
Click to expand...
Click to collapse
for this I hopped over to RA and just did a nandroid and saved the wimax image on my computer then gmailed it to myself.
thefredelement said:
for this I hopped over to RA and just did a nandroid and saved the wimax image on my computer then gmailed it to myself.
Click to expand...
Click to collapse
Smart option!!
although adding it to clockwork would still be awesome.
leenypost said:
Smart option!!
although adding it to clockwork would still be awesome.
Click to expand...
Click to collapse
I agree, I think primarily though cwm has to be setup for the new partitions on 003/004 phones that shipped with hboot 2.02+.
Sorry if this should be in a different thread. Not trying to get flamed. So I am coming from a captivate and am just wondering how is flashing stuff on the inspire different from the captivate? Typically most of my flashing was just done thru CWM on the captivate itself or thru ODIN. I know ODIN doesnt exist for the inspire, but what differences can I expect coming into? how do I get to recovery or download? Any answers on how the flashing experience is different would be much appreciated
Once you've rooted it's pretty much the same as captivate install rom manager and install Rom with cwm recovery. There isn't a need to flash back to stock. Just clear data and cache.
Sent from my Desire HD using Tapatalk
yup, clockwork mod makes life a hell of a lot easier.
And this restore a heck of a lot better than the captivate did. I don't even use titanium backup anymore. All my txt messages and apps automatically restores including wallpaper
Sent from my Desire HD using Tapatalk
Thanks guys, my only question is how to get CWM on this phone after root. Im assuming its thru a kernel?
same way you do it on the captivate get rom manager from the market. Install CWM Recovery.
There's no need for special recoveries like on the captivate as there's no lagfix craziness to deal with. HTC uses Android/Linux standard file systems
gunnyman said:
same way you do it on the captivate get rom manager from the market. Install CWM Recovery.
There's no need for special recoveries like on the captivate as there's no lagfix craziness to deal with. HTC uses Android/Linux standard file systems
Click to expand...
Click to collapse
Lol, kinda forgot thats all that needed to be done to get CWM. Too much stress with the captivate.
Yeah I had to retrain my brain as well.
p4ranoid4ndroid said:
Lol, kinda forgot thats all that needed to be done to get CWM. Too much stress with the captivate.
Click to expand...
Click to collapse
Totally agree, ill never get samsung again. I would probably flash a different rom on my captivate every other day to find out which one had what bugs and what didnt work correctly, lol. The Inspire is a lot harder to root then the captivate, but is well worth it when you do, for one roms are higher quality and all 100% working, even cm7 rc1. There is no download mode for inspire, you can manually boot into bootloader mode and from there you can enter CWM Recovery.
So i looked at the HTC hack kit, are there any better instructions for rooting? just didnt see anything laid out in that thread.
Another question for yall: On the captivate when wifi was active the 3g symbol would disappear. This doesnt happen on my inspire. Does that mean hspa is still running while im connected to wifi? Battery drain is my issue with this
there's a readme in the hack kit. Very easy to follow
There is youtube two part video walkthrough, thats what i used. I learn easier if i can see it happening.
Sent from Inspire 4G using XDA App
On the vibrant (captivate) a bad kernel or Rom could mean boot loop and no hope of getting into clockwork and we would have to use odin. This doesn't happen on the inspire?
Sent from my Inspire '4g'.
ive had boot loop happen twice so far and both times i manually went into boot loader and went to CWM recovery and wiped data and reflashed then everything was fine. The one time i reflashed and still got boot loop i just restored back up and then flashed and was good to go. I made a backup right after i rooted so i wouldnt have to do it again, i suggest you do the same just to be safe.
bkeaver said:
And this restore a heck of a lot better than the captivate did. I don't even use titanium backup anymore. All my txt messages and apps automatically restores including wallpaper
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Not to hijack, but what do you mean? How do you restore all your apps etc without titanium?
Corriewf said:
Not to hijack, but what do you mean? How do you restore all your apps etc without titanium?
Click to expand...
Click to collapse
lol dont mind the hijacking. the more questions asked the better.
the market auto restores your apps when you sign in with your google account, i cant really explain how it does this, but it sure is nice.
when you check back up my settings when you sign into google for teh first time, it starts keeping a list of market apps you've installed and restores them if you do a factory reset. doesn't seem to catch all of mine all the time though.
still have some questions regarding Flash
I read the rooting thread as well as saw the video, what I could understand is that in captivate we were rooting and then upgrading the ROM.
But here we are rooting and the downgrading.. Are we loosing any functionality? Its little difficult to understand..
can someone pls help?
You are actually downgrading the ROM then rooting THAT. After you have root, and have clockwork mod recovery installed you can install any rooted rom you like. There are a few to choose from in the Dev section.
The current Android release on the Inspire hasn't been "cracked" yet so you need to downgrade to get root.
I am coming from Evo 4G & early on there was a problem with clockwork recovery & wimax & a lot of people lost their RSA keys because of clockwork. I am just wondering if I risk losing my RSA keys if I restore to my nandroid of my rooted stock Rom. Is 4G different on the NS4G then on Evo? I am scared to restore, but I really want to until CM7 is more polished for the NS4G.
If you don't know the answer please tell me if you have restored a nandroid using Clockwork recovery on the NS4G and then connected to 4G afterward. This would ease my mind before restoring. I guess I could just flash a stock rooted Rom and wait for the AmonRA port to be finished.
Sent from my Nexus S 4G using XDA Premium App
Please answer if you know or if you have restored without losing 4G. Thanks in advance.
housry23 said:
Please answer if you know or if you have restored without losing 4G. Thanks in advance.
Click to expand...
Click to collapse
i have done many cwm restores and my 4g still works. i dont know anything about rsa keys, but mine is still working.
I do not know the answer to your question because I have the T-Mobile version but I used to have an Evo on Sprint so I am familiar with backing up WiMax being necessary due to RSA Keys stored in the WiMax image.
This thread should let you make a standalone WiMax img backup:
http://forum.xda-developers.com/showthread.php?t=1074584&highlight=wimax
The resulting image you can keep and can be flashed to your WiMax partition in case anything ever goes wrong in that regard.
Thanks matt2053. Went to thread and made a backup. This is exactly what I was looking for. Much appreciated. I am sure Clockwork has fixed this issue, but I always like to be on the safe side.
GT- P6210
So i used Chainfires apk to check to see if i'm in danger of the hard brick bug.
And it has said I'm at risk!, so i have ICS on my tab but am too scared to use it!
What are my options?
Should i just keep on using it and keep my fingers crossed?
My Noob guess is to go back to Honeycombe?
(download honeycomb rom tar, and flash via Odin?)
@riverboat2001
please check this thread. thanks.
http://forum.xda-developers.com/showthread.php?t=1818638
and also this link.
http://forum.xda-developers.com/showthread.php?p=27074278
aperture said:
@riverboat2001
please check this thread. thanks.
http://forum.xda-developers.com/showthread.php?t=1818638
and also this link.
http://forum.xda-developers.com/showthread.php?p=27074278
Click to expand...
Click to collapse
Hi, thanks for replying, i had already read that first post, but it doesn't seem to have an outcome.
As for the second one is it still relevant information if it's for the N7000?
The guy is saying avoid Samsung ROM's completely, what rom should i be using then?
Lastly do you know if it's safe to do a wipe/reset from within CWM ?
Cheers
riverboat2001 said:
Hi, thanks for replying, i had already read that first post, but it doesn't seem to have an outcome.
As for the second one is it still relevant information if it's for the N7000?
The guy is saying avoid Samsung ROM's completely, what rom should i be using then?
Lastly do you know if it's safe to do a wipe/reset from within CWM ?
Cheers
Click to expand...
Click to collapse
As long as you are using cm, I don't think it will be a problem. I will never go back to official. The problem stems from an issue with the stock recovery from Samsung. So in short, the devs are aware of the issue, but Samsung doesn't seem to care. As long as you are running the current cwm, and the dev isn't an idiot, you shouldn't have a problem. (No offense aorth and locerra, I know you're aware)
Sent from my Galaxy Tab 7 Plus
riverboat2001 said:
GT- P6210
So i used Chainfires apk to check to see if i'm in danger of the hard brick bug.
And it has said I'm at risk!, so i have ICS on my tab but am too scared to use it!
What are my options?
Should i just keep on using it and keep my fingers crossed?
My Noob guess is to go back to Honeycombe?
(download honeycomb rom tar, and flash via Odin?)
Click to expand...
Click to collapse
the thing is, if you go into recovery mode (hold power and volume up during boot) and then you see something like "recovery 3e" on the screen. THEN you have a problem.. it means you are on stock ICS with the stock Recovery and IF you do the "factory reset/wipe" in that recovery mode. your TAB is a goner..
then you get a linux system, get heimdall go to this thread
http://forum.xda-developers.com/showthread.php?t=1785862
and follow all instructions untill you have a non-stock (no 3e) recovery on your tab.
then your tab (*as far as other people say) is safe. then you can wipe/flash/backup and do whatever you want with a relatively (lower) risk than before..
wingie6200 said:
the thing is, if you go into recovery mode (hold power and volume up during boot) and then you see something like "recovery 3e" on the screen. THEN you have a problem.. it means you are on stock ICS with the stock Recovery and IF you do the "factory reset/wipe" in that recovery mode. your TAB is a goner..
then you get a linux system, get heimdall go to this thread
http://forum.xda-developers.com/showthread.php?t=1785862
and follow all instructions untill you have a non-stock (no 3e) recovery on your tab.
then your tab (*as far as other people say) is safe. then you can wipe/flash/backup and do whatever you want with a relatively (lower) risk than before..
Click to expand...
Click to collapse
Wow, thanks so much for taking the time to offer your advice.
I only have myself to blame for getting into this pickle! After Flashing so many different ROM's on loads of devices i just got a bit blaiz'e
Last night i did a wipe and factory reset through CWM and it all went well, so my question is, giving that i know i'm at risk, i can see three options,which is the "safest"
1/ Put tab away and don't use it until Samsung release a fix we can use
2/ Keep using the tab, but have that worrying niggle in the back of my mind
3/ Follow the post above and carry out the suggested procedure outlined above? (is it 1000% safe?
Can i assume that if i go as far as recovery mode via the ICS version to see the "recovery 3e" but don't wipe/factory reset i'm safe?
And consequently if i DON'T see that i would be safe to go ahead?
I do feel as if I'm sitting on a time-bomb here
(years ago i would have spent weeks messing around with this sort of thing, but as a middle aged housewife thats always on the go, i don't have the time, I just like to get my stuff working fast and bloatware free and i'm happy!)
Once again thanks for your input.
lol cant guarantee the 1000% safe part (since the offending code is in part coming from samsung) but people are aware of it / working to fix it and all non stock stuff is most probably safe. the CWM 6.0.1.0 definitely is, just used it myself.
and these things are kinda random (if all posts are to be believed) so i would just use the tab normally and worry about it much.. reports also say that samsung does repair these bricked tabs under warranty in case the unthinkable does happen.
and its not a time bomb :laugh:! (although there would probably be an app for that somewhere..)
I think the issue is only with the ics 3e recovery, not the hc one. Clockwork is fine, at least the newest one, not sure about the one Gary posted
Sent from my myTouch 4g via Tapatalk
ringnutz said:
I think the issue is only with the ics 3e recovery, not the hc one. Clockwork is fine, at least the newest one, not sure about the one Gary posted
Sent from my myTouch 4g via Tapatalk
Click to expand...
Click to collapse
What exactly trigger the brick bug? I already use the ICS stock recovery to do a wipe/factory reset your for my tab a couple of times and all was fine. I just was lucky? I have the second ICS update for the GT-P6210. Is this model affected? I mean, is someone with this model already trigger the brick bug?
Sorry for so many questions, thanks.
Kuniokun said:
What exactly trigger the brick bug? I already use the ICS stock recovery to do a wipe/factory reset your for my tab a couple of times and all was fine. I just was lucky? I have the second ICS update for the GT-P6210. Is this model affected? I mean, is someone with this model already trigger the brick bug?
Sorry for so many questions, thanks.
Click to expand...
Click to collapse
Yeah, I did.. happened the first time
Sent from my myTouch 4g via Tapatalk
Brickbug is caused by ****ty flashing firmware on some of our devices.
No danger with cwm 6.0.1.0 from aorth. We r safe!
Sent from my GT-P6200 using xda app-developers app
I bought this phone off ebay and I got two batteries. I am wondering if it is just me butt the seller said the battery was a month old and this thing won't last 3 hours off normal continuous use.and sometimes it just shuts off without giveing me a battery message, of any kind (when im doing something battery intensive)
Also before I knew about the chip issues I flashed and all.I used the method on unlockr.com and when I reached the part to get s off the root.sh wouldn't give me s off so some where in the comments I found a g free script ran it in the terminal emulater in the placer of root.sh and then returned to unlocker and continued to flash with visionary.apk and all is well. Flashed a few roms but im itching to flash like hell as that's, what I'm use to, so is it a case where the chip gets worse everytime I flash or can it go any time? Does it have to go?
I have read the posts and just need a little more clarity.
RUDE COMMENTS ARE NOT WELCOMED
sent from my doomed chip HTC glacier or mytouch 4g
xanda143 said:
I bought this phone off ebay and I got two batteries. I am wondering if it is just me butt the seller said the battery was a month old and this thing won't last 3 hours off normal continuous use.and sometimes it just shuts off without giveing me a battery message, of any kind (when im doing something battery intensive)
Also before I knew about the chip issues I flashed and all.I used the method on unlockr.com and when I reached the part to get s off the root.sh wouldn't give me s off so some where in the comments I found a g free script ran it in the terminal emulater in the placer of root.sh and then returned to unlocker and continued to flash with visionary.apk and all is well. Flashed a few roms but im itching to flash like hell as that's, what I'm use to, so is it a case where the chip gets worse everytime I flash or can it go any time? Does it have to go?
I have read the posts and just need a little more clarity.
RUDE COMMENTS ARE NOT WELCOMED
sent from my doomed chip HTC glacier or mytouch 4g
Click to expand...
Click to collapse
If the chip dies there will be likely be no warning. It will simply fail. Most don't. There are a lot of us with the "bad" eMMC that have flashed hundreds or even thousands of times.
I would flash a new ROM and compare battery life and behavior.
estallings15 said:
If the chip dies there will be likely be no warning. It will simply fail. Most don't. There are a lot of us with the "bad" eMMC that have flashed hundreds or even thousands of times.
I would flash a new ROM and compare battery life and behavior.
Click to expand...
Click to collapse
Ok I'm feeling a but more comfy now.and obviously I won't blame you should something go wrong. Thanks.makes no sense living in fear might as well enjoy it while it lasts
sent from my doomed chip HTC glacier or mytouch 4g
xanda143 said:
Ok I'm feeling a but more comfy now.and obviously I won't blame you should something go wrong. Thanks.makes no sense living in fear might as well enjoy it while it lasts
sent from my doomed chip HTC glacier or mytouch 4g
Click to expand...
Click to collapse
If your on stock battery will probably suck. It did for me
Sent from my HTC myTouch 4g using xda app-developers app
N_otori0us_ said:
If your on stock battery will probably suck. It did for me
Sent from my HTC myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
yeah i notied the huge diffrence when i switched to the viper rom........haveing a little trouble finding a compatible kernel that will give me smartass v2 tho.
quick question does a nandroid backup also backup the kernel that i was on when i made the backup?
crap i made a mistake and flashed a wrong kernel(fusion dragon and now the phone dosnt want to boot into recovery). i think the kernel was for the one S i didnt notice that. Anyway i know androids so am not worried about anything except my emmc chip can anyone give me the fastbood instructions to flash the various things on the glacier or are they the same for all phones also. a kernel that i can flash the will work with this viper rom would be nice.
i was trying fastboot flash zip rom.zip and that fails.
was really trying to avoid haveing to flash a PDM15.img but it as that would erase my ext4 recovery which i figure isnt working because the kernel i flashed was not for the phone and being touch based is messed up. so anyone knoe the fastboot commands to flash a rom in its zip form
xanda143 said:
crap i made a mistake and flashed a wrong kernel(fusion dragon and now the phone dosnt want to boot into recovery). i think the kernel was for the one S i didnt notice that. Anyway i know androids so am not worried about anything except my emmc chip can anyone give me the fastbood instructions to flash the various things on the glacier or are they the same for all phones also. a kernel that i can flash the will work with this viper rom would be nice.
i was trying fastboot flash zip rom.zip and that fails.
was really trying to avoid haveing to flash a PDM15.img but it as that would erase my ext4 recovery which i figure isnt working because the kernel i flashed was not for the phone and being touch based is messed up. so anyone knoe the fastboot commands to flash a rom in its zip form
Click to expand...
Click to collapse
Download the 4ext recovery image and
fastboot flash recovery recovery.img
Then boot into recovery and try flashing the zips. If you can't find the recovery.img, cwm images are available. You can easily switch back to 4ext later.
estallings15 said:
Download the 4ext recovery image and
fastboot flash recovery recovery.img
Then boot into recovery and try flashing the zips. If you can't find the recovery.img, cwm images are available. You can easily switch back to 4ext later.
Click to expand...
Click to collapse
i already have fastboot flash zip PD5IMG.zip and it worked ok and gave me back clockwork and official sesnse but should flashing an incompatible kernel damaged my recovery? seems flawedish seeing as i always saw recovery mode as my safe heaven. being its a touch recovery i can understand tho. if i had not flashed a eng bootloader i probly would have been screwed now. well lesson learned any info on a kernel that can work with the viper rom android 4.04 sense?
xanda143 said:
i already have fastboot flash zip PD5IMG.zip and it worked ok and gave me back clockwork and official sesnse but should flashing an incompatible kernel damaged my recovery? seems flawedish seeing as i always saw recovery mode as my safe heaven. being its a touch recovery i can understand tho. if i had not flashed a eng bootloader i probly would have been screwed now. well lesson learned any info on a kernel that can work with the viper rom android 4.04 sense?
Click to expand...
Click to collapse
Not sure about the kernel. I can tell you that different devices have different partition setups. The bootloader, system, recovery, etc. don't reside on the same partitions on every device. In fact, doing what you did can cause a hard brick on many devices.
what kernal did you use?
kkm323 said:
what kernal did you use?
Click to expand...
Click to collapse
The kernel wasn't for this phone so he got messed.
Sent from my myTouch 4g using xda app-developers app