Database Users

Liberty 1.5

Well since I cant post in the other forum yet Ill post here. I have issues getting into
clockwork mod sometimes. I eventually get there but its a pain. Anyway I wiped,backtostock,rooted,rom manager,bootstrap and installed liberty. Its loading now so will see how it goes. I was using Rubix and thought it was great but decided to try this. Will have to go back to stock in a few days and I need to swap my phone out.

Since I already have this thread going I do have a question. I have to return to somewhat stock. Is there a best option in deleting some programs and then unroot to get most stuff off so the carrier wont say anything?

This will get you back to stock. Click here.

Yeah I have that file thanks. I have used it but it still leaves traces of the other programs installed. I did wipe cache and the wipe and return to factory but there are still traces of programs. Do I just go into manage apps and will be able to uninstall rom manager ,z4root etc..? Ahh I just checked your link and maybe I didnt have that exact version. Will try that on thanks again.

Well I tried 3.4.2 and wanted to go back to liberty 1.5 and thought I did everything in the right order but am stuck at the liberty boot screen. Been there a long time. I can only get back to regular menu of wipe cache etc.. Any help please? Took forever to get into clockwork mode. went back into stock, installed liberty 1.5 again and should be back up in a little. Well now Im in need of some help again .It started to load and finished. I loaded or started to load my rom back on and the battery went dead. Now Im stuck at at black bootloader screen will a corrupt code and flashing low battery. It chargred several hours through usb and home charger but nothing. Do I need to find another way to chargre the battery and start all over or is it dead?

[Q] MyTouch 4g: Multiple problems... PLEASE help.

Okay, I've searched and searched and no one seems to have the specific problem that I'm having with my phone, so I'm taking to the forums myself. I've been rooting since the G1, I know how to adb push things, I have used google and multiple forums to try to fix this problem. So here goes, anyone that can help I thank you in advance.
1-My phone, like some other MT4G users, reboots itself each time it's plugged in. Initially I thought this was because I was using a Kindle cord to plug it into the pc, so I bought an MT4G usb cable from tmobile, and still it boot loops (just the first white screen for maybe 4 seconds, then black then again and again). The only way to charge it is to let it start boot looping, take the battery out, turn it on, and if I'm lucky enough that it begins to boot up correctly I plug it in mid boot. If I wait til it's fulled loaded it just starts rebooting again.
2-It will not at all from any angle go into Recovery mode. If I try to go to recovery from Rom Manager, or from the screen you get when holding power and lower volume key or by flashing a rom through Rom Manager, it just boot loops just like mentioned above, until I pull the battery for a while (it is currently sitting next to me with the battery out) and then put it back in.
3-If by chance it's on, and plugged into the computer, it is not at all recognized. Ever. While it's booting up my computer finds something, but doesn't know what it is, and doesn't allow me to view any folders on the SD card. Yes I've installed the HTC drivers file. I've adb'ed things to this phone before, now it says device not found. I don't know when it stopped being recognized...
4-I've even tried to fastboot something over to it, but to no avail, still not found.
If I try to do a factory reset, it boot loops. If I sneeze it boot loops.... I don't know what to do, and if I trade it in under warranty, I have to reset it to stock rom, or they're going to charge me for a new phone. Any ideas!?
I have Cyanogen mod 7 on here.

have you tried a fastboot wipe? or have you tried to reboot to recovery from adb?

First, I don't trust using the actual ROM Manager app to do the flashing/installing.
Since you've been flashing since the G1 days why not use Clockwork Recovery? Just go into recovery and do the necessary wipes.
So I suggest to do a complete full wipe in Clockwork, meaning wipe data, cache, and dalvik cache. Install the newest CM nightly (Which is working wonderfully BTW) and see if your problems still persists.
Edit: I didn't realize you tried to enter recovery, oops. But yeah try what the buy above me said. Try re-installing the latest CWM recovery, if that still fails then try heading into there via ADB.

