Related
Hi, I'm trying to help a fellow Atrix user after he formatted and partitioned the internal flash memory using Tenfar's CMW Recovery.
He has lost touch on the bottom part of his screen; about a 1/2" of screen space doesn't work.
Tenfar posted that he had done this too, and had resolved this by reformatting with the Stock Recovery. Another user asked in that same thread how he accomplished that, but no answer has been given yet.
This user cannot get the Recovery Menu to show up because of the lower touch screen not working.
Can the steps be run blindly without the Recovery Menu showing up?
Or, can someone help me on how to have him format the internal memory via ADB?
I've had him try the following ADB commands from both the /!\ Recovery Screen and after enabling Early USB Enumeration without luck.
Code:
adb shell
$ su
# format DATA:
Comes back with format: not found.
Can anyone help? I've seen a few others with this issue but have yet to see a full solution posted for those that aren't ADB experts.
I have this problem too! Tenfar was kind enough to try helping me but apparently I'm a retard and unfortunately can't follow his instructions. I've been spending an entire week reading hours each day and I'm embarrassed that I still can't fix it, despite him sending me almost a dozen PM's trying to do so. Very grateful but sad that I'm so dumb.
He's told me to do this:
$adb shell
$su
#busybox umount /sdcard (hit enter key)
#newfs_msdos -F 32 -S 512 -L MB860 -c 64 -u 16 /dev/block/mmcblk0p18 (hit enter key)
I'm not sure where to do this. I now think I do this while the device is in Early USB Numeration but I haven't tried it yet. The wife was getting really pissed because I spent the entire weekend trying to fix this and have been investing too much time on the computer. She's... having mad PMS so I'm leaving it for a few days lol
I tried earlier when the phone was booted up but after some research, believe it may need to be done in Early USB Numeration mode but there's only about a minute before it automatically reboots. I haven't tried this and hope that my assumption is correct. I know about 3 other people who are currently experiencing this challenge and I hope that it corrects it.
The wife is working a double shift today so I'll try after work. Can't blame her for getting upset with me. Soft bricked a few other phones but fixed them with relative ease. This has been by far the toughest. It was my birthday last week and I spent most of my day on the computer trying to fix my Atrix lol
After this, no more formatting internal SD partitions!!! Paypal is giving me grief but I plan on giving Tenfar a modest donation. He's been very supportive of my dumb ass lol
In this forum there is a very good guide on how to use adb. Can't remember where exactly it's at I just did a general search for How to use adb it may help you.
Edit I think this is the link androidsamurai.com/forum/viewforum.php?f=12
coldfusionb said:
In this forum there is a very good guide on how to use adb. Can't remember where exactly it's at I just did a general search for How to use adb it may help you.
Edit I think this is the link androidsamurai.com/forum/viewforum.php?f=12
Click to expand...
Click to collapse
Thank you!
I managed to install Ubuntu and I really like that.. tried from there too and it wasn't working. So I think it's definitely a problem with my dumb ass. If and when I get it working (I'm determined!...... and sort of stuck lol) then I'll post a guide.
Fuuuuuuuuuuck!!! Still not working!!
Yeah.. i ended up wiping with stock recovery and still a no go. Still no lower half of the screen or buttons. Sucks big time
Once ADB can be run in the recovery menu I think it should be fine.
Tenfar said he's fixed this problem but I'm no sure where he's run these commands. I feel bad after sending him a ton of PMs so I'm just waiting until he updates his Recovery app.
You could try restoring your sbf in rsd
Sent from my MB860 using XDA App
sgtmedeiros said:
You could try restoring your sbf in rsd
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
That's been mentioned and tried multiple times.
I have a simple script written with the command lines from Tenfar, but I am getting his input via PM to make sure it's correct and when exactly to run it. Hopefully he'll be able to direct me on how to get it done. Unfortunately, even if he says it looks right it's going to be completely untested. :-/
Sent via rooted Moto Atrix using Tapatalk
das8nt said:
I have a simple script written with the command lines from Tenfar, but I am getting his input via PM to make sure it's correct and when exactly to run it. Hopefully he'll be able to direct me on how to get it done. Unfortunately, even if he says it looks right it's going to be completely untested. :-/
Sent via rooted Moto Atrix using Tapatalk
Click to expand...
Click to collapse
There's still a glimmer of hope, buddy. Once we get ADB access in Recovery I think all should be well.. unless partitioning this block somehow corrupts and kills the digitizer or something.
I actually couldn't wait any longer. Ported to Bell and got a new Atrix so if things go bad I'll have an easier time swapping. When I fix this AT&T one I'll sell it to pay off my cancellation fee with Rogers. Or, if I end up sending it to Motorola I can go back with my buyer's remorse period and go back to Rogers.
Hope you've got a backup phone or something to use in the meanwhile, man. This issue drove me INSANE!!
Hope is good, but this isn't necessarily for me. That's why I can't test it; this didn't happen to my phone. I have just been trying to help those who this did happen to. I'm also sure it will continue to happen if the CWM port for our phones isn't preset to format correctly.
Glad you were able to get a working phone again, but too bad a phone had to go back under these conditions.
Well, I'll keep trying to figure it out; waiting on another reply from Tenfar. Our schedules don't mesh too well, so if there's anyone else that might have experience in formating via ADB any help would be appreciated. Thanks!
Sent via rooted Moto Atrix using Tapatalk
I have the same problem, I just wanna know if anyone found a solution to fix that?
Also, I live in Belgium (Europe), I bought the atrix in usa a month ago during my honey moon. Motorola Europe doesn't support yet the atrix, I don't know what to do!
The phone is not usable anymore, like someone said: "clicking on the soft button area registers as a click on the bottom of the screen". So, the back button don't work anymore (you have to reboot when your stuck in a menu!)
hi guys i'm currently with a reflashed stock 1.83 rom, i can use android recovery (there the bottom screen portion works) and i can run wipe data/cache.
but no matter how many times i tried when the phone finally boots up it starts with motoblur setup and i cannot pass it, all the buttons work like the bottom of the visible screen and i cannot raise up the keyboard to turn the setup off...
i read in the sbf thread that would be possible to flash or not some particular areas, so if the problems is the wrong partitioning of the /dev/block/mmcblk0p18
maybe some of them could create a sbf replacement toreflash only that partition
other side i was talking with bongd and he says he had problem with the psd.bin file that is in the mmcblk0p03...
so what is the current status of this? adb seems not to work even in early enumeration usb mode...
what if we execute the script using the update.zip function?
i can access my sdcard from windows in storage mode
if we put the script in one signed update.zip into the sd the phone should be able to execute itself?
KeRmiT80 said:
hi guys i'm currently with a reflashed stock 1.83 rom, i can use android recovery (there the bottom screen portion works) and i can run wipe data/cache.
but no matter how many times i tried when the phone finally boots up it starts with motoblur setup and i cannot pass it, all the buttons work like the bottom of the visible screen and i cannot raise up the keyboard to turn the setup off...
i read in the sbf thread that would be possible to flash or not some particular areas, so if the problems is the wrong partitioning of the /dev/block/mmcblk0p18
maybe some of them could create a sbf replacement toreflash only that partition
other side i was talking with bongd and he says he had problem with the psd.bin file that is in the mmcblk0p03...
so what is the current status of this? adb seems not to work even in early enumeration usb mode...
Click to expand...
Click to collapse
Tenfar told me it was mmcblk0p18 but it's actually mmcblk0p03 which needs to be corrected.
There's no ADB in recovery right now. Tenfar's apparently got it working but hasn't released it yet.
I also guarantee you can bypass the Motoblur setup as well. Hit these keys:
?123
ALT
ABC
e
?123
ALT
ABC
e
b
l
u
r
o
f
f
I'm positive because I've literally flashed every SBF and I've spent a lot of time troubleshooting this issue.
really i cannot open the keyboard while i'm in the blursetup screen, i keep pressing the menu button but it highlights only the emergency call and after many seconds it chance to emergency call screen...
At this time, your phone is 'bricked' since we can't get ADB access.
Sent from my MB860 using XDA Premium App
we don't have adb access but i tried and we can use the update function in the stock recovery...i tried to put a update.zip of my old milestone and the process worked till the sign verification that failed.
in the milestone that update.zip is used to run the updaterscript that launches the openrecovery by skrilax_cz, that works like the recovery of tenfar
i guess that if we have a correct update.zip for atrix and we put in it the script we need, it should be run.
unfortunately i don't have the knowledge to build the correct script and don't have access to a signed update.zip for atrix.
if we only could gain some interest of the devs i think our problem could be solved in short time...
edit: i sent 2 pm to tenfar but did not reply, maybe someone has more luck...
My viewpad 7 is boot-looping, it is restarting before reaching the launcher screen, and also stuck while booting into cw recovery mode. I changed font files of the root before this happened. Any way to restore it's rom without using cw recovery mode? Is it possible to boot from sd card?
Can you boot your VPAD7 into CW Recovery Mode ? (Hold down Vol. UP and Vol. Down buttons and press Power at the same time to get into recovery mode)
Anyway, you most likely need to flash a stock ROM first using the SUTL3_v1.7.9 utility available from Viewsonic and then one of the FM6*.nb0 files - it might not recognize or "see" the device, keep trying & reset/reboot and use that small "reset" button on the bottom if necessary.
Check your FTM (Factory Test Mode) for your Hardware & Software build info - and try to match the closest *.nb0 file for flashing. Hold down Vol. Down while pressing Power to start & run FTM, use tiny pin hole to press & reset device/exit this mode.
I haven't done this in a while, but it will most likely change the device back to unrooted, stock form. And, you will lose all your custom app settings - but it should come to life after a successful flash, restart & give it 5 to 10 minutes to complete initial install & setup - and, you should see your original screen again.
Then, follow steps to get it rooted again, do a NAND backup & set it aside for safe keeping, then reflash your choice of custom Rom, etc. Detailed directions are here on XDA - good luck & let us know if we can be of further help ....
I was making the root to my viewpad 7, and during the process, I took out the cable by accident. And now it's impossible for me that the process finish, it always stuck. Some ideas, please?
luisete123 said:
making root .... and during the process .... took out the cable .... And now it's stuck. Some ideas, please?
Click to expand...
Click to collapse
OMG, okay - relax & take a deep breath ....
It should be recoverable, I think - you will just need to flash the "proper" factory stock ROM first, get it working again & then repeat the rooting process.
First, check your hardware/software version in the FTM mode (it's for diagnostic, flash & download to ROM, etc. ....) & safe to do - hold down the left Volume Down key on top while pressing the Power button with the device off. If necessary, get someone to reset the device (use the smallest pin hole on the bottom of the device.) A pin works best but small paper clip will do.
In a few moment, it will show "Enter FTM Mode" and then display the VPAD7's info -
SWVer=3.410 or whatever is on yours
Model: FM6-0001 or whatever yours say
HWVer: 107 (106, 103 or whatever)
What to do with this info - it will help you select the correct or closest factory ROM to flash & restore your Vpad7 to stock condition, unrooted.
You will need one of the SULT3 or for oldest ROM, maybe SULT2 is better - download & save to PC, unzip the SULT* - and follow onscreen prompt & instructions to select your *.nb0 file.
Another suggestions, since you cannot get into Recovery Mode to wipe dalvik, cache & full system/data first, it might help to flash the *.nb0 file twice - it will take a bit of time, maybe 10 minutes or so and a few more minutes to do its initial boot-up configuration. Be patient - and write down any error messages, etc. if you run into problem.
It's best to take out any SIM card and even mSD card from your device, not required but recommended. When you can boot up again & get pass the Android activation wizard/screen, you can power down - put the mSD card back in and reboot again.
http://vsg.viewsonic.com/ViewPad7/
Good luck - there's a wealth of helpful info posted here, please set aside & take time to read it first & refer to those notes. Good Luck & Cheers - let us know if you succeed ....
A thousand of thanks Letitride!!
Before continue making mistakes, I want to ask if there is any problem to use SULT3 (because I read u posted it before) instead of SULT2, because yesterday, before post my question, I already installed SULT3_v1.7.9...
When I enter FTM Mode, the display shows:
SWVer=3.16R
Model: FM6-0001
HWVer: 106
So now I dont understand. I am a little bit lost, but I think I must to download something else from the viewsonic web that u posted (I can't repeat the link because I am new), isn't it?
Thanks again for your help. I know there are lots of help already posted, but about my problem I didnt find anything, that's why I asked. Thanks!!
Ok, I will explain what I tried, and the next error:
As I said, I already installed SUTL3_v1.7.9, so I used it. I downlodes for the viewsonic web that you posted FM6-316Q-0-1008-A01.nb0, and this is the error that the program said me:
Error Code: 0x4000
Error: Task 2 of 3, Download Image fail
Error = DEVICE_NOT_CONFIGURE (0x4000).
Maybe I need to uninstall SUTL3_v1.7.9 and try with SUTL2.1_v1.8.4? During the process I don't need to select nothing in the ViewPad screen, do I?
Thanks again!
EDIT:
I installed the SUTL2.1_v1.8.4 (without unistall the SUTL3_v1.7.9, and there is the next error:
Error Code: 0xf626
Error: Task 2 of 3, Download Image fail
Error = QPD_ERROR_ARMPRG_hello_TBUFFER (0xF626).
luisete123 said:
Ok, I will explain what I tried, and the next error:
I installed SUTL3_v1.7.9, FM6-316Q-0-1008-A01.nb0, the error:
Error Code: 0x4000
Error: Task 2 of 3, Download Image fail
Error = DEVICE_NOT_CONFIGURE (0x4000).
EDIT:I installed SUTL2.1_v1.8.4 (without SUTL3_v1.7.9, and next error:
Error Code: 0xf626
Error: Task 2 of 3, Download Image fail
Error = QPD_ERROR_ARMPRG_hello_TBUFFER (0xF626).
Click to expand...
Click to collapse
It looked like there might be a problem with your downloaded Image files itself - corrupted ? See if you can use a different PC to download the FM6-316Q again, and when you are ready to flash, put it in the same sub-directory as the installed SUTL2 sub-directory ....
Most likely, your device is non-ITE and as I recall, the FM6-3310 and 3350 nb0 files should work on your device & perhaps free of errors (not corrupted) - download it & try flashing it (besides, you got nothing to lose as your device isn't booting up anyway) - let us know what happen later.
Worst case situation, contact VS support & get authorization to return it for repair (if within warranty period)
Cheers & Happy "flashing" and let's hope one of the *.nb0 files work.
P.S. If anyone else has a working saved nb0 file for luisete123, please post a link for download or PM, whatever .... am sure s/he will appreciate our aid.
Letitride said:
It looked like there might be a problem with your downloaded Image files itself - corrupted ? See if you can use a different PC to download the FM6-316Q again, and when you are ready to flash, put it in the same sub-directory as the installed SUTL2 sub-directory ....
Most likely, your device is non-ITE and as I recall, the FM6-3310 and 3350 nb0 files should work on your device & perhaps free of errors (not corrupted) - download it & try flashing it (besides, you got nothing to lose as your device isn't booting up anyway) - let us know what happen later.
Worst case situation, contact VS support & get authorization to return it for repair (if within warranty period)
Cheers & Happy "flashing" and let's hope one of the *.nb0 files work.
P.S. If anyone else has a working saved nb0 file for luisete123, please post a link for download or PM, whatever .... am sure s/he will appreciate our aid.
Click to expand...
Click to collapse
Again thanks a lot Letitride!!!
I downloades it again in another laptop (FM6-316Q and SUTL2), and I did it and... IT WORKS!! I think it was a problem while I was downloading yesterday, because I don't know why, the speed was very very low. Otherwise I can't understand, because in this other laptop that I tried, the Windows is not original, and in mine it is...
So now, as I understand, I can root it without any problems, can't I? I will wait untill tomorrow, because I am on hurry now, and I dont wan't to do any more mistake
I am really greatful Letitride, thanks again!
luisete123 said:
Again thanks a lot Letitride!!!
I downloades it again in another laptop (FM6-316Q and SUTL2), and I did it and... IT WORKS!! I can root it without any problems, can't I?
Click to expand...
Click to collapse
Cheers - yes, we are happy for you. Never rush when doing these cool things to our device, I've seen stories about the family pet (cat/dog) jumping around & pulling the USB cable while it was doing .... you know, things happened but luckily, it was saved & you're recovered.
Now, you should be able to ROOT it again, just use SuperOneClick v1.7 & read/follow directions, or use GingerBreak.apk (it's easier but I've done both myself) - as soon as you do, boot back into ClockWorkMod Recovery, and do a BACKUP of your 316Q first, so that later on - you can easily flash the stock.
Then you can start to flash various custom ROM here, yours is most likely non-ITE hardware, so most of the ROM work - unless it is ITE specific. Good Luck & Happy Flashing.
Letitride said:
Cheers - yes, we are happy for you. Never rush when doing these cool things to our device, I've seen stories about the family pet (cat/dog) jumping around & pulling the USB cable while it was doing .... you know, things happened but luckily, it was saved & you're recovered.
Now, you should be able to ROOT it again, just use SuperOneClick v1.7 & read/follow directions, or use GingerBreak.apk (it's easier but I've done both myself) - as soon as you do, boot back into ClockWorkMod Recovery, and do a BACKUP of your 316Q first, so that later on - you can easily flash the stock.
Then you can start to flash various custom ROM here, yours is most likely non-ITE hardware, so most of the ROM work - unless it is ITE specific. Good Luck & Happy Flashing.
Click to expand...
Click to collapse
I am again really thank you! But, I still have the same problem... I am trying to use SuperOneClick v1.7 program, and again get stuck...
I will try with GingerBreak, but I was reading here another post about this program and I will need to read it again, in order not to make another stupid mistake!!
Cheers anyways!!
Wellp, I tried to install Cyanogenmod and it bricked the crap out of my phone. I followed their guide at http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide and got to the "The Samsung Vibrant now has ClockworkMod Recovery installed. Continue to the next section." step and upon my phone's startup (with the added Clockworkmod flash screen) was greeted with nothing but a black screen. All I see is the samsung "S," glowing for ten or so seconds, like the Windows logo, then it goes black. I tried One Click Unbrick (http://forum.xda-developers.com/showthread.php?t=1153310), which restarts my phone, and brings me back to the same screen. Next, I tried doing the three button (sound-up, sound-down, and power) boot into the Android System Recovery program. There, I deleted the cache data, all user data, and attempted to reinstall packages, but I got a "failed to verify whole-file signature" error, as well as a "signature verification failed" error. I also, tried to re-flash via ODIN, but the only way to get it to see the phone is to boot it to the S logo screen (and the darkness beyond). There is the no-man's-land that Odin detects. Unfortunately, Odin gets stuck at the connecting step, and goes no further (unless that takes more than a few minutes). Fun stuff.
I'm sure you get people asking for help all the time, so I am very sorry to be yet another person asking, but this is quite the frustrating brick.
I am able to boot into download mode, as well as the android recovery menu (the aforementioned area with clear cache, user data, etc.) so I have found a bit of solace in those facts.
Thank you so much for your time.
rushmix said:
Wellp, I tried to install Cyanogenmod and it bricked the crap out of my phone. I followed their guide at http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide and got to the "The Samsung Vibrant now has ClockworkMod Recovery installed. Continue to the next section." step and upon my phone's startup (with the added Clockworkmod flash screen) was greeted with nothing but a black screen. All I see is the samsung "S," glowing for ten or so seconds, like the Windows logo, then it goes black. I tried One Click Unbrick (http://forum.xda-developers.com/showthread.php?t=1153310), which restarts my phone, and brings me back to the same screen. Next, I tried doing the three button (sound-up, sound-down, and power) boot into the Android System Recovery program. There, I deleted the cache data, all user data, and attempted to reinstall packages, but I got a "failed to verify whole-file signature" error, as well as a "signature verification failed" error. I also, tried to re-flash via ODIN, but the only way to get it to see the phone is to boot it to the S logo screen (and the darkness beyond). There is the no-man's-land that Odin detects. Unfortunately, Odin gets stuck at the connecting step, and goes no further (unless that takes more than a few minutes). Fun stuff.
I'm sure you get people asking for help all the time, so I am very sorry to be yet another person asking, but this is quite the frustrating brick.
I am able to boot into download mode, as well as the android recovery menu (the aforementioned area with clear cache, user data, etc.) so I have found a bit of solace in those facts.
Thank you so much for your time.
Click to expand...
Click to collapse
which rom did u come from?
Froyo. I followed the guide to a 't' and got this black screen. I have no idea what I did wrong.
Well, I need to run off to work now, but I'd really appreciate any responses.
It seems like my phone isn't being detected by odin or windows when it is in download mode, though windows does recognize that a Samsung USB device is being connected. This is recognized in the windows tray (under the name "Samsung_Android"), and in Heimdall's Zadig driver tool ("Samsung_Android").
Hmm first tthings first, your reinstall package error seems pretty simple, yu dont have the right update.zip and recovery combination... if u wanna solve that problem, find the recovery 3e to 2e tool (google it) and run it (follow directions).. then you can run reinstall packages (might havr tto do it twice). If that doesnt cut it, find the CWM update.zip and put iit into the root of your internal sd card (the 12gb one), then run reinstall packages again. You may have to reinstall packages more than once.
Your odin problem might be caused by a lack of drivers on your comp... go on the android dev section and look for a thread talking aboout ms64 and 86 drivers samsung something...
If you can get into download mode, you can unbrick your phone so dont panic
Now odin is a very dangerous tool imo so if you really are sorry about askint, do us a favir and read the sticky oon how to odin before you use it so you dont have to come back and ask us about how to Really unbrick your phone
Also, your brick is referred to as a soft brick and the android recovery program is referred to as recovery mode.
And if you really **** up, we now have the unbrickable mod in the vibrant android dev section which will unbrick your phone no matter wat (it takes somr hardware modifying though)
Sent from a cell tower to the XDA server to you.
And if i were you, id redownload the cm7 package again to make sure that it wasnt a bad download and id read some general vibrant info before diving into cm7... if youre running stock recov and have never odined before etc, youre prob not the best candidate for flashing.. just my opinion
Sent from a cell tower to the XDA server to you.
Thank you very much for your reply. I couldn't find a related tool with the Google search string "3e to 2e recovery tool vibrant," but I did find a modified 3e tool at dkszone(*)net/bypass-e-signature-verification-fail-issue-on-samsung-vibrant-android-2.2 . However, this gets stuck at "checking for temporary root."
As for installing drivers, I have installed the Samsung galaxy 64 bit drivers several times now, but I'll give the 32 bit drivers a whirl as well.
I am unable to access the SD card, and don't have a mini SD card reader, so that compounds the problem (damn my lack of cash!).
*Edit* Upon my attempted installation of the 32 bit drivers I get the following (word for word) "Swallowtail has being used. You need to eject device and reboot your computer. Rerun (Japanese or Chinese characters) after reboot your computer." Google returns zero results when I search for this error. I tried rebooting my computer and running it again, but got the same error (even with the phone unplugged from the computer).
*Double Edit* I've been trying to use the AIO Vibrant Toolbox to restore my phone to factory defaults, but I've been having no luck, as it claims my phone is not in USB debugging mode (and obviously I can't change this, as I have no access to the Android OS).
Try this, mate and hopefully you will be up and running soon...
http://forum.xda-developers.com/showthread.php?t=1278683
When I run this the program handshakes, downloads the pit file, then restarts and "...Local and device PIT files don't match and repartition wasn't specified!
Ending session...
Rebooting device...
Device not connected.."
It reboots to the black screen of death and stays there. Perhaps I could select "Flash Bootloader," but the warning of possible permanent damage scares me.
According to the thread...
"REPARTITIONING ISSUE WITH HEIMDALL 1.3.0
Heimdall currently has an issue with repartitioning. 99% of the time you will not need to repartition. Failure to follow these directions can possibly lead to bricking:
Do not flash bootloaders if you see this message:
Code:
Local and device PIT files don't match and repartition wasn't specified!
This message means your partition tables do not match the firmware."
So I guess one of the roots of my problem is that my partition tables do not match the firmware. I have no idea what to do about that.
In this case try another computer if you can, install the right drivers and see odin recognizes your phone. I'm sure it will, for some people sometimes it takes fair few tries for no reason.
Another suggestion, take out sim card and external sd while connecting in download mode. Sometimes that helps.
---------- Post added 29th September 2011 at 12:01 AM ---------- Previous post was 28th September 2011 at 11:43 PM ----------
Here is a recent thread where someone had issue with odin connection.
http://forum.xda-developers.com/showthread.php?t=1225197#16797271
Well, I ran Heim one click on another computer and had the same boot-to-blackscreen process happen.
I was, however, successful at getting Odin to recognize the phone with AIO vibrant toolbox. Odin kept getting stuck at "set pit file" though.
Baby steps...
This is so frustrating. I feel like I'm so close.
How do I get the right PIT file on my phone if ODIN is getting stuck at that step?
Now, after installing the drivers provided with Heimdall-one-click's Zadig, ODIN doesn't recognize the phone.
One step forward, two steps back.
*Edit* Nevermind, got ODIN to recognize it again by uninstalling/reinstalling all related drivers.
Then odin to stock with tthe stock jfd files.. follow the manual, report results
Sent from a cell tower to the XDA server to you.
http://forum.xda-developers.com/showthread.php?t=734475
Use those files and the procedure for ODIN.
As for what caused your problem. You flashed a clockwork recovery for a different phone, possibly the Vibrant (non-MTD) mode? Usually installing Clockwork on the Vibrant only works from ROM Manager app when its running stock JFD. At least for me anyway. Any other ROM it ****s it somehow and I end up in a situation like yours. Not to worry though. Here's a quick install guide after you ODIN the phone to stock.
Put latest nightly of CM7 on the phone memory (not external microSD)
Install clockwork (Easiest way to do this is put the update.zip file I've attached onto the root of your phone memory, not the external microsd card, then reboot into recovery (hold both volume buttons and turn it on) and select Reinstall packages twice. It will then boot you into Clockwork).
Wipe data and cache in clockwork
Install zip from SD card--> pick the latest CM7 nightly.
DONE.
I'd like to use those files, but every single link is broken...
*Edit* Never mind. Found another source. I'll post upon success/failure.
*Edit again* Actually, it doesn't seem like the new link on mediafire has all the files required by the process (OP: http://forum.xda-developers.com/showthread.php?t=734475), and I can't post in that thread (because I'm a new user).
This is the post that uploaded the files: http://forum.xda-developers.com/showpost.php?p=17512889&postcount=615
So I haven't changed a damn thing yet, and all that happens when I try to put the phone in download mode is | Phone----Warning (!) Sign----Computer | screen comes up.
Even when I only plug it into a power outlet...
Flashing the IPhone was easier and more stable than this, years ago. I honestly expected better from Google.
*Edit*
OH MY GOD. Odin is going somewhere! Go, AIO Vibrant Toolbox, Go!
*Edit again*
And it stopped at about 90% with "<ID:0/003> dbdata.rfs
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
"
Well, I tried again and everything finished uploading, and got the green "pass!" for the first time in Odin.
Now my poor little 959v is stuck in a booting loop. The Samsung Vibrant screen comes up, disappears, comes up again, disappears, ad infinitum.
rushmix said:
Well, I tried again and everything finished uploading, and got the green "pass!" for the first time in Odin.
Now my poor little 959v is stuck in a booting loop. The Samsung Vibrant screen comes up, disappears, comes up again, disappears, ad infinitum.
Click to expand...
Click to collapse
959v is the not the vibrant, tis the galaxy s4g, if you odined vibrant files on your 4g then that's why you are in a bootloop
Dear god do I feel stupid. I googled it a while ago just to be sure, and it seemed to say that the V stood for "Vibrant." I guess that would be why I've been having this sneaking suspicion...
Well it's good news for you, mate. Head over to galaxy s 4g
forums and hopefully you will be able to get your phone back.
Hello everyone,
As this is my first post, i'd like to apologise in advance if this issue i'm about to detail has been posted before, but after about a month's worth of trial and inevitable error, reading everything i could find and following every walkthrough i've come across to the t...i'm at wit's end here.
So, i've got a Galaxy SII GT i9100, standard euro version i suppose, my provider is Vodafone Romania (wretched buggers the lot of 'em).
My troubles had started ever since the update from 2.3 with which the phone had arrived, to 4.0.3. I made the update through my home wifi, and i'm guessing the software was provided by either Google, Samsung or Vodafone Ro.
In any case, 4.0.3 was a lot more sluggish and badly calibrated in terms of touch responses and video lag while streaming.
About a month ago i got another notification to update to 4.0.4. This update worked fine for about 20 minutes till the thing decided to freeze up completely, and not turn off from the power button held down a while.
After i had removed the battery and turned it back on, i simply got the following message: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Naturally Kies is a steaming pile and recovery fails every time with a message composed only of empty squares instead of text, i'm guessing it's because i lack a certain language pack, but the only option is "OK".
So i turned to Odin, when that failed, instead of wiping the counter before sending it into the warranty, i did not. so they voided my warranty because it seems Odin is "unauthorized".
Multiple tries and failures later, quite a few attempts by other people that know more about this than myself...some have said i've got corrupt flash memory while other say "NAND rw corruption".
I'm a rather experienced pc builder...but this seriously stumps me.
I've also tried the walkthrough here on XDA with the same results.
So any new input would be much appreciated...be it through skype or another medium.
can you enter the download mode, if yes then try flashing stock firmware which comes with .PIT file (using odin)......may be that will help
try this thread as well http://forum.xda-developers.com/showthread.php?t=1457458
RazorwireClouds said:
Hello everyone,
As this is my first post, i'd like to apologise in advance if this issue i'm about to detail has been posted before, but after about a month's worth of trial and inevitable error, reading everything i could find and following every walkthrough i've come across to the t...i'm at wit's end here.
So, i've got a Galaxy SII GT i9100, standard euro version i suppose, my provider is Vodafone Romania (wretched buggers the lot of 'em).
My troubles had started ever since the update from 2.3 with which the phone had arrived, to 4.0.3. I made the update through my home wifi, and i'm guessing the software was provided by either Google, Samsung or Vodafone Ro.
In any case, 4.0.3 was a lot more sluggish and badly calibrated in terms of touch responses and video lag while streaming.
About a month ago i got another notification to update to 4.0.4. This update worked fine for about 20 minutes till the thing decided to freeze up completely, and not turn off from the power button held down a while.
After i had removed the battery and turned it back on, i simply got the following message: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Naturally Kies is a steaming pile and recovery fails every time with a message composed only of empty squares instead of text, i'm guessing it's because i lack a certain language pack, but the only option is "OK".
So i turned to Odin, when that failed, instead of wiping the counter before sending it into the warranty, i did not. so they voided my warranty because it seems Odin is "unauthorized".
Multiple tries and failures later, quite a few attempts by other people that know more about this than myself...some have said i've got corrupt flash memory while other say "NAND rw corruption".
I've also tried the walkthrough here on XDA with the same results.
So any new input would be much appreciated...be it through skype or another medium.
Click to expand...
Click to collapse
sorry i forgot to mention that i can enter Download mode using Vol. down + home + power, BUT...i can't enter recovery mode or whatever it's called with Vol. up + home + power...that button combo only starts the phone with the same old error message.
also, i've tried this walkthrough
as far as i know if you can enter into download mode, your phone is not dead...........................i don't know much about android development but i am sure that your phone can be revived...........keep searching the forum and try contacting some of the sgs2 developers they might be able to help you
cheers
RazorwireClouds said:
sorry i forgot to mention that i can enter Download mode using Vol. down + home + power, BUT...i can't enter recovery mode or whatever it's called with Vol. up + home + power...that button combo only starts the phone with the same old error message.
also, i've tried this walkthrough
Click to expand...
Click to collapse
pretty much what i'm thinking as well, there should be a way to restore it without resorting to cannibalism and taking a broken phone's mobo.
but i have been searching and being new to these forums i've no clue who to contact, but anyways, thanks for the reply sir. my thanks
bumpdonkey.
Come on,are you trying different things like disabling kies/USB cables/ports/different PC.
Have you tired flashing the stock Rom through Odin? You can find it at sammobile.com.
Sent from my SGH-I727 using xda app-developers app
as i've stated in the first post, i've tried almost everything. this includes flashing a series of different roms, kernels, pits etc.
as well as trying it with kies uninstalled, and since it's been attempted by other people, i'm guessing it's superfluous to try it on another PC than my own because others have already done so with it. and the cable is just a cable.
i have the same problem and i still searching
when i try to mount the data partition it fail
i tried all things but still no solution
come on guys help us to revive our sgs2
so far, the most i've accomplished was bringing it from the error message to the boot screen where it remains forever...by flashing the bootroom.
but if i tick "nand erase all" it fails to do anything.
No bumping
Do not bump this thread. The answer will come because someone knows it, not because it's bumped every few hours.
which reatmne
sorry about that, i'll cut the bumping then...i'm just...beyond frustrated at this point...it's been a brick for about a month now...nobody seems to know how to fix the blasted thing
Maybe...
I had once got stuck.
If you could get to the recovery, i think you can try wipe data, wipe data, wipe data....................
Then flash stock rom, or those you think is reliable.
wipe and flash. wipe and flash.
If you can't, use ODIN....... the only way
flash and flash the stock rom or any others.............
if it works, there you are.
Hope it works!!
you may wanna read the whole topic before replying, just saying
Your phone's obviously stuffed and only one of two (but 95% likely only one) things is going to fix it (nothing anyone here can suggest will).
I think you know what they both are. Continuing to post to this thread is simply delaying getting your phone fixed or getting another phone.
RazorwireClouds said:
you may wanna read the whole topic before replying, just saying
Click to expand...
Click to collapse
Exactly pal.Surprised he didnt say "if only you could boot up the phone you wouldnt need to get it repaired"......lol
MistahBungle said:
Your phone's obviously stuffed and only one of two (but 95% likely only one) things is going to fix it (nothing anyone here can suggest will).
I think you know what they both are. Continuing to post to this thread is simply delaying getting your phone fixed or getting another phone.
Click to expand...
Click to collapse
if i may ask what are thee two things which are going to fix the phone cuz mein is in the same situation thanks
I'm stuck in a similar position I'm stuck at galaxy s2 boot screen can get to download mode but not recovery I havnt tryed Odin yet only because I don't know what I'm.doing with Odin could somebody direct me on where to get the right files n stuff for Odin please I would be really gratfull thanks
Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app
Google Odin 3, use the 1.85 version. Get the stock Rom from sammobile.com for your device. Unzip Odin and then run it. In PDA browes to the stock Rom. Make sure only auto re boot and F. Reset are checked in odin. Then hit start. Check the stickies for more details. See vincom's in the development forum.
Sent from my SGH-I727 using xda app-developers app
Cheers mate am all sorted now bk rooted with the rom I wanted lol
Sent from my GT-I9100 using xda premium
Model: SM-G900T (T-MOBILE, USA, 16GB EDITION)
My Samsung Galaxy S5 is rooted. But I am not sure what caused my phone to get stuck in the bootloop. As I have been rooted for about 2 years and its been working fine. Also I was not manually installing any updates, mods or anything of the sort. Just tried to turn on my phone one day and it was stuck on the boot screen ( Samsung logo).
When I try to go to recovery mode I get the error:
Movinand checksum confirmation fail
If I try to install stock firm ware I get(odin):
There is no pit partition
If I try to install pit partition with the firmware or twrp I get(odin):
Complete (write) operation failed
Also whenever I try to flash with odin on my phone I get the error:
Mmc_read fail
Anyone know what might be the issue? Been tryingd to fix my phone fore quite awhile now.
Also sorry I didn't post any pictures! I'm going try and get 10 posts as quickly as I can so I can post some pictures.
Any advice is appreciated! Thanks!
-aj
ajxabstract said:
Model: SM-G900T (T-MOBILE, USA, 16GB EDITION)
My Samsung Galaxy S5 is rooted. But I am not sure what caused my phone to get stuck in the bootloop. As I have been rooted for about 2 years and its been working fine. Also I was not manually installing any updates, mods or anything of the sort. Just tried to turn on my phone one day and it was stuck on the boot screen ( Samsung logo).
When I try to go to recovery mode I get the error:
Movinand checksum confirmation fail
If I try to install stock firm ware I get(odin):
There is no pit partition
If I try to install pit partition with the firmware or twrp I get(odin):
Complete (write) operation failed
Also whenever I try to flash with odin on my phone I get the error:
Mmc_read fail
Anyone know what might be the issue? Been tryingd to fix my phone fore quite awhile now.
Also sorry I didn't post any pictures! I'm going try and get 10 posts as quickly as I can so I can post some pictures.
Any advice is appreciated! Thanks!
-aj
Click to expand...
Click to collapse
Do you want the good news or the bad news first?
The bad news- it's a hardware issue. And of course being a hardware issue there's no fixing it. Mmc stands for multimedia card. So your entire internal storage/partitions are probably dead.
The good news though- the s7 is out.......
Darn, is there a test to know if it is a hardware issue for sure? Im mostly worried about important data I still have on the phone. Is there at least some hope to recover it ?
-thanks
Aj
ajxabstract said:
Darn, is there a test to know if it is a hardware issue for sure? Im mostly worried about important data I still have on the phone. Is there at least some hope to recover it ?
-thanks
Aj
Click to expand...
Click to collapse
I can confirm it is indeed a hardware issue. An MMC read fail error means there was an error reading a file or files on the MMC chip. This could mean the entire storage chip is dead, or it could mean (and this is less likely based on the use patterns described) one or more parts of the chip were corrupted.
Either way, you won't be able to get anything off that phone, sorry. If you have an SD card in the phone, it should be fine.
If you're looking for new phones, I suggest a Nexus, they're easier to root and always get Android updates.