Here's the story:
A while back, I rooted my Nexus One without unlocking using the bait and switch method, and had been using various custom ROMs.
Recently, the power button hasn't been working well, so I called HTC to get a swap. Obviously, before sending my phone back, I need to unroot it.
I tried to restore my phone using the method in the XDA guides, but it hung on each step, and it didn't actually do anything. So, I flashed the non-rooted stock ERE27 through ROM Manager (this, I suspect was a huge mistake.)
Now, I have an rooted phone, that fails on any update attempt and so is stuck on 2.1, and worse, Clockwork Recovery is still on there. I've tried to unroot my phone again using both the bait and switch method, and the freenexus method, but both have run into errors. I've also tried installing Universal Androot and clicking Unroot, but it just tells me my phone isn't rooted.
So, I can't root my phone to attempt to flash the recovery, and I can't find a way to remove Clockwork Recovery, but I need to send this phone back to HTC within the next 7 days, or else I'm gonna be out $530.
Any ideas?
First: hate to be a douche, but someone's gotta say it: this is the wrong subforum for a question thread. Take a quick glance over the rules stickied at the top of the forum. There's a Q&A forum for things like this.
Second: HTC has typically honored the warranty for known hardware problems (of which the power button is probably the biggest) even for unlocked/rooted devices. They find for me, no problems. So relax.
Last, try using ClockworkMod recovery to flash CM 6 stable, then from that ROM, try flashing back to stock recovery. After that you should be able to flash a stock OTA ROM. You can't change recovery without root access, which you can't get on a stock ROM. So you have to change recovery first. And on your new phone, you should really just fastboot OEM unlock. Trying to deceive HTC makes them not want to give us this option anymore.
Yup no worries I had to send mine in because the trackball got stuck and they got it under warranty ... I had my phone running a custom recovery and rom and they didn't even ask about it.
Sorry if there is already a thread on this, I looked and couldnt find one....my phone was rooted and i followed step by step directions on here to get the 2.2 update and everything worked great...then i opened up my apps to find out my superuser is gone....went to the market and downloaded rom manager and it says i dont have root access. Sorry to bother you guys i know your busy, but if anyone can help i would really appreciate it!
You need to root your phone again. Any time you flash it won't be rooted unless you install a rom that has it packaged in.
Sent from my SAMSUNG-SGH-I897 using XDA App
Ive tried to root again and every time I try it says..."Error cant find signature" or something to that effect
You need to do a little more research Watcher. I'll explain it to you.
Froyo uses 3e recovery. Eclair uses 2e recovery. What does that mean you ask? You can't use the update.zip method to root your phone anymore. You need to go here: http://forum.xda-developers.com/showthread.php?t=803682 It will make the process nice and easy for you.
thanks man, worked like a charm...when i went to install 3rd party apps at the end it says failed cant find sqlite3....any suggestions?
Its a more involved process for you. You need to find the original thread for rooting 2.2 via adb and push it onto the phone. Download the attachment and follow the directions for pushing it onto the phone, changing permissions and so forth. If I was at the computer I could give you the link.
Sent from my Captivate
Here's the link: http://forum.xda-developers.com/showthread.php?t=797397
Disclaimer: You may brick your phone. NOT for AT&T
Reminder: Make sure your phone has enough battery charge to flash this, it's larger than normal.Hi,
Here is a huge CWM zip that restores your Bell phone to stock 2.2.2. I have tested it on my phone several times and it worked perfectly, there is still the chance that something may go wrong, but I am feeling confident in it.
What this does is similar to my app or scripts, it puts my backup of Bell's 2.2.2 partitions on your phone, but instead of using dd, it uses tenfar's CWM and flash_image. Some partitions are HUGE, and take a while, your phone is not locked up.
This has been updated to include the Bell bootloader for 2.2.2 and the radio for 2.2.2.
EDIT: This has been updated again to ram fix the boot and recovery partitions if there is a ram problem.
It writes to partitions 1, 2, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 17. 3 is left out because it's your pds partition, and data and cache have no relevant content. You must factory reset after using this to clear those. So, that's your boot, recovery, system, webtop, cdrom, preinstall, and several other partitions. This is to get back to stock Bell 2.2.2, it's not just a boot/system replacement, if that is a fruitcake, this is a gobstopper.
Please note: This restores your Bell phone to stock condition, that means you won't be unlocked, CWM will be overwritten with the stock recovery. It will be just like you bought it. If you want to keep flashing things in CWM with the unlocked bootloader, then immediately after flashing the stock zip, flash the unlock and fix zip. If you don't then you will have to reflash an unlocked bootloader, and reflash CWM recovery, which is time consuming any annoying, it doesn't mean you will be permanently locked again. I had to spell that out to the folks that don't really understand this stuff. At all.
If you want root after installing this, just install Superuser.apk from the market.
Bell_FR_2.2.2.zip (Froyo not France)
(md5 e431b4cc3ba7e3a27b6aad6982a31066)
Cheers!Oh, I forgot to mention, this is not quite stock, there are su and sudo binaries in /system/bin. Just install Superuser.apk to be rooted. they haven't been a problem for doing an OTA yet, but they are easy enough to remove if it comes up.
unlocked-fixed-Bell-2.2.2.zip
Mirror: unlocked-fixed-Bell-2.2.2.zip
Damn, nice work as always, man! This should come in handy for lots of us Bell Atrix users that feel left out. Lots will appreciate this!
When you say without amnesia are you talking about the bootstrap or are you talking about a user who is using the bell_ihop and then installs cwm and then reboots and looses recovery?
So a 2.3.4 bootloader and radio will work find booting a 2.2.2 bell ?
Will you eventually be able to compile a zip for Bell gingerbread?
IrshaadH said:
Will you eventually be able to compile a zip for Bell gingerbread?
Click to expand...
Click to collapse
the problem would be hosting it, not sure how he would be able to do that.
akurit said:
When you say without amnesia are you talking about the bootstrap or are you talking about a user who is using the bell_ihop and then installs cwm and then reboots and looses recovery?
So a 2.3.4 bootloader and radio will work find booting a 2.2.2 bell ?
Click to expand...
Click to collapse
keeping in mind that this is only for the recovery with unlocked devices, what he means is that the CWM recovery that tenfar put out has a problem with int'l phones (pretty sure it's all int'l) where IN recovery (not just the normal ROM, like the problem we had before) only 300 and some mb of RAM is available. since this zip is over 300mb, it can't all load into your RAM properly with normal recovery.
NFH found this bug, and patched recovery for us so as to fix the RAM problem. the two files attached are fixed recoveries for the two separate MBR versions of int'l devices.
to find what version you should use, connect to phone via ADB and then
Code:
adb shell
su
cat /proc/cmdline
and then search for the part of the output where it says "tegrapart=mbr:" and read that. it should have either "1100" or "d00" somewhere in it, use the CWM zip attached that has your respective output.
hope that clears up your question, if you have any further ask them in here.
IrshaadH said:
Will you eventually be able to compile a zip for Bell gingerbread?
Click to expand...
Click to collapse
Hi,
I believe y2whisper may be working on something like that. The point of getting back to stock 2.2.2 is to be able to apply the final OTA for Bell GB. Certainly something similar can be done for any firmware you want to flash.
Cheers!
i flashed the d00 and I do maintain unlock however no cwm just stock recovery with no menus.
tried it again and it work
but seems like i have to fastboot flash it each time i want to use recovery
akurit said:
i flashed the d00 and I do maintain unlock however no cwm just stock recovery with no menus.
tried it again and it work
but seems like i have to fastboot flash it each time i want to use recovery
Click to expand...
Click to collapse
I know what you are talking about, but I got that with a stock bootloader.
If you are going to be using CWM recovery with this 2.2.2, then flash the boot file for d00 as well, it gives you the ram fix and for some reason it doesn't cause that issue.
Cheers!
Here is an international CWM recovery, it detects the 1100 vs d00 tegraparts and installs the right recovery for it.
CWM_INT_Recovery.zip
(Just use it with whatever CWM recovery you are using now, it will update it with the ram fixed one.)
NFHimself said:
I know what you are talking about, but I got that with a stock bootloader.
If you are going to be using CWM recovery with this 2.2.2, then flash the boot file for d00 as well, it gives you the ram fix and for some reason it doesn't cause that issue.
Cheers!
Here is an international CWM recovery, it detects the 1100 vs d00 tegraparts and installs the right recovery for it.
CWM_INT_Recovery.zip
(Just use it with whatever CWM recovery you are using now, it will update it with the ram fixed one.)
Click to expand...
Click to collapse
ohhh, that's a nicely scripted installer you got there. i think that would be quite handy for int'l users trying to flash custom kernels, is it possible to apply that script to select the correct boot.img out of two for the right tegrapart? if that's possible i think you should hit faux/edgan up with that script and let them apply it to their int'l kernels so users can just use on CWM to install it.
raybond25 said:
ohhh, that's a nicely scripted installer you got there. i think that would be quite handy for int'l users trying to flash custom kernels, is it possible to apply that script to select the correct boot.img out of two for the right tegrapart? if that's possible i think you should hit faux/edgan up with that script and let them apply it to their int'l kernels so users can just use on CWM to install it.
Click to expand...
Click to collapse
Hi,
Sure, it's just replacing the word recovery with boot and having the right boot images in the file.
Cheers!
yes its zipping now. off to bed but tomorrow I will back up my stuff and attempt to flash to see if it works.
@akurit
I forget off the top of my head but there is a file that you just have to delete to prevent that. the file just flashes the old recovery on every reboot. get rid of that and you will be fine.
Awesome work! This makes it much easier to get back to 2.2.2
Its installing now!
now at some point the install stopped and I think I saw it say status 0 and then recovery rebooted. so I am not sure what happened there.
ive rebooted with no problems. and its uploading now. if someone is willing to test this out (a bit difficult for me since I am already on 2.3.4) let me know. and will send you the link. would like to see a proper install before i share it with the masses.
This is why hehee
tenfar said:
......
Please Remove install_recovery.sh located in your /system/etc/ ,so that the recovery will not be overwrite to stock one.........
Click to expand...
Click to collapse
now it remains unlocked and I have recovery even if i reboot... but the ram issue still exists
y2whisper said:
Its installing now!
now at some point the install stopped and I think I saw it say status 0 and then recovery rebooted. so I am not sure what happened there.
ive rebooted with no problems. and its uploading now. if someone is willing to test this out (a bit difficult for me since I am already on 2.3.4) let me know. and will send you the link. would like to see a proper install before i share it with the masses.
Click to expand...
Click to collapse
i could test it for you, i should be able to tell if it works alright or not, since i'm starting from an AT&T build of 2.3.4. would i have to head back to stock Bell using Gobstopper before i use your package too? i got a whole buncha time on my hands this week, so i should be able to test it however you want.
anyone try flashing the bootloader and radio?
kevnb said:
anyone try flashing the bootloader and radio?
Click to expand...
Click to collapse
Hi,
I have tested it, no problems, but went back to IHOP and the ram-fixed bootloader for 2.2.2 in the OP so recovery will work.
Also, the file install_recovery.sh located in your /system/etc/ doesn't exist in the Gobstopper, so that isn't causing recovery to be generated by patching boot.
Cheers!
So its when flashing the webtop that the install stops with the error code. when i boot up all is ok but a reboot later and recovery is gone (as in you select it and it just boots into android). reflashing cwm recovery fixes that.
I have tried swapping the webtop files to no avail. going to keep trying. any ideas are welcome
y2whisper said:
So its when flashing the webtop that the install stops with the error code. when i boot up all is ok but a reboot later and recovery is gone (as in you select it and it just boots into android). reflashing cwm recovery fixes that.
I have tried swapping the webtop files to no avail. going to keep trying. any ideas are welcome
Click to expand...
Click to collapse
Hi,
What recovery are you using, if it's not ram fixed you are going to run into situations where you don't have enough space to flash it.
Cheers!
ahhhh.
you know i was wondering if that was it. I even repackaged the recovery thinking it would be the cause.
I don't believe I was ram fixed at the time of the backup. So I am thinking either, have custom recovery flashed in that spot, or change the order to where recovery gets flashed after.
Hi everyone.
I have an Optimus 2x, and when i updated it to 2.3.4 i could not use superoneclick to root my phone instead i found an answer on how to root it.
I needed to install cwm 5 and after that busybox and so on, and it worked, it was rooted.
Now i have a other problem, i have an update on my phone and when i click on installing it starts to reebot then it comes to cwm screen, there i'm stuck.
I have tryed everything there trying to update it but nothing works.
So now i am wondering if any of you can help me?
Got any idea what i can do to update or what i am doing wrong?
//Szander.
Ok, so now i did a recover so i get back my phone as it was before i installed cwm and tryed to update, it did work fine.
Until the update was done, then it stopped, and nothing i did worked the little android just stand there and looked at me.
So what now, i removed the battery and hoped for the best, now the phone would not bot at all.
After a few tears and a few swear words, i thougt about something, maybe i could use nvflash to get it all back as it was ???
I tryed closed my eyes and after a few minutes i could restart my phone and it loaded as useall, but the update was gone, ofcourse.
So now back to square one again.
Sigh (
Hi Szander,
So just to be completely clear, you're back at a perfectly stock 2.3.4 unrooted ROM and you want to root it, right?
Why not trying to follow cyanogen wiki to root it?
LarsPT said:
Hi Szander,
So just to be completely clear, you're back at a perfectly stock 2.3.4 unrooted ROM and you want to root it, right?
Why not trying to follow cyanogen wiki to root it?
Click to expand...
Click to collapse
No.
I have cwm, and its still rooted.
What i want is to get rid of cwm so i can update to the latest update wich is v20q.
I have tryed this with recover but its only working on froyo, i belive i read it somewhere.
And when i recovered my phone then the problem really started, but thats fine now.
And as an plus is that now when i run LGMobileupdate tool its saying that i have v20q but in the phone it says that i still have v20I.
Weird.
I have read alittle more and (if i got it right) found out that i might just need to use smartflash on the phone via my computer to get rid of cwm and get a perfectly stocked phone again.
So can you help me please, hoping that you understand my problem.
Yup, as far as I know you are correct. To get your phone back to stock you need to flash a stock ROM using either smartflash or nvflash. I haven't done it so I can't guide you through it personally, but search this forum you should find the relevant threads easily enough.
If you have trouble finding it let me know I'll help you searching.
EDIT: By the way, thanks for Meshuggah, one of the best bands ever I should visit Sweden sometime
I'm pretty new to this, and I didn't fully understand the whole rom, flash, kernel stuff but I did it anyway, seeing as I jailbroke my ipod when I knew next to nothing about that kinda stuff...
Well, I rebooted into recovery using rom manager, and it didn't reboot. It shut off, but didn't turn back on.. I tried to turn it back on myself and only the lg logo would appear..
So I googled what was happening to my phone. It's either in the 'boot loop' or bricked... i don't know the difference, or if there's even one but what the hell do I do to fix it? ..
I tried holding down the power, 3D and volume down button but the recovery menu doesn't come up... and I really don't wanna download any more programs to fix it :/
Im sorry but you must now have to download some programs to fix. You follow this guide http://forum.xda-developers.com/showthread.php?t=1491870
And Flash your firmware using the kdz files. If you have anymore problems feel free to ask.
Sent from my LG-P925 using xda app-developers app
This worked for me
Sorry about the phone. This worked easier for me:
http://forum.xda-developers.com/show....php?t=1448803
BUT I already had .bin and .fls files on my computer, not .kdz. I suppose either way is about the same. It does feel like you are groping in the dark for a while, then it all comes together. And when you are done learning all about it you can fix all your friends' Androids for a bunch of Starbucks coffee or whatever.
:cyclops:
Also, be careful with custom recovery (CWM/TWRP); just be sure it works with your particular phone first. That's what 'bricked' mine; I had custom recovery not really compatible with the setup I have going on my Thrill and got bootloop. I had to reflash the ROM image as in above link or the one in the other poster to get out of it.
whoops
sorry guys ive been busy with work lately ill have to give that first option a go seeing as i basically have nothing left of the old system
ill update after i try it.
That last post of mine is old. This is my LG Flash Tool guide:
http://forum.xda-developers.com/showthread.php?p=39269819
Drivers are tricky to set up the first time you try it, but Flash Tool is more reliable in my opinion.
BTW P920 and P925 are the same device. Thrill is just the US AT&T branded version (who I have never used; I unlocked mine with a Straight Talk SIM). I have a Thrill and some small numbering inside the battery cover says "P920."
update
ok i just now have the time to try to restore my phone.
id like to get it back to rooted stock ics as its sole purpose will be games/other non important junk and id like to still have the 3d.
the phone currently has no os and boot to twrp i also dont have any of my old recovery files so im essentially starting from scratch on my new laptop.
where do i go from here?
can i just download a zip or recovery and and use the restore/install feature on twrp?
Follow the guide to install rooted stock ICS by way of LG Flash Tool.
bricked lg thrill 4g
my phone is bricked the only thing it has is cwm recovery
i need to be able to get an os on it ..i dont can if it stock or rooted gb or ics i just need it done.and the above link's files no longer work... i need a no bs way to get this fixed ..any takers?