Related
Is Odin really necessary for flashing ROMs on the Sidekick, or can I keep on using adb/fastboot? Or is there a native tool for Linux for flashing ROMs for Samsung?
Other forum threads I've seen recommend running ODIN on Virtualbox, which is doable but a pain in the keister.
samandiriel said:
Is Odin really necessary for flashing ROMs on the Sidekick, or can I keep on using adb/fastboot? Or is there a native tool for Linux for flashing ROMs for Samsung?
Other forum threads I've seen recommend running ODIN on Virtualbox, which is doable but a pain in the keister.
Click to expand...
Click to collapse
odin is only used when you soft brick and flash an image to get back to stock to recover a device you flash a rom through a recovery menu
tylermaciaszek said:
odin is only used when you soft brick and flash an image to get back to stock to recover a device you flash a rom through a recovery menu
Click to expand...
Click to collapse
Thanks, but that doesn't seem to really address my question. Fr'instance, I can use fastboot on my G1 to load a new ROM easily:
Code:
fastboot update -w [Rom_Filename.zip]
Is there a reason I couldn't do this with a stock ROM on a Sidekick in case of a softbrick instead of using ODIN? I know I've done this on my G1 when it freezes on the bootlogo, which seems to be a similar state.
samandiriel said:
Thanks, but that doesn't seem to really address my question. Fr'instance, I can use fastboot on my G1 to load a new ROM easily:
Code:
fastboot update -w [Rom_Filename.zip]
Is there a reason I couldn't do this with a stock ROM on a Sidekick in case of a softbrick instead of using ODIN? I know I've done this on my G1 when it freezes on the bootlogo, which seems to be a similar state.
Click to expand...
Click to collapse
sorry i misunderstood what you were saying but to answer you question no fastboot is an htc thing only
tylermaciaszek said:
sorry i misunderstood what you were saying but to answer you question no fastboot is an htc thing only
Click to expand...
Click to collapse
Ah so! Ok. What about adb then? Shouldn't that work for any Android device?
Code:
adb shell
/sbin/recovery --wipe_data
/sbin/recovery --update_package=SDCARD:romname.zip
samandiriel said:
Ah so! Ok. What about adb then? Shouldn't that work for any Android device?
Code:
adb shell
/sbin/recovery --wipe_data
/sbin/recovery --update_package=SDCARD:romname.zip
Click to expand...
Click to collapse
i never tried it because i dont really use adb but yes i believe it should work on all android devices!
Yes that should work, test it out. the worst you can do in adb is softbrick.
Heimdall I believe its called. But the adb method looks cool. Heimdall is a comandline flashing tool
Sent from my SGH-T839 using XDA Premium App
Heimdall is the open source version of Odin, ADB is the way you want to flash roms (if you're not gonna use CWM).
sduvick said:
Heimdall is the open source version of Odin, ADB is the way you want to flash roms (if you're not gonna use CWM).
Click to expand...
Click to collapse
Yah, I saw that but my understanding is that Heimdall is for the Samsung Galaxy S only
samandiriel said:
Yah, I saw that but my understanding is that Heimdall is for the Samsung Galaxy S only
Click to expand...
Click to collapse
nope u have seen someone on the sk4g threads used it to restore their device on the SK4G!
Heimdall is for Galaxy S *Series* phones, of which we are one on the SK4g :]
sduvick said:
Heimdall is for Galaxy S *Series* phones, of which we are one on the SK4g :]
Click to expand...
Click to collapse
Aha! Yay then, all is right with the world!
If you have any more questions, especially linux questions, feel free to PM me, I love me that Tux.
sduvick said:
If you have any more questions, especially linux questions, feel free to PM me, I love me that Tux.
Click to expand...
Click to collapse
Tux the penguin? And here I thought you were strictly a platypus man - you cross-species player, you!
Meh, it's all about the beaks, everybody loves Tux!
Heimdall
Ok, so Heimdall successfully flashes my mistakes away. One more person verifying that it works.
Does anyone know how to get it to successfully make a dump so it's a bit quicker to get back to something more than stock? Seems like all of all roms are sent out for CWM, which works great till I soft-brick everything.
My only best guess on getting a good dump is adb, remount,ro, and dd it all back to the computer. Seems like a bad place to be with halting everything mid-stride.
And with all the leaked roms lately, does any seem to support fastboot? theres been a few options out now and i'm a bit leery on mucking with the boot-loader
Fastboot is only for HTC, not samsung.
Is it possible to use ADB with linux?
Yes, install the Android SDK, that includes adb.
Problem with the ROM"Official OTA JB 4.1.1 for GSM Nexus S (CWM Flashable) + Extras"
Hello, this is the first topic i write on XDA. I have a huge problem with the ROM called "Official OTA JB 4.1.1 for GSM Nexus S (CWM Flashable) + Extras" uploaded by kibmcz
I have made a mistake, i forgot to install the file for root and now i do not have root, i can not connect my nexus s with the computer and i can not get on my Clockworkmod recovery to change ROM. I don't know what to do. Please help me to change this ROM!
You should still be able to boot into the bootloader (vol up + pwr). You can then flash CWM again via fastboot.
chronophase1 said:
You should still be able to boot into the bootloader (vol up + pwr). You can then flash CWM again via fastboot.
Click to expand...
Click to collapse
How can i flash CWM via fastboot? Can you give me directions please?
http://wiki.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide
You'll learn a lot more by reading up on it. It's worth your time. Seeing as you've unlocked your bootloader, this should be a cakewalk for you.
You'll learn a lot more by reading up on it. It's worth your time. Seeing as you've unlocked your bootloader, this should be a cakewalk for you.[/QUOTE]
Thanks a lot my friend, i hope that i won't have any problem to connect my nexus s with the PC because now i have due to this ROM..
Its not the roms fault. The point of a stock unmodified ROM is simple. To be a stock ROM unmodified ROM
You'll learn a lot more by reading up on it. It's worth your time. Seeing as you've unlocked your bootloader, this should be a cakewalk for you.[/QUOTE]
My friend i still can not connect my phone with the computer. So i can't follow these directions.
albundy2010 said:
Its not the roms fault. The point of a stock unmodified ROM is simple. To be a stock ROM unmodified ROM
Click to expand...
Click to collapse
But now unfortunately i can not connect my phone with the computer and flash recovery
error?
ironia. said:
error?
Click to expand...
Click to collapse
Yes..
christoscy said:
Yes..
Click to expand...
Click to collapse
And what error? That would be handy to know... if it's the lack of drivers just install PDAnet and follow the instructions, it will install the drivers for the Nexus S.
DeuXGod said:
And what error? That would be handy to know... if it's the lack of drivers just install PDAnet and follow the instructions, it will install the drivers for the Nexus S.
Click to expand...
Click to collapse
I have installed them but it still does not recognise my Nexus S. And it doesn't show me Android ADB Interface in device manager.
christoscy said:
I have installed them but it still does not recognise my Nexus S. And it doesn't show me Android ADB Interface in device manager.
Click to expand...
Click to collapse
With your phone up and running normally and android debugging on, go to cmd. type adb devices does it show? Just wondering.
jayjay3333 said:
With your phone up and running normally and android debugging on, go to cmd. type adb devices does it show? Just wondering.
Click to expand...
Click to collapse
No it doesn't show..
Hi,
I had before the OTA for Jelly Bean an ICS unlocked and rooted.
I tried to use ShabbyPenguin to get it rooted again but now I have a broken recovery.
So not sure what do I need to get it rooted again.. Is it possible?
Thanks!
Not positive, but could u flash cwm through adb? Then just flash a rooted ROM, or supuser.zip. Is the bootloader is still unlocked?
Haven't heard good stuff about root toolkits, its actually really easy to do for our phones.
Not sure if it is possible to flash cwm trough adb... However I will try it later today...
And yes, bootloader is still unlocked...
rustyjay said:
Not positive, but could u flash cwm through adb? Then just flash a rooted ROM, or supuser.zip. Is the bootloader is still unlocked?
Haven't heard good stuff about root toolkits, its actually really easy to do for our phones.
Click to expand...
Click to collapse
Yeah, I am positive u could use adb fast boot to flash a recovery, cwm or twrp u just need the image.
hhhmmmm... no luck yet...
I tried to flash a recovery and it keeps giving me a message
<waiting for device>
After that it seems like stuck..
I read somewhere else that maybe because of the drivers, but I already tried a couple of versions 1.3.8 and 1.5.6 with the same result...
btw I'm using a Windows 7 64 bit machine...
Not sure if use a Linux machine will have any benefit...
rustyjay said:
Yeah, I am positive u could use adb fast boot to flash a recovery, cwm or twrp u just need the image.
Click to expand...
Click to collapse
Well...
Also tried the google usb drivers with no luck....
I guess that I will try it with some other windows/linux version later today...
Off but on topic. Describe what you call a broken a recovery please.
When I try to run the recovery it appears a dead android with a red exclamation mark on the screen....
After that it takes some time to reboot again...
albundy2010 said:
Off but on topic. Describe what you call a broken a recovery please.
Click to expand...
Click to collapse
That is stock recovery. It is not broken.
Yes I was saying it was broken because before the OTA update I had twrp as recovery, and now I can't flash any recovery
albundy2010 said:
That is stock recovery. It is not broken.
Click to expand...
Click to collapse
When you flash/install a ota your recovery gets wiped back to stock once it boots up due to the flash recovery script in the stock ROM.
Nothing is wrong with your device. Just follow a real guide on how to unlock and root. Real meaning using the SDK. Or even use one of those stupid one click crap. should not have a issue.
Guides are in the forum stickies.
Hi Guys,
Well not sure what the problem was.... maybe the drivers, maybe Win7 64 bits or I don't what...
I used a WinXP machine with the pdanet installed and it worked like charm...
I succesfully installed the recovery and root again.
Anyway... thanks for your time.
Glad to hear that.
I unlocked the boot loader of my HTC One XL, flashed TWRP, wiped cache, dcache, did a factory reset. Booted in factory default, copied ROM and GAPPS to folder, booted in TWRP, installed the ROM zip, installed the GAPPS zip. Rebooted into system. Now my phone wont turn on, there's no charging light. I can't boot into recovery - pressing power and volume down does nothing. I'm not even getting a charging light.
Did I brick this thing?
Does anyone have any suggestions?
Was my mistake not to have flashed the boot img?
BTW, I posted in "general" - sorry - didn't know - but now I can't figure out how to delete the thread.
Not a good day...:crying:
i don't see why your phone would be messed up.
you do need to "fastboot flash boot boot.img" though. what rom did you flash?
not sure now...
DvineLord said:
i don't see why your phone would be messed up.
you do need to "fastboot flash boot boot.img" though. what rom did you flash?
Click to expand...
Click to collapse
i'm thinking now maybe it was the wrong ROM. looks like aokp_endeavoru_unofficial_Oct-10-12-v3.0
guess its not looking good...
trueblueinpw said:
i'm thinking now maybe it was the wrong ROM. looks like aokp_endeavoru_unofficial_Oct-10-12-v3.0
guess its not looking good...
Click to expand...
Click to collapse
I believe your boot.img got overwritten with the endeavoru's /system partition.
You can fix it on a linux computer.
Can you get into recovery at all?
how would i fix w/ linux?
absolutelygrim said:
I believe your boot.img got overwritten with the endeavoru's /system partition.
You can fix it on a linux computer.
Can you get into recovery at all?
Click to expand...
Click to collapse
is there nothing that linux does not make better?! how would i fix this on linux?:good:
trueblueinpw said:
is there nothing that linux does not make better?! how would i fix this on linux?:good:
Click to expand...
Click to collapse
Well first.. Can you get into Recovery?
and second.. Is your device listed in windows as "QHSUSB_DLOAD"?
if it is recognized as "QHSUSB_DLOAD" try this
http://unlimited.io./qhsusbdload.htm
you will need linux
if it works, hurry up and go flash a boot.img and then the ROM for the AT&T one X, no more internationals ok?
didn't work...
absolutelygrim said:
Well first.. Can you get into Recovery?
and second.. Is your device listed in windows as "QHSUSB_DLOAD"?
if it is recognized as "QHSUSB_DLOAD" try this
http://unlimited.io./qhsusbdload.htm
you will need linux
if it works, hurry up and go flash a boot.img and then the ROM for the AT&T one X, no more internationals ok?
Click to expand...
Click to collapse
dang - can't believe i flashed the wrong rom - what a moron i am!
alright - so i tried that on ubuntu - didn't work - thought that might do the trick - looked promising...
trueblueinpw said:
dang - can't believe i flashed the wrong rom - what a moron i am!
alright - so i tried that on ubuntu - didn't work - thought that might do the trick - looked promising...
Click to expand...
Click to collapse
Is your phone listed in device manager as QHSUSB_DLOAD?
it is...
absolutelygrim said:
Is your phone listed in device manager as QHSUSB_DLOAD?
Click to expand...
Click to collapse
is that good?:laugh:
no
trueblueinpw said:
is that good?:laugh:
Click to expand...
Click to collapse
Uhh, no. You now have a very expensive paper weight. For now. I think there is a way to fix by linux and adb. Sorry bro
Sent from my HTC One XL using xda app-developers app
trueblueinpw said:
is that good?:laugh:
Click to expand...
Click to collapse
DvineLord said:
no
Click to expand...
Click to collapse
It is bad.. But it is 'good' because unlimited.io tool should have fixed it
I'm sure he won't want to.. but you can PM beaups.. He knows how to fix it manually, if he is willing to help.
There is a way to fix this on Linux. It is lengthy and difficult. But I think the solution was to push a new hboot while in QHSUSB_DLOAD, not partition 4 (which is your issue)
alright...
absolutelygrim said:
It is bad.. But it is 'good' because unlimited.io tool should have fixed it
I'm sure he won't want to.. but you can PM beaups.. He knows how to fix it manually, if he is willing to help.
Click to expand...
Click to collapse
thanks for the help. i might still have some hope as my unbuntu was version 11 and the u.io.tool specs version 12. (not sure why that would matter as the tool seemed to run okay). if that doesn't work i'll try to pm beaups.
i do appreciate the help.:good:
trueblueinpw said:
thanks for the help. i might still have some hope as my unbuntu was version 11 and the u.io.tool specs version 12. (not sure why that would matter as the tool seemed to run okay). if that doesn't work i'll try to pm beaups.
i do appreciate the help.:good:
Click to expand...
Click to collapse
no. go update to Ubuntu 120.4, it should work then.
updating to 12 now...
absolutelygrim said:
no. go update to Ubuntu 120.4, it should work then.
Click to expand...
Click to collapse
hope it works... :fingers-crossed:
trueblueinpw said:
hope it works... :fingers-crossed:
Click to expand...
Click to collapse
You can also dd the partitions back to your phone.
You would need someone to give you a partition 4, and you would have to rewrite it back to your phone through emmc mode, I suggest reading up on this incase the unlimited.io tool doesn't resolve your problem
Sent from my HTC One XL using xda app-developers app
dd?
absolutelygrim said:
You can also dd the partitions back to your phone.
You would need someone to give you a partition 4, and you would have to rewrite it back to your phone through emmc mode, I suggest reading up on this incase the unlimited.io tool doesn't resolve your problem
Is there any information about how to "dd the partitions"? Before I flashed the [wrong] ROM, I copied the backup I made with TWRP. So I have the files on my Windows computer (boot.emmc.win, boot.emmc.win.md5, etc.). Would these backup files be at all helpful?
I'm just not sure what to do now. Any help?
Click to expand...
Click to collapse
trueblueinpw said:
absolutelygrim said:
You can also dd the partitions back to your phone.
You would need someone to give you a partition 4, and you would have to rewrite it back to your phone through emmc mode, I suggest reading up on this incase the unlimited.io tool doesn't resolve your problem
Is there any information about how to "dd the partitions"? Before I flashed the [wrong] ROM, I copied the backup I made with TWRP. So I have the files on my Windows computer (boot.emmc.win, boot.emmc.win.md5, etc.). Would these backup files be at all helpful?
I'm just not sure what to do now. Any help?
Click to expand...
Click to collapse
omfg, if you have a nandroid backup and can get into recovery just push you nand backup to your phone and restore it from recovery.
start there before you start dd'ing partitions.:silly:
Click to expand...
Click to collapse
I can't get into recovery mode...
Crappyvate said:
trueblueinpw said:
omfg, if you have a nandroid backup and can get into recovery just push you nand backup to your phone and restore it from recovery.
start there before you start dd'ing partitions.:silly:
Click to expand...
Click to collapse
I can NOT get into recover. My phone is unresponsive - push power and volume down does nothing - no charge light - tried plugging into wall charges, etc.
So, I don't know how to dd the partition information to my phone. I'm looking through the threads now but I haven't found anything.
I have a linux machine (Ubuntu v.12) windows 7 (where I have the backup files) and a Mac (like that's going to help...). I'm obviously new to the whole ROM flashing thing - but I'm pretty good with computers otherwise.
I guess what I'm looking for is a way to push the backup files I have from my TWRP to the heretofore brick HOX? I just don't know where to start.
Click to expand...
Click to collapse
Beaups is the man to ask. But I wouldn't count on a friendly reply as I'm sure he's been bombarded with this same question. He's pretty much the only one that could point you in the RIGHT direction. Although 18th.abn is also very good with that and more forgiving lol
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
Hey all, sorry if this seems like other questions being posted, but I can not get my phone to work even after attempting the other fixes posted on the forums. I rooted my phone and was running the stock rom that came preloaded with it. I attempted to install CM10 through Rom Manager to no success, so I then tried to manually flash it as well as Gapps. My phone initially got stuck at the CM10 bootloader, but i could still go into CWM Recovery 5.8.3.1. After trying to get the rom to work more, it seems as if all I can access is CWM Recovery and nothing else. My phone wont even boot into the bootloader anymore and all i have access to is CWM Recovery.
I am not the most tech savvy individual when it comes to this since it has been ages since i tinkered with roms, but I would really like to fix this. So heres the facts since my post is so long (sorry!):
-Phone WILL NOT go into bootloader
-Can ONLY ACCESS ClockworkMod Recovery (5.8.3.1)
-SD Card wont mount (I get error "E:Unable to open ums lunfile (No such file or directory)")
I really just want to go back to stock and root again from scratch to reduce any errors like this from occurring in the future and ANY help would be appreciated because I am totally lost and without a phone now. To make things even more difficult, I only have access to a Mac running Lion....although i do have Windows 8 through the use of a bootcamp program, so I CAN run windows programs. Thank you all for any information you may have!
Do you have NANDROID backup,if yes do NANDROID restore and see what happens
Sent from my HTC One S using xda app-developers app
luxandroid said:
Do you have NANDROID backup,if yes do NANDROID restore and see what happens
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
I do NOT have a nandroid backup. I dont even have access to my SD Card since my phone wont recognize it. I dont know where to even start in terms of fixing this. Any additional information anyone needs who thinks they can help me can be provided.
Porgress (Sort of)
I can now access my bootloader if this helps with anyone answering my issue! As I said before, any additional information from me about my phone that can help can and will be provided...just ask if you think you may be able to help!
fragkiller1 said:
I can now access my bootloader if this helps with anyone answering my issue! As I said before, any additional information from me about my phone that can help can and will be provided...just ask if you think you may be able to help!
Click to expand...
Click to collapse
Well since you in bootloader flash TWRP and then boot.img and then reflash the rom just to make sure.
Progress!
Darknites said:
Well since you in bootloader flash TWRP and then boot.img and then reflash the rom just to make sure.
Click to expand...
Click to collapse
Here is the inexperienced flasher in me asking this: How would I go about doing that? Is there a simplified way you could explain this to me, or even a guide? Thanks so much for the reply!
fragkiller1 said:
Here is the inexperienced flasher in me asking this: How would I go about doing that? Is there a simplified way you could explain this to me, or even a guide? Thanks so much for the reply!
Click to expand...
Click to collapse
Sorry. Best would be the All-In-One Toolkit, TWRP is a recovery to replace CWM because its that what's messing you up and also TWRP is better. Toolkit will also flash the boot.img too.
Darknites said:
Sorry. Best would be the All-In-One Toolkit, TWRP is a recovery to replace CWM because its that what's messing you up and also TWRP is better. Toolkit will also flash the boot.img too.
Click to expand...
Click to collapse
Okay, will do! Also, where would I find the Boot.img?
And on a side note; my phone says S-ON...I thought when rooted it was supposed to be S-OFF. Could that be causing problems as well?
fragkiller1 said:
Okay, will do! Also, where would I find the Boot.img?
And on a side note; my phone says S-ON...I thought when rooted it was supposed to be S-OFF. Could that be causing problems as well?
Click to expand...
Click to collapse
Boot.img is in the rom zip. S-On is not the reason its CWM thats messing you up with getting into the bootloader but also not flashing boot.img is not helping too.
Darknites said:
Boot.img is in the rom zip. S-On is not the reason its CWM thats messing you up with getting into the bootloader but also not flashing boot.img is not helping too.
Click to expand...
Click to collapse
The toolkit isnt working for me. Im not sure why... It seems like ill never get this phone up and running again
fragkiller1 said:
The toolkit isnt working for me. Im not sure why... It seems like ill never get this phone up and running again
Click to expand...
Click to collapse
Does the bootloader say fastboot usb?
Darknites said:
Does the bootloader say fastboot usb?
Click to expand...
Click to collapse
Yes it says fastboot USB, but i can not access it on my computer. Also, every time I try to run the toolkit you mentioned earlier... it says something along the line on "command not recognized" in CMD Prompt.
fragkiller1 said:
Yes it says fastboot USB, but i can not access it on my computer. Also, every time I try to run the toolkit you mentioned earlier... it says something along the line on "command not recognized" in CMD Prompt.
Click to expand...
Click to collapse
Hmm not sure have you tried redownloading it or reinstalling the HTC drivers and if that dont work best ask in the toolkit thread.
Darknites said:
Hmm not sure have you tried redownloading it or reinstalling the HTC drivers and if that dont work best ask in the toolkit thread.
Click to expand...
Click to collapse
That was the problem. the toolkit now works (in terms of doing what its supposed to do), but I can no longer access fastboot....just my recovery. any advice on how to get fix this?
fragkiller1 said:
That was the problem. the toolkit now works (in terms of doing what its supposed to do), but I can no longer access fastboot....just my recovery. any advice on how to get fix this?
Click to expand...
Click to collapse
I see that you got the toolkit and bootloader working but did you end up using the RUU?
Success!
Darknites said:
I see that you got the toolkit and bootloader working but did you end up using the RUU?
Click to expand...
Click to collapse
Yes, i ran the RUU and my phone reverted to its stock factory state, no problems at all! Im going to unlock the bootloader again as well as root and install CM10. Thank you for all your help!
fragkiller1 said:
Yes, i ran the RUU and my phone reverted to its stock factory state, no problems at all! Im going to unlock the bootloader again as well as root and install CM10. Thank you for all your help!
Click to expand...
Click to collapse
Np but this time use TWRP as your recovery and once you up and running with CM10 you can use Flash Image GUI to flash the boot.img if you ever update the rom.