If you were successful -- were you completely stock, or some GB upgrade (like LEEDROID), or some HC upgrade? At this point, it sounds like the third option is not possible, but I am wondering about the other two.
Thanks!
First post!
I am a US Best Buy WiFi owner.
I previously upgraded to Honeycomb using the first leaked release using the standard procedure.
I took a little risk and just flashed the new Honeycomb system image zip file. It boots into HC 3.2.1 without any problem without flashing anythign else. Everything seems to be fine with one exception - No wifi. Under the Wifi setting it says "error."
My guess is that if I flash the new radio image, then I will get Wifi Back. This would have to be done later because I have no access to a command line terminal here at work. I think we can probably skip the hboot and boot images.
Overall, the UI seems a little faster and there are some new transition animations.
Maybe someone can try to follow this procedure and see if it is successful.
What do you think?
I reverted back to the original HC release.
I'll update the radio image and then install the new HC sytem image again.
I had some funkiness (forced closes) when I went back. I had to wipe my user data but everything was fine after that. It is best to start everything with a blank slate.
lawguy said:
I reverted back to the original HC release.
I'll update the radio image and then install the new HC sytem image again.
I had some funkiness (forced closes) when I went back. I had to wipe my user data but everything was fine after that. It is best to start everything with a blank slate.
Click to expand...
Click to collapse
You'll have to keep us posted on this, as I too have a US WiFi only BB Flyer running HC (1st leak), so I'd like to see if this works too. However, I read another thread in the Dev forum from Globatron about fastboot flashing every item individually:
http://forum.xda-developers.com/showpost.php?p=18991623&postcount=497
EDIT: I assume this is due to S-ON...
That was my original thought - flashing each component just as you would in the original instructions. I would guess that this was tried and it did not work? Why else would we be instructed to go back to GB and start over? So I am hoping that just doing the radio image works and avoids whatever problems were encountered. I am thinking that since everything seems to work other than Wifi that it may only be necessary to flash the radio.
We'll see.
I have a combination of little fear and little skill so there is a good chance that I will brick my flyer.
fwiw...i have started a donation pledge drive in globatron's "Revert from HC to GB" thread and am starting it off with a $200 PayPal donation if others jump on board to pay for globatron to get a US Best Buy WiFi Flyer so we can not stress ultimately getting to ICS let alone a leaked HC.
http://forum.xda-developers.com/showthread.php?t=1307759
Maybe the boot.img and system image would work.
Sent from my ADR6400L using xda premium
I have a BB US Flyer that was running LEEDROID V2.2 and kernel 2.3 and I followed Paul's steps and successfully upgraded it to HC. All seems to be working at this point, except for that there was no English(USA) option so I chose UK for my language (bloody me, I have a strange accent now). Also, it thinks I have a phone capability, but I ignored those options. Step 17 I had to do manually by taking out the SD card, and step 7 I ignored because I already had the initial unlock.
Last night I tried totest my theory by flashing the radio image. No dice. I could not flash the Radio.
---------- Post added at 12:07 PM ---------- Previous post was at 11:59 AM ----------
Just a little more information: I think that the bootloader is locked and this is the reason that the radio cannot be flashed. Revolutionary does not support the Hboot version that is on the HC Flyers.
lawguy said:
Last night I tried totest my theory by flashing the radio image. No dice. I could not flash the Radio.
---------- Post added at 12:07 PM ---------- Previous post was at 11:59 AM ----------
Just a little more information: I think that the bootloader is locked and this is the reason that the radio cannot be flashed. Revolutionary does not support the Hboot version that is on the HC Flyers.
Click to expand...
Click to collapse
You might want to talk to PaulOBrian
http://forum.xda-developers.com/showthread.php?p=19012462
I don't have enough posts to do that yet!
lawguy said:
I took a little risk and just flashed the new Honeycomb system image zip file. It boots into HC 3.2.1 without any problem without flashing anythign else. Everything seems to be fine with one exception - No wifi. Under the Wifi setting it says "error."
Click to expand...
Click to collapse
And what else did you do?
Wipe you any data, cache, Dalvik cache?
And how did you flash the image? In fastboot, with recovery or?
lawguy said:
Last night I tried totest my theory by flashing the radio image. No dice. I could not flash the Radio.
---------- Post added at 12:07 PM ---------- Previous post was at 11:59 AM ----------
Just a little more information: I think that the bootloader is locked and this is the reason that the radio cannot be flashed. Revolutionary does not support the Hboot version that is on the HC Flyers.
Click to expand...
Click to collapse
You should try to flash it using the app that does so from normal android mode (if that makes sense). It's over in the evo3d themes and apps section. I'm pretty sure it allows people to flash things like kernels and radios that have a HTC unlocked bootloader. It's worth a shot.
Edit : nevermind you can't flash radios :/
Sent from my PG86100 using Tapatalk
I did the whole process two times.
The second time, I wiped the data and caches. This was all done through recovery.
One other issue I noticed is that I had difficulty restarting the Flyer after flashign with the new HC version. After pressing the power button, the menu came up as usual. After pressing restart, it would not restart. Instead, I had to press and hold the buttons to manually restart the flyer. This suggests some issue other than just the radio.
---------- Post added at 01:49 PM ---------- Previous post was at 01:48 PM ----------
Gumby63 said:
You should try to flash it using the app that does so from normal android mode (if that makes sense). It's over in the evo3d themes and apps section. I'm pretty sure it allows people to flash things like kernels and radios that have a HTC unlocked bootloader. It's worth a shot.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
I'll try it if you show me how to do it. I'm not sure what you mean.
Check the dev thread, we have working 3.2.1 wifi flyers going on there
Granted it's still in early stages, so there may be issues remaining to be worked out but things are looking good so far, I have this working on my US BB WiFi Flyer so far..
Cheers
BR
for those running HC, do you find it better in its current form than the gingerbread stock?
mcord11758 said:
for those running HC, do you find it better in its current form than the gingerbread stock?
Click to expand...
Click to collapse
Yes, If I had to define why all i could really say is that it just seems to fit running on a Tablet better than GB. Just my 2 cents tho.
Cheers
BR
For those that are flashing the new build you should follow the steps by Paul in the other thread http://forum.xda-developers.com/showthread.php?t=1330832 it is really very simple (it does involve using "ADB" tho, so if you are not familiar this may not be a good idea.
lawguy said:
First post!
I am a US Best Buy WiFi owner.
I previously upgraded to Honeycomb using the first leaked release using the standard procedure.
I took a little risk and just flashed the new Honeycomb system image zip file. It boots into HC 3.2.1 without any problem without flashing anythign else. Everything seems to be fine with one exception - No wifi. Under the Wifi setting it says "error."
My guess is that if I flash the new radio image, then I will get Wifi Back. This would have to be done later because I have no access to a command line terminal here at work. I think we can probably skip the hboot and boot images.
Overall, the UI seems a little faster and there are some new transition animations.
Maybe someone can try to follow this procedure and see if it is successful.
What do you think?
Click to expand...
Click to collapse
Hi, I think I was in the same situation when my flyer was on HC. I followed exactly paul's guide, but just like your flyer, mine also says wifi "error" in settings, and I can't check wifi. I think that should be the radio problem. For now, I rolled back to GB and wifi working good nwo, but really miss scribe using when I was on HC.
There is a simple upgrade method now to install the 3rd HC leak. Look in the DEV section for [Guide][Flyer]Honeycomb S-OFF, Honeycomb Easy Install, Recovery and Root. by globatron
http://forum.xda-developers.com/showthread.php?t=1358758
I followed the instructions last night and it went really well.
NEW USERS, installing HC first time, please read
NEW USERS:
HC works great on the BB wifi only. It takes a few steps to get it loaded and working. do your homework before installing HC ROMS, or you will be sorry and coming back for help.
Start with this thread.
http://forum.xda-developers.com/showthread.php?t=1358758
Have fun!!
Related
My phone completely died yesterday and I left it charging all night, when I woke up this morning all of the widgets were gone. The shortcuts to apps were still there but all my widgets including stock Motorola ones and various downloaded from the market were gone. Im running stock 2.3.4 minus the kernel. I have faux kernel installed. Anyone know why this may have happened?
Thanks
thats weird the exact same thing happened to me last night into this morning. i wake up. they are all gone. lol
There's worse things that could happen Haha, but still I don't remember where half of mine were haha
add me to that list
I lost mine as well, several times now. Just installed ADW to see if it happens again. It's getting frustrating.
Same thing happened to me when I was using a restored back-up of settings and configuration ADW.. Every time i would reboot I would loose my widgets or get "problem loading widget." I then uninstalled ADW and re-installed and did not use a restored configuration I have not had the problem since..
Hope this helps someone.
Same Problem
Funny, I had the same problem shortly after updating pudding (the unlocker SBF file that you install to unlock bootloader) and installing a custom kernel. For some reason, the two pieces work against each other to cause this problem.
All I did was flash the older pudding, called "Unlock SBF File" available at the page below, and reinstall my faux kernel, and my phone resumed fairly normal operation.
Unlock SBF page:
briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Hope that this helps
its still happening to me
I often get "problems loading widget" after a reboot.
No idea what's causing it.
Im running ninja 0.4.5 faux 0.1.7 on bell ATRIX..
Dame thing happened with cherrypi...
Oh yeah ... this is all on Launch Pro...
Anyone has any ideas what's causing it?
I had this problem when I installed faux's kernel... Installing version 1.3 or going to the stock kernel fixed it. Go into recovery wipe cache and dalvik cache then install the stock or faux's 1.3 kernel then reboot. Add your widgets again then reboot again to double check that your widgets didn't disappear.
yeah when i switched to kholk's kernel it worked fine, also on stock it works fine. Idk why faux's kernel does this
Sun3vi1 said:
Funny, I had the same problem shortly after updating pudding (the unlocker SBF file that you install to unlock bootloader) and installing a custom kernel. For some reason, the two pieces work against each other to cause this problem.
All I did was flash the older pudding, called "Unlock SBF File" available at the page below, and reinstall my faux kernel, and my phone resumed fairly normal operation.
Unlock SBF page:
briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Hope that this helps
Click to expand...
Click to collapse
I just tried your solution and it totally worked for me...that's awesome! thanks!!
Fixing permissions in CWM or Rom Manager fixes this problem.
Assimilated via WinBorg 4G
CaelanT said:
Fixing permissions in CWM or Rom Manager fixes this problem.
Assimilated via WinBorg 4G
Click to expand...
Click to collapse
that's good to know!
Sun3vi1 said:
Funny, I had the same problem shortly after updating pudding (the unlocker SBF file that you install to unlock bootloader) and installing a custom kernel. For some reason, the two pieces work against each other to cause this problem.
All I did was flash the older pudding, called "Unlock SBF File" available at the page below, and reinstall my faux kernel, and my phone resumed fairly normal operation.
Unlock SBF page:
briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Hope that this helps
Click to expand...
Click to collapse
It seems that the zomgunlock-lite.sbf, is what's in the zip on briefmobile now. Were you referring to a different pudding file?
---------- Post added at 09:35 PM ---------- Previous post was at 08:37 PM ----------
hoodlikegaza said:
It seems that the zomgunlock-lite.sbf, is what's in the zip on briefmobile now. Were you referring to a different pudding file?
Click to expand...
Click to collapse
WOW! After a week of getting owned by this disappearing widget issue and going back to the stock kernel, it seems this might be the solution.
The only thing is I did it the opposite from what you did. I originally unlocked with the zomgunlock-lite.sbf. I'm currently on the unlocked and pre-rooted gb SBF.
So I went to the pudding thread and downloaded the newer pudding sbf from that thread (4547-fix-try2.sbf), flashed it, and after about 10 battery pulls, I still have my widgets!
I didn't even have to oem unlock again, I was expecting to be soft bricked, but to my surprise the phone booted up normally, and everything worked correctly!
hoodlikegaza said:
It seems that the zomgunlock-lite.sbf, is what's in the zip on briefmobile now. Were you referring to a different pudding file?
---------- Post added at 09:35 PM ---------- Previous post was at 08:37 PM ----------
WOW! After a week of getting owned by this disappearing widget issue and going back to the stock kernel, it seems this might be the solution.
The only thing is I did it the opposite from what you did. I originally unlocked with the zomgunlock-lite.sbf. I'm currently on the unlocked and pre-rooted gb SBF.
So I went to the pudding thread and downloaded the newer pudding sbf from that thread (4547-fix-try2.sbf), flashed it, and after about 10 battery pulls, I still have my widgets!
I didn't even have to oem unlock again, I was expecting to be soft bricked, but to my surprise the phone booted up normally, and everything worked correctly!
Click to expand...
Click to collapse
This method apparently does not work for my T-Mobile UK Atrix. Any other fixes ?
Apparently it didn't work for me either.... Try the 0.1.7
Sent from my MB860 using Tapatalk
This has been also happening to me. I am on stock 2.3.4 with Faux's Enhanced stock kernel 2.0. I have tried fixing permissions, but it only worked with the first reboot after that
Try 0.1.7..... It's been a bit more stable for me.
Sent from my MB860 using Tapatalk
This will keep happening no matter how many fixes you try unless you:
1) Use stock kernel
or
2) Use CM7
Just trust me, I know you think the fix permission thing fixes it, but it will come back eventually, just a matter of time.
Sent from my MB860 using xda premium
Swiftks said:
This will keep happening no matter how many fixes you try unless you:
1) Use stock kernel
or
2) Use CM7
Just trust me, I know you think the fix permission thing fixes it, but it will come back eventually, just a matter of time.
Click to expand...
Click to collapse
Fingers crossed...I tried everything and never could get the Faux kernels to work with various roms and not with stock, either. Tried everything. (fix permissions CWM/Rom Manager/fastboot -w, fastboot erase everything, etc.)
Decided to give it a go a day and a half ago and tried the reunlock with the newer pudding unlocker (4547-fix-try2.sbf). Like the gent said didn't have to fastboot unlock, just rebooted. Then installed the Faux optimized 1.0 (not overclocked kernel).
Been running since with some reboots for good measure and the widgets are still there. We will see.
I was finally of the opinion that it was some problem between the kernel and setcpu..a month or so ago when I was running faux kernels. (I am not running setcpu at the moment)
We will see...
ps I intend to try CM7 but I am waiting for the lapdock to be functional. I use it everday
I just flashed [ROM] (5/25) Nils' Business ICS 4.0.3 Sense 3.6 last night for my S-OFF ReZound. Everything went beautifully and the ROM looks great. The problem I think I have is whenever an app throws up a notification my phone reboots. I first noticed it whenever I sync'd my Google account and it threw up a notification about new gmail messages. So I stopped syncing Gmail. Then it happened whenever I tried to open Twitter/Facebook or when I adjusted the ringtone volume or my alarm went off.
Does anyone have an idea why these things would cause the phone to reboot? Are there any commonalities between these functions?
Weird. Not sure about that. The only rebooting I get on the ROM is when I use my Lock Screen App instead of using the power button. From what I understand though, that is a problem with ALL the ICS versions for Rezound. I can't wait until that is fixed...I hate trying to press that little power button through the small hole in the case I use.
Did you do a full wipe and then flash? Sounds like something residual from a previous ROM. If you did wipe and flash, did you restore anything in Titanium? It clearly states in the OP for that ROM not to do that.
yea i did a full wipe and flash twice. i havent installed or used Titanium to this point.
it first started happening when i attempted to sync my google account, which was about the 3rd thing i did after installing the ROM.
Someone for mad at me for telling them search the old firmware patch
Is suggest you do the same
If you can't find your sdcard or if your phone reboots when it makes a sound.... You need to flash the old firmware patch
Sent from my ADR6425LVW using Tapatalk 2
superchilpil said:
Someone for mad at me for telling them search the old firmware patch
Is suggest you do the same
If you can't find your sdcard or if your phone reboots when it makes a sound.... You need to flash the old firmware patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
if you're referring to the GB firmware patch, then I did do that during the ROM install process per the instructions. i can try doing that again though.
You are on gingerbread firmware correct?
I have read about the patch not working the first time so that could be the issue
Sent from my ADR6425LVW using Tapatalk 2
i did come from GB firmware, but flashed the RUU 3.14.605.5 and then flashed the GB firmware patch. after doing this and booting into the RUU, i then flashed Nil's ROM.
nalees said:
i did come from GB firmware, but flashed the RUU 3.14.605.5 and then flashed the GB firmware patch. after doing this and booting into the RUU, i then flashed Nil's ROM.
Click to expand...
Click to collapse
if you flashed the 3.14RUU, you shouldn't need the GB firmware patch since you are now on ICS.
I would reinstall the ROM and skip the patch.
oh ok! i will do that now.
*update 2*
rats, 5 minutes later, as i'm refreshing my twitter app, it reboots. going to see if it continues to replicate. so far it has. uninstalling and reinstalling it. /// still rebooting when i refresh twitter. weird.
nalees said:
oh ok! i will do that now.
*update 2*
rats, 5 minutes later, as i'm refreshing my twitter app, it reboots. going to see if it continues to replicate. so far it has. uninstalling and reinstalling it. /// still rebooting when i refresh twitter. weird.
Click to expand...
Click to collapse
When you went from gb and ran the ics ruu, did you run the ruu twice.? It only updates a few things the first time through. The second time it does all items on the list.
Sent from my Rezound
oh my, just read through Nil's instructions again and you're right, it does say to run it twice...
i only did the RUU once.
ok, so from here, I need to reflash the RUU one more time? and then reload Nil's ROM?
hmm, also noticed on step #10 i need to unlock the bootloader again? is this true even if i'm s-off?
I went from completely stock to S-OFF and running Nils' latest Business Sense 2 days ago. I have not had any of the problems you mentioned.
His instructions do no say to install the RUU twice. They say that it's a 2 pass affair to install it. If you went through the whole process to install it once, you don't need to do it again.
However, I agree with an earlier post. Installing a GB firmware patch after installing an ICS RUU is probably your problem. Re-doing the whole thing from Nils' instructions for "Latest Leak and Installation Instructions", and then just installing his v4.1 ROM is probably all you need to do to get straightened out.
You absolutely need to flash the RUU twice. The 2nd time it will appear to be stuck on one of the times and flash it like 10 times but that is normal.
nalees said:
hmm, also noticed on step #11 i need to unlock the bootloader again? is this true even if i'm s-off?
Click to expand...
Click to collapse
It says that in Step #10, I believe. And yes, you have to do that in order to install (or re-install, as the case may be) AR Recovery (Step #11).
---------- Post added at 02:10 PM ---------- Previous post was at 02:03 PM ----------
con247 said:
You absolutely need to flash the RUU twice. The 2nd time it will appear to be stuck on one of the times and flash it like 10 times but that is normal.
Click to expand...
Click to collapse
I started on Monday with a bone stock Rezound. I unlocked, rooted, and did the wire trick for S-OFF.
Then I flashed the 3.14 RUU once, unlocked again, installed AR Recovery again, and then flashed Nils' v4.1 ROM (for S-OFF).
My phone seems to be working fine. Exchange mail (I don't use Gmail), contacts, calendar and tasks. Visual Voice Mail. Notifications. Text messaging. Facebook. WiFi Tether. Google Maps. Camera. Bluetooth handsfree. Everything seems to work fine. The only thing I haven't tested yet, that I mean to, is to force it to 3G only for data and test that I can talk and surf the Web at the same time.
Since I did not flash the RUU twice, what should I be looking for to not work right?
Do not HTC unlock after s-off.
Edit: saw you did.... Basically you will have unlocked or re locked. If you wanted the bootloader to appear stock you have to s-on and do the s-off process again. Then it would say locked. Not a big deal.... Unless you are paranoid and have to do a warranty swap.
Sent from my Rezound
ericsignals said:
Do not HTC unlock after s-off.
Sent from my Rezound
Click to expand...
Click to collapse
yea, i was reading this thread and that's why i thought that...
http://forum.xda-developers.com/showthread.php?t=1620211&page=6
i'll do some more reading before i proceed.
Just tested the SVDO.
Went into Phone Info and set my phone to CDMA Auto (PRL).
Turned off WiFi.
Confirmed status bar displayed 3G.
Called up my bank and let the automated menu thing talk over speakerphone.
Ran Speedtest on phone and it worked.
Went into Phone browser, did a Google search and got results.
Turned on WiFi Tether on my phone.
Connected my TouchPad (running ICS) to phone hotspot.
Ran Speedtest on TP. Got 1934kbps down and 1945kbps up.
I'd say simultaneous voice and 3G data work just fine with Nils' ROM, too...
so i redid everything tonight the proper way and its up and running perfectly! loving it
nalees said:
so i redid everything tonight the proper way and its up and running perfectly! loving it
Click to expand...
Click to collapse
And that releives me. Have fun
I recently used the Juoponutbear "Wire Trick" method to gain s-off on my phone, having been stuck with the HBoot 1.5 half-assed "unlock" for far too long. After using it, I had to use WiFi to download a file manager to move the 1.06 PG86ING.zip to the root of my sdcard, and WiFi worked fine. Flashed the new radio, then flashed MeanROM ICS 2.4. Now, WiFi immediately disconnects from any access point I try to use. I never tried using WiFi on the stock ROM after flashing the radio, but before flashing the ROM, so I cannot be sure at what point if stopped working properly. I have since flashed MeanROM GB (not sure which version, but I believe the latest), inbREDed ICS, and a stock-rooted GB ROM. WiFi no longer works in any of them. It turns on, it detects WiFi access points, but it always disconnects from then after just a few seconds. Does anyone have any idea what I cab do to fix this? Thanks in advance!
Sent from my PG86100 using Tapatalk 2
Make this a note in your mind when flashing any Roms If you have broken Wifi Most likely its the kernel and it didnt get flashed correctly or left out bits of info to it..... thats my experience I Garentee you and bet my own evo 3d that that is the issue
---------- Post added at 06:44 PM ---------- Previous post was at 06:41 PM ----------
it could be that or your wiretrick wasnt fully complete but it said Sucess Because ive had that happen ///
if thats the case then Stock PG86IMG The phone back to stock
and retry
The kernel flashed fine in all cases. It has turned out that the problem was with the WiFi access points I was trying to use, and not my phone. It's working fine now.
Sent from my PG86100 using Tapatalk 2
I need help badly.....I am using Evo 3d Gsm (Root,Unlock,S-off,Hboot 1.49.007) and this [ROM] CM 10 Gangnam Style. My 3g is not working if it is running for like 20 minutes even the 3g icon is still there. Also my phone some time getting very laggy and freeze...i have to lock the screen and turn it on to get this issue away....any1 can help me with this issue?? Many thanks....
hongsydney said:
I need help badly.....I am using Evo 3d Gsm (Root,Unlock,S-off,Hboot 1.49.007) and this [ROM] CM 10 Gangnam Style. My 3g is not working if it is running for like 20 minutes even the 3g icon is still there. Also my phone some time getting very laggy and freeze...i have to lock the screen and turn it on to get this issue away....any1 can help me with this issue?? Many thanks....
Click to expand...
Click to collapse
Data drops are a common issue on cm10 jb Roms, I would suggest using agrabren disarmed toaster version 67 , or helicopters 88 cm10 nightlies
Sent from my IdeaTabA2109A using Tapatalk HD
I'm using the same cm10 and it's ok.
Did you wipe all partitions first (except sd) and then install it?
Also you have to install the correct version of gapps. 20121011 i think it was. It's linked to from the op of the thread.
Also your touch screen issues with the Evo 3d could very likely be hardware related. I've had to have that fixed twice at the Sprint store. It's a known issue.
when rewinding video on IMDB says "can't play this video"
Thank mojo
mojomojo_man said:
I'm using the same cm10 and it's ok.
Did you wipe all partitions first (except sd) and then install it?
Also you have to install the correct version of gapps. 20121011 i think it was. It's linked to from the op of the thread.
Also your touch screen issues with the Evo 3d could very likely be hardware related. I've had to have that fixed twice at the Sprint store. It's a known issue.
Click to expand...
Click to collapse
Thank mojo for your reply....i did full wipe ( Wipe data/reset + Cach and davik + format partrition without sdcard) before install..About the laggy....it happens not only on my phone but on my friend phone that i try to install this rom on also...so i think this is not relating to hardware....i will try to reflash and choose the right Gapps to see if this fix the issue and report back..
No problem. Also you should be S-Off with any hboot except 1.58.
I did wire trick then flashed jbear 1.58 then downgraded to 1.50 jbear. Then did full wipe and flashed gangnam style cm10. My radio firmware was already up to date. Maybe you should first take the extra time to put it back to stock with ruu just to make sure your radios and everything are most recent? If you have the patience you could try to follow QADERSO (quick and dirty...) guide to returning to stock then doing root and s-off and jbear. Just add final step of downgrading to jbear 1.50 by downloading it to your sdcard and renaming it to PG86IMG.ZIP then going into bootloader once. Then you can wipe and install cm10. Also I use 4ext touch recovery and highly recommend it.
Doing all that should guarantee you are identical to me. There are still some issues with this ROM but not the serious ones you describe.
Problems I'm having are the camera resolution or ratio is weird (i get black bars above and below) and if i connect wifi with 4G on then the 4G goes into some kind of loop connecting then disconnecting then disable and enable adapter and repeat. CM10 power control in notification bar for 4g is kind of spotty too. I'll pay with it for a while longer before making a final decision but I think so far the pros outweigh the cons. I did find also that i was using tons more internal storage and ran out of space for my apps so i partitioned my sd card and have it a 3gb ext4 partition and installed Links2SD app and now have lots of space for apps. Maybe one of these days I'll write a guide for the whole process.
Found a bigger issue with this ROM and updating to today's release did not help. /data partition is filling up because wimax is running in debug mode or something. /data/wimax/logs directory is filling up quickly while wimax is on. I had 700mb from less than 24 hrs.
I cleaned them up manually but will need to schedule a batch job to delete it or figure out how to stop generating the logs...
mojomojo_man said:
Found a bigger issue with this ROM and updating to today's release did not help. /data partition is filling up because wimax is running in debug mode or something. /data/wimax/logs directory is filling up quickly while wimax is on. I had 700mb from less than 24 hrs.
I cleaned them up manually but will need to schedule a batch job to delete it or figure out how to stop generating the logs...
Click to expand...
Click to collapse
Known issue. Just "flash" the attached zip file from recovery which will delete/recreate that directory then mark it immutable so no more logs accumulate.
ramjet73
I had a couple of questions if anybody has had experience with such, first one...
Has anyone tried to use the Acid audio RLA5 sound mod and if so, I've heard that having a eq already in the ROM makes it
all goofy for install? Is this true and if so, has anyone else used this mod and what procedure did you do?
As for the second part, has anyone had any luck finding a full inverted gapps that everything will work? I thought I found one but it didn't have contacts inverted, then found another but it crashed google now. If anyone has had any luck could you drop me a link. ( all gapps including mms etc..)
On the 3rd part of the adventure of swapping out apks, I updated google ears via alert from playstore and it crashes something else.. LOL. Its just a never ending battle. But, through the day I found a piece here and there and now it all seems to be working and all inverted and that is after updating what play store wanted to.
Right now creating a flashable.zip that should work but not certain on the rules as to post. I already have a pre- written statement that announces that I take no credit in the creation and also name the Devs responsible and also will be linking their threads as well but not sure if that is enough. If anyone has any input that would be greatly appreciated.
Thanks,
Z.
thank Mojo
mojomojo_man said:
No problem. Also you should be S-Off with any hboot except 1.58.
I did wire trick then flashed jbear 1.58 then downgraded to 1.50 jbear. Then did full wipe and flashed gangnam style cm10. My radio firmware was already up to date. Maybe you should first take the extra time to put it back to stock with ruu just to make sure your radios and everything are most recent? If you have the patience you could try to follow QADERSO (quick and dirty...) guide to returning to stock then doing root and s-off and jbear. Just add final step of downgrading to jbear 1.50 by downloading it to your sdcard and renaming it to PG86IMG.ZIP then going into bootloader once. Then you can wipe and install cm10. Also I use 4ext touch recovery and highly recommend it.
Doing all that should guarantee you are identical to me. There are still some issues with this ROM but not the serious ones you describe.
Problems I'm having are the camera resolution or ratio is weird (i get black bars above and below) and if i connect wifi with 4G on then the 4G goes into some kind of loop connecting then disconnecting then disable and enable adapter and repeat. CM10 power control in notification bar for 4g is kind of spotty too. I'll pay with it for a while longer before making a final decision but I think so far the pros outweigh the cons. I did find also that i was using tons more internal storage and ran out of space for my apps so i partitioned my sd card and have it a 3gb ext4 partition and installed Links2SD app and now have lots of space for apps. Maybe one of these days I'll write a guide for the whole process.
Click to expand...
Click to collapse
thank Mojo again for a very clear instruction....I have a question:
1) Is it true that i get my radio update to version 11.77 (it is 10.xx at the moment) when i install this RUU file (RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed.exe).
2)Will my Hboot change after this install??? and also my phone come back to S-on????
3)When i do this install with this file PG86IMG.zip from bootloader then it will get hboot change as far as i know right....???
IF my knowledge was correct, i will give it a try to install the RUU file to update my phone's radio back to 11.77 (it was 11.77 before i did the downgrade hboot to 1.49.007 from 1.53.xx) then install Gangnam Style rom to see if the 3g issue go away....
If i was wrong that when i install the RUU, my phone will be S-on again...im so lazy to try this because i will stick with Viper3d sense 4.1 then...
1 more thing mojo...i am using the latest disarm toaster rom (DisarmedToaster-0.2.9-67-shooteru)
ramjet73 said:
Known issue. Just "flash" the attached zip file from recovery which will delete/recreate that directory then mark it immutable so no more logs accumulate.
ramjet73
Click to expand...
Click to collapse
Thanks ramjet. Actually I already switched to the AOKP release (Linaro build) which is very similar to the ROM mentioned in this topic and doesn't have the Wimax log issue but hopefully that zip is out there for others to find because I didn't see it in the dev thread for that ROM at least not at the time I mentioned it above anyway. There's a few small Q's I have about this AOKP ROM but I should start a new topic for those.
mojomojo_man said:
Thanks ramjet. Actually I already switched to the AOKP release (Linaro build) which is very similar to the ROM mentioned in this topic and doesn't have the Wimax log issue but hopefully that zip is out there for others to find because I didn't see it in the dev thread for that ROM at least not at the time I mentioned it above anyway. There's a few small Q's I have about this AOKP ROM but I should start a new topic for those.
Click to expand...
Click to collapse
If you are referring to mazda's AOKP ROM it does have the same problem with wimax logs accumulating and there is link to a post after the last question in the FAQ that has the same zip file I linked in this thread.
ramjet73
hongsydney said:
thank Mojo again for a very clear instruction....I have a question:
1) Is it true that i get my radio update to version 11.77 (it is 10.xx at the moment) when i install this RUU file (RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed.exe).
2)Will my Hboot change after this install??? and also my phone come back to S-on????
3)When i do this install with this file PG86IMG.zip from bootloader then it will get hboot change as far as i know right....???
IF my knowledge was correct, i will give it a try to install the RUU file to update my phone's radio back to 11.77 (it was 11.77 before i did the downgrade hboot to 1.49.007 from 1.53.xx) then install Gangnam Style rom to see if the 3g issue go away....
If i was wrong that when i install the RUU, my phone will be S-on again...im so lazy to try this because i will stick with Viper3d sense 4.1 then...
1 more thing mojo...i am using the latest disarm toaster rom (DisarmedToaster-0.2.9-67-shooteru)
Click to expand...
Click to collapse
That RUU file is for Europe.... Are you in Europe? Is that a GSM phone? If so I'm afraid I can't advise about radio firmware versions. Firmware for radio is probably different for European users and the guide which I was referencing is Ramjet's guide found here: http://forum.xda-developers.com/showthread.php?t=1889438 but that guide is for Sprint or Virgin Mobile users (CDMA phones). Basically the guide is accurate I think for European user too but the RUU file should be different. Well, you should consult Ramjet on that as he wrote the guide and may know more. Also, you are correct that running the RUU will return the phone almost completely to stock. It replaces radio firmwares and HBOOT and will put you back to non-root. I just suggested it as a way to make sure you go completely back to stock and start from scratch so I can be sure you were on same versions of everything as me but if you are in Europe you cannot exactly follow it maybe. Anyway, I think you have explained all your issues though. By the sound of it you probably flashed USA (Sprint) radio firmware by accident when you downgraded your HBOOT. Next time you downgrade HBOOT you should make sure the file you are using is HBOOT only with NO radio firmwares in it.
So I think you have two options....
1.) To go back to stock using latest Europe RUU, root/S-OFF phone again (S-OFF might stay, I forget), put 4EXT back and then try to downgrade HBOOT to a compatible version again. This time you must downgrade without changing radios or if you can find a flashable zip with just your proper European 11.77 radios then you can flash just the radios back to 11.77 after downgrade. I don't know the version numbers for GSM phones for HBOOT or radios so I apologize if I am getting this wrong.
2.) Assuming your only problem is the 3g connection currently then maybe you can just find a flashable zip which will update only your radio firmware back to 11.77 without having to go completely back to stock. If everything else about the phone seems OK then this is definitely faster assuming you can find the right file.
Again, I know little about GSM phones and European radios so you may want to find a more knowledgeable person to help you. Definitely though if you flashed the wrong radios then you will lose your 3G connection! I have seen HBOOT's posted both with and without radio firmwares included so I think from now on you must be extra careful when flashing HBOOT to make sure you are not changing radios to USA radios and you should keep around a flashable zip with only your 11.77 radios in it so you can fix this as it may happen again.
Good luck!
If you read the developer's thread carefully you'll notice that he affirmed that data drops will occur.
ramjet73 said:
If you are referring to mazda's AOKP ROM it does have the same problem with wimax logs accumulating and there is link to a post after the last question in the FAQ that has the same zip file I linked in this thread.
ramjet73
Click to expand...
Click to collapse
Yes, Mazda's rom is the one I am using now. I wiped everything, then flashed 3.5 and then immediately did incremental to 3.5.2 then gapps of course and wiped dalvik and rebooted into rom. I checked and wimax logs were not accumulating like they had been. I just checked again and there are only some small "sequansd##.log" files in that directory but these files are tiny (about 9kb) each. I suppose it could become a problem after many months of use but when I was using the Gangnam Style CM10 rom mentioned in the title I filled the remainder of my /data partition in a single day with a ton of 500K files (forgot the name of the file) in addition to the sequansd files. So I guess these logs if not rotated could eventually become a problem but the severity of the issue is nowhere near on the same scale with a clean install Mazda's 3.5.2.
I just set the /data/wimax/logs folder permissions to 440 and deleted the sequansd log files so I think that will suffice? If not I'll flash the zip. I'm just being lazy.
BTW, thanks for your posts in Mazda's thread (using Power Toggles now and I love it) and your QADERSO guide. Both have been very helpful to me.
That ROM is known to have data drops on a mobile network. You can't do anything about it as the ROM is built that way. The only fix would be for the developer to fix it or for you to chanhe ROM.
Goodluck!
mojomojo_man said:
I just set the /data/wimax/logs folder permissions to 440 and deleted the sequansd log files so I think that will suffice? If not I'll flash the zip. I'm just being lazy.
Click to expand...
Click to collapse
Logs were still being written even when people changed permissions. The only way to stop the logs was to make the folder immutable. I flash the zip as part of my install.
mojomojo_man said:
That RUU file is for Europe.... Are you in Europe? Is that a GSM phone? If so I'm afraid I can't advise about radio firmware versions. Firmware for radio is probably different for European users and the guide which I was referencing is Ramjet's guide found here: http://forum.xda-developers.com/showthread.php?t=1889438 but that guide is for Sprint or Virgin Mobile users (CDMA phones). Basically the guide is accurate I think for European user too but the RUU file should be different. Well, you should consult Ramjet on that as he wrote the guide and may know more. Also, you are correct that running the RUU will return the phone almost completely to stock. It replaces radio firmwares and HBOOT and will put you back to non-root. I just suggested it as a way to make sure you go completely back to stock and start from scratch so I can be sure you were on same versions of everything as me but if you are in Europe you cannot exactly follow it maybe. Anyway, I think you have explained all your issues though. By the sound of it you probably flashed USA (Sprint) radio firmware by accident when you downgraded your HBOOT. Next time you downgrade HBOOT you should make sure the file you are using is HBOOT only with NO radio firmwares in it.
So I think you have two options....
1.) To go back to stock using latest Europe RUU, root/S-OFF phone again (S-OFF might stay, I forget), put 4EXT back and then try to downgrade HBOOT to a compatible version again. This time you must downgrade without changing radios or if you can find a flashable zip with just your proper European 11.77 radios then you can flash just the radios back to 11.77 after downgrade. I don't know the version numbers for GSM phones for HBOOT or radios so I apologize if I am getting this wrong.
2.) Assuming your only problem is the 3g connection currently then maybe you can just find a flashable zip which will update only your radio firmware back to 11.77 without having to go completely back to stock. If everything else about the phone seems OK then this is definitely faster assuming you can find the right file.
Again, I know little about GSM phones and European radios so you may want to find a more knowledgeable person to help you. Definitely though if you flashed the wrong radios then you will lose your 3G connection! I have seen HBOOT's posted both with and without radio firmwares included so I think from now on you must be extra careful when flashing HBOOT to make sure you are not changing radios to USA radios and you should keep around a flashable zip with only your 11.77 radios in it so you can fix this as it may happen again.
Good luck!
Click to expand...
Click to collapse
WOW.....i think i got the wrong Rom downgrading my Hboot to 1.49.007......My phone's radio was 11.77.3504.00U_11.25.3504.06 and Hboot=1.53.......After i tried to S-off and downgrade hboot to 1.49.007....my phone radio is 10.53.9020.00U_10.13.9020.08 at the moment and it is working fine with my rom Viper3d R310. Also i live in asia Vietnam......
Mojo....do you think i should get my radio back to 11.77 even my phone is working fine with this radio 10.53,??? i really dont know where can i look up the file for the radio only??/ and how to install it....anyone here can help me with the correct file for the radio???
Yup. You're right. Still accumulating. I'll flash the zip. Although it's probably just a debug setting somewhere that needs to be flipped off. Could be in kernel or in the module loading. Although I'm thinking in Linux terms. Not sure how much of that really translates to android and I'm not about to start mucking around compiling my own kernel.
mojomojo_man said:
Yup. You're right. Still accumulating. I'll flash the zip. Although it's probably just a debug setting somewhere that needs to be flipped off. Could be in kernel or in the module loading. Although I'm thinking in Linux terms. Not sure how much of that really translates to android and I'm not about to start mucking around compiling my own kernel.
Click to expand...
Click to collapse
This issue first surfaced in agrabren's disarmed toaster CM10 ROM and he didn't offer another solution, so I have to believe that any thing other than what has already been suggested would not be trivial.
ramjet73
I very thoroughly apologize if this has been asked and discussed before, but apparently my search skills aren't the best. Anywho, her's the issue.
I've used a number of different ROM's since I first got my DNA back in January. I've used older Tranquil releases. But anything after 2.1 I believe it was, I haven't had WiFi. I have it just fine with all other ROM's. But no matter what I do for Tranquil (even up to and including RLS 4.2), there's no WiFi connection. It says it's trying to find sources or something and eventually errors out. I have no idea what the problem is. If I go back to 2.1 or 2.0, WiFi works great. This kind of sucks as I really enjoyed the earlier Tranquil releases and would like to continue using them. I'm currently using NOS m7's latest release for 4.1.2 (couldn't get their 4.2.2 release to work for some reason, just sat at the HTC screen for over 30 minutes, even after wiping the entire phone and attempting to sideload).
Anyway, if someone can tell me how to get WiFi to work on Tranquil releases after 2.1, that would be awesome. And again, I apologize if this has been covered before. I tried posting in the official thread but my lack of post count keeps me from doing so.
You need to update your firmware to 2.06
Sent from my HTC6435LVW using Tapatalk 4 Beta
Can I ask where it's failing? I'm running the 4.2 ROM, and WiFi seems to work fine.
Be happy to look at my settings for you if you need, but IIRC, it came up correctly the first time -- during initial setup.
-AJ
thatotherguy.. said:
You need to update your firmware to 2.06
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
Attempting to get the 2.06 update and then reunlock at the moment, but it's not recognizing the phone in Fastboot. Recognizes fine when it's on, but not Fastboot.
aweber1nj said:
Can I ask where it's failing? I'm running the 4.2 ROM, and WiFi seems to work fine.
Be happy to look at my settings for you if you need, but IIRC, it came up correctly the first time -- during initial setup.
-AJ
Click to expand...
Click to collapse
It does it right from the beginning. Any other ROM and my WiFi network shows immediately. Any release past 2.1 and no WiFi at all.
Make sure your cord works fine
Sent from my HTC6435LVW using Tapatalk 4 Beta
thatotherguy.. said:
Make sure your cord works fine
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
I've used this same cord to ADB push and sideload while in Recovery before. Plus it reads just fine when the phone is on as normal. Wouldn't that make it fine? (Note: Not being sarcastic or anything, genuine question. I know how things can be misinterpreted over the 'net so I kinda like to point out how I mean things.)
Edit: I got it to work so far. I'm reflashing back to complete stock now. Apparently a driver wasn't installed for it to be detected in Fastboot. I'll post back after I get back to stock, completely update to newest, and reflash Tranquil RLS4.2.
So I got everything installed, running again, latest updates, reunlocked, TWRP back on, flashed RLS 4.2... No WiFi still... What am I doing wrong here?
Edit: NOS M7 3.0.4 is doing the same thing it was before, also. It's not even getting passed the HTC screen, no matter how long I let it sit. This is quite frustrating. I put M7 2.0.3 back on and everything works as it should. Anyone have an possible solutions?
Do you upgrade your firmware?
Sent from my HTC6435LVW using Tapatalk 4 Beta
It was upgraded to 2.06 when everything was completely stock..
are you s-off or s-on sounds like youi aren't getting the kernel. If you are s-on you have to extract it and push it seperately, or find one marked to be flashed seperately s-on. I didn't see where anyone posted this. Sorry if I missed it. Busy here at work but saw your thread.
matthall9815 said:
are you s-off or s-on sounds like youi aren't getting the kernel. If you are s-on you have to extract it and push it seperately, or find one marked to be flashed seperately s-on. I didn't see where anyone posted this. Sorry if I missed it. Busy here at work but saw your thread.
Click to expand...
Click to collapse
Other than being rooted with the custom ROM, it's whatever the normal S is (can't remember off the top of my head). I rooted and tried the Moonshine thing but it never took (on stock 2.06) so I just went through and reunlocked with my original packet from the HTCDEV website and went about things that way.
Ok, it's an easy fix. When you flash from recovery you are getting the rom, but not the kernel information. I assume you've probably been having bad battery life also. The only way to falsh a kernal s-on is with adb push, or with a hboot flashable where it goes all the way back to the white screen. if you download the all in one kit I think you can use that to push a kernel easily. I can never remember the adb commands. I think they suggest beaups kernel for that rom. Go ahead and download the two, and pm me if you need any more instruction.
http://forum.xda-developers.com/showthread.php?t=2343352
http://forum.xda-developers.com/showthread.php?t=2000896
matthall9815 said:
Ok, it's an easy fix. When you flash from recovery you are getting the rom, but not the kernel information. I assume you've probably been having bad battery life also. The only way to falsh a kernal s-on is with adb push, or with a hboot flashable where it goes all the way back to the white screen. if you download the all in one kit I think you can use that to push a kernel easily. I can never remember the adb commands. I think they suggest beaups kernel for that rom. Go ahead and download the two, and pm me if you need any more instruction.
http://forum.xda-developers.com/showthread.php?t=2343352
http://forum.xda-developers.com/showthread.php?t=2000896
Click to expand...
Click to collapse
You're right. My battery life has been absolutely terrible. I can get maybe 6-8 hours until I'm at 30% or under, and that's not doing anything. Much less if I actually want to do anything with the phone. I'll give those two links a look. Thanks. :good:
Edit: So, I've noticed it's now S-On and the kernel isn't showing on the device. I copied the .zip over to the main directory where I always do, and it's not showing on the phone. But it shows just fine in Windows.
Edit again: Got it to flash using Sideload. Before I do anything else, is it okay to now flash RLS4.2 and see if WiFi works? Now that that's on there, it should be good, right? Or do I need to flash RLS4.2 and then reflash this kernal?
Yet another Edit: It took me a while, but I noticed a LOT of things were missing on the phone after flashing the 2.06 kernel. The one that made me notice was FaceBook. And Google Play Store wasn't there anymore, either. I've reflashed to Digital Dream 2.2 and everything is back to normal. This is really frustrating.
Pm me when you're working on this again I think there are a couple things that are confusing.
Sent from my HTC6435LVW using Tapatalk 4
I finally got it to connect.
I was running DigitalDream 2.2 while trying to figure this all out. I ended up getting S-Off and reflashing. For me to S-Off while already on DigitalDream 2.2, I used the first part of the Mooshine Method (downloading their 2.06firmware zip file, flashing that, rebooting) then used the FacePalm method. That successfully got me S-Off. I noticed that even on DG2.2 after that, I had no WiFi. So I decided to try flashing Tranquil 4.2 and now I have WiFi working. Hope this helps anyone that has the same issue I did.