Related
Hi guys, need some advice. I have read allot of confusing/conflicting info on this and I just want some clarification as a precaution.
I have a P1000 and am currently on the latest nightly of CM9 but I read about MTD and possible brick if flash incorrect rom. What I want to know is, is it safe to re-stock using Overcome and also to come back directly to CM9 or do I need to follow some other procedure first?
I previously came straight from Overcome to CM9 without issue but not sure if same goes for going back?
Sorry if this has been covered but couldn't find any clear cut answers.
Thanks in advance.
Actually I don't think it will cause hard brick.
At most you need to restock using Odin.
But no, you can't convert an MTD partition (running yaffs2) back to Overcome ext4 fs.
You need to restock with Odin with pit file selected.
EDIT: the updater can convert FROM ext4 to YAFFS2, so you go from Overcome to CM9 direct but not the other way round.
priyana said:
Actually I don't think it will cause hard brick.
At most you need to restock using Odin.
But no, you can't convert an MTD partition (running yaffs2) back to Overcome ext4 fs.
You need to restock with Odin with pit file selected.
EDIT: the updater can convert FROM ext4 to YAFFS2, so you go from Overcome to CM9 direct but not the other way round.
Click to expand...
Click to collapse
Well there isnt really any other brick then "hard" brick. If you can still use download/cwm etc then its not bricked at all. I think the term is just used far too loosely nowadays.
When I mentioned stock with Overcome I was referring to overcome safe stock guide/files, So its safe to re-stock with them after using CM9, I just need to repartition etc?
Thnx for reply bud.
pretty much it.
restock to GB-stock-safe-V5 with repartition should get rid of MTD safely.
MTD and EXT4 are different partition styles. All you need to do, as per priyana, is go to download mode, run odin, select the .pit file, check the re-partition and shoot. That will get you back to the stock partition style.
Actually....BML and MTD are partition type.
EXT4 and YAFFS2 are filesystem types.
Sent from my GT-P1000 using XDA
Can anyone help me?
I've did the exact thing that you're not supposed to do. Flash fra a MDT rom to a non MDT rom. Now whenever i try ti reflash to stock rom i'll get a bootloop. Not just with this rom but with all other roms. But if i try to flash the AOPK rom with MDT partition it boots fine.
How do i partition that MDT partition to stock?
Wrong to say not supposed to.
That in fact is how most if not all of us get to mtd rom.
How else to go to mtd if not from non mtd.
To flash back to stock, flash with Odin with pit file selected and repartition checked.
Sent from my GT-P1000 using XDA
Ok Safety Advice:
1st to go back from MTD to any file system whether RFS or EXT4 a FULL RESTOCK with with REPARTITION is mandatory (no workaround or shortcuts around that).
2nd Safety Advice. Since the dawn of the MTD CM9 has requires repeated attempts to restock. I would say you need to Strip the stock safe package from the bootloaders (just Delete boot.bin and sbl.bin files from the tar archive). They aren't needed anymore after you have jumped Ship from Froyo to GB. Also Bootloader bad flash is the only way really to brick a Samsung Device as you may have known.
Just my 2 cents.
So, it is not as easy as ABC to revert back to GB from CM9?
I see that GB-Stock-Safe-v5 has got everything in the package (including the dbdata.rfs that gives many people trouble). If after flashing it with a pit still does not work, what else can we do?
I found this youtube on moving from MTD back to BML, but on Samsung EPIC.
www.youtube.com/watch?v=ds9rwAoI2IQ
I know it's probably a stupid noobie question, ... but I did forgot to do this simple thing so many times:
You did a factory wipe and cache data wipe, right?
did you flash it like documented in the picture attached by phlooke here ?
http://forum.xda-developers.com/showthread.php?p=20974872
priyana said:
did you flash it like documented in the picture attached by phlooke here ?
http://forum.xda-developers.com/showthread.php?p=20974872
Click to expand...
Click to collapse
Oh, I am not the one in trouble (knock on the wood). I give comment because I also see his post on AOKP while I'm learning about the ROM. He mentioned that he already did repartition:
http://forum.xda-developers.com/showthread.php?t=1523174&page=168
Ah I see.
Well, I don't know what he did.
But if he re-stock. he should at least boot up the JQ1 stock rom and confirms everything is ok, which I am sure it was not yet ok for him.
He shouldn't go ahead with Overcome Kernel yet.
You have to proceed logically and rule out each possible cause of problem.
you cannot go back from mtd to ext4 so easily. you need to flash gb stock package via odin or heimdall to go back to ext4 from mtd. cwm will not work
Actually going back to stock means going from mtd to bml, not ext4.
And it will then format the partitions with RFS file system.
You only get ext4 if you flash overcome kernel.
Sent from my GT-P1000 using XDA
Already tried flashing stock rom with odin, and checking re-partition, didn't help.
Anyway it's working now ^^
@jakk212 -Please post your problem at ONE thread buddy. I'm sure you did not even see my reply at the AOKP thread.
----
And STOP flashing GB-stock-safe over and over again. I am very greatful teamovercome created it but sometimes there are easier and better solution than forcing it down your throat.
-----
As I said in the AOKP post, (actually the link I provided with it)
what I did was, I reverted to a 2.3.3 gingerbread STOCK downloaded from sammfirmware OR check.fus downloader attached it with .pit file(please search or use the one included with ODIN) while checking the repartition.
After finish, mostlikely you will still be in the bootloop because many ROMs do not inclide dbdata.rfs.
Flash dbdata.rfs.tar (please search).
when u r done flashing dbdata, reboot, and wait on the 'samsung' boot for as long as 10minutes for it to update the partition and retrieving and reading and updating.
Don't assume it is on a bootloop forever before you waited at least 10 minutes on SAMSUNG boot.
Jakk212 said:
Already tried flashing stock rom with odin, and checking re-partition, didn't help.
Anyway it's working now ^^
Click to expand...
Click to collapse
Anyway it's working now
(without telling us who tried to help, what did you do, for the benefit of others)
oh well... all good for you. That is good to hear.
Just wish you can share.
Ah! I missed that one short sentencd.
priyana said:
Anyway it's working now
(without telling us who tried to help, what did you do, for the benefit of others)
oh well... all good for you. That is good to hear.
Just wish you can share.
Click to expand...
Click to collapse
Dude relax;
I've followed the overocme stocksafe guide, but when flashing i've also included the modem.
So i've did the same as before but flashed the modem and it worked.
Sorry for spamming.
Hi, I beg you for help. I have updated my ROM ginger to ICS N7000XXLPY_N7000OXALPY_DBT. The next step I took was to wipe my mobile through CWM. I was trying to install android stock ROM but the setup stops at the very beginning (N7000XXLC1_N7000OXALC1_OXA, N7000ZSLPF_N7000OZSLPF_OZS <= these are ROMs which I have tried to install). Below there is a screen with the installation process and its end because there is no progress. I have tried to upload boot files (N7000_APBOOT_N7000ZSLPF_CL558430_REV02_user_low_ship.tar) but it didn't work either. While mobile is turning on there is an information which says that I should communicate with KIES.
Please anyone to tell me which ROM needs to be used and what files are needed in order my mobile to work properly.
elvisthc said:
Hi, I beg you for help. I have updated my ROM ginger to ICS N7000XXLPY_N7000OXALPY_DBT. The next step I took was to wipe my mobile through CWM. I was trying to install android stock ROM but the setup stops at the very beginning (N7000XXLC1_N7000OXALC1_OXA, N7000ZSLPF_N7000OZSLPF_OZS <= these are ROMs which I have tried to install). Below there is a screen with the installation process and its end because there is no progress. I have tried to upload boot files (N7000_APBOOT_N7000ZSLPF_CL558430_REV02_user_low_ship.tar) but it didn't work either. While mobile is turning on there is an information which says that I should communicate with KIES.
Please anyone to tell me which ROM needs to be used and what files are needed in order my mobile to work properly.
Click to expand...
Click to collapse
Now this is exactly the same place where I am also stuck by using PC Odin .. but i am installing GB ROM KL1_KL3 (India version).
Please help guys ..
Ok, Try to get a stock GB firmware and flash it WITHOUT pit files and repatition and bootloader update and see if it improves, If it doesnt, you may need to flash the patched pit files which are for recovering bricked notes.
How this you get like this ? What was your previous set up ? Did you have ICS ? Did you do a full wipe ?
elvisthc said:
I have updated my ROM ginger to ICS N7000XXLPY_N7000OXALPY_DBT. The next step I took was to wipe my mobile through CWM.
Click to expand...
Click to collapse
You mean stock CWM ?
if yes then that was biggest mistake you did.
It seems you became victim of super brick bug
Man this is the 3rd or 4th of these I've seen today..
Sorry but the good Dr is right, It would appear you have turned your device into a paperweight - but hopefully have warranty..
If not then there is still hope, albeit not the most ideal option..
Please people Read, read and read again, before flashing Research is the best way to avoid this... If you want to ask a question then ask, if you feel like a n00b so what, We've all been there...
This forum is filled with good guys and gals who will help out with anything, It's just a shame that the questions seem to come too late....
Good luck man...
azzledazzle said:
Ok, Try to get a stock GB firmware and flash it WITHOUT pit files and repatition and bootloader update and see if it improves, If it doesnt, you may need to flash the patched pit files which are for recovering bricked notes.
How this you get like this ? What was your previous set up ? Did you have ICS ? Did you do a full wipe ?
Click to expand...
Click to collapse
I had update of German ICS, rooted system and hidden root, in CWM I did full wipe :/
elvisthc said:
I had update of German ICS, rooted system and hidden root, in CWM I did full wipe :/
Click to expand...
Click to collapse
Hopefully once replaced - while waiting for it you can get your 'trigger finger' under control
azzledazzle said:
Ok, Try to get a stock GB firmware and flash it WITHOUT pit files and repatition and bootloader update and see if it improves, If it doesnt, you may need to flash the patched pit files which are for recovering bricked notes.
How this you get like this ? What was your previous set up ? Did you have ICS ? Did you do a full wipe ?
Click to expand...
Click to collapse
im in the same boat, yet i believe after brainstorming with CJSlim, that the issue on mine is one that can be cleared through adb push and clean the error coming from the cache file in recovery
I will post back after trying this today
Sent from my Transformer Prime TF201 using XDA premium HD
Devices - 64Gb Asus Transformer Prime rooted .28 Stock ROM
32Gb Asus Transformer completely stock
HTC Sensation XL running 4.0.3 with Musketeer ROM Sense 4.0
Samsung Galaxy S Running 4.0.3
HTC HD2 Leo, overclocked 1.4GHz 1 Gb RAM 4.0.3 tytung ROM, long live the LEO legend
right after hours of trouble shooting and trying different things yesterday i have come to the conclusion that my sons galaxy s i9000 will not wipe its memory in anyway at all, now i believe this could be down to the fact he has a virus on the phone of there is some software problem with the phone, has anyone ever had this problem or no a fix for it please, i have tried a few recovery roms now to no joy and tried flashing through odin but nothing seems to wipe the memory anymore.
thanks in advance
So I assume that
A.) The Factory reset setting under "Security" in Settings didn't work, and
B.) Wiping through recovery (no flasging, just wipe data and cache) didn't work either?
Unless you're going from 4.x.x to 2.3.x, flashing roms throuh Odin won't wipe data. If you're flashing a Gingerbread rom over another Gingerbread rom, no data is lost.
Same goes for recovery. If you're flashing roms through recovery, especially of the same version number, no data is lost.
Note that going from ICS to JB will wipe data automatically.
Sent from my GT-I9000 using xda premium
I don't know what rom you are using but you can try install gb with odin using pit file for the repartition to take place.
Did you already followed and tried all the things from your last thread? Especially the additional advices from @wGRV and @popic_u (just posted above), which are btw also mentioned in the HowTo in the rescuepack? And why is a new thread necessary? Just wondering . If you do the restocking via odin propper, with a 3 parted rom and with pit file and Re-partition ticked, as mentioned, then I should work...I never had a problem with restocking and following these steps.
rodman01 said:
Did you already followed and tried all the things from your last thread? Especially the additional advices from @wGRV and @popic_u (just posted above), which are btw also mentioned in the HowTo in the rescuepack? And why is a new thread necessary? Just wondering . If you do the restocking via odin propper, with a 3 parted rom and with pit file and Re-partition ticked, as mentioned, then I should work...I never had a problem with restocking and following these steps.
Click to expand...
Click to collapse
yep sorry about new thread, yes i tried all of the above and the rescue packs and nothing seems to be working on it at all, i myself have a galaxy 2 and never have come across any of the problems when flashing a new rom even from going to ICS and JB, it seems the internal memory can not be wiped at all so making me think its a problem with the phone its self, thank you guys for all your help so far its been great.
So I am trying to do a favour for a friend as their i9000m seems to be at the least, soft bricked.
I was able to find out that they had tried to use Odin to flash a rom on it to fix "something". Knowing that a mistake in Odin can make a mess, I bet that is what wrecked things. However, reflashing with the stock Bell Mobility ROM did not work. The following screen is what was happening BEFORE it was given to me to look at it and is still coming up.
Any help would be appreciated!
que3jxp said:
So I am trying to do a favour for a friend as their i9000m seems to be at the least, soft bricked.
I was able to find out that they had tried to use Odin to flash a rom on it to fix "something". Knowing that a mistake in Odin can make a mess, I bet that is what wrecked things. However, reflashing with the stock Bell Mobility ROM did not work. The following screen is what was happening BEFORE it was given to me to look at it and is still coming up.
Any help would be appreciated!
Click to expand...
Click to collapse
what screen? the picture? or use this i9000M Upgrade or Downgrade GB 2.3.3 UGKG3 ROM + UGKG3 Root & CWM + 512 PIT Ideal base for upgrading to ICS and JB
Check this out! Links to useful Guides and " Banned " Documentaries
Yes indeed the pictures I attached to the post.
Sadly, I tried your files and the PIT and it did not to anything more than with the ones I already had. (PIT not withstanding as I have never fussed with those in the past)
The phone is still doing the same thing after a restart. In my mind, it should have worked as there were no errors in the log from ODIN. I have tried straight factory flash and the CWM rooted Kernel.
I have also tried Heimdall with a rooted CWM Kernel and that does not work either. It says all went well but then nothing
As an owner of one of these i9000m models, this should not be this hard but who knows what the owner actually did to this when he tried to flash with ODIN.
que3jxp said:
As an owner of one of these i9000m models, this should not be this hard but who knows what the owner actually did to this when he tried to flash with ODIN.
Click to expand...
Click to collapse
Look here under unbricking and try to flash the pram.lfs
Check this out! Links to useful Guides and " Banned " Documentaries
Well, I tried that and also tried a lot of other things on that page. The closest I got was using the ezbase recovery kit.
After doing that package, I got the attached errors... I assume that that is REALLY bad and that whatever happened to this guy's phone, it is terminal?
que3jxp said:
Well, I tried that and also tried a lot of other things on that page. The closest I got was using the ezbase recovery kit.
After doing that package, I got the attached errors... I assume that that is REALLY bad and that whatever happened to this guy's phone, it is terminal?
Click to expand...
Click to collapse
as long as you have download mode, its not terminal, but the problem is your attached images shows nothing but a process still in motion, NO errors are mentioned.
Check this out! Links to useful Guides and " Banned " Documentaries
whoops... the attachment did not take...
Here it is... I hope
que3jxp said:
whoops... the attachment did not take...
Here it is... I hope
Click to expand...
Click to collapse
according to this 3 of your partitions are not in rfs format for stock ROM's to function , meaning they had been converted to Ext 4, 3 o2 as such stock which use rfs format , cannot use them
1) SD card, data partition and cache partition all need to be formatted back to rfs first..so use the CWM to reformat them back to rfs ..read this guide and others mentioned within to get an idea on how it can be done
Check this out! Links to useful Guides and " Banned " Documentaries
Nope. Nothing.
The worst part is that I can NEVER get into recovery mode. Not once with any of the flashes for anything. Sometimes when trying to get into recovery, the screen is just black. Earlier or if I were to flash back on all of the stock firmware, it will just go to the first screens I attached in the OP.
I am thinking that this is a lost cause as most of the solutions are to use an external SD and that is not something that is going to be pursued as he does not want it that bad...
Let me know if you have any other ideas but otherwise, thanks for the help you have given and Merry Christmas!
Ok, please don't laugh, but I'm a stay at home mum and I've just installed Mackay JB 4.2 (the file said 2.999 if that helps). I did a lot of research and successfully rooted and did the rom flashing. I even re-flashed a couple of times because I kept getting the keyboard isn't working error, so I've left off the gapps package for now. The 3.99 file still gave the error even without the gapps. So I feel quite chuffed BUT please excuse my ignorance, where on earth are some of the apps now (I know it all got wiped), but I thought the Superuser, Titanium, and CWM icons would still be there in the apps and they're not. Also, I downloaded (or tried) Root Browser (as I'm not sure if the IMEI was backed up and wanted to make sure before I proceeded) and it said it was installed but I can't find it anywhere. On one of the previous installs they were all there in File Manager but I didn't know how to get them out. Now they are not there and it says I need to change to root access mode which I don't know how to do. I need to get this sorted because my next step is to flash a new modem as that is why I've done all this, the phone is from Germany and we live in NZ and its not picking up signals out of town where it should be. Please help, I've searched all over :crying:
threeboys said:
, I've searched all over :crying:
Click to expand...
Click to collapse
Changing Modem, does not require root, it can be flashed via ODin or CWM recovery..refer to [Tutorial] How to Unbrick, Flash, Downgrade, Root, Update i9000 from Froyo to Kit Kat,
as for root look in developers Click System Information in Settings and tap Build Version 7 times and Development Option will be unlockedand root may be there ( depends on ROM)
also you should flash the gapps, as some ROM's need them for correct performance.
Check this out! Links to useful Guides and " Banned " Documentaries
OK, I've rooted and put the rom on now so may as well continue. I did the 7 times thing and now the files are all there in File Manager, but how do you get them out or access them (sorry very noob question), like is there a way to get say the titanium file back into the apps part?
Also, I can reflash gapps, that was easy enough, but I've tried two files already and both screwed up the keyboard, so does anyone know which one will work?
threeboys said:
OK, I've rooted and put the rom on now so may as well continue. I did the 7 times thing and now the files are all there in File Manager, but how do you get them out or access them (sorry very noob question), like is there a way to get say the titanium file back into the apps part?
Also, I can reflash gapps, that was easy enough, but I've tried two files already and both screwed up the keyboard, so does anyone know which one will work?
Click to expand...
Click to collapse
not too sure what you mean by getting titanium file back into the app..do you mean you have a backup from previous ROM and want to restore some apps?
as for gapps, look in the mackay ROM thread, where you downloaded the ROM, for the correct gapps that was recommended by developer.
Check this out! Links to useful Guides and " Banned " Documentaries
Thanks for your replies. What I mean is, I thought I'd lost CWM and Titanium etc, but I found them in File Manager with the other apps. But they're just listed, you can't open them, so how do I get them from there into the main apps screen as an icon?
Also, the two gapps packages I tried already were both listed with Mackay 4.2 downloads and 'what to do' information. So if they don't work what will? Thanks.
threeboys said:
Thanks for your replies. What I mean is, I thought I'd lost CWM and Titanium etc, but I found them in File Manager with the other apps. But they're just listed, you can't open them, so how do I get them from there into the main apps screen as an icon?
Also, the two gapps packages I tried already were both listed with Mackay 4.2 downloads and 'what to do' information. So if they don't work what will? Thanks.
Click to expand...
Click to collapse
CWM is a recovery ( have to use Combo key press to enter) if you have a CWM folder in your SD card ( which a file manager can open) its your backup files and cannot be opened but only used for restoring in CWM recovery. As for titanim it could be the same case, you need to install titanium backup from play store to open it.
How did you flash gapps? I mean the procedure you used?
Check this out! Links to useful Guides and " Banned " Documentaries
Oh dear, I've really stuffed things up. I decided to flash back the backup rom (GB 2.3.5) while in CWM. It told me it was successful and then gave the option to reboot with or without rooting (something like that) so I choose root. Now it won't go past the Samsung screen. I can get back into CWM recovery, but any options I choose I just get a list of errors 'can't mount' 'can't open' 'unknown volume' etc etc. Nothing seems to work. Please somebody help, I feel sick!
threeboys said:
Oh dear, I've really stuffed things up. I decided to flash back the backup rom (GB 2.3.5) while in CWM. It told me it was successful and then gave the option to reboot with or without rooting (something like that) so I choose root. Now it won't go past the Samsung screen. I can get back into CWM recovery, but any options I choose I just get a list of errors 'can't mount' 'can't open' 'unknown volume' etc etc. Nothing seems to work. Please somebody help, I feel sick!
Click to expand...
Click to collapse
refer to [Tutorial] How to Unbrick, Flash, Downgrade, Root, Update i9000 from Froyo to Kit Kat, and flash the gingerbread ROM with the PIT file
Check this out! Links to useful Guides and " Banned " Documentaries
Right. (This must be so painful for you 'xseman'). The tutorial saved my butt. Huge thank you, you must be very knowledeable. I did the EZBase recovery and rescue by nitr8. Worked great and the phone is great. Have no idea what its actually running now, it says 2.3.3 but doesn't say GB or anything. So I got all smarty pants and decided to flash a new modem which was the goal of this whole exercise. Did that in CWM but didn't work. Thankfully it rebooted and its fine. After the last exercise wondering if there's an sd card problem now. Anyway maybe I should be doing this in ODIN? Question is if you download a zipped modem which bit of it do you put in the Phone box in Odin? (Is that right???) And is the one I picked (BUJP5) going to clash with the rom on there? Or should I leave well alone/quit while I'm ahead
TTTHHHAAANNNKKKYYYOOOUUU
threeboys said:
Right. (This must be so painful for you 'xseman'). The tutorial saved my butt. Huge thank you, you must be very knowledeable. I did the EZBase recovery and rescue by nitr8. Worked great and the phone is great. Have no idea what its actually running now, it says 2.3.3 but doesn't say GB or anything. So I got all smarty pants and decided to flash a new modem which was the goal of this whole exercise. Did that in CWM but didn't work. Thankfully it rebooted and its fine. After the last exercise wondering if there's an sd card problem now. Anyway maybe I should be doing this in ODIN? Question is if you download a zipped modem which bit of it do you put in the Phone box in Odin? (Is that right???) And is the one I picked (BUJP5) going to clash with the rom on there? Or should I leave well alone/quit while I'm ahead
TTTHHHAAANNNKKKYYYOOOUUU
Click to expand...
Click to collapse
All the details you need are mentioned in the link , given earlier, you only need to explore the links inside, and you will know it all. Anyway, .zip files can be flashed in CWM or using Mobile Odin, yes even .tar files can be flashed by mobile odin (download from play store) direct from your phone. so download the modem, for your region ( explore the modem thread and you will know which modem is for meant for which country and using that would give you the best reception) or you can use odin3 from your PC for .tar modem files.
Australia and New Zealand use undermentioned modem and not what you mentioned. you can locate .zip in the modem threads.
XWJW1: Download
Check this out! Links to useful Guides and " Banned " Documentaries
Thanks for all your help, just going to keep flashing modems until we get a better signal!
threeboys said:
Thanks for all your help, just going to keep flashing modems until we get a better signal!
Click to expand...
Click to collapse
Hi there, I'm from NZ myself
Uhm. When I had my S, I used XXJW4, and subsequently that modem when on custom roms.
I guess it could depend on what carrier you're on, but I'm not exactly sure whether being on Telecom, 2degrees etc affects this or not. I'm on Vodafone myself and I never had problems using XXJW4, it gave me good reception (up in Auckland).
Sent from my GT-I9300 using Tapatalk
Soryuu said:
Hi there, I'm from NZ myself
Uhm. When I had my S, I used XXJW4, and subsequently that modem when on custom roms.
I guess it could depend on what carrier you're on, but I'm not exactly sure whether being on Telecom, 2degrees etc affects this or not. I'm on Vodafone myself and I never had problems using XXJW4, it gave me good reception (up in Auckland).
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Hi, thanks for that. Its the one I have on there currently, but so far none have improved reception. We're rural, but it still should be better than it is.
threeboys said:
Hi, thanks for that. Its the one I have on there currently, but so far none have improved reception. We're rural, but it still should be better than it is.
Click to expand...
Click to collapse
Hmm, I did notice that custom roms usually has less reception than stock overall (on stock it was always 4 bars, on custom roms it was occassional).
There was a 2.3.3 rom for Vodafone.. perhaps you could find the modem from that and use it?
Sent from my GT-I9300 using Tapatalk
Xsenman please help me
:crying::crying::crying:
Everything settled down with the phone and then decided tp put slimbean on. Couldn't text or gps so in the process of reflashing another rom I ended up with the black screen of death. Oh dear. Managed to get it back into download mode, but can't do the ezbase recovery in Odin because it's not picking up the USB connection. Tried all the USB suggestions. Tried heimdall one click but no connection. Decided to try Linux as might pick up connection, so put Ubuntu on laptop. Now of course Odin doesn't work. Heimdall looks so complicated, not sure about command lines etc and you need the front end one as we'll??? Also what would you put in what boxes etc from the ezbase kit? There must be something I can do. Any help GREATLY appreciated, thanks.
threeboys said:
Now of course Odin doesn't work. Heimdall looks so complicated, not sure about command lines etc and you need the front end one as we'll??? Also what would you put in what boxes etc from the ezbase kit? There must be something I can do. Any help GREATLY appreciated, thanks.
Click to expand...
Click to collapse
from link given to you earlier
Using Heimdall to flash
You can do the same process using heimdall instead of Odin3 too, to use heimdall one click you can download i9000 Rescue kit and flash. or use [GUIDE] Flashing with Heimdall
select files as follows...
primary boot > boot.bin
secondary boot > Sbl.bin
repartition > s1_odin_20100512.pit
factoryfs > factoryfs.rfs
cache > cache.rfs
dbdata > dbdata.rfs
param > param.lfs
modem > modem.bin
kernel > zImage
use version 1.1 if latest version does not boot
heimdall-suite-1.1.1-win32
heimdall-suite-1.3.1-win32
Heimdall Suite V 1.3.2 for PC
Heimdall Suite V 1.3.2 for MAC
or using Heimdall on a linux machine
Check this out! Links to useful Guides and " Banned " Documentaries
xsenman said:
from link given to you earlier
Using Heimdall to flash
You can do the same process using heimdall instead of Odin3 too, to use heimdall one click you can download i9000 Rescue kit and flash. or use [GUIDE] Flashing with Heimdall
select files as follows...
primary boot > boot.bin
secondary boot > Sbl.bin
repartition > s1_odin_20100512.pit
factoryfs > factoryfs.rfs
cache > cache.rfs
dbdata > dbdata.rfs
param > param.lfs
modem > modem.bin
kernel > zImage
use version 1.1 if latest version does not boot
heimdall-suite-1.1.1-win32
heimdall-suite-1.3.1-win32
Heimdall Suite V 1.3.2 for PC
Heimdall Suite V 1.3.2 for MAC
or using Heimdall on a linux machine
Check this out! Links to useful Guides and " Banned " Documentaries
Click to expand...
Click to collapse
Thanks for the response. That rescue kit link doesn't work anymore, I've tried to get it before. I'm going to try and put Heimdall on, does it make any difference if it goes on Windows or Ubuntu in terms of picking up a connection? I thought I would initially try and flash the ezbase kit on, but the files look different to the ones you've shown above, or do I just unzip a rom and pick the files out? If there's still no connection should I try a jig? Thanks for your help.
threeboys said:
Thanks for the response. That rescue kit link doesn't work anymore, I've tried to get it before. I'm going to try and put Heimdall on, does it make any difference if it goes on Windows or Ubuntu in terms of picking up a connection? I thought I would initially try and flash the ezbase kit on, but the files look different to the ones you've shown above, or do I just unzip a rom and pick the files out? If there's still no connection should I try a jig? Thanks for your help.
Click to expand...
Click to collapse
1) Connection problems are solved by following this [Tutorial] How to resolve micro USB connection problems [unknown USB device][code 43] ( link to this was given in [Tutorial] How to Unbrick, Flash, Downgrade, Root, Update i9000 from Froyo to Kit Kat )
2) you can use any, windows or ubuntu
3) yes you need to unzip the ROM to get the separate files
4) A JIG is always handy for putting phone into download mode but not for connecting to PC
Check this out! Links to useful Guides and " Banned " Documentaries
xsenman said:
1) Connection problems are solved by following this [Tutorial] How to resolve micro USB connection problems [unknown USB device][code 43] ( link to this was given in [Tutorial] How to Unbrick, Flash, Downgrade, Root, Update i9000 from Froyo to Kit Kat )
2) you can use any, windows or ubuntu
3) yes you need to unzip the ROM to get the separate files
4) A JIG is always handy for putting phone into download mode but not for connecting to PC
Check this out! Links to useful Guides and " Banned " Documentaries
Click to expand...
Click to collapse
Yes have followed through all of the tutorial and usb connection problems to no avail. I've downloaded the Heimdall suite but please excuse my ignorance how the heck do you install it? I've unzipped and dble clicked on the exe files, the heimdall.exe seems fine, but the heimdallfrontend.exe gives an error a file is missing. So not sure if its me, or it. Will keep trying. If I can't get heimdall to connect the phone what can I do? I've been all over the internet and I fail to see how it is completely stuffed, but still difficult to resolve.
Was epic reading this
Sent from my XT1032 using Tapatalk