Related
Hi,
I'm pretty sure the microUSB port on my AT&T Captivate is shot... It will charge using the outlet adapter, but will *not* charge or connect to any of several PCs. I've uninstalled/reinstalled drivers multi times, and another Captivate exactly like it connects just fine (with same cable, same port, etc.) Good news: it's still under warranty. Bad news: it's been rooted and updated with a "Low-designgears" util.
Do I need to revert to stock in order to return for warranty, and is it possible to do that if the phone can't connect to a PC?
Stupid questions probably. Thank you.
I would think that you need to return to stock...you can chance it. But it's up to you.
Sent from my SGH-I897 using XDA Premium App
What firmware are u on? I think there was a cwm flashable stock somewhere...don't know if that would help.
Sent from my SGH-I897 using XDA Premium App
There is a cwm flashable jh7 but I think it only works from 2.1. Might work with 2.2 but if all else fails format boot in recovery and tell at&t your phone said there was an update and it failed. I would probably format system, cache, and data too just so there isn't any evidence of your wrong doing. Unlikely it would ever find its way back to you though. Has worked for a lot of people.
It should hard brick your phone though
Sent from my I897 using xda premium
Firmware is 2.2. Thanks for the help. I'll look for that cwm flashable, and consider my options. Thanks.
xijar said:
There is a cwm flashable jh7 but I think it only works from 2.1. Might work with 2.2 but if all else fails format boot in recovery and tell at&t your phone said there was an update and it failed. I would probably format system, cache, and data too just so there isn't any evidence of your wrong doing. Unlikely it would ever find its way back to you though. Has worked for a lot of people.
It should hard brick your phone though
Sent from my I897 using xda premium
Click to expand...
Click to collapse
1. As long as it's rooted he can replace 3e recovery, install cwm, and flash that from 2.2.
2. Formatting does not hard brick. Why would there be an option that would completely **** your phone? Like a self destruct button that could accidentally be pressed if you don't know what you're doing. Makes no sense.
studacris said:
1. As long as it's rooted he can replace 3e recovery, install cwm, and flash that from 2.2.
2. Formatting does not hard brick. Why would there be an option that would completely **** your phone? Like a self destruct button that could accidentally be pressed if you don't know what you're doing. Makes no sense.
Click to expand...
Click to collapse
Sorry, back again guys...
I've got cwm installed but I can't find a way to get past 3e recovery. I tried to flash cwm recovery from rom mgr - and it says current recover is cwm 2.5.1.2 - but going into recovery mode still shows 3e (don't know what cwm recovery should look like). Flashing any rom (tried a couple customs too) dies with sig verification error.
been searching for a few hours on replacing 3e, but everything i run across requires ability to connect with the pc.
any idea how i can replace 3e recovery without ability to connect via usb?
http://forum.xda-developers.com/showthread.php?t=1052991
The second method does not require a pc. Download the fix files with your phone, then download a file explorer from the market that has root access, root explorer, file expert, astro file manager to name a couple. Paste in the file reboot into recovery, reinstall packages twice and that will boot you into cwm, which its green with more options...
brick the phone n say kies ****ed it up. that worked for me.
Samsung captivate
glitch kernel
cyanogenmod 7 #89
OC and UV
I'm fairly new to the rooting business but I've been treading lightly. I have a few newbish questions that I need answering, and I thank you in advance.
Today, using Psouza's Moto-1-click tools, I restored my /system/app to its stock state, unrooted, reformatted, and then installed 5.6.890 (the official OTA version), followed by re-rooting.
I wished to make a full backup of the complete stock system, and so I purchased "Droid 3 Bootstrap" from the Android Market. I proceeded to boot into Recovery Mode and created a backup of my now stock system. I also went ahead and downloaded "ClockworkMod Recovery" from the market and paid for the premium version. I noticed that I can also make a backup from "ClockworkMod Recovery" in the same way that I made a backup from "Droid 3 Bootstrap."
Question is this...what's the difference between the 2? I know that ClockworkMod Recovery gives me the capability to flash different ROMS, which is the reason I purchased it (awaiting future ROMS, figured I'd just download it now). But did I have to download Droid 3 Bootstrap Recovery as well? Couldn't I have just backed up using CWM Recovery?
Basically, I'd like to know the difference between the two...in the most basic explanation, if at all possible. I'm still learning about all this and I really enjoy it, but I'd like to have a full grasp of what I'm doing exactly.
Thank you in advance.
Lyxdeslic said:
I'm fairly new to the rooting business but I've been treading lightly. I have a few newbish questions that I need answering, and I thank you in advance.
Today, using Psouza's Moto-1-click tools, I restored my /system/app to its stock state, unrooted, reformatted, and then installed 5.6.890 (the official OTA version), followed by re-rooting.
I wished to make a full backup of the complete stock system, and so I purchased "Droid 3 Bootstrap" from the Android Market. I proceeded to boot into Recovery Mode and created a backup of my now stock system. I also went ahead and downloaded "ClockworkMod Recovery" from the market and paid for the premium version. I noticed that I can also make a backup from "ClockworkMod Recovery" in the same way that I made a backup from "Droid 3 Bootstrap."
Question is this...what's the difference between the 2? I know that ClockworkMod Recovery gives me the capability to flash different ROMS, which is the reason I purchased it (awaiting future ROMS, figured I'd just download it now). But did I have to download Droid 3 Bootstrap Recovery as well? Couldn't I have just backed up using CWM Recovery?
Basically, I'd like to know the difference between the two...in the most basic explanation, if at all possible. I'm still learning about all this and I really enjoy it, but I'd like to have a full grasp of what I'm doing exactly.
Thank you in advance.
Click to expand...
Click to collapse
I'm assuming the 'clockworkmod recovery' app is rom manager. Rom manager is best for easily downloading roms (if the developer sets it up on there, not all roms will be on rom manager). I personally recommend against using rom manager to do backups/restore/rom installs because it is known to cause some issues. So, my advice, just do it all manually to avoid problems down the road. All you need is the d3 bootstrapper app
Sent from my DROID3 using XDA App
erismaster said:
I'm assuming the 'clockworkmod recovery' app is rom manager. Rom manager is best for easily downloading roms (if the developer sets it up on there, not all roms will be on rom manager). I personally recommend against using rom manager to do backups/restore/rom installs because it is known to cause some issues. So, my advice, just do it all manually to avoid problems down the road. All you need is the d3 bootstrapper app
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Correct, the "CWM Recovery" I kept referring to is indeed Rom Manager, my apologies. So, in a nutshell, what you're recommending is; use D3 Bootstrap to create your custom backup, and use Rom Manager specifically for Mods only...correct?
I think he's saying to not use rom manager at all. You can flash roms from cwm recovery.
Edit: just to clarify I mean by booting into recovery using the bootstrapper and flashing a rom from there to avoid any issues caused from the rom manager
Sent from my rooted xt860
Lyxdeslic said:
Correct, the "CWM Recovery" I kept referring to is indeed Rom Manager, my apologies. So, in a nutshell, what you're recommending is; use D3 Bootstrap to create your custom backup, and use Rom Manager specifically for Mods only...correct?
Click to expand...
Click to collapse
I recommend to not even use the rom manager app, as everything can be done manually. Roms can be downloaded from forum sites. Just remember to do a wipe data/factory reset each time you flash a new rom. This prevents fc issues. On hashcodes blog you can get a modified version of the koush bootstrapper app that let's you enter recovery from bptools. That way if you screw up /system and can boot straight into recovery, restore a nandroid and you're good to go.
Sent from my DROID3 using XDA App
erismaster said:
I recommend to not even use the rom manager app, as everything can be done manually. Roms can be downloaded from forum sites. Just remember to do a wipe data/factory reset each time you flash a new rom. This prevents fc issues. On hashcodes blog you can get a modified version of the koush bootstrapper app that let's you enter recovery from bptools. That way if you screw up /system and can boot straight into recovery, restore a nandroid and you're good to go.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
I appreciate the responses. Could you explain to me how the modified version of D3 Bootstrapper allows you to enter recovery in case of a bootloop? What is "bptools" and how is it accessed if the phone won't boot up?
Edit: Also, what type of problems have been seen when using Rom Manager to flash Roms as opposed to a Bootstrapper? Aren't they both created by the same Dev? I would assume Rom Manager is just a more user-friendly method to flash Roms since it's so self-explanatory in the app itself.
Again, I appreciate the time you guys are taking to help me understand this.
Lyxdeslic said:
I appreciate the responses. Could you explain to me how the modified version of D3 Bootstrapper allows you to enter recovery in case of a bootloop? What is "bptools" and how is it accessed if the phone won't boot up?
Edit: Also, what type of problems have been seen when using Rom Manager to flash Roms as opposed to a Bootstrapper? Aren't they both created by the same Dev? I would assume Rom Manager is just a more user-friendly method to flash Roms since it's so self-explanatory in the app itself.
Again, I appreciate the time you guys are taking to help me understand this.
Click to expand...
Click to collapse
When your phone is powered off hold the m button on the keyboard then press the power buttong(keeping m pressed) you'll then get a list of boot options. Volume down scrolls while volume up selects. Bptools is at the bottom. When you go to bptools then press volume up and enter it you will boot to clockworkmod recovery. This only works with the modified bootstrapper app. This way is much safer because its possible to soft brick the phone with the normal koush recovery and not be able to enter recovery. You'd then need to flash the xml files. The normal bootstrap app requires that phone bootloop before the custom recovery will kick in. As for rom manager, its had problems wiping data/factory reset I think. You can still use it, there's just a possibility of of the rom not working properly
Sent from my DROID3 using XDA App
erismaster said:
When your phone is powered off hold the m button on the keyboard then press the power buttong(keeping m pressed) you'll then get a list of boot options. Volume down scrolls while volume up selects. Bptools is at the bottom. When you go to bptools then press volume up and enter it you will boot to clockworkmod recovery. This only works with the modified bootstrapper app. This way is much safer because its possible to soft brick the phone with the normal koush recovery and not be able to enter recovery. You'd then need to flash the xml files. The normal bootstrap app requires that phone bootloop before the custom recovery will kick in. As for rom manager, its had problems wiping data/factory reset I think. You can still use it, there's just a possibility of of the rom not working properly
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Thanks so much for the info man.
Okay right about now i am really confused about flashing roms on droid 3,
ok so i have root access now what recovery should i put?
and here is my big question.
can i flash dark droid or steel droid regardless of system?
my phone says .866 and droid steel says i need .890?
am confused on this part,
sorry for the stupid questions.
Yes you do need .890, and I recommend that you install the tweaked bp tools bootstrap by hashcode to get cwm, it saved my softbricked droid3
Sent from my DROID3 using XDA App
jojo4747 said:
Yes you do need .890, and I recommend that you install the tweaked bp tools bootstrap by hashcode to get cwm, it saved my softbricked droid3
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Not gunna lie im a lil confused too..what's the point of flashing the tweaked one if when you flash a new rom it overwrites it? So you can't access cwr from bp tools then
/droid3
under settings, about phone, your system version is .866? i think we were .959 and now we're .890. Yes, you would want to use hashcodes modified version of koush's bootstrap.
beard0 said:
Not gunna lie im a lil confused too..what's the point of flashing the tweaked one if when you flash a new rom it overwrites it? So you can't access cwr from bp tools then
/droid3
Click to expand...
Click to collapse
Basically installed on your phone as an app, and you re-bootstrap/recovery after you flash your custom rom so you can create new backups/restore/flash update .zip files ect. After the rom is flashed as well... if you think you wont have any issues ever after, by all means, brave the world without your cwm recovery on there... but that kinda seems like you'd be sinking your d*** in looseness w/o a rubber... and no body likes that itch in the AM...
Sent from my DROID3 using Tapatalk
Seirÿu said:
Basically installed on your phone as an app, and you re-bootstrap/recovery after you flash your custom rom so you can create new backups/restore/flash update .zip files ect. After the rom is flashed as well... if you think you wont have any issues ever after, by all means, brave the world without your cwm recovery on there... but that kinda seems like you'd be sinking your d*** in looseness w/o a rubber... and no body likes that itch in the AM...
Sent from my DROID3 using Tapatalk
Click to expand...
Click to collapse
Not saying it wont be usefull but if you can manage to navigate to the bootstrap app and hit the button for bootstrap recovery..why can't you just hit the button for reboot recovery? I guess im just missing my unlucked bootloader from my incredible lol I used to screw with my phone so much lol
But why does no one wipe for any of these roms?
And what is safe strap exactly?
/droid3
IF you can access the app, yes you could just hit reboot recovery. If youre bootlooping or something you can go into recovery and select bp tools and that reboots into the same recovery as selecing reboot recovery in cwm. and the safestrap is different from the tweaked bootstrap. the safestrap boots from /preinstall or something. Also, you should wipe especially after switching to/from CM7
MrJudylicious said:
IF you can access the app, yes you could just hit reboot recovery. If youre bootlooping or something you can go into recovery and select bp tools and that reboots into the same recovery as selecing reboot recovery in cwm. and the safestrap is different from the tweaked bootstrap. the safestrap boots from /preinstall or something. Also, you should wipe especially after switching to/from CM7
Click to expand...
Click to collapse
This. ^^^
Basically you want it if you can't actually boot your phone.
if you don't redo your recovery and just rely on clicking those buttons when you need them from the app... you'll be stuck if you bootloop and have to flash the sbf in order to get your phone back. I much rather restore from recovery and have 99% of my phone data back with no issues.
The safestrap and 2nd Int. stuff is wicked cool, I just wish i knew more about that... I couldn't really help describe that part lol.
Hi, first post here so if I screwup any of the etiquette please tell me.
Ok, so I've had my P1000 for about two years now, no contract, not locked to sprint / verizon etc.
I had 2.3.3 at the start, but after seeing mannnny people flashing to ICS successfully I had to give it a go.
Attempted to flash using overcome kernel for CWM, failed and I had to odin back to 2.3.6 (couldn't find a 2.3.3 rom).
I kept it on 2.3.6, but I was unhappy and so am trying again:
It's important to know that I am now on a mac, so will not had access to odin, and instead am forced to use heimdall. Please don't post any odin specific instructions.
In order to get CWM I had to flash the overcome kernel, which includes the recovery mod.
I successfully used heimdall for this, following a specific instruction guide.
I then downloaded "cm-9-20120703-NIGHTLY-p1.zip" from get.cm, and copied it to my externalSD on my gt.
Booted into recovery, wiped all data/factory reset, wiped cache, wiped dalvik, and went to install form an externalSD.
I chose my file, and the installation / flashing (not sure as to the terms. ) began.
It went through a few messages, but however once it said "Checking state of BML/MTD" it reboots instantly and shows the cm startup for about five seconds before going into recovery. Always does this on startup, no way to change.
The only way to fix this is to go into recovery and wipe all data, but this leaves me on my 2.3.6 rom.
I have NO idea what's happening, and I can't use most guides due to them being odin specific.
If anyone can assist me, please do.
Don't link to any odin threads, and don't tell me to search, for I have been doing so for eight hours.
Cheers,
Zero
EDIT: SOLVED!!!
After flashing once it failed at BML/MTD, so I opened recovery and flashed from "internal sd". Worked a charm, now installing gApps.
Cheers for helping Priyana!
that is call boot loop.
Just boot to recovery and flash it once more
it is quite documented.
About etiquette, post [Q] in Q&A subforum, not general
priyana said:
that is call boot loop.
Just boot to recovery and flash it once more
it is quite documented.
About etiquette, post [Q] in Q&A subforum, not general
Click to expand...
Click to collapse
That's the thing - when I boot to recovery after flashing (and failing) CM9, it is a different sort of recovery and doesn't allow me to install from an externalSD.
Cheers for replying,
Zero
just the name change.
the internal and external got swapped around in that newer recovery
priyana said:
just the name change.
the internal and external got swapped around in that newer recovery
Click to expand...
Click to collapse
As I just noticed.
Installed PERFECTLY!
It's up and running - however I can't see a market?
Cheers,
Zero
You didn't flash gapps.
Didn't you read the instruction?
Sent from my GT-P1000 using xda app-developers app
priyana said:
You didn't flash gapps.
Didn't you read the instruction?
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
I gave up on instructions after five hours of them failing.
Reread now and just about to reflash with gapps
Cheers,
Zero
Yeah. Believe it or not, early adopter has advantages because we have read up all!
Sent from my GT-P1000 using xda app-developers app
Yeah
Works so well, already have tapatalk and all gapps are working perfectly.
And the instructions - I was following them perfectly, but they did not go in depth when it came to reflashing with the newly installed rom-manager of cm9.
All works perfectly now, thanks for your help
Sent from my GT-P1000 using Tapatalk 2
I've got this exact issue coming over from Frankenclean 2.8 on the samsung fascinate. I decided to update my rom as it was falling behind the 'curve' if you will.
I'm now stuck at a bootloop "samsung" and "S-cyanogen(mod)" screen. they just go back and forth. I'm following this http://forum.xda-developers.com/showthread.php?t=1238070 to the letter and still getting the issue. I've tried flashing a newer kernel that is for 4.x.x builds and no luck.
When I install or attempt to install cyanogen10 it fails on the bml/mtd check and it just reboots to those two screens.
I followed the 'fix' at section 9 but haven't had any luck getting cyanogen to install... I'd really appreciate a little help, ideas, questions, anything.
I know it's an older device, I'm just hoping someone out there with more dev knowledge than I possess "read: none" can help me out.
bump...
Got it to boot into a stock rom, but have 0 luck getting my nandroid to load up and be functional using CWM 2.4 (red). Which is what I made the recovery with.
Might end up with a stock phone if I can't figure it out, I don't mess with roms often.
Luckily I do have titainium backup so all my apps are saved. Just sucks to not have a sleek rom anymore. Not to mention I want jellybean. Any help is appreciated!
fixed it, 4.1 didn't like my phone, got hellybean 4.2 on it without a problem .
Only issue is that google voice to text doesn't work, nor google search.
Intro
Hi guys, I just got my Galaxy Ace from my mom a month ago(She used it for a couple of months but was too "complex" for her that's why she just gave it to me). Anyway, I'm the type of person who wants to explore and unlock the full potential of things. The first thing I did when I received the phone was research about stuff like how to modify it, etc. I was able to successfully root(there's a "super user" icon in the menu) it. Today, I thought it'd be nice to add some metro ui theme on it. So I I downloaded 7 launcher from the play store. But, was not satisfied because it felt like it was only a "skin" and didn't changed the overall feeling of the phone. That's the time I started digging dipper into the realm of Android and came across this thing called "ROM"....
I followed an online guide on how to install roms. First, i downloaded the rom i wanted(it's called "WP7") and placed it at the root of my sd card. Just like what the tutorial suggested(in case something goes wrong), I made a "nandroid" with the use of Clock Work Mod. I then saved a copy of the nandroid into my computer just to be EXTRA safe. Everything seems to be in order so I proceeded with the operation. I accessed the recovery menu, and selected "wipe cache partition" and "wipe data/factory reset". After that, I went to "install zip from sd card" and selected the zip file. Everything went well. After the update, I rebooted the phone and it was successful.
The Problem
I checked the whole new ui design and it was what I expected it to be. But then, I immediately missed the old ui, so i decided to go back to the stock os/kernel/(whatever you guys call it ). I went to the recovery menu and selected "backup and restore". I chose the nandroid I just made through CWM. After loading, I rebooted my phone and bam... this is where my problem is. The Phone's name and model number appears in the screen but it's not loading. I waited for 2 minutes and nothing happened. So I restarted the phone by holding the power button and volume up. I accessed the recovery menu again and examined if I missed a step. After browsing the net, I concluded that I didn't wipe the cache and data before restoring . So I wiped both cache partition and data. I selected the nandroid and then rebooted the phone again. But, the boot loop is still there . I tried it again and again. Wiping, Restoring Rebooting. But the boot loop won't go away.
So I wiped it again but this time, I didn't select the nandroid and instead I went back to the new WP7 rom i just downloaded. My phone didn't do a boot loop and my phone is okay now. I'm stuck with my new rom for about an hour now. I'm starting to get used to it. Anyway, even though things are stable now and i'm on my new rom, I think it's still nice to go back to the phone's original kernel/os . Any ideas on how I can restore back my phone to the original/stock kernel/os without experiencing the boot loop? Or can you give me the causes why I'm experiencing the boot loop? My guess is, I think there's a problem with the nandroid I used. The wp7 rom doesn't experience any boot loop but when it comes to my nandroid, there's a boot loop.
Thanks in advance and sorry if it's too long to read. I just wanted it to be accurate and clear for you guys .
The only way would be flashing through Odin.
Enviado desde mi GT-S5830L usando Tapatalk 2
Search for your previous ROM around and flash it.
Here's a good TUTORIAL on how to flash ROMs
The only way to flash a stock rom is odin (its a pc program) .
after you flash back to stock, you should Be able to restore your nandroid backup without getting the bootloop
(at least, i'm pretty sure, can someone confirm this?)
Im sure ull find a guide on how to use odin somewhere on xda.
Sent from my GT-S5830 using xda premium
AaronvAce said:
The only way to flash a stock rom is odin (its a pc program) .
after you flash back to stock, you should Be able to restore your nandroid backup without getting the bootloop
(at least, i'm pretty sure, can someone confirm this?)
Im sure ull find a guide on how to use odin somewhere on xda.
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
Yea..u are correct..if it was a successful backup(without any errors)...then no problem in falshing nandroid backup after using odin
Best of luck
Sent from my GT-S5830 using xda premium
U need chainfire app to convert filesystem to rfs ... before returning to a backup of a stock rom! Otherwise u need a factoy reset from stock recovery
Hey guys. I came across a rom called stocklite and I was able to successfully install it. My new rom seems to speed up my phone and prolong its battery life. All of the bloatware that came with the stock os isn't present this rom. I don't think i'll be returning to the original stock os. So yeah, I appreciate all your help and cheers to everyone
is your keyboard ok in stocklite ROM
I can't type alphabets in 3*4 mode .
Now using s3 evolution beta3
Sent from my GT-S5830 using xda app-developers app
B A D R I said:
is your keyboard ok in stocklite ROM
I can't type alphabets in 3*4 mode .
Now using s3 evolution beta3
Sent from my GT-S5830 using xda app-developers app
Click to expand...
Click to collapse
The keyboard's working fine for me.
in my keypad it shows alphabet but when I type it shows numbers in screen. . Fed up so flashed back to s3 evolution beta 3 ultimate
Sent from my GT-S5830 using xda app-developers app
SunSleeper said:
Intro
...Any ideas on how I can restore back my phone to the original/stock kernel/os without experiencing the boot loop? Or can you give me the causes why I'm experiencing the boot loop?...
Click to expand...
Click to collapse
I know you're happy with your current ROM but just an FYI, I went through a similar process trying to unlock a T-Mo Samsung Dart T499 (similar to Mini/Galaxy Ace). I just flashed stock ROM via ODIN and it boot looped on me. After reading this post I went into stock recovery and clear cache partition and factory reset and voila!
So this post actually inspired me a bit! Haha! Thanks!
as already said, the batter way to solve that problem is clean up your device is flash a stock rom with Odin,
but then, you will need remake root, and install a CWM....
good Luck !!