A few days ago, I attempted to root my girlfriend's T-Mobile G1 phone, previously unrooted, by following the CM instructions in the CM Wiki page for G1 users.
Throughout the entire process, I received the expected output from the g1 screen - that is, until finally installing the latest CN stable ROM - 4.2.15.1. After this install completed from recovery mode, I rebooted the phone by pressing home + back, the screen displayed an image of a box and phone, and then proceeded to the recovery screen again; I rebooted the phone again - this is when the phone started to hang on the G1 screen.
There is a chance I may have forgotten to flash the CN ROM 4.2.15.1 before rebooting, and then subsequently flashing the CN ROM. I am not completely sure about this.
Anyways, here are the steps I took: Formatted SD Card to FAT 32; Downgraded my phone to RC29 - DREAIMG.nbh using the bootloader; after saving the recovery image file cm-recovery-1.4.img to my SD root dir, I used telnet to flash that recovery file. Next, I downloaded all the necessary OS files - DRC83 Base Defanged; Updated Radio file; 4.2.15.1 ROM. Next, in recovery mode, I wiped the phone, and proceeded to install those files in that order.
After getting the hang on the G1 splash screen, I tried to repeat the process over, from flashing the old RC29 ROM to flashing the updated ROM files. However, I have gotten the same result. Now, after reading about how to revert rooted G1 phones back to the stock firmware, I have managed to get the phone running on Cupcake - 1.5, through the CRB43 update. The CRC1 Update consistently fails during the installation - something like patch error code - failed update on line 243. I guess I may need to wait for a system update from t-mobile to get the phone up to date again.
I thought the original problem may have been a corrupted file - but I have repeated this rooting process many times, and have downloaded new files each time, and usually tried to confirm the MD5Check hash, so I doubt this is the problem. Also, today, I received a system update from TMO, and even then, the system hung on the G1 screen again. I've tried to fix this problem myself, but man, I'm at a dead end.
Any advice would help.
I have the same issue, although it first happened while I tried to upgrade from superD to CM5.
The only ROM I can get to run is the ADP1.6 from htc (the -ota- one)
I've tried every ROM and I can't even Nand back to my previous backup...
The thing is driving me nuts, but, although I reinstalled DangerSPL (with success), I can't run (because installation goes fine) anything else than stock 1.6 (which is still better than your cupcake my poor friend).
Even Defranged DRC83 won't run.
All ROMs get stuck on G1 screen...
I've opened a thread about this but so far, got no working advice.
If I have some time available, I'll try switching back from Amon_Ra's recovery 1.6.2 to Cyanogen's recovery 1.4 to see if it works (hell, that's the only thing I haven't tried. Spent a whole weekend on this ****...)
Let me know if you manage to run a custom ROM.
Good luck
alou2 said:
I have the same issue, although it first happened while I tried to upgrade from superD to CM5.
The only ROM I can get to run is the ADP1.6 from htc (the -ota- one)
I've tried every ROM and I can't even Nand back to my previous backup...
The thing is driving me nuts, but, although I reinstalled DangerSPL (with success), I can't run (because installation goes fine) anything else than stock 1.6 (which is still better than your cupcake my poor friend).
Even Defranged DRC83 won't run.
All ROMs get stuck on G1 screen...
I've opened a thread about this but so far, got no working advice.
If I have some time available, I'll try switching back from Amon_Ra's recovery 1.6.2 to Cyanogen's recovery 1.4 to see if it works (hell, that's the only thing I haven't tried. Spent a whole weekend on this ****...)
Let me know if you manage to run a custom ROM.
Good luck
Click to expand...
Click to collapse
I have this problem too, first time rooting for me too... I used this guide:
http://forum.xda-developers.com/showthread.php?t=548924&highlight=root
and got stuck on the G1 screen after pressing Back and Home after installing the same version of cyanogenmod
I have unfortunately bricked my phone, had put custom roms on my phone before and had itje's Touch 14.2 on my phone for about 6 months before deciding to change it.
After changing it, the phone would update to the rom i wanted, but then after about 6 hrs of rom use, the phone would stall, hang and require a hard reset, after trying with a number of roms, this became the norm. I was therefore trying to get my touch 14.2 rom back, but managed to brick my phone.
The phone starts in bootloader mode with:
"KOVS110
SPL - 0.72.0000
MicroP1-787
MicroP2-707
Contunue to Upgrade ROM, please wait...
USB"
That is with the phone connected to the usb port either charging, or connected to the computer (with the sim card out), when the sim card is in, it changed to
"loading..."
and stays on that screen.
I have d'loaded mtty, signed the drivers, but not sure what iam doing wrong..
Possible steps I may need to change for mtty to correct itself maybe due to these factors in this thread (http://forum.xda-developers.com/showthread.php?t=540290&highlight=serial)
MysticGenius said:
Follow this procedure for FLASHING YOUR ROM FROM INTERNAL STORAGE AFTER MTTY
Before you start grab: mtty1.42.zip
AND ENSURE YOU HAVE HARD-SPL ON YOU DEVICE!!
Procedure:
1: Download a ROM of your Choice, RENAME the *.nbh for your ROM to: DIAMIMG.nbh
2: Copy DIAMIMG.nbh to the "Internal Storage" of your Device.
.
Click to expand...
Click to collapse
* Phone needs to be in Hard SPL mode (not sure if the phone is in that mode anymore)
* Place *.nbh on the internal storage of the device (I cannot do this, as the phone is not recognised by the computer)
I have tried everything, but to no avail...
Hard resets, re-flashing, mtty....all come back to the same screen
Please help... : (
try this
try flashing a stock rom and then flash a cooked one...
i had the same problem on my x1...when i flashed a new rom it was fine till i make a soft reset...but instead of a soft reset it performed a hardreset...and sometimes hang on the SE logo
hope it works
report back
I fixed it!!!....
Used SEUS to update the ROM...
phew!!!..
now to hard spl my phone...again
task 29 will also un-brick your device, trying to reflash will give an error, but task29 will set you back to the beginning
Mod. edit: not dev related, moved to general
glad you managed
Big problem here, though I don't think it's hopeless...
I flashed my Kaiser with HardSPL 3.34, then unlocked the SIM, and then properly set up an Android system on it.
Anyway, then I decided I wanted to go back to WinMo, so I found a stock ROM, and tried to flash it back with the KAISimg.nbh method by rebooting and holding down power+camera.
However, that image apparently contained an SPL image, and so I inadvertently flashed my phone back with a normal SPL (and unsuccessfully flashed the WinMo image). Now when I try to boot and flash using power+camera, it just sits there at "Loading...", and Android boots the kernel but can't seem to mount the file system on the SSD. So the phone is useless right now.
Is there a way to fix it or am I screwed?
EDIT: Okay, it seems I had to remove the flash drive, then boot with power+camera. I plugged in my USB cable and it went into USB mode, then I installed an official ROM from HTC's website. Seems to work now! To everyone who helped me in the parallel universe where I didn't figure this out: thanks!
For future reference, if you actually got HardSPL installed then you wouldn't be able to flash a normal SPL without going through some extra hoops. (That's the point of HardSPL). Although it will say that it flashed the SPL it will not actually overwrite the HardSPL.
hi there,
i have a BIG problem, so please, can someone help me?
when i enter the boot load screen (hold down volume buton and press power) it shows something like:
KOVS110
SPL-0.78.0000
MicroP1-787
MicroP2-707
Upgrade ROM code error
Please try again
and whatever i do, the same error ocured. I tried to install hard spl, but it gives an communication error, and it doesn't load, it remains at 0%.
i tried to put a ROM on my micro sd card, put it in the phone, reboot it but it sais "LOADING.....NO IMAGE FILE" and gives me the same screen as sown above.
The ROM version is this k|WWE|Dec 1|.¸¸.·´¯`·.¸¸.Energy.¸¸.·´¯ 6.5|21916 / 6.5.X|23149 * Sense 2019 - xda-developers.
I should mention that i followed some tutorials from this forum about how to reinstall windows step by step. if it metters how i get it broken, i tried to update the software using sony ericsson update service, it loaded the update bar, then all of the sudden, it shut down, and after that it keeps sowing the screen as shown above.
please, can u help me with this problem? thanks a lot, and sorry for my english, is not perfect.
hi there mate, Im no expert but I had the same problem.im no expert and you may have to wait for expert advice,....but......
I reformatted the memory card with MiniTool Partition Wizard Home Edition 5.2 it reformatted the card slowly, you can search the forums for" format card"and download a proper formatting programme.
I also had problems with the actual download once, i kept having the no image error come up over and over, so i re downloaded the file and it worked ,....also when they say take the battery out and wait,...do it for 10 secs.
ionut. said:
hi there,
i have a BIG problem, so please, can someone help me?
when i enter the boot load screen (hold down volume buton and press power) it shows something like:
KOVS110
SPL-0.78.0000
MicroP1-787
MicroP2-707
Upgrade ROM code error
Please try again
and whatever i do, the same error ocured. I tried to install hard spl, but it gives an communication error, and it doesn't load, it remains at 0%.
i tried to put a ROM on my micro sd card, put it in the phone, reboot it but it sais "LOADING.....NO IMAGE FILE" and gives me the same screen as sown above.
The ROM version is this k|WWE|Dec 1|.¸¸.·´¯`·.¸¸.Energy.¸¸.·´¯ 6.5|21916 / 6.5.X|23149 * Sense 2019 - xda-developers.
I should mention that i followed some tutorials from this forum about how to reinstall windows step by step. if it metters how i get it broken, i tried to update the software using sony ericsson update service, it loaded the update bar, then all of the sudden, it shut down, and after that it keeps sowing the screen as shown above.
please, can u help me with this problem? thanks a lot, and sorry for my english, is not perfect.
Click to expand...
Click to collapse
ionut. said:
hi there,
i have a BIG problem, so please, can someone help me?
when i enter the boot load screen (hold down volume buton and press power) it shows something like:
KOVS110
SPL-0.78.0000
MicroP1-787
MicroP2-707
Upgrade ROM code error
Please try again
and whatever i do, the same error ocured. I tried to install hard spl, but it gives an communication error, and it doesn't load, it remains at 0%.
i tried to put a ROM on my micro sd card, put it in the phone, reboot it but it sais "LOADING.....NO IMAGE FILE" and gives me the same screen as sown above.
The ROM version is this k|WWE|Dec 1|.¸¸.·´¯`·.¸¸.Energy.¸¸.·´¯ 6.5|21916 / 6.5.X|23149 * Sense 2019 - xda-developers.
I should mention that i followed some tutorials from this forum about how to reinstall windows step by step. if it metters how i get it broken, i tried to update the software using sony ericsson update service, it loaded the update bar, then all of the sudden, it shut down, and after that it keeps sowing the screen as shown above.
please, can u help me with this problem? thanks a lot, and sorry for my english, is not perfect.
Click to expand...
Click to collapse
hm, not sure if I'm 100% with you, but lets try:
the output you describe (SPL-0.78.0000) clearly shows that you are still on the latest stock spl, which you either got by factory default or through one of your later updates through SEUS (depending on how old your phone is)
this (stock spl) automatically prevents flashing of customizes roms (like the mentioned Energy rom), all you can flash with that are stock roms
there is the hard-spl thread concerning this by olinex which you most probably read and tried
so as I understand it you failed at flashing the hard-spl, then tried to run SEUS which failed as well and now you cannot even start your phone?
after failing at SEUS did you retry to run the SE update utility? it sometimes fails before successfully completing
did you try putting a stock rom on your sd card and flashing this (that would delete personal items and settings not backed up)?
how did you try flashing hard-spl? synching your phone with your pc and launching from there?
Best, DK
hi,
thanks for your post, and for trying to help. i should mention that i have never sync the phone with pc, i never need this. and i tried to hard spl the phone, but also gives error, it shut down. from then i tried several tims to do the update with the sony-ericsson application, it check's the phone and said that i have the latest software, but if there is any problem, try reinstaling the software. i push the reinstall button, it starts reinstalling, but the bar goes between 10 to 25, other time even 60 %, and then gives the communication error, and sais to try again.
i am no expert, this is the first time i try to do this on a phone, so if there is anyone who is so kind to explain step by stpe what i have to do, i shoul thanks him verry much.
So you want to install custom ROM to your phone? you need hardSPL first
If you have it hardSPL it will show 0.7.2.ollinex
then you just flash it. Try google how to hardSPL and FLash
simple mechanism,
X1 (Stock ROM and Stock SPL) -> hard SPL -> X1 (Stock ROM + hardSPL) -> Flash custom ROM (Energy ROM) -> X1 (hard SPL + Custom ROM)
WHY should Hard SPL?
because as DK explained above, SPL is the bios of your X1 and won't accept any ROM beside Stock ROM. so to have your X1, you need to change by doing Hard SPL, it will make your X1 accept any kind of ROM, stock or customed.
is it better to upgrade Stock ROM and Stock SPL to install applications? sorry, i'm just new in SE phone specially x1, so many things to learn here..
outlaw021705 said:
is it better to upgrade Stock ROM and Stock SPL to install applications? sorry, i'm just knew in SE phone specially x1, so many things to learn here..
Click to expand...
Click to collapse
They're both the same. Applications will install fine on a stock rom as well as a custom rom, there's NO difference. Think of it as jailbreaking an iPod Touch or iPhone, they can still install apps from the app store with no problems, NOTHING is changed.
In fact, think of it as a car. An normal car uses petrol. A car with a modified engine ALSO uses petrol. So there's no difference.
The difference between a stock and custom rom however, is huge. A custom rom is basically a stock rom, but modified. Custom roms gives you more customizability, just like jailbreaking an iDevice. Most of the custom roms run more efficiently, and a lot faster than a stock rom.
It's NOT hard to install a custom rom, you just have to read the guides properly and follow the simple steps. It's worth every bit of your time. Just follow the 8 steps here to install hardSPL:
http://forum.xda-developers.com/showthread.php?t=431218
and here if you want video tutorials:
http://forum.xda-developers.com/showthread.php?t=497511
And btw, the SPL thing is just the same as a jailbreak. It's a hack basically. Installing hardSPL will jailbreak your device so that you can install custom roms on it, it's basically "unlocking" the device so you can do whatever you want with it.
So..i finally got mtty working. I don't really know how but i got it working despite the code 10 error while installing.But i decided to install the rom thorugh custom RUU after the task 29 format. So i did everything the mtty tutorial said but now, i can't flash the custom ruu.Whenever I try, it gives me 240 error. I cannot access my internal storage, activesync will not recognize my phone. I cannot boot into anything it gets blocked at the Touch Diamond screen. Did a hard reset..nothing worked. Please help me with a solution! i just want to flash a rom onto it so i can use it. Momentarily I can't do nothing with it...
EDIT : GOT IT! I had to reinstall the official rom back. after that everything back to normal.