In my attempt to root my phone, I have caused some major issues.
Specs:
Mytouch 3G (I guess 1.2 since it has the 3.5mm jack)
Current:
S-on
HBoot-1.76.007 (SAPP31000)
CPLD-13
Radio-2.22.23.02
I know I flashed the incorrect stuff from what I found in my research. I cannot use Fastboot because it does not allow remote. No recovery options
I tried following a direction to root, but the sapping file was on megaupload which is not there anymore, so I searched for another from a differant site. The whole issue is I kept getting the incorrect ones, so this happened.
The last one was way off, as you can tell from the above info. I believe I found a correct one, but a new issue arose. When trying to load it, it stay's on "Unzipping" for system. In this particular img, it is the first to be done. I thought it was a currupted file, so I got another from a different source. Same issue. Seems to do that with any I try, including those I got from this site. I am Guessing the incorrect version that got installed.
Only options I have is "Fastboot" and "Simlock". no recovery. The OS will not load and cannot do the home+power boot to get into recovery.
I have been trying to locate how to flash one item at a time from the goldcard I made, but with no luck, most of the links I find seem to be dead, or lacking in the detail I need.
Right now, my phone is useless, and any help would be most appreciated.
While I want to keep this thread open until it's fixed, I suppose the first question is "how to I flash the correct SLP from an SD card without anything else?"
Related
I have a 3125 that I acquired in a semi-bricked state. Bought it for spare parts, but think that maybe I can get it working. It will not boot to WM mode. Boots to bootloader with buttons held at power-on, which reports IPL 4.01.0001 and SPL 4.01.0000.
It recognizes the USB and the update tool recognizes it. But when the update starts, it never gets past 0% on the phone and the update tool eventually errors out and reports I need a newer update tool.
If I put in a µSD with the update file, it goes to the white screen briefly, saying it is checking the SD card, then goes back to tri-color.
I have tried both methods with the original Cingular ROM and the updated one. The µSD is properly recognized by a working phone with bootloader 2.04 (instructs me to press the key to perform the update, though I have not done so).
I have seen here that you must flash via µSD using only an official ROM, which I am doing, but I think that perhaps I don't have the correct official ROM to match this bootloader.
I do not know the history of the phone, so don't know how it came to have bootloader 4.01 or if the bricking happened at that time or later.
This is similar to, but not quite the same as, other threads I have seen where phones bricked after a bad load of WM6 and for which I have not seen a resolution. AFAIK, this was taken out of service before the WM6 ROM was cooked, but an attempt may have been made to load just about anything out there.
At this point, I don't really care what version of ROM gets in there, because I can use the informtation here to put what I want in once I can get to WM5. So, any light on what ROM I should try?
Anybody?
Well, my other 3125 is acting up (randomly resets itself) and now I'd REALLY like to get this one working. Anybody have a clue as to what I can try?
randomly reboots usually means that your battery door is loose. You ever get that "extra" one working?
rom
I have a 3125 with the same ipl/spl and have loaded several roms with no problem.
The link is for the official htc/cingular release. Try via ruu (with sd card removed) first, then if it does not work try the sd method. gl
http://download.america.htc.com/RUU_STAR100_4.1.502.5_02.79.30_CWS_SHIP.exe
lewnetoons said:
I have a 3125 with the same ipl/spl and have loaded several roms with no problem.
The link is for the official htc/cingular release. Try via ruu (with sd card removed) first, then if it does not work try the sd method. gl
Click to expand...
Click to collapse
I have tried both official ROMs with the same results both via PC and via µSD. What is the source of that IPL/SPL? (What ROM image loads it)? I suspect that if I can get THAT ROM image, then I can ressurect the phone. Maybe not and it really is bricked and the error message isn't really accurate.
Yours likely is SuperCID, so you can load anything, where this one appears to not be.
For the one who suggested the problem is the door: unfortunately not. A new door was one thing I did get from the bricked phone. Might be the actual door switch, though. I could try disabling it. Anybody know if its NO or NC?
rom
I will try to find out which rom loaded the ipl/spl, the only unlocking done on the phone is before I change a rom, I run the surrealnetworks cab. (app unlock)
will let you know what I find out reference the ipl/spl
the other thing you might want to try, is download all of the roms and run them, they are listed int he first sticky.
Tiger Shark said:
I have a 3125 that I acquired in a semi-bricked state. Bought it for spare parts, but think that maybe I can get it working. It will not boot to WM mode. Boots to bootloader with buttons held at power-on, which reports IPL 4.01.0001 and SPL 4.01.0000.
It recognizes the USB and the update tool recognizes it. But when the update starts, it never gets past 0% on the phone and the update tool eventually errors out and reports I need a newer update tool.
If I put in a µSD with the update file, it goes to the white screen briefly, saying it is checking the SD card, then goes back to tri-color.
I have tried both methods with the original Cingular ROM and the updated one. The µSD is properly recognized by a working phone with bootloader 2.04 (instructs me to press the key to perform the update, though I have not done so).
I have seen here that you must flash via µSD using only an official ROM, which I am doing, but I think that perhaps I don't have the correct official ROM to match this bootloader.
I do not know the history of the phone, so don't know how it came to have bootloader 4.01 or if the bricking happened at that time or later.
This is similar to, but not quite the same as, other threads I have seen where phones bricked after a bad load of WM6 and for which I have not seen a resolution. AFAIK, this was taken out of service before the WM6 ROM was cooked, but an attempt may have been made to load just about anything out there.
At this point, I don't really care what version of ROM gets in there, because I can use the informtation here to put what I want in once I can get to WM5. So, any light on what ROM I should try?
Click to expand...
Click to collapse
I have exactly the same problem. Did you ever find a solution?
Timmoi said:
I have exactly the same problem. Did you ever find a solution?
Click to expand...
Click to collapse
No, and I've seen even more folks with phones in this condition after a bad WM6 load and still no solution.
My best guess right now is that whatever crashes the system during a load somehow corrupts the boot loader and we are therefore SOL.
I've solved my random resetting problem by acquiring yet another phone with a bad keypad and swapping out my old keypad into it. So my need is no longer critical, but I'd still love to find a solution.
Tiger Shark said:
No, and I've seen even more folks with phones in this condition after a bad WM6 load and still no solution.
My best guess right now is that whatever crashes the system during a load somehow corrupts the boot loader and we are therefore SOL.
Click to expand...
Click to collapse
Just what I was affraid of. Thanks anyway for the answer.
Tiger Shark said:
I've solved my random resetting problem by acquiring yet another phone with a bad keypad and swapping out my old keypad into it. So my need is no longer critical, but I'd still love to find a solution.
Click to expand...
Click to collapse
That's just what I had in mind already. Hope to find some nice and cheap Startrek on Ebay or something.
Try this Full ROM:
RUU_STAR100_4.1.502.5_02.79.30_CWS_SHIP.exe
I have the same IPL/SPL version as yours. I always use this FULL ROM to flash my cell phone when I had problem with my customized ROM.
uniface said:
Try this Full ROM:
RUU_STAR100_4.1.502.5_02.79.30_CWS_SHIP.exe
I have the same IPL/SPL version as yours. I always use this FULL ROM to flash my cell phone when I had problem with my customized ROM.
Click to expand...
Click to collapse
Tried it, but without any luck
Thanks anyway!
I am hoping someone can shed some light on a possible solution:
Generic UK Hero.
Clockwork ROM Manager installed and have backed up and successfully restored my standard Hero Rom.
I recently updated to the newest Radio rom and am hugely impressed with the signal improvements. So some aspects of what I am doing is working.
However I have tried. Vanilla, Chronos and Damage control and whenever I try to update when I get to the reboot stage the phone just sits there on the startup screen that says HERO. No little droid poking his head out, no shiny effect on the Hero logo, just the static logo. Latest update attempt has been sitting there or 12 minutes now.
I can pop the battery out and restore my original backed up settings no problem.
This has been tried while charging, while plugged into the USB and while not plugged into anything.
Any ideas ?
Thanks
Are you using a CDMA or GSM Hero? Vanilla could be either, but as far as i know, Chronos is for GSM only, and Damagecontrol is CDMA only.
Dont put the wrong type on the wrong handset.
CDMA or GSM ?
not sure what the difference is, I have a UK Hero that does 3G. I have tried UK specific (I think) roms (Vanillain) with exactly the same result. When rebooting after applying the zip update I just sits on the HERO screen.
hmmmm
Bit more info
I have been playing with fastboot/hboot and while it's a bit quick, hboot is reporting no image or wrong image aginst these (and more files)
HERODIAG.ZIP
HERODIA3.nmh
HERODIA2.nmh
etc. there's more of these.
This indicates I have loaded the wrong ROM image? Or have screwed up the (seemingly) simple process of flashing a rom.
Arse!
God I feel such an arse. Loading CDMA ROM Image on GSM Hero will not work.. Just loaded VillainRom 5.5 and it's working.
Mebbe not
A bit too impatient posting there. No Villain has the same problem.
Fastboot gives me
Fat32 INit ok
Open File Fail
Reboot Device?
wodswods said:
Fat32 INit ok
Open File Fail
Reboot Device?
Click to expand...
Click to collapse
Sorry i dont know what that means. the only thing I can suggest is to follow BTDAG's guide which is linked in my signature,.... Or wait to see if anyone can shed any light on the error you get?
Or look for a thread with support for that Clockwork ROM Manager?
Wait longer and get a logcat running to see what is happening.
OK well I have trying my best as a noob to research for 2 days not in and out on how to fix my issue
My friend tried rooting my phone and to install a different rom. I am on 2.1 and unfortunately I got the phone used with 2.1 already on it so I don't know if it was a leaked or legit 2.1 rom, and I am learning as I go here to fix this issue as I have never new how to do this stuff nor have I ever done it.
Where I am at now:
only thing that happens when I hit power is the phone "vibrates then stays on the 3 skateboard screen" or press "volume down + power" and it goes to the Hboot screen. I go into recovery and it goes to clockworkmod and from there after trying to install any roms from the sd card it says on the last 3 lines
"E:Failure at line 9:
copy_dir PACKAGE:system SYSTEM:
Installation aborted.
and every time I go back or power up to the Hboot screen it does not have any "update bar" (I guess if this was done right as I read on other threads there should be some type of update bar) on the right corner or any other options "for me to select" accept:
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
and then with some other info above the Hboot highlighted in blue
I have tried formatting the sd card a bunch of times, I did the clearing of the "wipe data, wipe cache partition, wipe dalvikcache" as I read to do over my reading, but I see that if I go under any restore options under clockwork, no files are found for me to back up too so I am seeing he did not back up any of my info, I also have tried using 2 different ds cards.
So more less it looks like my options are to get this fixed from the only place my phone will boot to with options and thats when I press volume + and power so I guess loading whatever I need to my sd card>>if thats an option or am I screwed, I have seen many tutorials but none of them start where my particular position is stuck at in Hboot. this is my only phone and I had to buy a prepaid which is just about out of minutes, I put an add on craigslist trying to get someone I will pay to fix my issue but no luck, please I need help and I will pay u somehow to guide me through this of my exact issue, I was trying to get to rom 2.3 but if it's easier to get back to 2.1 rom then so be it.
PLEASE!~~
Please HELP!
Cheeva316 said:
Please HELP!
Click to expand...
Click to collapse
Got a solution in the making for you, just give me about 30 minutes.
Edit: Maybe 45 minutes lol, sorry i'm testing this before I have you do it to see if it works.
Ok download the following files:
http://www.mediafire.com/?njwqa7axwzyaqgb
http://www.mediafire.com/?f69cl8dc747h0l9
http://www.mediafire.com/?xg8nnqs177xggx4
http://www.mediafire.com/?qxpi5wsx5lzbhbo
http://www.mediafire.com/?4tg67hck7vh1xxs
Edit: Flash the "rootme.zip" first then follow the rest.
Now what you need to do first is extract the "nandroid" file to somewhere you can easily find it.
Now take the folder called "nandroid" along with all the other zip files you downloaded and place them on your sd card. Put your sd card in your phone and power on with volume down+end. Press volume up. Use the trackball to select "Backup/Restore". Use the trackball again to select "Nand Restore". Use it again to select "HT9BGHG01402". Use it again to select "BDS-20110125-0901". Let the restore run, then power off your phone. Turn your phone back on with just the power button, let it run (might even take up to 10 minutes for the phone to start up). Let me know if the phone boots up or not after about 10-15 minutes. This should work and if it does then we can go from there, even to getting you 2.3 if you want.
You might be asking, what the hell is he having me do ? Here's what i'm doing. I made a nandroid backup a few months ago of when I had kaosfroyov39 which is a 2.2 rom. I am going to have you flash MY backup to YOUR phone which when done right, CAN work. Anyway, let me know what happens and remember to give the phone about 10-15 minutes to boot all the way.
Cheeva316 said:
"E:Failure at line 9:
copy_dir PACKAGE:system SYSTEM:
Installation aborted.
Click to expand...
Click to collapse
( Another phone on the precipice of being ruined by someone's cobbled-together "clockwork" recovery. )
If the /system flash memory partition got corrupted in a way that left a lot of pages marked as bad pages, then the /system partition will be "short", and only small ROMs will successfully load into it, if at all. That might be the cause of the above error messages.
But - because you are using Clockwork, there is really no way to know if that is the case, or if you simply have a whole bunch of corrupted ROM files on your SD card. That's because Clockwork does not verify ROM files before it starts flashing them - which allows total garbage to be flashed to the phone. (That's why Clockwork should never be used by newbs).
Here's what I would suggest you do.
- Make sure you are keeping the phone well charged. (Leaving the phone in HBOOT mode will discharge the battery quickly, even if it is plugged in to the charger, BTW).
- Report the exact bootloader version you have - probably 1.47.0000 or 1.49.0000, but it could be something other. Please be precise.
- With the power off, eject the SD card out of the slot and see if you can boot into the normal HBOOT menu with no SD card in the slot. Report your result.
- Boot into the recovery menu and tell us what version # of the recovery you have. If you can determine the details of how your friend attempted to root the phone, that might be pertinent. Again - precise details are valuable; vague hand-waving not so much.
- The Amon_RA recovery has a mode ("USB-MS toggle") which allows you to mount the SD card to the PC. Does your "Clockwork" recovery have this feature, or are you able to put files onto the micro-SD card using a media slot on a PC?
- Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
What I would suggest you do at the moment is to find the SMALLEST Eris** ROM you can find, get it onto your SD card, verify that you didn't corrupt it, and then perform a "wipe data/factory reset" in your recovery and attempt to install it. If you get the same errors as above, then you should definitely NOT try to do a PB00IMG.ZIP or RUU installation. (The current gingerbread ROMs (e.g. GSB v1.4) are pretty small - they only use about 65% of the /system partition.)
I have a flashable "repair" file which might be applicable. It is not a "ROM" per se - it uses some low-level MTD (flash memory) repair techniques, and also flashes into place the original Amon_RA (v1.6.2) recovery, instead of whatever p.o.s. "Clockwork" recovery you currently have on the phone; but I regard it as something which should only be used as a last resort. But - without some more details and testing on your part, I don't feel comfortable about posting it up.
Let me know.
**PS I wanted to ask one more question - this is an Eris we are talking about, right? (I note you were posting in the Hero CDMA forum not so long ago).
Well I want to thank you for replying with such info but it seems that the recovery image file that I reinstalled on the phone was bad cause when it was updating the bar was going up but as it was going through each item it was updating.. I noticed "bootloader in red letters" with I believe saying "error" next to it and then same on another item it tried updating then the phone powered off and now it's dead, tried everything, no charging light comes on, computer (2 different computers) wont reconize it, it's doing nothing at all, I will try to get my hands on another battery but I am broke, but I doubt it's the battery cause I heard with a bootloader error (or damaged) then the phone won't boot up or do anything so I guess the phone is scrap for parts which sucks cause now my friend who started this deal killed my only phone me n my family had, another lesson learned...time to try n sell some stuff on craigslist..damn
Yes it's a Droid Eris...or was! damnnnn...
Again thank you for your help very much appreciated...
Wish I would of read this part before I let my friend re-load the "PB00IMG.ZIP" cause thats exactly what he loaded and then it started the process what I jus described above..f***k!
Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
Cheeva316 said:
Wish I would of read this part before I let my friend re-load the "PB00IMG.ZIP" cause thats exactly what he loaded and then it started the process what I jus described above..f***k!
Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
Click to expand...
Click to collapse
Well, I am very sorry that this happened to you and my advice to you didn't reach you in time. From the details that you added, I am pretty sure that you indeed have a hard brick.
BUT - the death of your Eris can still help others avoid the same fate. If you can reconstruct the rooting process you went through,
[SIZE=+2]PLEASE LET US KNOW EXACTLY WHAT ROOTING METHOD YOU USED[/SIZE] - and then we can wave people away from it.
When I say exactly, I mean extremely specific: do you still have the download file that you used? If so, push it up to an uploader site and give a link to it. (I think you mentioned unrevoked or something). Do you still have the exact link you used to download that rooting software? Was it Unrevoked? Z4root?
bftb0
I will tomorrow as I saved all the files on my laptop n I am on my pc now, but will do try my best as I am a newb to this phone stuff
Did you try what I suggested or is it too late ?
phone wont do anything so cant do nothing...
Did you find out any more details about the rooting method you used?
might be a couple more days till I can get to it, my laptop is messing up now...all the saved info was on it
Hi. I have spent the past 10 hours trying to root my phone and install an XtraLite type of ROM because I am so sick of have 75% of my RAM used up when I haven't even started using the phone. I softbricked my phone, and after hours of trying to solve every minor issue that came up I finally found a solution and managed to flash a stock ROM. I have a lot of questions that I would love to get answers to because I am a little bit confused right now.
My history.
Bootloader
I spent so much time googling this and I decided to trust one site that said, if you can't find the "OEM Unlocked" option in "Developer Options" then your bootloader is probably already unlocked. This was the closest I got to an answer, along with many people with SM-G925F saying the root was successful for them without doing something to their bootloader. Can someone please clarify what I need to do with the bootloader with my EU SM-G925F?
Flashmode/Download Mode
Prior to this I spent very long trying the "adb-windows reboot bootloader/flashboot-windows oem unlock" without any results. However I somehow came to the conclusion that "Download" mode for my Samsung was no different. Any clarification on this subject please?
Rooting
The first rooting guide I trusted was the CF-Auto-Root page. This is where the bootloader question was raised but as I came to the conclusion that the bootloader already was unlocked, I decided to give it a shot. I downloaded SM-G925F file, added it to AP on Odin, and flashed my phone. Now my phone was locked in a bootloop. According to CF-Root page "A modified recovery and cache partition will be flashed, which will install (only) SuperSU, then clean-up the cache partition and re-flash the stock recovery. For the root to work, the device must reboot into recovery. Most devices will do this automatically after flashing these files, but in case that does not happen, please boot into recovery manually.". As you probably guessed, my phone never booted into recovery mode, and I was never able to manually do it either since the phone was in a unstoppable bootloop. Did I do something wrong here or misunderstand anything?
ROM Instructions
My first choice was: http://forum.xda-developers.com/gal...xtrestolite-deodexed-mod-edition-1-3-t3119968
I failed the first step, never even managed to root with CF-Root. And regarding TWRP, I did download the correct version "twrp-3.0.0-0-zerolteeu" I assume. However, many descriptions say my phone needs to be rooted before I can install TWRP so I never tried to install it. Even if, I couldn't find a detailed enough description of how to install TWRP. All it says is "flash it". Problem is, I am not sure if I am supposed to be in "Download mode" and use Odin loading TWRP into "AP" or how does this work?
Never got to the ROM installing, but it would be nice to have something more detailed than "Put it on your phone, install it". Like, do I enter recovery mode and navigate to the rar file and chose to install it? Not sure how this works.
My solution to bootloop
This part took me the longest. For those stuck in a bootloop. Holding DownVolume + Power button for at least 15 sec will simulate disconnection of the battery. This helps you turn you device off. Also, if you nothing happens, make sure you unplug the USB cable as it keeps trying charge and show the status it tries to boot and keeps looping as a result. I could always manage to get into "download mode" through DownVolume + Home Button + Power Button no matter what, and I am grateful for that. I managed to find the exact build I was using on my phone "G925FXXU3COJ1_G925FOJV3COJ1_G925FXXU3COI9_HOME". But everytime I tried to flash, it always failed in the end. I spent hours on google. Someone mentioned something about it failing on a certain point of the writing, involving hidden.img. I googled for info on how to resolve this, and someone suggested to rename hidden.img to hidden.tar but it did not help. I also read some threads regarding using a matching PIT file and there were about 7 different ones to chose from. I tried them all without success. Finally I read something about removing hidden.img from the ROM. I renamed the ROM from .tar.md5 to .tar. Unpacked it, and then repacked it without hidden.img using tar-Tool from these forums. The following flash of the new created tar.md5 (without hidden.img in it) was successful.
Slave for stubborness
Unfortunately since I spent so long getting through this horrible experience, I would feel bad have wasted an entire day just to get a phone that is now reset. I could have done that in 30 seconds. However I am persistent to get this working and I am truly grateful for any help you people can supply my with. I did manage to root and ROM my old S3 but that was a while ago and I only remember a few small things about Odin and so forth. However things seem much more complicated now than before.
Thank you in advance,
Alex
I can't even complain about anything because if was going to, I should have done it before I goofed up. first strike was letting it goof the region. Fine. But what killed it was not flashing the image while moving to ics. It stayed at cleaning for like 40 minutes, and I turned it off. I'm certain I have the us version.
I am hoping someone can throw me a bone about what may have come after installing the image, as well as if there's some sort of command I can enter to push that skipped img file. Or if I can use the data from another one to fix this one. also if I can push something in adb to fetch the region. Or if there are gods, a region free update. Or a program that can flash via recovery and not in a normal boot.
I have a couple different versions of ics on the device, one wants a signature, and the other says something doesn't match and aborts it. Reading around I hear vaguely about how people with the same device managed to fix it, and the ones who have posted working links to drivers or zips, I have tried them to no avail. When the other one gets here, I'm hoping I can get the update zip from that and maybe click away at the screen until I get some type of results.
Also, is there any type of information on what hardware part all of this is stored on? Maybe I can replace that.
Maybe someone can point me in the right direction. Though, I'm sure someone might have shed light on some of it, and it's buried under a bunch of tablet s advice...