Well I had a Liquid E for less than a week and I actually wanted to root it, but now it's like a dead phone to me.
I rooted it, then used Nandroid backup on it
After that, rooted and tried the LCR.
I didn't really flash the LCR, just used the tester to see if it works
Somehow it stucked, I removed the battery and I got in the recovery mode again with no luck
Checking root system just hands, Nandroid is taking forever to restore.
*******FIXED : Just reflashed the LCR directly without testing and it worked fine. Would like to ask though, why does the testing didn't work?
Related
Damn near burst a vessel earlier, doods. I had downloaded the newest darchdroid, and was looking forward to some oc'd, jit-enabled, vanilla goodness. I booted into recovery, wiped everything, and tried to install. Ut oh! Got a bad download. No es bueno. But, imma careful sob, so I have like 4 nandroids sitting on my SD....2 from flipz' latest betas, 1 from the original fresh toast, and one from dc 2.0.8. And it was a damned good thing, too! The backups off the newest would NOT boot. They kept looping. I tried rewiping, nothing. No good. Finally, I tried one of the other nandroids, and It worked first try. Because I'm a curious person, I then immediately booted to recovery and tried my most recent nandroid (the first one that bootlooped). This time it worked like a charm. Consider this evidence that having more than one nandroid in storage is never a bad idea. Anyone with a clue about what might have happened, and why the nandroid wouldn't work...until suddenly it did?
dood, Nandroids are for pansies.
Maybe it has a bad temper, too.
-------------------------------------
Sent from your mom!
@Kcarpenter- Well, paint me pink and stick me in a pot! (i was gonna make a joke about your wife and my root, but in this current climate, it prolly would have gotten me banned for being off topic in my own thread)
@jerry- you're prolly right. I know it has my sense of humor, cause it keeps effing with me when I'm drunk....
Same experience
I tried to make a nand of darch and when it failed I tried to restore my last nand of my last rom and almost "oops_I_crapped_my_pants" when it failed too
Fortunately an older nand worked
So I just had to try darchdroid again and its nanding just fine . I probably wont stick with it fo eva but it is fast as crap after eating liquid dish soap.
btw, did you happen to see the very last stock wallpaper in darchdroid?? HOMINA HOMINA HOMINA. So hot, want to touch the hiney.. awwooooooo
phenicks said:
Same experience
I tried to make a nand of darch and when it failed I tried to restore my last nand of my last rom and almost "oops_I_crapped_my_pants" when it failed too
Fortunately an older nand worked
So I just had to try darchdroid again and its nanding just fine . I probably wont stick with it fo eva but it is fast as crap after eating liquid dish soap.
btw, did you happen to see the very last stock wallpaper in darchdroid?? HOMINA HOMINA HOMINA. So hot, want to touch the hiney.. awwooooooo
Click to expand...
Click to collapse
Na. I had a totally bad download. It never even finished installing. I'll try it again this afternoon, when I'm near a computer.
I am not sure if this will help, but I had a loop problem and I noticed it started when I installed an app. This was in my nandroid back up. If you boot, it will go into loop.
Through adb start removing programs in the /system/app/. I ended up removing the program (apk and/or odex) and it stopped the loop without rebooting. Not sure why it did this.
Once you find the program that may cause this, restore your nandroid and only remove that apk or odex.
Just try it and see if this works.
you should wipe and clear data before nandroiding back. probably why you had a boot loop. With recovery theres no reason why you cant take 5 seconds and wipe everything before nandroid. If you did do a wipe and clear data before hand then my sincere apologies.
Yeah, I rewiped MULTIPLE times (each time I tried to nandroid recover, so, like, 6 times or so). Thanks, though.
so I went a little too crazy initially with my new mytouch 4g. rooted, S=off(used VISIONary+ and ran the root.sh script), installed ROM Manager and flashed clockwork recovery.
Unfortunately, I've realized that there is a slight bulge on the left side of the device, where the 3 metal dots are. Also, GPS takes at least 10 minutes to get a location. I have had the phone for 8 days and should be able to just return it. To be safe I want to wipe/unroot it.
I have a 2 crucial questions I'd really like help with:
1. if I do a backup with clockwork Recovery (2.5.1.2) by booting into it select "backup and restore", then "backup". Is that a full nandroid style backup? and will I be able to flash that back to my replacement phone to get it back the way I had it before?
2. if I follow the instructions here http://theunlockr.com/2010/12/16/how-to-unroot-the-t-mobile-mytouch-4g/ (without the gfree part), will that revert my phone back to complete stock? with stock recovery and everything?
Just flash the stock nandroid found in the ROM Bible. Move it around alittle so it seems like you used it. They never check s=off if the complaint is cosmetic. I returned my MT4G twice now with s off. Just flash the stock nandrois tiger013 posted. Hope this helps.
well I performed my backup with clockwork recovery. flashed the file in my 2nd question (it looks like its brand new out of box, and has s=on) before I saw your reply.
I'll post back how the exchange with t-mobile turns out. I wonder how well the backup will work if I flash it back. hopefully 4g will work and the dang gps won't take as long to get a signal.
i had to replace my first phone, and i had made a backup. put my old sd in the new phone. rooted the new phone (made a back up just in case) and flashed the backup of my old phone. worked like a charm and even had my sms's from my old phone. contacts were all there, app's, everything!
one thing i don't know is if it will flash your old radio and that might give you problems??
thanks for the help. I got the new phone.
As far as all that screen mumbo jumbo: its a -00, made in taiwan. but looking at the data in the terminal, it is a 02 screen, and looks as good as the previous one from china.
my first mt4g, I was able to root quite easily using VISIONary and the root.sh script files for S=off.
This one, I could not get perm root with VISIONary, only temp root. Any attempts to permroot would lock up the phone until I pulled the battery (I waited 30 minutes each time before doing so) I was able to finally turn s=off using the gfree method. STILL can't permroot though. I flashed clockwork (while temprooting it), and now backing up the current rom. I will try to restore my backup from this morning. I hope that the radio doesn't screw up.
Will update when this finishes up.
and just finished the backup from this phone, and restore from the previous. it worked! I have 4g, root, working gps, s=off.
The hardware keys are also noticeably firmer too. the old ones were very creaky.
Nice! Gotta love clockwork!
Sent from my HTC Glacier using XDA App
I seem to have encountered a rather unusual issue with my nandroid back up. I was planning on flashing CM7 to test it out, and then after my test return to my backup. CM7 worked like a charm, but I was going to wait until I had more time on my hands to fully explore the rom, so I decided to do a nandroid restore using Clockwork Mod 3.0.2.4. It worked... sort of. After the restore, I rebooted. It brought me to my normal unlock screen, but when I unlocked it, I was presented with the MT4G initial setup, as if I had done a restore with the stock img. I knew my data is still in there, because it remembered little things, like my initial lock screen, my wifi settings and a couple of other things. I went hunting through a couple of forums, and found that the MT4G has issues when using clockwork 3.0.2.4 to flash non-Gingerbread, and that you ought to use clockwork 2.5.1.2. Thinking that may have been my problem, I tried, and it then told me there was a MD5 mismatch. I followed the recommendations found in this post http://forum.xda-developers.com/showthread.php?t=976453 for finding and correcting mismatched MD5s (the data.img file was the one with the mismatch if that helps). Now it flashed properly, but resulted in the same problem I had earlier... after reboot, I am presented with my lock screen, but then taken through the MT4G setup. I have a TI backup, so I'm not really worried, but, I am curious if anyone can shed some light on what happened to my restore so that it doesn't happen in the future, and so that if someone else has this problem, they can have it a little easier than I have.
Thanks in advance for your help,
WestBC
Any thoughts!
Basically, stick with froyo or GB. Don't jump back and fourth.
Hi guys. I seem to have outdone myself and am now stuck with a phone that plain refuses to boot any more. Let me give you some history so you get the full story.
Not long after I got my U8800 (18 months ago, 'ish) I decided to change my ROM to MIUI because I wanted to get rid of Froyo and Huawei were being incredibly slow to update officially. I did this with minimal troubles and ran it for a long time, updating etc. as needed to be done. Then along came ICS ports and I admit it, I had to fiddle once more...
I downloaded Aurora and read up in here on how to get it on my phone. It seemed before I did anything I needed to set my phone back to the defaults I had and this involved installing Froyo then the latest stock ROM for the U8800. I did all this without hassle and then tried to get the ICS on.
I don't know if it was me, bad reading, something built into the new stock ROM or what, but I could not get the ICS ROM on my phone no matter what I tried. It seemed to have issues deciding if it was rooted or not, it said it was but then failed to work when I needed it to, plus CWM Recovery completely failed to work for me and I just kept getting the stock recovery when trying to boot into it. ROM Manager was also being a pain and kept insisting my phone was a U8160 when previously it had worked as a U8800 (I may have flashed to the U8160 and having thought this I assumed this was my mistake).
I tried various methods of getting to my cust_ folders and manually changing the recovery.img but everything I tried ran into the same "is it or isn't it rooted" problem.
At this point I gave up and stayed with the official stock ROM from Huawei for a bit.
Two days ago I decided I couldn't hack the defaults any more, my phone was slower and I missed the MIUI way of doing things. I decided to have another go!
Ok, we are up to date, thanks for reading so far if you have.
I decided to try getting to the recovery.img again by doing the pink screen and connecting to my PC, problem was when I did this nothing ever showed on my PC, so I looked for other methods.
I uninstalled ROM Manager, because it still insisted I had the wrong phone and found the app, Root Explorer, it worked! Wish I'd have found it weeks ago. I instantly had access to the folders I needed and could mount them etc to overwrite/backup my recovery.img and as I was a little worried about the rooting thing again, despite Root Explorer working I though what harm can it do to overwrite the boot.img too. I did both by copying the originals to my SD Card and pasting the new ones that I had previously placed on my SD Card through the USB connection. I used the files recommended here: http://android.modaco.com/topic/340...-and-then-some-for-the-huawei-u8800-ideos-x5/ and here: http://forum.xda-developers.com/showthread.php?p=14870348
I rebooted the phone and again failed to get into CWM Recovery, just the default Android one.
I then hunted down another recovery and found this: http://www.androidxpert.com/2011/08...k-work-mod-recovery-on-huawei-u8800-ideos-x5/
It worked! I could finally get into CWM Recovery and figured I was home free.
Not so
I then downloaded the same stockwell MIUI I had used previously as I knew that worked, his latest stable version, and dropped the zip on my SD Card. Went to install it and found that CWM Recovery refused to mount my SD Card (16 gig sandisc). Tried a couple more times because I had issues with this card before and then the card ended up corrupted or something because it just refused to work now on anything I had. This was fairly major because I had backed up to this SD Card and forgot to take the backup off and into my PC for safer storage... I know... I do have the back up of recovery and boot.img though on my PC.
It was at this point I noticed I had a boot loop but could still get into CWM Recovery.
Not panicking too much, I tried my old 4gig SD Card, it mounted! I copied the MIUI Rom across to this card, booted into recovery and selected it. It stated it was installing etc but seemed to go pretty quickly. It said it was done so I rebooted as is the norm. Boot Loop. Damnit! Tried this a couple more times, made sure I once again wiped cache, dalvik etc, all of the things it states to do on the ultimate guides etc. Nothing.
Again, still not panicking I thought, fine, I will go back to stock rom. Downloaded the correct one, dropped dload into root, booted using vol + and - and up comes the unpacking screen. Trouble is it refuses to unpack. I quickly look on the net and find that some say if you take the battery out and connect just using the USB it will install it that way, maybe it does for them but it doesn't for me, it just boot loops again.
I am now at my wits end.
I have the feeling its something to do with my changing of the boot.img and I have the original should it be that but I cannot access the insides of my phone through Windows to change anything, plus of course I can't boot the phone due to the loop to change it back using Root Explorer (otherwise it would work anyway).
Is there anything you guys can help me with?
I can install Linux if needed, I read that it lets you view the phones file system better compared to Windows and with my slight knowledge of Linux Id quite expect this but even so, I am not sure what to do.
Any advice/solutions are extremely welcome.
Sorry for the long post, figured I should give as much info as possible.
So what was the latest Huawei official firmware you had on your phone?
What version of CWM are you trying to use?
What version of the huawei official rom did you have on the phone when you tried to install aurora?
What was the last huawei stock rom you tried to install?
Try and get a 2.2 froyo stock rom and flash it using the vol+and- method. This should hopefully get your pink screen back and access to recovery and boot.img. You can then use any recovery earlier then 5.0.2.6 and install stockwells miui.
It sounds like you have a Gingerbread based official rom flashed which you would have needed to flash aurora and are dropping bits into it like boot.img, roms and recoveries which are for froyo.
If this is the case and you can still get into recovery, I would try flash another rom like sbasils miui or wipe everything and format /system and then flash aurora again.
Ok, not sure what changed but, I figured whilst I wait for a reply I may as well keep playing and try to fix it myself still. So I stick my battery back in, was out all night, plug it in the USB as I wasn't sure what juice it had left and turn it on with vol + and - down for that one last try at the default install.
It starts unpacking!
I have no idea what changed, I did nothing different bar having left the battery out all night. Can it have had something in the residual memory?
Anyway, short version. Installed the default froyo, updated to the beta gingerbread (stock and latest).
Back up everything to internal storage this time, just incase and went to superclick to see if I could root it again, it did so. Used Root Explorer to copy CWM Recovery.img over, backed up it all again using CWM to internal, rebooted, worked.
At this point I got silly again and having it all backed up a few ways now decided to try Aurora again, 2.4 this time. It works.
Again, no idea what changed but its going again and after an initial mess with the SC Card again, that works too now.
Sorry to have wasted any ones time with this, though I still really appreciate the reply even if it seems to have fixed itself.
I just wish I was sure what fixed it so It could help others who have the same issue, unfortunately I don't
great stuff, seems upgrades are just a bit hit and miss on this phone. glad it all worked out.
So it has been rough week for me. My luck was so bad I went thru 3 phones. This all started last week when I flashed rom on my nexus 6p. Apparently I had vendor issue so I erased everything in twrp and then tried to restore everything back. This is when bad luck began. The rom went on Bootloop and wouldn't work. The phone wasn't booting I thought maybe since I just installed it might take while, turns at after 5 hours all i got was very very hot phone. I was like everything is fine I can just flash all other roms i have in twrp for just incase. I booted into twrp and it started asking me for password. When i tried to log in it wouldn't work so I went into allow modification mod. I couldn't do nothing major there so I " This is where I F$%* up " Formatted the whole thing thinking ill be back on stock. Everything was gone and I mean everything I started freaking out then I remembered I can just connected to internet and put rom and gapp file on phone folder and flash it in twrp. Well That didn't work either because when I flashed both files it's in bootloop still. Someone please help. I also broke my backup phone nexus 6 that I had in same day this happened. When I tried to take my brother moto x play I found out he bricked it. I really really need help. What should I do and please don't mind me and "noob" at this.
Have you tried to flash stock via fastboot or Nexus root toolkit by wugfresh?
Donald Nice said:
Have you tried to flash stock via fastboot or Nexus root toolkit by wugfresh?
Click to expand...
Click to collapse
like stock google.
Yes
Get wugfresh, follow instructions
thank you both very much what i did was i used nexus tool to flash the right vendor then put both rom and gapps in my folder and flashed it. It worked . thank you very much
Pleasure dude