Related
ok i have installed many roms for my g1, have had the hero for sprint for awhile and everytime I try to do the fresh rom i get errors, ive tried wiping it then installed the update.zip, tried to just overwrite it still errors which always forces me to nandroid restore,
I can do the eclair 2.1 no problem, but fresh always gives me errors. atm i have a rooted sprint htc hero, no custom rom on it atm. any help?
What kind of errors?
Have you tried re-downloading the ROM?
well when i first boot it up i does the "fresh" sound and goes though all the boot ups and says ok, then gets to the last one that says like boot up fresh o somethingthen [wait] i wait, it eventually starts up but mainly alot of force closes,
im thinking of unrooting my phone back to stock and I have been looking at pre kitchen, so once my phone is stock, i just plug my phone in and do auto-root? and thats all i have to do?
because im thinking of going stock then auto rooting for ease.
samrozzi said:
well when i first boot it up i does the "fresh" sound and goes though all the boot ups and says ok, then gets to the last one that says like boot up fresh o somethingthen [wait] i wait, it eventually starts up but mainly alot of force closes,
im thinking of unrooting my phone back to stock and I have been looking at pre kitchen, so once my phone is stock, i just plug my phone in and do auto-root? and thats all i have to do?
because im thinking of going stock then auto rooting for ease.
Click to expand...
Click to collapse
The long wait after the first flash is normal and you will see that every almost every rom after the first boot. If your phone is totally stock (you mentioned you tried wiping data) then you definitely shouldn't be getting FC's.
Did you wipe your data after using the 2.1 rom and before flashing fresh rom? That would be the easier way to go about things. But using the RUU to flash back to totally stock and starting over wouldn't hurt either.
yeah i have wiped everything and tried, i mean i rooted and hacked my g1 for over a year numerous times, so idk. just quick questions on how to revery back to stock because this have never done. im downloading the RUU 1.56 from here
http://geekfor.me/news/sprint-ruu-fails/
not really sure on steps to go back to stock once I get that file?
and also new to pre kitchen, once my phone is back to stock and unrooted etc... do i just plug in phone to pc, start pre kitchen and click auto rooter?
samrozzi said:
yeah i have wiped everything and tried, i mean i rooted and hacked my g1 for over a year numerous times, so idk. just quick questions on how to revery back to stock because this have never done. im downloading the RUU 1.56 from here
http://geekfor.me/news/sprint-ruu-fails/
not really sure on steps to go back to stock once I get that file?
and also new to pre kitchen, once my phone is back to stock and unrooted etc... do i just plug in phone to pc, start pre kitchen and click auto rooter?
Click to expand...
Click to collapse
Once you download that file just extract it and run it. It will walk you through it from there and once it's done you will have a stock from-the-factory Hero. Once you get it booted up and stuff then open the kitchen (get 0.2) and go under the help menu and run the diagnostic tests. As long as sendkeys, adb, and rooting tools pass then go ahead and go to the auto rooter and that's it. If any of those 3 fail then you may not be able to use the rooter.
hmm while trying to revert back to stock im getting a 170 error saying no usb connection which is strange.
not sure if i have to mount her or not because it is connected to my computer
samrozzi said:
hmm while trying to revert back to stock im getting a 170 error saying no usb connection which is strange.
Click to expand...
Click to collapse
Try closing the RUU, putting your phone in to fast boot and then checking device manager on your computer to make sure you aren't missing any drivers. If you aren't then start the RUU again.
To go in to fastboot power your phone completely down. Then hold volume down and power. This should get you a screen with 3 skateboarding androids. And then I believe it is volume up for fastboot. Make sure it's plugged in to your comp and confirm device manager is clean, and then run RUU.
samrozzi said:
hmm while trying to revert back to stock im getting a 170 error saying no usb connection which is strange.
not sure if i have to mount her or not because it is connected to my computer
Click to expand...
Click to collapse
I had that problem, and installing HTC Sync fixed it.
ok foundout its because i have windows 7. I dont have another computer with vista or xp.anything I can do?
samrozzi said:
ok foundout its because i have windows 7. I dont have another computer with vista or xp.anything I can do?
Click to expand...
Click to collapse
I have Windows 7, and both HTC Sync and the pre-kitchen work fine on my computer. What is it that you think Windows 7 is preventing you from doing?
samrozzi said:
ok foundout its because i have windows 7. I dont have another computer with vista or xp.anything I can do?
Click to expand...
Click to collapse
A couple of things.
Install HTC Sync or go get the Android SDK to install the ADB driver.
Then run RUU
Boot the phone into fastboot Power off, hold down volume down button while phone is booting back up.
When you are in Fastboot, press Volume up once.
Then plug the USB in and run RUU.
I have Win7 32 and x64 and have been able to do all ADB functions fine with both machines, its a little more cumbersome, but not an issue.
TTG flashing issues
I had TTG and was trying to reflash to MODACO. The Rom wouldn't reflash. I wiped, factory reset.... Just boot looped or froze. A lot of errors and force closes. I'm running GUTTED 1.6 now with no problems. Why would there have been an issue trying to flash MODACO...?
greetings...i've read far too many threads on not being able to boot into "recovery" and "download" and haven't found anything to fix me...
i can successfully get into "recovery" but when i try to reinstall the packages it starts to run a recovery with Clockworkmod etc...it stops and reboots into recovery...this will go on and on...
now when i try to boot into "download" i can't, i've tried many methods none work.
any help?
rooted/clockwork recovery/nandroid back up prior to trying the vibrant7
same problem here...
http://forum.xda-developers.com/showthread.php?p=7904808#post7904808
The K-Zoo Kid said:
same problem here...
http://forum.xda-developers.com/showthread.php?p=7904808#post7904808
Click to expand...
Click to collapse
sweet...well, not sweet...PM me if you find a fix: i'll do the same, i have a replacement on the way via t-mobile.
for the record, i've successfully gotten in to download mode and used Odin to get back to factory...twice, once for fun and once for resurrection...i don't know what went wrong, except while nandroiding maybe i backed up a bogus recovery rom before i flashed. i can't get past Vibrant, and i don't even see the battery recharge display either when i usb, i'm letting the battery run down to try and get to the green battery icon to try a "download" mode??? i've read of a move while you see the charging screen but i haven't been able to get there... oh well, live and learn. i am also searching for a way to boot from the removable sd card that has a system or recovery rom on it..nothing yet.
also, i've read people discussing newer models being blocked from download...well like i said i've done this with this phone before but i got a new SIM last week and this is the first attempt with the new SIM???? maybe a coincidence...
take battery out, plug in usb to pc, hold vol up n down, replace battery, boom download mode.
dsuycott said:
sweet...well, not sweet...PM me if you find a fix: i'll do the same, i have a replacement on the way via t-mobile.
for the record, i've successfully gotten in to download mode and used Odin to get back to factory...twice, once for fun and once for resurrection...i don't know what went wrong, except while nandroiding maybe i backed up a bogus recovery rom before i flashed. i can't get past Vibrant, and i don't even see the battery recharge display either when i usb, i'm letting the battery run down to try and get to the green battery icon to try a "download" mode??? i've read of a move while you see the charging screen but i haven't been able to get there... oh well, live and learn. i am also searching for a way to boot from the removable sd card that has a system or recovery rom on it..nothing yet.
also, i've read people discussing newer models being blocked from download...well like i said i've done this with this phone before but i got a new SIM last week and this is the first attempt with the new SIM???? maybe a coincidence...
Click to expand...
Click to collapse
Alright i will doo... and you restored from odin after the problem started...?
I flashed the stock kernel and everything is good... Its in the OP of Eugenes rom.
98classic said:
take battery out, plug in usb to pc, hold vol up n down, replace battery, boom download mode.
Click to expand...
Click to collapse
thanks for the reply...i've done that a bazillion times...won't go, i even went to the tmobile store in my hood and no go on their end...
The K-Zoo Kid said:
Alright i will doo... and you restored from odin after the problem started...?
Click to expand...
Click to collapse
not after, i had restored from odin about two weeks ago...
Did you read my post about The stock kernal in eugenes original post?
Sent from my SGH-T959 using XDA App
The K-Zoo Kid said:
Did you read my post about The stock kernal in eugenes original post?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
yes(but i'm over saturated right now, i might have missed something) ...i'm dead in the water, i can't get to the point of anything seeing my device...my computer won't see it except as unknown usb device, no partitions show up, adb doesn't recognize it in any way...maybe i'm a [email protected], but i don't see anyway to flash it without at least getting in to download mode, or somehow pushing a .zip at the sd for a recovery??? technically figuring out that stuff is beyond my remaining brain cells...this seems like a dicey way for the phone to rely on when restoring to factory.... it would be nice to have the device look at All available partitions, internal/removable, for a recovery system or have an altogether different sd in the phone for a -R dedicated recovery volume....don't know, i'm a noob at this android stuff sooo....
Hi everybody!
I'm trying to buy a used Nexus One, good price, but the owner claims that the phone "continuously reboots to "X" screen." but that IT can be fixed flashing the rom.
Is it true?
I'm reading on the internet that having the nexus one loop rebooting is a somehow common problem, and people got it fixed flashing the rom, or by moving some shifted pins on the battery. Do you guys think it's something reparable? Everybody that had this issue solved it? Or I risk that the phone is actually broken, and I might be buying a phone that I will not be able to use?
Thanks!
fastboot
just check for fastboot. the rest is easy cheeze.
how much is a good deal ?
unlocked $300 (cad)
What should I check? Instruct me plz, I never had a nexus one or even a Droid phone before ... (coming from 2 years old HTC cruise, with WM 6.5 with an XDA rom ....)
If I meet the guy, how to I check that hes not selling me a bricked nexus lol ?
Installing a new rom will fix it
Sent from my IPhone 4 using XDA App
Amritttt said:
Installing a new rom will fix it
Sent from my IPhone 4 using XDA App
Click to expand...
Click to collapse
are you 100% ?
I dont mind working on it, I just want to make sure that it is reparable via software/roms.
ppl plz tell yours, im just about calling this guy, really dont wanna waste $300
what is its restarts so much, that I cant flash the rom or something? there's no way that that could be the case, right?
sold ... goddamit lol But I'll get one one way or another
I was having this happen to me a lot. I moved in to a new place with no cable or internet yet, so my N1 was under extremely heavy use. And when it was warm, it would get both the touch screen problem and the random reboots.
I was using pershoots 2.35 Kernal. I went back to the stock kernal and the phone has since been running a lot cooler. Zero reboots, touch screen responds correctly. I take the stock kernal stability over an OC kernal any day.
It's a kernel issue that can most likely be fixed by flashing a new
ROM/Kernel, however there is always a small chance that it is triggered by faulty hardware.
My Nexus had this Problem Was unfixable by software. Hardware defect. I wouldn't buy.
Still waiting for my swap unit
i had a friend with a similar problem. He rooted the phone with the 1-click root app from the market, he then installed ROM manager from the market and try to flash Cyanogen mod ROM, afterward the phone went black. The only thing happen to the phone now is the X screen and its keep boot loop. I tried went to fastboot, works fine, then I tried to go to Recovery but it restart right afterward!!!
Now how am I suppose to wipe, or flash new rom without getting into the recovery? I got to fastboot and plugged in the USB cable and tried to ran terminal but it was unsucessful. I tried to copy some new files to the phone via adb command but keep getting the error "BootMagic failed".
Any help?
xxlikquidxx said:
i had a friend with a similar problem. He rooted the phone with the 1-click root app from the market, he then installed ROM manager from the market and try to flash Cyanogen mod ROM, afterward the phone went black. The only thing happen to the phone now is the X screen and its keep boot loop. I tried went to fastboot, works fine, then I tried to go to Recovery but it restart right afterward!!!
Now how am I suppose to wipe, or flash new rom without getting into the recovery? I got to fastboot and plugged in the USB cable and tried to ran terminal but it was unsucessful. I tried to copy some new files to the phone via adb command but keep getting the error "BootMagic failed".
Any help?
Click to expand...
Click to collapse
all is not lost if you can still get into hboot:
Have you tried to restore these original files via adb?
boot boot.img
recovery.img
system.img
I have this problem now...
It keeps on rebooting and rebooting ... and just comes not forther than the flashing X..
I tried system wipe but this didnt help ( I installed a battery widget which wasn't for my rom)
how can i restore my nexus now?
Pleas help!
Edit: Found a way...
Unlock you phone, fastboot, clockworkmod(?) recovery and the select the nandroid backup...
about passimg (see lower) i have no clue
passimg FRG33...
Sent from my Nexus One using XDA App
Even though solved, something to keep in mind: Its probably a ROM (or kernel issue as they said), but I had a revolving X due to a bad battery too.
it can be solved
ViSK said:
Hi everybody!
I'm trying to buy a used Nexus One, good price, but the owner claims that the phone "continuously reboots to "X" screen." but that IT can be fixed flashing the rom.
Is it true?
I'm reading on the internet that having the nexus one loop rebooting is a somehow common problem, and people got it fixed flashing the rom, or by moving some shifted pins on the battery. Do you guys think it's something reparable? Everybody that had this issue solved it? Or I risk that the phone is actually broken, and I might be buying a phone that I will not be able to use?
Thanks!
Click to expand...
Click to collapse
4 color problem can be solved ..
Hello fellow internet users, I've been trying to resolve a problem I've been having with my Nexus 4 device, but given that I failed, I came here hoping somebody here could help me.
Recently I wanted to update CM Mod on my device (to the latest version supporting Android 4.3), but little did I know that it'd replace my recovery program from TWRP to ClockwordMod. Afterwards I proceeded to install Franco Kernel (r. 193) since from what I read it should have been compatible with my recently downloaded version of CM. After I flashed it, all the tints of blue on my screen turned into tints of orange/yellow (and vice versa). Afterwards I tried to fix it with flashing one of the supposedly stock kernels I found on the internet, however all it achieved was to make it unable for my phone to boot - now when I turn it on in normal mode all I see is a weird blue screen with intermittently flashing pink squares that create a checkered pattern. I tried to access the android root kit to unroot the phone and bring back the default kernel + rom, but so far I've been unable to access my phone from my PC. And in case you wonder, yes, I was stupid enough to not store any backups on the internal storage.
I hope there is a work around it, since I really need my phone to work , thanks in advance to whoever can provide me with some sound advice.
cubeth said:
Hello fellow internet users, I've been trying to resolve a problem I've been having with my Nexus 4 device, but given that I failed, I came here hoping somebody here could help me.
Recently I wanted to update CM Mod on my device (to the latest version supporting Android 4.3), but little did I know that it'd replace my recovery program from TWRP to ClockwordMod. Afterwards I proceeded to install Franco Kernel (r. 193) since from what I read it should have been compatible with my recently downloaded version of CM. After I flashed it, all the tints of blue on my screen turned into tints of orange/yellow (and vice versa). Afterwards I tried to fix it with flashing one of the supposedly stock kernels I found on the internet, however all it achieved was to make it unable for my phone to boot - now when I turn it on in normal mode all I see is a weird blue screen with intermittently flashing pink squares that create a checkered pattern. I tried to access the android root kit to unroot the phone and bring back the default kernel + rom, but so far I've been unable to access my phone from my PC. And in case you wonder, yes, I was stupid enough to not store any backups on the internal storage.
I hope there is a work around it, since I really need my phone to work , thanks in advance to whoever can provide me with some sound advice.
Click to expand...
Click to collapse
It sounds you had flashed a wrong version of kernel for JWR and JSS. If you can boot into recovery, then just download another ROM and save it to your phone. Wipe factory reset and then flash the new ROM.
taodan said:
It sounds you had flashed a wrong version of kernel for JWR and JSS. If you can boot into recovery, then just download another ROM and save it to your phone. Wipe factory reset and then flash the new ROM.
Click to expand...
Click to collapse
Thank you for the swift reply. The problem is, while I can boot into recovery, I can't save anything to my phone right now since I can´t access it from my PC.
cubeth said:
Thank you for the swift reply. The problem is, while I can boot into recovery, I can't save anything to my phone right now since I can´t access it from my PC.
Click to expand...
Click to collapse
Were you able to connect your phone to your PC prior to flashing the CM mod? If yes, then you can mount it while in recovery. If no, then I suggest you might want to spend some time reading the materials which software that you will need in order to connect your phone to your PC.
taodan said:
Were you able to connect your phone to your PC prior to flashing the CM mod? If yes, then you can mount it while in recovery. If no, then I suggest you might want to spend some time reading the materials which software that you will need in order to connect your phone to your PC.
Click to expand...
Click to collapse
Yes, the problem is that I did all the previous operations on another computer (on which nexus usb drivers were installed too), which I'll have access to in around 10 days. I was simply curious whether it is possible to find a workaround the fact that the computer I'm using currently doesn't recognise my device/can't install drivers, regardless of the mode my phone is in (bootloader, recovery or normal).
cubeth said:
Yes, the problem is that I did all the previous operations on another computer (on which nexus usb drivers were installed too), which I'll have access to in around 10 days. I was simply curious whether it is possible to find a workaround the fact that the computer I'm using currently doesn't recognise my device/can't install drivers, regardless of the mode my phone is in (bootloader, recovery or normal).
Click to expand...
Click to collapse
You'll have to install drivers manually.
Your problem is easily fixed. You don't need to wipe anything; that would be unnecessary. All you have to do is flash your ROM again. You can't use custom kernels with cm unless they are made specifically for it.
Sent from my Nexus 7 using Tapatalk
korockinout13 said:
You'll have to install drivers manually.
Your problem is easily fixed. You don't need to wipe anything; that would be unnecessary. All you have to do is flash your ROM again. You can't use custom kernels with cm unless they are made specifically for it.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thank you for your advice, I'll try to follow it and see if it works as soon as I've got back home.
I panicked and probably did something quite stupid...
So I tried to flash the new cyanogenmod rom to have a taste of kit kat, but then I had the status 7 error.
This never occurred to me before, I didn't keep a backup to fall back onto... ( yes, I am an idiot, I learned my lesson, the hard way)
Than the device won't boot, it shows the Google logo twice, and then goes into the clockwork mod, where you choose to flash roms
and I am stuck.
I tried Nexus Root Toolkit, doesn't help because my device is not booting up, no way can it install the drivers properly...
and I think I did something more ingenious... I just tried anything on the Toolkit, and I got my rooted Nexus 7 locked...
But it's still the same, I am stuck at the clockwork mod thing just as before... Wiped whatever I can. and even formatted the sdcard and system...
Some Android Wizard out there... Please help...
If at boot you go to recovery directly... You have had to flash new version of recovery in wrong partition. You must flash it last version of recovery with "fastboot flash recovery yourrecovery.IMG" (see 'recovery' as partition to flash). Then flash boot and system partitions from factory image (in XDA have you multiples threads about it) if you want to keep your data. If not, flash factory image from usual ways (this wipes your data) and then flash recovery like I say above.
After that, try to flash CM again.
PS: I recommend TWRP instead of CWM.
Sent from my Nexus 7 (grouper) using Tapatalk.
but its more serious than that... My computer doesnt recognize the tablet because of some driver issues... I am not sure, at this moment, whether the USB debugging thing still works
i can only get to the clockwork mod page, bootloader and thats it.
I cant flash anything, I cant transfer files from the PC to tablet....
please, please help.
bump!,
Im in a similar boat. I bricked my tablet while trying to force an update. It wouldnt autoupdate (there was always an error about cant find zip file...) so I tied to install it with Skipsoft program. After 20 minutes i realize my computer has frozen....So I waited 2 hours and nada. So I had to reboot my desk top. At that time my tablet is now bricked....what do we do?
Vishnuisgod said:
bump!,
Im in a similar boat. I bricked my tablet while trying to force an update. It wouldnt autoupdate (there was always an error about cant find zip file...) so I tied to install it with Skipsoft program. After 20 minutes i realize my computer has frozen....So I waited 2 hours and nada. So I had to reboot my desk top. At that time my tablet is now bricked....what do we do?
Click to expand...
Click to collapse
hello friend.
1. we can pray
2. i think we have to look at some software that can do something more "fundamental" than wugus nexus tool kit, and communicate with the tablet
i am just guessing, i crashed my tablet, so....
dangercl0se said:
hello friend.
1. we can pray
2. i think we have to look at some software that can do something more "fundamental" than wugus nexus tool kit, and communicate with the tablet
i am just guessing, i crashed my tablet, so....
Click to expand...
Click to collapse
I think I got it!!!!!!!!!!
using the skipsoft,
first i did option 1, install usb settings; then
I used option #6 force recovery.. I think i did stock rom.
now Im update with kitkat and it updating to 4.4.2
Vishnuisgod said:
I think I got it!!!!!!!!!!
using the skipsoft,
first i did option 1, install usb settings; then
I used option #6 force recovery.. I think i did stock rom.
now Im update with kitkat and it updating to 4.4.2
Click to expand...
Click to collapse
hey
can you post links to where u got the stuff?
coz looks like the skipsoft homepage is not working
dangercl0se said:
hey
can you post links to where u got the stuff?
coz looks like the skipsoft homepage is not working
Click to expand...
Click to collapse
it was already on computer....
make sure you look for "android tool kit"....