Database Develop

[Q] Quick Question Regarding Odin, ADB and Flashing

Hello all! Long time lurker, first time poster! I'm on the verge (halfway through actually) of flashing my first custom rom: Serendipity 6.3. However I have run into a couple of issues that may or not be a problem.
1) I successfully used Odin 1click to flash back to stock from the official Froyo update when I went to master clear however at roughly 95% completion (On the Odin download bar) I got some sort of runtime error that had to force close Odin while the factory reset was occurring on the phone. Thankfully the phone rebooted and appeared to have wiped the Internal SD successfully. Was wondering if I should just re-download Odin if I plan on master clearing again. I abused the search function for the Cappy forums but couldn't find a solution to this specific problem.
2) After the whole Odin debacle I just decided to go on ahead with flashing Serendipity but ran into another problem... I cant reboot into recovery whereas I could prior to flashing back to stock... So I guess my question here is: Is it ok to use ADB reboot recovery to reinstall the packages that Serendipity uses as it's update.zip? Or should I download figure out how to use the other version of Odin that flashes the 3 button recovery?
I apologize for the length and possible redundancy and really dont want to step on any toes here but I have been wading through the sea of material (via the search function I promise!) on here and just get bogged down by the sheer volume of information out there on these multiple subjects...
If anyone could help me clarify any of this I would greatly appreciate it! You have truly taken me from wondering what rooting meant to beginning to experiment with custom roms! This site is truly a great resource!

Flash back to stock agin. Then try rooting it. Next install "rom manger" from market and install captivate update.zip . Next reboot into recovery (volume buttons plus power and release when see at&t screen) install packages then on clockwork manger recovery screen instal zip from sd and install your rom. But to hard reset dial *2767*3855#. But reflash stock sup don't have problems when flash your rom. Also cognition is as good rom if like stock look. P.m. me if need anything else.
Sent from my SAMSUNG-SGH-I897 using XDA App

Trying to load a custom rom, wth am i doing wrong?

Got a VZW Galaxy tab. Rooted and got ROM manager & SGS Kernel Flasher.
1. I flash using SGS and it successfully flashes, as it reboots and I can see from Settings->Device Info that it shows the Developer's version.
2. I then go to CWM (ROM Manager) load ROM from SD, chose the ROM which is in update.zip format, I select to wipe date and casche and then nothing.
It gets stuck at the SAMSUNG boot screen. So i have to use Heimdall to restore back to stock VZW Rom. I have tried several times, even after flash just tried to reboot directly into Recovery mod (Power+Volume Down) and same thing. Goes to SAMSUNG boot screen and freezes.
What am I missing or doing wrong???

First thing i would recommend is : uninstall rom manager. It causes more problems. If you did a search on these forums you would find loads more tales of woe re rom manager.
Second thing is: have look through the dev section, at the instructions for installing clockwork recovery. Then look for the appropriate rom for your device.
But whatever you do, uninstall rom manager
Sent from my thingymajig

Isn't ROM manager ClockworkMod?
I searched Clockworkmod on the market and when installed the icon says ROM Manager though...

o2sys said:
Got a VZW Galaxy tab. Rooted and got ROM manager & SGS Kernel Flasher.
1. I flash using SGS and it successfully flashes, as it reboots and I can see from Settings->Device Info that it shows the Developer's version.
2. I then go to CWM (ROM Manager) load ROM from SD, chose the ROM which is in update.zip format, I select to wipe date and casche and then nothing.
It gets stuck at the SAMSUNG boot screen. So i have to use Heimdall to restore back to stock VZW Rom. I have tried several times, even after flash just tried to reboot directly into Recovery mod (Power+Volume Down) and same thing. Goes to SAMSUNG boot screen and freezes.
What am I missing or doing wrong???
Click to expand...
Click to collapse
Where you went wrong is just jumping in qnd not even bothering to read ANY tutorials here.
Go and read them instead of screwing things up and then asking where you went wrong.

