Hi all just wondering if anyone could help me out I used to have root but after flashing a pulse rom I then used my backup to go back to super d then my phone wouldn't recognise my sdcard tried formatting wiping and still no luck so went back to rc7 using dreaimg.nbh I then tried rerooting but when I open up recovery I get e: can't read misc no memory left on device e:can't open cache/recovery/command I tried flashing new radio and spl but it just stays the same. Any help to get me rooted would be appreciated thanks adam
I have no idea what you did. Are you using rc7 on a non-rooted US device? That may be your problem. I believe RC29 is the US firmware with the security exploit.
Also, if you can get past the splash screens... is your device memory full? Can you clear cashes/app data? (I.E, have you tried a wipe?)
hi im from the uk so using rc7 when i open recovery i get e: cant read misc (no space left on device) e: cant read misc (no space left on device) e: cant read misc (no space left on device) it says this three times then i try to flash radio and spl these flash then it says^^^ after flashing. then if i boot into bootloader i still have hboot 0.95.000 and radio 1.22.12.29 so it doesnt seem to be flashing. then if i try and flash a rom it sticks on the g1 screen plz help
Bump still need this
think i no the problem now after hours of searching the misc partition is missin apparently i need to flash a misc.img could anyone provide a misc.img as i cant seem to find one thanks
Related
I was running cyanogen 4.0.1 and I tried to switch to the dudes cupcake rom and when I imaged the phone it said update complete but no matter what rom I image it always gets stuck on the G1 loading screen. Any ideas how to fix it?
Have you wiped?
Have you tried to restore a nandroid backup?
ffff00 said:
Have you wiped?
Have you tried to restore a nandroid backup?
Click to expand...
Click to collapse
most likely a wiping issue
wipe it, if that doesn't solve it, then hopefully you made a backup. not really all that urgent if you had searched.
#1 rule when apply new roms -> always wipe!
#2 rule, check to make sure your spl is the one required by the rom.
shaolinx said:
#1 rule when apply new roms -> always wipe!
#2 rule, check to make sure your spl is the one required by the rom.
Click to expand...
Click to collapse
#2 i do not think would matter because if he does not have the correct spl the rom will not flash. i had that happen with hero on someone elses phone where i thought i had flashed the new spl but instead of home and back to reboot i did reboot recovery from console so it wasn't writing the spl, and when i tried to flash hero it would not flash.
Wipe it.
Flash the dude's cupcake(as you said).
Personalize your phone how you like it.
Make a nandroid backup in case this happens again.
If it happens again, restore.
You'll be back to the exact same state as before.
Ok so I tried doing that for hours and it didnt work, but I finally got it to work by flashing the dreaming.nbh file. Then I turned retarded after I jailed broke my phone I tried to install the CM 3.6.8.1 and screwed my phone again..... I think I needed to flash the ota radio before I tryed to jump ahead. I tryed image the dreaming file again and it installs but I get stuck on the red blue and green screen and ideas.... I will donate..... please help!!!
before you completely fubar it, I would just start from scratch.
Unroot: http://forum.xda-developers.com/showthread.php?t=491350
only a couple steps to get you back to an original safe firmware
then root, recovery, radio, spl, etc
Go slow this time, it will save you time in the end!
ok what is the splash screen is that the red green and blue and when i connect my usb what do I have to get to to type fasboot erase splash2?
dont worry about erasing the splash2, that is just a cosmetic thing (in case you are sending in your phone under warranty). Just skip over it.
Ok I am at work right now but I will try it in the morning thanks for the help can I donate to your paypal or sumthing?
no need for that, just give back to the community when you master this stuff...there will always be others in need of help!
Thank you so much for the help. ok I just tryed to flash the original slp on to my G1 but I keep gettin and error message saying
E: no signature (5 files)
E: verification failed
what do I do now?
i sent you a PM, not sure if it will help but worth a try
ok I tried it and got the same error message......
I tried flashing about 8 different rom in hope one would work but all give me the same error message the dreaming.nbh file does update but when I hit the action button I just get the rainbow screen if i take the battery out and try to power on I get the same screen sometime the dreaming.nbh file doesnt flash and I get a error on system:fail so any ideas I looked on the forums and it seemed that a couple of people had the same problem but none of them got it fixed to what I could see......
OK on the rainbow screen I get
Drea100 PVT 32b
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
SEP 2 2008
SERIAL0
if that at all to know
That is odd, usually after pulling out the battery or giving it the 3 finger salute it will go to the g1 screen and eventually boot up...if it never does you must have more wrong than just the flash. Might be time to send it to tmobile or htc (I recommend htc, they are awesome to deal with unlike tmobile).
I'm trying to fix my friends G1, I hold the camera button and power button and only get into the hard reset screen.
I've tried ALT + L and wipe date/factory reset then reboot system now and nothing. All I can get is that hard reset screen.
Also in the system recovery at the bottom it says E: Cant open /cache/recovery/command.
Any ideas? I wanna try to get this thing up and working again. It's bone stock, never got rooted or changed in any way.
nbturbos said:
I'm trying to fix my friends G1, I hold the camera button and power button and only get into the hard reset screen.
I've tried ALT + L and wipe date/factory reset then reboot system now and nothing. All I can get is that hard reset screen.
Also in the system recovery at the bottom it says E: Cant open /cache/recovery/command.
Any ideas? I wanna try to get this thing up and working again. It's bone stock, never got rooted or changed in any way.
Click to expand...
Click to collapse
I would try loading the original DREAIMG.nbh file onto the sdcard and then try the bootloader option and see if the presence of the nbh file "forces" it to go into bootloader....
Otherwise, I'm pretty stumped...
I've just got a similar problem.
The ONLY thing I can do is entering the Android System recovery (2e) menu.
If I try powering off the phone and:
-Holding home = android system recovery with the reboot system now, apply sdcard:update.zip wipe data/factory reset and wipe cache partition options.
-holding camera = same thing.
It seems like whatever I try with the little android experience I have and reding on forums high and low, I cannot get ADB working, it doesn't list my device OR connect using adb devices and adb shell.
When trying fastboot It's just waiting for device.
If I try installing from sdcard with the alt-s option it either says verification error (custom roms) or with the signed OTA/original roms it starts/stops like this:
E:Can't open /cache/recovery/command
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Installation aborted.
This is VERY frustrating for me since I have NO idea what version is on it, the 1.5 or 1.6 original rom or some custom rom.
It seems like it's a "standard" rom onboard, but since I cannot get pass the "!" screen whatsoever, ADB doesn't work and fastboot is just waiting for better weather or something, I cannot verify ANYTHING.
I also have a Hero wich is flawless with ANY rom I trow at it, recovery image and radio.
So Any ideas on how to fix this ?
Heh, I really hope there is someone out there that REALLY can help me with this.
Thank you
bump ? someone ???
anyone ?
Plz come up with a solution, I've read and read, but nothing......
btw. I don't like the S.E. k850 !!!
hello
what happened to the phone in the end ? have you managed to unbrick it ?
If holding camera button while powering on gets you to recovery chances are your home button is stuck
Sent from my HTC Vision using xda premium
simple camera + power
any way to fix a hard brick? no bootloader, no recovery...just the g1 screen lol i flashed a spl before radio and it killed it
sure, if you jtag it!
other than that.... nothing
Damn! LOL meh,it had a good life. Time to move on to newer phones.
Sent from my Incredible using XDA
Hi everyone,
My N1 is stuck on the X, but my problem seems to be different to the other "my nexus is stuck on X" threads, as I've tried everything that was suggested and am still stuck...here is as much info as I can give.
My phone is rooted (has been since day 1 when it first came out) but I had not used it in a while.
The last rom I had on there was Cyangenmod 5.0.5 (or something like that.)
I booted into recovery (amon_ra from back in the days) and tried to flash Cyanogenmod 7.
The phone booted up, got passed the X but got stuck on the android on the CM circle with the rotating arrow...only the arrow was not rotating.
Anyway, I went back into recovery, and tried again...same thing...so I tried 5.0.5 and that worked.
Happy with my success I tried to install clockwork and try again...
this time, the phone got stuck on X...
tried going back to 5.0.5 but again, phone stuck on X.
So I tried to go back to stock.
fastboot flash boot boot.img and user data.img worked fine but system would fail.
I tried the PASSIMG.zip, but 7) system was fail-PU
read some more and some people said that with hboot 0.35 this was not possible, so I managed to downgrade to 0.33, but that didn't help either.
I've tried Clockwork and Amon
older roms and newer ones
PASSIMG.zip from different sources...nothing has worked.
In hboot now i have 0.35 and underneath I have a B (which I think is for amolded)
I've can't seem to get ADB to work either...I have done in the past, but for some reason this is not working for me this time...fastboot yes.
Could anyone PLEASE help me...
Thanks,
Lou
Fail-PU means Failed Partition Update, means your internal memory on /system partition couldn't be written, means a dead NAND, means your phone is really bad.
You could try to recover from it by using Blackrose hboot, and repartitioning the device.
Blackrose it is...I'll try that..thanks
L
So I got blackrose on, but that didn't help...still the same thing...
I've given up on the phone, but I'd still like to solve this, now that I've devoted som much time into it
L
You don't need to just load Blackrose, it won't solve a thing. You need to repartition your phone, making sure that the /system partition isn't sitting on the bad block. Try to move /system partition forward, making /data smaller.
I partitioned it as per the blackrose thread...are you saying i should use different values? could you recommend some to try?
L
I can't, because I don't know where the failure might be on the /system partition.
Try to change values between /system and /data, for example (move /system into /data). Just for testing. You'll need to find some position for it that won't cause write failures, and there's nothing I can suggest but to try and see at what address the failure seems to be, and repartition in such way as to exclude this address.
Phone stats -
rooted
s-off jopunutbear (however you spell that)
CWM Based Recovery v5.5.0.4
3500 mah battery
Symptoms-
Phone died, so I had my girlfriend put it on the charger, tried to turn the phone back on and it now stays on the white HTC screen. So I entered recovery mode to try and wipe the normal, cache, dalvik, etc... Tried rebooting, nothing. So I then tried a factory reset, still no luck. So I tried a Recovery which wont take, and is now completely missing. As soon as I go into recovery I'm getting the following errors:
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
So I checked the mounts, and I cannot mount the following:
/data
/system
/sd-ext
/cache
/emmc
I then tried installing a custom Kernel/ROM thinking it would possibly replace or fix the problem. Well, no such luck. If someone could please help, I would sincerely appreciate it. BTW, I'm using Ubuntu Linux, so windows tools are probably not going to work.
Can the phone get into hboot ?
Bigtjmc said:
Can the phone get into hboot ?
Click to expand...
Click to collapse
H-Boot and Recovery Yes
You need to relock the boot loader and run the stock ics ruu , if I remember right you never want to do a factory reset on a custom rom
Bigtjmc said:
You need to relock the boot loader and run the stock ics ruu , if I remember right you never want to do a factory reset on a custom rom
Click to expand...
Click to collapse
well, the rom wasnt custom, it was the stock rom. and how do I install an ruu on Linux?
I think it applies to custom recoveries as well, I'm.not sure is check out HTC's web site for that info , I will.check and see if I can.find that out also
Try using the ph9 update zip. Find it though because I tried looking for it but no look
Sent from my SCH-I905 using xda premium
xxjr89xx said:
Phone stats -
rooted
s-off jopunutbear (however you spell that)
CWM Based Recovery v5.5.0.4
3500 mah battery
Symptoms-
Phone died, so I had my girlfriend put it on the charger, tried to turn the phone back on and it now stays on the white HTC screen. So I entered recovery mode to try and wipe the normal, cache, dalvik, etc... Tried rebooting, nothing. So I then tried a factory reset, still no luck. So I tried a Recovery which wont take, and is now completely missing. As soon as I go into recovery I'm getting the following errors:
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: can't mount /cache/recovery/last_log
E: can't open /cache/recovery/last_log
So I checked the mounts, and I cannot mount the following:
/data
/system
/sd-ext
/cache
/emmc
I then tried installing a custom Kernel/ROM thinking it would possibly replace or fix the problem. Well, no such luck. If someone could please help, I would sincerely appreciate it. BTW, I'm using Ubuntu Linux, so windows tools are probably not going to work.
Click to expand...
Click to collapse
What you have to do is re s-on and relock your bootloader then download the HTC ruu and run it.. a guide is available to re s-on your device I think
Sent from my HTC PH39100 using xda app-developers app
Got same problem
I have the same problem too and haven't had time to fix it.
Will be glad to get help here.
INFO: I use windows and tried installing RUU via windows and it keeps telling me battery is less than 30%.
Hello,
SO it started when i used cyanogenmod installer app and windows app combined to easily install CNM. After half a year of using my phone suddenly stopped charging, when i wanted it to charge i needed to shut it down and press volume down combined with power button shortly, not to power it on. So i locked my device, following htc1guru return to stock guide guide, and then wiped all data, delvik, cache. Then i tried to use Windows RUU installer which failed after booting to grey htc sign. then it failed (usb connection error) i tried again, unknown error. so i unlocked my device and tried to boot my CNM again but i was stuck on loading screen (arrow circling around CNM's head).
so i flashed TWRP recovery and tried to flash ViperOne ROM but i couldnt open sdcard in my recovery. It says E:failed to mount sdcard (sdcard is internal storage called sdcard) but i couldnt, then i tried to flash it using sideload, failed aswell. Now iam kind of stuck in my hboot v 1.54/ TWRP. and cannot flash ANY ROM. So i heard about S-OFF tried to do it manually - didnt work, use custom unlockers, S-OFFERS -didnt work.
I'am VERY grateful for ANY advice.
I guess i forgot something if u need more info i will try to reply as fast as possible.
Thank you!
Cesn3G said:
Hello,
SO it started when i used cyanogenmod installer app and windows app combined to easily install CNM. After half a year of using my phone suddenly stopped charging, when i wanted it to charge i needed to shut it down and press volume down combined with power button shortly, not to power it on. So i locked my device, following htc1guru return to stock guide guide, and then wiped all data, delvik, cache. Then i tried to use Windows RUU installer which failed after booting to grey htc sign. then it failed (usb connection error) i tried again, unknown error. so i unlocked my device and tried to boot my CNM again but i was stuck on loading screen (arrow circling around CNM's head).
so i flashed TWRP recovery and tried to flash ViperOne ROM but i couldnt open sdcard in my recovery. It says E:failed to mount sdcard (sdcard is internal storage called sdcard) but i couldnt, then i tried to flash it using sideload, failed aswell. Now iam kind of stuck in my hboot v 1.54/ TWRP. and cannot flash ANY ROM. So i heard about S-OFF tried to do it manually - didnt work, use custom unlockers, S-OFFERS -didnt work.
I'am VERY grateful for ANY advice.
I guess i forgot something if u need more info i will try to reply as fast as possible.
Thank you!
Click to expand...
Click to collapse
wooow, long sentence
two things:
1) check the Frequently Asked Question sticky page 3
about those "failed to mount" errors
2) "... After half a year of using my phone suddenly stopped charging, ....." -> this could be a hardware problem if it happened all by itself
nkk71 said:
wooow, long sentence
two things:
1) check the Frequently Asked Question sticky page 3
about those "failed to mount" errors
2) "... After half a year of using my phone suddenly stopped charging, ....." -> this could be a hardware problem if it happened all by itself
Click to expand...
Click to collapse
Thanks! I didnt find that thread before and it helped me solve, already thanked
Cesn3G said:
Thanks! I didnt find that thread before and it helped me solve, already thanked
Click to expand...
Click to collapse
no problem, my pleasure .... that thread (not mine, but nonetheless) is a sticky, so it's one of the first you should read
anyway, glad it fixed it, and if you dont mind marking this thread as [SOLVED], it would be nice