Hi,
new to the android scene, always had a wm device, any way read all the wiki stuff and created a goldcard for my G2 /hero, downgraded rom and installed recovery image. downloaded a few roms to try and sucessfully flashed them.
My only problem is that any non original image i flash the phone is always in safe mode, go back to 1.5 stock image all is o.k.
any help or advice will be great.
thanks.
i have tried holding the menu button whilst booting many times and no luck
which recovery you installed?
recommended is RA-hero-1.6.2
make full wipe
flash rom (you can try VillainROM 12, for me works flawlessly, IMO best ROM for hero)
i am using 1.6.2 and have villainrom 12 as well as a rooted ota 2.1.
i also get an error whilst wiping ext, it tells me to wipe ext via adb
I have had the errors about wiping via adb before, not sure why this happens, usually i found it ok if i shut down then booted back into recovery and tried again.
If that doesnt work, use adb to wipe the ext or use another micro SD while u flash the rom.
Never had safe mode before so cant offer any more help sorry
Try to repair the ext in SDcard menu 1st, then wipe ext.
I have tried the repair ext and re-wipe all with the same results.
I have now tried to use the ota update from a stock 1.5 rom. The update worked ok but even with the ota update the phone was left in safe mode.
So it seems any 2.1 build leaves my phone in safe, how strange.
To wipe ext via adb boot into recovery menu then try this:
Code:
adb shell rm -fR /system/sd/*
If you would see your ext partition try this:
Code:
adb shell
parted /dev/block/mmcblk0
print
thanks for the suggestions, but still no luck, i have tried the 2.1 ota update, villain 12 rom and modaco r5 all with the same results. Flashed ok but when it starts its stuck in safe mode.
Maybe i will just have to wait for the official t-mobile update unless any one has any other ideas.
are you orange user ?
It's a t-mobile g2
I first thought it may be because of this but the stock 1.5
worked ok.
I have also tried multiple radio versions.
I can only asume that the rom isn't happy with something and that's why
it starts in safe mode, is there any system logs I could look at?
I've got the exact same problem with a UK Orange Hero. Have tried for days to get it booting normally on a 2.1 rom with no joy. Any ideas would be great.
Related
First, thanks for taking the time to read this. I appreciate that these forums get a lot of frustrating posts with people asking questions that have already been answered, and it is not my intention to do that. I have been lurking on these forums for a while, and have read around quite a bit of information. However, I cannot find the exact answers I am after.
To start, I am now on my 2nd HTC Magic 32B (Voda UK), after I sent my initial phone off for repair. I was running Cyanogen Mod on this phone, and flashed this rom by fastbooting in to Cyanogen's Recovery and going from there.
I was careful to take a nandroid backup before I flashed, and as such, when the time came to said the phone off for repair, I was able to restore the backup and send it off with the stock firmware running.
Unfortunately, the phone I have now received has a 'perfect' SPL, HBOOT-1.33.0007, so I cannot flash a rom using the same method.
My primary concern through all of this, is finding a way to flash roms such that I can revert everything back to normal if the need arises.
I have read around 1-click rooting, so, my proposed method at the moment would be:
1) use Flashrec to boot into Cyanogen Recovery
2) Backup using nandroid
3) using adb shell to flash Cyanogen Recovery
4) use Cyanogen Recovery to flash rom
I should now be in a position where I can a) flash back to the original recovery if needed, using the backup from nandroid, and b) flash back to the original rom if needed, using the backup from nandroid.
Would this work as I hope?
I have read about having to 'downgrade' the SPL when wishing to restore a nandroid backup, but I did not need to previously. What are the circumstances where you do need to? - I would not want to do this, since I have no way of flashing the original SPL back. I presume there is no way to backup my SPL? so I could return to it if need be?
Thanks for taking the time to read this, and I appreciate any help you may be able to give me.
Cheers.
I have a Rogers 32A that had a Perfect SPL (1.33.0010) on it and I got a rooted recovery ROM by using One Click Root. The Perfect SPL wasn't allowing me to fastboot at all (giving me a "no access" error or something). So instead I booted running the stock software, and used the one click root program to backup my ROM and then flash a recovery ROM (used the default Cyanogen Recovery 1.4). Then when I rebooted while holding down Power + Home, I came right into my rooted recovery ROM where I could install whatever .zip ROM I wanted (AFTER I BACKED UP WITH NANDROID, of course).
I didn't need to use ADB for anything, and I still ended up with root. So I guess I'm confused when you say you're going to use flashrec to boot into cyanogen recovery and then use adb shell to flash cyanogen recovery. I was under the impresion that flashrec FLASHES cyanogen recovery for you, eliminating the need to use ADB/Fastboot. Assumed "flashrec" stood for "Flash Recovery ROM".
My steps were:
1) Install/run flashrec
2) In FlashRec: Backup your current ROM
3) In FlashRec: Select a new recovery ROM to Flash (has Cyanogen's by default, can change to something on your SD Card)
4) In FlashRec: Flash the Recovery ROM
5) Exit FlashRec and reboot into Recovery Mode (Hold Home and Power)
6) You're done, you have a rooted phone. Go ahead and Nandroid a backup, wipe your data, and install a new ROM.
Thanks for your reply.
It is my understanding that flashrec does not flash the recovery rom, but just allows you to boot to it. (Similar to the fastboot boot filename.img command). I would guess that if you reboot your phone using home + power now, that it would boot to the standard recovery.
If it is the case that flashrec does flash the recovery image, then that would be handy, and presumably the backup could be restored using either nandroid or adb.
Thanks, this clarifies that my rooting procedure is along the right lines, however I am still concerned whether flashing everything back to normal will go as I expect.
Just booted into recovery, and its still CyanogenMod v1.4 + JF.
I'm trying to think if I did anything special during my rooting efforts. I don't think I did. I know that I flashrec'd twice. the First was with Amon_Ra's recovery console, and then I did it again a bit later with Cyanogen's. But I'm positive I was never able to successfully use adb's fastboot command due to my perfected SPL.
And you're right, I didn't address your concerns about unrooting at a later date. I assume that is what you're doing when you use flashrec to create a backup of the stock Recovery ROM, but i'm not positive.
Taken from:
http://www.ryebrye.com/blog/2009/08/16/android-rooting-in-1-click-in-progress/
EVERY TIME YOU REBOOT YOUR PHONE INTO NORMAL ANDROID IT UNDOES WHAT YOU JUST DID. Every time android boots, it reflashes the recovery partition with the default one from a file stored in your phone. For safety reasons, we are not replacing this file – just flashing the partition directly. So if you boot to recovery mode, then boot back into your normal mode, and then boot back into recovery mode – you will see a triangle with an exclamation point and only 3 options.
Click to expand...
Click to collapse
So I'm not sure what's going on.
Thanks for your input. I think I'm nearing enough confidence to go ahead and give this a try. Probably tomorrow.
Hi ParanoiaPersonified - can you post an update when you flash? I also have a new Voda Magic with the same SPL as yourself.....I got the OTA upgrade to Donut yesterday which I may have been silly about accepting.
I wasn't too impressed with the speed improvements in Donut and now want to flash something built by one of the XDA chefs, but am having problems rooting with the traditional methods - even 1 click doesn't seem to work....
Cheers.
It is my understanding that one-click-root only works on 1.5, and the exploit that it uses is patched in 1.6. I think you may need to use the 'gold card' method, radita.
I've realised that my handset has a fault (the scrollwheel does not work when scrolling to the right), so I will be unfortunately waiting for a replacement handset before taking any of the steps mentioned above.
Hopefully the replacement does come with 1.6 pre-installed!
"Gold card" method looks a little more involved....guess I don't have a choice though.
Thanks.
in order to remove some of the unwanted bloatware in the stock rom, i deleted some of them and everything is ok till now, after i did a factory rest i realized that removed apps are still removed, dunno why?
i thought that if i did a full wipe then factory reset then i will get back the removed apps.
i installed the full wipe.zip tool, run it in recovery mode, apply factory reset, but now the device is stuck on htc logo with no OS, what is happening, did the full wipe , wipe also the OS? if so, what should i do now, did i bricked my device in anyway?
tell me plz that i have to put the rom on my sd and install it in recovery mode? assuming that i have no sd card reader on my pc, is ther any other way to copy the rom on my sd in the device?
help me plz as i have no phone right now
Give me a few seconds and ill see if i can help you. I suggest you use a world wide edition rom and flash that. You should get a full reset
i want to install this rom
1.32.405.6
http://xdafil.es/DesireHD/RUU/RUU_A....140e_26.03.02.26_M_release_155891_signed.exe
first thing, what does signed means, is it a branded rom?
can i install this rom on my device from my desktop, as it is RUU?
if i cant, then i need it in zip format to install it in recovery mode, right? can you point me to a zip link of this rom?
thank you for your help
run the rom link you have there from your desktop and it should be fine.
do you have clockwork recovery installed?
signed "technically" means that i can be installed with the protection system that HTC has in place and its fine...
It is basically official from the manufacturer as they have a special method they use to "Authenticate" that the software is from them officially
and if that dont work you go into clockwork recovery and mount sdcard in recovery go to mounts and storage > mount usb storage
now you can see sdcard to put files on
as this way you can place a PD98IMG.zip on to sdcard
and flash that zip file from bootloader
here a thread thats tells you how to make a PD98IMG.zip from the RUU file
http://forum.xda-developers.com/showthread.php?t=841890
This is a good example of RTFM!!!
"FULL-WIPE.zip WILL FORMAT EVERYTHING!!
* BOOT
* SYSTEM
* DATA
* CACHE
* DALVIK-CACHE.
***WILL LEAVE SDCARD UNTOUCHED ***"
So basicly, nothing is wrong and your phone has no issues. You just didn't read the manual good
Download this file: http://forum.xda-developers.com/showthread.php?t=866752
Place it on your sd-card.
Boot phone into recovery.
Flash .zip from Sd-card.
Reboot
Your phone is back to life....
@ xmoo
i already downloaded the stock rom posted earlier by you 1.32.405.6
http://xdafil.es/DesireHD/RUU/RUU_Ac...891_signed.exe wich is signed and you are pointing me to unsigned this time, can you please tell me why? and what is the difference?
now i know what full wipe do, but lets say i removed some apps from the stock rom, doing dalvik and cach wipe then factory reset will bring back the removed apps or there is no way to get them back unless a fresh reinstall of the rom?
i installed the signed rom, and while doing HBOOT said, no image or image wrong, is it fine not finding an image?
thank you all for your great helps bringing back my DHD to life
no your apps have gone
and all that unsigned zip will do is rewrite the system and data
just need to follow what xmoo saying an you be all good again
i just installed the signed rom, before i saw xmoo reply and it's working ok, still dunno what is the difference btw signed and unsigned and why xmoo suggested the unsigned.
what thing that i noticed is that i dont get back the sample photos that comes with my device before i delete them.
note:
after flashing Soff still exist
root and CWM should be reinstalled
s-off remained cause of radio s-off.
Cause of you still having access to cmw, thats why I said flash the zip unsigned. This way you don't needed to re-root etc
Also stock pics are deleted, cause they were located on your sd-card.
vuedesprit said:
i just installed the signed rom, before i saw xmoo reply and it's working ok, still dunno what is the difference btw signed and unsigned and why xmoo suggested the unsigned.
what thing that i noticed is that i dont get back the sample photos that comes with my device before i delete them.
note:
after flashing Soff still exist
root and CWM should be reinstalled
Click to expand...
Click to collapse
Sent from my Desire HD using XDA App
Ok so I originally rooted my phone and put Fresh ROM on it, there was a little hiccup in the install but I didnt really think much of it, recently when I tried to flash a new ROM (I tried multiple ones just to be sure it wasn't the rom) but whenever I try to flash the ROM (using clockworkmod from recovery mode) it will say the install was successful but when I reboot it will do one of two things: stay on the "HTC EVO 4G" startup screen or continue to turn off and on like its in a bootloop. Does anyone have any ideas whats happening and what I should do? I have tried clearing/wiping all of the options that are available in clockworkmod and even tried using a new SD Card but it still does the same thing
guribe94 said:
Ok so I originally rooted my phone and put Fresh ROM on it, there was a little hiccup in the install but I didnt really think much of it, recently when I tried to flash a new ROM (I tried multiple ones just to be sure it wasn't the rom) but whenever I try to flash the ROM (using clockworkmod from recovery mode) it will say the install was successful but when I reboot it will do one of two things: stay on the "HTC EVO 4G" startup screen or continue to turn off and on like its in a bootloop. Does anyone have any ideas whats happening and what I should do? I have tried clearing/wiping all of the options that are available in clockworkmod and even tried using a new SD Card but it still does the same thing
Click to expand...
Click to collapse
Hi there. First off, I need a little more info, like which rom you are trying to flash right now. Also, what radio's and pri do you currently have?(menu>settings>about phone>software info, radio is baseband) If you have the older radio and PRI, (same as the ones in my sig), and you are flashing to a 3.70 software ROM, which most likely you are, you will need to either flash a custom kernel, while in recovery, just after flashing the rom (before you boot). Or upgrade your radios. If you have already updated your radios, and you're still experiencing this, I would first and foremost, switch to Amon Ra recovery (which version of clockwork are you on, btw?). The easiest way to switch to Amon Ra, is to get Rom Manager from the market. Use rom manager to "flash clockworkmod reocovery" (even though you already have clockwork, do this) Then scroll down, and you'll see "flash alternate recovery". Select that, and let it flash Amon Ra for you. Shut the phone down, and manually boot into recovery (vol down+power). Use amon's recovery to do a full wipe, (data, cache, davlik cache x3) Then flash calkulin's format all.zip. That will ensure a good wipe. Then follow my above mentioned instructions, and try again. That should work. If it doesn't, report what the exact errors are here. Good luck
Maybe this is a stupid question, but are you able to nand restore to a rom where your phone will actually boot up?
Calkulin format all zip is your best bet. It will wipe your system data, data, cache and dalvik cache. A full purge.
Just have a good zip like chris sprint lovers rom. And better yet a PC36100.zip from chris all in one update thread.
Sent by my eVo running Vin255764 Plutonium...yup
Here's a few suggestion:
Change your radio version - Some kernels don't work right with the newest, and some don't work right with older ones.
Change your kernel - This is always the best suggestion IMO. For a sense based ROM run one of netarchy's latest kernels. Often a bootloop is because of a kernel/radio issue.
Plus with netarchy and setcpu you'll get some wicked battery life.
Try wiping everything, and then try again. Also try flashing a different rom
having issues flashing myn rom
have 3.7 evo rooted unrevoked3/kernel 15
when i try to flash from clockwork mod it just blinks right quick but doesn't do anything.. all the things are up to date .. can anyone help?
when i flashed amon ra and flashed rom.. it says E: can't find update script..
i dl rom manager and did the alt recovery to amon ra. it still won't flash the rom.. but now i have another problem.. my sd card clockwork back up is not there... and now i can't restore to previous state. i can't get to the regular phone interface. what can i do to restore?
Right basically if you've followed my last thread, http://forum.xda-developers.com/showthread.php?p=27975788#post27975788 it turns out I haven't got anywhere really. Today I managed to flash both froyo and GB but after trying to root both and install a custom ROM it would fail and I'd end up in a bootloop. Normally I'd just reinstall the dload files from the SD card and start again. Now however, when I go to boot the dload files, I get pink a screen (with usb plugged in I have the image folder with various files). When I try and boot recovery, nothing happens, I've tried replacing the recovery image, but no success. So now I'm left with a phone that does pretty much nothing other than bootloop or turn pink on command. Any suggestions on what I can do to install froyo or GB?
Sorry and thanks again.
Before root the rom(s) run ok?
And how you root the device? Also are you sure that the root have success? How you check it?
The root was fine, followed the instructions from the thread in dev section, ran the one click root everything was fine, swapped the recovery to get v5 used remount and astro explorer. went to CWM, made sure i had a rom that ran with the kernel, installed it everything said it was fine reboot into a loop. my options now are boot loop or pink screen, it wont even pick up the dload from the sd card.
So the bootloop happen with the custom rom you flashed from recovery mode?
Which rom you flashed? Did you wipe data/cache/dalvic_cache before the reboot?
Indeed I did. Something corrupted in the image folder. So I found a custom Image folder by the guy who's developed the v5.5 of CWM. In his signature theres a load of zip files one of them had a custom Image folder which Ive swapped in to which the phone has read the dload files now finally. Im hoping this will work.
If the device boots fine with the official roms, and bootloops with the custom, there is nothing wrong with the image file. The problem is with the rom that you try to flash and maybe with the recovery version.
For whatever reason ive tried multiple roms today none of which have booted, the closest i came was the oxygen rom but that failed at the oxygen splash screen. As for my problem, something had happened after i flash a rom, no idea what but a file in the image folder had gone bad. after swapping that out for one i found, dload from the SD card booted and installed. I now have a stock GB running which i think i'll leave it at that. i'm clearly missing something when i flash a custom rom whether it be bootloader related or a incompatible rom to kernel. either way now it works, i'll leave it as is. Thanks for the help though much appreciated. I'm hoping other will find the help they need here.
Dave759 said:
For whatever reason ive tried multiple roms today none of which have booted, the closest i came was the oxygen rom but that failed at the oxygen splash screen. As for my problem, something had happened after i flash a rom, no idea what but a file in the image folder had gone bad. after swapping that out for one i found, dload from the SD card booted and installed. I now have a stock GB running which i think i'll leave it at that. i'm clearly missing something when i flash a custom rom whether it be bootloader related or a incompatible rom to kernel. either way now it works, i'll leave it as is. Thanks for the help though much appreciated. I'm hoping other will find the help they need here.
Click to expand...
Click to collapse
The only cases I can think a custom ROM won't work are
- installing a .32 ROM over a ROM based on .35 and vice versa
- installing a custom ROM without wiping data and caches of the previous ROM, especially if they are not related, like not different builds of the same ROM
- installing a .32 ROM using cwm other than 5.0.2.6 and below
- installing a .35 or ics ROM using a cwm other than 5.5.0.4 or 5.0.2.7
Are you sure you did none of that?
Sent from my U8800
Hey all.
Hope I am in the correct forum section.
I am having difficulty with flashing a custom rom and was hoping for some direction.
Can someone please confirm i am in the correct forum section I will give details of what has happened, what I have tried in my next post.
No1Daemon said:
Hey all.
Hope I am in the correct forum section.
I am having difficulty with flashing a custom rom and was hoping for some direction.
Can someone please confirm i am in the correct forum section I will give details of what has happened, what I have tried in my next post.
Click to expand...
Click to collapse
Device/Phone model number?
Any samsung bootllop can be solved here though
"If someone helps, never forget to hit thanks ? "
Thanks for the reply
Some details then
Model is Samsung S4 GT-I9505
I rushed into booting and selected an aokp rom and then selected the latest apps file for it and got stuck in an endless boot loop.
I am now trying to install a GPE Rom
gpe-rom-for-galaxy-s4-android-4-4-4
I am still able to get into recovery and download mode.
I flashed philz_touch_6.15.6-jflte.tar.md5 using odin3 on windows then rebooted into recovery and did a clean up for new rom and factory reset then attempted to move the rom onto my phone and thats where I have run into trouble. I am trying to use adb to push the file into it because I seem to have somehow wiped the sdcard(i.e. in phil recovery under mounts and storage there is no /sdcard to mount or unmount.
Thins I tried:
Using a micro sd card and copying the file to it and inserting it in the phone and installing from /sdcard1 but it just aborts the install and gives me a failed error
I tried to push the file with adb by opening terminal cd to downloads where the rom is located and used
Code:
adb push rom.zip /data/media/0 rom.zip
but this never completes. it is supposed to return the size of the files but nothing happens. I know adb can see the phone as when I type adb devices I get back a response saying recovery
Can anyone give me any pointers or advice. Happy to start from scratch but so far every tutorial/discussion on installing roms etc i have followed has failed.
Incidentally I do not have a backup because I thought I made one successfully when I fist rooted but when I went to restore it it gave me a md5 hash invalid error
Thanks
Have you tried a different recovery? You can try TWRP 2.8.1.0 and see how it goes. Just us odin to flash the recovery and use a usb card reader to put the rom onto the SD Card. To be safe you can also try a different rom, if you are after a GPE rom, I recommend Dan's GPE rom.
http://forum.xda-developers.com/showthread.php?t=2557353
That is one of the roms I was hoping to install before I successfully flashed it back to stock.
Will look into it.
I couldn't use a card reader to put the rom on because I was having difficulty reading the external sd card in recovery.
I tried many different recoveries. TWRP, CMR and Philz but had no luck with any of them.
Do you know if all packages get made into a complete rom to install with Odin? like I did with my stock rom?
Just seemed an easier way to install it.
My english is very bad.
Your back Stock Rom with Odín download firmware SamMobile.
Custom, download custom again its possible corrupt download, wipe data, system, caché, Factory reset.
You have use one recovery or not installing previous backup for MD5 Missmatch
Format SD in the phone.
Proccess very slow with Odín install Stock Rom, root, recovery, install custom
Try with recovery using for previous backup for restore backup.
Mi inglés es muy malo, en inglés no te lo puedo explicar mejor.
No1Daemon said:
That is one of the roms I was hoping to install before I successfully flashed it back to stock.
Will look into it.
I couldn't use a card reader to put the rom on because I was having difficulty reading the external sd card in recovery.
I tried many different recoveries. TWRP, CMR and Philz but had no luck with any of them.
Do you know if all packages get made into a complete rom to install with Odin? like I did with my stock rom?
Just seemed an easier way to install it.
Click to expand...
Click to collapse
Dont flash a custom rom on an already bootlooped phone.
Either flash your stock rom or you can restore a backup via recovery.
Then start experimenting again..as flashing and more flashing and more more flashing on a bootloop can cause a few things to go crazy.
It is not recommended. But then your choice. Its not a big task of coming to a stock firmware then continuing with things...
"If someone helps, never forget to hit thanks ? "
DeepankarS said:
Its not a big task of coming to a stock firmware then continuing with things...
Click to expand...
Click to collapse
I found it a big task and I am used to this sort of thing. I got there eventually but thanks for the advice. Will keep that in mind in case I get stuck in a boot loop again.
Will pay more attention to backups etc when I flash the next one.
No1Daemon said:
I found it a big task and I am used to this sort of thing. I got there eventually but thanks for the advice. Will keep that in mind in case I get stuck in a boot loop again.
Will pay more attention to backups etc when I flash the next one.
Click to expand...
Click to collapse
No generally what happens it people skip things while being hyper relating to flashing.
Basics are never to be left out. When adb terminals and things weren't there, the tedious processes were used to recover.
(flash stock..flash recovery..flash things then when you're in a boot loop if factory reset doesn't work)
And you should always have a backup+updated stock firmware handy.
If either doesn't work for you always have a support
"If someone helps, never forget to hit thanks ? "