TheATHEiST said:
Where you went wrong is just jumping in qnd not even bothering to read ANY tutorials here.
Go and read them instead of screwing things up and then asking where you went wrong.
Click to expand...
Click to collapse
i did following the tutorials, its how I went that far to begin with. Sorry for being a newb and maybe not fully understanding it thats why I am asking for help, not to spoon feed me...
Followed these steps:
http://forum.xda-developers.com/showthread.php?t=941781

o2sys said:
...
Followed these steps:
http://forum.xda-developers.com/showthread.php?t=941781
Click to expand...
Click to collapse
Have you tried booting into CW Recovery manually and running the KhasMek.Voodoo.Plus.CDMA.Tab.v5.OC.zip (like the instructions say)?
Your thread header says you are using ROM Manager and trying to run the update.zip package.
ROM Manager _should_ work, but maybe stick with instructions especially if you're having issues.

Yes I have tried going into Recovery manually as I stated in my original post.
I always flashed with SGS kernel flasher as it seemed to work well.
Then I tried manually going to Recovery w/o CWM and gets stuck at boot screen as well.
I tried WITH CWM and same stuck at boot screen.
Tried wiping data through Recovery, through the UI (Settings then ect, ect) and several other combos trying to load the custom ROM.
All I am successul is at rooting, then flashing the kernel. Then no matter which step I tried if i reboot it will get stuck at the SAMSUNG boot screen.
Even if I just turn it off and then turn it back on, after the flash, it will get stuck at the boot screen.
I downloaded the kernal flash directly from the link of the first page. And if the kernal file was courrupt i don't think the flash would go successfully.

I've never used the SGS Flasher so can't say what it would do if the file was corrupt.
Maybe flash it using Heimdall to check the file?

Sorry to hear you are having problems. I am also sorry for the rudeness on this forum. Although I seldom post I read it daily. Here is what I would try;
1. The issue may be with the file name update.zip if you can, rename it to anythingyoulike.zip on you computer and then copy it to your SD card. You may even have to take the card out of your tab to do this (delete the update.zip once the file is renamed). Once the renamed file is on the SD card try to reflash.
2. Have you tried to start again using Odin? There is a good clip on you tube about this. As long as the tab at least starts to boot it is not bricked. Feel free to PM me for any additional help.
Good luck.

tigercorp said:
I've never used the SGS Flasher so can't say what it would do if the file was corrupt.
Maybe flash it using Heimdall to check the file?
Click to expand...
Click to collapse
When I use SGS to flash, it reboots and i can see in settings that it has been flashed.
If I use Heimdall, it flashes then gets stuck at the boot screen.

Starting to get worried - bootloop [RESOLVED] :D

I was following the official cyanogen mod wiki guide and everything was fine up until step 6. I couldn't boot into recovery mode, but I could boot normally. So after turning the phone off to try again, I realized I am now stuck in a boot loop. I can boot into download mode perfectly but now ODIN doesn't recognize when the phone is plugged in. Should I be worried? I have no idea what to do..
Thanks in advance, if you need more info feel free to ask!
Original problem (bootloop) was solved by using Heimdall, as was every subsequent problem I encountered in this thread. Many thanks to all!

MrCathal09 said:
I was following the official cyanogen mod wiki guide and everything was fine up until step 6. I couldn't boot into recovery mode, but I could boot normally. So after turning the phone off to try again, I realized I am now stuck in a boot loop. I can boot into download mode perfectly but now ODIN doesn't recognize when the phone is plugged in. Should I be worried? I have no idea what to do..
Thanks in advance, if you need more info feel free to ask!
Click to expand...
Click to collapse
Don't worry, it doesn't sound bad.
Can you enter CWM recovery? If yes, wipe 3 times (data/factory reset - cache - dalvik cache under "advanced") and reboot. It should do it.
If only download mode is accessible, you must flash a stock ROM with PIT file which will do proper re-partition of the /system again, root it and install CWM. After that you can flash again CM10.2. Don't use the CM site, use the thread of developer pawitp, just flash also compatible Gapps version right after the rom while still in recovery.
Best stock ROM as basic for clean flashing of CyanogenMod seems to be Froyo with SpeedMod kernel. Check this thread, all download links are there and working. If it helps you, post in that thread that it worked:
http://forum.xda-developers.com/showthread.php?t=2444308
Good luck