mackster248 said:
First, I don't trust using the actual ROM Manager app to do the flashing/installing.
Since you've been flashing since the G1 days why not use Clockwork Recovery? Just go into recovery and do the necessary wipes.
So I suggest to do a complete full wipe in Clockwork, meaning wipe data, cache, and dalvik cache. Install the newest CM nightly (Which is working wonderfully BTW) and see if your problems still persists.
Click to expand...
Click to collapse
I second that, flashing ROMs from ROM Manager a terrible idea.

Well...if all else fails and if you are really thinking about returning it and still under warranty...few seconds in the microwave method should work just fine. They wont be able to see that its rooted if the phone wouldn't turn on, would they???

glimmer of hope...
So by the grace of god I did get it flashed back to unrooted, stock 2.2 by putting it as pd15img.zip on my sd card and going into bootloader. Once that was done I thought I would be out of the woods... I even plugged it in last night and no boot loop!! but this morning I unpllugged it (and I'm using a tmobile cable for the phone attached to my pc) and here it sits, next to me again with the battery out of it because everytime I try to turn it on (for over 40 minutes now) it boot loops to that stupid white screen (that is honestly driving me insane at this point). I know that it isn't rooted (because I dl'ed rom manager and it won't let me do anything without being rooted) so do we think that I'm safe to go to the store today to request a new one be sent? Thoughts? And thanks for the help thus far!

yeah I would send that back

Bad emmc chip? I'm sorry man, that's a terrible story.
Sent from my HTC Glacier using XDA App

I survived the Encryption Unsuccessful error unscathed?!

I've been a stalker on here for a long time, as I've been interested in custom ROMs but I never pulled the trigger, until last night. My Vibrant has served me well for a many years, I bought it shortly after they came out. All I'd ever done to it was network unlock it so I could keep using it after I moved to the UK.
I've been toying with getting a new phone for a few months now so I decided why not try and flash a custom ROM and get ICS on my Vibrant, if I got the EU error and bricked it, oh well, I'd get a new phone. So I after much reading and research, studying the tutorials on here I went for it. I am vary tech and computer savvy. I build my own computers from scratch, I've flashed my routers and set up networks so I was pretty confident I could do this with the help of the forums here.
I've read every thread I can find on the EU on here and I know that the community needs as much info as possible to try and solve this bug, so I will try and be as specific as possible and list everything I did. But bear in mind, I'm new to this and this was my first time doing much of this so some things may be muddled as I was up til quite late messing with all this.
To start my phone was running 2.2 which was updated using Kies Mini. The only thing I'd ever done to it was network unlock, and for that all I did was find the file on the phone with the code and then enter it to unlock.
I decided to follow Woodrube's guide (http://forum.xda-developers.com/showthread.php?t=1464423)
I followed the guide to the "T".
1. Used Odin to flash back to stock 2.1, worked fine, phone booted back up and everything worked. Phone Data showed I was on 2.1.
2. I put Clockwork Recovery downloaded from Woodrube's sig block on my internal sdcard labeled as Update.zip
3. Created a folder called ICS on my internal sdcard. Found and downloaded CM7 from the forums here and dropped it into the ICS folder. Found and downloaded the ICS Passion ROM from the forums and dropped it into the ICS folder
4. Booted to recovery mode and did Reinstall Packages. It ran but brought me back to the blue recovery screen. so per Woodrube's guide I did it again and the second time it brought me to the green CWR recovery screen
5. I did wipe data/ factory reset
6. I did wipe cache
7. I went to advanced and did wipe dalvik cache
8. I went to mounts and storage and did format system
9. I went to install from sdcard and found the ICS folder I made and ran the CM7 fille I dropped there. It worked the first time and booted right up, I let it sit for about 5 mins waiting for the request to install my google password as Woodrube mentions, but it never appeared, so I moved on after 5-6 min of waiting.
10. I then booted back into recovery mode using the extended power button menu
11. I went to install from sdcard again and this time ran the ICS Passion file. It ran some text lines showed on the screen as id did somethings and then I sw a Random Offset error and a small hex string but then it said successfully installed but didn't leave the recovery screen. So i scrolled up to reboot system.
12. The phone rebooted, showed me the Passion splash screens and a progress bar which filled and completed, then showed a few other splash screens and then it booted up showing my signal strength bar and notifications bar. I thought YES! I did it and it worked. then the screen flashed, it showed a single multi-colored line horizontally across the middle of the screen and then flashed again and I was looking at the Encryption Unsuccessful screen.
13. I DID NOT PUSH THE RESET BUTTON, I set the phone aside and followed Woodrube's link to the Captivate Forums and read up on the error, read all of it, then searched the forums for more threads on the error and read all of those, then I Googled the error and read everything else I could find.
14. First i tried just shutting the phone down with the power button and then restarting it. I did this about 5-6 times. Every time it rebooted it showed me the Passion splash screens then boots up shows my notification bar and signal strength meter and the EU screen. That didn't work. I next tried rebooting 5 times without my external sd card installed. Same results
15. Next I decided to see if I had lost access to my internal sdcard as I had read about. I wasn't sure if I had because I had never pushed the EU screen reset button. So I booted into recovery mode, went to install from sdcard and my sdcard list popped up. I still had access to my internal sdcard.
At this point I was torn... do I stop playing with fire and just got back to stock, update with Kies Mini and go back to using the phone as I had always been and forget all this or do I try and figure this out? Well my stubborn side hating to be stumped had encountered a problem and so wanted to move forward... on i went.
16. I decided, ok, I can still see my internal sdcard so why not try reflashing the ISC Passion and see if maybe it will take this time with no EU. I ran it and exactly the same thing happened as the first time.. right down to the flash with the horizontal line and all. (I did not wipe data, cache or anything, just reflashed. Not sure if I should have or not)
17. Back to recovery mode and check... yes still see my internal sdcard. hmmm
18. Decide ok, how about it I do Woodrube's guide all over again from the start? Maybe that will work. I followed the guide again using all the same files and wound up right back at the EU screen again.
19. Hmmm, how about a different ICS ROM? Went and found ICZen and downloaded it. Hmm, how do I get this unto my internal sdcard if the phone won't boot all the way? Booted it back to the EU screen and just plugged the phone into the usb on my computer, windows recognized it, made the device plugged in noise, and both my internal and external sdcards on the phone showed up as drives. Navigated to the ICS folder in the internal sdcard and dropped the ICZen file into it.
20. Rebooted the phone into recovery mode using the power button menu
21. Used install from sdcard and flashed the ICZen. (Again, I didn't wipe anything before hand. Again not sure if I was supposed to)
22. The ROM installed and got stuck in a boot loop. I pulled the battery and rebooted to recovery and reflashed the ICZen again with no wipes. This time it worked and the phone rebooted and I got the ICZen splash screens, then the notification bar and signal strength meter showed up.. and AGAIN the weird flash with the horizontal bar and then the EU screen. SIGH
23. Booted back to recovery mode and checked if I still had access to internal sdcard. yes it was still there.
24. Shut down and booted to download mode and ran Odin and flashed back to stock 2.1
This is where I am now, It was too late to try anything else and my wife was glaring at me to go to bed so shut off the phone and went to bed.
I tried to put everything I did down with as much detail as I could. I'm sure some of you pros out there might be wincing at stuff I did, but again this is all new stuff for me and I'm slowly learning.
If you have any questions or need clarification just ask and I will try and help/explain better.
Hopefully this might help in the quest to solve this bug or it may just be a waste of time to read, dunno.

I got to:
"To start my phone was running 2.2 which was updated using Kies Mini."
and stopped there
Come back to Froyo - always welcome here

Moped_Ryder said:
I got to:
"To start my phone was running 2.2 which was updated using Kies Mini."
and stopped there
Come back to Froyo - always welcome here
Click to expand...
Click to collapse
LOL, yea I know, but up until this adventure last night, I just used the phone with the Samsung updates as it was, didn't really have a need to do otherwise.

I think that you should flash one of Moped's ROMs and make sure that it will boot up and run ok and that you did, in fact get out of the EU bug safely.
Couple of things:
I did get your PM and I thank you for the info. This post is far more detailed, which is a ton better.
You say that you were unlocked. There was a theory not too long ago about a corrupted EFS file, but AdamOutler uploaded his and someone else replaced theirs with it and it didn't work. But I am thinking that there might be a link here bc I have seen several posts over the last few months that ICS ROMs have been out where someone's data has been borked or their IMIE was gone. Wonder if there is a correlation to that? I'll have to ask some people onver in the Captivate thread and if anyone in the Vibrant thread can chime in too(?).
If you want to flash another ROM, just follw my ICS guide but where it says to install CM7, just install your shiny, new 2.2 instead and there you are.
Great Job dodging that bullet and hope that you no longer lurk, but be a part of the community at large. If your intelligence is reflected in your post, you are welcome here anytime.

Thanks Woodrube,
I was thinking the same thing about loading a 2.2 ROM and be sure I'm all good.
I know the 2.1 I loaded last thing last night seemed to work fine. But I will try a 2.2 once I get home and will update on here after I do.
Funny thing about all this is that my wife now won't let me near her Captivate ROFL.

Can you blame her ?
For the sake of the thread i can chime in on the unlock part. I'm still untouched by the EU bug "touching wood(rube)" . I'm using the i896 version of the Captivate from Rogers and there was never codes inside of it so most app were unsuccesfull at pulling them. I had to use the free SGS Unlock website where you upload your nv_data.bin and it returns you a unlocked version. I also never encountered any efs/imei issue.

hi.
I saw you have not wiped when installing the ROMs. I think maybe you should try and do the wipe before installing the ICS ROM.
Wipe system, data, cache.
Good luck

romitkin said:
hi.
I saw you have not wiped when installing the ROMs. I think maybe you should try and do the wipe before installing the ICS ROM.
Wipe system, data, cache.
Good luck
Click to expand...
Click to collapse
BINGO!
So I followed Woodrube's guide again.. started from scratch... only change I made was I wiped data factory reset, wiped cache, wiped Dalvik cache, and under mounts and storage I format system BEFORE flashing the ICS Passion.
Logged into Google Account and set up phone and now I'm rockin' ICS
Not sure how or why this worked but it did.
Thoughts?

[Q] Can't get into recovery, no matter what I do... (Rooted, running rom...)

Ok, I just started experiencing an issue. I suddenly can't get into recovery. Here is a little back history. My N7 was running CNA 3.6.6 (I know, but...), and I was bored so I decided to try ParanoidAndroid. Well, I have that gotta try something else feeling again, and when I try to get into recovery, it will go to the google screen, then go black for about 10 seconds, then go back to the Google screen and boot up. This happens if I reboot to recovery through the power menu, or getting into recovery from the bootloader. I even tried Quick Boot, in hopes it had some magic I didn't. No luck. The same crap. I even switched from TWRP to clockwork recoveries, and the same crap happens (I tried the same things I did originally).
Also tried through other apps too, like Rom Manager, Rom Toolbox, and TiBu. Everything works, but I am bored with this rom... I have tried turning it off, plugging the N7 into a PC and trying to get into recovery. Again, I can get into the bootloader, but as soon as I select recovery, it goes black, then fully reboots...
Anyone have any ideas? Any help would be greatly appreciated.

Have you tried re-flashing a recovery image, eg TWRP 2.3, from fastboot?
Sent from my Nexus 7

BillGoss said:
Have you tried re-flashing a recovery image, eg TWRP 2.3, from fastboot?
Sent from my Nexus 7
Click to expand...
Click to collapse
Thanks for the reply. I will give this a try (gotta wait until after 10pm...or 17 minutes!). Again, thanks, hope this works.

MetalWych said:
Thanks for the reply. I will give this a try (gotta wait until after 10pm...or 17 minutes!). Again, thanks, hope this works.
Click to expand...
Click to collapse
Scheiße, I reflashed TWRP in fastboot, and I am getting the same result. I think my N7 forgot it has a recovery!? I will try flashing clockwork through fastboot and see if this works. Thanks for your help...
Edit: Clockwork does not help. There is no recovery for me. I am now at a loss. Hopefully someone will have some suggestions...

Finally got my recovery back...damn latest bootloader!
Yeah, this has sucked. I have spent several hours figuring out what the hell went wrong. It turns out its the latest bootloader. Others are having this issue. So, I had to go back to stock (which will erase EVERYTHING) and then had to re-root. Now that my bootloader is back to JRO03D, I am back up and running.
So, the first time I did this route, I decided to take the update and re-root my N7, and ran into the same issue. I could not get into recovery. So, I had to do it all over, this time not taking the update and not updating the bootloaders, and I am now back and already have a ROM running and everything installed.
If you want to go this route, here are a couple of links that will help...
http://rootzwiki.com/topic/28544-guide-nexus-7-bootloadersrecoveriesrootback-to-stock/#entry764328 and go to the Back To Stock section. The next part is for rooting (if you wish to do this yourself)...
http://www.talkandroid.com/guides/misc/how-to-unlock-and-root-the-nexus-7/
I will post this in case anyone has a need for this info...

Unable to get into Recovery after 4.1.2 upgrade... - xda-developers
Any help?

Nexus 7 stuck in bootloop after attempts to reflash stock and unroot

Hello everyone,
I tried to root my 32g Nexus 7 with WugFresh's toolkit 1.6.1 (I'm fairly new to the rooting thing so I tried to use a toolkit). It did not go well. During the process I received messages from the toolkit saying it could not read Fastboot - but they seemed to go away after I switched USB ports. After the bootloader unlocked, I went back into the device and saw that it didn't fully wipe (I thought it was supposed to wipe out *everything*). When the rooting portion was finished, there were no new apps in my app page (super user and whatnot).
So I decided to nix the whole thing and just put it back into stock and try again tomorrow. I followed the instructions to get the drivers to where they needed to be, and then set it to flash back to stock and unroot the device.
First time around, it stalled during the flash. Rebooted, tried again, flash went fine. Toolkit said it would appear to be stuck in a bootloop for about 5-10 minutes. Well, after 20 minutes, it was still on that colorful "x". So, I reset it once again, and now it's stuck on the pretty colored "x". I do think the unlock is still there because the open padlock still shows up when I reboot. It just gets stuck on the "x".
Can anyone help me? I'd really rather not remove the battery if I have to (though it doesn't look that hard).
I feel terrible about this. This was my Christmas gift, and I feel like I've completely ruined the thing over what was supposed to be an easy root procedure.
EDIT: I was able to get to the Android with the red triangle on it and did a factory reset, but it seems that it still can't get past the "x".

