Related
Hi,
I have a H2000 Phone, that is stuck in a boot loop,
How it all started:
I tried to use "LCD density changer"
and I set it to change density on boot (massive mistake)
when it rebooted it shows that android animation over and over again, it locks up then vibrates then starts the animation again... CRAP!!!
so my thoughts are well like the few android phones and tablet that I have had previously I will just re-write the ROM to it somehow
well..... seems as it that is like getting blood from a stone... nobody has it???.. how can this be???
nobody at all has ever written a customs ROM for this phone??, surely not?..
I have looked high and low for a ROM for this phone, spending hours using "google Translate" to read though Chinese forums, even randomly signing up to the forums to find that I can't fins any info at all.
I do not have the IMEI problem that most people are talking about (yet)
because I cant even get that far,
i have downloaded the system.img, recovery.img etc etc. for the device, but unless I can get them onto the phone they are useless to me,
I have tried the SPmultiportflashdownloadproject.exe and installed the Mediatek MT6516 drivers and the device is recognised by windows (for about 5 second after being plugged in then the phone shows the charging indicator on the screen and the device is no longer accessable by windows)
as far as I know I have the right bits to flash the firmware or ROM to the device, but i'll be buggered to know how to do it,
I have looked all though the forums and seems as nobody so far has a solution
i can get into revocery <3e> mode by holding "+" and "Power" this gives me a green android and a explanation mark inside a triangle
if I press the "home" soft key I get
Android system recovery <3e>
Android system recovery utility
then the options of;
Reboot system now
apply sdcard:update.zip
wipe data/facory reset
wipe cache partition
So I would assume I would be after an update.zip package to progress using this method.
I can also get a "factory menu" by pressing the "Camera button" and "power button" this gives me:
"Factory Mode"
with the option of:
Full Test
Item Test
Test report
clear flash
version
reboot
I can go through the menu items using the volume "-" and "+" keys but cannot select any of the options, I have tried a few different combinations of buttons but nothing helps..
I do however have access to a working H2000, if this helps at all, I doubt it..
I ripped the build.prop off the working H2000 and will post that in a sec
would be nice if somebody could write an update.zip with the build.prop info and sign it for me???...
Please help me...
Ok I used
SP flash tool v1.1052.3
I flashed the rom I had to the device,
but i had to untick preloader for the prog to recognise my device
and it told me to insert the cable in 5,4,3,2,1
BAM it worked..
It turns on and works!!!
...but the colour is like it is inverted..??
but I do have access to the device now
should be able to access via adb connect "ip" when I get home to my wireless connection and maybe mount /system as rw and push the build.prop file
it could be that I have the wrong firmware for this hardware? as I know some were resistive (H3000 is resistive in a different casing and some are Capacitive, H2000)
I think i need to find the recomended software "SP flash tool v1.1051.5"
if anyone knows where i can find it then i will try again
Cheers,
Keg
Ok now to make things worse
The dual sim IMIE's have disappeared... (DANG!!)
I have now hit my brick wall, it looks like to do anything usefull from here on I will need the special programming cable... without it I cannot do much usefull...
if anyone knows of somebody in Canberra Australia with a cable that would save me some greif...??? Lol..
on another side note, I DID work out how to successfully change the LCD density on this phone,
I STRESS HERE I CANNOT BE HELD RESPONSIBLE WITH ANY MISLEADING OR WRONG INFORMATION THAT IS PROVIDED BELOW, I AM RE_WRITING THIS FROM MY PROVEN TO BE HORRIBLE (just ask my missus) MEMORY,
I am providing it as a rough guide, and it may not work or could brick your phone like i did to mine!!!
Ok, here we go...
it involved installing Z4Root, running the permanent root option, then using ADB from the Android SDK, I typed
"adb devices" to check that only one device was connected,
then;
"adb shell"
this gave me "$" then I typed;
"su"
and accepted the superuser request on screen
then it gave me "#"
from here I typed
"Mount" to advise of the current mountings it told me /system was from /dev/block/mtdblock8
then to access and modify the build.prop file I had to make /system Read /Write by typing in;
"mount -o remount,rw -t yaffs2 /dev/block/mtdblock8 /system"
then i typed
"chmod 777 /system"
"exit"
"exit"
From here I could then use the file explorer that comes with phone to open up /system and navigate to build.prop
then by selecting it i could scroll down the screen to almost the end where is says
LCD DENSITY=160 Or something like that
and I changed it to 140 the first time and then saved.
I reset the phone and once it booted the LCD was set to 140!!!
I tried again by doing all the above again (to get rw in system again) and set to 100 rebooted and it was set to 100 (everything is smaller and doesn't croud the screen anymore) obviously this ROM wasn't ment to be set at anything else or b easily modifiable due to the face that nothing re-sizes properly and it looks kinda crappy... (Do'H, though on a plus side the browser should be able to scale a page better now though)
So after all that I DO NOT recommend doing this procedure unless you have the programming cable and the Factory ROM just incase you bugger it up like I did....
-CHEERS
-KEG
Hi there,
I hope this helps, here is a link for the H2000 rom, try this site as its great for chinese phones, www.pandawillforum.com thanks Mark
http://www.pandawillforum.com/viewthread.php?tid=3536&extra=page%3D1
also look at this link for flashing
http://www.pandawillforum.com/viewthread.php?tid=3536&extra=page%3D1
Help! H2000 Incoming calls rejected after "clean data"
My phone is a H2000 iPhone 4 Clone with Android 2.2 Froyo. Here is the problem: I have went to Settings and then Manage Applications. I scrolled down to the Settings application and clicked it.
I selected the buttons Clear Data and Clear Cache. I was then sent to the android homescreen. Since then, whenever someone tries to call my phone, My phone will vibrate for a second, not show anything on my screen, then display on the other callers phone "User Busy". However I can still call to other people, that works atleast.
Do any of you know a solution? The phone is definetly getting the call because it vibrates when it gets the call, it just doesnt show anything on the phones screen, thus I cannot accept the call and then the other caller gets "User Busy" on their phone. Any advice? Please? Im really stumped here . Thank you in advanced!
Edit: The phone was working FINE before I did this to the Settings application.
Thanks a lot
update+working skype
Hello.Nice to meet you.Did anybody have a update for H2000? Did anybody tried to use skype on this phone? Is there a working version of skype?Thank you.
**** USE AT YOUR OWN RISK ****
The following is posted so that I may share what I've done. It was done by me and for me. If you use it for you, then you take responsibility for whatever happens. This could, potentially, cause problems. It certainly will void your warranty (though it's pretty easy to undo this with no obvious signs.)
Install ClockworkMod Recovery and roots your P6210 tablet.
DO NOT ATTEMPT TO RESTORE ANY CWM BACKUP MADE WITH ANY OTHER VERSION/REVISION. IT WILL BREAK THINGS. THIS VERSION IS NOT BACKWARDS COMPATIBLE. JUST START WITH FRESH BACKUPS AND BE HAPPY.
WHAT THIS DOES:
Installed from recovery, this .zip will first ensure that it's running on the Samsung GT-P6210. If you have a different model, don't waste your time downloading it. It won't work. I have a P6210 to test with. I don't have any other 7 plus tab, so I can't test any other 7 plus tab, and therefore won't even act like it might work. If you want to try it anyway, you should have the knowledge to repair whatever you break - in which case you'll also have the knowledge to unpack this zip file and do things the manual way.
(starting with 20111210, a backup of the recovery is no longer made. I feel this is no longer needed as there is a confirmed working ODIN package people can use to restore their tablets with.)
Next, a new version of the clockwork mod recovery is installed.
(starting with 20111210, old backups are no longer purged. If you are upgrading from my original CWM recovery (previous to Dec 9th), please manually delete old clockwork recovery backups, as they are NOT VALID and will destroy your normal boot operation if you attempt to restore with a proper/current version of this recovery.)
Finally, the tab will be rooted. This only involves copying a tiny file (called 'su') to the system. In order for most android apps to make use of that, however, another application must be first installed. (See "Finishing SuperUser installation" below.) I considered putting that "SuperUser" application as part of this package, but it's really very easy to get it from the market.
INSTRUCTIONS:
Put the installation zip file on your tablet's external SD card. If you don't have an external SD card, you won't be able to install this. MicroSD cards are cheap. If you have a tablet that costs 399 USD, you can afford to spend a few extra dollars/euros/pesos/whatever on a microSD card. Just get one. Not only is it required for installing this from the factory recovery, but it makes a great place to back things up to. A nice 16GB card is suggested. 32GB is better. You'll need AT LEAST 1GB for this recovery. If you have a previous version of CWM already in-place, you won't need the storage card.
You can download the .zip file directly to your tablet and then possibly use the built in "My files" applet to move it to extStorages/SdCard, or you could download it to your computer and use "adb" to push the file to /mnt/sdcard/extStorages/SdCard, or you should be able to get it there with "Kies." If you have the proper adapter, you could also attach the microSD card directly to your computer and just copy it there. It doesn't matter HOW you get it on the card, as long as it's on the card.
After the zip file is on your microSD card, and the microSD card is inside (and recognized by) your tablet, then you need to...
Boot into recovery mode.
If the recovery version banner is "CWM-based Recovery v5.x.x.x", then you already have a version of CWM installed and should skip ahead to the proper section. If the banner is "Android system recovery (3e)", then you have the factory recovery and should continue with...
Installing from factory (3e) recovery:
Use the volume up/down buttons to move the highlight up and down, and the power button to select the highlighted option.
1. Select "apply update from external storage"
2. Select the file you placed on your storage card (starts with "p6210_CWMR".)
3. Sit back and watch it run. Read the information that is being sent to the screen. If there's an error, it'll display some message. If it works, it'll display a message starting with the word "Done!"
4. Select "reboot system now."
You now have a CWM-based recovery installed, and your tablet is rooted.
Please skip ahead to "Finishing SuperUser installation"
---------------------------------------------
Installing from CWM-based Recovery
Use the volume up/down buttons to move the highlight up and down, and the power button to select the highlighted option.
1. Select "Install zip from sdcard"
2. Select "choose zip from internal sdcard" (which will actually point to the external card.) (If you are upgrading and chose not to put the .zip on the external microSD card, you might need to select "choose zip from sdcard" instead.)
3. Select the file you placed on your storage card (starts with "p6210_CWMR".)
4. Select "Yes - Install (whatever filename you selected)"
5. Sit back and watch it run. Read the information that is being sent to the screen. If there's an error, it'll display some message. If it works, it'll display a message starting with the word "Done!"
6. Select "+++++ Go Back +++++"
7. Select "reboot system now."
---------------------------------------------
Finishing SuperUser installation
Install the SuperUser application directly from the android market:
https://market.android.com/details?id=com.noshufou.android.su
....
Post-installation Notes and Issues
It's a known issue with the version of CWM used in this recovery that the "internal sdcard" actually references the built in storage on the tablet. So, if you want to back up to your microSD card, choose "backup to internal sdcard". I'm retaining this issue to stay "compatible" with other CWM recoveries of the same version number. (won't fix)
The .zip package displays an incorrect version identifier/date when version 20111209 is being installed. (It's shows a banner with the date of 06-Dec) (cosmetic)
This recovery is NOT compatible with firmware updates via Kies (and perhaps not via other samsung official methods.) In order to perform a firmware update, I suggest the following procedure: First, perform a CWM Recovery backup, then use the ODIN package found elsewhere to restore this tablet to a factory state. Let Kies upgrade the tablet to whatever version it wants (give it a few tries in case multiple upgrades are needed.) Then re-install this recovery, and perform an "advanced restore" (or "advanced restore from internal sdcard if you made the backup using the similar option.) From there, restore "data." That will leave the entire firmware update in place. (boot is the normal boot kernel; system is what people like to call a ROM here, but is the samsung pre-installed apps; and data contains the applications you install and all your data.) Then "go back", wipe the cache partition, advanced, and wipe the dalvik partition. HOWEVER, please note that I have no way to know if any given samsung firmware update is "compatible" with this restore unless I've tried it myself. It's compatible with everything released up to the date of this note (10-Dec-2011), but I can't predict the future.
Donation?
I don't take donations. If you have spare money (I don't), please donate it to the Salvation Army, Red Cross, or just find a homeless person on the street and give them something. My favorite charity is the Shriner's Hospital for Children. (yes, I am.) If you'd like to thank me, there's a button at the bottom of this post dedicated to that. If you don't want to thank me, that's okay too.
Changes for 20120107:
Brought the recovery kernel up to date with the normal boot kernel. The only impact should be that if you keep crashing any time you boot normally (and before you are able to perform any action), you can now boot into recovery to _hopefully_ be able to retrieve the /proc/last_kmsg as a diagnostic tool.
Reduced the size of the .zip quite a bit.
Changes for 20111210:
* A backup of the existing recovery image is no longer being made. I feel this is no longer needed, as an ODIN package is now confirmed to be working that people can use to restore their tablets to a factory state.
* Old clockworkmod recovery backups are no longer being deleted when installing this. If you are installing this or newer from my CWM recovery previous to Dec 9th, 2011, please manually delete all those old backups. If you attempt to restore them, please be prepared to download ODIN and a factory ODIN image, as you'll need it in order to get your tablet working again. You've been warned...
* The issue that was causing backups to the tablet's built-in storage to fail has been corrected.
Changes for 20111209:
* Issues with getting into recovery are resolved.
* a backup of the recovery is only made if there is no sign of a previous version of this same recovery in place
Credits
Most obviously, Koush for his wonderful clockworkmod recovery. It's the basis of this entire project. Entropy512 for pointing me in the proper direction on a couple of things, pershoot mods to CWM for the Galaxy Tab 10.1 that I ported over to this one (due to the different partition structure of honeycomb devices.)
Links are below...
Take care
Gary
thanks gary, how might we be able to tell if this will be kosher with 3g version? do we need to --dump all pit via heimdall to ensure all partitions match up,etc? Thank you for your speedy work.
chrisrotolo said:
thanks gary, how might we be able to tell if this will be kosher with 3g version? do we need to --dump all pit via heimdall to ensure all partitions match up,etc? Thank you for your speedy work.
Click to expand...
Click to collapse
It's not kosher at all. I didn't wash my hands before compiling it, and had bacon bits on my salad for lunch. Sorry.
Thanks Gary. I have been watching your progress for about a week and you are like a put-bull. Amazing. u da man!!!
Pit bulls would be shamed as wussies. Many great devs possibly have a touch of Asperger's syndrome (with MUCH better socialization skills!) which, with tasks like this, is a benefit! At the very least just plain tenacious! lol
Thanks Gary. I've learned a lot just following along reading the discourse between you and others like Entropy. Appreciate it.
garyd9 said:
It's not kosher at all. I didn't wash my hands before compiling it, and had bacon bits on my salad for lunch. Sorry.
Click to expand...
Click to collapse
ahhh , close enough. anyways what could we do to find out without actually flashing this to possible incorrect partition??
chrisrotolo said:
ahhh , close enough. anyways what could we do to find out without actually flashing this to possible incorrect partition??
Click to expand...
Click to collapse
Which "3g" model do you have? The tmobile one or the international one?
I'm trying to narrow down which is the GT-P6200 and which is the SGH-T869!
I'm working with someone via PM and email to get the information needed for the SGH-T869, and I think it'll be pretty easy to get a recovery together for it, but other people will have to test and validate. I think this is the tmobile version...
international p6200
Soft Brick(kinda Sorta - well not really). Using defult 3e recovery. Tab would boot up, but would not go into recovery at all. Nada Nada. Thought it might have been some leftovers from other stuff I have been trying, so I odin3'd the factory image, did a wipe all and tried it again. Same difference. The only thing I could really think of was maybe I had a corrupted download.
funny thing is that it would boot up into the OS. Just not into recovery. will keep trying as I really want a way to make nandroid backups.
otamctech said:
Tab would boot up, but would not go into recovery at all.
Click to expand...
Click to collapse
No need to ODIN... that's why the package creates that backup recovery image. However, you said it's booting normally, correct? If so, it's not broken or bricked (and I experience the exact same thing.)
For some odd reason (that I haven't been able to figure out), after I flash a non-stock recovery, its very difficult to get the tab into recovery mode. Some times I get it instantly, and some times I have to try several times in a row. Are you using adb? If so, it might be easier. Power off the tab, plug it into your computer, and eventually the tab goes into a "low power mode" where you see the battery gauge but nothing else. From there (again, assuming you have adb installed/working), you can just run "adb reboot recovery" That usually gets me into recovery. 90% of the time.
If not, just try again. If you see the samsung animation starting, press/hold the power button to turn it off again, then press/hold volume up again... etc. It's a PITA, and a major annoyance of mine.
Two things about it make it REALLY annoying for me. First, I'm using samsung's own kernel for this... but I'm just repacking the initramfs portion of it. Second, if you put the factory recovery back, it's easy to get into recovery again.
chrisrotolo said:
international p6200
Click to expand...
Click to collapse
I'll get to that one eventually. I'm commited to do the tmobile one next, and I REALLY need to concentrate on my full-time job (the one that pays me a salary) which only leaves me a couple hours each day.
take care
Gary
absoultely, take your time. Is there a certain battery percentage requirement to get into either stock or CWM recovery say 50% or 60% minimum? we had this issue on dell streak 7. Let me know if I can help with partition layout or anything for p6200. thanks.
chrisrotolo said:
absoultely, take your time. Is there a certain battery percentage requirement to get into either stock or CWM recovery say 50% or 60% minimum? we had this issue on dell streak 7. Let me know if I can help with partition layout or anything for p6200. thanks.
Click to expand...
Click to collapse
No hard requirement I'm sure - but flashing at below 50% is just a stupid reckless risk, plain and simple as that.
If you are having issues getting into recovery after flashing this...
Here's a procedure I've come up with that has allowed me to get into this recovery 9 out of 10 attempts (and it doesn't require any special connections to a computer.) Please read all the steps before starting so you're prepared for what comes next. It'd really be annoying to have recovery finally pop up, but you weren't paying attention so the tablet turned off.
power off the tablet
Throughout this entire process the volume UP switch should be held and not released. This is the side of the volume switch closest to the power button. Once you see your recovery screen, you can release the volume switch (and any other button you might be holding at that time.)
Press/hold Volume Up (constant)
Press the power button, hold it down for 2-3 seconds, and release it.
You'll see the Samsung logo screen for a few seconds...
Instead of the expected recovery screen, you might see the samsung boot animation with music. If so, immediately (without releasing volume up), press and hold (and keep holding) the power button. Don't let it go this time.
The tablet will appear to power off after holding the power button for a few seconds, and then will power back on a second or two later.
(you're still holding that power button, right? how about volume up? Good.) Again, you'll see the samsung logo screen for a few seconds...
Instead of the boot animation, recovery should pop up this time. Release the power button as soon as it does or you'll just turn the tab back off again. You should also release the volume UP at this point.
(If you've flashed my recovery, please try this. If it doesn't work, please take the effort to reply to this post so I can know what people other than myself are experiencing.)
Take care
Gary
updated OP with:
Post-installation Notes and Issues
I'm aware that after flashing this, it is difficult to get back into recovery. I'm not sure WHY, but it's fairly consistantly a pain in the rear. However, I have found that following the steps in the following post seems to work (at least for me) 9 out of 10 times. (I was distracted on the 10th try, so not sure if it worked or not): http://forum.xda-developers.com/show...6&postcount=14
Remember above I mentioned that when this package installs, it creates a backup of the old recovery? Well, it does that no matter what recovery was in place. So, if you install this package with a factory recovery, that backup will be of the factory recovery (which is probably what you want.) If you install this package a second time when you already have the CWM Recovery installed, you'll overwrite that factory recovery backup with a backup of the CWM recovery (which makes no sense.) I'd strongly suggest that after you FIRST install this package, you make a copy of that backup recovery image file (and full filename is displayed when it's created), and stick that copy someplace safe. Perhaps just rename it and copy it to your SDcard or computer. A good name might be "p6210_factory_recovery.img"
The Tab 10.1 could be difficult to get into recovery too.
Usually, the following works for me:
Press and hold VolUp
Press and hold Power until the screen turns on (this is slightly different from your instructions)
Release Power but keep holding VolUp until Recovery shows
__________________
somebody9 said:
I was wondering if anyone knows what needs to be deleted in order to get rid of that pesky pop up menu you get by pressing on the Chevron/Arrow in the middle of the bar.
Click to expand...
Click to collapse
Please start a new thread for a new topic. Try to keep this one isolated to the CWM recovery.
garyd9 said:
Please start a new thread for a new topic. Try to keep this one isolated to the CWM recovery.
Click to expand...
Click to collapse
Sorry about that. Post removed.
Garys method of booting into recovery works fine. I'm just going to post it in linear format.
1. Press the power button and select Power Off
2. Press the volume up button (closest to power button) and do not release until the recovery screen is displayed
3. Press (do not hold) the power button
4. The static Galaxy 7.0 Tab Plus screen will display (possibly twice)
5. When the animated Samsung screen displays, press and hold the power button
6. The static Galaxy 7.0 Tab Plus screen will display
7. Release all buttons when the recovery screen displays.
This works every time for me
To whom ever can help out, I have a Galaxy Tab 2 7.0, and cannot seem to get my problem resolved by myself. I have somehow inadvertently managed to install an update.zip that had or had no relations to this particular OS of this particular model of android.
My problem is that I wanted to be able to, migrate my apps to the external SdCard or extSdCard, and I think I used an update.zip designed for the cellphone HTC Evo 4g. Not realizing that I will be later unable to use the restore feature from a previous backup I had made using CWM 6.0.1.0 to recover from my inadvertent mistake (not to comfortable making a backup, and thinking I can restore properly anymore, like I can on my cellphone that I am spoiled with).
Silly of me to think I could use an update.zip designed for another type of device such as the HTC Evo 4g, but… (anyway my bad what was I thinking…?). The update.zip, by the way is "dtapps2sd-2.7.5.2-signed", like I mentioned this is clearly designed for the HTC Evo 4g, and not for the Samsung GT2 7.0.
The problem I experience now is not complete lose of my GT2 7.0 device I can still install and change out OS through the CWM-Recovery and install apps through the Android Market. I do however experience the inability to check my Storage properties under my Settings profile. When I attempt to click on this link it pauses for a second as if it wants to open up and perform its normal function, then reports an error "Unfortunately, Settings has stopped". Now at this point this is where I would have to mention another issue similar to this one, and that is at startup. When I first start the device up and it runs through its process of startup configuration. It will then report a list of programs that are prevented from running properly it as follows;
Unfortunately, the process android.process.media has stopped.
Unfortunately, My Files has stopped.
Unfortunately, Factory Test has stopped.
Unfortunately, MTP has stopped.
Now my question is, how is-it possible to resolve this issue. I have tried to complete a fresh install of the OS, CWM-Recovery, and also attempted to wipe everything possible that the recovery will allow, but I am not expecting much, as I cannot even get the backup and restore feature to work efficiently enough to provide me with what I need it to do…
I have provided this post with a download of the update.zip I used as well as the version of the OS I have provided my Samsung GT2 7.0. If anyone can shine some insight on what direction I should attempt to do to resolve this issue I would be more that interested to take a look at what I could use to correct this error of mine…
-Samsung GT2 7.0 - OS (Use the Download link above the Rosewell signature)
http://forum.xda-developers.com/showthread.php?t=1784318
-dtapps2sd-2.7.5.2-signed
http://www.mediafire.com/?7jpc5oudzt6o76p
I might be comfortable to ADB Shell into my device to make changes, or if one was able provide me an update.zip/script that would be great. Also is there a better recovery out there than the ClockWorkRecovery.
Better recovery so you may try twrp or so
Try install a fresh firmware preferably with a pit file from odin pc
Sent from my GT-I9300 using xda app-developers app
Mohamedselim said:
Better recovery so you may try twrp or so
Try install a fresh firmware preferably with a pit file from odin pc
Click to expand...
Click to collapse
Mohamedselim, Thanks...
Will look into this..., any links by the way in regards to the "fresh firmware with a pit file"...?
Have you tried downloading and flashing a full Odin tar file to restore your device to stock?
imnuts said:
Have you tried downloading and flashing a full Odin tar file to restore your device to stock?
Click to expand...
Click to collapse
Yeap...!, I have tried this already, have had no promising results...
This is the only compatible version of a .pit file...;
http://forum.xda-developers.com/showthread.php?t=1642744
Can anyone provide me another one for the GT-p3113...?
Just checking in..., and wondering if anyone has a solution for this...?
Factory reset in stock recovery. So Odin a stock Rom and before u install anything custom, do a factory reset in recovery after u Odin back to stock. Then flash away.
I imagine you have alrdy tried a factory reset using a custom recovery.
WAIT!!! You don't have to factory reset, just reboot into CWM recovery ang go to mounts and storage>wipe internal storage. Confirm and reboot. You will lose anything on the sdcard but your apps will stay.
RomsWell said:
Factory reset in stock recovery. So Odin a stock Rom and before u install anything custom, do a factory reset in recovery after u Odin back to stock. Then flash away.
I imagine you have alrdy tried a factory reset using a custom recovery.
Click to expand...
Click to collapse
MultipleMonomials said:
WAIT!!! You don't have to factory reset, just reboot into CWM recovery ang go to mounts and storage>wipe internal storage. Confirm and reboot. You will lose anything on the sdcard but your apps will stay.
Click to expand...
Click to collapse
1. I am all over the Factory resets, and wipes.
2. Already tried Stock Rom(s).
3. I believe my problem is a bootloader, or partitioning script. (As this denies me access from inside settings>storage where I can view my allocated size, and Restore to Factory button. In addition in CWM, I am not allowed to mount/sdcard(internal), extSdCard is ok though. Also, I cannot plug Tab via USB to check contains on Internal or External sdcard, but I can remove the External to transfer data from it via sdcard slot on PC...)
Maybe you can recommend a good Stock Rom, so I can give that ago...
I was in the process last night, and could not get a good connection with Heimdall or Odin. I am now looking into driver issues, so...
Ok, so I was successful in taking RomsWell and MultipleMonomials advice, and was able to return my device back to "Normal" state, including "Stock Recovery". But I still have the original problem as in my request I asked in my first post...
I do however experience the inability to check my Storage properties under my Settings profile. When I attempt to click on this link it pauses for a second as if it wants to open up and perform its normal function, then reports an error "Unfortunately, Settings has stopped". Now at this point this is where I would have to mention another issue similar to this one, and that is at startup. When I first start the device up and it runs through its process of startup configuration. It will then report a list of programs that are prevented from running properly it as follows;
Unfortunately, the process android.process.media has stopped.
Unfortunately, My Files has stopped.
Unfortunately, Factory Test has stopped.
Unfortunately, MTP has stopped.
Click to expand...
Click to collapse
I think now, if I cannot get a sizable remedy..., is just to try and send it in Samsung so they can take a look at it...
Any suggestions...?
FYI; I have also tried connecting to Kies, but due to the inability to posses a "MTP" (Media Transfer Protocol), is the reason I cannot connect to my SdCard & extSdCard. I can "PTP" (Picture Transfer Protocol) into it, using "adb shell", but not using "MTP"...
So I do not know how much "MTP" has to do with this relationship of the other three items that I mentioned in my bullet list in my quote, but...
Anyway, I don't know what I am trying to say, but thank you two, for getting me this far...!
grassy-sneakers said:
1. I am all over the Factory resets, and wipes.
2. Already tried Stock Rom(s).
3. I believe my problem is a bootloader, or partitioning script. (As this denies me access from inside settings>storage where I can view my allocated size, and Restore to Factory button. In addition in CWM, I am not allowed to mount/sdcard(internal), extSdCard is ok though. Also, I cannot plug Tab via USB to check contains on Internal or External sdcard, but I can remove the External to transfer data from it via sdcard slot on PC...)
Maybe you can recommend a good Stock Rom, so I can give that ago...
I was in the process last night, and could not get a good connection with Heimdall or Odin. I am now looking into driver issues, so...
Click to expand...
Click to collapse
Did you try formatting internal storage in CWM?
MultipleMonomials said:
Did you try formatting internal storage in CWM?
Click to expand...
Click to collapse
I am not quite confident on how much this will work. As I have tried this multiple times to wipe "Wipe Factory/Data", "Wipe Cache", including all the partitions under the "Advance" section found in CWM Recovery. Even using TWRP Recovery.
Per this post; I just attempted to flash a "Stock Rom", but not before doing a factory/data, cache wipe using "Stock Recovery", including after a successful install...
No luck, the same problem still exist as above...
Ok, this was all just the rudest experience I put my self threw. As I have an HTC Evo 4g - cellphone and have become comfortable with installing ROM's, Kernels, and Updates.zips, as well as, other modification. All threw the Recovery designed for this particular device, and don't get me wrong there has been a couple of times. Maybe more than a couple, more like a few times I have installed incompatible downloads I find in the XDA forums. Which makes this screw up, difficult form me to know that as long as you can get into a Download/Bootloader or a modified Recovery designed for a particular device that was successful flashed correctly. Well the screw up are easily redeemed/recoverable.
So, to make a long story short. After having called Samsung Customer Care (the 1-800-SAMSUNG) number, it seems to have been a External SdCard getting in my way from having been real short from sending my Tab off to the repair department (where ever it is...). I in fact already had it in an envelope, all I needed was an address to send it to. Anyway the nice person on the other side of the phone requested that I remove my External SdCard, and confirm that I was able to get into my "Storage" tab under my settings. Well after success getting this option back, I then made the suggestion that maybe my Eternal SdCard is corrupt or incorrectly formatted. She then agreed maybe this is the case. After ending the phone call. I quickly restarted my Tab, again only to find out that I was no longer receiving the error messages like mentioned above, which is great, because after multiple flashes of "Stock Roms w/Stock Recovery", and forcing myself to believe that it was a system install error. It in fact the External SdCard in place preventing me from throwing my Tab against the wall / in the mail to Samsung Repair Center...
"Man what an ordeal...!!!"
Thanks to all that helped with the suggestions, as to what direction I most defiantly tried.
I am now in the process, since I am living back in Stock mode. To receive an OTA (Over The Air) Update, and am still in the process of seeing if this thing still possess any residual silent errors...
I will keep you posted.
If not, well it off to happy rooting for me...!!!
That is it, my problem is resolved. Damnedest thing this problem of mine, it seems the only thing I screwed up was the micro SdCard. to the point it was the cause of all the error I received when I started up the device, as well as when I attempted to access my storage through me settings options...!!!
Now re-rooted, and a happy camper, Cheers...!
Hi all,
Since a few days I have a very frustating problem with my Galaxy S2 (i9100) after I installed some new apps. At first all seemed good, but then the low space warning came. I tried to delete some apps, but the main problem is that, with the low space warning coming, all apps (system ones also) started crashing. The result is that even if I can go into the application management menu and delete some apps (it says uninstall successful and the apps disappear from the menu), in fact the apps don't seem to be uninstalled. When I reboot the phone, the apps are still here and the status is the same (low space and apps crashing). I also tried to wipe the dalvik cache through recovery but that didn't change anything. I also tried the *#9900# code to delete the loigs but nothing happened (I suppose the process crash before deleting anything).
I wanted to uninstall some apps through adb but when I choose the USB debugging option and plug the phone, nothing seems to happen, I can't see the device listed through adb devices. My guess here is that, as system apps are crashing, although the usb debugging appears as set, I can't in fact set it.
Next step was to reboot in recovery mode and try to access the phone through adb, but it seems the stock recovery mode (3e) doesn't allow adb connection.
Then next step is to try to install CWM (which supports adb if I'm not wrong). I can boot the phone in download mode, so I should be able to do the installation through Odin but I have some questions concerning CWM version. In most of the tutorials I saw, they're talking of JB and ICS version for GS2, but my phone is still in gingerbread (2.3.3). The CWM site isn't very clear about the versions (only talking of Recovery and Touch Recovery). From reading some blogs on Internet, it would seem that the 4.0.1.5 shoud be working with Gingerbread but nobody seems affirmative about that.
If even deleting apps through adb doesn't solve the stability issue, I hope to be able to do a full backup of the phone through CWM.
My goals here would be (in the following order) :
a) Get my phone fully operational to be able backup everything (sms, app list, data, ...) and continue to use it as-is (on the short term, time to install some kitkat rom)
b) Get an adb connection to backup everything (you can backup nearly anything through adb (sms, ...) ?) or a recovery installed permitting backup
c) Get a way to at least backup the data
So :
1) Have you ever encountered this behaviour ?
2) Were you able to solve it ? If yes how ?
All the threads I have seen (either on XDA or other forums/websites) talk about deleting apps, deleting logs (either through CLI if root or through the *#9900# code), ... But all these people seem to still have the control of their phone, contrary to me.
I have a few other questions :
3) Can you confirm that the stock recovery mode indeed doesn't support adb connections ?
4) Does CWM indeed support adb connections ?
5) What version of CWM would work with my phone ?
6) What are the risks of using another CWM version (if none work with gingerbread) ?
Thanks in advance for any assistance you could provide.
Phone details :
Galaxy S2 (i9100)
Android 2.3.3 / official ROM (as always, customized by the cellular company, but only on apps I suppose)
Version : Gingerbread.XWKE2
Kernel : 2.6.35.7-I9100XWKE2-CL187606 [email protected] #2
Hi!
I see that you already posted in your device section before here, which is the best place to ask for help.
XDA Assist is only here to help navigate the site. And you already found your way. ?
Good luck
So I have a problem with my Nexus 5. Yesterday I tried all kinds of different Lollipop roms and at the end of the day I sticked to Cataclysm. I liked it and my phone was all set up but I noticed there were a lot of unnecessary folders on my internal storage and a nested 0 folder (0 inside /0). I didn't like that so I thought about making a nandroid backup, storing it on my computer (together with my music etc.), wiping everything and restoring it by using TWRP and then eventually putting my music back.
So after I stored a backup on my computer, I started my device into recovery mode and chose the option 'advanced wipe'. Usually I would do a lot of research for everything I do but in this case I was a bit lazy to do that, I tried digging into the search results of Google concerning wiping but I gave up after some unsatisfying results. So I checked every box in the list, including data and system and went through with the wiping. So because my storage was completely wiped I didn't have a 'WRTP/BACKUPS' folder anymore. I made a backup from the stuff I had (which was only a few mb's) so I would have that folder again (otherwise I wouldn't be possible to locate my nandroid backup). I wanted to transfer my nandroid from my computer to my phone by connecting it through USB but for some reason the Nexus 5 didn't show up on my PC when it was booted in recovery (this sometimes happens for some reason)
I managed to do it by using 'adb push Cataclysm folder' in cmd. I went into recovery and restored my backup. My phone booted and I thought everything was as it should be. The wallpaper was black but that was logical because my internal storage was wiped, including my custom wallpaper. But then I noticed something strange, my status bar disappeared, sames goes for my navigation bar. I really have no idea what happened because I've restored nandroid backups before and everything went fine.
So then I put a clean version of Cataclysm on my phone and for some reason it asks me to insert a SIM-card into my device while it has one. I skipped that step and then it asked for my home Wi-Fi and I chose mine, then it checked the connection way longer than it would normally do. After I was done with all the steps my homepage entered my screen and guess what, my status bar and also my navigation bar were absent. It was like my cell phone was in immersive mode all the time. Then I tried flashing the KitKat factory image by going into recovery with my phone and opening 'flash-all.bat' on my PC but then it said '< waiting for devices >' while I enabled USB debugging... I opened cmd and typed 'adb decives' and mine showed up, so it was connected (although it now says 'unauthorized' when my phone is normally booted).
Then I flashed clean Cataclysm again and it again said I had to insert my SIM-card and it then again checked the connection with the Wi-Fi for a couple of minutes. When I was done with the installation I tried replacing the wallpaper with one from Lollipop but it didn't work although there was a preview available. There was again no status bar and navigation bar. I then opened chrome and went to this website and now I'm typing this on my Nexus 5 which has a permanent immersive mode now.
So I don't have much in my internal storage anymore, only a TWRP folder with backups, nothing more, not even a 0 folder if I'm not wrong. There's something wrong with my mobile connection and definitely something going on with my navigation bar and status bar. I hope anyone could help me with this because this is really frustrating becausr I tried to fix it for the last couple of hours, unfortunately without any result...
EDIT: I forgot to mention that when I was trying to figure out how to send the nandroid without being able to access my internal storage via my computer, I booted in recovery, went to 'advanced' and then to 'adb sideload' and tried that because I saw it somewhere on the internet. I somehow believe this contributed to the problem I have.
EDIT2: Now, when I try to power off my phone by holding the power button, it reboots the device instead, what's going on... And as I said, I have a black screen as wallpaper for some reason and I can't change this, but if I open my weather widget, the widget window shows up with my chosen wallpaper on the background, what kind of sorcery is this?
EDIT3: I wanted to download a terminal emulator from Google Play to do this but I couldn't get to 100% so I thought there was something wrong with the app on my device. I googled the apk and I wanted to download it from Zippyshare and when I clicked on the button 'download now', the phone showed the message 'no SD card', so I guess that's the culprit of all of this?
TL;DR My phone is acting really weird (no status or navigation bar, phone reboots instead of asking whether I want to have it shut down when I hold the power button, the wallpaper being strange, SIM-card isn't being recognised) after I wiped data and system and actually everything...
Reboot to bootmanager , flash a factory image , wipe , start over . Something must have gotten corrupted in your nandroid backup.
Regarding ADB not working , you also need to authorize the pc you are working from . You will get a prompt on your phone when connecting . If you dont , go to developer setting , wipe ADB credentials , reconnect the phone.
Also , adb push works fine for single files but it sometimes borks when you are pushing big/many files.
Edit : I hope you didn't wipe EFS as well ( though AFAIK TWRP doesn't wipe it on a advanced wipe) . If you did it's time to return it to stock and send it to LG/Google
Niflheimer said:
Reboot to bootmanager , flash a factory image , wipe , start over . Something must have gotten corrupted in your nandroid backup.
Regarding ADB not working , you also need to authorize the pc you are working from . You will get a prompt on your phone when connecting . If you dont , go to developer setting , wipe ADB credentials , reconnect the phone.
Also , adb push works fine for single files but it sometimes borks when you are pushing big/many files.
Edit : I hope you didn't wipe EFS as well ( though AFAIK TWRP doesn't wipe it on a advanced wipe) . If you did it's time to return it to stock and send it to LG/Google
Click to expand...
Click to collapse
Thank you for reading my huge explanation. After hours of searching and trying a lot of things with my device I figured out how to fix it. Do you remember I said that when I tried to flash the factory image with 'flash-all.bat' that it responded with '< waiting for devices >' ? Well, after reinstalling the drivers countless times and trying to find the culprit I realised I was trying to flash it with TWRP being open, and not the bootloader... So after I was aware of that I finally managed to put stock Lollipop on my phone, then I wiped everything and flashed Cataclysm. It felt pretty satisfying to have a working phone again, it's a pity I had to start from scratch but on the other side, I now how a phone without any rubbish.
Regarding adb push, if I would like to ever push a rom or a big file onto my phone in case I would ever have a similar annoyance, what do you recommend me to do it with?
And what is EFS exactly and what happens if I would ever wipe that? Thank in advance!
Regarding ADB push / twrp MTP mode you jst need to remember not to try and upload the entire content of a sdcard backup or > 3-4 gigs. Big files rarely missbehave , but I screwed up my SD permissions when trying to restore my sdcard ( thousands of files and about 14 gb total).
EFS is a secure partition that stores your GSM/network id and profile - IMEI and so on. AFAIK it's pretty hard to erase but it is possible if you play around with format/repartition commands. Just follow the guides and instructions on this forum and it should be fine.
Corrupted or erased EFS = no network connectivity besides WiFi . And since tampering with it is illegal in some countries the only way to fix it is by RMA/warranty.
I'm glad you've fixed it - I'm not surprised it was a simple mistake , I've been there myself ( tried for an hour to flash a factory image unsuccessfully only to realize I had my phone plugged in a USB3 socket ) .
Don't forget to make a nandroid now that you are set up with your fav. ROM - it will come in handy sometime.
Niflheimer said:
Regarding ADB push / twrp MTP mode you jst need to remember not to try and upload the entire content of a sdcard backup or > 3-4 gigs. Big files rarely missbehave , but I screwed up my SD permissions when trying to restore my sdcard ( thousands of files and about 14 gb total).
EFS is a secure partition that stores your GSM/network id and profile - IMEI and so on. AFAIK it's pretty hard to erase but it is possible if you play around with format/repartition commands. Just follow the guides and instructions on this forum and it should be fine.
Corrupted or erased EFS = no network connectivity besides WiFi . And since tampering with it is illegal in some countries the only way to fix it is by RMA/warranty.
I'm glad you've fixed it - I'm not surprised it was a simple mistake , I've been there myself ( tried for an hour to flash a factory image unsuccessfully only to realize I had my phone plugged in a USB3 socket ) .
Don't forget to make a nandroid now that you are set up with your fav. ROM - it will come in handy sometime.
Click to expand...
Click to collapse
I'll definitely make a nandroid, just in case. Thanks for the help and the clarification!
Try wiping your bum more thoroughly