tetakpatak said:
Don't worry, it doesn't sound bad.
Can you enter CWM recovery? If yes, wipe 3 times (data/factory reset - cache - dalvik cache under "advanced") and reboot. It should do it.
If only download mode is accessible, you must flash a stock ROM with PIT file which will do proper re-partition of the /system again, root it and install CWM. After that you can flash again CM10.2. Don't use the CM site, use the thread of developer pawitp, just flash also compatible Gapps version right after the rom while still in recovery.
Best stock ROM as basic for clean flashing of CyanogenMod seems to be Froyo with SpeedMod kernel. Check this thread, all download links are there and working. If it helps you, post in that thread that it worked:
http://forum.xda-developers.com/showthread.php?t=2444308
Update; Have restarted the laptop and tried a total of 4 different cables, to no avail.
Good luck
Click to expand...
Click to collapse
The speedy reply is appreciated, however Odin refuses to acknowledge my phone for some reason. The device is recognized by my PC, the drivers are installed, after all everything worked seamlessly the first time. Any ideas?

MrCathal09 said:
The speedy reply is appreciated, however Odin refuses to acknowledge my phone for some reason. The device is recognized by my PC, the drivers are installed, after all everything worked seamlessly the first time. Any ideas?
Click to expand...
Click to collapse
Is USB debugging enabled?
Otherwise, leave your i9000 turned off, run Odin and prepare all files first and turn the i9000 on into download mode just short before connecting and flashing. The i9000 has kind of "sleep mode" in download mode so if you run it into the download mode and wait few minutes, nothing will happen anymore.

also try a different USB socket on your computer

Samsung kies is killed???

No amount of port/wire changing seemed to work with Odim. However I followed a tut on youtube to flash with Heimdall, and my phone finally booted up with froyo 2.3.3
My original plan was to downgrade from Cyanogen mod, which my older brother put on a few years ago. The phone was beginning to lag and stuff, so yesterday I finally decided to do something about it. The PLAN was, to downgrade to froyo, and then upgrade to Cyanogen mod 10.2, however after getting froyo, my phone went a boot loop (hence this thread).
So I'm asking you all, what is my next step? I'm usually not this helpless, but I can't afford to screw this up again, and I'm honestly a bit scared to try anything without your say. As I said, I am now on froyo2.3.3, and the phone seems okay.
I'm looking through the file manager, and there's loads of cyanogenmod files in the root directory from before. I sorta wanna clean everything out before upgrading. Where should I go from here?

MrCathal09 said:
No amount of port/wire changing seemed to work with Odim. However I followed a tut on youtube to flash with Heimdall, and my phone finally booted up with froyo 2.3.3
My original plan was to downgrade from Cyanogen mod, which my older brother put on a few years ago. The phone was beginning to lag and stuff, so yesterday I finally decided to do something about it. The PLAN was, to downgrade to froyo, and then upgrade to Cyanogen mod 10.2, however after getting froyo, my phone went a boot loop (hence this thread).
So I'm asking you all, what is my next step? I'm usually not this helpless, but I can't afford to screw this up again, and I'm honestly a bit scared to try anything without your say. As I said, I am now on froyo2.3.3, and the phone seems okay.
I'm looking through the file manager, and there's loads of cyanogenmod files in the root directory from before. I sorta wanna clean everything out before upgrading. Where should I go from here?
Click to expand...
Click to collapse
Excellent BTW, 2.3.x is Gingerbread, not Froyo. Upgrading to CM10.2 from Froyo with SpeedMod kernel works very well. Here is a step-by-step guide:
http://forum.xda-developers.com/showthread.php?t=2444308
You are good adviced to read carefully, not just briefly. So you will void problems.
It could be, that your Samsung USB driver hasn't been installed properly. Installing Heimdall drivers has removed Samsung USB driver from my PC some months ago so be sure to have all working before flashing any new build.
If you flash now some Froyo build over your Gingerbread, you don't need PIT file and re-partition. Leave that field empty and don't touch any Odin options (re-partition will remain unchecked). Use compatible Odin version.

