I read a post somewhere that as of the Froyo update the secondary bootloader error that prevented Heimdall from recognizing the Fascinate on OS X has been fixed. Only, I really need it to work right now, but Heimdall says it can't find a device.
Has this been fixed, or was that post incorrect? I don't have access to a PC, and have borked my phone, so Heimdall is my only option.
Thanks in advance.
Install Linux or Windows via boot camp. That's what I did.
Sent from my SCH-I500 using XDA App
Question about that: I've always skipped over Boot Camp stuff because I never wanted Windows, but is that a separate installation? Is it on the OS X disc? And would I need to repartition my hard drive?
Thanks
eulipion2 said:
I read a post somewhere that as of the Froyo update the secondary bootloader error that prevented Heimdall from recognizing the Fascinate on OS X has been fixed. Only, I really need it to work right now, but Heimdall says it can't find a device.
Has this been fixed, or was that post incorrect? I don't have access to a PC, and have borked my phone, so Heimdall is my only option.
Thanks in advance.
Click to expand...
Click to collapse
Well, I have a mac and a fascinate. I am not able to use heimdall or odin with my fascinate even with windows installed via parallels desktop. Turns out the problem is with the fascinate. It has a faulty secondary bootloader and will not work with osx in download mode. I have read others say (like the guy who commented first) that they were able to get it to work, but not me. It's a problem with the fascinate
To use Bootcamp, you will have to repartition your drive. You start up the utility, let it repartition, and then install your copy of Windows. That's the only drawback... You have to by Windows. But it does work. I have my wife's MBP bootcamped, and that's how I use Odin for anything I need it for
Kevin Gossett said:
To use Bootcamp, you will have to repartition your drive. You start up the utility, let it repartition, and then install your copy of Windows. That's the only drawback... You have to by Windows. But it does work. I have my wife's MBP bootcamped, and that's how I use Odin for anything I need it for
Click to expand...
Click to collapse
Ick, I'm running a Hackintosh, and while I've read of others who have multi-boot systems it seems like a pain, and I rather like mine just the way it is. Other than for flashing, I have no good reason to have Windows or Linux when OS X does everything else I need. I'm sure the secondary bootloader problem will be fixed eventually, by Samsung, VZW, or someone here.
Fortunately I did manage to dig up my wife's old college laptop (6-year-old Dell), and while slow, it worked. Just means I can't flash too much. Of course, now that I flashed CWM I can flash ROMs from recovery, so problem solved I guess.
I may give Boot Camp a try on my next Mac/Hackintosh. Thanks for the input!
Yeah, I agree... It can definitely be a pain if you've already got your system up and running the way you like. Fortunately for me, Bootcamping Windows was one of the first things we did on my wife's MBP since she needed it for some software. Worked out for me
boot camp is awesome....period...the ability to run anything at anytime on one laptop is invaluable...i even have parallels as well with win7 installed, and google chrome btw...just when i need something quick, but having boot camp, if i have to odin something while commuting is a blessing, i mess with my phone hourly, so at anytime, i could brick it and have to flash a stock rom through odin, like i said...invaluable
JoeProcopio said:
boot camp is awesome....period...the ability to run anything at anytime on one laptop is invaluable...i even have parallels as well with win7 installed, and google chrome btw...just when i need something quick, but having boot camp, if i have to odin something while commuting is a blessing, i mess with my phone hourly, so at anytime, i could brick it and have to flash a stock rom through odin, like i said...invaluable
Click to expand...
Click to collapse
You don't need bootcamp to do this...multiboot setups are possible too. Though I must admit its a nice feature and easy to use.
I dual boot archlinux and hackintosh on my pc and must admit that its a bit of a pain to get working but I was able to do it with grub bootloader
Sent from my SCH-I500 using XDA Premium App
Related
Basically my dilema is this. I run Mac OSX exclusively at home, but I am able to use a friend's computer to flash via ODIN if neccessary. Its a pain, however. I'd like to use Heimdall with new frontend, but a requirement for heimdall on OSX is that you have previously installed a secondary bootloader.
My question is, what ROM or ROMs can I flash with ODIN to aquire the secondary bootloader and not have to bother my friends with my sick ROM fettish anymore?
(Currently soft-bricked off of Onyx 4.2UFL trying to flash JK6)
Not sure exactly what you are talking about... but i think the answer you are looking for is Rom Manager. There are 2 versions Free & Donate/Paid both are available in the market, so once you fix your soft brick find it and install it. The only thing you will need a computer for at that point is to copy the ROM to the internal SD card.
ROM manager is fine unless you need to recover from a brick. Its not much good if you do. I'd like to use Heimdall for OSX, but it requires a secondary bootloader. On the I9000 you can get it from a JPA ROM. I don't know which ROMs have this on the Vibrant.
hi all,
i've been trying to figure out how to root my phone. i know that it's pretty straightforward (one click type thing) with a windows computer, but unfortunately i do not have access to windows, only to linux (debian) and i cannot seem to find any information about how to do this anywhere. i am familiar with the command line, but not a complete geekhead and do not know that much about phones... however, i did previously have a rooted hero.
many thanks in advance for any help,
d0cA
d0ca said:
hi all,
i've been trying to figure out how to root my phone. i know that it's pretty straightforward (one click type thing) with a windows computer, but unfortunately i do not have access to windows, only to linux (debian) and i cannot seem to find any information about how to do this anywhere. i am familiar with the command line, but not a complete geekhead and do not know that much about phones... however, i did previously have a rooted hero.
many thanks in advance for any help,
d0cA
Click to expand...
Click to collapse
I particularly have successfully flashed and rooted my phone many times using a virtual machine (VirtualBox) running Windows XP under Ubuntu. However there is a cross-platform software called Heimdall http://forum.xda-developers.com/showthread.php?t=755265 which can be used as an alternative to Odin. I have never used it, but search for it in this forums and you'll find lots of positive feedback of this software.
If, like me you decide to go for a VM instead, you'll just need to config the usb connections to be used by the VM. The rest is very straightforward.
By the time that I first rooted my SGS2, Heimdall had not yet been tested on this phone, and that's why I opted for the VM. As it worked perfectly, I continued using this. Otherwise, I would certainly have opted for Heimdall as it is natively supported by Linux.
By the way, always avoid flashing .PIT files (repartition), either on Odin or Heimdall. I've learnt here in this forums that flashing .PIT or ticking "repartition" on Odin is the major factor of bricking devices!!!
angelomaldito said:
By the way, always avoid flashing .PIT files (repartition), either on Odin or Heimdall. I've learnt here in this forums that flashing .PIT or ticking "repartition" on Odin is the major factor of bricking devices!!!
Click to expand...
Click to collapse
Heimdall will need a PIT file to know where to flash things to, just dont tick repartition.
Odin wont as its samsung shizzel.
veyka said:
Heimdall will need a PIT file to know where to flash things to, just dont tick repartition.
Odin wont as its samsung shizzel.
Click to expand...
Click to collapse
Interesting, and makes sense. And in case you're only flashing a kernel or flashing a firmware packed into a single file, does it need the .PIT as well?
I just hot my S3 today and I am struggling with all the new information I have to study here . I was an HTC user all this years so terms like Odin are pretty new to me. Beyond that I have a mac . Very bad combination with Samsung mobile phones. Not even android file transfer is working at the moment. I tried first to accomplish all the rooting and recovery procedure with virtual machine of Windows 7 but the phone is not available to the guest,when it is in download mode. So I thought I will give Heimdall a try eventhouh Odin seems a far better solution. I don't know which programm is better but Heimdall has very bad documentation. So back the subject. I saw numerous complaints about Heimdall 1.3.2 so I decided to start with 1.3.1. My first question is about the pit file. It is not clear to me if I have to extract it from my device and if yes, how can I do this? Does anyone here has experience with this particular software ,to use it under OSX as a daily driver?
Sent from my GT-I9300 using xda app-developers app
Vintos said:
... Does anyone here has experience with this particular software ,to use it under OSX as a daily driver?
Click to expand...
Click to collapse
Yes and partially negative:
I have flashed the CWM and all went fine.
I have then tried to flash a new stock rom, all went fine and no errors in the program, but then the phone was not working:
it was saying no SIM card installed and was lagged in every operation.
I had to find a Windows PC and reflash with Odin to have my GS3 work again, i suppose Heimdall soft-bricked it, at least the modem part.
To be honest i created myself a Heimdall package with the files of the unpacked stock rom and my own phone downloaded PIT.
But even if i'm pretty sure i did all in the right way, the flashing result was a dead phone.
So, use it with caution ...
Okay so I bought this HTC Amaze the other day and needless to say, I love it.
The only bad thing about it is that it's on 2.3.4 cause it's the unbranded, Asian version. (My english is even set to bloody Malaysian)
Anywho, I read that there's actually an OTA for it that gives 4.0
YAY But that's for tmobile.
Coming from a Motorola Defy+ to HTC isn't exactly a smooth transition, cause in Motorola they couldn't unlock the bootloader and the original stock files were SBF's which were flashed by RSD lite. Also rooting is much easier, in my opinion.
So, I want to boot ICS on this, but not the original tmobile OTA, more like CM9, if possible? I saw there's a few roms I could use.
I tried doing some work on this phone but got confused.
I unlocked the bootloader, and I'm honestly not sure what to do next. Do I need to do S-OFF? I don't even know what that is, let alone how to do it.
Plus I read that it's only available for Ubuntu users?
.............................
Can someone please guide me in the right direction?
If your bootloader is unlocked and you have a custom recovery you should be able to flash a custom ROM like CM. In order to flash a ROM that is specific to another carrier I believe you have to be s-off and super cid
Okay so I installed 4EXT and rooted the device permanently. I tried doing a CM10.1 rom and gapps...... It loaded, but it wont go past the welcome screen where you select the language.
Gonna try to re-wipe and flash again. If not, I made a backup of 2.3.4.
Make sure you check the md5 sums before installation
Okay this is bad, the md5sums don't match and now I'm stuck at white background with htc logo on it all the time.
I can boot into bootloader then recovery. I can also flash roms but they don't work. I tried multiple, always doing a full format except sd card.
I tried flashing stock kernel, not working.
I tried using hasoon's aio to flash original RUU but device undetected.
IDK What to do
Redownload a ROM and make sure the md5 sums match then flash the ROM it you can restore a nandroid if you made one. If the md5 sums don't match that is why you are having issues. It's good you can boot into recovery.
I managed to get it to work on stock rom again, thanks to another forum thread.
I'm a bit scared to try doing it again, seeing that I have windows 8 and the programs don't work on it.
Maybe when I dual boot either ubuntu or windows7 I'll try it again.
Having a nandroid backup and checking the md5 sums before flashing should prevent most issues from happening. I'm running a dual boot windows 8/Ubuntu PC if that means anything to you
It means everything to me!!!!
Can you explain to me how you did it?
I have to burn the image on a cd still, but I tried to dual boot windows 7 and 8 but 7 couldn't be installed on a gpt partition.
I do have an external hard drive, but that's mainly for backing up my data, so I don't want to use that.
Here's what I was doing, I created a partition of 100gbs using the preloaded software on windows, formatted and put it as a letter and it worked well as a partition on windows 8 itself. But when I booted the windows 7 cd, it wouldn't install on it.
Darin_Ram said:
It means everything to me!!!!
Can you explain to me how you did it?
I have to burn the image on a cd still, but I tried to dual boot windows 7 and 8 but 7 couldn't be installed on a gpt partition.
I do have an external hard drive, but that's mainly for backing up my data, so I don't want to use that.
Here's what I was doing, I created a partition of 100gbs using the preloaded software on windows, formatted and put it as a letter and it worked well as a partition on windows 8 itself. But when I booted the windows 7 cd, it wouldn't install on it.
Click to expand...
Click to collapse
I installed Ubuntu with the windows installer if I remember correctly. It's been awhile since I did it so I don't remember exactly how I did it and I don't remember having any issues doing it. My laptop originally came with Windows 7 and I upgraded it to Windows 8 and installed Ubuntu sometime after upgrading to Windows 8. My older hardware may be the reason why it worked now that I'm looking over this stuff again. I'm pretty sure I downloaded the "Install Ubuntu with the Windows installer" to install it. Hopefully that helps.
kmok said:
I installed Ubuntu with the windows installer if I remember correctly. It's been awhile since I did it so I don't remember exactly how I did it and I don't remember having any issues doing it. My laptop originally came with Windows 7 and I upgraded it to Windows 8 and installed Ubuntu sometime after upgrading to Windows 8. My older hardware may be the reason why it worked now that I'm looking over this stuff again. I'm pretty sure I downloaded the "Install Ubuntu with the Windows installer" to install it. Hopefully that helps.
Click to expand...
Click to collapse
Yeah, having the hardware from win7 would have definitely had something to do with the compatibility of Ubuntu on the laptop.
:/ I'll google the windows installer, if it helps I'll let you know.
Darin_Ram said:
Yeah, having the hardware from win7 would have definitely had something to do with the compatibility of Ubuntu on the laptop.
:/ I'll google the windows installer, if it helps I'll let you know.
Click to expand...
Click to collapse
What exactly are you trying to do? Make your phone s-off? All you need is to boot ubuntu 32bit from a cd to make your phone s-off. Everything else is pretty much done through windows or custom recovery. All of t-mobiles RUUs are .zip files and are flashed through the bootloader and the windows toolkits should be able to flash them otherwise some of the other carrier RUUs are .exe files.
No, Hasoon's aio doesn't work on my operating system, I do not know why.
It works fine on windows 7, but I do not always have access to it.
That's why I wanted to dual boot with Ubuntu. If I could get the drivers and programs to work, I can try booting into Cyanogenmod knowing that if anything happens, I can reboot my phone the way I did last time.
I would try WindyCityRockr's WinDroid program. Hasoon's program wasn't Woking for me either but WinDroid worked for me on Windows 8. If that works you may not need to have Ubuntu installed. Booting Ubuntu from a CD is probably your best option
kmok said:
I would try WindyCityRockr's WinDroid program. Hasoon's program wasn't Woking for me either but WinDroid worked for me on Windows 8. If that works you may not need to have Ubuntu installed. Booting Ubuntu from a CD is probably your best option
Click to expand...
Click to collapse
I'll try it out, I still have to re-root my phone lol so if that works, I'll let you know.
I have been through hell and high water today with this Nord N200 5G today. Soft Brick after Soft Brick. iI only flashed TWRP and try to boot into OS after exiting TWRP but i get No OS you sure you want to reboot?. I also can't figure out how to get my internal storage viewed in TWRP. I've read multiple guides and still can't figure it out. I"m pretty new to this so . and they try to flash Magisk for root as well as super su during on adventure fiasco after fiasco today. The Bootloader and OEM unlock was simple straight forward. Most Guides though are not in LAMENS terms and have abbreviations that new people do not understand. i have had to reflash my phone 20+ today with factory due to the NO OS problem with TWRP and can't get it so i can view my internal data from twrp even though i've followed several guides and the ones that says to do the wipe thing i always get the error about it can't mount the data or it has encountered and error 255 and by got try looking things up for those and you you get sent all over the place. So If there is Anyone Out There That would like to help an old geezer out to be able to get a stable TWRP and a Stable root going on please Respond. Sorry Had to Vent......
Oh yea and not to mention Unable to install 3.6.2
TWRP is not officially launched for this phone. In my opinion lineage is the best option for this phone as of now. It has a custom recovery and is easily rooted as well. https://forum.xda-developers.com/t/rom-official-dre-12l-lineageos-19.4473129/
weirdfate said:
TWRP is not officially launched for this phone. In my opinion lineage is the best option for this phone as of now. It has a custom recovery and is easily rooted as well. https://forum.xda-developers.com/t/rom-official-dre-12l-lineageos-19.4473129/
Click to expand...
Click to collapse
A couple of questions before I jump into that.
How are updates handled? Does the OS do auto-updates?
How is the camera?
I don't know a lot about this phone, but previous phones I've owned had proprietary camera/software, and any custom ROM not based on the stock OS lost camera quality because it couldn't use the proprietary software..
jova33 said:
A couple of questions before I jump into that.
How are updates handled? Does the OS do auto-updates?
How is the camera?
I don't know a lot about this phone, but previous phones I've owned had proprietary camera/software, and any custom ROM not based on the stock OS lost camera quality because it couldn't use the proprietary software..
Click to expand...
Click to collapse
Obviously not who you were asking but I just updated to Lineage and it was fairly straightforward following the directions, just make sure you're on Android 11. Updates can be done through settings menu, I just actually applied an update and it worked fine. It can check for updates every day, week, month if you choose I don't know if it will automatically update it though. Camera I have not tried as I don't use it as an everyday phone but generally from what I've seen it's common to have quality go down using software other than stock but I could be wrong.
I can't speak on the difference in camera quality because I dont use it much. There is some loss of function between the stock camera app and the aftermarket rom camera app
This phone has no official twrp so it has tons of decrypting issues which explains almost all of your problems.
What worked for me is to avoid touching the phone if at all possible while in TWRP. It's very unstable and if you click something it will try to mount partitions and somehow brick you in the process. While booted into TWRP I did almost everything via ADB command from my computer instead of through the TWRP menus, including reboot.
I Pushed my magisk package to /tmp instead which worked. I'm just going to go the lineage route later though. I don't think it's worth messing with TWRP on this device.
Update: Phone Complete Bricked. Says something like The Image(boot/recovery) has been destroyed please flash the correct image or call customer service to fix it. on top of this....Unable to flash anything. everything no matter what it is, i even tried to follow a guide to get back to factory and it say that no such partition or volume full. Oh and it's an A/B partition phone
swee08315 said:
What worked for me is to avoid touching the phone if at all possible while in TWRP. It's very unstable and if you click something it will try to mount partitions and somehow brick you in the process. While booted into TWRP I did almost everything via ADB command from my computer instead of through the TWRP menus, including reboot.
I Pushed my magisk package to /tmp instead which worked. I'm just going to go the lineage route later though. I don't think it's worth messing with TWRP on this device.
Click to expand...
Click to collapse
how do you push? ive tried the adb push and to no avail... it just keeps saying it's unable to. oh and when i did have twrp installed it wouldn't boot into the os unless i fastboot boot twrp.img then it would reset and finally boot into regular os
MiniNinja2024 said:
how do you push? ive tried the adb push and to no avail... it just keeps saying it's unable to. oh and when i did have twrp installed it wouldn't boot into the os unless i fastboot boot twrp.img then it would reset and finally boot into regular os
Click to expand...
Click to collapse
I believe it was just "adb push boot.img /tmp/boot.img"
And then in TWRP when selecting a file to flash you have to click on the top level option to go up a directory and find /tmp while not clicking anything else. I pushed to tmp to avoid mounting any partitions since the phone bricked everytime that happened.
swee08315 said:
I believe it was just "adb push boot.img /tmp/boot.img"
And then in TWRP when selecting a file to flash you have to click on the top level option to go up a directory and find /tmp while not clicking anything else. I pushed to tmp to avoid mounting any partitions since the phone bricked everytime that happened.
Click to expand...
Click to collapse
how do i get the phone completely unbricked cause it's saying something like The Image[boot,recovery] has been destroyed please flash correct image or contact customer service to fix it
I forgot to mention that I can no long get into recovery it won't even flash a recovery anymore. it will say it completed successfully but i got to boot recovery and it just boot right back into bootloadre/fastboot mode. i even tried to do fastboot --set-active=a and fastboot --set-active=b tried booting into each of them and nothing. when i do fastboot getvar all it says that boot_a and boot_b are unbootable. any idea how to fix this?
Will be trying again in a week when i get my new unlock token. just took the phone to the store, said that the bricking of the phone happend during an update. They didn't have any Nord N200's in stock so they ordered one and said they would have it in the store in a day or two. onto the next phone til then. any ideas on a TCL A509DL Trac Phone?
MiniNinja2024 said:
I forgot to mention that I can no long get into recovery it won't even flash a recovery anymore. it will say it completed successfully but i got to boot recovery and it just boot right back into bootloadre/fastboot mode. i even tried to do fastboot --set-active=a and fastboot --set-active=b tried booting into each of them and nothing. when i do fastboot getvar all it says that boot_a and boot_b are unbootable. any idea how to fix this?
Click to expand...
Click to collapse
You need to use MSM tools to unbrick. It'll restore your device to stock and relock your bootloader.
swee08315 said:
You need to use MSM tools to unbrick. It'll restore your device to stock and relock your bootloader.
Click to expand...
Click to collapse
Having problems getting msm running on deb linux. Have the firmware and files needed but can't get msm to run on MX linux And can't get VMware to run either to try it through that on windows 10
MiniNinja2024 said:
Having problems getting msm running on deb linux. Have the firmware and files needed but can't get msm to run on MX linux And can't get VMware to run either to try it through that on windows 10
Click to expand...
Click to collapse
i'm not sure if you can even get the devices to connect to the unbrick tools in a virtual machine. to save some time, use a physical computer running windows 10+ and use a virtual machine as a last resort or if you don't have another computer.
by the way, make sure you have the drivers.
justauserthatusesaphone said:
i'm not sure if you can even get the devices to connect to the unbrick tools in a virtual machine. to save some time, use a physical computer running windows 10+ and use a virtual machine as a last resort or if you don't have another computer.
by the way, make sure you have the drivers.
Click to expand...
Click to collapse
i don't have another machine only the one i'm using running MX linux. and with all the Distro's of linux i have installed and used there is no need to install drivers for phones for every phone, 3 that i have connected to my computer it' has recognized all 3 phones and runs adb and fastboot commands fine on them. Lol, Took me a minute to read your name but Love the Name.
Haha, don't flash it. Boot it. I ended up stop using it and am now using the Lineage OS Recovery. SUPER stable. I am in the works making a new TWRP as well... This unofficial variant just isn't working for me either. So, I figured since im making it doe myself, might as well release it
justauserthatusesaphone said:
i'm not sure if you can even get the devices to connect to the unbrick tools in a virtual machine. to save some time, use a physical computer running windows 10+ and use a virtual machine as a last resort or if you don't have another computer.
by the way, make sure you have the drivers.
Click to expand...
Click to collapse
You can. Use virtualbox. I wouldn't bother with qemu.
swee08315 said:
You need to use MSM tools to unbrick. It'll restore your device to stock and relock your bootloader.
Click to expand...
Click to collapse
There is a command line alternative for Linux. It is originally made for flashing android boards, but works with phones as well.
Springles2 said:
You can. Use virtualbox. I wouldn't bother with qemu.
Click to expand...
Click to collapse
Interesting, that's actually useful to know. Thanks.
MiniNinja2024 said:
Update: Phone Complete Bricked. Says something like The Image(boot/recovery) has been destroyed please flash the correct image or call customer service to fix it. on top of this....Unable to flash anything. everything no matter what it is, i even tried to follow a guide to get back to factory and it say that no such partition or volume full. Oh and it's an A/B partition phone
how do you push? ive tried the adb push and to no avail... it just keeps saying it's unable to. oh and when i did have twrp installed it wouldn't boot into the os unless i fastboot boot twrp.img then it would reset and finally boot into regular os
Click to expand...
Click to collapse
I do adb push (File) partition