Hi everyone. My first official thread on here...althought I have been lurking for quite some time. Here is my issue.
I've done the 3 mods in the development forum to increase 3g data speeds. The two edits worked well but when I went in and replaced my lib_motoril.so file, now all of a sudden my phone is stuck at the boot logo/android recovery. I can get into BSR but after about 10 seconds of being in trying to navigate to my cm7 zip, it just reboots to the android recovery. I'm trying to avoid a complete wipe so I tried renamed my cm7 to update.zip and tried running that from android recovery but it won't let it run. ANY help is appreciated. If I must, I will wipe data but as I said, I am trying to avoid that. Thanks!
unt0uchable said:
Hi everyone. My first official thread on here...althought I have been lurking for quite some time. Here is my issue.
I've done the 3 mods in the development forum to increase 3g data speeds. The two edits worked well but when I went in and replaced my lib_motoril.so file, now all of a sudden my phone is stuck at the boot logo/android recovery. I can get into BSR but after about 10 seconds of being in trying to navigate to my cm7 zip, it just reboots to the android recovery. I'm trying to avoid a complete wipe so I tried renamed my cm7 to update.zip and tried running that from android recovery but it won't let it run. ANY help is appreciated. If I must, I will wipe data but as I said, I am trying to avoid that. Thanks!
Click to expand...
Click to collapse
IMHO CM7 needs nothing but a user....
I would back-up all your stuff, Titanium Backup is great... then SBF back to 2.3.4
There is nothing better then a clean slate, plus it only takes under an hour to SBF,root, install BSR, flash cm7...etc
Did you make a NANDdroid back up before you flashed these custom scripts/mods? That is usually the biggest mistake anyone can make...If you did great, now see if you can restore to that point
Hope the best for ya, hope ya Nandroided before flashing, and if anything just sbf
On cm7 & bsr bombing out. Can't boot right? Do a safe boot. Hold pwr & menu. @ the big m let go of pwr but stay on menu til the vib.
Hi everyone. Thanks for the replies. I was a dumbass and didn't do a backup before all of this happened. Not a huge deal anyways. I ended up SBF'ing and reflashing to cm7. I needed a fresh install anyways I was just being a sissy lala about it. Thanks again. Next time I'll be sure to nandroid. Hopefully this all didn't make me come off as too much a n00b on here. lol. Thanks guys.
-David
I would reccomend running cm7 stock. I have found everything else seems to take away from the performance.
unt0uchable said:
Hi everyone. Thanks for the replies. I was a dumbass and didn't do a backup before all of this happened. Not a huge deal anyways. I ended up SBF'ing and reflashing to cm7. I needed a fresh install anyways I was just being a sissy lala about it. Thanks again. Next time I'll be sure to nandroid. Hopefully this all didn't make me come off as too much a n00b on here. lol. Thanks guys.
-David
Click to expand...
Click to collapse
Now do yourself a favor before you do anything else...install the patched BSR and make a NANDroid backup
Agree with Travis... CM7 is great alone.
SMILE It's Not Illegal Yet
Travisdroidx2 said:
I would reccomend running cm7 stock. I have found everything else seems to take away from the performance.
Click to expand...
Click to collapse
I beg to differ. My 3g speeds are now 4x greater than before. I'm running at the same speed as my baseline ATT Uverse internet on wifi.
And I am definitely backing up now. Lol. Won't make that mistake twice.
Sent from my MB870 using XDA App
unt0uchable said:
I beg to differ. My 3g speeds are now 4x greater than before. I'm running at the same speed as my baseline ATT Uverse internet on wifi.
And I am definitely backing up now. Lol. Won't make that mistake twice.
Sent from my MB870 using XDA App
Click to expand...
Click to collapse
Your running a new fresh room
SMILE It's Not Illegal Yet
But my speeds were testing before it crashed (with mods 1 and 3 of the thread) and they were still 4x what they were before at full strength. I will admit, after the fresh install, they were even a little higher but the speeds hang out right around 2.5 Mpbs down and 1 Mbps up. Actual downloads, a 12 megabyte file took 10 seconds to download. So still, not too shabby. I'm going to download the 90mb CM7 zip and see how long it takes....
Are right under a "hub" cell tower? Set yo cm7 sig read out to dbm and what's yo signal . I live 3/4 of a mi from a hub and get -67 sig & 1.5 to 2 mips w/ moltcher's mods OR just the safe old throttle mods in /data/system/throttle. No difference see old thread.
Edit
It's so easy. In Airplane mode del the 2 files in the throttle folder. Then change perms of the throttle folder to r-x------. Reboot. Undo AP mode.
Related
So... Here's my question. If I am running Gingeritis and I need to go back to my PerfectStorm nandroid to retrieve data for an app I forgot to refresh a back up for, can I just load my back up in recovery get what I need and load my Gingeritis back up through recovery without switching the radios or breaking something? Thanks in advance...
So... Noone had an answer to this? I just want to make sure I don't send it into a loop.
bking_soda said:
So... Here's my question. If I am running Gingeritis and I need to go back to my PerfectStorm nandroid to retrieve data for an app I forgot to refresh a back up for, can I just load my back up in recovery get what I need and load my Gingeritis back up through recovery without switching the radios or breaking something? Thanks in advance...
Click to expand...
Click to collapse
His will work just fine. No need to flashing radios if you don't need signal for thr time being. I'm not ssure why people say you have to flash the radio after the rom and before it boots. I've tried all varieties and it doesn't matter. Hope this helps. But yea just make a back and restore your Froyo then restore your ginger and you'll be good to go.
Awesome. Thanks for the reply. I had a pretty good feeling it would work, I just wanted to verify before doing it.
Yeah... That didn't work. Haha. Backed up my current, tried to restore my froyo and it said mismatch Md5. Rebooted and sent the phone into boot loop. Lol. Battery pull, hboot, restore most recent back up and now everything is good again. You learn something new every day. Haha.
bking_soda said:
Yeah... That didn't work. Haha. Backed up my current, tried to restore my froyo and it said mismatch Md5. Rebooted and sent the phone into boot loop. Lol. Battery pull, hboot, restore most recent back up and now everything is good again. You learn something new every day. Haha.
Click to expand...
Click to collapse
If it said mismatch md5 then you had a bad backup. Has nothing to do with the radio.
dalrym05 said:
If it said mismatch md5 then you had a bad backup. Has nothing to do with the radio.
Click to expand...
Click to collapse
I'm 99% positive anyways. Maybe someone else will jump in and say for sure but ive gone back and forth the ssame way you wanted to wih no issues at all.
Yeah... Who knows. Either way... It now seems I'm never going back to froyo. Oh well, I'm happy with GB and Gingeritis. Runs smooth and stable. Not sure how my backup would be bad. Never ran into that problem before. Some things just weren't meant to be I guess. Goodbye froyo, it was fun while it lasted. Haha.
I don't remember the issue exactly as I saw it described but the md5 mismatch seems to have something to do with renaming the backup.
Sent from my HTC Thunderbolt
I had renamed the backup, but I've never had a problem renaming backups before... Don't know what's different now. Only difference is that this was the first time I tried to go from GB back to a froyo Rom.
I couldnt post this there, so im posting it here
I've flashed 2 other versions of this rom successfully in the past. The only difference is this time is factory reset it first. Then attempted to flash the rom. the Rom gave me an error, and thats when the bootlooping started.
I tried factory resetting, deleting cache, leaving battery out for 30 seconds.
Im stuck at the Moto screen
SO, what do i do? is there any pertinent information im leaving out?
Your going to want to flash the sbf, full instructions are in a thread in the development section, don't have access to the link at the moment I'm mobile, sorry mate.
Sent from my DROID X2 using XDA App
ok.
Is there any way to make sure this doesnt happen again? This is such a process
You could also try plugging the phone into a wall when its off to see if you can get into BSR and either restore a backup or try to flash again.
Sent from my DROID X2
lacross said:
Is there any way to make sure this doesnt happen again? This is such a process
Click to expand...
Click to collapse
It IS a bit of a process to go thorough. Part of the price to pay if you're gonna modify, I guess. If the suggestion above about trying the BSR program (Bootstrap Recovery program, also called "System Recovery" in app drawer) doesn't work for you, then SBF to stock, which should get you back live, then flash P3 rooted Gingerbread, then Eclipse. That will work. All the links with instructions and downloads have been graciously provided here by our Moderator, The Clown.
As you already know, Eclipse has loaded fairly easily in the past, and wiping data is the recommended procedure. While not absolutly necessary, it has helped others resolve problems they had after loading Eclipse in the past, so I wouldn't be afraid to do it. It's hard for anyone to say for sure why this happened to you this time. The process is a bit touchy, reqireing you to follow the instructions exactly - including, for example, plugging in the phone to a wall charger while using the System Recovery program. Perhaps you inadvertently left out some step along the way.
I dont THINK i did, but hey, i wouldnt doubt it.
Anywho, just for an update, im now pre-rooted GB, waiting for nitro to update the eclipse rom.
Problem is now, i dont have 3g. i tried *228 multiple times
Robin M said:
...the links with instructions and downloads have been graciously provided here by our Moderator, The Clown.
Click to expand...
Click to collapse
Thats MR. Clown to you!
lacross said:
I dont THINK i did, but hey, i wouldnt doubt it.
Anywho, just for an update, im now pre-rooted GB, waiting for nitro to update the eclipse rom.
Problem is now, i dont have 3g. i tried *228 multiple times
Click to expand...
Click to collapse
Whenever I have had to sbf back to froyo, I have always done the *228 before I installed the GB update.
nitwit said:
Thats MR. Clown to you!
Click to expand...
Click to collapse
Opps.
lacross said:
I dont THINK i did, but hey, i wouldnt doubt it.
Anywho, just for an update, im now pre-rooted GB, waiting for nitro to update the eclipse rom.
Problem is now, i dont have 3g. i tried *228 multiple times
Click to expand...
Click to collapse
Reflash the sbf, activate the phone, reflash P3Droids update, wipe data/cache/dalvik from custom recovery, flash Eclipse v0.3/4 wichever now that he has a newer release.... I had to do this yesterday as I wiped when I didnt get a homescreen after flashing Eclipse.
It's not clear to me why some people had a successful webOS 3.0.5 update with Android installed, others didn't. And some people even had stock Touchpads which have problems now after the update? Wow!
If I'm on 3.0.4 with XRON 2.9 installed; what is it I have to do in order to successfully update without having to wipe everything and start anew?
I've read this thread two or three times, plus this other thread, which seems to be ONLY for people who had a failed update, and I'm not entirely sure.
Can someone help with a 1,2,3 kind of scenario?
Thanks!
Well, it seems so far(that I have noticed) that the update will fail if you are using moboot 0.3.3 or 0.3.4. Follow this, and all should be good.
1.) Make a nandroid backup of your android in CWM
2.) Make a backup of webOS(Launcher>Settings>Backup
3.) Make sure you have moboot 0.3.5
4.) Click System Updates in webOS and let it download.
5.) Once finished, try to install.
6.A) Based on my observations, it should install fine.
6.B) If for some reason it doesn't work, that's ok, because you have backed up everything. Follow standard procedure for removing android, and getting webOS back to stock, and install everything(moboot, cwm, android). Then once everything is back, restore your backups.
Sent from my Legendary 2.2 infused device.
FWIW, I did the update yesterday without any major issues.
Prior to the update I had CM7 A3.5 installed and WebOS 3.04. My moboot was still on 0.3.3 as I had never updated it since my initial Android install.
I did the update in WebOS and let it do its thing for a while. When I rebooted the only difference was the bootloader was gone and it would just boot straight into WebOS 3.0.5.
I reinstalled Moboot (0.3.5 this time) and then booted back up into Android and all was fine. I hadn't backed anything up and I hadn't lost anything.
Of course, as always, YMMV.
I was on moboot 0.33 and webos 3.02 and the ota update locked into a boot loop.
Just had to doctor and re-acme CWM, CM7.1 and moboot before restoring my nandroid backup.
Sent from my HTC G2
Thanks guys; I just rebooted to see the menu, and indeed I have the lastest MoBoot (0.3.5). So I am going to back everything up and do this tomorrow.
Thanks for taking the confusion away. I love XDA, but let's be honest, there is so much information, so many threads with thousands of posts, that the whole thing becomes impossible to digest.
Too much information is sometimes worse than having not enough information!
Xaltotun said:
Thanks guys; I just rebooted to see the menu, and indeed I have the lastest MoBoot (0.3.5). So I am going to back everything up and do this tomorrow.
Thanks for taking the confusion away. I love XDA, but let's be honest, there is so much information, so many threads with thousands of posts, that the whole thing becomes impossible to digest.
Too much information is sometimes worse than having not enough information!
Click to expand...
Click to collapse
Good luck bud. Just be sure to back up both as I stated just in case the install doesn't work.
Sent from my Legendary 2.2 infused device.
not to add more confusion to this, but I upgraded without any trouble and I later found out I'm on moboot 3.3. once the upgrade was done I shut off the tp and when I restarted it went straight into moboot. So I'm not sure the moboot version is the critical factor here.
As long as you backup both webos and android I think you should be fine. Although I might ask if you still use webos enough to bother. I didn't see a whole lot new but I didn't spent much time on it.
I failed twice updating, restored palm kernels removed all preware patches and success. Moboot 3.0.4, xron 2.9 were untouched.
Will we be able to run tablet compatible apps in ics?
Sent from my Touchpad using xda premium
sLiKK said:
Will we be able to run tablet compatible apps in ics?
Sent from my Touchpad using xda premium
Click to expand...
Click to collapse
Yes.
Sent from my Legendary 2.2 infused device.
I'm on 0.3.5 and its failed everytime. I unistalled kernels, etc.
zanderman112 said:
Yes.
Sent from my Legendary 2.2 infused device.
Click to expand...
Click to collapse
Can't wait .....
Sent from my SGH-T959 using xda premium
sLiKK said:
Can't wait .....
Sent from my SGH-T959 using xda premium
Click to expand...
Click to collapse
I cant wait for CM9.
Sent from something with a Ｋモ尺れモㄥ.
Well I backed-up everything and did the update. It seems to have worked.
I did get a couple of random reboots, but I got those before. Not sure if the reboots are due to the update or not.
Thanks to all who have contributed to this thread.
it wont load past the HTC screen..
flashed WARM-3.5-evo3d-unofficial-r100.zip
from sdcard.
had down a factory wipe initially.. tried clearing dalvik cache again but still cannot get past htc screen. ugh
correction i flashed to r119.zip
Did you wipe system as well? How long are you giving it at the HTC Splash screen before you decide it's frozen? I haven't been keeping up to date with the Warm train lately, so I'm not sure if there have been any issues with the builds. I know back in the day, sometimes the build bot that myn used would bork a build from time to time and it wouldn't flash. Have you tried flashing any other builds, or just r119?
yes i did a complete wipe initially.. flashed.. got stuck at screen.. i left it there for 2-3 mins with no response.. just hovering at the HTC screen. I have not tried flashing any other roms as I wasnt sure what if any adverse affect this may have on the current problem
tre976 said:
yes i did a complete wipe initially.. flashed.. got stuck at screen.. i left it there for 2-3 mins with no response.. just hovering at the HTC screen. I have not tried flashing any other roms as I wasnt sure what if any adverse affect this may have on the current problem
Click to expand...
Click to collapse
Before you go any further in trying to figure it out, I would let it sit at the HTC screen a bit longer than a couple minutes. I've had it hang there for 5 or 6 minutes on certain sense roms that I flash, especially on the first boot. Give it a solid 7 minutes or so, and if it's still hanging there..then yea it's stuck. After that, I would simply try flashing something else and see if it works. Perhaps you got a bad download as well, maybe try re downloading it.
suggestions on how to move rom to sdcard if phone isnt booting hence PC isnt seeing the drive?
is it possible to go back to stock rom if this doesnt work?
tre976 said:
suggestions on how to move rom to sdcard if phone isnt booting hence PC isnt seeing the drive?
is it possible to go back to stock rom if this doesnt work?
Click to expand...
Click to collapse
Transfer it to the SD card from recovery. I'm not sure what recovery you're on, but every recovery has the feature to mount the sd card from within recovery. It's like USB MS Toggle or something to that nature. In TWRP 2, I think it's under the 'mount' tab.
Did you just try turning it on again yet, and seeing if it will eventually get past the HTC Screen? Again, it could take a bit more than 2 or 3 minutes on the first boot.
EDIT: And yea, you should be able to get back to a stock ROM no problem, or at least get back to a functioning phone, lol. Did you make a nandroid of your stock setup right after you rooted, before you tried flashing warm?
no i didnt make a nandroid backup sadly. im letting it sit for 10 mins before i give up on tyhis version
I don't think that ROM will boot as I'm pretty sure it has no boot image in it. Joelz was doing some stuff on the later builds and removed the bootimage.
Go into the thread and look for Vin's post. He is on the front page or on post 2. He has been the one updating the ROM for Joelz. the last version I knew of was around 01/12 or so?
tre976 said:
no i didnt make a nandroid backup sadly. im letting it sit for 10 mins before i give up on tyhis version
Click to expand...
Click to collapse
Again, you said you're hboot 1.4, right? So you S-offed with revolutionary? Cuz if you're 1.5, then we're missing an important step....
Sent from my PG86100 using Tapatalk
Never mind, 01/27/12 was his last update.
Here ya go, flash this one.
http://forum.xda-developers.com/showpost.php?p=21019364&postcount=279
KB112 said:
I don't think that ROM will boot as I'm pretty sure it has no boot image in it. Joelz was doing some stuff on the later builds and removed the bootimage.
Go into the thread and look for Vin's post. He is on the front page or on post 2. He has been the one updating the ROM for Joelz. the last version I knew of was around 01/12 or so?
Click to expand...
Click to collapse
LOL, that would certainly explain his problems. As I said, I haven't been keeping up to date with the warm team
Sent from my PG86100 using Tapatalk
Yeah, I read his post too fast. I didn't realize he was flashing Sense 3.5 version. Vins version is really nice and clean, he's done an excellent job helping JoelZ and keeping the ROM alive.
k2buckley said:
Again, you said you're hboot 1.4, right? So you S-offed with revolutionary? Cuz if you're 1.5, then we're missing an important step....
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
no it was 1.4 from revolutinary.io.. it has the nandroid option i missed that step in the instructions before flashing. Thanks i'll try the link above
k2buckley said:
Transfer it to the SD card from recovery. I'm not sure what recovery you're on, but every recovery has the feature to mount the sd card from within recovery. It's like USB MS Toggle or something to that nature. In TWRP 2, I think it's under the 'mount' tab.
Did you just try turning it on again yet, and seeing if it will eventually get past the HTC Screen? Again, it could take a bit more than 2 or 3 minutes on the first boot.
EDIT: And yea, you should be able to get back to a stock ROM no problem, or at least get back to a functioning phone, lol. Did you make a nandroid of your stock setup right after you rooted, before you tried flashing warm?
Click to expand...
Click to collapse
gives me a Mount system or mount /data..
oh i see it i mounted sdcard.. oddly windows doesnt see the card tho as a drive still
tre976 said:
gives me a Mount system or mount /data..
oh i see it i mounted sdcard.. oddly windows doesnt see the card tho as a drive still
Click to expand...
Click to collapse
What recovery are you using?
It should be Toggle USB or something like that
i used my wifes phone sdcard to bypass the problem. that flash got me to a loading phone boot now. thanks! but i'm apparently not connecting to sprint. lol. go figure..
fwiw im using twrp 1.0.3
Ok, now you may have to call them ask to have your data reset. There is a specific thing to ask for. It's in the threads on how to root the Evo 3D.
Ok so I'm on Note #3. While setting this last one up, I forgot one step during the root, ROM process. The last 2 I did were fine. But I forgot to make a Nandroid backup of stock ROM. I know.... Dumb rookie mistake but hey, I was excited and since this is my first Android device, I guess I'm still a rookie. So my question is this: is that backup really necessary? I mean there are stock ROM files out there and stock radio files too. So theoretically I could just flash those to go back yes? I'm on Saurom now and except for getting an official ICS update which could be forever coming, I'm doing just fine on the current setup.
Opinions and advice welcome here!
Thanks XDA. No doubt the BEST community ever!
Sent from my SAMSUNG-SGH-I717 using XDA
You can always get back to stock using a downloaded ROM from XDA. No worries.
There are threads in the development section with stock AT & T tar files for odin which will put it exactly as it was out of the box.
Sent from my SAMSUNG-SGH-I717 using xda premium
I never nandroid.
Odin and tibu make that pointless.
studacris said:
I never nandroid.
Odin and tibu make that pointless.
Click to expand...
Click to collapse
I don't know about that..
restoring a hand takes about 10-15 minutes; restoring with odin/tb, can take up to 45 minutes, so, if you screw something up, and just want to quickly go back to how you were b4 the screw up, restoring a nand is still the fastest, easiest way..
but, yeah, odin/heimdall and TB is pretty easy too!
wase4711 said:
I don't know about that..
restoring a hand takes about 10-15 minutes; restoring with odin/tb, can take up to 45 minutes, so, if you screw something up, and just want to quickly go back to how you were b4 the screw up, restoring a nand is still the fastest, easiest way..
but, yeah, odin/heimdall and TB is pretty easy too!
Click to expand...
Click to collapse
What?? What Odin do you use? Mine flashes to stock in 3-4 mins, 45 mins is crazy talk. And I just keep the rooms in my SD! They flash faster than nandroid!
odin/heimdall is fast; its restoring 100-200 apps with Titatnium Backup that takes all the time...
kimtyson said:
You can always get back to stock using a downloaded ROM from XDA. No worries.
Click to expand...
Click to collapse
Yeah, that's what I figured but had to ask. Now, knowing all this, should I Nandroid backup for my current ROM which is Saurom 7.1? If I did, could I then flash an ICS ROM and if I didn't like it, backup from the Saurom 7.1 backup I made?
Sent from my SAMSUNG-SGH-I717 using XDA
dakleenupman said:
Yeah, that's what I figured but had to ask. Now, knowing all this, should I Nandroid backup for my current ROM which is Saurom 7.1? If I did, could I then flash an ICS ROM and if I didn't like it, backup from the Saurom 7.1 backup I made?
Sent from my SAMSUNG-SGH-I717 using XDA
Click to expand...
Click to collapse
Yep thats exactly what I did. Went from 7.1 to ics and then back to Surom. It's like you never left. Just be sure to follow all the instructoins while installing ics
Sent from my SAMSUNG-SGH-I717 using xda premium
truth77 said:
What?? What Odin do you use? Mine flashes to stock in 3-4 mins, 45 mins is crazy talk. And I just keep the rooms in my SD! They flash faster than nandroid!
Click to expand...
Click to collapse
I have to respectfully disagree with you on this one. I would highly recommend you make a nandroid backup before flashing any new roms. Nothing is faster, easier, more comprehensive, and safe than nandroid. It restores your phone back to an exact copy of itself at that moment in time. All your data, settings, and apps go with it, not to mention your nice functional (and hopefully stable) rom. Its the best protection when flashing custom roms. And plus you don't have to worry about broken links in old stock rom posts.
Flashing via Odin means you have to use Titanium Backup to restore apps and data. That takes a minimum of 20-30 mins for anyone with more than 100 apps. Plus, if I'm not mistaken, that also means you have to take the time out to place them back on their respective homescreens or folders, and redo all your custom settings and so forth. That takes another 20-60 minutes, depending on how particular you are (and I'm particular).
That being said, its not a critical step in the flashing/rooting process. It's just a safety net for when you inevitably fail (cause we all do...im sure even the best of devs have soft-bricked a phone...if you haven't, it just means you haven't flashed enough... )... No worries if you forgot...if you have an old nandroid you can use that, or go back to stock via one of the posted roms....