tetakpatak said:
*snip*
Click to expand...
Click to collapse
You're a hero! So I am now following that guide, and here are the steps I think I need first;
Root & install CWM recovery: turn off your i9000 and download speedmod-kernel-k13e-500hz.tar
Run Odin as admin, set "speedmod-kernel-k13e-500hz.tar" under PDA. Reboot and reset time checked, re-partition unchecked(!!)
start your i9000 in download mode with 3-button-combo and connect it via USB cable
if <Added!> and ID:COM port number are displayed in Odin, click on "Start"
after only few seconds kernel will be flashed and your i9000 will automatically reboot
Enjoy, now you can install zips of the CM build and compatible gapps for it via CWM recovery, SpeedMod kernel features CWM version 2xxx so after first attempt to install CM.zip it will upgrade just the CWM recovery to version 6xxx, so after that you can really flash the CMbuild.zip
How would I go about doing this process with Heimdall, as Odin is really not an option anymore

you could also try Mobile Odin Pro (google it) then choose the flashing kernel from here http://ndroidplay.blogspot.com/2012/08/mobile-odin-flash-kernels.html?m=1 then just flash the custom rom from Mobile Odin.
EDIT: this is the flashing kernel for i9000 http://dl.xda-developers.com/attach...9/9/8/7/MobileODIN_FlashKernel_I9000-v2.0.zip
---------- Post added at 12:53 PM ---------- Previous post was at 12:31 PM ----------
actually to use Mobile Odin i forgot you need a phone that working and can boot into the OS to install it so may not be an option for you.

After many hours of errors and whatnot, I have finally managed to upgrade my phone to Cyanogen Mod 11-20131207-NIGHTLY-galaxysmtd.
However, there's no play store!
Apparently I'm running android 4.4.1 and CM 11, therefore none of the gapp files are applicable?
I tried installing the latest one, only to get the error: (bad)

Did you use the latest nightly from today (20131208) ???
And the gapps for CM 11 ??? ==> http://wiki.cyanogenmod.org/w/Gapps
MrCathal09 said:
After many hours of errors and whatnot, I have finally managed to upgrade my phone to Cyanogen Mod 11-20131207-NIGHTLY-galaxysmtd.
However, there's no play store!
Apparently I'm running android 4.4.1 and CM 11, therefore none of the gapp files are applicable?
I tried installing the latest one, only to get the error: (bad)
Click to expand...
Click to collapse

freakymod2120 said:
Did you use the latest nightly from today (20131208) ???
And the gapps for CM 11 ??? ==> http://wiki.cyanogenmod.org/w/Gapps
Click to expand...
Click to collapse
Exactly what I needed. Many thanks!
And thanks to everyone else who helped, I really thought my phone was busted for a while there.

MrCathal09 said:
You're a hero! So I am now following that guide, and here are the steps I think I need first;
Root & install CWM recovery: turn off your i9000 and download speedmod-kernel-k13e-500hz.tar
Run Odin as admin, set "speedmod-kernel-k13e-500hz.tar" under PDA. Reboot and reset time checked, re-partition unchecked(!!)
start your i9000 in download mode with 3-button-combo and connect it via USB cable
if <Added!> and ID:COM port number are displayed in Odin, click on "Start"
after only few seconds kernel will be flashed and your i9000 will automatically reboot
Enjoy, now you can install zips of the CM build and compatible gapps for it via CWM recovery, SpeedMod kernel features CWM version 2xxx so after first attempt to install CM.zip it will upgrade just the CWM recovery to version 6xxx, so after that you can really flash the CMbuild.zip
How would I go about doing this process with Heimdall, as Odin is really not an option anymore
Click to expand...
Click to collapse
Cool, congratulations!
Please if it helped, just post it in my thread that it helped:
http://forum.xda-developers.com/showthread.php?t=2444308
...and also please post info/workflow how did you solve it with the Heimdall, so that other forum users who are in need can benefit from your experience.
Have lot of fun with the KitKat

