Ok...Problem...
I was following forum.xda-developers.com/showthread.php?t=672992, Cyanogen's thread to install 5.0.7-DS-test1. I had the latest CM stable build before.
Since it was my first time flashing the CM5 I followed step 3 in the installation post and jumped to wiki.cyanogenmod.com/index.php/DangerSPL, the installation of DangerSPL. I followed the instruction, downloaded and fastbooted the G1-radio-2_22_23_02 (fastboot flash radio radio.img) with my Magic in Fastboot (back+power). It was loaded to the Magic ok, installed ok.
Rebooted the device to begin to install CM5-, GAPPS- and 32A-kernelzips in recovery mode... But I only got the htc magic-logo (home+power).
Fastboot (back+power) works, but my computer can't connect to my device via adb/fastboot (error:device not found).
On screen:
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.33.2005 (SAPP10000)
CPLD-12
RADIO-2.22.23.02
If I start normally (power) I get the htc magic-logo and a red box in the upper left corner of the screen saying "FASTBOOT USB". Nothing else happens...
I tried to flash the DangerSPL by just powering up the device getting "htc magic" and red box. From console (fastbbot boot hboot.img) loaded ok (white vertical "load"-bar in right screen corner), but then I get "booting... FAILED (remote: reproduce boot image with on-flash ramdisk error)" in the console?!?!
HELP! Is it a brick? Then I have to cry...my magic...
Hi i have just tried to flash amons new 1.7.0 recovery image from terminal amd got, read error at 0×0000000 out of memory. so then i exited terminal then tried to reboot into recovery with no success it just hanged on the g1 logo? but im able to reboot my phone normally? please can anybody help me
Sent from my HTC Dream using Tapatalk
if you can reboot your phone normally try doing it in the terminal emulator.
Code:
Copy recovery-RA-dream-v1.7.0.img to the root of your sdcard
start the terminal app
#flash_image recovery /sdcard/recovery-RA-dream-v1.7.0.img
Make sure you are root when you run this command.
But don't do this if your running Cyanogen 5.0.7. If your running Cyanogen you'll have to do the fasboot method.
Code:
Copy recovery-RA-dream-v1.7.0.img to a location where fastboot can find it.
Boot your G1 into fastboot mode (boot while holding BACK)
Connect your G1 via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.7.0.img
This is the same code for all versions on RA. Just change RA-dream-v1.7.0.img, to whatever image file you have for your specific phone.
thanks for the quick reply ill try it when i get home thanks again!
Sent from my HTC Dream using Tapatalk
thanks for ur help i have done it through droid installer, mods close this thread please
Sent from my HTC Dream using Tapatalk
kylepotts said:
Code:
Copy recovery-RA-dream-v1.7.0.img to a location where fastboot can find it.
Boot your G1 into fastboot mode (boot while holding BACK)
Connect your G1 via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.7.0.img
This is the same code for all versions on RA. Just change RA-dream-v1.7.0.img, to whatever image file you have for your specific phone.
Click to expand...
Click to collapse
I have recently changed the SPL to version 1.33.2010 as well as the RECOVERY to RA-sapphire.v1.7.0 in my Magic following the procedure above but, although the flash command seems to finish properly and I can reboot into the new recovery just after the update, when I boot completely the phone (load Android) and reboot into recovery again, something changes the recovery version back to the original one (Android 2e), while the SPL is correct.
Do you have any idea of what may be happening?
This is the original config I had:
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.2004 (SAPP10000)
CPLD-10
RADIO-2.22.19.26I
And this is the current one:
SAPPHIRE PVT 32B ENG S-OFF H
HBOOT-1.33.2010 (SAPP10000)
CPLD-10
RADIO-2.22.19.26I
Jun 2 2009, 17:27:03
Thank you.
Phone Info:
Sapphire PVT 32b SHIP s-on G
HBOOT-1.33.0006 (sapp30000)
cpld-10
radio-2.22.23.02
May 27 2009,19:06:41
History:
So I deleted at least one to0 many applications and now the phone will not boot to the OS. It freezes then restarts during the boot process.
I cannot get into the recovery mode with home+power. It just sits with the green myTouch logo until I give up holding it and it then tries to boot.
I can press back+home and get to the FASTBOOT screen.
Help:
Where exactly do I go from here? I cannot find my gold card and have no way of making one right now.
Thanks!
Anyone have any thoughts or know what files I need to work with fastboot?
Hello
Install first HTC Sync for Drivers (here). (if nothing works, go to pc -> device manager -> right click unknown device and uninstall. than install again.
After this try start your device with hold back+power button.
Go to cmd and write
1. cd C:\androidsdk\tools
2. fastboot devices
if you see your fastboot device than you can remote boot a recovery file. Get recovery here.
3. fastboot boot recovery.img
than restore your nandroid backup or install your rom.
i had exact same problem 1 hour ago and i solved it with this
hope it helps.
I'm trying to put 2 ROMS on an Desire S, but i get stuck. (separately from eachother)
I have the following:
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.02.0002
RADIO-3831.19.00.110
eMMC-boot
Jul 31 2012, 15:41:32
4EXT Recovery v2.2.7 RC5
Made an backup and this works in recovery.
I tried to install the following ROMS
- CM-10.1-20130808-signed.zip
- saga_PAC_JB_4.2.2-v23.0.0_20130706-232137.zip
and
gapps-jb-20130301.zip
I have wiped data/factory reset, cache, dalvik cache, battery stats.
then Install from sdcard.
CM-10.1-20130808-signed.zip
gapps-jb-20130301.zip
4EXT says installation has been completed
I reboot the phone and the screen gives first the white HTC boot screen and then there is an black screen and it 'll not proceed in the booting proces.
Am i doing something wrong? (I guess so but i don't know what the problem is) I have read several rooting guides on XDA but am a bit lost in the information.:silly:
Can somobody give me an helping hand.
Many thanks
ur S-ON and not S-OFF so u must do this:
1 open the rom.zip in your pc
2 extract the boot.img
3 put the boot.img in the folder where u have the fastboot.exe
4 in this folder hold shift button on the pc keybord and right click on the mouse and select "run windows command here"
5 put your phone in fastboot mode and connect into your pc
6 in the command line opened at point 4 write
" fastboot erase cache " and do the command.
now write
"fastboot flash boot boot.img " and do the command
this must be done everytime u change rom (otherwise u can s-off your device -> search in general topic)
Thx, i'll try this tommorow.
Send from GT-I9300 with Tapatalk
It works.
Thank you very much, it works like a charm.
Edit: solution to the problem in post #4
I have accidentally replaced my boot.img with fastboot - now the phone is stuck in a boot loop/freeze
the bootloader is unlocked
it is S-ON
it is an unlocked (not branded phone)
running twrp 2.6.0.0
both adb and fastboot appear to work
the phone is not rooted (that was where the problem started...)
I have access to hboot and recovery, but that is it
I have erased everything (cache, system, dalvik, sd) several times and tried a number of suggestions found on other threads describing similar problems.
I can't get access to the SD card from a PC, and fastboot flash or adb push both fail to transfer a stock RUU (JmzM4StockRootedDeOdex-WWE-1.22.401.1.zip) to the phone.
I have replace the kernel (and flashed the appropriate boot.img with it) to get out of the boot loop.
Any suggestion would be greatly appreciated! gettting desperate now...
Thanks, K
----------
the recovery screen reads:
***TAMPERED***
***UNLOCKED***
M4_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.22.40e.00.07
OpenDSP-v15.2.0268.0819
OS-1.40.401.1
eMMC-boot 1024MB
ilchkai said:
I have accidentally replaced my boot.img with fastboot - now the phone is stuck in a boot loop/freeze
the bootloader is unlocked
it is S-ON
it is an unlocked (not branded phone)
running twrp 2.6.0.0
both adb and fastboot appear to work
the phone is not rooted (that was where the problem started...)
I have access to hboot and recovery, but that is it
I have erased everything (cache, system, dalvik, sd) several times and tried a number of suggestions found on other threads describing similar problems.
I can't get access to the SD card from a PC, and fastboot flash or adb push both fail to transfer a stock RUU (JmzM4StockRootedDeOdex-WWE-1.22.401.1.zip) to the phone.
I have replace the kernel (and flashed the appropriate boot.img with it) to get out of the boot loop.
Any suggestion would be greatly appreciated! gettting desperate now...
Thanks, K
----------
the recovery screen reads:
***TAMPERED***
***UNLOCKED***
M4_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.22.40e.00.07
OpenDSP-v15.2.0268.0819
OS-1.40.401.1
eMMC-boot 1024MB
Click to expand...
Click to collapse
Hi! If you still need help, PM me and we'll get it sorted, no problem.....
nelvinchi said:
Hi! If you still need help, PM me and we'll get it sorted, no problem.....
Click to expand...
Click to collapse
excellent - thanks, pm sent
Here is the solution to the above problem, no guarantees – just thought I share it here if anyone else is in the same predicament… I was walked through this by nelvinchi - many thanks for that !!!!
(n.b. I can't post urls yet as I am a noobie here, so that you will need to find the required files in the forum somewhere - maybe someone can leave links to the appropriate files in a post below)
Required files:
1. ABD (get the smaller version from the forum)
-> download this and extract to a folder called c:\adb\
2. Updated Super SU "UPDATE-SuperSU-v1.86.zip"
3. Rom (Stock2.12.401.1Deodex(tr1gg3r84).zip)
-> SuperSU and Rom, into the same folder as above (c:\adb\)
(4. TeamWinRecoveryProject recovery, here version 2.6.0.0)
Procedure:
[NB.: I had access to bootloader (unlocked) & recovery (twrp 2.6.0.0); the phone was S-ON]
Open a command prompt from the folder (shift+right click somewhere in the window and choose “open command window here”, or WIN+R and enter cmd and press enter and navigate to the folder where the files and adb are located)
Boot phone to recovery
Go to the mount menu, check system and data [data was not selectable, thus I had to: Go to wipe menu, Format data, Type yes, after that reboot to recovery, and mount menu, check system and data…]
Back to main menu
Plug your phone into computer (mine was plugged in all along, so no worries)
In the cmd prompt (on PC) type: adb devices [phone should be found and indicated by the serial number and the status, in this case it should say recovery after the number – proceed if phone is found]
Type: adb push Stock2.12.401.1Deodex(tr1gg3r84).zip /sdcard/
[there is no indication of progress when pushing, just be patient – it will take a few minutes. And, just in case – if you need to interrupt/cancel the push process it can be done with Ctrl+c]
Type: adb push UPDATE-SuperSU-v1.86.zip /sdcard/
On the phone, in recovery, Go to install
Choose the NEW rom (Stock2.12.401.1Deodex(tr1gg3r84).zip)
Choose add more zips and add the SuperSU zip
Confirm flash
When done, DON'T reboot, go back, reboot menu, reboot recovery
On the PC, open the ROM zip, and extract boot.img to the folder (c:\adb\) [this will need you to have 7zip or Winrar or similar installed on your computer]
Reboot menu and select Reboot bootloader
Select fastboot (fastboot should be indicated by fastboot USB)
On the PC type fastboot flash boot boot.img
Choose bootloader, then recovery
In recovery: Go to wipe, Advanced wipe, Check cache and dalvik, and wipe!
Go to Reboot menu, and Reboot system
Now, don't panic – it will take some time to do its thing… the phone should be fine after that and normal setup process should start.
!!! Massive thanks to nelvinchi, who walked me through this process!!!
Links
A little late, but:
SuperSU: http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip?retrieve_file=1
Stock Flashable zip: https://mega.co.nz/#!8d0jhQTS!N2V5KTty4spxzNOwU-43vzqd3BF_ektVbH_TuHec26c
TWRP: http://forum.xda-developers.com/showthread.php?t=2418938
ADB: http://forum.xda-developers.com/showthread.php?p=42407269 (i think you ment this one, right?)
Yaaay, fixed my mini. Thx for these instructions!
:laugh:
ilchkai said:
Here is the solution to the above problem, no guarantees – just thought I share it here if anyone else is in the same predicament… I was walked through this by nelvinchi - many thanks for that !!!!
(n.b. I can't post urls yet as I am a noobie here, so that you will need to find the required files in the forum somewhere - maybe someone can leave links to the appropriate files in a post below)
Required files:
1. ABD (get the smaller version from the forum)
-> download this and extract to a folder called c:\adb\
2. Updated Super SU "UPDATE-SuperSU-v1.86.zip"
3. Rom (Stock2.12.401.1Deodex(tr1gg3r84).zip)
-> SuperSU and Rom, into the same folder as above (c:\adb\)
(4. TeamWinRecoveryProject recovery, here version 2.6.0.0)
Procedure:
[NB.: I had access to bootloader (unlocked) & recovery (twrp 2.6.0.0); the phone was S-ON]
Open a command prompt from the folder (shift+right click somewhere in the window and choose “open command window here”, or WIN+R and enter cmd and press enter and navigate to the folder where the files and adb are located)
Boot phone to recovery
Go to the mount menu, check system and data [data was not selectable, thus I had to: Go to wipe menu, Format data, Type yes, after that reboot to recovery, and mount menu, check system and data…]
Back to main menu
Plug your phone into computer (mine was plugged in all along, so no worries)
In the cmd prompt (on PC) type: adb devices [phone should be found and indicated by the serial number and the status, in this case it should say recovery after the number – proceed if phone is found]
Type: adb push Stock2.12.401.1Deodex(tr1gg3r84).zip /sdcard/
[there is no indication of progress when pushing, just be patient – it will take a few minutes. And, just in case – if you need to interrupt/cancel the push process it can be done with Ctrl+c]
Type: adb push UPDATE-SuperSU-v1.86.zip /sdcard/
On the phone, in recovery, Go to install
Choose the NEW rom (Stock2.12.401.1Deodex(tr1gg3r84).zip)
Choose add more zips and add the SuperSU zip
Confirm flash
When done, DON'T reboot, go back, reboot menu, reboot recovery
On the PC, open the ROM zip, and extract boot.img to the folder (c:\adb\) [this will need you to have 7zip or Winrar or similar installed on your computer]
Reboot menu and select Reboot bootloader
Select fastboot (fastboot should be indicated by fastboot USB)
On the PC type fastboot flash boot boot.img
Choose bootloader, then recovery
In recovery: Go to wipe, Advanced wipe, Check cache and dalvik, and wipe!
Go to Reboot menu, and Reboot system
Now, don't panic – it will take some time to do its thing… the phone should be fine after that and normal setup process should start.
!!! Massive thanks to nelvinchi, who walked me through this process!!!
Click to expand...
Click to collapse
I followed these instrutions to a T but im still getting boot loopat the HTC screen
I am Unlocked bootloader
S-Off
cid-CWS__001
hboot 2.19.0000
radio 1.19.40d.00.14
any suggestion?
please help
romy134 said:
I followed these instrutions to a T but im still getting boot loopat the HTC screen
I am Unlocked bootloader
S-Off
cid-CWS__001
hboot 2.19.0000
radio 1.19.40d.00.14
any suggestion?
Click to expand...
Click to collapse
I'm having the same problem.
I've followed those instructions over and over with different roms but TWRP always tells me that there is no OS installed when I do the final reboot. I am stuck at the white HTC screen and can't get any rom to load up. Please help.
This is what my bootloader says:
--TAMPERED--
--UNLOCKED--
M4_UL PVT SHIP S-ON RL
HBOOT-2.22.0000
RADIO-1.25.40G.00.19
OPENDSP-V19.2.0268.0927
OS-3.10.502.3
eMMC-boot 1024mb
I can flash recoveries and boot.img. ADB works to push roms into /sdcard/, can also sideload. I'm suspecting my filesystem/ partition data is all screwed but but can't figure out why Roms won't load.
I got the phone yesterday and it was untouched, stock. I tried to follow this guide (http://forum.xda-developers.com/showthread.php?t=2789272) to get it rooted and install a custom rom. I got stuck at getting S-OFF. rumrunner was giving me the "Fatal: download latest package" error. I also could not get su in the shell to try firewater. At this point I was reading that people had luck getting S-OFF after installing JmzM4StockRootedOdex-WWE-1.22.401.1 custom rom and kernel. I tried to do that but I wasn't sure what I was doing and ended up with no OS and a bootloop at the white HTC screen. I have a bit of Android experience from messing with the HP touchpad tablet but I'm rusty and this phone has me beat right now.
Thanks for your help.
...
try replacing TWRP with an older version (mine was 2.6.0.0) and reset/clear/delete/format everything from there and restart the process outlined above
and apparently S-Off is pointless and very risky on this model, there is no reason to do it - it will just cause problems
good luck and I hope some else who has actual knowledge about this will get back to you
ilchkai said:
try replacing TWRP with an older version (mine was 2.6.0.0) and reset/clear/delete/format everything from there and restart the process outlined above
and apparently S-Off is pointless and very risky on this model, there is no reason to do it - it will just cause problems
good luck and I hope some else who has actual knowledge about this will get back to you
Click to expand...
Click to collapse
Thanks.. I've been using TWRP 2.7.1.0 because I read that I have the newer partion scheme with HBOOT 2.22 but I'm not really sure.
When I try TWRP 2.7.1.1 ADB doesn't work and I get a different /sdcard/ than in 2.7.1.0. Not sure what's going on there either.
The only reason I tried S-off is because I blindly followed that guide on how to get the HTC one mini up to date and that was the 2nd step. I should have skipped it and paid more attention to the custom rom flashing aspect.
I'll try TWRP 2.6.0.0 as I don't have many other options at this point.. I also tried to use CWM recovery but it couldnt flash a rom either.
Thanks for your input.