Horadrius said:
Hello everyone,
I tried to root my 32g Nexus 7 with WugFresh's toolkit 1.6.1 (I'm fairly new to the rooting thing so I tried to use a toolkit). It did not go well. During the process I received messages from the toolkit saying it could not read Fastboot - but they seemed to go away after I switched USB ports. After the bootloader unlocked, I went back into the device and saw that it didn't fully wipe (I thought it was supposed to wipe out *everything*). When the rooting portion was finished, there were no new apps in my app page (super user and whatnot).
So I decided to nix the whole thing and just put it back into stock and try again tomorrow. I followed the instructions to get the drivers to where they needed to be, and then set it to flash back to stock and unroot the device.
First time around, it stalled during the flash. Rebooted, tried again, flash went fine. Toolkit said it would appear to be stuck in a bootloop for about 5-10 minutes. Well, after 20 minutes, it was still on that colorful "x". So, I reset it once again, and now it's stuck on the pretty colored "x". I do think the unlock is still there because the open padlock still shows up when I reboot. It just gets stuck on the "x".
Can anyone help me? I'd really rather not remove the battery if I have to (though it doesn't look that hard).
I feel terrible about this. This was my Christmas gift, and I feel like I've completely ruined the thing over what was supposed to be an easy root procedure.
EDIT: I was able to get to the Android with the red triangle on it and did a factory reset, but it seems that it still can't get past the "x".
Click to expand...
Click to collapse
The best thing to do is reflash using fastboot. Google "flash n7 with fastboot". It is really the best way to work on an n7, or any nexus device.
Sent from my Nexus 7 using xda premium

rebel1699 said:
The best thing to do is reflash using fastboot. Google "flash n7 with fastboot". It is really the best way to work on an n7, or any nexus device.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Oh wow, it worked!!! I used the .tgz file with the Toolkit and it came back!!! Thank you so much!!