tetakpatak said:
Cool, congratulations!
Please if it helped, just post it in my thread that it helped:
http://forum.xda-developers.com/showthread.php?t=2444308
...and also please post info/workflow how did you solve it with the Heimdall, so that other forum users who are in need can benefit from your experience.
Have lot of fun with the KitKat
Click to expand...
Click to collapse
I might write up a more in-depth tut later on for those as clueless to the scene as I am, however for now the whole process can be summed up in a few major steps;
Down/Upgrade to GingerBread (Android 2.3-2.3.2)
Root
Install ClockWorkMod
Wipe cache/data
Install Cyanogenmod

Perfect, good to hear, that your phone works as "desgined" :good:
MrCathal09 said:
Exactly what I needed. Many thanks!
And thanks to everyone else who helped, I really thought my phone was busted for a while there.
Click to expand...
Click to collapse

Need help with installing ROM.

So far, I have rooted the phone. The bootloader says the device is unlocked.
Where do I go from here?
I have a ROM picked out already, it's on the SD card, on the phone, all ready to go. The problem I'm having is I have no idea how to "reboot to recovery" in the ROM instalation steps when I can't figure how to install a recovery like CWM (which doesn't seem to be avaliable for this phone?).
I've been at this for an hour and a half and so far I've made no progress other than simply frustrating myself with my inability to figure out what seems to be something so simple.
I have a fully rooted and moded Atrix2, but I was able to install CWM Recovery from google play, and it's all simple from there, but that's where I'm stuck at with this AtrixHD, I can't find a recovery to install to flash ROM, flash gapps, clear dalvic, and carry on my happy way.
I've been searching and trying more things and with no luck. It's been two hours now. I can't find a CWM Recovery to install, and TWRP just gives me dead-droid that I have to unscrew the battery connector to hard reset the phone to go back and try again.
I've been refraining from posting this, but I'm going to bed now and I've had no luck at all. Really could just use some help.

Use myth tools to install cwm. You can also download the latest cwm or Philz and flash it in fastboot mode.

Myth Tools is a windows binary, I'm running linux, so it doesn't do me much good at all.
Also, I don't know where to get the latest CWM. Haven't heard of Philz, but I'll see if I can find it. As for flashing it in fastboot mode, never done that before (since I never had to with old phone), so not entirely sure how to.
Found the how to flash a recovery finally http://wiki.cyanogenmod.org/w/Install_CM_for_mb886 no longer stuck now. Installing ROM as I type this.

Did you unlock the bootloader?

audit13 said:
Did you unlock the bootloader?
Click to expand...
Click to collapse
Yes, ROM is loaded onto the phone already now, I was stuck at not having CWM recovery, but I found a how-to with replacing it now.
I just wasn't having luck finding out what to do with that step. It's kinda a learning curve with installing custom roms, once you learn it, it's simple, but with every device being somewhat different and needing special steps for some devices, and different steps for others, this wasn't the same process as my old phone and it left me a bit lost and quite stuck. The URL I put above gave me everything I needed to know that I didn't already have knowledge about.

Download philz recovery and then download flashify from play store and flash recovery through it
Sent from my ATRIX HD using XDA Premium 4 mobile app

[Q] Help - N7000 - can't flash new rom - getting EMMC message

