Hi,
I'm pretty sure my bootloader is corrupt on my mipad2 tablet (all my own fault, naturally...).
So, I was wondering if there is any general advice regarding how to deal with this (or any
advice at all!). I'm pretty sure it's a *serious* problem - I guess I'm wondering when it can
be dealt with (and how) and when it can't.
Any pointers appreciated.
BR,
Seán.
Related
Hi All,
As a newbie on the block I have been reading trhough the various posts here on upgrading or updating the PPC. There is a lot to be found on what rom's to use etc, etc, but nonetheless I am now stuck after a partial upgrade probably with a m1000 that will not go any further then the bootloader.
As i gathered from other posts it's waiting to be "fed".
But the feeding is not working, with none of the realeases I tried for this Himalaya type.
All of them either lock up or bum out with an error 119, telling me to reset the device and try again...
I can keep doing this until i'm old and grey I guess as each time the same thing happens.
Anyone here have a suggestion how to get some new data into "his brain" or should I just consider the unit trashed and throw it into a wastebin ?
I am really lost here. Any help is much appreciated.
Peter
Petey said:
Hi All,
As a newbie on the block I have been reading trhough the various posts here on upgrading or updating the PPC. There is a lot to be found on what rom's to use etc, etc, but nonetheless I am now stuck after a partial upgrade probably with a m1000 that will not go any further then the bootloader.
As i gathered from other posts it's waiting to be "fed".
But the feeding is not working, with none of the realeases I tried for this Himalaya type.
All of them either lock up or bum out with an error 119, telling me to reset the device and try again...
I can keep doing this until i'm old and grey I guess as each time the same thing happens.
Anyone here have a suggestion how to get some new data into "his brain" or should I just consider the unit trashed and throw it into a wastebin ?
I am really lost here. Any help is much appreciated.
Peter
Click to expand...
Click to collapse
additionally i cannot get to the bootmenu to format registry and storage, so please, if anyone has an original rom backed up that can help me restore it, let me know.
peter
Hi, I'm using an international based galaxy S2 I9100. I've been using PA roms for my S2 for quite a while, then I start to get the annoying problems because my google apps (like chrome, maps, etc) doesn't want to update properly because "storage not sufficient" issue.
So I decided to find a way to expand my S2 internal memory of 2GB and found a thread here about .pit files. Downloaded a modified .pit files to make the internal memory to be 6GB and the SDcard (ums) to be 8GB. Flashed the .pit files according to the instructions through odin (data wiping, cache wipe, delvik cache wipe).
When the flashing finished my internal storage did change into 6GB but my 8GB SD card (ums) is gone. I installed diskinfo and it shows that my 8GB was stated as unmounted.
Then I accidentally flashed another kernel without full wipe, so I tried to recover by re-flashing the samsung official stock rom.
After the md5.tar was finished being installed, I was stuck at the booting screen, it keeps playing the samsung logo over and over again.
Then I decided to download an original .pit files, thinking that the partition is the one who most likely makes it bootlooping. Once again because I'm a bit panicking, I didn't realize that I downloaded .pit file for I9100G not I9100. After flashing, the phone was supposed to reboot, but it just turned off and that's it...
I couldn't get it on, usb driver didn't work anymore (pc won't recognize). I've checked with samsung service center, they confirmed that the device still actually have electric current when we turned them on...but because of flashing rom and stuff the only service they offer is to change the mainboard, but the service lady was kind enough to let me know that I might still have a chance without changing my mb, and that is by trying jtag though they didn't provide it @ samsung service center.
I believe my device is in deadbrick situation and I worries that the most important thing is to actually fix the partition even if the jtag able to revive my phone. I've contacted some mobile phone service center in my town to check about jtag, but most of them gave a not so clear answer to some of my questions..
So I'm asking for some answers of my question from experts in xda forum :
1. Can JTAG / RIFF solve my S2 deadbrick problem & partition as well? And how do they really work?
2. Do you think due to what I did (mentioned above), there's some serious problem that JTAG/RIFF won't fix and if the answer is yes, what is the suitable fix?
Due to this problem I had a bad day, would be appreciated that negative comment is not given coz I know I probably did some stupid things above, but that's part of learning...so answers and good advise are welcome and will be greatly appreciated.
Thanks.
Emtzzz
1 & 2) Nobody here could possibly answer your questions, because we don't have the phone in front of us with the JTAG equipment. Anyone here who tries to tell you otherwise is lying out their arse.
You're only going to know if it's JTAG'able or not when someone who does JTAG's has a look at it/tries to do it.
MistahBungle said:
1 & 2) Nobody here could possibly answer your questions, because we don't have the phone in front of us with the JTAG equipment. Anyone here who tries to tell you otherwise is lying out their arse.
You're only going to know if it's JTAG'able or not when someone who does JTAG's has a look at it/tries to do it.
Click to expand...
Click to collapse
Yes, I understand, that's why I'm hoping there's somebody in this forum who done JTAG or had similar problem with mine might be able to explain to me the solution to my situation...and if they're actually using JTAG as the solution they could probably let me know what to expect / ask from the one who's gonna do the jtag for me.
jtag flashes the bootloader.
If your nand is stuffed, you are looking at mobo change.
Sent from the little guy
I have done a fair amount of research with my problem and would not post unless I was at wits end. So I made a terrible mistake and formatted my phone and took off my back ups. So after researching the problem I learned how to use ADB to either push or side load. Unfortunately my driver for my G2 is not present, and I have had no luck updating it. The device ID presently is USB\VID_18D1&PID_D001&REV_0232
I feel there is most likely an easy fix for my problem that I am overlooking but after hours of trial and error I am now completely out of ideas. My question is simple; how do I fix my driver.
Any help or suggestions would be much appreciated.
There is hope!
Denux2k10 said:
I have done a fair amount of research with my problem and would not post unless I was at wits end. So I made a terrible mistake and formatted my phone and took off my back ups. So after researching the problem I learned how to use ADB to either push or side load. Unfortunately my driver for my G2 is not present, and I have had no luck updating it. The device ID presently is USB\VID_18D1&PID_D001&REV_0232
I feel there is most likely an easy fix for my problem that I am overlooking but after hours of trial and error I am now completely out of ideas. My question is simple; how do I fix my driver.
Any help or suggestions would be much appreciated.
Click to expand...
Click to collapse
I have a sprint G2 Rooted with TWRP I couldn't for the life of me get ADB working when i bricked doing an OTA. Go to this link and follow instructions EXACTLY!!! This is the only thing that saved my G2... let me know...
http://forum.xda-developers.com/showthread.php?t=2432476
Suppose a Samsung phone is stuck in a boot loop, getting only as far as the Samsung logo. Recovery mode doesn't work - it only shows a sick robot with 'No Command' and some text about 'applying CSC' (whatever that is) before going back into the boot loop. Download mode works. You can inspect the hardware, and do whatever is necessary in download mode. Aside from that which can be worked out somehow, the history of the phone (original network, firmware installed, what's been flashed to the phone, unlock status etc) is unknown.
What are the possible causes of this boot loop problem? Does anybody actually know, or is everyone just hiding behind comments like 'there are many possible causes', pretending to be knowledgeable when they don't actually know anything? I ask because I really want to know and genuinely have not seen a complete answer to this question after hours of searching and seriously wonder whether anyone actually knows. If there are 'many possible causes', list them and explain how they result in a boot loop.
How do you work out what software needs flashing to repair the phone? If it can't be worked out, is there a sure-fire way of flashing all of the necessary software so that it will definitely work?
For any phone model, there are many firmwares available, according to country, carrier, and firmware date. What actually governs whether a given firmware is going to work on the phone? Surely the hardware is pretty much always the same? So why does the firmware version matter as long as you get the right phone model?
If the model of the phone is significant (i.e., it isn't possible to give a general answer to these questions that can be followed for any model of Samsung phone), please explain why it is significant for your answer (rather than hiding behind that as an excuse for not answering), and then assume an S4 mini.
Thanks.
Thread moved to Android Q&A, Help & Troubleshooting.
Regards,
Wood Man
Forum Moderator
Hi,
I'm not a developer so sorry if my questions sound basic but I much appreciate your help.
I have a big issue with my GT-i9000 (which works well until now).
It gets into boot loop - when trying to start up it doesn't get through the screen GT-i9000 (every time goes black screen and so on).
I read various discussions here that indicate it could be a bootloop issue that I can fix with Odin and certain fix file that I can't find active source to download it (most of the posts were a few years back).
Also I'm not familiar at all with Odin, adb and other similar softwares and terms, and certain explanations here sound very complicated to me.
I don't want to go through such fix process and to found out later that all of the media files were deleted.
Can you please instruct me how can I fix it at the most simple way (again, I'm not an expert)?
Also, is there a possibility to copy the media files that I have in the phone to my computer and to somehow bypass the loop issue? (without going through Odin etc.)
Anyway I have another phone so if this one will stop working but still I can save all the files I can live with that (of course I prefer this phone will also work).
Thanks a lot in advance!
Thomas
Can you please respond?
It's very urgent, any response will be much appreciated. Thanks.