[Q] P1000N in unstable state - Galaxy Tab Q&A, Help & Troubleshooting

Device
PT1000N 2.3.3 (Kies upgrade) then rooted using ODIN (several months ago, do not remember which process)
Starting problem
I was using go launcher and frozen samsung home apps using root uninstaller pro. Then installed a driver companion, tablet hung. After reset:
"Sorry The application Samsung Home (process com.sec.android.app.twlauncher) has stopped unexpectedly. Please try again."
What I did
tried to flash back to 2.3.3 using heimdall, no fail messages (first)
hard reset
What I get now
It takes 1 hours aprox (no kidding) then displays error messages for loading swipe, system and other apps. Runs VERY slow and hangs at some point.
Once showed message "UUIDs inconsistent" or something alike ...
Also notice that all installed apps and eve my google credentials are still on the system. Such info should be erased by hard reset (I suppose).
Tried other rooms, tried flashing with ODIN
Big Question:
What can be done ?
TIA

What happened when you try odin? what error msg did you get?
Did you do a full wipe(factory reset, data cache, and dalvik) in recovery after flash?
Side note: for future reference, you should try freeze command in gemini app manager first before uninstalling any systemapps.
You should have done a nandroid backup from CWM before tweaking any sytem apps or data. You would have been able to restore from cwm.
EDIT: May we know whicb ROM and kernel you flashed?

yappoe said:
What happened when you try odin? what error msg did you get?
Did you do a full wipe(factory reset, data cache, and dalvik) in recovery after flash?
EDIT: May we know whicb ROM and kernel you flashed?
Click to expand...
Click to collapse
No errors with odin nor in heidmall when flashing.
Flashing Stock Ginger 2.3.3
Thanks for the tip, should have been more careful when dealing with system sutff

valter.espindola said:
No errors with odin nor in heidmall when flashing.
Flashing Stock Ginger 2.3.3
Thanks for the tip, should have been more careful when dealing with system sutff
Click to expand...
Click to collapse
There are plenty of GB 2.3.3 and most of them are for P1000.
Are you sure yours is for P1000N?
GB 2.3.3 for P1000N should read: P1000NUBJP7
how about yours?
Please check it at Settings > About Device
Download your firmware from http://www.sammobile.com/firmware/ you will have a choice of 2.3.5 or 2.3.6 even.
But word of warning.. it's not easy to root 2.3.5 or 2.3.6.

Related

Stuck at "touch the android to begin"

This concerns my galaxy note n7000. I had a rooted checkrom v4 working on my note. I tried to install criskelorom v2 and got bootloops. I then tried to go back to stock via odin and flashed stock N7000 KL3 ROM which i had earlier used, I had to go to stock because after bootloop even recovery was not working. now after flashing stock i am getting a strange problem of the phone getting stuck at the welcome to gt-n7000 screen . "touch the android to begin" . nothing is happening after touching the android on the screen although i can change the language etc and even the pull down notification is also working but the phone is stuck at the initial stage. I have a nandroid backup of my initial checkrom in my internal sd card but cannot restore it before installing a rom with root and cwm. Kindly help . Thanks.
I'm having the exact problem. I'm hoping we can create a soft brick sticky thread. I walked away from my phone last night because I was getting frustrated.
My attempts to flash stock ROM via Odin resulted in the "not responding" message in windows. I can get to both CWM and download mode, however any ROM flashed via CWM results in the behavior described by the OP. fortunately I have access to another Samsung phone, so I can double check driver installation (although it worked for flashing previously).
I'm continuing a search through the forums to find some alternate methods for unbricking. Hope someone has an idea.
Thanks!
It seems that the stock roms i was trying to flash were nonwipe ones so i flashed xxla3 which is a wipe rom and was able to boot . I then flashed the earlier kl3 rom over this rom because kl3 is rootable. I then rooted and installed cwm booted into recovery and restored my earlier nandroid backup. I think the situation arises because the nonwipe rom was unable to clear the cache , user data etc
Thank you for the information. I had exactly the same problem. What did you use to root KL3 ?
Just wipe both cash and user data, and reboot.
reboot to recovery mode -> mount and storage -> format system, format cache, format data.
and do a factory reset and wipe cache.
problem should be solved cause that's what i did
Flo1389 said:
Just wipe both cash and user data, and reboot.
Click to expand...
Click to collapse
Thanks
liewkingyan said:
reboot to recovery mode -> mount and storage -> format system, format cache, format data.
And do a factory reset and wipe cache.
Problem should be solved cause that's what i did
Click to expand...
Click to collapse
daaamnnn!!! I'm scared to dead because of this!! Thanks dude!!!, no more **** ass ics
I had an issue like this once or twice.
http://www.youtube.com/watch?v=L5XjF6sPef4
This skips the that screen. then I cleared some things like google framework and it all was peachy
But its not wroking for me