Hello All,
I've spent the last 6 months learning how to flash roms, realise you need the right kernel and made many mistakes which resulted in bricking my phone. I've learnt a lot and as you often suggest on this site, read and learn. I've been trying my best to do this over the months and have managed to even use Odin, after about 70 hours reading, track down a kernel XXLT to get my phone back into recovery and many other painful experiences.
I thought i had the basics down pat by now but i've bricked my phone this time and I'm truly stumped as it brings up an EMMC message and nothing i do with Odin or flashing kernels afterwards brings the phone back at all. I'm sure it's on here somewhere and you will point it out to me but I have tried as it's the only way to learn. Now, if you are willing, i could really benefit from some expert advice?
I have been running CM11 for the last week, really enjoying how it worked on my n7000. I was doing some further reading and came across the page for the Forest Kernel for CM11 on the n7000. I thought no problem, download file, follow flash instructions (wipe dalvik) and proceed as normal. But the zip file would not load and the recovery aborted. I was using CWM touch and in the malaise that followed, i now can't rememer which one it was but it was the grey screen one with the touch functionality.
I thought maybe i didn't have the right CWM to flash this file so I thought I would try a later version of CWM but use PHilz' touch version - using the 'about in recovery' it has v 6.0.3.7.
So i flashed the file again using Philz' version and then i just got a lot of fast scrolling text and I was stuck in recovery from that point on. I tried wiping for reinstall , installing raw kernels and everything i think i know about trying to fix it myself.
However, with lots of fast scrolling text going by, i started looking more closely at it and noticed this message:
Created filesytem with 11/32768 inodes and 4206/131072 blocks
warning wipe_block_device: wipe via secure discard suppressed due to bug in emmc.
now flash a new rom
Since this message, nothing works from the flashing a new ROM in recovery onwards. I just get message like cannot load .ini or failed to open zip etc.
Now i did spend time months ago reading about teh ICS emmc recovery problem but because I've been on 4.4.3 to begin with i thought I'd already surpassed the problem.
I've been running Slimsaber and recently CM11 on KK 4.4.4 so i didn't think i could initiate an 'emmc' problem.
So now i'm stuck and of course, bricked my phone just when i need it most. I only undertook flashing the Forest kernel because it seemed such a low level risk, wipe dalvik and flash.
If any of you could offer some advice, yes, even if you tell me to read it etc, I will understand. It's just after having taught myself so much from these pages I seem to have met my match this time in recovering my phone, so any advice or assistance will be appreciated.
I understand though if asking for this help is inappropriate.
Thanks in advance.
Regards,
Paul

For my part I simply do not understand when you did what thing in which order. It's a little bit chaotic.
So if you want to check if you really bricked your device:
download a stock rom and try to flash it with PC Odin.
If there are errors post them with snapshots.
No need to write a complete story...

Did you try to flash a stock Samsung JB rom using Odin and start fresh?

I didn't read the complete post, title is enough for me, I had same problem some time ago. Flash a 2.3.6 Rom, do wipe data from recovery and then flash 4.1.2 rom.
Greetings.

ThaiDai said:
For my part I simply do not understand when you did what thing in which order. It's a little bit chaotic.
So if you want to check if you really bricked your device:
download a stock rom and try to flash it with PC Odin.
If there are errors post them with snapshots.
No need to write a complete story...
Click to expand...
Click to collapse
Dear ThaiDai,
Sorry, when it goes wrong, it certainly is chaotic. The whole process of going wrong snowballs.
I'll try and follow your advice, thanks for your help.
Cheers,

nokiamodeln91 said:
Did you try to flash a stock Samsung JB rom using Odin and start fresh?
Click to expand...
Click to collapse
Hello Nokiamodel. Thanks for your help. No, i didn't. As i ended up stuck in Philz touch recovery, I tried pushing a raw kernel on via Odin.
When i bought this phone, it came with Gingerbread on it so does that mean i should use gingerbread to return to stock?
cheers,
p

majaretilla said:
I didn't read the complete post, title is enough for me, I had same problem some time ago. Flash a 2.3.6 Rom, do wipe data from recovery and then flash 4.1.2 rom.
Greetings.
Click to expand...
Click to collapse
Majaretilla, thanks for this advice.
I was about to do this when i remembered reading somewhere on another forum that sometimes taking the battery out can sort something like this out. I took out the battery, and when i put it back in, it did not boot into philz touch recovery but what i now realise is the stock recovery. It's the one where you move the cursor by using power and volume keys.
This recovery flashed over the kernel and then roms I had onboard the phone until i got it back to CM11.
The only thing I can't crack now is why that Forest CM11 kernel won't flash using CWM or Philz. It gets aborted. I've tried v2, v4 and v5 and it never works.
I can't find out why or how to overcome the problem so I think i'll leave well alone. It's justfrustrating not knowing why it doesn't.
Thanks again for your help,
p