I've got a month-old mytouch running spl-1.33.0006. I first rooted it using theunlockr.com's guide. I flashed a bunch of Hero roms, had limited sucess. I tried out CM Mod and love it- simple and stable. But now I want to go back and try some updated Hero and Sense roms.. The only problem is that I get stuck in a boot loop in every one I try(eVil v3s, OPTIMIZEDprime, SenseHero, etc). I try to go back to the earlier roms I tried(HERO 1.9.1A, 1.8, Jacheroski2.2a) and get the same problem. I wipe/re-partition/reboot/wipe/flash on every flash. I've even unrooted and re-rooted with the same luck. Is it my spl?
m4ttj00 said:
I've got a month-old mytouch running spl-1.33.0006. I first rooted it using theunlockr.com's guide. I flashed a bunch of Hero roms, had limited sucess. I tried out CM Mod and love it- simple and stable. But now I want to go back and try some updated Hero and Sense roms.. The only problem is that I get stuck in a boot loop in every one I try(eVil v3s, OPTIMIZEDprime, SenseHero, etc). I try to go back to the earlier roms I tried(HERO 1.9.1A, 1.8, Jacheroski2.2a) and get the same problem. I wipe/re-partition/reboot/wipe/flash on every flash. I've even unrooted and re-rooted with the same luck. Is it my spl?
Click to expand...
Click to collapse
yes it is the spl. you need to update it to an engineering spl
got it
It was actually the partitions. I've been using sparted but on a whim I switched to regular 'ol parted and it's running like a champ. I did update my spl to an engineering release after the fact but I didn't notice much difference. For anyone interested, here's what I've tried on my 4gb microsd:
(didn't work)
sparted -es 512M -ss 128M
reboot / wipe / flash
(worked)
parted /dev/block/mmcblk0
rm 1
rm 2
rm 3
mkpartfs primary fat32 0M 3369M
mkpartfs primary ext2 3369M 3869M
mkpartfs primary linux-swap 3869M 3965M
reboot / wipe /flash
Related
Hi there,
as you may know, some owners of a desire have an issue with their USB/BT/FM functions. For example only fastboot works but no adb / mass storage ...
So, i thought opening this thread to collect your issues, please post the following informations:
Bootloader Infos
Rooted or not
Which rom
Have you used mass storage switch in recovery
Do you use a2sd or a2sd+?
If there are enough answers i will send the collected infos to paul from modaco, who tries to adress the issue.
no usb-bt-fm
bootloader 0.75
original rom 1.15.405.4
when does it happen for you
Also posted om Modaco
Bootloader 0.75
Stock ROM 1.15.405.4 Rooted + App2sd + dalvic
Yes, I used Mass storage in recovery
Issue startet when I transfered the MCR custom fra PC to phone via recovery
I loaded a rom amended with root permissions, not happy I restored everything to its original state with the 1.15.405.4 but now no longer works usb-bt - FM ... and access to most recovery so I can not load the rom recovery .. . Help
From what i know the guys looking into this have problems to dress the trigger of the brick, so all infos on how and when ar great
Bare in mind that the rooting process was at your own risk: no-one (HTC or Paul) will take responsibility if features are no longer working.
Personally, everyone works fine on mine including adb/mass storage. I don't actually see why it'd break.
OP, what OS are you using? I had to add some udev lines into Ubuntu as otherwise adb would work but Mass Storage would fail (on my netbook, even adb wouldn't function without adding the android rules).
I know it's our risc, but hey without some investigation no progress, right?
Btw. Paul is looking into this but no ETA for now
I had exactly the same issue as you lot, only difference was that my new rom flash was interrupted by me knocking the phone and the battery falling out!
I was on evil's 1.0 and decided to change to his 1.1. In the middle of the phone formatting during the flash, I knocked the phone and the battery dislodged causing it to lose power. I had the sd card formatted and was already using a2sd. Turning it back on and restarting the root process from step 1 on Tiny Core Linux got me back with a semi working phone. I had no BT, no SD card, and didn't check the FM radio. It also started to lose signal and would require a reboot to get it back.
I tried unrooting it using paul's method and it was still the same. I just took it back to the shop and acted stupid. They gave me a brand new boxed one, no questions asked I'm scared to try flashing again now though lol.
0.75
Modaco R2 with A2SD+
Yes i have used USB-MS (still works)
no usb connectivity from within android.... but adb works
Bootloader 0.75, tried a few different ROMs (primarily eViL's, tried some MoDaCo), and I've definitely mounted the SD from within recovery. Every single ROM swap I've done was accompanied with a full wipe and SD partition afterwards.
So far I guess I've just been lucky. USB still works, though it can take a long damn time to get recognized in Windows if I'm syncing through the Desire; if I take the SD card out and pop it in a reader, it pops up instantly.
So: .75, lots of ROMs, definitely mounted SD from recovery, always full wipe and format. No issues. Supremely lucky, apparently. :/
Hboot 0.80 o2 Germany ModacoCustomRom r3.
Today after reflashing MCR3! Before all was very well the only thing was that iwasnt able to mount my sdcard without a witget!
Bootloader 0.75
MoDaCo r3 Rom with app2sd+
I used Mass storage in recovery
Issue startet after I flash the jit patch,it can't use recovery again
Can you all confirm that you had a boot loop at some point during your flashing?
The conversations on Modaco now have me convinced that this is triggered when you go through a boot loop of three cycles.
Loccy said:
Can you all confirm that you had a boot loop at some point during your flashing?
The conversations on Modaco now have me convinced that this is triggered when you go through a boot loop of three cycles.
Click to expand...
Click to collapse
yes,I think it's,but have a solution now?
miyu-hitori said:
yes,I think it's,but have a solution now?
Click to expand...
Click to collapse
No, not for those who've been bitten, but I think the rule for those of us still flashing is:
1) Flash rom (or update.zip for kernel, make changes to system, etc) in recovery
2) reboot
3) immediately do adb logcat on your PC and watch first boot like a hawk
4) if logcat reveals that your device is bootlooping, PULL THE BATTERY IMMEDIATELY. Reboot into recovery (which should count as a "successful" boot, and reset the counter) and flash a known good ROM, restore your backup, whatever.
Fixing those phones that are dead is unfortunately a task for a greater mind than mine.
Hi,
I have Googled around quite a bit and have attained enough knowledge to be able to run custom ROMs on my HTC Desire. Presently, I am running the Desire with S-OFF and the Sense partition image.
Here's the issue I am facing. My phone only seems to be able to run Cyanogenmod (any version) or MIUIROM (any version). Apart from these two ROMs, it's not able to get anything to work. Other ROMs install well using Clockwordmod Recovery, but I can't get the phone to boot into the ROM. The only thing that shows during the boot is the "AlphaRev" bootscreen (The one with the Why So Serious joker image). I have read that ROMs take time to stabilize on first run and hence left the phone in the boot state for quite some time (once for almost 6 hours), but nothing happened. Any help at all would be appreciated. I really want to expand my boundaries beyond CM7 and MIUIROM. Please take time out to help this Android fan
Here's my config again:
1) HTC Desire Rooted
2) S-OFF using Alpha-Rev
3) 4 GB microSD with 1 GB ext. Rest is FAT
4) CM7RC4 or MIUIROM depending on my mood.
5) Clockworkmod Recovery 2.5.0.7
6) Sense image by AlphaRev
7) Data2Whatever 0.4d for managing ext
Regards
Abhigyan
I said I would flash cyanogenmod on a friends G1 because he was fed up with 1.6. I've flashed many custom ROM's on several different devices before but I've made a mess of things with this G1 and I can hardly hand back an unusable phone so I would really appreciate your help.
I rooted the phone using Androot, backed up the apps and settings using titanium backup and then the texts using a text backup app. I then downloaded Rom manager and flashed the latest clockworkmod recovery. Next I downloaded the latest official cyanogenmod rom for the dream/g1 and placed it on the phones SD card using my computer. I then re-opened rom manager and used it to select the zip file from the sd (to flash it) on prompt I checked two boxes one to wipe data and one to wipe the dalvik cache and pressed ok.
The phone rebooted into the recovery wiped the stuff, supposedly flashed the rom and rebooted. However it got stuck on the t-mobile g1 boot screen(it never showed anything else first or anything after) I left it for ages with no joy. I then tried wiping from the recovery and flashing again - same thing so i put cm5 on and tried flashing that. Same problem. Then i realised that it probably would not work because I would need to use DangerSPL as the /system partition is too small on the dream/g1. To be honest at this point I can't be bothered with to do that and this guy will be happy with anything above 1.6 to be honest so I thought I would try and flash CM4 because that's based on Eclair I believe (and so it not require I use DangerSPL or any other method to repartition the NAND). However, I tried it twice and still no luck.
At this point I'm somewhat panicking as I cannot seem to make the phone boot and it isn't even mine! Is anyone able to help?
Anyone? Please?
Look, at this stage I will forget custom roms etc. If anyone can tell me the easiest way to get this phone booting android again i would be very grateful.
Even if you could just tell me exactly how to restore it to stock 1.6 from here?
I have flashed roms on phones before - never had a problem but this is driving me crazy - please help!
wollac11 said:
Hi I said I would flash cyanogenmod on a friends G1 coz he was pissed off with 1.6 but im having trouble and I can hardly hand back an unusable phone so i really need your help.
I rooted the phone using Androot, backed up the apps and settings using titanium backup and then the texts using a text backup app. I then downloaded Rom manager and flashed the latest clockworkmod recovery. Next I downloaded the latest official cyanogenmod rom for the dream/g1 and placed it on the phones SD card using my computer. I then re-opened rom manager and used it to select the zip file from the sd (to flash it) on prompt I checked two boxes one to wipe data and one to wipe the dalvik cache and pressed ok.
The phone rebooted into the recovery wiped the stuff, supposedly flashed the rom and rebooted. However it got stuck on the t-mobile g1 boot screen(it never showed anything else first or anything after) I left it for ages with no joy. I then tried wiping from the recovery and flashing again - same thing so i put cm5 on and tried flashing that. Same problem. Then i realised that it probably would not work coz i would need to use DangerSPL coz the /system partition is too small on the dream/g1. Tbh i'm tired so I cba to do that and this guy is not that technical so he will be happy with anything above 1.6 so I thought I do CM4 coz thats 2.0 or 2.1 i seem to remember (and it not require I use DangerSPL) - tried it twice and still not luck.
HOW THE HELL CAN A GET THIS STUPID THING TO WORK AGAIN!??
MAJOR PANIC AS THIS IS NOT MY PHONE - PLEASE HELP!!!
Click to expand...
Click to collapse
Try this thread: http://forum.xda-developers.com/showthread.php?t=803482. I hope it helps.
It's been way too long since I rooted mine to be of any real help but I shall try nonetheless.
Firstly, there is a guide in the G1 forum to unroot and get back to stock firmware: Here (but note that I've never done this).
I must stress though (admittedly from memory) that if you have flashed an SPL or radio image at all, be VERY careful about the order in which you revert back to stock (or go to get a custom ROM depending on which way you decide to go). The G1 is very picky, and flashing things (mostly SPL and radio IIRC) in the wrong order will brick the device. That said, if you follow the instructions you find to the letter you should be OK. But yeah, read twice, flash once.
There is a lot of information in the stickies in the G1 forum. It could take a while to wade through but it should all be there. Failing that, post in the Q&A or General G1 subforums and I'm sure a current user will help you out.
I apologise if I've just posted a bunch of stuff you already know/have read - like I said, I've not used the phone in a while - just trying to offer what I can.
Thanks
No worries now guys i've done it! It was quite complicated but its all sorted now. If anyone is trying this and has the same (or similar) issue then pm me and I will tell you how I sorted it.
Otherwise thanks guys and you can conciser this thread:
---------------------closed--------------------------
Hi need a bit of help with this one if possible.
start the top..
went to flash leedroids rom..flashed boot image but forgot to pull rom over.
so had various issues getting over in the end had to mess around with recoverys and totally wipe my sd for it to be recognized.
so i solved all this then..now the issue is..of everything i push over..only one rom boots up and installs fine..and that is a cm9 test without sd mounting..so it solves nothing.
any ideas of how to get a rom on there where i can mount the sd..download a rom and put it on..
ill be honest..htc+internal sd card=not happy
ive pushed leedroids..virtuous..utbs rom but nothing.
i tried aokp but it didnt even push.
with these also some get corrupted by a protocol failure..
many questions. currently has cm9 on..but no mounting..so great
Did you already try a factory reset after flashing the stock recovery (e.g. from MoDaCo)?
-
Hi rootrider, yeah i followed a post i found..
basically i used the one click toolkit to flash the stock recovery..then cleared storage and all data etc.then installed clockwork back..it doesnt like the working roms though
cm9 is the only one i can boot up..at least it sees the sd card again in clockwork though
Had your problem as well... I don't remember exactly what I did to get out among many other things (sh..).
Had some trouble as well flashing stock recovery with the one click tool kit. It didn't work as expected. So I did it with adb. Just keep on trying, there is a way out.
-
My next course of action is, to flash the stock recovery, clear everything,reinstall clockwork then install aokp..if its something with the type of rom.maybe that will work..i can mount..get a rom on the sd and resume business as usual..
debatebale whether itll work lol
If this doesn't help get Thor's hammer and flash your appropriate RUU (again).
Easiest method would be to run an RUU and start over again. I see your vodafone UK so try this one
http://dl.dropbox.com/u/69014495/RU..._2_10.23.31501S.10L_release_258386_signed.exe
It also includes the new radio too !
Just relock bootloader before running it, After its finished unlock and fastboot flash cwm..
easy peasy !!
--
thanks people, im running leedroids rom now, seemed my issue was is after pushing the file over i just tried to install immediatley..after a couple of reboots just for the hell of it,untouchables rom started installing...phew..
sadly all my sd contents have gone..very dissapointed with the sd card business!
still least its working again!
thankfully azzle didnt need to go back to ruu
Aye, captain. Glad to read this.
Hi
So I was using CM7 with Link2SD and everything was going smoothly.
Then I discovered I could call using my headphones which was possible on stock ROM. After I searched, I found out that the nightly build had that bug corrected. So I update to nightly.
Then the you know what hit the fan
So I boot back and get a warning from Link2SD that my card could not be mounted during boot and that therefore my apps were not available and that I had to reboot. So I did. Same message. I recreated the scripts and rebooted, same message.
So I go back on the stable version of CM7. Same problem.
I tried recreating the partitions on gparted and using ClockWorkMod and trying different formats (ext2, ext3, ext4, Fat32), formatted everything including /system, went back to stock ROM and then back on CM7, nothing works! I keep getting the same error message.
I went to see the log and it says that it cannot be mounted because device or resource busy.
So, here are my questions:
- Does that mean that something from the nightly build has been left behind?
- If so, how do I get rid of it?
- If not, how can I get rid of this error. I tried everything I could find.
I also think that it may have left some files behind because I'm on Koodo. The only stock ROM I could find was Telus. The first time I restored stock ROM using the Telus ROM, I had to do some keypad numbering to get Koodo back. But the last time I restored the stock ROM it detected it as Koodo instantly.
Thank you