Fussy GT-S5830

Hello all. I'm having trouble with a galaxy ace, in that it seems very fussy about which ROMs it will run. Bought it about 6mo ago from Optus Australia on prepaid and unlocked it to use on another network. I tried at the time to upload a custom ROM, but failed and ended up having to re-load it with Odin 4.38 and the only images I could then find, which are these:
APBOOT_S5830XXKPH_CL260130_REV03_user_low_true.tar.md5
CODE_S5830XXKPH_CL260130_REV03_user_low_true.tar.md5
CSC_S5830XXKPH_CL260130_REV03_user_low_true.tar.md5
MODEM_S5830XXKPH_CL260130_REV03.tar.md5
Just recently the device has been unstable so I looked around and found the stable CM 7.2 ROM recently released (cm-7.2.0-cooper.zip) so I grabbed that, installed CWM 5.0.2.6, ran a backup and tried to install it. Device only got as far as the black boot screen with the word Android in uppercase doublespaced and hung.
Booted back into CWM and tried to restore, got the MD5 checksum error. Fixed the nandroid.md5 and tried again, and the device then hung at the initial boot screen for the stock rom (says Samsing Galaxy Ace GT-S5830 or similar).
Back to Odin. Found a recent version (4.42) and a one package ROM, S5830XWKT7_S5830OPPKS6_S5830XWKT3_HOME.tar.md5 and loaded this to the handset. This one gives me an Optus spashscreen followed by the sort of pulsing SAMSUNG text in an infinite loop.
Eventually tried the flasher and ROM I used six months ago (at the top of the thread) and was able to get the phone to boot successfully. Reinstalled the rooting package, reinstalled CWM5 and managed to restore just data out of the advanced backup/restore menu.
So I'm back to where I started, only six hours worse off Has anyone got any idea why this isn't working for me, or any good suggestions of how to proceed?
Cheers,
Alex
Are you sure you are using the GT-S5830 and not the Gt-S5830i ?
This was sent from a Galaxy Ace.
damn, that would be a stupid mistake
No, I'm not absolutely positive. The sticker under the battery says GT-S5830, but from a look at google images the two handsets appear identical? How can I establish for sure?
4lex said:
damn, that would be a stupid mistake
No, I'm not absolutely positive. The sticker under the battery says GT-S5830, but from a look at google images the two handsets appear identical? How can I establish for sure?
Click to expand...
Click to collapse
Alright , then that's weird.....what are your key combinations for DL Mode ?
This was sent from a Galaxy Ace.
Vol- & home ?
4lex said:
Vol- & home ?
Click to expand...
Click to collapse
Alright , I hereby conclude you have a problematic device and that I can't find services
"As a friend, just....put an end to me" - Ventus
Did u wiped data after the flash?
Sent from my brain using my GT-S5830
Marco Chung said:
Did u wiped data after the flash?
Sent from my brain using my GT-S5830
Click to expand...
Click to collapse
His system is still in ext4 file system he has to wipe data after the flash! You will no longer stuck in bootloop!
Oh god why
I forgot stock = RFS
"As a friend, just....put an end to me." - Ventus
thanks. How can I find out more about this file system issue? is there an app that will tell me how it's currently configured?
4lex said:
thanks. How can I find out more about this file system issue? is there an app that will tell me how it's currently configured?
Click to expand...
Click to collapse
Unfortunately , no.....
"As a friend, just....put an end to me." - Ventus
Use Odin 4.38, download any one package firmware from sammobile with your backup's android version (ie 2.3.4, 2.3.5 or whatever).
Flash it, wipe everything after Flash (from stock recovery), then root, install cwm and restore your backup.
Boot loops are mostly caused when you don't wipe after flashing. Connection issues can be fixed by flashing your region's modem.
Also, restore backups using the appropiate cwm version (backups of cwm5 restore with cwm5)
Cheers. Dunno if I'm being a bit simple here, but I'm only finding 10 most recent FWs here, all of which are 2.3.6 ?
I didn't do as much wiping as you suggest last time though, so i'll give it another whirl and see if I do any better.
I was being simple. Hadn't selected a region.
trying now.
Flash DXKPB 2.3.4 Asian firmware first. If you flash that, it will format all of your partition back to rfs
And after that you can just flash newer firmware like XWKT7 2.3.6 and wipe data. Voila!
Sent from my GT-S5830 using Tapatalk 2
i had stock 2.3.6 and i decided to download and flash Jellaxy
it works, but sometimes its slow, lagging and apps crashing
i have nandroids of both (stock and jellaxy)
i tried restoring stock 2.3.6
error restoring /system
advanced restore just system didnt work, too
i flashed 2.3.5 italian through odin (download mode)
odin didnt finish because of bootloop
i dont remember exactly, but i did wipe, factory reset, cache and/or other
it booted, finally (in italian)
then i formatted /data and recovered old data
bootloop
i tried wiping all at once: dalvik, cache, data, factory reset
bootloop
now i cant go to download / recovery by holding vol down/up and home and power, it goes to ramdump
recovery is now home + power
i can restore jellaxy, but not stock
what to do? i'm stuck on jellaxy
trogper said:
i had stock 2.3.6 and i decided to download and flash Jellaxy
it works, but sometimes its slow, lagging and apps crashing
i have nandroids of both (stock and jellaxy)
i tried restoring stock 2.3.6
error restoring /system
advanced restore just system didnt work, too
i flashed 2.3.5 italian through odin (download mode)
odin didnt finish because of bootloop
i dont remember exactly, but i did wipe, factory reset, cache and/or other
it booted, finally (in italian)
then i formatted /data and recovered old data
bootloop
i tried wiping all at once: dalvik, cache, data, factory reset
bootloop
now i cant go to download / recovery by holding vol down/up and home and power, it goes to ramdump
recovery is now home + power
i can restore jellaxy, but not stock
what to do? i'm stuck on jellaxy
Click to expand...
Click to collapse
To restore a stock rom your file systen to rfs !!!
And all custum rom are ext4!!
Meaning ... Use stock recovery to wipe data causing the system to become rfs again then install cwm and ONLY !!! Restore ! Otherwise if u format it will convert to ext4 again !
U can also use chainfire ext4 app to change file system in jellaxy and then restore.
Take care
Sent from my GT-S5830 using xda premium
SnowPluralism said:
To restore a stock rom your file systen to rfs !!!
And all custum rom are ext4!!
Meaning ... Use stock recovery to wipe data causing the system to become rfs again then install cwm and ONLY !!! Restore ! Otherwise if u format it will convert to ext4 again !
U can also use chainfire ext4 app to change file system in jellaxy and then restore.
Take care
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
what about that ramdump?
can i use mobile odin?

