Database Develop

[SOLVED] Stuck on X - HELP!?

ADDING THE LINK HERE NOW : https://www.dropbox.com/s/it4ji9mlohfgagf/NexusOne-rescue-tools.zip
And please, a THANKS would be great if this helped you.
For some reason the phone one day just didn't boot. Was stuck on X logo.
We have tried alot... can't get into recovery, so flashed custom recovery, both RA and CWM... can't get into any of them, just stuck on X.
The phone was stock, and unrooted.
We managed to unlock bootloader via fastboot and root it.
Tried the PASSIMG.ZIP method - not working.
Any ideas?
.... please? =(
EDIT: Problem solved! Send me a PM if you're in the same seat, and i could send you all the files you need.
Oh, all you need is your FASTBOOT to work, no need for ADB, since it didn't work for me either.
EDIT #2:
The reason is that i have a file (ADB, and all the *.img's) needed on my server, and don't wanna post the link here so that's why i have done it thru PM.
But i'll update the first post and just delete the link, so when anyone needs it they can PM me.
So far (2012-02-10) 14 phones confirmed back up running, including mine. Got 2 unconfirmed, and just sent 5 PM's to guys with the same problem.
*** PM ME FOR THE LINK TO THE *.ZIP ***
Unzip, open an command promt, and:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash radio radio.img
fastboot flash system system.img
do the commands in that order, and when you are done reboot the phone
and see if it boots.
if NOT: keep on flashing ONLY the boot.img again and again until it
boots. it seems like the boot partition is corrupted and may need alot
of flashing until it works.
i think i flashed like 100 times before it booted. =)
There is also another recovery in that zip... RA's recovery. You can also try that one, no harm done!
Once you get it to boot, you will have FroYo 2.2 installed.
If you got it to boot with recovery.img just let android update to latest (2.3.7?)
If you have RA's recovery, just flash back recovery.img or you wont be able to upgrade to 2.3.7 "the stock way"

Can you boot without sd card?
Maybe Hardware--

rugmankc said:
Can you boot without sd card?
Maybe Hardware--
Click to expand...
Click to collapse
Sorry, no. Not booting when i remove sdcard either.
:/

May be hardware

rugmankc said:
May be hardware
Click to expand...
Click to collapse
How do i find out?
When we searched yesterday (google), we found some ppl who had fixed it, now i can't find those pages again..
So anyone here who knows what to try?

I've been in a similar situation before and just kept fastboot flashing system, recovery, and boot, and eventually I recovered the phone...

I assume since you mentioned that you unlocked the bootloader, that you can get into fastboot? If so, flash a custom recovery (I'd recommend CWM since it includes an option to wipe the system partition) and boot into it.
Code:
fastboot flash recovery "c:\location\to\recovery.img
fastboot boot recovery "c:\location\to\recovery.img
If you can get that far, wipe your /system partition and do a factory reset. Then install CM7 (or whatever ROM you want) and gapps.

bassmadrigal said:
I assume since you mentioned that you unlocked the bootloader, that you can get into fastboot? If so, flash a custom recovery (I'd recommend CWM since it includes an option to wipe the system partition) and boot into it.
Code:
fastboot flash recovery "c:\location\to\recovery.img
fastboot boot recovery "c:\location\to\recovery.img
If you can get that far, wipe your /system partition and do a factory reset. Then install CM7 (or whatever ROM you want) and gapps.
Click to expand...
Click to collapse
Thanks!
But we have tried to fastboot system.img, boot.img and recovery.img
Still stuck on X.
Is that code any different perhaps?
I can't try that now, that's why i ask instead of try it =)

All the commands that I posted are supposed to do is install a custom recovery and then boot into it. From recovery, you need to wipe your device by wiping the /system partition and doing a Factory Reset/Data Wipe. Then install whatever ROM you want to.
I've never tried using fastboot to install the system image, so I can't comment on that at all.

O M G!!!
i actually got the phone up and running!! everything is working now, i'm just too awesome
If anyone is interested, i could find out what i did, and which files i flashed, etc etc.

Just an update:
(mostly to bump this)
3 more ppl who had the same problem has now got this fixed

Woa, check your PM

Check you inbox buddy! Tack på förhand

mrBira said:
Just an update:
(mostly to bump this)
3 more ppl who had the same problem has now got this fixed
Click to expand...
Click to collapse
Is it an illegal method, or is there another reason why a fix like this you're only sharing by PM instead of posting it here? I sent you a PM over 24hrs ago and haven't heard back yet. I would think making one helpful post would be much easier than getting irritated at replying to each of 10-100+ PMs

NismoDrift240 said:
Is it an illegal method, or is there another reason why a fix like this you're only sharing by PM instead of posting it here? I sent you a PM over 24hrs ago and haven't heard back yet. I would think making one helpful post would be much easier than getting irritated at replying to each of 10-100+ PMs
Click to expand...
Click to collapse
HEHEH... illegal
No, ofc not (is there any way to fix a phone that's not legal?).
The reason is that i have a file (ADB, and all the *.img's) needed on my server, and don't wanna post the link here so that's why i have done it thru PM.
But i'll update the first post and just delete the link, so when anyone needs it they can PM me.
So far 14 phones confirmed back up running, including mine. Got 2 unconfirmed, and just sent 5 PM's to guys with the same problem.

mrBira said:
HEHEH... illegal
No, ofc not (is there any way to fix a phone that's not legal?).
The reason is that i have a file (ADB, and all the *.img's) needed on my server, and don't wanna post the link here so that's why i have done it thru PM.
But i'll update the first post and just delete the link, so when anyone needs it they can PM me.
So far 14 phones confirmed back up running, including mine. Got 2 unconfirmed, and just sent 5 PM's to guys with the same problem.
Click to expand...
Click to collapse
That makes perfect sense, I'm the same way. Thanks for getting back to me, here's to hoping I make 15...

same prob.
I sent you a PM, bro. Get back to me as soon as you can! Thanks!

Nexus One recovery boot error
PM sent. Thank you for your assistance.

i would like to know how to you solve the problem

No recovery for unrooted fones
first root ur phone using passimg.img
and fastboot flash bootloard oem unlock etc
and then try to flash a recovery using
fastboot flash recovery recovery.img
then u r done
Thank if it helps u

[ROM] Stock Rooted 5.1.1

Since pepole have no knolege of what they are doing and kind of blame me for it i will not provide the images anymore.
Please lock this thread.

Thank you so much!
Question: Do we have to flash the stock recovery after flashing the rooted system image? I prefer to have TWRP recovery anyways.

akarol said:
Thank you so much!
Question: Do we have to flash the stock recovery after flashing the rooted system image? I prefer to have TWRP recovery anyways.
Click to expand...
Click to collapse
worst case just reflash TWRP =]

akarol said:
Thank you so much!
Question: Do we have to flash the stock recovery after flashing the rooted system image? I prefer to have TWRP recovery anyways.
Click to expand...
Click to collapse
You can use whatever recovery you would like, the system image does not affect the recovery in any way.

Thanks - flashed your bootloader files which got me out of a never ending boot animation issue

j32olger said:
Thanks - flashed your bootloader files which got me out of a never ending boot animation issue
Click to expand...
Click to collapse
The bootloop have nothing to do with my bootloader files, they are completley stock from the ota file!
If you installing the new bootloader files on older roms you are asking for troubles.
Boot the watch in bootloader mode and flash the files as described and you watch will work.
Af if it bootlooping run a "Fastboot -w" after flashing.

Greetings, Is the newly released OTA compatible with your rom?

drmcatchr said:
Greetings, Is the newly released OTA compatible with your rom?
Click to expand...
Click to collapse
No ota files will only work with stock untouched rom.

bunny0007 said:
No ota files will only work with stock untouched rom.
Click to expand...
Click to collapse
Are you planning on releasing a pre-rootet image of the latest ota?
Would be greatly appreciated!

2k4ever said:
Are you planning on releasing a pre-rootet image of the latest ota?
Would be greatly appreciated!
Click to expand...
Click to collapse
Have added it today.

I tried this using the update (LCA44B) and now the watch doesn't even turn on. No LG logo or anything.

GuiyeC said:
I tried this using the update (LCA44B) and now the watch doesn't even turn on. No LG logo or anything.
Click to expand...
Click to collapse
And you did follow the instuctions?7
Flash bootloader stuff
Flash system image
Flash boot image
Have testet it serval times without errors.

bunny0007 said:
And you did follow the instuctions?7
Flash bootloader stuff
Flash system image
Flash boot image
Have testet it serval times without errors.
Click to expand...
Click to collapse
Yep, just like in the steps, the thing did show a FAILED (anti-rollback) when flashing the 'aboot'. I just used everything that was on the zip, now the watch doesn't even show the LG logo, I've tried plugging it on and off and keeping the reset button pressed for a while. I really don't know what else to try.
I'm waiting for it to run out of battery, but I don't even know if it's "on".

GuiyeC said:
Yep, just like in the steps, the thing did show a FAILED (anti-rollback) when flashing the 'aboot'. I just used everything that was on the zip, now the watch doesn't even show the LG logo, I've tried plugging it on and off and keeping the reset button pressed for a while. I really don't know what else to try.
I'm waiting for it to run out of battery, but I don't even know if it's "on".
Click to expand...
Click to collapse
Did just ran it on my own watch and everything working.
If you aboot fails flashing your watch might have another problem, i assume that your watch have an unlocked bootloader??

bunny0007 said:
Did just ran it on my own watch and everything working.
If you aboot fails flashing your watch might have another problem, i assume that your watch have an unlocked bootloader??
Click to expand...
Click to collapse
Yes, it had the boot loader unlocked, and I can't try again flashing the aboot because I can't get it to recovery mode or fast boot mode or anything.

Who can I get the images from?

bunny0007 said:
Since pepole have no knolege of what they are doing and kind of blame me for it i will not provide the images anymore.
Please lock this thread.
Click to expand...
Click to collapse
By people, do you mean 1 person ???
Pretty unfair for other, isn't it ?

I am looking for bootloader files for the G Watch R to flash over what I believe to be a corrupt bootloader on my device. It will only boot when on the charging stand, and so far I have only been able to get it to boot to 5.0.1 successfully. Once the device tries to pull down the OTA update it reboots and proceeds to run the update and then it fails and powers off.
Currently I can access fastboot and I can get it to boot a stock recovery and twrp with the 5.0.1 boot.img flashed to my device.

Can anyone who has downloaded the original package from this thread PM me the files? I need to reflash my bootloader files to attempt to fix a booting issue with my watch. Any help would be appreciated and I will not hold anyone accountable if I hard brick my device.

fnj00 said:
Can anyone who has downloaded the original package from this thread PM me the files? I need to reflash my bootloader files to attempt to fix a booting issue with my watch. Any help would be appreciated and I will not hold anyone accountable if I hard brick my device.
Click to expand...
Click to collapse
Hi there ,
Why don't you try this one ??
http://forum.xda-developers.com/g-w...edroid-r-urbane-port-v1-0-0-june-6th-t3128850

Stuck in recovery mode

I was trying to fix my google play "no connection error" but it didn't work so i just reset my phone as a last resort to try and fix this problem. It restarted in recovery mode i thought this was just a procedure and i just hit reboot -> system. it rebooted again into recovery mode i checked if there were any wtuck volume rockers but there aren't any help?
(FYI: one plus 3T: Rooted)
(FYI: link to what i used to try and fix my google play store:https: //forum.xda-developers.com/showthread.php?t=2273994)

What recovery are you running? Stock or TWRP?

bealer said:
What recovery are you running? Stock or TWRP?
Click to expand...
Click to collapse
TWRP

And telling TWRP to boot system just bring you back into TWRP?
Hmm... sounds like you might need to reflash whatever rom you were on.

bealer said:
And telling TWRP to boot system just bring you back into TWRP?
Hmm... sounds like you might need to reflash whatever rom you were on.
Click to expand...
Click to collapse
already did that but still brings me back into TWRP

TrappleV3 said:
already did that but still brings me back into TWRP
Click to expand...
Click to collapse
This happened to me. I installed custom rom then I went into fastboot and installed stock recovery. I would search in this forum for the stock recovery img file. Once installed, I rebooted and it loaded the rom. I had this problem on the latest twrp version. I installed the previous twrp and I am all good now.

Droid-2 said:
This happened to me. I installed custom rom then I went into fastboot and installed stock recovery. I would search in this forum for the stock recovery img file. Once installed, I rebooted and it loaded the rom. I had this problem on the latest twrp version. I installed the previous twrp and I am all good now.
Click to expand...
Click to collapse
you have a link to the file because i can't seem to find it. But thank you anyway for your help.

TrappleV3 said:
you have a link to the file because i can't seem to find it. But thank you anyway for your help.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015

mximer said:
https://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015
Click to expand...
Click to collapse
Thank You.

Issue has been resolved. OP is my little cousin who's been messing around a bit too frantically [emoji14]
I restored his device with the unbrick tool by Haris K., all's peachy again. There are still some issues with TWRP for 3T, doesn't run nearly as smooth as on the OPO. It completely failed to restore any working system (both from backup or from reflashing). Sideloading seemingly worked, but rebooted to recovery again, adb push only resulted in errors. Are there any tweaked TWRP releases that can do better?
Cooked with Resurrected bacon!

Phone stuck on color lines at bootup

Hello i tried to flash new roms but i think my phone is bricked now. i have tried to unbrick. Every time i flash a rom it says done after 1 second. So i know its not flashing properly. before i go buy a new phone can someone help me out please.
Thank you so much

lonster27 said:
Hello i tried to flash new roms but i think my phone is bricked now. i have tried to unbrick. Every time i flash a rom it says done after 1 second. So i know its not flashing properly. before i go buy a new phone can someone help me out please.
Thank you so much
Click to expand...
Click to collapse
Tell us what exactly you did and what exactly fastboot is outputting

Benjamin_L said:
Tell us what exactly you did and what exactly fastboot is outputting
Click to expand...
Click to collapse
i unlocked it which worked and i could still get back into the phone. Then i installed twrp recovery on the phone and then installed from there DM verity disabler. after that is was bricked. now i can not even get back into twrp i just freezes. i am still able to get into fastboot that is all.

lonster27 said:
i unlocked it which worked and i could still get back into the phone. Then i installed twrp recovery on the phone and then installed from there DM verity disabler. after that is was bricked. now i can not even get back into twrp i just freezes. i am still able to get into fastboot that is all.
Click to expand...
Click to collapse
Then you can still flash the fastboot roms. Guides are found here. Or use the included script.
Why would I want to disable dm verity after all?

Benjamin_L said:
Then you can still flash the fastboot roms. Guides are found here. Or use the included script.
Why would I want to disable dm verity after all?
Click to expand...
Click to collapse
thanks can you please maybe provide a link for me please for both methods.

i got the same result when i rebooted the phone after trying to clear the cache in chrome browser ...

HELP! My device is corrupt

I tried re-rooting after updating and now it says Your device is corrupt. It cant be trusted and may not work properly.
It freezes on the Google if I continue. Not sure what happened.
Any remedy for this?

features99 said:
I tried re-rooting after updating and now it says Your device is corrupt. It cant be trusted and may not work properly.
It freezes on the Google if I continue. Not sure what happened.
Any remedy for this?
Click to expand...
Click to collapse
Need more specific details, like specific method of rooting, version of Magisk, updating to what?, etc...

Unfortunately you may have to flash the factory image and start all over again if no one else can help you with it. At least you have the option. Sucks when that happens.

I mean... the first message just sounds like the bootloader unlocked message which would show up even if you could fully boot in.
I wouldn't factory reset over just this though. Flash the factory image without the -w parameter in flash-all.bat

jljtgr said:
I mean... the first message just sounds like the bootloader unlocked message which would show up even if you could fully boot in.
I wouldn't factory reset over just this though. Flash the factory image without the -w parameter in flash-all.bat
Click to expand...
Click to collapse
I agree. Flashing the factory image without the -w would likely allow him to boot up again. But it would be helpful for that person to tell us exactly what they did so we can help them avoid it in the future, e.g. maybe they flashed the stable version of Magisk instead of Beta or Canary, or maybe they tried a direct install instead of patching the boot image, etc...

Ok guys sorry for not giving more details.
So I rooted awhile back when I got the phone, havent updated in a long time so I thought it was time.
I updated to Android 11 with the latest security updates and tried to re-root.
I updated Magisk to the latest version and patched the matching boot image, but Im pretty sure I used the stable version.
I should of researched it more as Im reading the beta method is the way to go.
I opened the command prompt with the following commands:
cd Downloads
cd fastboot
fastboot flash boot magisk_patched.img
fastboot reboot
Seems like everything went ok...
Then afterwards got the corrupted message and Google hang.
I can still load to fastboot but recovery or rescue doesnt work.
So where can I go from here? I only rooted a few phones in the past so Im still learning and reading lots of posts.
Also I didnt modify my own boot image, but one I downloaded from a matching build.
I really appreciate the help

features99 said:
Ok guys sorry for not giving more details.
So I rooted awhile back when I got the phone, havent updated in a long time so I thought it was time.
I updated to Android 11 with the latest security updates and tried to re-root.
I updated Magisk to the latest version and patched the matching boot image, but Im pretty sure I used the stable version.
I should of researched it more as Im reading the beta method is the way to go.
I opened the command prompt with the following commands:
cd Downloads
cd fastboot
fastboot flash boot magisk_patched.img
fastboot reboot
Seems like everything went ok...
Then afterwards got the corrupted message and Google hang.
I can still load to fastboot but recovery or rescue doesnt work.
So where can I go from here? I only rooted a few phones in the past so Im still learning and reading lots of posts.
I really appreciate the help
Click to expand...
Click to collapse
I would try fastboot flashing the stock boot image first.

If Magisk says you're on a version before 21.0, the patched image won't work for Android 11. Stable is currently 20.4 released in March.

Lughnasadh said:
I would try fastboot flashing the stock boot image first.
Click to expand...
Click to collapse
tried that..it didnt work

features99 said:
tried that..it didnt work
Click to expand...
Click to collapse
Then I would flash the December factory image using fastboot but with the -w removed from the flash-all.bat file so it won't erase your data.

Lughnasadh said:
Then I would flash the December factory image using fastboot but with the -w removed from the flash-all.bat file so it won't erase your data.
Click to expand...
Click to collapse
Yes that worked, didn't know about edited the .bat to remove the the -w and saving all data. Back in business for now...
Thank you all for expertise, much appreciated!

features99 said:
Yes that worked, didn't know about edited the .bat to remove the the -w and saving all data. Back in business for now...
Thank you all for expertise, much appreciated!
Click to expand...
Click to collapse
No problem. Glad you got it going. As I see you've already found out, Magisk Beta 21.1 is a good way to go. Canary as well but then you may run into problems in the future when Canary gets updated since those are "cutting edge" builds.