Related
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.
Hey Guys, I don't think this has been posted before, so thought I'd share. I managed to get CM9 working with my Bell XT860 *without* needing to change up the phone using another country's fastboot file.
My phone was Bell 2.3.6, rooted, otherwise stock. I used Hashcode's safestrap to make a nandroid backup and install the latest patched CM9 from Rick#2 available here: http://forum.xda-developers.com/showthread.php?t=1465297
I actually didn't expect it to boot up, but thought I'd give it a go since even if it failed the worst that could happen is that I'd have to SBF anyways.
At first it was a black screen, I had to do a battery pull. After the battery went back in, it started booting up with the animation screen, which showed multiple times over about 5-10 minutes. Then the phone started up Ice Cream Sandwich!
I've been testing it out a bit.. not much yet, but Market is working, data 3g seems to be working 2700 kbps up / 1341 kbps down (with a server that's super far away, 321ms ping). GPS is working... Wifi good. Camera does not work.
Wow, I never expected this. I think this gives hope to those who want to try out Ice Cream Sandwich but still want the ability to go back to stock. Or am I missing something?
ncho2233 said:
Hey Guys, I don't think this has been posted before, so thought I'd share. I managed to get CM9 working with my Bell XT860 *without* needing to change up the phone using another country's fastboot file.
My phone was Bell 2.3.6, rooted, otherwise stock. I used Hashcode's safestrap to make a nandroid backup and install the latest patched CM9 from Rick#2 available here: http://forum.xda-developers.com/showthread.php?t=1465297
I actually didn't expect it to boot up, but thought I'd give it a go since even if it failed the worst that could happen is that I'd have to SBF anyways.
At first it was a black screen, I had to do a battery pull. After the battery went back in, it started booting up with the animation screen, which showed multiple times over about 5-10 minutes. Then the phone started up Ice Cream Sandwich!
I've been testing it out a bit.. not much yet, but Market is working, data 3g seems to be working 2700 kbps up / 1341 kbps down (with a server that's super far away, 321ms ping). GPS is working... Wifi good. Camera does not work.
Wow, I never expected this. I think this gives hope to those who want to try out Ice Cream Sandwich but still want the ability to go back to stock. Or am I missing something?
Click to expand...
Click to collapse
If you bootloop while in safe mode DON'T SBF. Safestrap works by renaming /system to /systemorig and making /preinstall your new /system.
This means when you're in safemode you can always access recovery. So if you bootloop just battery pull to get out of the loop and then you'll e able to hit menu and enter safestrap. Either flash a different rom or return to nonsafe. If you are using safestrap 1.08 and not 1.08d you can't even flash nonsafe mode (1.08d is tweaked to allow advanced user to flash over their nonsafe, for example I have both liberty and eclipse roms on my phone no stock at all)
Also first boot of a rom always takes a long time. After that it should boot much faster
As another note if you do manage to screw up /systemorig somehow you can use motofastboot utility to flash just the system.img part of the SBF package. This will only replace the rom, then you just reboot, install safestrap and restore you backup.
Sent from my XT860 using xda premium
Wow, thanks for the warning, very good information! It's so good to be able to try some custom roms again. I'm out of CM9 already for lack of camera but so far am really impressed with Liberty, it's like my phone has come to life again. Very quick and responsive, amazing ability to customize as well.
Endoroid said:
If you bootloop while in safe mode DON'T SBF. Safestrap works by renaming /system to /systemorig and making /preinstall your new /system.
This means when you're in safemode you can always access recovery. So if you bootloop just battery pull to get out of the loop and then you'll e able to hit menu and enter safestrap. Either flash a different rom or return to nonsafe. If you are using safestrap 1.08 and not 1.08d you can't even flash nonsafe mode (1.08d is tweaked to allow advanced user to flash over their nonsafe, for example I have both liberty and eclipse roms on my phone no stock at all)
Also first boot of a rom always takes a long time. After that it should boot much faster
As another note if you do manage to screw up /systemorig somehow you can use motofastboot utility to flash just the system.img part of the SBF package. This will only replace the rom, then you just reboot, install safestrap and restore you backup.
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
hi there ,i using 1.08d and try to flash willis111's bell 2.3.6 rom ,and I want to flash it to the orig system ,not the preinstall ,but every I flashed it ,the my xt860 restart and into the ori rom(2.3.5 bra),not the bell 2.3.6.
here is what i do
1 restart my xt860,and press menu
2 in the safestrap,wipe date ,format system ,then in advance flash .zip nonsafe
3 restart my xt860,and still the 2.3.5 bra rom ..
sorry for my bad English ,and great thx
---------- Post added at 04:44 AM ---------- Previous post was at 04:29 AM ----------
Endoroid said:
(1.08d is tweaked to allow advanced user to flash over their nonsafe, for example I have both liberty and eclipse roms on my phone no stock at all)
Click to expand...
Click to collapse
all I want to know is how to ....thxxxxxxxxx
That's how it should be done
Last time I flashed my /systemorig was before 1.08d had been released so I did it co ming off a fresh fastboot flash using bootstrap to flash liberty, then installed safestrap. I haven't found a rom to replace liberty in my /systemorig yet so I haven't tried the advance flash yet. Sorry.
Sent from my XT860 using xda premium
newaxis said:
hi there ,i using 1.08d and try to flash willis111's bell 2.3.6 rom
Click to expand...
Click to collapse
Hi
i' desperate for willis111's bell 2.3.6 rom but can't download from rapidshar, there is a way you upload the file to non-repidsher site?
Thanks ahead
Current phone information should be attached. Short form is, I'm using the Gummi 1.2.0 rom, put onto my phone after using safestrap (and following the instructions to make a backup before doing so). Safesystem is enabled.
Two backups: located on my external SD card
nonsafe-2012-05-26.07.52.54/
safe-2012-05-27.08.06.28/
Safestrap recovery v1.09 (afraid to update to 2.0 without breaking more stuff)
What I'm looking to do is return my phone to working stock, which I believe was Gingerbread 2.3.6. That said, every time I've touched this thing trying to go back, I've black screened it. I don't live in an area with 4g (screw the mountains, and their 1x service), so any attempts to connect to the 4g network for any part of the process will require me driving into Pennsylvania, 30 minutes away. I've heard before that you can't return from the ICS leak to the Stock for the Droid 4, for various reasons (but i believe the important one was it was a later firmware and it isn't a process designed to go backwards)
I'd like to know if thats still the case currently, or if something has changed. I'm getting shaky wifi/data/cell reception up here, and its flawless back on stock. Hell, I've got an old razor as an emergency phone that's flawless up here. Next time I'll do more research for this stuff I was a proud OG droid owner, and ran cyanogenmod on it before the vid card fried one evening. Thought the droid 4 would be a good deal, but I've had nothing but trouble with the roms on it.
All that said, I can simply smash and return this droid if its the only way to get a stock one back, but I don't like destroying useful and good technology when I can help it. Besides, I like fixing the problems I create.
Thanks for the help XDA, either way.
-- TheChaoticDoctor
Did you flash the leak ICS from Motorola or did you use Safestrap and flash Gummy ICS?
If you flashed the leaked ICS, there is no going back. You will need to find get the files to flash the partial .219 system back so you can run the .206 leak update again.
If you just used safestrap to flash Gummy 1.2.0 then you can use the .219 flash files to completely re-do your phone.
Currently there are no ROMs to flash if you are on the leak, Hashcode just released his Safestrap 2.0 to do so but still nothing to flash. All the current ICS ROM builds are for the stock phone running the Gingerbread Kernel.
Sorry about the delay, was off camping. I rooted the phone first on gingerbread, then eventually installed safestrap and flashed the gummi rom. Can you (or someone else) walk me through the steps for flashing the .219 files and then flashing the .206 files?
TheChaoticDoctor said:
Sorry about the delay, was off camping. I rooted the phone first on gingerbread, then eventually installed safestrap and flashed the gummi rom. Can you (or someone else) walk me through the steps for flashing the .219 files and then flashing the .206 files?
Click to expand...
Click to collapse
You should probably go up to .208, that's the latest leak. Make sure to use rootkeeper, and follow all the instructions. So far I haven't lost root, but be aware I'm stuck on .206 because I don't want to lose root....
Look here for more info:
http://forum.xda-developers.com/showthread.php?p=26311439
Sent from my XT894 running ICS
First of all, it sounds to me like you've just flashed a ROM, not flashed the leak. If that is the case, you can just toggle the safe mode in safestrap to get back to stock. Safestrap lets you toggle between stock and the ROM. It is pretty awesome because you can play with the ROM and then go back to stock whenever you need to.
If you HAVE flashed the Motorola leak (as opposed to just a ROM) you are SOL.
If you haven't flashed the Motorola leak and just want to get back to factory conditions, you'll have to flash via RSDLite. That info you should be able to find here:
http://forum.xda-developers.com/showthread.php?t=1622256
Honestly I WOULD NOT flash the leak at this time. IMHO, it doesn't really offer enough to risk getting off the upgrade path forever, and losing the ability to flash back via RSDLite.
Yesterday i flashed if i remember the 223 leak. I flashed from 905, rooted with razor ics root. I went in to sqlite and changed the setting to get the free hotspot and than rebooted. Now on my top banner the wifi icon and my signal icon stay gray! They never got to blue! I have data service but the are always gray. Also later my signal strength went noticeably lower than before i flashed! Any help would be great! ...... also i just noticed that my browser is talking! Had chrome installed, couldn't find anything in the settings so i uninstalled and went to reinstall. Play store says that NOW its not compatible with my device! And now my stock browser is talking to me! PLEASE HELP!!!!!!
Sent from my DROID BIONIC using xda app-developers app
One thing at a tine.
Browser talking - check you're accessibility settings, see if Talkback is enabled.
For the GNow, that does not come with the ICS leaks. Either you installed an unofficial leak, or you installed GNow before the leak, or you installed it after the leak. There is a thread in XDA that details how to get GNow working in ICS.
For the sqlite mod, change the string back. Foxfi is free, doesn't require root, and works.
Sent from my rooted BIONIC running ICS 6.7.235 via Tapatalk 2
Thanks, I FXZed back and reloaded everything no sqlite no root and everything seems good! Still lost data for a while last night but l don't have great service at home! Might root later today, we'll see!
Sent from my DROID BIONIC using xda app-developers app
I do have one more question! If i go from .233 can i just flash .235 or do i need to FXZ again?
Sent from my DROID BIONIC using xda app-developers app
Each time you try to flash a new ics leak you HAVE TO FLASH BACK TO 902/905
if you flash to 235 YOU CAN NOT FLASH BACK TO 902/905 but you can only move foward
I recommend you stay on 232 unless you dont care about flashing back to gb
bhp117 said:
Each time you try to flash a new ics leak you HAVE TO FLASH BACK TO 902/905
if you flash to 235 YOU CAN NOT FLASH BACK TO 902/905 but you can only move foward
I recommend you stay on 232 unless you dont care about flashing back to gb
Click to expand...
Click to collapse
If people are going to keep stating this, then they need to qualify it with the fact that you can still install GB roms on the safe side. You can even put .905 stock back on safe or unsafe using the backup restore within Safestrap (if you have the stock .905 backup file that is). There's a lot of scare about .235, but all you have to do is change how you flash and you don't "lose" anything. **Wonder if I will have to make another tutorial for people on .235...goodness**
What? We have a locked boot loader... can't run .235 on one side and .905 on the other lol
What he said was correct.. you cannot use RSD lite to fxz back to .902/.905 with .235 so unless you're a fool don't make the move... 232 is great
Finally Iced Out Legitimately... Bionic is back
You cannot go back to fully stock Gingerbread anything once you flash .235 so for the sake of newer users being thrown off the upgrade path and not being able to FXZ back to .905 we all should just leave it at that.
cnorman76 said:
I do have one more question! If i go from .233 can i just flash .235 or do i need to FXZ again?
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
I think you've gotten the gist of the info, but I'll reiterate.
You have to be on .905 to flash any of the current ICS leaks (and there is a 99% chance of that being true with any future leaks / soak tests / final OTA b/c .905 is the current official OS version for the BIONIC.
You can flash .235 off of .905, but once you are in .235, you cannot restore your phone to .905 via FXZ, and you cannot try to fool the system with a simple Nandroid backup of .905 that you restore over .235. The reason is that the update script also looks to patch several things.
First of all, no update script ever includes the boot.img of the version that is being installed. It includes a patch file that requires you to have either the boot.img of the system that you are coming from, or the system that you are going to. Any other version and it throws up an error and does not allow the update to continue. IOW, if, say, leak .241 comes out, and you're on .235, you have no way to getting .241 without using a method to make the .241 kernel. You cannot flash the .905 kernel onto a .235 system - it trips eFuse and bricks the phone. You have no .241 kernel to install b/c, as I said, the update only includes a patch file, not the full kernel.
Second, even provide that you pass that (which in theory you might as you are on a .235 leak with only .905 /system restored from a Nandroid backup, and if the new leak uses the exact same kernel you'll pass), it also verifies every file in /system that it is going to patch, along with every file in /preinstall that you are going to patch. Restoring that Nandroid backup does wonders for having the .905 /system on your phone, but the current leak you are on has already patched several files in /preinstall, so those signatures will not match, and you'll fail the verification step, and ultimately the update will fail.
For the record, a typical FXZ flashes 17 different partitions on our phones. Nandroid backups on the BIONIC typically can only make backups of 3-4 of those partitions. We have figured out ways to grab a few more of them, but we are still stuck at grabbing a couple of them, and there are 4-5 that we cannot grab from our phones at all.
Since the folks with RAZRs went through something very similar in May and June, mattlgroff figured out a way to fool the update into thinking you have all the components correct in place that need to be there, and the update proceeds. Thus far, after bricking my phone trying to FXZ back to .905 / .902, I used a script to get back on .235, then verified that the move to reinstall the .235 leak works. If another leak is found, then I can test the second part of the script, that which allows new leaks to be installed. The script does not allow any older ICS leak to be installed, and currently there is no way to go back to a previous leak nor a previous GB stock FXZ at all. Even if we had a .223X ICS FXZ or a .22X ICS FXZ or a .230/.232 FXZ, they would not work on a phone that has been updated to .235.
That is why we're saying hold off unless you're 100% positive you're willing to accept the risk - this is way beyond the risk associated with rooting your phone. If Motorola makes the next leak force the phone to have components from .905 that we cannot flash into a .235 upgraded phone, I (and several others that have taken the plunge) might be permanently stuck on .235 until an FXZ for a version of ICS higher than or equal to .235 is released. And that typically takes 6-8 weeks.
HTH
crobs808 said:
If people are going to keep stating this, then they need to qualify it with the fact that you can still install GB roms on the safe side. You can even put .905 stock back on safe or unsafe using the backup restore within Safestrap (if you have the stock .905 backup file that is). There's a lot of scare about .235, but all you have to do is change how you flash and you don't "lose" anything. **Wonder if I will have to make another tutorial for people on .235...goodness**
Click to expand...
Click to collapse
Make a guide if you will and state the proper steps to do so
I had one issue with. 232. I noticed the lock screen is useless. My home button unlicked the screen plus the notification bar scrolled down to unlock also lol. Other that that it amazing
Sent from my DROID BIONIC using xda app-developers app
dblkspecial said:
I had one issue with. 232. I noticed the lock screen is useless. My home button unlicked the screen plus the notification bar scrolled down to unlock also lol. Other that that it amazing
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
i noticed that the other day when I got a text while my screen was locked. I naturally pulled the notification bar down and noticed that I didn't unlock my phone at first. Tried it just now and it's unlocking without swiping to unlock. My home button doesn't do anything howerver.
I recently rooted my bionic, then, thanks to crobbs, flashed ics .232 onto it. during this whole process i safe-strapped a recovery to my sd-ext. i then heard that ics should come out no latter than Sept. 30th.(if Motorola and Verizon come through) so i decided id go back to the stock version so i could get the ota update whenever it came out. i went back to stock using the fxz tools and im back to .905 GB stock un rooted. (or so i hope, not to sure how to tell if im on the ota)
***My main question.....since i still have my very first original safestrap recovery saved....if i was to root right now and use that original safestrap recovery, would i get everything i had from my old phone back just the way i had it when i first safe-strapped?