I just made it worse

Ok, I had the NULL problem with the keyboard and stupidly tried to re-flash the ROM I had on my external_sd card using Mobile Odin Pro.
The ROM image was ICS 4.0.4 N7000DXLR2_N7000OLBLR1_N7000DXLR1_HOME.tar.md5 which has been working fine for a few months.
This didn't work and all I'm getting now is a partially working phone with the messages
"Unfortunately, the process com.android.phone has stopped". and "Unfortunately, TwLaincher has stopped" and similar.
I tried using PC Odin to re-load an older version of GB 3.5 but the result is the same.
I'm totally out of my depth here so will probably need to take it to a Samsung Service Centre but if anyone has the patience to suggest anything I can try, I'd be very grateful.
Thanks in advance
Trevor
I got that message before (even when I had flashed stock GB), usually the workaround for that is to just 'Wipe Cache partitioned' and 'Wipe Dalvic Cache'... all in CWMR. Those messages would clear itself out next time you bootup your phone. No need for you to return that back to SSC.
But the phone still works right ?
Just simply flash a stock GB ROM using PC Odin and do a data wipe in the stock recovery....
The problem will be fixed...
letters_to_cleo said:
I got that message before (even when I had flashed stock GB), usually the workaround for that is to just 'Wipe Cache partitioned' and 'Wipe Dalvic Cache'... all in CWMR. Those messages would clear itself out next time you bootup your phone. No need for you to return that back to SSC.
Click to expand...
Click to collapse
Thanks a lot for the reply. I just discovered that doing wipe/hard reset fixed it (I didn't do Wipe Dalvic cache. I haven't learned what that it is yet).
I then used PC Odin to install latest ICS and then followed Dr Ketan's instructions for rooting. All worked pretty well but I was panicking back there when the phone started to really screw around. Phew. I'm relieved.
Thanks again.
Trevor
warfareonly said:
But the phone still works right ?
Just simply flash a stock GB ROM using PC Odin and do a data wipe in the stock recovery....
The problem will be fixed...
Click to expand...
Click to collapse
It was booting up but not working at all with all the fatal errors. But you're right. All it needed was a wipe and hard reset. I was trying to install ROMs thinking it would clear the problem. I learned a lot today.
Thanks again.
Trevor
Why posting multiple threads for the same problem?? U already have another thread for this...
↖(^▽^)↗ Sent from Rego Galaxy Note ↖(^▽^)↗

