Hey guys,
dunno if I have to write english or german here, feel welcomed to answer in your prefered languages. The more opinions, the better!
I used rooted XXJVT (DBT) for a very long time but by time it went laggy AF.
Now I decided not only to reset the phone to make it work lagfree again but also flash Android KitKat via CWM.
The biggest problem I encountered: my eMMC died a few years ago, so I was forced to run the phone via microSD (had to scratch the chip off the mainboard to make it accept the microSD when flashing) and exchange the vold.fstab to make the phone use the microSD as internal storage. That way, it worked again. Until now.
Since the WhatsApp Services don't let any 2.3.7 and older OS verify their Account anymore (but those who were already verified can keep WhatsApp until Feb 2020) + I can't flash Custom Roms via CWM ("Waiting for SD-Card to mount" counting down from 20 to 0, then restart and same screen again, looped) probably because of the dead (no more existent) eMMC Chip, i guess the only way to make my phone work WITH WhatsApp again would be find a rom above 2.3.7 that I can flash via Odin..
Otherwise I guess I can shred my phone because it is restricted to SMS/Calls from now Q_Q
Now I need your help: Is there any possibility that I don't know yet? Any ROM out there that I could flash via Odin, dodging the "flash via CWM" way that doesn't seem to work for me (atleast, since my eMMC is dead, I don't know how could make it go past this "Waiting for SD-Card to mount" ****?
Greetings,
A desperate Android User^^
Related
Hi,
I am a rather experienced user when it comes to flashing/using odin and I had successfully updated to JVK from JV1 and had been using it for a few days. I decided I wanted to use a ROM now, so I went to http://romkitchen.org/beta/ and downloaded a no-wipe rom. I was already rooted but needed CWM so I flashed the new version of CF-Root. Everything worked fine so I used CWM to flash the rom. It started an endless boot cycle (Just the galaxy s i9000 words over and over again) so I decided to just repartition and flash JVK with Odin again as I had a backup and wouldn't lose anything. That worked normally but once the phone started restarting (before it got to any boot image) it went to a password entry box. These were the exact same files that I had used to to flash gingerbread before and I have never had this happen to me before. The only physical button that does anything is the menu button which dims the screen. Pulling out the battery/restarting/reflashing JVK or JV1 doesn't help. Froyo (JS5) does work though so I am using that now. I have tried 3 different versions of Odin, going to JV1 then JVK, different .pit downloads, bootloader and non bootloader version of JVK, none of them make a difference, always the password. I have tried all my passwords, and none of them work.
Anyone have any ideas?
Thanks
I have the same problem. Tried a lot of variants without any luck. Currently running JPU instead.
I've started to wonder if the phone is actually asking for a unlock code, as if the phone was locked to specific operator. But anyway there is a digit code you can check if your phone is locked, and mine is not.
Please anyone know how to work around this and what is causing this password prompt?
Rooting or putting a modded kernel on jvk does not help either, still asks for password.
First of all try 'samfirmware.com' as the password, may be a long shot but maybe the rom originally came from there.
if that doesnt work, i would send doc or stefunel a PM (or check thread) incase some one else has had this issue, they may no the password considering it was downloaded from their kitchen.
Tried that before, didn't work. It's not their rom anymore, just the stock JVK.
Did you try some common pre-set passwords on electronic devices like '0000' or '1234' ? Maybe this is just something like on a dvb receiver...
Sounds unlikely but since you've tried the 'normal' ways...
very strange. Try Samsung , Gingerbread , 0000 , 1234 , I don't know anything else .
BUT AT YOUR OWN RISK!!!
no idea if it will even work
hacksome said:
FIX for anyone having "Confirm Password" issue on Boot:-
1) Just enter some wrong password multiple times
2) Then a Warning message will appear telling you it will remove all SD Card data
3) Type something wrong again!
4) Let the SD Card get wiped.
5) Then the system will bootup properly next time.
I just did one more *2767*3855# Full wipe after bootup.
Click to expand...
Click to collapse
link to the original poster http://goo.gl/hyzin not sure it will work
PAGOT said:
BUT AT YOUR OWN RISK!!!
no idea if it will even work
link to the original poster http://goo.gl/hyzin not sure it will work
Click to expand...
Click to collapse
Thanks!!!!!!!!!! It worked! Now to install Darkys Rom.
It works
Thanks Pagot, that worked and didn't erase my internal SD card (I have no external one).
just enter many wrong password it'll no erase your internal or externe sd card
Tested on JVO
It Works
Had installed deodexed JVP(2.3.4) via CWM, decided to reset and erase the internal SD card. Got the dreaded confirm password on boot, typed in the wrong password multiple times, the phone rebooted, internal SD card was formatted.
Could that be the encryption password!!???
I was testing my device against a MDM (Mobile device management) system called Afaria, where I work and have enabled encryption in the policy applied to the device. When I got the enter password dialog box I entered the encryption password and the device accepted the password...
this saved my life ahah
works fine with 2.3.5 too
thanks
Very helpful thank you. Worked for me on my Infuse. Took about thirty tries and waiting through about 4-5 30 second timeouts for incorrect password but finally said it would wipe data in accordance with security policy and bam back up running Entropy's DD deodexed and rooted. Thanks fellas. You guys sure helped a noob out.
2992
Thought to update:
Worked for me too - happened every now and then on my lost EFS'ed i9000, as I was trying to install different roms.
Entering it wrong enough times wiped the sd card (that I could careless about)
Cheers!
Hey guys I been having a huge problem with my Samsung Galaxy S 1900M its currently locked with Bell/Virgin Canada. I bought it off of some 2nd hand company. The phone was sold as is saying that it was unable to connect to the computer, (computer does not recognize it at ALL). I bought the phone amusing it was a ROM load problem. It came to me rooted and in almost perfect condition so I was quite happy with my purchase considering I paid $180 USD ($170 CAD). I tried connecting to the computer using the USB that came with the phone, and as stated it does not recognize it at all on ANY Windows/Linux base PCs. I also have another Samsung USB cable that I know works, I tired that as well...no success.
So I am assuming who ever loaded a ROM did not know what they were doing.So I have been searching all over the internet/google, XDA forums and Q&A and everyone point to loading a new kernal....BUT here is where it gets weird. Who ever had this phone previous did not flash a new kernal when updating and put the 3e recovery on the phone, WHICH MEANS I cannot flash any new: Kernals, OR ROMS using the CWM, which btw I am pretty sure isn't working properly because it goes into the base recovery mode with limited options, ex. reboot, sdcard update.zip, wipe cashe, format sdcard...nothing else.
Which brings us back to the original problem, I can not connect to the PC for ODIN to work its magic on the kernal....Please help....
Here is the current load,
Firmware Version: 2.2
Baseband: 19000UGJK4
Kernal Version: 2.6.32.9 shout.leeSEP-09 #1 ( I have never heard of this?)
Build: FROYO.UGJK4
may be a issue with drivers dont quote me though, i had to update drivers after flashing and updateing my galaxy s, as i had simular issue with odin, by not reconize, do you mean windows wont even detect the phone added, or is it connect and nothing? does the phone charge when connected to the pc ?
The phone does charge, but even with the Samsun Keis app, and having the proper Sumsung drivers it still wont even detect the phone. I even went to Device Manager and searched for new hardware/device. I also tried putting it into download mode, and connecting Odin. Windows still wont even detect it. I think its a problem with the kernal....for both issues...
Fixed the problem, hope this helps for others.
Just following up on this as I figured out what to do on my own in case anyone else has this issue.
It was quite simple actually, the kernal was faulty, and so was the ROM that was loaded just as I anticipated
1st:The person that previously owned the phone loaded FROYO custom build that was taken from a leaked version prior to the official release and had no USB support, therefore being unable to connect to the computer.
2nd: The kernal was a custom build and had a 3e recovery built into it and was not able to load any un-verified files(unofficial ROMS, firmwares, updates etc.), therefore I was not able to load a new ROM to fix the first problem, stated above, and visa versa.
I found a program on the market place called "kernal manager", I downloaded the PRO version by searching Google on the computer for the .apk file, I then copied the .apk file onto my external 2 GB SD card and ran the .apk file through the phone. I then opened "kernal manger pro" and opened the menu button, then hit search for kernals. A list of different models of phones came up, I browsed down to my handset maodel (Samsung Galaxy s 19000), press on it, and got a list of kernals. I took each top rated and downloaded kernal listed, did a little research on the internet and found one of them to be suitable. I then went back to the phone chose that kernal through "kernal manager", it asked me to flash then reboot, I hit yes, it then begun the process, and when finished reboot on its own. I then reboot into recovery again after the kernal had loaded and the first reboot and found that the new kernal had succsefully been flashed. I then was able to go about as I please. I uploaded a cm7.zip file to the external sd card, put it in the phone, boot to recovery browsed to the file, and ran it having complete success.
I am now happily running Cyanogen 7. Hope this helps anyone that needs it. Any questions just ask
Hi , i write from italy. I have a N1 and i am trying to install this Rom.
Updated to radio 5-12.00.08 and HBoot 0.35.0017
Format the MicroSd SanDisk 16 Gb class4 with 128 Mb swap , ext4 2048 .
Use Sdformatter and parted magic 6.1
With previous versions (1.5 , 2.1 and 2.2 ) i had no problem.
Now , with 2.3 , after flash Rom N1 remains blocked with X colored and padlock.
In an italian forum showed the kernel evil as a novelty compared to previous versions.
I have installed the kernel evil indicated in 3D ( vers. 2.2 ) With RcAds vers. 2.2 Functioning and , to rebott N1 blocked.
I downloaded from this 3D the kernel evil 35-9 -11-2 -720p-ir-svs and patch of the camera..
I have installed rom , kernel and patches, and at the end done reboot..
N1, after the boot , always stuck to X colored.
Fullwipe , after formatting , is indispensable?
Mistaken some transition or may be my N1 to have problems?
Rcadc 2.1 2.2 & -Cyano 7.0 .x 7.1 are working properly.
Help me please.
Sorry for the bad english.
Did you follow the script?
No swap required, and 2GB ext4 can be unstable, 1GB is more than enough.
And try first with standard kernel.
Hi ,I have followed the script step by step.
I have carried out several times the total wipe , but the final result is always the same: N1 blocked.
I tried also adb logcat during boot , but does not pass anything.
Reinstalling the Vers.2.2 everything works , also adb logcat.
These tests were made with a new Sd 4 Gb.
Therefore it is not a problem of the Sd and N1 , seems to be the Vers.2.3 not part on my N1.
I don't know tests do.
Thank you for the answer
same problam
I have the same problam, Rcads 2.2 working fine but 2.3 just stucks on the google X on stratup...
I've read it takes a long time to boot and i did try to wait for about an hour...
Did you wipe System before wiping data/caches
I run all the wipe repeatedly , from the first to the last.
The first thing i run the formatting and partition, then wipe and then flash the rom.
Bye
I did the same, wiping everything and I even tried to flash 2.2 which is working fine and then flashing 2.3 bt with no luck either.
anybody got an idea why it is stuck on the google X on stratup?
I have also tried to connect N1 to the pc ,via usb , with adb logcat. With the Vers.2.2 seen pass all the steps in the boot and loading HTC , while with the Vers.2.3 remains - Waiting device -.
It seems that with the new version does not start nothing.
same
i did the same, open logcat when rcads 2.2 running and everything's working great.
when i opened logcat while 2.3 tryed to run, i only get, Waiting for device aswell.
anybody know's the reason?
did any one got success in installing the latest version on N1
pls let us know so that the one who wants to install gets some courage to install it
pls guide me
thanks in adv..........
Some Info:
First things first: This is not my primary tablet anymore so If I can't get it working that is okay.
Second: I am trying to fix it for my parents or to sell it.
Third: It is the Sprint CDMA Version.
Okay so the problem with the tablet is when I turn on the device after flashing anything (whether it be the stock Gingerbread Rom via Odin/Heimdall or Cyanogenmod/AOKP) it works fine for a couple of moments... I set it up.. I open a couple of apps... and suddenly every single app starts to force close!!
On Stock it shows some apps like Swype and on ICS roms it shows some acore process.
I really want to know how to unbrick this and I can't send it in cause my warranty ended in February.
I'm also having a similar problem.
But I can't flash any ROM.
Even if I copy the zip file to the tab memory, after I reboot it, the file disappears. It always goes to Italian language. Can't remove the google account or the hotmail account.
I have tried to reset to factory defaults, etc and still the same...
Any ideas?
What android version your tablet have ?
AtaAlla said:
What android version your tablet have ?
Click to expand...
Click to collapse
Stock Gingerbread but the problem started when I had AOKP on it.
I tried flashing back to stock yesterday and now it's in a boot loop on the second Samsung logo after the Sprint logo.
The things that crash are android.process.acore, all gapps, Swype on stock, and Google Play.
Hello guys
i have bad news for you...
if you can't do wipe(i mean, you do it nothing change)
you need JTAG-spacialist
many people had problem with Sprint Tab
i am work on this problem-- i buying P1000 with same problem (2 weeks ago)
but now i see that is big problem
you have read-only movinand
i think it is /dev/block/mmcblk0p2 it is /data part
i find bad blocks , but i can't fix them
sorry for my terrible english
Hello Xda-Users:
I've been lurking this forum since I got my X8, like one year ago. I had a lot of problems with the stock kernel and ROM and they all got away when I flashed the excellent nAa kernel with the marvellous MiniCM7 rom. Anyway a few weeks ago I decided to try the S2Ext method in order to gain memory. I installed the app and prepared my sd card with variable results as I think it had a racing condition in which if the phone was booted and the sd card wasn't ready it made the cellphone crash in the worst of ways, though a reboot helped to get it straight.
Well I got fed up and decided to flash a fresh copy of MiniCM7 again so I could use the phone with no problems. Everything went OK except that the mobile connection now doesn't work. For convenience I will bullet point what I have done to this day in order to fix this:
I tried to repair the phone via PCC but it says it cannot find any software for my phone (Also it shows the phone as a X10 for some reason)
I tried to use SEUS but it crashed on start for no reason (My current pc is Windows 8 x64)
I reseted the partition in my SD card erasing the ext4 part
Got around and flashed a stock kernel I found with some ROM that could use it but that still didn't work
I tried my sim card over other cellphone and 3G worked
Of course I configured my APN accordingly and Mobile data is enabled
Also I ran a
Code:
logcat -b radio
and it showed a Wrong Network Type:0
Any hints? Every bit of information might help to solve this mystery.
Thanks!
Lisergishnu said:
Hello Xda-Users:
I've been lurking this forum since I got my X8, like one year ago. I had a lot of problems with the stock kernel and ROM and they all got away when I flashed the excellent nAa kernel with the marvellous MiniCM7 rom. Anyway a few weeks ago I decided to try the S2Ext method in order to gain memory. I installed the app and prepared my sd card with variable results as I think it had a racing condition in which if the phone was booted and the sd card wasn't ready it made the cellphone crash in the worst of ways, though a reboot helped to get it straight.
Well I got fed up and decided to flash a fresh copy of MiniCM7 again so I could use the phone with no problems. Everything went OK except that the mobile connection now doesn't work. For convenience I will bullet point what I have done to this day in order to fix this:
I tried to repair the phone via PCC but it says it cannot find any software for my phone (Also it shows the phone as a X10 for some reason)
I tried to use SEUS but it crashed on start for no reason (My current pc is Windows 8 x64)
I reseted the partition in my SD card erasing the ext4 part
Got around and flashed a stock kernel I found with some ROM that could use it but that still didn't work
I tried my sim card over other cellphone and 3G worked
Of course I configured my APN accordingly and Mobile data is enabled
Also I ran a
Code:
logcat -b radio
and it showed a Wrong Network Type:0
Any hints? Every bit of information might help to solve this mystery.
Thanks!
Click to expand...
Click to collapse
Full wipe the rom or reinstall if you can, & i got to say mobile data problems is not related to kernel (I'm taking about nAa & alf kernels,they're the most bugless kernel for x8)
Do not repair with seus or pcc, they'll lock your bootloader again
& remember to reduce paragraphs in the next thread so others will answer you
Sent from my E15i using Tapatalk 2