[Q] the process com.android.phone has stopped unexpectedly

I'm currently running the latest CM9 on it with moboot... It seems like every time it boots up it pops up with that error message and literally won't go away and you have to reboot the device.. the only way I've found to temporarily fix it is to just wipe cache.... but it always comes back.
Is there any way to prevent this from popping up? It happened when I was on Classicnerd BUTTA too.
Wipe the system and caches, then reflash
I had this problem as well a while back. Wiping caches and reflashing the ROM worked for me.
And you guys didn't have the problem again, after that?
Help manually moving contacts and choosing a JB ROM.
If a pro could help me out I would appreciate it very much. I have been trying to move from a dangerous ICS build to JB and I am having this same problem.
My N7000 previously had this on it:
android 4.03
radio 19220zclp6
kernal version 3.0.15-i9220zclp1-cl131270 (bad ics kernal)
build number midnote 2.0 iml74k.zclp1
So I used ODIN to flash it to a GB rom but I got the com.android.process error and my phone would lock up.
So then I found this link http://forum.xda-developers.com/showthread.php?t=1424997 and flashed this ROM "N7000UBLR3 N7000UVOLR1 - Download - Argentina" from the bottom of the page. I wiped only the the cache (not the phone reset) and flashed it again but I still get the process error and phone locking up. I don't even know if this ROM is a safe ROM!!
Am I even on a safe kernal now? kernal n7000ublr3-cl890184 build imm76d.ublr3
What I need help doing is the following.
1. Before doing a full wipe, I need to either manually save my contacts to my PC or back them up. (no apps work but my pc can browse my phone) If I knew where my contacts were located, maybe I can manually copy them to my pc? So any help saving data from a partially unusable phone would help.
2. Flash to a safe GB rom, so I can then do the full wipes safely and then flash to a stable JB rom. (I have no clue which roms to choose here and need help).
Thanks for any help..

[Q] STOCK ROM and all went wrong

Dear Friends,
I was trying to root my phone. I downloaded a STOCK ROM using Desktop ODIN and after the ROM was downloaded, the phone started and I keep getting errors like these
Unfortunately maps has stopped
Unfortunately the process android.process.acrore has stopped
Unfortunately Google Play Store has stopped
.
.
And so on
I have tried with N7000XXLRK_N7000DBTLRK_N7000XXLRK_HOME.tar.md5 and N7000DDLR6_N7000ODDLR2_N7000DDLR1_HOME.tar.md5 so far and I have also tried the Pre-Rooted ROM SGN_XX_OXA_KJ1_FACTORYFS.tar
My phone is un-usable as of now. I cannot even enter the menu. All i have to keep doing is pressing ok on these error messages.
Please help. How can i restore the phone back to normal?
gudddu said:
Dear Friends,
I was trying to root my phone. I downloaded a STOCK ROM using Desktop ODIN and after the ROM was downloaded, the phone started and I keep getting errors like these
Unfortunately maps has stopped
Unfortunately the process android.process.acrore has stopped
Unfortunately Google Play Store has stopped
.
.
And so on
I have tried with N7000XXLRK_N7000DBTLRK_N7000XXLRK_HOME.tar.md5 and N7000DDLR6_N7000ODDLR2_N7000DDLR1_HOME.tar.md5 so far and I have also tried the Pre-Rooted ROM SGN_XX_OXA_KJ1_FACTORYFS.tar
My phone is un-usable as of now. I cannot even enter the menu. All i have to keep doing is pressing ok on these error messages.
Please help. How can i restore the phone back to normal?
Click to expand...
Click to collapse
Ok, there is no need to open a new thread for this stuff. You already had one....
That is because you are doing dirty flashes. Do the following:
Reboot into stock recovery and flash philz kernel (just to make sure that you are safe)
Reboot recovery (you should have CWM now)
Do a full wipe (wipe data/factory reset - wipe cache partition - format system - format data - format preload)
Reboot in download mode and re flash the Stock firmware with ODIN PC
Then you should be ready to go...

Categories

Resources